CN118283624A

CN118283624A - Resource allocation method, device, terminal and network side equipment

Info

Publication number: CN118283624A
Application number: CN202211716730.2A
Authority: CN
Inventors: 赵亚利; 伯特兰·皮埃尔
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Filing date: 2022-12-29
Publication date: 2024-07-02

Abstract

The application provides a resource allocation method, a resource allocation device, a terminal and network side equipment. The method comprises the following steps: the method comprises the steps that a terminal determines token bucket related parameters corresponding to a logical channel LCH set, wherein the LCH set is a group of LCHs corresponding to a Data Radio Bearer (DRB), and the group of LCHs comprises at least two LCHs; and the terminal executes resource allocation according to the token bucket related parameters corresponding to the LCH set. In the embodiment of the application, under the condition that one DRB is mapped to a group of LCH, the terminal determines the relevant parameters of the token bucket based on the LCH set, and performs resource allocation according to the relevant parameters of the token bucket of the LCH set, so that the QoS parameters of the DRB and PDU set can be ensured simultaneously when one DRB is mapped to a group of LCH, and the user experience of XR service is improved.

Description

Resource allocation method, device, terminal and network side equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a resource allocation method, a device, a terminal, and a network side device.

Background

The 5G system supports video services such as augmented reality (eXtended Reality, XR) and cloud gaming. For the transmission characteristics of XR traffic, the higher layer introduces the concept of a set of packet data units (PACKET DATA units, PDUs) (PDU set). After introducing the PDU set concept, qoS (Quality Of Service ) of different PDU sets within one data radio bearer (Data Radio Bearer, DRB) may be different, so it may be necessary to support mapping of one DRB to multiple Logical Channels (LCHs). In this case, if the resource allocation method under the existing DRB and LCH one-to-one mapping scheme is used, qoS of both DRB and PDU set cannot be guaranteed for XR service.

Disclosure of Invention

The application aims to provide a resource allocation method, a device, a terminal and network side equipment, which solve the problem that the existing resource allocation method can not guarantee QoS of DRB and PDU set at the same time.

The embodiment of the application provides a resource allocation method, which is applied to a terminal and comprises the following steps:

The method comprises the steps that a terminal determines token bucket related parameters corresponding to a logical channel LCH set, wherein the LCH set is a group of LCHs corresponding to a Data Radio Bearer (DRB), and the group of LCHs comprises at least two LCHs;

And the terminal executes resource allocation according to the token bucket related parameters corresponding to the LCH set.

Optionally, the token bucket related parameters include one or more of:

Prioritized bit rates (Prioritized Bit Rate, PBR);

token bucket size (Bucket Size Duration, BSD).

Optionally, the determining the token bucket related parameter corresponding to the logical channel LCH set includes one or more of the following:

for Uu interface between terminal and network side equipment, determining token bucket related parameters corresponding to LCH set according to radio resource control (RadioResource Control, RRC) signaling;

And for the direct communication interface between the terminal and the terminal, determining the token bucket related parameters corresponding to the LCH set according to the RRC signaling or broadcast message or the pre-configuration information.

Optionally, the determining, according to the RRC signaling or the broadcast message or the pre-configuration information, the token bucket related parameter corresponding to the LCH set includes:

Under the condition that the terminal is in an RRC connection state, determining token bucket related parameters corresponding to the LCH set according to RRC signaling; or alternatively

Under the condition that the terminal is in an RRC idle state or an RRC inactive state, determining token bucket related parameters corresponding to the LCH set according to a broadcast message sent by network side equipment; or alternatively

And under the condition that the terminal is in an off-network OOC state, determining the token bucket related parameters corresponding to the LCH set according to the pre-configuration information of the terminal.

Optionally, the token bucket related parameter corresponding to the LCH set is configured based on a data radio bearer DRB, or is configured based on the LCH set.

Optionally, in the case that the token bucket related parameters corresponding to the LCH set are configured based on the LCH set,

The LCH configuration information corresponding to each LCH in the LCH set is configured with token bucket related parameters, and DRB configuration information or the LCH configuration information contains indication information, wherein the indication information is used for determining the corresponding relation between the LCH and the LCH set;

Or alternatively

The LCH configuration information corresponding to part of LCH in the LCH set is configured with token bucket related parameters, and the DRB configuration information or the LCH configuration information contains indication information, wherein the indication information is used for determining the corresponding relation between the LCH and the LCH set.

Optionally, the method further comprises:

according to the token bucket related parameters corresponding to the LCH set, carrying out token bucket maintenance based on the LCH set;

Or alternatively

And carrying out token bucket maintenance based on each LCH in the LCH set according to the token bucket related parameters corresponding to the LCH set.

Optionally, the performing token bucket maintenance based on the LCH set according to the token bucket related parameter corresponding to the LCH set includes:

For each LCH set, when a first LCH of the LCH set is established, setting the number of tokens in a token bucket corresponding to the LCH set to be 0;

And updating the number of tokens in the token bucket corresponding to the LCH set according to the token bucket related parameters and the time length corresponding to the LCH set.

Optionally, the updating the number of tokens in the token bucket corresponding to the LCH set according to the token bucket related parameter and the time length corresponding to the LCH set includes:

The token quantity in the token bucket corresponding to the LCH set is updated as follows: the sum of the number of tokens in the current token bucket and the number of target tokens;

wherein the target number of tokens is equal to the product of PBR in the token bucket related parameters corresponding to the LCH set and the time length; the time length is the difference between the current update time and the last token bucket token number update time.

Optionally, the updating the number of tokens in the token bucket corresponding to the LCH set further includes:

if the number of tokens in the token bucket corresponding to the updated LCH set is larger than the maximum number of tokens which can be accommodated by the token bucket, setting the number of tokens in the token bucket corresponding to the LCH set as the maximum number of tokens;

wherein the maximum token number is the product of PBR and BSD in the token bucket related parameters corresponding to the LCH set.

Optionally, the performing token bucket maintenance based on each LCH in the LCH set according to the token bucket related parameter corresponding to the LCH set includes:

determining relevant parameters of a token bucket corresponding to each LCH in the LCH set;

and carrying out token bucket maintenance based on each LCH according to the token bucket related parameters corresponding to each LCH.

Optionally, the determining the token bucket related parameter corresponding to each LCH in the LCH set includes:

the token bucket related parameters corresponding to the LCH set are distributed averagely to each LCH in the LCH set;

Or alternatively

Based on the weighting value corresponding to each LCH in the LCH set, distributing the token bucket related parameters corresponding to the LCH set according to the weighting value corresponding to each LCH; and the weighting value corresponding to the LCH and the priority of the LCH have a mapping relation.

Optionally, a mapping relationship between the weighted value corresponding to the LCH and the priority of the LCH is preconfigured;

Or alternatively

The mapping relation between the weighting value corresponding to the LCH and the priority of the LCH is configured by the network side equipment through broadcast messages or special signaling.

Optionally, the maintaining the token bucket based on the LCH according to the token bucket related parameter corresponding to each LCH includes:

when the LCH is established, setting the number of tokens in a token bucket corresponding to the LCH set to be 0;

And updating the number of tokens in the token bucket corresponding to the LCH according to the token bucket related parameters and the time length corresponding to the LCH set.

Optionally, the performing resource allocation according to the token bucket related parameter corresponding to the LCH set includes:

for Uu interface or direct communication interface authorization, sequentially distributing resources for data to be transmitted of a first LCH according to the descending order of the priority of the first LCH; the first LCH is an LCH which meets the priority mapping limit of a logic channel and the number of tokens in a token bucket of a belonging LCH set is greater than 0;

and if the residual resources exist, distributing the resources for the residual data in the first LCH according to the descending order of the priority of the first LCH until the resources are exhausted or all the data to be transmitted are distributed with the resources.

Optionally, the method further comprises:

And updating the number of tokens in the token bucket of the LCH set to which the LCH belongs according to the resource allocation condition.

The embodiment of the application provides a token bucket related parameter configuration method, which is applied to network side equipment and comprises the following steps:

The network side equipment configures token bucket related parameters corresponding to the LCH set based on the DRB, or configures token bucket related parameters corresponding to the LCH set based on the LCH set;

the network side equipment sends token bucket related parameters corresponding to the LCH set to a terminal;

wherein, the LCH set is a group of LCH corresponding to one DRB, and the group of LCH comprises at least two LCH.

Optionally, the sending the token bucket related parameter to the terminal includes one of the following:

For Uu interface between terminal and network side equipment, the network side equipment sends token bucket related parameters corresponding to the LCH set to the terminal through RRC signaling;

For the direct communication interface between the terminal and the terminal, the network side device sends the token bucket related parameters corresponding to the LCH set to the terminal through RRC signaling or broadcast message or pre-configuration information.

Optionally, the network side device sends the token bucket related parameter corresponding to the LCH set to the terminal through RRC signaling or a broadcast message or preconfiguration information, including:

under the condition that the terminal is in an RRC connection state, the network side equipment sends token bucket related parameters corresponding to the LCH set to the terminal through RRC signaling; or alternatively

Under the condition that the terminal is in an RRC idle state or an RRC inactive state, the network side equipment sends token bucket related parameters corresponding to the LCH set to the terminal through a broadcast message; or alternatively

And under the condition that the terminal is in an off-network OOC state, the network side equipment sends the token bucket related parameters corresponding to the LCH set to the terminal through the pre-configuration information.

Optionally, the configuring, based on the LCH set, a token bucket related parameter corresponding to the LCH set includes:

Configuring token bucket related parameters in LCH configuration information corresponding to each LCH in the LCH set, and configuring indication information in DRB configuration information or the LCH configuration information, wherein the indication information is used for determining the corresponding relation between the LCH and the LCH set;

Or alternatively

And configuring token bucket related parameters in LCH configuration information corresponding to part of LCH in the LCH set, and configuring indication information in DRB configuration information or the LCH configuration information, wherein the indication information is used for determining the corresponding relation between the LCH and the LCH set.

Optionally, the method further comprises:

And sending the mapping relation between the weighting value corresponding to the LCH and the priority of the LCH to the terminal through a broadcast message or a special signaling.

An embodiment of the present application provides a terminal including: memory, transceiver, processor:

A memory for storing a computer program; a transceiver for receiving and transmitting data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

determining a token bucket related parameter corresponding to a logical channel LCH set, wherein the LCH set is a group of LCHs corresponding to a Data Radio Bearer (DRB), and the group of LCHs comprises at least two LCHs;

And executing resource allocation according to the token bucket related parameters corresponding to the LCH set.

Optionally, the token bucket related parameters include one or more of:

Prioritized bit rate PBR;

Token bucket size BSD.

Optionally, the processor is configured to read the computer program in the memory and perform one or more of the following operations:

for Uu interface between terminal and network side equipment, determining relevant parameters of token bucket corresponding to LCH set according to Radio Resource Control (RRC) signaling;

Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

Under the condition that the terminal is in an off-network OOC state, determining token bucket related parameters corresponding to an LCH set according to the pre-configuration information of the terminal

Or alternatively

The embodiment of the application provides network side equipment, which comprises the following components: memory, transceiver, processor:

Configuring token bucket related parameters corresponding to the LCH set based on the DRB, or configuring token bucket related parameters corresponding to the LCH set based on the LCH set;

Sending token bucket related parameters corresponding to the LCH set to a terminal;

Optionally, the processor is configured to read the computer program in the memory and perform one of the following operations:

Or alternatively

An embodiment of the present application provides a resource allocation device, which is applied to a terminal, and includes:

A determining unit, configured to determine a token bucket related parameter corresponding to a logical channel LCH set, where the LCH set is a group of LCHs corresponding to one data radio bearer DRB, and the group of LCHs includes at least two LCHs;

And the allocation unit is used for executing resource allocation according to the token bucket related parameters corresponding to the LCH set.

An embodiment of the present application provides a token bucket related parameter configuration apparatus, which is applied to a network side device, and includes:

a configuration unit, configured to configure a token bucket related parameter corresponding to the LCH set based on the DRB, or configure a token bucket related parameter corresponding to the LCH set based on the LCH set;

a first sending unit, configured to send token bucket related parameters corresponding to the LCH set to a terminal;

Embodiments of the present application provide a processor-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the resource allocation method described above, or performs the steps of the token bucket-related parameter configuration method described above.

The technical scheme of the application has the beneficial effects that:

In the embodiment of the application, under the condition that one DRB is mapped to a group of LCH, the terminal determines the relevant parameters of the token bucket based on the LCH set, and performs resource allocation according to the relevant parameters of the token bucket of the LCH set, so that the QoS parameters of the DRB and PDU set can be ensured simultaneously when one DRB is mapped to a group of LCH, and the user experience of XR service is improved.

Drawings

Fig. 1 is a schematic diagram of a structure of a user plane protocol stack according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a data frame according to an embodiment of the present application;

FIG. 3 shows a mapping diagram of an embodiment of the present application;

FIG. 4 is a flow chart of a resource allocation method according to an embodiment of the present application;

FIG. 5 is a flow chart illustrating a token bucket related parameter configuration method according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a resource allocation device according to an embodiment of the present application;

FIG. 7 is a schematic diagram of a token bucket related parameter configuration device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a network side device according to an embodiment of the present application.

Detailed Description

In order to make the technical problems, technical solutions and advantages to be solved more apparent, the following detailed description will be given with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided merely to facilitate a thorough understanding of embodiments of the application. It will therefore be apparent to those skilled in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the application. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present application, it should be understood that the sequence numbers of the following processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

In the embodiment of the application, the term "and/or" describes the association relation of the association objects, which means that three relations can exist, for example, a and/or B can be expressed as follows: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

The term "plurality" in embodiments of the present application means two or more, and other adjectives are similar.

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

In describing embodiments of the present application, some concepts used in the following description are first explained.

