[go: up one dir, main page]

WO2014177099A1 - Procédé de tri de données basé sur une transmission a flux multiples et dispositif de réception - Google Patents

Procédé de tri de données basé sur une transmission a flux multiples et dispositif de réception Download PDF

Info

Publication number
WO2014177099A1
WO2014177099A1 PCT/CN2014/078624 CN2014078624W WO2014177099A1 WO 2014177099 A1 WO2014177099 A1 WO 2014177099A1 CN 2014078624 W CN2014078624 W CN 2014078624W WO 2014177099 A1 WO2014177099 A1 WO 2014177099A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
pdu
timer
data
lost
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2014/078624
Other languages
English (en)
Chinese (zh)
Inventor
和峰
黄亚达
艾建勋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2014177099A1 publication Critical patent/WO2014177099A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
    • 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/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of 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/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/624—Altering the ordering of packets in an individual queue

Definitions

  • the present invention relates to a technique for ensuring sequential transmission of multi-connection data in a mobile communication system, and more particularly to a data sequencing method and receiving apparatus based on multi-stream transmission. Background technique
  • LTE Long Term Evolution
  • LTE Advanced enhanced LTE
  • the existing user plane data protocol stack of LTE is shown in Figure 1.
  • the downlink data received from the core network via the User Channel GPRS Tunneling Protocol (GTP-U, GPRS Tunneling Protocol for the User Plane) is packetized and then passed through the packet data.
  • the PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Physical Layer
  • UE User Equipment
  • the transmission of uplink data is exactly the opposite of the downlink.
  • the data transmission link between the network and the UE is a one-to-one dedicated link, so the signal quality of the link and the size of the resources used determine the data transmission performance between the two.
  • LPNs Low-power nodes
  • Pico eNB micro base station
  • LPN cells the coverage of the LPN cell is relatively small compared to the macro cell (Macro Cell)
  • the capacity is relatively small, and some LPN cells may be easily occupied by users, resulting in excessive load, thereby affecting users.
  • the throughput of the data while other LPN cells or macro cells will be at a relatively low load level. If the load is to be balanced, the network side needs to perform load balancing operations, but the process is not flexible enough, especially when there are many cells. The load imbalance caused by the lack of flexibility is more serious. In addition, because the number of LPN cells is relatively large, when a user equipment (UE, User Equipment) or terminal moves within the network, frequent inter-cell handover is caused. Handover), which leads to frequent data service terminals and even dropped calls, which also leads to a decline in user data throughput and user experience.
  • UE User Equipment
  • Dual Connectivity is one of them.
  • the dual-connected terminal can simultaneously and two (or more than two, the double connection described in this article is only a generic term, and does not limit the number of connections).
  • the network node remains connected, as shown in Figure 2, where the primary node is called MeNB.
  • Master eNB generally referred to as a macro base station node
  • SeNB Secondary eNB, generally referred to as a micro base station or a low power node
  • the UE is simultaneously connected to the macro cell and the LPN cell.
  • the network side can adjust the amount of transmission data of the terminal on the MeNB and the SeNB node in real time, and if the UE moves or other reasons cause the SeNB cell to change, another cell can still maintain the connection, and the change Does not cause excessive signaling impact.
  • the service data of the bearer 2 on the MeNB is divided into two parts at the PDCP layer, and respectively delivered to the RLC layer of the local lower layer and the RLC layer of the SeNB, and finally sent to the terminal.
  • the sender has not changed the existing protocol very much, mainly involving the shunt problem. But at the receiving end, it involves how to combine multiple connections, ie data received from the connection between the MeNB and the SeNB.
  • the PDCP layer maintains the PDCP count value (PDCP COUNT ) for counting each PDU, which is composed of two parts, including a super frame number (HFN, Hyper frame number) and an order. ⁇ 1 J (SN, sequence number ). In this way, the order delivery of the PDCP SDU is done.
  • the behavior of the receiving end PDCP is related to the transmission mode of the lower layer RLC.
  • the transmission mode of the RLC can be divided into an acknowledge mode (AM, Acknowledged Mode), an unacknowledged mode (UM, Unacknowledged Mode), and a transparent mode (TM). , Transparent Mode ).
  • AM acknowledge mode
  • UM unacknowledged Mode
  • TM transparent mode
  • Transparent Mode Transparent Mode
  • the corresponding two RLC layer entities on the UE side correspond to the RLC entities of the SeNB and the MeNB.
  • the data received by the two LC entities is uniformly delivered to the upper layer.
  • the PDCP layer although the data delivered by each RLC is ordered, because the two connections are not synchronized, the received data is out of order from the PDCP side of the stage. A problem can occur if it is still performed in accordance with the functions of the PDCP in the existing protocol.
  • the processing flow of the normal PDCP in the existing PDCP protocol is as shown in FIG. 4, and includes the following processes:
  • the receiving end PDCP entity maintains a receiving window and receives a PDCP protocol data packet (PDU) from the RLC layer.
  • the window represents the reception and delivery status of the current PDCP Protocol Packet (PDU), which is recorded by a series of PDU SN related variables associated with the receiving window, which may identify the start and end of the window.
  • the window size is fixed, and the receiving window is continuously updated as the PDU is received and delivered.
  • Step 402 Determine, according to the SN number of the currently received PDU, whether it falls within the sequence number range of the window.
  • the PDU SN number is only the low bit in the PDCP count value, when the SN number reaches the maximum, a carry to the HFN occurs, and then restarts from 0, that is, the SN number is cyclic. Therefore, it is necessary to judge the HFN of the PDU when judging.
  • Step 403 if it falls within the window, the PDCP entity needs to perform security processing for the data packet.
  • Step 404 if it falls within the window, the PDCP entity needs to perform header decompression processing (if configured) for the data packet.
  • Step 405 If there is no data packet repeated in the receiving buffer window, the service data packet (SDU) in the PDU is stored in the cache in the order of the SN number of the PDU.
  • SDU service data packet
  • Step 406 Determine whether the currently received PDU is received by the underlying reconstruction. If not, proceed to step 407, otherwise proceed to step 408.
  • Step 407 The PDCP sends all the received SDU data whose PDCP COUNT value is smaller than the current received PDU COUNT value, and the SDU data corresponding to all the consecutive PDUs that are currently receiving the PDCP COUNT value to the upper layer in sequence, and then proceeds to step 410.
  • Step 408 Determine whether the currently received PDU satisfies the delivery condition, that is, determine whether it is the first data packet in the window, and if yes, proceed to step 409.
  • Step 409 The PDCP delivers the SDU data corresponding to all consecutive PDUs starting from the PDU to the upper layer in sequence, and then proceeds to step 410.
  • Step 410 sliding the receiving window.
  • the embodiment of the present invention is to provide a data sorting method and a receiving apparatus based on multi-stream transmission, which can at least reorder the received data to avoid problems caused by out-of-order data arrangement.
  • a data sorting method based on multi-stream transmission comprising:
  • the data is transmitted in multiple streams between the transmitting side and the receiving side, and the receiving side temporarily stores the service data packet SDU corresponding to the received valid protocol data packet PDU in the order of the PDU count value;
  • the receiving side distinguishes between the missing or lost packets in the PDU data packet, and starts the timer management. After the PDU data packet meets the delivery condition, the receiving side transmits the temporary SDU corresponding to the PDU that satisfies the delivery condition. Give the upper layer.
  • the receiving side is a packet data convergence protocol PDCP; the valid PDU is a PDU that falls within a reasonable range of the PDU, and can be correctly processed by the packet data convergence protocol PDCP.
  • the processing of the PDU that can be correctly processed by the PDCP includes at least: successfully decrypting, and/or successfully verifying through the PDCP integrity protection, and/or successfully implementing the header solution. Compression operation.
  • the missing or missing packets that cause discontinuities are:
  • the vacant data packet is generated for the discontinuous valid PDU data packet due to out-of-order or other abnormal reasons, and the vacant data packet needs to be further divided into the missing packet or the lost packet.
  • the receiving side is a packet data convergence protocol (PDCP); the distinguishing is the missing packet or the lost packet, including:
  • PDCP packet data convergence protocol
  • the PDCP receives a packet larger than the current packet PDCP count value from each protocol entity of the underlying protocol, and determines that the current packet is a lost packet, and cannot determine that the other vacant packet of the lost packet is a missing packet; or
  • the timer management includes: starting, stopping, or timeout processing of the timer. Wherein, if the current data packet is a lost packet, the timer management is:
  • the timer management is:
  • the determining whether to stop the reordering timer includes:
  • the method further includes: The reordering timer independently opens a reordering timer for each missing PDU; or enables a reordering timer for a group of missing PDUs;
  • the reordering timer if all missing packets are received, the reordering timer is stopped. Otherwise, if the packet corresponding to the reordering timer is lost, the packet is lost.
  • the timer management when it is determined that the received data packet is received because the underlying layer is re-established, the timer management includes:
  • the determining whether the PDU data packet meets the delivery condition includes:
  • the PDU packet has been successfully received or confirmed to be a lost packet, and all PDU packets before the buffered PDU packet have been successfully received or confirmed to be lost.
  • the method further includes: temporarily storing the SDU corresponding to the PDU that satisfies the delivery condition is deleted, to store the subsequent SDU. Reorder data.
  • a receiving device comprising:
  • the receiving unit is configured to transmit data in multiple streams between the transmitting side and the receiving side, and temporarily store the service data packet SDU corresponding to the received valid protocol data packet PDU in the order of the PDU count value;
  • the data packet type distinguishing unit is configured to distinguish Continuing missing or missing packets in the PDU packet;
  • the sending unit is configured to start timer management. After the PDU data packet meets the delivery condition, the temporary SDU corresponding to the PDU that satisfies the delivery condition is delivered to the upper layer.
  • the receiving unit is located in a packet data convergence protocol (PDCP), and the valid PDU is a PDU that falls within a reasonable range of the PDU and can be correctly processed by the packet data convergence protocol PDCP.
  • the receiving unit is further configured to perform processing on the PDU that can be correctly processed by the PDCP, including at least: successfully decrypting, and/or successfully performing PDCP integrity protection verification, and/or successfully implementing a header decompression operation. .
  • the packet type distinguishing unit is further configured to generate a vacant packet for the discontinuity of the received valid PDU packet due to out-of-order or other abnormal reasons, and the vacant packet needs to be further divided into the missing packet.
  • the receiving unit is located in a packet data convergence protocol PDCP;
  • the packet type distinguishing unit is further configured to: the PDCP receives a packet larger than the current packet PDCP count value from each protocol entity of the underlying protocol, and determines that the current data packet is a lost packet, and cannot be determined as a lost packet.
  • the other vacant packet is a missing packet; or, when the reordering timer expires, it is determined that the packet corresponding to the reordering timer is lost, and the packet is lost.
  • the sending unit further includes:
  • the timer management module is configured to start, stop, or time out the timer.
  • the timer management module is further configured to: if the current data packet is a lost packet, determine whether a timer corresponding to the lost packet is running, and if yes, stop the timer corresponding to the lost packet .
  • the timer management module is further configured to: when a reordering timer for the missing packet is not enabled, start a reordering timer corresponding to the missing packet; for the reordering timer that is running And determining, according to the currently received PDU, whether to stop the reordering timer.
  • the timer management module is further configured to determine whether to stop the reordering timer, if the data packet corresponding to the reordering timer has been successfully received or confirmed as a lost packet, the timer management module does not exist. Missing package, stop the reordering timer.
  • the timer management module is further configured to use the reordering timer for each missing
  • the PDU independently starts a reordering timer; or starts a reordering timer for a group of missing PDUs; if all missing packets are received during the reordering timer, the reordering timer is stopped, otherwise the reordering is considered If the timer packet is lost, it is a lost packet.
  • the timer management module is further configured to stop all running reordering timers when the received data packet is received because the underlying layer is reestablished; or restart the reordering timer.
  • the sending unit further includes:
  • a condition determining module configured to determine whether the PDU data packet satisfies a delivery condition, and if the PDU data packet has been successfully received or is confirmed to be lost, the packet is lost, and all of the temporary storage of the PDU data packet The PDU packets have been successfully received or confirmed to be lost.
  • the sending unit further includes:
  • the method further includes: deleting the SDU corresponding to the PDU that satisfies the delivery condition, and deleting the SDU to store the subsequent weight Sort the data.
  • the receiving unit, the data packet type distinguishing unit, the sending unit, the timer management module, the condition determining module, and the deleting module may use a central processing unit (CPU, Central) when performing processing.
  • CPU Central
  • Processing Unit Digital Signal Processor
  • FPGA Field-Programmable Gate Array
  • the method of the embodiment of the present invention includes: transmitting data in multiple streams between the transmitting side and the receiving side, and receiving, by the receiving side, the service data packet SDU corresponding to the received valid protocol data packet PDU is temporarily stored in the order of the PDU count value;
  • the PDU packet causes a discontinuous missing packet or a lost packet.
  • the timer management is started. After the PDU packet satisfies the delivery condition, the receiving side transmits the temporarily stored SDU corresponding to the PDU that satisfies the delivery condition to the upper layer.
  • the PDU count value is temporarily stored in the order of the PDU, and the type of the data packet is classified as a missing packet or a lost packet, and is managed by the timer.
  • the receiving side After the delivery condition is satisfied, the receiving side temporarily stores the PDU corresponding to the delivery condition that satisfies the delivery condition.
  • the SDU is passed to the upper layer. Therefore, the reordering method can at least reorder the received data to avoid the problem caused by the out-of-order arrangement of the data.
  • 1 is a schematic diagram of an existing LTE user plane protocol stack
  • FIG. 2 is a schematic diagram of an existing dual connection scenario
  • FIG. 3 is a schematic diagram of a conventional multi-connection data offloading manner
  • FIG. 4 is a schematic diagram of a PDCP layer processing flow in an existing protocol
  • FIG. 5 is a schematic diagram of a PDCP reordering process according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a timer management process according to an embodiment of the present invention.
  • FIG. 7 is another schematic diagram of a timer management process according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a lost packet determination process according to an embodiment of the present invention. detailed description
  • the data sorting scheme based on multi-stream transmission in the embodiment of the present invention can be applied to a scene and a mode (for example, AM mode or UM mode) for ensuring sequential transmission of multi-connection data in a mobile communication system.
  • a mode for example, AM mode or UM mode
  • the data sorting method based on multi-stream transmission in the embodiment of the present invention is an example of a PDCP reordering scheme based on multi-stream transmission in the case of multi-connection data transmission, and includes at least the following contents:
  • the PDCP stores the service data packets (SDUs) corresponding to the valid protocol data packets (PDUs) in the cache according to the PDU count value, and distinguishes between the missing packets and the lost packets caused by the PDU data packets, and starts the timer management. , PDCP when the PDU packet meets the delivery conditions The stored SDU corresponding to the PDU that satisfies the delivery condition is delivered to the upper layer.
  • SDUs service data packets
  • PDUs valid protocol data packets
  • the valid PDU refers to a PDU that falls within a reasonable range of the PDU count value and can be correctly processed by the PDCP protocol function.
  • the PDU count value is greater than COUNT1 and less than equal to COU T2.
  • COUNTl is the maximum PDU count value corresponding to the SDU that the previous PDCP has submitted
  • COU T2 COU Tl+ A
  • ⁇ is the reordering window width. It is generally half the length of the PDCP SN number.
  • the correct processing by the PDCP protocol function comprises: successfully decrypting, and/or successfully performing PDCP integrity protection verification, and/or successfully implementing operations such as head decompression.
  • the specific processing content depends on the different processing of the data packet by the transmitting end.
  • the missing packet and the lost packet are caused by the out-of-order or other abnormal reasons, and the received valid PDU data packet is discontinuous, and the vacant data packet is generated, wherein the vacant data packet can be further distinguished.
  • the vacant data packet is generated, wherein the vacant data packet can be further distinguished.
  • the method for judging the lost packet is: the PDCP receives a packet larger than the current packet PDCP COUNT value from each protocol entity of the underlying protocol, and determines that the current data packet is a lost packet, or corresponds to a reordering timer. When the timeout expires, it is confirmed that the packet corresponding to the timer is lost and becomes a lost packet.
  • the missing package that is, other vacant packets that cannot be determined as missing packets.
  • the timer management is configured to be reordered to solve the transmission disorder problem. At this point, you need to start at the right time to wait for the missing packets, or stop the timer to ensure that the data is normally delivered to the upper layer.
  • the timer management mainly includes starting, stopping, and timeout processing of the timer.
  • the timer management comprises:
  • the timer management includes:
  • the reordering timer for the current missing packet. That is, if the reordering timer for the missing packet has not been opened, the reordering timer is started; For the running reordering timer, it is determined whether to stop the reordering timer according to the currently received PDU.
  • the determining whether to stop the reordering timer comprises:
  • the data packet corresponding to the timer has been successfully received or confirmed as a lost packet, that is, if there is no missing packet, the reordering timer is stopped.
  • the length of the timer is determined by a specific implementation, for example, it may be dynamically estimated according to the delay between different transmission links, or may be set to a fixed value.
  • the reordering timer may independently enable one reordering timer for each missing PDU, or may open a reordering timer for a group of missing PDUs.
  • the PDCP may further distinguish whether the currently received data packet is received due to the underlying reconstruction. If the currently received PDU is received due to the underlying reconstruction, the timer management may be directed to This scene is further enhanced. At this time, the timer management includes:
  • the method for determining whether a certain PDU data packet satisfies the delivery includes: the PDU has been successfully received or confirmed to be a lost packet, and all the PDUs before the PDU have been successfully received or It was confirmed that a loss occurred.
  • the corresponding SDU is empty.
  • the corresponding data stored in the cache is to be deleted to store subsequent other reordered data.
  • the receiving unit is configured to transmit data in multiple streams between the transmitting side and the receiving side, and temporarily store the service data packet SDU corresponding to the received valid protocol data packet PDU in the order of the PDU count value; a packet type distinguishing unit configured to distinguish between a missing packet or a lost packet in the PDU packet;
  • the sending unit is configured to start timer management. After the PDU data packet meets the delivery condition, the temporary SDU corresponding to the PDU that satisfies the delivery condition is delivered to the upper layer.
  • the receiving unit is located in a packet data convergence protocol PDCP, and the valid PDU is specifically a PDU that falls within a reasonable range of the PDU and can be correctly processed by the packet data convergence protocol PDCP.
  • PDCP packet data convergence protocol
  • the receiving unit is further configured to perform processing on the PDU that can be correctly processed by the PDCP, at least: successfully decrypting, and/or successfully verifying by PDCP integrity protection, and/or successfully implementing header decompression operating.
  • the data packet type distinguishing unit is further configured to generate a vacant data packet for a discontinuity of the received valid PDU data packet due to out-of-order or other abnormal reasons, and the vacant data packet needs to be further divided into the Missing package or the missing package.
  • the receiving unit is located in a packet data convergence protocol PDCP;
  • PDCP packet data convergence protocol
  • the packet type distinguishing unit is further configured to: the PDCP receives a packet larger than the current packet PDCP count value from each protocol entity of the underlying protocol, and determines that the current data packet is a lost packet, and cannot be determined as a lost packet.
  • the other vacant packet is a missing packet; or, when the reordering timer expires, it is determined that the packet corresponding to the reordering timer is lost, and the packet is lost.
  • the sending unit further includes: a timer management module configured to start, stop, or timeout processing of the timer.
  • a timer management module configured to start, stop, or timeout processing of the timer.
  • the timer management module is further configured to: if the current data packet is a lost packet, determine whether a timer corresponding to the lost packet is running, and if yes, stop the timing of the corresponding lost packet Device.
  • the timer management module is further configured to not open the missing package When the reordering timer is started, a reordering timer corresponding to the missing packet is started; and for the reordering timer that is running, determining whether to stop the reordering timer according to the currently received PDU.
  • the timer management module is further configured to determine whether to stop the reordering timer, if the data packet corresponding to the reordering timer has been successfully received or confirmed as a lost packet, then There is a missing packet, stopping the reordering timer.
  • the timer management module is further configured to: the reordering timer independently open a reordering timer for each missing PDU; or enable a reordering timer for a group of missing PDUs; During the time, if all the missing packets are received, the reordering timer is stopped. Otherwise, if the packet corresponding to the reordering timer is lost, the packet is lost.
  • the sending unit further includes:
  • a condition determining module configured to determine whether the PDU data packet satisfies a delivery condition, and if the PDU data packet has been successfully received or is confirmed to be lost, the packet is lost, and all of the temporary storage of the PDU data packet The PDU packets have been successfully received or confirmed to be lost, which is a lost packet.
  • the timer management module is further configured to stop all running reordering timers when the received data packet is received due to the underlying reconstruction, or restart the reordering timer.
  • the sending unit further includes:
  • the method further includes: deleting the SDU corresponding to the PDU that satisfies the delivery condition, and deleting the SDU to store the subsequent weight Sort the data.
  • the receiving unit is specifically a receiver
  • the sending unit is specifically a receiver
  • the timer management module is specifically a timing controller
  • the data packet type distinguishing unit, the condition determining module, and the deleting module may be implemented by using a processor.
  • CPU Central Processing Unit
  • DSP Digital Singnal Processor
  • FPGA Programmable Array
  • the beneficial effects of the data sorting scheme of the embodiment of the present invention are as follows: Reordering the received data can solve the problem of packet out-of-sequence caused by the unsynchronization between multiple connections, and complete the PDCP to multi-connection splitting data. Sorting, guarantees an orderly data transfer for the upper layer. Prevent PDCP packet loss, count value confusion, and security protection failure due to out-of-order.
  • the method described in the present invention fully multiplexes the existing delivery mechanism to ensure the backward compatibility of the network and the terminal on the hardware and software to the greatest extent.
  • the PDCP reordering process in the embodiment of the present invention includes the following steps: Step 501: The receiving end PDCP receives a PDCP protocol data packet (PDU) from the bottom layer.
  • PDU PDCP protocol data packet
  • RLC entities ie, RLC entities
  • the method of the present invention is also applicable to any of a plurality of underlying protocol entities.
  • Step 502 Determine whether the currently received PDCP PDU count value falls within a reasonable range, that is, determine whether the PDCP COUNT of the current PDU is greater than the maximum PDCP COUNT value submitted by the last upper layer, and the difference is not greater than the reordering window width. . If yes, step 503 is performed. Otherwise, step 511 exception processing is performed, and the data packet is discarded.
  • Step 503 The PDCP entity needs to perform corresponding PDCP protocol processing for the data packet, which may include decryption, and/or integrity protection verification, and/or header decompression, and the like. If the corresponding processing is successful, the packet is considered to be a valid PDU packet.
  • Step 504 If there is no data packet in the receiving buffer that is duplicated, the service data packet (SDU) in the PDU is stored in the cache in the order of the count value of the PDU. Step 505, performing timer management.
  • SDU service data packet
  • Step 506 Determine whether the stored data packet satisfies the delivery condition, and if yes, proceed to step 509.
  • the PDCP delivers the SDU sequence corresponding to all the PDUs satisfying the delivery condition to the upper layer.
  • step 506 if the timer is turned on at the granularity of each PDU, a reordering timer is turned on for each missing PDU.
  • the timer management process of the embodiment of the present invention assumes that the SN number of the currently received PDU is n, including:
  • Step 601 Determine whether there is currently a reordering timer corresponding to the SNn running, if yes, go to 602, otherwise go to 603.
  • Step 602 if there is a reordering timer running, stop the timer, and then go to the step
  • Step 603 Determine whether there is a missing packet in the PDU before the currently received data packet with the SN being n in the current receiving window. If yes, go to 604, otherwise go to step 606.
  • step 604 it is judged whether or not each missing packet has been lost. If yes, the process proceeds to 607, otherwise, the process proceeds to step 605.
  • step 605 it is determined whether each missing packet has a corresponding reordering timer running, and if so, it proceeds to 609, otherwise proceeds to step 606.
  • Step 606 Enable a corresponding reordering timer for each missing packet, and proceed to step 609.
  • Step 607 Determine whether there is a reordering timer corresponding to the lost packet, if yes, go to 608, otherwise go to step 609.
  • Step 608 stopping the reordering timer for the PDU.
  • the timer management module processes the processing, and proceeds to the next processing.
  • step 604 the receiving end determines that a PDU is lost:
  • the reordering timer corresponding to the data packet times out
  • PDCP receives PDUs with COUNT values greater than the COUNT value of each packet from each of the underlying protocol entities, that is, these PDUs are not received due to the underlying re-establishment, and the packet is judged to be lost.
  • two RLC protocol entities under the PDCP are taken as an example.
  • the process of determining the lost packet is as shown in FIG. 8 , which is the state of the PDU received by the PDCP side, where the data packets 4 and 5 are the PDUs received from the RLC1.
  • Packet 7 is the PDU received from RLC2, and packets 4, 5, and 7 are not received because the underlying reconstruction occurs, and packets 1, 2, 3, and 6 are missing packets, so the data before packet 7 It is not continuous. But you can continue to make further judgments on packets 1, 2, 3 and 6:
  • PDCP receives packets larger than its COUNT value from both LC1 and RLC2, so the packets corresponding to 1, 2, and 3 can be considered to have been lost.
  • the receiving end determines that a PDU has been lost, it may not need to start the reordering timer. If the reordering timer for the data packet has been started before, the reordering timer may be stopped.
  • a reordering timer is turned on for a group of missing PDUs. It is possible to maintain reordering timers for several groups at the same time, or one PDCP entity can maintain only one reordering timer.
  • the timer management process of the embodiment of the present invention is as shown in FIG. 7. As shown, it is assumed that the SN number of the currently received PDU is n, including:
  • Step 701 Determine whether the current receiving PDU has a corresponding reordering timer running, and if yes, proceed to step 702, otherwise proceed to step 704.
  • Step 702 Determine whether all the missing PDUs corresponding to the timing are received or confirmed to be lost. If yes, go to step 703, otherwise go to step 706.
  • Step 703 stopping the reordering timer.
  • Step 704 Determine whether there is a missing packet before the PDU corresponding to the maximum PDCP COUNT value received in the current receiving window. If there is a missing packet, go to step 705, otherwise go to step 706.
  • the determination in this step may also be equivalently described as determining whether the corresponding PDCP PDU in the current receive buffer is discontinuous. If the answer is yes, then go to step 705, otherwise go to step 706.
  • Step 705 start a timer for all missing packets.
  • the missing PDU corresponding to the reordering timer includes all the missing packets before the PDU corresponding to the received maximum PDCP COUNT value in the current receiving window. Or described as all missing packets before the last PDU in the received PDU in the receiving window;
  • Step 706 the timer management module processes the processing, and proceeds to the next processing.
  • the judgment in steps 702 and 704 in the above process is the same as the flow of Fig. 8 when distinguishing the lost packets.
  • the receiving end determines that a PDU has been lost, it does not count it into the missing PDU. That is, the packet is not considered to be a missing packet, but the packet is lost.
  • the missing data packet corresponding to the timer that has not been received is considered to be lost. That is to become a lost package.
  • step 507 it is determined whether the data packet satisfies the delivery condition. It can also be equivalently described as determining whether the currently received data packet is the first PDU data packet after the last completed PDU, that is, whether the PDCP COUNT value of the current PDU is equal to the largest PDU corresponding to the SDU that the previous PDCP has delivered. The count value is +1.
  • the receiving end refers to the terminal for the downlink data, and refers to the network side, that is, the MeNB and the SeNB for the uplink data.
  • the RLC protocol entities are described as the underlying protocol entity of the PDCP.
  • the PDCP underlying protocol is any other protocol, as long as the underlying protocol can ensure the orderly delivery of the PDCP PDU.
  • the method of the present invention is illustrated by the steps in FIG. 5, but in the specific implementation process, it is not limited to a specific step, and all the reordering methods according to the present invention are described. Similar reordering methods are within the scope of the present invention.
  • the integrated modules described in the embodiments of the present invention may also be stored in a computer readable storage medium if they are implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product.
  • the computer software product is stored in a storage medium and includes a plurality of instructions.
  • a computer device (which may be a personal computer, server, or network device, etc.) is implemented to perform all or part of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like.
  • the medium of the code includes: a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like.
  • the medium of the code includes: a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like.
  • the medium of the code is not limited to any specific combination of hardware and software.
  • an embodiment of the present invention further provides a computer storage medium, wherein a computer program is stored, where the computer program is used to execute a multi-stream transmission based data sorting method according to an embodiment of the present invention.
  • the method of the embodiment of the present invention includes: transmitting data in multiple streams between the transmitting side and the receiving side, and receiving, by the receiving side, the service data packet SDU corresponding to the received valid protocol data packet PDU is temporarily stored in the order of the PDU count value;
  • the PDU packet causes a discontinuous missing packet or a lost packet.
  • the timer management is started. After the PDU packet satisfies the delivery condition, the receiving side transmits the temporarily stored SDU corresponding to the PDU that satisfies the delivery condition to the upper layer.
  • the reordering manner can at least reorder the received data to avoid the problem caused by the disordered arrangement of the data.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Communication Control (AREA)

