WO2019214524A1

WO2019214524A1 - Resource allocation method and apparatus

Info

Publication number: WO2019214524A1
Application number: PCT/CN2019/085380
Authority: WO
Inventors: 赵亚利; 皮埃尔; 刘佳敏; 谌丽
Original assignee: 电信科学技术研究院有限公司
Priority date: 2018-05-09
Filing date: 2019-04-30
Publication date: 2019-11-14
Also published as: CN110475284A; CN110475284B

Abstract

A resource allocation method and apparatus, used to resolve the issue in the prior art in which no specific solution exists for a resource allocation method based on MDBV data transmission in a 5G system. In the embodiment of the present invention, a terminal and a network side device determine an MDBV corresponding to an object and a token bucket used for MDBV control, and allocate resources to the object according to the determined MDBV and the token bucket used for MDBV control. Data transmission resources are allocated according to a token bucket used for MDBV control, thereby ensuring that the amount of data sent by each QoS Flow does not exceed an MDBV limit, and eliminating, when a system is under heavy loading, the situation in which a delay-sensitive service preempts resources of other services.

Description

Method and device for resource allocation

The present application claims priority to Chinese Patent Application No. 201810438523.2, entitled "A Method and Apparatus for Resource Allocation", which is filed on May 9, 2018, the entire disclosure of which is incorporated herein by reference. In the application.

Technical field

The present invention relates to the field of wireless communication technologies, and in particular, to a method and apparatus for performing resource allocation.

Background technique

For the 5G NR (New Radio) system, the core network configures the QoS (Quality of Service) profile for each Flow. The RAN (Radio Access Network) performs QoS management based on the QoS profile configured by the core network for each Flow. One parameter in the QoS profile is 5QI (5G QoS Identifier, the fifth generation mobile communication system service quality identifier). MDBV (Maximum Data Burst Volume) is a parameter included in 5QI. The 5G NR system mainly supports three types of services: the first is eMBB (enhanced Mobile Broadband) service, the second is mMTC (massive machine type communication) service, and the third is URLLC. (Ultra-Reliable and Low Latency Communications) business.

Among them, the URLLC service has a relatively high latency requirement, so it is also generally called a Delay-Sensed GBR (Guaranteed Bit Rate) service. For the service, when the core network defines the QoS profile based on the flow, the 5QI generally includes the MDBV parameter. The MDBV indicates that the 5G access network needs to process the maximum data of a Flow within the time range of the PDB (Packet Delay Budget). Quantity, and 5QI can be standardized or non-standardized.

However, in the prior art, there is no clear solution for how to perform a resource allocation method based on MDBV data transmission for a 5G system.

Summary of the invention

The present invention provides a method and apparatus for resource allocation, which solves the problem that the resource allocation method based on MDBV data transmission in the 5G system in the prior art has no clear solution.

In a first aspect, the terminal determines an MDBV corresponding to the logical channel and a token bucket for MDBV control; and then performs resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control.

In the embodiment of the present invention, the terminal first determines the MDBV corresponding to the logical channel and the token bucket used for the MDBV control, and then performs resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control. In the embodiment of the present invention, the resources of the data transmission are allocated according to the token bucket used for the MDBV control, so that the amount of data sent by each QoS Flow does not exceed the MDBV limit, thereby avoiding the delay when the system load is heavy. Sensitive services seize resources from other businesses.

In some specific implementations, after determining that the logical channel is established, the terminal determines an MDBV corresponding to the logical channel and a token bucket for MDBV control; and/or the terminal needs to receive the network-side device to transmit based on the MDBV. After the notification of resource allocation, the MDBV corresponding to the logical channel and the token bucket for MDBV control are determined.

In some implementations of the specific point, the terminal determines the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel at the MAC (Medium Access Control) layer.

In some implementations of the specific point, if the Flow and the logical channel adopt a 1:1 mapping, the terminal uses the MDBV corresponding to the Flow as the MDBV corresponding to the logical channel; or

If the flow and the logical channel adopt the M:1 mapping, the terminal uses the sum of the MDBVs corresponding to the Flows that can be mapped to the logical channel as the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel; or

If the Flow and the logical channel adopt the M:1 mapping, the terminal will use the sum of the MDBVs corresponding to the Flows actually mapped to the logical channel as the MDBV corresponding to the logical channel according to the Flow and logical channel mapping relationship; M is a positive integer.

In the embodiment of the present invention, the terminal determines the MDBV corresponding to the logical channel according to different situations, so that the resource allocation is ensured when the resource is allocated, and the delay sensitive service is prevented from preempting resources of other services.

In some implementations, before the terminal determines the MDBV corresponding to the object through the MAC layer, the terminal needs to notify the mapping relationship between the MAC layer Flow and the logical channel through a SDAP or RRC (Radio Resource Control) layer; or

The terminal notifies the mapping relationship between the MAC layer Flow and the logical channel and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or

The terminal notifies the MAC layer to actually map to the flow of the logical channel through the SDAP layer; or

The terminal notifies the MAC layer to actually map to the flow of the logical channel and the MDBV corresponding to the QFI through the SDAP layer; or

After the terminal device notifies the MDBV corresponding to the logical channel of the MAC layer through the SDAP layer, the MDBV corresponding to the object is determined by the MAC layer.

In the embodiment of the present invention, since the terminal is the MDBV corresponding to the logical channel determined by the MAC layer, but the MAC layer does not know the corresponding mapping relationship, multiple ways of notifying the MAC layer are introduced, which is more diverse and guaranteed. The terminal can determine the MDBV corresponding to the logical channel at the MAC layer.

In the embodiment of the present invention, since the terminal is the MDBV corresponding to the logical channel determined by the MAC layer, but the MAC layer does not know the corresponding mapping relationship, multiple manners of notifying the MAC layer are introduced to ensure that the terminal can determine the logic at the MAC layer. The MDBV corresponding to the channel.

In some implementations, the size of the token bucket for MDBV control is the MDBV corresponding to the logical channel. Determining, by the terminal, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and using the difference between the size of the token bucket and the M as the The number of available tokens in the token bucket corresponding to the logical channel; where N is the scheduling moment, and the PDB is the packet delay budget corresponding to the logical channel.

In some specific implementations, the terminal determines the PDB corresponding to the logical channel by:

Determining, according to the logical channel and the flow mapping relationship, a 5QI corresponding to all flows that are mapped to the logical channel or a 5QI corresponding to all flows that are actually mapped to the logical channel; determining a maximum PDB according to the 5QI corresponding to the Flow as the The PDB corresponding to the logical channel.

In the embodiment of the present invention, the number of tokens actually used in the time slot (N-PDB, N) within the token bucket for the MDBV control is determined according to the token bucket size used for the MDBV control and the logical channel is determined for the MDBV control. Determining the number of available tokens in the token bucket corresponding to the logical channel, and performing resource allocation according to the number of available tokens in the token bucket corresponding to the determined logical channel, which fully ensures that the amount of data sent by each QoS Flow is not The MDBV limit is exceeded, so that the delay-sensitive service can seize resources of other services when the system is heavily loaded.

In some specific implementations, for the logical channel with MDBV requirements when allocating resources:

1: The terminal sorts logical channels with available PBR tokens and data transmission requirements according to logical channel priority descending order, and then performs first round resource allocation on each logical channel based on PBR, and updates each logic simultaneously. The number of tokens in the PBR token bucket corresponding to the channel, and the number of available tokens in the MDBV token bucket corresponding to the logical channel after the PBR-based resource allocation is completed for the logical channel with the MDBV requirement;

2: After determining that there are remaining resources, the terminal performs a second round of resource allocation in descending order of logical channel priority for all logical channels having data transmission requirements:

For a logical channel with MDBV requirements, the logical channel allows the amount of data to be allocated in the second round of resource allocation process to take the logical channel for the number of available tokens in the token bucket controlled by the MDBV and the logic The channel has a smaller value of the data of the resource to be allocated, and performs resource allocation on the logical channel; if the logical channel that needs to be allocated is a logical channel that is not required by the MDBV, the terminal currently allocates resources according to the logical channel. The amount of data is allocated to the logical channel.

3: If the terminal determines that there are remaining resources, allocate resources to the remaining to-be-transmitted data in descending order of all logical channel priorities with data transmission requirements until the resources are exhausted or the data to be transmitted of all logical channels are allocated. Resources.

And when performing resource allocation, for logical channels without MDBV requirements:

1: The terminal sorts logical channels with available PBR tokens and data transmission requirements according to logical channel priority descending order, and then performs first round resource allocation on each logical channel based on PBR, and updates each logic simultaneously. The number of tokens in the PBR token bucket corresponding to the channel, and the number of available tokens for the MDBV control after the PBR-based resource allocation is completed for the logical channel with the MDBV requirement;

For a logical channel with MDBV requirements, the logical channel allows the amount of data to be allocated in the second round of resource allocation process to take the logical channel for the number of available tokens in the token bucket controlled by the MDBV and the logic The smaller of the data amount of the current resource to be allocated, and the resource allocation to the logical channel; if the logical channel that needs to be allocated currently is a logical channel that does not have the MDBV requirement and includes a GBR (Guarantee Bit Rate) service And the terminal performs resource allocation on the logical channel;

3: If the terminal determines that there are remaining resources, the terminal allocates resources to the remaining to-be-transmitted data in descending order of all logical channel priorities with data transmission requirements until the resources are exhausted or the data to be transmitted of all logical channels All resources are allocated.

The number of tokens that can be used in the token bucket for the MDBV control corresponding to the logical channel is the MDBV corresponding to the logical channel and the command for MDBV control corresponding to the logical channel. The difference in the number of tokens that have actually been used in the bucket.

The terminal determines the number M of tokens that have been actually used in the time slot (N-PDB, N) in the token bucket controlled by the MDBV, and sets the size of the token bucket and the difference of M as The number of available tokens in the token bucket corresponding to the object, so that after completing the PBR-based resource allocation, the number of available tokens in the token bucket used for MDBV control is performed on the logical channel required by the MDBV. The purpose of the update.

In the embodiment of the present invention, when performing resource allocation, resource allocation is performed in different manners for a logical channel without MDBV requirements and a logical channel having MDBV requirements, further ensuring that the amount of data sent by each QoS Flow does not exceed MDBV. Restrictions, so that delay-sensitive services can seize resources of other services when the system is heavily loaded.

In a second aspect, an embodiment of the present invention provides a method for performing resource allocation, where the method includes:

Determining, by the network side device, the MDBV corresponding to the resource allocation object and the token bucket for the MDBV control; and then the network side device performs the resource allocation object according to the determined MDBV and the token bucket for MDBV control Resource allocation; wherein, if uplink resource allocation is performed, the resource allocation object is a logical channel group; and if downlink resource allocation is performed, the resource allocation object is a logical channel.

In the above solution, the network side device determines the MDBV corresponding to the resource allocation object and the token bucket used for the MDBV control, and then performs resource allocation for the resource allocation object according to the determined MDBV and the token bucket for MDBV control. In the embodiment of the present invention, the resources of the data transmission are allocated according to the token bucket used for the MDBV control, so that the amount of data sent by each QoS Flow does not exceed the MDBV limit, thereby avoiding the delay when the system load is heavy. Sensitive services seize resources from other businesses.

In some implementations, after determining that the logical channel is established, the network side device determines the MDBV corresponding to the resource allocation object and the token bucket used for the MDBV control; and/or determines that the resource allocation needs to be performed based on the MDBV according to the system load. Determine the MDBV corresponding to the resource allocation object and the token bucket for MDBV control.

If the uplink resource allocation is performed, the network side device determines that the resource allocation needs to be performed based on the MDBV according to the system load, and notifies the terminal that the resource allocation needs to be performed based on the MDBV.

In the embodiment of the present invention, the network side device determines the MDBV corresponding to the logical channel according to different situations, so that the resource allocation is ensured when the resource is allocated, and the delay sensitive service is prevented from preempting resources of other services.