1. Basic process for 5G air interface data processing

As shown in fig. 1, the 5G user plane air interface protocol layer includes a service data adaptation protocol (SERVICE DATA Adaptation Protocol, SDAP) layer, a packet data convergence protocol (PACKET DATA Convergence Protocol, PDCP) layer, a radio link layer Control protocol (Radio Link Control, RLC) layer, a medium access Control (MEDIA ACCESS Control, MAC) layer, and a Physical (PHY) layer.

After one QoS flow (flow) arrives at the SDAP, the SDAP performs QoS flow to DRB mapping, which forms an SDAP protocol data unit (Protocol Data Unit, PDU). SDAP PDU is PDCP service data Unit (SERVICE DATA Unit, SDU). The PDCP layer performs operations such as header compression, encryption and the like on the PDCP SDU, and then delivers the PDCP SDU to the RLC layer, and then the RLC layer packages RLC PDUs according to the scheduling information of the MAC layer, delivers the RLC PDUs to the MAC, packages the received RLC PDUs into MAC PDUs, and delivers the MAC PDUs to the physical layer for transmission.

The rule of performing QoS flow to DRB mapping by the SDAP is as follows, and since QoS attributes of data packets in one QoS flow are basically consistent, one QoS flow can only be mapped to one DRB.

2. Basic concept of XR

XR is divided into the following categories:

1) Augmented reality (Augmented Reality, AR): seamlessly integrating the real world and the virtual world;

2) Virtual Reality (VR): generating a virtual world by using equipment simulation;

3) Mixed Reality (MR): and contains real physical entity and virtual information.

XR traffic is modeled in terms of data frames (frames), which can be partitioned into multiple packet data units (PACKET DATA units, PDUs), as shown in fig. 2. The PDU set is defined as follows: one or more PDUs corresponding to the same information unit constitute one PDU set.

3. For PDU set, the mapping relationship among PDU set, quality of service (Quality of Service, qoS) flow (flow), data radio bearer (Data Radio Bearer, DRB), logical Channel (LCH) may be as shown in fig. 3, i.e. one DRB may be mapped to a plurality of LCHs.

The embodiment of the application provides a resource allocation method, a device, a terminal and network side equipment, which are used for solving the problem that the existing resource allocation method can not ensure QoS of DRB and PDU set at the same time.

The method and the device are based on the same application, and because the principles of solving the problems by the method and the device are similar, the implementation of the device and the method can be referred to each other, and the repetition is not repeated.

As shown in fig. 4, an embodiment of the present application provides a resource allocation method, which is applied to a terminal, and specifically includes the following steps:

Step 401, a terminal determines a token bucket related parameter corresponding to a logical channel LCH set, wherein the LCH set is a group of LCHs corresponding to a data radio bearer DRB, and the group of LCHs includes at least two LCHs;

And step 402, the terminal executes resource allocation according to the token bucket related parameters corresponding to the LCH set.

In this embodiment, if one bearer or one DRB of the terminal corresponds to one LCH set, that is, one bearer or one DRB is mapped to one LCH set, the terminal determines a token bucket related parameter based on the LCH set, and performs resource allocation according to the token bucket related parameter of the LCH set, so that QoS parameters of the DRB and PDU set can be ensured at the same time when one DRB is mapped to one LCH set, and user experience of the XR service is improved.

Wherein the number of LCHs in the LCH set is an integer greater than or equal to 2.

Optionally, the token bucket related parameters include one or more of:

Prioritized bit rate PBR;

a token bucket size BSD, such as the maximum number of tokens that a token bucket can accommodate.

In the embodiment of the application, when the terminal determines the relevant parameters of the token bucket corresponding to the LCH set, the relevant parameters of the token bucket can be determined for Uu interfaces between the terminal and the network side equipment, and the relevant parameters of the token bucket can also be determined for direct communication interfaces (such as PC5 interfaces and bypass interfaces) between the terminal and the terminal, namely, the resource allocation method in the embodiment of the application can be applied to uplink and downlink communication between the terminal and the network side equipment and can also be applied to direct communication of side links (Sidelink and SL) between the terminal and the terminal.

As an optional embodiment, the determining the token bucket related parameter corresponding to the logical channel LCH set includes one or more of the following:

(1) And for Uu interface between the terminal and the network side equipment, determining the token bucket related parameters corresponding to the LCH set according to the Radio Resource Control (RRC) signaling.

In this embodiment, the network side device may send an RRC dedicated signaling to the terminal, where the RRC dedicated information includes token bucket related parameters, and the terminal determines the token bucket related parameters in the RRC dedicated signaling as token bucket related parameters corresponding to the LCH set.

(2) And for the direct communication interface between the terminal and the terminal, determining the token bucket related parameters corresponding to the LCH set according to the RRC signaling or broadcast message or the pre-configuration information.

In this embodiment, the first message may be a message sent by the network side device to the terminal, or may be a preconfigured message of the terminal, where the first message includes a token bucket related parameter, and the terminal determines the token bucket related parameter in the first message as a token bucket related parameter corresponding to the LCH set.

1) And under the condition that the terminal is in the RRC connection state, determining the token bucket related parameters corresponding to the LCH set according to the RRC signaling. If the terminal is in the RRC connected state, the network side device sends an RRC signaling to the terminal, where the RRC signaling includes token bucket related parameters, and the terminal determines the token bucket related parameters in the RRC signaling as token bucket related parameters corresponding to the LCH set.

Or 2) under the condition that the terminal is in an RRC IDLE (IDLE) state or an RRC INACTIVE (INACTIVE) state, determining token bucket related parameters corresponding to the LCH set according to a broadcast message sent by network side equipment; if the terminal is in RRC IDLE state or RRC INACTIVE state, the network side device sends a broadcast message, for example, a system information block (System Information Block, SIB), to the terminal, where the broadcast message includes token bucket related parameters, and the terminal determines the token bucket related parameters in the received broadcast message as token bucket related parameters corresponding to the LCH set.

Or 3) under the condition that the terminal is in an off-network OOC state, determining the token bucket related parameters corresponding to the LCH set according to the pre-configuration information of the terminal. Optionally, the pre-configuration information is SL pre-configuration information. In this embodiment, if the terminal is in OOC state, the SL pre-configuration information includes a token bucket related parameter, and the terminal determines the token bucket related parameter in the SL pre-configuration information as a token bucket related parameter corresponding to the LCH set.

In this embodiment, when the network side device configures the token bucket related parameters, the network side device may be configured based on DRB or LCH set. For example: for Uu interface between terminal and network side equipment, network side equipment sends RRC special signaling to terminal, wherein the RRC special signaling contains token bucket related parameters configured based on DRB or LCH set, and the terminal uses the token bucket related parameters contained in the RRC special signaling as token bucket related parameters corresponding to LCH set.

