WO2019237530A1 - 数据按序递交的方法、网络设备及终端设备 - Google Patents

数据按序递交的方法、网络设备及终端设备 Download PDF

Info

Publication number
WO2019237530A1
WO2019237530A1 PCT/CN2018/104908 CN2018104908W WO2019237530A1 WO 2019237530 A1 WO2019237530 A1 WO 2019237530A1 CN 2018104908 W CN2018104908 W CN 2018104908W WO 2019237530 A1 WO2019237530 A1 WO 2019237530A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
data stream
data
bearer
instruction information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/104908
Other languages
English (en)
French (fr)
Inventor
尤心
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
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
Priority to SG11202006962SA priority Critical patent/SG11202006962SA/en
Priority to CN202010564121.4A priority patent/CN111654883B/zh
Priority to EP18922754.9A priority patent/EP3720033B1/en
Priority to BR112020015544-6A priority patent/BR112020015544A2/pt
Priority to MX2020008734A priority patent/MX2020008734A/es
Priority to JP2020544643A priority patent/JP7097981B2/ja
Priority to AU2018427836A priority patent/AU2018427836B2/en
Priority to CA3089382A priority patent/CA3089382C/en
Priority to KR1020207025593A priority patent/KR102332206B1/ko
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to RU2020127015A priority patent/RU2751673C1/ru
Priority to CN201880068680.7A priority patent/CN111247765A/zh
Priority to TW108120565A priority patent/TW202002701A/zh
Publication of WO2019237530A1 publication Critical patent/WO2019237530A1/zh
Priority to US16/892,444 priority patent/US11018832B2/en
Anticipated expiration legal-status Critical
Priority to US17/231,573 priority patent/US11689334B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0096—Indication of changes in allocation
    • 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/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00222—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between different packet switched [PS] network technologies, e.g. transferring data sessions between LTE and WLAN or LTE and 5G
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023—Buffering or recovering information during reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/142—Reselecting a network or an air interface over the same radio air interface technology
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present invention relates to the field of information processing technology, and in particular, to a method for sequentially submitting data, a network device, a terminal device, and a computer storage medium.
  • eMBB enhanced mobile ultra-broadband
  • URLLC low-latency high-reliability communication
  • mMTC large-scale machine-type communication
  • LTE-NR Dual Connectivity LTE-NR Dual Connectivity
  • MN master node
  • SN secondary node
  • Figure 1-3 shows the network deployment and networking architecture.
  • DC dual connection
  • EN-DC the LTE node acts as the MN node
  • NR node acts as the SN node, which is connected to the EPC core network.
  • the NR acts as the MN node and the eLTE acts as the SN node, which is connected to the 5GC core network.
  • eLTE acts as the MN node and NR acts as the SN node, which connects to the 5GC core network.
  • NRDC NR acts as the MN node and NR acts as the SN node, which is connected to the 5GC core network.
  • the bearer types in DC mode are shown in Figure 4.
  • the bearer types on the user plane include the primary cell group (MCG) bearer, the secondary cell group (SCG) bearer, and the MCG split (Split). ) bearer.
  • MCG primary cell group
  • SCG secondary cell group
  • Split MCG split
  • SDAP Service Data Adaptation Protocol
  • This protocol layer is used to map data from the QoS data flow (Flow) of the core network to different DRBs.
  • ELTE supports LTE base stations to access the 5G core network in LTE, so the eLTE protocol stack also includes the SDAP protocol.
  • NE-DC, 5GC-EN-DC, and NR DC each MN and SN node will use the SDAP protocol. Therefore, there is a problem of out-of-order delivery during the bearer change process in the prior art.
  • an embodiment of the present invention provides a method for sequentially submitting data, a network device, a terminal device, and a computer storage medium.
  • An embodiment of the present invention provides a method for sequentially submitting data, which is applied to a first network device.
  • the method includes:
  • the first network device When the data stream bearer is transferred from the first network device to the second network device, the first network device sends a first instruction information to the second network device; wherein the first instruction information is used to indicate the first network device
  • the second network device starts to sequentially transfer the transferred data stream on the new bearer.
  • An embodiment of the present invention provides a method for sequentially submitting data, which is applied to a second network device.
  • the method includes:
  • the first instruction information sent by the first network device is received; wherein the first instruction information is used to instruct the second network device to start
  • the transferred data streams are transmitted in sequence on the new bearer.
  • An embodiment of the present invention provides a method for sequentially submitting data, which is applied to a terminal device.
  • the method includes:
  • the terminal device transmits the first part of the data stream and the second instruction information to the first network device; the second instruction information is used for Indicates that the first part of the data transfer in the data stream that was not completed when the transfer occurred is complete.
  • An embodiment of the present invention provides a method for sequentially submitting data, which is applied to a first network device.
  • the method includes:
  • the data stream bearer When the data stream bearer is transferred from the first network device to the second network device, the first part of the data stream from the terminal device and the second instruction information from the terminal device are received; the second instruction information is The completion of the first part of the data transmission that was not completed in the data stream when the transfer occurred;
  • An embodiment of the present invention provides a method for sequentially submitting data, which is applied to a second network device.
  • the method includes:
  • the bearer of the data stream When the bearer of the data stream is transferred from the first network device to the second network device, the first part of the data stream and the second indication information from the first network device are received, or the second part from the first network device is received. Instruction information; the second instruction information is used to indicate that the first part of the data stream that is not transmitted and completed in the data stream when the transfer occurs is completed;
  • the second network device Based on the second instruction information, after the second network device submits the first part of data to the core network, the second network device delivers the second part of the data stream to the core network.
  • An embodiment of the present invention provides a first network device, including:
  • the first communication unit when the data stream bearer is transferred from the first network device to the second network device, the first network device sends the first instruction information to the second network device; wherein the first instruction information is And instructing the second network device to start sequentially transferring the transferred data stream on a new bearer.
  • An embodiment of the present invention provides a second network device, including:
  • the second communication unit receives the first instruction information sent by the first network device when the bearer of the data stream is transferred from the first network device to the second network device, wherein the first instruction information is used to indicate the The second network device starts to sequentially transfer the transferred data stream on the new bearer.
  • An embodiment of the present invention provides a terminal device, including:
  • the third communication unit when the data stream bearer is transferred from the first network device to the second network device, transmits the first part of the data stream and the second instruction information to the first network device; the second instruction information is used to The first part of the data stream in the data stream that is not completed when the transfer is indicated is complete.
  • An embodiment of the present invention provides a first network device, including:
  • a fourth communication unit when the data stream bearer is transferred from the first network device to the second network device, receiving the first part of the data stream sent by the terminal device and the second instruction information sent by the terminal device; Two instructions, which are used to indicate that the first part of the data stream that has not been transmitted is completed when the transfer occurs; sending the first part of the data stream and the second instruction information to the second network device, or The first part of the data stream is sent to a core network and the second indication information is sent to a second network device.
  • An embodiment of the present invention provides a second network device, including:
  • a fifth communication unit when the data stream bearer is transferred from the first network device to the second network device, receiving the first part of the data stream and the second indication information from the first network device, or receiving the first network device
  • the second instruction information sent; the second instruction information is used to indicate that the first part of the data stream that has not been completed in the data stream when the transfer occurs is completed;
  • a fifth processing unit after the first part of the data is submitted to the core network based on the second instruction information, submits the second part of the data stream to the core network.
  • An embodiment of the present invention provides a network device, including: a processor and a memory for storing a computer program capable of running on the processor, wherein when the processor is used to run the computer program, execute the steps of the foregoing method .
  • An embodiment of the present invention provides a terminal device including a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the method when the computer program is run. step.
  • An embodiment of the present invention provides a computer storage medium.
  • the computer storage medium stores computer-executable instructions. When the computer-executable instructions are executed, the foregoing method steps are implemented.
  • the first network device when the bearer of the data stream is transferred from the first network device to the second network device, the first network device can send the first instruction information to the second network device.
  • the first indication information causes the second network device to start sequentially transferring the transferred data stream on a new bearer. Therefore, when the data flow transfer occurs, the destination network device side can guarantee the order of transmitting data.
  • Figure 1-3 is a schematic diagram of DC network deployment and networking architecture
  • FIG. 4 is a schematic diagram of a bearer type in a DC mode
  • FIG. 5 is a schematic diagram of out-of-order delivery of a bearer transfer in the prior art
  • FIG. 6 is a first schematic flowchart of a method for sequentially submitting data according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of a downlink data processing scenario according to an embodiment of the present invention.
  • FIG. 8 is a second schematic flowchart of a method for sequentially submitting data according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of an uplink data processing scenario according to an embodiment of the present invention.
  • FIG. 10 is a third schematic flowchart of a method for sequentially submitting data according to an embodiment of the present invention.
  • FIG. 11 is a schematic flowchart of a method for sequentially submitting data according to an embodiment of the present invention.
  • FIG. 12 is a first schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 13 is a second schematic diagram of a structure of a network device according to an embodiment of the present invention.
  • FIG. 14 is a schematic diagram of a hardware composition structure according to an embodiment of the present invention.
  • An embodiment of the present application provides a method for sequentially submitting data, which is applied to a first network device.
  • the method includes:
  • the first network device When the data stream bearer is transferred from the first network device to the second network device, the first network device sends a first instruction information to the second network device; wherein the first instruction information is used to indicate the first network device
  • the second network device starts to sequentially transfer the transferred data stream on the new bearer.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the first network device keeps the original data radio bearer DRB, and transmits the first part of the unconfirmed data stream to the terminal device. Data, and forward the second part of data from the core network to the second network device.
  • the unacknowledged data may be part of the data without receiving the ACK confirmation information sent by the receiving end; and the second part of the data stream is when the data stream is transferred from the first network device to the second network device, Data still at the first network device.
  • the method may further include: the first network device sends the second part of the data to the second network device until the part of the data is sent.
  • the first instruction information is generated, and then the first instruction information is sent to the second network device.
  • the first indication information may be a blank data packet, or may be a data packet containing a preset identifier.
  • the preset identifier may be set according to an actual situation, for example, it may be Nbit data, and the Nbit data is a preset arrangement, which is not exhaustive in this embodiment.
  • the sending, by the first network device, the first indication information to the second network device includes: the first network device sends the first indication information to the second network device through an Xn interface.
  • FIG. 6 including:
  • Step 601 When the bearer of the data stream is transferred from the first network device to the second network device, the first network device maintains the original data radio bearer DRB, and transmits the unconfirmed data stream to the terminal device. Part of the data, and forward the second part of the data from the core network to the second network device;
  • Step 602 When the second part of the data stream is completely sent to the second network device, send the first indication information to the second network device.
  • the second network device may start to sequentially transfer the transferred data stream on the new bearer, where the sequential transmission may be The second part of the data stream is transmitted first, and then the third part of the data is transmitted from the core network.
  • the second part of the data is arranged before the third part of the data for transmission, so that when the data stream bearer is transferred, no out-of-order occurs.
  • DL downlink
  • Flow Qos data flow
  • the first part of the data stream 1 is kept sent to the terminal device through the original bearer, and the original node continues to
  • the PDCP PDU of the first part of the QoS data stream 1 obtained by the ACK, that is, the first part of the QoS data stream 1 continues to be transmitted; at the same time, the first network device receives the second part of the data from the core network and sends the second network device (also That is, SN) sends the second part of the data until all the remaining PDCP PDUs of the second part of the QoS data stream 1 that have not been acknowledged by ACK are transmitted to the SN.
  • the second network device also That is, SN
  • the primary node sends the first instruction information to the target side through the Xn interface. (SN); Wherein, the instruction indicates that the target side can start to perform data transmission on the newly transferred Qos data flow (Flow) on the new bearer.
  • SN that is, the second network device in this embodiment, receives the second part of the data stream and the first indication information, it transmits the second part of the data first, and then transmits itself. The third part of the data. In this way, it is guaranteed that the transmitted data will not be out of order.
  • the first network device when the data stream bearer is transferred from the first network device to the second network device, the first network device can send the first instruction information to the second network device, and the first instruction can be transmitted through the first instruction.
  • the information causes the second network device to start sequentially transferring the transferred data stream on the new bearer. Therefore, when the data flow transfer occurs, the destination network device side can guarantee the order of transmitting data.
  • An embodiment of the present application provides a method for sequentially submitting data, which is applied to a second network device.
  • the method includes:
  • the first instruction information sent by the first network device is received; wherein the first instruction information is used to instruct the second network device to start
  • the transferred data streams are transmitted in sequence on the new bearer.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the first network device maintains the original data radio bearer DRB and transmits a second portion of data to the second network device.
  • the second network device may also receive the second part of the data stream from the first network device.
  • the first instruction information is generated, and then the first instruction information is sent to the second network device.
  • the first indication information may be a blank data packet, or may be a data packet containing a preset identifier.
  • the preset identifier may be set according to an actual situation, for example, it may be Nbit data, and the Nbit data is a preset arrangement, which is not exhaustive in this embodiment.
  • the first instruction information sent by the first network device is received through an Xn interface.
  • the method further includes: receiving the third portion of data sent by the core network device; that is, when the bearer of the data stream is transferred, the second network device starts to receive the third portion of data from the core network.
  • FIG. 8 including:
  • Step 801 When the data stream bearer is transferred from the first network device to the second network device, receive the second part of the data stream from the first network device, and receive the first part of the data stream from the first network device. Instructions
  • Step 802 Sort the second part of the data stream and the third part of the data for transmission based on the first indication information, where the third part of the data may be received by the second network device from the core network. data.
  • the second network device may start to sequentially transfer the data stream that has been transferred on the new bearer, where the in-sequence transmission may be the The second portion of data is transmitted before the third portion of data.
  • the order of the second part of the data is before the third part of the data. Therefore, when sorting, the second part of the data is arranged before the third part of the data for transmission. This can ensure that the data stream bearer does not appear out of order when transferring.
  • DL downlink
  • Flow Qos data flow
  • the first part of the data stream 1 is kept sent to the terminal device through the original bearer, and the original node continues to
  • the PDCP PDU of the first part of the QoS data stream 1 obtained by the ACK, that is, the first part of the QoS data stream 1 continues to be transmitted; at the same time, the first network device receives the second part of the data from the core network and sends the second network device (also That is, SN) sends the second part of the data until all the remaining PDCP PDUs of the second part of the QoS data stream 1 that have not been acknowledged by ACK are transmitted to the SN.
  • the second network device also That is, SN
  • the primary node sends the first instruction information to the target side through the Xn interface. (SN); Wherein, the instruction indicates that the target side can start to perform data transmission on the newly transferred Qos data flow (Flow) on the new bearer.
  • SN that is, the second network device in this embodiment, receives the second part of the data stream and the first indication information, it transmits the second part of the data first, and then transmits itself. The third part of the data. In this way, it is guaranteed that the transmitted data will not be out of order.
  • the first network device when the data stream bearer is transferred from the first network device to the second network device, the first network device can send the first instruction information to the second network device, and the first instruction can be transmitted through the first instruction.
  • the information causes the second network device to start sequentially transferring the transferred data stream on the new bearer. Therefore, when the data flow transfer occurs, the destination network device side can guarantee the order of transmitting data.
  • An embodiment of the present application provides a method for sequentially submitting data, which is applied to a terminal device.
  • the method includes:
  • the data stream bearer When the data stream bearer is transferred from the first network device to the second network device, the first part of the data stream from the first network device is received.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the first network device keeps the original data radio bearer DRB, and transmits the first part of the unconfirmed data stream to the terminal device. Data, and forward the second part of data from the core network to the second network device.
  • the receiving the first part of the data stream from the first network device includes:
  • the original data radio bearer DRB is maintained with the first network device, and the first part of the unconfirmed data stream transmitted by the first network device is received.
  • DL downlink
  • Flow Qos data flow
  • the first part of the data stream 1 is kept sent to the terminal device through the original bearer, and the original node continues to
  • the PDCP PDU of the first part of the QoS data stream 1 obtained by the ACK, that is, the first part of the QoS data stream 1 continues to be transmitted; at the same time, the first network device receives the second part of the data from the core network and sends the second network device (also That is, SN) sends the second part of the data until all the remaining PDCP PDUs of the second part of the QoS data stream 1 that have not been acknowledged by ACK are transmitted to the SN.
  • the second network device also That is, SN
  • the primary node sends the first instruction information to the target side through the Xn interface. (SN); Wherein, the instruction indicates that the target side can start to perform data transmission on the newly transferred Qos data flow (Flow) on the new bearer.
  • SN that is, the second network device in this embodiment, receives the second part of the data stream and the first indication information, it transmits the second part of the data first, and then transmits itself. The third part of the data. In this way, it is guaranteed that the transmitted data will not be out of order.
  • the first network device when the data stream bearer is transferred from the first network device to the second network device, the first network device can send the first instruction information to the second network device, and the first instruction can be transmitted through the first instruction.
  • the information causes the second network device to start sequentially transferring the transferred data stream on the new bearer. Therefore, when the data flow transfer occurs, the destination network device side can guarantee the order of transmitting data.
  • An embodiment of the present application provides a method for sequentially submitting data, which is applied to a terminal device.
  • the method includes:
  • the terminal device transmits the first part of the data stream and the second instruction information to the first network device; the second instruction information is used for Indicates that the first part of the data transfer in the data stream that was not completed when the transfer occurred is complete.
  • This embodiment is applicable to a scenario in which a bearer transfer of a data stream occurs when a terminal device sends uplink data to a network side.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the transmitting, by the terminal device, the first part of data of the data stream to the first network device includes:
  • the data radio bearer DRB between the first network device and the first network device is maintained, and the unidentified data stream is sent to the first network device.
  • the first part of the PDCP PDU is the first part of the PDCP PDU.
  • the DRB of the original network device continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the UE Continue to transmit the first PDCP PDU of the data stream without ACK acknowledgement to the first network device (for example, MN) through the original bearer.
  • the terminal device transmits a second part of the data stream to the second network device.
  • the terminal device finishes transmitting the first part of the data stream of the data stream to the first network device, it generates second instruction information, and then sends the second instruction information to the first network device.
  • the second indication information may be a blank data packet, or may be a data packet containing a preset identifier.
  • the preset identifier may be set according to an actual situation, for example, it may be Nbit data, and the Nbit data is a preset arrangement, which is not exhaustive in this embodiment.
  • a Qos data flow (Flow) bearer When a Qos data flow (Flow) bearer is transferred from one node to another, such as MN to SN transfer; the DRB of the original node continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the terminal and the pump continues to PDCP without ACK acknowledgement continues to be transmitted. As shown in the figure, the terminal device continues to send the first part of data of data stream 1 to the MN; after the first part of data stream of data stream 1 is transmitted, the second instruction is transmitted to the original node. information;
  • the second indication information may be located in the last data packet of the first part of the data; the second indication information is used to tell the original node that the uncompleted data transmission of the transferred Qos data flow (Flow) has been completed.
  • the primary node will receive the first part of the data stream 1, such as SDAP, SDU, and SDAP Endmarker, which is the second indication information, and pass it to the target node (SN) through the Xn interface; the target node (SN) will The data SDAP and SDU of the primary node are sent to the core network. After receiving the second instruction information, the second part of the data stream 1 received by the local data is sent to the core network.
  • the first part of data of the data stream 1 received by the primary node for example, the SDAP SDU and the SDAP end marker are received as the second indication information; the primary node first passes the received SDAP SDU between the core network through the node The GTP tunnel corresponding to the PDU session is sent to the core network, and then the SDAP end marker is transmitted to the target side through the Xn interface. After the target side receives the end marker indication, it sends the data received by the local side to the core network.
  • An embodiment of the present application provides a method for sequentially submitting data, which is applied to a first network device. As shown in FIG. 10, the method includes:
  • Step 1001 when the data stream bearer is transferred from the first network device to the second network device, receiving the first part of the data stream from the terminal device and the second instruction information from the terminal device; the second instruction Information used to indicate the completion of the first part of the data transfer that was not completed in the data stream when the transfer occurred;
  • Step 1002 sending the first part of the data stream and the second indication information to a second network device, or sending the first part of the data stream to the core network and sending the second indication information To the second network device.
  • This embodiment is applicable to a scenario in which a bearer transfer of a data stream occurs when a terminal device sends uplink data to a network side.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the first part of data in the data stream sent by the receiving terminal device includes:
  • the data radio bearer DRB of the first network device continues to be maintained, and the first part of the data stream that is not acknowledged by the receiving device is PDCP. PDU.
  • the DRB of the original network device continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the UE Continue to transmit the first PDCP PDU of the data stream without ACK acknowledgement to the first network device (for example, MN) through the original bearer.
  • the terminal device transmits a second part of the data stream to the second network device.
  • the terminal device finishes transmitting the first part of the data stream of the data stream to the first network device, it generates second instruction information, and then sends the second instruction information to the first network device.
  • the second indication information may be a blank data packet, or may be a data packet containing a preset identifier.
  • the preset identifier may be set according to an actual situation, for example, it may be Nbit data, and the Nbit data is a preset arrangement, which is not exhaustive in this embodiment.
  • the sending the first part of the data stream and the second indication information to a second network device includes: sending the first part of the data stream and the second indication information through an Xn interface. Sending to the second network device;
  • the sending the first part of the data to the core network and sending the second instruction information to a second network device includes:
  • the method further includes: establishing a GTP tunnel with the second network device on the Xn interface; wherein the GTP tunnel is used to forward data to the second network device.
  • the first network device receives the first part of the data and the second instruction sent by the terminal device based on the original bearer, it sends these information to the second network in real time through the GTP tunnel established by the Xn interface with the second network device. device.
  • the second network device sorts the first part of the data and the second part of the data received by itself, and then submits it to the upper layer.
  • a Qos data flow (Flow) bearer When a Qos data flow (Flow) bearer is transferred from one node to another, such as MN to SN transfer; the DRB of the original node continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the terminal and the pump continues to PDCP without ACK acknowledgement continues to be transmitted. As shown in the figure, the terminal device continues to send the first part of data of data stream 1 to the MN; after the first part of data stream of data stream 1 is transmitted, the second instruction is transmitted to the original node. information;
  • the second indication information may be located in the last data packet of the first part of the data; the second indication information is used to tell the original node that the uncompleted data transmission of the transferred Qos data flow (Flow) has been completed.
  • the primary node will receive the first part of the data stream 1, such as SDAP, SDU, and SDAP Endmarker, which is the second indication information, and pass it to the target node (SN) through the Xn interface; the target node (SN) will The data SDAP and SDU of the primary node are sent to the core network, and after receiving the second instruction information, the second part of the data stream 1 received by the local side is sent to the core network.
  • the first part of data of the data stream 1 received by the primary node for example, the SDAP SDU and the SDAP end marker are received as the second indication information; the primary node first passes the received SDAP SDU between the core network through the node The GTP tunnel corresponding to the PDU session is sent to the core network, and then the SDAP end marker is transmitted to the target side through the Xn interface. After the target side receives the second instruction information, that is, the SDAP end marker indicator, it sends the data received by the local side. To the core network.
  • the second instruction information that is, the SDAP end marker indicator
  • An embodiment of the present application provides a method for sequentially submitting data, which is applied to a second network device. As shown in FIG. 11, the method includes:
  • Step 1101 When the data stream bearer is transferred from the first network device to the second network device, receive the first part of the data stream and the second indication information from the first network device, or receive the first network device.
  • the second instruction information is used to indicate that the first part of the data stream in the data stream that has not been transmitted is completed when the transfer occurs;
  • Step 1102 Based on the second instruction information, after the second network device delivers the first portion of data to the core network, the second network device submits the second portion of data in the data stream to the core network.
  • This embodiment is applicable to a scenario in which a bearer transfer of a data stream occurs when a terminal device sends uplink data to a network side.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the data radio bearer DRB of the first network device continues to be maintained, and the first part of the data stream that is not acknowledged by the receiving device is PDCP. PDU. That is, when the Qos data flow (Flow) is transferred from one network device to another, such as MN to SN transfer, the DRB of the original network device continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the UE Continue to transmit the first PDCP PDU of the data stream without ACK acknowledgement to the first network device (for example, MN) through the original bearer.
  • Flow Qos data flow
  • the terminal device transmits a second part of the data stream to the second network device.
  • the terminal device finishes transmitting the first part of the data stream of the data stream to the first network device, it generates second instruction information, and then sends the second instruction information to the first network device.
  • the second indication information may be a blank data packet, or may be a data packet containing a preset identifier.
  • the preset identifier may be set according to an actual situation, for example, it may be Nbit data, and the Nbit data is a preset arrangement, which is not exhaustive in this embodiment.
  • the receiving the first part of the data stream and the second indication information from the first network device includes: receiving the first part of the data stream and the second indication information from the first network device through the Xn interface;
  • receiving the second instruction information sent by the first network device includes:
  • the method further includes: establishing a GTP tunnel with the first network device on the Xn interface; wherein the GTP tunnel is used to receive data sent by the first network device.
  • the method further includes: judging whether the second indication information is received, and if not received, keeping the second part of the data stream from being sent to the core network; if it is received, controlling sending the first part of the data After reaching the core network, the second part of the received data stream is submitted to the core network. That is, when the first network device receives the first part of the data and the second instruction sent by the terminal device based on the original bearer, it sends these information to the second network in real time through the GTP tunnel established by the Xn interface with the second network device. device. The second network device sorts the first part of the data and the second part of the data it receives, and then submits it to the upper layer.
  • a Qos data flow (Flow) bearer When a Qos data flow (Flow) bearer is transferred from one node to another, such as MN to SN transfer; the DRB of the original node continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the terminal and the pump continues to PDCP without ACK acknowledgement continues to be transmitted. As shown in the figure, the terminal device continues to send the first part of data of data stream 1 to the MN; after the first part of data stream of data stream 1 is transmitted, the second instruction is transmitted to the original node. information;
  • the second indication information may be located in the last data packet of the first part of the data; the second indication information is used to tell the original node that the uncompleted data transmission of the transferred Qos data flow (Flow) has been completed.
  • the primary node will receive the first part of the data stream 1, such as SDAP, SDU, and SDAP Endmarker, which is the second indication information, and pass it to the target node (SN) through the Xn interface; the target node (SN) will The data SDAP and SDU of the primary node are sent to the core network, and after receiving the second instruction information, the second part of the data stream 1 received by the local side is sent to the core network.
  • the first part of data of the data stream 1 received by the primary node for example, the SDAP SDU and the SDAP end marker are received as the second indication information; the primary node first passes the received SDAP SDU between the core network through the node The GTP tunnel corresponding to the PDU session is sent to the core network, and then the SDAP end marker is transmitted to the target side through the Xn interface. After the target side receives the second instruction information, that is, the SDAP end marker indicator, it sends the data received by the local side. To the core network.
  • the second instruction information that is, the SDAP end marker indicator
  • An embodiment of the present application provides a first network device, including:
  • the first communication unit when the data stream bearer is transferred from the first network device to the second network device, the first network device sends the first instruction information to the second network device; wherein the first instruction information is And instructing the second network device to start sequentially transferring the transferred data stream on a new bearer.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the first communication unit maintains the original data radio bearer DRB, and transmits the first part of the data stream of the unconfirmed data stream to the terminal device. To forward the second part of the data from the core network to the second network device.
  • the unacknowledged data may be part of the data without receiving the ACK confirmation information sent by the receiving end; and the second part of the data stream is when the data stream is transferred from the first network device to the second network device, Data still at the first network device.
  • it may further include: a first communication unit that keeps sending a second portion of data to the second network device until this portion of data is sent.
  • the first instruction information is generated, and then the first instruction information is sent to the second network device.
  • the first indication information may be a blank data packet, or may be a data packet containing a preset identifier.
  • the preset identifier may be set according to an actual situation, for example, it may be Nbit data, and the Nbit data is a preset arrangement, which is not exhaustive in this embodiment.
  • the first communication unit sends the first instruction information to the second network device through the Xn interface.
  • DL downlink
  • Flow Qos data flow
  • the first part of the data stream 1 is kept sent to the terminal device through the original bearer, and the original node continues to
  • the PDCP PDU of the first part of the QoS data stream 1 obtained by the ACK, that is, the first part of the QoS data stream 1 continues to be transmitted; at the same time, the first network device receives the second part of the data from the core network and sends the second network device (also That is, SN) sends the second part of the data until all the remaining PDCP PDUs of the second part of the QoS data stream 1 that have not been acknowledged by ACK are transmitted to the SN.
  • the second network device also That is, SN
  • the primary node sends the first instruction information to the target side through the Xn interface. (SN); Wherein, the instruction indicates that the target side can start to perform data transmission on the newly transferred Qos data flow (Flow) on the new bearer.
  • SN that is, the second network device in this embodiment, receives the second part of the data stream and the first indication information, it transmits the second part of the data first, and then transmits itself. The third part of the data. In this way, it is guaranteed that the transmitted data will not be out of order.
  • the first network device when the data stream bearer is transferred from the first network device to the second network device, the first network device can send the first instruction information to the second network device, and the first instruction can be transmitted through the first instruction.
  • the information causes the second network device to start sequentially transferring the transferred data stream on the new bearer. Therefore, when the data flow transfer occurs, the destination network device side can guarantee the order of transmitting data.
  • An embodiment of the present application provides a second network device, as shown in FIG. 12, including:
  • the second communication unit 1201 receives the first instruction information sent by the first network device when the bearer of the data stream is transferred from the first network device to the second network device, wherein the first instruction information is used to indicate the The second network device starts to sequentially transfer the transferred data stream on the new bearer.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the first network device maintains the original data radio bearer DRB and transmits a second portion of data to the second network device.
  • the first instruction information is generated, and then the first instruction information is sent to the second network device.
  • the first indication information may be a blank data packet, or may be a data packet containing a preset identifier.
  • the preset identifier may be set according to an actual situation, for example, it may be Nbit data, and the Nbit data is a preset arrangement, which is not exhaustive in this embodiment.
  • the second communication unit 1201 receives the first instruction information sent by the first network device through an Xn interface.
  • the second communication unit 1201 may start to sequentially transfer the data stream that has been transferred on the new bearer.
  • the second network device further includes:
  • the second processing unit 1202 sorts the first part of the data of the data stream and the second part of the data based on the first instruction information and transmits the data.
  • the second communication unit 1201 receives the third part of data sent by the core network device; that is, when the bearer of the data stream is transferred, the second network device starts to receive the third part of data from the core network.
  • the second network device may start to sequentially transfer the data stream that has been transferred on the new bearer, where the in-sequence transmission may be the The second portion of data is transmitted before the third portion of data.
  • the order of the second part of the data is before the third part of the data. Therefore, when sorting, the second part of the data is arranged before the third part of the data for transmission. This can ensure that the data stream bearer does not appear out of order when transferring.
  • DL downlink
  • Flow Qos data flow
  • the first part of the data stream 1 is kept sent to the terminal device through the original bearer, and the original node continues to
  • the PDCP PDU of the first part of the QoS data stream 1 obtained by the ACK, that is, the first part of the QoS data stream 1 continues to be transmitted; at the same time, the first network device receives the second part of the data from the core network and sends the second network device (also That is, SN) sends the second part of the data until all the remaining PDCP PDUs of the second part of the QoS data stream 1 that have not been acknowledged by ACK are transmitted to the SN.
  • the second network device also That is, SN
  • the primary node sends the first instruction information to the target side through the Xn interface. (SN); Wherein, the instruction indicates that the target side can start to perform data transmission on the newly transferred Qos data flow (Flow) on the new bearer.
  • SN that is, the second network device in this embodiment, receives the second part of the data stream and the first indication information, it transmits the second part of the data first, and then transmits itself. The third part of the data. In this way, it is guaranteed that the transmitted data will not be out of order.
  • the first network device when the data stream bearer is transferred from the first network device to the second network device, the first network device can send the first instruction information to the second network device, and the first instruction can be transmitted through the first instruction.
  • the information causes the second network device to start sequentially transferring the transferred data stream on the new bearer. Therefore, when the data flow transfer occurs, the destination network device side can guarantee the order of transmitting data.
  • An embodiment of the present application provides a terminal device, including:
  • the sixth communication unit receives the first part of the data stream from the first network device when the data stream bearer is transferred from the first network device to the second network device.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the first network device keeps the original data radio bearer DRB, and transmits the first part of the unconfirmed data stream to the terminal device. Data, and forward the second part of data from the core network to the second network device.
  • the sixth communication unit maintains the original data radio bearer DRB with the first network device, and receives the first part of data of the unconfirmed data stream transmitted by the first network device.
  • DL downlink
  • Flow Qos data flow
  • the first part of the data stream 1 is kept sent to the terminal device through the original bearer, and the original node continues to
  • the PDCP PDU of the first part of the QoS data stream 1 obtained by the ACK, that is, the first part of the QoS data stream 1 continues to be transmitted; at the same time, the first network device receives the second part of the data from the core network and sends the second network device (also That is, SN) sends the second part of the data until all the remaining PDCP PDUs of the second part of the QoS data stream 1 that have not been acknowledged by ACK are transmitted to the SN.
  • the second network device also That is, SN
  • the primary node sends the first instruction information to the target side through the Xn interface. (SN); Wherein, the instruction indicates that the target side can start to perform data transmission on the newly transferred Qos data flow (Flow) on the new bearer.
  • SN that is, the second network device in this embodiment, receives the second part of the data stream and the first indication information, it transmits the second part of the data first, and then transmits itself. The third part of the data. In this way, it is guaranteed that the transmitted data will not be out of order.
  • the first network device when the data stream bearer is transferred from the first network device to the second network device, the first network device can send the first instruction information to the second network device, and the first instruction can be transmitted through the first instruction.
  • the information causes the second network device to start sequentially transferring the transferred data stream on the new bearer. Therefore, when the data flow transfer occurs, the destination network device side can guarantee the order of transmitting data.
  • An embodiment of the present application provides a terminal device, including:
  • a third communication unit when the data stream bearer is transferred from the first network device to the second network device, the terminal device transmits the first part of the data stream and the second indication information to the first network device; Indication information is used to indicate that the first part of the data stream in the data stream that has not been completed when the transfer occurs is completed.
  • This embodiment is applicable to a scenario in which a bearer transfer of a data stream occurs when a terminal device sends uplink data to a network side.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the third communication unit when the data stream bearer is transferred from the first network device to the second network device, maintains a data radio bearer DRB with the first network device, and sends an unacknowledged to the first network device PDCP PDU for the first part of the data stream.
  • the DRB of the original network device continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the UE Continue to transmit the first PDCP PDU of the data stream without ACK acknowledgement to the first network device (for example, MN) through the original bearer.
  • the third communication unit transmits the second part of the data stream to the second network device.
  • the third communication unit generates second instruction information when the first part of the data stream of the data stream is transmitted to the first network device, and then sends the second instruction information to the first network device.
  • the second indication information may be a blank data packet, or may be a data packet containing a preset identifier.
  • the preset identifier may be set according to an actual situation, for example, it may be Nbit data, and the Nbit data is a preset arrangement, which is not exhaustive in this embodiment.
  • a Qos data flow (Flow) bearer When a Qos data flow (Flow) bearer is transferred from one node to another, such as MN to SN transfer; the DRB of the original node continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the terminal and the pump continues to PDCP without ACK acknowledgement continues to be transmitted. As shown in the figure, the terminal device continues to send the first part of data of data stream 1 to the MN; after the first part of data stream of data stream 1 is transmitted, the second instruction is transmitted to the original node. information;
  • the second indication information may be located in the last data packet of the first part of the data; the second indication information is used to tell the original node that the uncompleted data transmission of the transferred Qos data flow (Flow) has been completed.
  • the primary node will receive the first part of the data stream 1, such as SDAP, SDU, and SDAP Endmarker, which is the second indication information, and pass it to the target node (SN) through the Xn interface; the target node (SN) will The data SDAP and SDU of the primary node are sent to the core network. After receiving the second instruction information, the second part of the data stream 1 received by the local data is sent to the core network.
  • An embodiment of the present application provides a first network device, including:
  • a fourth communication unit when the data stream bearer is transferred from the first network device to the second network device, receiving the first part of the data stream sent by the terminal device and the second instruction information sent by the terminal device; Two instructions, which are used to indicate that the first part of the data stream that has not been transmitted is completed when the transfer occurs; sending the first part of the data stream and the second instruction information to the second network device, or The first part of the data stream is sent to a core network and the second indication information is sent to a second network device.
  • This embodiment is applicable to a scenario in which a bearer transfer of a data stream occurs when a terminal device sends uplink data to a network side.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the fourth communication unit when the data stream bearer is transferred from the first network device to the second network device, the data radio bearer DRB continues to be maintained, and the PDCP PDU of the first part of the data stream that is not acknowledged from the terminal device is received.
  • the DRB of the original network device continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the UE Continue to transmit the first PDCP PDU of the data stream without ACK acknowledgement to the first network device (for example, MN) through the original bearer.
  • the terminal device transmits a second part of the data stream to the second network device.
  • the terminal device finishes transmitting the first part of the data stream of the data stream to the first network device, it generates second instruction information, and then sends the second instruction information to the first network device.
  • the second indication information may be a blank data packet, or may be a data packet containing a preset identifier.
  • the preset identifier may be set according to an actual situation, for example, it may be Nbit data, and the Nbit data is a preset arrangement, which is not exhaustive in this embodiment.
  • the fourth communication unit sends the first part of the data stream and the second indication information to the second network device through the Xn interface.
  • the fourth communication unit sends the first part of the data stream to the core network through a GTP tunnel with the core network; and sends the second instruction information to the second network device through the Xn interface.
  • a fourth communication unit establishes a GTP tunnel with the second network device on the Xn interface; wherein the GTP tunnel is used to forward data to the second network device.
  • the first network device when the first network device receives the first part of the data and the second instruction sent by the terminal device based on the original bearer, it sends these information to the second network in real time through the GTP tunnel established by the Xn interface with the second network device. device.
  • the second network device sorts the first part of the data and the second part of the data it receives, and then submits it to the upper layer.
  • a Qos data flow (Flow) bearer When a Qos data flow (Flow) bearer is transferred from one node to another, such as MN to SN transfer; the DRB of the original node continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the terminal and the pump continues to PDCP without ACK acknowledgement continues to be transmitted. As shown in the figure, the terminal device continues to send the first part of data of data stream 1 to the MN; after the first part of data stream of data stream 1 is transmitted, the second instruction is transmitted to the original node. information;
  • the second indication information may be located in the last data packet of the first part of the data; the second indication information is used to tell the original node that the uncompleted data transmission of the transferred Qos data flow (Flow) has been completed.
  • the primary node will receive the first part of the data stream 1, such as SDAP, SDU, and SDAP Endmarker, which is the second indication information, and pass it to the target node (SN) through the Xn interface; the target node (SN) will The data SDAP and SDU of the primary node are sent to the core network, and after receiving the second instruction information, the second part of the data stream 1 received by the local side is sent to the core network.
  • the first part of data of the data stream 1 received by the primary node for example, the SDAP SDU and the SDAP end marker are received as the second indication information; the primary node first passes the received SDAP SDU between the core network through the node The GTP tunnel corresponding to the PDU session is sent to the core network, and then the SDAP end marker is transmitted to the target side through the Xn interface. After the target side receives the second instruction information, that is, the SDAP end marker indicator, it sends the data received by the local side. To the core network.
  • the second instruction information that is, the SDAP end marker indicator
  • An embodiment of the present application provides a second network device, as shown in FIG. 13, including:
  • the fifth communication unit 1301 when the data stream bearer is transferred from the first network device to the second network device, receives the first part of the data stream and the second instruction information sent by the first network device, or receives the first network Second instruction information sent by the device; the second instruction information is used to indicate that the first part of the data stream that is not transmitted in the data stream is completed when the transfer occurs;
  • the fifth processing unit 1302 after the first part of the data is submitted to the core network based on the second instruction information, submits the second part of the data stream to the core network.
  • This embodiment is applicable to a scenario in which a bearer transfer of a data stream occurs when a terminal device sends uplink data to a network side.
  • the data flow in this embodiment may be understood as a QoS data flow; the first network device may be an original node, and the second network device may be a destination node.
  • the first network device and the second network device may be a primary node (MN) and a secondary node (SN) in a dual connection (DC), of course, and may also be other nodes in a DC scenario, but it is not performed here. To repeat.
  • the data stream in this embodiment may be a Qos data stream.
  • the data radio bearer DRB of the first network device continues to be maintained, and the first part of the data stream that is not acknowledged by the receiving device is PDCP. PDU. That is, when the Qos data flow (Flow) is transferred from one network device to another, such as MN to SN transfer, the DRB of the original network device continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the UE Continue to transmit the first PDCP PDU of the data stream without ACK acknowledgement to the first network device (for example, MN) through the original bearer.
  • Flow Qos data flow
  • the terminal device transmits a second part of the data stream to the second network device.
  • the terminal device finishes transmitting the first part of the data stream of the data stream to the first network device, it generates second instruction information, and then sends the second instruction information to the first network device.
  • the second indication information may be a blank data packet, or may be a data packet containing a preset identifier.
  • the preset identifier may be set according to an actual situation, for example, it may be Nbit data, and the Nbit data is a preset arrangement, which is not exhaustive in this embodiment.
  • the fifth communication unit 1301 receives the first part of data of the data stream and the second instruction information sent by the first network device through the Xn interface.
  • the fifth communication unit 1301 receives the second indication information of the data stream sent by the first network device through the Xn interface.
  • the fifth communication unit 1301 establishes a GTP tunnel with the first network device on the Xn interface, where the GTP tunnel is used to receive data sent by the first network device.
  • the fifth processing unit 1302 determines whether the second instruction information is received, and if not received, it keeps not sending the second part of the data stream to the core network; if it is received, it controls to send the first part of the data After reaching the core network, the second part of the received data stream is submitted to the core network. That is, when the first network device receives the first part of the data and the second instruction sent by the terminal device based on the original bearer, it sends these information to the second network in real time through the GTP tunnel established by the Xn interface with the second network device. device. The second network device sorts the first part of the data and the second part of the data it receives, and then submits it to the upper layer.
  • a Qos data flow (Flow) bearer When a Qos data flow (Flow) bearer is transferred from one node to another, such as MN to SN transfer; the DRB of the original node continues to be maintained after the bearer is changed, and the protocol stack corresponding to the original node in the terminal and the pump continues to PDCP without ACK acknowledgement continues to be transmitted. As shown in the figure, the terminal device continues to send the first part of data of data stream 1 to the MN; after the first part of data stream of data stream 1 is transmitted, the second instruction is transmitted to the original node. information;
  • the second indication information may be located in the last data packet of the first part of the data; the second indication information is used to tell the original node that the uncompleted data transmission of the transferred Qos data flow (Flow) has been completed.
  • the primary node will receive the first part of the data stream 1, such as SDAP, SDU, and SDAP Endmarker, which is the second indication information, and pass it to the target node (SN) through the Xn interface; the target node (SN) will The data SDAP and SDU of the primary node are sent to the core network, and after receiving the second instruction information, the second part of the data stream 1 received by the local side is sent to the core network.
  • the first part of data of the data stream 1 received by the primary node for example, the SDAP SDU and the SDAP end marker are received as the second indication information; the primary node first passes the received SDAP SDU between the core network through the node The GTP tunnel corresponding to the PDU session is sent to the core network, and then the SDAP end marker is transmitted to the target side through the Xn interface. After the target side receives the second instruction information, that is, the SDAP end marker indicator, it sends the data received by the local side. To the core network.
  • the second instruction information that is, the SDAP end marker indicator
  • An embodiment of the present invention further provides a hardware component architecture of a terminal device or a network device, as shown in FIG. 14, including: at least one processor 1401, a memory 1402, and at least one network interface 1403.
  • the various components are coupled together via a bus system 1404. It can be understood that the bus system 1404 is used to implement connection and communication between these components.
  • the bus system 1404 includes a power bus, a control bus, and a status signal bus in addition to the data bus. However, for the sake of clarity, various buses are labeled as the bus system 1404 in FIG. 14.
  • the memory 1402 in the embodiment of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories.
  • the memory 1402 stores the following elements, executable modules or data structures, or their subsets, or their extended sets:
  • the processor 1401 is configured to be capable of processing the method steps of any one of the foregoing Embodiments 1-5, and details are not described herein again.
  • a computer storage medium provided by an embodiment of the present invention, wherein the computer storage medium stores computer-executable instructions, and when the computer-executable instructions are executed, the method steps of any one of the foregoing embodiments 1-5 are performed.
  • the foregoing device is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.
  • the computer software product is stored in a storage medium and includes several instructions for A computer device (which may be a personal computer, a server, or a network device) is caused to execute all or part of the methods described in the embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read Only Memory), a magnetic disk, or an optical disk, and other media that can store program codes.
  • ROM Read Only Memory
  • magnetic disk or an optical disk, and other media that can store program codes.

