WO2017193861A1 - 一种业务数据的传输方法、终端及网络侧设备 - Google Patents

一种业务数据的传输方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2017193861A1
WO2017193861A1 PCT/CN2017/082977 CN2017082977W WO2017193861A1 WO 2017193861 A1 WO2017193861 A1 WO 2017193861A1 CN 2017082977 W CN2017082977 W CN 2017082977W WO 2017193861 A1 WO2017193861 A1 WO 2017193861A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
service data
transmitted
scheduling
transmission
Prior art date
Application number
PCT/CN2017/082977
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 JP2018559776A priority Critical patent/JP6765446B2/ja
Priority to US16/090,579 priority patent/US11160092B2/en
Priority to EP17795479.9A priority patent/EP3457778B1/en
Priority to KR1020187036217A priority patent/KR102184035B1/ko
Publication of WO2017193861A1 publication Critical patent/WO2017193861A1/zh

Links

Images

Classifications

    • 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/50—Allocation or scheduling criteria for wireless resources
    • H04W72/51—Allocation or scheduling criteria for wireless resources based on terminal or device properties
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter
    • H04L7/04—Speed or phase control by synchronisation signals
    • H04L7/10—Arrangements for initial synchronisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1221—Wireless traffic scheduling based on age of data to be sent
    • 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
    • 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
    • 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/535—Allocation or scheduling criteria for wireless resources based on resource usage policies
    • 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/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method, an apparatus, and a network side device for transmitting service data.
  • the basic time unit of resource allocation and data transmission is TTI (transmission time interval).
  • TTI transmission time interval
  • the length of the TTI is 1 ms (hereinafter referred to as 1 ms TTI).
  • LTE in order to better support delay-sensitive services, LTE introduces a shorter TTI (hereinafter referred to as short TTI), and the short TTI length is less than 1 ms;
  • the uplink channel supporting the short TTI transmission includes at least a short physical uplink control channel (s-PUCCH, Short Physical Uplink Control CHannel) and a short physical uplink shared channel (s-PUSCH, Short Physical Uplink Shared CHannel);
  • the downlink channel of the TTI transmission includes at least a short physical downlink control channel (s-PDCCH, Short Physical Downlink Control CHannel) and a short physical downlink shared channel (s-PDSCH, Short Physical Downlink Shared CHannel).
  • RB Radio Bearer
  • Packets with different QoS requirements are mapped to different RBs for transmission. For example, a data packet of a voice service is mapped to a strict delay requirement, but a partial packet loss RB is allowed to be transmitted; a data packet of the ftp service is mapped to an RB whose delay requirement is low but the bit error rate is low.
  • the structure of the air interface protocol stack of the UE is as shown in FIG. 1.
  • the internal scheduling process of the UE includes: each RB corresponds to a pair of PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Layer Control Protocol) entities, and different RBs are Gather together and transmit through the physical layer (PHY).
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Layer Control Protocol
  • the MAC of the UE After the MAC of the UE receives the uplink scheduling signaling of the eNB:
  • the MAC is scheduled according to the size of the resources allocated by the eNB, the QoS requirements of the data packets of each RB, the amount of data, the queue waiting time, the historical transmission rate, etc. Which RBs are transmitted for data transmission and how much data is transmitted by each RB;
  • the MAC layer applies data of the corresponding data volume to the RLC and PDCP entities of the scheduled RBs, and aggregates them into one MAC PDU (packet data unit), and puts it into the sending buffer of the corresponding HARQ entity, and passes through the physical layer. , sent at the air interface;
  • the MAC entity transmits the data in the transmission buffer of the corresponding HARQ entity to the physical layer, and sends the data in the air interface.
  • a resource collision (hereinafter referred to as 1 ms TTI and short TTI collision) occurs.
  • the technical problem to be solved by the present disclosure is to provide a method for transmitting service data, a terminal, and a network side device.
  • the UE may perform the uplink data allocation of the eNB according to the delay requirement of the service data to be transmitted. Map on and transfer.
  • an embodiment of the present disclosure provides a method for transmitting a service data packet, including:
  • the service data to be transmitted is determined according to the delay requirement of the current service data packet to be transmitted.
  • the steps of mapping the packet to the uplink resource for transmission include:
  • mapping according to the judgment result, the to-be-transmitted service data packet to the second scheduling resource indicated by the second scheduling command received on or after the first scheduling resource, and transmitting;
  • the second transmission delay of the second scheduling resource is different from the first transmission delay of the first scheduling resource.
  • the first transmission delay is greater than the second transmission delay.
  • the step of mapping the to-be-transmitted service data packet to the first scheduling resource and performing the transmission according to the determining result includes:
  • the current to-be-transmitted service data packet except the The other to-be-transmitted service data packets to be transmitted are to be mapped to the first scheduling resource, and are transmitted in the first transmission delay.
  • the current to-be-transmitted service data packet further includes: a second to-be-transmitted service data packet having a second delay requirement, and the length of the second delay request is greater than the length of the first delay requirement, And mapping at least a part of the first to-be-transmitted service data packet and the second to-be-transmitted service data packet to the first scheduling resource, and transmitting in the first transmission delay.
  • the step of mapping the to-be-transmitted service data packet to the second scheduling resource indicated by the second scheduling command that is received later includes:
  • the first transmission delay of the first scheduling resource does not meet the first delay requirement of the first to-be-transmitted service data packet in the current to-be-transmitted service data packet, and then receives the second scheduling command indication sent by the network-side device And the second scheduling resource with the second transmission delay, and mapping the first to-be-transmitted service data packet to the second scheduling resource.
  • the method for transmitting the service data packet further includes:
  • the second scheduling resource indicated by the second scheduling command is received, if the current service data packet is to be transmitted Terminating the transmission of the first scheduling resource by mapping the second to-be-transmitted service data packet to the second to-be-transmitted service data packet, and mapping the second to-be-transmitted service data packet to the The second scheduling resource is transmitted and transmitted;
  • the second scheduling command is ignored.
  • the method for transmitting the service data packet further includes:
  • the second scheduling resource indicated by the command performs the transmission of the service data packet to be transmitted or the transmission of the service data packet to be transmitted on the contention resource by actively initiating the scheduling request of the uplink resource.
  • the step of mapping the to-be-transmitted service data packet to the uplink resource for transmission according to the delay requirement of the current service data packet to be transmitted includes:
  • the step of determining a to-be-transmitted service data packet corresponding to a transmission delay of the scheduling resource indicated by the currently received scheduling command includes:
  • the delay requirement of the first transport service data packet is lower than the delay requirement of other service data packets to be transmitted.
  • the method further includes:
  • the second scheduling resource indicated by the second scheduling command is not received in a predetermined period of time, and the uplink resource is actively initiated according to the correspondence between the delay requirement of the pre-configured transmission service data packet and the first scheduling resource.
  • the method of scheduling the request is performed to transmit the service data packet to be transmitted or to transmit the first to-be-transmitted service data packet on the contention resource.
  • the step of determining a to-be-transmitted service data packet corresponding to a transmission delay of the scheduling resource indicated by the currently received scheduling command includes:
  • the delay of transmitting a service data packet is lower than the delay of other service data packets to be transmitted.
  • the method for transmitting the service data packet further includes:
  • the second scheduling resource indicated by the second scheduling command is received, if the first to-be-transmitted service data packet is not waiting for transmission in the current to-be-transmitted service data packet, the second scheduling command is ignored.
  • the terminating the transmission of the first scheduling resource includes:
  • the terminating the transmission of the first scheduling resource further includes:
  • the retransmission of the first scheduling resource is performed according to the retransmission scheduling command.
  • the step of determining a to-be-transmitted service data packet corresponding to a transmission delay of the scheduling resource indicated by the currently received scheduling command includes:
  • the scheduling resource indicated by the currently received scheduling command has a lower transmission delay than the data packet delay requirement of the to-be-transmitted service packet. Length, mapping the to-be-transmitted service data packet to the uplink resource for transmission.
  • An embodiment of the present disclosure further provides a terminal, including:
  • An acquiring module configured to acquire, when receiving a scheduling command of an uplink resource sent by the network side device, attribute information of a current service data packet to be transmitted; where the attribute information packet of the service data packet Including: delay;
  • a transmission module configured to map the to-be-transmitted service data packet to the uplink resource for transmission according to a delay requirement of the current service data packet to be transmitted.
  • the transmission module is specifically configured to:
  • a determining unit configured to determine whether a first transmission delay of the first scheduling resource indicated by the first scheduling command sent by the network side device meets a delay requirement of the current data packet to be transmitted, and obtain a determination result
  • a first mapping unit configured to map, according to the determination result, the to-be-transmitted service data packet to a second scheduling resource indicated by the second scheduling command received on or after the first scheduling resource, and transmit the data ;
  • the second transmission delay of the second scheduling resource is different from the first transmission delay of the first scheduling resource.
  • the first transmission delay is greater than the second transmission delay.
  • the first mapping unit includes:
  • the first to-be-transmitted service data packet is mapped to the first scheduling resource, and are transmitted within the first transmission delay.
  • the current data packet to be transmitted further includes: a second to-be-transmitted service data packet having a second delay requirement, and the length of the second delay request is greater than the length of the first delay requirement
  • the first mapping unit maps at least a part of the first to-be-transmitted service data packet and the second to-be-transmitted service data packet to the first scheduling resource, and transmits the first transmission delay.
  • the first mapping unit includes:
  • the second scheduling resource of the second transmission delay, the number of the first to-be-transmitted services The packet is mapped to the second scheduling resource.
  • the terminal further includes:
  • a second mapping unit configured to: when the second scheduling resource indicated by the second scheduling command is received, if the current to-be-transmitted service data packet has a second to-be-transmitted service with a lower latency requirement than the first to-be-transmitted service data packet Transmitting, by the data packet, the transmission of the first scheduling resource, mapping the second to-be-transmitted service data packet to the second scheduling resource, and transmitting the data packet;
  • the third mapping unit ignores the second scheduling command if there is no other data packet in the current to-be-transmitted service data packet that is lower than the first to-be-transmitted service data packet.
  • the terminal further includes:
  • the first request transmission module is configured to: if the transmission delay requirement of the first scheduling resource does not meet the first delay requirement of the first to-be-transmitted service data packet in the current to-be-transmitted service data packet, and then a preset time period If the second scheduling resource indicated by the second scheduling command is not received, the transmission of the service data packet to be transmitted or the transmission of the service data packet to be transmitted on the contention resource is performed by actively initiating the scheduling request of the uplink resource.
  • the transmission module includes:
  • a determining unit configured to determine a to-be-transmitted service data packet corresponding to a transmission delay of the scheduling resource indicated by the currently received scheduling command, according to a correspondence between the delay requirement of the pre-configured transmission service data packet and the scheduling resource;
  • a transmitting unit configured to map the to-be-transmitted service data packet to the scheduling resource for transmission.
  • the determining unit comprises:
  • the delay requirement of the first transport service data packet is lower than the delay requirement of other service data packets to be transmitted.
  • the terminal further includes:
  • the second request transmission module is configured to: according to the second scheduling resource indicated by the second scheduling command that is not received within a preset time period, according to the preset configuration, the time delay requirement of the transport service data packet corresponds to the first scheduling resource Relationship, to be transmitted in a manner that actively initiates a scheduling request for an uplink resource The transmission of the service data packet or the transmission of the first to-be-transmitted service data packet on the contention resource.
  • the determining unit comprises:
  • the delay of transmitting a service data packet is lower than the delay of other service data packets to be transmitted.
  • the terminal further includes:
  • a fourth mapping unit configured to: when receiving the second scheduling resource indicated by the second scheduling command, if the first to-be-transmitted service data packet in the current to-be-transmitted service data packet is waiting to be transmitted, terminate the first scheduling resource And transmitting, by the first to-be-transmitted service data packet, to the second scheduling resource, and transmitting;
  • a fifth mapping unit configured to: when the second scheduling resource indicated by the second scheduling command is received, if the first to-be-transmitted service data packet is not waiting for transmission in the current to-be-transmitted service data packet, the second scheduling command is ignored.
  • the terminating the transmission of the first scheduling resource includes:
  • the terminal further includes:
  • a retransmission module configured to perform retransmission of the first scheduling resource according to the retransmission scheduling command when the retransmission time arrives.
  • the determining unit comprises:
  • the scheduling resource indicated by the currently received scheduling command has a lower transmission delay than the data packet delay requirement of the to-be-transmitted service packet. Length, mapping the to-be-transmitted service data packet to the uplink resource for transmission. .
  • An embodiment of the present disclosure further provides a method for transmitting a service data packet, including:
  • the receiving terminal maps to the service data packet on the uplink resource according to the delay requirement of the current service data packet to be transmitted.
  • the step of mapping, by the receiving terminal, the service data packet on the uplink resource, according to the delay requirement of the current to-be-transmitted service packet, on the uplink resource indicated by the scheduling command, includes:
  • the receiving terminal starts to map to the service data packet on the first scheduling resource according to the delay requirement of the current service data packet to be transmitted; or in the second scheduling The start transmission time of the second scheduling resource indicated by the command is started, and the receiving terminal is mapped to the service data packet on the first scheduling resource according to the delay of the current service data packet to be transmitted;
  • the service data packet on the first scheduling resource and the service data packet on the second scheduling resource are: the terminal determines whether the transmission delay requirement of the first scheduling resource indicated by the first scheduling command sent by the network side device meets the current to-be-transmitted service.
  • the delay request of the data packet is obtained, and the judgment result is obtained; and according to the judgment result, the to-be-transmitted service data packet is mapped to the second scheduling resource indicated by the second scheduling command received on the first scheduling resource or after receiving And transmitting, by the service data packet, where the second transmission delay of the second scheduling resource is different from the first transmission delay of the first scheduling resource.
  • An embodiment of the present disclosure further provides a network side device, including:
  • a sending module configured to send a scheduling command of an uplink resource to the terminal
  • the receiving module is configured to: on the uplink resource indicated by the scheduling command, the receiving terminal maps to the service data packet on the uplink resource according to the delay requirement of the current service data packet to be transmitted.
  • the receiving module includes:
  • the receiving terminal starts to map to the service data packet on the first scheduling resource according to the delay requirement of the current service data packet to be transmitted; or in the second scheduling The start transmission time of the second scheduling resource indicated by the command is started, and the receiving terminal is mapped to the service data packet on the first scheduling resource according to the delay of the current service data packet to be transmitted;
  • the service data packet on the first scheduling resource and the service data packet on the second scheduling resource are transmission delays of the first scheduling resource indicated by the first scheduling command sent by the terminal to determine the network side device. And determining whether the time delay requirement of the current service data packet to be transmitted is met, and obtaining a determination result; and mapping, according to the determination result, the to-be-transmitted service data packet to the first scheduling resource or the second scheduling received thereafter
  • the service data packet is transmitted on the second scheduling resource indicated by the command, and the second transmission delay of the second scheduling resource is different from the first transmission delay of the first scheduling resource.
  • the foregoing solution enables the terminal to obtain the attribute information of the current service data packet to be transmitted when receiving the scheduling command of the uplink resource sent by the network side device, where the attribute information of the service data packet includes: a delay; The time delay of the service data packet is required to map the to-be-transmitted service data packet to the uplink resource for transmission.
  • FIG. 1 is a schematic diagram of an interactive transmission process of a data packet inside a terminal
  • FIG. 2 is a schematic diagram showing a time relationship between a terminal supporting 1 ms TTI transmission and a short TTI transmission;
  • FIG. 3 is a schematic diagram of a collision between a 1ms TTI transmission and a short TTI transmission supported by the terminal;
  • FIG. 4 is a schematic flowchart of a method for transmitting a service data packet according to a first embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a method for transmitting a service data packet according to a second embodiment of the present disclosure
  • FIG. 6 is a schematic flowchart of a method for transmitting a service data packet according to a third embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of an application scenario of a method for transmitting a service data packet according to the second and third embodiments of the present disclosure
  • FIG. 8 is a schematic diagram of the application scenario 1 of the process shown in FIG. 7 for performing scheduled transmission of service data packets;
  • FIG. 9 is a schematic diagram of the application scenario 2 of the process shown in FIG. 7 for scheduling transmission of service data packets;
  • FIG. 10 is a schematic diagram of scheduling application transmission of service data packets in application scenario 3 of the process shown in FIG. 7;
  • FIG. 11 is a schematic flowchart of a method for transmitting a service data packet according to a fourth embodiment of the present disclosure.
  • FIG. 12 is a schematic flowchart of a method for transmitting a service data packet according to a fifth embodiment of the present disclosure
  • FIG. 13 is a schematic flowchart of a method for transmitting a service data packet according to a sixth embodiment of the present disclosure
  • FIG. 14 is a schematic flowchart of an application scenario of a method for transmitting a service data packet according to the fourth, fifth, and sixth embodiments of the present disclosure
  • FIG. 15 is a schematic diagram of the application scenario 1 of the process shown in FIG. 14 for scheduling transmission of service data packets.
  • 16 is a schematic diagram of scheduling application transmission of service data packets in application scenario 2 of the process shown in FIG. 14;
  • FIG. 17 is a schematic structural diagram of a terminal according to an eighth embodiment of the present disclosure.
  • FIG. 18 is a schematic flowchart of a method for transmitting the service data packet of a network side device according to a ninth embodiment of the present disclosure.
  • a first embodiment of the present disclosure provides a method for transmitting a service data packet, including:
  • Step 41 Acquire, when receiving the scheduling command of the uplink resource sent by the network side device, the attribute information of the current service data packet to be transmitted, where the attribute information of the service data packet includes: a delay;
  • Step 42 Map the to-be-transmitted service data packet to the uplink resource for transmission according to the current delay requirement of the service data packet to be transmitted.
  • the UE when the UE has the capability of processing multiple TTIs (such as the 1 ms TTI and the short TTI capability), when receiving the scheduling of the uplink resource of the eNB, according to the delay requirement of the data packet to be transmitted, the mapping of the to-be-transmitted data packet on the uplink resource is performed and transmitted.
  • TTIs such as the 1 ms TTI and the short TTI capability
  • a second embodiment of the present disclosure provides a method for transmitting a service data packet, including:
  • Step 51 Acquire, when receiving the scheduling command of the uplink resource sent by the network side device, the attribute information of the current service data packet to be transmitted, where the attribute information of the service data packet includes: a delay;
  • Step 52 Determine whether the first transmission delay of the first scheduling resource indicated by the first scheduling command sent by the network side device meets the delay requirement of the current data packet to be transmitted, and obtain a determination result;
  • Step 53 According to the determination result, mapping the to-be-transmitted service data packet to the second scheduling resource indicated by the second scheduling command received on or after the first scheduling resource, and transmitting, where The second transmission delay of the second scheduling resource is different from the first transmission delay of the first scheduling resource.
  • the transmission delays of the respective scheduling resources are different from each other.
  • the first transmission delay is greater than the second transmission delay.
  • the step of mapping the to-be-transmitted service data packet to the first scheduling resource according to the determining result includes:
  • Step 531 If the first transmission delay of the first scheduling resource meets the first delay requirement of the first to-be-transmitted service data packet in the current data packet to be transmitted, mapping the first to-be-transmitted service data packet to the On the first scheduling resource, and transmitting in the first transmission delay;
  • the current to-be-transmitted service data packet further includes: a second to-be-transmitted service data packet having a second delay requirement, and the length of the second delay request is greater than a length of the first delay requirement, And mapping at least a part of the first to-be-transmitted service data packet and the second to-be-transmitted service data packet to the first scheduling resource, and transmitting in the first transmission delay.
  • the current to-be-transmitted service data packet includes, in addition to RB1, the RB2 waiting to transmit the service packet, and the transmission delay of the RB2 is higher than the transmission delay of the RB1, that is, the RB1 is a low-latency service data packet, which may be RB1 and part of RB2 are mapped to the first scheduling resource, and are transmitted within the first transmission delay of the first scheduling resource.
  • Step 532 If the first transmission delay of the first scheduling resource does not meet the first delay requirement of the first to-be-transmitted service data packet in the current to-be-transmitted service data packet, the current to-be-transmitted service data packet is removed.
  • the other to-be-transmitted service data packet except the first to-be-transmitted service data packet is mapped to the first scheduling resource, and is transmitted in the first transmission delay.
  • the terminal supports the transmission of the first scheduling resource (TB1) corresponding to the TTI of 1 ms and the second scheduling resource (TB2) corresponding to the TTI less than 1 ms, whether the terminal delays according to the currently scheduled first scheduling resource Can meet the delay requirements of the current data packets to be transmitted?
  • the first transmission delay of the first scheduling resource for example, one transmission or the expected number of retransmission delays
  • the first delay requirement of the first to-be-transmitted service data packet such as RB1 in the data packet to be transmitted, mapping the first to-be-transmitted service data packet to the first scheduling resource, and Transmitting within the first transmission delay
  • the current to-be-transmitted service data packet is In addition to the first to-be-transmitted service data packet, in addition to the first to-be-transmitted service data packet, the current to-be-transmitted service data packet includes RB2 waiting for transmission service packet, and the transmission delay of RB2 is higher than RB1.
  • the transmission delay of the RB1, that is, the RB1 is a low-latency service data packet, is mapped to the first scheduling resource, and is transmitted within the first transmission delay. At this time, RB1 will wait for the arrival of the second scheduling resource indicated by the second scheduling command.
  • the step of mapping the to-be-transmitted service data packet to the second scheduling resource indicated by the second scheduling command that is received later, according to the determining result includes:
  • Step 533 If the first transmission delay of the first scheduling resource does not meet the first delay requirement of the first to-be-transmitted service data packet in the current to-be-transmitted service data packet, and then receives the second transmission sent by the network-side device And the second scheduling resource with the second transmission delay indicated by the scheduling command, and mapping the first to-be-transmitted service data packet to the second scheduling resource.
  • step 534 if the transmission delay requirement of the first scheduling resource does not meet the first delay requirement of the first to-be-transmitted service data packet in the current data packet to be transmitted, and does not exist within a preset time period And the second scheduling resource indicated by the second scheduling command is configured to perform the transmission of the to-be-transmitted service data packet or the transmission of the to-be-transmitted service data packet on the contention resource.
  • the third embodiment of the present disclosure further provides a method for transmitting a service data packet, including:
  • Step 61 Acquire, when receiving the scheduling command of the uplink resource sent by the network side device, the attribute information of the current service data packet to be transmitted, where the attribute information of the service data packet includes: a delay;
  • Step 62 Determine a first scheduling resource indicated by the first scheduling command sent by the network side device. Whether the transmission delay satisfies the delay requirement of the current service data packet to be transmitted, and obtains a judgment result;
  • Step 63 According to the determination result, mapping the to-be-transmitted service data packet to the second scheduling resource indicated by the second scheduling command received on or after the first scheduling resource, and performing transmission;
  • Step 64 When receiving the second scheduling resource indicated by the second scheduling command, if the current to-be-transmitted service data packet has a delay request lower than the second to-be-transmitted service data packet of the first to-be-transmitted service data packet, Terminating the transmission of the first scheduling resource, mapping the second to-be-transmitted service data packet to the second scheduling resource, and transmitting;
  • the second scheduling command is ignored.
  • the terminal when the terminal collides with the short TTI, the terminal records the transport block corresponding to the first scheduling resource on the 1 ms TTI as TB1, and the UE processing mode is:
  • the UE does not have a lower latency service data packet to be transmitted (the service data packet is not mapped to TB1), ignoring the allocation of the second scheduling resource on the short TTI, and continuing to send TB1;
  • the UE has a lower latency service data packet to be transmitted (the lower latency service data packet (such as RB3) is not mapped to TB1), the low latency service data packet (RB3) to be mapped is mapped to TB2, which is short. Map and send on TTI resources.
  • the lower latency service data packet such as RB3 is not mapped to TB1
  • the low latency service data packet (RB3) to be mapped is mapped to TB2, which is short. Map and send on TTI resources.
  • the UE may terminate the transmission of TB1 in the 1 ms TTI and perform retransmission at the next retransmission time.
  • the terminating the transmission of the first scheduling resource herein includes:
  • the first case is: when the start of the first scheduling resource does not arrive, the transmission of the first scheduling resource is terminated; for example, the starting transmission time of the transport block TB1 corresponding to the first scheduling resource is t1, and the second The start transmission time of the transport block TB2 corresponding to the scheduling resource is t2. If it is determined before the start of time t1, the transmission of TB1 will be terminated because of the transmission TB2, the TB1 is not transmitted from t1, and the transmission of TB2 is started at time t2;
  • the second case is: when the start transmission time of the second scheduling resource arrives, the transmission of the first scheduling resource is terminated, for example, the data symbol of the TB1 is not transmitted only at the TB2 location, that is, the resource location corresponding to the transmission TB2 The punch position for TB1 transmission.
  • the retransmission of the first scheduling resource is performed according to the retransmission scheduling command.
  • Step 101 Receive a scheduling command 1 (corresponding to 1 ms TTI);
  • Step 102 Determine whether the transmission delay of the transport block TB1 corresponding to the 1 ms TTI meets the delay requirement of the current service data packet RB1.
  • Step 103 If the transmission delay of the transport block TB1 corresponding to the 1ms TTI does not meet the delay requirement of the current service data packet RB1, only the RB data packets other than the RB1 in the to-be-transmitted service data packet in the buffer are mapped to the TB1. ;
  • Step 104 waiting for a short TTI (less than 1 ms TTI) scheduling, if there is a short TTI, mapping RB1 to the transport block TB2 corresponding to the short TTI;
  • Step 105 If there is no short TTI within a preset time period, a scheduling request may be initiated or RB1 may be transmitted on the contention resource;
  • Step 106 If the transmission delay of the transport block TB1 corresponding to the 1ms TTI meets the delay requirement of the current service data packet RB1, the RB1 or some or all of the other transportable service data packets RB2 that can be accommodated are further mapped to the TB1. And transmit;
  • step 107 when the scheduling command 2 is received, the scheduling command 2 corresponds to the short TTI transmission block TB2. If the short TTI and the 1 ms TTI collide, it is determined whether there is a lower delay service in the data packet to be transmitted in the buffer. Packet (RB3) to be transmitted? The delay requirement of RB2 is less than the delay requirement of RB1, and the delay requirement of RB1 is less than the delay requirement of RB3.
  • Step 108 if yes, can terminate the transmission of TB1, map the RB3 data packet to TB2 for transmission, otherwise, proceed to step 109;
  • step 109 the scheduling command 2 is ignored.
  • step 110 when the retransmission time of TB1 arrives, TB1 can be retransmitted.
  • the UE determines whether to transmit the low-latency service data packet in the 1 ms TTI according to whether the delay requirement can be met (case 1).
  • the scheduling command 1 allocates 1 ms TTI uplink resources, and starts transmission from time t1; the scheduling command 2 allocates short TTI uplink resources, and starts transmission from time t2; the bearer data packets buffered by the UE before scheduling command 1 are RB1 data packets and RB2 respectively. Packet, RB1 is a low latency service bearer.
  • Step 1 The UE receives the scheduling command 1 and determines that the 1 ms TTI starting at time t1 satisfies the delay requirement of RB1.
  • Step 2 organize the data packet of the RB1 and the data packet of the RB2 that can be accommodated into the TB1;
  • Step 3 The UE receives the scheduling command 2, determines that there is no lower delay requesting the service data packet, and ignores the scheduling command 2;
  • Step 4 At time t1, TB1 is transmitted on the 1ms TTI.
  • the third and fourth steps can be interchanged according to the chronological order.
  • Step 1 Send a scheduling command 1 to allocate an uplink transmission resource on a 1 ms TTI starting at time t1;
  • Step 2 Send a scheduling command 2, allocate an uplink transmission resource on a short TTI starting at time t2, and collide a short TTI resource with a 1 ms TTI;
  • Step 3 The eNB starts receiving the TB1 of the 1ms TTI at time t1, and starts receiving the TB2 of the short TTI at time t2;
  • Step 4 The eNB performs data parsing on the received uplink transmission, correctly receives TB1, and determines that TB2 has no data transmission.
  • the UE determines whether to transmit the low-latency service data packet in the 1 ms TTI according to whether the delay requirement can be met (Case 2).
  • the scheduling command 1 allocates 1 ms TTI uplink resources, and starts transmission from time t1; the scheduling command 2 allocates short TTI uplink resources, and starts transmission from time t2; the bearer data packets buffered by the UE before scheduling command 1 are RB1 data packets and RB2 respectively. Packet, RB1 is a low latency service bearer.
  • Step 1 The UE receives the scheduling command 1 and determines that the 1 ms TTI starting at time t1 cannot meet the delay requirement of RB1.
  • Step 2 Organize the data packets of RB2 into TB1;
  • Step 3 At time t1, TB1 is transmitted on the 1ms TTI.
  • Step 4 The UE receives the scheduling command 2, and organizes the RB1 data packet into the TB2.
  • Step 5 Start at time t2, terminate TB1 transmission, and transmit TB2.
  • Step 5 has two optimization directions. 1) If it is determined before the start of time t1, the transmission of TB1 will be terminated because of transmission TB2, TB1 will not be transmitted from t1, and TB2 will be transmitted at time t2. 2) Only in TB2 position The data symbol of TB1, that is, the location of the resource corresponding to the transmission of TB2 is the puncturing position of TB1 transmission. Under optimization 2), it is possible for the eNB to correctly resolve TB1.
  • Step 6 The UE retransmits TB1. (Do not consider step 5 optimization 2), the default TB1 current transmission fails)
  • Step 1 Send a scheduling command 1 to allocate an uplink transmission resource on a 1 ms TTI starting at time t1;
  • Step 2 Send a scheduling command 2, allocate an uplink transmission resource on a short TTI starting at time t2, and collide a short TTI resource with a 1 ms TTI;
  • Step 3 The eNB starts receiving the TB1 of the 1ms TTI at time t1, and starts receiving the TB2 of the short TTI at time t2;
  • Step 4 The eNB performs data parsing on the received uplink transmission, correctly receives TB2, and determines that TB1 is terminated (or according to step 5 of the UE side optimization 2), and the base station may correctly receive TB1).
  • the UE determines whether to transmit a low-latency service data packet in the 1 ms TTI according to whether the delay requirement can be met (Case 3).
  • the scheduling command 1 allocates 1 ms TTI uplink resources, and starts transmission from time t1; the scheduling command 2 allocates short TTI uplink resources, and starts transmission from time t2; the bearer data packets buffered by the UE before scheduling command 1 are RB1 data packets and RB2 respectively.
  • Packet, RB1 is a low-latency service bearer; after scheduling command 1, packets with lower latency service data packet RB3 arrive at the UE buffer.
  • Step 1 The UE receives the scheduling command 1 and determines that the 1 ms TTI starting at time t1 can meet the delay requirement of RB1.
  • Step 2 organize the data packet of the RB1 and the data packet of the RB2 that can be accommodated into the TB1;
  • Step 3 At time t1, TB1 is transmitted on the 1ms TTI.
  • Step 4 The UE receives the scheduling command 2, and determines that there is a lower delay requesting the number of service data packets RB3. According to the package, it will be organized into TB2;
  • Step 5 Start at time t2, terminate TB1 transmission, and transmit TB2.
  • Step 5 has two optimization directions. 1) If it is determined before the start of time t1, the transmission of TB1 will be terminated because of transmission TB2, TB1 will not be transmitted from t1, and TB2 will be transmitted at time t2. 2) Only in TB2 position The data symbol of TB1, that is, the location of the resource corresponding to the transmission of TB2 is the puncturing position of TB1 transmission. Under optimization 2), it is possible for the eNB to correctly resolve TB1.
  • Step 6 The UE retransmits TB1. (Do not consider step 5 optimization 2), the default TB1 current transmission fails)
  • Step 1 Send a scheduling command 1 to allocate an uplink transmission resource on a 1 ms TTI starting at time t1;
  • Step 2 Send a scheduling command 2, allocate an uplink transmission resource on a short TTI starting at time t2, and collide a short TTI resource with a 1 ms TTI;
  • Step 3 The eNB starts receiving the TB1 of the 1ms TTI at time t1, and starts receiving the TB2 of the short TTI at time t2;
  • Step 4 The eNB performs data parsing on the received uplink transmission, correctly receives TB2, and determines that TB1 is terminated (or according to step 5 of the UE side optimization 2), and the base station may correctly receive TB1.
  • a fourth embodiment of the present disclosure provides a method for transmitting service data, including:
  • Step 111 Acquire, when receiving the scheduling command of the uplink resource sent by the network side device, the attribute information of the current service data packet to be transmitted, where the attribute information of the service data packet includes: a delay;
  • Step 112 Determine a to-be-transmitted service data packet corresponding to a transmission delay of a scheduling resource indicated by the currently received scheduling command, according to a correspondence between a delay requirement of the pre-configured transmission service data packet and the scheduling resource; The to-be-transmitted service data packet is mapped to the scheduling resource for transmission.
  • determining that the to-be-transmitted service data packet except the first to-be-transmitted service data packet in the to-be-transmitted service data packet corresponds to the transmission delay of the first scheduling resource indicated by the currently received scheduling command, to be transmitted a service data packet; wherein the first transmission service data packet has a delay requirement It is lower than the delay requirement of other data packets to be transmitted.
  • Step 113 In a preset time period, the second scheduling resource indicated by the second scheduling command that is not received is initiated according to the corresponding relationship between the delay requirement of the pre-configured transmission service data packet and the first scheduling resource.
  • the scheduling request of the uplink resource is used to transmit the service data packet to be transmitted or to transmit the first to-be-transmitted service data packet on the contention resource.
  • a fifth embodiment of the present disclosure provides a method for transmitting service data, including:
  • Step 121 Acquire, when receiving the scheduling command of the uplink resource sent by the network side device, the attribute information of the current service data packet to be transmitted, where the attribute information of the service data packet includes: a delay;
  • Step 122 Determine, according to the correspondence between the delay requirement of the pre-configured transmission service data packet and the first scheduling resource, that the first to-be-transmitted service data packet in the to-be-transmitted service data packet is the currently received second scheduling command indication.
  • the transmission delay of the second scheduling resource corresponds to the to-be-transmitted service data packet; wherein the delay of the first transmission service data packet is lower than the delay of other service data packets to be transmitted.
  • Step 123 When receiving the second scheduling resource indicated by the second scheduling command, if the first to-be-transmitted service data packet in the current to-be-transmitted service data packet is waiting for transmission, the transmission of the first scheduling resource is terminated.
  • the first to-be-transmitted service data packet is mapped to the second scheduling resource, and is transmitted;
  • Step 124 When receiving the second scheduling resource indicated by the second scheduling command, if the first to-be-transmitted service data packet is not waiting for transmission in the current to-be-transmitted service data packet, the second scheduling command is ignored.
  • the terminating the transmission of the first scheduling resource herein includes:
  • the first case is: when it is determined that the transmission of the first scheduling resource is terminated, if the start transmission time of the first scheduling resource does not arrive, the transmission of the first scheduling resource is not performed; for example, the transport block corresponding to the first scheduling resource
  • the start transmission time of TB1 is t1
  • the start transmission time of the transport block TB2 corresponding to the second scheduling resource is t2
  • the transmission of TB1 does not transmit TB1 from t1, and waits for t2 to start transmitting TB2;
  • the second case is: when the start transmission time of the second scheduling resource arrives, the transmission of the first scheduling resource is terminated, for example, the data symbol of the TB1 is not transmitted only at the TB2 location, that is, the resource location corresponding to the transmission TB2 The punch position for TB1 transmission.
  • the retransmission of the first scheduling resource is performed according to the retransmission scheduling command.
  • a sixth embodiment of the present disclosure provides a method for transmitting service data, including:
  • Step 131 Acquire, when receiving the scheduling command of the uplink resource sent by the network side device, the attribute information of the current service data packet to be transmitted, where the attribute information of the service data packet includes: a delay;
  • Step 132 According to the correspondence between the delay requirement of the pre-configured transmission service data packet and the first scheduling resource, if the current service data packet to be transmitted includes only one service data packet to be transmitted required by the transmission delay, and currently The transmission delay of the scheduling resource indicated by the received scheduling command is lower than the length of the delay of the to-be-transmitted service data packet, and the service data packet to be transmitted is mapped to the uplink resource for transmission.
  • Step 141 receiving a scheduling command 1 (corresponding to 1 ms TTI);
  • Step 142 mapping data packets of other RBs other than RB1 to TB1;
  • Step 143 waiting for the scheduled second scheduling resource TB2 of the short TTI, if there is a short TTI, mapping RB1 to the transmission block TB2 corresponding to the short TTI; or if there is no short TTI within a preset time period , initiating a scheduling request or transmitting a data packet of RB1 on a contention resource;
  • Step 144 when the start transmission time of TB1 arrives, the transmission is performed
  • Step 145 If the scheduling command 2 is received, corresponding to the short TTI, if a short TTI occurs and a 1 ms TTI collides;
  • Step 146 Determine whether there is a low-latency service data packet in the to-be-transmitted service data packet in the cache. (RB1) to be transmitted?
  • Step 147 if yes, can terminate the transmission of TB1, map the RB1 data packet to TB2 for transmission, otherwise, proceed to step 148;
  • step 148 the scheduling command 2 is ignored. Or if the UE obtains a short TTI resource allocation, and there is no low-latency service data packet in the cache, other service data packets (RB2) may also be transmitted.
  • RB2 service data packets
  • step 149 when the retransmission time of TB1 arrives, TB1 can be retransmitted.
  • the UE transmits different delay requirement data packets according to the TTI length (case 1).
  • the scheduling command 1 allocates 1 ms TTI uplink resources, and starts transmission from time t1; the scheduling command 2 allocates short TTI uplink resources, and starts transmission from time t2; the bearer data packets buffered by the UE before scheduling command 1 are RB1 data packets and RB2 respectively. Packet, RB1 is a low latency service bearer.
  • Step 1 The UE receives the scheduling command 1, and determines that the allocated resource is a 1 ms TTI;
  • Step 2 Organize the data packets of RB2 into TB1;
  • Step 3 At time t1, TB1 is transmitted on the 1ms TTI.
  • Step 4 The UE receives the scheduling command 2, and organizes the RB1 data packet into the TB2.
  • Step 5 Start at time t2, terminate TB1 transmission, and transmit TB2.
  • Step 5 has two optimization directions. 1) If it is determined before the start of time t1, the transmission of TB1 will be terminated because of transmission TB2, TB1 will not be transmitted from t1, and TB2 will be transmitted at time t2. 2) Only in TB2 position The data symbol of TB1, that is, the location of the resource corresponding to the transmission of TB2 is the puncturing position of TB1 transmission. Under optimization 2), it is possible for the eNB to correctly resolve TB1.
  • Step 6 The UE retransmits TB1. (Do not consider step 5 optimization 2), the default TB1 current transmission fails)
  • Step 1 Send a scheduling command 1 to allocate an uplink transmission resource on a 1 ms TTI starting at time t1;
  • Step 2 Send a scheduling command 2, allocate an uplink transmission resource on a short TTI starting at time t2, and collide a short TTI resource with a 1 ms TTI;
  • Step 3 The eNB starts receiving TB1 of 1 ms TTI at time t1, and starts receiving short at time t2.
  • Step 4 The eNB performs data parsing on the received uplink transmission, correctly receives TB2, and determines that TB1 is terminated (or according to step 5 of the UE side optimization 2), and the base station may correctly receive TB1.
  • the UE transmits different delay requirement data packets according to the TTI length (Case 2).
  • the scheduling command allocates a short TTI uplink resource, and the transmission starts from time t2; the bearer data packet buffered by the UE before the scheduling command has only the data packet of the RB2 whose delay requirement is not high.
  • Step 1 The UE receives the scheduling command, and determines that the allocated resource is a short TTI;
  • Step 2 Organize the data packets of RB2 into TB2;
  • Step 3 Start at time t2 and transmit TB1 on the short TTI.
  • Step 1 Send a scheduling command, and allocate a short TTI uplink transmission resource starting from time t2;
  • Step 2 The eNB starts receiving the TB2 of the short TTI at time t2;
  • Step 3 The eNB performs data parsing on the received uplink transmission, and correctly receives TB2.
  • the method described in the above embodiments of the present disclosure is applicable to a general scenario of long TTI (1 ms TTI) and short TTI length collision, and is not limited to 1 ms and short TTI collision. If the UE cannot simultaneously use the two scheduled resources for data transmission when the 1 ms TTI and the short TTI collide, the method described in the above embodiment of the present disclosure ensures that the data of the delay-sensitive service is preferentially transmitted.
  • the seventh embodiment of the present disclosure further provides a terminal, including:
  • An obtaining module configured to: when receiving a scheduling command of an uplink resource sent by the network side device, obtain the attribute information of the current service data packet to be transmitted; where the attribute information of the service data packet includes: a delay;
  • a transmission module configured to map the to-be-transmitted service data packet to the uplink resource for transmission according to a delay requirement of the current service data packet to be transmitted.
  • the transmission module is specifically configured to:
  • the determining unit is configured to determine whether the first transmission delay of the first scheduling resource indicated by the first scheduling command sent by the network side device meets the delay requirement of the current service data packet to be transmitted, and obtain a judgment result. fruit;
  • a first mapping unit configured to map, according to the determination result, the to-be-transmitted service data packet to a second scheduling resource indicated by the second scheduling command received on or after the first scheduling resource, and transmit the data ;
  • the second transmission delay of the second scheduling resource is different from the first transmission delay of the first scheduling resource.
  • the first transmission delay is greater than the second transmission delay.
  • the first mapping unit includes:
  • the first to-be-transmitted service data packet is mapped to the first scheduling resource, and are transmitted within the first transmission delay.
  • the current data packet to be transmitted further includes: a second to-be-transmitted service data packet having a second delay requirement, and the length of the second delay request is greater than the length of the first delay requirement
  • the first mapping unit maps at least a part of the first to-be-transmitted service data packet and the second to-be-transmitted service data packet to the first scheduling resource, and transmits the first transmission delay.
  • the first mapping unit includes:
  • the first transmission delay of the first scheduling resource does not meet the delay requirement of the first to-be-transmitted service data packet in the current to-be-transmitted service data packet, and then receives the second scheduling command sent by the network-side device, And transmitting, by the second scheduling resource of the second transmission delay, the first to-be-transmitted service data packet to the second scheduling resource.
  • the above terminal further includes:
  • a second mapping unit configured to: when the second scheduling resource indicated by the second scheduling command is received, if the current to-be-transmitted service data packet has a second to-be-transmitted service with a lower latency requirement than the first to-be-transmitted service data packet Transmitting, by the data packet, the transmission of the first scheduling resource, mapping the second to-be-transmitted service data packet to the second scheduling resource, and transmitting the data packet;
  • the third mapping unit ignores the second scheduling command if there is no other data packet in the current to-be-transmitted service data packet that is lower than the first to-be-transmitted service data packet.
  • the above terminal further includes:
  • the first request transmission module is configured to: if the transmission delay requirement of the first scheduling resource does not meet the first delay requirement of the first to-be-transmitted service data packet in the current to-be-transmitted service data packet, and then a preset time period If the second scheduling resource indicated by the second scheduling command is not received, the transmission of the service data packet to be transmitted or the transmission of the service data packet to be transmitted on the contention resource is performed by actively initiating the scheduling request of the uplink resource.
  • the transmission module includes:
  • a determining unit configured to determine a to-be-transmitted service data packet corresponding to a transmission delay of the scheduling resource indicated by the currently received scheduling command, according to a correspondence between the delay requirement of the pre-configured transmission service data packet and the scheduling resource;
  • a transmitting unit configured to map the to-be-transmitted service data packet to the scheduling resource for transmission.
  • the determining unit comprises:
  • the delay requirement of the first transport service data packet is lower than the delay requirement of other service data packets to be transmitted.
  • the terminal further includes:
  • the second request transmission module is configured to: according to the second scheduling resource indicated by the second scheduling command that is not received within a preset time period, according to the preset configuration, the time delay requirement of the transport service data packet corresponds to the first scheduling resource
  • the relationship is to transmit the service data packet to be transmitted or to transmit the first data packet to be transmitted on the contention resource by actively initiating a scheduling request of the uplink resource.
  • the determining unit comprises:
  • the delay of transmitting a service data packet is lower than the delay of other service data packets to be transmitted.
  • the terminal further includes:
  • a fourth mapping unit configured to: when receiving the second scheduling resource indicated by the second scheduling command, if the first to-be-transmitted service data packet in the current to-be-transmitted service data packet is waiting to be transmitted, terminate the first scheduling resource And transmitting, by the first to-be-transmitted service data packet, to the second scheduling resource, and transmitting;
  • a fifth mapping unit configured to: when the second scheduling resource indicated by the second scheduling command is received, if the first to-be-transmitted service data packet is not waiting for transmission in the current to-be-transmitted service data packet, the second scheduling command is ignored.
  • the terminating the transmission of the first scheduling resource includes:
  • the terminal further includes:
  • a retransmission module configured to perform retransmission of the first scheduling resource according to the retransmission scheduling command when the retransmission time arrives.
  • the determining unit comprises:
  • the scheduling resource indicated by the currently received scheduling command has a lower transmission delay than the data packet delay requirement of the to-be-transmitted service packet. Length, mapping the to-be-transmitted service data packet to the uplink resource for transmission.
  • the terminal is a terminal corresponding to the foregoing method, and all implementation manners in the foregoing method embodiments are applicable to the terminal, and the same technical effect can be achieved.
  • an eighth embodiment of the present disclosure further provides a terminal, including: a processor 600; and a memory 620 connected to the processor 600 through a bus interface, where the memory 620 is configured to store the The program and data used by the processor in performing the operations, when the processor 600 calls and executes the programs and data stored in the memory 620, the processor is configured to implement The function of obtaining the attribute information of the current service data packet to be transmitted when receiving the scheduling command of the uplink resource sent by the network side device; wherein the attribute information of the service data packet includes: a delay;
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 600 and various circuits of memory represented by memory 620.
  • 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 610 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 user interface 630 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 can store data used by the processor 600 in performing operations.
  • a ninth embodiment of the present disclosure further provides a method for transmitting a service data packet, including:
  • Step 181 Send a scheduling command of an uplink resource to the terminal.
  • Step 182 On the uplink resource indicated by the scheduling command, the receiving terminal maps to the service data packet on the uplink resource according to the delay requirement of the current service data packet to be transmitted.
  • step 182 includes:
  • the receiving terminal starts to map to the service data packet on the first scheduling resource according to the delay requirement of the current service data packet to be transmitted; or in the second scheduling The start transmission time of the second scheduling resource indicated by the command is started, and the receiving terminal is mapped to the service data packet on the first scheduling resource according to the delay of the current service data packet to be transmitted;
  • the service data packet on the first scheduling resource and the service data packet on the second scheduling resource are: the terminal determines whether the transmission delay requirement of the first scheduling resource indicated by the first scheduling command sent by the network side device meets the current to-be-transmitted service. The delay requirement of the data packet, the judgment result is obtained; Assorted, the service data packet to be transmitted is mapped to the second scheduling resource indicated by the second scheduling command received on or after the first scheduling resource, and the service data packet is transmitted; The second transmission delay of the second scheduling resource is different from the first transmission delay of the first scheduling resource.
  • the tenth embodiment of the present disclosure further provides a network side device, including:
  • a sending module configured to send a scheduling command of an uplink resource to the terminal
  • the receiving module is configured to: on the uplink resource indicated by the scheduling command, the receiving terminal maps to the service data packet on the uplink resource according to the delay requirement of the current service data packet to be transmitted.
  • the receiving module includes:
  • the receiving terminal starts to map to the service data packet on the first scheduling resource according to the delay requirement of the current service data packet to be transmitted; or in the second scheduling The start transmission time of the second scheduling resource indicated by the command is started, and the receiving terminal is mapped to the service data packet on the first scheduling resource according to the delay of the current service data packet to be transmitted;
  • the service data packet on the first scheduling resource and the service data packet on the second scheduling resource are: the terminal determines whether the transmission delay requirement of the first scheduling resource indicated by the first scheduling command sent by the network side device meets the current to-be-transmitted service.
  • the delay request of the data packet is obtained, and the judgment result is obtained; and according to the judgment result, the to-be-transmitted service data packet is mapped to the second scheduling resource indicated by the second scheduling command received on the first scheduling resource or after receiving And transmitting, by the service data packet, where the second transmission delay of the second scheduling resource is different from the first transmission delay of the first scheduling resource.
  • the network side device may be a base station, and is a device corresponding to the method described in the foregoing network side device. All the implementation manners in the foregoing embodiments are applicable to the embodiment of the terminal, and the foregoing method can also be achieved. The same effect.
  • An eleventh embodiment of the present disclosure further provides a network side device, including: a processor; a memory connected to the processor through a bus interface; and a transceiver connected to the processor through a bus interface; the memory Storing programs and data used by the processor when performing operations; Transmitting data information or pilots through the transceiver, and receiving a downlink control channel through the transceiver; when the processor invokes and executes programs and data stored in the memory, the processor is configured to implement the following functions And a scheduling command for transmitting the uplink resource to the terminal; on the uplink resource indicated by the scheduling command, the receiving terminal maps to the service data packet on the uplink resource according to the delay requirement of the current service data packet to be transmitted.
  • a network side device including: a processor; a memory connected to the processor through a bus interface; and a transceiver connected to the processor through a bus interface; the memory Storing programs and data used by the processor when performing operations; Transmitting data information or pilots through the transceiver, and receiving
  • the method described in the above embodiments of the present disclosure is applicable to a general scenario of long TTI (1 ms TTI) and short TTI length collision, and is not limited to 1 ms and short TTI collision. If the UE cannot simultaneously use the two scheduled resources for data transmission when the 1 ms TTI and the short TTI collide, the method described in the above embodiment of the present disclosure ensures that the data of the delay-sensitive service is preferentially transmitted.
  • the objects of the present disclosure can also be achieved by running a program or a set of programs on any computing device.
  • the computing device can be a well-known general purpose device.
  • the objects of the present disclosure may also be realized by merely providing a program product including program code for implementing the method or apparatus. That is to say, such a program product also constitutes the present disclosure, and a storage medium storing such a program product also constitutes the present disclosure.
  • the storage medium may be any known storage medium or any storage medium developed in the future.
  • various components or steps may be decomposed and/or recombined.

