WO2018201833A1 - 一种上行资源分配方法和装置 - Google Patents

一种上行资源分配方法和装置 Download PDF

Info

Publication number
WO2018201833A1
WO2018201833A1 PCT/CN2018/081558 CN2018081558W WO2018201833A1 WO 2018201833 A1 WO2018201833 A1 WO 2018201833A1 CN 2018081558 W CN2018081558 W CN 2018081558W WO 2018201833 A1 WO2018201833 A1 WO 2018201833A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
logical channel
uplink
resource allocation
uplink scheduling
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/081558
Other languages
English (en)
French (fr)
Inventor
赵亚利
伯特兰皮埃尔
李心宇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Academy of Telecommunications Technology CATT
Original Assignee
China Academy of Telecommunications Technology CATT
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Academy of Telecommunications Technology CATT filed Critical China Academy of Telecommunications Technology CATT
Publication of WO2018201833A1 publication Critical patent/WO2018201833A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to an uplink resource allocation method and apparatus.
  • LCP Logical Channel Prioritization
  • 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.
  • PBR Primary Bit Rate
  • 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.
  • the 5G NR system mainly supports three types of services:
  • eMBB enhanced Mobile Broadband
  • the delay requirement of the URLLC service is particularly high, and the end-to-end delay is 0.5 ms.
  • 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.
  • 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.
  • 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.
  • 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.
  • the baseband parameters that can be used by different services may also be different.
  • the baseband parameters used by URLLC and eMBB may be different.
  • the TTI length is 1 ms.
  • 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.
  • 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.
  • the priority parameter priority and service delay in the current service QoS parameters are not significant.
  • 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.
  • 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.
  • an uplink resource allocation method includes:
  • the terminal receives one or more uplink grants (UL grants);
  • the terminal 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.
  • the terminal 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.
  • the method further includes:
  • 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 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.
  • mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length includes:
  • 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 a 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 terminal 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:
  • 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.
  • Uplink resources 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 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.
  • the predetermined resource allocation manner is configured by a network, or is agreed by a protocol, or depends on a terminal implementation.
  • 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.
  • 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 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;
  • 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.
  • MAC Media Access Control
  • 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 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.
  • 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.
  • 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.
  • mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length includes:
  • 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 a 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 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 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 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.
  • the predetermined resource allocation manner is configured by a network, or is agreed by a protocol, or depends on a terminal implementation.
  • 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.
  • 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 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.
  • 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;
  • An uplink resource is allocated for each bearer or logical channel, and 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 executable on the processor, the processor implementing the program as described above The steps in the uplink resource allocation method.
  • 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.
  • 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.
  • FIG. 1 is a flowchart of an uplink resource allocation method in an embodiment of the present disclosure
  • step 102 in FIG. 1 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.
  • step 303 in FIG. 3 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.
  • step 502 in FIG. 5 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.
  • 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.
  • 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.
  • bearers and logical channel expressions have the same meaning.
  • 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 baseband parameter and/or the TTI length corresponding to the uplink scheduling grant includes any one or more of the following representations:
  • the baseband parameters and TTI lengths corresponding to the uplink scheduling grant are the baseband parameters and TTI lengths corresponding to the uplink scheduling grant.
  • 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.
  • mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length specifically refers to:
  • 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.
  • step 102 specifically includes:
  • Step 1021 Determine a processing sequence of multiple uplink scheduling grants, and generate an uplink scheduling authorization processing priority queue.
  • 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;
  • 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;
  • the priority of the bearer or logical channel may be determined by a QoS parameter corresponding to the bearer or the logical channel.
  • a QoS parameter corresponding to the bearer or the logical channel.
  • 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.
  • 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.
  • the predetermined resource allocation manner may be configured by the network, or by a protocol, or depending on the terminal.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • steps 301 and 302 are the same as the steps 101 and 102 shown in FIG. 1 .
  • steps 301 and 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.
  • step 303 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.
  • 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.
  • 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.
  • 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.
  • Step 501 Determine an uplink scheduling authorization processing priority queue.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the terminal organizes the MAC PDU according to the uplink resource allocation result, and there are two ways:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length includes:
  • 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 a 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 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.
  • 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.
  • 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.
  • the predetermined resource allocation manner is configured by a network, or is agreed by a protocol, or is implemented by a terminal.
  • 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.
  • 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 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.
  • the apparatus 700 further includes:
  • 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;
  • 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
  • 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 including: a memory, a processor, and a computer program stored on the memory and operable on the processor
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • mapping relationship between the bearer or logical channel and the baseband parameter and/or the TTI length includes:
  • 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 a 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 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
  • 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.
  • the predetermined resource allocation manner is configured by a network, or is agreed by a protocol, or depends on a terminal implementation.
  • 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.
  • 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 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 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.
  • system and “network” are used interchangeably herein.
  • B corresponding to A means that B is associated with A, and B can be determined from A.
  • 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.
  • the disclosed method and apparatus may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • 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.
  • 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.
  • 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. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

提供了一种上行资源分配方法和装置，方法包括：终端接收一个或多个上行调度授权；所述终端在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。

Description