Landscapes

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

Abstract

本发明公开了数据按序递交的方法、网络设备、终端设备及计算机存储介质；所述方法包括：当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。

Description

数据按序递交的方法、网络设备及终端设备 技术领域
本发明涉及信息处理技术领域，尤其涉及一种数据按序递交的方法、网络设备、终端设备及计算机存储介质。
背景技术
5G的主要应用场景为：增强移动超宽带(eMBB)、低时延高可靠通信(URLLC)、大规模机器类通信(mMTC)。在NR早期部署时，完整的NR覆盖很难获取，所以典型的网络覆盖是广域的LTE覆盖和NR的孤岛覆盖模式。而且大量的LTE部署在6GHz以下，可用于5G的6GHz以下频谱很少。所以NR必须研究6GHz以上的频谱应用，同时为了保护移动运营商前期在LTE投资，提出了LTE和NR之间tight interworking的工作模式。NR也可以独立部署。
为了能够尽快实现5G网络部署和商业应用，3GPP在2017年12底前首先完成第一个5G版本，即EN-DC(LTE-NR Dual Connectivity)。这里LTE作为主节点MN(Master Node)，NR作为辅助节点SN(Secondary Node)，网络部署和组网架构如图1-3所示。在双连接(DC)中，包括EN-DC，NE-DC，5GC-EN-DC，NR DC。EN-DC中，LTE节点作为MN节点，NR节点作为SN节点，连接EPC核心网。NE-DC中NR作为MN节点，eLTE作为SN节点，连接5GC核心网。5GC-EN-DC中，eLTE作为MN节点，NR作为SN节点，连接5GC核心网。NR DC中，NR作为MN节点，NR作为SN节点，连接5GC核心网。DC模式下的承载类型如图4所示，在LTE DC中，用户面的承载类型包括主小区群(MCG)承载(bearer)，辅助小区群(SCG)承载(bearer)，MCG分叉(Split)bearer。为了最小化MCG split bearer和SCG split bearer之间的变更，提出了承载协调(bearer harmonization)的概念，即MCG split bearer和SCG split bearer统一为分叉承载(Split bearer)。
在5G NR中，引入了新的协议层业务数据适应协议(SDAP，Service Data Adaptation Protocol)，该协议层用于将来自核心网的Qos数据流(Flow)的数据映射到不同的DRB上去。而eLTE就是在LTE中支持LTE基站接入5G核心网，所以eLTE的协议栈中也包含SDAP协议。如图5所示，对于NE-DC，5GC-EN-DC，NR DC中，每个MN、SN节点都会用到SDAP协议。因此，在现有技术中的承载变更过程中，存在乱序递交的问题。
发明内容
为解决上述技术问题，本发明实施例提供了一种数据按序递交的方法、网络设备、终端设备及计算机存储介质。
本发明实施例提供了一种数据按序递交的方法，应用于第一网络设备，所述方法包括：
当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
本发明实施例提供了一种数据按序递交的方法，应用于第二网络设备，所述方法包括：
当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
本发明实施例提供了一种数据按序递交的方法，应用于终端设备，所述方法包括：
当数据流的承载从第一网络设备转移到第二网络设备时，所述终端设备向第一网络设备传输数据流的第一部分数据，以及第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成。
本发明实施例提供了一种数据按序递交的方法，应用于第一网络设备，所述方法包括：
当数据流的承载从第一网络设备转移到第二网络设备时，接收终端设备发来的数据流的第一部分数据，以及终端设备发来的第二指示信息；所述第二指示信息，用于指示 发生转移时数据流中未传输完成的第一部分数据传输完成；
将所述数据流的第一部分数据以及所述第二指示信息发送至第二网络设备，或者，将所述数据流的第一部分数据发送至核心网以及将所述第二指示信息发送至第二网络设备。
本发明实施例提供了一种数据按序递交的方法，应用于第二网络设备，所述方法包括：
当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的数据流的第一部分数据以及第二指示信息，或者，接收第一网络设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；
基于所述第二指示信息，所述第二网络设备将所述第一部分数据递交至核心网之后，将数据流的第二部分数据递交至核心网。
本发明实施例提供了一种第一网络设备，包括：
第一通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
本发明实施例提供了一种第二网络设备，包括：
第二通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
本发明实施例提供了一种终端设备，包括：
第三通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，向第一网络设备传输数据流的第一部分数据，以及第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成。
本发明实施例提供了一种第一网络设备，包括：
第四通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，接收终端设备发来的数据流的第一部分数据，以及终端设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；将所述数据流的第一部分数据以及所述第二指示信息发送至第二网络设备，或者，将所述数据流的第一部分数据发送至核心网以及将所述第二指示信息发送至第二网络设备。
本发明实施例提供了一种第二网络设备，包括：
第五通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的数据流的第一部分数据以及第二指示信息，或者，接收第一网络设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；
第五处理单元，基于所述第二指示信息，将所述第一部分数据递交至核心网之后，将数据流的第二部分数据递交至核心网。
本发明实施例提供了一种网络设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行前述方法的步骤。
本发明实施例提供了一种终端设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行所述方法的步骤。
本发明实施例提供了一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实现前述方法步骤。
通过采用本发明实施例的技术方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息，通过所述第一指示信息使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
附图说明
图1-3为DC的网络部署和组网架构示意图；
图4为DC模式下的承载类型示意图；
图5为现有技术中出现承载转移是的乱序递交的示意图；
图6为本发明实施例数据按序递交的方法流程示意图一；
图7为本发明实施例下行数据处理场景示意图；
图8为本发明实施例数据按序递交的方法流程示意图二；
图9为本发明实施例上行数据处理场景示意图；
图10为本发明实施例数据按序递交的方法流程示意图三；
图11为本发明实施例数据按序递交的方法流程示意图四；
图12为本发明实施例网络设备组成结构示意图一；
图13为本发明实施例网络设备组成结构示意图二；
图14为本发明实施例的一种硬件组成结构示意图。
具体实施方式
为了能够更加详尽地了解本发明实施例的特点与技术内容，下面结合附图对本发明实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本发明实施例。
实施例一、
本申请实施例提供了一种数据按序递交的方法，应用于第一网络设备，所述方法包括：
当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
另外，当所述数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备保持原数据无线承载DRB，向所述终端设备传输未得到确认的数据流的第一部分数据，向第二网络设备转发来自核心网的第二部分数据。
其中，未得到确认可以为未得到接收端发来的ACK确认信息的部分数据；并且，所述数据流的第二部分数据为当数据流由第一网络设备转移到第二网络设备的同时，仍然在第一网络设备处的数据。
此时，还可以包括：第一网络设备向第二网络设备发送第二部分数据，直至此部分数据发完为止。
当数据流的第二部分数据完成发送至第二网络设备的时候，生成第一指示信息，然后向第二网络设备发送第一指示信息。
其中，所述第一指示信息可以为空白数据包、或者、可以为包含有预设标识的数据包。其中，预设标识可以为根据实际情况设置的，比如，可以为Nbit的数据，该N bit的数据为预设排列，本实施例中不对其进行穷举。
进一步地，所述第一网络设备向第二网络设备发送第一指示信息，包括：所述第一网络设备通过Xn接口，向第二网络设备发送第一指示信息。
具体的，可以参见图6，包括：
步骤601：当所述数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备保持原数据无线承载DRB，向所述终端设备传输未得到确认的数据流的第一部分数据，向第二网络设备转发来自核心网的第二部分数据；
步骤602：当数据流的第二部分数据完成发送至第二网络设备的时候，向第二网络设备发送第一指示信息。
相应的，当第二网络设备接收到所述第一指示信息时，所述第二网络设备就可以开始在新的承载上对发生转移的数据流进行按序传输；其中，按序传输可以为先传输数据流的第二部分数据，然后传输自核心网的第三部分数据。当进行排序的时候，将第二部分数据排列在第三部分数据之前进行传输，从而能够保证数据流的承载发生转移的时候不会出现乱序。
下面结合图7对上述场景进行说明：对于下行(DL)数据，一个Qos数据流(Flow)1从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持(可以为将接入和移动管理功能(AMF)发来的QoS数据流1的第一部分数据)，数据流1的第一部分数据通过原承载保持向终端设备发送，原侧节点继续将未 得到ACK确认的QoS数据流1的第一部分PDCP PDU，也就是QoS数据流1的第一部分数据继续传输；同时，第一网络设备接收来自核心网的第二部分数据，向第二网络设备(也就是SN)发送第二部分数据，直至剩余的所有未得到ACK确认的QoS数据流1的第二部分PDCP PDU向SN传输完毕，原侧节点(MN)通过Xn接口发送第一指示信息给目标侧(SN)；其中，该指示指示目标侧可以开始在新的承载上开始对上述发生转移的Qos数据流(Flow)进行数据传输。还需要指出的是，当SN，也就是本实施例中的第二网络设备，接收到数据流的第二部分数据以及第一指示信息之后，将第二部分数据先进行传输、然后再传输自身的第三部分数据。如此，就保证了传输的数据不会乱序。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息，通过所述第一指示信息使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例二、
本申请实施例提供了一种数据按序递交的方法，应用于第二网络设备，所述方法包括：
当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
另外，当所述数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备保持原数据无线承载DRB，向第二网络设备传输第二部分数据。相应的，所述第二网络设备，还会接收所述第一网络设备发来的数据流的第二部分数据。
当数据流的第而部分数据完成发送至第二网络设备的时候，生成第一指示信息，然后向第二网络设备发送第一指示信息。
其中，所述第一指示信息可以为空白数据包、或者、可以为包含有预设标识的数据包。其中，预设标识可以为根据实际情况设置的，比如，可以为Nbit的数据，该N bit的数据为预设排列，本实施例中不对其进行穷举。
进一步地，通过Xn接口接收所述第一网络设备发送的第一指示信息。
所述方法还包括：接收所述核心网设备发送的第三部分数据；也就是说，当数据流的承载转移的时候，第二网络设备开始从核心网接收第三部分数据。
具体的，可以参见图8，包括：
步骤801：当数据流的承载从第一网络设备转移到第二网络设备时，接收所述第一网络设备发来的数据流的第二部分数据、以及接收第一网络设备发来的第一指示信息；
步骤802：基于所述第一指示信息，将所述数据流的第二部分数据、以及第三部分数据排序后进行传输；其中，第三部分数据可以为第二网络设备从核心网接收到的数据。
当第二网络设备接收到所述第一指示信息时，所述第二网络设备就可以开始在新的承载上对发生转移的数据流进行按序传输；其中，按序传输可以为所述将所述第二部分数据排在第三部分数据之前进行传输。
由于第二部分数据发生在数据流转移的时候，因此第二部分数据的顺序在第三部分数据之前，所以，当进行排序的时候，将第二部分数据排列在第三部分数据之前进行传输，从而能够保证数据流的承载发生转移的时候不会出现乱序。
下面结合图7对上述场景进行说明：对于下行(DL)数据，一个Qos数据流(Flow)1从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持(可以为将接入和移动管理功能(AMF)发来的QoS数据流1的第一部分数据)，数据流1的第一部分数据通过原承载保持向终端设备发送，原侧节点继续将未得到ACK确认的QoS数据流1的第一部分PDCP PDU，也就是QoS数据流1的第一部分数据继续传输；同时，第一网络设备接收来自核心网的第二部分数据，向第二网络设备(也就是SN)发送第二部分数据，直至剩余的所有未得到ACK确认的QoS数据流 1的第二部分PDCP PDU向SN传输完毕，原侧节点(MN)通过Xn接口发送第一指示信息给目标侧(SN)；其中，该指示指示目标侧可以开始在新的承载上开始对上述发生转移的Qos数据流(Flow)进行数据传输。还需要指出的是，当SN，也就是本实施例中的第二网络设备，接收到数据流的第二部分数据以及第一指示信息之后，将第二部分数据先进行传输、然后再传输自身的第三部分数据。如此，就保证了传输的数据不会乱序。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息，通过所述第一指示信息使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例三、
本申请实施例提供了一种数据按序递交的方法，应用于终端设备，所述方法包括：
当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的数据流的第一部分数据。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
另外，当所述数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备保持原数据无线承载DRB，向所述终端设备传输未得到确认的数据流的第一部分数据，向第二网络设备转发来自核心网的第二部分数据。
所述接收第一网络设备发来的数据流的第一部分数据，包括：
与所述第一网络设备保持原数据无线承载DRB，接收所述第一网络设备传输的未得到确认的数据流的第一部分数据。
下面结合图7对上述场景进行说明：对于下行(DL)数据，一个Qos数据流(Flow)1从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持(可以为将接入和移动管理功能(AMF)发来的QoS数据流1的第一部分数据)，数据流1的第一部分数据通过原承载保持向终端设备发送，原侧节点继续将未得到ACK确认的QoS数据流1的第一部分PDCP PDU，也就是QoS数据流1的第一部分数据继续传输；同时，第一网络设备接收来自核心网的第二部分数据，向第二网络设备(也就是SN)发送第二部分数据，直至剩余的所有未得到ACK确认的QoS数据流1的第二部分PDCP PDU向SN传输完毕，原侧节点(MN)通过Xn接口发送第一指示信息给目标侧(SN)；其中，该指示指示目标侧可以开始在新的承载上开始对上述发生转移的Qos数据流(Flow)进行数据传输。还需要指出的是，当SN，也就是本实施例中的第二网络设备，接收到数据流的第二部分数据以及第一指示信息之后，将第二部分数据先进行传输、然后再传输自身的第三部分数据。如此，就保证了传输的数据不会乱序。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息，通过所述第一指示信息使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例四、
本申请实施例提供了一种数据按序递交的方法，应用于终端设备，所述方法包括：
当数据流的承载从第一网络设备转移到第二网络设备时，所述终端设备向第一网络设备传输数据流的第一部分数据，以及第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成。
本实施例适用于终端设备向网络侧发送上行数据时，发生数据流的承载转移的场景中。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
所述终端设备向第一网络设备传输数据流的第一部分数据，包括：
当数据流的承载从第一网络设备转移到第二网络设备时，保持与所述第一网络设备之间的数据无线承载DRB，向所述第一网络设备发送未得到确认的所述数据流的第一部分PDCP PDU。
也就是说，当Qos数据流(Flow)从一个网络设备转移到另一个网络设备时，例如MN到SN转移，原侧网络设备的DRB在承载变更后继续保持，UE内原侧节点对应的协议栈继续将未得到ACK确认的数据流的第一部分PDCP PDU继续通过原承载向第一网络设备(比如，MN)传输。
另外，在执行前述方案的同时，所述终端设备向第二网络设备传输数据流的第二部分数据。
所述终端设备向第一网络设备传输数据流的第一部分数据完成的时候，生成第二指示信息，然后向第一网络设备发送第二指示信息。
其中，所述第二指示信息可以为空白数据包、或者、可以为包含有预设标识的数据包。其中，预设标识可以为根据实际情况设置的，比如，可以为Nbit的数据，该N bit的数据为预设排列，本实施例中不对其进行穷举。
下面结合图9对上述场景进行说明：对于UL，首先在建立SN节点时或者承载变更时，在MN以及SN之间的Xn接口上建立GTP隧道用于传输原侧收到的数据转发。
当一个Qos数据流(Flow)的承载从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持，终端和水泵内原侧节点对应的协议栈继续将未得到ACK确认的PDCP PDU继续传输，如图中所示，终端设备继续将数据流1的第一部分数据发送至MN；直至数据流1的第一部分数据传输完成后，向原侧节点传输第二指示信息；
其中，所述第二指示信息可以位于第一部分数据的最后一个数据包内；该第二指示信息用于告诉原侧节点该转移的Qos数据流(Flow)的未完成的数据传输已经完成。
原侧节点将接收到的数据流1的第一部分数据，比如SDAP SDU，以及SDAP end marker即第二指示信息，通过Xn接口传递给目标侧节点(SN)；目标侧节点(SN)首先将来自原侧节点的数据SDAP SDU发送给核心网，收到第二指示信息后，将本侧数据收到的数据流1的第二部分数据发给核心网。
原侧节点接收到的数据流1的第一部分数据，比如，接收到SDAP SDU以及SDAP end marker即第二指示信息；所述原侧节点首先将接收到的SDAP SDU通过本节点于核心网之间的该PDU session对应的GTP隧道发送给核心网，然后将SDAP end marker通过Xn接口传递给目标侧，目标侧收到end marker指示后，再将本侧收到的数据发给核心网。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，向第二网络设备发送指示信息，使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例五、
本申请实施例提供了一种数据按序递交的方法，应用于第一网络设备，如图10所示，所述方法包括：
步骤1001：当数据流的承载从第一网络设备转移到第二网络设备时，接收终端设备发来的数据流的第一部分数据，以及终端设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；
步骤1002：将所述数据流的第一部分数据以及所述第二指示信息发送至第二网络设备，或者，将所述数据流的第一部分数据发送至核心网以及将所述第二指示信息发送至第二网络设备。
本实施例适用于终端设备向网络侧发送上行数据时，发生数据流的承载转移的场景中。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
所述接收终端设备发来的数据流的第一部分数据，包括：
当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备的数据无线承载DRB继续保持，接收终端设备发来的未得到确认的所述数据流的第一部分PDCP PDU。
也就是说，当Qos数据流(Flow)从一个网络设备转移到另一个网络设备时，例如MN到SN转移，原侧网络设备的DRB在承载变更后继续保持，UE内原侧节点对应的协议栈继续将未得到ACK确认的数据流的第一部分PDCP PDU继续通过原承载向第一网络设备(比如，MN)传输。
另外，在执行前述方案的同时，所述终端设备向第二网络设备传输数据流的第二部分数据。
所述终端设备向第一网络设备传输数据流的第一部分数据完成的时候，生成第二指示信息，然后向第一网络设备发送第二指示信息。
其中，所述第二指示信息可以为空白数据包、或者、可以为包含有预设标识的数据包。其中，预设标识可以为根据实际情况设置的，比如，可以为Nbit的数据，该N bit的数据为预设排列，本实施例中不对其进行穷举。
所述将所述数据流的第一部分数据、以及所述第二指示信息，发送至第二网络设备，包括：将所述数据流的第一部分数据、以及所述第二指示信息，通过Xn接口发送至第二网络设备；
或者，
所述将所述数据流的第一部分数据发送至核心网以及将所述第二指示信息发送至第二网络设备，包括：
将所述数据流的第一部分数据通过与核心网之间的GTP隧道发送至核心网；
将所述第二指示信息通过Xn接口发送至第二网络设备。
所述方法还包括：在Xn接口建立与第二网络设备之间的GTP隧道；其中，所述GTP隧道用于向第二网络设备进行数据转发。
即第一网络设备在接收到终端设备基于原承载发来的第一部分数据以及第二指示的时候，实时的将这些信息通过与第二网络设备之间Xn接口建立的GTP隧道发送至第二网络设备。使得第二网络设备对第一部分数据以及本身接收到的第二部分数据进行排序之后向上层提交。
下面结合图9对上述场景进行说明：对于UL，首先在建立SN节点时或者承载变更时，在MN以及SN之间的Xn接口上建立GTP隧道用于传输原侧收到的数据转发。
当一个Qos数据流(Flow)的承载从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持，终端和水泵内原侧节点对应的协议栈继续将未得到ACK确认的PDCP PDU继续传输，如图中所示，终端设备继续将数据流1的第一部分数据发送至MN；直至数据流1的第一部分数据传输完成后，向原侧节点传输第二指示信息；
其中，所述第二指示信息可以位于第一部分数据的最后一个数据包内；该第二指示信息用于告诉原侧节点该转移的Qos数据流(Flow)的未完成的数据传输已经完成。
原侧节点将接收到的数据流1的第一部分数据，比如SDAP SDU，以及SDAP end marker即第二指示信息，通过Xn接口传递给目标侧节点(SN)；目标侧节点(SN)首先将来自原侧节点的数据SDAP SDU发送给核心网，收到第二指示信息后，将本侧收到的数据流1的第二部分数据发给核心网。
或者，
原侧节点接收到的数据流1的第一部分数据，比如，接收到SDAP SDU以及SDAP end marker即第二指示信息；所述原侧节点首先将接收到的SDAP SDU通过本节点于核心网之间的与PDU session对应的GTP隧道发送给核心网，然后将SDAP end marker通过Xn接口传递给目标侧，目标侧收到第二指示信息即SDAP end marker指示后，再将本侧收到的数据发给核心网。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，向第二网络设备发送指示信息，使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例六、
本申请实施例提供了一种数据按序递交的方法，应用于第二网络设备，如图11所示，所述方法包括：
步骤1101：当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的数据流的第一部分数据以及第二指示信息，或者，接收第一网络设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；
步骤1102：基于所述第二指示信息，所述第二网络设备将所述第一部分数据递交至核心网之后，将数据流的第二部分数据递交至核心网。
本实施例适用于终端设备向网络侧发送上行数据时，发生数据流的承载转移的场景中。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备的数据无线承载DRB继续保持，接收终端设备发来的未得到确认的所述数据流的第一部分PDCP PDU。也就是说，当Qos数据流(Flow)从一个网络设备转移到另一个网络设备时，例如MN到SN转移，原侧网络设备的DRB在承载变更后继续保持，UE内原侧节点对应的协议栈继续将未得到ACK确认的数据流的第一部分PDCP PDU继续通过原承载向第一网络设备(比如，MN)传输。
另外，在执行前述方案的同时，所述终端设备向第二网络设备传输数据流的第二部分数据。
所述终端设备向第一网络设备传输数据流的第一部分数据完成的时候，生成第二指示信息，然后向第一网络设备发送第二指示信息。
其中，所述第二指示信息可以为空白数据包、或者、可以为包含有预设标识的数据包。其中，预设标识可以为根据实际情况设置的，比如，可以为Nbit的数据，该N bit的数据为预设排列，本实施例中不对其进行穷举。
所述接收第一网络设备发来的数据流的第一部分数据、以及第二指示信息，包括：通过Xn接口接收第一网络设备发来的数据流的第一部分数据、以及第二指示信息；
或者所述接收第一网络设备发来的第二指示信息，包括：
通过Xn接口接收第一网络设备发来的数据流的第二指示信息。
所述方法还包括：在Xn接口建立与第一网络设备之间的GTP隧道；其中，所述GTP隧道用于接收第一网络设备发送的数据。
所述方法还包括：判断是否接收到第二指示信息，若未接收到，则保持不向核心网发送所述数据流的第二部分数据；若接收到，则控制将所述第一部分数据发送至核心网之后，将接收到的数据流的第二部分数据递交至核心网。即第一网络设备在接收到终端设备基于原承载发来的第一部分数据以及第二指示的时候，实时的将这些信息通过与第二网络设备之间Xn接口建立的GTP隧道发送至第二网络设备。第二网络设备对第一部分数据以及本身接收到的第二部分数据进行排序之后向上层提交。
下面结合图9对上述场景进行说明：对于UL，首先在建立SN节点时或者承载变更时，在MN以及SN之间的Xn接口上建立GTP隧道用于传输原侧收到的数据转发。
当一个Qos数据流(Flow)的承载从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持，终端和水泵内原侧节点对应的协议栈继续将未得到ACK确认的PDCP PDU继续传输，如图中所示，终端设备继续将数据流1的第一部分数据发送至MN；直至数据流1的第一部分数据传输完成后，向原侧节点传输第二指示信息；
其中，所述第二指示信息可以位于第一部分数据的最后一个数据包内；该第二指示信息用于告诉原侧节点该转移的Qos数据流(Flow)的未完成的数据传输已经完成。
原侧节点将接收到的数据流1的第一部分数据，比如SDAP SDU，以及SDAP end marker即第二指示信息，通过Xn接口传递给目标侧节点(SN)；目标侧节点(SN)首先将来自原侧节点的数据SDAP SDU发送给核心网，收到第二指示信息后，将本侧收到 的数据流1的第二部分数据发给核心网。
或者，
原侧节点接收到的数据流1的第一部分数据，比如，接收到SDAP SDU以及SDAP end marker即第二指示信息；所述原侧节点首先将接收到的SDAP SDU通过本节点于核心网之间的与PDU session对应的GTP隧道发送给核心网，然后将SDAP end marker通过Xn接口传递给目标侧，目标侧收到第二指示信息即SDAP end marker指示后，再将本侧收到的数据发给核心网。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，向第二网络设备发送指示信息，使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例七、
本申请实施例提供了一种第一网络设备，包括：
第一通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
另外，当所述数据流的承载从第一网络设备转移到第二网络设备时，第一通信单元，保持原数据无线承载DRB，向所述终端设备传输未得到确认的数据流的第一部分数据，向第二网络设备转发来自核心网的第二部分数据。
其中，未得到确认可以为未得到接收端发来的ACK确认信息的部分数据；并且，所述数据流的第二部分数据为当数据流由第一网络设备转移到第二网络设备的同时，仍然在第一网络设备处的数据。
此时，还可以包括：第一通信单元，保持向第二网络设备发送第二部分数据，直至此部分数据发完为止。
当数据流的第二部分数据完成发送至第二网络设备的时候，生成第一指示信息，然后向第二网络设备发送第一指示信息。
其中，所述第一指示信息可以为空白数据包、或者、可以为包含有预设标识的数据包。其中，预设标识可以为根据实际情况设置的，比如，可以为Nbit的数据，该N bit的数据为预设排列，本实施例中不对其进行穷举。
进一步地，所述第一通信单元，通过Xn接口，向第二网络设备发送第一指示信息。
下面结合图7对上述场景进行说明：对于下行(DL)数据，一个Qos数据流(Flow)1从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持(可以为将接入和移动管理功能(AMF)发来的QoS数据流1的第一部分数据)，数据流1的第一部分数据通过原承载保持向终端设备发送，原侧节点继续将未得到ACK确认的QoS数据流1的第一部分PDCP PDU，也就是QoS数据流1的第一部分数据继续传输；同时，第一网络设备接收来自核心网的第二部分数据，向第二网络设备(也就是SN)发送第二部分数据，直至剩余的所有未得到ACK确认的QoS数据流1的第二部分PDCP PDU向SN传输完毕，原侧节点(MN)通过Xn接口发送第一指示信息给目标侧(SN)；其中，该指示指示目标侧可以开始在新的承载上开始对上述发生转移的Qos数据流(Flow)进行数据传输。还需要指出的是，当SN，也就是本实施例中的第二网络设备，接收到数据流的第二部分数据以及第一指示信息之后，将第二部分数据先进行传输、然后再传输自身的第三部分数据。如此，就保证了传输的数据不会乱序。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息，通过所述第一指示信息使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例八、
本申请实施例提供了一种第二网络设备，如图12所示，包括：
第二通信单元1201，当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
另外，当所述数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备保持原数据无线承载DRB，向第二网络设备传输第二部分数据。
当数据流的第而部分数据完成发送至第二网络设备的时候，生成第一指示信息，然后向第二网络设备发送第一指示信息。
其中，所述第一指示信息可以为空白数据包、或者、可以为包含有预设标识的数据包。其中，预设标识可以为根据实际情况设置的，比如，可以为Nbit的数据，该N bit的数据为预设排列，本实施例中不对其进行穷举。
进一步地，第二通信单元1201，通过Xn接口接收所述第一网络设备发送的第一指示信息。
当第二网络设备接收到所述第一指示信息时，第二通信单元1201，就可以开始在新的承载上对发生转移的数据流进行按序传输。
所述第二网络设备还包括：
第二处理单元1202，基于所述第一指示信息，将所述数据流的第一部分数据、以及第二部分数据排序后进行传输。
第二通信单元1201，接收所述核心网设备发送的第三部分数据；也就是说，当数据流的承载转移的时候，第二网络设备开始从核心网接收第三部分数据。
当第二网络设备接收到所述第一指示信息时，所述第二网络设备就可以开始在新的承载上对发生转移的数据流进行按序传输；其中，按序传输可以为所述将所述第二部分数据排在第三部分数据之前进行传输。
由于第二部分数据发生在数据流转移的时候，因此第二部分数据的顺序在第三部分数据之前，所以，当进行排序的时候，将第二部分数据排列在第三部分数据之前进行传输，从而能够保证数据流的承载发生转移的时候不会出现乱序。
下面结合图7对上述场景进行说明：对于下行(DL)数据，一个Qos数据流(Flow)1从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持(可以为将接入和移动管理功能(AMF)发来的QoS数据流1的第一部分数据)，数据流1的第一部分数据通过原承载保持向终端设备发送，原侧节点继续将未得到ACK确认的QoS数据流1的第一部分PDCP PDU，也就是QoS数据流1的第一部分数据继续传输；同时，第一网络设备接收来自核心网的第二部分数据，向第二网络设备(也就是SN)发送第二部分数据，直至剩余的所有未得到ACK确认的QoS数据流1的第二部分PDCP PDU向SN传输完毕，原侧节点(MN)通过Xn接口发送第一指示信息给目标侧(SN)；其中，该指示指示目标侧可以开始在新的承载上开始对上述发生转移的Qos数据流(Flow)进行数据传输。还需要指出的是，当SN，也就是本实施例中的第二网络设备，接收到数据流的第二部分数据以及第一指示信息之后，将第二部分数据先进行传输、然后再传输自身的第三部分数据。如此，就保证了传输的数据不会乱序。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息，通过所述第一指示信息使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例九、
本申请实施例提供了一种终端设备，包括：
第六通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的数据流的第一部分数据。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网 络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
另外，当所述数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备保持原数据无线承载DRB，向所述终端设备传输未得到确认的数据流的第一部分数据，向第二网络设备转发来自核心网的第二部分数据。
所述第六通信单元，与所述第一网络设备保持原数据无线承载DRB，接收所述第一网络设备传输的未得到确认的数据流的第一部分数据。
下面结合图7对上述场景进行说明：对于下行(DL)数据，一个Qos数据流(Flow)1从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持(可以为将接入和移动管理功能(AMF)发来的QoS数据流1的第一部分数据)，数据流1的第一部分数据通过原承载保持向终端设备发送，原侧节点继续将未得到ACK确认的QoS数据流1的第一部分PDCP PDU，也就是QoS数据流1的第一部分数据继续传输；同时，第一网络设备接收来自核心网的第二部分数据，向第二网络设备(也就是SN)发送第二部分数据，直至剩余的所有未得到ACK确认的QoS数据流1的第二部分PDCP PDU向SN传输完毕，原侧节点(MN)通过Xn接口发送第一指示信息给目标侧(SN)；其中，该指示指示目标侧可以开始在新的承载上开始对上述发生转移的Qos数据流(Flow)进行数据传输。还需要指出的是，当SN，也就是本实施例中的第二网络设备，接收到数据流的第二部分数据以及第一指示信息之后，将第二部分数据先进行传输、然后再传输自身的第三部分数据。如此，就保证了传输的数据不会乱序。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息，通过所述第一指示信息使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例十、
本申请实施例提供了一种终端设备，包括：
第三通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，所述终端设备向第一网络设备传输数据流的第一部分数据，以及第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成。
本实施例适用于终端设备向网络侧发送上行数据时，发生数据流的承载转移的场景中。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
第三通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，保持与所述第一网络设备之间的数据无线承载DRB，向所述第一网络设备发送未得到确认的所述数据流的第一部分PDCP PDU。
也就是说，当Qos数据流(Flow)从一个网络设备转移到另一个网络设备时，例如MN到SN转移，原侧网络设备的DRB在承载变更后继续保持，UE内原侧节点对应的协议栈继续将未得到ACK确认的数据流的第一部分PDCP PDU继续通过原承载向第一网络设备(比如，MN)传输。
另外，在执行前述方案的同时，第三通信单元，向第二网络设备传输数据流的第二部分数据。
第三通信单元，向第一网络设备传输数据流的第一部分数据完成的时候，生成第二指示信息，然后向第一网络设备发送第二指示信息。
其中，所述第二指示信息可以为空白数据包、或者、可以为包含有预设标识的数据包。其中，预设标识可以为根据实际情况设置的，比如，可以为Nbit的数据，该N bit的数据为预设排列，本实施例中不对其进行穷举。
下面结合图9对上述场景进行说明：对于UL，首先在建立SN节点时或者承载变 更时，在MN以及SN之间的Xn接口上建立GTP隧道用于传输原侧收到的数据转发。
当一个Qos数据流(Flow)的承载从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持，终端和水泵内原侧节点对应的协议栈继续将未得到ACK确认的PDCP PDU继续传输，如图中所示，终端设备继续将数据流1的第一部分数据发送至MN；直至数据流1的第一部分数据传输完成后，向原侧节点传输第二指示信息；
其中，所述第二指示信息可以位于第一部分数据的最后一个数据包内；该第二指示信息用于告诉原侧节点该转移的Qos数据流(Flow)的未完成的数据传输已经完成。
原侧节点将接收到的数据流1的第一部分数据，比如SDAP SDU，以及SDAP end marker即第二指示信息，通过Xn接口传递给目标侧节点(SN)；目标侧节点(SN)首先将来自原侧节点的数据SDAP SDU发送给核心网，收到第二指示信息后，将本侧数据收到的数据流1的第二部分数据发给核心网。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，向第二网络设备发送指示信息，使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例十一、
本申请实施例提供了一种第一网络设备，包括：
第四通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，接收终端设备发来的数据流的第一部分数据，以及终端设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；将所述数据流的第一部分数据以及所述第二指示信息发送至第二网络设备，或者，将所述数据流的第一部分数据发送至核心网以及将所述第二指示信息发送至第二网络设备。
本实施例适用于终端设备向网络侧发送上行数据时，发生数据流的承载转移的场景中。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
第四通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，数据无线承载DRB继续保持，接收终端设备发来的未得到确认的所述数据流的第一部分PDCP PDU。
也就是说，当Qos数据流(Flow)从一个网络设备转移到另一个网络设备时，例如MN到SN转移，原侧网络设备的DRB在承载变更后继续保持，UE内原侧节点对应的协议栈继续将未得到ACK确认的数据流的第一部分PDCP PDU继续通过原承载向第一网络设备(比如，MN)传输。
另外，在执行前述方案的同时，所述终端设备向第二网络设备传输数据流的第二部分数据。
所述终端设备向第一网络设备传输数据流的第一部分数据完成的时候，生成第二指示信息，然后向第一网络设备发送第二指示信息。
其中，所述第二指示信息可以为空白数据包、或者、可以为包含有预设标识的数据包。其中，预设标识可以为根据实际情况设置的，比如，可以为Nbit的数据，该N bit的数据为预设排列，本实施例中不对其进行穷举。
第四通信单元，将所述数据流的第一部分数据、以及所述第二指示信息，通过Xn接口发送至第二网络设备。
或者，第四通信单元，将所述数据流的第一部分数据通过与核心网之间的GTP隧道发送至核心网；将所述第二指示信息通过Xn接口发送至第二网络设备。
第四通信单元，在Xn接口建立与第二网络设备之间的GTP隧道；其中，所述GTP隧道用于向第二网络设备进行数据转发。
即第一网络设备在接收到终端设备基于原承载发来的第一部分数据以及第二指示的时候，实时的将这些信息通过与第二网络设备之间Xn接口建立的GTP隧道发送至第二网络设备。使得第二网络设备对第一部分数据以及本身接收到的第二部分数据进行排 序之后向上层提交。
下面结合图9对上述场景进行说明：对于UL，首先在建立SN节点时或者承载变更时，在MN以及SN之间的Xn接口上建立GTP隧道用于传输原侧收到的数据转发。
当一个Qos数据流(Flow)的承载从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持，终端和水泵内原侧节点对应的协议栈继续将未得到ACK确认的PDCP PDU继续传输，如图中所示，终端设备继续将数据流1的第一部分数据发送至MN；直至数据流1的第一部分数据传输完成后，向原侧节点传输第二指示信息；
其中，所述第二指示信息可以位于第一部分数据的最后一个数据包内；该第二指示信息用于告诉原侧节点该转移的Qos数据流(Flow)的未完成的数据传输已经完成。
原侧节点将接收到的数据流1的第一部分数据，比如SDAP SDU，以及SDAP end marker即第二指示信息，通过Xn接口传递给目标侧节点(SN)；目标侧节点(SN)首先将来自原侧节点的数据SDAP SDU发送给核心网，收到第二指示信息后，将本侧收到的数据流1的第二部分数据发给核心网。
或者，
原侧节点接收到的数据流1的第一部分数据，比如，接收到SDAP SDU以及SDAP end marker即第二指示信息；所述原侧节点首先将接收到的SDAP SDU通过本节点于核心网之间的与PDU session对应的GTP隧道发送给核心网，然后将SDAP end marker通过Xn接口传递给目标侧，目标侧收到第二指示信息即SDAP end marker指示后，再将本侧收到的数据发给核心网。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，向第二网络设备发送指示信息，使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
实施例十二、
本申请实施例提供了一种第二网络设备，如图13所示，包括：
第五通信单元1301，当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的数据流的第一部分数据以及第二指示信息，或者，接收第一网络设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；
第五处理单元1302，基于所述第二指示信息，将所述第一部分数据递交至核心网之后，将数据流的第二部分数据递交至核心网。
本实施例适用于终端设备向网络侧发送上行数据时，发生数据流的承载转移的场景中。
本实施例中的数据流可以理解为QoS数据流；第一网络设备可以为原节点、第二网络设备可以为目的节点。另外，第一网络设备以及第二网络设备可以分别为双连接(DC)中的主节点(MN)以及辅助节点(SN)，当然，还可以为DC场景下的其他节点，只是这里不再进行赘述。
还需要指出的是，本实施例中的数据流可以为Qos数据流。
当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备的数据无线承载DRB继续保持，接收终端设备发来的未得到确认的所述数据流的第一部分PDCP PDU。也就是说，当Qos数据流(Flow)从一个网络设备转移到另一个网络设备时，例如MN到SN转移，原侧网络设备的DRB在承载变更后继续保持，UE内原侧节点对应的协议栈继续将未得到ACK确认的数据流的第一部分PDCP PDU继续通过原承载向第一网络设备(比如，MN)传输。
另外，在执行前述方案的同时，所述终端设备向第二网络设备传输数据流的第二部分数据。
所述终端设备向第一网络设备传输数据流的第一部分数据完成的时候，生成第二指示信息，然后向第一网络设备发送第二指示信息。
其中，所述第二指示信息可以为空白数据包、或者、可以为包含有预设标识的数据包。其中，预设标识可以为根据实际情况设置的，比如，可以为Nbit的数据，该N bit的数据为预设排列，本实施例中不对其进行穷举。
第五通信单元1301，通过Xn接口接收第一网络设备发来的数据流的第一部分数据、 以及第二指示信息。
或者，所述第五通信单元1301，通过Xn接口接收第一网络设备发来的数据流的第二指示信息。
第五通信单元1301，在Xn接口建立与第一网络设备之间的GTP隧道；其中，所述GTP隧道用于接收第一网络设备发送的数据。
第五处理单元1302，判断是否接收到第二指示信息，若未接收到，则保持不向核心网发送所述数据流的第二部分数据；若接收到，则控制将所述第一部分数据发送至核心网之后，将接收到的数据流的第二部分数据递交至核心网。即第一网络设备在接收到终端设备基于原承载发来的第一部分数据以及第二指示的时候，实时的将这些信息通过与第二网络设备之间Xn接口建立的GTP隧道发送至第二网络设备。第二网络设备对第一部分数据以及本身接收到的第二部分数据进行排序之后向上层提交。
下面结合图9对上述场景进行说明：对于UL，首先在建立SN节点时或者承载变更时，在MN以及SN之间的Xn接口上建立GTP隧道用于传输原侧收到的数据转发。
当一个Qos数据流(Flow)的承载从一个节点转移到另一个节点时，例如MN到SN转移；原侧节点的DRB在承载变更后继续保持，终端和水泵内原侧节点对应的协议栈继续将未得到ACK确认的PDCP PDU继续传输，如图中所示，终端设备继续将数据流1的第一部分数据发送至MN；直至数据流1的第一部分数据传输完成后，向原侧节点传输第二指示信息；
其中，所述第二指示信息可以位于第一部分数据的最后一个数据包内；该第二指示信息用于告诉原侧节点该转移的Qos数据流(Flow)的未完成的数据传输已经完成。
原侧节点将接收到的数据流1的第一部分数据，比如SDAP SDU，以及SDAP end marker即第二指示信息，通过Xn接口传递给目标侧节点(SN)；目标侧节点(SN)首先将来自原侧节点的数据SDAP SDU发送给核心网，收到第二指示信息后，将本侧收到的数据流1的第二部分数据发给核心网。
或者，
原侧节点接收到的数据流1的第一部分数据，比如，接收到SDAP SDU以及SDAP end marker即第二指示信息；所述原侧节点首先将接收到的SDAP SDU通过本节点于核心网之间的与PDU session对应的GTP隧道发送给核心网，然后将SDAP end marker通过Xn接口传递给目标侧，目标侧收到第二指示信息即SDAP end marker指示后，再将本侧收到的数据发给核心网。
可见，通过采用上述方案，就能够当数据流的承载从第一网络设备转移到第二网络设备时，向第二网络设备发送指示信息，使得所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。从而，就能够保证发生数据流转移的时候，目的网络设备侧能够保证传输数据的顺序。
本发明实施例还提供了一种终端设备、或者网络设备的硬件组成架构，如图14所示，包括：至少一个处理器1401、存储器1402、至少一个网络接口1403。各个组件通过总线系统1404耦合在一起。可理解，总线系统1404用于实现这些组件之间的连接通信。总线系统1404除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图14中将各种总线都标为总线系统1404。
可以理解，本发明实施例中的存储器1402可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。
在一些实施方式中，存储器1402存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：
操作系统14021和应用程序14022。
其中，所述处理器1401配置为：能够处理前述实施例一至五任一项的方法步骤，这里不再进行赘述。
本发明实施例提供的一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实施前述实施例一至五任一项的方法步骤。
本发明实施例上述装置如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可 以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read Only Memory)、磁碟或者光盘等各种可以存储程序代码的介质。这样，本发明实施例不限制于任何特定的硬件和软件结合。
尽管为示例目的，已经公开了本发明的优选实施例，本领域的技术人员将意识到各种改进、增加和取代也是可能的，因此，本发明的范围应当不限于上述实施例。