For example, for a direct communication interface between a terminal and the terminal, the terminal is in an RRC connection state, and an RRC dedicated signaling sent by the network side device to the terminal includes token bucket related parameters configured based on DRBs or based on LCH sets, where the terminal uses the token bucket related parameters as token bucket related parameters corresponding to the LCH sets; or if the terminal is in the RRC IDLE or INACTIVE state, the broadcast message sent by the network side equipment to the terminal contains the token bucket related parameters configured based on the DRB or based on the LCH set, and the terminal takes the token bucket related parameters as the token bucket related parameters corresponding to the LCH set; or if the terminal is in a desquamation state, the SL pre-configuration information comprises token bucket related parameters configured based on DRB or LCH set, and the terminal takes the token bucket related parameters as token bucket related parameters corresponding to the LCH set.

Or alternatively

In this embodiment, for the case of configuring the token bucket related parameters based on the LCH set, a specific configuration manner may be: and each LCH configuration corresponding to the LCH set comprises a token bucket related parameter, and indication information is carried in DRB configuration information or LCH configuration information, wherein the indication information is used for determining the corresponding relation between the LCH and the LCH set. For example, the indication information may be LCH set indication information to which LCH belongs or the indication information may be an identifier, where LCHs corresponding to the same identifier belong to one LCH set; or part of LCH (for example, N LCH, N is an integer greater than or equal to 1) configuration in the LCH set contains the relevant parameters of the token bucket, and the DRB configuration information or the LCH configuration information carries indication information, wherein the indication information is used for determining the corresponding relation between the LCH and the LCH set. For example, the indication information may be LCH set indication information to which LCH belongs or the indication information may be an identifier, where LCHs corresponding to the same identifier belong to one LCH set.

As an alternative embodiment, the method further comprises:

Or alternatively

In this embodiment, performing token bucket maintenance may include maintaining a number of tokens in the token bucket. Specifically, token bucket maintenance may be performed based on an LCH set, or token bucket related parameters corresponding to each LCH in the LCH set may be determined based on token bucket related parameters corresponding to the LCH set, and token bucket maintenance may be performed based on the LCH.

For each LCH set, when a first LCH of the LCH set is established, setting the number of tokens in a token bucket corresponding to the LCH set to be 0; and updating the number of tokens in the token bucket corresponding to the LCH set according to the token bucket related parameters and the time length corresponding to the LCH set.

In this embodiment, when the token bucket is maintained, if the token bucket is maintained based on the LCH set, for each LCH set, when the DRB or the first LCH in the LCH set is established, the initial value of the number of tokens in the token bucket (denoted by Bj) is set to 0; as time T increases, the number of tokens in the token bucket is updated.

Optionally, the updating the number of tokens in the token bucket corresponding to the LCH set according to the token bucket related parameter and the time length corresponding to the LCH set includes: the token quantity in the token bucket corresponding to the LCH set is updated as follows: the sum of the number of tokens in the current token bucket and the number of target tokens; wherein the target number of tokens is equal to the product of PBR in the token bucket related parameters corresponding to the LCH set and the time length; the time length is the difference between the current update time and the last token bucket token number update time.

In this embodiment, with time, the number of tokens Bj in the updated token bucket is bj=bj0+pbr×t, bj0 is the number of tokens in the token bucket before the update, and T is the length of time from the update to the last Bj update.

Optionally, the updating the number of tokens in the token bucket corresponding to the LCH set further includes: if the number of tokens in the token bucket corresponding to the updated LCH set is larger than the maximum number of tokens which can be accommodated by the token bucket, setting the number of tokens in the token bucket corresponding to the LCH set as the maximum number of tokens; wherein the maximum token number is the product of PBR and BSD in the token bucket related parameters corresponding to the LCH set. In this embodiment, if Bj is greater than the maximum number of tokens that the token bucket can hold, bj is set to the maximum number of tokens that the token bucket can hold. Where the maximum number of tokens that a token bucket can accommodate = PBR x BSD.

As an optional embodiment, the performing token bucket maintenance based on each LCH in the LCH set according to the token bucket related parameter corresponding to the LCH set includes: determining relevant parameters of a token bucket corresponding to each LCH in the LCH set; and carrying out token bucket maintenance based on each LCH according to the token bucket related parameters corresponding to each LCH.

Or alternatively

In this embodiment, when determining the token bucket related parameter corresponding to each LCH in the LCH set based on the token bucket related parameter corresponding to the LCH set, the terminal depends on the terminal implementation. For example: the terminal performs average allocation on the token bucket related parameters corresponding to the LCH set among LCHs in the LCH set according to the token bucket related parameters corresponding to the LCH set; or the terminal carries out weighted allocation on the token bucket related parameters corresponding to the LCH set aiming at each LCH in the LCH set based on the token bucket related parameters corresponding to the LCH set and the priority of each LCH in the LCH set, wherein the allocation weights corresponding to the LCH with different priorities are different.

Or alternatively

In this embodiment, the correspondence between the priority of the LCH and the weighting value corresponding to the LCH may be preconfigured, or configured by the network side device through a broadcast message, or configured by the network side device through dedicated signaling.

Optionally, according to the token bucket related parameter corresponding to each LCH, performing token bucket maintenance based on the LCH includes: when the LCH is established, setting the number of tokens in a token bucket corresponding to the LCH set to be 0; and updating the number of tokens in the token bucket corresponding to the LCH according to the token bucket related parameters and the time length corresponding to the LCH set.

In this embodiment, when the terminal performs token bucket maintenance based on LCH, for each LCH, when the LCH is established, the initial value of the number of tokens Bj in the token bucket is set to 0; as time T increases, the update Bj is bj=bj0+pbr×t, and T is the length of time this update is from the last Bj update. And if Bj is equal to the maximum number of tokens which can be contained in the token bucket, setting Bj as the maximum number of tokens which can be contained in the token bucket. The maximum number of tokens that the token bucket can accommodate is: pbr×bsd.

As an optional embodiment, the performing resource allocation according to the token bucket related parameters corresponding to the LCH set includes:

Optionally, the method further comprises: and updating the number of tokens in the token bucket of the LCH set to which the LCH belongs according to the resource allocation condition.

In this embodiment, for Uu interface authorization (e.g., UL grant), the terminal selects an LCH that satisfies the logical channel priority mapping constraint and that has a Bj greater than 0 corresponding to the LCH set to which the LCH belongs, and allocates resources according to the priority degradation order of the LCH. If the PBR corresponding to the LCH set to which the LCH belongs is infinite, resources are allocated to all data to be transmitted of the LCH. If there are remaining resources, the LCHs satisfying the logical channel priority mapping constraint are allocated resources in descending order of priority (not limited by Bj) until the resources are exhausted or all data of the LCHs are allocated resources. Wherein, the logical channel priority mapping limitation may refer to: logical channels meeting priority requirements (e.g., priority greater than a predetermined priority).

Optionally, in the resource allocation process, updating the Bj corresponding to the LCH set to which the LCH belongs according to the resource allocation condition, for example: an n-bit (bit) resource is allocated for the first portion of data of one LCH, and then Bj is updated to Bj-n.

