WO2018227501A1 - 传输数据的方法和设备 - Google Patents

传输数据的方法和设备 Download PDF

Info

Publication number
WO2018227501A1
WO2018227501A1 PCT/CN2017/088515 CN2017088515W WO2018227501A1 WO 2018227501 A1 WO2018227501 A1 WO 2018227501A1 CN 2017088515 W CN2017088515 W CN 2017088515W WO 2018227501 A1 WO2018227501 A1 WO 2018227501A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
submitted
delivery mode
window
receiving end
Prior art date
Application number
PCT/CN2017/088515
Other languages
English (en)
French (fr)
Inventor
唐海
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2017/088515 priority Critical patent/WO2018227501A1/zh
Priority to MX2019015070A priority patent/MX2019015070A/es
Priority to PCT/CN2018/077052 priority patent/WO2018227994A1/zh
Priority to JP2019569446A priority patent/JP7143337B2/ja
Priority to SG11201912132XA priority patent/SG11201912132XA/en
Priority to CN202010074394.0A priority patent/CN111294153B/zh
Priority to CA3067481A priority patent/CA3067481A1/en
Priority to KR1020197037932A priority patent/KR20200017424A/ko
Priority to CN201880038288.8A priority patent/CN110771255B/zh
Priority to RU2019143071A priority patent/RU2749896C1/ru
Priority to BR112019026476-0A priority patent/BR112019026476A2/pt
Priority to AU2018286006A priority patent/AU2018286006A1/en
Priority to EP18818444.4A priority patent/EP3621407B1/en
Priority to TW107120592A priority patent/TWI734010B/zh
Publication of WO2018227501A1 publication Critical patent/WO2018227501A1/zh
Priority to CL2019003649A priority patent/CL2019003649A1/es
Priority to IL271375A priority patent/IL271375A/en
Priority to US16/713,948 priority patent/US11050862B2/en
Priority to ZA2019/08560A priority patent/ZA201908560B/en
Priority to US17/338,120 priority patent/US11553067B2/en

Links

Images