Abstract

La présente invention concerne un procédé de tri de données basé sur une transmission à flux multiples et un dispositif de réception, ledit procédé comprenant les opérations suivantes : des données sont transmises dans de multiples flux entre un côté envoi et un côté réception, le côté réception stocke temporairement, conformément à un ordre de valeur de comptage de PDU, une unité de données de service (SDU) correspondant à une unité de données de protocole (PDU) valide ; le côté réception effectue une distinction entre des unités manquantes ou des unités perdues qui entraînent une discontinuité dans ladite unité de données PDU ; une gestion de temporisateur est démarrée et, après que l'unité de données de PDU satisfait des conditions de distribution, le côté réception transmet la SDU stockée temporairement, correspondant à la PDU qui satisfait des conditions de distribution, à un niveau supérieur.
PCT/CN2014/078624 2013-09-26 2014-05-28 Procédé de tri de données basé sur une transmission a flux multiples et dispositif de réception Ceased WO2014177099A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310447176.7A CN104519524A (zh) 2013-09-26 2013-09-26 一种基于多流传输的数据排序方法及接收装置
CN201310447176.7 2013-09-26

Publications (1)

Publication Number Publication Date
WO2014177099A1 true WO2014177099A1 (fr) 2014-11-06

Family

ID=51843174

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/078624 Ceased WO2014177099A1 (fr) 2013-09-26 2014-05-28 Procédé de tri de données basé sur une transmission a flux multiples et dispositif de réception

