WO2018201833A1

WO2018201833A1 - Uplink resource allocation method and device

Info

Publication number: WO2018201833A1
Application number: PCT/CN2018/081558
Authority: WO
Inventors: 赵亚利; 伯特兰皮埃尔; 李心宇
Original assignee: 电信科学技术研究院有限公司
Priority date: 2017-05-04
Filing date: 2018-04-02
Publication date: 2018-11-08
Also published as: CN106961741A; CN106961741B

Abstract

Provided are an uplink resource allocation method and device. The method comprises: a terminal receiving one or more uplink scheduling grants; and when performing uplink resource allocation for each of the uplink scheduling grants, the terminal allocating, on the basis of a mapping relationship between a bearer or a logical channel and a numerology and/or TTI length, an uplink resource to a bearer or logical channel having data to be transmitted and having a corresponding numerology and/or TTI length equal to a maximum supportable numerology and/or TTI length.

Description

Uplink resource allocation method and device

Cross-reference to related applications

Priority is claimed on Japanese Patent Application No. 20171030894, filed on Jan. 4,,,,,,,,,,,

Technical field

The present disclosure relates to the field of communications technologies, and in particular, to an uplink resource allocation method and apparatus.

Background technique

1) LCP (Logical Channel Prioritization) process of the traditional LTE (Long Term Evolution) system

The LCP of the LTE system is based on a priority parameter priority corresponding to a single RB (Radio Bearer) of the network configuration. The specific implementation process is as follows:

Step 1: Perform the first round of resource allocation in the order of priority order of priority parameters of all logical channels with tokens. The first round of resource allocation is performed based on the PBR (Prioritized Bit Rate) of each logical channel. At the same time, the number of tokens available for each logical channel is updated according to the uplink resource allocation.

Step 2: If there are remaining resources, then perform the second round of resource allocation. The second round of resource allocation is allocated as a data allocation resource other than PBR in the order of priority order of priority parameters of all logical channels having data transmission. Resource allocation allocates resources or exhausts resources of all logical channels with tokens.

2) Introduction of the business supported by NR (New Radio) of the fifth generation (5G) mobile communication system

The 5G NR system mainly supports three types of services:

eMBB (enhanced Mobile Broadband)

mMTC (massive Machine Type Communications)

URLLC (Ultra-Reliable and Low Latency Communications, high reliability and low latency communication)

The delay requirement of the URLLC service is particularly high, and the end-to-end delay is 0.5 ms. However, when the core network is configured with the QoS (Quality of Service) parameter, the priority of the priority parameter in the QoS parameter does not need to consider the delay, and the priority of the URLLC service may be lower than the priority of the eMBB service.

3) Baseband parameters

The baseband parameter (Numerology) is a term of the 3GPP (3rd Generation Partnership Project) RAN (Radio Access Network). The main difference between the different baseband parameters is that the subcarrier spacing supported by the different baseband parameters is different. For example, the subcarrier spacing supported by the 5G NR system includes at least: 15 kHz, 60 kHz, and the baseband parameters corresponding to the two different subcarrier spacings are two independent baseband parameters.

In general, the baseband parameters used by high-speed terminals are different from the baseband parameters used by low-speed terminals; the baseband parameters used by high-frequency terminals and low-frequency terminals are also different. In addition to the speed and frequency associated with the use of different baseband parameters, there is another understanding in the industry that the baseband parameters that can be used by different services may also be different. For example, the baseband parameters used by URLLC and eMBB may be different.

4) TTI (Transmission Time Interval)

In a conventional LTE system, the TTI length is 1 ms. Starting from LTE R14, in order to support delay reduction, different TTI lengths, such as one OFDM (Orthogonal Frequency Division Multiplexing) symbol length, are introduced. Different TTI lengths are used in 5G systems and can be applied to each baseband parameter. That is, different baseband parameters in 5G NR can use different TTI lengths, and the same TTI length can be used, and any baseband parameters can be different at any one time. The length of the TTI used by the terminal can be dynamically changed.

The selection of the length of the TTI is mainly related to the service delay. For example, the URLLC service may have a shorter TTI length, such as the TTI length of one OFDM symbol, because the delay requirement is relatively high.

For a wireless communication system, the priority parameter priority and service delay in the current service QoS parameters are not significant. However, for the 5G and later systems, with the introduction of the URLLC service, if the priority parameter is still independent of the delay, then there may be a problem that the transmission resource of the URLLC service is preempted by the higher priority service, resulting in the URLLC. The latency requirements of the business cannot be met.

Summary of the invention

In view of the above technical problem, the embodiments of the present disclosure provide a solution to the problem that a transmission resource of a low priority but delay sensitive service is preempted by a high priority service.

According to a first aspect of the embodiments of the present disclosure, an uplink resource allocation method is provided, where the method includes:

The terminal receives one or more uplink grants (UL grants);

When the terminal performs uplink resource allocation on each uplink scheduling grant, based on the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or the TTI length that can be supported is equal to the uplink scheduling grant. The corresponding baseband parameter and/or TTI length, and the bearer or logical channel with data to be transmitted allocates uplink resources.

Optionally, when the terminal performs uplink resource allocation on each uplink scheduling grant, based on the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or TTI length that can be supported. After the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the bearer or the logical channel to which the data needs to be transmitted, the method further includes:

If the uplink scheduling grant has a remaining uplink resource, the maximum baseband parameter and/or the TTI length that can be supported is greater than the baseband parameter corresponding to the uplink scheduling grant, based on the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length. / or TTI length, and the bearer or logical channel with data to be transmitted allocates uplink resources.

Optionally, the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length is a network side configuration or a protocol convention.

Optionally, the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length includes:

a mapping relationship between a bearer or logical channel and all baseband parameters and/or TTI lengths used by the bearer or logical channel; or

The mapping relationship between the bearer or logical channel and the maximum baseband parameter and/or TTI length used by the bearer or logical channel.

Optionally, when the terminal performs resource allocation on each uplink scheduling grant, based on a mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or TTI length that can be supported is equal to the The baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the bearer or the logical channel to which the data needs to be transmitted allocate uplink resources, including:

Determining a processing sequence of the multiple uplink scheduling grants, and generating an uplink scheduling grant processing priority queue;

Determining, according to the processing priority of the uplink scheduling grant in the priority scheduling queue, the uplink scheduling grant to be processed, and determining the baseband parameter and/or TTI corresponding to the to-be-processed uplink scheduling grant. length;

According to the correspondence between the bearer or logical channel and the baseband parameter and/or the TTI length, the selected maximum baseband parameter and/or the TTI length is equal to the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant to be processed and the data needs to be transmitted. Carrying or logical channel, sorting the selected bearer or logical channel according to the priority of the bearer or logical channel, and generating a bearer or logical channel priority queue;

Allocating uplink resources to bearers or logical channels in the bearer or logical channel priority queue according to a predetermined resource allocation manner, until all uplink resources corresponding to all uplink scheduling grants in the uplink scheduling authorization processing priority queue are allocated or all bearers are allocated. Or the uplink data is allocated to the data to be transmitted of the logical channel.