Landscapes

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

Abstract

本公开提供一种业务数据的传输方法、终端及网络侧设备；该方法包括：在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输。

Description

一种业务数据的传输方法、终端及网络侧设备
相关申请的交叉引用
本申请主张在2016年5月13日在中国提交的中国专利申请号No.201610320112.4的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，特别是指一种业务数据的传输方法、装置及网络侧设备。
背景技术
在LTE(长期演进)系统中，空口之间进行调度，资源分配和数据传输的基本时间单位为TTI(传输时间间隔)，在Rel-13版本之前，TTI的长度为1ms(下称1ms TTI)。
Rel-14版本中，为了更好的支持时延敏感业务，LTE引入了更短的TTI(下称短TTI)，短TTI长度小于1ms；
目前确定，支持使用短TTI传输的上行信道至少包括短物理上行控制信道(s-PUCCH，Short Physical Uplink Control CHannel)和短物理上行共享信道(s-PUSCH，Short Physical Uplink Shared CHannel)；支持使用短TTI传输的下行信道至少包括短物理下行控制信道(s-PDCCH，Short Physical Downlink Control CHannel)和短物理下行共享信道(s-PDSCH，Short Physical Downlink Shared CHannel)。
在LTE中，RB(Radio Bearer，无线承载)是进行QoS管理的基本单位。具有不同QoS需求的数据包被映射到不同的RB上进行传输。如语音业务的数据包被映射到时延要求严格，但允许部分丢包的RB上传输；ftp业务的数据包被映射到时延要求不高但误码率很低的RB上进行传输。
UE的空口协议栈结构如图1所示，UE内部调度过程包括：每一个RB对应一对PDCP(分组数据汇聚协议)/RLC(无线链路层控制协议)实体，不同的RB在MAC层被汇聚在一起，通过物理层(PHY)传输。
当UE的MAC收到eNB的上行调度信令后：
如果是HARQ(混合自动重传请求)初始传输：MAC根据eNB分配的资源的大小，以及各RB的数据包的QoS需求，数据量，排队等候时长，历史传输速率等因素，进行调度，决定本次传输哪些RB可以进行数据传输，以及每个RB传输多少数据；
然后，根据调度结果，MAC层向被调度的各RB的RLC和PDCP实体申请对应数据量的数据，并汇聚成一个MAC PDU(分组数据单元)，放入对应HARQ实体的发送缓存，经过物理层，在空口发送；
如果是HARQ重传：MAC实体将对应HARQ实体的发送缓存中的数据传递给物理层，在空口发送。
如图2和图3所示，在eNB为UE调度了使用1ms TTI进行上行传输后，有可能为UE调度短TTI资源。一旦eNB为同一个UE调度的1ms TTI和短TTI时间上有交叠，则会出现资源碰撞(下称1ms TTI和短TTI碰撞)。
在1ms TTI和短TTI碰撞时，如果UE不能同时使用两次调度的资源进行数据发送(例如：受限UE的上行发送能力，两次调度的资源包含了相同的频率资源等)，就不能保证业务数据的正确传输。
发明内容
本公开要解决的技术问题是提供一种业务数据的传输方法、终端及网络侧设备。当UE同时具有处理多种TTI的能力(如同时处理1ms TTI和短TTI能力)时，在收到eNB上行资源分配时，UE可以根据待传业务数据时延要求，进行待传数据在上行资源上的映射并进行传输。
为解决上述技术问题，本公开的实施例提供一种业务数据包的传输方法，包括：
在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输。
其中，根据当前待传输业务数据包的时延要求，将所述待传输业务数据 包映射到所述上行资源上进行传输的步骤包括：
判断网络侧设备发送的第一调度命令指示的第一调度资源的第一传输时延是否满足当前待传输业务数据包的时延要求，得到判断结果；
根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输；
其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
其中，所述第一传输时延大于第二传输时延。
其中，根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上，并进行传输的步骤包括：
若第一调度资源的第一传输时延满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，则将所述第一待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输；
若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，则将所述当前待传输业务数据包中，除所述第一待传输业务数据包外的其它待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输。
其中，若当前待传输业务数据包中还包括：具有第二时延要求的第二待传输业务数据包，且所述第二时延要求的长度大于所述第一时延要求的长度，则将所述第一待传输业务数据包和所述第二待传输业务数据包的至少一部分映射到所述第一调度资源上，并在所述第一传输时延内传输。
其中，根据所述判断结果，将所述待传输业务数据包映射到之后接收到的第二调度命令指示的第二调度资源的步骤包括：
若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，且之后接收到所述网络侧设备发送的第二调度命令指示的具有第二传输时延的第二调度资源，则将所述第一待传输业务数据包映射到所述第二调度资源上。
其中，业务数据包的传输方法还包括：
接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包 中具有时延要求低于所述第一待传输业务数据包的第二待传输业务数据包，则终止所述第一调度资源的传输，将所述第二待传输业务数据包映射到所述第二调度资源上，并进行传输；
若当前待传输业务数据包中没有时延低于所述第一待传输业务数据包的其他数据包，忽略所述第二调度命令。
其中，业务数据包的传输方法还包括：
若所述第一调度资源的传输时延要求不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，且之后一预设时间段内没有接收到的第二调度命令指示的第二调度资源，则通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行待传输业务数据包的传输。
其中，根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输的步骤包括：
根据预先配置的传输业务数据包的时延要求与调度资源的对应关系，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包；
将所述待传输业务数据包映射到所述调度资源上进行传输。
其中，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包的步骤包括：
确定待传输业务数据包中除第一待传输业务数据包之外的其它待传输业务数据包为当前接收到的调度命令指示的第一调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延要求低于其它待传输业务数据包的时延要求。
其中，将所述其它待传输业务数据包映射到所述第一调度资源上之后还包括：
在一预设时间段内，没有接收到的第二调度命令指示的第二调度资源，根据预先配置的传输业务数据包的时延要求与第一调度资源的对应关系，通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行第一待传输业务数据包的传输。
其中，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包的步骤包括：
确定所述待传输业务数据包中第一待传输业务数据包为当前接收到的第二调度命令指示的第二调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延低于其它待传输业务数据包的时延。
其中，业务数据包的传输方法还包括：
接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中的所述第一待传输业务数据包等待传输，则终止所述第一调度资源的传输，将所述第一待传输业务数据包映射到所述第二调度资源上，并进行传输；
接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中没有所述第一待传输业务数据包等待传输，忽略所述第二调度命令。
其中，终止所述第一调度资源的传输包括：
判断确定终止第一调度资源的传输时，如果所述第一调度资源的开始传输时刻没到达时，不进行第一调度资源的传输；或者
在所述第二调度资源的开始传输时刻到达时，终止所述第一调度资源的传输；或者
在所述第二调度资源的开始传输时刻到达时，暂停所述第一调度资源的传输，在所述第二调度资源传输结束时，继续第一调度资源剩余部分的传输。
其中，终止所述第一调度资源的传输后还包括：
重传时刻到达时，根据重传调度命令进行所述第一调度资源的重传。
其中，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包的步骤包括：
若当前待传输业务数据包中只包括：一种传输时延要求的待传输业务数据包，且当前接收到的调度命令指示的调度资源的传输时延低于该待传输业务数据包时延要求长度，将所述待传输业务数据包映射到所述上行资源上进行传输。
本公开的实施例还提供一种终端，包括：
获取模块，用于在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包 括：时延；
传输模块，用于根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输。
其中，所述传输模块具体用于：
判断单元，用于判断网络侧设备发送的第一调度命令指示的第一调度资源的第一传输时延是否满足当前待传输业务数据包的时延要求，得到判断结果；
第一映射单元，用于根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输；
其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
其中，所述第一传输时延大于第二传输时延。
其中，所述第一映射单元包括：
若第一调度资源的第一传输时延满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，则将所述第一待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输；
若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的时延要求，则将所述当前待传输业务数据包中，除所述第一待传输业务数据包外的其它待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输。
其中，若当前待传输业务数据包中还包括：具有第二时延要求的第二待传输业务数据包，且所述第二时延要求的长度大于所述第一时延要求的长度，所述第一映射单元将所述第一待传输业务数据包和所述第二待传输业务数据包的至少一部分映射到所述第一调度资源上，并在所述第一传输时延内传输。
其中，所述第一映射单元包括：
若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的时延要求，且之后接收到所述网络侧设备发送的第二调度命令指示的具有第二传输时延的第二调度资源，则将所述第一待传输业务数 据包映射到所述第二调度资源上。
其中，终端还包括：
第二映射单元，用于接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中具有时延要求低于所述第一待传输业务数据包的第二待传输业务数据包，则终止所述第一调度资源的传输，将所述第二待传输业务数据包映射到所述第二调度资源上，并进行传输；
第三映射单元，若当前待传输业务数据包中没有时延低于所述第一待传输业务数据包的其他数据包，忽略所述第二调度命令。
其中，终端还包括：
第一请求传输模块，用于若所述第一调度资源的传输时延要求不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，且之后一预设时间段内没有接收到的第二调度命令指示的第二调度资源，则通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行待传输业务数据包的传输。
其中，所述传输模块包括：
确定单元，用于根据预先配置的传输业务数据包的时延要求与调度资源的对应关系，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包；
传输单元，用于将所述待传输业务数据包映射到所述调度资源上进行传输。
其中，所述确定单元包括：
确定待传输业务数据包中除第一待传输业务数据包之外的其它待传输业务数据包为当前接收到的调度命令指示的第一调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延要求低于其它待传输业务数据包的时延要求。
其中，终端还包括：
第二请求传输模块，用于在一预设时间段内，没有接收到的第二调度命令指示的第二调度资源，根据预先配置的传输业务数据包的时延要求与第一调度资源的对应关系，通过主动发起上行资源的调度请求的方式进行待传输 业务数据包的传输或者在竞争资源上进行第一待传输业务数据包的传输。
其中，所述确定单元包括：
确定所述待传输业务数据包中第一待传输业务数据包为当前接收到的第二调度命令指示的第二调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延低于其它待传输业务数据包的时延。
其中，终端还包括：
第四映射单元，用于接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中的所述第一待传输业务数据包等待传输，则终止所述第一调度资源的传输，将所述第一待传输业务数据包映射到所述第二调度资源上，并进行传输；
第五映射单元，用于接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中没有所述第一待传输业务数据包等待传输，忽略所述第二调度命令。
其中，终止所述第一调度资源的传输包括：
判断确定终止第一调度资源的传输时，如果所述第一调度资源的开始传输时刻没到达时，不进行第一调度资源的传输；或者
在所述第二调度资源的开始传输时刻到达时，终止所述第一调度资源的传输；或者
在所述第二调度资源的开始传输时刻到达时，暂停所述第一调度资源的传输，在所述第二调度资源传输结束时，继续第一调度资源剩余部分的传输。
其中，终端还包括：
重传模块，用于在重传时刻到达时，根据重传调度命令进行所述第一调度资源的重传。
其中，所述确定单元包括：
若当前待传输业务数据包中只包括：一种传输时延要求的待传输业务数据包，且当前接收到的调度命令指示的调度资源的传输时延低于该待传输业务数据包时延要求长度，将所述待传输业务数据包映射到所述上行资源上进行传输。。
本公开的实施例还提供一种业务数据包的传输方法，包括：
向终端发送上行资源的调度命令；
在所述调度命令指示的上行资源上，接收终端根据当前待传输业务数据包的时延要求，映射到所述上行资源上的业务数据包。
其中，在所述调度命令指示的上行资源上，接收终端根据当前待传输业务包的时延要求，映射到所述上行资源上的业务数据包的步骤包括：
在第一调度命令指示的第一调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延要求，映射到所述第一调度资源上的业务数据包；或者在第二调度命令指示的第二调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延，映射到所述第一调度资源上的业务数据包；
其中，第一调度资源上的业务数据包和第二调度资源上的业务数据包是终端判断网络侧设备发送的第一调度命令指示的第一调度资源的传输时延要求是否满足当前待传输业务数据包的时延要求，得到判断结果；并根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输的业务数据包；其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
本公开的实施例还提供一种网络侧设备，包括：
发送模块，用于向终端发送上行资源的调度命令；
接收模块，用于在所述调度命令指示的上行资源上，接收终端根据当前待传输业务数据包的时延要求，映射到所述上行资源上的业务数据包。
其中，所述接收模块包括：
在第一调度命令指示的第一调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延要求，映射到所述第一调度资源上的业务数据包；或者在第二调度命令指示的第二调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延，映射到所述第一调度资源上的业务数据包；
其中，第一调度资源上的业务数据包和第二调度资源上的业务数据包是终端判断网络侧设备发送的第一调度命令指示的第一调度资源的传输时延要 求是否满足当前待传输业务数据包的时延要求，得到判断结果；并根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输的业务数据包；其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
本公开的上述技术方案的有益效果如下：
上述方案使得终端在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；可以根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输。
附图说明
图1为终端内部的数据包的交互传输处理示意图；
图2为终端支持1msTTI传输和短TTI传输的时间关系示意图；
图3为终端支持的1msTTI传输和短TTI传输发生碰撞的示意图；
图4为本公开的第一实施例所述业务数据包的传输方法流程示意图；
图5为本公开的第二实施例所述业务数据包的传输方法流程示意图；
图6为本公开的第三实施例所述业务数据包的传输方法流程示意图；
图7为本公开的第二、三实施例所述业务数据包的传输方法的应用场景整体流程示意图；
图8为图7所示流程的应用场景一进行业务数据包的调度传输的示意图；
图9为图7所示流程的应用场景二进行业务数据包的调度传输的示意图；
图10为图7所示流程的应用场景三进行业务数据包的调度传输的示意图；
图11为本公开的第四实施例所述业务数据包的传输方法流程示意图；
图12为本公开的第五实施例所述业务数据包的传输方法流程示意图；
图13为本公开的第六实施例所述业务数据包的传输方法流程示意图；
图14为本公开的第四、五、六实施例所述业务数据包的传输方法的应用场景整体流程示意图；
图15为图14所示流程的应用场景一进行业务数据包的调度传输的示意 图；
图16为图14所示流程的应用场景二进行业务数据包的调度传输的示意图；
图17为本公开的第八实施例所述终端的结构示意图；
图18为本公开的第九实施例网络侧设备的所述业务数据包的传输方法流程示意图。
具体实施方式
为使本公开要解决的技术问题、技术方案和优点更加清楚，下面将结合附图及具体实施例进行详细描述。
第一实施例
如图4所示，本公开的第一实施例提供一种业务数据包的传输方法，包括：
步骤41，在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
步骤42，根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输。
本公开的实施例，当UE同时具有处理多种TTI的能力(如同时处理1ms TTI和短TTI能力)时，在收到eNB上行资源的调度时，根据待传业务数据包的时延要求，进行待传数据包在上行资源上的映射并进行传输。
第二实施例
如图5所示，本公开的第二实施例提供一种业务数据包的传输方法，包括：
步骤51，在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
步骤52，判断网络侧设备发送的第一调度命令指示的第一调度资源的第一传输时延是否满足当前待传输业务数据包的时延要求，得到判断结果；
步骤53，根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输；其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
如果终端支持多个不同传输时延的调度资源传输的情况下，各个调度资源的传输时延互不相同。
可选的，所述第一传输时延大于第二传输时延。
下面以终端支持2个调度资源传输的情况为例进行说明：
上述步骤53中，根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上的步骤包括：
步骤531，若第一调度资源的第一传输时延满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，则将所述第一待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输；
进一步的，若当前待传输业务数据包中还包括：具有第二时延要求的第二待传输业务数据包，且所述第二时延要求的长度大于所述第一时延要求的长度，则将所述第一待传输业务数据包和所述第二待传输业务数据包的至少一部分映射到所述第一调度资源上，并在所述第一传输时延内传输。
如缓存中，当前待传输业务数据包除RB1之外，还包括RB2等待传输业务包，且RB2的传输时延高于RB1的传输时延，即RB1是低时延的业务数据包，可以将RB1和部分RB2映射到第一调度资源上，并在所述第一调度资源的第一传输时延内传输。
步骤532，若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，则将所述当前待传输业务数据包中，除所述第一待传输业务数据包外的其它待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输。
例如：终端支持1ms的TTI对应的第一调度资源(TB1)以及小于1ms的TTI对应的第二调度资源(TB2)的传输的情况下，终端根据当前调度的第一调度资源的时延，是否能满足当前待传输业务数据包的时延要求？
若第一调度资源的第一传输时延(例如一次传输或预期次数重传时延) 满足当前待传输业务数据包中第一待传输业务数据包(如RB1)的第一时延要求，则将所述第一待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输；
若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包(如RB1)的第一时延要求，则将所述当前待传输业务数据包中，除所述第一待传输业务数据包外的其它待传输业务数据包(如缓存中，当前待传输业务数据包除RB1之外，还包括RB2等待传输业务包，且RB2的传输时延高于RB1的传输时延，即RB1是低时延的业务数据包)映射到所述第一调度资源上，并在所述第一传输时延内传输。此时，RB1将会等待第二调度命令指示的第二调度资源的到来。
上述步骤53中，根据所述判断结果，将所述待传输业务数据包映射到之后接收到的第二调度命令指示的第二调度资源的步骤包括：
步骤533，若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，且之后接收到所述网络侧设备发送的第二调度命令指示的具有第二传输时延的第二调度资源，则将所述第一待传输业务数据包映射到所述第二调度资源上。
进一步的，步骤534，若所述第一调度资源的传输时延要求不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，且之后一预设时间段内没有接收到的第二调度命令指示的第二调度资源，则通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行待传输业务数据包的传输。
第三实施例
上述第二实施例的基础上，在第一调度资源和第二调度资源发生碰撞时处理，如图6所示，本公开的第三实施例还提供一种业务数据包的传输方法，包括：
步骤61，在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
步骤62，判断网络侧设备发送的第一调度命令指示的第一调度资源的第 一传输时延是否满足当前待传输业务数据包的时延要求，得到判断结果；
步骤63，根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输；
步骤64，接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中具有时延要求低于所述第一待传输业务数据包的第二待传输业务数据包，则终止所述第一调度资源的传输，将所述第二待传输业务数据包映射到所述第二调度资源上，并进行传输；
若当前待传输业务数据包中没有时延低于所述第一待传输业务数据包的其他数据包，忽略所述第二调度命令。
例如，终端在1ms TTI和短TTI碰撞时，将1ms TTI上的第一调度资源对应的传输块记为TB1，UE处理方式为：
UE如果没有更低时延业务数据包待传(该业务数据包未映射到TB1中)，忽略短TTI上的第二调度资源的分配，继续发送TB1；
UE如果有更低时延业务数据包待传(该更低时延业务数据包(如RB3)未映射到TB1中)，将待传低时延业务数据包(RB3)映射到TB2，在短TTI资源上映射和发送。
UE可以终止TB1在本1ms TTI的传输，在下次重传时刻进行重传。
这里的终止所述第一调度资源的传输包括：
第一种情况：在所述第一调度资源的开始传输时刻没到达时，终止所述第一调度资源的传输；例如，第一调度资源对应的传输块TB1的开始传输时刻为t1，第二调度资源对应的传输块TB2的开始传输时刻为t2，如果在t1时刻开始前确定将会因为传输TB2终止TB1的传输，从t1开始就不传TB1，等待t2时刻开始传输TB2；
第二种情况：在所述第二调度资源的开始传输时刻到达时，终止所述第一调度资源的传输，例如，只在TB2位置不传TB1的数据符号，即相当于传输TB2的资源位置为TB1传输的打孔位置。
在重传时刻到达时，根据重新传输调度命令进行所述第一调度资源的重新传输。
下面结合具体的调度场景说明上述各实施例的总体流程以及第二实施例至第三实施例分别对应的方法的过程，如图7所示，
步骤101，接收调度命令1(对应1ms TTI)；
步骤102，判断该1msTTI对应的传输块TB1的传输时延是否满足当前待传输业务数据包RB1的时延要求？
步骤103，若1msTTI对应的传输块TB1的传输时延不满足当前待传输业务数据包RB1的时延要求，只将缓存中待传输业务数据包中除RB1以外的其它RB数据包，映射到TB1；
步骤104，等待短TTI(小于1msTTI)的调度，如果有短TTI，则将RB1映射到在该短TTI对应的传输块TB2上传输；
步骤105，如果在一预设时间段内，没有短TTI，则可以发起调度请求或者在竞争资源上传输RB1；
步骤106，若1msTTI对应的传输块TB1的传输时延满足当前待传输业务数据包RB1的时延要求，则将RB1或者进一步将可容纳的其它待传输业务数据包RB2的一部分或者全部映射到TB1，并进行传输；
步骤107，之后接收到调度命令2时，该调度命令2对应的是短TTI的传输块TB2，若短TTI和1msTTI发生碰撞，判断缓存中待传输业务数据包中是否有更低时延的业务数据包(RB3)待传输？其中，RB2的时延要求小于RB1的时延要求，RB1的时延要求小于RB3的时延要求；
步骤108，如果有，则可以终止TB1的传输，将RB3数据包映射到TB2上传输，否则，进行步骤109；
步骤109，忽略调度命令2。
步骤110，在TB1的重传时刻到来时，可以重传TB1。
实现场景一：
如图8所示，UE根据是否能满足时延需求确定是否在1ms TTI传输低时延业务数据包(情况1)
调度命令1分配1ms TTI上行资源，从t1时刻开始传输；调度命令2分配短TTI上行资源，从t2时刻开始传输；UE在调度命令1前缓存的承载数据包分别为RB1的数据包和RB2的数据包，RB1是低时延业务承载。
UE侧：
步骤一：UE接收调度命令1，判断t1时刻开始的1ms TTI满足RB1的时延要求；
步骤二：将RB1的数据包及可容纳的RB2的数据包组织到TB1中；
步骤三：UE接收调度命令2，判断没有更低时延要求业务数据包，忽略调度命令2；
步骤四：t1时刻开始，在1ms TTI上传输TB1。第三、四步根据时间先后顺序可以互换。
基站侧：
步骤一：发送调度命令1，分配t1时刻开始的1ms TTI上的上行传输资源；
步骤二：发送调度命令2，分配t2时刻开始的短TTI上的上行传输资源，1ms TTI与短TTI资源碰撞；
步骤三：eNB在t1时刻开始接收1ms TTI的TB1，在t2时刻开始接收短TTI的TB2；
步骤四：eNB对接收到的上行传输进行数据解析，正确接收TB1，判断出TB2没有数据传输。
实现场景二：
如图9所示，UE根据是否能满足时延需求确定是否在1ms TTI传输低时延业务数据包(情况2)
调度命令1分配1ms TTI上行资源，从t1时刻开始传输；调度命令2分配短TTI上行资源，从t2时刻开始传输；UE在调度命令1前缓存的承载数据包分别为RB1的数据包和RB2的数据包，RB1是低时延业务承载。
UE侧：
步骤一：UE接收调度命令1，判断t1时刻开始的1ms TTI不能满足RB1的时延要求；
步骤二：将RB2的数据包组织到TB1中；
步骤三：t1时刻开始，在1ms TTI上传输TB1。
步骤四：UE接收调度命令2，将RB1数据包组织到TB2中；
步骤五：t2时刻开始，终止TB1传输，传输TB2。
步骤五有两个优化方向，1)如果在t1时刻开始前确定将会因为传输TB2终止TB1的传输，从t1开始就不传TB1，等待t2时刻开始传输TB2。2)只在TB2位置不传TB1的数据符号，即相当于传输TB2的资源位置为TB1传输的打孔位置。优化2)下，eNB有可能正确解析TB1。
步骤六：UE重传TB1。(不考虑步骤五优化2)，则默认TB1当前传输失败)
基站侧：
步骤一：发送调度命令1，分配t1时刻开始的1ms TTI上的上行传输资源；
步骤二：发送调度命令2，分配t2时刻开始的短TTI上的上行传输资源，1ms TTI与短TTI资源碰撞；
步骤三：eNB在t1时刻开始接收1ms TTI的TB1，在t2时刻开始接收短TTI的TB2；
步骤四：eNB对接收到的上行传输进行数据解析，正确接收TB2，判断出TB1被终止(或者按照UE侧步骤五优化2)，基站有可能正确接收TB1)。
实现场景三：
如图10所示，UE根据是否能满足时延需求确定是否在1ms TTI传输低时延业务数据包(情况3)
调度命令1分配1ms TTI上行资源，从t1时刻开始传输；调度命令2分配短TTI上行资源，从t2时刻开始传输；UE在调度命令1前缓存的承载数据包分别为RB1的数据包和RB2的数据包，RB1是低时延业务承载；在调度命令1之后，有更低时延业务数据包RB3的数据包到达UE缓存。
UE侧：
步骤一：UE接收调度命令1，判断t1时刻开始的1ms TTI能满足RB1的时延要求；
步骤二：将RB1的数据包及可容纳的RB2的数据包组织到TB1中；
步骤三：t1时刻开始，在1ms TTI上传输TB1。
步骤四：UE接收调度命令2，判断有更低时延要求业务数据包RB3中数 据包待传，将其组织到TB2；
步骤五：t2时刻开始，终止TB1传输，传输TB2。
步骤五有两个优化方向，1)如果在t1时刻开始前确定将会因为传输TB2终止TB1的传输，从t1开始就不传TB1，等待t2时刻开始传输TB2。2)只在TB2位置不传TB1的数据符号，即相当于传输TB2的资源位置为TB1传输的打孔位置。优化2)下，eNB有可能正确解析TB1。
步骤六：UE重传TB1。(不考虑步骤五优化2)，则默认TB1当前传输失败)
基站侧：
步骤一：发送调度命令1，分配t1时刻开始的1ms TTI上的上行传输资源；
步骤二：发送调度命令2，分配t2时刻开始的短TTI上的上行传输资源，1ms TTI与短TTI资源碰撞；
步骤三：eNB在t1时刻开始接收1ms TTI的TB1，在t2时刻开始接收短TTI的TB2；
步骤四：eNB对接收到的上行传输进行数据解析，正确接收TB2，判断出TB1被终止(或者按照UE侧步骤五优化2)，基站有可能正确接收TB1。
第四实施例
如图11所示，本公开的第四实施例提供一种业务数据的传输方法，包括：
步骤111，在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
步骤112，根据预先配置的传输业务数据包的时延要求与调度资源的对应关系，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包；将所述待传输业务数据包映射到所述调度资源上进行传输。
具体来说，确定待传输业务数据包中除第一待传输业务数据包之外的其它待传输业务数据包为当前接收到的调度命令指示的第一调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延要求 低于其它待传输业务数据包的时延要求。
并进一步，还可以包括：
步骤113，在一预设时间段内，没有接收到的第二调度命令指示的第二调度资源，根据预先配置的传输业务数据包的时延要求与第一调度资源的对应关系，通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行第一待传输业务数据包的传输。
第五实施例
如图12所示，本公开的第五实施例提供一种业务数据的传输方法，包括：
步骤121，在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
步骤122，根据预先配置的传输业务数据包的时延要求与第一调度资源的对应关系，确定所述待传输业务数据包中第一待传输业务数据包为当前接收到的第二调度命令指示的第二调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延低于其它待传输业务数据包的时延。
进一步的，还包括：
步骤123，接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中的所述第一待传输业务数据包等待传输，则终止所述第一调度资源的传输，将所述第一待传输业务数据包映射到所述第二调度资源上，并进行传输；
步骤124，接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中没有所述第一待传输业务数据包等待传输，忽略所述第二调度命令。
这里的终止所述第一调度资源的传输包括：
第一种情况：判断确定终止第一调度资源的传输时，如果所述第一调度资源的开始传输时刻没到达时，不进行第一调度资源的传输；例如，第一调度资源对应的传输块TB1的开始传输时刻为t1，第二调度资源对应的传输块TB2的开始传输时刻为t2，如果在t1时刻开始前确定将会因为传输TB2终止 TB1的传输，从t1开始就不传TB1，等待t2时刻开始传输TB2；
第二种情况：在所述第二调度资源的开始传输时刻到达时，终止所述第一调度资源的传输，例如，只在TB2位置不传TB1的数据符号，即相当于传输TB2的资源位置为TB1传输的打孔位置。
第三种情况：在所述第二调度资源的开始传输时刻到达时，暂停所述第一调度资源的传输，在所述第二调度资源传输结束时，继续第一调度资源剩余部分的传输。
重传时刻到达时，根据重传调度命令进行所述第一调度资源的重传。
第六实施例
如图13所示，本公开的第六实施例提供一种业务数据的传输方法，包括：
步骤131，在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
步骤132，根据预先配置的传输业务数据包的时延要求与第一调度资源的对应关系，若当前待传输业务数据包中只包括：一种传输时延要求的待传输业务数据包，且当前接收到的调度命令指示的调度资源的传输时延低于该待传输业务数据包时延要求长度，将所述待传输业务数据包映射到所述上行资源上进行传输。
如图14，下面结合具体的调度场景说明上述各实施例的总体流程以及第四实施例至第六实施例分别对应的方法的过程，
步骤141，接收调度命令1(对应1ms TTI)；
步骤142，将RB1以外的其它RB的数据包映射到TB1；
步骤143，等待短TTI的调度的第二调度资源TB2，如果有短TTI，则将RB1映射到在该短TTI对应的传输块TB2上传输；或者如果在一预设时间段内，没有短TTI，则发起调度请求或者在竞争资源上传输RB1的数据包；
步骤144，在TB1的开始传输时刻到来时，进行传输；
步骤145，若接收到调度命令2，对应短TTI，若发生短TTI和1msTTI发生碰撞；
步骤146，判断缓存中待传输业务数据包中是否有低时延的业务数据包 (RB1)待传输？
步骤147，如果有，则可以终止TB1的传输，将RB1数据包映射到TB2上传输，否则，进行步骤148；
步骤148，忽略调度命令2。或者如果UE得到短TTI资源分配，而缓存中没有低时延业务数据包，也可以传输其他业务数据包(RB2)。
步骤149，在TB1的重传时刻到来时，可以重传TB1。
实现场景一：
如图15所示，UE根据TTI长度传输不同时延需求数据包(情况1)
调度命令1分配1ms TTI上行资源，从t1时刻开始传输；调度命令2分配短TTI上行资源，从t2时刻开始传输；UE在调度命令1前缓存的承载数据包分别为RB1的数据包和RB2的数据包，RB1是低时延业务承载。
UE侧：
步骤一：UE接收调度命令1，判断分配的资源是1ms TTI；
步骤二：将RB2的数据包组织到TB1中；
步骤三：t1时刻开始，在1ms TTI上传输TB1。
步骤四：UE接收调度命令2，将RB1数据包组织到TB2中；
步骤五：t2时刻开始，终止TB1传输，传输TB2。
步骤五有两个优化方向，1)如果在t1时刻开始前确定将会因为传输TB2终止TB1的传输，从t1开始就不传TB1，等待t2时刻开始传输TB2。2)只在TB2位置不传TB1的数据符号，即相当于传输TB2的资源位置为TB1传输的打孔位置。优化2)下，eNB有可能正确解析TB1。
步骤六：UE重传TB1。(不考虑步骤五优化2)，则默认TB1当前传输失败)
基站侧：
步骤一：发送调度命令1，分配t1时刻开始的1ms TTI上的上行传输资源；
步骤二：发送调度命令2，分配t2时刻开始的短TTI上的上行传输资源，1ms TTI与短TTI资源碰撞；
步骤三：eNB在t1时刻开始接收1ms TTI的TB1，在t2时刻开始接收短 TTI的TB2；
步骤四：eNB对接收到的上行传输进行数据解析，正确接收TB2，判断出TB1被终止(或者按照UE侧步骤五优化2)，基站有可能正确接收TB1。
场景二：
如图16所示，UE根据TTI长度传输不同时延需求数据包(情况2)
调度命令分配短TTI上行资源，从t2时刻开始传输；UE在调度命令前缓存的承载数据包只有时延要求不高的RB2的数据包。
UE侧：
步骤一：UE接收调度命令，判断分配的资源是短TTI；
步骤二：将RB2的数据包组织到TB2中；
步骤三：t2时刻开始，在短TTI上传输TB1。
基站侧：
步骤一：发送调度命令，分配t2时刻开始的短TTI上行传输资源；
步骤二：eNB在t2时刻开始接收短TTI的TB2；
步骤三：eNB对接收到的上行传输进行数据解析，正确接收TB2。
本公开的上述实施例中所述的方法适用于长TTI(1ms TTI)、短TTI长度冲突的一般场景，不限于1ms和短TTI冲突。如果在1ms TTI和短TTI碰撞时，如果UE不能同时使用两次调度的资源进行数据发送，通过本公开的上述实施例所述的方法确保时延敏感的业务的数据被优先传输。
第七实施例
本公开的第七实施例还提供一种终端，包括：
获取模块，用于在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
传输模块，用于根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输。
其中，所述传输模块具体用于：
判断单元，用于判断网络侧设备发送的第一调度命令指示的第一调度资源的第一传输时延是否满足当前待传输业务数据包的时延要求，得到判断结 果；
第一映射单元，用于根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输；
其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
其中，所述第一传输时延大于第二传输时延。
其中，所述第一映射单元包括：
若第一调度资源的第一传输时延满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，则将所述第一待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输；
若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的时延要求，则将所述当前待传输业务数据包中，除所述第一待传输业务数据包外的其它待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输。
其中，若当前待传输业务数据包中还包括：具有第二时延要求的第二待传输业务数据包，且所述第二时延要求的长度大于所述第一时延要求的长度，所述第一映射单元将所述第一待传输业务数据包和所述第二待传输业务数据包的至少一部分映射到所述第一调度资源上，并在所述第一传输时延内传输。
其中，所述第一映射单元包括：
若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的时延要求，且之后接收到所述网络侧设备发送的第二调度命令指示的具有第二传输时延的第二调度资源，则将所述第一待传输业务数据包映射到所述第二调度资源上。
其中，上述终端还包括：
第二映射单元，用于接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中具有时延要求低于所述第一待传输业务数据包的第二待传输业务数据包，则终止所述第一调度资源的传输，将所述第二待传输业务数据包映射到所述第二调度资源上，并进行传输；
第三映射单元，若当前待传输业务数据包中没有时延低于所述第一待传输业务数据包的其他数据包，忽略所述第二调度命令。
其中，上述终端还包括：
第一请求传输模块，用于若所述第一调度资源的传输时延要求不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，且之后一预设时间段内没有接收到的第二调度命令指示的第二调度资源，则通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行待传输业务数据包的传输。
其中，所述传输模块包括：
确定单元，用于根据预先配置的传输业务数据包的时延要求与调度资源的对应关系，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包；
传输单元，用于将所述待传输业务数据包映射到所述调度资源上进行传输。
其中，所述确定单元包括：
确定待传输业务数据包中除第一待传输业务数据包之外的其它待传输业务数据包为当前接收到的调度命令指示的第一调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延要求低于其它待传输业务数据包的时延要求。
其中，终端还包括：
第二请求传输模块，用于在一预设时间段内，没有接收到的第二调度命令指示的第二调度资源，根据预先配置的传输业务数据包的时延要求与第一调度资源的对应关系，通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行第一待传输业务数据包的传输。
其中，所述确定单元包括：
确定所述待传输业务数据包中第一待传输业务数据包为当前接收到的第二调度命令指示的第二调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延低于其它待传输业务数据包的时延。
其中，终端还包括：
第四映射单元，用于接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中的所述第一待传输业务数据包等待传输，则终止所述第一调度资源的传输，将所述第一待传输业务数据包映射到所述第二调度资源上，并进行传输；
第五映射单元，用于接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中没有所述第一待传输业务数据包等待传输，忽略所述第二调度命令。
其中，终止所述第一调度资源的传输包括：
判断确定终止第一调度资源的传输时，如果所述第一调度资源的开始传输时刻没到达时，不进行第一调度资源的传输；或者
在所述第二调度资源的开始传输时刻到达时，终止所述第一调度资源的传输；或者
在所述第二调度资源的开始传输时刻到达时，暂停所述第一调度资源的传输，在所述第二调度资源传输结束时，继续第一调度资源剩余部分的传输。
其中，终端还包括：
重传模块，用于在重传时刻到达时，根据重传调度命令进行所述第一调度资源的重传。
其中，所述确定单元包括：
若当前待传输业务数据包中只包括：一种传输时延要求的待传输业务数据包，且当前接收到的调度命令指示的调度资源的传输时延低于该待传输业务数据包时延要求长度，将所述待传输业务数据包映射到所述上行资源上进行传输。
需要说明的是：该终端是与上述方法对应的终端，上述方法实施例中所有实现方式均适用于该终端，也能达到相同的技术效果。
第八实施例
如图17所示，本公开的第八实施例还提供一种终端，包括：处理器600；以及通过总线接口与所述处理器600相连接的存储器620，所述存储器620用于存储所述处理器在执行操作时所使用的程序和数据，当处理器600调用并执行所述存储器620中所存储的程序和数据时，所述处理器被配置实现如 下功能：在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输。
其中，在图17中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器600代表的一个或多个处理器和存储器620代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机610可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口630还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。处理器600负责管理总线架构和通常的处理，存储器620可以存储处理器600在执行操作时所使用的数据。
第九实施例
如图18所示，本公开的第九实施例还提供一种业务数据包的传输方法，包括：
步骤181，向终端发送上行资源的调度命令；
步骤182，在所述调度命令指示的上行资源上，接收终端根据当前待传输业务数据包的时延要求，映射到所述上行资源上的业务数据包。
其中，步骤182包括：
在第一调度命令指示的第一调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延要求，映射到所述第一调度资源上的业务数据包；或者在第二调度命令指示的第二调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延，映射到所述第一调度资源上的业务数据包；
其中，第一调度资源上的业务数据包和第二调度资源上的业务数据包是终端判断网络侧设备发送的第一调度命令指示的第一调度资源的传输时延要求是否满足当前待传输业务数据包的时延要求，得到判断结果；并根据所述 判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输的业务数据包；其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
第十实施例
本公开的第十实施例还提供网络侧设备，包括：
发送模块，用于向终端发送上行资源的调度命令；
接收模块，用于在所述调度命令指示的上行资源上，接收终端根据当前待传输业务数据包的时延要求，映射到所述上行资源上的业务数据包。
其中，所述接收模块包括：
在第一调度命令指示的第一调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延要求，映射到所述第一调度资源上的业务数据包；或者在第二调度命令指示的第二调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延，映射到所述第一调度资源上的业务数据包；
其中，第一调度资源上的业务数据包和第二调度资源上的业务数据包是终端判断网络侧设备发送的第一调度命令指示的第一调度资源的传输时延要求是否满足当前待传输业务数据包的时延要求，得到判断结果；并根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输的业务数据包；其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
需要说明的是，该网络侧设备可以是基站，是与上述网络侧设备所述的方法对应的装置，上述实施例中所有实现方式均适用于该终端的实施例中，也能达到与上述方法相同的效果。
第十一实施例
本公开的第十一实施例还提供一种网络侧设备，包括：处理器；通过总线接口与所述处理器相连接的存储器，以及通过总线接口与处理器相连接的收发机；所述存储器用于存储所述处理器在执行操作时所使用的程序和数据； 通过所述收发机发送数据信息或者导频，还通过所述收发机接收下行控制信道；当处理器调用并执行所述存储器中所存储的程序和数据时，所述处理器被配置实现如下功能：向终端发送上行资源的调度命令；在所述调度命令指示的上行资源上，接收终端根据当前待传输业务数据包的时延要求，映射到所述上行资源上的业务数据包。
本公开的上述实施例中所述的方法适用于长TTI(1ms TTI)、短TTI长度冲突的一般场景，不限于1ms和短TTI冲突。如果在1ms TTI和短TTI碰撞时，如果UE不能同时使用两次调度的资源进行数据发送，通过本公开的上述实施例所述的方法确保时延敏感的业务的数据被优先传输。
以上结合具体实施例描述了本公开的基本原理，但是，需要指出的是，对本领域的普通技术人员而言，能够理解本公开的方法和装置的全部或者任何步骤或者部件，可以在任何计算装置(包括处理器、存储介质等)或者计算装置的网络中，以硬件、固件、软件或者它们的组合加以实现，这是本领域普通技术人员在阅读了本公开的说明的情况下运用他们的基本编程技能就能实现的。
因此，本公开的目的还可以通过在任何计算装置上运行一个程序或者一组程序来实现。所述计算装置可以是公知的通用装置。因此，本公开的目的也可以仅仅通过提供包含实现所述方法或者装置的程序代码的程序产品来实现。也就是说，这样的程序产品也构成本公开，并且存储有这样的程序产品的存储介质也构成本公开。显然，所述存储介质可以是任何公知的存储介质或者将来所开发出来的任何存储介质。还需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行。某些步骤可以并行或彼此独立地执行。
以上所述是本公开的可选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本公开所述原理的前提下，还可以作出若干改进和润饰，这些改进和润饰也应视为本公开的保护范围。