In some implementations, if the downlink resource allocation is performed, the network side device determines the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel; or

If the uplink resource allocation is performed, the network side device determines the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel, and uses the sum of the MDBVs corresponding to the logical channels in the same logical channel group as the MDBV corresponding to the logical channel group; or ,

If the uplink resource allocation is performed, the network side device uses the sum of the MDBVs corresponding to the logical channels reported by the terminal as the MDBV corresponding to the logical channel group; or

If the uplink resource allocation is performed, the network side device receives the MDBV corresponding to the logical channel group reported by the terminal.

In some implementations, if the Flow and the logical channel adopt a 1:1 mapping, the network side device uses the MDBV corresponding to the Flow as the MDBV corresponding to the logical channel; or

If the flow and the logical channel adopt the M:1 mapping, the network side device uses, according to the mapping relationship between the flow and the logical channel, the sum of the MDBVs corresponding to the flows that can be mapped to the logical channel as the MDBV corresponding to the logical channel; or ,

If the flow and the logical channel adopt the M:1 mapping, the network side device will use the sum of the MDBVs corresponding to the Flows actually mapped to the logical channel as the MDBV corresponding to the logical channel according to the Flow and logical channel mapping relationship; , M is a positive integer.

In some implementations, before the network side device determines the MDBV corresponding to the resource allocation object by using the MAC layer, the network side device needs to notify the MAC layer of the flow and the logical channel by using a SDAP or a RRC (Radio Resource Control) layer. Mapping relationship; or,

The network side device notifies the mapping relationship between the MAC layer Flow and the logical channel and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or

The network side device notifies the MAC layer to actually map to the flow of the logical channel through the SDAP layer; or

The network side device notifies the MAC layer to actually map to the flow of the logical channel and the MDBV corresponding to the QFI through the SDAP layer; or

After the network side device is configured to notify the MDBV corresponding to the logical channel of the MAC layer by using the SDAP layer, the MDBV corresponding to the resource allocation object is determined by the MAC layer.

In some implementations, the MAC layer does not know the mapping relationship between the logical channel and the logical channel group when the uplink resource is allocated, so the RRC layer needs to notify the mapping relationship between the logical layer and the logical channel group of the MAC layer, so that the network side The device can determine the MDBV corresponding to the logical channel group at the MAC layer.

In some specific implementations, if the resource allocation object is a logical channel group, the network side device notifies the mapping relationship between the MAC layer logical channel and the logical channel group through the RRC layer.

In the embodiment of the present invention, since the network side device is the MDBV corresponding to the logical channel determined by the MAC layer, but the MAC layer does not know the corresponding mapping relationship, multiple ways of notifying the MAC layer are introduced to ensure that the network side device can The MAC layer determines the MDBV corresponding to the logical channel.

In some implementations, the size of the token bucket for MDBV control is the MDBV corresponding to the logical channel. Determining, by the network side device, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and using the difference between the size of the token bucket and the M The number of available tokens in the token bucket corresponding to the logical channel; where N is a scheduling moment, and the PDB is a packet delay budget corresponding to the logical channel.

In some specific implementations, the network side device determines the PDB corresponding to the logical channel by:

In the embodiment of the present invention, due to the token bucket size for the MDBV control and the tokens that have been actually used in the time bucket (N-PDB, N) in the token bucket for the MDBV control according to the resource allocation object. The number of available tokens in the token bucket corresponding to the resource allocation object is determined, and the resource allocation is performed according to the number of available tokens in the token bucket corresponding to the determined resource allocation object, which fully ensures the transmission of each QoS Flow. The amount of data does not exceed the MDBV limit, so that the delay-sensitive service can seize resources of other services when the system is heavily loaded.

In some implementations, if the downlink resource allocation is performed, the network side device uses, as the difference between the MDBV corresponding to the logical channel and the number of tokens actually used in the token bucket for MDBV control. The logical channel is capable of allocating the amount of data of the resource; then the minimum value between the number of available tokens in the token bucket corresponding to the logical channel MDBV and the actual amount of data to be transmitted of the current logical channel is the logic The channel performs resource allocation.

In some implementations, if the uplink resource allocation is performed, the network side device has actually used the MDBV corresponding to the logical channel group and the token bucket for MDBV control corresponding to the logical channel group. The difference between the number of the tokens is the number of available tokens in the token bucket corresponding to the logical channel group; and then the number of available tokens in the token bucket corresponding to the logical channel group and the current logical channel. The minimum value between the data amount of the actual resource to be allocated is resource allocation for the logical channel group.

In a third aspect, an embodiment of the present invention provides a terminal for performing resource allocation, where the terminal includes: a processor, a memory, and a transceiver;

The processor is configured to read a program in the memory and execute:

Determining a MDBV corresponding to the logical channel and a token bucket for MDBV control; performing resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control.

In a fourth aspect, an embodiment of the present invention provides a network side device that performs resource allocation, where the network side device includes: a processor, a memory, and a transceiver;

The processor is configured to read a program in the memory and execute:

Determining, by the MDBV and the token bucket for the MDBV control, resource allocation for the resource allocation object In the case of allocation, the resource allocation object is a logical channel group; if downlink resource allocation is performed, the resource allocation object is a logical channel.

In a fifth aspect, an embodiment of the present invention provides a terminal for performing resource allocation, where the terminal includes:

a first determining module, configured to determine an MDBV corresponding to the logical channel and a token bucket for the MDBV control;

And a first allocation module, configured to perform resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control.

In a sixth aspect, an embodiment of the present invention provides a network side device that performs resource allocation, where the network side device includes:

a second determining module, configured to determine an MDBV corresponding to the resource allocation object and a token bucket used for MDBV control;

a second allocation module, configured to perform resource allocation for the resource allocation object according to the determined MDBV and the token bucket for MDBV control;

If the uplink resource allocation is performed, the resource allocation target is a logical channel group; and when downlink resource allocation is performed, the resource allocation object is a logical channel.

In addition, the technical effects brought by the implementations of the second aspect to the sixth aspect can be referred to the technical effects brought about by the implementation manners in the first aspect, and details are not described herein again.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying for inventive labor.

FIG. 1 is a schematic diagram of a system for performing resource allocation according to an embodiment of the present invention; FIG.

2 is a schematic flowchart of a complete method for resource allocation of downlink resources according to an embodiment of the present invention;

3 is a schematic flowchart of a complete method for performing resource allocation on a terminal side of an uplink resource according to an embodiment of the present invention;

4 is a schematic flowchart of a complete method for performing resource allocation on a network device side of an uplink resource according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a terminal for performing resource allocation according to an embodiment of the present invention; FIG.

FIG. 6 is a schematic structural diagram of a network side device for performing resource allocation according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of another terminal for performing resource allocation according to an embodiment of the present invention; FIG.

FIG. 8 is a schematic structural diagram of another network side device for performing resource allocation according to an embodiment of the present invention;

FIG. 9 is a schematic flowchart of a method for performing resource allocation according to an embodiment of the present invention;

FIG. 10 is a schematic flowchart of another method for performing resource allocation according to an embodiment of the present invention.

detailed description

In the application scenario of the MDBV data transmission in the 5G NR system, the core network configures the QoS profile for each flow for the 5G NR system. The RAN performs QoS management based on the QoS profile configured by the core network for each Flow. One parameter in the QoS profile is 5QI, and MDBV is a parameter included in 5QI. In the embodiment of the present invention, the terminal first determines the MDBV corresponding to the object and the token bucket used for MDBV control, and performs resource allocation according to the determined MDBV and the token bucket for MDBV control. In the embodiment of the present invention, the resources of the data transmission are allocated according to the token bucket used for the MDBV control, so that the amount of data sent by each QoS Flow does not exceed the MDBV limit, thereby avoiding when the system is heavily loaded. Delay sensitive business to seize resources of other businesses.

The present invention will be further described in detail with reference to the accompanying drawings, in which . All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

As shown in FIG. 1 , an embodiment of the present invention provides a system for performing resource allocation, where the system includes: a terminal 100 and a network side device 101.

The terminal 100 is configured to determine an MDBV corresponding to the logical channel and a token bucket for the MDBV control, and perform resource allocation on the logical channel according to the determined MDBV and the token bucket for MDBV control.

The network side device 101 is configured to determine an MDBV corresponding to the resource allocation object and a token bucket for MDBV control, and perform resources for the resource allocation object according to the determined MDBV and the token bucket for MDBV control. The resource allocation object is a logical channel group if the uplink resource allocation is performed, and the resource allocation object is a logical channel if the downlink resource allocation is performed.

In the embodiment of the present invention, the terminal and the network side device first determine the MDBV corresponding to the object and the token bucket for MDBV control, and perform resource allocation according to the determined MDBV and the token bucket for MDBV control. In the embodiment of the present invention, the resources of the data transmission are allocated according to the token bucket used for the MDBV control, so that the amount of data sent by each QoS Flow does not exceed the MDBV limit, thereby avoiding when the system is heavily loaded. Delay sensitive business to seize resources of other businesses.

The following uses the downlink resources as an example to describe the system for resource allocation.

Method 1: Resource allocation for downlink resources.

When the resource allocation is performed on the downlink resource, after the network side device determines that the logical channel establishment is completed and/or the network side device determines that the resource allocation needs to be performed based on the MDBV according to the system load, the network side device determines the MDBV corresponding to the logical channel and is used for the MDBV control. Token bucket.

When the network side device determines the MDBV corresponding to the logical channel at the MAC layer, there are several different situations in the mapping relationship between the flow and the logical channel. Therefore, the MDBV corresponding to the logical channel determined by the network side device is different. Explain different situations:

The first case: if the Flow and the logical channel adopt 1:1 mapping, the network side device will use the MDBV corresponding to the Flow as the MDBV corresponding to the logical channel;

For example, the 1:1 scale mapping used by the Flow and the logical channel is that only one logical channel only maps one Flow. At this time, the MDBV of the Flow is used as the MDBV corresponding to the logical channel.

The second case: if the flow and the logical channel adopt the M:1 scale mapping, the network side device obtains the MDBV corresponding to the flow corresponding to the flow of the logical channel according to the mapping relationship between the flow and the logical channel, and the MDBV corresponding to the logical channel, where M is a positive integer.

For example, the flow and logical channels adopt a 6:1 scale mapping. In this case, 6 flows are mapped to the same logical channel, and the network side device adds the MDBVs corresponding to the 6 flows, and the sum of the MDBVs is used as the logical channel. MDBV.

The third case: if the flow and the logical channel adopt the M:1 scale mapping, the network side device uses the sum of the MDBV corresponding to the Flow actually mapped to the logical channel in the Flow and logical channel mapping relationship as the MDBV corresponding to the logical channel. Where M is a positive integer.

For example, the flow and logical channels adopt a 6:1 scale mapping. According to the actual mapping rule, there should be M flows mapped to the same logical channel at this time, but only three flows are mapped to the same logical channel. The network side device adds the MDBVs corresponding to the three Flows, and the sum of the MDBVs is the MDBV corresponding to the logical channel.

Since the network side device determines the MDBV corresponding to the logical channel at the MAC layer root, but the MAC layer does not know the mapping relationship between the flow and the logical channel and the MDBV corresponding to the logical channel, the MAC layer needs to be notified in advance, and the network side device can be in the MAC. The layer determines the MDBV corresponding to the logical channel, and specifically can notify the MAC layer in the following manner.

(1) The network side device notifies the MAC layer Flow and logical channel mapping relationship through a Service Data Adaptation Protocol (SDAP) or an RRC layer;

When the network side device notifies the MAC layer of the flow and the logical channel mapping relationship, the flow is represented by QFI. The MAC layer determines the MDBV corresponding to each Flow according to the correspondence between the QFI and the 5QI identifier stored by the MAC layer and the correspondence between the 5QI and the MDBV. Finally, the MDBVs corresponding to the Flows mapped to the logical channels are added to obtain the MDBVs corresponding to the logical channels.

