WO2019085741A1 - 上行数据包资源分配方法和用户终端 - Google Patents

上行数据包资源分配方法和用户终端 Download PDF

Info

Publication number
WO2019085741A1
WO2019085741A1 PCT/CN2018/110458 CN2018110458W WO2019085741A1 WO 2019085741 A1 WO2019085741 A1 WO 2019085741A1 CN 2018110458 W CN2018110458 W CN 2018110458W WO 2019085741 A1 WO2019085741 A1 WO 2019085741A1
Authority
WO
WIPO (PCT)
Prior art keywords
grant
target object
user terminal
mapping relationship
logical channel
Prior art date
Application number
PCT/CN2018/110458
Other languages
English (en)
French (fr)
Inventor
赵亚利
伯特兰⋅皮埃尔
谌丽
Original Assignee
电信科学技术研究院有限公司
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 电信科学技术研究院有限公司 filed Critical 电信科学技术研究院有限公司
Priority to US16/760,660 priority Critical patent/US11706756B2/en
Priority to KR1020207013719A priority patent/KR20200064140A/ko
Priority to KR1020247013780A priority patent/KR20240058991A/ko
Priority to EP18873382.8A priority patent/EP3706488B1/en
Priority to KR1020227040846A priority patent/KR20220162850A/ko
Priority to JP2020524588A priority patent/JP7106639B2/ja
Publication of WO2019085741A1 publication Critical patent/WO2019085741A1/zh
Priority to US18/174,922 priority patent/US20230209540A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/26025—Numerology, i.e. varying one or more of symbol duration, subcarrier spacing, Fourier transform size, sampling rate or down-clocking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • 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/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to an uplink packet resource allocation method and a user terminal.
  • the LCP of the LTE system is a priority parameter corresponding to a single RB (Radio Bearer) based on the network configuration. Priority.
  • the specific execution process is as follows: First, the first round of resource allocation is performed in the descending order of priority parameters priority of all logical channels with tokens. The first round of resource allocation is performed based on the PBR (Prioritized Bit Rate) of each logical channel. At the same time, the number of tokens available for each logical channel is updated according to the resource allocation. Then, if there are remaining resources, then a second round of resource allocation is made. 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.
  • LCP restriction the limiting factor that LCP needs to consider at present is called LCP restriction.
  • the LCP restriction in the related art mainly includes SCS (Sub-Carrier Space) and PUSCH transmission duration (physical uplink shared channel transmission duration, its essence). It is the same as the Transmission Time Interval (TTI) and the cell Cell.
  • TTI Transmission Time Interval
  • the embodiments of the present disclosure provide an uplink data packet resource allocation method and a user terminal to solve the problem that scheduling performance is limited.
  • the embodiment of the present disclosure provides an uplink data packet resource allocation method, which is applied to a user terminal, and includes:
  • the LCP restriction includes at least a mapping relationship between a target object and a UL grant type, where the target object is a service type or a logical channel or a logical channel group.
  • mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the user terminal, or determined by a network device or agreed by a protocol.
  • the network device when the mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the network device, the network device sends the mapping relationship to the user by using high layer signaling or physical layer signaling. terminal;
  • the method further includes: sending, by using high layer signaling or physical layer signaling, the mapping relationship to the Network equipment.
  • the service type is one of an IP-based voice VOIP service, a high-reliability low-latency URLLC service, and an enhanced broadband communication eMBB service.
  • the UL grant type is one of dynamic scheduling, unauthorized scheduling, and semi-persistent scheduling.
  • the LCP restriction further includes one or a combination of: a subcarrier spacing SCS, a physical uplink shared channel transmission duration PUSCH transmission duration, and a cell Cell.
  • the embodiment of the present disclosure further provides a user terminal, including:
  • a receiving module configured to receive at least one uplink grant information UL grant sent by the network device
  • a determining module configured to determine, according to a logical channel priority limiting factor LCP restriction corresponding to the target object, a correspondence between the target object and the UL grant;
  • a resource allocation module configured to perform resource allocation on each of the UL grants according to a correspondence between the target object and the UL grant;
  • the LCP restriction includes at least a mapping relationship between a target object and a UL grant type, where the target object is a service type or a logical channel or a logical channel group.
  • mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the user terminal, or determined by a network device or agreed by a protocol.
  • the service type is one of an IP-based voice VOIP service, a high-reliability low-latency URLLC service, and an enhanced broadband communication eMBB service.
  • the UL grant type is one of dynamic scheduling, unauthorized scheduling, and semi-persistent scheduling.
  • Embodiments of the present disclosure also provide a user terminal, a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor;
  • the transceiver is configured to receive at least one uplink grant information UL grant sent by the network device;
  • the processor is configured to read a program in the memory, and perform the following process: determining, according to a logical channel priority limiting factor LCP restriction corresponding to the target object, a correspondence between the target object and the UL grant; and determining, according to the target object a resource allocation on each of the UL grants, where the LCP restriction includes at least a mapping relationship between a target object and a UL grant type, where the target object is a service type or a logical channel or Logical channel group.
  • mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the user terminal, or determined by a network device or agreed by a protocol.
  • the network device when the mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the network device, the network device sends the mapping relationship to the user by using high layer signaling or physical layer signaling. terminal;
  • the transceiver is further configured to send the mapping relationship by using high layer signaling or physical layer signaling.
  • the network device when the mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the user terminal, the transceiver is further configured to send the mapping relationship by using high layer signaling or physical layer signaling.
  • the service type is one of an IP-based voice VOIP service, a high-reliability low-latency URLLC service, and an enhanced broadband communication eMBB service.
  • the UL grant type is one of dynamic scheduling, unauthorized scheduling, and semi-persistent scheduling.
  • the LCP restriction further includes one or a combination of: a subcarrier spacing SCS, a physical uplink shared channel transmission duration PUSCH transmission duration, and a cell Cell.
  • the embodiment of the present disclosure further provides a computer readable storage medium having a computer program stored thereon, wherein the program is executed by the processor to implement the steps in the uplink data packet resource allocation method provided by the embodiment of the present disclosure.
  • the at least one uplink grant information UL grant sent by the receiving network device is received; and the correspondence between the target object and the UL grant is determined according to the logical channel priority limiting factor LCP restriction corresponding to the target object; Resource mapping is performed on each of the UL grants, where the LCP restriction includes at least a mapping relationship between the target object and a UL grant type, where the target object is a service type or Logical channel or logical channel group. Since the UL grant type is added to the LCP restriction, the target object is mapped, so that the correspondence between the target object and the UL grant is first determined in the process of the LCP, and then according to the correspondence between the target object and the UL grant, Resource allocation on the UL grant. Therefore, the embodiments of the present disclosure can ensure that data transmitted on each UL grant is data expected by the network side, thereby improving scheduling performance.
  • FIG. 1 is a schematic structural diagram of a network applicable to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of an uplink data packet resource allocation method according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of an implementation of an uplink data packet resource allocation method according to an embodiment of the present disclosure
  • FIG. 4 is a second implementation flowchart of an uplink data packet resource allocation method according to an embodiment of the present disclosure
  • FIG. 5 is a third flowchart of an implementation method for providing an uplink data packet resource according to an embodiment of the present disclosure
  • FIG. 6 is a structural diagram of a user terminal according to an embodiment of the present disclosure.
  • FIG. 7 is a structural diagram of another user terminal according to an embodiment of the present disclosure.
  • FIG. 1 is a schematic diagram of a network structure applicable to an embodiment of the present disclosure.
  • a user equipment (User Equipment, UE) 11 and a network device 12 are illustrated.
  • the user terminal 11 may be a mobile phone or a tablet.
  • Terminal side devices such as (Tablet Personal Computer), Laptop Computer, Personal Digital Assistant (PDA), Mobile Internet Device (MID), or Wearable Device It should be noted that the specific type of the user terminal 11 is not limited in the embodiment of the present disclosure.
  • the network device 12 may be a base station, for example, a macro station, an LTE eNB, a 5G NR NB, etc.; the network device 12 may also be a small station, such as a low power node (LPN: low power node) pico, a femto, or the like, or a network device. 12 can be an access point (AP); the base station can also be a network unit composed of a central unit (CU) and a plurality of transmission reception points (TRPs) that are managed and controlled. It should be noted that the specific type of the network device 12 is not limited in the embodiment of the present disclosure.
  • FIG. 2 is a flowchart of an uplink data packet resource allocation method according to an embodiment of the present disclosure.
  • the uplink data packet resource allocation method provided by the embodiment of the present disclosure is applied to a user terminal, and is used to control uplink data of the user terminal.
  • Packet resource allocation, as shown in FIG. 2, the uplink packet resource allocation method includes the following steps:
  • the LCP restriction includes at least a mapping relationship between a target object and a UL grant type, where the target object is a service type or a logical channel or a logical channel group.
  • the network device After the user equipment accesses the network device, the network device sends the indication information to the user terminal to indicate that the user terminal performs the uplink transmission.
  • the indication information carries the UL grant, and the user terminal may use the UL grant sent by the network device.
  • the LCP process as shown in steps 202 and 203 will be performed.
  • the foregoing UL grant type may be set according to actual needs.
  • the UL grant type is one of dynamic scheduling, grant-free scheduling and semi-persistent scheduling (SPS).
  • SPS semi-persistent scheduling
  • the number of UL grants sent by the network device may be set according to actual needs, and is not further limited.
  • the type of each UL grant sent may be one of dynamic scheduling, unauthorized scheduling, and semi-persistent scheduling.
  • two UL grants sent by the network device received by the user equipment one UL grant may be a dynamically scheduled UL grant, and the other UL grant is an SPS grant.
  • the foregoing mapping relationship may be a mapping relationship between a UL grant type and a service type, a mapping relationship between a UL grant type and a logical channel, and a mapping relationship between a UL grant type and a logical channel group.
  • the mapping relationship is a mapping relationship between a service type and a logical channel
  • the mapping relationship is a mapping between a specific service and a UL grant type.
  • the mapping relationship is a mapping between a UL grant type and a logical channel
  • the mapping relationship is The mapping relationship is represented by the mapping information of the logical channel number and the UL grant type.
  • mapping relationship is a mapping relationship between the UL grant type and the logical channel group
  • the mapping relationship is represented by a logical channel group (ie, a set of multiple logical channels).
  • the mapping information with the UL grant type for example, uniformly maps multiple logical channels to one or more UL grant types.
  • mapping relationship in step 202 may be determined by the user terminal, the network device determines, or the protocol is agreed.
  • the mapping relationship in step 202 is determined by the user terminal.
  • each user terminal can determine its own mapping relationship.
  • the mapping relationship can be sent to the currently accessed network device by signaling to notify the network device.
  • the user terminal may send the mapping relationship to the network device by using the high layer signaling or the physical layer signaling, where the high layer signaling may be an RRC (Radio Resource Control) or MAC (media access control) signaling.
  • the user terminal may also update the mapping relationship. After the mapping relationship is updated, the updated mapping relationship needs to be sent to the network device.
  • the mapping relationship in step 202 is determined by the network device.
  • the network device can configure a mapping relationship for each user terminal that is accessed, and send the mapping relationship to the corresponding user terminal.
  • the network device may send the mapping relationship to the user terminal by using high layer signaling or physical layer signaling.
  • the high layer signaling may be RRC or MAC signaling.
  • the network device can also update the mapping relationship. After the mapping relationship is updated, the updated mapping relationship needs to be sent to the user terminal.
  • the mapping relationship in step 202 is agreed by the protocol.
  • the foregoing mapping relationship may be agreed in the user equipment and the network device by using a protocol, and the user terminal may obtain the mapping relationship agreed by the protocol to perform step 202.
  • the target object with data to be sent may be filtered according to the LCP restriction, and the correspondence between the target object and the UL grant may be determined.
  • Each target object is provided with a corresponding LCP restriction, and the LCP restriction includes at least a mapping relationship between the target object and the UL grant type.
  • resource allocation is performed on each UL grant. Specifically, the resource allocation process on each UL grant is the same as LTE.
  • the first round of resource allocation is first performed according to the priority of the logical channel that can use the UL grant, the PRB requirement of the logical channel is satisfied, and then there are remaining resources, then the second round of resource allocation is performed, and resources are allocated for the remaining data until the resource Depleted or all data is allocated resources.
  • the service type is one of a voice over Internet Protocol (VOIP) service, a highly reliable low latency URLLC service, and an enhanced broadband communication eMBB service.
  • VOIP voice over Internet Protocol
  • URLLC highly reliable low latency
  • eMBB enhanced broadband communication
  • mapping relationship is as follows:
  • mapping relationship when the mapping relationship is a mapping relationship between a service type and a UL grant type, the mapping relationship may include:
  • the mapping relationship when the mapping relationship is a mapping relationship between a logical channel and a UL grant type, the mapping relationship may include: a logical channel number and a UL grant mapping.
  • the logical channel corresponding to the VOIP service and the dynamically scheduled UL grant and/or the semi-persistently scheduled UL grant mapping; the logical channel corresponding to the URLLC service and the dynamically scheduled UL grant and/or the UL grant mapping of the unlicensed scheduling; the eMBB service The corresponding logical channel is mapped with the dynamically scheduled UL grant.
  • the mapping relationship when the mapping relationship is a mapping relationship between a logical channel group and a UL grant type, the mapping relationship may include: a logical channel group number and a UL grant mapping.
  • the logical channel corresponding to the VOIP service and the dynamically scheduled UL grant and/or the semi-persistently scheduled UL grant mapping; the logical channel corresponding to the URLLC service and the dynamically scheduled UL grant and/or the UL grant mapping of the unlicensed scheduling; the eMBB service The corresponding logical channel is mapped with the dynamically scheduled UL grant.
  • the foregoing LCP restriction may further include one or a combination of: SCS, PUSCH transmission duration, and Cell.
  • LCP restriction includes at least a mapping relationship between a target object and a UL grant type, the target object being a service type or a logical channel or a logical channel group. Since the UL grant type is added to the LCP restriction, the UL grant type is mapped to the target object, so that the correspondence between the target object and the UL grant is first determined in the LCP process, and then the correspondence between the target object and the UL grant is determined. Resource allocation is performed on each of the UL grants. Therefore, the embodiments of the present disclosure can ensure that data transmitted on each UL grant is data expected by the network side, thereby improving scheduling performance.
  • an implementation flowchart of an uplink data packet resource allocation method includes:
  • Step 301 The network device determines, for each user terminal, a mapping relationship between a UL grant type of each user terminal and a service type, a logical channel, or a logical channel group, and notifies the corresponding user terminal.
  • the network device may notify the user terminal by using high layer signaling (RRC or MAC signaling) or physical layer signaling, and allow the network to change the mapping relationship. If the mapping relationship changes, the network is required. The device re-notifies the user terminal.
  • the user terminal can have multiple parallel services, including VOIP, URLLC, and eMBB.
  • the above mapping relationship can adopt the following mapping relationship:
  • Step 302 When the user terminal has data to transmit, perform LCP.
  • the user terminal has two logical channels (logical channel 1 and logical channel 2) having data to be transmitted, logical channel 1 corresponding to VOIP service data to be transmitted, and logical channel 2 corresponding to eMBB service data to be transmitted, and accepted.
  • logical channel 1 and logical channel 2 having data to be transmitted
  • logical channel 1 corresponding to VOIP service data to be transmitted
  • logical channel 2 corresponding to eMBB service data to be transmitted
  • UL grants grant1 is SPS grant and grant2 is dynamically scheduled UL grant.
  • the first step determines the correspondence between the logical channel and the UL grant according to the LCP restriction (ie, the correspondence between logical channel 1 and grant1 and grant2, and the correspondence between logical channel 2 and grant1 and grant2).
  • the LCP restriction includes the foregoing mapping relationship, and may further include one or a combination of the following: SCS, PUSCH transmission duration, and Cell.
  • the LCP restriction can determine the correspondence between the logical channel and the UL grant by filtering the logical channel that the user terminal needs to send data. Assume that the corresponding correspondence is as follows:
  • Logical channel 1 is mapped to grant 1 and grant 2;
  • Logical channel 2 is mapped to grant 2.
  • resource allocation is performed on each UL grant according to the correspondence between the logical channel and the UL grant.
  • the resource allocation process on each UL grant is the same as LTE. That is, the first round of resource allocation is first performed according to the priority of the logical channel that can use the UL grant, the PRB requirement of the logical channel is satisfied, and then there are remaining resources, then the second round of resource allocation is performed, and resources are allocated for the remaining data until the resource Depleted or all data is allocated resources.
  • an implementation flowchart of an uplink data packet resource allocation method includes:
  • Step 401 The user terminal determines the mapping relationship between the UL grant type and the service type, the logical channel, or the logical channel group, and notifies the network device.
  • the user terminal may notify the network device by using high layer signaling (RRC or MAC signaling) or physical layer signaling, and allow the network to change the mapping relationship. If the mapping relationship changes, the user is required.
  • the terminal re-notifies the network device.
  • the user terminal can have multiple parallel services, including VOIP, URLLC, and eMBB.
  • the above mapping relationship can adopt the following mapping relationship:
  • the step 402 is the same as the step 401 in the first embodiment. For details, refer to the description in the first embodiment, and details are not described herein again.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • Step 501 The user terminal and the network device determine, according to the protocol agreement, a mapping relationship between the UL grant type of each user terminal and a service type, a logical channel, or a logical channel group.
  • mapping relationship in this step is determined by the user terminal and the network device according to the protocol agreement.
  • the terminal has multiple parallel services, such as VOIP, URLLC and eMBB.
  • the protocol can stipulate the mapping relationship between the UL grant type and the service type, logical channel or logical channel group.
  • the above mapping relationship can adopt the following mapping relationship:
  • the step 502 is the same as the step 301 in the first embodiment. For details, refer to the description in the first embodiment, and details are not described herein again.
  • FIG. 6 is a schematic structural diagram of a user terminal according to an embodiment of the present disclosure. As shown in FIG. 6, the user terminal 600 includes:
  • the receiving module 601 is configured to receive at least one uplink grant information UL grant sent by the network device;
  • a determining module 602 configured to determine, according to a logical channel priority limiting factor LCP restriction corresponding to the target object, a correspondence between the target object and the UL grant;
  • a resource allocation module 603, configured to perform resource allocation on each of the UL grants according to a correspondence between the target object and the UL grant;
  • the LCP restriction includes at least a mapping relationship between a target object and a UL grant type, where the target object is a service type or a logical channel or a logical channel group.
  • the mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the user terminal, or determined by a network device or agreed by a protocol.
  • the network device when the mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the network device, the network device sends the mapping relationship to the user by using high layer signaling or physical layer signaling. terminal;
  • the user terminal when the mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the user terminal, the user terminal further includes: a sending module, configured to use high layer signaling or physical layer signaling The mapping relationship is sent to the network device.
  • a sending module configured to use high layer signaling or physical layer signaling The mapping relationship is sent to the network device.
  • the service type is one of an IP-based voice VOIP service, a high-reliability low-latency URLLC service, and an enhanced broadband communication eMBB service.
  • the UL grant type is one of dynamic scheduling, unauthorized scheduling, and semi-persistent scheduling.
  • the LCP restriction further includes one or a combination of: a subcarrier spacing SCS, a physical uplink shared channel transmission duration PUSCH transmission duration, and a cell Cell.
  • the user terminal 600 may be a user terminal in any embodiment of the method in the embodiment of the disclosure, and any implementation manner of the user terminal in the method embodiment of the disclosure may be used in this embodiment.
  • the foregoing user terminal 600 in the embodiment is implemented, and the same beneficial effects are achieved, and details are not described herein again.
  • FIG. 7 is a structural diagram of another user terminal according to an embodiment of the present disclosure.
  • the user terminal includes: a transceiver 720, a memory 710, a processor 700, and a memory stored in the memory.
  • a program on 710 and operable on the processor 700 wherein:
  • the transceiver is configured to receive at least one uplink grant information UL grant sent by the network device;
  • the processor is configured to read a program in the memory, and perform the following process: determining, according to a logical channel priority limiting factor LCP restriction corresponding to the target object, a correspondence between the target object and the UL grant; and determining, according to the target object a resource allocation on each of the UL grants, where the LCP restriction includes at least a mapping relationship between a target object and a UL grant type, where the target object is a service type or a logical channel or Logical channel group.
  • the transceiver 720 is configured to receive and transmit data under the control of the processor 700.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 700 and various circuits of memory represented by memory 710.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 720 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 700 is responsible for managing the bus architecture and general processing, and the memory 710 can store data used by the processor 700 in performing operations.
  • the memory 710 does not limit one device only on the user terminal, and the memory 710 and the processor 700 may be separated in different geographical locations in the future.
  • mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the user terminal, or determined by a network device or agreed by a protocol.
  • the network device when the mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the network device, the network device sends the mapping relationship to the user by using high layer signaling or physical layer signaling. terminal;
  • the transceiver is further configured to send the mapping relationship by using high layer signaling or physical layer signaling.
  • the network device when the mapping relationship between the target object and the UL grant type included in the LCP restriction is determined by the user terminal, the transceiver is further configured to send the mapping relationship by using high layer signaling or physical layer signaling.
  • the service type is one of an IP-based voice VOIP service, a high-reliability low-latency URLLC service, and an enhanced broadband communication eMBB service.
  • the UL grant type is one of dynamic scheduling, unauthorized scheduling, and semi-persistent scheduling.
  • the LCP restriction further includes one or a combination of: a subcarrier spacing SCS, a physical uplink shared channel transmission duration PUSCH transmission duration, and a cell Cell.
  • the foregoing user terminal may be a user terminal in any embodiment of the method in the embodiment of the disclosure, and any implementation manner of the user terminal in the method embodiment in the embodiment of the disclosure may be implemented by the implementation.
  • the above-mentioned user terminal in the example is implemented, and the same beneficial effects are achieved, and details are not described herein again.
  • the embodiment of the present disclosure further provides a computer readable storage medium, where the computer program is stored, and when the program is executed by the processor, the steps in the uplink data resource allocation method provided by the embodiment of the present disclosure are implemented.
  • 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 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, and the program code can be stored. Medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开实施例提供一种上行数据包资源分配方法和用户终端，该方法包括：接收网络设备发送的至少一个上行授权信息UL grant；根据目标对象对应的逻辑信道优先级限制因素LCP restriction，确定所述目标对象和所述ULgrant的对应关系，根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。