Classifications

    • 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • 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/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • 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/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0036—Systems modifying transmission characteristics according to link quality, e.g. power backoff arrangements specific to the receiver
    • 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/1607—Details of the supervisory signal
    • H04L1/1621—Group acknowledgement, i.e. the acknowledgement message defining a range of identifiers, e.g. of sequence numbers
    • 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
    • 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1832—Details of sliding window management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/90—Buffering arrangements
    • H04L49/9057—Arrangements for supporting packet reassembly or resequencing
    • 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/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/27—Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/32—Flow control; Congestion control by discarding or delaying data units, e.g. packets or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present application relates to the field of communications and, more particularly, to a method and apparatus for transmitting data.
  • the Radio Link Control (LCC) entity submits data to the Packet Data Convergence Protocol (PDCP) layer in a sequential delivery manner.
  • the Service Data Unit (SDU) n must be submitted to the PDCP layer before the SDU n+1.
  • the embodiment of the present application provides a method and a device for transmitting data, which can implement real-time delivery of data to a high layer.
  • a method of transmitting data comprising:
  • the receiving end starts the timer of the first delivery mode, and the first delivery mode is used to indicate that the receiving end directly directly receives the data when receiving the data. Submit to the top;
  • the receiving end submits the to-submit data to the upper layer by using the first delivery mode.
  • the receiving end may implement the first delivery mode to deliver data to the upper layer by starting the timer of the first delivery mode, in the first delivery mode, After receiving the data, the receiving end does not need to save the discontinuous data in the receiving Buffer, but can directly submit the data to the upper layer, so that the data can be delivered in time, and in the first delivery mode, it is not necessary to use Receive buffers, thus saving system resources.
  • the method further comprises:
  • the receiving end stops the timing of the first delivery mode in a case where it is determined that the delivered data is continuous with the data to be submitted. Device.
  • the start condition of the timer of the first delivery mode may be the data to be delivered and the discontinuity of the submitted data, when the first delivery When the mode timer is in the working state, the stop condition of the timer of the first delivery mode may be that the data to be submitted and the data to be delivered are consecutive.
  • the method further comprises:
  • the receiving end determines whether the submitted data and the to-submitted data are continuous according to the window information of the reordering window and the information of the submitted data.
  • the window information of the reordering window includes a window lower bound identifier of the reordering window, and the receiving end is configured according to the window information of the reordering window, and the The information of the data has been submitted to determine whether the submitted data and the data to be submitted are consecutive, including:
  • the receiving end determines whether the delivered data and the to-submitted data are continuous according to the window lower bound identifier of the reordering window and the serial number SN of the last delivered service data unit SDU.
  • the window lower bound identifier of the reordering window may be a sequence number (SN) of the next PDU waiting to be received, or the next SN of the highest SN in the received PDU, if a data packet The SN is smaller than the lower bound of the window of the reordering window, that is, the SN of the data packet is outside the reordering window, then the data packet can be considered to have been successfully received and submitted to the upper layer, and the window upper bound identifier of the window can be the lower bound of the window + Window size.
  • SN sequence number
  • the window lower bound identifier of the reordering window can indicate information of the data to be submitted, for example, the minimum SN of the data to be submitted, so that the receiving end judges the two according to the minimum SN of the data to be submitted and the maximum SN of the submitted data. Whether it is continuous, so as to determine whether the data to be submitted and the submitted data are continuous.
  • the receiving end determines the submitted data according to a window lower bound identifier of the reordering window and a sequence number SN of the last delivered service data unit SDU Whether the data to be submitted is continuous, including:
  • the count value corresponding to the next SN of the SN of the SDU may be the last data submitted.
  • the SN, plus 1 is then determined in conjunction with RX_HFN.
  • the method further comprises:
  • the window lower bound identifier of the reordering window is set to a counter value corresponding to the SDU that is expected to be delivered next time.
  • the count value corresponding to the SDU that is expected to be delivered next time may be the SN that is expected to be delivered next time, and is determined in combination with RX_HFN.
  • the receiving end starts the timer of the first delivery mode, where the receiving end determines that the submitted data is not continuous with the data to be submitted, including:
  • the timer of the first delivery mode is turned on if the count value corresponding to the SDU that is expected to be delivered next time is not equal to the count value corresponding to the last delivered SDU.
  • the receiving end is a terminal device or a network device.
  • the receiving end is a terminal device, and the method further includes:
  • the receiving end receives the indication information sent by the network device, where the indication information is used to indicate that the terminal device submits data to the upper layer by using the first delivery mode or the second delivery mode, where the second delivery mode is used for Instructing the receiving end to deliver data to the higher layer in order.
  • the receiving end receives the indication information sent by the network device, including:
  • the receiving end receives the radio resource control RRC signaling sent by the network device, where the radio resource control signaling includes the indication information.
  • the receiving end receives the indication information sent by the network device, including:
  • the receiving end receives a medium access control MAC control element CE or a packet data convergence association PDCP control protocol data unit PDU sent by the network device, where the MAC CE or PDCP control PDU includes the indication information.
  • a method of transmitting data including:
  • the receiving end sets the duration of the timer of the second delivery mode to zero;
  • the receiving end adopts a first delivery mode to submit data to be submitted to the upper layer
  • the first delivery mode is used to indicate that the receiving end directly delivers data to a higher layer when receiving data
  • the second delivery mode is used to indicate that the receiving end delivers the number to the upper layer in order. according to.
  • an apparatus for transmitting data comprising means for performing the method of the first aspect or any alternative implementation of the first aspect.
  • an apparatus for transmitting data comprising means for performing the method of any of the alternative aspects of the second aspect or the second aspect.
  • a fifth aspect provides an apparatus for transmitting data, including a memory, a processor, and a transceiver, wherein the memory is for storing a program, the processor is configured to execute a program, and when the program is executed, the processor is based on The transceiver performs the method of the first aspect or any alternative implementation of the first aspect.
  • a sixth aspect provides an apparatus for transmitting data, including a memory, a processor, and a transceiver, wherein the memory is for storing a program, the processor is configured to execute a program, and when the program is executed, the processor is based on The transceiver performs the method of the second aspect or any alternative implementation of the second aspect.
  • a seventh aspect a computer readable medium storing program code for execution by a terminal device, the program code comprising any optional implementation for performing the first aspect or the first aspect The instructions in the method.
  • a computer readable medium storing program code for execution by a terminal device, the program code comprising any alternative implementation for performing the second aspect or the second aspect The instructions in the method.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform the method of any of the first aspect or the optional implementation of the first aspect.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform the method of any of the alternative aspects of the second aspect or the second aspect.
  • FIG. 1 is a schematic diagram of a wireless communication system in accordance with an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method of transmitting data according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a method for transmitting data according to another embodiment of the present application.
  • FIG. 4 is a schematic block diagram of an apparatus for transmitting data according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of an apparatus for transmitting data according to another embodiment of the present application.
  • FIG. 6 is a schematic block diagram of an apparatus for transmitting data according to still another embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UPD Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • FIG. 1 shows a wireless communication system 100 to which an embodiment of the present application is applied.
  • the wireless communication system 100 can include a network device 110.
  • Network device 100 can be a device that communicates with a terminal device.
  • Network device 100 may provide communication coverage for a particular geographic area and may communicate with terminal devices (e.g., UEs) located within the coverage area.
  • the network device 100 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or may be a base station (NodeB, NB) in a WCDMA system, or may be an evolved base station in an LTE system.
  • BTS Base Transceiver Station
  • NodeB NodeB
  • the network device can be a relay station, an access point, an in-vehicle device, a wearable device, A network side device in a future 5G network or a network device in a publicly available Public Land Mobile Network (PLMN) in the future.
  • PLMN Public Land Mobile Network
  • the wireless communication system 100 also includes at least one terminal device 120 located within the coverage of the network device 110.
  • Terminal device 120 can be mobile or fixed.
  • the terminal device 120 may refer to an access terminal, a user equipment (User Equipment, UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, and a wireless communication.
  • UE User Equipment
  • Device user agent, or user device.
  • the access terminal can be a cellular phone, a cordless phone, a session Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device, or connection to a wireless modem
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • Other processing devices in-vehicle devices, wearable devices, terminal devices in future 5G networks, or terminal devices in future evolved PLMNs, and the like.
  • a 5G system or network may also be referred to as an NR system or network.
  • the Radio Link Control (RLC) layer is located between a Packet Data Convergence Protocol (PDCP) layer and a Media Access Control (MAC) layer.
  • the RLC layer communicates with the PDCP layer through a Service Access Point (SAP) and communicates with the MAC layer through a logical channel.
  • SAP Service Access Point
  • the data received by the RLC entity from the PDCP layer, or the data sent to the PDCP layer is referred to as an RLC SDU or PDCP PDU.
  • the data received by the RLC entity from the MAC layer, or the data sent to the MAC layer is referred to as an RLC PDU or a MAC SDU.
  • the RLC PDU received by the receiving end (which may be a terminal device or a network device) in the reordering window is out of order, it needs to be reordered and then submitted to the PDCP layer.
  • the out-of-order RLC PDU is saved in the receiving first. In the buffer, until the previous RLC PDU has been successfully received and delivered to the PDCP layer.
  • t_Reordering When the receiving end receives the RLC PDU data, it needs to detect which RLC PDU is lost. To avoid excessive reordering delay, the reordering timer (t_Reordering) can be triggered to wait for the lost RLC PDU. Simply put, the receiving end only waits for the return. The RLC PDUs that have not been received are not available for a while. t_Reordering determines how long it takes to wait for a PDU that has not yet been received. In the existing LTE protocol, the behavior of t_Reordering, that is, the start condition, the stop condition, the trigger condition, and the behavior after the trigger are specified. In summary, the purpose of t_Reordering is to ensure that the data packets in the reordering window are delivered to the PDCP layer in order. .
  • the out-of-order data submitted by the RLC can be sorted by the PDCP layer, then the RLC layer can timely deliver the received data to the PDCP layer. In order for the PDCP layer to process the data.
  • the embodiment of the present application provides a method for transmitting data, and provides a mode for timely delivery, thereby realizing timely delivery of data from the RLC layer to the PDCP layer.
  • FIG. 2 is a schematic flowchart of a method 200 for transmitting data according to an embodiment of the present application, where The method 200 can be performed by a terminal device or a network device in the wireless communication system shown in FIG. 1. As shown in FIG. 2, the method 200 includes:
  • the receiving end starts a timer of the first delivery mode, where the first delivery mode is used to indicate that the receiving end directly receives the data, where the receiving end is determined to be discontinuous. Submit data to the top;
  • the receiving end submits the to-submitted data to a higher layer by using the first delivery mode.
  • the receiving end saves the data to be submitted in the cache until the data has been submitted.
  • the data before the data to be submitted after the data that is, the data of the gap part, is successfully submitted to the upper layer, and the data to be submitted is submitted to the upper layer, and therefore, the timely delivery of the data to be submitted cannot be realized.
  • the receiving end may open the timer of the first delivery mode in the case that the submitted data and the data to be submitted are discontinuous, thereby submitting data to the upper layer by using the first delivery mode, in the first delivery mode.
  • the receiving end does not need to save the discontinuous data in the receiving Buffer, but can directly submit the data to the upper layer. Therefore, in the first delivery mode, it is not necessary to use the receiving buffer. , saving system resources.
  • the direct transfer of data to the upper layer mentioned herein may be that the received RLC PDU data is directly delivered to the upper layer, or the received RLC PDU data may be reassembled to obtain an RLC SDU, and the RLC SDU is obtained.
  • the high layer mentioned here may be the PDCP layer, and the first delivery mode may also be referred to as a timely delivery mode, or a real delivery mode.
  • the receiving end may always use the timely delivery mode to submit data to the upper layer, that is, the data is received. It is then delivered directly to the upper layer until the timer of the first delivery mode is stopped, or timed out.
  • the timer expires. If the timer is not exceeded, but the stop condition is met, the timer is stopped. When the timer is in a failed state or a stopped state, or the timer is When in the inactive state, the receiving end does not use the timely delivery mode to submit data to the upper layer, but uses the sequential delivery mode in the prior art to submit data to the upper layer.
  • the method 200 may further include:
  • the receiving end determines that the In the case where the delivery data is continuous with the data to be submitted, the timer of the first delivery mode is stopped.
  • the start condition of the timer of the first delivery mode may be the data to be delivered and the discontinuity of the submitted data
  • the stop condition of the timer of the first delivery mode may be the data to be submitted and the data that has been submitted. continuous. That is, when the timer of the first delivery mode is in an inactive state, the receiving end may start the timer of the first delivery mode in the case that the data to be delivered and the submitted data are discontinuous, thereby adopting
  • the timely delivery mode delivers data to the upper layer.
  • the delivery mode in the prior art can be adopted, that is, the data is delivered to the upper layer in a sequential delivery manner.
  • the start condition of the timer of the first delivery mode may be the data to be delivered and the discontinuity of the submitted data, when the first delivery When the mode timer is in the working state, the stop condition of the timer of the first delivery mode may be that the data to be submitted and the data to be delivered are consecutive.
  • the timer of the first delivery mode is reset to zero by the receiving end, so that the timer of the first delivery mode is inactive, when When the duration of the timer of the first delivery mode is set to a value greater than zero, the timer of the first delivery mode is started, and the timer of the first delivery mode is in an active state when the first delivery mode is When the timer is enabled, the receiving end will directly submit the data to the upper layer after receiving the data in the reordering window. Even if there is a packet loss, the packet is not waiting for the packet, as long as new data arrives, The new data received is submitted to the top.
  • the method 200 further includes:
  • the receiving end determines whether the submitted data and the to-submitted data are continuous according to the window information of the reordering window and the information of the submitted data.
  • the window information of the reordering window may include information such as a window lower bound identifier of the reordering window, a window upper bound identifier, and a window size, and the size of the reordering window is used to indicate that the PDU can be received without moving the window. Quantity.
  • the movement of the reordering window is mainly driven by the lower bound of the window, that is, only the data packet of the lower boundary of the window is successfully received and submitted to the upper layer, or the reordering timer is invalid, and the window moves backward, therefore, the reordering window
  • the lower window identifier of the window can indicate information of the data to be submitted, for example, the minimum SN of the data to be submitted, so that the receiving end determines whether the two are continuous according to the minimum SN of the data to be submitted and the maximum SN of the submitted data, thereby determining Whether the data to be submitted and the submitted data are continuous.
  • the SN of the RLC SDU that the receiving end last delivered to the upper layer is recorded as Last_Submitted_PDCP_RX_SN, and the receiving end combines the window lower bound identifier indication of the reordering window according to the SN of the last delivered SDU.
  • the SN determines whether the data to be submitted and the submitted data are continuous.
  • the The receiving end can determine the count value (COUNT) corresponding to the last delivered SDU according to the SN of the last delivered SDU, combined with RX_HFN, that is, the serial number of the SDU actually delivered to the upper layer by the receiving end.
  • COUNT the count value corresponding to the last delivered SDU according to the SN of the last delivered SDU
  • RX_HFN the serial number of the SDU actually delivered to the upper layer by the receiving end.
  • the same method can be used to calculate the corresponding count value according to the lower bound of the window, that is, the count value corresponding to the minimum SN of the data to be submitted.
  • the receiving end determines whether the delivered data and the to-be-submitted data are consecutive according to the window information of the reordering window and the information of the submitted data, including:
  • the count value corresponding to the lower boundary identifier of the window can reflect the actual serial number value of the data to be submitted
  • the lower boundary of the window may be set as the last submitted SDU.
  • SN when the comparison is performed, the corresponding count value is not equal to the count value corresponding to the SN of the last delivered SDU, and the determined data and the data to be submitted are discontinuous.
  • the count value corresponding to the lower bound of the window is equal to the count value corresponding to the SN of the last delivered SDU, and it is determined that the submitted data and the data to be submitted are consecutive. That is to say, the specific judgment condition can be adjusted according to the definition of the lower boundary identifier of the window, which is not specifically limited in the embodiment of the present application.
  • the method 200 further includes:
  • the window lower bound identifier of the reordering window is set to a counter value corresponding to the SDU that is expected to be delivered next time.
  • the timer of the first delivery mode is in a failure state. It can be understood that the timer of the first delivery mode is in an inactive state.
  • the receiving end may set the window lower bound identifier of the reordering window to a count value corresponding to the count value (hereinafter referred to as Next_PDCP_RX_SN) corresponding to the SDU that is to be delivered next time.
  • the receiving end may combine and receive according to Next_PDCP_RX_SN.
  • the current RX_HFN determines the corresponding COUNT value.
  • the receiving end may not count the corresponding value of the SDU corresponding to the last delivered SDU. In the case of a value, that is, if the data to be submitted and the data to be delivered are not consecutive, the timer of the first delivery mode is turned on, so that the data can be submitted to the upper layer using the timely delivery mode.
  • the receiving end may be a terminal device or a network device, which is not specifically limited in this embodiment of the present application.
  • the method 200 may further include:
  • the receiving end receives the indication information sent by the network device, where the indication information is used to indicate that the terminal device submits data to the upper layer by using the first delivery mode or the second delivery mode, where the second delivery mode is used for Instructing the receiving end to deliver data to the higher layer in order.
  • the network device when the receiving end is a terminal device, which delivery mode is specifically adopted, the network device can be configured to the terminal device, and the network device can configure the delivery mode of the terminal device to the upper layer according to factors such as system requirements or high-level processing capabilities. Submit the data. For example, the network device may configure the terminal device to adopt the first delivery mode, that is, the timely delivery mode to deliver data to the upper layer to reduce the data transmission delay, or the processing capability at the upper layer is strong. In the case of using the timely delivery mode to submit data to the high-level, that is, directly submit the out-of-order data to At the upper level, the data is reordered by the upper layers.
  • the receiving end receives the indication information sent by the network device, including:
  • the receiving end receives the radio resource control RRC signaling sent by the network device, where the radio resource control signaling includes the indication information.
  • the network device may semi-statically configure which delivery mode is adopted by the receiving end through RRC signaling.
  • the receiving end receives the indication information sent by the network device, including:
  • the receiving end receives a medium access control MAC control element CE or a packet data convergence association PDCP control protocol data unit PDU sent by the network device, where the MAC CE or PDCP control PDU includes the indication information.
  • the network device can dynamically configure which delivery mode the terminal device uses to deliver data to the upper layer through dynamic signaling, for example, MAC CE or PDCP control PDU.
  • dynamic signaling for example, MAC CE or PDCP control PDU.
  • the network device may send the indication information to the receiving end by using other manners, where the embodiment of the application does not limit the specific notification manner of the indication information.
  • the receiving end can open the timer of the timely delivery mode in the case that the data to be delivered and the submitted data are discontinuous, thereby realizing the delivery of data to the upper layer by means of timely delivery. Conducive to the timely delivery of data, reducing the transmission delay of data.
  • FIG. 3 is a schematic flowchart of a method 300 for transmitting data according to another embodiment of the present application.
  • the method 300 may be performed by a terminal device or a network device in the wireless communication system shown in FIG. 1, as shown in FIG.
  • the method 300 includes:
  • the receiving end sets the duration of the timer of the second delivery mode to zero.
  • the receiving end adopts a first delivery mode, and submits data to be submitted to a higher layer;
  • the first delivery mode is used to indicate that the receiving end directly delivers data to a higher layer when receiving data
  • the second delivery mode is used to instruct the receiving end to deliver data to a higher layer in order.
  • the window upper bound identifier of the reordering window may be the next SN number of the highest SN number in the received PDU, if the SN of one data packet is greater than the window upper bound identifier of the reordering window, that is, the The SN of the packet is outside the reordering window, so the packet can be considered If the receiving end receives a data packet whose SN is larger than the current window upper bound identifier, the receiving end may update the window upper bound identifier to the SN of the newly received data packet, that is, the window is backward. mobile.
  • the movement of the reordering window is mainly driven by the upper bound of the window, that is, as long as the receiving end receives a larger SN packet, the window will move backward.
  • the receiving end only needs to set the second delivery mode, that is, the duration of the timer in the sequential delivery mode to zero, and the timer is inactive when the duration of the timer in the sequential delivery mode is zero. Therefore, even if there is a packet loss, the packet loss waits, so that the window moves with the reception of the new packet. Therefore, when receiving a new packet, the receiver can directly add the new packet.
  • the received data packet is delivered to the upper layer, so that timely delivery of the received data is included.
  • the receiving end does not need to determine whether the submitted data and the to-be-submitted data packet are consecutive, as long as the duration of the second delivery mode timer is set to 0, the received data can be implemented.
  • To submit in time, or to submit data in order simply set the duration of the second delivery mode timer to a value greater than zero. Therefore, the receiving end can realize the switching of the two modes in the timely delivery and the sequential delivery by controlling the duration of the timer of the second delivery mode.
  • FIG. 4 is a schematic block diagram of an apparatus for transmitting data according to an embodiment of the present application.
  • the device 400 of Figure 4 includes:
  • the processing module 410 is configured to start a timer of the first delivery mode, where the first delivery mode is used to indicate that the device receives the data, if the data that is to be delivered is not continuous with the data to be submitted. Submit data directly to the top;
  • the communication module 420 is configured to submit the to-submit data to the upper layer by using the first delivery mode if the timer of the first delivery mode is not invalid.
  • the processing module 410 is further configured to:
  • the timer of the first delivery mode is in an open state, in a case where it is determined that the delivered data is continuous with the data to be submitted, the timer of the first delivery mode is stopped.
  • the device further includes:
  • a determining module configured to determine, according to the window information of the reordering window and the information of the submitted data, whether the submitted data and the to-submitted data are consecutive.
  • the window information of the reordering window includes a window lower bound identifier of the reordering window, where the determining module is specifically configured to:
  • the determining module is specifically configured to:
  • the processing module 410 is further configured to:
  • the window lower bound identifier of the reordering window is set to a counter value corresponding to the SDU that is expected to be delivered next time.
  • the processing module 410 is further configured to:
  • the timer of the first delivery mode is turned on if the count value corresponding to the SDU that is expected to be delivered next time is not equal to the count value corresponding to the last delivered SDU.
  • the device is a terminal device or a network device.
  • the device is a terminal device
  • the communication module 420 is further configured to:
  • the indication information is used to indicate that the terminal device submits data to the upper layer by using the first delivery mode or the second delivery mode, where the second delivery mode is used to indicate the device Submit data to the top level in order.
  • the communication module 420 is specifically configured to:
  • Radio resource control RRC signaling sent by the network device, where the radio resource control signaling includes the indication information.
  • the communication module 420 is specifically configured to:
  • MAC CE media access control MAC control element CE or a packet data convergence association PDCP control protocol data unit PDU, where the MAC CE or PDCP control PDU includes the indication information.
  • the device 400 may correspond to (for example, may be configured or be itself) the terminal device described in the foregoing method 200, and each module or unit in the device 400 is used to execute the terminal device in the foregoing method 200, respectively. Execution of each action or process, here, in order to avoid embarrassment The detailed description is omitted.
  • FIG. 5 is a schematic block diagram of an apparatus for transmitting data according to an embodiment of the present application.
  • the device 500 of Figure 5 includes:
  • the setting module 510 is configured to set a duration of the timer of the second delivery mode to zero;
  • the communication module 520 is configured to submit data to be submitted to the upper layer by using the first delivery mode
  • the first delivery mode is used to indicate that the device directly delivers data to a higher layer when receiving data
  • the second delivery mode is used to instruct the device to deliver data to a higher layer in order.
  • the device 500 may correspond to (for example, may be configured or be itself) the terminal device described in the foregoing method 300, and each module or unit in the device 500 is used to execute the terminal device in the foregoing method 300, respectively.
  • Each of the operations or processes performed is omitted here for the sake of avoiding redundancy.
  • the embodiment of the present application further provides a device 600 for transmitting data, which may be the device 400 in FIG. 4 or the device 500 in FIG. 5, which can be used to perform and FIG.
  • the device 600 includes an input interface 610, an output interface 620, a processor 630, and a memory 640.
  • the input interface 610, the output interface 620, the processor 630, and the memory 640 can be connected by a bus system.
  • the memory 640 is used to store programs, instructions or code.
  • the processor 630 is configured to execute a program, an instruction or a code in the memory 640 to control the input interface 610 to receive a signal, control the output interface 620 to send a signal, and complete the operations in the foregoing method embodiments.
  • the processor 630 may be a central processing unit (“CPU"), and the processor 630 may also be other general-purpose processors, digital signal processors ( DSP), application specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 640 can include read only memory and random access memory and provides instructions and data to the processor 630. A portion of the memory 640 can also include a non-volatile random access memory. For example, the memory 640 can also store information of the device type.
  • each content of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 630 or an instruction in a form of software.
  • the content of the method disclosed in the embodiment of the present application may be directly implemented as a hardware processor execution, or a hardware and software module group in the processor.
  • the execution is completed.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 640, and the processor 630 reads the information in the memory 640 and completes the contents of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the processing module 410 included in the device 400 of FIG. 4 may be implemented by the processor 630 of FIG. 6.
  • the communication module 420 included in the device 400 of FIG. 4 may be configured by using the input interface 610 of FIG.
  • the output interface 620 is implemented.
  • the setting module 510 included in the device 500 of FIG. 5 can be implemented by the processor 630 of FIG. 6, and the communication module 520 included in the device 500 of FIG. 5 can be used with the input interface 610 of FIG.
  • the output interface 620 is implemented.
  • the embodiment of the present application further provides a computer readable storage medium storing one or more programs, the one or more programs including instructions, when the portable electronic device is included in a plurality of applications When executed, the portable electronic device can be caused to perform the method of the embodiment shown in FIG. 2 or 3.
  • the embodiment of the present application also proposes a computer program comprising instructions for causing a computer to execute a corresponding flow of the method of the embodiment shown in FIG. 2 or FIG. 3 when the computer program is executed by a computer.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling through some interface, device or unit.
  • the or communication connection can be in electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)

Abstract

本申请实施例提供了一种传输数据的方法和设备，能够实现数据的及时递交，该方法包括：接收端在确定已递交数据与待递交数据不连续的情况下，开启第一递交模式的定时器，其中，所述第一递交模式用于指示所述接收端在接收到数据时，直接将数据递交至高层；在所述第一递交模式的定时器未失效的情况下，所述接收端采用所述第一递交模式向高层递交所述待递交数据。

Description

传输数据的方法和设备 技术领域
本申请涉及通信领域，并且更具体地，涉及一种传输数据的方法和设备。
背景技术
在长期演进(Long Term Evolution，LTE)系统中，无线链路控制(Radio Link Control RLC)实体采用按序递交的方式向分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层递交数据，也就是说，业务数据单元(Service Data Unit，SDU)n必须在SDU n+1之前递交给PDCP层。
但是，在新无线(New Radio，NR)系统中，有些情况下，并不需要按序递交，因此，需要一种新的递交方式，以满足不同场景的需求。
发明内容
本申请实施例提供了一种传输数据的方法和设备，能够实现实时向高层递交数据。
第一方面，提供了一种传输数据的方法，包括：
接收端在确定已递交数据与待递交数据不连续的情况下，开启第一递交模式的定时器，其中，所述第一递交模式用于指示所述接收端在接收到数据时，直接将数据递交至高层；
在所述第一递交模式的定时器未失效的情况下，所述接收端采用所述第一递交模式向高层递交所述待递交数据。
因此，在已递交数据和待递交数据不连续的情况下，接收端可以通过开启第一递交模式的定时器，实现采用第一递交模式向高层递交数据，在该第一递交模式下，所述接收端在接收到数据后，不必将不连续的数据保存在接收Buffer中，而是可以直接将数据递交至高层，从而能够实现数据的及时递交，并且，在该第一递交模式下，不必使用接收buffer，因此，节约了系统资源。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
若所述第一递交模式的定时器处于开启状态，所述接收端在确定所述已递交数据与所述待递交数据连续的情况下，停止所述第一递交模式的定时 器。
也就是说，当所述第一递交模式的定时器处于不工作状态时，所述第一递交模式的定时器的启动条件可以是待递交数据和已递交数据不连续，当所述第一递交模式的定时器处于工作状态时，所述第一递交模式的定时器的停止条件可以是待递交数据和已递交数据连续。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
所述接收端根据重排序窗口的窗口信息，以及所述已递交数据的信息，确定所述已递交数据和所述待递交数据是否连续。
结合第一方面，在第一方面的某些实现方式中，所述重排序窗口的窗口信息包括所述重排序窗口的窗口下界标识，所述接收端根据重排序窗口的窗口信息，以及所述已递交数据的信息，确定所述已递交数据和所述待递交数据是否连续，包括：
所述接收端根据重排序窗口的窗口下界标识，以及上次递交的业务数据单元SDU的序列号SN，确定所述已递交数据和所述待递交数据是否连续。
可选地，重排序窗口的窗口下界标识可以为等待接收的下一个PDU的序列号(Sequence Number，SN)，或者说，已经接收到的PDU中的最高SN的下一个SN，如果一个数据包的SN小于重排序窗口的窗口下界标识，即该数据包的SN在重排序窗口外，那么可以认为该数据包已经被成功接收并递交至高层，窗口的窗口上界标识可以为窗口下界标识+窗口大小。
因此，重排序窗口的窗口下界标识能够指示待递交数据的信息，例如，待递交数据的最小SN，这样，所述接收端根据待递交数据的最小SN和已递交数据的最大SN，判断两者是否连续，从而确定待递交数据和已递交数据是否连续。
结合第一方面，在第一方面的某些实现方式中，所述接收端根据重排序窗口的窗口下界标识，以及上次递交的业务数据单元SDU的序列号SN，确定所述已递交数据和所述待递交数据是否连续，包括：
若所述窗口下界标识对应的计数值不等于上次递交的SDU的SN的下一个SN对应的计数值，确定所述已递交数据和所述待递交数据不连续；或
若所述窗口下界标识对应的计数值等于上次递交的SDU的SN的下一个SN对应的计数值，确定所述已递交数据和所述待递交数据连续。
这里的SDU的SN的下一个SN对应的计数值，可以是上次递交的数据 的SN，加1，然后结合RX_HFN确定的。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
在所述第一递交模式的定时器处于失效状态的情况下，将重排序窗口的窗口下界标识设置为下次期望递交的SDU对应的计数值。
这里的下次期望递交的SDU对应的计数值，可以是下次期望递交的SN，结合RX_HFN确定的。
结合第一方面，在第一方面的某些实现方式中，所述接收端在确定已递交数据与待递交数据不连续的情况下，开启第一递交模式的定时器，包括：
在所述下次期望递交的SDU对应的计数值不等于上次递交的SDU对应的计数值的情况下，开启所述第一递交模式的定时器。
结合第一方面，在第一方面的某些实现方式中，所述接收端为终端设备或网络设备。
结合第一方面，在第一方面的某些实现方式中，所述接收端为终端设备，所述方法还包括：
所述接收端接收网络设备发送的指示信息，所述指示信息用于指示所述终端设备采用所述第一递交模式或第二递交模式向高层递交数据，其中，所述第二递交模式用于指示所述接收端按序向高层递交数据。
结合第一方面，在第一方面的某些实现方式中，所述接收端接收网络设备发送的指示信息，包括：
所述接收端接收所述网络设备发送的无线资源控制RRC信令，所述无线资源控制信令包括所述指示信息。
结合第一方面，在第一方面的某些实现方式中，所述接收端接收网络设备发送的指示信息，包括：
所述接收端接收所述网络设备发送的媒体接入控制MAC控制元素CE或分组数据汇聚协PDCP控制协议数据单元PDU，所述MAC CE或PDCP控制PDU包括所述指示信息。
第二方面，提供了一种传输数据的方法，包括：
接收端将第二递交模式的定时器的时长设置为零；
所述接收端采用第一递交模式，向高层递交待递交数据；
其中，所述第一递交模式用于指示所述接收端在接收到数据时，直接将数据递交至高层，所述第二递交模式用于指示所述接收端按序向高层递交数 据。
第三方面，提供了一种传输数据的设备，包括用于执行第一方面或第一方面的任一可选的实现方式中的方法的单元。
第四方面，提供了一种传输数据的设备，包括用于执行第二方面或第二方面的任一可选的实现方式中的方法的单元。
第五方面，提供一种传输数据的设备，包括存储器、处理器和收发器，所述存储器用于存储程序，所述处理器用于执行程序，当所述程序被执行时，所述处理器基于所述收发器执行第一方面或第一方面的任一可选实现方式中的方法。
第六方面，提供一种传输数据的设备，包括存储器、处理器和收发器，所述存储器用于存储程序，所述处理器用于执行程序，当所述程序被执行时，所述处理器基于所述收发器执行第二方面或第二方面的任一可选的实现方式中的方法。
第七方面，提供一种计算机可读介质，所述计算机可读介质存储用于终端设备执行的程序代码，所述程序代码包括用于执行第一方面或第一方面的任一可选实现方式中的方法的指令。
第八方面，提供一种计算机可读介质，所述计算机可读介质存储用于终端设备执行的程序代码，所述程序代码包括用于执行第二方面或第二方面的任一可选实现方式中的方法的指令。
第九方面，提供一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任一可选的实现方式中的方法。
第十方面，提供一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面或第二方面的任一可选的实现方式中的方法。
附图说明
图1是根据本申请实施例的无线通信系统的示意性图。
图2是根据本申请实施例的传输数据的方法的示意性流程图。
图3是根据本申请另一实施例的传输数据的方法的示意性流程图。
图4是根据本申请实施例的传输数据的设备的示意性框图。
图5是根据本申请另一实施例的传输数据的设备的示意性框图。
图6是根据本申请再一实施例的传输数据的设备的示意性框图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，简称为“GSM”)系统、码分多址(Code Division Multiple Access，简称为“CDMA”)系统、宽带码分多址(Wideband Code Division Multiple Access，简称为“WCDMA”)系统、通用分组无线业务(General Packet Radio Service，简称为“GPRS”)、长期演进(Long Term Evolution，简称为“LTE”)系统、LTE频分双工(Frequency Division Duplex，简称为“FDD”)系统、LTE时分双工(Time Division Duplex，简称为“TDD”)、通用移动通信系统(Universal Mobile Telecommunication System，简称为“UMTS”)、全球互联微波接入(Worldwide Interoperability for Microwave Access，简称为“WiMAX”)通信系统或未来的5G系统等。
图1示出了本申请实施例应用的无线通信系统100。该无线通信系统100可以包括网络设备110。网络设备100可以是与终端设备通信的设备。网络设备100可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备(例如UE)进行通信。可选地，该网络设备100可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备、未来5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该无线通信系统100还包括位于网络设备110覆盖范围内的至少一个终端设备120。终端设备120可以是移动的或固定的。可选地，终端设备120可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话 启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
可选地，5G系统或网络还可以称为NR系统或网络。
以下，对跟本申请实施例相关的背景知识做个简单介绍。
无线链路控制(Radio Link Control，RLC)层位于分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层和媒体接入控制(Media Access Control，MAC)层之间。RLC层通过服务访问点(Service Access Point，SAP)与PDCP层进行通信，并通过逻辑信道与MAC层进行通信。每个UE的每个逻辑信道都有一个RLC实体。RLC实体从PDCP层接收到的数据，或发往PDCP层的数据被称作RLC SDU或PDCP PDU。RLC实体从MAC层接收到的数据，或发往MAC层的数据被称作RLC PDU或MAC SDU。
如果接收端(可以是终端设备或网络设备)在重排序窗口接收到的RLC PDU是乱序的，需要先进行重排序，然后再递交至PDCP层，乱序到达的RLC PDU会先保存在接收缓存(buffer)中，直到之前的RLC PDU都已成功接收并递送给PDCP层。
接收端接收到RLC PDU数据时，需要检测丢失了哪个RLC PDU，为了避免过度的重排序延迟，可以触发重排序定时器(t_Reordering)等待丢失的RLC PDU，简单地说，接收端只会等待还未收到的RLC PDU一段时间，等不到就不等了。t_Reordering决定了在多长时间内等待一个还未收到的PDU。现有的LTE协议中，规定了t_Reordering的行为，即启动条件，停止条件，触发条件以及触发之后的行为等，总而言之，t_Reordering的目的是为了保证重排序窗口内的数据包按序递交至PDCP层。
但是，不是所有情况下，都需要按序递交，例如，若PDCP层有排序能力，RLC递交的乱序数据可以由PDCP层进行排序的话，那么RLC层可以将接收到的数据及时递交至PDCP层，以便于PDCP层对数据进行处理。
有鉴于此，本申请实施例提供了一种传输数据的方法，提供了一种及时递交的模式，从而实现数据从RLC层到PDCP层的及时递交。
图2是本申请实施例提出的传输数据的方法200的示意性流程图，所述 方法200可以由图1所示的无线通信系统中的终端设备或网络设备执行，如图2所示，该方法200包括：
S210，接收端在确定已递交数据与待递交数据不连续的情况下，开启第一递交模式的定时器，其中，所述第一递交模式用于指示所述接收端在接收到数据时，直接将数据递交至高层；
S220，在所述第一递交模式的定时器未失效的情况下，所述接收端采用所述第一递交模式向高层递交所述待递交数据。
现有技术中，当已递交数据与待递交数据不连续的情况下，即已递交数据和待递交数据之间有空洞(gap)，接收端会将待递交数据保存在缓存中，直到已递交数据之后待递交数据之前的数据，即gap部分的数据，被成功递交至高层，才将所述待递交数据递交至高层，因此，不能实现待递交数据的及时递交。
在本申请实施例中，接收端可以在已递交数据和待递交数据不连续的情况下，开启第一递交模式的定时器，从而采用第一递交模式向高层递交数据，在该第一递交模式下，所述接收端在接收到数据后，不必将不连续的数据保存在接收Buffer中，而是可以直接将数据递交至高层，因此，在该第一递交模式下，不必使用接收buffer，因此，节约了系统资源。
需要说明的是，这里提到的直接将数据递交至高层可以是将接收到的RLC PDU数据直接递交至高层，或者也可以将接收到的RLC PDU数据进行重组，得到RLC SDU，并将RLC SDU递交至高层，这里提到的高层可以是PDCP层，所述第一递交模式也可以称为及时递交模式，或实时递交模式等。
在所述第一递交模式的定时器处于开启状态时，或者说所述第一递交模式的定时器处于工作状态时，所述接收端可以一直使用及时递交模式向高层递交数据，即接收到数据后直接递交至高层，直到所述第一递交模式的定时器被停止，或者超时。
当超过定时器的时长时，定时器失效，若未超过定时器的时长，但满足停止条件时，所述定时器被停止，当定时器处于失效状态或停止状态时，或者说所述定时器处于不工作状态时，所述接收端不采用及时递交模式向高层递交数据，而是采用现有技术中的按序递交模式向高层递交数据。
可选地，在一些实施例中，所述方法200还可以包括：
若所述第一递交模式的定时器处于开启状态，所述接收端在确定所述已 递交数据与所述待递交数据连续的情况下，停止所述第一递交模式的定时器。
总的来说，所述第一递交模式的定时器的启动条件可以是待递交数据和已递交数据不连续，所述第一递交模式的定时器的停止条件可以是待递交数据和已递交数据连续。也就是说，当所述第一递交模式的定时器处于不工作状态时，所述接收端可以在待递交数据和已递交数据不连续的情况下，启动第一递交模式的定时器，从而采用及时递交模式向高层递交数据，在待递交数据和已递交数据连续的情况下，可以采用现有技术中的递交模式，即按序递交的方式向高层递交数据。
也就是说，当所述第一递交模式的定时器处于不工作状态时，所述第一递交模式的定时器的启动条件可以是待递交数据和已递交数据不连续，当所述第一递交模式的定时器处于工作状态时，所述第一递交模式的定时器的停止条件可以是待递交数据和已递交数据连续。
当第一递交模式的定时器被停止时，所述接收端重置所述第一递交模式的定时器的时长为零，这样所述第一递交模式的定时器处于不工作状态，当将所述第一递交模式的定时器的时长设置为大于零的值时，所述第一递交模式的定时器启动，所述第一递交模式的定时器处于工作状态，当所述第一递交模式的定时器开启时，所述接收端在重排序窗口中接收到数据后，会将数据直接递交至高层，即使有丢包的情况，也不进行丢包的等待，只要有新数据到达就可以将接收到的新数据递交至高层。
可选的，作为一个实施例，所述方法200还包括：
所述接收端根据重排序窗口的窗口信息，以及所述已递交数据的信息，确定所述已递交数据和所述待递交数据是否连续。
其中，重排序窗口的窗口信息可以包括重排序窗口的窗口下界标识，窗口上界标识和窗口大小等信息，重排序窗口的大小用于指示在不进行窗口移动的前提下，能够接收的PDU的数量。
例如，重排序窗口的窗口下界标识可以为等待接收的下一个PDU的序列号(Sequence Number，SN)，或者说，已经接收到的PDU中的最高SN的下一个SN，如果一个数据包的SN小于重排序窗口的窗口下界标识，即该数据包的SN在重排序窗口外，那么可以认为该数据包已经被成功接收并递交至高层，窗口的窗口上界标识可以为窗口下界标识+窗口大小。举例来 说，已经接收到的数据包的最大SN为50，那么窗口下界标识可以为SN+1＝51，若窗口大小为512，那么窗口上界标识可以为51+512＝563。
这种情况下，重排序窗口的移动主要靠窗口下界的推动，即只有窗口下界的数据包被成功接收并递交至高层，或者重排序定时器失效，窗口才往后移动，因此，重排序窗口的窗口下界标识能够指示待递交数据的信息，例如，待递交数据的最小SN，这样，所述接收端根据待递交数据的最小SN和已递交数据的最大SN，判断两者是否连续，从而确定待递交数据和已递交数据是否连续。
因此，在本申请实施例中，将所述接收端上次递交至高层的RLC SDU的SN记为Last_Submitted_PDCP_RX_SN，所述接收端根据上次递交的SDU的SN，结合重排序窗口的窗口下界标识指示的SN，确定待递交数据和已递交数据是否连续。
具体地，由于SN是有范围的，大于该范围时，SN会重新计数，当前的超帧号(Hyper Frame Number，HFN)，记为RX_HFN，可以用于记录重新计数的次数，因此，所述接收端根据上次递交的SDU的SN，结合RX_HFN，就可以确定上次递交的SDU对应的计数值(COUNT)，即所述接收端实际递交至高层的SDU的序号。采用同样的方法可以根据窗口下界标识计算对应的计数值，即待递交数据的最小SN对应的计数值。
优选地，所述接收端根据重排序窗口的窗口信息，以及所述已递交数据的信息，确定所述已递交数据和所述待递交数据是否连续，包括：
若所述窗口下界标识对应的计数值不等于上次递交的SDU的SN的下一个SN对应的计数值，确定所述已递交数据和所述待递交数据不连续；或
若所述窗口下界标识对应的计数值等于上次递交的SDU的SN的下一个SN对应的计数值，确定所述已递交数据和所述待递交数据连续。
由于窗口下界标识对应的计数值能够反映待递交数据的实际序号值，上次递交的SDU的SN对应的计数值能够反映上次递交的SDU的实际序号值，通过对比这两个计数值是否连续，从而可以判断已递交数据和待递交数据是否连续，例如，窗口下界标识对应的计数值为COUNT1，上次递交的SDU的SN对应的计数值为COUNT2，若COUNT1＝COUNT2+1，那么可以确定已递交数据和待递交数据连续，否则，确定已递交数据和待递交数据不连续。
应理解，在具体实现时，可以设置窗口下界标识为上次递交的SDU的 SN，这样进行对比时，可以在所述窗口下界标识对应的计数值不等于上次递交的SDU的SN对应的计数值，确定所述已递交数据和所述待递交数据不连续，在所述窗口下界标识对应的计数值等于上次递交的SDU的SN对应的计数值，确定所述已递交数据和所述待递交数据连续。也就是说，具体判断条件，可以根据窗口下界标识的定义进行调整，本申请实施例对此不作特别限定。
可选地，作为一个实施例，所述方法200还包括：
在所述第一递交模式的定时器处于失效状态的情况下，将重排序窗口的窗口下界标识设置为下次期望递交的SDU对应的计数值。
其中，所述第一递交模式的定时器处于失效状态可以理解为所述第一递交模式的定时器处于不工作状态。
具体地，所述接收端可以将重排序窗口的窗口下界标识设置为下次期望递交的SDU对应的计数值(记为Next_PDCP_RX_SN)对应的计数值，例如，所述接收端可以根据Next_PDCP_RX_SN，结合接收端当前的RX_HFN确定对应的COUNT值，那么，当第一递交模式的定时器处于失效状态时，所述接收端可以在下次期望递交的SDU对应的计数值不等于上次递交的SDU对应的计数值的情况下，即待递交数据和已递交数据不连续的情况下，开启所述第一递交模式的定时器，从而可以使用及时递交模式向高层递交数据。
应理解，在本申请实施例中，所述接收端可以是终端设备，也可以是网络设备，本申请实施例对此不作特别限定。
若所述接收端为终端设备，作为一个实施例，所述方法200还可以包括：
所述接收端接收网络设备发送的指示信息，所述指示信息用于指示所述终端设备采用所述第一递交模式或第二递交模式向高层递交数据，其中，所述第二递交模式用于指示所述接收端按序向高层递交数据。
也就是说，当接收端为终端设备时，具体采用哪种递交模式，可以由网络设备配置给终端设备，网络设备可以根据系统需求或高层处理能力等因素，配置终端设备采用什么递交模式向高层递交数据。例如，所述网络设备可以在时延要求高的情况下，配置终端设备采用第一递交模式，即及时递交模式向高层递交数据，以降低数据的传输时延，或者在高层的处理能力较强的情况下，采用及时递交模式向高层递交数据，即直接将乱序的数据递交至 高层，由高层进行数据的重排序。
可选地，作为一个实施例，所述接收端接收网络设备发送的指示信息，包括：
所述接收端接收所述网络设备发送的无线资源控制RRC信令，所述无线资源控制信令包括所述指示信息。
即所述网络设备可以通过RRC信令，给所述接收端半静态配置采用哪种递交模式。
可选地，作为另一个实施例，所述接收端接收网络设备发送的指示信息，包括：
所述接收端接收所述网络设备发送的媒体接入控制MAC控制元素CE或分组数据汇聚协PDCP控制协议数据单元PDU，所述MAC CE或PDCP控制PDU包括所述指示信息。
也就是说，网络设备可以通过动态信令，例如，MAC CE或PDCP控制PDU，动态配置终端设备采用哪种递交模式向高层递交数据。
可选地，所述网络设备还可以通过其他方式向所述接收端发送所述指示信息，本申请实施例并不限定所述指示信息的具体通知方式。
因此，本申请实施例的传输数据的方法，接收端在待递交数据和已递交数据不连续的情况下，能够开启及时递交模式的定时器，从而实现采用及时递交的方式向高层递交数据，有利于实现数据的及时递交，降低数据的传输时延。
图3是本申请另一实施例的传输数据的方法300的示意性流程图，所述方法300可以由图1所示的无线通信系统中的终端设备或网络设备执行，如图3所示，该方法300包括：
S310，接收端将第二递交模式的定时器的时长设置为零；
S320，所述接收端采用第一递交模式，向高层递交待递交数据；
其中，所述第一递交模式用于指示所述接收端在接收到数据时，直接将数据递交至高层，所述第二递交模式用于指示所述接收端按序向高层递交数据。
在本实施例中，重排序窗口的窗口上界标识可以为已经接收到的PDU中的最高SN号的下一个SN号，如果一个数据包的SN大于重排序窗口的窗口上界标识，即该数据包的SN在重排序窗口外，那么可以认为该数据包 还未被成功接收，若接收端接收到一个SN大于当前的窗口上界标识的数据包，那么所述接收端可以将窗口上界标识更新为新接收到的数据包的SN，即将窗口往后移动。
也就是说，重排序窗口的移动主要靠窗口上界的推动，即只要接收端接收到更大SN的数据包，窗口就会往后移动。这种情况下，所述接收端只要将第二递交模式，即按序递交模式的定时器的时长设置为零，在按序递交模式的定时器的时长为零时，定时器处于不工作状态，因此，即使有丢包的存在，也不进行丢包的等待，这样，窗口会跟着新数据包的接收往后移动，因此，在接收到一个新的数据包时，接收端可以直接将新接收的数据包递交至上层，从而实现将接收到的数据包括的及时递交。
因此，在此场景下，所述接收端无需判断确定已递交数据和待递交数据包是否连续，只要将第二递交模式的定时器的时长设置为0，即可实现将接收到的数据包括的及时递交，或者若需要按序递交数据，只需将第二递交模式的定时器的时长设置为大于零的值即可。因此，所述接收端通过控制第二递交模式的定时器的时长即可实现及时递交和按序递交两种模式的切换。
上文结合图2和图3，详细描述了本申请的方法实施例，下文结合图4至图6，详细描述本申请的装置实施例，应理解，装置实施例与方法实施例相互对应，类似的描述可以参照方法实施例。
图4是根据本申请实施例的传输数据的设备的示意性框图。图4的设备400包括：
处理模块410，用于在确定已递交数据与待递交数据不连续的情况下，开启第一递交模式的定时器，其中，所述第一递交模式用于指示所述设备在接收到数据时，直接将数据递交至高层；
通信模块420，用于在所述第一递交模式的定时器未失效的情况下，采用所述第一递交模式向高层递交所述待递交数据。
可选地，在一些实施例中，所述处理模块410还用于：
若所述第一递交模式的定时器处于开启状态，在确定所述已递交数据与所述待递交数据连续的情况下，停止所述第一递交模式的定时器。
可选地，在一些实施例中，所述设备还包括：
确定模块，用于根据重排序窗口的窗口信息，以及所述已递交数据的信息，确定所述已递交数据和所述待递交数据是否连续。
可选地，在一些实施例中，所述重排序窗口的窗口信息包括所述重排序窗口的窗口下界标识，所述确定模块具体用于：
根据重排序窗口的窗口下界标识，以及上次递交的业务数据单元SDU的序列号SN，确定所述已递交数据和所述待递交数据是否连续。
可选地，在一些实施例中，所述确定模块具体用于：
若所述窗口下界标识对应的计数值不等于上次递交的SDU的SN的下一个SN对应的计数值，确定所述已递交数据和所述待递交数据不连续；或
若所述窗口下界标识对应的计数值等于上次递交的SDU的SN的下一个SN对应的计数值，确定所述已递交数据和所述待递交数据连续。
可选地，在一些实施例中，所述处理模块410还用于：
在所述第一递交模式的定时器处于失效状态的情况下，将重排序窗口的窗口下界标识设置为下次期望递交的SDU对应的计数值。
可选地，在一些实施例中，所述处理模块410还用于：
在所述下次期望递交的SDU对应的计数值不等于上次递交的SDU对应的计数值的情况下，开启所述第一递交模式的定时器。
可选地，在一些实施例中，所述设备为终端设备或网络设备。
可选地，在一些实施例中，所述设备为终端设备，所述通信模块420还用于：
接收网络设备发送的指示信息，所述指示信息用于指示所述终端设备采用所述第一递交模式或第二递交模式向高层递交数据，其中，所述第二递交模式用于指示所述设备按序向高层递交数据。
可选地，在一些实施例中，所述通信模块420具体用于：
接收所述网络设备发送的无线资源控制RRC信令，所述无线资源控制信令包括所述指示信息。
可选地，在一些实施例中，所述通信模块420具体用于：
接收所述网络设备发送的媒体接入控制MAC控制元素CE或分组数据汇聚协PDCP控制协议数据单元PDU，所述MAC CE或PDCP控制PDU包括所述指示信息。
具体地，该设备400可以对应(例如，可以配置于或本身即为)上述方法200中描述的终端设备，并且，该设备400中的各模块或单元分别用于执行上述方法200中终端设备所执行的各动作或处理过程，这里，为了避免赘 述，省略其详细说明。
图5是根据本申请实施例的传输数据的设备的示意性框图。图5的设备500包括：
设置模块510，用于将第二递交模式的定时器的时长设置为零；
通信模块520，用于采用第一递交模式，向高层递交待递交数据；
其中，所述第一递交模式用于指示所述设备在接收到数据时，直接将数据递交至高层，所述第二递交模式用于指示所述设备按序向高层递交数据。
具体地，该设备500可以对应(例如，可以配置于或本身即为)上述方法300中描述的终端设备，并且，该设备500中的各模块或单元分别用于执行上述方法300中终端设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
如图6所示，本申请实施例还提供了一种传输数据的设备600，所述设备600可以为图4中的设备400或图5中的设备500，其能够用于执行与图2中方法200或图3中方法300对应的终端设备的内容。所述设备600包括：输入接口610、输出接口620、处理器630以及存储器640，所述输入接口610、输出接口620、处理器630和存储器640可以通过总线系统相连。所述存储器640用于存储包括程序、指令或代码。所述处理器630，用于执行所述存储器640中的程序、指令或代码，以控制输入接口610接收信号、控制输出接口620发送信号以及完成前述方法实施例中的操作。
应理解，在本申请实施例中，所述处理器630可以是中央处理单元(Central Processing Unit，简称为“CPU”)，所述处理器630还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者所述处理器也可以是任何常规的处理器等。
所述存储器640可以包括只读存储器和随机存取存储器，并向处理器630提供指令和数据。存储器640的一部分还可以包括非易失性随机存取存储器。例如，存储器640还可以存储设备类型的信息。
在实现过程中，上述方法的各内容可以通过处理器630中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的内容可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组 合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。所述存储介质位于存储器640，处理器630读取存储器640中的信息，结合其硬件完成上述方法的内容。为避免重复，这里不再详细描述。
一个具体的实施方式中，图4中设备400包括的处理模块410可以用图6的处理器630实现，图4中设备400包括的通信模块420可以用图6的所述输入接口610和所述输出接口620实现。
在另一个具体的实施方式中，图5中设备500包括的设置模块510可以用图6的处理器630实现，图5中设备500包括的通信模块520可以用图6的所述输入接口610和所述输出接口620实现。
本申请实施例还提出了一种计算机可读存储介质，该计算机可读存储介质存储一个或多个程序，该一个或多个程序包括指令，该指令当被包括多个应用程序的便携式电子设备执行时，能够使该便携式电子设备执行图2或图3所示实施例的方法。
本申请实施例还提出了一种计算机程序，该计算机程序包括指令，当该计算机程序被计算机执行时，使得计算机可以执行图2或图3所示实施例的方法的相应流程。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应所述理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦 合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者所述技术方案的部分可以以软件产品的形式体现出来，所述计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (24)

  1. 一种传输数据的方法，其特征在于，包括：
    接收端在确定已递交数据与待递交数据不连续的情况下，开启第一递交模式的定时器，其中，所述第一递交模式用于指示所述接收端在接收到数据时，直接将数据递交至高层；
    在所述第一递交模式的定时器未失效的情况下，所述接收端采用所述第一递交模式向高层递交所述待递交数据。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    若所述第一递交模式的定时器处于开启状态，所述接收端在确定所述已递交数据与所述待递交数据连续的情况下，停止所述第一递交模式的定时器。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述接收端根据重排序窗口的窗口信息，以及所述已递交数据的信息，确定所述已递交数据和所述待递交数据是否连续。
  4. 根据权利要求3所述的方法，其特征在于，所述重排序窗口的窗口信息包括所述重排序窗口的窗口下界标识，所述接收端根据重排序窗口的窗口信息，以及所述已递交数据的信息，确定所述已递交数据和所述待递交数据是否连续，包括：
    所述接收端根据重排序窗口的窗口下界标识，以及上次递交的业务数据单元SDU的序列号SN，确定所述已递交数据和所述待递交数据是否连续。
  5. 根据权利要求4所述的方法，其特征在于，所述接收端根据重排序窗口的窗口下界标识，以及上次递交的业务数据单元SDU的序列号SN，确定所述已递交数据和所述待递交数据是否连续，包括：
    若所述窗口下界标识对应的计数值不等于上次递交的SDU的SN的下一个SN对应的计数值，确定所述已递交数据和所述待递交数据不连续；或
    若所述窗口下界标识对应的计数值等于上次递交的SDU的SN的下一个SN对应的计数值，确定所述已递交数据和所述待递交数据连续。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    在所述第一递交模式的定时器处于失效状态的情况下，将重排序窗口的窗口下界标识设置为下次期望递交的SDU对应的计数值。
  7. 根据权利要求6所述的方法，其特征在于，所述接收端在确定已递交数据与待递交数据不连续的情况下，开启第一递交模式的定时器，包括：
    在所述下次期望递交的SDU对应的计数值不等于上次递交的SDU对应的计数值的情况下，开启所述第一递交模式的定时器。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述接收端为终端设备或网络设备。
  9. 根据权利要求8所述的方法，其特征在于，所述接收端为终端设备，所述方法还包括：
    所述接收端接收网络设备发送的指示信息，所述指示信息用于指示所述终端设备采用所述第一递交模式或第二递交模式向高层递交数据，其中，所述第二递交模式用于指示所述接收端按序向高层递交数据。
  10. 根据权利要求9所述的方法，其特征在于，所述接收端接收网络设备发送的指示信息，包括：
    所述接收端接收所述网络设备发送的无线资源控制RRC信令，所述无线资源控制信令包括所述指示信息。
  11. 根据权利要求9所述的方法，其特征在于，所述接收端接收网络设备发送的指示信息，包括：
    所述接收端接收所述网络设备发送的媒体接入控制MAC控制元素CE或分组数据汇聚协PDCP控制协议数据单元PDU，所述MAC CE或PDCP控制PDU包括所述指示信息。
  12. 一种传输数据的方法，其特征在于，包括：
    接收端在确定采用第一递交模式向高层递交数据的情况下，将第二递交模式的定时器的时长设置为零；
    所述接收端采用所述第一递交模式，向高层递交待递交数据；
    其中，所述第一递交模式用于指示所述接收端在接收到数据时，直接将数据递交至高层，所述第二递交模式用于指示所述接收端按序向高层递交数据。
  13. 一种传输数据的设备，其特征在于，包括：
    处理模块，用于在确定已递交数据与待递交数据不连续的情况下，开启第一递交模式的定时器，其中，所述第一递交模式用于指示所述设备在接收到数据时，直接将数据递交至高层；
    通信模块，用于在所述第一递交模式的定时器未失效的情况下，采用所述第一递交模式向高层递交所述待递交数据。
  14. 根据权利要求13所述的设备，其特征在于，所述处理模块还用于：
    若所述第一递交模式的定时器处于开启状态，在确定所述已递交数据与所述待递交数据连续的情况下，停止所述第一递交模式的定时器。
  15. 根据权利要求13或14所述的设备，其特征在于，所述设备还包括：
    确定模块，用于根据重排序窗口的窗口信息，以及所述已递交数据的信息，确定所述已递交数据和所述待递交数据是否连续。
  16. 根据权利要求15所述的设备，其特征在于，所述重排序窗口的窗口信息包括所述重排序窗口的窗口下界标识，所述确定模块具体用于：
    根据重排序窗口的窗口下界标识，以及上次递交的业务数据单元SDU的序列号SN，确定所述已递交数据和所述待递交数据是否连续。
  17. 根据权利要求16所述的设备，其特征在于，所述确定模块具体用于：
    若所述窗口下界标识对应的计数值不等于上次递交的SDU的SN的下一个SN对应的计数值，确定所述已递交数据和所述待递交数据不连续；或
    若所述窗口下界标识对应的计数值等于上次递交的SDU的SN的下一个SN对应的计数值，确定所述已递交数据和所述待递交数据连续。
  18. 根据权利要求13至17中任一项所述的设备，其特征在于，所述处理模块具体用于：
    在所述第一递交模式的定时器处于失效状态的情况下，将重排序窗口的窗口下界标识设置为下次期望递交的SDU对应的计数值。
  19. 根据权利要求18所述的设备，其特征在于，所述处理模块还用于：
    在所述下次期望递交的SDU对应的计数值不等于上次递交的SDU对应的计数值的情况下，开启所述第一递交模式的定时器。
  20. 根据权利要求13至19中任一项所述的设备，其特征在于，所述设备为终端设备或网络设备。
  21. 根据权利要求20所述的设备，其特征在于，所述设备为终端设备，所述通信模块具体用于：
    接收网络设备发送的指示信息，所述指示信息用于指示所述终端设备采用所述第一递交模式或第二递交模式向高层递交数据，其中，所述第二递交 模式用于指示所述设备按序向高层递交数据。
  22. 根据权利要求21所述的设备，其特征在于，所述通信模块具体用于：
    接收所述网络设备发送的无线资源控制RRC信令，所述无线资源控制信令包括所述指示信息。
  23. 根据权利要求22所述的设备，其特征在于，所述通信模块具体用于：
    接收所述网络设备发送的媒体接入控制MAC控制元素CE或分组数据汇聚协PDCP控制协议数据单元PDU，所述MAC CE或PDCP控制PDU包括所述指示信息。
  24. 一种传输数据的设备，其特征在于，包括：
    设置模块，用于将第二递交模式的定时器的时长设置为零；
    通信模块，用于采用第一递交模式，向高层递交待递交数据；
    其中，所述第一递交模式用于指示所述设备在接收到数据时，直接将数据递交至高层，所述第二递交模式用于指示所述吧按序向高层递交数据。