Country Status (2)

Country Link
CN (1) CN104519524A (fr)
WO (1) WO2014177099A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113726477A (zh) * 2017-07-10 2021-11-30 北京小米移动软件有限公司 数据传输方法及装置、接收端设备和发送端设备
EP3926916A4 (fr) * 2019-03-27 2022-04-20 Huawei Technologies Co., Ltd. Procédé de commande de temporisateur, procédé de traitement de paquet de données et dispositif
US20230216804A1 (en) * 2022-01-04 2023-07-06 Vmware, Inc. Efficient mechanism for the transmission of multipath duplicate packets

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9999049B2 (en) * 2015-08-31 2018-06-12 Qualcomm Incorporated Avoiding unnecessary protocol data unit (PDU) transmissions
CN105871747B (zh) * 2016-03-24 2019-07-30 京信通信系统（中国）有限公司 通信系统下行数据传输方法和系统
GB2561545B (en) * 2017-03-24 2021-12-15 Tcl Communication Ltd Layer 2 architecture for cellular radio systems
CN108810984B (zh) * 2017-05-05 2020-03-24 维沃移动通信有限公司 数据处理方法及装置
CN109565377A (zh) * 2017-07-21 2019-04-02 Oppo广东移动通信有限公司 传输数据的方法和设备
CN109474651B (zh) * 2017-09-08 2020-08-25 华为技术有限公司 处理数据的方法和设备
WO2019047912A1 (fr) * 2017-09-08 2019-03-14 华为技术有限公司 Procédé et dispositif de traitement de données
CN109803277B (zh) * 2017-11-16 2020-12-22 华为技术有限公司 数据包处理的方法和设备
CN109039549B (zh) * 2018-07-13 2021-07-23 新华三技术有限公司 一种报文重传方法及装置
WO2020172656A1 (fr) * 2019-02-22 2020-08-27 Apple Inc. Système et procédé de réduction d'interruptions de transfert intercellulaire
CN110278058B (zh) * 2019-06-05 2020-11-03 华为技术有限公司 一种冗余信息反馈方法及通信装置
CN113543040B (zh) * 2020-04-22 2023-04-07 维沃移动通信有限公司 数据处理方法、数据处理装置及通信设备
WO2022205062A1 (fr) * 2021-03-31 2022-10-06 华为技术有限公司 Appareil et procédé de traitement de données
CN115707134A (zh) * 2021-08-10 2023-02-17 大唐移动通信设备有限公司 数据处理方法、装置及存储介质
CN114268991A (zh) * 2021-12-27 2022-04-01 展讯通信（上海）有限公司 数据传输方法、装置、电子设备、存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101677266A (zh) * 2008-09-19 2010-03-24 大唐移动通信设备有限公司 控制重排序和重复消除操作的方法、系统及装置
CN102104535A (zh) * 2009-12-18 2011-06-22 华为技术有限公司 一种pdcp数据发送方法、装置及系统
CN102958102A (zh) * 2011-08-22 2013-03-06 中兴通讯股份有限公司 一种rlc分流传输方法及系统
CN103141051A (zh) * 2010-10-01 2013-06-05 交互数字专利控股公司 用于启动从多个传输点的接收的mac和rlc架构和程序
CN103201977A (zh) * 2010-11-08 2013-07-10 高通股份有限公司 用于使用多链路pdcp 子层进行多点hsdpa 通信的系统和方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101043301B (zh) * 2006-03-22 2011-08-10 华为技术有限公司 一种无线通信系统中的数据重排重组方法及其基站
WO2008136115A1 (fr) * 2007-04-26 2008-11-13 Fujitsu Limited Station de base, station mobile, système de communication, procédé de transmission et procédé de réordonnancement
CN101795494B (zh) * 2009-02-03 2012-10-10 中国移动通信集团公司 一种lte-a系统内的数据分流方法、装置及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101677266A (zh) * 2008-09-19 2010-03-24 大唐移动通信设备有限公司 控制重排序和重复消除操作的方法、系统及装置
CN102104535A (zh) * 2009-12-18 2011-06-22 华为技术有限公司 一种pdcp数据发送方法、装置及系统
CN103141051A (zh) * 2010-10-01 2013-06-05 交互数字专利控股公司 用于启动从多个传输点的接收的mac和rlc架构和程序
CN103201977A (zh) * 2010-11-08 2013-07-10 高通股份有限公司 用于使用多链路pdcp 子层进行多点hsdpa 通信的系统和方法
CN102958102A (zh) * 2011-08-22 2013-03-06 中兴通讯股份有限公司 一种rlc分流传输方法及系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113726477A (zh) * 2017-07-10 2021-11-30 北京小米移动软件有限公司 数据传输方法及装置、接收端设备和发送端设备
EP3926916A4 (fr) * 2019-03-27 2022-04-20 Huawei Technologies Co., Ltd. Procédé de commande de temporisateur, procédé de traitement de paquet de données et dispositif
US11627190B2 (en) 2019-03-27 2023-04-11 Huawei Technologies Co., Ltd. Timer control method, data packet processing method, and device
US20230216804A1 (en) * 2022-01-04 2023-07-06 Vmware, Inc. Efficient mechanism for the transmission of multipath duplicate packets