Claims (38)

  1. 一种业务数据包的传输方法，包括：
    在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
    根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输。
  2. 根据权利要求1所述的业务数据包的传输方法，其中，根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输的步骤包括：
    判断网络侧设备发送的第一调度命令指示的第一调度资源的第一传输时延是否满足当前待传输业务数据包的时延要求，得到判断结果；
    根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输；
    其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
  3. 根据权利要求2所述的业务数据包的传输方法，其中，所述第一传输时延大于第二传输时延。
  4. 根据权利要求3所述的业务数据包的传输方法，其中，根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上，并进行传输的步骤包括：
    若第一调度资源的第一传输时延满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，则将所述第一待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输；
    若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，则将所述当前待传输业务数据包中，除所述第一待传输业务数据包外的其它待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输。
  5. 根据权利要求4所述的业务数据包的传输方法，其中，若当前待传输 业务数据包中还包括：具有第二时延要求的第二待传输业务数据包，且所述第二时延要求的长度大于所述第一时延要求的长度，则将所述第一待传输业务数据包和所述第二待传输业务数据包的至少一部分映射到所述第一调度资源上，并在所述第一传输时延内传输。
  6. 根据权利要求2所述的业务数据包的传输方法，其中，根据所述判断结果，将所述待传输业务数据包映射到之后接收到的第二调度命令指示的第二调度资源的步骤包括：
    若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，且之后接收到所述网络侧设备发送的第二调度命令指示的具有第二传输时延的第二调度资源，则将所述第一待传输业务数据包映射到所述第二调度资源上。
  7. 根据权利要求4或6所述的业务数据包的传输方法，还包括：
    接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中具有时延要求低于所述第一待传输业务数据包的第二待传输业务数据包，则终止所述第一调度资源的传输，将所述第二待传输业务数据包映射到所述第二调度资源上，并进行传输；
    若当前待传输业务数据包中没有时延低于所述第一待传输业务数据包的其他数据包，忽略所述第二调度命令。
  8. 根据权利要求2所述的业务数据包的传输方法，还包括：
    若所述第一调度资源的传输时延要求不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，且之后一预设时间段内没有接收到的第二调度命令指示的第二调度资源，则通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行待传输业务数据包的传输。
  9. 根据权利要求1所述的业务数据包的传输方法，其中，根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输的步骤包括：
    根据预先配置的传输业务数据包的时延要求与调度资源的对应关系，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务 数据包；
    将所述待传输业务数据包映射到所述调度资源上进行传输。
  10. 根据权利要求9所述的业务数据包的传输方法，其中，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包的步骤包括：
    确定待传输业务数据包中除第一待传输业务数据包之外的其它待传输业务数据包为当前接收到的调度命令指示的第一调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延要求低于其它待传输业务数据包的时延要求。
  11. 根据权利要求10所述的业务数据包的传输方法，其中，将所述其它待传输业务数据包映射到所述第一调度资源上之后还包括：
    在一预设时间段内，没有接收到的第二调度命令指示的第二调度资源，根据预先配置的传输业务数据包的时延要求与第一调度资源的对应关系，通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行第一待传输业务数据包的传输。
  12. 根据权利要求9所述的业务数据包的传输方法，其中，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包的步骤包括：
    确定所述待传输业务数据包中第一待传输业务数据包为当前接收到的第二调度命令指示的第二调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延低于其它待传输业务数据包的时延。
  13. 根据权利要求12所述的业务数据包的传输方法，还包括：
    接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中的所述第一待传输业务数据包等待传输，则终止所述第一调度资源的传输，将所述第一待传输业务数据包映射到所述第二调度资源上，并进行传输；
    接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中没有所述第一待传输业务数据包等待传输，忽略所述第二调度命令。
  14. 根据权利要求7或13所述的业务数据包的传输方法，其中，终止所述第一调度资源的传输包括：
    判断确定终止第一调度资源的传输时，如果所述第一调度资源的开始传输时刻没到达时，不进行第一调度资源的传输；或者
    在所述第二调度资源的开始传输时刻到达时，终止所述第一调度资源的传输；或者
    在所述第二调度资源的开始传输时刻到达时，暂停所述第一调度资源的传输，在所述第二调度资源传输结束时，继续第一调度资源剩余部分的传输。
  15. 根据权利要求7或13所述的业务数据包的传输方法，其中，终止所述第一调度资源的传输后还包括：
    重传时刻到达时，根据重传调度命令进行所述第一调度资源的重传。
  16. 根据权利要求9所述的业务数据包的传输方法，其中，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包的步骤包括：
    若当前待传输业务数据包中只包括：一种传输时延要求的待传输业务数据包，且当前接收到的调度命令指示的调度资源的传输时延低于该待传输业务数据包时延要求长度，将所述待传输业务数据包映射到所述上行资源上进行传输。
  17. 一种终端，包括：
    获取模块，用于在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
    传输模块，用于根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输。
  18. 根据权利要求17所述的终端，其中，所述传输模块具体用于：
    判断单元，用于判断网络侧设备发送的第一调度命令指示的第一调度资源的第一传输时延是否满足当前待传输业务数据包的时延要求，得到判断结果；
    第一映射单元，用于根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输；
    其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
  19. 根据权利要求18所述的终端，其中，所述第一传输时延大于第二传输时延。
  20. 根据权利要求19所述的终端，其中，所述第一映射单元用于：
    若第一调度资源的第一传输时延满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，则将所述第一待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输；
    若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的时延要求，则将所述当前待传输业务数据包中，除所述第一待传输业务数据包外的其它待传输业务数据包映射到所述第一调度资源上，并在所述第一传输时延内传输。
  21. 根据权利要求20所述的终端，其中，若当前待传输业务数据包中还包括：具有第二时延要求的第二待传输业务数据包，且所述第二时延要求的长度大于所述第一时延要求的长度，所述第一映射单元将所述第一待传输业务数据包和所述第二待传输业务数据包的至少一部分映射到所述第一调度资源上，并在所述第一传输时延内传输。
  22. 根据权利要求18所述的终端，其中，所述第一映射单元用于：
    若第一调度资源的第一传输时延不满足当前待传输业务数据包中第一待传输业务数据包的时延要求，且之后接收到所述网络侧设备发送的第二调度命令指示的具有第二传输时延的第二调度资源，则将所述第一待传输业务数据包映射到所述第二调度资源上。
  23. 根据权利要求20或22所述的终端，还包括：
    第二映射单元，用于接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中具有时延要求低于所述第一待传输业务数据包的第二待传输业务数据包，则终止所述第一调度资源的传输，将所述第二待传输业务数据包映射到所述第二调度资源上，并进行传输；
    第三映射单元，若当前待传输业务数据包中没有时延低于所述第一待传输业务数据包的其他数据包，忽略所述第二调度命令。
  24. 根据权利要求18所述的终端，还包括：
    第一请求传输模块，用于若所述第一调度资源的传输时延要求不满足当前待传输业务数据包中第一待传输业务数据包的第一时延要求，且之后一预设时间段内没有接收到的第二调度命令指示的第二调度资源，则通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行待传输业务数据包的传输。
  25. 根据权利要求17所述的终端，其中，所述传输模块包括：
    确定单元，用于根据预先配置的传输业务数据包的时延要求与调度资源的对应关系，确定与当前接收到的调度命令指示的调度资源的传输时延相对应的待传输业务数据包；
    传输单元，用于将所述待传输业务数据包映射到所述调度资源上进行传输。
  26. 根据权利要求25所述的终端，其中，所述确定单元包括：
    确定待传输业务数据包中除第一待传输业务数据包之外的其它待传输业务数据包为当前接收到的调度命令指示的第一调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延要求低于其它待传输业务数据包的时延要求。
  27. 根据权利要求26所述的终端，还包括：
    第二请求传输模块，用于在一预设时间段内，没有接收到的第二调度命令指示的第二调度资源，根据预先配置的传输业务数据包的时延要求与第一调度资源的对应关系，通过主动发起上行资源的调度请求的方式进行待传输业务数据包的传输或者在竞争资源上进行第一待传输业务数据包的传输。
  28. 根据权利要求25所述的终端，其中，所述确定单元包括：
    确定所述待传输业务数据包中第一待传输业务数据包为当前接收到的第二调度命令指示的第二调度资源的传输时延相对应的待传输业务数据包；其中，所述第一传输业务数据包的时延低于其它待传输业务数据包的时延。
  29. 根据权利要求28所述的终端，还包括：
    第四映射单元，用于接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中的所述第一待传输业务数据包等待传输，则终止所述 第一调度资源的传输，将所述第一待传输业务数据包映射到所述第二调度资源上，并进行传输；
    第五映射单元，用于接收到第二调度命令指示的第二调度资源时，若当前待传输业务数据包中没有所述第一待传输业务数据包等待传输，忽略所述第二调度命令。
  30. 根据权利要求23或29所述的终端，其中，终止所述第一调度资源的传输包括：
    判断确定终止第一调度资源的传输时，如果所述第一调度资源的开始传输时刻没到达时，不进行第一调度资源的传输；或者
    在所述第二调度资源的开始传输时刻到达时，终止所述第一调度资源的传输；或者
    在所述第二调度资源的开始传输时刻到达时，暂停所述第一调度资源的传输，在所述第二调度资源传输结束时，继续第一调度资源剩余部分的传输。
  31. 根据权利要求23或29所述的终端，还包括：
    重传模块，用于在重传时刻到达时，根据重传调度命令进行所述第一调度资源的重传。
  32. 根据权利要求25所述的终端，其中，所述确定单元包括：
    若当前待传输业务数据包中只包括：一种传输时延要求的待传输业务数据包，且当前接收到的调度命令指示的调度资源的传输时延低于该待传输业务数据包时延要求长度，将所述待传输业务数据包映射到所述上行资源上进行传输。
  33. 一种业务数据包的传输方法，包括：
    向终端发送上行资源的调度命令；
    在所述调度命令指示的上行资源上，接收终端根据当前待传输业务数据包的时延要求，映射到所述上行资源上的业务数据包。
  34. 根据权利要求33所述的业务数据包的传输方法，其中，在所述调度命令指示的上行资源上，接收终端根据当前待传输业务包的时延要求，映射到所述上行资源上的业务数据包的步骤包括：
    在第一调度命令指示的第一调度资源的开始传输时刻，开始接收终端根 据当前待传输业务数据包的时延要求，映射到所述第一调度资源上的业务数据包；或者在第二调度命令指示的第二调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延，映射到所述第一调度资源上的业务数据包；
    其中，第一调度资源上的业务数据包和第二调度资源上的业务数据包是终端判断网络侧设备发送的第一调度命令指示的第一调度资源的传输时延要求是否满足当前待传输业务数据包的时延要求，得到判断结果；并根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输的业务数据包；其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
  35. 一种网络侧设备，包括：
    发送模块，用于向终端发送上行资源的调度命令；
    接收模块，用于在所述调度命令指示的上行资源上，接收终端根据当前待传输业务数据包的时延要求，映射到所述上行资源上的业务数据包。
  36. 根据权利要求35所述的网络侧设备，其中，所述接收模块包括：
    在第一调度命令指示的第一调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延要求，映射到所述第一调度资源上的业务数据包；或者在第二调度命令指示的第二调度资源的开始传输时刻，开始接收终端根据当前待传输业务数据包的时延，映射到所述第一调度资源上的业务数据包；
    其中，第一调度资源上的业务数据包和第二调度资源上的业务数据包是终端判断网络侧设备发送的第一调度命令指示的第一调度资源的传输时延要求是否满足当前待传输业务数据包的时延要求，得到判断结果；并根据所述判断结果，将所述待传输业务数据包映射到所述第一调度资源上或者之后接收到的第二调度命令指示的第二调度资源上，并进行传输的业务数据包；其中，所述第二调度资源的第二传输时延与所述第一调度资源的第一传输时延不同。
  37. 一种终端，包括：处理器以及通过总线接口与所述处理器相连接的存储器；所述存储器用于存储所述处理器在执行操作时所使用的程序和数据；当处理器调用并执行所述存储器中所存储的程序和数据时，所述处理器被配置实现如下功能：
    在接收到网络侧设备发送的上行资源的调度命令时，获取当前待传输业务数据包的属性信息；其中，所述业务数据包的属性信息包括：时延；
    根据当前待传输业务数据包的时延要求，将所述待传输业务数据包映射到所述上行资源上进行传输。
  38. 一种网络侧设备，包括：处理器以及通过总线接口与所述处理器相连接的存储器；所述存储器用于存储所述处理器在执行操作时所使用的程序和数据；当处理器调用并执行所述存储器中所存储的程序和数据时，所述处理器被配置实现如下功能：
    向终端发送上行资源的调度命令；
    在所述调度命令指示的上行资源上，接收终端根据当前待传输业务数据包的时延要求，映射到所述上行资源上的业务数据包。