The implementation process of the resource allocation method is respectively illustrated below for Uu interface between the terminal and the network side device and direct communication interface between the terminal and the terminal.

(1) Taking Uu interface between terminal and network side equipment as an example, and assuming token bucket maintenance based on LCH set, the resource allocation process includes:

Step 1, a terminal determines relevant parameters of a token bucket corresponding to an LCH set.

The method comprises the steps that a terminal receives RRC special signaling sent by network side equipment, wherein the RRC special signaling comprises token bucket related parameters configured based on DRB or token bucket related parameters configured by LCH sets, and the terminal takes the token bucket related parameters in the RRC special signaling as token bucket related parameters corresponding to the LCH sets. Wherein the token bucket related parameters include PBR and/or BSD.

If the token bucket related parameters are configured based on the LCH set, the specific configuration mode may be one of the following:

1) Each LCH configuration information corresponding to the LCH set contains a token bucket related parameter, and indication information is carried in DRB configuration information or LCH configuration information, wherein the indication information is used for determining the corresponding relation between the LCH and the LCH set. For example, the indication information may be LCH set indication information to which LCH belongs or the indication information may be an identifier, where LCHs corresponding to the same identifier belong to one LCH set.

2) The method comprises the steps that a part of LCH (for example, N LCH, N is an integer greater than or equal to 1) configuration in an LCH set comprises token bucket related parameters, and indication information is carried in DRB configuration information or LCH configuration information, wherein the indication information is used for determining the corresponding relation between the LCH and the LCH set. For example, the indication information may be LCH set indication information to which LCH belongs or the indication information may be an identifier, where LCHs corresponding to the same identifier belong to one LCH set.

And 2, the terminal executes token bucket maintenance based on the LCH set aiming at the UL grant.

Specifically, the terminal performs token bucket maintenance based on the LCH set, which may specifically include one or a combination of the following contents:

1) For each LCH set, when the DRB or the first LCH in the LCH set is established, the initial value of the number of tokens Bj in the token bucket is set to 0.

As time T increases, update Bj to bj=bj0+pbr×t, bj0 being the current number of tokens in the token bucket; t is the length of time since the last Bj update. If Bj > the maximum number of tokens that the token bucket can hold, then Bj is set to the maximum number of tokens that the token bucket can hold. Where the maximum number of tokens that a token bucket can accommodate = PBR x BSD.

Optionally, the token bucket maintenance of the terminal based on the LCH set further includes an LCP procedure:

for the UL grant, selecting a logical channel satisfying the mapping constraint and Bj >0 corresponding to the LCH set to which the LCH belongs, and sequentially allocating resources according to the descending order of the priorities of the logical channels. If the PBR corresponding to the LCH set to which the LCH belongs is infinite, resources are allocated to all data to be transmitted of the LCH.

And updating Bj corresponding to the LCH set to which the LCH belongs according to the resource allocation condition.

If there are remaining resources, the LCHs satisfying the logical channel priority mapping constraint are allocated resources in descending order of priority (not limited by Bj) until the resources are exhausted or all data of the LCHs are allocated resources.

(2) Taking Uu interface between the terminal and the network side device as an example, and assuming that token bucket maintenance is performed based on each LCH in the LCH set, the resource allocation process includes:

The method comprises the steps that a terminal receives RRC special signaling sent by network side equipment, wherein the RRC special signaling comprises token bucket related parameters configured based on DRB or token bucket related parameters configured by LCH sets, and the terminal takes the token bucket related parameters in the RRC special signaling as token bucket related parameters corresponding to the LCH sets.

And 2, the terminal determines the relevant parameters of the token bucket corresponding to each LCH.

The terminal determines the token bucket related parameters corresponding to each LCH in the LCH set based on the token bucket related parameters corresponding to the LCH set, and how to implement the token bucket related parameters depends on the terminal implementation, for example:

1) And according to the token bucket related parameters corresponding to the LCH set, carrying out average allocation on the token bucket related parameters corresponding to the LCH set aiming at each LCH in the LCH set.

2) Based on the token bucket related parameters corresponding to the LCH set and the priority of each LCH in the LCH set, weighting and distributing the token bucket related parameters corresponding to the LCH set for each LCH in the LCH set, wherein the distribution weights corresponding to LCH with different priorities are different.

Wherein the mapping between the priority and the weighting value may be determined in one of the following ways:

pre-configuring;

configuring by the network device via broadcast;

configured by the network device through dedicated signaling.

For example, assuming that the PBR corresponding to the LCH set is 100gbps, two LCHs are included in the LCH set, labeled LCH1 and LCH2, respectively. If the relevant parameters of the token bucket adopt an average allocation mode, the PBR corresponding to the LCH1 and the LCH2 are both 50Gbps. If the token bucket related parameters adopt a weighting mode, the weighting value corresponding to LCH1 is 4, the weighting value corresponding to LCH2 is 1, the PBR corresponding to LCH1 is 40Gbps, and the PBR corresponding to LCH1 is 10Gbps.

For another example, assume that the BSD corresponding to the LCH set is 100gb, and that two LCHs are included in the LCH set, labeled LCH1 and LCH2, respectively. If the relevant parameters of the token bucket adopt an average distribution mode, the BSDs corresponding to the LCH1 and the LCH2 are both 50Gb. If the token bucket related parameter adopts a weighting mode, the weighting value corresponding to LCH1 is 4, the weighting value corresponding to LCH2 is 1, the BSD corresponding to LCH1 is 40Gb, and the PBR corresponding to LCH2 is 10Gb.

And 3, the terminal executes token bucket maintenance based on LCH aiming at the UL grant.

Terminal LCH-based token bucket maintenance may include:

For each LCH, when the LCH is established, the initial value of the number of tokens Bj in the token bucket is set to 0. As time T increases, the update Bj is bj=bj0+pbr×t, bj0 is the current number of tokens in the token bucket, and T is the length of time since the last Bj update. And if Bj is equal to the maximum number of tokens which can be contained in the token bucket, setting Bj as the maximum number of tokens which can be contained in the token bucket. The maximum number of tokens that the token bucket can accommodate is: pbr×bsd.

The terminal LCH-based token bucket maintenance also includes the LCP procedure:

(3) Taking a direct communication interface between terminals as an example, and assuming that token bucket maintenance is performed based on an LCH set, the resource allocation process includes:

For the interface (direct communication interface or PC5 interface or bypass interface) between the terminals, the specific manner of determining the token bucket related parameters corresponding to the LCH set may be one of the following manners:

Mode one: if the terminal is in an RRC connection state, the terminal can receive an RRC dedicated signaling sent by the network side equipment, wherein the RRC dedicated signaling contains token bucket related parameters configured based on DRB or LCH sets, and the terminal takes the token bucket related parameters as token bucket related parameters corresponding to the LCH sets.

Mode two: if the terminal is in the RRC IDLE or INACTIVE state, the terminal may receive a broadcast message (such as SIB) sent by the network side device, where the RRC dedicated signaling includes token bucket related parameters configured based on the DRB or on the LCH set, and the terminal uses the token bucket related parameters as token bucket related parameters corresponding to the LCH set.