Also Published As

Publication number Publication date
CN104519524A (zh) 2015-04-15

Similar Documents

Publication Publication Date Title
WO2014177099A1 (fr) Procédé de tri de données basé sur une transmission a flux multiples et dispositif de réception
CN113396607B (zh) 用于在无线通信系统中执行切换的方法和设备
US10021663B2 (en) Method and device for realizing data transmission
US11057797B2 (en) Method and device for processing information
EP2999296B1 (fr) Configurer un temporisateur de rejet
EP3039900B1 (fr) Procédés de remise en ordre de paquets pdcp
US9906994B2 (en) Handover method, master base station and slave base station
RU2603626C2 (ru) Работа с множеством планировщиков в беспроводной системе
CN103888222B (zh) 一种数据包处理方法及装置
EP2981128B1 (fr) Procédé et système de transmission de données
CN114946217A (zh) 下一代移动通信系统中当daps移交失败时为每个承载配置回退的方法和装置
EP4145735A1 (fr) Procédé et système pour des améliorations de couche de protocole dans le délestage de données sur de petites cellules
KR20190129079A (ko) 신규 무선 접속 기술에서의 중복 및 rlc 동작
WO2015117516A1 (fr) Procédé et terminal de transmission de données de liaison montante
WO2015027719A1 (fr) Procédé de transmission de données à flux multiples coordonnés, et enb
CN103533586A (zh) 切换过程中的信令交互及层重建的方法和设备
CN105493554A (zh) 缓解双连接系统中的流量阻塞
WO2014114101A1 (fr) Procédé et appareil de transmission de données multiflux
US20160373962A1 (en) Data package shunting transmission method and system, and computer stoarge medium
TWI797414B (zh) 用於行動性增強之方法及其使用者設備
CN109246852A (zh) 无线协议层实体处理方法以及相应的用户设备
WO2014114121A1 (fr) Procédé, appareil et système pour réaliser une détection de sécurité dans un réseau hétérogène
WO2015123939A1 (fr) Procédé d'interaction d'informations, système et station de base
CN105323852B (zh) 上行承载的修改方法及装置
EP3876582A1 (fr) Procédé et appareil de transmission de données

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

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

Country of ref document: EP

Kind code of ref document: A1