Optionally, the processing sequence of the multiple uplink scheduling grants is agreed by a protocol, or configured by a network side, or depends on a terminal implementation.

Optionally, the predetermined resource allocation manner is configured by a network, or is agreed by a protocol, or depends on a terminal implementation.

Optionally, the predetermined resource allocation manner includes:

The first round of PBR resource allocation is performed according to the PBR of each bearer or logical channel in the bearer or logical channel priority queue. If the first round of PBR resource allocation ends with the uplink scheduling grant and the remaining uplink resources, the bearer or bearer is again compared. Each of the logical channel priority queues has remaining data of the bearer or logical channel that needs to be transmitted, and the second round of remaining data resource allocation is performed until all uplink resources corresponding to the uplink scheduling grant are allocated or carried or logical channel priority queues All the bearer or logical channel data to be transmitted are allocated uplink resources; or

All the bearers or logical channels in the bearer or logical channel priority queue are allocated resources according to the amount of data to be transmitted in sequence, until the uplink resources corresponding to the uplink scheduling grant are all allocated or all bearers in the bearer or logical channel priority queue or The uplink data is allocated to the data to be transmitted of the logical channel; or

The first round of PBR resource allocation is performed according to its PBR for each bearer or logical channel in the bearer or logical channel priority queue, wherein the bearer or logical channel that does not need to perform two rounds of resource allocation is determined in the bearer or logical channel priority queue. In the first round of PBR resource allocation, it is necessary to allocate uplink resources for all the data; if the first round of PBR resource allocation ends corresponding to the uplink scheduling grant and the remaining uplink resources, then the bearer or logical channel priority queue is again compared. The remaining data of the bearer or logical channel that has the remaining data to be transmitted is subjected to the second round of remaining data resource allocation until the uplink resources corresponding to the uplink scheduling grant are all allocated or all bearers or logical channels in the bearer or logical channel priority queue are allocated. Uplink resources are allocated to the data to be transmitted; or

The first round of PBR resource allocation is performed according to its PBR for each bearer or logical channel in the bearer or logical channel priority queue, wherein the bearer or logic that does not need to perform two rounds of resource allocation in the bearer or logical channel priority queue is determined. The channel does not need to be allocated uplink resources for the first round of PBR resource allocation; if the first round of PBR resource allocation ends with the uplink scheduling grant and the remaining uplink resources, it is again compared with the bearer or logical channel priority queue. Each of the remaining data of the bearer or logical channel that needs to be transmitted with the remaining data is allocated for the second round of resources until all uplink resources corresponding to the uplink scheduling grant are allocated or all bearers or logical channels in the logical channel priority queue are to be transmitted. The data is allocated uplink resources.

Optionally, if the corresponding uplink scheduling grant has remaining uplink resources, based on the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or the TTI length that can be supported is greater than the uplink scheduling. Authorize the corresponding baseband parameters and/or TTI length, and have bearer or logical channel allocation resources for data transmission, including:

The maximum baseband parameter and/or the TTI length that is selected to be supported is greater than the baseband parameter corresponding to the uplink scheduling grant to be processed, according to the corresponding relationship between the bearer or logical channel and the baseband parameter and/or the TTI length. And/or TTI length, and some or all of the bearer or logical channel with data to be transmitted;

Sorting the selected bearer or logical channel according to the priority of the bearer or logical channel, generating a bearer or logical channel priority queue, and performing uplink resource allocation on the bearer or logical channel in the bearer or logical channel priority queue until All data of the uplink resources are allocated or all data mapped to the bearer or logical channel on the uplink scheduling grant are allocated uplink resources.

Optionally, the method further includes:

The terminal combines the uplink resources allocated to the same bearer or logical channel, and then determines the data amount of the bearer or logical channel, and organizes a Media Access Control (MAC) service data unit for one bearer or logical channel. (Service Data Unit, SDU); or

The terminal allocates an uplink resource for each bearer or logical channel, and generates a MAC SDU for the bearer or logical channel.

According to a second aspect of the embodiments of the present disclosure, an uplink resource allocation apparatus is further provided, where the apparatus includes:

a receiving module, configured to receive one or more uplink scheduling authorizations;

a first resource allocation module, configured to perform a maximum resource base parameter and/or a TTI length based on a mapping relationship between a bearer or a logical channel and a baseband parameter and/or a TTI length when performing uplink resource allocation on each uplink scheduling grant. It is equal to the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the bearer or the logical channel to which the data needs to be transmitted allocates the uplink resource.

Optionally, the device further includes:

a second resource allocation module, configured to: if the corresponding uplink scheduling grant has remaining uplink resources, based on a mapping relationship between the bearer or the logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or the TTI length that can be supported is greater than the The uplink scheduling grant corresponds to the baseband parameter and/or the TTI length, and the bearer or the logical channel to which the data needs to be transmitted allocates the uplink resource.

Optionally, the first resource allocation module includes:

a first determining unit, configured to determine a processing sequence of the multiple uplink scheduling grants, and generate an uplink scheduling grant processing priority queue;

a second determining unit, configured to sequentially select an uplink scheduling grant to be processed according to a processing priority of the uplink scheduling grant in the uplink scheduling authorization processing priority queue from high to low, and determine that the uplink scheduling grant to be processed corresponds to Baseband parameters and/or TTI lengths;

a first queue generating unit, configured to select a supported maximum baseband parameter and/or a TTI length equal to a baseband parameter corresponding to an uplink scheduling grant to be processed, and/or according to a correspondence between a bearer or a logical channel and a baseband parameter and/or a TTI length. A bearer or a logical channel having a TTI length and having data to be transmitted, and sorting the selected bearer or logical channel according to the priority of the bearer or the logical channel to generate a bearer or a logical channel priority queue;

a first resource allocation unit, configured to perform uplink resource allocation on a bearer or a logical channel in the bearer or logical channel priority queue according to a predetermined resource allocation manner, until all uplink scheduling grants in the uplink scheduling authorization processing priority queue are corresponding The uplink resources are all allocated or the data to be transmitted of all bearers or logical channels are allocated uplink resources.

Optionally, the predetermined resource allocation manner includes:

Optionally, the second resource allocation module includes:

The selecting unit is configured to: if the corresponding uplink scheduling grant has remaining uplink resources, according to the correspondence between the bearer or the logical channel and the baseband parameter and/or the TTI length, the maximum supported baseband parameter and/or the TTI length is greater than the uplink scheduling to be processed. Authorize the corresponding baseband parameters and/or TTI length, and have some or all of the bearers or logical channels for which data needs to be transmitted;

a second queue generating unit, configured to sort the selected bearer or logical channel according to priorities of the bearer or the logical channel, and generate a bearer or a logical channel priority queue;