(2) The network side device notifies the mapping relationship between the MAC layer Flow and the logical channel and the MDBV corresponding to the QFI through the SDAP or the RRC layer.

After the MAC layer knows the mapping between the flow and the logical channel and the MDBV corresponding to the QFI, the network side device can know the flow mapped to the logical channel according to the mapping relationship between the flow and the logical channel, and then find the corresponding corresponding to each flow according to the MDBV corresponding to the QFI. The MDBV finally adds the MDBVs corresponding to the Flows mapped to the logical channels to obtain the MDBVs corresponding to the logical channels.

(3) The network side device notifies the MDBV corresponding to the MAC layer logical channel through the SDAP or the RRC layer.

In this case, the network side device can directly determine the MDBV corresponding to the logical channel according to the SDAP or RRC layer notification.

(4) The network side device notifies the MAC layer to actually map to the Flow of the logical channel through the SDAP layer.

The network side device notifies the MAC layer to actually map to the flow of the logical channel through the SDAP, and the flow is represented by QFI. The MAC layer determines the MDBV corresponding to each flow according to the correspondence between the QFI and the 5QI identifier stored by the MAC layer and the correspondence between the 5QI and the MDBV. . Finally, the MDBVs corresponding to the Flows mapped to the logical channels are added to obtain the MDBVs corresponding to the logical channels.

(5) The network side device notifies the MAC layer to actually map to the flow of the logical channel and the MDBV corresponding to the QFI through the SDAP layer.

After the MAC layer is actually mapped to the MDBV corresponding to the flow and the QFI of the logical channel, the network side device finds the MDBV corresponding to the Flow mapped to the logical channel according to the MDBV corresponding to the QFI, and finally maps the flow actually mapped to the logical channel. The corresponding MDBVs are added to obtain the MDBV corresponding to the logical channel.

(6) The network side device notifies the MDBV corresponding to the MAC layer logical channel through the SDAP layer.

The network side device can directly determine the MDBV corresponding to the logical channel according to the SDAP layer notification.

It should be noted here that one of the above manners may be used when notifying the MAC layer, or multiple methods may be used at the same time.

Correspondingly, after the network side device determines the MDBV corresponding to the logical channel, the network side device uses the MDBV corresponding to the logical channel as the logical channel for the size of the MDBV controlled token bucket, and determines the logical channel for the MDBV control. The number M of tokens actually used in the time slot (N-PDB, N) within the bucket, where N is the scheduling moment, and the PDB is the packet delay budget corresponding to the logical channel. Then the MDBV and The difference of M is taken as the number of available tokens at the current time N.

In a specific implementation, an optional implementation manner is: the network side device uses the MDBV corresponding to the logical channel and the current logical channel as the difference between the number of tokens actually used in the token bucket controlled by the MDBV. The logical channel is used for the number of available tokens in the token bucket controlled by the MDBV.

Correspondingly, after obtaining the number of available tokens in the token bucket used as the logical channel for the MDBV control, the network side device uses the number of available tokens in the token bucket controlled by the MDBV according to the logical channel. The minimum value between the data volume of the current logical channel actually to be allocated resources is resource allocation for the logical channel.

Among them, the PDB is determined as follows:

The terminal determines, according to the mapping relationship of the logical channels, the 5QI corresponding to all the flows of all the logical channels that can be mapped or the 5QIs of all the flows that are actually mapped to the logical channels; and finally determines the largest PDB as the logical channel from the 5QI corresponding to the Flow. Corresponding PDB.

For example, the network side device first determines that the logical channels that can be mapped to the logical channel group or are actually mapped to the logical channel group are the logical channels 1, 2, 3, and 4, and then the network side device determines that the logical channels 1, 2, 3, and 4 correspond to The 5QI corresponding to the Flow is determined from the determined 5QI corresponding to the Flow, and the largest PDB is determined as the PDB corresponding to the logical channel group according to the standardized 5QI table of the 3GPP.

After the network side device determines the MDBV corresponding to the logical channel and the token bucket for the MDBV control, the resource allocation is performed for the logical channel according to the determined MDBV and the token bucket for the MDBV control.

For example, if the number of available tokens in the token bucket used by the MDBV control is smaller than the amount of data required by the logical channel, the network side device preferentially allocates resources for the data required to meet the MDBV corresponding to the logical channel, if there is still remaining The resource, the network side device allocates resources according to the data amount that the logical channel can allocate resources according to the MDBV requirements that do not satisfy the logical channel group.

As shown in FIG. 2, the embodiment of the present invention provides a schematic flowchart of a complete method for resource allocation for downlink resources.

Step 200: The network side device determines that the logical channel establishment is completed, and/or the network side device determines, according to the system load, that resource allocation needs to be performed based on the MDBV.

Step 201: The network side device determines, by using a MAC layer, an MDBV corresponding to the logical channel.

Step 202: The network side device determines, by the logical channel, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV;

Step 203: The network side device uses the difference between the MDBV corresponding to the logical channel and the number M of tokens actually used in the time period (N-PDB, N) in the MDBV control token bucket as a logical channel for MDBV control. Number of tokens available in the token bucket;

Step 204: The network side device allocates resources to the logical channel according to a minimum value between the number of available tokens in the token bucket used by the logical channel for the MDBV control and the data volume of the actual logical channel to be allocated.

Method 2: Allocate resources to uplink resources.

When the resource allocation is performed on the uplink resource, the network side device needs to allocate uplink resources for different terminals. When the network side device determines that the logical channel establishment is completed and/or the network side device determines that the resource allocation needs to be performed based on the MDBV according to the system load, the logical channel is determined. The corresponding MDBV of the group and the token bucket for MDBV control.

The network side device can determine the MDBV corresponding to the logical channel group in the following centralized manner:

1. The network side device determines the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel, and uses the sum of the MDBVs corresponding to the logical channels in the same logical channel group as the MDBV corresponding to the logical channel group.

For example, the network side device determines the MDBV corresponding to the logical channels 1, 2, and 3 according to the mapping relationship between the flow and the logical channel, and the logical channels 1 and 2 are in the same logical channel group 1, and the network side device sets the logical channel 1 The sum of the corresponding MDBVs of 2 is the MDBV corresponding to the logical channel group 1.

However, there are several different situations in the mapping between the flow and the logical channel. Therefore, the MDBV corresponding to the logical channel determined by the network device is different. The following describes different situations:

The first case: if the Flow and the logical channel adopt a 1:1 scale mapping, the network side device will use the MDBV corresponding to the Flow as the MDBV corresponding to the logical channel;

The second case: if the flow and the logical channel adopt the M:1 scale mapping, the network side device uses the sum of the MDBVs corresponding to the Flows that can be mapped to the logical channel as the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel. Where M is a positive integer.

The third case: if the Flow and the logical channel adopt the M:1 scale mapping, the network side device will use the sum of the MDBVs corresponding to the Flow actually mapped to the logical channel according to the Flow and logical channel mapping relationship. The MDBV corresponding to the logical channel. Where M is a positive integer.

For example, the flow and logical channels adopt a 6:1 scale mapping. According to the actual mapping rule, there should be 6 flows mapped to the same logical channel at this time, but only three flows are mapped to the same logical channel. The network side device adds the MDBVs corresponding to the three Flows, and the sum of the MDBVs is the MDBV corresponding to the logical channel.

2. The network side device receives the sum of the MDBVs corresponding to the logical channels reported by the terminal, and uses the sum of the MDBVs corresponding to the reported logical channels as the MDBV corresponding to the logical channel group.

For example, the network side device will receive the sum of the MDBVs corresponding to the logical channels 1, 2, and 3 reported by the receiving end, and the logical channels 1, 2, and 3 are in the same logical channel group 1, and the logical channel 1 to be reported by the network side device at this time. The sum of the MDBVs corresponding to 2 and 3 is the MDBV corresponding to the logical channel group 1.

3. The network side device receives the MDBV corresponding to the logical channel group reported by the terminal, and then uses the MDBV corresponding to the reported logical channel group as the MDBV corresponding to the logical channel group.

For example, the terminal reports the sum of the MDBVs corresponding to the logical channels 1, 2, and 3 in the same logical channel group 1 to the network side device, and the sum of the MDBVs corresponding to the same logical channel group 1 reported by the network side device at this time. As the MDBV corresponding to logical channel group 1.

Since the network side device determines the MDBV corresponding to the logical channel group at the MAC layer, the MAC layer does not know the mapping relationship between the Flow and the logical channel and the MDBV corresponding to the logical channel, so the MAC layer needs to be notified in advance.

In addition, since the MAC layer does not know the mapping relationship between the logical channel and the logical channel group when performing uplink allocation of resources, the RRC layer also needs to notify the mapping relationship between the logical layer and the logical channel group of the MAC layer, so that the network side device can be in the MAC. The layer determines the MDBV corresponding to the logical channel group, and specifically can notify the MAC layer in the following manner.

(1) The network side device notifies the MAC layer Flow and the logical channel mapping relationship through the SDAP or the RRC layer;

The MAC layer then determines the sum of the MDBVs of all logical channels mapped to the logical channel group as the MDBV of the logical channel group based on the mapping relationship between the logical channel and the logical channel group.

The MAC layer then determines the sum of the MDBVs of all the logical channels mapped to the logical channel group as the MDBV of the logical channel group according to the mapping relationship between the logical channel and the logical channel group.

An interaction information is required between the terminal SDAP and the network side SDAP, so that the network side device learns the terminal side device, and the network side device actually maps the flow information of the logical channel through the SDAP layer.

Then, the network side SDAP notifies the MAC layer to actually map to the flow of the logical channel, and the flow is represented by QFI. The MAC layer determines the MDBV corresponding to each Flow according to the correspondence between the QFI and the 5QI identifier stored by the MAC layer and the correspondence between the 5QI and the MDBV. Finally, the MDBVs corresponding to the Flows mapped to the logical channels are added to obtain the MDBVs corresponding to the logical channels.

Then, the network side SDAP notifies the MAC layer to actually map to the flow of the logical channel. After the MAC layer knows the actual mapping to the logical channel and the MDBV corresponding to the QFI, the network side device finds the mapping to the logic according to the MDBV corresponding to the QFI. The MDBV corresponding to the Flow of the channel is finally added to the MDBV corresponding to the Flow that is actually mapped to the logical channel, and the MDBV corresponding to the logical channel is obtained.

Then, the network side SDAP layer determines the MDBV corresponding to the logical channel according to the mapping relationship between the actual Flow and the logical channel, and the MAC layer can directly determine the MDBV corresponding to the logical channel according to the SDAP layer notification.

It should be noted here that the above method of notifying the MAC layer may use one of the methods separately, or may use multiple methods at the same time.

Correspondingly, after the network side device determines the MDBV corresponding to the logical channel group, the network side device uses the MDBV as the logical channel group for the size of the MDBV controlled token bucket, and determines the token bucket for the MDBV control at the time. The number M of tokens actually used in the segment (N-PDB, N), where N is the scheduling time, and the PDB is the packet delay budget corresponding to the logical channel. The difference between the MDBV and the M is the current time N. The number of tokens that can be used by the token bucket for MDBV control.

The PDB is determined as follows:

The terminal determines, according to the mapping relationship between the flow and the logical channel, the 5QI corresponding to all flows that can be mapped to the logical channel group or the 5QI corresponding to all the flows that are actually mapped to the logical channel group, and finally determines the largest PDB according to the 5QI corresponding to the Flow. The PDB corresponding to the logical channel group.

For example, the network side device first determines that the logical channels that can be mapped to the logical channel group or are actually mapped to the logical channel group are the logical channels 1, 2, 3, and 4, and then the network side device determines that the logical channels 1, 2, 3, and 4 correspond to The 5QI corresponding to the Flow further determines the largest PDB as the PDB corresponding to the logical channel group from the determined 5QI corresponding to the Flow.

After the network side device determines the MDBV corresponding to the logical channel group and the token bucket for the MDBV control, the resource allocation is performed for the logical channel group according to the determined MDBV and the token bucket for MDBV control.