Claims (51)

  1. 一种数据按序递交的方法，应用于第一网络设备，所述方法包括：
    当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    当所述数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备保持原数据无线承载DRB，向所述终端设备传输未得到确认的数据流的第一部分数据，向第二网络设备转发来自核心网的第二部分数据。
  3. 根据权利要求1或2所述的方法，其中，所述第一网络设备向第二网络设备发送第一指示信息，包括：
    所述第一网络设备通过Xn接口，向第二网络设备发送第一指示信息。
  4. 一种数据按序递交的方法，应用于第二网络设备，所述方法包括：
    当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
  5. 根据权利要求4所述的方法，其中，所述方法还包括：
    通过Xn接口接收所述第一网络设备发送的第一指示信息。
  6. 根据权利要求4或5所述的方法，其中，所述方法还包括：
    接收所述第一网络设备发来的数据流的第二部分数据。
  7. 根据权利要求4-6任一项所述的方法，其中，所述方法还包括：
    接收所述核心网设备发送的第三部分数据。
  8. 根据权利要求7所述的方法，其中，所述方法还包括：
    基于所述第一指示信息，将所述数据流的第二部分数据、以及第三部分数据排序后进行传输。
  9. 根据权利要求8所述的方法，其中，所述将所述数据流的第二部分数据、以及第三部分数据排序后进行传输，包括：
    将所述数据流的第二部分数据排在第三部分数据之前进行传输。
  10. 一种数据按序递交的方法，应用于终端设备，所述方法包括：
    当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的数据流的第一部分数据。
  11. 根据权利要求10所述的方法，其中，所述接收第一网络设备发来的数据流的第一部分数据，包括：
    与所述第一网络设备保持原数据无线承载DRB，接收所述第一网络设备传输的未得到确认的数据流的第一部分数据。
  12. 一种数据按序递交的方法，应用于终端设备，所述方法包括：
    当数据流的承载从第一网络设备转移到第二网络设备时，所述终端设备向第一网络设备传输数据流的第一部分数据，以及第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成。
  13. 根据权利要求12所述的方法，其中，所述方法还包括：
    所述终端设备向第二网络设备传输数据流的第二部分数据。
  14. 根据权利要求12所述的方法，其中，所述终端设备向第一网络设备传输数据流的第一部分数据，包括：
    当数据流的承载从第一网络设备转移到第二网络设备时，保持与所述第一网络设备之间的数据无线承载DRB，向所述第一网络设备发送未得到确认的所述数据流的第一部分PDCP PDU。
  15. 一种数据按序递交的方法，应用于第一网络设备，所述方法包括：
    当数据流的承载从第一网络设备转移到第二网络设备时，接收终端设备发来的数据流的第一部分数据，以及终端设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；
    将所述数据流的第一部分数据以及所述第二指示信息发送至第二网络设备，或者，将所述数据流的第一部分数据发送至核心网以及将所述第二指示信息发送至第二网络设备。
  16. 根据权利要求15所述的方法，其中，所述将所述数据流的第一部分数据以及所述第二指示信息，发送至第二网络设备，包括：
    将所述数据流的第一部分数据、以及所述第二指示信息，通过Xn接口发送至第二网络设备。
  17. 根据权利要求15所述的方法，其中，所述将所述数据流的第一部分数据发送至核心网以及将所述第二指示信息发送至第二网络设备，包括：
    将所述数据流的第一部分数据通过与核心网之间的GTP隧道发送至核心网；
    将所述第二指示信息通过Xn接口发送至第二网络设备。
  18. 根据权利要求15所述的方法，其中，所述接收终端设备发来的数据流的第一部分数据，包括：
    当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备的数据无线承载DRB继续保持，接收终端设备发来的未得到确认的所述数据流的第一部分PDCP PDU。
  19. 根据权利要求18所述的方法，其中，所述方法还包括：
    在Xn接口建立与第二网络设备之间的GTP隧道；其中，所述GTP隧道用于向第二网络设备进行数据转发。
  20. 一种数据按序递交的方法，应用于第二网络设备，所述方法包括：
    当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的数据流的第一部分数据以及第二指示信息，或者，接收第一网络设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；
    基于所述第二指示信息，所述第二网络设备将所述第一部分数据递交至核心网之后，将数据流的第二部分数据递交至核心网。
  21. 根据权利要求20所述的方法，其中，所述接收第一网络设备发来的数据流的第一部分数据、以及第二指示信息，包括：
    通过Xn接口接收第一网络设备发来的数据流的第一部分数据、以及第二指示信息。
  22. 根据权利要求20所述的方法，其中，所述接收第一网络设备发来的第二指示信息，包括：
    通过Xn接口接收第一网络设备发来的数据流的第二指示信息。
  23. 根据权利要求20所述的方法，其中，所述方法还包括：
    判断是否接收到第二指示信息，若未接收到，则保持不向核心网发送所述数据流的 第二部分数据；若接收到，则控制将所述第一部分数据发送至核心网之后，将接收到的数据流的第二部分数据递交至核心网。
  24. 根据权利要求23所述的方法，其中，所述方法还包括：
    在Xn接口建立与第一网络设备之间的GTP隧道；其中，所述GTP隧道用于接收第一网络设备发送的数据。
  25. 一种第一网络设备，包括：
    第一通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备向第二网络设备发送第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
  26. 根据权利要求25所述的第一网络设备，其中，所述第一通信单元，当所述数据流的承载从第一网络设备转移到第二网络设备时，所述第一网络设备保持原数据无线承载DRB，向所述终端设备传输未得到确认的数据流的第一部分数据，向第二网络设备转发来自核心网的第二部分数据。
  27. 根据权利要求25或26所述的第一网络设备，其中，所述第一通信单元，通过Xn接口，向第二网络设备发送第一指示信息。
  28. 一种第二网络设备，包括：
    第二通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的第一指示信息；其中，所述第一指示信息，用于指示所述第二网络设备开始在新的承载上对发生转移的数据流进行按序传输。
  29. 根据权利要求28所述的第二网络设备，其中，所述第二通信单元，通过Xn接口接收所述第一网络设备发送的第一指示信息。
  30. 根据权利要求28或29所述的第二网络设备，其中，所述第二通信单元，接收所述第一网络设备发来的数据流的第二部分数据。
  31. 根据权利要求28-30任一项所述的第二网络设备，其中，所述第二通信单元，接收所述核心网设备发送的第三部分数据。
  32. 根据权利要求31所述的第二网络设备，其中，所述第二网络设备还包括：
    第二处理单元，基于所述第一指示信息，将所述数据流的第二部分数据、以及第三部分数据排序后进行传输。
  33. 根据权利要求32所述的第二网络设备，其中，所述第二通信单元，将所述数据流的第二部分数据排在第三部分数据之前进行传输。
  34. 一种终端设备，包括：
    第六通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的数据流的第一部分数据。
  35. 根据权利要求34所述的终端设备，其中，所述第六通信单元，与所述第一网络设备保持原数据无线承载DRB，接收所述第一网络设备传输的未得到确认的数据流的第一部分数据。
  36. 一种终端设备，包括：
    第三通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，向第一网络设备传输数据流的第一部分数据，以及第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成。
  37. 根据权利要求36所述的终端设备，其中，所述第三通信单元，向第二网络设备传输数据流的第二部分数据。
  38. 根据权利要求37所述的终端设备，其中，所述第三通信单元，当数据流的承 载从第一网络设备转移到第二网络设备时，保持与所述第一网络设备之间的数据无线承载DRB，向所述第一网络设备发送未得到确认的所述数据流的第一部分PDCP PDU。
  39. 一种第一网络设备，包括：
    第四通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，接收终端设备发来的数据流的第一部分数据，以及终端设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；将所述数据流的第一部分数据以及所述第二指示信息发送至第二网络设备，或者，将所述数据流的第一部分数据发送至核心网以及将所述第二指示信息发送至第二网络设备。
  40. 根据权利要求39所述的第一网络设备，其中，
    第四通信单元，将所述数据流的第一部分数据、以及所述第二指示信息，通过Xn接口发送至第二网络设备。
  41. 根据权利要求39所述的第一网络设备，其中，
    第四通信单元，将所述数据流的第一部分数据通过与核心网之间的GTP隧道发送至核心网；将所述第二指示信息通过Xn接口发送至第二网络设备。
  42. 根据权利要求39所述的第一网络设备，其中，
    第四通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，数据无线承载DRB继续保持，接收终端设备发来的未得到确认的所述数据流的第一部分PDCP PDU。
  43. 根据权利要求42所述的第一网络设备，其中，
    第四通信单元，在Xn接口建立与第二网络设备之间的GTP隧道；其中，所述GTP隧道用于向第二网络设备进行数据转发。
  44. 一种第二网络设备，包括：
    第五通信单元，当数据流的承载从第一网络设备转移到第二网络设备时，接收第一网络设备发来的数据流的第一部分数据以及第二指示信息，或者，接收第一网络设备发来的第二指示信息；所述第二指示信息，用于指示发生转移时数据流中未传输完成的第一部分数据传输完成；
    第五处理单元，基于所述第二指示信息，将所述第一部分数据递交至核心网之后，将数据流的第二部分数据递交至核心网。
  45. 根据权利要求44所述的第二网络设备，其中，所述第五通信单元，通过Xn接口接收第一网络设备发来的数据流的第一部分数据、以及第二指示信息。
  46. 根据权利要求44所述的第二网络设备，其中，所述第五通信单元，通过Xn接口接收第一网络设备发来的数据流的第二指示信息。
  47. 根据权利要求44所述的第二网络设备，其中，所述第五处理单元，判断是否接收到第二指示信息，若未接收到，则保持不向核心网发送所述数据流的第二部分数据；若接收到，则控制将所述第一部分数据发送至核心网之后，将接收到的数据流的第二部分数据递交至核心网。
  48. 根据权利要求47所述的第二网络设备，其中，所述第五通信单元，在Xn接口建立与第一网络设备之间的GTP隧道；其中，所述GTP隧道用于接收第一网络设备发送的数据。
  49. 一种网络设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
    其中，所述处理器用于运行所述计算机程序时，执行权利要求1-9、15-24任一项所述方法的步骤。
  50. 一种终端设备，包括：处理器和用于存储能够在处理器上运行的计算机程序的存储器，
    其中，所述处理器用于运行所述计算机程序时，执行权利要求10-14任一项所述方法的步骤。
  51. 一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令，所述计算机可执行指令被执行时实现权利要求1-24任一项所述的方法步骤。