PCT/CN2017/088515 2017-06-15 2017-06-15 传输数据的方法和设备 WO2018227501A1 (zh)

Priority Applications (19)

Application Number Priority Date Filing Date Title
PCT/CN2017/088515 WO2018227501A1 (zh) 2017-06-15 2017-06-15 传输数据的方法和设备
RU2019143071A RU2749896C1 (ru) 2017-06-15 2018-02-23 Способ и устройство для передачи данных
BR112019026476-0A BR112019026476A2 (pt) 2017-06-15 2018-02-23 método para transmitir dados, dispositivo para transmitir dados e dispositivo terminal para transmitir dados
JP2019569446A JP7143337B2 (ja) 2017-06-15 2018-02-23 データを伝送する方法及び機器
SG11201912132XA SG11201912132XA (en) 2017-06-15 2018-02-23 Method and device for transmitting data
CN202010074394.0A CN111294153B (zh) 2017-06-15 2018-02-23 传输数据的方法和设备
CA3067481A CA3067481A1 (en) 2017-06-15 2018-02-23 Method and device for transmitting data
KR1020197037932A KR20200017424A (ko) 2017-06-15 2018-02-23 데이터 전송 방법 및 장치
CN201880038288.8A CN110771255B (zh) 2017-06-15 2018-02-23 传输数据的方法和设备
MX2019015070A MX2019015070A (es) 2017-06-15 2018-02-23 Metodo y dispositivo para transmitir datos.
PCT/CN2018/077052 WO2018227994A1 (zh) 2017-06-15 2018-02-23 传输数据的方法和设备
AU2018286006A AU2018286006A1 (en) 2017-06-15 2018-02-23 Method and device for transmitting data
EP18818444.4A EP3621407B1 (en) 2017-06-15 2018-02-23 Method and device for transmitting data
TW107120592A TWI734010B (zh) 2017-06-15 2018-06-14 傳輸數據的方法和設備
CL2019003649A CL2019003649A1 (es) 2017-06-15 2019-12-12 Método y dispositivo para transmitir datos.
IL271375A IL271375A (en) 2017-06-15 2019-12-12 Method and device for data transmission
US16/713,948 US11050862B2 (en) 2017-06-15 2019-12-13 Method and device for transmitting data
ZA2019/08560A ZA201908560B (en) 2017-06-15 2019-12-20 Method and device for transmitting data
US17/338,120 US11553067B2 (en) 2017-06-15 2021-06-03 Method and device for transmitting data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/088515 WO2018227501A1 (zh) 2017-06-15 2017-06-15 传输数据的方法和设备