In a specific implementation, an optional implementation manner is: the network side device uses the difference between the MDBV corresponding to the logical channel group and the number of tokens actually used in the token bucket for MDBV control as the logical channel group. The number of available tokens in the corresponding token bucket.

For example, the MDBV corresponding to the logical channel group is 200 bits, and the number of tokens that have been actually used in the token bucket controlled by the MDBV is 100 bits. In this case, the difference between the two is 100-100=100. The difference (100-bit) logical channel group is used to control the number of available tokens in the MDBV control token bucket to be 100 bits.

After obtaining the number of available tokens in the token bucket used as the logical channel group for the MDBV control, if the number of available tokens of the logical channel group is smaller than the actual amount of data to be transmitted by the logical channel group, the network side device preferentially satisfies The data allocation resource required by the MDBV corresponding to the logical channel group. If the remaining resources still exist, the network side device allocates resources according to the data that the logical channel group actually needs to transmit but does not satisfy the MDBV corresponding to the logical channel group.

Correspondingly, after the network side device allocates resources to different terminals, the allocated resources are notified to the terminal, and the terminal needs to perform resource allocation on the logical channel based on the resources allocated by the network side, so when the terminal determines that the logical channel is established and/or received. After the notification sent by the network side device that needs to be allocated based on the MDBV, the terminal determines the token bucket for the MDBV control and the MDBV corresponding to the logical channel.

When the terminal determines the MDBV corresponding to the logical channel at the MAC layer, there are several different situations in the mapping relationship between the flow and the logical channel. Therefore, the MDBV corresponding to the logical channel determined by the terminal is different, and the following describes different situations. :

The first case: if the Flow and the logical channel adopt a 1:1 ratio mapping, the terminal will use the MDBV corresponding to the Flow as the MDBV corresponding to the logical channel;

For example, the Flow and the logical channel adopt a 1:1 ratio mapping. In this case, the terminal uses the MDBV of the Flow as the MDBV corresponding to the logical channel.

The second case: if the flow and the logical channel adopt the M:1 scale mapping, the terminal uses the sum of the MDBVs corresponding to the Flows that can be mapped to the logical channel as the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel; , M is a positive integer.

For example, the flow and logical channels adopt a 6:1 scale mapping. In this case, 6 flows are mapped to the same logical channel, and the terminal adds the MDBVs corresponding to the 6 flows, and the sum of the MDBVs is used as the MDBV corresponding to the logical channel. .

In the third case, if the flow and the logical channel adopt the M:1 scale mapping, the terminal uses the sum of the MDBVs corresponding to the Flows actually mapped to the logical channel as the logical channel according to the flow and logical channel mapping relationship. MDBV, where M is a positive integer.

For example, the flow and logical channels adopt a 6:1 scale mapping. According to the actual mapping rule, there should be 6 flows mapped to the same logical channel at this time, but only three flows are mapped to the same logical channel. In the middle, the MDBVs corresponding to the three Flows are added, and the sum of the MDBVs is taken as the MDBV corresponding to the logical channel.

Since the terminal determines the MDBV corresponding to the logical channel at the MAC layer, but the MAC layer does not know the mapping relationship between the MDBV corresponding to the logical channel and the flow and the logical channel, it is necessary to introduce an inter-layer interaction mechanism to notify the MAC layer that the terminal can be in the MAC layer. The MDBV corresponding to the logical channel is determined, and the MAC layer may be notified in the following manner.

(1) The terminal notifies the medium access control MAC layer Flow and the logical channel mapping relationship through the service data adaptation layer SDAP or the radio resource control RRC layer.

When the terminal SDAP or the RRC notifies the MAC layer of the flow and the logical channel mapping relationship, the flow is represented by QFI. The MAC layer determines the MDBV corresponding to each Flow according to the correspondence between the QFI and the 5QI identifier stored by the MAC layer and the correspondence between the 5QI and the MDBV. Finally, the MDBVs corresponding to the Flows mapped to the logical channels are added to obtain the MDBVs corresponding to the logical channels.

(2) The terminal notifies the mapping relationship between the MAC layer Flow and the logical channel and the MDBV corresponding to the QFI through the SDAP or the RRC layer.

After the MAC layer knows the mapping between the flow and the logical channel and the MDBV corresponding to the QFI, the terminal can know the flow mapped to the logical channel according to the mapping relationship between the flow and the logical channel, and then find the MDBV corresponding to each flow according to the MDBV corresponding to the QFI. Finally, the MDBVs corresponding to the Flows mapped to the logical channels are added to obtain the MDBVs corresponding to the logical channels.

(3) The terminal notifies the MDBV corresponding to the logical channel of the MAC layer through the SDAP or the RRC layer.

The MAC can directly obtain the MDBV corresponding to the logical channel according to the notification. The MDBV is the sum of MDBVs corresponding to Flows that can be mapped to the logical channel.

(4) The terminal notifies the MAC layer to actually map to the Flow of the logical channel through the SDAP layer.

After the MAC layer is actually mapped to the MDBV corresponding to the Flow and the QFI of the logical channel, the MDBV corresponding to the Flow mapped to the logical channel is found according to the MDBV corresponding to the QFI, and finally the MDBV corresponding to the Flow mapped to the logical channel is actually mapped. Add together to get the MDBV corresponding to the logical channel.

(5) The terminal notifies the MAC layer to actually map to the flow of the logical channel and the MDBV corresponding to the QFI through the SDAP layer.

(6) The terminal device notifies the MDBV corresponding to the logical channel of the MAC layer through the SDAP layer.

The MAC layer can directly obtain the MDBV corresponding to the logical channel according to the notification. The MDBV is the sum of the MDBVs corresponding to the Flows actually mapped to the logical channel.

It should be noted here that the above two ways of notifying the MAC layer can be used alone or in combination.

Correspondingly, after the terminal determines the MDBV corresponding to the logical channel, the terminal uses the MDBV corresponding to the logical channel group as the logical channel group for the size of the token bucket controlled by the MDBV, and determines the token bucket for the MDBV control at the time. The number of tokens actually used in the segment (N-PDB, N), where N is the scheduling moment, and the PDB is the packet delay budget corresponding to the logical channel. Then the difference between MDBV and M is taken as the current moment. The number of tokens available for N.

After the terminal determines the MDBV corresponding to the logical channel group and the token bucket for the MDBV control, the terminal performs resource allocation for the logical channel group according to the determined MDBV and the token bucket for MDBV control, an optional implementation manner. for:

1: The terminal first sorts the logical channels with available PBR tokens and data transmission requirements in descending order of logical channel priority, and then the terminal sequentially allocates the first round of resources based on PBR for each logical channel, and updates each logic simultaneously. The number of tokens in the PBR token bucket corresponding to the channel, and after completing the PBR-based resource allocation for the logical channel with the MDBV requirement, the number of available tokens in the MDBV token bucket corresponding to the logical channel is updated.

The number of available tokens in the token bucket corresponding to the logical channel herein is the difference between the MDBV and the number of tokens actually used by the logical channel in the token bucket corresponding to the current time;

For example, the MDBV corresponding to the logical channel is 200 bits, and the number of tokens that have been actually used in the token bucket controlled by the MDBV is 100 bits. In this case, the difference between the two is 200-100=100, then the logical channel group The number of tokens that can be used in the corresponding token bucket is 100 bits.

2: After the terminal determines that there are remaining resources that can be allocated, the second round of resource allocation is performed on all logical channels having data transmission requirements in descending order of logical channel priority, specifically:

For a logical channel with MDBV requirements, the logical channel allows the amount of data to be allocated in the second round of resource allocation process. The logical channel is used for the number of tokens that can be used in the token bucket controlled by the MDBV and the current resource to be allocated. a smaller of the amount of data, resource allocation for the logical channel;

If the logical channel that needs to be allocated is a logical channel that does not have the MDBV requirement, the terminal allocates resources to the logical channel according to the data amount of the resource to be allocated by the logical channel.

For example, the terminal determines that there is a logical channel required by the MDBV, and the number of available tokens in the current token bucket corresponding to the logical channel is 40 bits, and the amount of data that can be allocated in the current token bucket of the logical channel is 60 bits, at which time the terminal takes a smaller value (40 bits) between the two to allocate resources to the logical channel.

If the logical channel that the terminal currently needs to allocate is a logical channel that does not have the MDBV requirement, the terminal has two ways to allocate resources.

One way is: the terminal allocates resources to the logical channel according to the amount of data of the resource to be allocated currently on the logical channel:

For example, the amount of data of the resource to be allocated on the logical channel is 600 bits, and the terminal allocates resources according to the 600 bits.

The other way is: if the logical channel that needs to be allocated before is a logical channel that does not have the MDBV requirement and includes the GBR service, the terminal allocates resources to the logical channel according to the data amount of the resource to be allocated by the logical channel.

For example, the data volume of the logical channel to be allocated is 600 bits, and the logical channel that needs to be allocated is a logical channel that includes the GBR service. At this time, the terminal allocates resources only to the logical channel according to the 600 bits.

3: After the second round of allocation, if the terminal determines that there are remaining resources, the remaining to-be-transmitted data is allocated in descending order of all logical channels having data transmission requirements until the resources are exhausted or all logical channels are Resources are allocated for the data to be transmitted.

After the allocation is completed, the terminal determines whether there are any remaining resources. If there are remaining resources, the resources are allocated to the respective logical channels according to the remaining resources according to the order of the logical channels.

Among them, the PDB is determined as follows:

The terminal determines the 5QI corresponding to all flows that can be mapped to the logical channel group or the 5QIs corresponding to all the flows that are actually mapped to the logical channel group according to the mapping relationship between the flow and the logical channel, and finally determines the largest PDB according to the 5QI corresponding to the Flow as the logic. The PDB corresponding to the channel group.

For example, the network side device first determines that the logical channel that can be mapped or the actually mapped logical channel is the logical channel 1, 2, 3, and 4, and then the field determines the 5QI corresponding to the Flow corresponding to the logical channels 1, 2, 3, and 4, and then The maximum PDB is determined as the PDB corresponding to the logical channel from the determined 5QI corresponding to the Flow.

As shown in FIG. 3, the embodiment of the present invention provides a schematic flowchart of a complete method for performing resource allocation on an uplink side of an uplink resource.

Step 300: The terminal needs to determine that the logical channel is established and/or receives a notification that the network side device needs to perform resource allocation based on the MDBV.

Step 301: The terminal determines, by using a MAC layer, an MDBV corresponding to the logical channel.

Step 302: The terminal network side device determines, by the logical network channel, the number of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV;

Step 303: The terminal sorts logical channels having available PBR tokens and having data transmission requirements in descending order of logical channel priorities.

Step 304: The terminal sequentially performs a first round of resource allocation based on the PBR for each logical channel, and simultaneously updates the number of tokens in the PBR token bucket corresponding to each logical channel group, and updates each logical channel group corresponding to the MDBV. The number of tokens available in the controlled token bucket;

Step 305: After completing the PBR-based resource allocation on the logical channel required by the MDBV, the terminal updates the logical channel for the number of available tokens in the token bucket controlled by the MDBV.

Step 306, after the terminal determines that there are remaining resources that can be allocated, it is determined whether the logical channel that needs to be allocated currently has a logical channel required by the MDBV, if yes, step 307 is performed; otherwise, step 308 is performed;

Step 307: The terminal takes a logical channel for a smaller value of the number of available tokens in the token bucket controlled by the MDBV and the data volume of the current resource to be allocated of the logical channel, and performs resource allocation on the logical channel.

Step 308: The terminal allocates resources to the logical channel according to the data amount of the resource to be allocated by the logical channel, or the logical channel that needs to be allocated before is a logical channel that does not have an MDBV requirement, and includes a GBR service, and the current resource to be allocated according to the logical channel. The amount of data is allocated to the logical channel;