Description

上行数据包资源分配方法和用户终端
相关申请的交叉引用
本申请主张在2017年11月3日在中国提交的中国专利申请号No.201711071243.4的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种上行数据包资源分配方法和用户终端。
背景技术
在长期演进(Long Term Evolution，LTE)系统的LCP(Logical Channel Prioritization，逻辑信道优先级)过程中，LTE系统的LCP是基于网络配置的单一的RB(Radio Bearer,无线承载)对应的优先级参数priority进行的。具体执行过程如下：首先，按照所有有令牌的逻辑信道的优先级参数priority降序的顺序进行第一轮资源分配。第一轮资源分配基于每个逻辑信道的PBR(Prioritized Bit Rate，优先化比特速率)进行。同时根据资源分配情况更新每个逻辑信道可用的令牌数。然后，如果还有剩余资源，那么进行第二轮资源分配。第二轮资源分配是按照所有有数据传输的逻辑信道的优先级参数priority降序的顺序分配为PBR之外的数据分配资源。资源分配以所有有令牌的逻辑信道的数据都分配了资源或者资源耗尽为止。
然而，在以后的通信系统，例如：5G新空口(New Radio，NR)通信系统中，主要支持三类业务：eMBB(enhanced Mobile Broadband,增强型宽带通信)业务、mMTC(massive Machine Type Communications，大量机器类型通信)业务和URLLC(Ultra-Reliable and Low Latency Communications，高可靠低时延通信)业务。对于NR系统，目前将LCP需要考虑的限制因素称为LCP restriction，相关技术中的LCP restriction主要包括SCS(Sub-Carrier Space,子载波间隔)、PUSCH transmission duration(物理上行共享信道传输时长，其本质和传输时间间隔(Transmission Time Interval，TTI)是一样的)和小区Cell。 但是由于NR系统中不同的业务对应的延时需求不同，若仅考虑相关技术中的LCP restriction，将会使得调度性能受限。
发明内容
本公开实施例提供一种上行数据包资源分配方法和用户终端，以解决调度性能受限的问题。
本公开实施例提供一种上行数据包资源分配方法，应用于用户终端，包括：
接收网络设备发送的至少一个上行授权信息UL grant；
根据目标对象对应的逻辑信道优先级限制因素LCP restriction，确定所述目标对象和所述UL grant的对应关系；
根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；
其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。
可选的，所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定，或者由网络设备确定或者协议约定。
可选的，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由网络设备确定时，所述网络设备通过高层信令或物理层信令将所述映射关系发送给所述用户终端；
或者，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定时，所述方法还包括：通过高层信令或物理层信令将所述映射关系发送给所述网络设备。
可选的，所述业务类型为基于IP的语音VOIP业务，高可靠低时延URLLC业务和增强型宽带通信eMBB业务之中的一种。
可选的，所述UL grant类型为动态调度、免授权调度和半持续调度之中的一种。
可选的，所述LCP restriction还包括如下之一或者组合：子载波间隔SCS、物理上行共享信道传输时长PUSCH transmission duration和小区Cell。
本公开实施例还提供一种用户终端，包括：
接收模块，用于接收网络设备发送的至少一个上行授权信息UL grant；
确定模块，用于根据目标对象对应的逻辑信道优先级限制因素LCP restriction，确定所述目标对象和所述UL grant的对应关系；
资源分配模块，用于根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；
其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。
可选的，所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定，或者由网络设备确定或者协议约定。
可选的，所述业务类型为基于IP的语音VOIP业务，高可靠低时延URLLC业务和增强型宽带通信eMBB业务之中的一种。
可选的，所述UL grant类型为动态调度、免授权调度和半持续调度之中的一种。
本公开实施例还提供一种用户终端，收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序；
所述收发机用于接收网络设备发送的至少一个上行授权信息UL grant；
所述处理器用于读取存储器中的程序，执行下列过程：根据目标对象对应的逻辑信道优先级限制因素LCP restriction，确定所述目标对象和所述UL grant的对应关系；以及根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。
可选的，所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定，或者由网络设备确定或者协议约定。
可选的，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由网络设备确定时，所述网络设备通过高层信令或物理层信令将所述映射关系发送给所述用户终端；
或者，当所述LCP restriction中包含的目标对象和UL grant类型的映射关 系由所述用户终端确定时，所述收发机还用于通过高层信令或物理层信令将所述映射关系发送给所述网络设备。
可选的，所述业务类型为基于IP的语音VOIP业务，高可靠低时延URLLC业务和增强型宽带通信eMBB业务之中的一种。
可选的，所述UL grant类型为动态调度、免授权调度和半持续调度之中的一种。
可选的，所述LCP restriction还包括如下之一或者组合：子载波间隔SCS、物理上行共享信道传输时长PUSCH transmission duration和小区Cell。
本公开实施例还提供一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现本公开实施例提供的上行数据包资源分配方法中的步骤。
本公开实施例中，接接收网络设备发送的至少一个上行授权信息UL grant；根据目标对象对应的逻辑信道优先级限制因素LCP restriction，确定所述目标对象和所述UL grant的对应关系；根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。由于在LCP restriction中增加了UL grant类型的考虑，将目标对象进行映射，从而在LCP的过程中首先确定目标对象和UL grant的对应关系，然后根据目标对象和UL grant的对应关系，在每个UL grant上进行资源分配。因此，本公开实施例可以保证各个UL grant上传输的数据是网络侧期望的数据，从而提升了调度的性能。
附图说明
图1是本公开实施例可应用的网络结构示意图；
图2是本公开实施例提供的一种上行数据包资源分配方法的流程图；
图3是本公开实施例提供上行数据包资源分配方法的实现流程图之一；
图4是本公开实施例提供上行数据包资源分配方法的实现流程图之二；
图5是本公开实施例提供上行数据包资源分配方法的实现流程图之三；
图6是本公开实施例提供的一种用户终端的结构图；
图7是本公开实施例提供的另一种用户终端的结构图。
具体实施方式
参见图1，图1是本公开实施例可应用的网络结构示意图，如图1所示，包括用户终端(User Equipment，UE)11和网络设备12，其中，用户终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、个人数字助理(personal digital assistant，简称PDA)、移动上网装置(Mobile Internet Device，MID)或可穿戴式设备(Wearable Device)等终端侧设备，需要说明的是，在本公开实施例中并不限定用户终端11的具体类型。网络设备12可以是基站，例如：宏站、LTE eNB、5G NR NB等；网络设备12也可以是小站，如低功率节点(LPN：low power node)pico、femto等小站，或者网络设备12可以接入点(AP，access point)；基站也可以是中央单元(CU，central unit)与其管理是和控制的多个传输接收点(TRP，Transmission Reception Point)共同组成的网络节点。需要说明的是，在本公开实施例中并不限定网络设备12的具体类型。
请参见图2，图2是本公开实施例提供的一种上行数据包资源分配方法的流程图，本公开实施例提供的上行数据包资源分配方法应用于用户终端，用于控制用户终端上行数据包资源分配，如图2所示，该上行数据包资源分配方法包括以下步骤：
201、接收网络设备发送的至少一个上行授权信息UL grant；
202、根据目标对象对应的逻辑信道优先级限制因素LCP restriction确定所述目标对象和所述UL grant的对应关系；
203、根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；
其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。
在用户终端接入网络设备后，通常由网络设备向用户终端发送指示信息，以指示用户终端进行上行传输，该指示信息中携带有上述UL grant，用户终端可以根据网络设备发送的UL grant，在有上行数据发送时，将会执行如步 骤202和203所示的LCP过程。
应理解，上述UL grant类型可以根据实际需要进行设置，在本实施例中UL grant类型为动态调度、免授权调度grant-free和半持续调度SPS(Semi-Persistent Scheduling)之中的一种。网络设备发送的UL grant的数量可以根据实际需要进行设置，在此不做进一步的限定，该发送的每一UL grant的类型可以为动态调度、免授权调度和半持续调度之中的一种。例如用户终端接收到的网络设备发送的两个UL grant，其中一个UL grant可以为动态调度的UL grant，另一个UL grant为SPS grant。
上述映射关系可以为UL grant类型与业务类型的映射关系，也可以为UL grant类型与逻辑信道的映射关系，还可以为UL grant类型与逻辑信道组的映射关系。其中，当上述映射关系为业务类型与逻辑信道的映射关系时，该映射关系表现为具体的业务与UL grant类型的映射信息；当上述映射关系为UL grant类型与逻辑信道的映射关系时，该映射关系表现为逻辑信道编号与UL grant类型的映射信息；当上述映射关系为UL grant类型与逻辑信道组的映射关系时，该映射关系表现为逻辑信道组(即多个逻辑信道的集合)编号与UL grant类型的映射信息，例如，将多个逻辑信道统一与一个或多个UL grant类型进行映射。
需要说明的是，上述步骤202中的映射关系的确定方式可以存在多种实现方式，例如步骤202中映射关系可以由所述用户终端确定、所述网络设备确定或者协议约定。
在第一实施方式中，步骤202中的映射关系为所述用户终端确定。这里，各用户终端可以自行决定自身的映射关系，在确定了映射关系后，可以通过信令的方式向当前接入的网络设备发送映射关系，以通知网络设备。具体地，本实施例中，用户终端可以通过高层信令或物理层信令向所述网络设备发送所述映射关系，其中，高层信令可以为RRC(Radio Resource Control，无线资源控制协议)或者MAC(media access control，媒体接入控制)信令。另外，用户终端还可以对映射关系进行更新，在进行映射关系更新后，同样也需要将更新后的映射关系发送给网络设备。
在第二实施方式中，步骤202中的映射关系由所述网络设备确定。这里 网络设备可以为接入的各用户终端配置映射关系，并发送至相应的用户终端。该网络设备可以通过高层信令或物理层信令向所述用户终端发送所述映射关系。其中，高层信令可以为RRC或者MAC信令。另外，网络设备还可以对映射关系进行更新，在进行映射关系更新后，同样也需要将更新后的映射关系发送给用户终端。
在第三实施方式中，步骤202中的映射关系由协议约定。这里，可以预先通过协议在用户设备和网络设备中约定上述映射关系，用户终端可以获取协议约定的映射关系以执行步骤202。
在上述步骤202中可以根据LCP restriction对有数据需要发送的目标对象进行筛选，即可确定目标对象和UL grant的对应关系。其中，每一目标对象均设有对应的LCP restriction，该LCP restriction中至少包括该目标对象与UL grant类型的映射关系。然后根据目标对象和UL grant的对应关系，在每个UL grant上进行资源分配。具体的，每个UL grant上的资源分配过程和LTE一样。即首先根据能够使用该UL grant的逻辑信道的优先级进行第一轮资源分配，满足逻辑信道的PRB需求，然后还有剩余资源，则进行第二轮资源分配，为剩余数据分配资源，直到资源耗尽或者所有数据都分配了资源。
可选的，业务类型为基于IP的语音VOIP(Voice over Internet Protocol)业务，高可靠低时延URLLC业务和增强型宽带通信eMBB业务之中的一种。
应当说明的是，上述映射关系中具体的映射内容可以根据实际需要进行设置，本实施例中，为了保证业务的服务质量QoS，对映射关系作出如下约定，具体的，
在第一种情况中，当上述映射关系为业务类型与UL grant类型之间的映射关系时，该映射关系可以包括：
VOIP业务与动态调度的UL grant和/或半静态调度的UL grant映射；
URLLC业务与动态调度的UL grant和/或免授权调度的UL grant映射；
eMBB业务与动态调度的UL grant映射。
在第二种情况中，当上述映射关系为逻辑信道与UL grant类型之间的映射关系时，该映射关系可以包括：逻辑信道编号与UL grant映射。
其中，VOIP业务对应的逻辑信道与动态调度的UL grant和/或半静态调 度的UL grant映射；URLLC业务对应的逻辑信道与动态调度的UL grant和/或免授权调度的UL grant映射；eMBB业务对应的逻辑信道与动态调度的UL grant映射。
在第三种情况中，当上述映射关系为逻辑信道组与UL grant类型之间的映射关系时，该映射关系可以包括：逻辑信道组编号与UL grant映射。
其中，VOIP业务对应的逻辑信道与动态调度的UL grant和/或半静态调度的UL grant映射；URLLC业务对应的逻辑信道与动态调度的UL grant和/或免授权调度的UL grant映射；eMBB业务对应的逻辑信道与动态调度的UL grant映射。
应理解，在执行LCP的过程中，除了需要考虑UL grant类型这一LCP restriction，还可以考虑其他的LCP restriction。例如，在本实施例中，上述LCP restriction还可以包括如下之一或者组合：SCS、PUSCH transmission duration和Cell。
需要说明的是，本公开实施例中介绍的多种可选的实施方式，彼此可以相互结合实现，也可以单独实现，对此本公开实施例不作限定。
本公开实施例中，接收网络设备发送的至少一个上行授权信息UL grant；
根据目标对象对应的逻辑信道优先级限制因素LCP restriction，确定所述目标对象和所述UL grant的对应关系；根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。由于在LCP restriction中增加了UL grant类型的考虑，将UL grant类型与目标对象进行映射，从而在LCP的过程中首先确定目标对象和UL grant的对应关系，然后根据目标对象和UL grant的对应关系，在每个所述UL grant上进行资源分配。因此，本公开实施例可以保证各个UL grant上传输的数据是网络侧期望的数据，从而提升了调度的性能。
为了更好的理解本公开，以下通过具体的实施方式进行详细说明：
实施方式一，如图3所示，上行数据包资源分配方法的实现流程图包括：
步骤301，网络设备针对每个用户终端确定各用户终端的UL grant类型与业务类型、逻辑信道或逻辑信道组的映射关系，并通知相应的用户终端。
该步骤中，网络设备确定映射关系后，可以通过高层信令(RRC或者MAC信令)或者物理层信令通知给用户终端，并且允许网络变更该映射关系，如果映射关系发生变更，则需要网络设备重新通知给用户终端。其中用户终端可以有多种并行业务，比如包括VOIP，URLLC和eMBB。上述映射关系可以采用以下映射关系：
VOIP业务与动态调度的UL grant和/或半静态调度的UL grant映射；
URLLC业务与动态调度的UL grant和/或免授权调度的UL grant映射；
eMBB业务与动态调度的UL grant映射。
步骤302：用户终端有数据需要传输时，执行LCP。
该步骤中，假设用户终端有两个逻辑信道(逻辑信道1和逻辑信道2)有数据要发送，逻辑信道1对应VOIP的业务数据要发送，逻辑信道2对应eMBB的业务数据要发送，并且接受到两种类型的UL grant(grant1为SPS grant，grant2为动态调度的UL grant)。
在执行LCP的过程中，第一步根据LCP restriction确定逻辑信道和UL grant的对应关系(即逻辑信道1与grant1及grant2的对应关系，以及逻辑信道2与grant1及grant2的对应关系)。
其中，LCP restriction包括上述映射关系，此外还可以包括如下之一或者组合：SCS、PUSCH transmission duration和Cell。
在第一步中，上述LCP restriction对用户终端有数据需要发送的逻辑信道进行筛选就可以确定逻辑信道和UL grant的对应关系。假设确定出来的对应关系如下：
逻辑信道1与grant 1及grant 2映射；
逻辑信道2与grant 2映射。
第二步，根据逻辑信道和UL grant的对应关系在每个UL grant上进行资源分配。
该步骤中，每个UL grant上的资源分配过程和LTE一样。即首先根据能够使用该UL grant的逻辑信道的优先级进行第一轮资源分配，满足逻辑信道的PRB需求，然后还有剩余资源，则进行第二轮资源分配，为剩余数据分配资源，直到资源耗尽或者所有数据都分配了资源。
实施方式二，如图4所示，上行数据包资源分配方法的实现流程图包括：
步骤401，用户终端自行确定UL grant类型与业务类型、逻辑信道或逻辑信道组的映射关系，并通知网络设备。
该步骤中，用户终端确定映射关系后，可以通过高层信令(RRC或者MAC信令)或者物理层信令通知给网络设备，并且允许网络变更该映射关系，如果映射关系发生变更，则需要用户终端重新通知给网络设备。其中用户终端可以有多种并行业务，比如包括VOIP，URLLC和eMBB。上述映射关系可以采用以下映射关系：
VOIP业务与动态调度的UL grant和/或半静态调度的UL grant映射；
URLLC业务与动态调度的UL grant和/或免授权调度的UL grant映射；
eMBB业务与动态调度的UL grant映射。
步骤402与实施方式一中的步骤401一致，具体可以参见实施方式一中的表述，在此不再赘述。
实施方式三：
步骤501，用户终端和网络设备根据协议约定确定该各用户终端的UL grant类型与业务类型、逻辑信道或逻辑信道组的映射关系。
该步骤中映射关系由用户终端和网络设备根据协议约定确定。例如终端有多种并行业务，比如包括VOIP，URLLC和eMBB。那么协议可以约定UL grant类型与业务类型、逻辑信道或逻辑信道组的映射关系。上述映射关系可以采用以下映射关系：
VOIP业务与动态调度的UL grant和/或半静态调度的UL grant映射；
URLLC业务与动态调度的UL grant和/或免授权调度的UL grant映射；
eMBB业务与动态调度的UL grant映射。
步骤502与实施方式一中的步骤301一致，具体可以参见实施方式一中的表述，在此不再赘述。
请参见图6，图6是本公开实施例提供的一种用户终端的结构示意图，如图6所示，用户终端600包括：
接收模块601，用于接收网络设备发送的至少一个上行授权信息UL grant；
确定模块602，用于根据目标对象对应的逻辑信道优先级限制因素LCP  restriction，确定所述目标对象和所述UL grant的对应关系；
资源分配模块603，用于根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；
其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。
可选的，当所述网络设备发送的映射关系时，所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定，或者由网络设备确定或者协议约定。
可选的，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由网络设备确定时，所述网络设备通过高层信令或物理层信令将所述映射关系发送给所述用户终端；
或者，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定时，所述用户终端还包括：发送模块，用于通过高层信令或物理层信令将所述映射关系发送给所述网络设备。
可选的，所述业务类型为基于IP的语音VOIP业务，高可靠低时延URLLC业务和增强型宽带通信eMBB业务之中的一种。
可选的，所述UL grant类型为动态调度、免授权调度和半持续调度之中的一种。
可选的，所述LCP restriction还包括如下之一或者组合：子载波间隔SCS、物理上行共享信道传输时长PUSCH transmission duration和小区Cell。
需要说明的是，本实施例中上述用户终端600可以是本公开实施例中方法实施例中任意实施方式的用户终端，本公开实施例中方法实施例中用户终端的任意实施方式都可以被本实施例中的上述用户终端600所实现，以及达到相同的有益效果，此处不再赘述。
请参考图7，图7是本公开实施例提供的另一种用户终端的结构图，如图7所示，该用户终端包括：收发机720、存储器710、处理器700及存储在所述存储器710上并可在所述处理器700上运行的程序，其中：
所述收发机用于接收网络设备发送的至少一个上行授权信息UL grant；
所述处理器用于读取存储器中的程序，执行下列过程：根据目标对象对 应的逻辑信道优先级限制因素LCP restriction，确定所述目标对象和所述UL grant的对应关系；以及根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。
上述收发机720用于在处理器700的控制下接收和发送数据。
在图7中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器700代表的一个或多个处理器和存储器710代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机720可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。
处理器700负责管理总线架构和通常的处理，存储器710可以存储处理器700在执行操作时所使用的数据。
需要说明的是，存储器710并不限定只在用户终端上的一种设备，可以将来存储器710和处理器700分离处于不同的地理位置。
可选的，所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定，或者由网络设备确定或者协议约定。
可选的，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由网络设备确定时，所述网络设备通过高层信令或物理层信令将所述映射关系发送给所述用户终端；
或者，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定时，所述收发机还用于通过高层信令或物理层信令将所述映射关系发送给所述网络设备。
可选的，所述业务类型为基于IP的语音VOIP业务，高可靠低时延URLLC业务和增强型宽带通信eMBB业务之中的一种。
可选的，所述UL grant类型为动态调度、免授权调度和半持续调度之中的一种。
可选的，所述LCP restriction还包括如下之一或者组合：子载波间隔SCS、 物理上行共享信道传输时长PUSCH transmission duration和小区Cell。
需要说明的是，本实施例中上述用户终端可以是本公开实施例中方法实施例中任意实施方式的用户终端，本公开实施例中方法实施例中用户终端的任意实施方式都可以被本实施例中的上述用户终端所实现，以及达到相同的有益效果，此处不再赘述。
本公开实施例还提供一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现本公开实施例提供的上行数据包资源分配方法中的步骤。
在本申请所提供的几个实施例中，应该理解到，所揭露方法和装置，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述收发方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述是本公开的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本公开所述原理的前提下，还可以作出若干改进和润饰，这些改进和润饰也应视为本公开的保护范围。