Mode three: if the terminal is in the OOC state, the SL pre-configuration information comprises token bucket related parameters configured based on DRB or LCH set, and the terminal takes the token bucket related parameters as token bucket related parameters corresponding to the LCH set.

And 2, the terminal executes token bucket maintenance based on the LCH set aiming at the SL grant.

For SL grant, selecting a logic channel which satisfies the mapping limit and corresponds to Bj >0 of LCH set to which LCH belongs, and sequentially distributing resources according to the descending order of the priority of the logic channel. If the PBR corresponding to the LCH set to which the LCH belongs is infinite, resources are allocated to all data to be transmitted of the LCH.

(4) Taking a direct communication interface between terminals as an example, and assuming that token bucket maintenance is performed based on each LCH in the LCH set, the resource allocation procedure includes:

pre-configuring;

configuring by the network device via broadcast;

configured by the network device through dedicated signaling.

And 3, the terminal executes token bucket maintenance based on LCH aiming at the SL grant.

Terminal LCH-based token bucket maintenance may include:

Optionally, the terminal LCH-based token bucket maintenance further includes the following LCP procedure:

As shown in fig. 5, an embodiment of the present application provides a token bucket related parameter configuration method, which is applied to a network side device, and the method includes:

step 501, the network side device configures token bucket related parameters corresponding to the LCH set based on the DRB, or configures token bucket related parameters corresponding to the LCH set based on the LCH set;

Step 502, the network side device sends token bucket related parameters corresponding to the LCH set to a terminal;

In this embodiment, the network side device configures token bucket related parameters corresponding to the LCH set based on the DRB or based on the LCH set, and sends the token bucket related parameters corresponding to the LCH set to the terminal, so that the terminal can determine the token bucket related parameters corresponding to the LCH set. The LCH set is a group of LCH corresponding to one DRB, the group of LCH comprises at least two LCH, and the terminal determines the relevant parameters of the token bucket of the group of LCH corresponding to one DRB, so that QoS parameters of the DRB and PDU set can be ensured at the same time, and the user experience of XR service is improved.

Optionally, the token bucket related parameters include one or more of:

PBR；

BSD, e.g., the maximum number of tokens that a token bucket can accommodate.

As an optional embodiment, the sending the token bucket related parameter to the terminal includes one of:

(1) For Uu interface between terminal and network side equipment, the network side equipment sends token bucket related parameters corresponding to the LCH set to the terminal through RRC signaling.

(2) For the direct communication interface between the terminal and the terminal, the network side device sends the token bucket related parameters corresponding to the LCH set to the terminal through RRC signaling or broadcast message or pre-configuration information.

In this embodiment, the RRC signaling or broadcast message or the preconfiguration information includes a token bucket related parameter, and the terminal determines the token bucket related parameter in the RRC signaling or broadcast message or the preconfiguration information as a token bucket related parameter corresponding to the LCH set.

1) Under the condition that the terminal is in an RRC connection state, the network side equipment sends token bucket related parameters corresponding to the LCH set to the terminal through RRC signaling; for example: if the terminal is in the RRC connection state, the network side equipment sends RRC signaling to the terminal, wherein the RRC signaling contains token bucket related parameters, and the terminal determines the token bucket related parameters in the RRC signaling as token bucket related parameters corresponding to the LCH set.

Or 2) under the condition that the terminal is in an RRC idle state or an RRC inactive state, the network side equipment sends token bucket related parameters corresponding to the LCH set to the terminal through a broadcast message; for example: if the terminal is in the RRC IDLE state or RRC INACTIVE state, the network side device sends a broadcast message, for example, an SIB, to the terminal, where the broadcast message includes token bucket related parameters, and the terminal determines the token bucket related parameters in the received broadcast message as token bucket related parameters corresponding to the LCH set.

Or 3) under the condition that the terminal is in an OOC state, the network side equipment sends the token bucket related parameters corresponding to the LCH set to the terminal through the pre-configuration information. Optionally, the pre-configuration information is SL pre-configuration information. In this embodiment, if the terminal is in OOC state, the SL pre-configuration information includes a token bucket related parameter, and the terminal determines the token bucket related parameter in the SL pre-configuration information as a token bucket related parameter corresponding to the LCH set.

Or alternatively

In this embodiment, for the case of configuring the token bucket related parameters based on the LCH set, a specific configuration manner may be: and each LCH configuration corresponding to the LCH set comprises a token bucket related parameter, and indication information is carried in DRB configuration information or LCH configuration information, wherein the indication information is used for determining the corresponding relation between the LCH and the LCH set. For example, the indication information may be LCH set indication information to which LCH belongs or the indication information may be an identifier, where LCHs corresponding to the same identifier belong to one LCH set; or part of LCH (for example, N LCH, N is an integer greater than or equal to 1) configuration in the LCH set contains token bucket related parameters, and indication information is carried in DRB configuration information or LCH configuration information, wherein the indication information is used for determining the corresponding relation between the LCH and the LCH set. For example, the indication information may be LCH set indication information to which LCH belongs or the indication information may be an identifier, where LCHs corresponding to the same identifier belong to one LCH set.

Optionally, the method further comprises: and sending the mapping relation between the weighting value corresponding to the LCH and the priority of the LCH to the terminal through a broadcast message or a special signaling.

In this embodiment, the mapping relationship between the weighted value of the LCH and the priority of the LCH may be used for the terminal to determine the token bucket related parameter of each LCH in the LCH set. The terminal can determine the relevant parameters of the token bucket corresponding to each LCH based on the relevant parameters of the token bucket of the LCH set; and carrying out token bucket maintenance based on the LCH according to the token bucket related parameters corresponding to each LCH. Specifically, when determining the token bucket related parameter corresponding to each LCH, the token bucket related parameter corresponding to the LCH set may be distributed equally among each LCH in the LCH set, or the token bucket related parameter corresponding to the LCH set may be distributed according to the weighted value of the LCH for each LCH based on the weighted value of each LCH in the LCH set. The execution process of the token bucket maintenance by the terminal is not described in detail herein.

In the embodiment of the application, the network side equipment configures the token bucket related parameters corresponding to the LCH set based on the DRB or based on the LCH set, and sends the token bucket related parameters corresponding to the LCH set to the terminal, so that the terminal determines the token bucket related parameters corresponding to the LCH set. The LCH set is a group of LCH corresponding to one DRB, the group of LCH comprises at least two LCH, and the terminal determines the relevant parameters of the token bucket of the group of LCH corresponding to one DRB, so that QoS parameters of the DRB and PDU set can be ensured at the same time, and the user experience of XR service is improved.

The above embodiments are described with respect to the resource allocation method and the token bucket related parameter configuration method of the present application, and the following embodiments will further describe the corresponding devices with reference to the accompanying drawings.

Specifically, as shown in fig. 6, an embodiment of the present application provides a resource allocation apparatus 600, applied to a terminal, including:

a determining unit 610, configured to determine a token bucket related parameter corresponding to a logical channel LCH set, where the LCH set is a group of LCHs corresponding to one data radio bearer DRB, and the group of LCHs includes at least two LCHs;

and an allocation unit 620, configured to perform resource allocation according to the token bucket related parameters corresponding to the LCH set.

Optionally, the token bucket related parameters include one or more of:

Prioritized bit rate PBR;

Token bucket size BSD.

Optionally, the determining unit is specifically configured to perform one or more of the following:

Optionally, the determining unit is specifically configured to:

And under the condition that the terminal is in an OOC state, determining the token bucket related parameters corresponding to the LCH set according to the pre-configuration information of the terminal.

Or alternatively

Optionally, the apparatus further includes: the maintenance unit is specifically used for:

Or alternatively

Optionally, the maintenance unit is specifically configured to:

Optionally, the maintenance unit is further configured to:

Optionally, the maintenance unit is specifically configured to:

The token bucket related parameters corresponding to the LCH sets are distributed evenly among each LCH in the LCH sets;

Or alternatively

Optionally, the maintenance unit is specifically configured to:

Optionally, the distribution unit is specifically configured to:

Optionally, the apparatus further includes:

And the updating unit is used for updating the number of tokens in the token bucket of the LCH set to which the LCH belongs according to the resource allocation condition.

It should be noted that, the above device provided in the embodiment of the present application can implement all the method steps implemented in the method embodiment applied to the terminal, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those in the method embodiment in the embodiment are omitted.

Specifically, as shown in fig. 7, an embodiment of the present application provides a token bucket related parameter configuration apparatus 700, applied to a network side device, including:

A configuration unit 710, configured to configure a token bucket related parameter corresponding to the LCH set based on the DRB, or configure a token bucket related parameter corresponding to the LCH set based on the LCH set;

A first sending unit 720, configured to send, to a terminal, a token bucket related parameter corresponding to the LCH set;

Optionally, the first sending unit is specifically configured to perform one of the following:

Optionally, the first sending unit is specifically configured to:

Optionally, the configuration unit is specifically configured to:

Or alternatively

Optionally, the apparatus further includes:

and the second sending unit is used for sending the mapping relation between the weighting value corresponding to the LCH and the priority of the LCH to the terminal through a broadcast message or a special signaling.

It should be noted that, the above device provided in this embodiment of the present application can implement all the method steps implemented in the method embodiment applied to the network side device, and can achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those in the method embodiment in this embodiment are omitted.

It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a processor-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

As shown in fig. 8, an embodiment of the present application further provides a terminal, including: memory 820, transceiver 800, processor 810; wherein the memory 820 is used for storing a computer program; a transceiver 800 for receiving and transmitting data under the control of the processor 810; a processor 810 for reading the computer program in the memory and performing the following operations:

Optionally, the token bucket related parameters include one or more of:

Prioritized bit rate PBR;

Token bucket size BSD.

Or alternatively

and updating the number of tokens in the token bucket corresponding to the LCH set 5 according to the token bucket related parameters and the time length corresponding to the LCH set.

Wherein the target token number is equal to the product of 0PBR in the token bucket related parameters corresponding to the LCH set and the time length; the time length is the difference between the current update time and the last token bucket token number update time.

If the number of tokens in the token bucket corresponding to the updated LCH set is larger than the maximum number of tokens which can be accommodated by the token bucket, setting the number of tokens in the token bucket corresponding to the LCH set as the maximum number of tokens of 5;

Determining relevant parameters of a token bucket corresponding to each LCH in the LCH set; and 0, carrying out token bucket maintenance based on each LCH according to the token bucket related parameters corresponding to each LCH.

Or alternatively

5, Distributing the token bucket related parameters corresponding to the LCH set according to the weighting values corresponding to the LCH for each LCH based on the weighting values corresponding to each LCH in the LCH set; and the weighting value corresponding to the LCH and the priority of the LCH have a mapping relation.

Or alternatively

Wherein in fig. 8, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 810 and various circuits of memory represented by memory 820, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 800 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 830 may also be an interface capable of interfacing with an inscribed desired device for a different user device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 810 is responsible for managing the bus architecture and general processing, and the memory 820 may store data used by the processor 810 in performing operations.

Alternatively, the processor 810 may be a Central Processing Unit (CPU), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA), or complex Programmable logic device (Complex Programmable Logic Device, CPLD), which may also employ a multi-core architecture.

The processor is operable to perform any of the methods provided by embodiments of the present application in accordance with the obtained executable instructions by invoking a computer program stored in a memory. The processor and the memory may also be physically separate.

As shown in fig. 9, an embodiment of the present application further provides a network side device, including: memory 920, transceiver 900, processor 910; wherein the memory 920 is used for storing a computer program; a transceiver 900 for receiving and transmitting data under the control of the processor 910; a processor 910 for reading the computer program in the memory and performing the following operations:

Or alternatively

Wherein in fig. 9, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 910 and various circuits of memory represented by memory 920, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. Transceiver 900 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 910 is responsible for managing the bus architecture and general processing, and the memory 920 may store data used by the processor 910 in performing operations.

The processor 910 may be a Central Processing Unit (CPU), an Application SPECIFIC INTEGRATED Circuit (ASIC), a Field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA), or a complex Programmable logic device (Complex Programmable Logic Device, CPLD), or the processor may employ a multi-core architecture.

In addition, the specific embodiment of the present application further provides a processor readable storage medium, on which a computer program is stored, where the program when executed by a processor implements the steps of the resource allocation method or the steps of the token bucket related parameter configuration method, and the same technical effects can be achieved, and for avoiding repetition, a detailed description is omitted herein. The readable storage medium may be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic storage (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, nonvolatile storage (NAND FLASH), solid State Disk (SSD)), etc.

It should be noted that the technical solution provided by the embodiment of the present application may be applicable to various systems, especially a 5G system. For example, applicable systems may be global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) universal packet Radio service (GENERAL PACKET Radio service, GPRS), long term evolution (long term evolution, LTE), LTE frequency division duplex (frequency division duplex, FDD), LTE time division duplex (time division duplex, TDD), long term evolution-advanced (long term evolution advanced, LTE-a), universal mobile system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX), 5G New air interface (New Radio, NR) systems, and the like. Terminal devices and network devices are included in these various systems. Core network parts may also be included in the system, such as Evolved packet system (Evolved PACKET SYSTEM, EPS), 5G system (5 GS), etc.

The terminal device according to the embodiment of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem, etc. The names of the terminal devices may also be different in different systems, for example in a 5G system, the terminal devices may be referred to as User Equipment (UE). The wireless terminal device may communicate with one or more Core Networks (CNs) via a radio access Network (Radio Access Network, RAN), which may be mobile terminal devices such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, e.g., portable, pocket, hand-held, computer-built-in or vehicle-mounted mobile devices that exchange voice and/or data with the radio access Network. Such as Personal communication services (Personal Communication Service, PCS) phones, cordless phones, session initiation protocol (Session Initiated Protocol, SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital assistants (Personal DIGITAL ASSISTANT, PDA) and the like. The wireless terminal device may also be referred to as a system, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), remote station (remote station), access point (access point), remote terminal device (remote terminal), access terminal device (ACCESS TERMINAL), user terminal device (user terminal), user agent (user agent), user equipment (user device), and embodiments of the present application are not limited.