Step 309: The terminal determines that there are remaining resources, and performs resource allocation on the remaining data to be transmitted in descending order of all logical channel priorities having data transmission requirements.

As shown in FIG. 4, the embodiment of the present invention provides a schematic flowchart of a complete method for performing resource allocation on a network side device for uplink resources.

Step 400: The network side device determines that the logical channel establishment is complete and/or the network side device determines that the resource allocation needs to be performed based on the MDBV according to the system load, and notifies the terminal to determine, according to the system load, that the resource allocation needs to be performed based on the MDBV.

Step 401: The network side device determines, by using a MAC layer, an MDBV corresponding to the logical channel group.

Step 402: The network side device determines, by the logical channel, the number of tokens that have been actually used in the time slot (N-PDB, N) in the token bucket controlled by the MDBV;

Step 403: The network side device uses, as a logical channel group, the difference between the MDBV corresponding to the logical channel group and the number M of tokens actually used in the time period (N-PDB, N) in the MDBV control token bucket. The number of tokens available in the token bucket controlled by MDBV;

Step 404: The network side device preferentially allocates resources for data required to meet the MDBV corresponding to the logical channel group.

Step 405: The network side device determines that there are remaining resources. If the step 406 is performed, the resource allocation is ended.

Step 406: The network side device further allocates resources according to data required to be transmitted by the logical channel group but does not meet the MDBV requirement corresponding to the logical channel group.

Step 407: The network side device ends resource allocation.

As shown in FIG. 5, an embodiment of the present invention provides a terminal for performing resource allocation, where the terminal includes: a processor 500, a memory 501, and a transceiver 502;

The processor 500 is configured to read a program in the memory 501 and execute:

Optionally, the processor 500 is further configured to:

Before determining the MDBV corresponding to the logical channel and the token bucket for the MDBV control, determining that the logical channel establishment is completed; and/or receiving the notification that the network side device needs to perform resource allocation based on the MDBV.

Optionally, the processor 500 is specifically configured to:

The MDBV corresponding to the logical channel is determined according to the mapping relationship between the Flow and the logical channel.

Optionally, the processor is specifically configured to:

If the Flow and the logical channel adopt a 1:1 mapping, the MDBV corresponding to the Flow is used as the MDBV corresponding to the logical channel; or

If the flow and the logical channel adopt the M:1 mapping, the sum of the MDBVs corresponding to the Flows that can be mapped to the logical channels is used as the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel; or

If the Flow and the logical channel adopt the M:1 mapping, the sum of the MDBVs corresponding to the Flows actually mapped to the logical channel is used as the MDBV corresponding to the logical channel according to the Flow and logical channel mapping relationship; wherein the M is A positive integer.

Optionally, the processor 500 is specifically configured to:

The MDBV corresponding to the logical channel is determined at the MAC layer.

Optionally, the processor 500 is further configured to:

Before the MDBV corresponding to the logical channel is determined by the MAC layer, the mapping relationship between the MAC layer Flow and the logical channel is notified through the SDAP or the RRC layer; or

Notifying the mapping relationship between the MAC layer Flow and the logical channel and the MDBV corresponding to the QFI through the SDAP or RRC layer; or

Notifying the MDBV corresponding to the MAC layer logical channel through the SDAP or RRC layer; or

Notifying the MAC layer to actually map to the flow of the logical channel through the SDAP layer; or

Notifying the MAC layer to actually map to the flow channel of the logical channel and the MDBV corresponding to the QFI through the SDAP layer; or

The MDBV corresponding to the MAC layer logical channel is notified through the SDAP layer.

Optionally, the size of the token bucket used for the MDBV control is an MDBV corresponding to the logical channel.

Optionally, the processor 500 is further configured to:

First, the logical channel is used for the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and the difference between the size of the token bucket and the difference of M is used as the logical channel. The number of available tokens in the corresponding token bucket, where N is the scheduling moment, and the PDB is the packet delay budget corresponding to the logical channel.

Optionally, the processor is specifically configured to: determine, by using the following manner, a PDB corresponding to the logical channel:

Determining, according to a mapping relationship between the flow and the logical channel, a 5QI corresponding to all flows that are mapped to the logical channel or a 5QI corresponding to all flows that are actually mapped to the logical channel; determining, according to the 5QI corresponding to the Flow, a maximum PDB as a The PDB corresponding to the logical channel.

Optionally, the processor 500 is specifically configured to:

The terminal sorts logical channels with available PBR tokens and data transmission requirements according to logical channel priority descending order, and then performs first round resource allocation on each logical channel based on PBR, and updates each logical channel correspondingly. The number of tokens in the PBR token bucket, and the number of available tokens in the token bucket controlled by the MDBV after the PBR-based resource allocation is completed for the logical channel with the MDBV requirement;

After determining that there are remaining resources, the terminal performs a second round of resource allocation in descending order of logical channel priorities for all logical channels having data transmission requirements:

For a logical channel with MDBV requirements, the logical channel allows the amount of data to be allocated in the second round of resource allocation process to take the logical channel for the number of available tokens in the token bucket controlled by the MDBV and the logic a smaller value of the amount of data to be transmitted by the channel, and performing resource allocation on the logical channel; if the logical channel that needs to be allocated is a logical channel that is not required by the MDBV, the terminal is currently to be transmitted according to the logical channel. A quantity is allocated to the logical channel.

Optionally, the processor 500 is further configured to:

After performing the second round of resource allocation in descending order of logical channel priority for all logical channels having data transmission requirements, if the terminal determines that there are remaining resources, the logical channel priorities are reversed in order for all data transmission requirements. The remaining data to be transmitted is allocated for resources until resources are exhausted or resources of all logical channels to be transmitted are allocated.

Optionally, the processor 500 is further configured to:

The terminal sorts logical channels with available PBR tokens and data transmission requirements according to logical channel priority descending order, and then performs first round resource allocation on each logical channel based on PBR, and updates each logical channel correspondingly. The number of tokens in the PBR token bucket, and the number of available tokens for the MDBV control after the PBR-based resource allocation is completed for the logical channel with the MDBV requirement;

For a logical channel with MDBV requirements, the logical channel allows the amount of data to be allocated in the second round of resource allocation process to take the logical channel for the number of available tokens in the token bucket controlled by the MDBV and the logic a smaller value of the data amount of the current resource to be allocated, and performing resource allocation on the logical channel; if the logical channel currently required to be allocated is a logical channel that does not have an MDBV requirement and includes a GBR service, the terminal pairs the logic Channel for resource allocation;

Optionally, the processor 500 is further configured to:

Optionally, the number of tokens that can be used in the token bucket for the MDBV control corresponding to the logical channel is the MDBV corresponding to the logical channel, and the MDBV control corresponding to the logical channel. The difference between the number of tokens actually used in the token bucket.

Optionally, the processor 500 is specifically configured to:

Determining, by the logical channel, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and using the difference between the size of the token bucket and M as the object Number of tokens available in the token bucket;

Where N is the scheduling time, and the PDB is the data packet delay budget corresponding to the logical channel.

The processor 500 is responsible for managing the bus architecture and general processing, and the memory 501 can store data used by the processor 500 when performing operations. The transceiver 502 is configured to receive and transmit data under the control of the processor 500.

The bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 500 and various circuits of memory represented by memory 501. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein. The bus interface provides an interface. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 501 can store data used by the processor 500 when performing operations.

The flow disclosed in the embodiment of the present invention may be applied to the processor 500 or implemented by the processor 500. In the implementation process, each step of the signal processing flow may be completed by an integrated logic circuit of hardware in the processor 500 or an instruction in the form of software. The processor 500 can be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, which can be implemented or executed in an embodiment of the invention. Various methods, steps, and logic blocks of the disclosure. A general purpose processor can be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 501, and the processor 500 reads the information in the memory 501 and completes the steps of the signal processing flow in conjunction with its hardware.

As shown in FIG. 6, the embodiment of the present invention provides a network side device for performing resource allocation, where the network side device includes: a processor 600, a memory 601, and a transceiver 602;

The processor 600 is configured to read a program in the memory 601 and execute:

Optionally, the processor 600 is further configured to:

Before determining the MDBV corresponding to the resource allocation object and the token bucket for MDBV control, determining that the logical channel establishment is completed; and/or determining that resource allocation based on the MDBV is required according to the system load.

Optionally, the processor 600 is further configured to:

If the uplink resource allocation is performed, after determining that the resource allocation needs to be performed based on the MDBV according to the system load, the notification terminal needs to perform resource allocation based on the MDBV.

Optionally, the processor 600 is specifically configured to:

If downlink resource allocation is performed, the MDBV corresponding to the logical channel is determined according to the mapping relationship between the flow and the logical channel; or

If the uplink resource allocation is performed, the MDBV corresponding to the logical channel is determined according to the mapping relationship between the flow and the logical channel, and the sum of the MDBVs corresponding to the logical channels in the same logical channel group is used as the MDBV corresponding to the logical channel group; or

If the uplink resource allocation is performed, the sum of the MDBVs corresponding to the logical channels reported by the terminal is used as the MDBV corresponding to the logical channel group; or

If the uplink resource allocation is performed, the MDBV corresponding to the logical channel group reported by the terminal is received.

Optionally, the processor 600 is specifically configured to:

The MDBV corresponding to the resource allocation object is determined at the MAC layer.

Optionally, the processor 600 is further configured to:

Before the MAC layer determines the MDBV corresponding to the resource allocation object, notifying the mapping relationship between the MAC layer Flow and the logical channel through the SDAP or the RRC layer; or

Optionally, the processor 600 is further configured to:

If the resource allocation object is a logical channel group, the mapping relationship between the MAC layer logical channel and the logical channel group is notified by the RRC layer.

Optionally, the processor 600 is further configured to:

If the downlink resource allocation is performed, the size is determined according to the size of the token bucket used by the logical channel for MDBV control and the number M of tokens in the token bucket that the logical channel has used in the time period (N-PDB, N) Number of available tokens in the token bucket corresponding to the logical channel; or,

If uplink resource allocation is performed, it is determined according to the size of the token bucket used by the logical channel group for MDBV control and the number M of tokens in the token bucket that have been used by the logical channel group in the time period (N-PDB, N) The number of available tokens in the token bucket corresponding to the logical channel group; where N is a scheduling moment, and the PDB is a data packet delay budget corresponding to the logical channel.

Optionally, the processor 600 is specifically configured to: determine, by using the following manner, a PDB corresponding to the logical channel group:

Determining, according to the Flow and the logical channel mapping relationship, a 5QI corresponding to all flows that are mapped to the logical channel or a 5QI corresponding to all flows that are actually mapped to the logical channel; determining a maximum PDB according to the 5QI corresponding to the Flow as the The PDB corresponding to the logical channel.

Optionally, the processor 600 is specifically configured to:

If the downlink resource allocation is performed, the difference between the MDBV corresponding to the logical channel and the number of tokens actually used in the token bucket for the MDBV control is used as the data amount of the logical channel capable of allocating resources; The logical channel is used for resource allocation of the logical channel for the minimum value between the number of available tokens in the token bucket controlled by the MDBV and the actual amount of data to be transmitted of the current logical channel.

Optionally, the processor 600 is specifically configured to:

If the uplink resource allocation is performed, the difference between the MDBV corresponding to the logical channel group and the number of tokens actually used in the token bucket for MDBV control corresponding to the logical channel group is used as the logic. The number of available tokens in the token bucket corresponding to the channel group; the minimum value between the number of tokens available in the token bucket corresponding to the logical channel group and the actual amount of data to be transmitted in the current logical channel group Resource allocation is performed for the logical channel group.

The processor 600 is responsible for managing the bus architecture and general processing, and the memory 601 can store data used by the processor 600 in performing operations. The transceiver 602 is configured to receive and transmit data under the control of the processor 600.

The bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 600 and various circuits of memory represented by memory 601. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein. The bus interface provides an interface. The processor 600 is responsible for managing the bus architecture and general processing, and the memory 601 can store data used by the processor 600 in performing operations.