Claims (15)

  1. 一种上行数据包资源分配方法，应用于用户终端，包括：
    接收网络侧设备发送的至少一个上行授权信息UL grant；
    根据目标对象对应的逻辑信道优先级限制因素LCP restriction，确定所述目标对象和所述UL grant的对应关系；
    根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；
    其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。
  2. 如权利要求1所述的方法，其中，所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定，或者由网络设备确定或者协议约定。
  3. 根据权利要求2所述的方法，其中，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由网络设备确定时，所述网络设备通过高层信令或物理层信令将所述映射关系发送给所述用户终端；
    或者，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定时，所述方法还包括：通过高层信令或物理层信令将所述映射关系发送给所述网络设备。
  4. 根据权利要求1所述的方法，其中，所述业务类型为基于IP的语音VOIP业务，高可靠低时延URLLC业务和增强型宽带通信eMBB业务之中的一种。
  5. 根据权利要求1所述的方法，其中，所述UL grant类型为动态调度、免授权调度和半持续调度之中的一种。
  6. 一种用户终端，包括：
    接收模块，用于接收网络设备发送的至少一个上行授权信息UL grant；
    确定模块，用于根据目标对象对应的逻辑信道优先级限制因素LCP restriction，确定所述目标对象和所述UL grant的对应关系；
    资源分配模块，用于根据所述目标对象和所述UL grant的对应关系，在 每个所述UL grant上进行资源分配；
    其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。
  7. 如权利要求6所述的用户终端，其中，所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定，或者由网络设备确定或者协议约定。
  8. 根据权利要求6所述的用户终端，其中，所述业务类型为基于IP的语音VOIP业务，高可靠低时延URLLC业务和增强型宽带通信eMBB业务之中的一种。
  9. 根据权利要求6所述的用户终端，其中，所述UL grant类型为动态调度、免授权调度和半持续调度之中的一种。
  10. 一种用户终端，包括：收发机、存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序；其中，
    所述收发机用于接收网络设备发送的至少一个上行授权信息UL grant；
    所述处理器用于读取存储器中的程序，执行下列过程：根据目标对象对应的逻辑信道优先级限制因素LCP restriction，确定所述目标对象和所述UL grant的对应关系；以及根据所述目标对象和所述UL grant的对应关系，在每个所述UL grant上进行资源分配；其中，所述LCP restriction至少包含目标对象和UL grant类型的映射关系，所述目标对象为业务类型或逻辑信道或逻辑信道组。
  11. 根据权利要求10所述的用户终端，其中，所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定，或者由网络设备确定或者协议约定。
  12. 根据权利要求11所述的用户终端，其中，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由网络设备确定时，所述网络设备通过高层信令或物理层信令将所述映射关系发送给所述用户终端；
    或者，当所述LCP restriction中包含的目标对象和UL grant类型的映射关系由所述用户终端确定时，所述收发机还用于通过高层信令或物理层信令将所述映射关系发送给所述网络设备。
  13. 根据权利要求10所述的用户终端，其中，所述业务类型为基于IP的语音VOIP业务，高可靠低时延URLLC业务和增强型宽带通信eMBB业务之中的一种。
  14. 根据权利要求10所述的用户终端，其中，所述UL grant类型为动态调度、免授权调度和半持续调度之中的一种。
  15. 一种计算机可读存储介质，其上存储有计算机程序，其中，该程序被处理器执行时实现如权利要求1至5中任一项所述的上行数据包资源分配方法中的步骤。