a second resource allocation unit, configured to perform uplink resource allocation on a bearer or a logical channel in the bearer or logical channel priority queue, until all uplink resources are allocated or all mapped to a bearer or logical channel on the uplink scheduling grant All data is allocated uplink resources.

Optionally, the device further includes:

a MAC SDU generating module, configured to combine uplink resources allocated to the same bearer or logical channel, and then determine the amount of data of the bearer or logical channel, and organize one MAC SDU for one bearer or logical channel; or

An uplink resource is allocated for each bearer or logical channel, and a MAC SDU is generated for the bearer or logical channel.

According to a third aspect of the embodiments of the present disclosure, there is also provided a terminal comprising: a memory, a processor, and a program stored on the memory and executable on the processor, the processor implementing the program as described above The steps in the uplink resource allocation method.

According to a fourth aspect of the embodiments of the present disclosure, there is also provided a computer readable storage medium having stored thereon a program, the program being executed by a processor to implement the steps in the uplink resource allocation method as described above.

One technical solution in the foregoing technical solution has the following advantages or advantages: the terminal receives N uplink scheduling grants (N ≥ 1), and performs resource allocation on each uplink scheduling grant based on bearer or logical channel and baseband parameters. / or TTI length mapping, preferentially for the maximum baseband parameters that can be supported and / or the TTI length equal to the baseband parameters and / or TTI length corresponding to the uplink scheduling grant and the bearer or logical channel allocated resources for data transmission; further If the corresponding uplink scheduling grant has remaining resources, the maximum baseband parameter and/or the TTI length that can be supported is greater than the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the data needs to be transmitted. A resource that avoids the problem that transmission resources of low-priority but delay-sensitive traffic are preempted by high-priority services.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the description of the embodiments of the present disclosure will be briefly described. It is obvious that the drawings in the following description are only some embodiments of the present disclosure. Other drawings may also be obtained from those of ordinary skill in the art in view of the drawings.

FIG. 1 is a flowchart of an uplink resource allocation method in an embodiment of the present disclosure;

2 is a specific flowchart of step 102 in FIG. 1;

FIG. 3 is a flowchart of an uplink resource allocation method in another embodiment of the present disclosure;

4 is a specific flowchart of step 303 in FIG. 3;

FIG. 5 is a flowchart of an uplink resource allocation method in still another embodiment of the present disclosure;

6 is a specific flowchart of step 502 in FIG. 5;

FIG. 7 is a block diagram of an uplink resource allocation apparatus in an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.

detailed description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the embodiments of the present invention have been shown in the drawings, the embodiments Rather, these embodiments are provided so that this disclosure will be more fully understood and the scope of the disclosure will be fully disclosed.

Referring to FIG. 1, a flow of an uplink resource allocation method in an embodiment is shown, and the specific steps are as follows:

Step 101: The terminal receives one or more uplink scheduling authorizations.

Upstream scheduling authorization: UL grant.

It should be noted that the specific number of uplink scheduling grants is not limited in this embodiment.

Step 102: When the terminal performs uplink resource allocation on each uplink scheduling grant, based on the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or the TTI length that can be supported is equal to the uplink scheduling. Authorize the corresponding baseband parameters and/or TTI length, and the bearer or logical channel with data to be transmitted allocates uplink resources.

It should be noted that, in this embodiment, bearers and logical channel expressions have the same meaning.

In this embodiment, the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length includes any one or more of the following representations:

The mapping relationship between the bearer and the baseband parameters;

The mapping relationship between the bearer and the TTI length;

The mapping relationship between the bearer and the baseband parameters and the TTI length;

The mapping relationship between logical channels and baseband parameters;

a mapping relationship between a logical channel and a TTI length;

a mapping relationship between logical channels and baseband parameters and TTI lengths;

In this embodiment, the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant includes any one or more of the following representations:

Baseband parameters corresponding to the uplink scheduling grant;

The length of the TTI corresponding to the uplink scheduling grant;

The baseband parameters and TTI lengths corresponding to the uplink scheduling grant.

In this embodiment, the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length may be a network side configuration or a protocol convention.

In this embodiment, the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length specifically refers to:

The mapping relationship between the bearer or logical channel and the maximum baseband parameter and/or TTI length used by the bearer or logical channel is of course not limited thereto.

Referring to FIG. 2, the foregoing step 102 specifically includes:

Step 1021: Determine a processing sequence of multiple uplink scheduling grants, and generate an uplink scheduling authorization processing priority queue.

In this embodiment, the processing sequence of multiple uplink scheduling grants is agreed by the protocol, for example, the processing sequence of multiple uplink scheduling grants or the processing of multiple uplink scheduling grants according to the baseband parameters and/or the length of the TTI from small to large. The order is configured by the network side, or the processing order of multiple uplink scheduling grants depends on the terminal implementation. Of course, it is not limited to this.

Step 1022: Select an uplink scheduling grant to be processed in order of processing priority of the uplink scheduling grant in the priority scheduling queue according to the uplink scheduling authorization, and determine a baseband parameter corresponding to the to-be-processed uplink scheduling grant and/or TTI length;

In this embodiment, the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant to be processed may be determined in a manner related to the related art, and is not repeatedly described herein.

Step 1023: Select a supported maximum baseband parameter and/or a TTI length equal to a baseband parameter and/or a TTI length corresponding to an uplink scheduling grant to be processed, and have data according to a correspondence between a bearer or a logical channel and a baseband parameter and/or a TTI length. A bearer or a logical channel to be transmitted, and the selected bearer or logical channel is sorted according to the priority of the bearer or the logical channel to generate a bearer or a logical channel priority queue;

In this embodiment, optionally, the priority of the bearer or logical channel may be determined by a QoS parameter corresponding to the bearer or the logical channel. Of course, it is not limited to this.

Step 1024: Perform uplink resource allocation on the bearer or logical channel in the bearer or logical channel priority queue according to a predetermined resource allocation manner, until all uplink resources corresponding to all uplink scheduling grants in the uplink scheduling authorization processing priority queue are allocated. Or the uplink data is allocated to all data to be transmitted of the bearer or logical channel.

In this embodiment, after uplink resource allocation is performed on the bearer or logical channel in the bearer or logical channel priority queue according to a predetermined resource allocation manner, the predetermined resources in

steps

1022, 1023, and 1024 are repeatedly performed. The allocation mode performs uplink resource allocation on the bearer or logical channel in the bearer or logical channel priority queue until all uplink resources corresponding to all uplink scheduling grants in the uplink scheduling authorization processing priority queue are allocated or all bearers or logical channels are allocated. Uplink resources are allocated to the data to be transmitted.

In this embodiment, the predetermined resource allocation manner may be configured by the network, or by a protocol, or depending on the terminal.

In this embodiment, the predetermined resource allocation manner includes any one of the following:

Manner 1: The first round of PBR resource allocation is performed according to the PBR of each bearer or logical channel in the bearer or logical channel priority queue. If the first round of PBR resource allocation ends with the uplink scheduling grant and the remaining uplink resources, then again Performing the second round of remaining data resource allocation according to the remaining data of the bearer or logical channel that needs to be transmitted in each of the bearer or logical channel priority queues until all uplink resources corresponding to the uplink scheduling grant are allocated or bearer or logical channel priority The uplink data is allocated to the data to be transmitted of all bearers or logical channels in the level queue;

Manner 2: performing resource allocation according to the amount of data to be transmitted in sequence for each bearer or logical channel in the bearer or logical channel priority queue until all uplink resources corresponding to the uplink scheduling grant are allocated or carried or in the logical channel priority queue All the data to be transmitted of the bearer or logical channel is allocated uplink resources;

Manner 3: The first round of PBR resource allocation is performed according to the PBR of each bearer or logical channel in the bearer or logical channel priority queue, where the bearer that does not need to perform two rounds of resource allocation is determined for the bearer or logical channel priority queue. Or logical channel, in the first round of PBR resource allocation, need to allocate uplink resources for all the data; if the first round of PBR resource allocation ends corresponding to the uplink scheduling grant and the remaining uplink resources, then compare the bearer or logical channel priority again. Each of the remaining data in the queue with the remaining data to be transmitted or the remaining data of the logical channel performs the second round of remaining data resource allocation until all uplink resources corresponding to the uplink scheduling grant are allocated or all bearers in the bearer or logical channel priority queue or The uplink data is allocated to the data to be transmitted of the logical channel;

The above two rounds of resource allocation refer to: the first round of PBR resource allocation and the second round of remaining data resource allocation.

Manner 4: The first round of PBR resource allocation is performed according to the PBR of each bearer or logical channel in the bearer or logical channel priority queue, wherein it is determined that the two rounds of resource allocation are not required for the bearer or logical channel priority queue. For the first round of PBR resource allocation, the uplink resource does not need to be allocated for the first round of PBR resource allocation; if the first round of PBR resource allocation ends with the uplink scheduling grant and the remaining uplink resources, then the bearer or logical channel priority is compared again. Each of the remaining data in the queue that has the remaining data to be transmitted or the remaining data of the logical channel performs the second round of resource allocation until all the uplink resources corresponding to the uplink scheduling grant are allocated or all bearers or logical channels in the bearer or logical channel priority queue are allocated. The uplink data is allocated for the data to be transmitted.

In this embodiment, the terminal organizes the MAC PDU according to the uplink resource allocation result, and there are two ways:

Manner 1: The terminal combines the uplink resources allocated to the same bearer or logical channel, and then determines the data volume of the bearer or logical channel, and organizes one MAC SDU for one bearer or logical channel;

Manner 2: The terminal allocates an uplink resource to each bearer or logical channel, and generates a MAC SDU for the bearer or logical channel.

In this embodiment, the terminal receives N uplink scheduling grants (N ≥ 1), and performs resource allocation on each uplink scheduling grant, based on the mapping relationship between the bearer or logical channel and the baseband parameters and/or the TTI length. Avoiding low priority but relatively sensitive to delay, in order to support the maximum baseband parameter and/or the baseband parameter and/or TTI length corresponding to the uplink scheduling grant and the bearer or logical channel with data to be transmitted. The transmission resource of the service is preempted by high-priority services.

Referring to FIG. 3, a flow of an uplink resource allocation method in another embodiment is shown. The specific steps are as follows:

Step 301: The terminal receives one or more uplink scheduling grants.

Step 302: When the terminal performs uplink resource allocation on each uplink scheduling grant, based on the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or the TTI length that can be supported is equal to the uplink scheduling. Authorize the corresponding baseband parameters and/or TTI length, and the bearer or logical channel with data to be transmitted allocates uplink resources.

It should be noted that the foregoing

steps

301 and 302 are the same as the

steps

101 and 102 shown in FIG. 1 . For the specific implementation process of step 302, refer to the introduction of step 102, which is not described herein.

Step 303: If the uplink scheduling grant has a remaining uplink resource, the maximum baseband parameter and/or the TTI length that can be supported is greater than the uplink scheduling grant corresponding to the mapping between the bearer or logical channel and the baseband parameter and/or the TTI length. The baseband parameters and/or the TTI length, and the bearer or logical channel with data to be transmitted allocates uplink resources.

Referring to FIG. 4, the specific process of step 303 is as follows:

Step 3031: If there is any uplink resource corresponding to the uplink scheduling grant, according to the correspondence between the bearer or the logical channel and the baseband parameter and/or the TTI length, the maximum supported baseband parameter and/or the TTI length is greater than the uplink scheduling grant to be processed. Baseband parameters and/or TTI lengths and some or all of the bearer or logical channels for which data needs to be transmitted;

Step 3032: Sort the selected bearer or logical channel according to the priority of the bearer or the logical channel, generate a bearer or logical channel priority queue, and perform uplink resources on the bearer or logical channel in the bearer or logical channel priority queue. Allocating, until the uplink resources are all allocated or all data mapped to the bearer or logical channel on the uplink scheduling grant are allocated uplink resources.

In this embodiment, the terminal receives N uplink scheduling grants (N ≥ 1), and performs resource allocation on each uplink scheduling grant, based on the mapping relationship between the bearer or logical channel and the baseband parameters and/or the TTI length. Allocating resources for a maximum baseband parameter and/or a baseband parameter and/or a TTI length corresponding to the uplink scheduling grant and having a data to be transmitted or a logical channel; if there is remaining resources corresponding to the uplink scheduling grant, Low priority but delay comparison can be avoided for the maximum baseband parameters that can be supported and/or the bearer or logical channel allocation resources with the TTI length corresponding to the base scheduling parameters and/or TTI length corresponding to the uplink scheduling grant and having data to be transmitted. The transmission resources of sensitive services are preempted by high-priority services.

Referring to FIG. 5, the flow of the uplink resource allocation on the terminal side is shown, and the specific steps are as follows:

Step 501: Determine an uplink scheduling authorization processing priority queue.

Specifically, the terminal receives the N uplink scheduling grants, determines the processing sequence of the N uplink scheduling grants, and generates an uplink scheduling grant processing priority queue, where N is greater than or equal to 1.

Optionally, the processing sequence of the N uplink scheduling grants may be a protocol, for example, the sequence of the N uplink scheduling grants may be configured by the network side according to the baseband parameters and/or the length of the TTI from small to large.

Step 502: Process the priority queue according to the uplink scheduling authorization, select an uplink scheduling grant at the head of the queue, and perform uplink resource allocation for the uplink scheduling grant.

Optionally, performing uplink resource allocation on the uplink scheduling grant according to the manner shown in FIG. 6:

Step 5021: Select an uplink scheduling grant to process the first uplink scheduling grant to be processed in the priority queue, and determine a baseband parameter and/or a TTI length corresponding to the uplink scheduling grant.