PCT/CN2017/082977 2016-05-13 2017-05-04 一种业务数据的传输方法、终端及网络侧设备 WO2017193861A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2018559776A JP6765446B2 (ja) 2016-05-13 2017-05-04 サービスデータ伝送方法、端末およびネットワーク側機器
US16/090,579 US11160092B2 (en) 2016-05-13 2017-05-04 Service data transmission method, user equipment and network side device
EP17795479.9A EP3457778B1 (en) 2016-05-13 2017-05-04 Service data transmission method, terminal and network side device
KR1020187036217A KR102184035B1 (ko) 2016-05-13 2017-05-04 서비스 데이터의 전송 방법, 단말기 및 네트워크측 기기

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610320112.4 2016-05-13
CN201610320112.4A CN107371246B (zh) 2016-05-13 2016-05-13 一种业务数据的传输方法、终端及网络侧设备

Publications (1)

Publication Number Publication Date
WO2017193861A1 true WO2017193861A1 (zh) 2017-11-16

Family

ID=60266189

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/082977 WO2017193861A1 (zh) 2016-05-13 2017-05-04 一种业务数据的传输方法、终端及网络侧设备

Country Status (6)

Country Link
US (1) US11160092B2 (zh)
EP (1) EP3457778B1 (zh)
JP (1) JP6765446B2 (zh)
KR (1) KR102184035B1 (zh)
CN (1) CN107371246B (zh)
WO (1) WO2017193861A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108631960B (zh) * 2017-03-24 2021-08-20 华为技术有限公司 一种数据传输方法和相关设备
US10701001B2 (en) * 2018-08-29 2020-06-30 REALTEK SINGAPORE Pte. Ltd. Wireless communication circuit with scheduling circuit in MAC layer
AU2019438207B2 (en) * 2019-03-28 2022-08-11 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for transmitting data and terminal device
CN112911636B (zh) 2019-12-04 2023-01-13 华为技术有限公司 数据处理方法和相关装置
CN111885735B (zh) * 2020-06-30 2023-10-31 广东小天才科技有限公司 一种上行调度指示方法、终端设备及网络设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1578069A1 (en) * 2004-03-18 2005-09-21 Fujitsu Limited Resource reservation for packet switched call during ongoing circuit switched call
CN101330313A (zh) * 2007-06-19 2008-12-24 中兴通讯股份有限公司 一种lte系统中上行调度请求的方法
CN102104974A (zh) * 2011-02-28 2011-06-22 华为技术有限公司 上行预调度处理方法、装置和系统
CN104619034A (zh) * 2015-01-16 2015-05-13 电子科技大学 一种lte通信系统中面向实时业务的分组调度方法
CN105188150A (zh) * 2015-08-12 2015-12-23 中国电子科技集团公司第七研究所 降低lte上行数据传输延时的方法和系统

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070297386A1 (en) * 2005-07-28 2007-12-27 Interdigital Technology Corporation Method and system for scheduling uplink transmissions in a single carrier frequency division multiple access system
EP1909521A1 (en) 2006-10-02 2008-04-09 Matsushita Electric Industrial Co., Ltd. Method for supporting quality of service over a connection lifetime
CN101237278A (zh) * 2007-01-30 2008-08-06 西门子通信技术（北京）有限公司 移动通信中传输数据的方法、系统、中继站及基站
CN101610235A (zh) * 2009-07-17 2009-12-23 中兴通讯股份有限公司南京分公司 一种发射端及数据发射方法
CN102932924B (zh) * 2011-08-11 2015-12-16 华为技术有限公司 上行短时延通信的数据传输方法和设备
CN102970761A (zh) * 2011-09-01 2013-03-13 华为技术有限公司 数据发送方法和用户设备
CN103220102B (zh) * 2012-01-21 2016-12-28 华为技术有限公司 控制信令的传输方法和设备
CN104604287B (zh) * 2013-08-30 2019-04-23 华为技术有限公司 一种无线通信网络数据传输的控制方法及装置
EP3195508A1 (en) * 2014-09-08 2017-07-26 Interdigital Patent Holdings, Inc. Systems and methods of operating with different transmission time interval (tti) durations
US9844072B2 (en) 2014-09-26 2017-12-12 Qualcomm Incorporated Ultra-low latency LTE uplink frame structure
US10727983B2 (en) * 2014-10-29 2020-07-28 Qualcomm Incorporated Variable length transmission time intervals (TTI)
US9603165B2 (en) * 2015-01-30 2017-03-21 Telefonaktiebolaget L M Ericsson (Publ) Random-access response with analog beamforming
US20180020467A1 (en) * 2015-02-03 2018-01-18 Telefonaktiebolaget Lm Ericsson (Publ) Scheduling voice-over-ip users in wireless systems using carrier aggregation
CN107534525A (zh) * 2015-05-14 2018-01-02 华为技术有限公司 一种数据发送方法及装置
CN106664702B (zh) * 2015-08-12 2020-09-04 华为技术有限公司 一种数据传输方法、装置及系统
US10609725B2 (en) * 2015-12-10 2020-03-31 Huawei Technologies Co., Ltd. Data transmission method of system, user equipment, and base station
CN105554892A (zh) * 2016-01-14 2016-05-04 珠海市魅族科技有限公司 用于lte网络的资源配置方法及装置、基站
WO2017127974A1 (zh) * 2016-01-25 2017-08-03 广东欧珀移动通信有限公司 传输数据的方法和终端
HUE053028T2 (hu) * 2016-03-18 2021-06-28 Guangdong Oppo Mobile Telecommunications Corp Ltd Adatátviteli eljárás, végberendezés készülék és hálózati készülék
CN106793135A (zh) * 2016-04-01 2017-05-31 北京展讯高科通信技术有限公司 通信资源调度方法、终端设备和基站设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1578069A1 (en) * 2004-03-18 2005-09-21 Fujitsu Limited Resource reservation for packet switched call during ongoing circuit switched call
CN101330313A (zh) * 2007-06-19 2008-12-24 中兴通讯股份有限公司 一种lte系统中上行调度请求的方法
CN102104974A (zh) * 2011-02-28 2011-06-22 华为技术有限公司 上行预调度处理方法、装置和系统
CN104619034A (zh) * 2015-01-16 2015-05-13 电子科技大学 一种lte通信系统中面向实时业务的分组调度方法
CN105188150A (zh) * 2015-08-12 2015-12-23 中国电子科技集团公司第七研究所 降低lte上行数据传输延时的方法和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3457778A4 *