PCT/CN2018/110458 2017-11-03 2018-10-16 上行数据包资源分配方法和用户终端 WO2019085741A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
US16/760,660 US11706756B2 (en) 2017-11-03 2018-10-16 Method of allocating uplink data packet resource and user equipment
KR1020207013719A KR20200064140A (ko) 2017-11-03 2018-10-16 상향링크 데이터 패킷 자원 할당 방법 및 사용자 단말기
KR1020247013780A KR20240058991A (ko) 2017-11-03 2018-10-16 상향링크 데이터 패킷 자원 할당 방법 및 사용자 단말기
EP18873382.8A EP3706488B1 (en) 2017-11-03 2018-10-16 Uplink data packet resource allocation method and user terminal
KR1020227040846A KR20220162850A (ko) 2017-11-03 2018-10-16 상향링크 데이터 패킷 자원 할당 방법 및 사용자 단말기
JP2020524588A JP7106639B2 (ja) 2017-11-03 2018-10-16 アップリンクデータパケットリソース割り当て方法およびユーザ端末
US18/174,922 US20230209540A1 (en) 2017-11-03 2023-02-27 Method of allocating uplink data packet resource and user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711071243.4A CN109756986B (zh) 2017-11-03 2017-11-03 一种上行数据包资源分配方法和用户终端
CN201711071243.4 2017-11-03

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/760,660 A-371-Of-International US11706756B2 (en) 2017-11-03 2018-10-16 Method of allocating uplink data packet resource and user equipment
US18/174,922 Continuation US20230209540A1 (en) 2017-11-03 2023-02-27 Method of allocating uplink data packet resource and user equipment