Step 5022: Select a supported maximum baseband parameter and/or a TTI length equal to a baseband parameter and/or a TTI length corresponding to an uplink scheduling grant to be processed according to a correspondence between a bearer or a logical channel and a baseband parameter and/or a TTI length, and have data. The bearer that needs to be transmitted is then sorted in descending order according to the priority of the bearer or logical channel according to the priority of the bearer or logical channel to generate a bearer or logical channel priority queue.

Step 5023: Perform uplink resource allocation on the bearer or logical channel in the bearer or logical channel priority queue.

There are several ways to do this:

Manner 1: The first round of resource allocation is performed according to its PBR for each bearer or logical channel in the bearer or logical channel priority queue. If there are remaining resources at the end of the first round of resource allocation, the second round of resource allocation is performed again against the remaining data of the bearer or logical channel in the bearer or logical channel priority queue that needs to be transmitted, until the resources are exhausted or The resources to be transmitted of all bearers in the bearer priority queue are allocated resources.

Manner 2: The resources are allocated according to the amount of data to be transmitted in sequence for each bearer or logical channel in the bearer or logical channel priority queue. Resources are allocated until the resource is exhausted or the data to be transmitted of all bearers or logical channels in the bearer or logical channel priority queue.

Manner 3: The first round of resource allocation is performed according to its PBR for each bearer or logical channel in the bearer or logical channel priority queue. For the bearer or logical channel in the bearer or logical channel priority queue that does not need to perform two rounds of resource allocation, in the first round of resource allocation, resources need to be allocated for all the data. If there are remaining resources at the end of the first round of resource allocation, the second round of resource allocation is performed again against the remaining data of the bearer or logical channel in the bearer or logical channel priority queue that needs to be transmitted, until the resources are exhausted or The data to be transmitted of all bearers or logical channels in the bearer or logical channel priority queue are allocated resources.

Optionally, the bearer or logical channel configured in the bearer or logical channel priority queue that does not need to perform two rounds of resource allocation is transmitted in the first round of resource allocation.

Manner 4: The first round of resource allocation is performed according to the PBR of each bearer or logical channel in the bearer or logical channel priority queue. For the bearer or logical channel in the bearer or logical channel priority queue that does not need to perform two rounds of resource allocation, no resources need to be allocated for the first round of resource allocation. If there are remaining resources at the end of the first round of resource allocation, the second round of resource allocation is performed again against the remaining data of the bearer or logical channel in the bearer or logical channel priority queue that needs to be transmitted, until the resources are exhausted or The data to be transmitted of all bearers or logical channels in the bearer or logical channel priority queue are allocated resources.

For bearers or logical channels in the bearer or logical channel priority queue that do not need to perform two rounds of resource allocation, all data is allocated resources in the second round of resource allocation.

Step 5024: If the uplink scheduling grant has remaining resources after the resource allocation is completed in step 5023, the maximum supported baseband parameter and/or TTI length is greater than the corresponding relationship between the bearer or logical channel and the baseband parameter and/or the TTI length. The baseband parameters and/or TTI lengths corresponding to the uplink scheduling grant to be processed and some or all of the bearers or logical channels for which data needs to be transmitted. Then, the selected bearer or logical channel is sorted in descending order according to the priority of the bearer or logical channel, and a bearer or logical channel priority queue is generated, and steps 5023 and 5024 are continued until the uplink scheduling authorization resource is exhausted. Or all data that can be mapped to a bearer or logical channel on the uplink scheduling grant is allocated resources.

Step 503: Update the uplink scheduling grant priority processing queue, delete the already processed uplink scheduling grant, and then repeat step 502 until all uplink scheduling grant resources are exhausted or all bearers or logical channels are in their corresponding baseband parameters/ The uplink resource is allocated on the uplink scheduling grant corresponding to the TTI.

Manner 1: Combine the resources allocated to the same bearer, determine the amount of data that can be carried, and organize a MAC SDU for one bearer.

Manner 2: Each time a resource is allocated to one bearer or logical channel (for example, resource allocation for PBR or resource allocation for remaining data), a MAC SDU is generated for the bearer.

In this embodiment, the terminal receives N uplink scheduling grants (N ≥ 1), and when performing resource allocation on each uplink scheduling grant, based on the mapping relationship between the bearer and the baseband parameter/TTI length, the priority is the maximum that can be supported. The baseband parameter/TTI length is equal to the baseband parameter/TTI length corresponding to the uplink scheduling grant and there is a bearer allocation bearer or logical channel allocation resource for which data needs to be transmitted; if there are remaining resources, the maximum baseband parameter/TTI length that can be supported is greater than The uplink scheduling grant corresponds to the baseband parameter/TTI length and the data needs to be transmitted by the bearer allocation bearer or the logical channel allocation resource, which can prevent the transmission resource of the low priority but relatively delay sensitive service from being preempted by the high priority service. The problem.

Based on the same inventive concept, an uplink resource allocation apparatus is also provided in the embodiment of the present disclosure. The uplink resource allocation apparatus is similar to the uplink resource allocation method in the embodiments of the present disclosure. The implementation of the dispensing device can be seen in the implementation of the method, and the repetitions are not described.

Referring to FIG. 7, a structure of an uplink resource allocation apparatus is shown. The apparatus 700 includes:

The receiving module 701 is configured to receive one or more uplink scheduling grants;

The first resource allocation module 702 is configured to: when the uplink resource allocation is performed on each uplink scheduling grant, based on the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or TTI that can be supported. The length is equal to the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the bearer or the logical channel to which the data needs to be transmitted allocates the uplink resource.

In this embodiment, optionally, with continued reference to FIG. 7, the apparatus 700 further includes:

The second resource allocation module 703 is configured to: if the corresponding uplink scheduling grant has remaining uplink resources, based on the mapping relationship between the bearer or the logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or the TTI length that can be supported is greater than The uplink scheduling grant corresponds to a baseband parameter and/or a TTI length, and a bearer or a logical channel to which the data needs to be transmitted allocates an uplink resource.

In this embodiment, optionally, the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length is a network side configuration or a protocol convention.

In this embodiment, optionally, the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length includes:

In this embodiment, optionally, with continued reference to FIG. 7, the first resource allocation module 702 includes:

The first determining unit 7021 is configured to determine a processing sequence of the multiple uplink scheduling grants, and generate an uplink scheduling authorization processing priority queue.

The second determining unit 7022 is configured to sequentially select the uplink scheduling grant to be processed according to the processing priority of the uplink scheduling grant in the uplink scheduling authorization processing priority queue from high to low, and determine the uplink scheduling grant to be processed. Corresponding baseband parameters and/or TTI lengths;

The first queue generating unit 7023 is configured to select a supported maximum baseband parameter and/or a TTI length equal to a baseband parameter corresponding to the uplink scheduling grant to be processed according to the correspondence between the bearer or logical channel and the baseband parameter and/or the TTI length. Or a bearer or a logical channel having a TTI length and having data to be transmitted, and sorting the selected bearer or logical channel according to the priority of the bearer or the logical channel to generate a bearer or a logical channel priority queue;

