CN110475284B - Method and device for resource allocation - Google Patents

Method and device for resource allocation Download PDF

Info

Publication number
CN110475284B
CN110475284B CN201810438523.2A CN201810438523A CN110475284B CN 110475284 B CN110475284 B CN 110475284B CN 201810438523 A CN201810438523 A CN 201810438523A CN 110475284 B CN110475284 B CN 110475284B
Authority
CN
China
Prior art keywords
mdbv
logic channel
resource allocation
logical channel
channel
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810438523.2A
Other languages
Chinese (zh)
Other versions
CN110475284A (en
Inventor
赵亚利
皮埃尔
刘佳敏
谌丽
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Datang Mobile Communications Equipment Co Ltd
Original Assignee
Telecommunications Science and Technology Research Institute Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telecommunications Science and Technology Research Institute Co Ltd filed Critical Telecommunications Science and Technology Research Institute Co Ltd
Priority to CN201810438523.2A priority Critical patent/CN110475284B/en
Priority to PCT/CN2019/085380 priority patent/WO2019214524A1/en
Publication of CN110475284A publication Critical patent/CN110475284A/en
Application granted granted Critical
Publication of CN110475284B publication Critical patent/CN110475284B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0252Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/52Allocation or scheduling criteria for wireless resources based on load
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/53Allocation or scheduling criteria for wireless resources based on regulatory allocation policies

Abstract

The invention discloses a method and a device for resource allocation, which are used for solving the problem that no clear solution is available for a resource allocation method based on MDBV data transmission in a 5G system in the prior art. In the embodiment of the invention, the terminal and the network side equipment firstly determine the MDBV corresponding to the object and the token bucket used for controlling the MDBV, and carry out resource allocation on the object according to the determined MDBV and the token bucket used for controlling the MDBV. In the embodiment of the invention, the resources for data transmission are distributed according to the token bucket for MDBV control, so that the data volume sent by each QoS Flow is ensured not to exceed the MDBV limit, and the delay sensitive service is prevented from preempting the resources of other services when the system load is heavier.

Description

Method and device for resource allocation
Technical Field
The present invention relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for resource allocation.
Background
For a 5G NR (New Radio, New air interface) system, the core network may configure a QoS (Quality of Service) Profile for each Flow. The RAN (Radio Access Network, Access Network) performs QoS management for QoS Profile configured for each Flow based on the core Network. One parameter in QoS profile is 5QI (5G QoS Identifier, fifth generation mobile communication system quality of service Identifier). MDBV (Maximum Data Burst Volume) is one parameter contained in 5 QI. While the 5G NR system mainly supports three types of services: the first is an enhanced Mobile Broadband (eMBB) service, the second is a massive Machine Type communication (mtc) service, and the third is a very high-reliability and Low-Latency communication (URLLC) service.
Among them, URLLC traffic has a relatively high delay requirement, and is therefore generally referred to as delay-sensitive GBR traffic. For such services, when the core network defines QoS profile based on Flow, the 5QI generally includes MDBV parameters, where MDBV indicates the maximum amount of data that the 5G access network needs to handle one Flow within the PDB time range, and the 5QI may be standardized or non-standardized.
However, there is no clear solution for the resource allocation method based on MDBV data transmission in the prior art for the 5G system.
Disclosure of Invention
The invention provides a method and a device for resource allocation, which are used for solving the problem that no clear solution is available for a resource allocation method based on MDBV data transmission in a 5G system in the prior art.
In the first aspect, a terminal determines an MDBV corresponding to a logical channel and a token bucket for MDBV control; and then performing resource allocation on the logical channel according to the determined MDBV and the token bucket for MDBV control.
In the embodiment of the invention, the terminal firstly determines the MDBV corresponding to the logical channel and the token bucket used for MDBV control, and then performs resource allocation for the logical channel according to the determined MDBV and the token bucket used for MDBV control. In the embodiment of the invention, the resources for data transmission are distributed according to the token bucket for MDBV control, so that the data volume sent by each QoS Flow is ensured not to exceed the MDBV limit, and the delay sensitive service is prevented from preempting the resources of other services when the system load is heavier.
In some specific implementations, after the terminal determines that the logical channel is established, determining an MDBV corresponding to the logical channel and a token bucket for MDBV control; and/or after the terminal receives a notification which is sent by the network side equipment and needs to allocate resources based on the MDBV, determining the MDBV corresponding to the logical channel and a token bucket used for controlling the MDBV.
In some specific implementations, the terminal determines, in a Medium Access Control (MAC) layer, an MDBV corresponding to a logical channel according to a mapping relationship between a Flow and the logical channel.
In some embodiments, if the Flow and logical channels use 1:1, mapping, wherein the terminal takes the MDBV corresponding to the Flow as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the terminal takes the sum of MDBVs corresponding to the Flow which can be mapped to the logic channel as the MDBVs corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the terminal takes the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
In the embodiment of the invention, the terminal determines the MDBV corresponding to the logic channel according to different conditions, so that the reasonable resource allocation is ensured during resource allocation, and the delay sensitive service is prevented from preempting the resources of other services.
In some specific implementations, before a terminal determines an MDBV corresponding to an object through an MAC layer, the terminal needs to notify a mapping relationship between a Flow and a logical channel of the MAC layer through an SDAP (Radio Resource Control) or RRC (Radio Resource Control) layer; or
The terminal informs the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
The terminal informs the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
The terminal informs the MAC layer of the Flow actually mapped to the logic channel through the SDAP layer; or
The terminal informs the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And after the terminal informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer, the MDBV corresponding to the object is determined through the MAC layer.
In the embodiment of the invention, as 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 relation, a plurality of ways of informing the MAC layer are introduced, thereby being more diversified and ensuring that the terminal can determine the MDBV corresponding to the logical channel at the MAC layer.
In the embodiment of the invention, as 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 relation, a plurality of ways of informing the MAC layer are introduced to ensure that the terminal can determine the MDBV corresponding to the logical channel at the MAC layer.
In some implementations, the token bucket for MDBV control is sized for an MDBV for a logical channel. The terminal determines the number M of tokens which are actually used in a token bucket for MDBV control in a logical channel within a time period (N-PDB, N), and takes 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, wherein N is scheduling time, and PDB is data packet delay budget corresponding to the logical channel.
In some specific implementations, the terminal determines the PDB corresponding to the logical channel by:
determining 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the logic channel and the Flow mapping relation; and determining the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
In the embodiment of the invention, the number of the available tokens in the token bucket corresponding to the logical channel is determined according to the size of the token bucket for MDBV control and the number of the tokens actually used in the token bucket for determining the logical channel for MDBV control in the time period (N-PDB, N), and the resource allocation is carried out according to the number of the available tokens in the token bucket corresponding to the determined logical channel, so that the data volume sent by each QoS Flow is fully ensured not to exceed the MDBV limit, and the delay sensitive service is prevented from preempting the resources of other services when the system load is heavy.
In some implementations, in allocating resources, for logical channels with MDBV requirements:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens in an MDBV token bucket corresponding to the logic channel after completing PBR-based resource allocation on the logic channel;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount of the resources to be allocated currently by the logic channel, and allocating the resources to the logic channel; and if the logical channel needing to be allocated currently is the logical channel without the MDBV requirement, the terminal allocates the resources to the logical channel according to the data volume of the resources to be allocated currently of the logical channel.
And step 3: and if the terminal determines that the residual resources exist, performing resource allocation on the residual data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the resources are allocated to the data to be transmitted of all the logic channels.
And when allocating resources, for the logical channels without MDBV requirement:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens used for MDBV control of the logic channel with MDBV requirements after completing PBR-based resource allocation;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount of the resources to be allocated currently by the logic channel, and allocating the resources to the logic channel; if the current logical channel needing to be allocated is the logical channel without MDBV requirement and containing GBR (guaranteed Bit Rate) service, the terminal allocates resources to the logical channel;
and step 3: and if the terminal determines that the residual resources exist, the terminal performs resource allocation on the residual data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the resources are allocated to the data to be transmitted of all the logic channels.
The number of the tokens which can be used in the token bucket for MDBV control corresponding to the logical channel is the difference value between the MDBV corresponding to the logical channel and the number of the tokens which have been actually used in the token bucket for MDBV control corresponding to the logical channel.
The terminal determines the number M of tokens which are actually used in a token bucket for MDBV control by a logical channel within a time period (N-PDB, N), and the difference value between the size of the token bucket and the M is used as the number of available tokens in the token bucket corresponding to the object, so that the purpose of updating the number of available tokens in the token bucket for MDBV control by the logical channel with MDBV requirements after PBR-based resource allocation is completed is achieved.
In the embodiment of the invention, when the resources are allocated, different modes are adopted for the logic channel without the MDBV requirement and the logic channel with the MDBV requirement, so that the data volume sent by each QoS Flow is further ensured not to exceed the MDBV limit, and the time delay sensitive service is prevented from preempting the resources of other services when the system load is heavier.
In a second aspect, an embodiment of the present invention provides a method for resource allocation, where the method includes:
the network side equipment determines an MDBV corresponding to the resource allocation object and a token bucket for controlling the MDBV; then the network side equipment performs resource allocation on the resource allocation object according to the determined MDBV and the token bucket for MDBV control; if uplink resource allocation is carried out, the resource allocation object is a logical channel group; and if the downlink resource allocation is carried out, the resource allocation object is a logical channel.
According to the method, the network side equipment determines the MDBV corresponding to the resource allocation object and the token bucket used for MDBV control, and then performs resource allocation on the resource allocation object according to the determined MDBV and the token bucket used for MDBV control. In the embodiment of the invention, the resources for data transmission are distributed according to the token bucket for MDBV control, so that the data volume sent by each QoS Flow is ensured not to exceed the MDBV limit, and the delay sensitive service is prevented from preempting the resources of other services when the system load is heavier.
In some specific implementations, after the network side device determines that the establishment of the logical channel is completed, it determines an MDBV and a token bucket for MDBV control, which correspond to the resource allocation object; and/or determining the MDBV corresponding to the resource allocation object and a token bucket for controlling the MDBV after determining that the resource allocation needs to be carried out based on the MDBV according to the system load.
And if the uplink resource allocation is carried out, the network side equipment informs the terminal of the resource allocation needing to be carried out based on the MDBV after determining that the resource allocation needs to be carried out based on the MDBV according to the system load.
In the embodiment of the invention, because the network side equipment determines the MDBV corresponding to the logic channel according to different conditions, the reasonable resource allocation is ensured during resource allocation, and the time delay sensitive service is prevented from preempting the resources of other services.
In some specific implementations, if downlink resource allocation is performed, the network side device determines an MDBV corresponding to a logical channel according to a mapping relationship between Flow and the logical channel; or
If uplink resource allocation is carried out, the network side equipment determines the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel, and takes the sum of the MDBVs corresponding to the logic channels in the same logic channel group as the MDBV corresponding to the logic channel group; or
If uplink resource allocation is carried out, the network side equipment takes the sum of MDBVs corresponding to the logical channels reported by the terminal as the MDBV corresponding to the logical channel group; or
And if the uplink resource allocation is carried out, the network side equipment receives the MDBV corresponding to the logical channel group reported by the terminal.
In some implementations, if the Flow and logical channels use 1:1, the network side equipment takes the MDBV corresponding to the Flow as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the network side equipment takes the sum of MDBVs corresponding to the Flow which can be mapped to the logic channel as the MDBVs corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the network side equipment takes the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
In some specific implementations, before a network side device determines an MDBV corresponding to a resource allocation object through an MAC layer, the network side device needs to notify a mapping relationship between a Flow and a logical channel of the MAC layer through an SDAP (Radio resource control) or RRC (Radio resource control) layer; or
The network side equipment informs the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
The network side equipment informs the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
The network side equipment informs the MAC layer of the Flow actually mapped to the logic channel through the SDAP layer; or
The network side equipment informs the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And after the network side equipment informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer, determining the MDBV corresponding to the resource allocation object through the MAC layer.
In some specific implementations, when performing uplink resource allocation, the MAC layer does not know the mapping relationship between the logical channel and the logical channel group, and therefore the RRC layer also needs to notify the mapping relationship between the logical channel and the logical channel group of the MAC layer, so that the network side device can determine the MDBV corresponding to the logical channel group in the MAC layer.
In some specific implementations, if the resource allocation pair is a logical channel group, the network side device notifies, through the RRC layer, a mapping relationship between a MAC layer logical channel and the logical channel group.
In the embodiment of the invention, because the network side equipment is the MDBV corresponding to the logical channel determined in the MAC layer, but the MAC layer does not know the corresponding mapping relation, a plurality of ways of informing the MAC layer are introduced to ensure that the network side equipment can determine the MDBV corresponding to the logical channel in the MAC layer.
In some implementations, the token bucket for MDBV control is sized for an MDBV for a logical channel. The network side equipment determines the number M of tokens which are actually used in a token bucket for MDBV control by a logical channel in a time period (N-PDB, N), and takes 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, wherein N is scheduling time, and PDB is data 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:
determining 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the logic channel and the Flow mapping relation; and determining the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
In the embodiment of the invention, the number of the available tokens in the token bucket corresponding to the resource allocation object is determined according to the size of the token bucket for MDBV control and the number of the tokens actually used in the token bucket for determining the resource allocation object for MDBV control in the time period (N-PDB, N), and the resource allocation is carried out according to the number of the available tokens in the token bucket corresponding to the determined resource allocation object, so that the data volume sent by each QoS Flow is fully ensured not to exceed the MDBV limit, and the time delay sensitive service is prevented from preempting the resources of other services when the system load is heavier.
In some specific implementations, if downlink resource allocation is performed, the network side device takes a difference between the MDBV corresponding to the logical channel and the number of tokens that have been actually used in the token bucket for MDBV control as a data amount of resources that can be allocated by the logical channel; and then performing resource allocation on the logic channel according to the minimum value between the number of available tokens in a token bucket corresponding to the logic channel MDBV and the actual data volume to be transmitted of the current logic channel.
In some specific implementations, if uplink resource allocation is performed, the network side device takes a difference between the MDBV corresponding to the logical channel group and the number of actually used tokens in the token bucket for MDBV control corresponding to the logical channel group as the number of available tokens in the token bucket corresponding to the logical channel group; and then, performing resource allocation on the logical channel group according to the minimum value between the number of available tokens in the token bucket corresponding to the logical channel group and the data amount of the actual resource to be allocated of the current logical channel.
In a third aspect, an embodiment of the present invention provides a terminal for resource allocation, where the terminal includes: a processor, a memory, and a transceiver;
wherein the processor is configured to read a program in the memory and execute:
determining an MDBV corresponding to the logic channel and a token bucket for MDBV control; and performing resource allocation on 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 for resource allocation, where the network side device includes: a processor, a memory, and a transceiver;
wherein the processor is configured to read a program in the memory and execute:
determining an MDBV corresponding to the resource allocation object and a token bucket for controlling the MDBV; performing resource allocation on the resource allocation object according to the determined MDBV and the token bucket for MDBV control; if uplink resource allocation is carried out, the resource allocation object is a logical channel group; and if the downlink resource allocation is carried out, the resource allocation object is a logical channel.
In a fifth aspect, an embodiment of the present invention provides a terminal for resource allocation, where the terminal includes:
the system comprises a first determining module, a second determining module and a token bucket, wherein the first determining module is used for determining the MDBV corresponding to a logic channel and the token bucket used for controlling the MDBV;
and the first allocation module is used for allocating resources for the logic 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 for resource allocation, where the network side device includes:
the second determining module is used for determining the MDBV corresponding to the resource allocation object and a token bucket for controlling the MDBV;
a second allocating module, configured to perform resource allocation on the resource allocation object according to the determined MDBV and the token bucket for MDBV control;
if uplink resource allocation is carried out, the resource allocation object is a logical channel group; and if the downlink resource allocation is carried out, the resource allocation object is a logical channel.
In addition, for technical effects brought by any one implementation manner of the second aspect to the sixth aspect, reference may be made to technical effects brought by the implementation manner of the first aspect, and details are not described here.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a diagram illustrating a system for allocating resources according to an embodiment of the present invention;
fig. 2 is a flowchart of a complete method for allocating resources for downlink resources according to an embodiment of the present invention;
fig. 3 is a flowchart of a complete method for allocating resources to a terminal side by using uplink resources according to an embodiment of the present invention;
fig. 4 is a flowchart of a complete method for allocating resources to a network device side by using uplink resources according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a terminal for resource allocation according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a network-side device for resource allocation according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of another terminal for resource allocation according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of another network-side device for resource allocation according to an embodiment of the present invention;
FIG. 9 is a flowchart of a method for allocating resources according to an embodiment of the present invention;
fig. 10 is a flowchart of another method for allocating resources according to an embodiment of the present invention.
Detailed Description
The embodiment of the invention is applied to an application scene of MDBV data transmission in a 5G NR system, and for the 5G NR system, a core network can configure QoS Profile for each Flow. And the RAN performs QoS management for each Flow based on the QoS Profile configured by the core network. One parameter in QoS profile is 5QI, and MDBV is one parameter contained in 5 QI. In the embodiment of the invention, the terminal firstly determines the MDBV corresponding to the object and the token bucket used for MDBV control, and performs resource allocation for the object according to the determined MDBV and the token bucket used for MDBV control. In the embodiment of the invention, the resources for data transmission are distributed according to the token bucket for MDBV control, so that the data volume sent by each QoS Flow is ensured not to exceed the MDBV limit, and the delay sensitive service is prevented from preempting the resources of other services when the system load is heavier.
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, an embodiment of the present invention provides a system for resource allocation, where the system includes: a terminal 100 and a network side device 101.
A terminal 100, configured to determine an MDBV corresponding to a logical channel and a token bucket for MDBV control; and performing resource allocation on the logical channel according to the determined MDBV and the token bucket for MDBV control.
The network side device 101 is mainly used for determining an MDBV corresponding to the resource allocation object and a token bucket for controlling the MDBV; performing resource allocation on the resource allocation object according to the determined MDBV and the token bucket for MDBV control; if uplink resource allocation is carried out, the resource allocation object is a logical channel group; and if the downlink resource allocation is carried out, the resource allocation object is a logical channel.
In the embodiment of the invention, the terminal and the network side equipment firstly determine the MDBV corresponding to the object and the token bucket used for controlling the MDBV, and carry out resource allocation on the object according to the determined MDBV and the token bucket used for controlling the MDBV. In the embodiment of the invention, the resources for data transmission are distributed according to the token bucket for MDBV control, so that the data volume sent by each QoS Flow is ensured not to exceed the MDBV limit, and the delay sensitive service is prevented from preempting the resources of other services when the system load is heavier.
The following describes a system for allocating resources in detail by taking downlink resources as an example.
Method one, carry on the resource allocation to the downlink resource
When the downlink resources are allocated, after the network side equipment determines that the establishment of the logical channel is completed and/or the network side equipment determines that the resource allocation needs to be performed based on the MDBV according to the system load, the network side equipment determines the MDBV corresponding to the logical channel and a token bucket for controlling the MDBV.
When the network side device determines the MDBV corresponding to the logical channel in the MAC layer, because several different situations exist in the mapping relationship between the Flow and the logical channel, the MDBV corresponding to the logical channel determined by the network side device may also be different, and the following description is made for different situations:
in the first case: if Flow and logical channels use 1:1, the network side device takes the MDBV corresponding to the Flow as the MDBV corresponding to the logic channel;
for example, Flow and logical channel use 1: and 1, mapping according to the ratio, wherein only 1 logic channel is mapped with only 1 Flow, and the MDBV of the Flow is taken as the MDBV corresponding to the logic channel.
In the second case: if the Flow and the logic channel adopt M:1 ratio mapping, the network side equipment obtains the sum of MDBV corresponding to the Flow mapped to the logic channel according to the mapping relation of the Flow and the logic channel and takes the sum as the MDBV corresponding to the logic channel, wherein M is a positive integer.
For example, the Flow and the logical channel adopt 6:1 ratio mapping, at this time, 6 flows are mapped to the same logical channel, the network side device adds the MDBV corresponding to the 6 flows, and the sum of the MDBV is used as the MDBV corresponding to the logical channel.
In the third case: and if the Flow and the logic channel adopt M:1 ratio mapping, the network side equipment takes the sum of MDBVs corresponding to the flows actually mapped to the logic channel in the mapping relation of the Flow and the logic channel as the MDBVs corresponding to the logic channel, wherein M is a positive integer.
For example, the flows and the logical channels adopt 6:1 ratio mapping, and M flows should be mapped to the same logical channel at this time according to an actual mapping rule, but only 3 flows are actually mapped to the same logical channel, and at this time, the network side device adds up the MDBVs corresponding to the 3 flows, and takes the sum of the MDBVs as the MDBV corresponding to the logical channel.
Since the network side device determines the MDBV corresponding to the logical channel at the root of the MAC layer, 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 network side device may determine the MDBV corresponding to the logical channel at the MAC layer only by notifying the MAC layer in advance, and specifically, may notify the MAC layer in the following manner.
(1) The network side equipment informs the mapping relation between the Flow and the logical channel of the MAC layer through the SDAP or RRC layer;
and when the network side equipment informs the mapping relation between the Flow and the logical channel of the MAC layer, the Flow is expressed by QFI, and the MAC layer determines the MDBV corresponding to each Flow according to the corresponding relation between the QFI and the 5QI identification stored in the MAC layer and the corresponding relation between the 5QI and the MDBV. And finally, adding the MDBVs corresponding to the flows mapped to the logic channels to obtain the MDBV corresponding to the logic channels.
(2) And the network side equipment informs the mapping relation between the Flow and the logical channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer.
After the mapping relation between the Flow and the logic channel and the MDBV corresponding to the QFI are known by the MAC layer, the Flow mapped to the logic channel can be known by the network side equipment according to the mapping relation between the Flow and the logic channel, the MDBV corresponding to each Flow is found according to the MDBV corresponding to the QFI, and finally the MDBVs corresponding to the flows mapped to the logic channel are added to obtain the MDBV corresponding to the logic channel.
(3) And the network side equipment informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer.
In this case, the network side device may directly determine the MDBV corresponding to the logical channel according to the notification of the SDAP or the RRC layer.
(4) And the network side equipment informs the MAC layer of the Flow actually mapped to the logical channel through the SDAP layer.
The network side device informs the MAC layer of the Flow actually mapped to the logical channel through the SDAP, the Flow is represented by QFI, and the MAC layer determines the MDBV corresponding to each Flow according to the corresponding relation of the QFI and the 5QI identification stored in the MAC layer and the corresponding relation of the 5QI and the MDBV. And finally, adding the MDBVs corresponding to the flows mapped to the logic channels to obtain the MDBV corresponding to the logic channels.
(5) And the network side equipment informs the MAC layer of the MDBV corresponding to the Flow and the QFI actually mapped to the logic channel through the SDAP layer.
And after the MAC layer knows the Flow actually mapped to the logic channel and the MDBV corresponding to the QFI, the network side equipment finds out the MDBV corresponding to each Flow actually mapped to the logic channel according to the MDBV corresponding to the QFI, and finally adds up the MDBVs corresponding to the flows actually mapped to the logic channel to obtain the MDBV corresponding to the logic channel.
(6) And the network side equipment informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
The network side equipment can directly determine the MDBV corresponding to the logic channel according to the notification of the SDAP layer.
Here, it should be noted that: one of the above modes may be adopted when the MAC layer is notified, or a plurality of modes may be used simultaneously.
Correspondingly, after the network side equipment determines that the MDBV corresponding to the logical channel is used, the network side equipment takes the MDBV corresponding to the logical channel as the size of a token bucket used for MDBV control by the logical channel, and determines the number M of tokens which are actually used in a time period (N-PDB, N) of the token bucket used for MDBV control by the logical channel, wherein N is a scheduling time, and PDB is a data packet delay budget corresponding to the logical channel.
In a specific implementation, an optional implementation is: and the network side equipment takes the difference between the MDBV corresponding to the logical channel and the number of the tokens which are actually used in the token bucket for MDBV control of the current logical channel as the number of the available tokens in the token bucket for MDBV control of the logical channel.
Correspondingly, after the number of the available tokens in the token bucket used for MDBV control as the logical channel is obtained, the network side equipment allocates resources for the logical channel according to the minimum value between the number of the available tokens in the token bucket used for MDBV control by the logical channel and the data amount of the actual resources to be allocated by the current logical channel.
The PDB determination mode is as follows:
the terminal determines 5 QIs corresponding to all flows of all logical channels capable of being mapped or 5 QIs corresponding to all flows actually mapped to the logical channels according to the mapping relation of the logical channels; and finally, determining the maximum PDB from the 5QI corresponding to the Flow as the PDB corresponding to the logic channel.
For example, the network side device first determines that the logical channels that can be mapped to the logical channel group or actually mapped to the logical channel group are logical channels 1, 2, 3, and 4, then the network side device determines 5 QIs corresponding to flows corresponding to the logical channels 1, 2, 3, and 4, and then determines the largest PDB as the PDB corresponding to the logical channel group according to a standardized 5QI table of 3GPP from the determined 5 QIs corresponding to flows.
And after the network side equipment determines the MDBV corresponding to the logical channel and the token bucket used for controlling the MDBV, performing resource allocation on the logical channel according to the determined MDBV and the token bucket used for controlling the MDBV.
For example, if the number of available tokens in the token bucket used by the logical channel for MDBV control is smaller than the data amount required by the logical channel, the network side device preferentially allocates resources for the data that meets the MDBV requirement corresponding to the logical channel, and if there are remaining resources, the network side device allocates resources for the data that does not meet the MDBV requirement corresponding to the logical channel group according to the data amount of the resources that can be allocated by the logical channel.
As shown in fig. 2, an embodiment of the present invention provides a flowchart of a complete method for resource allocation of downlink resources.
Step 200, the network side equipment determines that the establishment of the logical channel is completed and/or the network side equipment determines that resource allocation needs to be carried out based on MDBV according to the system load;
step 201, the network side device determines the MDBV corresponding to the logical channel through the MAC layer;
step 202, the network side device determines the number M of the tokens which are actually used in a token bucket for MDBV control in a time period (N-PDB, N);
step 203, the network side device takes the difference between the MDBV corresponding to the logical channel and the number M of the tokens which are actually used in the time period (N-PDB, N ]) in the token bucket for controlling the MDBV as the number of the available tokens in the token bucket for controlling the MDBV by the logical channel;
and step 204, the network side equipment allocates resources for the logical channels according to the minimum value between the number of available tokens in the token bucket for MDBV control of the logical channels and the data volume of the resources to be actually allocated by the current logical channels.
Second mode, resource allocation is carried out on uplink resources
When the uplink resources are allocated, the network side equipment needs to allocate the uplink resources for different terminals, and when the network side equipment determines that the establishment of the logical channel is completed and/or the network side equipment determines that the resource allocation needs to be performed based on the MDBV according to the system load, the MDBV corresponding to the logical channel group and the token bucket used for controlling the MDBV are determined.
The network side device may determine the MDBV corresponding to the logical channel group in the following centralized manner:
1. and the network side equipment determines the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel, and takes the sum of the MDBVs corresponding to the logic channels in the same logic channel group as the MDBV corresponding to the logic 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 at this time, the network side device takes the sum of the MDBV corresponding to the logical channels 1 and 2 as the MDBV corresponding to the logical channel group 1.
However, because there are several different situations in the mapping relationship between the Flow and the logical channel, the MDBV corresponding to the logical channel determined by the network side device will also be different, and the following description will be made for different situations:
in the first case: if Flow and logical channels use 1:1, the network side device takes the MDBV corresponding to the Flow as the MDBV corresponding to the logic channel;
for example, Flow and logical channel use 1: and 1, mapping according to the ratio, wherein only 1 logic channel is mapped with only 1 Flow, and the MDBV of the Flow is taken as the MDBV corresponding to the logic channel.
In the second case: if the Flow and the logic channel adopt M:1 ratio mapping, the network side equipment takes the sum of MDBVs corresponding to the Flow which can be mapped to the logic channel as the MDBVs corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
For example, the Flow and the logical channel adopt 6:1 ratio mapping, at this time, 6 flows are mapped to the same logical channel, the network side device adds the MDBV corresponding to the 6 flows, and the sum of the MDBV is used as the MDBV corresponding to the logical channel.
In the third case: if the Flow and the logic channel adopt M:1 ratio mapping, at this time, the network side device will take the sum of the MDBVs corresponding to the Flow actually mapped to the logic channel as the MDBVs corresponding to the logic channel according to the mapping relation of the Flow and the logic channel. Wherein M is a positive integer.
For example, the flows and the logical channels adopt 6:1 ratio mapping, and at this time, 6 flows should be mapped to the same logical channel according to an actual mapping rule, but only 3 flows are actually mapped to the same logical channel, and at this time, the network side device adds up the MDBVs corresponding to the 3 flows, and takes the sum of the MDBVs as the MDBV corresponding to the logical channel.
2. And the network side equipment receives the sum of the MDBVs corresponding to the logical channels reported by the terminal, and takes 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 may receive the sum of the MDBV corresponding to the logical channels 1, 2, and 3 reported by the end, where the logical channels 1, 2, and 3 are in the same logical channel group 1, and at this time, the network side device takes the sum of the MDBV corresponding to the reported logical channels 1, 2, and 3 as the MDBV corresponding to the logical channel group 1.
3. And the network side equipment receives the MDBV corresponding to the logical channel group reported by the terminal, and then takes 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 MDBV corresponding to the logical channels 1, 2, and 3 in the same logical channel group 1 to the network side device, and the network side device takes the reported sum of the MDBV corresponding to the same logical channel group 1 as the MDBV corresponding to the logical channel group 1.
Since the network side device determines the MDBV corresponding to the logical channel group in 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, and thus needs to notify the MAC layer in advance.
In addition, when the uplink resource allocation is performed, the MAC layer does not know the mapping relationship between the logical channel and the logical channel group, and therefore the RRC layer also needs to notify the mapping relationship between the logical channel and the logical channel group of the MAC layer, so that the network side device can determine the MDBV corresponding to the logical channel group in the MAC layer, and specifically, the MAC layer can be notified in the following manner.
(1) The network side equipment informs the mapping relation between the Flow and the logical channel of the MAC layer through the SDAP or RRC layer;
and when the network side equipment informs the mapping relation between the Flow and the logical channel of the MAC layer, the Flow is expressed by QFI, and the MAC layer determines the MDBV corresponding to each Flow according to the corresponding relation between the QFI and the 5QI identification stored in the MAC layer and the corresponding relation between the 5QI and the MDBV. And finally, adding the MDBVs corresponding to the flows mapped to the logic channels to obtain the MDBV corresponding to the logic channels.
And then the MAC layer 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 relation between the logical channels and the logical channel group.
(2) And the network side equipment informs the mapping relation between the Flow and the logical channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer.
After the mapping relation between the Flow and the logic channel and the MDBV corresponding to the QFI are known by the MAC layer, the Flow mapped to the logic channel can be known by the network side equipment according to the mapping relation between the Flow and the logic channel, the MDBV corresponding to each Flow is found according to the MDBV corresponding to the QFI, and finally the MDBVs corresponding to the flows mapped to the logic channel are added to obtain the MDBV corresponding to the logic channel.
And then the MAC layer 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 relation between the logical channels and the logical channel group.
(3) And the network side equipment informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer.
In this case, the network side device may directly determine the MDBV corresponding to the logical channel according to the notification of the SDAP or the RRC layer.
And then the MAC layer 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 relation between the logical channels and the logical channel group.
(4) And the network side equipment informs the MAC layer of the Flow actually mapped to the logical channel through the SDAP layer.
The terminal SDAP and the network side SDAP need information interaction, and the network equipment acquires the Flow information actually mapped to the logic channel by the network side equipment of the terminal side equipment through the SDAP layer.
And then the SDAP of the network side informs the MAC layer of the Flow actually mapped to the logical channel, the Flow is expressed by QFI, and the MAC layer determines the MDBV corresponding to each Flow according to the corresponding relation of the QFI and the 5QI identification stored by the MAC layer and the corresponding relation of the 5QI and the MDBV. And finally, adding the MDBVs corresponding to the flows mapped to the logic channels to obtain the MDBV corresponding to the logic channels.
(5) And the network side equipment informs the MAC layer of the MDBV corresponding to the Flow and the QFI actually mapped to the logic channel through the SDAP layer.
The terminal SDAP and the network side SDAP need information interaction, and the network equipment acquires the Flow information actually mapped to the logic channel by the network side equipment of the terminal side equipment through the SDAP layer.
Then the network side SDAP informs the MAC layer of the Flow actually mapped to the logic channel, after the Flow actually mapped to the logic channel and the MDBV corresponding to the QFI are known by the MAC layer, the network side equipment finds the MDBV corresponding to each Flow actually mapped to the logic channel according to the MDBV corresponding to the QFI, and finally adds the MDBVs corresponding to the flows actually mapped to the logic channel to obtain the MDBV corresponding to the logic channel.
(6) And the network side equipment informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
The terminal SDAP and the network side SDAP need information interaction, and the network equipment acquires the Flow information actually mapped to the logic channel by the network side equipment of the terminal side equipment through the SDAP layer.
And then the SDAP layer at the network side determines the MDBV corresponding to the logical channel according to the mapping relation 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 notification of the SDAP layer.
Here, it should be noted that: the above manner of notifying the MAC layer may be one of the manners, or may be a plurality of manners 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 size of the token bucket used for MDBV control by the logical channel group, and determines the number M of the tokens actually used by the token bucket used for MDBV control in a time period (N-PDB, N), wherein N is a scheduling time, and PDB is a data packet delay budget corresponding to the logical channel.
PDB was determined as follows:
and the terminal determines all 5 QIs corresponding to all flows which can be mapped to the logic channel group or all 5 QIs corresponding to all flows which are actually mapped to the logic channel group according to the mapping relation between the flows and the logic channels, and finally determines the largest PDB as the PDB corresponding to the logic channel group according to the 5 QIs corresponding to the flows.
For example, the network side device first determines that the logical channels that can be mapped to the logical channel group or actually mapped to the logical channel group are logical channels 1, 2, 3, and 4, then the network side device determines 5 QIs corresponding to flows corresponding to the logical channels 1, 2, 3, and 4, and then determines the largest PDB as the PDB corresponding to the logical channel group from the determined 5 QIs corresponding to the flows.
And after the network side equipment determines the MDBV corresponding to the logical channel group and the token bucket for controlling the MDBV, performing resource allocation on the logical channel group according to the determined MDBV and the token bucket for controlling the MDBV.
In a specific implementation, an optional implementation is: and the network side equipment takes the difference between the MDBV corresponding to the logical channel group and the number of the tokens which are actually used in the token bucket for MDBV control as the number of the available tokens in the token bucket corresponding to the logical channel group.
For example, the MDBV corresponding to the logical channel group is 200 bits, the number of the tokens actually used in the token bucket for MDBV control is 100 bits, and at this time, the difference between the MDBV and the tokens is 100-100, and the number of the available tokens used in the token bucket for MDBV control by the difference (100 bits) is 100 bits.
After the number of available tokens in a token bucket used for MDBV control as a logical channel group is obtained, if the number of the available tokens of the logical channel group is less than the actual data volume to be transmitted of the logical channel group, the network side equipment preferentially allocates resources for the data meeting the MDBV requirement corresponding to the logical channel group, and if remaining resources exist, the network side equipment allocates resources according to the data which are actually to be transmitted of the logical channel group but do not meet the MDBV requirement corresponding to the logical channel group.
Correspondingly, after the network side device allocates resources for different terminals, the allocated resources are notified to the terminals, and the terminals need to perform resource allocation on the logical channels based on the resources allocated by the network side, so that after the terminals determine that the logical channels are established and/or receive the notification that the resources are required to be allocated based on the MDBV and sent by the network side device, the terminals determine the token bucket for controlling the MDBV and the MDBV corresponding to the logical channels.
When the terminal determines the MDBV corresponding to the logical channel in the MAC layer, the MDBV corresponding to the logical channel determined by the terminal may be different because several different situations may exist in the mapping relationship between the Flow and the logical channel, and the following description is made for different situations:
in the first case: if Flow and logical channels use 1:1, the terminal takes the MDBV corresponding to the Flow as the MDBV corresponding to the logic channel;
for example, the Flow and the logical channel adopt a 1:1 ratio mapping, and at this time, the terminal will use the MDBV of the Flow as the MDBV corresponding to the logical channel.
In the second case: if the Flow and the logic channel adopt M:1 ratio mapping, the terminal takes the sum of MDBVs corresponding to the Flow which can be mapped to the logic channel as the MDBVs corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
For example, the Flow and the logical channel adopt 6:1 ratio mapping, at this time, 6 flows are mapped to the same logical channel, the terminal adds the MDBV corresponding to the 6 flows, and the sum of the MDBV is used as the MDBV corresponding to the logical channel.
In the third case: and if the Flow and the logic channel adopt M:1 ratio mapping, the terminal takes the sum of the MDBVs corresponding to the Flow actually mapped to the logic channel as the MDBVs corresponding to the logic channel according to the mapping relation of the Flow and the logic channel, wherein M is a positive integer.
For example, the flows and the logical channels adopt 6:1 ratio mapping, and at this time, 6 flows should be mapped to the same logical channel according to an actual mapping rule, but actually, only 3 flows are mapped to the same logical channel, and at this time, the MDBV corresponding to the 3 flows are added, and the sum of the MDBV is taken as the MDBV corresponding to the logical channel.
Since the terminal determines the MDBV corresponding to the logical channel in the MAC layer, but the MAC layer does not know the MDBV corresponding to the logical channel and the mapping relationship between the Flow and the logical channel, an inter-layer interaction mechanism needs to be introduced to notify the MAC layer logic, and the terminal can determine the MDBV corresponding to the logical channel in the MAC layer, and specifically, the following manner can be adopted to notify the MAC layer.
(1) And the terminal informs the media access control MAC layer of the mapping relation between the Flow and the logical channel through a service data adaptation layer SDAP or a radio resource control RRC layer.
And the Flow is expressed by QFI when the SDAP or RRC of the terminal informs the mapping relation between the Flow and the logical channel of the MAC layer, and the MAC layer determines the MDBV corresponding to each Flow according to the corresponding relation between the QFI and the 5QI identification stored in the MAC layer and the corresponding relation between the 5QI and the MDBV. And finally, adding the MDBVs corresponding to the flows mapped to the logic channels to obtain the MDBV corresponding to the logic channels.
(2) And the terminal informs the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer.
After the mapping relation between the Flow and the logic channel and the MDBV corresponding to the QFI are known by the MAC layer, the Flow mapped to the logic channel can be known by the terminal according to the mapping relation between the Flow and the logic channel, the MDBV corresponding to each Flow is found according to the MDBV corresponding to the QFI, and finally the MDBVs corresponding to the flows mapped to the logic channel are added to obtain the MDBV corresponding to the logic channel.
(3) And the terminal informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP or the RRC layer.
The MAC can obtain the MDBV corresponding to the logical channel directly according to the notification. The MDBV is a sum of MDBV corresponding to flows that can be mapped to the logical channel.
(4) And the terminal informs the MAC layer of the Flow actually mapped to the logical channel through the SDAP layer.
And after the MAC layer knows the Flow actually mapped to the logic channel and the MDBV corresponding to the QFI, finding out the MDBV corresponding to each Flow actually mapped to the logic channel according to the MDBV corresponding to the QFI, and finally adding the MDBVs corresponding to the flows actually mapped to the logic channel to obtain the MDBV corresponding to the logic channel.
(5) And the terminal informs the MAC layer of the MDBV corresponding to the Flow and QFI actually mapped to the logic channel through the SDAP layer.
And after the MAC layer knows the Flow actually mapped to the logic channel and the MDBV corresponding to the QFI, finding out the MDBV corresponding to each Flow actually mapped to the logic channel according to the MDBV corresponding to the QFI, and finally adding the MDBVs corresponding to the flows actually mapped to the logic channel to obtain the MDBV corresponding to the logic channel.
(6) And the terminal informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
The MAC layer can obtain the MDBV corresponding to the logical channel directly according to the notification. The MDBV is a sum of MDBV corresponding to flows actually mapped to the logical channel.
Here, it should be noted that: the above two manners of notifying the MAC layer may be used either alone or in combination.
Correspondingly, after the terminal determines the MDBV corresponding to the logical channel, the terminal takes the MDBV corresponding to the logical channel group as the size of the token bucket used for MDBV control by the logical channel group, and determines the number of the tokens which are actually used by the token bucket used for MDBV control in a time period (N-PDB, N), wherein N is the scheduling time, and PDB is the data packet delay budget corresponding to the logical channel.
After the terminal determines the MDBV and the token bucket for MDBV control corresponding to the logical channel group, the terminal performs resource allocation for the logical channel group according to the determined MDBV and the token bucket for MDBV control, and an optional implementation manner is as follows:
step 1: the terminal firstly sorts the logic channels with available PBR tokens and data transmission requirements according to the descending order of the priority of the logic channels, then the terminal carries out first round of resource allocation on each logic channel based on the PBR in sequence, meanwhile, the number of tokens in a PBR token bucket corresponding to each logic channel is updated, and after the PBR-based resource allocation is completed on the logic channel with MDBV requirements, the number of available tokens in the MDBV token bucket corresponding to the logic channel is updated.
The number of the available tokens in the token bucket corresponding to the logical channel is the difference between the MDBV and the number of the tokens actually used by the logical channel in the token bucket corresponding to the current moment;
for example, the MDBV corresponding to the logical channel group is 200 bits, the number of tokens that have been actually used in the token bucket for MDBV control is 100 bits, and at this time, the difference between the MDBV and the token bucket is 200 bits and 100 bits, so that the number of tokens that can be used in the token bucket corresponding to the logical channel group is 100 bits.
Step 2: after the terminal determines that the remaining allocable resources exist, performing a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities, specifically:
for the logic channel with the MDBV requirement, in the second round of resource allocation process, the logic channel allows the data amount of the allocated resources to measure the logic channel for the smaller value of the number of the usable tokens in the token bucket controlled by the MDBV and the data amount of the resources to be allocated currently by the logic channel, and the resources are allocated to the logic channel;
and if the logical channel needing to be allocated currently is the logical channel without the MDBV requirement, the terminal allocates the resources to the logical channel according to the data volume of the resources to be allocated currently of the logical channel.
For example, the terminal determines a logical channel having an MDBV requirement, and at this time, the number of available tokens in the current token bucket corresponding to the logical channel is 40 bits, the data volume of the resource that can be allocated in the current token bucket of the logical channel is 60 bits, and at this time, the terminal takes the smaller value (40 bits) between the two to allocate the resource to the logical channel.
If the logical channel which the terminal needs to allocate currently is the logical channel without the MDBV requirement, the terminal has two modes to allocate the resource.
One way is as follows: the terminal allocates resources to the logical channels according to the data volume of the resources to be allocated currently of the logical channels:
for example, the data amount of the current resource to be allocated of the logical channel is 600 bits, and the terminal performs resource allocation according to the 600 bits at this time.
The other mode is as follows: and if the logical channel needing to be allocated is the logical channel without the MDBV requirement and containing the GBR service, the terminal allocates the resources to the logical channel according to the data volume of the resources to be allocated currently by the logical channel.
For example, the data size of the current resource to be allocated of the logical channel is 600 bits, and the current logical channel to be allocated is a logical channel including GBR traffic, and at this time, the terminal performs resource allocation only on the logical channel according to the 600 bits.
And step 3: after the second round of allocation, if the terminal determines that the remaining resources exist, resource allocation is performed on the remaining data to be transmitted according to the descending order of priority of all the logical channels with the data transmission requirements until the resources are exhausted or the resources are allocated to the data to be transmitted of all the logical channels.
And after the allocation is finished, the terminal judges whether the residual resources exist or not, and if the residual resources exist, the terminal performs resource allocation on each logic channel according to the residual resources and the priority sequence of the logic channel.
The PDB determination mode is as follows:
and the terminal determines 5 QIs corresponding to all flows which can be mapped to the logic channel group or 5 QIs corresponding to all flows which are actually mapped to the logic channel group according to the mapping relation between the flows and the logic channels, and finally determines the largest PDB as the PDB corresponding to the logic channel group according to the 5 QIs corresponding to the flows.
For example, the network side device first determines that a logical channel that can be mapped or a logical channel that is actually mapped is logical channels 1, 2, 3, and 4, then determines a 5QI corresponding to a Flow corresponding to the logical channels 1, 2, 3, and 4 from a field, and then determines the largest PDB as the PDB corresponding to the logical channel from the determined 5QI corresponding to the Flow.
As shown in fig. 3, an embodiment of the present invention provides a flowchart of a complete method for allocating uplink resources at a terminal side.
Step 300, the terminal needs to determine that the establishment of the logical channel is completed and/or receives a notification that the resource allocation needs to be performed based on MDBV and sent by the network side equipment;
step 301, the terminal determines the MDBV corresponding to the logic channel through the MAC layer;
step 302, the terminal network side device determines the number of tokens which are actually used in a token bucket for MDBV control in a time period (N-PDB, N);
step 303, the terminal sorts the logical channels with available PBR tokens and data transmission requirements according to the descending order of the priority of the logical channels;
step 304, the terminal sequentially performs a first round of resource allocation on each logical channel based on the PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logical channel group, and updates the number of available tokens in the token bucket for MDBV control corresponding to each logical channel group;
305, after the terminal completes resource allocation based on PBR for the logic channel with the MDBV requirement, updating the number of available tokens in a token bucket used for MDBV control by the logic channel;
step 306, after the terminal determines that there are remaining allocable resources, it is determined whether the current logical channel to be allocated has a logical channel required by MDBV, if yes, step 307 is executed; otherwise, go to step 308;
307, the terminal takes the smaller value of the number of available tokens in a token bucket used for MDBV control by the logical channel and the data size of the current resource to be allocated by the logical channel, and allocates the resource to the logical channel;
308, the terminal allocates resources to the logical channel according to the data volume of the current resources to be allocated to the logical channel, or the logical channel which is required to be allocated before is a logical channel which has no MDBV requirement and contains GBR service, and allocates resources to the logical channel according to the data volume of the current resources to be 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 according to the descending order of priority of all the logical channels having the data transmission requirement.
As shown in fig. 4, an embodiment of the present invention provides a flowchart of a complete method for resource allocation of uplink resources to a network device.
Step 400, the network side device determines that the establishment of the logical channel 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, and notifies the terminal that the resource allocation needs to be performed based on the MDBV according to the system load;
step 401, the network side device determines the MDBV corresponding to the logical channel group through the MAC layer;
step 402, the network side device determines the number of tokens which are actually used in a token bucket for MDBV control in a time period (N-PDB, N) of a logical channel;
step 403, the network side device takes the difference between the MDBV corresponding to the logical channel group and the number M of the tokens that have been actually used in the time period (N-PDB, N ") in the token bucket for MDBV control as the number of available tokens in the token bucket for MDBV control of the logical channel group;
step 404, the network side device preferentially allocates resources for the data meeting the MDBV requirement corresponding to the logical channel group;
step 405, the network side device judges that the residual resources exist, if yes, step 406 is executed, otherwise, the resource allocation is ended;
step 406, the network side device allocates resources according to the data to be actually transmitted in the logical channel group but not meeting the MDBV requirement corresponding to the logical channel group;
step 407, the network side device ends the resource allocation.
As shown in fig. 5, an embodiment of the present invention provides a terminal for 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:
determining an MDBV corresponding to the logic channel and a token bucket for controlling the MDBV; and performing resource allocation on the logical channel according to the determined MDBV and the token bucket for MDBV control.
Optionally, the processor 500 is further configured to:
before determining the MDBV corresponding to the logical channel and a token bucket for MDBV control, determining that the establishment of the logical channel is completed; and/or receiving a notification sent by the network side equipment and needing to allocate resources based on the MDBV.
Optionally, the processor 500 is specifically configured to:
and determining the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel.
Optionally, the processor is specifically configured to:
if Flow and logical channels use 1:1 mapping, wherein the MDBV corresponding to the Flow is used as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, according to the mapping relation of the Flow and the logic channel, taking the sum of MDBV corresponding to the Flow which can be mapped to the logic channel as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, taking the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
Optionally, the processor 500 is specifically configured to:
and determining the MDBV corresponding to the logical channel at the MAC layer.
Optionally, the processor 500 is further configured to:
before determining the MDBV corresponding to the logical channel through the MAC layer, informing the mapping relation between the Flow and the logical channel through the SDAP or RRC layer; or
Informing the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
Informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer; or
Notifying the MAC layer of the Flow actually mapped to the logical channel through the SDAP layer; or
Informing the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
Optionally, the size of the token bucket for MDBV control is an MDBV corresponding to a logical channel.
Optionally, the processor 500 is further configured to:
firstly, determining the number M of tokens which are actually used in a token bucket of a logical channel for MDBV control in a time period (N-PDB, N), and taking 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, wherein N is a scheduling time, and PDB is a data packet delay budget corresponding to the logical channel.
Optionally, the processor is specifically configured to: determining the PDB corresponding to the logic channel by the following modes:
determining 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the mapping relation between the flows and the logic channel; and determining the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
Optionally, the processor 500 is specifically configured to:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens in a token bucket for MDBV control of the logic channel with MDBV requirements after completing the PBR-based resource allocation;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount to be transmitted currently by the logic channel, and allocating the resources of the logic channel; and if the logic channel needing to be allocated currently is the logic channel without the MDBV requirement, the terminal allocates resources to the logic channel according to the data volume to be transmitted currently of the logic channel.
Optionally, the processor 500 is further configured to:
after performing the second round of resource allocation on all the logic channels with the data transmission requirements according to the descending order of the priority of the logic channels, if the terminal determines that the remaining resources exist, performing resource allocation on the remaining data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the data to be transmitted of all the logic channels are allocated with the resources.
Optionally, the processor 500 is further configured to:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens used for MDBV control of the logic channel with MDBV requirements after completing PBR-based resource allocation;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount of the resources to be allocated currently by the logic channel, and allocating the resources to the logic channel; if the current logical channel needing to be allocated is the logical channel without MDBV requirement and containing GBR service, the terminal allocates resources to the logical channel;
optionally, the processor 500 is further configured to:
after performing the second round of resource allocation on all the logic channels with the data transmission requirements according to the descending order of the priority of the logic channels, if the terminal determines that the remaining resources exist, performing resource allocation on the remaining data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the data to be transmitted of all the logic channels are allocated with the resources.
Optionally, the number of tokens that can be used in the token bucket for MDBV control corresponding to the logical channel is a difference between the MDBV corresponding to the logical channel and the number of tokens that have been actually used in the token bucket for MDBV control corresponding to the logical channel.
Optionally, the processor 500 is specifically configured to:
determining the number M of tokens which are actually used in a token bucket for MDBV control by a logical channel within a time period (N-PDB, N), and taking the difference value between the size of the token bucket and the M as the number of available tokens in the token bucket corresponding to the object;
and the PDB is a data packet delay budget corresponding to the logic channel.
The processor 500 is responsible for managing the bus architecture and general processing, and the memory 501 may store data used by the processor 500 in performing operations. The transceiver 502 is used to receive and transmit data under the control of the processor 500.
The bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 500 and various circuits of memory represented by memory 501 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 501 may store data used by the processor 500 in performing operations.
The processes disclosed in the embodiments of the present invention may be applied to the processor 500, or implemented by the processor 500. In implementation, the steps of the signal processing flow may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 500. The processor 500 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof that may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 51, and the processor 500 reads the information in the memory 501, and completes the steps of the signal processing flow in combination with the hardware thereof.
As shown in fig. 6, an embodiment of the present invention provides a network side device for 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:
determining an MDBV corresponding to the resource allocation object and a token bucket for controlling the MDBV; performing resource allocation on the resource allocation object according to the determined MDBV and the token bucket for MDBV control; if uplink resource allocation is carried out, the resource allocation object is a logical channel group; and if the downlink resource allocation is carried out, the resource allocation object is a logical channel.
Optionally, the processor 600 is further configured to:
before determining the MDBV corresponding to the resource allocation object and a token bucket for MDBV control, determining that the establishment of a logical channel is completed; and/or determining a need for resource allocation based on MDBV based on system load.
Optionally, the processor 600 is further configured to:
and if the uplink resource allocation is carried out, after the fact that the resource allocation needs to be carried out based on the MDBV is determined according to the system load, the terminal is informed that the resource allocation needs to be carried out based on the MDBV.
Optionally, the processor 600 is specifically configured to:
if the downlink resource allocation is carried out, determining the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel; or
If uplink resource allocation is carried out, determining the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel, and taking the sum of the MDBVs corresponding to the logic channels in the same logic channel group as the MDBV corresponding to the logic channel group; or
If uplink resource allocation is carried out, taking the sum of MDBVs corresponding to the logical channels reported by the terminal as the MDBV corresponding to the logical channel group; or
And if the uplink resource allocation is carried out, receiving the MDBV corresponding to the logical channel group reported by the terminal.
Optionally, the processor 600 is specifically configured to:
if Flow and logical channels use 1:1 mapping, wherein the MDBV corresponding to the Flow is used as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, according to the mapping relation of the Flow and the logic channel, taking the sum of MDBV corresponding to the Flow which can be mapped to the logic channel as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, taking the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
Optionally, the processor 600 is specifically configured to:
and determining the MDBV corresponding to the resource allocation object in the MAC layer.
Optionally, the processor 600 is further configured to:
before the MAC layer determines the MDBV corresponding to the resource allocation object, informing the mapping relation between the Flow and the logic channel of the MAC layer through the SDAP or RRC layer; or
Informing the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
Informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer; or
Notifying the MAC layer of the Flow actually mapped to the logical channel through the SDAP layer; or
Informing the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
Optionally, the processor 600 is further configured to:
and if the resource allocation pair is a logical channel group, informing the mapping relation between the logical channel and the logical channel group by the RRC layer.
Optionally, the processor 600 is further configured to:
if the downlink resource allocation is carried out, determining the number of available tokens in the token bucket corresponding to the logic channel according to the size of the token bucket used for MDBV control by the logic channel and the number M of tokens in the token bucket already used by the logic channel in a time period (N-PDB, N), or
And if uplink resource allocation is carried out, determining the number of available tokens in the token bucket corresponding to the logical channel group according to the size of the token bucket used for MDBV control by the logical channel group and the number M of tokens in the token bucket already used by the logical channel group in a time period (N-PDB, N), wherein N is the scheduling time, and PDB is the data packet delay budget corresponding to the logical channel.
Optionally, the processor 600 is specifically configured to: determining the PDB corresponding to the logical channel group by the following method:
determining 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the mapping relation between the flows and the logic channel; and determining the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
Optionally, the processor 600 is specifically configured to:
if downlink resource allocation is carried out, taking the difference between the MDBV corresponding to the logic channel and the number of tokens which are actually used in the token bucket for MDBV control as the data volume of resources which can be allocated by the logic channel; and performing resource allocation on the logic channel according to the minimum value between the number of available tokens in a token bucket used for MDBV control by the logic channel and the actual data volume to be transmitted by the current logic channel.
Optionally, the processor 600 is specifically configured to:
if uplink resource allocation is carried out, taking the difference value of the number of the MDBV corresponding to the logical channel group and the number of the tokens which are actually used in the token bucket for MDBV control corresponding to the logical channel group as the number of the available tokens in the token bucket corresponding to the logical channel group; and performing resource allocation on the logical channel group according to the minimum value between the number of the 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.
The processor 600 is responsible for managing the bus architecture and general processing, and the memory 601 may store data used by the processor 600 in performing operations. The transceiver 602 is used to receive and transmit data under the control of the processor 600.
The bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 600 and various circuits of memory represented by memory 601 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The processor 600 is responsible for managing the bus architecture and general processing, and the memory 601 may store data used by the processor 600 in performing operations.
The processes disclosed in the embodiments of the present invention may be applied to the processor 600, or implemented by the processor 600. In implementation, the steps of the signal processing flow may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 600. The processor 600 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof that may implement or perform the methods, steps or logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. 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 combination with the hardware thereof.
As shown in fig. 7, an embodiment of the present invention provides a terminal for resource allocation, where the terminal includes:
a first determining module 700, configured to determine an MDBV corresponding to a logical channel and a token bucket for MDBV control;
a first allocating module 701, 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:
before determining the MDBV corresponding to the logical channel and a token bucket for MDBV control, determining that the establishment of the logical channel is completed; and/or receiving a notification sent by the network side equipment and needing to allocate resources based on the MDBV.
Optionally, the first determining module 700 is further configured to:
and determining the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel.
Optionally, the first determining module 700 is specifically configured to:
if Flow and logical channels use 1:1 mapping, wherein the MDBV corresponding to the Flow is used as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, according to the mapping relation of the Flow and the logic channel, taking the sum of MDBV corresponding to the Flow which can be mapped to the logic channel as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, taking the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
Optionally, the first determining module 700 is specifically configured to:
and determining the MDBV corresponding to the logical channel at the MAC layer.
Optionally, the first determining module 700 is further configured to:
before determining the MDBV corresponding to the logical channel through the MAC layer, informing the mapping relation between the Flow and the logical channel through the SDAP or RRC layer; or
Informing the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
Informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer; or
Notifying the MAC layer of the Flow actually mapped to the logical channel through the SDAP layer; or
Informing the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
Optionally, the size of the token bucket for MDBV control is an MDBV corresponding to a logical channel.
Optionally, the first determining module 700 is specifically configured to:
determining the number M of tokens which are actually used in a token bucket of a logical channel for MDBV control in a time period (N-PDB, N), and taking 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, wherein N is a scheduling time, and PDB is a data packet delay budget corresponding to the logical channel.
Optionally, the first determining module 700 is specifically configured to: determining the PDB corresponding to the logic channel by the following modes:
determining 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the mapping relation between the flows and the logic channel; and determining the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
Optionally, the first allocating module 701 is specifically configured to:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens in a token bucket for MDBV control of the logic channel with MDBV requirements after completing the PBR-based resource allocation;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount to be transmitted currently by the logic channel, and allocating the resources of the logic channel; and if the logic channel needing to be allocated currently is the logic channel without the MDBV requirement, the terminal allocates resources to the logic channel according to the data volume to be transmitted currently of the logic channel.
Optionally, the first distribution module 701 is further configured to:
after performing the second round of resource allocation on all the logic channels with the data transmission requirements according to the descending order of the priority of the logic channels, if the terminal determines that the remaining resources exist, performing resource allocation on the remaining data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the data to be transmitted of all the logic channels are allocated with the resources.
Optionally, the first distribution module 701 is further configured to:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens in a token bucket for MDBV control of the logic channel with MDBV requirements after completing the PBR-based resource allocation;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount of the resources to be allocated currently by the logic channel, and allocating the resources to the logic channel; if the current logical channel needing to be allocated is the logical channel without MDBV requirement and containing GBR service, the terminal allocates resources to the logical channel;
optionally, the first distribution module 701 is further configured to:
and after performing second round resource allocation on all the logic channels with the data transmission requirements according to the descending order of the priorities of the logic channels, if the terminal determines that the remaining resources exist, performing resource allocation on the remaining data to be transmitted according to the descending order of the priorities of the logic channels with the data transmission requirements until the resources are exhausted or the data to be transmitted of all the logic channels are allocated with the resources.
Optionally, the number of tokens that can be used in the token bucket for MDBV control corresponding to the logical channel is a difference between the MDBV corresponding to the logical channel and the number of tokens that have been actually used in the token bucket for MDBV control corresponding to the logical channel.
Optionally, the first determining module 700 is further configured to:
determining the number M of tokens which are actually used in a token bucket of a logical channel for MDBV control in a time period (N-PDB, N), and taking the difference value between the size of the token bucket and the M as the number of available tokens in the token bucket corresponding to the object, wherein N is the scheduling time, and PDB is the data packet delay budget corresponding to the logical channel.
As shown in fig. 8, an embodiment of the present invention provides a network side device for resource allocation, where 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 MDBV control;
a second allocating module 801, configured to perform resource allocation on the resource allocation object according to the determined MDBV and the token bucket for MDBV control;
if uplink resource allocation is carried out, the resource allocation object is a logical channel group; and if the downlink resource allocation is carried out, the resource allocation object is a logical channel.
Optionally, the second determining module 800 is further configured to:
before determining the MDBV corresponding to the resource allocation object and a token bucket for MDBV control, determining that the establishment of a logical channel is completed; and/or determining a need for resource allocation based on MDBV based on system load.
Optionally, the second determining module 800 is further configured to:
and if the uplink resource allocation is carried out, after the fact that the resource allocation needs to be carried out based on the MDBV is determined according to the system load, the terminal is informed that the resource allocation needs to be carried out based on the MDBV.
Optionally, the second determining module 800 is specifically configured to:
if the downlink resource allocation is carried out, determining the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel; or
If uplink resource allocation is carried out, determining the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel, and taking the sum of the MDBVs corresponding to the logic channels in the same logic channel group as the MDBV corresponding to the logic channel group; or
If uplink resource allocation is carried out, taking the sum of MDBVs corresponding to the logical channels reported by the terminal as the MDBV corresponding to the logical channel group; or
And if the uplink resource allocation is carried out, receiving the MDBV corresponding to the logical channel group reported by the terminal.
Optionally, the second determining module 800 is further configured to:
if Flow and logical channels use 1:1 mapping, wherein the MDBV corresponding to the Flow is used as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, according to the mapping relation of the Flow and the logic channel, taking the sum of MDBV corresponding to the Flow which can be mapped to the logic channel as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, taking the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
Optionally, the second determining module 800 is specifically configured to:
and determining the MDBV corresponding to the resource allocation object in the MAC layer.
Optionally, the second determining module 800 is further configured to:
before the MAC layer determines the MDBV corresponding to the resource allocation object, informing the mapping relation between the Flow and the logic channel of the MAC layer through the SDAP or RRC layer; or
Informing the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
Informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer; or
Notifying the MAC layer of the Flow actually mapped to the logical channel through the SDAP layer; or
Informing the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
Optionally, the second determining module 800 is further configured to:
and if the resource allocation pair is a logical channel group, informing the mapping relation between the logical channel and the logical channel group by the RRC layer.
Optionally, the second determining module 800 is further configured to:
if the downlink resource allocation is carried out, determining the number of available tokens in the token bucket corresponding to the logic channel according to the size of the token bucket used for MDBV control by the logic channel and the number M of tokens in the token bucket already used by the logic channel in a time period (N-PDB, N), or
And if uplink resource allocation is carried out, determining the number of available tokens in the token bucket corresponding to the logical channel group according to the size of the token bucket used for MDBV control by the logical channel group and the number M of tokens in the token bucket already used by the logical channel group in a time period (N-PDB, N), wherein N is the scheduling time, and PDB is the data packet delay budget corresponding to the logical channel.
Optionally, the second determining module 800 is specifically configured to:
determining the PDB corresponding to the logic channel by the following modes:
determining 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the mapping relation between the flows and the logic channel; and determining the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
Optionally, the second determining module 800 is specifically configured to:
if downlink resource allocation is carried out, taking the difference between the MDBV corresponding to the logic channel and the number of tokens which are actually used in the token bucket for MDBV control as the data volume of resources which can be allocated by the logic channel; and performing resource allocation on the logical channel according to the minimum value between the number of the available tokens in the token bucket used for MDBV control by the logical channel and the data amount of the actual resources to be allocated by the current logical channel.
Optionally, the second determining module 800 is specifically configured to:
if uplink resource allocation is carried out, taking the difference value of the number of the MDBV corresponding to the logical channel group and the number of the tokens which are actually used in the token bucket for MDBV control corresponding to the logical channel group as the number of the available tokens in the token bucket corresponding to the logical channel group; and performing resource allocation on the logical channel group according to the minimum value between the number of the available tokens in the token bucket corresponding to the logical channel group and the data amount of the actual resource to be allocated of the current logical channel.
Fig. 9 shows that, an embodiment of the present invention provides a method for resource allocation, where the method includes:
step 900, the terminal determines the MDBV corresponding to the logic channel and a token bucket for MDBV control;
and 901, the terminal allocates resources to the logic channel according to the determined MDBV and the token bucket for MDBV control.
Optionally, before the terminal determines the MDBV corresponding to the logical channel and the token bucket for MDBV control, it determines that the establishment of the logical channel is completed; and/or receiving a notification sent by the network side equipment and needing to allocate resources based on the MDBV.
Optionally, the terminal determines an MDBV corresponding to the logical channel according to a mapping relationship between the Flow and the logical channel.
Optionally, if the Flow and the logical channel use 1:1, mapping, wherein the terminal takes the MDBV corresponding to the Flow as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the terminal takes the sum of MDBVs corresponding to the Flow which can be mapped to the logic channel as the MDBVs corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the terminal takes the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
Optionally, the terminal determines an MDBV corresponding to the logical channel in the MAC layer.
Optionally, the terminal notifies the mapping relationship between the Flow and the logical channel in the MAC layer through the SDAP or RRC layer; or
The terminal informs the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
The terminal informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer; or
The terminal informs the MAC layer of the Flow actually mapped to the logic channel through the SDAP layer; or
The terminal informs the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And after the terminal informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer, the MDBV corresponding to the object is determined through the MAC layer.
Optionally, the size of the token bucket for MDBV control is an MDBV corresponding to a logical channel.
Optionally, the terminal determines the number M of tokens that have been actually used in a time period (N-PDB, N) of a token bucket used for MDBV control by a logical channel, and uses the difference between the size of the token bucket and M as the number of available tokens in the token bucket corresponding to the logical channel;
and the PDB is a data packet delay budget corresponding to the logic channel.
Optionally, the terminal determines the PDB corresponding to the logical channel by the following method:
determining 5 QIs corresponding to all flows which can be mapped to the logical channels or 5 QIs corresponding to all flows which are actually mapped to the logical channels according to the mapping relation of the logical channels;
and determining the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
Optionally, the terminal performs resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens in an MDBV token bucket corresponding to the logic channel after completing PBR-based resource allocation on the logic channel;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount of the resources to be allocated currently by the logic channel, and allocating the resources to the logic channel; and if the logical channel needing to be allocated currently is the logical channel without the MDBV requirement, the terminal allocates the resources to the logical channel according to the data volume of the resources to be allocated currently of the logical channel.
Optionally, after performing the second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities, the terminal further includes:
and if the terminal determines that the residual resources exist, performing resource allocation on the residual data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the resources are allocated to the data to be transmitted of all the logic channels.
Optionally, the terminal performs resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens in a corresponding MDBV token bucket corresponding to the logic channel after completing the PBR-based resource allocation on the logic channel;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount of the resources to be allocated currently by the logic channel, and allocating the resources to the logic channel; if the current logical channel needing to be allocated is the logical channel without MDBV requirement and containing GBR service, the terminal allocates resources to the logical channel;
optionally, after performing the second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities, the terminal further includes:
and if the terminal determines that the residual resources exist, performing resource allocation on the residual data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the resources are allocated to the data to be transmitted of all the logic channels.
Optionally, the number of tokens that can be used in the token bucket for MDBV control corresponding to the logical channel is a difference between the MDBV corresponding to the logical channel and the number of tokens that have been actually used in the token bucket for MDBV control corresponding to the logical channel.
Optionally, the updating, by the terminal, the number of available tokens in the token bucket used for MDBV control by the logical channel includes:
the terminal determines the number M of tokens which are actually used in a token bucket for MDBV control by a logical channel within a time period (N-PDB, N), and takes 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, wherein N is the scheduling time, and PDB is the data packet delay budget corresponding to the logical channel.
As shown in fig. 10, an embodiment of the present invention provides a method for resource allocation, where the method includes:
step 1000, the network side equipment determines an MDBV corresponding to the resource allocation object and a token bucket for controlling the MDBV;
step 1001, the network side equipment performs resource allocation on the resource allocation object according to the determined MDBV and the token bucket for MDBV control;
if uplink resource allocation is carried out, the resource allocation object is a logical channel group; and if the downlink resource allocation is carried out, the resource allocation object is a logical channel.
Optionally, before determining a token bucket used by the logical channel for MDBV control and an MDBV corresponding to the object, the network side device determines that the establishment of the logical channel is completed; and/or determining a need for resource allocation based on MDBV based on system load.
Optionally, if uplink resource allocation is performed, after determining that resource allocation needs to be performed based on the MDBV according to the system load, the network side device notifies the terminal that resource allocation needs to be performed based on the MDBV.
Optionally, if downlink resource allocation is performed, the network side device determines an MDBV corresponding to the logical channel according to a mapping relationship between the Flow and the logical channel; or
If uplink resource allocation is carried out, the network side equipment determines the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel, and takes the sum of the MDBVs corresponding to the logic channels in the same logic channel group as the MDBV corresponding to the logic channel group; or
If uplink resource allocation is carried out, the network side equipment takes the sum of MDBVs corresponding to the logical channels reported by the terminal as the MDBV corresponding to the logical channel group; or
And if the uplink resource allocation is carried out, the network side equipment receives the MDBV corresponding to the logical channel group reported by the terminal.
Optionally, if the Flow and the logical channel use 1:1, the network side equipment takes the MDBV corresponding to the Flow as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the network side equipment takes the sum of MDBVs corresponding to the Flow which can be mapped to the logic channel as the MDBVs corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the network side equipment takes the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
Optionally, the network side device determines, in 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 MAC layer of a mapping relationship between Flow and a logical channel through the SDAP or RRC layer; or
The network side equipment informs the Flow of an MAC layer, the mapping relation of a logical channel and the MDBV corresponding to the QFI through an SDAP or RRC layer; or
The network side equipment informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer; or
The network side equipment informs the MAC layer of the Flow actually mapped to the logic channel through the SDAP layer; or
The network side equipment informs the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And the network side equipment informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
Optionally, if the resource allocation pair is a logical channel group, the method further includes:
and the network side equipment informs the mapping relation between the logical channels and the logical channel groups of the MAC layer through the RRC layer.
Optionally, if downlink resource allocation is performed, the network side device determines the number of available tokens in the token bucket corresponding to the logical channel 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 already used by the logical channel in the time period (N-PDB, N) ], or
If uplink resource allocation is carried out, the size of a token bucket used for MDBV control by the network side equipment logical channel group and the number M of tokens in the token bucket already used by the logical channel group in a time period (N-PDB, N) determine the number of available tokens in the token bucket corresponding to the logical channel group;
and the PDB is a data packet delay budget corresponding to the logic channel.
Optionally, the network side device determines the PDB corresponding to the logical channel by the following means:
the network side equipment determines 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the mapping relation between the flows and the logic channel;
and the network side equipment determines the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
Optionally, if downlink resource allocation is performed, the network side device uses a difference between the MDBV corresponding to the logical channel and the number of tokens that have been actually used in the token bucket for MDBV control as a data amount of resources that can be allocated by the logical channel;
and the network side equipment performs resource allocation on the logical channel according to the minimum value between the number of available tokens in a token bucket used for MDBV control by the logical channel and the data amount of the actual resource to be allocated by the current logical channel.
Optionally, if uplink resource allocation is performed, the network side device uses a difference between the MDBV corresponding to the logical channel group and the number of actually used tokens in the token bucket for MDBV control corresponding to the logical channel group as the number of available tokens in the token bucket corresponding to the logical channel group;
and the network side equipment performs resource allocation on the logical channel group according to the minimum value between the number of the available tokens in the token bucket corresponding to the logical channel group and the data amount of the actual resource to be allocated of the current logical channel.
The present application is described above with reference to block diagrams and/or flowchart illustrations of methods, apparatus (systems) and/or computer program products according to embodiments of the application. It will be understood that one block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, and/or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks.
Accordingly, the subject application may also be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). Furthermore, the present application may 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 the medium for use by or in connection with an instruction execution system. In the context of this application, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (56)