Publications (1)

Publication Number Publication Date
WO2018227501A1 true WO2018227501A1 (zh) 2018-12-20

Family

ID=64659666

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2017/088515 WO2018227501A1 (zh) 2017-06-15 2017-06-15 传输数据的方法和设备
PCT/CN2018/077052 WO2018227994A1 (zh) 2017-06-15 2018-02-23 传输数据的方法和设备

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077052 WO2018227994A1 (zh) 2017-06-15 2018-02-23 传输数据的方法和设备

Country Status (16)

Country Link
US (2) US11050862B2 (zh)
EP (1) EP3621407B1 (zh)
JP (1) JP7143337B2 (zh)
KR (1) KR20200017424A (zh)
CN (2) CN111294153B (zh)
AU (1) AU2018286006A1 (zh)
BR (1) BR112019026476A2 (zh)
CA (1) CA3067481A1 (zh)
CL (1) CL2019003649A1 (zh)
IL (1) IL271375A (zh)
MX (1) MX2019015070A (zh)
RU (1) RU2749896C1 (zh)
SG (1) SG11201912132XA (zh)
TW (1) TWI734010B (zh)
WO (2) WO2018227501A1 (zh)
ZA (1) ZA201908560B (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018227501A1 (zh) * 2017-06-15 2018-12-20 Oppo广东移动通信有限公司 传输数据的方法和设备
CN113543040B (zh) * 2020-04-22 2023-04-07 维沃移动通信有限公司 数据处理方法、数据处理装置及通信设备
US20220070659A1 (en) * 2020-08-28 2022-03-03 Qualcomm Incorporated Techniques for controlling a packet data convergence protocol mode at a user equipment
KR102276090B1 (ko) * 2020-11-16 2021-07-12 한국인터넷진흥원 트래픽 데이터 재배열 방법 및 그 장치
WO2022233033A1 (zh) * 2021-05-07 2022-11-10 Oppo广东移动通信有限公司 无线通信的方法及设备
CN115942301A (zh) * 2021-09-18 2023-04-07 维沃移动通信有限公司 多播业务的状态变量指示方法和设备
CN114124840B (zh) * 2021-11-26 2023-09-15 哲库科技(北京)有限公司 一种接收pdcp包的方法、装置及终端设备
CN115277608B (zh) * 2022-07-22 2023-10-24 哲库科技(北京)有限公司 无线通信的方法及设备
WO2024041340A1 (zh) * 2022-08-23 2024-02-29 华为技术有限公司 一种数据交付方法及通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141405A (zh) * 2007-10-17 2008-03-12 华为技术有限公司 无线网络数据传输方法及无线网络控制器
CN104426638A (zh) * 2013-08-20 2015-03-18 联芯科技有限公司 一种数据递交方法和装置
CN104812000A (zh) * 2014-01-27 2015-07-29 中兴通讯股份有限公司 一种实现数据传输的方法及装置

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB9518540D0 (en) * 1995-09-11 1995-11-08 Nokia Mobile Phones Ltd Radio telephones and methods of operation
JP2005318429A (ja) * 2004-04-30 2005-11-10 Sony Ericsson Mobilecommunications Japan Inc 再送制御方法及び無線通信端末
US20070070937A1 (en) * 2005-09-28 2007-03-29 Mustafa Demirhan Multi-radio mesh network channel selection and load balancing
US7761767B2 (en) * 2005-10-21 2010-07-20 Interdigital Technology Corporation Method and apparatus for retransmission management for reliable hybrid ARQ process
GB2439369A (en) * 2006-06-26 2007-12-27 Samsung Electronics Co Ltd Grouping and transmitting mobile television services available to a mobile device user
WO2009018318A2 (en) * 2007-08-02 2009-02-05 Interdigital Patent Holdings, Inc. Packet data convergence protocol procedures
KR101488015B1 (ko) * 2008-01-25 2015-01-29 엘지전자 주식회사 핸드오버 수행방법 및 데이터 생성방법
CN101729396A (zh) * 2008-10-31 2010-06-09 华为技术有限公司 数据包的发送、接收方法及装置、以及处理方法及系统
KR101315853B1 (ko) * 2009-12-21 2013-10-08 한국전자통신연구원 소스 기지국 시스템에서 핸드오버 처리 방법 및 소스 기지국 시스템
CN101883354A (zh) * 2010-02-04 2010-11-10 重庆索伦互联网信息服务有限公司 基于3g移动网络的自助建站方法
RU2461136C2 (ru) * 2010-04-30 2012-09-10 Виктор Николаевич Куделя Способ гарантированной доставки блоков данных в коммутируемой сети с потерями
CN102655448B (zh) * 2011-03-03 2014-07-16 工业和信息化部电信传输研究所 一种长期演进系统媒质访问控制层的数据传输方法
US20120294281A1 (en) * 2011-05-16 2012-11-22 Electronics And Telecommunications Research Institute Data delivery method performed in receiving apparatus of mobile communication system
US9826502B2 (en) * 2011-07-25 2017-11-21 Qualcomm Incorporated Managing handoff triggering between unicast and multicast services
US20140301188A1 (en) * 2013-04-04 2014-10-09 Nokia Siemens Networks Oy Delivery of protocol data units
US9572171B2 (en) * 2013-10-31 2017-02-14 Intel IP Corporation Systems, methods, and devices for efficient device-to-device channel contention
TWI619315B (zh) 2014-04-02 2018-03-21 Molex Inc Cable termination structure
US20170045258A1 (en) 2014-04-21 2017-02-16 United Technologies Corporation Active Regenerative Heating and Cooling
WO2015163593A1 (en) * 2014-04-22 2015-10-29 Lg Electronics Inc. Method for processing received pdcp pdus for d2d communication system and device therefor
WO2015163625A1 (en) * 2014-04-24 2015-10-29 Lg Electronics Inc. Method for establishing layer-2 entities for d2d communication system and device therefor
BR112016016595B1 (pt) * 2014-08-06 2023-10-17 Ntt Docomo, Inc. Equipamento de usuário
WO2016021820A1 (en) * 2014-08-08 2016-02-11 Lg Electronics Inc. Method for processing a packet data convergence protocol re-ordering function at a user equipment in a dual connectivity system and device therefor
EP3182658A1 (en) * 2015-12-16 2017-06-21 Alcatel Lucent Method, device and system for overhead minimization
CN110505656B (zh) 2016-09-30 2020-07-24 华为技术有限公司 数据处理方法、装置及系统
WO2018227501A1 (zh) * 2017-06-15 2018-12-20 Oppo广东移动通信有限公司 传输数据的方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141405A (zh) * 2007-10-17 2008-03-12 华为技术有限公司 无线网络数据传输方法及无线网络控制器
CN104426638A (zh) * 2013-08-20 2015-03-18 联芯科技有限公司 一种数据递交方法和装置
CN104812000A (zh) * 2014-01-27 2015-07-29 中兴通讯股份有限公司 一种实现数据传输的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Link Control (RLC) protocol specification (Release 7). 3GPP Technical Specification", 3GPP TS 25.322 V7.3.0., 30 June 2007 (2007-06-30), pages 10 - 25, XP050367795 *

Also Published As

Publication number Publication date
CN111294153B (zh) 2021-11-16
IL271375A (en) 2020-01-30
TWI734010B (zh) 2021-07-21
CL2019003649A1 (es) 2020-06-19
TW201906439A (zh) 2019-02-01
CN110771255A (zh) 2020-02-07
US20210297512A1 (en) 2021-09-23
ZA201908560B (en) 2021-04-28
US11050862B2 (en) 2021-06-29
AU2018286006A1 (en) 2020-01-16
CN111294153A (zh) 2020-06-16
JP7143337B2 (ja) 2022-09-28
MX2019015070A (es) 2020-02-13
US11553067B2 (en) 2023-01-10
KR20200017424A (ko) 2020-02-18
WO2018227994A1 (zh) 2018-12-20
BR112019026476A2 (pt) 2020-07-14
EP3621407A4 (en) 2020-07-08
EP3621407B1 (en) 2022-11-09
CN110771255B (zh) 2024-05-10
CA3067481A1 (en) 2018-12-20
US20200120192A1 (en) 2020-04-16
JP2020523908A (ja) 2020-08-06
EP3621407A1 (en) 2020-03-11
SG11201912132XA (en) 2020-01-30
RU2749896C1 (ru) 2021-06-18

Similar Documents

Publication Publication Date Title
WO2018227501A1 (zh) 传输数据的方法和设备
EP3829202B1 (en) Paging method and device
JP2020523908A5 (zh)
CN110800365B (zh) 处理数据的方法和设备
CN112399468B (zh) 一种数据传输方法及接收设备
WO2019095975A1 (zh) 数据包处理的方法和设备
EP3723409A1 (en) Wireless communication method and apparatus
WO2019014918A1 (zh) 传输数据的方法和设备
US11343713B2 (en) Data processing method, transmitter and receiver
WO2023066106A1 (zh) 数据丢弃方法、装置、终端及网络侧设备
CN110326325B (zh) 数据传输的方法、终端设备和网络设备
WO2019095293A1 (zh) 数据处理方法和设备
WO2020097819A1 (zh) 切换时数据传输的方法、装置、芯片及计算机程序
WO2018152751A1 (zh) 一种配置pdcp实体的方法、接收装置和发送装置
WO2019028607A1 (zh) 业务接入的方法和设备

Legal Events

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

Ref document number: 17914113

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17914113

Country of ref document: EP

Kind code of ref document: A1