PCT/CN2018/104908 2018-06-15 2018-09-10 数据按序递交的方法、网络设备及终端设备 Ceased WO2019237530A1 (zh)

Priority Applications (14)

Application Number Priority Date Filing Date Title
KR1020207025593A KR102332206B1 (ko) 2018-06-15 2018-09-10 데이터를 순차적으로 제출하는 방법, 네트워크 장치 및 단말 장치
EP18922754.9A EP3720033B1 (en) 2018-06-15 2018-09-10 Method for delivering data in order and network device
BR112020015544-6A BR112020015544A2 (pt) 2018-06-15 2018-09-10 método para entregar dados em ordem, método para entregar dados em sequência e primeiro e segundo dispositivo de rede
MX2020008734A MX2020008734A (es) 2018-06-15 2018-09-10 Metodo para presentar datos en secuencia, dispositivo de red y dispositivo terminal.
JP2020544643A JP7097981B2 (ja) 2018-06-15 2018-09-10 データを順次提出する方法、ネットワーク装置及び端末装置
AU2018427836A AU2018427836B2 (en) 2018-06-15 2018-09-10 Method for submitting data in sequence, network device and terminal device
CA3089382A CA3089382C (en) 2018-06-15 2018-09-10 Method for submitting data in sequence, network device and terminal device
SG11202006962SA SG11202006962SA (en) 2018-06-15 2018-09-10 Method for submitting data in sequence, network device and terminal device
RU2020127015A RU2751673C1 (ru) 2018-06-15 2018-09-10 Способ отправки данных по порядку, сетевое устройство и терминальное устройство
CN202010564121.4A CN111654883B (zh) 2018-06-15 2018-09-10 数据按序递交的方法、网络设备及终端设备
CN201880068680.7A CN111247765A (zh) 2018-06-15 2018-09-10 数据按序递交的方法、网络设备及终端设备
TW108120565A TW202002701A (zh) 2018-06-15 2019-06-13 數據按序遞交的方法、網路設備及終端設備
US16/892,444 US11018832B2 (en) 2018-06-15 2020-06-04 Method for submitting data in sequence, network device and terminal device
US17/231,573 US11689334B2 (en) 2018-06-15 2021-04-15 Method for submitting data in sequence, network device and terminal device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
PCT/CN2018/091672 WO2019237364A1 (zh) 2018-06-15 2018-06-15 数据按序递交的方法、网络设备及终端设备
CNPCT/CN2018/091672 2018-06-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/892,444 Continuation US11018832B2 (en) 2018-06-15 2020-06-04 Method for submitting data in sequence, network device and terminal device