1. A method for resource allocation, the method comprising:
the terminal determines the maximum data burst capacity MDBV corresponding to the logic channel and a token bucket for controlling the MDBV;
and the terminal performs resource allocation on the logic channel according to the determined MDBV and the token bucket for MDBV control.
2. The method of claim 1, wherein the terminal, prior to determining the MDBV for the logical channel and the token bucket for MDBV control, further comprises:
the terminal determines that the establishment of the logical channel is completed; and/or
And the terminal receives a notification which is sent by the network side equipment and needs to allocate resources based on the MDBV.
3. The method of claim 1, wherein the determining, by the terminal, the MDBV corresponding to the logical channel comprises:
and the terminal determines the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel.
4. The method of claim 3, wherein the determining, by the terminal, the MDBV corresponding to the logical channel according to a mapping relationship between the Flow and the logical channel comprises:
if Flow and logical channels use 1:1, mapping, wherein the terminal takes the MDBV corresponding to the Flow as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the terminal takes the sum of MDBVs corresponding to the Flow which can be mapped to the logic channel as the MDBVs corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the terminal takes the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
5. The method of claim 4, wherein the determining the MDBV corresponding to the logical channel by the terminal comprises:
and the terminal determines the MDBV corresponding to the logic channel in a Media Access Control (MAC) layer.
6. The method of claim 5, wherein before the terminal determines the MDBV corresponding to the logical channel through the MAC layer, the method further comprises:
the terminal informs the mapping relation between the Flow and the logic channel of the MAC layer through a protocol data adaptation layer SDAP or a radio resource control RRC layer; or
The terminal informs the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
The terminal informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer; or
The terminal informs the MAC layer of the Flow actually mapped to the logic channel through the SDAP layer; or
The terminal informs the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And the terminal informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
7. The method of claim 1, wherein a size of the token bucket for MDBV control is an MDBV for a logical channel.
8. The method of claim 1, wherein the terminal determining the number of available tokens in a token bucket for a logical channel for MDBV control comprises:
the terminal determines the number M of tokens which are actually used in a token bucket for MDBV control in a time period (N-PDB, N) of a logical channel, and takes 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;
and the PDB is a data packet delay budget corresponding to the logic channel.
9. The method of claim 8, wherein the terminal determines the PDB corresponding to the logical channel by:
the terminal determines 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the mapping relation between the flows and the logic channel;
and the terminal determines the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
10. The method of claim 1, wherein the terminal performing resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control comprises:
step 1: the terminal sorts the logical channels with the PBR tokens and the data transmission requirements according to the descending order of the priority of the logical channels, then sequentially performs first round resource allocation on each logical channel based on the PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logical channel, and simultaneously updates the number of available tokens in a token bucket for MDBV control corresponding to the logical channel with the MDBV requirements after completing the resource allocation based on the PBR;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount of the resources to be allocated currently by the logic channel, and allocating the resources to the logic channel; and if the logical channel needing to be allocated currently is the logical channel without the MDBV requirement, the terminal allocates the resources to the logical channel according to the data volume of the resources to be allocated currently of the logical channel.
11. The method as claimed in claim 10, wherein after the terminal performs the second round of resource allocation on all logical channels requiring data transmission according to the descending order of logical channel priority, the method further comprises:
and if the terminal determines that the residual resources exist, performing resource allocation on the residual data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the resources are allocated to the data to be transmitted of all the logic channels.
12. The method of claim 1, wherein the terminal performs resource allocation for the logical channel according to the determined MDBV and the token bucket for MDBV control, further comprising:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens in a token bucket for MDBV control of the logic channel with MDBV requirements after completing the PBR-based resource allocation;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount of the resources to be allocated currently by the logic channel, and allocating the resources to the logic channel; and if the current logical channel needing to be allocated is the logical channel without the MDBV requirement and containing the GBR service, the terminal allocates resources to the logical channel.
13. The method as claimed in claim 12, wherein after the terminal performs the second round of resource allocation on all logical channels requiring data transmission according to the descending order of logical channel priority, the method further comprises:
and if the terminal determines that the residual resources exist, the terminal performs resource allocation on the residual data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the resources are allocated to the data to be transmitted of all the logic channels.
14. The method of claim 10 or 12, wherein a number of tokens that can be used in the token bucket for MDBV control for the logical channel is a difference between an MDBV for the logical channel and a number of tokens that have been actually used in the token bucket for MDBV control for the logical channel.
15. The method of claim 10 or 12, wherein the terminal updating the number of available tokens in the token bucket for MDBV control for the logical channel comprises:
the terminal determines the number M of tokens which are actually used in a token bucket for MDBV control by a logical channel within a time period (N-PDB, N), and takes the difference between the size of the token bucket and the M as the number of available tokens in the token bucket corresponding to an object;
and the PDB is a data packet delay budget corresponding to the logic channel.
16. A method for resource allocation, the method comprising:
the network side equipment determines an MDBV corresponding to the resource allocation object and a token bucket for controlling the MDBV;
the network side equipment performs resource allocation on the resource allocation object according to the determined MDBV and the token bucket for MDBV control;
if uplink resource allocation is carried out, the resource allocation object is a logical channel group; and if the downlink resource allocation is carried out, the resource allocation object is a logical channel.
17. The method of claim 16, wherein the network-side device, prior to determining the MDBV and the token bucket for MDBV control to which the resource allocation object corresponds, further comprises:
the network side equipment determines that the establishment of the logical channel is completed; and/or
And the network side equipment determines that resource allocation needs to be carried out based on MDBV according to the system load.
18. The method of claim 17, further comprising:
if the uplink resource allocation is carried out, after the network side equipment determines that the resource allocation needs to be carried out based on the MDBV according to the system load, the terminal is informed that the resource allocation needs to be carried out based on the MDBV.
19. The method of claim 16, wherein the determining, by the network-side device, the MDBV corresponding to the resource allocation object comprises:
if downlink resource allocation is carried out, the network side equipment determines the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel; or
If uplink resource allocation is carried out, the network side equipment determines the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel, and takes the sum of the MDBVs corresponding to the logic channels in the same logic channel group as the MDBV corresponding to the logic channel group; or
If uplink resource allocation is carried out, the network side equipment takes the sum of MDBVs corresponding to the logical channels reported by the terminal as the MDBV corresponding to the logical channel group; or
And if the uplink resource allocation is carried out, the network side equipment receives the MDBV corresponding to the logical channel group reported by the terminal.
20. The method of claim 19, wherein the determining, by the network-side device, the MDBV corresponding to the logical channel according to the mapping relationship between the Flow and the logical channel includes:
if Flow and logical channels use 1:1, the network side equipment takes the MDBV corresponding to the Flow as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the network side equipment takes the sum of MDBVs corresponding to the Flow which can be mapped to the logic channel as the MDBVs corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, the network side equipment takes the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
21. The method of claim 20, wherein the determining, by the network-side device, the MDBV corresponding to the resource allocation object comprises:
and the network side equipment determines the MDBV corresponding to the resource allocation object in an MAC layer.
22. The method of claim 21, wherein before the network-side device determines the MDBV for the resource allocation object at the MAC layer, the method further comprises:
the network side equipment informs the mapping relation between the Flow and the logical channel of the MAC layer through the SDAP or RRC layer; or
The network side equipment informs the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
The network side equipment informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer; or
The network side equipment informs the MAC layer of the Flow actually mapped to the logic channel through the SDAP layer; or
The network side equipment informs the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And the network side equipment informs the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
23. The method of claim 22, wherein if the resource allocation pair is a logical channel group, the method further comprises:
and the network side equipment informs the mapping relation between the logical channels and the logical channel groups of the MAC layer through the RRC layer.
24. The method of claim 16, wherein the network-side device resource allocation object is used for a number of available tokens in a token bucket for MDBV control, comprising:
if the downlink resource allocation is carried out, the network side equipment determines the number of available tokens in the token bucket corresponding to the logic channel according to the size of the token bucket used for MDBV control by the logic channel and the number M of tokens in the token bucket already used by the logic channel in the time period (N-PDB, N), or
If uplink resource allocation is carried out, the size of a token bucket used for MDBV control by the network side equipment logical channel group and the number M of tokens in the token bucket already used by the logical channel group in a time period (N-PDB, N) determine the number of available tokens in the token bucket corresponding to the logical channel group;
and the PDB is a data packet delay budget corresponding to the logic channel.
25. The method of claim 24, wherein the network side device determines the PDB corresponding to the logical channel group by:
the network side equipment determines 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the mapping relation between the flows and the logic channel;
and the network side equipment determines the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
26. The method according to any one of claims 16 to 25, wherein the allocating, by the network side device, the resource for the resource allocation object according to the determined MDBV and the token bucket for MDBV control comprises:
if the downlink resource allocation is carried out, the network side equipment takes the difference between the MDBV corresponding to the logic channel and the number of the tokens which are actually used in the token bucket for MDBV control as the number of the available tokens in the token bucket corresponding to the logic channel MDBV;
and the network side equipment performs resource allocation on the logical channel according to the minimum value between the number of available tokens in a token bucket corresponding to the logical channel MDBV and the data amount of the actual resource to be allocated of the current logical channel.
27. The method according to any one of claims 16 to 25, wherein the allocating, by the network side device, the resource for the resource allocation object according to the determined token bucket for MDBV control and the MDBV comprises:
if uplink resource allocation is carried out, the network side equipment takes the difference value of the number of the MDBV corresponding to the logical channel group and the number of the tokens which are actually used in the token bucket for MDBV control corresponding to the logical channel group as the number of the available tokens in the token bucket corresponding to the logical channel;
and the network side equipment performs resource allocation on the logical channel group according to the minimum value between the number of the 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.
28. A terminal for performing resource allocation, the terminal comprising: a processor, a memory, and a transceiver;
wherein the processor is configured to read a program in the memory and execute:
determining an MDBV corresponding to the logic channel and a token bucket for controlling the MDBV; and performing resource allocation on the logical channel according to the determined MDBV and the token bucket for MDBV control.
29. The terminal of claim 28, wherein the processor is further configured to:
before determining the MDBV corresponding to the logical channel and a token bucket for MDBV control, determining that the establishment of the logical channel is completed; and/or receiving a notification sent by the network side equipment and needing to allocate resources based on the MDBV.
30. The terminal of claim 28, wherein the processor is further configured to:
and determining the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel.
31. The terminal of claim 30, wherein the processor is further configured to:
if Flow and logical channels use 1:1 mapping, wherein the MDBV corresponding to the Flow is used as the MDBV corresponding to the logic channel;
or if the Flow and the logic channel adopt M:1 mapping, according to the mapping relation of the Flow and the logic channel, taking the sum of MDBV corresponding to the Flow which can be mapped to the logic channel as the MDBV corresponding to the logic channel;
or if the Flow and the logic channel adopt M:1 mapping, taking the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
32. The terminal of claim 31, wherein the processor is further configured to:
and determining the MDBV corresponding to the logical channel at the MAC layer.
33. The terminal of claim 32, wherein the processor is further configured to:
before determining the MDBV corresponding to the logical channel through the MAC layer, informing the mapping relation between the Flow and the logical channel through the SDAP or RRC layer; or
Informing the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
Informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer; or informing the MAC layer of the Flow actually mapped to the logical channel through the SDAP layer; or
Informing the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
34. The terminal of claim 28, wherein the size of the token bucket for MDBV control is an MDBV for a logical channel.
35. The terminal of claim 28, wherein the processor is further configured to:
determining the number M of tokens which are actually used in a token bucket for MDBV control by a logical channel within a time period (N-PDB, N), and taking 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;
and the PDB is a data packet delay budget corresponding to the logic channel.
36. The terminal of claim 35, wherein the processor is further configured to: determining the PDB corresponding to the logic channel by the following modes:
determining 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the mapping relation between the flows and the logic channel; and determining the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
37. The terminal of claim 28, wherein the processor is further configured to:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens used for MDBV control of the logic channel with MDBV requirements after completing PBR-based resource allocation;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount of the resources to be allocated currently by the logic channel, and allocating the resources to the logic channel; and if the logical channel needing to be allocated currently is the logical channel without the MDBV requirement, the terminal allocates the resources to the logical channel according to the data volume of the resources to be allocated currently of the logical channel.
38. The terminal of claim 37, wherein the processor is further configured to:
after performing the second round of resource allocation on all the logic channels with the data transmission requirements according to the descending order of the priority of the logic channels, if the terminal determines that the remaining resources exist, performing resource allocation on the remaining data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the data to be transmitted of all the logic channels are allocated with the resources.
39. The terminal of claim 28, wherein the processor is further configured to:
step 1: the terminal sorts the logic channels with available PBR tokens and data transmission requirements according to a logic channel priority descending order, then sequentially performs first round resource allocation on each logic channel based on PBR, simultaneously updates the number of tokens in a PBR token bucket corresponding to each logic channel, and simultaneously updates the number of available tokens in a token bucket for MDBV control of the logic channel with MDBV requirements after completing the PBR-based resource allocation;
step 2: after determining that the remaining resources exist, the terminal performs a second round of resource allocation on all the logical channels with the data transmission requirements according to the descending order of the logical channel priorities:
for a logic channel with MDBV requirement, in the second round of resource allocation process, taking the data amount of the allowed allocated resources of the logic channel as the smaller value of the available token number in a token bucket used for MDBV control by the logic channel and the data amount of the resources to be allocated currently by the logic channel, and allocating the resources to the logic channel; and if the current logical channel needing to be allocated is the logical channel without the MDBV requirement and containing the GBR service, the terminal allocates resources to the logical channel.
40. The terminal of claim 39, wherein the processor is further configured to:
after performing the second round of resource allocation on all the logic channels with the data transmission requirements according to the descending order of the priority of the logic channels, if the terminal determines that the remaining resources exist, performing resource allocation on the remaining data to be transmitted according to the descending order of the priority of all the logic channels with the data transmission requirements until the resources are exhausted or the data to be transmitted of all the logic channels are allocated with the resources.
41. The terminal of claim 37 or 39, wherein the number of tokens that can be used in the token bucket for MDBV control for the logical channel is a difference between the MDBV for the logical channel and a number of tokens that have been actually used in the token bucket for MDBV control for the logical channel.
42. The terminal of claim 37 or 39, wherein the processor is further configured to:
determining the number M of tokens which are actually used in a time period (N-PDB, N) of a token bucket for MDBV control by a logical channel, and taking the difference value between the size of the token bucket and the M as the number of available tokens in the token bucket corresponding to an object;
and the PDB is a data packet delay budget corresponding to the logic channel.
43. A network side device for resource allocation, the network side device comprising: a processor, a memory, and a transceiver;
wherein the processor is configured to read a program in the memory and execute:
determining an MDBV corresponding to the resource allocation object and a token bucket for controlling the MDBV; performing resource allocation on the resource allocation object according to the determined MDBV and the token bucket for MDBV control; if uplink resource allocation is carried out, the resource allocation object is a logical channel group; and if the downlink resource allocation is carried out, the resource allocation object is a logical channel.
44. The network-side device of claim 43, wherein the processor is further configured to:
before determining the MDBV corresponding to the resource allocation object and a token bucket for MDBV control, determining that the establishment of a logical channel is completed; and/or determining a need for resource allocation based on MDBV based on system load.
45. The network-side device of claim 44, wherein the network-side device comprises:
and the notification module is used for notifying the terminal that the resource allocation is required to be carried out based on the MDBV after determining that the resource allocation is required to be carried out based on the MDBV according to the system load if the uplink resource allocation is carried out.
46. The network-side device of claim 43, wherein the processor is specifically configured to:
if the downlink resource allocation is carried out, determining the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel;
if uplink resource allocation is carried out, determining the MDBV corresponding to the logic channel according to the mapping relation between the Flow and the logic channel, and taking the sum of the MDBVs corresponding to the logic channels in the same logic channel group as the MDBV corresponding to the logic channel group; or
If uplink resource allocation is carried out, taking the sum of MDBVs corresponding to the logical channels reported by the terminal as the MDBV corresponding to the logical channel group; or
And if the uplink resource allocation is carried out, receiving the MDBV corresponding to the logical channel group reported by the terminal.
47. The network-side device of claim 46, wherein the processor is specifically configured to:
if Flow and logical channels use 1:1 mapping, wherein the MDBV corresponding to the Flow is used as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, according to the mapping relation of the Flow and the logic channel, taking the sum of MDBV corresponding to the Flow which can be mapped to the logic channel as the MDBV corresponding to the logic channel; or
If the Flow and the logic channel adopt M:1 mapping, taking the sum of MDBV corresponding to the Flow actually mapped to the logic channel as the MDBV corresponding to the logic channel according to the mapping relation of the Flow and the logic channel; wherein M is a positive integer.
48. The network-side device of claim 47, wherein the processor is specifically configured to:
and determining the MDBV corresponding to the resource allocation object in the MAC layer.
49. The network-side device of claim 48, wherein the processor is further configured to:
before the MAC layer determines the MDBV corresponding to the resource allocation object, informing the mapping relation between the Flow and the logic channel of the MAC layer through the SDAP or RRC layer; or
Informing the mapping relation between the Flow and the logic channel of the MAC layer and the MDBV corresponding to the QFI through the SDAP or the RRC layer; or
Informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP or RRC layer; or
Notifying the MAC layer of the Flow actually mapped to the logical channel through the SDAP layer; or
Informing the MAC layer of MDBV corresponding to Flow and QFI actually mapped to the logic channel through the SDAP layer; or
And informing the MDBV corresponding to the logic channel of the MAC layer through the SDAP layer.
50. The network-side device of claim 49, wherein if the resource allocation pair is a logical channel group, the processor is further configured to:
and informing the mapping relation between the logic channels and the logic channel group of the MAC layer through the RRC layer.
51. The network-side device of claim 43, wherein the processor is further configured to:
if the downlink resource allocation is carried out, determining the number of available tokens in the token bucket corresponding to the logic channel according to the size of the token bucket used for MDBV control by the logic channel and the number M of tokens in the token bucket already used by the logic channel in a time period (N-PDB, N), or
If uplink resource allocation is carried out, determining the number of available tokens in a token bucket corresponding to a logical channel group according to the size of the token bucket used for MDBV control by the logical channel group and the number M of tokens in the token bucket already used by the logical channel group in a time period (N-PDB, N) ];
and the PDB is a data packet delay budget corresponding to the logic channel.
52. The network-side device of claim 51, wherein the processor is specifically configured to: determining the PDB corresponding to the logic channel by the following modes:
determining 5 QIs corresponding to all flows which can be mapped to the logic channel or 5 QIs corresponding to all flows which are actually mapped to the logic channel according to the mapping relation between the flows and the logic channel; and determining the maximum PDB as the PDB corresponding to the logic channel according to the 5QI corresponding to the Flow.
53. The network-side device of any one of claims 43 to 52, wherein the processor is specifically configured to:
if downlink resource allocation is carried out, taking the difference between the MDBV corresponding to the logic channel and the number of tokens which are actually used in the token bucket for MDBV control as the data volume of resources which can be allocated by the logic channel; and performing resource allocation on the logical channel according to the minimum value between the number of the available tokens in the token bucket corresponding to the logical channel MDBV and the data amount of the actual resource to be allocated of the current logical channel.
54. The network-side device of any one of claims 43 to 52, wherein the processor is specifically configured to:
if uplink resource allocation is carried out, taking the difference value of the number of the MDBV corresponding to the logical channel group and the number of the tokens which are actually used in the token bucket for MDBV control corresponding to the logical channel group as the number of the available tokens in the token bucket corresponding to the logical channel group; and performing resource allocation on the logical channel group according to the minimum value between the number of the 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.
55. A terminal for performing resource allocation, the terminal comprising:
the system comprises a first determining module, a second determining module and a token bucket, wherein the first determining module is used for determining the MDBV corresponding to a logic channel and the token bucket used for controlling the MDBV;
and the first allocation module is used for allocating resources for the logic channel according to the determined MDBV and the token bucket for MDBV control.
56. A network side device for resource allocation, the network side device comprising:
the second determining module is used for determining the MDBV corresponding to the resource allocation object and a token bucket for controlling the MDBV;
a second allocating module, configured to perform resource allocation on the resource allocation object according to the determined MDBV and the token bucket for MDBV control;
if uplink resource allocation is carried out, the resource allocation object is a logical channel group; and if the downlink resource allocation is carried out, the resource allocation object is a logical channel.
CN201810438523.2A 2018-05-09 2018-05-09 Method and device for resource allocation Active CN110475284B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201810438523.2A CN110475284B (en) 2018-05-09 2018-05-09 Method and device for resource allocation
PCT/CN2019/085380 WO2019214524A1 (en) 2018-05-09 2019-04-30 Resource allocation method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810438523.2A CN110475284B (en) 2018-05-09 2018-05-09 Method and device for resource allocation