一种上行资源分配方法和装置
相关申请的交叉引用
本申请主张在2017年5月4日在中国提交的中国专利申请No.201710308940.0的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种上行资源分配方法和装置。
背景技术
1)传统LTE(Long Term Evolution，长期演进)系统的LCP(Logical Channel Prioritization，逻辑信道优先级)过程
LTE系统的LCP是基于网络配置的单一的RB(Radio Bearer，无线承载)对应的优先级参数priority进行的。具体执行过程如下：
步骤1：按照所有有令牌的逻辑信道的优先级参数priority降序的顺序进行第一轮资源分配。第一轮资源分配基于每个逻辑信道的PBR(Prioritized Bit Rate，优先化比特速率)进行。同时根据上行资源分配情况更新每个逻辑信道可用的令牌数。
步骤2：如果还有剩余资源，那么进行第二轮资源分配。第二轮资源分配是按照所有有数据传输的逻辑信道的优先级参数priority降序的顺序分配为PBR之外的数据分配资源。资源分配以所有有令牌的逻辑信道的数据都分配了资源或者资源耗尽为止。
2)第五代(5G)移动通信系统的NR(New Radio，新空口)支持的业务介绍
5G NR系统主要支持三类业务：
eMBB(enhanced Mobile Broadband，增强型宽带通信)
mMTC(massive Machine Type Communications，大量机器类型通信)
URLLC(Ultra-Reliable and Low Latency Communications，高可靠低时延通信)
其中URLLC业务的时延要求特别高，端到端时延为0.5ms。但是核心网配置QoS(Quality of Service，服务质量)参数时，由于QoS参数中的优先级参数priority不需要考虑时延，URLLC业务优先级可能低于eMBB业务优先级。
3)基带参数
基带参数(Numerology)是3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)RAN(Radio Access Network，无线接入网)1的一个专业术语。不同基带参数之间的主要区别是不同基带参数支持的子载波间隔不同。比如5G NR系统支持的子载波间隔至少包括：15KHz，60KHz，这两个不同子载波间隔对应的基带参数就是两个独立的基带参数。
一般而言，高速终端使用的基带参数和低速终端使用的基带参数不同；高频终端和低频终端使用的基带参数也不相同。不同基带参数的使用除了和移动速度以及频率相关外，业界还有一种理解就是不同业务可以使用的基带参数也可能不同，比如URLLC和eMBB使用的基带参数可能不同。
4)TTI(Transmission Time interval，传输时间间隔)
传统的LTE系统中，TTI长度为1ms。从LTE R14开始，为了支持时延缩减，引入了不同TTI长度，比如1个OFDM(Orthogonal Frequency Division Multiplexing，正交频分复用)符号长度。不同TTI长度在5G系统中得到沿用并可以应用于每个基带参数上，即5G NR中不同基带参数可以使用不同TTI长度，也可以使用相同TTI长度，并且任何一个时刻某个基带参数上针对不同终端使用的TTI长度可以是动态变化的。
TTI长度的选择主要和业务时延相关，比如对于URLLC业务因为其支持的时延要求比较高，所以可能会选择长度较短的TTI长度，比如1个OFDM符号的TTI长度。
对于无线通信系统，目前业务QoS参数中的优先级参数priority和业务时延关系不大。但是对于5G以及之后的系统，随着URLLC业务的引入，如果优先级参数仍然和时延无关，那么就可能会出现一个问题，就是URLLC业务的传输资源被更高优先级的业务抢占，导致URLLC业务的时延需求无法满足。
发明内容
鉴于上述技术问题，本公开实施例提供一种解决低优先级但对时延比较敏感的业务的传输资源被高优先级业务抢占的问题。
依据本公开实施例的第一个方面，提供了一种上行资源分配方法，所述方法包括：
终端接收一个或多个上行调度授权(Uplink grant，UL grant)；
所述终端在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
可选地，在所述终端在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源之后，所述方法还包括：
如果对应上行调度授权还有剩余上行资源，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
可选地，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系是网络侧配置或者协议约定。
可选地，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系包括：
承载或逻辑信道与该承载或逻辑信道使用的所有基带参数和/或TTI长度组合的映射关系；或者
承载或逻辑信道与该承载或逻辑信道使用的最大的基带参数和/或TTI长度的映射关系。
可选地，所述终端在每个上行调度授权上进行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据 需要传输的承载或逻辑信道分配上行资源，包括：
确定所述多个上行调度授权的处理顺序，生成上行调度授权处理优先级队列；
按照所述上行调度授权处理优先级队列中上行调度授权的处理优先级从高到低的顺序依次选择待处理的上行调度授权，并确定该待处理的上行调度授权对应的基带参数和/或TTI长度；
根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度等于待处理的上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载或逻辑信道，对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；
按照预定的资源分配方式对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行调度授权处理优先级队列中所有上行调度授权对应的上行资源全部被分配或者所有承载或逻辑信道的待传输数据都分配了上行资源。
可选地，所述多个上行调度授权的处理顺序由协议约定，或者由网络侧配置，或者取决于终端实现。
可选地，所述预定的资源分配方式由网络配置，或者由协议约定，或者取决于终端实现。
可选地，所述预定的资源分配方式包括：
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照所有待传输数据量进行资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配 了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，需要为其全部数据分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中，对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，不需要为其分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源。
可选地，所述如果对应上行调度授权还有剩余上行资源，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配资源，包括：
如果对应上行调度授权还有剩余上行资源，根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度大于待处理的上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的部分或者全部承载或逻辑信道；
对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列，对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行资源全部被分配或者所有映射到该上行调度授权上的承载或逻辑信道的所有数据都分配了上行资源。
可选地，所述方法还包括：
所述终端将分配给同一个承载或逻辑信道的上行资源合并，然后确定承载或逻辑信道的数据量，并针对一个承载或逻辑信道组织一个媒体接入控制(Media Access Control，MAC)服务数据单元(Service Data Unit，SDU)；或者
所述终端对一个承载或逻辑信道每分配一次上行资源，针对该承载或逻辑信道生成一个MAC SDU。
依据本公开实施例的第二个方面，还提供了一种上行资源分配装置，所述装置包括：
接收模块，用于接收一个或多个上行调度授权；
第一资源分配模块，用于在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
可选地，所述装置还包括：
第二资源分配模块，用于如果对应上行调度授权还有剩余上行资源，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
可选地，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系是网络侧配置或者协议约定。
可选地，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系包括：
承载或逻辑信道与该承载或逻辑信道使用的所有基带参数和/或TTI长度组合的映射关系；或者
承载或逻辑信道与该承载或逻辑信道使用的最大的基带参数和/或TTI长度的映射关系。
可选地，所述第一资源分配模块包括：
第一确定单元，用于确定所述多个上行调度授权的处理顺序，生成上行调度授权处理优先级队列；
第二确定单元，用于按照所述上行调度授权处理优先级队列中上行调度授权的处理优先级从高到低的顺序依次选择待处理的上行调度授权，并确定该待处理的上行调度授权对应的基带参数和/或TTI长度；
第一队列生成单元，用于根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度等于待处理的上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载或逻辑信道，对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；
第一资源分配单元，用于按照预定的资源分配方式对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行调度授权处理优先级队列中所有上行调度授权对应的上行资源全部被分配或者所有承载或逻辑信道的待传输数据都分配了上行资源。
可选地，所述多个上行调度授权的处理顺序由协议约定，或者由网络侧配置，或者取决于终端实现。
可选地，所述预定的资源分配方式由网络配置，或者由协议约定，或者取决于终端实现。
可选地，所述预定的资源分配方式包括：
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照所有待传输数据量进行资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中对于承载或逻辑信道优先级队列中确定不需 要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，需要为其全部数据分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中，对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，不需要为其分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源。
可选地，所述第二资源分配模块包括：
选择单元，用于如果对应上行调度授权还有剩余上行资源，根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度大于待处理的上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的部分或者全部承载或逻辑信道；
第二队列生成单元，用于对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；
第二资源分配单元，用于对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行资源全部被分配或者所有映射到该上行调度授权上的承载或逻辑信道的所有数据都分配了上行资源。
可选地，所述装置还包括：
MAC SDU生成模块，用于将分配给同一个承载或逻辑信道的上行资源合并，然后确定承载或逻辑信道的数据量，并针对一个承载或逻辑信道组织一个MAC SDU；或者
对一个承载或逻辑信道每分配一次上行资源，针对该承载或逻辑信道生 成一个MAC SDU。
依据本公开实施例的第三个方面，还提供了一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的程序，所述处理器执行所述程序时实现如上所述的上行资源分配方法中的步骤。
依据本公开实施例的第四个方面，还提供了一种计算机可读存储介质，其上存储有程序，该程序被处理器执行时实现如上所述的上行资源分配方法中的步骤。
上述技术方案中的一个技术方案具有如下优点或有益效果：终端接收到N个上行调度授权(N≥1)，在每个上行调度授权上进行资源分配时，基于承载或逻辑信道和基带参数和/或TTI长度的映射关系，优先为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载或逻辑信道分配资源；进一步地，如果对应上行调度授权还有剩余资源，则为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度的且有数据需要传输的承载或逻辑信道分配资源，避免低优先级但对时延比较敏感的业务的传输资源被高优先级业务抢占的问题。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本公开的一个实施例中的上行资源分配方法的流程图；
图2为图1中步骤102的具体流程图；
图3本公开的另一个实施例中的上行资源分配方法的流程图；
图4为图3中步骤303的具体流程图；
图5为本公开的又一个实施例中的上行资源分配方法的流程图；
图6为图5中步骤502的具体流程图；
图7为本公开一个实施例中的上行资源分配装置的框图；
图8为本公开一个实施例中终端的结构示意图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
参见图1，图中示出了一个实施例中上行资源分配方法的流程，具体步骤如下：
步骤101、终端接收一个或多个上行调度授权；
上行调度授权：UL grant。
需要说明的是，在本实施例中并不限定上行调度授权的具体数量。
步骤102、终端在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
需要说明的是，在本实施例中承载和逻辑信道表达的含义相同。
在本实施例中，上述承载或逻辑信道与基带参数和/或TTI长度的映射关系包括以下任意一种或多种表示形式：
承载与基带参数的映射关系；
承载与TTI长度的映射关系；
承载与基带参数和TTI长度的映射关系；
逻辑信道与基带参数的映射关系；
逻辑信道与TTI长度的映射关系；
逻辑信道与基带参数和TTI长度的映射关系；
在本实施例中，上述上行调度授权对应的基带参数和/或TTI长度，包括以下任意一种或多种表示形式：
上行调度授权对应的基带参数；
上行调度授权对应的TTI长度；
上行调度授权对应的基带参数和TTI长度。
在本实施例中，承载或逻辑信道与基带参数和/或TTI长度的映射关系可以是网络侧配置或者协议约定。
在本实施例中，承载或逻辑信道与基带参数和/或TTI长度的映射关系具体是指：
承载或逻辑信道与该承载或逻辑信道使用的所有基带参数和/或TTI长度组合的映射关系；或者
承载或逻辑信道与该承载或逻辑信道使用的最大的基带参数和/或TTI长度的映射关系，当然也并不限于此。
参见图2，上述步骤102具体包括：
步骤1021、确定多个上行调度授权的处理顺序，生成上行调度授权处理优先级队列；
在本实施例中，多个上行调度授权的处理顺序由协议约定，比如根据基带参数和/或TTI长度从小到大的顺序约定多个上行调度授权的处理顺序，或者多个上行调度授权的处理顺序由网络侧配置，或者多个上行调度授权的处理顺序取决于终端实现。当然也并不限于此。
步骤1022、按照上行调度授权处理优先级队列中上行调度授权的处理优先级从高到低的顺序依次选择待处理的上行调度授权，并确定该待处理的上行调度授权对应的基带参数和/或TTI长度；
在本实施例中，可以通过相关技术中的方式确定待处理的上行调度授权对应的基带参数和/或TTI长度，在此不再复述。
步骤1023、根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度等于待处理的上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载或逻辑信道，对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；
在本实施例中，可选地，可以通过与承载或逻辑信道对应的QoS参数确定承载或逻辑信道的优先级。当然也并不限于此。
步骤1024、按照预定的资源分配方式对所述承载或逻辑信道优先级队列 中的承载或逻辑信道进行上行资源分配，直到上行调度授权处理优先级队列中所有上行调度授权对应的上行资源全部被分配或者所有承载或逻辑信道的待传输数据都分配了上行资源。
在本实施例中，在按照预定的资源分配方式对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配之后，重复执行步骤1022、1023以及步骤1024中的按照预定的资源分配方式对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行调度授权处理优先级队列中所有上行调度授权对应的上行资源全部被分配或者所有承载或逻辑信道的待传输数据都分配了上行资源。
在本实施例中，预定的资源分配方式可以由网络配置，或者由协议约定，或者取决于终端实现。
在本实施例中，所述预定的资源分配方式包括以下任意一种：
方式一、对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；
方式二、对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照所有待传输数据量进行资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；
方式三、对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，需要为其全部数据分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信 道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；
上述两轮资源分配是指：第一轮PBR资源分配和第二轮剩余数据资源分配。
方式四、对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中，对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，不需要为其分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源。
在本实施例中，终端根据上行资源分配结果组织MAC PDU，具体有两种方式：
方式一、终端将分配给同一个承载或逻辑信道的上行资源合并，然后确定承载或逻辑信道的数据量，并针对一个承载或逻辑信道组织一个MAC SDU；
方式二、终端对一个承载或逻辑信道每分配一次上行资源，针对该承载或逻辑信道生成一个MAC SDU。
在本实施例中，终端接收到N个上行调度授权(N≥1)，在每个上行调度授权上进行资源分配时，基于承载或逻辑信道和基带参数和/或TTI长度的映射关系，优先为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载或逻辑信道分配资源，避免低优先级但对时延比较敏感的业务的传输资源被高优先级的业务抢占的问题。
参见图3，图中示出了另一个实施例中上行资源分配方法的流程，具体步骤如下：
步骤301、终端接收一个或多个上行调度授权；
步骤302、终端在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数 和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
需要说明的是，上述步骤301和步骤302与图1所示的步骤101和步骤102相同，步骤302的具体实现过程可参见对步骤102的介绍，在此不再敷述。
步骤303、如果对应上行调度授权还有剩余上行资源，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
参见图4，步骤303的具体过程如下：
步骤3031、如果对应上行调度授权还有剩余上行资源，根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度大于待处理的上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的部分或者全部承载或逻辑信道；
步骤3032、对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列，对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行资源全部被分配或者所有映射到该上行调度授权上的承载或逻辑信道的所有数据都分配了上行资源。
在本实施例中，终端根据上行资源分配结果组织MAC PDU，具体有两种方式：
方式一、终端将分配给同一个承载或逻辑信道的上行资源合并，然后确定承载或逻辑信道的数据量，并针对一个承载或逻辑信道组织一个MAC SDU；
方式二、终端对一个承载或逻辑信道每分配一次上行资源，针对该承载或逻辑信道生成一个MAC SDU。
在本实施例中，终端接收到N个上行调度授权(N≥1)，在每个上行调度授权上进行资源分配时，基于承载或逻辑信道和基带参数和/或TTI长度的映射关系，优先为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载或逻辑信道分配资 源；如果对应上行调度授权还有剩余资源，则为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度的且有数据需要传输的承载或逻辑信道分配资源，能够避免低优先级但对时延比较敏感的业务的传输资源被高优先级的业务抢占的问题。
参见图5，图中示出了终端侧上行资源分配的流程，具体步骤如下：
步骤501、确定上行调度授权处理优先级队列；
具体地，终端接收到N个上行调度授权，确定N个上行调度授权的处理顺序，生成上行调度授权处理优先级队列，N大于等于1。
可选地，N个上行调度授权的处理顺序可以是协议约定，比如根据基带参数和/或TTI长度从小到大的顺序，N个上行调度授权的处理顺序也可以由网络侧配置。
步骤502、按照上行调度授权处理优先级队列，选择处于队首的上行调度授权，对该上行调度授权进行上行资源分配。
可选地，按照图6所示的方式对该上行调度授权进行上行资源分配：
步骤5021、选择上行调度授权处理优先级队列中第一个要处理的上行调度授权，并确定该上行调度授权对应的基带参数和/或TTI长度。
步骤5022、根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度等于要处理的上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载，然后对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级从高到低进行降序排序，生成承载或逻辑信道优先级队列。
步骤5023、对承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配。
具体有如下几种方式：
方式一：对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮资源分配。如果第一轮资源分配结束还有剩余资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮资源分配，直到资源耗尽或者承载优先级队列中的所有承载的待传输数据都分配了资源。
方式二：对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照所有待传输数据量进行资源分配。直到资源耗尽或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了资源。
方式三：对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮资源分配。其中，对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮资源分配时，需要为其全部数据分配资源。如果第一轮资源分配结束还有剩余资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮资源分配，直到资源耗尽或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了资源。
可选地，对于承载或逻辑信道优先级队列中配置了不需要进行两轮资源分配的承载或逻辑信道其对应的数据都在第一轮资源分配时传输。
方式四：对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮资源分配。其中，对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮资源分配时，不需要为其分配资源。如果第一轮资源分配结束还有剩余资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮资源分配，直到资源耗尽或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了资源。
对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，其所有数据都在第二轮资源分配时分配资源。
步骤5024、如果步骤5023资源分配结束后，该上行调度授权还有剩余资源，则根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度大于要处理的上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的部分或者全部承载或逻辑信道。然后对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级从高到低进行降序排序，生成承载或逻辑信道优先级队列，并继续执行步骤5023和5024，直到该上行调度授权资源耗尽或者所有可以映射到该上行调度授权上的承载或逻辑信道的所有数据都分配了资源。
步骤503、更新上行调度授权优先级处理队列，将已经处理过的上行调度授权删除，然后重复步骤502，直到所有上行调度授权的资源耗尽或者所有承载或逻辑信道都在其对应的基带参数/TTI对应的上行调度授权上分配了上行资源。
在本实施例中，终端根据上行资源分配结果组织MAC PDU，具体有两种方式：
方式一：将分配给同一个承载的资源合并，然后确定可以承载的数据量，并针对一个承载组织一个MAC SDU。
方式二：每对一个承载或逻辑信道分配一次资源(比如针对PBR分配资源或者针对剩余数据分配资源算作两次资源分配)，则针对该承载生成一个MAC SDU。
在本实施例中，终端接收到N个上行调度授权(N≥1)，在每个上行调度授权上进行资源分配时，基于承载和基带参数/TTI长度的映射关系，优先为能够支持的最大基带参数/TTI长度等于该上行调度授权对应的基带参数/TTI长度且有数据需要传输的承载分配承载或逻辑信道分配资源；如果还有剩余资源，则为能够支持的最大基带参数/TTI长度大于该上行调度授权对应的基带参数/TTI长度的且有数据需要传输的承载分配承载或逻辑信道分配资源，能够避免低优先级但对时延比较敏感的业务的传输资源被高优先级的业务抢占的问题。
基于同一发明构思，本公开实施例中还提供了一种上行资源分配装置，由于该上行资源分配装置解决问题的原理与本公开实施例图1～5中上行资源分配方法相似，因此该上行资源分配装置的实施可以参见方法的实施，重复之处不再敷述。
参见图7，图中示出了一种上行资源分配装置的结构，该装置700包括：
接收模块701，用于接收一个或多个上行调度授权；
第一资源分配模块702，用于在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
在本实施例中，可选地，继续参见图7，装置700还包括：
第二资源分配模块703，用于如果对应上行调度授权还有剩余上行资源，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
在本实施例中，可选地，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系是网络侧配置或者协议约定。
在本实施例中，可选地，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系包括：
承载或逻辑信道与该承载或逻辑信道使用的所有基带参数和/或TTI长度组合的映射关系；或者
承载或逻辑信道与该承载或逻辑信道使用的最大的基带参数和/或TTI长度的映射关系。
在本实施例中，可选地，继续参见图7，所述第一资源分配模702包括：
第一确定单元7021，用于确定所述多个上行调度授权的处理顺序，生成上行调度授权处理优先级队列；
第二确定单元7022，用于按照所述上行调度授权处理优先级队列中上行调度授权的处理优先级从高到低的顺序依次选择待处理的上行调度授权，并确定该待处理的上行调度授权对应的基带参数和/或TTI长度；
第一队列生成单元7023，用于根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度等于待处理的上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载或逻辑信道，对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；
第一资源分配单元7024，用于按照预定的资源分配方式对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行调度授权处理优先级队列中所有上行调度授权对应的上行资源全部被分配或者所有承载或逻辑信道的待传输数据都分配了上行资源。
在本实施例中，可选地，所述多个上行调度授权的处理顺序由协议约定， 或者由网络侧配置，或者取决于终端实现。
在本实施例中，可选地，所述预定的资源分配方式由网络配置，或者由协议约定，或者取决于终端实现。
在本实施例中，可选地，所述预定的资源分配方式包括：
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照所有待传输数据量进行资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，需要为其全部数据分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中，对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，不需要为其分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有 承载或逻辑信道的待传输数据都分配了上行资源。
在本实施例中，可选地，继续参见图7，所述第二资源分配模块703包括：
选择单元7031，用于如果对应上行调度授权还有剩余上行资源，根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度大于待处理的上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的部分或者全部承载或逻辑信道；
第二队列生成单元7032，用于对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；
第二资源分配单元7033，用于对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行资源全部被分配或者所有映射到该上行调度授权上的承载或逻辑信道的所有数据都分配了上行资源。
在本实施例中，可选地，继续参见图7，所述装置700还包括：
MAC SDU生成模块704，用于将分配给同一个承载或逻辑信道的上行资源合并，然后确定承载或逻辑信道的数据量，并针对一个承载或逻辑信道组织一个MAC SDU；或者
对一个承载或逻辑信道每分配一次上行资源，针对该承载或逻辑信道生成一个MAC SDU。
本公开实施例还提供了一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现如图1～图6所示的上行资源分配方法中的步骤。
参见图8，示出了一种终端的结构，该终端包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现以下步骤：接收一个或多个上行调度授权；在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
在图8中，以总线800代表的总线架构可以包括任意数量的互联的总线和桥，总线800将包括由通用处理器801代表的一个或多个处理器和存储器 804代表的存储器的各种电路链接在一起。总线800还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起。总线接口803在总线800和收发机802之间提供接口。收发机802可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。例如：收发机802从其他设备接收外部数据。收发机802用于将处理器801处理后的数据发送给其他设备。取决于计算系统的性质，还可以提供用户接口，例如小键盘、显示器、扬声器、麦克风、操纵杆。
处理器801负责管理总线800和通常的处理，如前述所述运行通用操作系统。而存储器704可以被用于存储处理器801在执行操作时所使用的数据。
可选地，处理器801可以是CPU(Central Processing Unit，中央处理单元)、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field-Programmable Gate Array，现场可编程门阵列)或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
可选地，处理器801还用于：如果对应上行调度授权还有剩余上行资源，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
可选地，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系是网络侧配置或者协议约定。
可选地，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系包括：
承载或逻辑信道与该承载或逻辑信道使用的所有基带参数和/或TTI长度组合的映射关系；或者
承载或逻辑信道与该承载或逻辑信道使用的最大的基带参数和/或TTI长度的映射关系。
可选地，处理器801进一步用于：确定所述多个上行调度授权的处理顺序，生成上行调度授权处理优先级队列；按照所述上行调度授权处理优先级队列中上行调度授权的处理优先级从高到低的顺序依次选择待处理的上行调度授权，并确定该待处理的上行调度授权对应的基带参数和/或TTI长度；根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基 带参数和/或TTI长度等于待处理的上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载或逻辑信道，对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；按照预定的资源分配方式对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行调度授权处理优先级队列中所有上行调度授权对应的上行资源全部被分配或者所有承载或逻辑信道的待传输数据都分配了上行资源。
可选地，所述多个上行调度授权的处理顺序由协议约定，或者由网络侧配置，或者取决于终端实现。
可选地，所述预定的资源分配方式由网络配置，或者由协议约定，或者取决于终端实现。
可选地，所述预定的资源分配方式包括：
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照所有待传输数据量进行资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，需要为其全部数据分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先 级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中，对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，不需要为其分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源。
可选地，处理器801进一步用于：如果对应上行调度授权还有剩余上行资源，根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度大于待处理的上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的部分或者全部承载或逻辑信道；对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行资源全部被分配或者所有映射到该上行调度授权上的承载或逻辑信道的所有数据都分配了上行资源。
可选地，处理器801还用于：将分配给同一个承载或逻辑信道的上行资源合并，然后确定承载或逻辑信道的数据量，并针对一个承载或逻辑信道组织一个MAC SDU；或者对一个承载或逻辑信道每分配一次上行资源，针对该承载或逻辑信道生成一个MAC SDU。
本公开实施例还提供了一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现如图1～图6所示的上行资源分配方法中的步骤。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本公开的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
在本公开的各种实施例中，应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本公开实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常可互换使用。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
在本申请所提供的实施例中，应理解，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
在本申请所提供的几个实施例中，应该理解到，所揭露方法和装置，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络侧设备等)执行本公开各个实施例所述收发方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述的是本公开的优选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以做出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (20)

  1. 一种上行资源分配方法，包括：
    终端接收一个或多个上行调度授权(UL grant)；
    所述终端在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数(numerology)和/或传输时间间隔(Transmission Time interval，TTI)长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
  2. 根据权利要求1所述的方法，其中，在所述终端在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源之后，所述方法还包括：
    如果对应上行调度授权还有剩余上行资源，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
  3. 根据权利要求1或2所述的方法，其中，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系是网络侧配置或者协议约定。
  4. 根据权利要求3所述的方法，其中，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系包括：
    承载或逻辑信道与该承载或逻辑信道使用的所有基带参数和/或TTI长度组合的映射关系；或者
    承载或逻辑信道与该承载或逻辑信道使用的最大的基带参数和/或TTI长度的映射关系。
  5. 根据权利要求1所述的方法，其中，所述终端在每个上行调度授权上进行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参 数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源，包括：
    确定所述多个上行调度授权的处理顺序，生成上行调度授权处理优先级队列；
    按照所述上行调度授权处理优先级队列中上行调度授权的处理优先级从高到低的顺序依次选择待处理的上行调度授权，并确定该待处理的上行调度授权对应的基带参数和/或TTI长度；
    根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度等于待处理的上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载或逻辑信道，对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；
    按照预定的资源分配方式对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行调度授权处理优先级队列中所有上行调度授权对应的上行资源全部被分配或者所有承载或逻辑信道的待传输数据都分配了上行资源。
  6. 根据权利要求5所述的方法，其中，所述多个上行调度授权的处理顺序由协议约定，或者由网络侧配置，或者取决于终端实现；或者
    所述预定的资源分配方式由网络配置，或者由协议约定，或者取决于终端实现。
  7. 根据权利要求5所述的方法，其中，所述预定的资源分配方式包括：
    对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其优先化比特速率(Prioritized Bit Rate，PBR)进行第一轮PBR资源分配；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
    对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照所有待传输数据量进行资源分配，直到对应上行调度授权的上行资源全部被分配或 者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
    对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，需要为其全部数据分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
    对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中，对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，不需要为其分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源。
  8. 根据权利要求2所述的方法，其中，所述如果对应上行调度授权还有剩余上行资源，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配资源，包括：
    如果对应上行调度授权还有剩余上行资源，根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度大于待处理的上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的部分或者全部承载或逻辑信道；
    对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列，对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行资源全部被分配或者所有映射到 该上行调度授权上的承载或逻辑信道的所有数据都分配了上行资源。
  9. 根据权利要求1所述的方法，还包括：
    所述终端将分配给同一个承载或逻辑信道的上行资源合并，然后确定承载或逻辑信道的数据量，并针对一个承载或逻辑信道组织一个媒体接入控制(Media Access Control，MAC)服务数据单元(Service Data Unit，SDU)；或者
    所述终端对一个承载或逻辑信道每分配一次上行资源，针对该承载或逻辑信道生成一个MAC SDU。
  10. 一种上行资源分配装置，包括：
    接收模块，用于接收一个或多个上行调度授权；
    第一资源分配模块，用于在每个上行调度授权上进行上行资源分配时，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度等于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
  11. 根据权利要求10所述的装置，还包括：
    第二资源分配模块，用于如果对应上行调度授权还有剩余上行资源，基于承载或逻辑信道与基带参数和/或TTI长度的映射关系，为能够支持的最大基带参数和/或TTI长度大于该上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的承载或逻辑信道分配上行资源。
  12. 根据权利要求10或11所述的装置，其中，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系是网络侧配置或者协议约定。
  13. 根据权利要求12所述的装置，其中，所述承载或逻辑信道与基带参数和/或TTI长度的映射关系包括：
    承载或逻辑信道与该承载或逻辑信道使用的所有基带参数和/或TTI长度组合的映射关系；或者
    承载或逻辑信道与该承载或逻辑信道使用的最大的基带参数和/或TTI长度的映射关系。
  14. 根据权利要求10所述的装置，其中，所述第一资源分配模块包括：
    第一确定单元，用于确定所述多个上行调度授权的处理顺序，生成上行 调度授权处理优先级队列；
    第二确定单元，用于按照所述上行调度授权处理优先级队列中上行调度授权的处理优先级从高到低的顺序依次选择待处理的上行调度授权，并确定该待处理的上行调度授权对应的基带参数和/或TTI长度；
    第一队列生成单元，用于根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度等于待处理的上行调度授权对应的基带参数和/或TTI长度且有数据需要传输的承载或逻辑信道，对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；
    第一资源分配单元，用于按照预定的资源分配方式对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行调度授权处理优先级队列中所有上行调度授权对应的上行资源全部被分配或者所有承载或逻辑信道的待传输数据都分配了上行资源。
  15. 根据权利要求14所述的装置，其中，所述多个上行调度授权的处理顺序由协议约定，或者由网络侧配置，或者取决于终端实现；或者
    所述预定的资源分配方式由网络配置，或者由协议约定，或者取决于终端实现。
  16. 根据权利要求14所述的装置，其中，所述预定的资源分配方式包括：
    对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
    对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照所有待传输数据量进行资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
    对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR 进行第一轮PBR资源分配，其中对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，需要为其全部数据分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮剩余数据资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源；或者
    对承载或逻辑信道优先级队列中的各个承载或逻辑信道依次按照其PBR进行第一轮PBR资源分配，其中，对于承载或逻辑信道优先级队列中确定不需要进行两轮资源分配的承载或逻辑信道，则在第一轮PBR资源分配时，不需要为其分配上行资源；如果第一轮PBR资源分配结束对应上行调度授权还有剩余上行资源，则再次对照承载或逻辑信道优先级队列中的各个有剩余数据需要传输的承载或逻辑信道的剩余数据进行第二轮资源分配，直到对应上行调度授权的上行资源全部被分配或者承载或逻辑信道优先级队列中的所有承载或逻辑信道的待传输数据都分配了上行资源。
  17. 根据权利要求11所述的装置，其中，所述第二资源分配模块包括：
    选择单元，用于如果对应上行调度授权还有剩余上行资源，根据承载或逻辑信道与基带参数和/或TTI长度的对应关系，选择支持的最大基带参数和/或TTI长度大于待处理的上行调度授权对应的基带参数和/或TTI长度，且有数据需要传输的部分或者全部承载或逻辑信道；
    第二队列生成单元，用于对选择出来的承载或逻辑信道按照承载或逻辑信道的优先级进行排序，生成承载或逻辑信道优先级队列；
    第二资源分配单元，用于对所述承载或逻辑信道优先级队列中的承载或逻辑信道进行上行资源分配，直到上行资源全部被分配或者所有映射到该上行调度授权上的承载或逻辑信道的所有数据都分配了上行资源。
  18. 根据权利要求10所述的装置，还包括：
    MAC SDU生成模块，用于将分配给同一个承载或逻辑信道的上行资源合并，然后确定承载或逻辑信道的数据量，并针对一个承载或逻辑信道组织一个MAC SDU；或者
    对一个承载或逻辑信道每分配一次上行资源，针对该承载或逻辑信道生成一个MAC SDU。
  19. 一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的程序，所述处理器执行所述程序时实现如权利要求1～9中任一项所述的上行资源分配方法中的步骤。
  20. 一种计算机可读存储介质，其上存储有程序，其中，该程序被处理器执行时实现如权利要求1～9中任一项所述的上行资源分配方法中的步骤。