Also Published As

Publication number Publication date
JP6765446B2 (ja) 2020-10-07
KR102184035B1 (ko) 2020-11-27
EP3457778A1 (en) 2019-03-20
CN107371246A (zh) 2017-11-21
EP3457778A4 (en) 2019-04-24
CN107371246B (zh) 2020-01-10
US11160092B2 (en) 2021-10-26
US20190116606A1 (en) 2019-04-18
JP2019515597A (ja) 2019-06-06
EP3457778B1 (en) 2020-12-23
KR20190002706A (ko) 2019-01-08

Similar Documents

Publication Publication Date Title
WO2017193861A1 (zh) 一种业务数据的传输方法、终端及网络侧设备
US10178676B2 (en) Data transmission method, device, and system
KR101087118B1 (ko) 버퍼 상태 리포트를 유발하기 위한 타이머를 핸들링하는 방법 및 장치
US20240348374A1 (en) Low latency harq protocol for urllc services
US20240224113A1 (en) Scheduling request processing method and terminal device
TWI731061B (zh) 自動重傳的調度方法、終端、網路側設備以及存儲媒介
US20160338044A1 (en) Data transmission method and system, and device
JP7262591B2 (ja) 無線通信方法及び装置
WO2017016351A1 (zh) 一种上行数据的传输方法及装置
CN106171004B (zh) 一种rlc数据包分流方法及基站
WO2006106634A1 (ja) 無線ｌａｎシステム、その基地局および端末局
WO2016029737A1 (zh) 一种数据传输方法及基站
WO2019062838A1 (zh) 数据传输方法及装置
CN113647182B (zh) 无线通信的方法和设备
WO2023185353A1 (zh) 数据传输方法、电子设备和存储介质
CN117561781A (zh) 无线通信方法、终端设备和网络设备
CN113647171B (zh) 无线通信的方法和设备
WO2017193948A1 (zh) 一种数据传输方法及终端
KR102129026B1 (ko) ａＧＰＳ에서 그랜트 구간을 전환 및 동기화하는 방법 및 시스템
US11997704B2 (en) Systems and methods for packet scheduling for integrated 5G and multi-domain TSN systems
CN105429737B (zh) 一种用于帧确认的方法和装置
WO2016074201A1 (zh) 随机接入过程中bsr的上报方法和装置
WO2020263551A1 (en) User equipment-requested semi-persistent scheduling

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2018559776

Country of ref document: JP

Kind code of ref document: A

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

Ref document number: 17795479

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20187036217

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017795479

Country of ref document: EP

Effective date: 20181213