Publications (2)

Publication Number Publication Date
CN110475284A CN110475284A (en) 2019-11-19
CN110475284B true CN110475284B (en) 2021-01-22

Family

ID=68467711

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810438523.2A Active CN110475284B (en) 2018-05-09 2018-05-09 Method and device for resource allocation

Country Status (2)

Country Link
CN (1) CN110475284B (en)
WO (1) WO2019214524A1 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112235833B (en) * 2020-10-14 2023-06-02 中国联合网络通信集团有限公司 Dynamic configuration method of data flow parameters and session management functional entity
EP4335162A1 (en) * 2021-05-07 2024-03-13 Telefonaktiebolaget LM Ericsson (publ) Variable maximum data burst volume patterns

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102791003A (en) * 2011-05-20 2012-11-21 中兴通讯股份有限公司 Service stream admission control realizing method and device

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621457B (en) * 2008-07-01 2012-05-23 大唐移动通信设备有限公司 Multi-service scheduling method and system
CN107204836B (en) * 2016-03-16 2020-02-04 电信科学技术研究院 Parallel scheduling method and device for carrier aggregation
US11444850B2 (en) * 2016-05-02 2022-09-13 Huawei Technologies Co., Ltd. Method and apparatus for communication network quality of service capability exposure

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102791003A (en) * 2011-05-20 2012-11-21 中兴通讯股份有限公司 Service stream admission control realizing method and device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
MDBV in Uplink;Nokia Shanghai Bell;《3GPP TSG-RAN WG2 Meeting #101bis R2-1804911》;20180420;节2,正文1-3页 *