Publications (1)

Publication Number Publication Date
WO2019237530A1 true WO2019237530A1 (zh) 2019-12-19

Family

ID=68841755

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2018/091672 Ceased WO2019237364A1 (zh) 2018-06-15 2018-06-15 数据按序递交的方法、网络设备及终端设备
PCT/CN2018/104908 Ceased WO2019237530A1 (zh) 2018-06-15 2018-09-10 数据按序递交的方法、网络设备及终端设备

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/091672 Ceased WO2019237364A1 (zh) 2018-06-15 2018-06-15 数据按序递交的方法、网络设备及终端设备

Country Status (13)

Country Link
US (2) US11018832B2 (zh)
EP (1) EP3720033B1 (zh)
JP (1) JP7097981B2 (zh)
KR (1) KR102332206B1 (zh)
CN (2) CN111654883B (zh)
AU (1) AU2018427836B2 (zh)
BR (1) BR112020015544A2 (zh)
CA (1) CA3089382C (zh)
MX (1) MX2020008734A (zh)
RU (1) RU2751673C1 (zh)
SG (1) SG11202006962SA (zh)
TW (1) TW202002701A (zh)
WO (2) WO2019237364A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021208863A1 (zh) * 2020-04-16 2021-10-21 华为技术有限公司 数据传输方法及通信装置

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB201621072D0 (en) * 2016-12-12 2017-01-25 Samsung Electronics Co Ltd NR QOS handling
EP3834586B1 (en) * 2018-08-06 2022-03-23 Telefonaktiebolaget Lm Ericsson (Publ) Tunnel setup for split bearers in multi-rat dual connectivity (mr-dc) and nr-nr dual connectivity (nr-dc)
EP4021079A1 (en) * 2018-11-02 2022-06-29 Telefonaktiebolaget Lm Ericsson (Publ) Handling service data application protocol (sdapp) end markers at handover
WO2020200287A1 (en) * 2019-04-02 2020-10-08 Huawei Technologies Co., Ltd. Method, apparatus and systems for supporting packet delivery
CN113316202A (zh) * 2020-02-27 2021-08-27 华为技术有限公司 一种切换方法及通信装置
CN113543217B (zh) * 2020-04-16 2025-12-05 华为技术有限公司 数据传输方法及通信装置
CN116325900B (zh) * 2020-10-22 2026-01-06 华为技术有限公司 一种通信方法及装置
CN114513236B (zh) * 2020-11-16 2023-10-27 中国移动通信有限公司研究院 一种多天线预编码方法、装置及设备
CN116436499A (zh) * 2021-12-30 2023-07-14 中国移动通信有限公司研究院 一种信息处理方法、装置、设备和可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160352578A1 (en) * 2015-05-26 2016-12-01 Dell Products L.P. System and method for adaptive paths locator for virtual network function links
CN107404396A (zh) * 2016-05-20 2017-11-28 中国移动通信有限公司研究院 一种数据传输方法和装置
CN107484183A (zh) * 2016-06-08 2017-12-15 中国移动通信有限公司研究院 一种分布式基站系统、cu、du及数据传输方法
CN107770807A (zh) * 2016-08-15 2018-03-06 华为技术有限公司 一种数据处理方法及装置
CN107786493A (zh) * 2016-08-24 2018-03-09 中国移动通信有限公司研究院 一种数据传输方法及装置