Publications (1)

Publication Number Publication Date
WO2019085741A1 true WO2019085741A1 (zh) 2019-05-09

Family

ID=66331301

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/110458 WO2019085741A1 (zh) 2017-11-03 2018-10-16 上行数据包资源分配方法和用户终端

Country Status (7)

Country Link
US (2) US11706756B2 (zh)
EP (1) EP3706488B1 (zh)
JP (1) JP7106639B2 (zh)
KR (3) KR20240058991A (zh)
CN (1) CN109756986B (zh)
TW (1) TWI692989B (zh)
WO (1) WO2019085741A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114828073A (zh) * 2021-01-29 2022-07-29 大唐移动通信设备有限公司 资源配置方法、装置、设备以及存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020003539A1 (ja) * 2018-06-29 2020-01-02 富士通株式会社 移動局、基地局、通信システム、及び通信方法
CN110838899B (zh) * 2018-08-16 2021-12-24 大唐移动通信设备有限公司 一种直接通信链路资源分配方法及终端
CN112200396B (zh) * 2019-07-08 2024-02-09 钉钉控股（开曼）有限公司 资源转移及分配方法、装置
US11671970B2 (en) * 2019-08-07 2023-06-06 Qualcomm Incorporated LCP restriction enhancement

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106998590A (zh) * 2015-12-28 2017-08-01 中国信息通信研究院 一种上行资源调度方法和装置
WO2017186160A1 (en) * 2016-04-29 2017-11-02 Huawei Technologies Co., Ltd. System and method for coexistence of grant-free and grant-based uplink traffic

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8873474B2 (en) * 2008-10-17 2014-10-28 Telefonaktiebolaget L M Ericsson (Publ) Method and mobile terminal providing priority-based uplink scheduling information
CN101873704A (zh) * 2009-04-24 2010-10-27 大唐移动通信设备有限公司 长期演进系统中资源调度方法、系统及设备
WO2013049769A1 (en) * 2011-09-30 2013-04-04 Interdigital Patent Holdings, Inc. Multipoint transmission in wireless communication
US9591661B2 (en) * 2012-11-09 2017-03-07 Apple Inc. Reducing scheduling requests by a wireless communication device transmitting voice data over dynamically scheduled resources
US9661653B2 (en) * 2014-05-08 2017-05-23 Intel IP Corporation Device to-device (D2D) communications
EP3244680B1 (en) 2015-01-29 2019-12-04 Huawei Technologies Co., Ltd. Data transmission method and device
US20160226632A1 (en) * 2015-01-29 2016-08-04 Intel IP Corporation Carrier aggregation enhancements for unlicensed spectrum and 5g
US10405336B2 (en) * 2015-04-09 2019-09-03 Lg Electronics Inc. Method for performing a logical channel prioritization in a carrier aggregation with at least one SCell operating in an unlicensed spectrum and a device therefor
CN107079465B (zh) * 2015-08-28 2019-11-05 华为技术有限公司 一种通信方法、装置及系统
CN105451345B (zh) 2016-01-18 2020-07-14 中磊电子（苏州）有限公司 一种上行授权信息发送方法及基站
US10470204B2 (en) * 2016-08-10 2019-11-05 Ofinno, Llc Multiple semi persistent scheduling in a wireless network
CN106961741B (zh) * 2017-05-04 2019-11-22 电信科学技术研究院 一种上行资源分配方法和装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106998590A (zh) * 2015-12-28 2017-08-01 中国信息通信研究院 一种上行资源调度方法和装置
WO2017186160A1 (en) * 2016-04-29 2017-11-02 Huawei Technologies Co., Ltd. System and method for coexistence of grant-free and grant-based uplink traffic

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Consideration of Grant-free Transmission from LCP Perspective,", 3GPP TSG RAN WG2 #99BIS R2-1711597, 29 September 2017 (2017-09-29), XP051355644 *
See also references of EP3706488A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114828073A (zh) * 2021-01-29 2022-07-29 大唐移动通信设备有限公司 资源配置方法、装置、设备以及存储介质