Also Published As

Publication number Publication date
CN110475284A (en) 2019-11-19
WO2019214524A1 (en) 2019-11-14

Similar Documents

Publication Publication Date Title
US9516511B2 (en) Communication system
CN110838899B (en) Direct communication link resource allocation method and terminal
CN110505653B (en) Method, equipment and computer storage medium for controlling service quality
CN107006000B (en) Method and user equipment for transmitting messages
CN109392148B (en) Uplink resource allocation method, terminal and network equipment
CN110691382B (en) Wireless resource allocation method and network element equipment
JP6271019B2 (en) Resource allocation method, apparatus and system
CN108633088B (en) Resource scheduling method and device
CN114830818A (en) QoS management method, relay terminal, PCF network element, SMF network element and remote terminal
CN107113821A (en) The method and apparatus of transmitting uplink data
CN116406033A (en) Bearer mapping method of wireless backhaul node, wireless backhaul node and donor base station
CN110475284B (en) Method and device for resource allocation
EP3338499B1 (en) Decreasing free-riding data traffic in uplink scheduling
WO2009117955A1 (en) A method for allocating uplink resource and a user apparatus
CN104981014B (en) Descending resource allocation method and base station
CN111148225B (en) Resource scheduling method, device and equipment
CN112702109B (en) User equipment access method and device, and user equipment switching method and device
CN111955043B (en) Dynamic maximum data burst implementation in user equipment
CN110475341B (en) Method and device for resource allocation
CN111418177A (en) Reliable transmission method and related product
CN104427630B (en) A kind of grouping scheduling method and device
CN113316262B (en) Uplink resource allocation method and device, computer readable storage medium and user equipment
CN108882367B (en) Data transmission control method and device
CN113545111B (en) Resource reservation method, device and terminal
WO2015085562A1 (en) System, device and method for coordinating load balance

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20210528

Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing

Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd.

Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road

Patentee before: Telecommunications Science and Technology Research Institute Co.,Ltd.

TR01 Transfer of patent right