The flow disclosed in the embodiment of the present invention may be applied to the processor 600 or implemented by the processor 600. In the implementation process, each step of the signal processing flow may be completed by an integrated logic circuit of hardware in the processor 600 or an instruction in the form of software. The processor 600 can be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can be implemented or executed in an embodiment of the invention. Various methods, steps, and logic blocks of the disclosure. A general purpose processor can be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor. The software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like. The storage medium is located in the memory 601, and the processor 600 reads the information in the memory 601 and completes the steps of the signal processing flow in conjunction with its hardware.

As shown in FIG. 7, an embodiment of the present invention provides a terminal for performing resource allocation, where the terminal includes:

a first determining module 700, configured to determine an MDBV corresponding to the logical channel and a token bucket for MDBV control;

The first allocating module 701 is configured to perform resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control.

Optionally, the first determining module 700 is further configured to:

Optionally, the first determining module 700 is specifically configured to:

The MDBV corresponding to the logical channel is determined at the MAC layer.

Optionally, the first determining module 700 is further configured to:

Optionally, the first determining module 700 is specifically configured to:

Determining, by the logical channel, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and comparing the size of the token bucket with the difference of M as the logical channel The number of available tokens in the token bucket; where N is the scheduling moment and the PDB is the packet delay budget corresponding to the logical channel.

Optionally, the first determining module 700 is specifically configured to: determine, by using the following manner, a PDB corresponding to the logical channel:

Optionally, the first allocating module 701 is specifically configured to:

Optionally, the first allocating module 701 is further configured to:

After all the logical channels having data transmission requirements are subjected to the second round of resource allocation in descending order of logical channel priority, if the terminal determines that there are remaining resources, the remaining channels are in descending order of all logical channels having data transmission requirements. The data to be transmitted is allocated for resources until resources are exhausted or resources of all logical channels to be transmitted are allocated.

Optionally, the first determining module 700 is further configured to:

Determining, by the logical channel, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and using the difference between the size of the token bucket and M as the object The number of available tokens in the token bucket; where N is the scheduling moment and the PDB is the packet delay budget corresponding to the logical channel.

As shown in FIG. 8, the embodiment of the present invention provides a network side device that performs resource allocation, and the network side device includes:

a second determining module 800, configured to determine an MDBV corresponding to the resource allocation object and a token bucket for the MDBV control;

a second allocation module 801, configured to perform resource allocation for the resource allocation object according to the determined MDBV and the token bucket for MDBV control;

Optionally, the second determining module 800 is further configured to:

Optionally, the second determining module 800 is specifically configured to:

If the downlink resource allocation is performed, the MDBV corresponding to the logical channel is determined according to the mapping relationship between the flow and the logical channel; or

Optionally, the second determining module 800 is further configured to:

Optionally, the second determining module 800 is specifically configured to:

Optionally, the second determining module 800 is further configured to:

Optionally, the second determining module 800 is specifically configured to:

The PDB corresponding to the logical channel is determined in the following manner:

Optionally, the second determining module 800 is specifically configured to:

If the downlink resource allocation is performed, the difference between the MDBV corresponding to the logical channel and the number of tokens actually used in the token bucket for the MDBV control is used as the data amount of the logical channel capable of allocating resources; The logical channel is used for resource allocation of the logical channel for the minimum value between the number of available tokens in the token bucket controlled by the MDBV and the data volume of the actual logical channel to be allocated.

Optionally, the second determining module 800 is specifically configured to:

If the uplink resource allocation is performed, the difference between the MDBV corresponding to the logical channel group and the number of tokens actually used in the token bucket for MDBV control corresponding to the logical channel group is used as the logic. The number of available tokens in the token bucket corresponding to the channel group; the minimum between the number of tokens available in the token bucket corresponding to the logical channel group and the amount of data of the current logical channel to be allocated. A value is allocated for the logical channel group.

As shown in FIG. 9, an embodiment of the present invention provides a method for performing resource allocation, where the method includes:

Step 900: The terminal determines an MDBV corresponding to the logical channel and a token bucket used for MDBV control.

Step 901: The terminal performs resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control.

Optionally, before determining, by the terminal, the MDBV corresponding to the logical channel and the token bucket for the MDBV control, determining that the logical channel is established; and/or receiving the notification that the network side device needs to perform resource allocation based on the MDBV.

Optionally, the terminal determines, according to the mapping relationship between the flow and the logical channel, the MDBV corresponding to the logical channel.

Optionally, if the Flow and the logical channel adopt a 1:1 mapping, the terminal uses the MDBV corresponding to the Flow as the MDBV corresponding to the logical channel; or

Optionally, the terminal determines, at the MAC layer, an MDBV corresponding to the logical channel.

Optionally, the terminal notifies, by using a SDAP or an RRC layer, a mapping relationship between a MAC layer flow and a logical channel; or

The terminal notifies the MDBV corresponding to the logical channel of the MAC layer through the SDAP or the RRC layer; or

Optionally, the terminal determines, by the logical channel, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and the difference between the size of the token bucket and the M. The value is the number of available tokens in the token bucket corresponding to the logical channel;

Optionally, the terminal determines, according to the following manner, a PDB corresponding to the logical channel:

Determining, according to a mapping relationship of the logical channels, a 5QI corresponding to all flows that can be mapped to the logical channel or a 5QI corresponding to all flows actually mapped to the logical channel;

Determining the largest PDB as the PDB corresponding to the logical channel according to the 5QI corresponding to the Flow.

Optionally, the terminal allocates resources for the logical channel according to the determined MDBV and the token bucket for MDBV control:

Optionally, after the terminal performs the second round of resource allocation in descending order of logical channel priority for all logical channels that have data transmission requirements, the terminal further includes:

If the terminal determines that there are remaining resources, the remaining to-be-transmitted data is allocated according to the logical channel priority descending order of all data transmission requirements until the resources are exhausted or the resources to be transmitted of all logical channels are allocated resources.

1: The terminal sorts logical channels with available PBR tokens and data transmission requirements according to logical channel priority descending order, and then performs first round resource allocation on each logical channel based on PBR, and updates each logic simultaneously. The number of tokens in the PBR token bucket corresponding to the channel, and the number of available tokens in the corresponding MDBV token bucket corresponding to the logical channel after the PBR-based resource allocation is completed for the logical channel with the MDBV requirement. ;

Optionally, the terminal updates the logical channel for the number of available tokens in the token bucket controlled by the MDBV, including:

Determining, by the terminal, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and using the difference between the size of the token bucket and the M as the The number of available tokens in the token bucket corresponding to the object; where N is the scheduling moment, and the PDB is the packet delay budget corresponding to the logical channel.

As shown in FIG. 10, an embodiment of the present invention provides a method for performing resource allocation, where the method includes:

Step 1000: The network side device determines an MDBV corresponding to the resource allocation object and a token bucket used for MDBV control.

Step 1001: The network side device performs resource allocation for the resource allocation object according to the determined MDBV and the token bucket for MDBV control.

Optionally, before determining that the logical channel is used for the MDBV controlled token bucket and the MDBV corresponding to the object, the network side device determines that the logical channel establishment is completed; and/or determines that the resource allocation needs to be performed based on the MDBV according to the system load.

Optionally, if the uplink resource allocation is performed, the network side device determines that the resource allocation needs to be performed based on the MDBV according to the system load, and notifies the terminal that the resource allocation is performed based on the MDBV.

Optionally, if the downlink resource allocation is performed, the network side device determines, according to the mapping relationship between the flow and the logical channel, the MDBV corresponding to the logical channel; or

Optionally, if the Flow and the logical channel adopt a 1:1 mapping, the network side device uses the MDBV corresponding to the Flow as the MDBV corresponding to the logical channel; or

Optionally, the network side device determines, at the MAC layer, an MDBV corresponding to the resource allocation object.

Optionally, before the MAC layer determines the MDBV corresponding to the resource allocation object, the network side device notifies the mapping relationship between the MAC layer Flow and the logical channel through the SDAP or the RRC layer; or

The network side device notifies the MDBV corresponding to the MAC layer logical channel through the SDAP or the RRC layer; or

The network side device notifies the MDBV corresponding to the MAC layer logical channel through the SDAP layer.

Optionally, if the resource allocation object is a logical channel group, the method further includes:

The network side device notifies the mapping relationship between the MAC layer logical channel and the logical channel group through the RRC layer.

Optionally, if the downlink resource allocation is performed, the network side device uses the size of the token bucket controlled by the MDBV according to the logical channel, and the token bucket that has been used by the logical channel in the time period (N-PDB, N) The number of tokens M determines the number of available tokens in the token bucket corresponding to the logical channel; or

If the uplink resource allocation is performed, the logical channel group of the network side device is used for the size of the token bucket controlled by the MDBV and the token within the token bucket that has been used by the logical channel group in the N-PDB, N] The number M determines the number of available tokens in the token bucket corresponding to the logical channel group;

Where N is the scheduling moment, and the PDB is the packet delay budget corresponding to the logical channel.

Optionally, the network side device determines, according to the following manner, a PDB corresponding to the logical channel:

The network side device determines, according to a mapping relationship between the flow and the logical channel, a 5QI corresponding to all flows that can be mapped to the logical channel or a 5QI corresponding to all flows that are actually mapped to the logical channel;

The network side device determines, according to the 5QI corresponding to the Flow, the largest PDB as the PDB corresponding to the logical channel.

Optionally, if the downlink resource allocation is performed, the network side device uses, as the logic, a difference between the MDBV corresponding to the logical channel and the number of tokens actually used in the token bucket for MDBV control. The amount of data that the channel can allocate resources;

The network side device performs resources for the logical channel according to a minimum value between the number of available tokens in the token bucket used by the MDBV control and the actual data volume of the current logical channel to be allocated. distribution.

Optionally, if the uplink resource allocation is performed, the network side device, the MDBV corresponding to the logical channel group, and the token used in the MDBV control token bucket corresponding to the logical channel group are actually used. The difference of the number is used as the number of available tokens in the token bucket corresponding to the logical channel group;

The network side device allocates resources to the logical channel group according to a minimum value between the number of available tokens in the token bucket corresponding to the logical channel group and the data amount of the current logical channel to be allocated. .

The present application has been described above with reference to block diagrams and/or flowchart illustrations of a method, apparatus (system) and/or computer program product according to embodiments of the present application. It will be understood that one block of the block diagrams and/or flowchart illustrations and combinations of blocks of the block diagrams and/or flowchart illustrations can be implemented by computer program instructions. These computer program instructions may be provided to a general purpose computer, a processor of a special purpose computer, and/or other programmable data processing apparatus to produce a machine such that instructions for execution via a computer processor and/or other programmable data processing apparatus are created for A method of implementing the functions/actions specified in the block diagrams and/or flowchart blocks.

Accordingly, the application can also be implemented in hardware and/or software (including firmware, resident software, microcode, etc.). Still further, the application can take the form of a computer program product on a computer usable or computer readable storage medium having computer usable or computer readable program code embodied in a medium for use by an instruction execution system or Used in conjunction with the instruction execution system. In the context of the present application, a computer usable or computer readable medium can be any medium that can contain, store, communicate, communicate, or transport a program for use by an instruction execution system, apparatus or device, or in conjunction with an instruction execution system, Used by the device or device.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims

A method for resource allocation, characterized in that the method comprises:

The terminal determines a maximum data burst capacity MDBV corresponding to the logical channel and a token bucket for MDBV control;

And the terminal performs resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control.
The method according to claim 1, wherein the determining, by the terminal, the MDBV corresponding to the logical channel and the token bucket for the MDBV control, the method further includes:

The terminal determines that the logical channel establishment is complete; and/or,

The terminal receives the notification that the network side device needs to perform resource allocation based on the MDBV.
The method of claim 1, wherein the determining, by the terminal, the MDBV corresponding to the logical channel comprises:

The terminal determines the MDBV corresponding to the logical channel according to the mapping relationship between the flowFlow and the logical channel.
The method according to claim 3, wherein the terminal determines the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel, including:

If the 1:1 mapping is used for the flow and the logical channel, the terminal uses the MDBV corresponding to the Flow as the MDBV corresponding to the logical channel; or

If the flow and the logical channel adopt the M:1 mapping, the terminal uses the sum of the MDBVs corresponding to the Flows that can be mapped to the logical channel as the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel; or

If the Flow and the logical channel adopt the M:1 mapping, the terminal will use the sum of the MDBVs corresponding to the Flows actually mapped to the logical channel as the MDBV corresponding to the logical channel according to the Flow and logical channel mapping relationship; M is a positive integer.
The method of claim 4, wherein the determining, by the terminal, the MDBV corresponding to the logical channel comprises:

The terminal determines an MDBV corresponding to the logical channel at the medium access control MAC layer.
The method according to claim 5, wherein before the determining, by the MAC layer, the MDBV corresponding to the logical channel, the terminal further includes:

The terminal notifies the mapping relationship between the MAC layer Flow and the logical channel through the protocol data adaptation layer SDAP or the radio resource control RRC layer; or

The terminal notifies the mapping relationship between the MAC layer Flow and the logical channel and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or

The terminal notifies the MDBV corresponding to the logical channel of the MAC layer through the SDAP or the RRC layer; or

The terminal notifies the MAC layer to actually map to the flow of the logical channel through the SDAP layer; or

The terminal notifies the MAC layer to actually map to the flow of the logical channel and the MDBV corresponding to the QFI through the SDAP layer; or

The terminal device notifies the MDBV corresponding to the MAC layer logical channel through the SDAP layer.
The method according to claim 1, wherein the size of the token bucket for MDBV control is an MDBV corresponding to a logical channel.
The method according to claim 1, wherein the terminal determines the number of available tokens in the token bucket used by the MDBV control logical channel, including:

Determining, by the terminal, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and using the difference between the size of the token bucket and the M as the Number of available tokens in the token bucket corresponding to the logical channel;

Where N is the scheduling time, and the PDB is the data packet delay budget corresponding to the logical channel.
The method according to claim 8, wherein the terminal corresponds to the PDB by the logical channel in the following manner:

Determining, by the terminal, the 5QI corresponding to all flows that are mapped to the logical channel or the 5QIs corresponding to all flows that are actually mapped to the logical channel according to the mapping relationship between the flow and the logical channel;

The terminal determines, according to the 5QI corresponding to the Flow, the largest PDB as the PDB corresponding to the logical channel.
The method according to claim 1, wherein the terminal performs resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control, including:

The terminal sorts logical channels having PBR tokens and having data transmission requirements according to logical channel priority descending order, and then sequentially performs first round resource allocation on each logical channel based on PBR, and simultaneously updates each logical channel corresponding to each logical channel. The number of tokens in the token bucket of the PBR token bucket, and the number of available tokens in the token bucket for the MDBV control corresponding to the logical channel after the PBR-based resource allocation is completed for the logical channel with the MDBV requirement;

After determining that there are remaining resources, the terminal performs a second round of resource allocation in descending order of logical channel priorities for all logical channels having data transmission requirements:

For a logical channel with MDBV requirements, the logical channel allows the amount of data to be allocated in the second round of resource allocation process to take the logical channel for the number of available tokens in the token bucket controlled by the MDBV and the logic The channel has a smaller value of the data of the resource to be allocated, and performs resource allocation on the logical channel; if the logical channel that needs to be allocated is a logical channel that is not required by the MDBV, the terminal currently allocates resources according to the logical channel. The amount of data is allocated to the logical channel.
The method according to claim 10, wherein after the terminal performs the second round of resource allocation in descending order of logical channel priority for all logical channels having data transmission requirements, the terminal further includes:

If the terminal determines that there are remaining resources, the remaining to-be-transmitted data is allocated according to the logical channel priority descending order of all data transmission requirements until the resources are exhausted or the resources to be transmitted of all logical channels are allocated resources.
The method according to claim 1, wherein the terminal performs resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control, and further includes:

The terminal sorts logical channels with available PBR tokens and data transmission requirements according to logical channel priority descending order, and then performs first round resource allocation on each logical channel based on PBR, and updates each logical channel correspondingly. The number of tokens in the PBR token bucket, and the number of available tokens in the token bucket controlled by the MDBV after the PBR-based resource allocation is completed for the logical channel with the MDBV requirement;

After determining that there are remaining resources, the terminal performs a second round of resource allocation in descending order of logical channel priorities for all logical channels having data transmission requirements:

For a logical channel with MDBV requirements, the logical channel allows the amount of data to be allocated in the second round of resource allocation process to take the logical channel for the number of available tokens in the token bucket controlled by the MDBV and the logic a smaller value of the data amount of the current resource to be allocated, and performing resource allocation on the logical channel; if the logical channel currently required to be allocated is a logical channel that does not have an MDBV requirement and includes a GBR service, the terminal pairs the logic The channel performs resource allocation.
The method according to claim 12, wherein after the terminal performs the second round of resource allocation in descending order of logical channel priority for all logical channels having data transmission requirements, the terminal further includes:

If the terminal determines that there are remaining resources, the terminal allocates resources to the remaining to-be-transmitted data in descending order of all logical channel priorities having data transmission requirements until the resources are exhausted or the data to be transmitted of all logical channels are allocated. Resources.
The method according to claim 10 or 12, wherein the number of tokens that can be used in the token bucket for MDBV control corresponding to the logical channel is the MDBV and the corresponding channel of the logical channel. The difference between the number of tokens actually used in the token bucket for the MDBV control corresponding to the logical channel.
The method according to claim 10 or 12, wherein the terminal updates the logical channel for the number of available tokens in the token bucket controlled by the MDBV, including:

Determining, by the terminal, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and using the difference between the size of the token bucket and the M as the Number of available tokens in the token bucket corresponding to the object;

Where N is the scheduling time, and the PDB is the data packet delay budget corresponding to the logical channel.
A method for resource allocation, characterized in that the method comprises:

The network side device determines the MDBV corresponding to the resource allocation object and the token bucket used for the MDBV control;

The network side device performs resource allocation for the resource allocation object according to the determined MDBV and the token bucket for MDBV control;

If the uplink resource allocation is performed, the resource allocation target is a logical channel group; and when downlink resource allocation is performed, the resource allocation object is a logical channel.
The method according to claim 16, wherein before the network side device determines the MDBV corresponding to the resource allocation object and the token bucket for the MDBV control, the network side device further includes:

The network side device determines that the logical channel establishment is completed; and/or,

The network side device determines that resource allocation needs to be performed based on the MDBV according to the system load.
The method of claim 17 further comprising:

If the uplink resource allocation is performed, the network side device determines that the resource allocation needs to be performed based on the MDBV according to the system load, and notifies the terminal that the resource allocation needs to be performed based on the MDBV.
The method of claim 16, wherein the network side device determines the MDBV corresponding to the resource allocation object, including:

If the downlink resource allocation is performed, the network side device determines the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel; or

If the uplink resource allocation is performed, the network side device determines the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel, and uses the sum of the MDBVs corresponding to the logical channels in the same logical channel group as the MDBV corresponding to the logical channel group; or ,

If the uplink resource allocation is performed, the network side device uses the sum of the MDBVs corresponding to the logical channels reported by the terminal as the MDBV corresponding to the logical channel group; or

If the uplink resource allocation is performed, the network side device receives the MDBV corresponding to the logical channel group reported by the terminal.
The method according to claim 19, wherein the network side device determines the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel, including:

If the Flow and the logical channel adopt a 1:1 mapping, the network side device uses the MDBV corresponding to the Flow as the MDBV corresponding to the logical channel; or

If the flow and the logical channel adopt the M:1 mapping, the network side device uses, according to the mapping relationship between the flow and the logical channel, the sum of the MDBVs corresponding to the flows that can be mapped to the logical channel as the MDBV corresponding to the logical channel; or ,

If the flow and the logical channel adopt the M:1 mapping, the network side device will use the sum of the MDBVs corresponding to the Flows actually mapped to the logical channel as the MDBV corresponding to the logical channel according to the Flow and logical channel mapping relationship; , M is a positive integer.
The method of claim 20, wherein the network side device determines the MDBV corresponding to the resource allocation object, including:

The network side device determines, at the MAC layer, an MDBV corresponding to the resource allocation object.
The method of claim 21, wherein before the MAC layer determines the MDBV corresponding to the resource allocation object, the network side device further includes:

The network side device notifies the mapping relationship between the MAC layer Flow and the logical channel through the SDAP or the RRC layer; or

The network side device notifies the mapping relationship between the MAC layer Flow and the logical channel and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or

The network side device notifies the MDBV corresponding to the MAC layer logical channel through the SDAP or the RRC layer; or

The network side device notifies the MAC layer to actually map to the flow of the logical channel through the SDAP layer; or

The network side device notifies the MAC layer to actually map to the flow of the logical channel and the MDBV corresponding to the QFI through the SDAP layer; or

The network side device notifies the MDBV corresponding to the MAC layer logical channel through the SDAP layer.
The method of claim 22, wherein if the resource allocation object is a logical channel group, the method further comprises:

The network side device notifies the mapping relationship between the MAC layer logical channel and the logical channel group through the RRC layer.
The method according to claim 16, wherein the network side device resource allocation object is used for the number of available tokens in the token bucket controlled by the MDBV, including:

If the downlink resource allocation is performed, the network side device uses the size of the token bucket controlled by the MDBV according to the logical channel and the token token in the token bucket that has been used by the logical channel in the time period (N-PDB, N) The number M determines the number of available tokens in the token bucket corresponding to the logical channel; or

If the uplink resource allocation is performed, the logical channel group of the network side device is used for the size of the token bucket controlled by the MDBV and the token within the token bucket that has been used by the logical channel group in the N-PDB, N] The number M determines the number of available tokens in the token bucket corresponding to the logical channel group;

Where N is the scheduling moment, and the PDB is the packet delay budget corresponding to the logical channel.
The method according to claim 24, wherein the network side device determines the PDB corresponding to the logical channel group by:

The network side device determines, according to a mapping relationship between the flow and the logical channel, a 5QI corresponding to all flows that can be mapped to the logical channel or a 5QI corresponding to all flows that are actually mapped to the logical channel;

The network side device determines, according to the 5QI corresponding to the Flow, the largest PDB as the PDB corresponding to the logical channel.
The method according to any one of claims 16 to 25, wherein the network side device performs resource allocation for the resource allocation object according to the determined MDBV and the token bucket for MDBV control, including :

If the downlink resource allocation is performed, the network side device uses, as the logical channel MDBV, a difference between the MDBV corresponding to the logical channel and the number of tokens actually used in the token bucket for MDBV control. Number of tokens available in the token bucket;

The network side device performs resource allocation for the logical channel according to a minimum value between the number of available tokens in the token bucket corresponding to the logical channel MDBV and the data amount of the current logical channel to be allocated.
The method according to any one of claims 16 to 25, wherein the network side device performs resource allocation for the resource allocation object according to the determined token bucket for MDBV control and the MDBV, including :

If the uplink resource allocation is performed, the network side device compares the MDBV corresponding to the logical channel group with the number of tokens actually used in the token bucket for MDBV control corresponding to the logical channel group. The value is the number of available tokens in the token bucket corresponding to the logical channel;

The network side device performs resource allocation for the logical channel group according to a minimum value between the number of available tokens in the token bucket corresponding to the logical channel group and the actual data volume to be transmitted of the current logical channel group.
A terminal for performing resource allocation, wherein the terminal comprises: a processor, a memory, and a transceiver;

The processor is configured to read a program in the memory and execute:

Determining a MDBV corresponding to the logical channel and a token bucket for MDBV control; performing resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control.
The terminal of claim 28, wherein the processor is further configured to:

Before determining the MDBV corresponding to the logical channel and the token bucket for the MDBV control, determining that the logical channel establishment is completed; and/or receiving the notification that the network side device needs to perform resource allocation based on the MDBV.
The terminal according to claim 28, wherein the processor is specifically configured to:

The MDBV corresponding to the logical channel is determined according to the mapping relationship between the Flow and the logical channel.
The terminal according to claim 30, wherein the processor is specifically configured to:

If the Flow and the logical channel adopt a 1:1 mapping, the MDBV corresponding to the Flow is used as the MDBV corresponding to the logical channel;

Or if the Flow and the logical channel adopt the M:1 mapping, according to the mapping relationship between the Flow and the logical channel, the sum of the MDBVs corresponding to the Flows that can be mapped to the logical channel is used as the MDBV corresponding to the logical channel;

Or if the Flow and the logical channel adopt the M:1 mapping, the sum of the MDBVs corresponding to the Flows actually mapped to the logical channels is used as the MDBV corresponding to the logical channel according to the Flow and logical channel mapping relationship; wherein, the M is Is a positive integer.
The terminal according to claim 31, wherein the processor is specifically configured to:

The MDBV corresponding to the logical channel is determined at the MAC layer.
The terminal according to claim 32, wherein the processor is further configured to:

Before the MDBV corresponding to the logical channel is determined by the MAC layer, the mapping relationship between the MAC layer Flow and the logical channel is notified through the SDAP or the RRC layer; or

Notifying the mapping relationship between the MAC layer Flow and the logical channel and the MDBV corresponding to the QFI through the SDAP or RRC layer; or

Notifying the MDBV corresponding to the MAC layer logical channel through the SDAP or RRC layer; or notifying the MAC layer to actually map to the Flow of the logical channel through the SDAP layer; or

Notifying the MAC layer to actually map to the flow channel of the logical channel and the MDBV corresponding to the QFI through the SDAP layer; or

The MDBV corresponding to the MAC layer logical channel is notified through the SDAP layer.
The terminal according to claim 28, wherein the size of the token bucket for MDBV control is an MDBV corresponding to a logical channel.
The terminal of claim 28, wherein the processor is further configured to:

Determining, by the logical channel, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and comparing the size of the token bucket with the difference of M as the logical channel Number of tokens available in the token bucket;

Where N is the scheduling time, and the PDB is the data packet delay budget corresponding to the logical channel.
The terminal according to claim 35, wherein the processor is specifically configured to: determine a PDB corresponding to the logical channel by:

Determining, according to a mapping relationship between the flow and the logical channel, a 5QI corresponding to all flows that are mapped to the logical channel or a 5QI corresponding to all flows that are actually mapped to the logical channel; determining, according to the 5QI corresponding to the Flow, a maximum PDB as a The PDB corresponding to the logical channel.
The terminal according to claim 28, wherein the processor is specifically configured to:

The terminal sorts logical channels with available PBR tokens and data transmission requirements according to logical channel priority descending order, and then performs first round resource allocation on each logical channel based on PBR, and updates each logical channel correspondingly. The number of tokens in the PBR token bucket, and the number of available tokens for the MDBV control after the PBR-based resource allocation is completed for the logical channel with the MDBV requirement;

After determining that there are remaining resources, the terminal performs a second round of resource allocation in descending order of logical channel priorities for all logical channels having data transmission requirements:

For a logical channel with MDBV requirements, the logical channel allows the amount of data to be allocated in the second round of resource allocation process to take the logical channel for the number of available tokens in the token bucket controlled by the MDBV and the logic The channel has a smaller value of the data of the resource to be allocated, and performs resource allocation on the logical channel; if the logical channel that needs to be allocated is a logical channel that is not required by the MDBV, the terminal currently allocates resources according to the logical channel. The amount of data is allocated to the logical channel.
The terminal according to claim 37, wherein the processor is further configured to:

After performing the second round of resource allocation in descending order of logical channel priority for all logical channels having data transmission requirements, if the terminal determines that there are remaining resources, the logical channel priorities are reversed in order for all data transmission requirements. The remaining data to be transmitted is allocated for resources until resources are exhausted or resources of all logical channels to be transmitted are allocated.
The terminal of claim 28, wherein the processor is further configured to:

The terminal sorts logical channels with available PBR tokens and data transmission requirements according to logical channel priority descending order, and then performs first round resource allocation on each logical channel based on PBR, and updates each logical channel correspondingly. The number of tokens in the PBR token bucket, and the number of available tokens in the token bucket controlled by the MDBV after the PBR-based resource allocation is completed for the logical channel with the MDBV requirement;

After determining that there are remaining resources, the terminal performs a second round of resource allocation in descending order of logical channel priorities for all logical channels having data transmission requirements:

For a logical channel with MDBV requirements, the logical channel allows the amount of data to be allocated in the second round of resource allocation process to take the logical channel for the number of available tokens in the token bucket controlled by the MDBV and the logic a smaller value of the data amount of the current resource to be allocated, and performing resource allocation on the logical channel; if the logical channel currently required to be allocated is a logical channel that does not have an MDBV requirement and includes a GBR service, the terminal pairs the logic The channel performs resource allocation.
The terminal according to claim 39, wherein the processor is further configured to:

After performing the second round of resource allocation in descending order of logical channel priority for all logical channels having data transmission requirements, if the terminal determines that there are remaining resources, the logical channel priorities are reversed in order for all data transmission requirements. The remaining data to be transmitted is allocated for resources until resources are exhausted or resources of all logical channels to be transmitted are allocated.
The terminal according to claim 37 or 39, wherein the number of tokens that can be used in the token bucket for MDBV control corresponding to the logical channel is the MDBV and the corresponding channel of the logical channel. The difference between the number of tokens actually used in the token bucket for the MDBV control corresponding to the logical channel.
The terminal according to claim 37 or 39, wherein the processor is specifically configured to:

Determining, by the logical channel, the number M of tokens that have been actually used in the time period (N-PDB, N) in the token bucket controlled by the MDBV, and using the difference between the size of the token bucket and M as the object Number of tokens available in the token bucket;

Where N is the scheduling time, and the PDB is the data packet delay budget corresponding to the logical channel.
A network side device for performing resource allocation, wherein the network side device comprises: a processor, a memory, and a transceiver;

The processor is configured to read a program in the memory and execute:

Determining, by the MDBV and the token bucket for the MDBV control, resource allocation for the resource allocation object In the case of allocation, the resource allocation object is a logical channel group; if downlink resource allocation is performed, the resource allocation object is a logical channel.
The network side device according to claim 43, wherein the processor is further configured to:

Before determining the MDBV corresponding to the resource allocation object and the token bucket for MDBV control, determining that the logical channel establishment is completed; and/or determining that resource allocation based on the MDBV is required according to the system load.
The network side device according to claim 44, wherein the network side device comprises:

The notification module is configured to notify the terminal that resource allocation based on the MDBV is performed after determining that the resource allocation needs to be performed based on the MDBV according to the system load.
The network side device according to claim 43, wherein the processor is specifically configured to:

If the downlink resource allocation is performed, determining the MDBV corresponding to the logical channel according to the mapping relationship between the flow and the logical channel;

If the uplink resource allocation is performed, the MDBV corresponding to the logical channel is determined according to the mapping relationship between the flow and the logical channel, and the sum of the MDBVs corresponding to the logical channels in the same logical channel group is used as the MDBV corresponding to the logical channel group; or

If the uplink resource allocation is performed, the sum of the MDBVs corresponding to the logical channels reported by the terminal is used as the MDBV corresponding to the logical channel group; or

If the uplink resource allocation is performed, the MDBV corresponding to the logical channel group reported by the terminal is received.
The network side device according to claim 46, wherein the processor is specifically configured to:

If the Flow and the logical channel adopt a 1:1 mapping, the MDBV corresponding to the Flow is used as the MDBV corresponding to the logical channel; or

If the Flow and the logical channel adopt the M:1 mapping, the sum of the MDBVs corresponding to the Flows that can be mapped to the logical channels is used as the MDBV corresponding to the logical channel according to the mapping relationship between the Flow and the logical channel; or

If the Flow and the logical channel adopt the M:1 mapping, the sum of the MDBVs corresponding to the Flows actually mapped to the logical channel is used as the MDBV corresponding to the logical channel according to the Flow and logical channel mapping relationship; wherein the M is A positive integer.
The network side device according to claim 47, wherein the processor is specifically configured to:

The MDBV corresponding to the resource allocation object is determined at the MAC layer.
The network side device according to claim 48, wherein the processor is further configured to:

Before the MAC layer determines the MDBV corresponding to the resource allocation object, notifying the mapping relationship between the MAC layer Flow and the logical channel through the SDAP or the RRC layer; or

Notifying the mapping relationship between the MAC layer Flow and the logical channel and the MDBV corresponding to the QFI through the SDAP or RRC layer; or

Notifying the MDBV corresponding to the MAC layer logical channel through the SDAP or RRC layer; or

Notifying the MAC layer to actually map to the flow of the logical channel through the SDAP layer; or

Notifying the MAC layer to actually map to the flow channel of the logical channel and the MDBV corresponding to the QFI through the SDAP layer; or

The MDBV corresponding to the MAC layer logical channel is notified through the SDAP layer.
The network side device according to claim 49, wherein if the resource allocation object is a logical channel group, the processor is further configured to:

The mapping relationship between the MAC layer logical channel and the logical channel group is notified by the RRC layer.
The network side device according to claim 43, wherein the processor is further configured to:

If the downlink resource allocation is performed, the size is determined according to the size of the token bucket used by the logical channel for MDBV control and the number M of tokens in the token bucket that the logical channel has used in the time period (N-PDB, N) Number of available tokens in the token bucket corresponding to the logical channel; or,

If uplink resource allocation is performed, it is determined according to the size of the token bucket used by the logical channel group for MDBV control and the number M of tokens in the token bucket that have been used by the logical channel group in the time period (N-PDB, N) The number of available tokens in the token bucket corresponding to the logical channel group;

Where N is the scheduling moment, and the PDB is the packet delay budget corresponding to the logical channel.
The network side device according to claim 51, wherein the processor is specifically configured to: determine a PDB corresponding to the logical channel by:

Determining, according to a mapping relationship between the flow and the logical channel, a 5QI corresponding to all flows that are mapped to the logical channel or a 5QI corresponding to all flows that are actually mapped to the logical channel; determining, according to the 5QI corresponding to the Flow, a maximum PDB as a The PDB corresponding to the logical channel.
The network side device according to any one of claims 43 to 52, wherein the processor is specifically configured to:

If the downlink resource allocation is performed, the difference between the MDBV corresponding to the logical channel and the number of tokens actually used in the token bucket for the MDBV control is used as the data amount of the logical channel capable of allocating resources; The minimum value between the number of available tokens in the token bucket corresponding to the logical channel MDBV and the data amount of the actual logical channel to be allocated is resource allocation for the logical channel.
The network side device according to any one of claims 43 to 52, wherein the processor is specifically configured to:

If the uplink resource allocation is performed, the difference between the MDBV corresponding to the logical channel group and the number of tokens actually used in the token bucket for MDBV control corresponding to the logical channel group is used as the logic. The number of available tokens in the token bucket corresponding to the channel group; the minimum value between the number of tokens available in the token bucket corresponding to the logical channel group and the actual amount of data to be transmitted in the current logical channel group Resource allocation is performed for the logical channel group.
A terminal for performing resource allocation, wherein the terminal comprises:

a first determining module, configured to determine an MDBV corresponding to the logical channel and a token bucket for the MDBV control;

And a first allocation module, configured to perform resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control.
A network side device that performs resource allocation, where the network side device includes:

a second determining module, configured to determine an MDBV corresponding to the resource allocation object and a token bucket used for MDBV control;

a second allocation module, configured to perform resource allocation for the resource allocation object according to the determined MDBV and the token bucket for MDBV control;

If the uplink resource allocation is performed, the resource allocation target is a logical channel group; and when downlink resource allocation is performed, the resource allocation object is a logical channel.