Family Cites Families (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AP9901611A0 (en) * 1997-02-03 1999-09-30 Mci Communications Corp A communication system architecture.
US7328033B2 (en) * 2003-10-01 2008-02-05 Rappaport Theodore S Wireless network system and method
US7653037B2 (en) * 2005-09-28 2010-01-26 Qualcomm Incorporated System and method for distributing wireless network access parameters
CN1968198A (zh) * 2006-06-16 2007-05-23 华为技术有限公司 一种无线接入承载分组数据业务的QoS管理方法
CN101400156B (zh) * 2007-09-29 2012-06-06 华为技术有限公司 基于s1切换的下行及上行数据包转发方法
EP2107848B1 (en) * 2008-03-31 2013-03-13 Mitsubishi Electric R&D Centre Europe B.V. Method and device for carrying out a handover between base stations of a mobile telecommunication network for a mobile terminal
US8706118B2 (en) * 2011-09-07 2014-04-22 Telefonaktiebolaget L M Ericsson (Publ) 3G LTE intra-EUTRAN handover control using empty GRE packets
CN102438284A (zh) * 2011-12-12 2012-05-02 大唐移动通信设备有限公司 一种基于基站内小区切换的数据倒换方法及装置
US10045386B2 (en) * 2012-05-31 2018-08-07 Interdigital Patent Holdings, Inc. Method and apparatus for device-to-device (D2D) mobility in wireless systems
CA2917271C (en) * 2013-07-05 2019-03-05 Jian Xu Method and apparatus for forwarding data for small cell in wireless communication system
US20150043492A1 (en) * 2013-08-12 2015-02-12 Electronics And Telecommunications Research Institute Method for providing dual connectivity in wireless communication system
US9572171B2 (en) * 2013-10-31 2017-02-14 Intel IP Corporation Systems, methods, and devices for efficient device-to-device channel contention
CN104854938B (zh) * 2013-11-15 2021-05-14 荣耀终端有限公司 一种建立无线承载的方法及基站
EP3122146A1 (en) * 2014-03-20 2017-01-25 Kyocera Corporation Secondary base station, mobile station, communication control method, and master base station
CN103997604B (zh) * 2014-04-29 2017-03-01 小米科技有限责任公司 照片同步方法及装置
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
CN106941733B (zh) * 2016-01-04 2022-05-13 中兴通讯股份有限公司 双连接中实现重配置的方法、主服务基站及辅服务基站
CN106993313A (zh) * 2016-01-21 2017-07-28 中兴通讯股份有限公司 一种实现承载切换的方法及终端和基站
US10194480B2 (en) * 2016-03-09 2019-01-29 Cisco Technology, Inc. Core signalling reduction in dual connectivity
WO2018030982A1 (en) * 2016-08-08 2018-02-15 Nokia Technologies Oy End marker handling for mobility between 5g and lte
US10904806B2 (en) * 2016-08-12 2021-01-26 Ntt Docomo, Inc. Core network and base station
US10582523B2 (en) * 2016-08-13 2020-03-03 Qualcomm Incorporated Method and apparatus for secondary base station mobility
EP3488626B1 (en) * 2016-08-22 2022-09-28 Samsung Electronics Co., Ltd. Method and apparatus for providing services of network to terminal by using slice
EP3902368B1 (en) * 2016-09-30 2023-05-03 Samsung Electronics Co., Ltd. Method and apparatus for establishing dual-connectivity to transmit data in new radio communication architecture
WO2018079998A1 (ko) * 2016-10-27 2018-05-03 엘지전자(주) 무선 통신 시스템에서 핸드오버를 수행하기 위한 방법 및 이를 위한 장치
US11523319B2 (en) * 2017-01-09 2022-12-06 Lg Electronics Inc. Method for managing PDU session in wireless communication system and device for same
CN115278658B (zh) * 2017-01-30 2026-03-17 瑞典爱立信有限公司 针对用户平面数据的完整性保护的方法
KR102026137B1 (ko) * 2017-03-15 2019-09-27 한국전자통신연구원 밀리미터파 기반의 통신 시스템에서 통신 노드의 동작 방법
EP3598812B1 (en) * 2017-03-16 2022-02-09 LG Electronics Inc. Notifying a mobility event in a wireless communication system
US10368334B2 (en) * 2017-03-17 2019-07-30 Ofinno Technologies, Llc Radio access network paging area configuration
US10264622B2 (en) * 2017-03-17 2019-04-16 Ofinno Technologies, Llc Inactive state data forwarding
US10582560B2 (en) * 2017-03-17 2020-03-03 Ofinno, Llc Radio access network notification area update failure
US10448423B2 (en) * 2017-03-22 2019-10-15 Ofinno, Llc Data multiplexing in a wireless device and wireless network
US10757621B2 (en) * 2017-03-22 2020-08-25 Ofinno, Llc Conditional handover execution
US10512036B2 (en) * 2017-03-22 2019-12-17 Ofinno, Llc Secondary base station change
US11425594B2 (en) * 2017-03-23 2022-08-23 Nokia Technologies Oy Quality of service flow relocation
US10873911B2 (en) * 2017-03-23 2020-12-22 Ofinno, LCC Uplink transmission power adjustment
US10716094B2 (en) * 2017-03-23 2020-07-14 Ofinno, Llc Packet duplication in a wireless device and wireless network
EP3603168B1 (en) * 2017-03-23 2022-01-05 LG Electronics Inc. Method for transmitting lossless data packet based on quality of service (qos) framework in wireless communication system and a device therefor
WO2018178075A1 (en) * 2017-03-30 2018-10-04 Sony Corporation Wireless telecommunications apparatus and methods
US20180324631A1 (en) * 2017-05-05 2018-11-08 Mediatek Inc. Using sdap headers for handling of as/nas reflective qos and to ensure in-sequence packet delivery during remapping in 5g communication systems
CN108811016B (zh) * 2017-05-05 2022-02-25 北京三星通信技术研究有限公司 一种支持切换的方法
CN111183706B (zh) * 2017-06-16 2023-11-14 苹果公司 在双重连通中使能非活跃模式的gNB的装置
US20180367288A1 (en) * 2017-06-16 2018-12-20 Huawei Technologies Co., Ltd. Dynamic activation and deactivation of packet duplication
EP3453221B1 (en) * 2017-06-16 2020-01-22 Telefonaktiebolaget LM Ericsson (publ.) Race condition avoidance between master base station initiated secondary base station release and secondary base station initiated secondary base station change procedures
AU2017424739B2 (en) * 2017-07-25 2023-02-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Switching method, access network device and terminal device
US10419982B1 (en) * 2018-03-14 2019-09-17 Cisco Technology, Inc. Methods and apparatus for providing end marker functionality in mobile networks having SRv6-configured mobile user planes

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160352578A1 (en) * 2015-05-26 2016-12-01 Dell Products L.P. System and method for adaptive paths locator for virtual network function links
CN107404396A (zh) * 2016-05-20 2017-11-28 中国移动通信有限公司研究院 一种数据传输方法和装置
CN107484183A (zh) * 2016-06-08 2017-12-15 中国移动通信有限公司研究院 一种分布式基站系统、cu、du及数据传输方法
CN107770807A (zh) * 2016-08-15 2018-03-06 华为技术有限公司 一种数据处理方法及装置
CN107786493A (zh) * 2016-08-24 2018-03-09 中国移动通信有限公司研究院 一种数据传输方法及装置

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021208863A1 (zh) * 2020-04-16 2021-10-21 华为技术有限公司 数据传输方法及通信装置

Also Published As

Publication number Publication date
TW202002701A (zh) 2020-01-01
JP7097981B2 (ja) 2022-07-08
US20210234660A1 (en) 2021-07-29
US11018832B2 (en) 2021-05-25
SG11202006962SA (en) 2020-12-30
KR20200118142A (ko) 2020-10-14
CA3089382C (en) 2023-08-01
BR112020015544A2 (pt) 2021-02-02
AU2018427836A1 (en) 2020-08-06
MX2020008734A (es) 2020-09-28
CN111654883B (zh) 2023-01-31
CN111247765A (zh) 2020-06-05
CA3089382A1 (en) 2019-12-19
JP2021515467A (ja) 2021-06-17
EP3720033A4 (en) 2021-03-31
RU2751673C1 (ru) 2021-07-15
US11689334B2 (en) 2023-06-27
CN111654883A (zh) 2020-09-11
EP3720033A1 (en) 2020-10-07
EP3720033B1 (en) 2023-06-14
AU2018427836B2 (en) 2021-07-08
WO2019237364A1 (zh) 2019-12-19
KR102332206B1 (ko) 2021-12-02
US20200295902A1 (en) 2020-09-17

Similar Documents

Publication Publication Date Title
WO2019237530A1 (zh) 数据按序递交的方法、网络设备及终端设备
CN107277879B (zh) 一种支持无缝切换的方法及基站设备
AU2017424739B2 (en) Switching method, access network device and terminal device
CN110868733B (zh) 一种数据传输方法和装置
EP3177071A1 (en) Method for user equipment to switch base station, base station and user equipment
WO2019242748A1 (zh) 信息传输方法及装置
WO2020146991A1 (zh) 一种数据流处理方法、设备及存储介质
US20080084846A1 (en) Wireless communication system, wireless base station, and wireless communication control method
JP7250114B2 (ja) サービスノードの更新方法、端末機器、および、ネットワーク側機器
US20240129798A1 (en) Method, apparatus, system and device for configuring data stream, and computer medium
CN111586769A (zh) 无线通信系统中的切换方法、装置及系统
CN107438273B (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: 18922754

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018922754

Country of ref document: EP

Effective date: 20200701

ENP Entry into the national phase

Ref document number: 3089382

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2018427836

Country of ref document: AU

Date of ref document: 20180910

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020544643

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20207025593

Country of ref document: KR

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020015544

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112020015544

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200730