The first resource allocation unit 7024 is configured to perform uplink resource allocation on the bearer or logical channel in the bearer or logical channel priority queue according to a predetermined resource allocation manner, until all uplink scheduling grants in the uplink scheduling authorization processing priority queue correspond to Uplink resources are all allocated or all bearer or logical channel data to be transmitted are allocated uplink resources.

In this embodiment, optionally, the processing sequence of the multiple uplink scheduling grants is agreed by a protocol, or configured by a network side, or implemented by a terminal.

In this embodiment, optionally, the predetermined resource allocation manner is configured by a network, or is agreed by a protocol, or is implemented by a terminal.

In this embodiment, optionally, the predetermined resource allocation manner includes:

In this embodiment, optionally, referring to FIG. 7, the second resource allocation module 703 includes:

The selecting unit 7031 is configured to: if the corresponding uplink scheduling grant has remaining uplink resources, according to the correspondence between the bearer or the logical channel and the baseband parameter and/or the TTI length, the maximum supported baseband parameter and/or the TTI length is greater than the uplink to be processed. Scheduling the corresponding baseband parameters and/or TTI lengths, and having some or all of the bearers or logical channels for which data needs to be transmitted;

The second queue generating unit 7032 is configured to sort the selected bearer or logical channel according to the priority of the bearer or the logical channel, and generate a bearer or a logical channel priority queue.

a second resource allocation unit 7033, configured to perform uplink resource allocation on a bearer or a logical channel in the bearer or logical channel priority queue, until all uplink resources are allocated or all bearers or logical channels mapped to the uplink scheduling grant All data is allocated uplink resources.

a MAC SDU generating module 704, configured to combine uplink resources allocated to the same bearer or logical channel, determine data volume of the bearer or logical channel, and organize one MAC SDU for one bearer or logical channel; or

Each time an uplink resource is allocated to a bearer or logical channel, a MAC SDU is generated for the bearer or logical channel.

The embodiment of the present disclosure further provides a terminal, including: a memory, a processor, and a computer program stored on the memory and operable on the processor, where the processor executes the program as shown in FIG. 1 to FIG. 6 The steps in the illustrated uplink resource allocation method.

Referring to FIG. 8, there is shown a structure of a terminal including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor executing the program to implement the following steps: receiving One or more uplink scheduling grants; the maximum baseband parameter and/or TTI length that can be supported based on the mapping relationship between bearer or logical channel and baseband parameters and/or TTI length when performing uplink resource allocation on each uplink scheduling grant It is equal to the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the bearer or the logical channel to which the data needs to be transmitted allocates the uplink resource.

In FIG. 8, the bus architecture represented by bus 800 can include any number of interconnected buses and bridges, and bus 800 will include various circuits of memory represented by one or more processors and memory 804 represented by general purpose processor 801. Linked together. The bus 800 can also link various other circuits such as peripherals, voltage regulators, and power management circuits. Bus interface 803 provides an interface between bus 800 and transceiver 802. Transceiver 802 can be an element or a plurality of elements, such as multiple receivers and transmitters, providing means for communicating with various other devices on a transmission medium. For example, transceiver 802 receives external data from other devices. The transceiver 802 is configured to send the processed data of the processor 801 to other devices. Depending on the nature of the computing system, a user interface can also be provided, such as a keypad, display, speaker, microphone, joystick.

The processor 801 is responsible for managing the bus 800 and the usual processing, running the general purpose operating system as described above. The memory 704 can be used to store data used by the processor 801 when performing operations.

Optionally, the processor 801 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex). Programmable Logic Device, Complex Programmable Logic Device).

Optionally, the processor 801 is further configured to: if the corresponding uplink scheduling grant has remaining uplink resources, based on a mapping relationship between the bearer or the logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or the TTI that can be supported. The length is greater than the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the bearer or the logical channel to which the data needs to be transmitted allocates the uplink resource.

Optionally, the processor 801 is further configured to: determine a processing sequence of the multiple uplink scheduling grants, generate an uplink scheduling grant processing priority queue, and process a processing priority of an uplink scheduling grant in the priority queue according to the uplink scheduling grant. Selecting an uplink scheduling grant to be processed in order from high to low, and determining a baseband parameter and/or a TTI length corresponding to the to-be-processed uplink scheduling grant; according to a correspondence between a bearer or a logical channel and a baseband parameter and/or a TTI length And selecting a supported maximum baseband parameter and/or a TTI length equal to a baseband parameter and/or a TTI length corresponding to the uplink scheduling grant to be processed and having a data bearer or a logical channel to be transmitted, and selecting the bearer or logical channel according to the bearer or The priority of the logical channel is sorted to generate a bearer or logical channel priority queue; the uplink resource allocation is performed on the bearer or logical channel in the bearer or logical channel priority queue according to a predetermined resource allocation manner, until the uplink scheduling authorization process is prioritized All uplink resources corresponding to all uplink scheduling grants in the level queue Transmitting data to be allocated or all the bearers or logical channels are allocated uplink resource.

Optionally, the predetermined resource allocation manner includes:

Optionally, the processor 801 is further configured to: if the corresponding uplink scheduling grant has remaining uplink resources, select a supported maximum baseband parameter and/or a TTI length according to a correspondence between the bearer or the logical channel and the baseband parameter and/or the TTI length. The baseband parameter and/or the TTI length corresponding to the uplink scheduling grant to be processed, and some or all of the bearer or logical channel that the data needs to be transmitted; sorting the selected bearer or logical channel according to the priority of the bearer or the logical channel, Generating a bearer or logical channel priority queue; performing uplink resource allocation on the bearer or logical channel in the bearer or logical channel priority queue until all uplink resources are allocated or all bearers or logical channels mapped to the uplink scheduling grant All data is allocated uplink resources.

Optionally, the processor 801 is further configured to: combine the uplink resources allocated to the same bearer or logical channel, determine the data volume of the bearer or the logical channel, and organize one MAC SDU for one bearer or logical channel; or Each time a bearer or logical channel allocates an uplink resource, a MAC SDU is generated for the bearer or logical channel.

The embodiment of the present disclosure further provides a computer readable storage medium having stored thereon a computer program, the program being executed by the processor to implement the steps in the uplink resource allocation method as shown in FIGS. 1 to 6.

It is to be understood that the phrase "one embodiment" or "an embodiment" or "an" or "an" Thus, "in one embodiment" or "in an embodiment" or "an" In addition, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present disclosure, it should be understood that the size of the serial numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present disclosure. The implementation process constitutes any limitation.

Additionally, the terms "system" and "network" are used interchangeably herein.

It should be understood that the term "and/or" herein is merely an association relationship describing an associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and A and B exist simultaneously. There are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

In the embodiments provided herein, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined from A. However, it should also be understood that determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.

In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

In addition, each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

The above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium. The above software functional unit is stored in a storage medium and includes a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network side device, etc.) to perform part of the steps of the transceiving method of the various embodiments of the present disclosure. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