Also Published As

Publication number Publication date
EP3706488A4 (en) 2020-11-18
CN109756986A (zh) 2019-05-14
US20230209540A1 (en) 2023-06-29
TW201919428A (zh) 2019-05-16
KR20200064140A (ko) 2020-06-05
US11706756B2 (en) 2023-07-18
KR20240058991A (ko) 2024-05-03
EP3706488A1 (en) 2020-09-09
EP3706488B1 (en) 2022-08-17
KR20220162850A (ko) 2022-12-08
JP2021501536A (ja) 2021-01-14
TWI692989B (zh) 2020-05-01
JP7106639B2 (ja) 2022-07-26
US20200351915A1 (en) 2020-11-05
CN109756986B (zh) 2021-07-13

Similar Documents

Publication Publication Date Title
WO2019085741A1 (zh) 上行数据包资源分配方法和用户终端
US11438918B2 (en) Scheduling request with different numerologies
KR101480598B1 (ko) 무선 네트워크에서 통신을 개시하기 위한 기법
WO2017035762A1 (zh) 资源分配方法及装置
WO2020192244A1 (zh) 一种通信方法和装置
TWI697239B (zh) 資源塊組的劃分方法和使用者終端
JP2020523924A (ja) リソースブロックグループサイズを決定するための方法および装置
WO2017215642A1 (zh) 一种资源分配方法、网络设备及终端设备
WO2020169063A1 (zh) 一种数据传输方法及通信装置
CN103814596A (zh) 传输数据的方法、装置和系统
CN110971349B (zh) 一种重复传输方法、终端和网络侧设备
US20190097771A1 (en) Indicating Contiguous Resource Allocation
CN108024341B (zh) 一种调度方法、终端及基站
US20220400502A1 (en) Policy-Based Resource Pool Allocation for Low-Latency IIOT and Other Applications
WO2021155604A1 (zh) 信息处理方法及设备
WO2018141091A1 (zh) 发送信息的方法、接收信息的方法和装置
CN111132223B (zh) 一种数据包的传输方法和通信设备
WO2019154010A1 (zh) 资源分配方法、终端和网络侧设备
WO2021023294A1 (zh) 信息传输方法及电子设备
WO2019137204A1 (zh) 控制资源集coreset的分配方法、用户终端和网络侧设备
WO2019091225A1 (zh) 跳频物理资源确定方法、用户终端和网络侧设备
WO2019157679A1 (zh) 一种信息指示方法及相关设备
WO2017185907A1 (zh) 一种共享物理资源的方法和装置
WO2023142120A1 (zh) 通信方法、装置、设备、芯片、存储介质、产品及程序
CN113840307B (zh) 请求发送方法、资源分配方法、终端和网络侧设备

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: 18873382

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020524588

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207013719

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018873382

Country of ref document: EP

Effective date: 20200603