PCT/CN2018/081558 2017-05-04 2018-04-02 一种上行资源分配方法和装置 Ceased WO2018201833A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710308940.0A CN106961741B (zh) 2017-05-04 2017-05-04 一种上行资源分配方法和装置
CN201710308940.0 2017-05-04

Publications (1)

Publication Number Publication Date
WO2018201833A1 true WO2018201833A1 (zh) 2018-11-08

Family

ID=59482146

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081558 Ceased WO2018201833A1 (zh) 2017-05-04 2018-04-02 一种上行资源分配方法和装置

Country Status (2)

Country Link
CN (1) CN106961741B (zh)
WO (1) WO2018201833A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114223307A (zh) * 2019-10-16 2022-03-22 Oppo广东移动通信有限公司 数据传输方法、装置、设备及存储介质
EP3911086A4 (en) * 2019-01-11 2022-05-11 Spreadtrum Communications (Shanghai) Co., Ltd. PROCEDURE FOR SELECTING AN UPLINK TRANSMISSION RESOURCE, TERMINAL AND STORAGE MEDIUM

Families Citing this family (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018120985A1 (zh) * 2016-12-29 2018-07-05 电信科学技术研究院 一种进行资源分配的方法和设备
CN108282278B (zh) * 2017-01-05 2021-02-05 华为技术有限公司 传输数据的方法、终端设备和网络设备
CN106961741B (zh) * 2017-05-04 2019-11-22 电信科学技术研究院 一种上行资源分配方法和装置
US11160107B2 (en) 2017-07-21 2021-10-26 Lg Electronics Inc. Method for performing a LCP procedure in wireless communication system and a device therefor
IL271210B2 (en) * 2017-08-04 2024-01-01 Guangdong Oppo Mobile Telecommunications Corp Ltd Resource scheduling method, terminal device, and network device
CN109392148B (zh) * 2017-08-11 2021-06-04 电信科学技术研究院 一种上行资源分配的方法、终端及网络设备
CN111096034B (zh) * 2017-08-11 2024-10-01 Oppo广东移动通信有限公司 资源分配方法、装置、系统及计算机可读存储介质
WO2019033428A1 (zh) * 2017-08-18 2019-02-21 北京小米移动软件有限公司 上行资源分配方法、装置和终端
CN109451855B (zh) * 2017-08-18 2023-05-12 北京小米移动软件有限公司 上行资源分配方法、装置和终端
CN114944904A (zh) 2017-09-11 2022-08-26 中兴通讯股份有限公司 资源指示方法及装置、存储介质
CN109756986B (zh) 2017-11-03 2021-07-13 大唐移动通信设备有限公司 一种上行数据包资源分配方法和用户终端
WO2019095112A1 (zh) * 2017-11-14 2019-05-23 Oppo广东移动通信有限公司 传输数据的方法、终端设备和网络设备
EP3714555A4 (en) * 2017-11-20 2021-07-07 Nokia Solutions and Networks Oy BACKHAUL TRANSFER BETWEEN NETWORK DEVICES
JP2021508206A (ja) * 2017-12-27 2021-02-25 オッポ広東移動通信有限公司Ｇｕａｎｇｄｏｎｇ Ｏｐｐｏ Ｍｏｂｉｌｅ Ｔｅｌｅｃｏｍｍｕｎｉｃａｔｉｏｎｓ Ｃｏｒｐ．， Ｌｔｄ． データ送信方法、装置、コンピュータ装置及び記憶媒体
CN110139373B (zh) * 2018-02-09 2021-08-20 大唐移动通信设备有限公司 一种资源选择方法及用户终端
CN110167066B (zh) * 2018-02-14 2022-09-02 华为技术有限公司 一种数据传输方法及装置
CN110324902B (zh) * 2018-03-30 2023-06-27 华为技术有限公司 通信方法、通信装置和系统
ES2989693T3 (es) 2018-04-04 2024-11-27 Zte Corp Métodos y aparato para apropiarse de un recurso de transmisión de enlace ascendente en una comunicación inalámbrica
CN110636532B (zh) * 2018-06-21 2021-01-08 维沃移动通信有限公司 一种功率分配方法及终端
CN110838899B (zh) * 2018-08-16 2021-12-24 大唐移动通信设备有限公司 一种直接通信链路资源分配方法及终端
CN113747596A (zh) 2018-09-21 2021-12-03 华为技术有限公司 无线调度的方法和装置
CN111132351B (zh) * 2018-10-31 2023-04-07 大唐移动通信设备有限公司 一种资源分配方法、终端及节点设备
CN111328138B (zh) * 2018-12-13 2023-04-07 大唐移动通信设备有限公司 Mac pdu的组织方法、装置及终端
CN111385883B (zh) * 2018-12-28 2023-01-10 展讯通信（上海）有限公司 一种数据传输方法及装置、存储介质、终端
CN110602796B (zh) * 2019-01-29 2023-06-06 北京中科晶上科技股份有限公司 移动宽带共享信道上的资源调度方法及电子设备
CN111726865B (zh) * 2019-03-21 2023-06-30 大唐移动通信设备有限公司 媒质接入控制业务数据单元处理、接收方法、设备及装置
CN111294165B (zh) * 2019-03-22 2021-06-08 展讯通信（上海）有限公司 资源分配方法及装置、存储介质、终端
CN111294964A (zh) * 2019-03-28 2020-06-16 展讯通信（上海）有限公司 资源选择、配置方法及装置、存储介质、用户设备、基站
CN111836389B (zh) * 2019-04-23 2023-07-25 中国移动通信有限公司研究院 上行资源调度方法、终端及网络侧设备
CN111601383A (zh) * 2019-06-17 2020-08-28 维沃移动通信有限公司 一种资源分配方法、终端和网络设备
WO2021081908A1 (zh) * 2019-10-31 2021-05-06 Oppo广东移动通信有限公司 为上行逻辑信道分配资源的方法和终端设备
CN111428973B (zh) * 2020-03-11 2024-04-12 慧镕电子系统工程股份有限公司 一种能有效提高资源利用率的虚拟资源分配方法
CN113630891B (zh) * 2020-05-06 2022-08-19 展讯通信（上海）有限公司 Mac层优先级排序方法及装置、存储介质、用户设备
CN113840305B (zh) * 2020-06-24 2024-06-07 大唐移动通信设备有限公司 数据传输方法、参数配置方法、终端和网络侧设备
CN117425223A (zh) * 2022-07-08 2024-01-19 大唐移动通信设备有限公司 资源分配、信息配置方法、装置、终端设备及网络设备
CN121397756A (zh) * 2024-07-22 2026-01-23 维沃移动通信有限公司 Lcp处理方法、传输方法、装置、终端及网络侧设备
CN121510305A (zh) * 2024-08-01 2026-02-10 荣耀终端股份有限公司 一种通信方法、通信装置及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105979597A (zh) * 2016-06-27 2016-09-28 宇龙计算机通信科技(深圳)有限公司 通信资源的分配方法、分配装置、基站和终端
CN106961741A (zh) * 2017-05-04 2017-07-18 电信科学技术研究院 一种上行资源分配方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013109888A1 (en) * 2012-01-19 2013-07-25 Futurewei Technologies, Inc. Systems and method for uplink resource allocation
CN104363663B (zh) * 2014-11-17 2018-02-06 电子科技大学 一种lte通信系统中基于混合业务的分组调度方法
CN106376050B (zh) * 2016-09-30 2022-03-18 宇龙计算机通信科技(深圳)有限公司 子载波间隔的设置/确定方法、装置、基站和终端

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105979597A (zh) * 2016-06-27 2016-09-28 宇龙计算机通信科技(深圳)有限公司 通信资源的分配方法、分配装置、基站和终端
CN106961741A (zh) * 2017-05-04 2017-07-18 电信科学技术研究院 一种上行资源分配方法和装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CATT: "MAC Model in NR", 3GPP TSG - RAN WG 2 MEETING #96, R2-167950, 18 November 2016 (2016-11-18), XP051177679 *
HUAWEI ET AL.: "LCP with Multiple Numerologies", 3GPP TSG - RAN WG 2 MEETING #96, R2-167575, 18 November 2016 (2016-11-18), XP055505421 *
NOKIA ET AL.: "Report of email discUSsion on [96#28][NR] MAC to support multiple numerologies", 3GPP TSG - RAN WG 2 NR ADHOC, R2-1700250, 19 January 2017 (2017-01-19), XP051203658 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3911086A4 (en) * 2019-01-11 2022-05-11 Spreadtrum Communications (Shanghai) Co., Ltd. PROCEDURE FOR SELECTING AN UPLINK TRANSMISSION RESOURCE, TERMINAL AND STORAGE MEDIUM
CN114223307A (zh) * 2019-10-16 2022-03-22 Oppo广东移动通信有限公司 数据传输方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN106961741B (zh) 2019-11-22
CN106961741A (zh) 2017-07-18

Similar Documents

Publication Publication Date Title
WO2018201833A1 (zh) 一种上行资源分配方法和装置
EP3554125B1 (en) Data processing method, apparatus and system
EP3840512B1 (en) Sidelink resource allocation method and terminal
US11039448B2 (en) Resource scheduling method and apparatus
WO2018059234A1 (zh) 一种缓存状态报告的上报方法及装置
CN114514772B (zh) 包括具有优先值的mac ce的逻辑信道的优先级化的方法和装置
CN106954277B (zh) 一种调度请求处理方法和装置
CN108347784A (zh) 一种资源调度方法以及无线接入网设备和终端设备
WO2020034740A1 (zh) 一种调度请求资源确定及配置方法、设备及存储介质
CN113556785A (zh) 一种业务质量流的控制方法及相关设备
WO2014117347A1 (zh) 一种数据调度方法和设备
CN108811140A (zh) 一种数据业务传输方法及系统
CN108024341A (zh) 一种调度方法、终端及基站
CN107872897B (zh) 一种进行上行数据操作的方法和设备
CN111385883B (zh) 一种数据传输方法及装置、存储介质、终端
US20240007895A1 (en) Communication control device, communication control method and recording medium
CN110446263B (zh) 数据传输方法及装置
CN111866903B (zh) 一种混合自动重传请求模式的配置方法及相关装置
CN108260220B (zh) 一种进行资源分配的方法和设备
WO2018120985A1 (zh) 一种进行资源分配的方法和设备
WO2026058757A1 (ja) 通信装置、無線通信システム、制御方法及びプログラム
CN111328138B (zh) Mac pdu的组织方法、装置及终端
WO2026009628A1 (ja) 端末装置、端末装置の方法及び基地局装置
KR20260049103A (ko) 통신 네트워크에서 확장 현실 서비스의 품질 관리를 위한 방법 및 장치
WO2026009629A1 (ja) 端末装置、端末装置の方法及び基地局装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18794699

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18794699

Country of ref document: EP

Kind code of ref document: A1