The above is a preferred embodiment of the present disclosure, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present disclosure. Within the scope of protection of the present disclosure.

Claims

An uplink resource allocation method includes:

The terminal receives one or more uplink scheduling grants (UL grants);

When the terminal performs the uplink resource allocation on each uplink scheduling grant, the mapping relationship between the bearer or the logical channel and the numerology and/or the transmission time interval (TTI) length is the maximum that can be supported. The baseband parameter and/or the TTI length is equal to the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the bearer or logical channel with the data to be transmitted allocates the uplink resource.
The method according to claim 1, wherein when the terminal performs uplink resource allocation on each uplink scheduling grant, based on a mapping relationship between a bearer or a logical channel and a baseband parameter and/or a TTI length, the maximum supported After the baseband parameter and/or the TTI length is equal to the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the data is to be transmitted, the bearer or the logical channel allocates the uplink resource, the method further includes:

If the uplink scheduling grant has a remaining uplink resource, the maximum baseband parameter and/or the TTI length that can be supported is greater than the baseband parameter corresponding to the uplink scheduling grant, based on the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length. / or TTI length, and the bearer or logical channel with data to be transmitted allocates uplink resources.
The method according to claim 1 or 2, wherein the mapping relationship between the bearer or logical channel and baseband parameters and/or TTI length is a network side configuration or a protocol convention.
The method of claim 3, wherein the mapping of the bearer or logical channel to baseband parameters and/or TTI length comprises:

a mapping relationship between a bearer or logical channel and all baseband parameters and/or TTI lengths used by the bearer or logical channel; or

The mapping relationship between the bearer or logical channel and the maximum baseband parameter and/or TTI length used by the bearer or logical channel.
The method according to claim 1, wherein when the terminal performs resource allocation on each uplink scheduling grant, the maximum baseband parameter that can be supported is based on a mapping relationship between a bearer or a logical channel and a baseband parameter and/or a TTI length. And/or the TTI length is equal to the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the bearer or the logical channel to which the data needs to be transmitted allocates uplink resources, including:

Determining a processing sequence of the multiple uplink scheduling grants, and generating an uplink scheduling grant processing priority queue;

Determining, according to the processing priority of the uplink scheduling grant in the priority scheduling queue, the uplink scheduling grant to be processed, and determining the baseband parameter and/or TTI corresponding to the to-be-processed uplink scheduling grant. length;

According to the correspondence between the bearer or logical channel and the baseband parameter and/or the TTI length, the selected maximum baseband parameter and/or the TTI length is equal to the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant to be processed and the data needs to be transmitted. Carrying or logical channel, sorting the selected bearer or logical channel according to the priority of the bearer or logical channel, and generating a bearer or logical channel priority queue;

Allocating uplink resources to bearers or logical channels in the bearer or logical channel priority queue according to a predetermined resource allocation manner, until all uplink resources corresponding to all uplink scheduling grants in the uplink scheduling authorization processing priority queue are allocated or all bearers are allocated. Or the uplink data is allocated to the data to be transmitted of the logical channel.
The method according to claim 5, wherein the processing order of the plurality of uplink scheduling grants is agreed by a protocol, or configured by a network side, or depends on a terminal implementation; or

The predetermined resource allocation manner is configured by the network, or by a protocol, or depending on the terminal.
The method of claim 5 wherein said predetermined method of resource allocation comprises:

The first round of PBR resource allocation is performed according to the prioritized bit rate (PBR) of each bearer or logical channel in the bearer or logical channel priority queue; if the first round of PBR resource allocation ends corresponding to the uplink scheduling grant If there is any remaining uplink resource, the second round of remaining data resource allocation is performed again with respect to the remaining data of the bearer or logical channel that needs to be transmitted in the bearer or logical channel priority queue, until the uplink resources corresponding to the uplink scheduling grant are all Allocating or carrying or carrying data of all bearers or logical channels in the logical channel priority queue are allocated uplink resources; or

All the bearers or logical channels in the bearer or logical channel priority queue are allocated resources according to the amount of data to be transmitted in sequence, until the uplink resources corresponding to the uplink scheduling grant are all allocated or all bearers in the bearer or logical channel priority queue or The uplink data is allocated to the data to be transmitted of the logical channel; or

The first round of PBR resource allocation is performed according to its PBR for each bearer or logical channel in the bearer or logical channel priority queue, wherein the bearer or logical channel that does not need to perform two rounds of resource allocation is determined in the bearer or logical channel priority queue. In the first round of PBR resource allocation, it is necessary to allocate uplink resources for all the data; if the first round of PBR resource allocation ends corresponding to the uplink scheduling grant and the remaining uplink resources, then the bearer or logical channel priority queue is again compared. The remaining data of the bearer or logical channel that has the remaining data to be transmitted is subjected to the second round of remaining data resource allocation until the uplink resources corresponding to the uplink scheduling grant are all allocated or all bearers or logical channels in the bearer or logical channel priority queue are allocated. Uplink resources are allocated to the data to be transmitted; or

The first round of PBR resource allocation is performed according to its PBR for each bearer or logical channel in the bearer or logical channel priority queue, wherein the bearer or logic that does not need to perform two rounds of resource allocation in the bearer or logical channel priority queue is determined. The channel does not need to be allocated uplink resources for the first round of PBR resource allocation; if the first round of PBR resource allocation ends with the uplink scheduling grant and the remaining uplink resources, it is again compared with the bearer or logical channel priority queue. Each of the remaining data of the bearer or logical channel that needs to be transmitted with the remaining data is allocated for the second round of resources until all uplink resources corresponding to the uplink scheduling grant are allocated or all bearers or logical channels in the logical channel priority queue are to be transmitted. The data is allocated uplink resources.
The method according to claim 2, wherein if the corresponding uplink scheduling grant has remaining uplink resources, based on a mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter that can be supported and/or Or the TTI length is greater than the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the bearer or logical channel allocated resources for which the data needs to be transmitted, including:

The maximum baseband parameter and/or the TTI length that is selected to be supported is greater than the baseband parameter corresponding to the uplink scheduling grant to be processed, according to the corresponding relationship between the bearer or logical channel and the baseband parameter and/or the TTI length. And/or TTI length, and some or all of the bearer or logical channel with data to be transmitted;

Sorting the selected bearer or logical channel according to the priority of the bearer or logical channel, generating a bearer or logical channel priority queue, and performing uplink resource allocation on the bearer or logical channel in the bearer or logical channel priority queue until All data of the uplink resources are allocated or all data mapped to the bearer or logical channel on the uplink scheduling grant are allocated uplink resources.
The method of claim 1 further comprising:

The terminal combines the uplink resources allocated to the same bearer or logical channel, and then determines the data amount of the bearer or logical channel, and organizes a Media Access Control (MAC) service data unit for one bearer or logical channel. (Service Data Unit, SDU); or

The terminal allocates an uplink resource for each bearer or logical channel, and generates a MAC SDU for the bearer or logical channel.
An uplink resource allocation device includes:

a receiving module, configured to receive one or more uplink scheduling authorizations;

a first resource allocation module, configured to perform a maximum resource base parameter and/or a TTI length based on a mapping relationship between a bearer or a logical channel and a baseband parameter and/or a TTI length when performing uplink resource allocation on each uplink scheduling grant. It is equal to the baseband parameter and/or the TTI length corresponding to the uplink scheduling grant, and the bearer or the logical channel to which the data needs to be transmitted allocates the uplink resource.
The apparatus of claim 10 further comprising:

a second resource allocation module, configured to: if the corresponding uplink scheduling grant has remaining uplink resources, based on a mapping relationship between the bearer or the logical channel and the baseband parameter and/or the TTI length, the maximum baseband parameter and/or the TTI length that can be supported is greater than the The uplink scheduling grant corresponds to the baseband parameter and/or the TTI length, and the bearer or the logical channel to which the data needs to be transmitted allocates the uplink resource.
The apparatus of claim 10 or 11, wherein the mapping of the bearer or logical channel to baseband parameters and/or TTI length is a network side configuration or a protocol convention.
The apparatus of claim 12, wherein the mapping relationship between the bearer or logical channel and baseband parameters and/or TTI length comprises:

a mapping relationship between a bearer or logical channel and all baseband parameters and/or TTI lengths used by the bearer or logical channel; or

The mapping relationship between the bearer or logical channel and the maximum baseband parameter and/or TTI length used by the bearer or logical channel.
The apparatus of claim 10, wherein the first resource allocation module comprises:

a first determining unit, configured to determine a processing sequence of the multiple uplink scheduling grants, and generate an uplink scheduling authorization processing priority queue;

a second determining unit, configured to sequentially select an uplink scheduling grant to be processed according to a processing priority of the uplink scheduling grant in the uplink scheduling authorization processing priority queue from high to low, and determine that the uplink scheduling grant to be processed corresponds to Baseband parameters and/or TTI lengths;

a first queue generating unit, configured to select a supported maximum baseband parameter and/or a TTI length equal to a baseband parameter corresponding to an uplink scheduling grant to be processed, and/or according to a correspondence between a bearer or a logical channel and a baseband parameter and/or a TTI length. A bearer or a logical channel having a TTI length and having data to be transmitted, and sorting the selected bearer or logical channel according to the priority of the bearer or the logical channel to generate a bearer or a logical channel priority queue;

a first resource allocation unit, configured to perform uplink resource allocation on a bearer or a logical channel in the bearer or logical channel priority queue according to a predetermined resource allocation manner, until all uplink scheduling grants in the uplink scheduling authorization processing priority queue are corresponding The uplink resources are all allocated or the data to be transmitted of all bearers or logical channels are allocated uplink resources.
The apparatus according to claim 14, wherein the processing order of the plurality of uplink scheduling grants is agreed by a protocol, or configured by a network side, or depends on a terminal implementation; or

The predetermined resource allocation manner is configured by the network, or by a protocol, or depending on the terminal.
The apparatus of claim 14, wherein the predetermined resource allocation manner comprises:

The first round of PBR resource allocation is performed according to the PBR of each bearer or logical channel in the bearer or logical channel priority queue. If the first round of PBR resource allocation ends with the uplink scheduling grant and the remaining uplink resources, the bearer or bearer is again compared. Each of the logical channel priority queues has remaining data of the bearer or logical channel that needs to be transmitted, and the second round of remaining data resource allocation is performed until all uplink resources corresponding to the uplink scheduling grant are allocated or carried or logical channel priority queues All the bearer or logical channel data to be transmitted are allocated uplink resources; or

All the bearers or logical channels in the bearer or logical channel priority queue are allocated resources according to the amount of data to be transmitted in sequence, until the uplink resources corresponding to the uplink scheduling grant are all allocated or all bearers in the bearer or logical channel priority queue or The uplink data is allocated to the data to be transmitted of the logical channel; or

The first round of PBR resource allocation is performed according to its PBR for each bearer or logical channel in the bearer or logical channel priority queue, wherein the bearer or logical channel that does not need to perform two rounds of resource allocation is determined for the bearer or logical channel priority queue. In the first round of PBR resource allocation, it is necessary to allocate uplink resources for all the data; if the first round of PBR resource allocation ends corresponding to the uplink scheduling grant and the remaining uplink resources, then the bearer or logical channel priority queue is again compared. The remaining data of the bearer or logical channel that has the remaining data to be transmitted is subjected to the second round of remaining data resource allocation until the uplink resources corresponding to the uplink scheduling grant are all allocated or all bearers or logical channels in the bearer or logical channel priority queue are allocated. Uplink resources are allocated to the data to be transmitted; or

The first round of PBR resource allocation is performed according to its PBR for each bearer or logical channel in the bearer or logical channel priority queue, wherein the bearer or logic that does not need to perform two rounds of resource allocation in the bearer or logical channel priority queue is determined. The channel does not need to be allocated uplink resources for the first round of PBR resource allocation; if the first round of PBR resource allocation ends with the uplink scheduling grant and the remaining uplink resources, it is again compared with the bearer or logical channel priority queue. Each of the remaining data of the bearer or logical channel that needs to be transmitted with the remaining data is allocated for the second round of resources until all uplink resources corresponding to the uplink scheduling grant are allocated or all bearers or logical channels in the logical channel priority queue are to be transmitted. The data is allocated uplink resources.
The apparatus of claim 11, wherein the second resource allocation module comprises:

The selecting unit is configured to: if the corresponding uplink scheduling grant has remaining uplink resources, according to the correspondence between the bearer or the logical channel and the baseband parameter and/or the TTI length, the maximum supported baseband parameter and/or the TTI length is greater than the uplink scheduling to be processed. Authorize the corresponding baseband parameters and/or TTI length, and have some or all of the bearers or logical channels for which data needs to be transmitted;

a second queue generating unit, configured to sort the selected bearer or logical channel according to priorities of the bearer or the logical channel, and generate a bearer or a logical channel priority queue;

a second resource allocation unit, configured to perform uplink resource allocation on a bearer or a logical channel in the bearer or logical channel priority queue, until all uplink resources are allocated or all mapped to a bearer or logical channel on the uplink scheduling grant All data is allocated uplink resources.
The apparatus of claim 10 further comprising:

a MAC SDU generating module, configured to combine uplink resources allocated to the same bearer or logical channel, and then determine the amount of data of the bearer or logical channel, and organize one MAC SDU for one bearer or logical channel; or

Each time an uplink resource is allocated to a bearer or logical channel, a MAC SDU is generated for the bearer or logical channel.
A terminal, comprising: a memory, a processor, and a program stored on the memory and operable on the processor, the processor implementing the program, implementing the uplink resource according to any one of claims 1 to 9. The steps in the assignment method.
A computer readable storage medium having stored thereon a program, wherein the program is executed by a processor to implement the steps of the uplink resource allocation method according to any one of claims 1 to 9.