The network side device according to the embodiment of the present application may be a base station, where the base station may include a plurality of cells for providing services for a terminal. A base station may also be called an access point or may be a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or other names, depending on the particular application. The network side device may be configured to exchange received air frames with internet protocol (Internet Protocol, IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network side device according to the embodiment of the present application may be a network device (Base Transceiver Station, BTS) in a global system for mobile communications (Global System for Mobile communications, GSM) or code division multiple access (Code Division Multiple Access, CDMA), a network device (NodeB) in a wideband code division multiple access (Wide-band Code Division Multiple Access, WCDMA), an evolved network device (evolutional Node B, eNB or e-NodeB) in a long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), a home evolved base station (Home evolved Node B, heNB), a relay node (relay node), a home base station (femto), a pico base station (pico), etc., which are not limited in the embodiment of the present application. In some network structures, the network devices may include centralized unit (centralized unit, CU) nodes and Distributed Unit (DU) nodes, which may also be geographically separated.

Multiple-input Multiple-output (Multi Input Multi Output, MIMO) transmission can be performed between the network side device and the terminal device by using one or more antennas, and the MIMO transmission can be Single-User MIMO (SU-MIMO) or Multiple-User MIMO (MU-MIMO). The MIMO transmission may be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or may be diversity transmission, precoding transmission, beamforming transmission, or the like, depending on the form and number of the root antenna combinations.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flowchart and/or block of the flowchart illustrations and/or block diagrams, and combinations of flowcharts and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. A method for resource allocation, comprising:

2. The method of claim 1, wherein the token bucket related parameters comprise one or more of:

Prioritized bit rate PBR;

Token bucket size BSD.

3. The method of claim 1, wherein determining token bucket related parameters corresponding to a set of logical channels LCHs comprises one or more of:

4. A method according to claim 3, wherein the determining the token bucket related parameter corresponding to the LCH set according to RRC signaling or broadcast message or pre-configuration information comprises:

5. The method of claim 1, wherein the token bucket related parameters for the LCH set are configured based on a data radio bearer, DRB, or are configured based on an LCH set.

6. The method of claim 5, wherein, in the case where the token bucket related parameters corresponding to the LCH set are configured based on the LCH set,

Or alternatively

7. The method according to claim 1, wherein the method further comprises:

Or alternatively

8. The method of claim 7, wherein the performing token bucket maintenance based on the LCH set according to the token bucket related parameters corresponding to the LCH set comprises:

9. The method of claim 8, wherein updating the number of tokens in the token bucket corresponding to the LCH set according to the token bucket related parameter and the time length corresponding to the LCH set comprises:

10. The method of claim 9, wherein the updating the number of tokens in the token bucket corresponding to the LCH set further comprises:

11. The method of claim 7, wherein the performing token bucket maintenance based on each LCH in the set of LCHs according to the token bucket-related parameter corresponding to the set of LCHs comprises:

12. The method of claim 11, wherein the determining token bucket related parameters for each LCH in the set of LCHs comprises:

Or alternatively

13. The method of claim 12, wherein a mapping relationship between the weighted value corresponding to the LCH and the priority of the LCH is preconfigured;

Or alternatively

14. The method of claim 11, wherein the performing token bucket maintenance based on LCHs according to the token bucket related parameters corresponding to each LCH comprises:

15. The method of claim 1, wherein the performing resource allocation according to the token bucket related parameters corresponding to the LCH set comprises:

16. The method of claim 15, wherein the method further comprises:

17. A method for configuring token bucket related parameters, comprising:

18. The method of claim 17, wherein the sending the token bucket related parameters corresponding to the LCH set to the terminal comprises one of:

19. The method of claim 18, wherein the network side device sends the token bucket related parameters corresponding to the LCH set to the terminal through RRC signaling or a broadcast message or a preconfiguration information, including:

20. The method of claim 17, wherein configuring the token bucket related parameters corresponding to the LCH set based on the LCH set comprises:

Or alternatively

21. The method of claim 17, wherein the method further comprises:

22. A terminal, comprising: memory, transceiver, processor:

23. The terminal of claim 22, wherein the token bucket related parameters include one or more of:

Prioritized bit rate PBR;

Token bucket size BSD.

24. The terminal of claim 22, wherein the processor is configured to read the computer program in the memory and perform one or more of the following:

25. The terminal of claim 24, wherein the processor is configured to read the computer program in the memory and perform the following operations: :

26. The terminal of claim 22, wherein the token bucket related parameters corresponding to the LCH set are configured based on a data radio bearer, DRB, or based on an LCH set.

27. The terminal of claim 26, wherein, in the case where the token bucket related parameters corresponding to the LCH set are configured based on the LCH set,

Or alternatively

28. The terminal of claim 22, wherein the processor is configured to read the computer program in the memory and perform the following operations:

Or alternatively

29. The terminal of claim 28, wherein the processor is configured to read the computer program in the memory and perform the following operations:

30. The terminal of claim 29, wherein the processor is configured to read the computer program in the memory and perform the following:

31. The terminal of claim 30, wherein the processor is configured to read the computer program in the memory and perform the following operations:

32. The terminal of claim 28, wherein the processor is configured to read the computer program in the memory and perform the following operations:

33. The terminal of claim 32, wherein the processor is configured to read the computer program in the memory and perform the following operations:

Or alternatively

34. The terminal of claim 33, wherein a mapping relationship between the weighted value corresponding to the LCH and the priority of the LCH is preconfigured;

Or alternatively

35. The terminal of claim 32, wherein the processor is configured to read the computer program in the memory and perform the following operations:

36. The terminal of claim 22, wherein the processor is configured to read the computer program in the memory and perform the following operations:

37. The terminal of claim 36, wherein the processor is configured to read the computer program in the memory and perform the following operations:

38. A network side device, comprising: memory, transceiver, processor:

39. The network-side device of claim 38, wherein the processor is configured to read the computer program in the memory and perform one of:

40. The network-side device of claim 39, wherein the processor is configured to read the computer program in the memory and perform the following:

41. The network-side device of claim 38, wherein the processor is configured to read the computer program in the memory and perform the following operations:

Or alternatively

42. The network-side device of claim 38, wherein the processor is configured to read the computer program in the memory and perform the following operations:

43. A resource allocation apparatus, comprising:

44. A token bucket-related parameter configuration apparatus, comprising:

45. A processor readable storage medium having stored thereon a computer program, which when executed by a processor performs the steps of the resource allocation method according to any of claims 1 to 16 or the steps of the token bucket related parameter configuration method according to any of claims 17 to 21.