WO2018171791A1 - 数据传输方法、接入网设备、终端及通信系统 - Google Patents

数据传输方法、接入网设备、终端及通信系统 Download PDF

Info

Publication number
WO2018171791A1
WO2018171791A1 PCT/CN2018/080396 CN2018080396W WO2018171791A1 WO 2018171791 A1 WO2018171791 A1 WO 2018171791A1 CN 2018080396 W CN2018080396 W CN 2018080396W WO 2018171791 A1 WO2018171791 A1 WO 2018171791A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
access network
data packet
drb
terminal
Prior art date
Application number
PCT/CN2018/080396
Other languages
English (en)
French (fr)
Inventor
韩立锋
黄曲芳
戴明增
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to BR112019019834A priority Critical patent/BR112019019834A2/pt
Priority to JP2019552519A priority patent/JP6882510B2/ja
Priority to RU2019133658A priority patent/RU2762681C2/ru
Priority to EP18770178.4A priority patent/EP3606149B1/en
Priority to EP21177366.8A priority patent/EP3941110A1/en
Priority to CN201880020910.2A priority patent/CN110463256B/zh
Publication of WO2018171791A1 publication Critical patent/WO2018171791A1/zh
Priority to US16/581,151 priority patent/US10785825B2/en
Priority to US17/002,193 priority patent/US11540349B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1642—Formats specially adapted for sequence numbers
    • 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
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • 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
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/086—Load balancing or load distribution among access entities
    • H04W28/0861—Load balancing or load distribution among access entities between base stations
    • H04W28/0865—Load balancing or load distribution among access entities between base stations of different Radio Access Technologies [RATs], e.g. LTE or WiFi
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • 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/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • 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/22—Performing reselection for specific purposes for handling the traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • 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

Definitions

  • the present application relates to the field of wireless communications, and in particular, to a data transmission method, an access network device, a terminal, and a communication system.
  • New RAN new radio access networks
  • new radio access networks can provide shorter time. Delay, greater bandwidth, and support for a large number of connections to meet the growing demand for mobile communications.
  • QoS quality of service
  • PDU protocol data unit
  • the core network provides the QoS requirements of the flow to the base station, and the base station completes the data radio bearer (DRB) according to the QoS requirements.
  • DRB data radio bearer
  • the mapping for example, maps flows with the same QoS requirements to the same DRB through which the DRB transmits.
  • a tunnel is established between the source base station and the target base station, and the terminal data packet on the source base station is sent to the target base station. Further, the target base station communicates with the terminal. Since the target base station and the source base station are configured with different mappings between the flow and the DRB, the terminal data packet may be lost or duplicated during transmission to the target base station or subsequent air interface transmission, which affects the communication continuity of the terminal.
  • the embodiment of the present application provides a data transmission method, an access network device, a terminal, and a communication system.
  • an embodiment of the present application provides a data transmission method, including:
  • the first access network device receives the forwarding data packet from the second access network device; the first access network device maps the data packet that does not include the flow identifier in the forwarding data packet to the first data radio bearer (data radio Bearer, DRB), the first DRB corresponds to the DRB of the second access network device; the first access network device, according to the second mapping relationship, the data packet including the flow identifier in the forwarded data packet Mapping to the second DRB, where the second mapping relationship is a mapping relationship between the flow and the DRB in the first access network device.
  • DRB data radio Bearer
  • the first DRB and the DRB of the second access network device respectively satisfy a first mapping relationship, where the first mapping relationship is a mapping relationship between a flow and a DRB in the second access network device.
  • the first DRB is a mapping DRB of a DRB of the second access network device.
  • the forwarding data packet includes at least one data packet: the data of the packet data convergence protocol (PDCP) layer of the second access network device that has been assigned the sequence number and is not received by the terminal. a data packet of a PDCP layer of an unassigned sequence number of the second access network device; a data packet of a service data adaptation protocol (SDAP) layer of the second access network device.
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • each access network device can independently set the mapping relationship between the flow and the DRB, the data packet with the flow identifier is mapped to the second DRB for transmission, and the data packet without the flow identifier is mapped to the first DRB.
  • the data packet transmission mode can be selected according to the actual situation of the network, so as to avoid data packet loss or repeated packet delivery problems caused by the mapping relationship between the flow and the DRB of each access network device in the scenario of switching or dual connectivity. Improve the continuity of terminal services and improve communication quality.
  • the first access network device sends, by using the first DRB, a data packet that has been allocated a sequence number in the forwarding data packet and does not include a flow identifier to the terminal; the first access The network device sends, by using the second DRB, a data packet in the forwarding data packet that is not assigned a sequence number and includes a flow identifier.
  • the data packet may be a data packet of the PDCP layer, and the sequence number is a serial number of the PDCP layer.
  • the first access network device sends, by using the first DRB, a data packet that does not include a flow identifier in the forwarded data packet to the terminal, where the first access network device passes the
  • the second DRB sends, to the terminal, a data packet that includes the flow identifier in the forwarded data packet.
  • the data packet including the flow identifier may be a data packet of a PDCP layer to which the flow identifier is allocated and/or a data packet of an SDAP layer.
  • the method further includes: the first access network device routing, by the SDAP entity, the data packet that includes the flow identifier in the forwarding data packet to the second DRB.
  • the receiving, by the first access network device, the forwarding data packet from the second access network device includes: the first access network device, the tunnel established by using the DRB, and the tunnel established based on the session Receiving, by the second access network device, the forwarding data packet, where the DRB-based tunnel is used to transmit a data packet of a PDCP layer of an allocated sequence number of the second access network device; a tunnel established by the session for transmitting a data packet of the SDAP layer of the second access network device, and/or for transmitting a PDCP layer of the second access network device that includes a flow identifier and has no assigned sequence number data pack.
  • the receiving, by the first access network device, the forwarding data packet from the second access network device includes: the first access network device from the second access by using a DRB-based tunnel
  • the network device receives the forwarded data packet.
  • the tunnel established based on the DRB may have one or more. For example, when there are two tunnels established based on DRB, one of the tunnels can be used to transmit the data packet with the flow identifier; the other tunnel can be used to transmit the data packet without the flow identifier.
  • the receiving, by the first access network device, the forwarding data packet from the second access network device includes: the first access network device from the second access by using a session established tunnel The network device receives the data packet including the flow identifier in the forwarded data packet.
  • the first access network device routes, by the SDAP entity, a data packet of the PDCP layer of the allocated sequence number received from the session establishment tunnel to the first DRB; and the unassigned sequence number is The data packet of the PDCP layer or the data packet of the SDAP layer is routed to the second DRB.
  • tunnel establishment methods can be applied to the transmission scenarios of multiple forwarding data packets. Whether the forwarding data packet contains the flow identifier and whether the forwarding data packet has the assigned sequence number can be forwarded through an appropriate tunnel. In order to avoid packet loss or repeated packet delivery during data pre-transmission, network performance is improved.
  • the method further includes: the first access network device releasing the first DRB, thereby saving system resources. .
  • the first access network device may send the second mapping relationship to the second access network device, and send the second mapping network device to the terminal.
  • the embodiment of the present application provides a data transmission method, including: a first access network device receives a forwarding data packet from a second access network device; and the first access network device forwards the data packet At least one data packet including the flow identifier is mapped to the first DRB, and the first DRB corresponds to the DRB of the second access network device.
  • the first DRB and the DRB of the second access network device respectively satisfy a first mapping relationship, where the first mapping relationship is a mapping relationship between a flow and a DRB in the second access network device.
  • the forwarding data packet includes at least one data packet: an allocated sequence number of the second access network device, and a data packet of a PDCP layer that does not receive an acknowledgement by the terminal; and the second access network device
  • the data packet of the PDCP layer of the sequence number is not allocated; the data packet of the SDAP layer of the second access network device.
  • the method further includes: the first access network device mapping, by the first access network device, a data packet that does not include a flow identifier in the forwarded data packet to the first DRB.
  • the method further includes: the first access network device mapping, in the second mapping relationship, the forwarding data packet to at least one of the first DRBs including the flow identifier The data packet is mapped to the second DRB, where the second mapping relationship is a mapping relationship between the flow and the DRB in the first access network device.
  • the first access network device sends the forwarding data packet to the terminal by using the first DRB or by using the first DRB and the second DRB.
  • the first access network device may establish a different type of tunnel with the second access network device for transmitting the forwarding data packet.
  • a specific tunnel type refer to the related description in the first aspect. Do not repeat them.
  • the various ways of establishing a tunnel can be applied to the transmission scenarios of multiple forwarding data packets. Whether the forwarding data packet contains a flow identifier or whether the forwarding data packet has a distribution sequence number can be forwarded through an appropriate tunnel. Therefore, packet loss or repeated packet transmission during data pre-transmission is avoided, and network performance is improved.
  • the method further includes: sending, by the first access network device, the data packet of the PDCP layer of the allocated sequence number in the forwarding data packet to the terminal by using the first DRB;
  • the first access network device sends, by using the second DRB, the data packet of the PDCP layer of the untransmitted sequence number in the forwarded data packet to the terminal.
  • the method further includes: the first access network device releasing the first DRB.
  • the first access network device may send the second mapping relationship to the second access network device, and send the second mapping network device to the terminal.
  • the first access network device sends a forwarding data packet to the terminal by using the first DRB corresponding to the second access network device, and further, in order to obtain better network performance, the first The access network device establishes a second DRB, where the second DRB is configured to transmit another data packet with the flow identifier other than the data packet mapped to the first DRB in the forwarding data packet, where the second DRB meets the first The mapping between the flow configured by the access network device and the DRB. Therefore, the forwarding data packet can be transmitted through different DRBs, and the transmission mode is flexible.
  • the data packet transmission mode can be selected according to the actual situation of the network, so that in the scenario of handover or dual connectivity, each base station independently configures the flow and the DRB.
  • the data loss or repeated packet issue caused by the mapping relationship improves the continuity of the terminal service and improves the communication quality.
  • the embodiment of the present application provides a data transmission method, including: a first access network device generates a forwarding data packet including a flow identifier; and the first access network device sends a data to a second access network device.
  • a forwarding packet containing a flow identifier is a forwarding packet containing a flow identifier.
  • the method further includes: the first access network device sends a first mapping relationship to the second access network device, where the first mapping relationship is the second The mapping between the flow and the DRB in the access network device.
  • the first access network device generates the forwarding data packet that includes the flow identifier, including:
  • the method further includes: the first access network device sending, to the second access network device, a forwarding data packet that does not include the flow identifier.
  • the forwarding data packet includes at least one data packet: an allocated sequence number of the first access network device, and a data packet of a PDCP layer that does not receive an acknowledgement by the terminal; a packet of the PDCP layer of the unassigned sequence number of the access network device; a packet of the SDAP layer of the first access network device.
  • the forwarding data packet includes: an out-of-order data packet received by the first access network device from the terminal.
  • the embodiment of the present application provides a data transmission method, including: a first access network device receives a forwarding data packet from a second access network device, where the forwarding data packet includes a flow identifier; and the forwarding data packet The data packet of the out-of-order PDCP layer received by the second access network device from the terminal is included.
  • the receiving, by the first access network device, the forwarding data packet from the second access network device includes: the first access network device from the second access network device by using a DRB-based tunnel Receive forwarded packets.
  • the method further includes: the first access network device receiving an uplink data packet from the terminal, where the uplink data packet includes at least one of the following data packets, and the terminal is not successfully a data packet of the PDCP layer of the allocated sequence number sent by the second access network device; a data packet of the PDCP layer of the terminal without an assigned sequence number; and a data packet of the SDAP layer of the terminal.
  • the receiving, by the first access network device, the uplink data packet from the terminal includes: receiving, by the first access network device, the uplink data packet by using the first DRB; or An access network device receives the uplink data packet by using the second DRB.
  • the receiving, by the first access network device, the uplink data packet from the terminal includes: receiving, by the first access network device, the terminal in the uplink data packet by using the first DRB device a data packet of a PDCP layer to which a sequence number has been allocated; the first access network device receives, by the second DRB, a data packet of a PDCP layer of an unassigned sequence number of the terminal in the uplink data packet and/or Or the data packet of the service data adaptation protocol SDAP layer.
  • the receiving, by the first access network device, the uplink data packet from the terminal includes: receiving, by the first access network device, the terminal in the uplink data packet by using the first DRB device a data packet of the PDCP layer; the first access network device receives, by using the second DRB, a data packet of a service data adaptation protocol SDAP layer of the terminal in the uplink data packet.
  • the first access network device receives, from the second access network device, a forwarding data packet that includes a flow identifier, where the forwarding data packet includes the second access An out-of-order packet received by a network device from a terminal.
  • the terminal can use the different DRBs to send the uplink data packet to the network side.
  • the transmission mode is flexible and diverse, and the data packet transmission mode can be selected according to the actual situation of the network, thereby avoiding the scenario of switching or dual connectivity, etc.
  • Each base station independently configures the data packet loss or duplicate packet issue caused by the mapping relationship between the flow and the DRB, improves the continuity of the terminal service, and improves the communication quality.
  • the embodiment of the present application provides a data transmission method, including: a terminal sends an uplink data packet to a first access network device, where the uplink data packet includes a flow identifier; and/or, the terminal accesses from the terminal
  • the network device receives the downlink data packet, where the at least one data packet of the downlink data packet includes a flow identifier, where the downlink data packet includes a forward data packet sent by the second access network device to the first access network device.
  • the sending, by the terminal, the uplink data packet to the access network device includes: sending, by the first DRB, the allocated serial number in the uplink data packet to the first access network device by using the first DRB a data packet of the PDCP layer; and the terminal sends, by using the second DRB, the data packet of the unallocated sequence number of the PDCP layer in the uplink data packet and/or the data packet of the SDAP layer to the first access network device
  • the first DRB satisfies the mapping relationship between the flow and the DRB in the second access network device; the second DRB satisfies the mapping relationship between the flow and the DRB in the first access network device.
  • the sending, by the terminal, the uplink data packet to the access network device includes: sending, by the terminal, the data packet of the PDCP layer in the uplink data packet to the access network device by using the first DRB; The terminal sends the data packet of the SDAP layer in the uplink data packet to the access network device by using the second DRB.
  • the receiving, by the terminal, the downlink data packet from the access network device includes: receiving, by the first DRB, the data packet that does not include the flow identifier in the downlink data packet from the first access network device by using the first DRB. And the terminal receives, by using the second DRB, the data packet that includes the flow identifier in the downlink data packet from the first access network device.
  • the receiving, by the terminal, the downlink data packet from the access network device includes: receiving, by the first DRB, the PDCP layer of the allocated sequence number in the downlink data packet from the first access network device by using the first DRB.
  • the data packet, and the data packet of the PDCP layer and/or the SDAP layer of the downlink data packet and the unassigned sequence number of the downlink data packet are received from the first access network device by using the second DRB.
  • the first DRB in the implementation manner of the foregoing fifth aspect meets the mapping relationship between the flow and the DRB in the second access network device; the second DRB meets the information in the first access network device.
  • the mapping relationship between the flow and the DRB is the mapping relationship between the flow and the DRB.
  • an embodiment of the present application provides an access network device, where the access network device has the first access network device in any one of the foregoing data transmission methods, or has any one of the foregoing data transmission methods.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more units or means corresponding to the functions described above.
  • the structure of the access network device includes a processor and a transceiver, and the processor is configured to support the access network device to perform a corresponding function in the foregoing data transmission method.
  • the transceiver is configured to support communication between the access network device and the terminal, and send information or instructions involved in the foregoing data transmission method to the terminal.
  • the access network device can also include a memory for coupling with the processor that retains the necessary program instructions and data for the access network device.
  • the access network device can also include a communication interface for communicating with other network devices.
  • the access network device is a base station.
  • the embodiment of the present application provides a terminal, where the access network device has a function of implementing terminal behavior in any one of the foregoing data transmission methods.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more units or means corresponding to the functions described above.
  • the structure of the terminal includes a processor and a transceiver, and the processor is configured to support the access network device to perform a corresponding function in the foregoing data transmission method.
  • the transceiver is configured to support communication between the access network device and the terminal, and send information or instructions involved in the foregoing data transmission method to the access network device.
  • the terminal may also include a memory for coupling with the processor, which stores program instructions and data necessary for the terminal.
  • an embodiment of the present invention provides a communications system, including the access network device and the terminal in the foregoing aspects.
  • the embodiment of the present application provides a computer readable storage medium, where the computer readable storage medium stores instructions, when executed on a computer, causing the computer to perform the data transmission described in any of the above aspects. method.
  • an embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing a computer to perform the data transmission method of any of the above aspects.
  • a flexible and diverse forwarding packet transmission mode is adopted, so that data loss or duplication caused by the mapping relationship between the flow and the DRB is independently configured in each scenario of the handover or the dual connectivity.
  • the problem of issuing a package improves the continuity of the terminal business and improves the communication quality.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a data transmission method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a signaling flow of a data transmission method according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of an access network device 700 according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of an access network device 800 according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of an access network device 900 according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of an access network device 1000 according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a terminal 1100 according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of an access network device 1200 according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of an access network device 1300 according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of a terminal 1400 according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of a communication system 1500 according to an embodiment of the present application.
  • the techniques described in the embodiments of the present application can be applied to the 5G (the fifth generation) communication system, or other next generation communication systems, such as the New Radio Access Network (New RAN, NR).
  • 5G the fifth generation
  • NR New Radio Access Network
  • the access network device in the embodiment of the present application includes a base station device in the NR, such as a gNB, a trasmission point (TRP), or a centralized unit (CU) and a distributed unit (DU).
  • a base station device wherein the CU can also be referred to as a control unit.
  • the LTE eNB may also be referred to as an eLTE eNB when the base station device in the long term evolution (LTE) system, that is, the evolved node B (eNB) can connect to the 5G core network (5G-Core, 5G CN).
  • LTE long term evolution
  • eNB evolved node B
  • the eLTE eNB is an LTE base station device that is evolved on the basis of the LTE eNB, and can directly connect to the 5G CN.
  • the eLTE eNB also belongs to the base station device in the NR.
  • the access network device may also be an access point (AP), or other network device having the capability of communicating with the terminal and the core network.
  • the type of the access network device is not limited in this embodiment.
  • the 5G CN described in the embodiment of the present application may also be referred to as a new core network, or a 5G New Core, or a next generation core (NGC).
  • the 5G-CN is set independently of the existing core network, such as an evolved packet core (EPC).
  • EPC evolved packet core
  • the terminal involved in the embodiment of the present application may include a handheld device having a wireless communication function, an in-vehicle device, a wearable device, a computing device, or other processing device connected to the wireless modem, and various forms of user equipment (UE) ), mobile station (MS), terminal equipment, and the like.
  • UE user equipment
  • MS mobile station
  • the embodiment of the present application defines that the one-way communication link of the access network to the terminal is a downlink, the data transmitted on the downlink is downlink data, and the transmission direction of the downlink data is called a downlink direction; and the terminal to the access network
  • the one-way communication link is an uplink, and the data transmitted on the uplink is uplink data, and the transmission direction of the uplink data is called an uplink direction.
  • the source access network device in the embodiment of the present application refers to an access network device device that the terminal currently accesses or camps on, and the terminal will switch from the access network device device to other access network device devices.
  • the target access network device in the embodiment of the present application refers to an access network device device to which the terminal will be handed over.
  • Multiple appearing in the embodiments of the present application means two or more.
  • connection in the embodiment of the present application refers to various connection modes such as a direct connection or an indirect connection, so as to implement communication between devices, which is not limited in this embodiment.
  • the "network” and the “system” appearing in the embodiment of the present application express the same concept, and the communication system is a communication network.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • the communication system includes a core network device 110, a first access network device 120, a second access network 130, and a terminal 140, wherein the first access network device 120 and the second access network device 130 Communicating with the core network device 110 through a communication interface, for example, the NG interface shown in FIG. 1; and a communication interface may exist between the first access network device 120 and the second access network device 130.
  • a communication interface may exist between the first access network device 120 and the second access network device 130.
  • the Xn interface shown in Figure 1 is used to exchange information between devices.
  • the core network device 110 is a core network device in the 5G CN, and includes one or more functional entities that are independently set or integrated.
  • the core network device 110 can be controlled by a control plane (CP) network element and a user plane. (user plane, UP) network element, for example, user plane gateway (UPGW).
  • CP control plane
  • UP user plane gateway
  • the foregoing first access network device 120 or the second access network device 130 is any one of the gNB or the eLTE eNB, which is not limited in this embodiment.
  • the first access network device 120 is a gNB, and the second access network device 130 is a gNB; or the first access network device 120 is an eLTE eNB, and the second access network device 130 is an eLTE eNB; or The first access network device 120 is a gNB, and the second access network device 130 is an eLTE eNB; or the first access network device 120 is an eLTE eNB, and the second access network device 130 is a gNB.
  • the core network device 110 communicates with the first access network device 120 and/or the second access network device 130 respectively through a protocol data unit (PDU) session, and one PDU session may include multiple flows.
  • the QoS requirements of different flows may be the same or different, and the core network 110 provides the QoS requirements of the flows to the first access network device 120 and/or the second access network device 130, by the first access network device 120 and/or Or the second access network device 130 completes the mapping to the DRB, and accordingly, the flows included in one DRB have the same or similar QoS requirements.
  • the access network device may establish at least one DRB for each session of the accessed terminal, where a default DRB (default DRB) is included. The DRB is established between the access network device and the terminal for transmitting air interface data.
  • a flow with certain QoS requirements may be referred to as QoS flow, and a QoS flow is composed of at least one data packet.
  • QoS flow corresponds to one or more service types.
  • the QoS flow is simply referred to as "stream" in the following embodiments.
  • the terminal 140 switches the accessed access network device during the mobile process to obtain the best communication service. For example, when the terminal 140 moves from the currently accessed first access network device 120 to the signal coverage of the second access network device 130, the terminal 140 may initiate a handover procedure, and the first access network device 120 switches to The second access network device 130, in the handover process, the first access network device 120 may send the flow prepared for transmission with the terminal 140 to the second access network device 130, where the second access network device 130 may The stream prepared for transmission with the terminal 140 is mapped to the DRB that conforms to the QoS requirement of the stream, and then the stream is transmitted by the DRB and the terminal.
  • the terminal 140 accesses the first access network device 120 and the second access network device 130 simultaneously, when the first access network device 120 determines that a part of the service is to be determined.
  • the first access network device 120 may send the flow corresponding to the part of the service to the second access network device 130, and the second access network device 130 may map the flow to match The DRB required by the QoS of the flow, and then the transmission of the flow by the DRB and the terminal.
  • the access network device connected by the terminal may be divided into: a primary access network device having a control plane function and a user plane function between the terminal, and a user plane data transmission between the terminal and the terminal. Secondary access network equipment.
  • the primary access network device can control the traffic of the terminal to migrate between the primary access network device and the secondary access network device, and the traffic corresponding to the service is forwarded between the access network device and the air interface is transmitted, and the primary access network is not distinguished.
  • the device is also a secondary access network device. Therefore, the first access network device 120 and the second access network device 130 need not be limited to be a primary access network device or a secondary access network device. It can be understood that the terminal can also access one primary access network device and multiple secondary access network devices, and details are not described herein.
  • the first access network device 120 transmits the data packet related to the terminal 140 to the second access network device 130, and the second access network device 130 continues to perform the data with the terminal 140.
  • the transmission process of the data packet may be referred to as data forwarding, and may also be referred to as data back propagation or data forwarding.
  • a tunnel may be established between the first access network device 120 and the second access network device 130 for transmitting data pre-transmitted data packets.
  • the tunnel may be established by the DRB; or may be established according to the SDAP entity or the session; or two tunnels may be established at the same time, that is, one is established according to the DRB, and one is established according to the SDAP entity or the session, wherein the tunnel established by the DRB may be used for Transmitting data packets in the PDCP layer corresponding to the DRB.
  • a tunnel established according to a session or a SDAP entity may be used to transmit a data packet buffered in the SDAP or to transmit a data packet carrying the flow identifier in the PDCP layer.
  • the SDAP layer refers to a user plane protocol layer established on the PDCP layer of the user plane in a protocol stack connected to the access network side of the NGC.
  • the SDAP layer can be used to map a flow from a non-access stratum (NAS) to a DRB of an access stratum (AS).
  • An SDAP entity is an instance established by the SDAP layer to complete the functions of the SDAP layer.
  • the SDAP entity is also responsible for adding a flow identifier to the air interface protocol stack.
  • the flow identifier includes an upstream identifier and a downstream identifier, and is used to identify an uplink data stream or a downlink data stream.
  • the access network device can map different flows to the same or different DRBs according to the QoS requirements of each DRB, that is, establish a mapping relationship between the flows and the DRBs. For example, if the stream 1 transmitted by the core network to the access network device is a stream corresponding to a machine type communication (MTC) service, and the stream 2 is a stream corresponding to a mobile broadband (MBB) service, the access is regarded as the access.
  • MTC machine type communication
  • MBB mobile broadband
  • the network device supports different types of services. Stream 1 and stream 2 can be mapped to the same DRB of the access network device, for example, the default DRB.
  • the SDAP entity or the SDAP layer can also be referred to by other names, such as a packet data association protocol (PDAP) entity or layer, as long as it is a protocol layer that conforms to the above description of the definition and function of the SDAP layer. All belong to the scope protected by the SDAP layer described in the embodiment of the present application.
  • PDAP packet data association protocol
  • each access network device independently sets the mapping relationship between the flow and the DRB, after the data packet transmitted by the foregoing data is sent to the second access network device 130, if the second access network device 130 still follows the first access network device 120.
  • the mapping between the configured flow and the DRB transmits the above data packet, which may result in packet loss or repeated packet transmission, which affects the continuity of the terminal service.
  • the application embodiment proposes a data transmission method.
  • the “first access network device” or the “second access network device” appearing in the following embodiments all have the same meaning, and will not be described below.
  • the first access network device in the embodiment of the present application may be a target access network device
  • the second access network device may be a source access network device.
  • the second access network device in the embodiment of the present application may offload part of the service to the first access network device, and the first access network device and the terminal perform the transmission of the service. .
  • the second access network device is the primary base station and the first access network device is the secondary base station; or, when the secondary cell group is used (second cell)
  • MCG bearer master cell group bearer
  • the second access network device is the secondary base station and the first access network device is the primary base station.
  • FIG. 2 is a schematic flowchart diagram of a data transmission method according to an embodiment of the present application.
  • the data transmission method provided by the present application can be applied to various types of communication scenarios, such as a handover process of a terminal or a dual connection process, and the data pre-allocation process between the base stations, which is not limited in this embodiment.
  • the method comprises the following steps:
  • the first access network device receives the forwarding data packet from the second access network device.
  • the forwarded data packet is a data pre-transmission data packet sent by the second access network device to the first access network device, that is, the data sent by the second access network device to the first access network device during the data pre-transmission process. package.
  • the forwarded data packet includes at least one type of data packet: an allocated sequence number (SN) of the second access network device, and data of a PDCP layer that is not received by the terminal to be acknowledged.
  • SN allocated sequence number
  • a packet, a data packet of a PDCP layer of an unassigned sequence number of the second access network device, and a data packet of a SDAP layer of the second access network device are examples of data packets.
  • the data packet of the PDCP layer includes a PDCP PDU and a PDCP SDU.
  • the second access network device may decrypt the PDCP PDU, remove the protocol header, and the like.
  • the PDCP SDU of the reserved sequence number is obtained. Therefore, the data packets of the PDCP layer are forwarded between the base stations in the form of PDCP SDU, including the PDCP SDU with the assigned sequence number and the PDCP SDU with the unassigned sequence number.
  • the serial number of the PDCP SDU refers to a PDCP layer serial number, which may be represented as a PDCP SN.
  • the first access network device maps at least one data packet that includes the flow identifier to the first DRB, where the first DRB corresponds to the DRB of the second access network device. .
  • the first access network device may map all data packets in the forwarded data packet that contain the flow identifier or a data packet that partially includes the flow identifier to the first DRB.
  • the first DRB and the DRB of the second access network device respectively satisfy a first mapping relationship, where the first mapping relationship is a mapping relationship between a flow and a DRB in the second access network device.
  • the first DRB is established by the first access network device, and is used for data transmission between the first access network device and the terminal.
  • the first access network device may establish a mapping DRB (reflect DRB).
  • the mapping DRB may continue the transmission state of one of the second access network devices and continue to transmit the data packets on the DRB in the second access network device.
  • the DRB in the second access network device corresponding to the mapping DRB may be referred to as a “third DRB”.
  • the mapping DRB has the same PDCP SN state and a hyper frame number (HFN) state as the third DRB, wherein the PDCP SN state and the HFN state may indicate the transmission and reception states of the PDCP packets on the DRB.
  • the mapping DRB is the above-mentioned "first DRB".
  • the first access network device receives the first mapping relationship from the second access network device.
  • the first access network device maps the data packet that does not include the flow identifier in the forwarding data packet to the first DRB.
  • the first access network device After the first access network device maps some or all of the data packets in the forwarding data packet to the first DRB, the first access network device sends a corresponding data packet to the terminal by using the first DRB, for example, The data packet including part or all of the forwarded data packet containing the flow identifier and all data packets not including the flow identifier are sent by the first DRB.
  • the method further includes: the first access network device mapping the forwarded data packet to be outside the first DRB according to the second mapping relationship. At least one data packet including the flow identifier is mapped to the second DRB; wherein the second mapping relationship is a mapping relationship between the flow and the DRB in the first access network device.
  • the second mapping relationship may include a correspondence between a flow identifier of each flow in the first access network device and a DRB.
  • the first access network device may configure a mapping relationship between the flow and the DRB according to the QoS requirement, and establish the second DRB according to the mapping relationship.
  • the DRB established by the access network device according to the mapping relationship between the flow and the DRB configured by the access network device may also be referred to as a new DRB (new DRB).
  • the QoS requirement includes a QoS parameter.
  • the QoS parameters may be configured by the source access network device and sent to the target access network device; when the access network devices pass through the core network For the handover, the QoS parameters may be sent from the source base station to the core network device, and then sent by the core network device to the target access network device, wherein the core network device may modify the QoS parameters.
  • the first access network device may send, by using the first DRB and the second DRB, the data packet that includes the flow identifier in the forwarding data packet, for example, a part of the data packet including the flow identifier is sent to the terminal by using the first DRB, and the other The data packet containing the flow identifier is sent to the terminal through the second DRB.
  • the first access network device may send, by using the first DRB, a data packet of the PDCP layer that has the assigned sequence number in the forwarding data packet that includes the flow identifier, and send the included flow to the terminal by using the second DRB.
  • the packet of the PDCP layer of the sequence number is not assigned in the identified forwarding packet.
  • the data packet including the flow identifier may be routed to a different DRB by a SDAP entity of the first access network entity.
  • the second DRB and the first DRB may be the same or different. If the first mapping relationship and the second mapping relationship are the same, the first DRB is the same as the second DRB. Specifically, one DRB in the first access network device may first send the received forwarding data packet as a mapping DRB, and then send the data packet received from the core network as a new DRB, and divide the same DRB into a mapping in a time dimension. The DRB and the new DRB can use different mappings between different flows and DRBs for receiving different data packets at different times. If the first mapping relationship and the second mapping relationship are different, the first DRB and the second DRB may be two independently established DRBs.
  • the first access network device and the terminal may release the first DRB, thereby reducing the overhead of the terminal and the first access network device.
  • the first access network device may notify the terminal to release the first DRB.
  • the terminal receives the notification message of releasing the first DRB from the first access network device, and releases the configuration of the first DRB.
  • the terminal can confirm that the sending of the downlink data packet on the first DRB is completed.
  • the notification message can be viewed as an end marker for indicating the end of the transmission of the downstream data packet in the first DRB.
  • the first access network device may send the second mapping relationship to the second access network device, and send the second mapping network device to the terminal.
  • the first access network device receives the forwarded data packet by using a tunnel with the second access network device.
  • the tunnel between the first access network device and the second access network device may have different establishment manners.
  • the manner of establishing the tunnel is not particularly limited in the embodiment of the present application.
  • the tunnel is a tunnel established based on DRB.
  • the DRB-based tunnel may be established between the third DRB of the second access device and the mapping DRB of the first access device, or may be established in the third DRB and the new DRB of the first access device. between.
  • One or more DRB-based tunnels may be established between the first access network device and the second access network device.
  • the DRB-based tunnel may be used to transmit data packets of the PDCP layer.
  • the first access network device may map the data packet not included in the flow identifier received by the DRB based tunnel to the first DRB, and map the data packet including the flow identifier received through the DRB based tunnel establishment. Go to the second DRB.
  • the tunnel is a tunnel based on session establishment.
  • the session-based tunnel may also be referred to as a tunnel established based on a SDAP entity, and the tunnel is established between a SDAP entity of the first access device and a SDAP entity of the same session of the second access network device.
  • the session-based tunnel may be used to transmit a data packet carrying a flow identifier and not having a sequence number in a forwarded data packet of all DRBs in the session.
  • the first access network device routes, by the SDAP entity, a data packet of the PDCP layer of the allocated sequence number received from the session establishment tunnel to the first DRB; and the unassigned sequence number is The data packet of the PDCP layer or the data packet of the SDAP layer is routed to the second DRB.
  • the tunnel includes a DRB-based tunnel and a session-based tunnel.
  • the DRB-based tunnel is used to transmit a data packet of a PDCP layer
  • the session-based tunnel is used to transmit a data packet of the SDAP layer.
  • the DRB-based tunnel is used to transmit the data packet of the allocated sequence number buffered in the PDCP layer of the second access network device.
  • the session-based tunnel is used to transmit a data packet carrying a flow identifier in a forwarding data packet, including a data packet of a SDAP layer of the second access network device, and/or a second access network device A packet buffered in the PDCP layer that carries a stream identifier and is not assigned a sequence number.
  • the first access network device may map the data packets received through the DRB-based tunnel to the first DRB and map the data packets received through the session-based tunnel to the second DRB.
  • the data packet of the SDAP layer includes a data packet buffered by the SDAP layer
  • the data packet of the PDCP layer includes a data packet buffered by the PDCP layer
  • the establishing of the DRB by the first access network device may be performed at the same time.
  • the handover request message sent by the second access network device to the first access network device includes establishing a tunnel.
  • the required information and the information required to establish the DRB, after the first access network device receives the relevant information, can perform the corresponding operation.
  • the first access network device receives the forwarding data packet from the second access network device; the first access network device may include at least one of the forwarding data packets The data packet is mapped to the first DRB established by the first access network device; wherein the first DRB corresponds to the DRB of the first access network device; further, in order to obtain better network performance, the first access
  • the second DRB is configured to transmit a data packet with a flow identifier other than the data packet mapped to the first DRB in the forwarded data packet, where the second DRB satisfies the first access
  • the mapping between the flow configured by the network device and the DRB Therefore, the forwarding data packet can be transmitted through different DRBs, and the transmission mode is flexible.
  • the data packet transmission mode can be selected according to the actual situation of the network, so that in the scenario of handover or dual connectivity, each base station independently configures the flow and the DRB.
  • the data loss or repeated packet issue caused by the mapping relationship improves the continuity of the terminal service and improves the communication quality.
  • FIG. 3 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • the data transmission method provided in this embodiment is applicable to various scenarios of a data transmission process between the base stations, such as a handover process or a dual connection process of the terminal, and details are not described herein.
  • the method comprises the following steps:
  • S301 The first access network device receives the forwarding data packet from the second access network device.
  • the first access network device maps the data packet that does not include the flow identifier in the forwarding data packet to the first DRB, where the first DRB corresponds to the DRB of the second access network device (referred to as "Third DRB").
  • the first DRB and the third DRB respectively satisfy a first mapping relationship, where the first mapping relationship is a mapping relationship between a flow and a DRB in the second access network device.
  • the first access network device receives the first mapping relationship from the second access network device.
  • the first access network device maps, according to the second mapping relationship, the data packet that includes the flow identifier in the forwarding data packet to the second DRB, where the second mapping relationship is the first The mapping between the flow and the DRB in the access network device.
  • the first DRB is a mapping DRB
  • the second DRB is a new DRB.
  • first DRB and the second DRB are respectively established by the first access network device, and the first access network device establishes a sequence in which the steps of the first DRB and the second DRB are not performed.
  • first mapping relationship and the second mapping relationship For a detailed description of the first mapping relationship and the second mapping relationship, reference may be made to the related content of the embodiment shown in FIG. 2, and details are not described herein.
  • the first access network device routes, by using a SDAP entity, the data packet that includes the flow identifier in the forwarding data packet to the second DRB.
  • step S302 and the step S303 are not performed in the order of execution, for example, S302 may be performed first, and then S303 may be performed; S303 may be performed first, then S302 may be performed; or S302 and S303 may be performed simultaneously, and the present application is implemented. This example does not specifically limit this.
  • the method further includes: the first access network device sends, by using the first DRB, the allocated sequence number in the forwarding data packet to the terminal, and does not include the flow.
  • the identified data packet ; the first access network device sends, by using the second DRB, a data packet in the forwarding data packet that is not assigned a sequence number and includes a flow identifier.
  • the data packet may be a data packet of a PDCP layer, and the serial number is a PDCP SN.
  • the method further includes: sending, by the first access network device, the data packet that does not include the flow identifier in the forwarding data packet to the terminal by using the first DRB;
  • the first access network device sends, by using the second DRB, a data packet that includes a flow identifier in the forwarded data packet to the terminal.
  • the first access network device and the terminal may release the first DRB, respectively, thereby reducing the overhead of the terminal and the first access network device.
  • the first access network device may send the second mapping relationship to the second access network device, and send the second mapping network device to the terminal.
  • the first access network device receives the forwarded data packet by using a tunnel with the second access network device.
  • the tunnel between the first access network device and the second access network device may have different establishment manners.
  • the first access network device receives the forwarded data packet from the second access network device through a DRB-based tunnel and a session-based tunnel.
  • the DRB-based tunnel is used to transmit the data packet of the allocated sequence number buffered in the PDCP layer of the second access network device.
  • the session-based tunnel is used to transmit a data packet carrying a flow identifier in a forwarding data packet, including a data packet of a SDAP layer of the second access network device, and/or a second access network device A packet buffered in the PDCP layer that carries a stream identifier and is not assigned a sequence number.
  • the first access network device receives the forwarded data packet from the second access network device through a tunnel established based on the DRB.
  • the first access network device receives the data packet including the flow identifier in the forwarded data packet from the second access network device by using a tunnel established based on the session.
  • the first access network device routes, by the SDAP entity, the data packet of the PDCP layer of the allocated sequence number received from the session-established tunnel to the first DRB; and the PDCP that does not allocate the sequence number
  • the data packet of the layer or the data packet of the SDAP layer is routed to the second DRB.
  • the first access network device may release the first DRB to save resources, and a detailed description about releasing the first DRB may be referenced.
  • the related content in the embodiment shown in FIG. 2 is not described herein.
  • each access network device can independently set the mapping relationship between the flow and the DRB, the data packet with the flow identifier is mapped to the second DRB for transmission, and there will be no
  • the data packet of the flow identifier is mapped to the first DRB for transmission, and the data packet transmission mode can be selected according to the actual situation of the network, so as to avoid the mapping relationship between the flow and the DRB of each access network device in the scenario of switching or dual connectivity.
  • the resulting data packet loss or repeated packet issue improves the continuity of the terminal service and improves the communication quality.
  • FIG. 4 is a schematic flowchart diagram of a data transmission method according to an embodiment of the present application.
  • the data transmission method provided in this embodiment is applicable to various scenarios of a data pre-allocation process between base stations, such as a handover process of a terminal or a dual connection process, and is not described herein.
  • the method comprises the following steps:
  • the first access network device receives the forwarded data packet from the second access network device, where the forwarded data packet includes a flow identifier, where the forwarded data packet includes the out-of-order received by the second access network device from the terminal. Packet.
  • the forwarded data packet is a data packet of the out-of-order PDCP layer received by the second access network device from the terminal.
  • the sequence number of the last PDCP SDU received by the second access network device is SN, that is, the PDCP SDUs before the sequence number is SN (..., SN-1, SN) are received in order, then
  • the out-of-order PDCP SDU after the sequence number is SN received by the second access network device is a data packet that needs to be forwarded by data.
  • the second access network device receives the sequence after the PDCP SDU with the sequence number SN.
  • the PDCP SDUs numbered SN+3, SN+4, and SN+6 require data pre-transmission.
  • the first access network device sends the received forwarding data packet to the core network device.
  • the first access network device receives the forwarded data packet by using a tunnel with the second access network device.
  • the tunnel may be a DRB-based tunnel between the first access network device and the second access network device.
  • DRB-based tunnel refer to the related description of the DRB-based tunnel in other embodiments of the present application.
  • the method further includes: the first access network device receives an uplink data packet from a terminal, where the uplink data packet includes at least one of the following data packets: a data packet of a PDCP layer of an allocated sequence number that is not successfully transmitted by the terminal to the second access network device; a data packet of a PDCP layer of an unassigned sequence number of the terminal; a data packet of the SDAP layer of the terminal .
  • the terminal may request the first access network device to release the first DRB.
  • the first access network device may consider that the request sent by the terminal to release the first DRB is an end tag, and the request is used to indicate the end of the uplink data packet transmission in the first DRB.
  • the uplink data packet may be sent to the first access network device by using different sending manners.
  • the first access network device receives the uplink data packet by using the first DRB.
  • the first access network device receives the uplink data packet by using the second DRB.
  • the first access network device receives, by using the first DRB, a data packet of a PDCP layer of an allocated sequence number of the terminal in the uplink data packet; and the first access network device Receiving, by the second DRB, a data packet of an unallocated sequence number and/or a data packet of an SDAP layer in a PDCP layer of the terminal in the uplink data packet.
  • the first access network device receives, by using the first DRB, a data packet of a PDCP layer of the terminal in the uplink data packet, and the first access network device passes the second The DRB receives the data packet of the SDAP layer of the terminal in the uplink data packet.
  • the first DRB is a mapping DRB
  • the second DRB is a new DRB.
  • the first access network device receives, from the second access network device, a forwarding data packet that includes a flow identifier, where the forwarding data packet includes the second access An out-of-order packet received by a network device from a terminal.
  • the terminal can use the different DRBs to send the uplink data packet to the network side.
  • the transmission mode is flexible and diverse, and the data packet transmission mode can be selected according to the actual situation of the network, thereby avoiding the scenario of switching or dual connectivity, etc.
  • Each base station independently configures the data packet loss or duplicate packet issue caused by the mapping relationship between the flow and the DRB, improves the continuity of the terminal service, and improves the communication quality.
  • FIG. 5 is a schematic flowchart of a data transmission method according to an embodiment of the present application.
  • the data transmission method provided in this embodiment is applicable to various scenarios of a data transmission process between the base stations, such as a handover process or a dual connection process of the terminal, and details are not described herein.
  • the method comprises the following steps:
  • the second access network device generates a forwarding data packet that includes the flow identifier.
  • the second access network device sends the forwarded data packet that includes the flow identifier to the first access network device.
  • the forwarding data packet includes at least one data packet: an allocated sequence number of the second access network device, and a data packet of a PDCP layer that does not receive an acknowledgement by the terminal; The data packet of the PDCP layer of the unassigned sequence number of the second access network device; the data packet of the service data adaptation protocol SDAP layer of the first access network device.
  • the second access network device further sends, to the first access network device, a forwarding data packet that does not include a flow identifier.
  • the second access network device may send the forwarded data packet to the first access network device by using a different type of tunnel.
  • a different type of tunnel For details about the various types of tunnels and the forwarding of the forwarding packets on the various types of tunnels, reference may be made to the related content of other embodiments of the present application, and details are not described herein.
  • the first access network device can send a downlink data packet including a forwarding data packet to the terminal.
  • the first access network device may forward the data packet according to the content (for example, forwarding the data packet with or without the flow identifier, or forwarding)
  • the data packet has a distribution sequence number, and the type of the tunnel carrying the forwarded data packet, and the forwarding packet is mapped to the corresponding DRB for transmission.
  • the specific description of the first access network device mapping the forwarded data packet to the corresponding DRB may be The related content of other embodiments of the present application is not described herein.
  • the first access network device sends other downlink data packets acquired from the core network to the terminal.
  • the PDCP entity of the second access network device acquires the flow identifier, so that the second access network device may add a flow identifier to the forwarded data packet, and generate The forwarding packet includes a flow identifier, and the first access network device parses the forwarded data packet to obtain the flow identifier.
  • the second access network device obtains the flow identifier of the data packet according to the correspondence between the service access point (SAP) and the flow identifier.
  • the second access network device establishes one or more SAPs between the SDAP entity and the PDCP entity, and the PDCP entity caches the PDCP PDU or the PDCP SDU according to the SAP and the flow identifier respectively, where each SAP corresponds to one flow.
  • the second access network device may send the PDCP PDU or the PDCP SDU to the SDAP entity according to the SAP, and the SDAP entity may obtain the flow of the data packet of the PDCP layer according to the correspondence between the SAP and the flow.
  • logo the service access point
  • the PDCP entity may also obtain a flow identifier based on the SAP information.
  • the forwarding data packet includes a PDCP PDU and a PDCP SDU, where the PDCP PDU is subjected to a removal protocol header, decryption, and the like to generate a PDCP SDU carrying a sequence number.
  • the second access network device acquires the flow identifier of the data packet according to the cache location of the data packet.
  • the SDAP entity of the second access network device sends the flow identifier of the data packet to the PDCP entity, and the PDCP entity establishes a correspondence between the flow identifier and the data packet cache location.
  • the PDCP entity may receive the received PDCP according to the flow identifier.
  • the SDU is cached, and the second access network device obtains the cache location of the forwarded data packet, where the cached location of the forwarded data packet corresponds to the flow identifier of the forwarded data packet; the second access network The device obtains a flow identifier of the data packet according to a cache location of the data packet.
  • the SDAP layer of the second access network device further includes indication information, where the indication information is used to indicate whether the PDCP layer adds the flow identifier in the PDCP PDU and sends the information in the air interface.
  • the indication information indicates that the flow identification is not added, and the PDCP PDU is generated by the data identifying the flow identifier in the SDAP header. Since the PDCP PDU does not contain a flow identifier, data overhead is saved.
  • the SDAP entity of the second access network device may add a flow identifier to the received data packet, and indicate that the flow identifier is used only for the handover process, so that the first access network device may The outflow identifier is restored according to the received forwarding packet.
  • the SDAP entity of the second access network device may add a flow identifier to the received data packet, for example, starting from a frozen transmission state of the second access network device, where the frozen transmission state refers to The two access network devices no longer send data to the terminal, and the SDAP entity adds a flow identifier to the data packets sent to the PDCP layer, so that the first access network device can recover the outflow identifier according to the received forwarding data packet.
  • the second access network device determines the flow identifier according to the sequence number included in the forwarded data packet. Specifically, the SDAP entity of the second access network device caches the data packet, and configures a SDAP sequence number for the buffered data packet, and sends the data packet configured with the SDAP sequence number to the PDCP entity. And if the PDCP entity successfully sends the data packet including the PDCP SN to the first access network device, sending an indication to the SDAP layer, and after receiving the indication, the SDAP layer deletes the data packet corresponding to the data packet including the PDCP SN.
  • the SDAP entity of the second access network device is The SDAP sequence number of the data packet received by the forwarded data packet from the PDPC layer matches the flow identifier of the data packet.
  • the forwarding data packet includes: an out-of-order data packet received by the first access network device from the terminal.
  • Forward packets in the upstream direction contain flow identifiers.
  • the second access network device may send the forwarded data packet in the uplink direction to the first access network device by using the tunnel established by the DRB, and details are not described herein.
  • the first access network device may send the forwarded data packet to the core network.
  • the uplink data packet can be sent to the first access network device by using different DRBs.
  • FIG. 6 is a schematic diagram of a signaling flow of a data transmission method according to an embodiment of the present application.
  • the embodiment shown in FIG. 6 illustrates the data transmission method provided by the embodiment of the present application by taking the terminal from the source base station to the target base station as an example. It can be understood that the embodiment shown in FIG. 6 is the embodiment shown in FIG. 2 to FIG.
  • the source base station is an example of a second access network device in the embodiment shown in FIG. 2 to FIG. 5, and the target base station is the first one in the embodiment shown in FIG. 2-5.
  • the embodiments provided in the present application can be cross-referenced.
  • the method comprises the following steps:
  • S601 The terminal sends a measurement report to the source base station.
  • the source base station determines to trigger the handover process according to the received measurement report.
  • the source base station sends a first mapping relationship to the target base station.
  • the first mapping relationship refers to a mapping relationship between a flow configured by a source base station and a DRB.
  • the first mapping relationship refers to a mapping relationship between a flow configured by a source base station and a DRB.
  • the first mapping relationship is included in the signaling or the message sent by the source base station to the target base station in a handover process, such as a handover request message, which is not limited in this embodiment.
  • the target base station may establish a DRB with the terminal, including a mapping DRB of the transmission state of the DRB of the source base station (ie, FIG. 2 or FIG. 3 above).
  • the first DRB in the embodiment in addition to mapping the DRB, the target base station may also establish a new bearer according to the mapping relationship between the flow and the DRB configured by itself (that is, the second in the embodiment shown in FIG. 2 or FIG. 3 above).
  • the mapping DRB and the new DRB reference may be made to related content of other embodiments of the present application, and details are not described herein.
  • the target base station sends a second mapping relationship to the source base station.
  • the second mapping relationship may be included in the signaling or the message sent by the target base station to the source base station in a handover process such as a handover request response message, which is not limited in this embodiment of the present application.
  • the second mapping relationship refers to a mapping relationship between a flow configured by the target base station and a DRB.
  • the second mapping relationship refers to a mapping relationship between a flow configured by the target base station and a DRB.
  • S605 The source base station sends a handover command to the terminal.
  • the handover command may include the second mapping relationship, and the terminal may acquire the second mapping relationship.
  • the second mapping relationship may be the same as the first mapping relationship, or may be different.
  • the mapping relationship between the DRB and the flow configured by the target base station may be the same as the mapping between the DRB and the flow configured by the source base station, and the mapping relationship between the DRB and the flow configured by the source base station may be the same. It may also be different.
  • the response message and the handover command further include a third mapping relationship, where the third mapping relationship refers to a mapping relationship between the mapping DRB configured by the target base station and the DRB configured by the target base station.
  • the source base station sends the air interface transmission status of the PDCP layer to the target base station.
  • the air interface transmission state of the PDCP layer refers to a transmission state and a reception state of a data packet of the PDCP layer in the DRB of the target base station.
  • the transmission status of the uplink data packet includes: a sequence number of the first lost PDCP SDU, and a reception status of the PDCP SDU between the first lost PDCP SDU and the received last PDCP SDU, where the reception status is specific It means receiving a packet or not receiving a packet.
  • the transmission status of the downlink data packet includes: a sequence number of a next PDCP SDU to which the target base station needs to allocate a sequence number, the sequence number including the PDCP SN and the HFN.
  • the source base station sends a forwarding data packet to the target base station.
  • the forwarding data packet includes a forwarding data packet in an uplink direction, and/or a forwarding data packet in a downlink direction.
  • a forwarding data packet in an uplink direction and/or a forwarding data packet in a downlink direction.
  • the source base station may send the forwarded data packet to the target base station by using a tunnel with the target base station.
  • a tunnel with the target base station.
  • the PDCP entity of the source base station acquires the flow identifier of the data packet, so that the source base station can add a flow identifier to the forwarded data packet, and the target base station can map the forwarded data packet to the corresponding DRB according to the flow identifier.
  • the data packet that the source base station generates the flow identifier reference may be made to the related content in the embodiment shown in FIG. 5, and details are not described herein.
  • S608 The terminal accesses the target base station.
  • S609 The target base station performs path switching.
  • the method further includes: the target base station notifying the control plane management network element of the core network, and the control plane management network element notifying the user plane network element, and sending the subsequent data packet related to the terminal to the target base station.
  • the method further includes: S6010: the terminal performs data communication with the target base station.
  • the data communication includes uplink data transmission and/or downlink data transmission.
  • the target base station may send the forwarded data packet in the downlink direction and other downlink data packets received from the core network to the terminal; in the uplink data transmission process, the target base station may send the uplink direction forwarding to the core network. Packets and other upstream packets received from the terminal.
  • the forwarded data packet is transmitted in preference to other uplink data packets received from the terminal or other downlink data packets received from the core network.
  • the DRB carrying the uplink data packet and the DRB carrying the downlink data packet may be the same DRB, that is, the two-way DRB is used to provide the uplink service and the downlink service, and the different DRBs respectively carry the uplink data packet and Downstream packet.
  • the target base station may send, by using the first DRB or the second DRB, a downlink data packet including a forwarding data packet to the terminal.
  • the specific manner in which the target base station sends the data packet to the terminal may include:
  • the target base station may send the forwarding data packet to the terminal by using the first DRB, and further, after the forwarding data packet is sent, the first DRB is still sent through the SDAP layer from the core network. Other downstream packets received.
  • the target base station may send, by using the first DRB, a data packet that is received by the target base station by using the DRB-established tunnel, and the second DRB is used to Transmitting, by the terminal, a data packet received by the target base station by using the session established tunnel.
  • the target base station sends, on the second DRB, the data packet that includes the flow identifier in the forwarding data packet to the terminal, and the access network device is located on the first DRB.
  • the terminal sends a data packet that does not include a flow identifier in the forwarded data packet.
  • the target base station may send, on the first DRB, the PDCP SDU of the allocated sequence number in the forwarding data packet to the terminal, and the target base station is located on the second DRB.
  • the terminal sends a PDCP SDU that contains a flow identifier and is not assigned a sequence number.
  • the target base station may further send a data packet of the SDAP layer of the source base station to the terminal on the second DRB.
  • the first DRB can be used to transmit a data packet with a flow identifier or a data packet without a flow identifier. Therefore, as long as the PDCP SDU with the serial number, whether or not the flow identifier is included, can be transmitted on the first DRB.
  • the source base station may allocate a sequence number to the PDCP SDU of the unassigned sequence number buffered in the PDCP layer, and send the PDCP SDU with the sequence number as part of the forwarded data packet to the target base station through the DRB-based tunnel.
  • the target base station can directly transmit the PDCP SDU of the allocated sequence number in the first DRB in the subsequent communication process, and does not need to allocate a sequence number for it, thereby simplifying the process and improving the transmission efficiency.
  • the target base station may route the data packet of the PDCP layer of the allocated sequence number in the data packet to the server through the SDAP entity.
  • Decoding a first DRB and sending, by using the first DRB, a data packet of the PDCP layer of the allocated sequence number to the terminal; the target base station, by using a SDAP entity, buffering data packets of the remaining data packets, for example, an SDAP layer And/or a data packet of the unassigned sequence number of the PDCP layer, routed to the second DRB, and sends the remaining data packet to the terminal through the second DRB.
  • the SDAP entity may determine, according to the mapping relationship of the flow to the DRB in the target base station, the multiple second DRBs, and transmit the remaining data packets to the multiple DRBs to the terminal.
  • the data packet of the PDCP layer with the assigned sequence number in the forwarding data packet may carry the identifier of the third DRB, and the target base station may forward the received allocated sequence number data packet according to the mapping relationship between the third DRB and the first DRB. Go to the corresponding first DRB.
  • the specific manner in which the target base station sends the data packet to the terminal includes:
  • the target base station sends, by using the first DRB, the data packet that the target base station receives through the DRB-established tunnel to the terminal, and further, forwards the data packet.
  • the first DRB is still used to send other data packets received from the core network through the SDAP layer.
  • the source base station may allocate a sequence number to the PDCP SDU of the unassigned sequence number buffered in the PDCP layer, and send the PDCP SDU with the sequence number as part of the forwarded data packet to the target base station, and no further description is provided.
  • the target base station sends, by using the first DRB, to the terminal, the data packet received by the target base station through the DRB-established tunnel does not include a flow identifier. a data packet; and the target base station sends, by using the second DRB, the data packet that includes the flow identifier in the data packet received by the target base station through the DRB-established tunnel to the terminal.
  • the target base station may route the data packet containing the flow identifier in the received data packet to the second DRB through the SDAP entity. , transmitted by the second DRB.
  • other data packets that do not contain the flow identifier are sent through the first DRB.
  • the source base station may obtain the flow identifier of the forwarded data packet by sending the flow identifier to the PDCP layer by the SDAP entity at the time of the handover, and indicate the flow identifier for the handover in the forwarded data packet.
  • the source base station may also generate a flow identifier for the data packet without the PDCP SN in the PDCP layer by using other methods for obtaining the flow identifier in the embodiment of the present application, and forward the data packet including the flow identifier to the target base station, without further description. .
  • the source base station may further generate a flow identifier for the data packet of the PDCP layer that is not assigned the sequence number by using various manners of obtaining the flow identifier described in the application, and send the forwarded data packet that includes the flow identifier to the The target base station will not be described.
  • the forwarding data packet is a data packet of a PDCP layer that is not assigned a sequence number, and some of the data packets include a flow identifier, and the remaining data packets do not include the flow identifier
  • the forwarded data packet is sent to the terminal by using the first DRB. It can improve the continuity and quasi-determination of packet transmission.
  • the data packet of the non-access stratum stream having the Reflective QoS feature may be transmitted in the manner described above on the first DRB.
  • Reflective QoS means that the flow has the characteristics of uplink and downlink symmetry, that is, the QoS of the flow in the uplink direction and the flow in the downlink direction are the same, and the traffic flow template (TFT) of the uplink and downlink is also symmetric, for example, the source of the uplink.
  • the address and source port number are the destination address and destination port number of the downlink; the destination address and destination port number of the uplink are the source address and source port number of the downlink.
  • the access network device carries the flow identifier in the air interface data packet, and the terminal acquires the QoS of the uplink flow and the corresponding TFT according to the received flow identifier and the quintuple information of the downlink data packet.
  • the terminal may send, by using the first DRB or the second DRB, an uplink data packet including a forwarding data packet to the target base station.
  • the uplink data packet sent by the terminal to the target base station includes: a PDCP SDU of the allocated sequence number that the terminal does not transmit successfully by the DRB of the source base station, and a PDCP SDU that does not allocate the sequence number, and the like, and the data packet that needs to continue uplink transmission.
  • the flow identifier is included in the uplink data packet.
  • the target base station receives the uplink data packet from the first DRB.
  • the terminal may continue to send the data packet of the PDCP layer in the first DRB.
  • the data packet of the PDCP layer includes a PDCP SDU of an allocated sequence number that has not been successfully transmitted and/or a PDCP SDU of an unallocated sequence number that has not been successfully transmitted.
  • the source base station sends a status report to the terminal, and the terminal determines, according to the status report, the data packet to be sent.
  • the status report may be a PDCP status report, indicating a receiving status of a PDCP SDU on the mapped DRB in the target base station, and configured to notify the terminal to send a PDCP SDU that is not correctly received by the receiving side. If the target base station does not send the PDCP status report, the terminal may send all PDCP SDUs in the cache on the mapped DRB.
  • the terminal may continue to send the PDCP SDU of the allocated sequence number buffered in the PDCP layer and/or the PDCP SDU of the unassigned sequence number in the first DRB.
  • the terminal may route other data packets, such as data packets buffered by the SDAP layer, to the second DRB by the SDAP entity.
  • the PDCP entity of the terminal may notify the target base station that the SDAP entity data packet transmission has been completed.
  • the target base station receives the uplink data packet from the second DRB.
  • the receiving mode can be applied to a scenario in which the first mapping relationship and the second mapping relationship are different.
  • the terminal may send the data packet of the PDCP layer corresponding to each DRB, including the PDCP SDU of the allocated sequence number that has not been successfully transmitted, and/or the PDCP SDU of the unallocated sequence number that is not successfully transmitted, to the SDAP entity.
  • the sequential transmission refers to sending the data packet to the SDAP layer in the order in which the PDCP layer receives the data packet from the SDAP layer.
  • the SDAP entity is established according to the session, and the data packet sent to the SDAP entity includes the flow identifier.
  • the PDCP PDU includes the data packet successfully received by the target base station, and the PDCP entity of the corresponding DRB in the target base station removes the sequence number of the PDCP PDU, decrypts, etc., converts the PDCP PDU into a PDCP SDU, or is The corresponding SDAP entity in the target base station removes the sequence number of the PDCP PDU.
  • the SDAP entity of the terminal routes the data packet received from the PDCP layer to the corresponding DRB according to the second mapping relationship, that is, the second DRB, and the SDAP entity first sends the data packet received from the PDCP layer to the second DRB, and then The data packet received by the upper layer is sent to the second DRB. It can be understood that, in this scenario, the target base station and the second access network device may not perform the data pre-transmission process in the uplink direction.
  • the target base station receives, from the first DRB, a data packet of a PDCP layer with an assigned sequence number in the uplink data packet, and receives, in the uplink data packet, the second DRB.
  • the packet of the PDCP layer of the sequence number and/or the packet of the SDAP layer are not allocated.
  • the receiving mode is applicable to a scenario in which the first mapping relationship and the second mapping relationship are different.
  • the terminal may continue to transmit the PDCP SDU of the allocated sequence number that is not successfully transmitted in the first DRB, where the source base station may send a status report to the terminal, and the terminal determines, according to the status report, the data packet to be sent. Do not repeat them.
  • the terminal can send the PDCP SDUs to the SDAP entity in order.
  • the data packets sent to the SDAP entity all contain the flow identifier.
  • the SDAP entity routes the data packet received from the PDCP layer to the corresponding DRB according to the second mapping relationship.
  • the SDAP entity first sends the data packet received from the PDCP, and then sends the data packet received from the upper layer to the corresponding DRB.
  • an air interface when an air interface performs an unacknowledged mode (UM) service, for example, a cell broadcast or an IP phone, the service between the target base station and the source base station does not need to be transmitted.
  • Air interface transmission status information of the packet Specifically, in the uplink direction, the source base station sends the successfully received data packet to the core network, and does not need to perform data pre-transmission.
  • the terminal accesses the target base station, and the terminal transmits the data packet on the new DRB according to the second mapping relationship configured by the target base station.
  • This scenario is applicable to scenarios in which the first mapping relationship and the second mapping relationship are the same or different.
  • the source base station forwards the untransmitted data packet and the new data packet received from the core network to the target base station.
  • the forwarded data packet does not include the PDCP SDU of the allocated sequence number on the DRB in the target base station, that is, the source base station does not need to send the PDCP SDU that is not successfully transmitted in the source DRB to the target.
  • Base station The remaining behaviors of the target base station or the source base station are consistent with the downlink data transmission process in the AM mode, and are not described herein.
  • the target base station after receiving the uplink data packet, delivers the uplink data packet to the core network in the order of the PDCP SDU of the allocated sequence number in the increasing order of the PDCP SN and the PDCP SDU of the unallocated sequence number. .
  • data packets belonging to the same flow may be transmitted in different DRBs, for example, some data packets in the same flow are mapped to the SRB.
  • the remaining data packets are transmitted on the new DRB, and the mapping DRB and the new DRB are only differentiated in the time dimension, for example, the data packet transmitted to the target base station first is transmitted on the mapping DRB, and then transmitted to the target base station. If the data is transmitted on the new DRB, the data packets in the same stream can be transmitted in sequence in any of the following manners.
  • the control of the data packet transmission sequence is performed by the transmitting end. Specifically, after the first DRB sends the forwarding data packet, the second DRB is notified to send other data packets.
  • the PDCP entity corresponding to the second DRB may be notified by the PDCP entity corresponding to the first DRB. If the first DRB contains data packets of multiple flows, the first DRB may need to notify the second DRB of each flow map. Or, after the first DRB sends the forwarding data packet, the SDAP entity is notified. For example, the PDCP of the first DRB may notify the corresponding SDAP entity that the forwarding of the packet transmission has been completed.
  • the PDCP entity corresponding to the first DRB can obtain the flow identifier, the PDCP can notify the corresponding SDAP entity to forward the data packet belonging to one flow in the data packet.
  • the SDAP entity After the SDAP entity receives the forwarded data packet sent by the PDCP entity, the SDAP entity starts to forward the data packet of the corresponding stream to the corresponding second DRB, where the data packet of the corresponding stream is the stream that is sent in the first DRB. Packets in the SDAP layer.
  • the control of the data packet transmission sequence is performed by the receiving end.
  • the receiving end receives the data packets in the same stream from the first DRB and the second DRB, and the receiving end can distinguish the data packets from different DRBs according to the end tag, thereby sorting the data packets received by different DRBs.
  • the receiving end first delivers the data packet in the stream received from the first DRB to the upper layer protocol layer entity, and then delivers the data packet in the stream received from the second DRB.
  • the end tag is used to indicate the end of the transmission of the data packet in the first DRB.
  • the end tag may be an independent data packet or a control packet, such as an independent data packet or a control packet of the SDAP layer or the PDCP layer, or may also indicate a certain data packet, such as a PDCP PDU, as an end tag.
  • the transmitting end is the network side, for example, the target base station, and the receiving end is the terminal side; in the uplink direction, the transmitting end is the terminal side, and the receiving end is the network side, for example, the target base station.
  • the target base station can send a data packet to the terminal in any of the following manners:
  • the target base station may send the forwarded data packet to the terminal by using the first DRB (ie, mapping DRB). Further, after the forwarding of the forwarded data packet, the first DRB is still used to transmit other data packets received from the core network through the SDAP layer. It can be understood that the sending method is applicable to any scenario in which the first mapping relationship is the same as or different from the second mapping relationship.
  • the session-based tunnel may be used to transmit the buffered data packet in the SDAP layer, and the DRB-based tunnel may be used. Used to transmit packets buffered in the PDCP layer. Specifically, if the second mapping relationship is the same as the first mapping relationship, the target base station may send the forwarded data packet to the terminal by using the first DRB (mapped DRB), and further, after the forwarding of the forwarded data packet, the first DRB is still used. Send other packets received from the core network through the SDAP layer.
  • the second mapping relationship is different from the first mapping relationship, all the forwarded data packets of the DRB-based tunnel are sent on the corresponding mapping DRB of the target base station.
  • the SDAP entity of the target base station may uniformly forward the forwarded data packet received from the session-established tunnel to the new DRB, and the new DRB performs the data packet transmission.
  • the source base station may allocate a sequence number to the PDCP SDU buffered in the PDCP layer, and send the PDCP SDU with the sequence number as a part of the forwarding data packet to the target base station, and no further description is provided.
  • the target base station When the forwarded data packet is sent to the target base station through a tunnel established by the session, the target base station routes the forwarded data packet to the second DRB according to the second mapping relationship and sends the data packet. All out-of-order packets are discarded by the receiving end. Further, the receiving end may notify the initial sequence number of the data packet discarded by the target base station, or the sequence number of the last data packet delivered to the core network. In this scenario, the target base station may not establish a mapping DRB.
  • the forwarding data packet refers to all the data packets from the identifier data packet in the PDCP layer, and the identifier data packet is used to identify that the data packet before the data packet is not sent by the sending end, and the sending end is repeated. The packet after the packet is sent.
  • the data transmission method provided by the embodiment of the present application transmits and forwards the data packet through different types of tunnels in the downlink direction, and sends the forwarded data packet to the terminal by using a transmission mode corresponding to the tunnel type; in the uplink direction, the terminal adopts different The DRB sends an uplink packet to the network side.
  • a flexible and diverse data packet transmission mode is provided, and the data packet transmission mode can be selected according to the actual situation of the network, thereby avoiding the independent configuration flow and DRB of each base station in a scenario such as handover or dual connectivity.
  • the data loss or repeated packet issue caused by the mapping relationship improves the continuity of the terminal service and improves the communication quality.
  • FIG. 7 is a schematic structural diagram of an access network device 700 according to an embodiment of the present application.
  • the access network device 700 can be applied to the communication system shown in FIG.
  • the access network device 700 can perform the operations performed by the first access network device in the embodiment shown in Fig. 2 or Fig. 5 or the target base station in the embodiment shown in Fig. 6.
  • the access network device 700 includes:
  • the receiving unit 701 is configured to receive a forwarding data packet from the second access network device.
  • the access network device 700 is a target base station, and the second access network device is a source base station.
  • the access network device 700 is a secondary base station, and the second access network device is a primary base station; or the access network device 700 is a primary base station, and the The second access network device is a secondary base station.
  • the processing unit 702 is configured to map, by the at least one data packet that includes the flow identifier, to the first DRB, where the first DRB corresponds to the DRB of the second access network device.
  • the first DRB and the DRB of the second access network device respectively satisfy a first mapping relationship, where the first mapping relationship is a mapping relationship between a flow and a DRB in the second access network device.
  • processing unit 702 is further configured to: map the data packet that does not include the flow identifier in the forwarded data packet to the first DRB.
  • the processing unit 702 is further configured to: map, according to the second mapping relationship, the at least one data packet that includes the flow identifier that is mapped to the first DRB in the forwarding data packet to the second DRB, where
  • the second mapping relationship is a mapping relationship between a flow and a DRB in the first access network device.
  • the first DRB is a mapping DRB that can continue the transmission state of the DRB of the second access network device.
  • the second DRB is a new DRB established by the access network device 700 according to the mapping relationship between the flow and the DRB configured by the access network device 700, that is, the second mapping relationship.
  • the first DRB can be used to transmit a data packet containing the flow identifier or a data packet not including the flow identifier; the second DRB can be used to transmit the data packet including the flow identifier.
  • first DRB the second DRB
  • first mapping relationship the first mapping relationship
  • second mapping relationship the second mapping relationship
  • processing unit 702 is further configured to: after the first DRB completes the sending of the data packet, release the first DRB, and the detailed description may refer to related content in other embodiments of the present application, and details are not described herein.
  • the receiving unit 701 is specifically configured to: receive the forwarding data packet from the second access network device by using a DRB-based tunnel and a session-based tunnel.
  • the DRB-based tunnel may be used to transmit a data packet of a PDCP layer of the allocated sequence number of the second access network device; and the session-established tunnel may be used to transmit the second connection.
  • the data packet of the SDAP layer of the network access device, and/or the session-based tunnel is used to transmit the data packet of the PDCP layer of the second access network device that includes the flow identifier and is not assigned a sequence number.
  • the processing unit 702 can map the data packet received through the tunnel established based on the DRB to the first DRB, and map the data packet received through the tunnel established based on the session to the second DRB.
  • the receiving unit 701 is specifically configured to: receive, by using one or more DRB-based tunnels, the forwarding data packet from the second access network device. Further, the processing unit 702 may map the data packet that does not include the flow identifier in the received forwarding data packet to the first DRB, and map the data packet including the flow identifier in the forwarded data packet to the second DRB.
  • the receiving unit 701 is specifically configured to: receive, by using the session established tunnel, the data packet that includes the flow identifier in the forwarding data packet from the second access network device. . Further, the processing unit 702 may route, by using a SDAP entity, a data packet of the PDCP layer with the assigned sequence number in the forwarding data packet to the first DRB, and a data packet or SDAP of the PDCP layer to which the sequence number is not allocated. The data packets of the layer are routed to the second DRB.
  • the access network device 700 further includes a sending unit 703, configured to send, by using the first DRB, a downlink data packet including the forwarded data packet to the terminal by using the first DRB and the second DRB.
  • the sending unit 703 is configured to send, by using the first DRB, a data packet of a PDCP layer of the allocated sequence number in the forwarding data packet to the terminal, and send the forwarding data packet to the terminal by using the second DRB.
  • FIG. 8 is a schematic structural diagram of an access network device 800 according to an embodiment of the present application.
  • Access network device 800 is applicable to the communication system as shown in FIG.
  • the access network device 800 can perform the operations performed by the first access network device in the embodiment shown in FIG. 3 or FIG. 5 or the target base station in the embodiment shown in FIG. 6.
  • the access network device 800 includes:
  • the receiving unit 801 is configured to receive a forwarding data packet from the second access network device.
  • the processing unit 802 is configured to: map the data packet that does not include the flow identifier in the forwarding data packet to the first data radio bearer DRB, where the first DRB corresponds to the DRB of the second access network device; And mapping, according to the second mapping relationship, the data packet that includes the flow identifier in the forwarding data packet to the second DRB, where the second mapping relationship is a mapping between the flow and the DRB in the first access network device relationship.
  • the first DRB and the DRB of the second access network device respectively satisfy a first mapping relationship, where the first mapping relationship is a mapping relationship between a flow and a DRB in the second access network device.
  • first DRB the second DRB
  • first mapping relationship the first mapping relationship
  • second mapping relationship the second mapping relationship
  • processing unit 802 is further configured to: route, by the SDAP entity, the data packet that includes the flow identifier in the forwarding data packet to the second DRB.
  • the access network device 800 further includes a sending unit 803, configured to send, by using the first DRB, the allocated sequence number in the forwarded data packet to the terminal, and does not include the flow identifier. And sending, by the second DRB, a data packet in the forwarding data packet that is not assigned a sequence number and includes a flow identifier.
  • processing unit 802 is further configured to: after the first DRB completes the sending of the data packet, release the first DRB, and the detailed description may refer to related content in other embodiments of the present application, and details are not described herein.
  • the receiving unit 801 receives the forwarded data packet by using a tunnel with the second access network device.
  • the tunnel between the first access network device and the second access network device may have different establishment manners.
  • FIG. 9 is a schematic structural diagram of an access network device 900 according to an embodiment of the present application.
  • the access network device 900 can be applied to the communication system shown in FIG.
  • the access network device 900 can perform the operations performed by the second access network device in any of the embodiments of Figures 2-5 or the source base station in the embodiment illustrated in Figure 6.
  • Access network device 900 includes:
  • the processing unit 901 is configured to generate a forwarding data packet that includes the flow identifier.
  • the sending unit 902 is configured to send, to the first access network device, the forwarded data packet that includes the flow identifier.
  • the forwarding data packet includes at least one data packet: an allocated sequence number of the second access network device, and a data packet of a PDCP layer that does not receive an acknowledgement by the terminal; The data packet of the PDCP layer of the unassigned sequence number of the second access network device; the data packet of the service data adaptation protocol SDAP layer of the first access network device.
  • the sending unit 902 is further configured to send, to the first access network device, a forwarding data packet that does not include a flow identifier.
  • the sending unit 902 can be configured to send the foregoing forwarding data packet to the first access network device by using a different type of tunnel.
  • a different type of tunnel For details about the various types of tunnels and the forwarding of the forwarding packets on the various types of tunnels, reference may be made to the related content of other embodiments of the present application, and details are not described herein.
  • the processing unit may be further configured to: obtain, by using a PDCP entity, a flow identifier, to add a flow identifier to the forwarded data packet, and generate forwarding data that includes the flow identifier. And the packet is further parsed by the first access network device to obtain the flow identifier.
  • a flow identifier to add a flow identifier to the forwarded data packet, and generate forwarding data that includes the flow identifier.
  • the packet is further parsed by the first access network device to obtain the flow identifier.
  • the forwarding data packet includes: an out-of-order data packet received from the terminal.
  • the access network device 900 can receive the out-of-order data packet through the receiving unit 903. Forward packets in the upstream direction contain flow identifiers.
  • the sending unit 902 may send the forwarded data packet in the uplink direction to the first access network device by using the tunnel established by the DRB, and details are not described herein.
  • FIG. 10 is a schematic structural diagram of an access network device 1000 according to an embodiment of the present application.
  • the access network device 1000 can be applied to a communication system as shown in FIG.
  • the access network device 1000 can perform the operations performed by the first access network device in the embodiment shown in FIG. 4, or the operations performed by the target base station in the embodiment shown in FIG. 6.
  • the access network device 1000 includes:
  • the receiving unit 1001 is configured to receive, by the second access network device, a forwarding data packet, where the forwarding data packet includes a flow identifier, where the forwarding data packet includes out-of-order data received by the second access network device from the terminal. package.
  • the sending unit 1002 is configured to send the received forwarding data packet to the core network device.
  • the receiving unit 1001 receives the forwarded data packet by using a tunnel with the second access network device.
  • the tunnel may be a DRB-based tunnel between the first access network device and the second access network device.
  • DRB-based tunnel refer to the related description of the DRB-based tunnel in other embodiments of the present application.
  • the receiving unit 1001 is further configured to: receive an uplink data packet from the terminal, where the uplink data packet includes at least one of the following data packets: the allocated serial number of the terminal that is not successfully sent by the terminal to the second access network device a data packet of the PDCP layer; a data packet of the PDCP layer of the terminal having no assigned sequence number; and a data packet of the SDAP layer of the terminal.
  • the receiving unit 1001 is specifically configured to receive the uplink data packet by using the first DRB.
  • the receiving unit 1001 is specifically configured to receive the uplink data packet by using the second DRB.
  • the receiving unit 1001 is specifically configured to receive, by using the first DRB, a data packet of a PDCP layer of an allocated sequence number of the terminal in the uplink data packet; and the first access network device passes the The second DRB receives the data packet of the unallocated sequence number and/or the data packet of the SDAP layer in the PDCP layer of the terminal in the uplink data packet.
  • the receiving unit 1001 is specifically configured to receive, by using the first DRB, a data packet of a PDCP layer of the terminal in the uplink data packet, and the first access network device receives the data packet by using the second DRB. a data packet of the SDAP layer of the terminal in the uplink data packet.
  • the first DRB is a mapping DRB.
  • the second DRB is a new DRB.
  • FIG. 11 is a schematic structural diagram of a terminal 1100 according to an embodiment of the present application.
  • the terminal 1100 is applicable to a communication system as shown in FIG. 1.
  • the terminal 1100 can perform the operations performed by the terminal in any of the embodiments of FIGS. 2-6.
  • the terminal 1100 includes:
  • the sending unit 1101 is configured to send an uplink data packet to the access network device, where the uplink data packet includes a flow identifier; and/or
  • the receiving unit 1102 is configured to receive a downlink data packet from the access network device, where at least one data packet in the downlink data packet includes a flow identifier.
  • the downlink data packet includes the forwarding data packet in the downlink direction.
  • forwarding data packet For the specific content of the forwarding data packet, reference may be made to the related description in other embodiments of the present application, and details are not described herein.
  • the sending unit 1101 is specifically configured to: send, by using the first DRB, an uplink data packet to the access network device.
  • the sending unit 1101 is specifically configured to: send, by using the second DRB, an uplink data packet to the access network device.
  • the sending unit 1101 is specifically configured to: send, by using the first DRB, a data packet of a PDCP layer of the allocated sequence number in the uplink data packet to the access network device; and
  • the network access device sends a data packet of an unassigned sequence number and/or a data packet of the SDAP layer in the PDCP layer in the uplink data packet.
  • the data packet of the PDCP layer transmitted by the first DRB may be a data packet including a flow identifier, or may be a data packet that does not include a flow identifier.
  • the sending unit 1101 is configured to: send, by using the first DRB, a data packet of a PDCP layer in the uplink data packet to an access network device; and send, by using the second DRB, an access network device to the access network device.
  • the data packet of the PDCP layer includes a data packet with an assigned sequence number and a data packet with no assigned sequence number.
  • the receiving unit 1102 is specifically configured to: receive, by using the first DRB, a downlink data packet from the access network device.
  • the receiving unit 1102 is specifically configured to: receive, by using the second DRB, a downlink data packet that includes the flow identifier from the access network device.
  • the receiving unit 1102 is specifically configured to: receive, by using the first DRB, the data packet that does not include the flow identifier in the downlink data packet from the access network device, and receive the flow included in the downlink data packet from the access network device by using the second DRB. The identified packet.
  • the receiving unit 1102 is specifically configured to: receive, by using the first DRB, the data packet of the PDCP layer of the allocated sequence number in the downlink data packet from the access network device, and receive the downlink data packet from the access network device by using the second DRB.
  • the first DRB is a mapping DRB.
  • the second DRB is a new DRB.
  • the access network device is an access network device that the terminal has accessed.
  • the downlink data packet includes a downlink data packet and an access network.
  • FIG. 12 is a schematic structural diagram of an access network device 1200 according to an embodiment of the present application.
  • the access network device 1200 can be applied to the communication system shown in FIG.
  • the access network device 1200 can perform the operations performed by the first access network device in any of the embodiments of Figures 2-5 or the target base station in the embodiment illustrated in Figure 6.
  • Access network device 1200 includes one or more remote radio unit (RRU) 1201 and one or more baseband units (BBUs) 1202.
  • the RRU 1201 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 12011 and a radio frequency unit 12012.
  • the RRU 1201 is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals and baseband signals, for example, for transmitting signaling information and the like described in the foregoing method embodiments to the UE.
  • the BBU 1202 part is mainly used for performing baseband processing, controlling access network equipment, and the like.
  • the RRU 1201 and the BBU 1202 may be physically disposed together or physically separated, that is, distributed access network devices.
  • the function of the RRU may be implemented by the DU, and the function of the BBU may be implemented by the CU; or the function of the RRU and some functions of the BBU are implemented by the DU, and other functions of the BBU are implemented by the CU; Or some functions of the RRU are implemented by the DU, and other functions of the RRU and functions of the BBU are implemented by the CU, and are not limited.
  • the BBU 1202 is a control center of an access network device, and may also be referred to as a processing unit, and is mainly used to perform baseband processing functions, such as channel coding, multiplexing, modulation, and spreading.
  • the BBU may be used to control the operation performed by the access network device 1200 to perform the first access network device in any of the embodiments of FIG. 2 to FIG. 5 or the target base station in the embodiment shown in FIG. 6.
  • the BBU 1202 may be composed of one or more boards, and multiple boards may jointly support a single access standard radio access network (such as an NR access network), or may separately support different access modes of wireless. Access Network.
  • the BBU 1202 also includes a memory 12021 and a processor 12022.
  • the memory 12021 is used to store necessary instructions and data.
  • the memory 12021 stores the context of the UE in the above embodiment.
  • the processor 12022 is configured to control the access network device 1200 to perform necessary actions, for example, to control the operation of the access network device 1200 to perform the first access network device in any of the embodiments of FIG. 2 to FIG. 4, or
  • the access network device 1200 is controlled to perform the actions of the target base station in the embodiment shown in FIG.
  • the memory 12021 and the processor 12022 can serve one or more boards. That is, the memory and processor can be individually set on each board. It is also possible that multiple boards share the same memory and processor. In addition, the necessary circuits are also provided on each board.
  • the BBU 1202 further includes a communication unit 12023, which is configured to support the access network device 1200 to communicate with network elements such as other access network device devices or core network devices, for example, to support the access network device 1200.
  • the second access network device receives the forwarded data packet.
  • the communication unit 12023 may include a communication interface, such as a communication interface between the access network device 1200 and the second access network device, or a communication interface between the access network device 1200 and the core network device.
  • FIG. 13 is a schematic structural diagram of an access network device 1300 according to an embodiment of the present application.
  • the access network device 1300 can be applied to the communication system shown in FIG. 1.
  • the access network device 1300 can perform operations that can be performed by the second access network device in any of the embodiments of Figures 2-5 or the source base station in the embodiment illustrated in Figure 6.
  • Access network device 1300 includes one or more RRUs 1301 and one or more BBUs 1302.
  • the BBU 1302 may be used to control the access network device 1300 to perform operations performed by the second access network device in the implementation shown in FIG. 2-5, or to control the access network device 1300 to perform the source in the embodiment shown in FIG. The operation performed by the access network device.
  • the BBU 1302 may be composed of one or more boards, and multiple boards may jointly support a single access standard radio access network (such as an NR access network), or may separately support different access modes of wireless. Access Network.
  • the BBU 1302 also includes a memory 13021 and a processor 13022.
  • the memory 13021 is used to store necessary instructions and data.
  • the memory 13021 stores the context of the UE acquired from the first access network device in the above embodiment.
  • the processor 13022 is configured to control the access network device 1300 to perform necessary actions, for example, to control the operation of the access network device 1300 to perform the second access network device in the embodiment shown in FIG. 2 to FIG.
  • the access network device 1300 performs the actions of the source base station in the embodiment shown in FIG.
  • the BBU 1302 further includes a communication unit 13023, where the communication unit 13023 is configured to support the access network device 1300 to communicate with other network elements such as the access network device device or the core network device, for example, the access network device 1300 is supported.
  • the first access network device sends a forwarded data packet.
  • the communication unit 13023 may include a communication interface, such as a communication interface between the access network device 1300 and the first access network device, or a communication interface between the access network device 1300 and the core network device.
  • FIG. 14 is a schematic structural diagram of a terminal 1400 according to an embodiment of the present application.
  • the terminal 1400 can be applied to the communication system shown in FIG. 1.
  • the terminal 1400 can perform the operations performed by the terminal in any of the embodiments of FIGS. 2-6.
  • FIG. 14 shows only the main components of the terminal.
  • the terminal 1400 includes a processor, a memory, a control circuit, an antenna, and an input and output device.
  • the processor is mainly used for processing the communication protocol and the communication data, and controlling the entire user equipment, executing the software program, and processing the data of the software program, for example, for supporting the terminal 1400 to execute the terminal described in the sections of FIG. 2-6. Actions.
  • the memory is primarily used to store software programs and data, such as the context of the terminals described in the above embodiments.
  • the control circuit is mainly used for converting baseband signals and radio frequency signals and processing radio frequency signals.
  • the control circuit and the antenna together may also be called a transceiver, and are mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves, for example, may be used to perform uplink data packets to be sent to the access network device, or receive downlink data packets from the access network device.
  • Input and output devices such as touch screens, display screens, keyboards, etc., are primarily used to receive user input data and output data to the user.
  • the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program.
  • the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit performs radio frequency processing on the baseband signal, and then sends the radio frequency signal to the outside through the antenna in the form of electromagnetic waves.
  • the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor, which converts the baseband signal into data and processes the data.
  • FIG. 14 shows only one memory and processor for ease of illustration. In an actual terminal, there may be multiple processors and memories.
  • the memory may also be referred to as a storage medium or a storage device, and the like.
  • the processor may include a baseband processor and a central processing unit, and the baseband processor is mainly used to process communication protocols and communication data, and the central processing unit is mainly used to control the entire terminal and execute the software.
  • the processor in FIG. 14 integrates the functions of the baseband processor and the central processing unit.
  • the baseband processor and the central processing unit can also be independent processors and interconnected by technologies such as a bus.
  • the terminal may include multiple baseband processors to accommodate different network standards.
  • the terminal may include multiple central processors to enhance its processing capabilities, and various components of the terminal may be connected through various buses.
  • the baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processor can also be expressed as a central processing circuit or a central processing chip.
  • the functions of processing the communication protocol and the communication data may be built in the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.
  • FIG. 15 is a schematic diagram of a communication system 1500 according to an embodiment of the present application.
  • the communication system 1500 includes:
  • the first access network device may perform operations performed by the first access network device in any of the embodiments of FIG. 2 to FIG. 5 or perform execution by the target base station in the embodiment shown in FIG. Operation.
  • it may be an access network device of the embodiment shown in FIG. 7, FIG. 8, FIG. 10 or FIG.
  • a second access network device 1502 which may perform the operations performed by the second access network device in any of the embodiments of FIG. 2 to FIG. 5 or perform the source base station in the embodiment shown in FIG. The action performed.
  • it may be an access network device as shown in the embodiment of FIG. 9 or FIG.
  • the communication system may further include a terminal 1503 that communicates with the first access network device 1501 and the second access network device 1502, and the terminal 1503 may perform operations performed by the terminal in any of the embodiments of FIG. 2-6. It may be the terminal described in the embodiment of Fig. 11 or Fig. 14.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the disclosed systems, devices, and methods may be implemented in other manners without departing from the scope of the present application.
  • the embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined. Or it can be integrated into another system, or some features can be ignored or not executed.
  • the units described as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. .
  • Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.
  • the described systems, devices, and methods, and the schematic diagrams of various embodiments may be combined or integrated with other systems, modules, techniques or methods without departing from the scope of the present application.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in electronic, mechanical or other form.

Landscapes

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

Abstract

本申请提供了一种数据传输方法，第一接入网设备建立第一DRB(数据无线承载)和第二DRB；所述第一接入网设备从第二接入网设备接收转发数据包；所述第一接入网设备将所述转发数据包中不包含流标识的数据包映射到所述第一DRB，所述第一DRB对应于第二接入网设备的DRB；所述第一接入网设备根据第二映射关系，将所述转发数据包中包含流标识的数据包映射到所述第二DRB，所述第二映射关系为所述第一接入网设备中的流与DRB的映射关系，从而，避免在切换或者双连接等场景中，由于每个接入网设备独立配置流与DRB的映射关系而导致的数据丢包或者重复发包的问题，提升终端业务的连续性，提高通信质量。

Description

数据传输方法、接入网设备、终端及通信系统
本申请要求于2017年3月24日提交中国专利局、申请号为201710183306.9、申请名称为“数据传输方法、接入网设备、终端及通信系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信领域，尤其是一种数据传输方法、接入网设备、终端及通信系统。
背景技术
随着用户需求的不断提升，对新无线接入网(new radio access network，New RAN的研究越来越深入。相较于现有的无线通信系统，新无线接入网能够提供更短的时延，更大的带宽，并且支持大量连接，以满足移动通信日益增长的需求。
在新无线接入网中，服务质量(quality of service，QoS)管理是基于流(flow)的，包括，接入网设备和核心网之间建立协议数据单元(protocol data unit，PDU)会话，所述PDU会话可以包括多条流，不同流可以有不同的QoS要求，核心网向基站提供流的QoS要求，由基站根据所述QoS要求，完成流与数据无线承载(data radio bearer，DRB)的映射，例如，将具有相同QoS要求的流映射到同一个DRB，通过该DRB进行传输。
当基站间进行数据传输时，例如在切换(handover)或者双连接(dual connection，DC)的场景中，源基站与目标基站之间建立隧道，将源基站上的终端数据包发送给目标基站，进而由目标基站与终端进行通信。由于目标基站与源基站会配置不同的流与DRB的映射关系，终端数据包在发送给目标基站或者后续空口传输的过程中会出现丢包、重复发包等问题，影响终端的通信连续性。
发明内容
本申请实施例提供了一种数据传输方法、接入网设备、终端及通信系统。
第一方面，本申请实施例提供了一种数据传输方法，包括：
第一接入网设备从第二接入网设备接收转发数据包；所述第一接入网设备将所述转发数据包中不包含流标识的数据包映射到第一数据无线承载(data radio bearer，DRB)，所述第一DRB对应于所述第二接入网设备的DRB；所述第一接入网设备根据第二映射关系，将所述转发数据包中包含流标识的数据包映射到第二DRB，其中，所述第二映射关系为所述第一接入网设备中的流与DRB的映射关系。
其中，所述第一DRB与所述第二接入网设备的DRB分别满足第一映射关系，所述第一映射关系为所述第二接入网设备中的流与DRB的映射关系。所述第一DRB是所述第二接入网设备的DRB的映射DRB。
其中，所述转发数据包包括如下至少一种数据包：所述第二接入网设备的已分配序列号且未得到终端接收确认的分组数据汇聚协议(packet data convergence protocol，PDCP)层的数据包；所述第二接入网设备的未分配序列号的PDCP层的数据包；第二接入网设备的业务数据适配协议(service data adaptation protocol，SDAP)层的数据包。
在每个接入网设备可以独立设置流与DRB的映射关系的前提下，通过将有流标识的数据包映射到第二DRB进行传输，并将没有流标识的数据包映射到第一DRB进行传输，可以根据网络实际情况选择数据包传输方式，从而避免在切换或者双连接等场景中，由于每个接入网设备独立配置流与DRB的映射关系而导致的数据丢包或者重复发包问题，提升终端业务的连续性，提高通信质量。
在一个可能的实现方式中，所述第一接入网设备通过所述第一DRB向终端发送所述转发数据包中已分配序列号且不包含流标识的数据包；所述第一接入网设备通过所述第二DRB向终端发送所述转发数据包中未分配序列号且包含流标识的数据包。所述数据包可以是PDCP层的数据包，则所述序列号为PDCP层的序列号。
在一个可能的实现方式中，所述第一接入网设备通过所述第一DRB向终端发送所述转发数据包中不包含流标识的数据包；所述第一接入网设备通过所述第二DRB向终端发送所述转发数据包中包含流标识的数据包。其中，所述包含流标识的数据包可以是已分配流标识的PDCP层的数据包和/或SDAP层的数据包。
在一个可能的实现方式中，所述方法还包括：所述第一接入网设备通过SDAP实体将所述转发数据包中包含流标识的数据包路由到所述第二DRB。
在一个可能的实现方式中，所述第一接入网设备从第二接入网设备接收转发数据包包括：所述第一接入网设备通过基于DRB建立的隧道以及基于会话建立的隧道从所述第二接入网设备接收所述转发数据包；其中，所述基于DRB建 立的隧道用于传输所述第二接入网设备的已分配序列号的PDCP层的数据包；所述基于会话建立的隧道用于传输所述第二接入网设备的SDAP层的数据包，和/或，用于传输所述第二接入网设备的包含流标识且未分配序列号的PDCP层的数据包。
在一个可能的实现方式中，所述第一接入网设备从第二接入网设备接收转发数据包包括：所述第一接入网设备通过基于DRB建立的隧道从所述第二接入网设备接收所述转发数据包。其中，基于DRB建立的隧道可以有一条或多条。例如，当有两基于DRB建立的隧道时，其中的一条隧道可以用于传输有流标识的数据包；另一条隧道可以用于传输没有流标识的数据包。
在一个可能的实现方式中，所述第一接入网设备从第二接入网设备接收转发数据包包括：所述第一接入网设备通过基于会话建立的隧道从所述第二接入网设备接收所述转发数据包中包含流标识的数据包。可选地，所述第一接入网设备通过SDAP实体将从所述基于会话建立的隧道接收的已分配序列号的PDCP层的数据包路由到所述第一DRB；且将未分配序列号的PDCP层的数据包或者SDAP层的数据包路由到所述第二DRB。
上述各类建立隧道的方式可以适用于多种转发数据包的传输场景，对于转发数据包有无包含流标识，以及转发数据包有无分配序列号，都能通过适当的隧道进行转发数据包传输，从而避免数据前传过程中的丢包或者重复发包，提升网络性能。
在一个可能的实现方式中，当映射到所述第一DRB上的转发数据包发送完成后，所述方法还包括：所述第一接入网设备释放所述第一DRB，从而节约系统资源。
在一个可能的实现方式中，所述第一接入网设备可以将所述第二映射关系发送给所述第二接入网设备，并通过第二接入网设备发送给终端。
第二方面，本申请实施例提供了一种数据传输方法，包括：第一接入网设备从第二接入网设备接收转发数据包；所述第一接入网设备将所述转发数据包中至少一个包含流标识的数据包映射到第一DRB，所述第一DRB对应于所述第二接入网设备的DRB。
其中，所述第一DRB与所述第二接入网设备的DRB分别满足第一映射关系，所述第一映射关系为所述第二接入网设备中的流与DRB的映射关系。
其中，所述转发数据包包括如下至少一种数据包：所述第二接入网设备的已分配序列号且未得到终端接收确认的PDCP层的数据包；所述第二接入网设备的未分配序列号的PDCP层的数据包；第二接入网设备的SDAP层的数据包。
在一个可能的实现方式中，所述方法还包括：所述第一接入网设备将所述转发数据包中不包含流标识的数据包映射到所述第一DRB。
在一个可能的实现方式中，所述方法还包括：所述第一接入网设备根据第二映射关系，将所述转发数据包中映射到所述第一DRB之外的至少一个包含流标识的数据包映射到第二DRB；其中，所述第二映射关系为所述第一接入网设备中的流与DRB的映射关系。
在一个可能的实现方式中，所述第一接入网设备通过所述第一DRB或者通过所述第一DRB与所述第二DRB向终端发送所述转发数据包。
可选地，在第二方面中，第一接入网设备可以与第二接入网设备建立不同类型的隧道用于传输转发数据包，具体的隧道类型举例可以参照第一方面中的相关描述，不做赘述。各类建立隧道的方式可以适用于多种转发数据包的传输场景，对于转发数据包有无包含流标识，以及转发数据包有无分配序列号，都能通过适当的隧道进行转发数据包传输，从而避免数据前传过程中的丢包或者重复发包，提升网络性能。
在一个可能的实现方式中，所述方法还包括：所述第一接入网设备通过所述第一DRB向终端发送所述转发数据包中已分配序列号的PDCP层的数据包；所述第一接入网设备通过所述第二DRB向终端发送所述转发数据包中未分配序列号的PDCP层的数据包。
在一个可能的实现方式中，当映射到所述第一DRB上的转发数据包发送完成后，所述方法还包括：所述第一接入网设备释放所述第一DRB。
在一个可能的实现方式中，所述第一接入网设备可以将所述第二映射关系发送给所述第二接入网设备，并通过第二接入网设备发送给终端。
采用本申请实施例提供的数据传输方法，第一接入网设备通过对应于第二接入网设备的第一DRB向终端发送转发数据包，进一步地，为获得更好的网络性能，第一接入网设备建立第二DRB，所述第二DRB用于传输所述转发数据包中映射到第一DRB的数据包之外的其他有流标识的数据包，所述第二DRB满足第一接入网设备配置的流与DRB的映射关系。因此，转发数据包可以通过不同DRB进行传输，传输方式灵活多样，可以根据网络实际情况进行选择数据包传输方式，从而避免在切换或者双连接等场景中，由于每个基站独立配置流与DRB的映射关系而导致的数据丢包或者重复发包问题，提升终端业务的连续性，提高通信质量。
第三方面，本申请实施例提供了一种数据传输方法，包括：第一接入网设备生成包含流标识的转发数据包；所述第一接入网设备向第二接入网设备发送所述包含流标识的转发数据包。
在一个可能的实现方式中，所述方法还包括：所述第一接入网设备向所述第二接入网设备发送第一映射关系；其中，所述第一映射关系为所述第二接入网设备中的流与DRB的映射关系。
在一个可能的实现方式中，第一接入网设备生成包含流标识的转发数据包包括：
所述第一接入网设备获取所述转发数据包的缓存位置，所述缓存位置对应于所述转发数据包的流标识；所述第一接入网设备根据所述缓存位置获取所述转发数据包的流标识，所述第一接入网设备将所述流标识添加在所述转发数据包的包头中。
在一个可能的实现方式中，所述方法还包括：所述第一接入网设备向第二接入网设备发送不包含流标识的转发数据包。
在一个可能的实现方式中，所述转发数据包包括如下至少一种数据包：所述第一接入网设备的已分配序列号且未得到终端接收确认的PDCP层的数据包；所述第一接入网设备的未分配序列号的PDCP层的数据包；第一接入网设备的SDAP层的数据包。
在一个可能的实现方式中，所述转发数据包包括：所述第一接入网设备从终端接收的乱序的数据包。
第四方面，本申请实施例提供了一种数据传输方法，包括：第一接入网设备从第二接入网设备接收转发数据包，所述转发数据包包含流标识；所述转发数据包中包括所述第二接入网设备从终端接收的乱序的PDCP层的数据包。
在一个可能的实现方式中，所述第一接入网设备从第二接入网设备接收转发数据包包括：所述第一接入网设备通过基于DRB建立的隧道从第二接入网设备接收转发数据包。
在一个可能的实现方式中，所述方法还包括：所述第一接入网设备从终端接收上行数据包，其中，所述上行数据包包括以下至少一种数据包，所述终端未成功向所述第二接入网设备发送的已分配序列号的PDCP层的的数据包；所述终端的未分配序列号的PDCP层的数据包；所述终端的SDAP层的数据包。
在一个可能的实现方式中，所述第一接入网设备从终端接收上行数据包包括：所述第一接入网设备通过所述第一DRB接收所述上行数据包；或者，所述第一接入网设备通过所述第二DRB接收所述上行数据包。
在一个可能的实现方式中，所述第一接入网设备从终端接收上行数据包包括：所述第一接入网设备通过所述第一DRB接收所述上行数据包中的所述终端的已分配序列号的PDCP层的的数据包；所述第一接入网设备通过所述第二DRB接收所述上行数据包中的所述终端的未分配序列号的PDCP层的数据包和/或业 务数据适配协议SDAP层的数据包。
在一个可能的实现方式中，所述第一接入网设备从终端接收上行数据包包括：所述第一接入网设备通过所述第一DRB接收所述上行数据包中的所述终端的PDCP层的数据包；所述第一接入网设备通过所述第二DRB接收所述上行数据包中的所述终端的业务数据适配协议SDAP层的数据包。
采用本申请实施例提供的数据传输方法，在上行方向，第一接入网设备从第二接入网设备接收包含流标识的转发数据包，所述转发数据包中包括所述第二接入网设备从终端接收的乱序的数据包。当转发数据包发送完成后，终端可以采用不同DRB向网络侧发送上行数据包，传输方式灵活多样，可以根据网络实际情况进行选择数据包传输方式，从而避免在切换或者双连接等场景中，由于每个基站独立配置流与DRB的映射关系而导致的数据丢包或者重复发包问题，提升终端业务的连续性，提高通信质量。
第五方面，本申请实施例提供了一种数据传输方法，包括，终端向第一接入网设备发送上行数据包，所述上行数据包包含流标识；和/或，所述终端从接入网设备接收下行数据包，所述下行数据包中至少一个数据包包含流标识，所述下行数据包中包含第二接入网设备向第一接入网设备发送的转发数据包。
在一个可能的实现方式中，所述终端向接入网设备发送上行数据包包括：所述终端通过第一DRB向所述第一接入网设备发送所述上行数据包中的已分配序列号的PDCP层的数据包；且所述终端通过第二DRB向所述第一接入网设备发送所述上行数据包中的PDCP层的未分配序列号的数据包和/或SDAP层的数据包，其中，所述第一DRB满足所述第二接入网设备中的流与DRB的映射关系；所述第二DRB满足所述第一接入网设备中的流与DRB的映射关系。
在一个可能的实现方式中，所述终端向接入网设备发送上行数据包包括：所述终端通过第一DRB向接入网设备发送所述上行数据包中的PDCP层的数据包；且所述终端通过第二DRB向接入网设备发送所述上行数据包中的SDAP层的数据包。
在一个可能的实现方式中，所述终端从接入网设备接收下行数据包包括：所述终端通过第一DRB从所述第一接入网设备接收下行数据包中不包含流标识的数据包，且所述终端通过第二DRB从所述第一接入网设备接收下行数据包中包含流标识的数据包。
在一个可能的实现方式中，所述终端从接入网设备接收下行数据包包括：所述终端通过第一DRB从所述第一接入网设备接收下行数据包中已分配序列号的PDCP层的数据包，且通过第二DRB从所述第一接入网设备接收下行数据包中包含流标识且未分配序列号的PDCP层的数据包和/或SDAP层的数据包。
以上第五方面中任一一种实现方式中所述的第一DRB满足所述第二接入网 设备中的流与DRB的映射关系；第二DRB满足所述第一接入网设备中的流与DRB的映射关系。
第六方面，本申请实施例提供了一种接入网设备，该接入网设备具有实现以上任一一种数据传输方法中第一接入网设备或者具有实现以上任一一种数据传输方法中第二接入网设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或手段(means)。
在第六方面的一种可能的实现方式中，该接入网设备的结构中包括处理器和收发器，所述处理器被配置为支持接入网设备执行上述数据传输方法中相应的功能。所述收发器用于支持接入网设备与终端之间的通信，向终端发送上述数据传输方法中所涉及的信息或者指令。接入网设备中还可以包括存储器，所述存储器用于与处理器耦合，其保存接入网设备必要的程序指令和数据。接入网设备中还可以包括通信接口，所述通信接口用于与其他网络设备通信。
在一个可能的实现方式中，该接入网设备为基站。
第七方面，本申请实施例提供了一种终端，该接入网设备具有实现以上任一一种数据传输方法中终端行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或手段(means)。
在第七方面的一种可能的实现方式中，该终端的结构中包括处理器和收发器，所述处理器被配置为支持接入网设备执行上述数据传输方法中相应的功能。所述收发器用于支持接入网设备与终端之间的通信，向接入网设备发送上述数据传输方法中所涉及的信息或者指令。终端中还可以包括存储器，所述存储器用于与处理器耦合，其保存终端必要的程序指令和数据。
第八方面，本发明实施例提供了一种通信系统，包括以上方面所述的接入网设备、以及终端。
第九方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述任一方面所述的数据传输方法。
第十方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一方面所述的数据传输方法。
通过本申请实施例提供的技术方案，采用灵活多样的转发数据包传输方式，避免在切换或者双连接等场景中，由于每个基站独立配置流与DRB的映射关系而导致的数据丢包或者重复发包问题，提升终端业务的连续性，提高通信质量。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的一种通信系统的示意图；
图2是本申请实施例提供的一种数据传输方法的流程示意图；
图3是本申请实施例提供的一种数据传输方法的流程示意图；
图4是本申请实施例提供的一种数据传输方法的流程示意图；
图5是本申请实施例提供的一种数据传输方法的流程示意图；
图6是本申请实施例提供的一种数据传输方法的信令流程示意图；
图7是本申请实施例提供的一种接入网设备700的结构示意图；
图8是本申请实施例提供的一种接入网设备800的结构示意图；
图9是本申请实施例提供的一种接入网设备900的结构示意图；
图10是本申请实施例提供的一种接入网设备1000的结构示意图；
图11是本申请实施例提供的一种终端1100的结构示意图；
图12是本申请实施例提供的一种接入网设备1200的结构示意图；
图13是本申请实施例提供的一种接入网设备1300的结构示意图；
图14是本申请实施例提供的一种终端1400的结构示意图；
图15是本申请实施例提供的一种通信系统1500的示意图。
具体实施方式
本申请实施例中描述的技术可用于5G(the fifth generation，第五代)通信系统，或者其他下一代通信系统，例如新无线接入网(New RAN，NR)。
本申请实施例中所述的接入网设备包括NR中的基站设备，例如gNB、传输点(trasmission point，TRP)，或者由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的基站设备，其中，CU也可以称为控制单元(control unit)。当长期演进(long term evolution，LTE)系统中的基站设备，即演进型节点B(evolved nodeB，eNB)可以连接5G核心网(5G-Core，5G CN)时，LTE eNB也可以称为eLTE eNB。具体地，eLTE eNB是在LTE eNB基础上 演进的LTE基站设备，可以直接连接5G CN。eLTE eNB也属于NR中的基站设备。所述接入网设备还可以是接入点(access point，AP)，或者其他具有与终端及核心网通信能力的网络设备，本申请实施例对接入网设备的类型不做特别限定。
本申请实施例中所述的5G CN也可以称为新型核心网(new core)、或者5G New Core、或者下一代核心网(next generation core，NGC)等。5G-CN独立于现有的核心网，例如演进型分组核心网(evolved packet core，EPC)而设置。
本申请实施例所涉及到的终端可以包括具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备(user equipment，UE)，移动台(mobile station，MS)，终端设备(terminal equipment)等。
本申请实施例定义接入网到终端的单向通信链路为下行链路，在下行链路上传输的数据为下行数据，下行数据的传输方向称为下行方向；而终端到接入网的单向通信链路为上行链路，在上行链路上传输的数据为上行数据，上行数据的传输方向称为上行方向。
本申请实施例中所述的源接入网设备是指终端当前接入或驻留的接入网设备设备，且终端将从该接入网设备设备切换至其他接入网设备设备。对应地，本申请实施例中所述的目标接入网设备是指终端将切换到的接入网设备设备。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/“，表示前后关联对象是一种“或”的关系。
本申请实施例中出现的“多个”是指两个或两个以上。
本申请实施例中出现的第一、第二等描述，仅作示意与区分描述对象之用，没有次序之分，也不表示本申请实施例中对设备个数的特别限定，不能构成对本申请实施例的任何限制。
本申请实施例中出现的“连接”是指直接连接或者间接连接等各种连接方式，以实现设备间的通信，本申请实施例对此不做任何限定。
本申请实施例中出现的“网络”与“系统”表达的是同一概念，通信系统即为通信网络。
图1是本申请实施例提供的一种通信系统的示意图。
如图1所示，该通信系统包括核心网设备110、第一接入网设备120、第二接入网130和终端140，其中，第一接入网设备120、第二接入网设备130分别通过通信接口与核心网设备110相通信，所述通信接口例如是图1中所示的NG 接口；且第一接入网设备120、第二接入网设备130之间可以存在通信接口，例如图1中所示的Xn接口，用于交互设备间信息。
可以理解，上述核心网设备110是5G CN中的核心网设备，包括一个或多个独立设置或集成的功能实体，例如核心网设备110可以由控制面(control plane，CP)网元和用户面(user plane，UP)网元，例如用户面网关(user plane gateway，UPGW)组成。
可选地，上述第一接入网设备120或者第二接入网设备130是gNB或者eLTE eNB中的任意一种基站设备，本申请实施例对此不做任何限定。例如，第一接入网设备120是gNB，且第二接入网设备130是gNB；或者，第一接入网设备120是eLTE eNB，且第二接入网设备130是eLTE eNB；或者，第一接入网设备120是gNB，且第二接入网设备130是eLTE eNB；或者，第一接入网设备120是eLTE eNB，且第二接入网设备130是gNB。
核心网设备110通过协议数据单元(protocol data unit，PDU)会话(session)分别与第一接入网设备120和/或第二接入网设备130进行通信，一个PDU会话可以包括多个流，不同的流的QoS要求可能相同，也可能不同，核心网110向第一接入网设备120和/或第二接入网设备130提供流的QoS要求，由第一接入网设备120和/或第二接入网设备130完成流到DRB的映射，相应地，一个DRB包括的流具有相同或相似的QoS要求。具体地，接入网设备可以为接入的终端的每一个会话建立至少一个DRB，其中，包括一个默认DRB(default DRB)。DRB建立在接入网设备与终端之间，用于传输空口数据。
本申请实施例中，具备某种QoS要求的流可以称为QoS flow，一个QoS flow由至少一个数据包组成。每个QoS flow对应于一种或多种业务类型。以下实施例中将QoS flow简称为“流”。
在一种可能的切换(handover)场景中，终端140在移动过程中切换接入的接入网设备，以获取最佳的通信服务。例如，当终端140从当前接入的第一接入网设备120的移动到第二接入网设备130的信号覆盖范围内，终端140可以启动切换流程，由第一接入网设备120切换至第二接入网设备130，在切换过程中，第一接入网设备120可以将预备与终端140进行传输的流发送给第二接入网设备130，第二接入网设备130可以将所述预备与终端140进行传输的流映射到符合流的QoS要求的DRB，进而通过所述DRB与终端进行流的传输。
在一种可能的双连接(dual-connection，DC)场景中，终端140同时接入第一接入网设备120及第二接入网设备130，当第一接入网设备120确定将一部分业务转移至第二接入网设备130时，第一接入网设备120可以向第二接入网设备130发送这部分业务对应的流，第二接入网设备130可以将所述流映射到符合所述流的QoS要求的DRB，进而通过所述DRB与终端进行流的传输。其中，终端连接的接入网设备根据功能不同可以分为：具备与终端之间的控制面功能 和用户面功能的主接入网设备，以及，可以用于和终端之间的用户面数据传输的辅接入网设备。由于主接入网设备可以控制终端的业务在主接入网设备和辅接入网设备之间迁移，业务对应的流在接入网设备间的转发和空口的传输，不用区分主接入网设备还是辅接入网设备，因此，上述第一接入网设备120及第二接入网设备130无需限定是主接入网设备或者是辅接入网设备。可以理解，终端还可以接入一个主接入网设备以及多个辅接入网设备，不做赘述。
在切换过程或者双连接过程中，第一接入网设备120将与终端140相关的数据包发送给第二接入网设备130，由第二接入网设备130继续与终端140进行所述数据包的传输，所述数据包属于一个或多个流。该数据包的传输过程可以称为数据前传(data forwarding)，也可以称为数据反传或者数据转发。
具体地，在第一接入网设备120和第二接入网设备130之间可以建立隧道(tunnel)用于传输数据前传的数据包。隧道可以是按DRB建立；也可以是按照SDAP实体或会话建立的；还可以同时建立两种隧道，即一条按照DRB建立，一条按照SDAP实体或会话建立，其中，按DRB建立的隧道可以用于传输所述DRB对应的PDCP层中的数据包。按照会话或SDAP实体建立的隧道可以用于传输SDAP中缓存的数据包或者传输PDCP层中携带流标识的数据包。其中，所述SDAP层是指在连接到NGC的接入网侧的协议栈中，在用户面的PDCP层之上建立的用户面协议层。SDAP层可以用于将来自非接入层(non-access stratum，NAS)的流映射到接入层(access stratum，AS)的DRB上。SDAP实体是由SDAP层建立的，用于完成SDAP层的功能而建立的实例。SDAP实体还负责在空口协议栈中添加流标识。所述流标识包括上行流标识以及下行流标识，用于标识上行数据流或者下行数据流。接入网设备可以根据每条流的流标识，根据每个DRB的QoS要求，将不同的流映射到同一个或者不同的DRB上，即建立流与DRB的映射关系。例如，核心网传输到接入网设备的流1为机器类通信(machine type communication，MTC)业务对应的流，流2为移动宽带(mobile broadband，MBB)业务对应的流，则视该接入网设备支持的业务类型不同，流1和流2可以映射到该接入网设备的同一个DRB，例如默认DRB；也可以分别映射到两个DRB。
可以理解，SDAP实体或者SDAP层还可以采用其他名称指代，例如分组数据链接协议(packets data association protocol，PDAP)实体或层，只要是符合上述对SDAP层的定义以及功能的描述的协议层，都属于本申请实施例描述的SDAP层所保护的范围。
由于每个接入网设备独立设置流与DRB的映射关系，上述数据前传的数据包发送给第二接入网设备130后，如果第二接入网设备130仍然按照第一接入网设备120配置的流与DRB的映射关系传输上述数据包，可能会导致数据丢包或者重复发包，影响终端业务的连续性。
因此，为了解决在每个接入网设备独立设置流与DRB的映射关系的前提下， 特别是在切换或者双连接场景中，如何进行数据前传以及在空口传输数据前传的数据包的问题，本申请实施例提出了一种数据传输方法。
为了方便说明，以下各实施例中出现的“第一接入网设备”或“第二接入网设备”均表示相同的含义，下文将不再赘述。例如。在切换过程中，本申请实施例中的第一接入网设备可以是目标接入网设备，且第二接入网设备可以是源接入网设备。在双连接场景中，本申请实施例中的第二接入网设备可以将部分业务分流(offload)到第一接入网设备中，由第一接入网设备与终端进行这部分业务的传输。例如，当采用主小区组承载(master cell group bearer，MCG bearer)时，第二接入网设备是主基站且第一接入网设备是辅基站；或者，当采用辅小区组承载(second cell group bearer，SCG bearer)时，第二接入网设备是辅基站且第一接入网设备是主基站。
图2是本申请实施例提供的一种数据传输方法的流程示意图。
本申请提供的数据传输方法可以适用于终端的切换过程或者双连接过程等有基站间数据前传过程的各类通信场景，本申请实施例对此不做任何限定。
该方法包括如下步骤：
S201：第一接入网设备从第二接入网设备接收转发数据包。
所述转发数据包为第二接入网设备向第一接入网设备发送的数据前传数据包，即在数据前传过程中，由第二接入网设备向第一接入网设备发送的数据包。
具体地，在下行方向，所述转发数据包包括如下至少一种数据包：所述第二接入网设备的已分配序列号(sequence number，SN)且未得到终端接收确认的PDCP层的数据包，所述第二接入网设备的未分配序列号的PDCP层的数据包，第二接入网设备的SDAP层的数据包。
其中，PDCP层的数据包包括PDCP PDU以及PDCP SDU，当第二接入网设备向第一接入网设备转发PDCP PDU，第二接入网设备可以将PDCP PDU进行解密、移除协议头等处理，得到保留序列号的PDCP SDU，因此，所述PDCP层的数据包在基站间转发的形式均为PDCP SDU，包括已分配序列号的PDCP SDU以及未分配序列号的PDCP SDU。本申请实施例中，所述PDCP SDU的序列号是指PDCP层序列号，可以表示为PDCP SN。
S202：所述第一接入网设备将所述转发数据包中至少一个包含流标识的数据包映射到第一DRB；其中，所述第一DRB对应于所述第二接入网设备的DRB。
所述第一接入网设备可以将所述转发数据包中所有包含流标识的数据包或者部分包含流标识的数据包映射到所述第一DRB。
其中，所述第一DRB与所述第二接入网设备的DRB分别满足第一映射关系，所述第一映射关系为所述第二接入网设备中的流与DRB的映射关系。具体 地，所述第一DRB由第一接入网设备建立，用于第一接入网设备中与终端间的数据传输。当第一接入网设备接收了第二接入网设备中的DRB上的一条或多条流的信息，则第一接入网设备可以建立映射DRB(reflect DRB)。所述映射DRB可以延续第二接入网设备中的某一个DRB的传输状态，继续传输第二接入网设备中的DRB上的数据包。为了方便说明，与所述映射DRB对应的第二接入网设备中的DRB可以称为“第三DRB”。具体地，映射DRB具有与第三DRB相同的PDCP SN状态和超帧号(hyper frame number，HFN)状态，其中，PDCP SN状态以及HFN状态可以指示在DRB上的PDCP数据包的发送和接收状态。所述映射DRB即为上述“第一DRB”。
可选地，第一接入网设备从第二接入网设备接收上述第一映射关系。
可选地，所述第一接入网设备将所述转发数据包中不包含流标识的数据包映射到所述第一DRB。
当所述第一接入网设备将转发数据包中的部分或者全部数据包映射到第一DRB之后，所述第一接入网设备通过所述第一DRB向终端发送相应的数据包，例如通过第一DRB发送所述转发数据包中部分或全部包含流标识的数据包以及全部不包含流标识的数据包。
可选地，在本申请的一个实施方式中，所述方法还包括：所述第一接入网设备根据第二映射关系，将所述转发数据包中映射到所述第一DRB之外的至少一个包含流标识的数据包映射到所述第二DRB；其中，所述第二映射关系为所述第一接入网设备中的流与DRB的映射关系。
所述第二映射关系可以包括第一接入网设备中的每个流的流标识与DRB的对应关系。第一接入网设备可以根据QoS要求配置流和DRB的映射关系，并根据该映射关系建立所述第二DRB。此类由接入网设备根据自身配置的流与DRB的映射关系建立的DRB也可以称为新DRB(new DRB)。其中，QoS要求包括QoS参数，当接入网设备间通过直接接口进行切换，则QoS参数可以由源接入网设备配置并发送给目标接入网设备；当接入网设备间通过核心网进行切换，则QoS参数可以从源基站发送到核心网设备，再由核心网设备发送给目标接入网设备，其中，核心网设备可以对QoS参数进行修改。
第一接入网设备可以将转发数据包中包含流标识的数据包分别通过所述第一DRB以及第二DRB发送，例如，一部分包含流标识的数据包通过第一DRB向终端发送，且其他包含流标识的数据包通过第二DRB向终端发送。具体地，第一接入网设备可以通过所述第一DRB向终端发送包含流标识的转发数据包中已分配序列号的PDCP层的数据包，且通过所述第二DRB向终端发送包含流标识的转发数据包中未分配序列号的PDCP层的数据包。
具体地，可以由第一接入网实体的SDAP实体将所述包含流标识的数据包 分别路由(route)到不同的DRB。
可以理解，所述第二DRB和第一DRB可以相同或不同。若第一映射关系和第二映射关系相同，则第一DRB与第二DRB相同。具体地，第一接入网设备中的一个DRB可以先作为映射DRB发送接收到的转发数据包，再作为新DRB发送从核心网接收的数据包，在时间维度上将同一个DRB分为了映射DRB与新DRB，即可以对不同时间接收到不同数据包采用不同的流与DRB的映射关系。若第一映射关系和第二映射关系不同，则第一DRB与第二DRB可以是两个独立建立的DRB。
可选地，在本申请的一个实施方式中，若第二DRB的数量比第一DRB的数量少，且第一DRB与第二DRB不同，那么，在第一DRB完成数据包的发送后，第一接入网设备与终端可以释放所述第一DRB，从而，可以减少终端以及第一接入网设备的开销。具体地，第一接入网设备可以通知终端释放所述第一DRB。终端接收到来自第一接入网设备的释放第一DRB的通知消息，释放第一DRB的配置，终端接收到上述通知消息后，可以确认该第一DRB上的下行数据包的发送完成。该通知消息可以被视为一种结束标记(end marker)，用于指示下行数据包在第一DRB中传输的结束。
可选地，第一接入网设备可以将所述第二映射关系发送给第二接入网设备，并由第二接入网设备发送给终端。
可选地，在本申请的一个实施方式中，第一接入网设备通过与第二接入网设备之间的隧道接收所述转发数据包。在下行方向，所述第一接入网设备与所述第二接入网设备间的隧道可以有不同的建立方式。本申请实施例对所述隧道的建立方式不做特别限定。
例如，所述隧道是基于DRB建立的隧道。所述基于DRB建立的隧道可以建立在第二接入设备的第三DRB和第一接入设备的映射DRB之间，也可以建立在所述第三DRB以及上述第一接入设备的新DRB之间。第一接入网设备与第二接入网设备间可以建立一条或多条基于DRB的隧道。所述基于DRB建立的隧道可以用于传输PDCP层的数据包。
可选地，第一接入网设备可以将通过基于DRB建立隧道接收到的不包含流标识的数据包映射到第一DRB，并将通过基于DRB建立隧道接收到的包含流标识的数据包映射到第二DRB。
又例如，所述隧道是基于会话建立的隧道。所述基于会话建立的隧道也可以称为基于SDAP实体建立的隧道，该隧道建立在第一接入设备的SDAP实体和第二接入网设备的同一会话的SDAP实体之间。
所述基于会话建立的隧道可以用于传输该会话下的所有DRB的转发数据包中携带流标识且未分配序列号的数据包。
可选地，所述第一接入网设备通过SDAP实体将从所述基于会话建立的隧道接收的已分配序列号的PDCP层的数据包路由到所述第一DRB；且将未分配序列号的PDCP层的数据包或者SDAP层的数据包路由到所述第二DRB。
又例如，所述隧道包括基于DRB建立的隧道以及基于会话建立的隧道。
可选地，所述基于DRB建立的隧道用于传输PDCP层的数据包，且所述基于会话建立的隧道用于传输SDAP层的数据包。
可选地，所述基于DRB建立的隧道用于传输第二接入网设备的PDCP层中缓存的已分配序列号的数据包。所述基于会话建立的隧道用于传输转发数据包中携带流标识的数据包，包括所述第二接入网设备的SDAP层的数据包，和/或，所述第二接入网设备的PDCP层中缓存的携带流标识且未分配序列号的数据包。
可选地第一接入网设备可以将通过基于DRB建立的隧道接收的数据包映射到第一DRB，并将通过基于会话建立的隧道接收的数据包映射到第二DRB。
本申请实施例中，SDAP层的数据包包括SDAP层缓存的数据包；PDCP层的数据包包括PDCP层缓存的数据包。
可以理解，第一接入网设备建立隧道与建立DRB可以是同时进行的，例如，在切换场景中，第二接入网设备向第一接入网设备发送的切换请求消息中包含建立隧道所需的信息以及建立DRB所需的信息，则第一接入网设备接收到相关信息后，就可以执行相应操作。
采用本申请实施例提供的数据传输方法，第一接入网设备从第二接入网设备接收转发数据包；所述第一接入网设备可以将所述转发数据包中至少一个包含流标识的数据包映射到第一接入网设备建立的第一DRB；其中，所述第一DRB对应于第一接入网设备的DRB；进一步地，为获得更好的网络性能，第一接入网设备建立第二DRB，所述第二DRB用于传输所述转发数据包中映射到第一DRB的数据包之外的其他有流标识的数据包，所述第二DRB满足第一接入网设备配置的流与DRB的映射关系。因此，转发数据包可以通过不同DRB进行传输，传输方式灵活多样，可以根据网络实际情况进行选择数据包传输方式，从而避免在切换或者双连接等场景中，由于每个基站独立配置流与DRB的映射关系而导致的数据丢包或者重复发包问题，提升终端业务的连续性，提高通信质量。
图3是本申请实施例提供的一种数据传输方法的流程示意图。
与图2所示实施例类似，该实施例提供的数据传输方法适用于终端的切换过程或者双连接过程等有基站间数据前传过程的各类场景，不做赘述。
该方法包括如下步骤：
S301：第一接入网设备从第二接入网设备接收转发数据包。
关于转发数据包的详细描述可以参照图2所示实施例的相关内容，在此不做赘述。
S302：所述第一接入网设备将所述转发数据包中不包含流标识的数据包映射到第一DRB，所述第一DRB对应于所述第二接入网设备的DRB(简称为“第三DRB”)。
具体地，所述第一DRB与所述第三DRB分别满足第一映射关系，所述第一映射关系为所述第二接入网设备中的流与DRB的映射关系。
可选地，第一接入网设备从第二接入网设备接收上述第一映射关系。
S303：所述第一接入网设备根据第二映射关系，将所述转发数据包中包含流标识的数据包映射到所述第二DRB，其中，所述第二映射关系为所述第一接入网设备中的流与DRB的映射关系。
其中，所述第一DRB为映射DRB，所述第二DRB为新DRB，相关的详细描述可以参照图2所示实施例的相关内容，在此不做赘述。可以理解，第一DRB及第二DRB分别由第一接入网设备建立，第一接入网设备建立第一DRB与第二DRB的步骤没有执行的先后顺序之分。
关于第一映射关系以及第二映射关系的详细描述可以参照图2所示实施例的相关内容，在此不做赘述。
可选地，所述第一接入网设备通过SDAP实体将所述转发数据包中包含流标识的数据包路由到所述第二DRB。
可以理解，步骤S302和步骤S303没有执行的先后顺序之分，例如可以先执行S302，再执行S303；也可以先执行S303，再执行S302；或者同时执行S302以及S303这两个步骤，本申请实施例对此不做特别限定。
可选地，在本申请的一个实施方式中，所述方法还包括：所述第一接入网设备通过所述第一DRB向终端发送所述转发数据包中已分配序列号且不包含流标识的数据包；所述第一接入网设备通过所述第二DRB向终端发送所述转发数据包中未分配序列号且包含流标识的数据包。其中，所述数据包可以是PDCP层的数据包，且所述序列号为PDCP SN。
可选地，在本申请的一个实施方式中，所述方法还包括：所述第一接入网设备通过所述第一DRB向终端发送所述转发数据包中不包含流标识的数据包；所述第一接入网设备通过所述第二DRB向终端发送所述转发数据包中包含流标识的数据包。
可选地，在本申请的一个实施方式中，若第二DRB的数量比第一DRB的数量少，且第一DRB与第二DRB不同，那么，在第一DRB完成数据包的发送后，第一接入网设备与终端可以分别释放所述第一DRB，从而，可以减少终端 以及第一接入网设备的开销。相关的详细描述可以参照图2所示实施例的相关内容，在此不做赘述。
可选地，第一接入网设备可以将所述第二映射关系发送给第二接入网设备，并由第二接入网设备发送给终端。
可选地，在本申请的一个实施方式中，第一接入网设备通过与第二接入网设备之间的隧道接收所述转发数据包。在下行方向，所述第一接入网设备与所述第二接入网设备间的隧道可以有不同的建立方式。
例如，第一接入网设备通过基于DRB建立的隧道以及基于会话建立的隧道从所述第二接入网设备接收所述转发数据包。
可选地，所述基于DRB建立的隧道用于传输第二接入网设备的PDCP层中缓存的已分配序列号的数据包。所述基于会话建立的隧道用于传输转发数据包中携带流标识的数据包，包括所述第二接入网设备的SDAP层的数据包，和/或，所述第二接入网设备的PDCP层中缓存的携带流标识且未分配序列号的数据包。
又例如，第一接入网设备通过基于DRB建立的隧道从所述第二接入网设备接收所述转发数据包。
又例如，第一接入网设备通过基于会话建立的隧道从所述第二接入网设备接收所述转发数据包中包含流标识的数据包。
可选地，第一接入网设备通过SDAP实体将从所述基于会话建立的隧道接收的已分配序列号的PDCP层的数据包路由到所述第一DRB；且将未分配序列号的PDCP层的数据包或者SDAP层的数据包路由到所述第二DRB。
关于上述各类隧道的详细描述可以参照图2所示实施例的相关内容，在此不做赘述。
可选地，当映射到所述第一DRB上的转发数据包发送完成后，第一接入网设备可以释放所述第一DRB，以节约资源，关于释放第一DRB的详细描述可以参考图2所示实施例中的相关内容，在此不做赘述。
采用本申请实施例提供的数据传输方法，在每个接入网设备可以独立设置流与DRB的映射关系的前提下，通过将有流标识的数据包映射到第二DRB进行传输，并将没有流标识的数据包映射到第一DRB进行传输，可以根据网络实际情况选择数据包传输方式，从而避免在切换或者双连接等场景中，由于每个接入网设备独立配置流与DRB的映射关系而导致的数据丢包或者重复发包问题，提升终端业务的连续性，提高通信质量。
图4是本申请实施例提供的一种数据传输方法的流程示意图。
该实施例提供的数据传输方法适用于终端的切换过程或者双连接过程等有基站间数据前传过程的各类场景，不做赘述。
该方法包括如下步骤：
S401：第一接入网设备从第二接入网设备接收转发数据包，所述转发数据包包含流标识，所述转发数据包中包括所述第二接入网设备从终端接收的乱序的数据包。
具体地，在上行方向，所述转发数据包为所述第二接入网设备从终端接收的乱序的PDCP层的数据包。例如，第二接入网设备收到的顺序的最后一个PDCP SDU的序列号为SN，即序列号为SN之前的PDCP SDU(…，SN-1，SN)都已按顺序收到，则第二接入网设备接收到的序列号为SN之后的乱序的PDCP SDU则是需要进行数据前传的数据包，例如，第二接入网设备在序列号为SN的PDCP SDU之后，接收到序列号为SN+3，SN+4，以及SN+6的PDCP SDU需要进行数据前传。
S402：第一接入网设备将接收到的转发数据包发送给核心网设备。
可选地，第一接入网设备通过与第二接入网设备间的隧道接收所述转发数据包。所述隧道可以是第一接入网设备和第二接入网设备之间基于DRB建立的隧道，可以参照本申请其他实施例中基于DRB建立的隧道的相关描述，不做赘述。
可选地，在本申请的一个实施方式中，所述方法还包括：所述第一接入网设备从终端接收上行数据包，其中，所述上行数据包包括以下至少一种数据包：所述终端未成功向所述第二接入网设备发送的已分配序列号的PDCP层的数据包；所述终端的未分配序列号的PDCP层的数据包；所述终端的SDAP层的数据包。
可选地，终端完成在第一DRB中的上行数据包发送后，终端可以请求第一接入网设备释放所述第一DRB。第一接入网设备可认为终端发送的释放所述第一DRB的请求是一种结束标记，该请求用于指示上行数据包在所述第一DRB中传输的结束。
终端接入第一接入网设备后，可以采用不同的发送方式向第一接入网设备发送上行数据包。
可选地，所述第一接入网设备通过所述第一DRB接收所述上行数据包。
可选地，所述第一接入网设备通过所述第二DRB接收所述上行数据包。
可选地，所述第一接入网设备通过所述第一DRB接收所述上行数据包中的所述终端的已分配序列号的PDCP层的数据包；且所述第一接入网设备通过所述第二DRB接收所述上行数据包中的所述终端的PDCP层中的未分配序列号的 数据包和/或SDAP层的数据包。
可选地，所述第一接入网设备通过所述第一DRB接收所述上行数据包中的所述终端的PDCP层的数据包；且所述第一接入网设备通过所述第二DRB接收所述上行数据包中的所述终端的SDAP层的数据包。
其中，所述第一DRB为映射DRB，所述第二DRB为新DRB，相关的详细描述可以参照本申请其他实施例的相关内容，在此不做赘述。
采用本申请实施例提供的数据传输方法，在上行方向，第一接入网设备从第二接入网设备接收包含流标识的转发数据包，所述转发数据包中包括所述第二接入网设备从终端接收的乱序的数据包。当转发数据包发送完成后，终端可以采用不同DRB向网络侧发送上行数据包，传输方式灵活多样，可以根据网络实际情况进行选择数据包传输方式，从而避免在切换或者双连接等场景中，由于每个基站独立配置流与DRB的映射关系而导致的数据丢包或者重复发包问题，提升终端业务的连续性，提高通信质量。
图5是本申请实施例提供的一种数据传输方法的流程示意图。
与图2所示实施例类似，该实施例提供的数据传输方法适用于终端的切换过程或者双连接过程等有基站间数据前传过程的各类场景，不做赘述。
该方法包括如下步骤：
S501：第二接入网设备生成包含流标识的转发数据包。
S502：第二接入网设备向第一接入网设备发送所述包含流标识的转发数据包。
可选地，在下行方向，所述转发数据包包括如下至少一种数据包：所述第二接入网设备的已分配序列号且未得到终端接收确认的PDCP层的数据包；所述第二接入网设备的未分配序列号的PDCP层的数据包；第一接入网设备的业务数据适配协议SDAP层的数据包。
可选地，在下行方向，所述第二接入网设备还向所述第一接入网设备发送不包含流标识的转发数据包。
可选地，在下行方向，第二接入网设备可以通过不同类型的隧道向第一接入网设备发送上述转发数据包。关于各类隧道以及在各类隧道上传输转发数据包的具体描述可以参照本申请其他实施例的相关内容，在此不做赘述。
可以理解，在下行方向，第一接入网设备可以向终端发送包括转发数据包在内的下行数据包。具体地，当第二接入网设备将上述转发数据包发送给第一接入网设备后，第一接入网设备可以根据转发数据包的内容(例如转发数据包有无流标识、或者转发数据包有无分配序列号)、承载转发数据包的隧道类型 等因素，将转发数据包映射到相应的DRB上传输，关于第一接入网设备将转发数据包映射到相应DRB的具体描述可以参照本申请其他实施例的相关内容，在此不做赘述。进而，第一接入网设备向终端发送从核心网获取的其他下行数据包。
可选地，在本申请的一个实施方式中，在下行反向，第二接入网设备的PDCP实体获取流标识，从而第二接入网设备可以为所述转发数据包增加流标识，生成包含流标识的转发数据包，进而由第一接入网设备解析所述转发数据包，获取所述流标识。
可选地，第二接入网设备根据业务接入节点(service access point，SAP)与流标识的对应关系获取数据包的流标识。具体地，第二接入网设备在SDAP实体和PDCP实体之间建立一个或多个SAP，PDCP实体将PDCP PDU或者PDCP SDU分别按照SAP以及流标识进行缓存，其中，每一个SAP对应着一个流。在进行数据前传时，第二接入网设备可以将所述PDCP PDU或者PDCP SDU按照SAP发送到SDAP实体，则SDAP实体可以根据SAP与流的对应关系，获取所述PDCP层的数据包的流标识。或者，PDCP实体也可以根据SAP信息，得到流标识。其中，所述转发数据包包括PDCP PDU以及PDCP SDU，其中，将PDCP PDU进行移除协议头、解密等处理生成携带序列号的PDCP SDU。
可选地，第二接入网设备根据数据包的缓存位置获取所述数据包的流标识。具体地，第二接入网设备的SDAP实体向PDCP实体发送数据包的流标识，由PDCP实体建立流标识和数据包缓存位置的对应关系，例如，PDCP实体可按照流标识将收到的PDCP SDU进行缓存，进而，第二一接入网设备获取所述转发数据包的缓存位置，所述转发数据包的缓存位置对应于所述转发数据包的流标识；所述第二一接入网设备根据所述数据包的缓存位置得到所述数据包的流标识。可选地，第二接入网设备的SDAP层还包括指示信息，该指示信息用于指示PDCP层是否将流标识添加在PDCP PDU中并在空口发送。例如，该指示信息指示不添加流标识，则PDCP PDU是由去除SDAP包头中的流标识的数据生成。由于PDCP PDU不包含流标识，节约了数据开销。
可选地，切换准备过程中，第二接入网设备的SDAP实体可以为接收到的数据包增加流标识，且指示所述流标识仅用于切换过程，从而，第一接入网设备可以根据接收到的转发数据包，恢复出流标识。
可选地，切换准备过程中，第二接入网设备的SDAP实体可以为接收到的数据包增加流标识，例如从第二接入网设备冻结传输状态开始，其中，冻结传输状态是指第二接入网设备不再向终端发送数据，SDAP实体为发送到PDCP层的数据包都增加流标识，从而第一接入网设备可以根据接收到的转发数据包恢复出流标识。
可选地，第二接入网设备根据所述转发数据包包含的序列号确定所述流标 识。具体地，第二接入网设备的SDAP实体对数据包进行缓存，并为缓存的数据包配置SDAP序列号，且将配置了SDAP序列号的数据包发送给PDCP实体。若PDCP实体向第一接入网设备成功发送包含PDCP SN的数据包，则向SDAP层发送指示，SDAP层收到该指示后，删除与所述包含PDCP SN的数据包对应的数据包。由于SDAP层中缓存的数据包具有流标识，而SDAP实体发送给PDCP实体的数据包中包含SDAP序列号，且SDAP序列号与流标识对应，因此，第二一接入网设备的SDAP实体根据转发数据包从PDPC层接收到的数据包的SDAP序列号匹配到所述数据包的流标识。
可选地，在上行方向，所述转发数据包包括：所述第一接入网设备从终端接收的乱序的数据包。上行方向的转发数据包都包含流标识。第二接入网设备可以通过基于DRB建立的隧道向第一接入网设备发送上行方向的转发数据包，不做赘述。
可以理解，在上行方向，当第二接入网设备将上述转发数据包发送给第一接入网设备后，第一接入网设备可以将转发数据包发送给核心网。而当终端接入第一接入网设备后，可以通过不同的DRB向第一接入网设备发送上行数据包。关于终端向第一接入网设备发送上行数据包的具体描述可以参照本申请其他实施例的相关内容，在此不做赘述。
图6是本申请实施例提供的一种数据传输方法的信令流程示意图。
图6所示实施例以终端从源基站切换至目标基站为例对本申请实施例提供的数据传输方法进行说明，可以理解，图6所示实施例是对图2-图5所示实施例的进一步解释与说明，所述源基站为图2-图5所示实施例中的第二接入网设备的一种示例，所述目标基站为图2-图5所示实施例中的第一接入网设备的一种示例。本申请提供的各实施例之间可以相互参照。
该方法包括如下步骤：
S601：终端向源基站发送测量报告。
S602：源基站根据接收到的测量报告决定触发切换流程。
S603：源基站向目标基站发送第一映射关系。
所述第一映射关系是指源基站配置的流与DRB的映射关系。关于第一映射关系的详细描述可以参照本申请其他实施例的相关内容，在此不做赘述。
可选地，所述第一映射关系包含在例如切换请求消息等切换过程中源基站向目标基站发送的信令或者消息中，本申请实施例对此不做任何限定。
可选地，当目标基站设备接收到源基站发送的切换请求消息后，目标基站 可以建立与终端间的DRB，包括延续源基站的DRB的传输状态的映射DRB(即上述图2或图3所示实施例中的第一DRB)，在映射DRB之外，目标基站还可以根据自身配置的流与DRB的映射关系建立新承载(即即上述图2或图3所示实施例中的第二DRB)，关于映射DRB以及新DRB的详细描述可以参照本申请其他实施例的相关内容，在此不做赘述。
S604：目标基站向所述源基站发送第二映射关系。
所述第二映射关系可以包含在例如切换请求响应消息等切换过程中，目标基站向源基站发送的信令或者消息中，本申请实施例对此不做任何限定。
所述第二映射关系是指目标基站配置的流和DRB的映射关系。关于第二映射关系的详细描述可以参照本申请其他实施例的相关内容，在此不做赘述。
S605：源基站向终端发送切换命令。
所述切换命令可以包括所述第二映射关系，则终端可以获取所述第二映射关系。
所述第二映射关系与所述第一映射关系可以相同，也可以不同。具体地，由于每个接入网设备基于流的QoS要求独立配置DRB与流的映射关系，因此，目标基站配置的DRB与流的映射关系与源基站配置的DRB与流的映射关系可能相同，也可能不同。
可选地，所述响应消息以及切换命令中还包含第三映射关系，所述第三映射关系是指目标基站配置的映射DRB和目标基站配置的DRB的对应关系。
S606：源基站向目标基站发送PDCP层的空口传输状态。
其中，PDCP层的空口传输状态是指：目标基站的DRB中PDCP层的数据包的发送状态和接收状态。其中上行数据包的传输状态包含：第一个丢失的PDCP SDU的序列号，以及第一个丢失的PDCP SDU和接收到的最后的PDCP SDU之间的PDCP SDU的接收状态，所述接收状态具体是指接收到数据包或者没有接收到数据包。下行数据包的传输状态包含：目标基站需要分配序列号的下一个PDCP SDU的序列号，所述序列号包含PDCP SN和HFN。
S607：源基站向目标基站发送转发数据包。
其中，所述转发数据包包括上行方向的转发数据包，和/或，下行方向的转发数据包。关于转发数据包的详细描述可以参照图2-图4所示实施例的相关内容，在此不做赘述。
具体地，源基站可以通过与目标基站间的隧道向目标基站发送所述转发数据包。关于各类隧道以及隧道的具体建立方式可以参照图2-图5所示实施例的相关内容，在此不做赘述。
在该实施例中，源基站的PDCP实体获取数据包的流标识，从而源基站可以为所述转发数据包增加流标识，进而由目标基站可以根据流标识将转发数据包映射到相应的DRB。关于源基站生成包含流标识的数据包的具体描述可以参照图5所示实施例中的相关内容，在此不做赘述。
S608：终端接入目标基站。
S609：目标基站进行路径切换。
可选地，所述方法还包括，目标基站通知核心网的控制面管理网元，由控制面管理网元通知用户面网元，将后续和终端相关的数据包发送到目标基站。
可选地，在本申请的一个实施方式中，当终端切换到目标基站之后，所述方法还包括，S6010：终端与目标基站进行数据通信。
其中，所述数据通信包括上行数据传输和/或下行数据传输。
具体地，在上行数据传输或者下行数据传输过程中，对于通过不同类型的隧道接收到的转发数据包，有不同的传输方式，本申请实施例对此不做特别限定。此外，在下行数据传输过程中，目标基站可以向终端发送下行方向的转发数据包以及从核心网接收的其他下行数据包；在上行数据传输过程中，目标基站可以向核心网发送上行方向的转发数据包以及从终端接收的其他上行数据包。转发数据包优先于从终端接收的其他上行数据包或者从核心网接收的其他下行数据包进行传输。可选地，承载上行数据包的DRB和承载下行数据包的DRB可以是同一个DRB，即，由一个双向的DRB来提供上业务及下行业务，也可以由不同的DRB分别承载上行数据包和下行数据包。
下行方向，目标基站可以通过所述第一DRB或者第二DRB向终端发送包括转发数据包在内的下行数据包。
例如，当所述转发数据包通过一条基于DRB的隧道以及一条基于会话建立的隧道发送给目标基站时，目标基站向终端发送数据包的具体方式可以包括：
若第二映射关系与第一映射关系相同，目标基站可以采用第一DRB向终端发送所述转发数据包，进而，在转发数据包发送完成后，仍然采用第一DRB发送通过SDAP层从核心网接收的其他下行数据包。
若第二映射关系与第一映射关系不同，目标基站可以通过所述第一DRB向终端发送所述目标基站通过所述基于DRB建立的隧道接收到的数据包；并通过所述第二DRB向所述终端发送所述目标基站通过所述基于会话建立的隧道接收到的数据包。
可选地，所述目标基站在所述第二DRB上向所述终端发送所述转发数据包中包含流标识的数据包，且，所述接入网设备在所述第一DRB上向所述终端发送所述转发数据包中不包含流标识的数据包。
可选地，所述目标基站可以在所述第一DRB上向所述终端发送所述转发数据包中已分配序列号的PDCP SDU，且，所述目标基站在所述第二DRB上向所述终端发送包含流标识且未分配序列号的PDCP SDU。所述目标基站还可以在所述第二DRB上向所述终端发送所述源基站的SDAP层的数据包。可以理解，第一DRB可以用于传输有流标识的数据包或者没有流标识的数据包，因此，只要具有序列号的PDCP SDU，无论是否包含流标识，都可以在第一DRB上传输。
可选地，源基站可以为PDCP层中缓存的未分配序列号的PDCP SDU分配序列号，将分配了序列号的PDCP SDU作为转发数据包的一部分通过所述基于DRB建立的隧道发送至目标基站，进而，目标基站可以在后续通信过程中在第一DRB中直接传输上述已分配序列号的PDCP SDU，无需再为其分配序列号，简化流程，提升传输效率。
又例如，当所述转发数据包通过一条基于会话建立的隧道发送给目标基站时，所述目标基站可以通过SDAP实体将所述数据包中的已分配序列号的PDCP层的数据包路由到所述第一DRB，并通过所述第一DRB向所述终端发送所述已分配序列号的PDCP层的数据包；所述目标基站通过SDAP实体将其余数据包，例如SDAP层缓存的数据包和/或PDCP层的未分配序列号的数据包，路由到所述第二DRB，并通过所述第二DRB向所述终端发送所述其余数据包。可选地，SDAP实体可以根据目标基站中的流到DRB的映射关系来确定多个第二DRB，将所述其余数据包承载于所述多个第二DRB传输至终端。其中，转发数据包中已分配序列号的PDCP层的数据包可携带第三DRB的标识，目标基站可根据第三DRB和第一DRB的映射关系，将收到的已分配序列号数据包转发到对应的第一DRB。
又例如，当所述转发数据包通过一条或多条基于DRB建立的隧道发送给目标基站时，目标基站向终端发送数据包的具体方式包括：
若第一映射关系与第二映射关系相同，目标基站通过所述第一DRB向所述终端发送所述目标基站通过所述基于DRB建立的隧道接收到的数据包，进而，在转发数据包发送完成后，仍然采用第一DRB发送通过SDAP层从核心网接收的其他数据包。
可选地，源基站可以为PDCP层中缓存的未分配序列号的PDCP SDU分配序列号，将分配了序列号的PDCP SDU作为转发数据包的一部分发送至目标基站，不做赘述。
若第一映射关系与第二映射关系不同，所述目标基站通过所述第一DRB向所述终端发送所述目标基站通过所述基于DRB建立的隧道接收到的数据包中不包含流标识的数据包；且述目标基站通过所述第二DRB向所述终端发送所述目标基站通过所述基于DRB建立的隧道接收到的数据包中包含流标识的数据包。具体地，当目标基站与源基站之间存在两条基于DRB建立的隧道，则通过基于 源基站的第三DRB以及第一DRB建立的隧道传输的数据包则在第一DRB上传输，且通过基于源基站的DRB以及第二DRB建立的隧道传输的数据包则在第二DRB上传输。当目标基站与源基站之间只有一条基于源基站的第三DRB以及第一DRB建立的隧道，则目标基站可以通过SDAP实体将接收到的数据包中包含流标识的数据包路由到第二DRB，由第二DRB进行传输。在该实施方式中，其他不包含流标识的数据包则通过第一DRB发送。在该实施方式中，源基站可通过SDAP实体在切换时发送流标识到PDCP层的方式来获取转发数据包的流标识，并在转发数据包中指示该流标识用于切换。源基站还可以通过本申请实施例中描述的其它获取流标识的方式，对PDCP层中没有PDCP SN的数据包都产生流标识，并将包含流标识的数据包转发到目标基站，不做赘述。
在该实施方式中，源基站还可以通过本申请中描述的各种获取流标识的方式，为未分配序列号的PDCP层的数据包生成流标识，并将包含流标识的转发数据包发送到目标基站，不做赘述。
可选地，若转发数据包为未分配序列号的PDCP层的数据包，且其中部分数据包包含流标识，其余数据包不包含流标识，则该转发数据包通过第一DRB发送给终端，可以提升数据包传输的连续性与准确定。对于具有Reflective QoS特性的非接入层的流的数据包可以采用上述在第一DRB上发送的方式。其中，Reflective QoS是指流具备上行和下行对称特性，即上行方向的流和下行方向的流的QoS相同，上行和下行的业务流模板(traffic flow template，TFT)也是对称的，例如上行的源地址和源端口号，为下行的目的地址和目的端口号；上行的目的地址和目的端口号，为下行的源地址和源端口号。在该场景中，接入网设备在空口数据包中携带流标识，终端根据接收到的流标识和该下行数据包的五元组信息，获取上行方向的流的QoS和对应的TFT。
上行方向，终端可以通过所述第一DRB或者第二DRB向目标基站发送包括转发数据包在内的上行数据包。
可选地，终端向目标基站发送的上行数据包包括：终端通过源基站的DRB未传输成功的已分配序列号的PDCP SDU和未分配序列号的PDCP SDU等需要继续进行上行传输的数据包。其中，上行数据包中都包含流标识。
可选地，目标基站从第一DRB上接收上行数据包。具体地，若第一映射关系和第二映射关系相同，终端可将PDCP层的数据包在第一DRB中继续发送。所述PDCP层的数据包包括未传输成功的已分配序列号的PDCP SDU和/或未传输成功的未分配序列号的PDCP SDU。
可选地，源基站给该终端发送状态报告(status report)，终端根据该状态报告来确定将发送的数据包。其中，所述状态报告可以是PDCP状态报告，指示目标基站中的映射DRB上的PDCP SDU的接收状态，用于通知终端发送接收侧未正确接收的PDCP SDU。若目标基站没有发送上述PDCP状态报告，则终 端可以在映射DRB上发送缓存中所有的PDCP SDU。
若第一映射关系和第二映射关系不同，终端可将PDCP层中缓存的已分配序列号的PDCP SDU和/或未分配序列号的PDCP SDU等数据包均在第一DRB中继续发送。终端可在PDCP层的数据包发送完成后，由SDAP实体将其他数据包，例如SDAP层缓存的数据包，路由到第二DRB上发送。其中，终端的PDCP实体可以通知目标基站的SDAP实体数据包发送已完成。
可选地，目标基站从第二DRB上接收所述上行数据包。该接收方式可以适用于第一映射关系和第二映射关系不同的场景。具体地，终端可以将各DRB对应的PDCP层的数据包，包括未传输成功的已分配序列号的PDCP SDU和/或未传输成功的未分配序列号的PDCP SDU，按序发送到SDAP实体，所述按序发送是指按照PDCP层从SDAP层接收上述数据包的顺序再将数据包发送到SDAP层。其中，SDAP实体是按照会话建立的，且发送到SDAP实体的数据包都包含流标识。所述PDCP PDU包含了目标基站中已成功接收的数据包，终端在目标基站中对应的DRB的PDCP实体去除PDCP PDU的序列号、解密等操作，将PDCP PDU转变成PDCP SDU，或者由终端在目标基站中的对应SDAP实体去除PDCP PDU的序列号。终端的SDAP实体按照第二映射关系将从PDCP层收到的数据包路由到对应的DRB，即第二DRB，且SDAP实体先向第二DRB发送从PDCP层收到的数据包，再将从上层收到的数据包发送到第二DRB。可以理解，此场景下，目标基站和第二接入网设备可以不进行上行方向的数据前传过程。
可选地，所述目标基站从所述第一DRB上接收所述上行数据包中已分配序列号的PDCP层的数据包，以及，从所述第二DRB上接收所述上行数据包中的未分配序列号的PDCP层的数据包和/或SDAP层的数据包。该接收方式适用于第一映射关系和第二映射关系不同的场景。具体地，终端可以将未成功传输的已分配序列号的PDCP SDU在第一DRB中继续发送，其中，源基站可以给该终端发送状态报告，由终端根据该状态报告来确定将发送的数据包，不做赘述。此外，终端可以将PDCP SDU，按序发送到SDAP实体。其中，发送到SDAP实体的数据包都包含流标识。SDAP实体按照第二映射关系将从PDCP层收到的数据包路由到对应的DRB，SDAP实体先发送从PDCP收到的数据包，再发送从上层收到的数据包到对应的DRB。
在本申请的一个实施方式中，当空口上进行的是非确认模式(unacknowledged mode，UM)的业务，例如，小区广播或IP电话等业务，目标基站和源基站之间不需要传递所述业务相关的数据包的空口传输状态信息。具体地，在上行方向，源基站将接收成功的数据包发送到核心网，不需要进行数据前传。终端接入目标基站，终端根据目标基站配置的第二映射关系，终端在新DRB上传输数据包。这种场景适用于第一映射关系和第二映射关系相同或不同的场景。在下行方向，源基站将未传输的数据包和从核心网接收的新数据 包转发到目标基站。与确认模式(acknowledged mode，AM)的业务相比，转发数据包中不包含目标基站中DRB上的已分配序列号的PDCP SDU，即源基站无需发送在源DRB未发送成功的PDCP SDU给目标基站。目标基站或源基站的其余行为与AM模式下的下行数据传输过程一致，不做赘述。
可选地，目标基站在接收到所述上行数据包后，将所述上行数据包按照PDCP SN递增顺序的已分配序列号的PDCP SDU、以及未分配序列号的PDCP SDU的顺序投递到核心网。
在本申请的一个实施方式中，在上述下行方向或上行方向的数据包的传输过程，属于同一个流的数据包可以在不同的DRB中传输，例如同一个流中的部分数据包在映射SRB上传输，其余数据包在新DRB上传输，且映射DRB和新DRB仅是在时间维度上的区分，例如先传输到目标基站的数据包在映射DRB上传输，后传输到目标基站的数据包在新DRB上传输，则可以采用如下任意一种方式可以使得同一个流中的数据包按序传输。
可选地，由发送端进行数据包传输顺序的控制。具体地，当第一DRB发送转发数据包完毕后，通知第二DRB发送其他数据包。可选地，可以由第一DRB对应的PDCP实体通知第二DRB对应的PDCP实体。若第一DRB中包含多个流的数据包，则第一DRB可能需要通知每一个流映射的第二DRB。或者，当第一DRB发送转发数据包完毕后，通知SDAP实体。例如，可以由第一DRB的PDCP通知对应的SDAP实体转发数据包发送已完成。若第一DRB对应的PDCP实体可以获知流标识，则PDCP可以通知对应的SDAP实体转发数据包中属于一个流的数据包发送完成。SDAP实体接收到PDCP实体发送的转发数据包发送成功，则SDAP实体开始将对应流的数据包路由到对应的第二DRB上，所述对应流的数据包是第一DRB中发送完成的流在SDAP层中的数据包。
可选地，由接收端进行数据包传输顺序的控制。具体地，接收端接收来自第一DRB和第二DRB的同一流中的数据包，接收端可以根据结束标记来区分来自不同DRB的数据包，从而对不同DRB收到的数据包进行排序。例如，接收端先向上层协议层实体投递从第一DRB中接收到的所述流中的数据包，再投递从第二DRB中接收到的所述流中的数据包。所述结束标记用于指示数据包在第一DRB中传输的结束。其中，所述结束标记可以是一个独立的数据包或控制包，例如SDAP层或PDCP层的独立数据包或控制包，或者，也可以指示某一数据包，例如PDCP PDU，为结束标记。
可以理解，在下行方向中，发送端为网络侧，例如是目标基站，且接收端为终端侧；在上行方向中，发送端为终端侧，且接收端为网络侧，例如是目标基站。
在本申请的一个实施方式中，若源基站的PDCP层未获取数据包的流标识，则源基站向目标基站发送的转发数据包不包含流标识。在此场景中，在下行方 向，目标基站可以采用如下任意一种方式向终端发送数据包：
当所述转发数据包通过一条或多条基于DRB建立的隧道发送给目标基站时，目标基站可以采用第一DRB(即映射DRB)向终端发送所述转发数据包。进而，在转发数据包发送完成后，仍然采用第一DRB发送通过SDAP层从核心网接收的其他数据包。可以理解，该发送方法适用于第一映射关系与第二映射关系相同或者不同的任一场景。
当所述转发数据包通过一条基于DRB的隧道以及一条基于会话建立的隧道发送给目标基站时，基于会话建立的隧道可以用于传输SDAP层中缓存的数据包，而基于DRB建立的隧道，可以用于传输PDCP层中缓存的数据包。具体地，若第二映射关系与第一映射关系相同，目标基站可以采用第一DRB(映射DRB)向终端发送所述转发数据包，进而，在转发数据包发送完成后，仍然采用第一DRB发送通过SDAP层从核心网接收的其他数据包。若第二映射关系与第一映射关系不同，那么，所有基于DRB的隧道的转发数据包都在目标基站的对应的映射DRB上发送。其中，目标基站的SDAP实体可以将从所述基于会话建立的隧道中接收的转发数据包统一进行路由到新DRB中，由新DRB进行数据包的发送。
可选地，源基站可以为PDCP层中缓存的PDCP SDU分配序列号，将分配了序列号的PDCP SDU作为转发数据包的一部分发送至目标基站，不做赘述。
当所述转发数据包通过一条基于会话建立的隧道发送给目标基站时，目标基站按照第二映射关系，将转发数据包路由到第二DRB并发送。由接收端丢弃所有乱序的数据包。进一步的，接收端可以通知目标基站丢弃的数据包的初始序列号，或者向核心网投递的最后一个数据包的序号。在此场景下，目标基站可以不建立映射DRB。其中，所述转发数据包是指从PDCP层中的标识数据包之后的所有数据包，所述标识数据包，用于标识发送端不会再发送该数据包之前的数据包，发送端会重复发送该数据包之后的数据包。
采用本申请实施例提供的数据传输方法，在下行方向，通过不同类型的隧道传输转发数据包，并采用与隧道类型相应的传输方式向终端发送所述转发数据包；在上行方向，终端采用不同DRB向网络侧发送上行数据包。在本申请实施例中，提供了灵活多样的数据包传输方式，可以根据网络实际情况进行选择数据包传输方式，从而避免在切换或者双连接等场景中，由于每个基站独立配置流与DRB的映射关系而导致的数据丢包或者重复发包问题，提升终端业务的连续性，提高通信质量。
图7是本申请实施例提供的一种接入网设备700的结构示意图。
接入网设备700可以应用于图1所示的通信系统。接入网设备700可以执 行图2或图5所示的实施例中第一接入网设备或者图6所示的实施例中的目标基站执行的操作。
如图7所示，所述接入网设备700包括：
接收单元701：用于从第二接入网设备接收转发数据包。
可选地，在切换场景中，所述接入网设备700是目标基站，所述第二接入网设备为源基站。
可选地，在双连接场景中，所述接入网设备700为辅基站，所述第二接入网设备为主基站；或者，所述接入网设备700为主基站，所述所述第二接入网设备为辅基站。
处理单元702：用于将所述转发数据包中至少一个包含流标识的数据包映射到第一DRB，所述第一DRB对应于所述第二接入网设备的DRB。
其中，所述第一DRB与所述第二接入网设备的DRB分别满足第一映射关系，所述第一映射关系为所述第二接入网设备中的流与DRB的映射关系。
可选地，处理单元702还用于：将所述转发数据包中不包含流标识的数据包映射到所述第一DRB。
可选地，处理单元702还用于：根据第二映射关系，将所述转发数据包中映射到所述第一DRB之外的至少一个包含流标识的数据包映射到第二DRB；其中，所述第二映射关系为所述第一接入网设备中的流与DRB的映射关系。
其中，第一DRB是可以延续第二接入网设备的DRB的传输状态的映射DRB。第二DRB是接入网设备700根据自身配置的流与DRB的映射关系即第二映射关系建立的新DRB。
可以理解，第一DRB可以用于传输包含流标识的数据包或者不包含流标识的数据包；第二DRB可以用于传输包含流标识的数据包。
关于第一DRB、第二DRB、第一映射关系及第二映射关系的详细描述，均可以参照本申请其他实施例的相关内容，不做赘述。
可选地，所述处理单元702还用于，在第一DRB完成数据包的发送后，释放所述第一DRB，详细描述可以参照本申请其他实施例的相关内容，不做赘述。
可选地，在本申请的一个实施方式中，所述接收单元701具体用于：通过基于DRB建立的隧道以及基于会话建立的隧道从所述第二接入网设备接收所述转发数据包。其中，所述基于DRB建立的隧道可以用于传输所述第二接入网设备的已分配序列号的PDCP层的数据包；且所述基于会话建立的隧道可以用于传输所述第二接入网设备的SDAP层的数据包，和/或，所述基于会话建立的隧道用于传输所述第二接入网设备的包含流标识且未分配序列号的PDCP层的数 据包。进而，处理单元702可以将通过基于DRB建立的隧道接收的数据包映射到第一DRB，并将通过基于会话建立的隧道接收的数据包映射到第二DRB。
可选地，在本申请的一个实施方式中，所述接收单元701具体用于：通过一条或多条基于DRB建立的隧道从所述第二接入网设备接收所述转发数据包。进而，处理单元702可以将接收到的转发数据包中不包含流标识的数据包映射到第一DRB，并将所述转发数据包中包含流标识的数据包映射到第二DRB。
可选地，在本申请的一个实施方式中，所述接收单元701具体用于：通过基于会话建立的隧道从所述第二接入网设备接收所述转发数据包中包含流标识的数据包。进而，所述处理单元702可以通过SDAP实体将所述转发数据包中已分配序列号的PDCP层的数据包路由到所述第一DRB；且将未分配序列号的PDCP层的数据包或者SDAP层的数据包路由到所述第二DRB。
可选地，所述接入网设备700还包括发送单元703，用于通过第一DRB，或者，通过第一DRB与第二DRB向终端发送包括所述转发数据包在内的下行数据包。例如，所述发送单元703用于通过所述第一DRB向终端发送所述转发数据包中已分配序列号的PDCP层的数据包；且通过所述第二DRB向终端发送所述转发数据包中未分配序列号的PDCP层的数据包。
关于上述通过不同类型的隧道接收所述转发数据包，以及与不同类型隧道对应的下行数据传输方式的具体描述可以参照本申请其他实施例的相关内容，在此不做赘述。
图8是本申请实施例提供的一种接入网设备800的结构示意图。
接入网设备800可应用于如图1所示的通信系统。接入网设备800可以执行图3或图5所示实施例中的第一接入网设备或者图6所示实施例中的目标基站执行的操作。
所述接入网设备800包括：
接收单元801：用于从第二接入网设备接收转发数据包。
处理单元802：用于将所述转发数据包中不包含流标识的数据包映射到第一数据无线承载DRB，所述第一DRB对应于所述第二接入网设备的DRB；以及，用于根据第二映射关系，将所述转发数据包中包含流标识的数据包映射到第二DRB，其中，所述第二映射关系为所述第一接入网设备中的流与DRB的映射关系。
其中，所述第一DRB与所述第二接入网设备的DRB分别满足第一映射关系，所述第一映射关系为所述第二接入网设备中的流与DRB的映射关系。
关于第一DRB、第二DRB、第一映射关系及第二映射关系的详细描述，均可以参照本申请其他实施例的相关内容，不做赘述。
可选地，处理单元802还用于，通过SDAP实体将所述转发数据包中包含流标识的数据包路由到所述第二DRB。
可选地，在本申请的一个实施方式中，接入网设备800还包括发送单元803，用于通过所述第一DRB向终端发送所述转发数据包中已分配序列号且不包含流标识的数据包；并通过所述第二DRB向终端发送所述转发数据包中未分配序列号且包含流标识的数据包。
可选地，所述处理单元802还用于，在第一DRB完成数据包的发送后，释放所述第一DRB，详细描述可以参照本申请其他实施例的相关内容，不做赘述。
可选地，在本申请的一个实施方式中，接收单元801通过与第二接入网设备之间的隧道接收所述转发数据包。在下行方向，所述第一接入网设备与所述第二接入网设备间的隧道可以有不同的建立方式。关于通过不同类型的隧道接收所述转发数据包，以及与不同类型隧道对应的下行数据传输方式的具体描述可以参照本申请其他实施例的相关内容，在此不做赘述。
图9是本申请实施例提供的一种接入网设备900的结构示意图。
接入网设备900可以应用于图1所示的通信系统。接入网设备900可以执行图2-图5任一实施例中第二接入网设备或者图6所示的实施例中的源基站执行的操作。
接入网设备900包括：
处理单元901，用于生成包含流标识的转发数据包。
发送单元902，用于向第一接入网设备发送所述包含流标识的转发数据包。
可选地，在下行方向，所述转发数据包包括如下至少一种数据包：所述第二接入网设备的已分配序列号且未得到终端接收确认的PDCP层的数据包；所述第二接入网设备的未分配序列号的PDCP层的数据包；第一接入网设备的业务数据适配协议SDAP层的数据包。
可选地，在下行方向，发送单元902还可以用于，向所述第一接入网设备发送不包含流标识的转发数据包。
可选地，在下行方向，发送单元902可以用于通过不同类型的隧道向第一接入网设备发送上述转发数据包。关于各类隧道以及在各类隧道上传输转发数据包的具体描述可以参照本申请其他实施例的相关内容，在此不做赘述。
可选地，在本申请的一个实施方式中，在下行反向，处理单元还可以用于，通过PDCP实体获取流标识，从而为所述转发数据包增加流标识，生成包含流标识的转发数据包，进而由第一接入网设备解析所述转发数据包，获取所述流标识。关于如何生成包含流标识的数据包的具体描述可以参照图5所示实施例中的相关内容，在此不做赘述。
可选地，在上行方向，所述转发数据包包括：从终端接收的乱序的数据包。接入网设备900可以通过接收单元903接收所述乱序的数据包。上行方向的转发数据包都包含流标识。发送单元902可以通过基于DRB建立的隧道向第一接入网设备发送上行方向的转发数据包，在此不做赘述。
图10是本申请实施例提供的一种接入网设备1000的结构示意图。
接入网设备1000可应用于如图1所示的通信系统。接入网设备1000可以执行图4所示实施例中第一接入网设备执行的操作，或者图6所示实施例中的目标基站执行的操作。
所述接入网设备1000包括：
接收单元1001，用于从第二接入网设备接收转发数据包，所述转发数据包包含流标识，所述转发数据包中包括所述第二接入网设备从终端接收的乱序的数据包。
发送单元1002：用于将接收到的转发数据包发送给核心网设备。
可选地，接收单元1001通过与第二接入网设备间的隧道接收所述转发数据包。所述隧道可以是第一接入网设备和第二接入网设备之间基于DRB建立的隧道，可以参照本申请其他实施例中基于DRB建立的隧道的相关描述，不做赘述。
接收单元1001还用于：从终端接收上行数据包，其中，所述上行数据包包括以下至少一种数据包：所述终端未成功向所述第二接入网设备发送的已分配序列号的PDCP层的数据包；所述终端的未分配序列号的PDCP层的数据包；所述终端的SDAP层的数据包。
可选地，接收单元1001具体用于通过第一DRB接收所述上行数据包。
可选地，接收单元1001具体用于通过第二DRB接收所述上行数据包。
可选地，接收单元1001具体用于通过所述第一DRB接收所述上行数据包中的所述终端的已分配序列号的PDCP层的数据包；且所述第一接入网设备通过所述第二DRB接收所述上行数据包中的所述终端的PDCP层中的未分配序列号的数据包和/或SDAP层的数据包。
可选地，接收单元1001具体用于通过所述第一DRB接收所述上行数据包 中的所述终端的PDCP层的数据包；且所述第一接入网设备通过所述第二DRB接收所述上行数据包中的所述终端的SDAP层的数据包。
其中，所述第一DRB是映射DRB。第二DRB是新DRB，关于第一DRB与第二DRB的详细描述可以参照本申请其他实施例的相关内容，不做赘述。
图11是本申请实施例提供的一种终端1100的结构示意图。
终端1100可应用于如图1所示的通信系统。终端1100可以执行图2-图6任一实施例中的终端执行的操作。
所述终端1100包括：
发送单元1101：用于向接入网设备发送上行数据包，所述上行数据包包含流标识；和/或
接收单元1102：用于从接入网设备接收下行数据包，所述下行数据包中至少一个数据包包含流标识。
其中，所述下行数据包中包含下行方向的转发数据包，关于转发数据包的具体内容可以参照本申请其他实施例的相关描述，在此不做赘述。
可选地，发送单元1101具体用于：通过第一DRB向接入网设备发送上行数据包。
可选地，发送单元1101具体用于：通过第二DRB向接入网设备发送上行数据包。
可选地，发送单元1101具体用于：通过所述第一DRB向接入网设备发送所述上行数据包中的已分配序列号的PDCP层的数据包；且通过所述第二DRB向接入网设备发送所述上行数据包中的PDCP层中的未分配序列号的数据包和/或SDAP层的数据包。其中，通过第一DRB传输的PDCP层的数据包可以是包含流标识的数据包；也可以是不包含流标识的数据包。
可选地，发送单元1101具体用于：通过所述第一DRB向接入网设备发送所述上行数据包中的PDCP层的数据包；且通过所述第二DRB向接入网设备发送所述上行数据包中的SDAP层的数据包。其中，所述PDCP层的数据包包括已分配序列号的数据包和未分配序列号的数据包。
可选地，接收单元1102具体用于：通过第一DRB从接入网设备接收下行数据包。
可选地，接收单元1102具体用于：通过第二DRB从接入网设备接收包含流标识的下行数据包。
可选地，接收单元1102具体用于：通过第一DRB从接入网设备接收下行数据包中不包含流标识的数据包，且通过第二DRB从接入网设备接收下行数据包中包含流标识的数据包。
可选地，接收单元1102具体用于：通过第一DRB从接入网设备接收下行数据包中已分配序列号的PDCP层的数据包，且通过第二DRB从接入网设备接收下行数据包中包含流标识且未分配序列号的PDCP层的数据包和/或SDAP层的数据包。
其中，所述第一DRB是映射DRB。第二DRB是新DRB，关于第一DRB与第二DRB的详细描述可以参照本申请其他实施例的相关内容，不做赘述。
上述接入网设备是终端已经接入的接入网设备。当所述接入网设备是终端切换后接入的接入网设备或双连接过程中接收分流数据的接入网设备，则所述下行数据包中包含下行方向的转发数据包以及接入网设备从核心网接收的其他下行数据包，详细描述可以参照本申请其他实施例的相关内容，不做赘述。
图12是本申请实施例提供的一种接入网设备1200的结构示意图。
接入网设备1200可以应用于图1所示的通信系统。接入网设备1200可以执行图2-图5任一实施例中第一接入网设备或者图6所示的实施例中的目标基站执行的操作。
接入网设备1200包括一个或多个远端射频单元(remote radio unit，RRU)1201和一个或多个基带单元(baseband unit，BBU)1202。RRU1201可以称为收发单元、收发机、收发电路、或者收发器等等，其可以包括至少一个天线12011和射频单元12012。RRU1201分主要用于射频信号的收发以及射频信号与基带信号的转换，例如用于向UE发送上述方法实施例中所述的信令指示等信息。所述BBU1202部分主要用于进行基带处理，对接入网设备进行控制等。RRU1201与BBU1202可以是可以是物理上设置在一起，也可以物理上分离设置的，即分布式接入网设备。在接入网设备由CU与DU组成时，RRU的功能可以由DU实现，BBU的功能可以由CU实现；或者RRU的功能与BBU的部分功能由DU实现，且BBU的其他功能由CU实现；或者RRU的部分功能由DU实现，且RRU的其他功能与BBU的功能由CU实现，不做限定。
所述BBU1202为接入网设备的控制中心，也可以称为处理单元，主要用于完成基带处理功能，如信道编码，复用，调制，扩频等等。例如所述BBU可以用于控制接入网设备1200可以执行图2-图5任一实施例中第一接入网设备或者图6所示的实施例中的目标基站执行的操作。
在一个示例中，BBU1202可以由一个或多个单板构成，多个单板可以共同 支持单一接入制式的无线接入网(如NR接入网)，也可以分别支持不同接入制式的无线接入网。所述BBU1202还包括存储器12021和处理器12022。所述存储器12021用以存储必要的指令和数据。例如存储器12021存储上述实施例中的UE的上下文。所述处理器12022用于控制接入网设备1200进行必要的动作，例如用于控制接入网设备1200执行执行图2-图4任一实施例中的第一接入网设备的动作、或者控制接入网设备1200执行如图5所示实施例中目标基站的动作。所述存储器12021和处理器12022可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板公用相同的存储器和处理器。此外每个单板上还设置有必要的电路。
在一个示例中，BBU1202还包括通信单元12023，所述通信单元12023用于支持接入网设备1200与其他接入网设备设备或者核心网设备等网元进行通信，例如支持接入网设备1200从第二接入网设备接收转发数据包。所述通信单元12023可以包括通信接口，例如接入网设备1200与第二接入网设备间的通信接口，或者接入网设备1200与核心网设备间的通信接口。
图13是本申请实施例提供的一种接入网设备1300的结构示意图。
接入网设备1300可以应用于图1所示的通信系统。接入网设备1300可以执行可以执行图2-图5任一实施例中第二接入网设备或者图6所示的实施例中的源基站执行的操作。
接入网设备1300包括一个或多个RRU1301和一个或多个BBU1302。
所述BBU1302可以用于控制接入网设备1300执行图2-图5所示实施中的第二接入网设备执行的操作，或者控制接入网设备1300执行图6所示实施例中的源接入网设备执行的操作。
在一个示例中，BBU1302可以由一个或多个单板构成，多个单板可以共同支持单一接入制式的无线接入网(如NR接入网)，也可以分别支持不同接入制式的无线接入网。所述BBU1302还包括存储器13021和处理器13022。所述存储器13021用以存储必要的指令和数据。例如存储器13021存储上述实施例中从第一接入网设备获取的UE的上下文。所述处理器13022用于控制接入网设备1300进行必要的动作，例如用于控制接入网设备1300执行如图2-图5所示实施例中第二接入网设备的动作，或者控制接入网设备1300执行图6所示实施例中的源基站的动作。
在一个示例中，BBU1302还包括通信单元13023，所述通信单元13023用于支持接入网设备1300与其他接入网设备设备或者核心网设备等网元进行通信，例如支持接入网设备1300向第一接入网设备发送转发数据包。所述通信单元13023可以包括通信接口，例如接入网设备1300与第一接入网设备间的通信接 口，或者接入网设备1300与核心网设备间的通信接口。
关于RRU和BBU功能的详细说明，以及BBU中的存储器及处理器等装置的功能的详细说明可以参照图13所示实施例中的相关内容，在此不做赘述。
图14是本申请实施例提供的一种终端1400的结构示意图。
终端1400可以应用于图1所示的通信系统。终端1400可以执行图2-图6任一实施例中的终端执行的操作。
为了便于说明，图14仅示出了终端的主要部件。如图14所示，终端1400包括处理器、存储器、控制电路、天线以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理，以及对整个用户设备进行控制，执行软件程序，处理软件程序的数据，例如用于支持终端1400执行附图2-图6部分所描述的终端的动作。存储器主要用于存储软件程序和数据，例如存储上述实施例中所描述的终端的上下文。控制电路主要用于基带信号与射频信号的转换以及对射频信号的处理。控制电路和天线一起也可以叫做收发器，主要用于收发电磁波形式的射频信号，例如可以用于执行向接入网设备发送上行数据包，或者从接入网设备接收下行数据包，具体可参照方法部分实施例的相关描述。输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。
当终端开机后，处理器可以读取存储单元中的软件程序，解释并执行软件程序的指令，处理软件程序的数据。当需要通过无线发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。
本领域技术人员可以理解，为了便于说明，图14仅示出了一个存储器和处理器。在实际的终端中，可以存在多个处理器和存储器。存储器也可以称为存储介质或者存储设备等，本申请实施例对此不做限制。
作为一种可选的实现方式，处理器可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端进行控制，执行软件程序，处理软件程序的数据。图14中的处理器集成了基带处理器和中央处理器的功能，本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独立的处理器，通过总线等技术互联。本领域技术人员可以理解，终端可以包括多个基带处理器以适应不同的网络制式，终端可以包括多个中央处理器以增强其处理能力，终端的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中 央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储单元中，由处理器执行软件程序以实现基带处理功能。
图15是本申请实施例提供的一种通信系统1500的示意图。
该通信系统1500中包括：
第一接入网设备1501，该第一接入网设备可以执行图2-图5任一实施例中的第一接入网设备执行的操作或者执行图6所示实施例中的目标基站执行的操作。例如，可以是图7、图8、图10或图12所示实施例的接入网设备。
第二接入网设备1502，该第二接入网设备1502可以执行图2-图5任一实施例中的第二接入网设备执行的操作或者执行图6所示实施例中的源基站执行的操作。例如，可以是图9或图13实施例所示的接入网设备。
该通信系统中还可以包括与第一接入网设备1501、第二接入网设备1502分别进行通信的终端1503，该终端1503可以执行图2-图6任一实施例中的终端执行的操作，可以是图11或图14实施例所述的终端。
本所属领域的技术人员可以清楚地了解到，本申请提供的各实施例的描述可以相互参照，为描述的方便和简洁，例如关于本申请实施例提供的各装置、设备的功能以及执行的步骤可以参照本申请方法实施例的相关描述，各方法实施例之间、各装置实施例之间也可以互相参照。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、设备和方法，在没有超过本申请的范围内，可以通过其他的方式实现。例如，以上所描述的实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑 功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
另外，所描述系统、设备和方法以及不同实施例的示意图，在不超出本申请的范围内，可以与其它系统，模块，技术或方法结合或集成。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电子、机械或其它的形式。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (31)

  1. 一种数据传输方法，其特征在于，包括：
    第一接入网设备从第二接入网设备接收转发数据包；
    所述第一接入网设备将所述转发数据包中不包含流标识的数据包映射到第一数据无线承载DRB，所述第一DRB对应于所述第二接入网设备的DRB；
    所述第一接入网设备根据第二映射关系，将所述转发数据包中包含流标识的数据包映射到第二DRB，其中，所述第二映射关系为所述第一接入网设备中的流与DRB的映射关系。
  2. 根据权利要求1所述的方法，其特征在于，所述第一DRB对应于所述第二接入网设备的DRB包括：
    所述第一DRB与所述第二接入网设备的DRB分别满足第一映射关系，所述第一映射关系为所述第二接入网设备中的流与DRB的映射关系。
  3. 根据权利要求1或2所述的方法，所述方法还包括：
    所述第一接入网设备通过所述第一DRB向终端发送所述转发数据包中已分配序列号且不包含流标识的数据包；
    所述第一接入网设备通过所述第二DRB向终端发送所述转发数据包中未分配序列号且包含流标识的数据包。
  4. 根据权利要求1-3任一所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备通过业务数据适配协议SDAP实体将所述转发数据包中包含流标识的数据包路由到所述第二DRB。
  5. 根据权利要求1-4任一所述的方法，其特征在于，所述第一接入网设备从第二接入网设备接收转发数据包包括：
    所述第一接入网设备通过基于DRB建立的隧道以及基于会话建立的隧道从所述第二接入网设备接收所述转发数据包；
    其中，所述基于DRB建立的隧道用于传输所述第二接入网设备的已分配序列号的分组数据汇聚协议PDCP层的数据包；
    所述基于会话建立的隧道用于传输所述第二接入网设备的SDAP层的数据包，和/或，用于传输所述第二接入网设备的包含流标识且未分配序列号的PDCP层的数据包。
  6. 根据权利要求1-4任一所述的方法，其特征在于，所述第一接入网设备从第二接入网设备接收转发数据包包括：
    所述第一接入网设备通过基于DRB建立的隧道从所述第二接入网设备接收所述转发数据包。
  7. 根据权利要求1-4任一所述的方法，其特征在于，所述第一接入网设备从第二接入网设备接收转发数据包包括：
    所述第一接入网设备通过基于会话建立的隧道从所述第二接入网设备接收所述转发数据包中包含流标识的数据包。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括，
    所述第一接入网设备通过SDAP实体将从所述基于会话建立的隧道接收的已分配序列号的PDCP层的数据包路由到所述第一DRB；且将未分配序列号的PDCP层的数据包或者SDAP层的数据包路由到所述第二DRB。
  9. 根据权利要求1-8任一所述的方法，其特征在于，所述转发数据包包括如下至少一种数据包：
    所述第二接入网设备的已分配序列号且未得到终端接收确认的PDCP层的数据包；所述第二接入网设备的未分配序列号的PDCP层的数据包；第二接入网设备的SDAP层的数据包。
  10. 根据权利要求1-9任一所述的方法，其特征在于，当映射到所述第一DRB上的转发数据包发送完成后，所述方法还包括：
    所述第一接入网设备释放所述第一DRB。
  11. 一种数据传输方法，其特征在于，包括：
    第一接入网设备生成包含流标识的转发数据包；
    所述第一接入网设备向第二接入网设备发送所述包含流标识的转发数据包。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备向所述第二接入网设备发送第一映射关系；
    其中，所述第一映射关系为所述第二接入网设备中的流与数据无线承载DRB的映射关系。
  13. 根据权利要求11或12所述的方法，其特征在于，第一接入网设备生成包含流标识的转发数据包包括：
    所述第一接入网设备获取所述转发数据包的缓存位置，所述缓存位置对应于所述转发数据包的流标识；
    所述第一接入网设备根据所述缓存位置获取所述转发数据包的流标识，
    所述第一接入网设备将所述流标识添加在所述转发数据包的包头中。
  14. 根据权利要求11-13任一所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备向第二接入网设备发送不包含流标识的转发数据包。
  15. 根据权利要求11-14任一所述的方法，其特征在于，所述转发数据包包括如下至少一种数据包：
    所述第一接入网设备的已分配序列号且未得到终端接收确认的分组数据汇聚协议PDCP层的数据包；所述第一接入网设备的未分配序列号的PDCP层的数据包；第一接入网设备的业务数据适配协议SDAP层的数据包。
  16. 根据权利要求11或12所述的方法，其特征在于，所述转发数据包包括：
    所述第一接入网设备从终端接收的乱序的数据包。
  17. 一种接入网设备，其特征在于，包括：存储器，处理器及收发器，其中，
    所述存储器用于存储指令；
    所述收发器用于所述接入网设备与其他网络设备通信；
    所述处理器用于执行所述存储器存储的指令，使得所述网络设备执行权利要求1-10任一所述的数据传输方法。
  18. 一种接入网设备，其特征在于，包括：存储器，处理器及收发器，其中，
    所述存储器用于存储指令；
    所述收发器用于所述接入网设备与其他网络设备通信；
    所述处理器用于执行所述存储器存储的指令，使得所述网络设备执行权利要求11-16任一所述的数据传输方法。
  19. 一种数据传输方法，其特征在于，
    第一接入网设备从第二接入网设备接收转发数据包，所述转发数据包包含流标识；
    所述转发数据包中包括所述第二接入网设备从终端接收的乱序的数据包。
  20. 根据权利要求19所述的方法，其特征在于，所述第一接入网设备从第二接入网设备接收转发数据包包括：
    所述第一接入网设备通过基于数据无线承载DRB建立的隧道从第二接入网设备接收转发数据包。
  21. 根据权利要求19所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备从终端接收上行数据包，其中，
    所述上行数据包包括以下至少一种数据包：所述终端未成功向所述第二接入网设备发送的已分配序列号的分组数据汇聚协议PDCP层的的数据包；所述终端的未分配序列号的PDCP层的数据包；所述终端的业务数据适配协议SDAP层的数据包。
  22. 根据权利要求21所述的方法，其特征在于，所述第一接入网设备从终端接收上行数据包包括：
    所述第一接入网设备通过所述第一DRB接收所述上行数据包；或者
    所述第一接入网设备通过所述第二DRB接收所述上行数据包。
  23. 根据权利要求21所述的方法，其特征在于，所述第一接入网设备从终端接收 上行数据包包括：
    所述第一接入网设备通过所述第一DRB接收所述上行数据包中的所述终端的已分配序列号的PDCP层的的数据包；且
    所述第一接入网设备通过所述第二DRB接收所述上行数据包中的所述终端的未分配序列号的PDCP层的数据包和/或SDAP层的数据包。
  24. 根据权利要求21所述的方法，其特征在于，所述第一接入网设备从终端接收上行数据包包括：
    所述第一接入网设备通过所述第一DRB接收所述上行数据包中的所述终端的PDCP层的数据包；
    所述第一接入网设备通过所述第二DRB接收所述上行数据包中的所述终端的SDAP层的数据包。
  25. 一种数据传输方法，其特征在于，包括，
    终端向第一接入网设备发送上行数据包，所述上行数据包包含流标识；和/或
    所述终端从接入网设备接收下行数据包，所述下行数据包中至少一个数据包包含流标识，所述下行数据包中包含第二接入网设备向第一接入网设备发送的转发数据包。
  26. 根据权利要求25所述的方法，其特征在于，所述终端向接入网设备发送上行数据包包括：
    所述终端通过第一数据无线承载DRB向所述第一接入网设备发送所述上行数据包中的已分配序列号的分组数据汇聚协议PDCP层的数据包；且
    所述终端通过第二DRB向所述第一接入网设备发送所述上行数据包中的分组数据汇聚协议PDCP层的未分配序列号的数据包和/或业务数据适配协议SDAP层的数据包，其中，所述第一DRB满足所述第二接入网设备中的流与DRB的映射关系；所述第二DRB满足所述第一接入网设备中的流与DRB的映射关系。
  27. 根据权利要求25所述的方法，其特征在于，所述终端向接入网设备发送上行数据包包括：
    所述终端通过第一DRB向接入网设备发送所述上行数据包中的PDCP层的数据包；且
    所述终端通过第二DRB向接入网设备发送所述上行数据包中的SDAP层的数据包，其中，所述第一DRB满足所述第二接入网设备中的流与DRB的映射关系；所述第二DRB满足所述第一接入网设备中的流与DRB的映射关系。
  28. 根据权利要求25-27任一所述的方法，其特征在于，所述终端从接入网设备接收下行数据包包括：
    所述终端通过第一DRB从所述第一接入网设备接收下行数据包中不包含流标识的数据包，且
    所述终端通过第二DRB从所述第一接入网设备接收下行数据包中包含流标识的数据包，其中，所述第一DRB满足所述第二接入网设备中的流与DRB的映射关系；所述第二DRB满足所述第一接入网设备中的流与DRB的映射关系。
  29. 根据权利要求25-27任一所述的方法，其特征在于，所述终端从接入网设备接收下行数据包包括：
    所述终端通过第一DRB从所述第一接入网设备接收下行数据包中已分配序列号的PDCP层的数据包，且
    所述终端通过第二DRB从所述第一接入网设备接收下行数据包中包含流标识且未分配序列号的PDCP层的数据包和/或SDAP层的数据包，其中，所述第一DRB满足所述第二接入网设备中的流与DRB的映射关系；所述第二DRB满足所述第一接入网设备中的流与DRB的映射关系。
  30. 一种接入网设备，其特征在于，包括：存储器，处理器及收发器，其中，
    所述存储器用于存储指令；
    所述收发器用于所述接入网设备与其他网络设备通信；
    所述处理器用于执行所述存储器存储的指令，使得所述网络设备执行权利要求19-24任一所述的数据传输方法。
  31. 一种终端，其特征在于，包括：存储器，处理器及收发器，其中，
    所述存储器用于存储指令；
    所述收发器用于所述终端与其他网络设备通信；
    所述处理器用于执行所述存储器存储的指令，使得所述终端执行权利要求25-29任一所述的数据传输方法。
PCT/CN2018/080396 2017-03-24 2018-03-24 数据传输方法、接入网设备、终端及通信系统 WO2018171791A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
BR112019019834A BR112019019834A2 (pt) 2017-03-24 2018-03-24 método de transmissão de dados, aparelho, dispositivo de rede de acesso, terminal, produto de programa de computador e sistema de comunicação
JP2019552519A JP6882510B2 (ja) 2017-03-24 2018-03-24 データ送信方法、アクセスネットワーク装置、端末、及び通信システム
RU2019133658A RU2762681C2 (ru) 2017-03-24 2018-03-24 Способ передачи данных, устройство сети доступа, терминал и система связи
EP18770178.4A EP3606149B1 (en) 2017-03-24 2018-03-24 Data transmission method, access network device, terminal and communications system
EP21177366.8A EP3941110A1 (en) 2017-03-24 2018-03-24 Data transmission method, access network device, terminal, and communications system
CN201880020910.2A CN110463256B (zh) 2017-03-24 2018-03-24 数据传输方法、接入网设备、终端及通信系统
US16/581,151 US10785825B2 (en) 2017-03-24 2019-09-24 Data transmission method, access network device, terminal, and communications system
US17/002,193 US11540349B2 (en) 2017-03-24 2020-08-25 Data transmission method, access network device, terminal, and communications system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710183306.9A CN108924876B (zh) 2017-03-24 2017-03-24 数据传输方法、接入网设备、终端及通信系统
CN201710183306.9 2017-03-24

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/581,151 Continuation US10785825B2 (en) 2017-03-24 2019-09-24 Data transmission method, access network device, terminal, and communications system

Publications (1)

Publication Number Publication Date
WO2018171791A1 true WO2018171791A1 (zh) 2018-09-27

Family

ID=63584959

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/080396 WO2018171791A1 (zh) 2017-03-24 2018-03-24 数据传输方法、接入网设备、终端及通信系统

Country Status (7)

Country Link
US (2) US10785825B2 (zh)
EP (2) EP3941110A1 (zh)
JP (1) JP6882510B2 (zh)
CN (3) CN108924876B (zh)
BR (1) BR112019019834A2 (zh)
RU (1) RU2762681C2 (zh)
WO (1) WO2018171791A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111225423A (zh) * 2018-11-27 2020-06-02 中国移动通信有限公司研究院 一种数据前转的方法和设备
CN111586769A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 无线通信系统中的切换方法、装置及系统

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11582654B2 (en) 2016-11-04 2023-02-14 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods of handing over a wireless device
CN109041119B9 (zh) * 2017-06-08 2020-07-03 维沃移动通信有限公司 一种数据传输方法、相关设备及系统
CN108702261B (zh) * 2017-08-18 2021-10-08 北京小米移动软件有限公司 数据承载重映射过程中数据包处理的方法、装置和系统
US11234261B2 (en) * 2017-09-22 2022-01-25 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data processing method and related device
US10721648B2 (en) * 2017-10-12 2020-07-21 Apple Inc. Device requested protocol data unit session modification in the 5G system
US11310707B2 (en) * 2018-04-13 2022-04-19 Qualcomm Incorporated Facilitating quality of service flow remapping utilizing a service data adaptation protocol layer
US20190349805A1 (en) * 2018-05-11 2019-11-14 Mediatek Inc. User equipments and methods for handling an update on quality of service (qos) flow to data radio bearer (drb) mapping
CN112910719B (zh) * 2018-06-21 2022-12-13 中兴通讯股份有限公司 一种数据流的配置方法、装置、系统、设备及计算机介质
CN110839267B (zh) 2018-08-17 2022-01-28 维沃移动通信有限公司 服务节点更新方法、终端设备和网络侧设备
CN111278065B (zh) * 2019-01-04 2021-04-02 维沃移动通信有限公司 数据传输方法和网络节点
CN111436078B (zh) * 2019-01-15 2022-04-29 华为技术有限公司 通信方法和网络设备
CN111447650B (zh) * 2019-01-17 2021-11-19 中国移动通信有限公司研究院 一种数据前转的方法、设备及存储介质
CN111628957B (zh) * 2019-02-28 2021-10-01 华为技术有限公司 一种数据传输方法以及网络设备
CN111654890B (zh) * 2019-03-04 2022-07-19 中国移动通信有限公司研究院 切换方法及装置、用户设备
CN111726890B (zh) * 2019-03-21 2022-06-07 中国移动通信有限公司研究院 Sdap实体的状态切换方法、数据处理方法及通信设备
CN114630360A (zh) * 2019-04-30 2022-06-14 华为技术有限公司 通信方法、装置及系统
EP3963769A1 (en) * 2019-05-02 2022-03-09 Nokia Technologies Oy Apparatus, method and computer program
CN112399476B (zh) * 2019-08-15 2023-04-18 华为技术有限公司 一种数据包传输方法、终端设备及网络设备
CN112584450A (zh) * 2019-09-30 2021-03-30 大唐移动通信设备有限公司 一种锚点转换处理方法、装置及设备
CN112866311A (zh) * 2019-11-26 2021-05-28 中兴通讯股份有限公司 Ftp上下行业务同传方法、系统、网络设备及存储介质
CN113498125B (zh) * 2020-03-20 2024-09-17 华为技术有限公司 一种通信方法、接入网设备、终端设备和核心网设备
CN113473525B (zh) * 2020-03-31 2023-11-10 华为技术有限公司 一种数据传输的方法及装置
WO2021208863A1 (zh) * 2020-04-16 2021-10-21 华为技术有限公司 数据传输方法及通信装置
WO2022016429A1 (zh) * 2020-07-22 2022-01-27 Oppo广东移动通信有限公司 切换方法、装置、设备及存储介质
WO2022082680A1 (zh) * 2020-10-22 2022-04-28 华为技术有限公司 一种通信方法及装置
CN114697989A (zh) * 2020-12-31 2022-07-01 大唐移动通信设备有限公司 一种通信传输的方法、设备及系统
CN115150910B (zh) * 2021-03-31 2024-06-25 华为技术有限公司 通信方法及通信装置
CN115190547A (zh) * 2021-04-01 2022-10-14 展讯通信（上海）有限公司 一种通信方法及装置
US20240187340A1 (en) * 2021-05-28 2024-06-06 Intel Corporation Enhanced service classification for service function chaining in next generation cellular networks
CN115843064A (zh) * 2021-09-18 2023-03-24 展讯通信（上海）有限公司 一种数据传输方法、通信装置、芯片及其模组设备
US11997155B2 (en) * 2022-01-31 2024-05-28 Discover Financial Services Trace context over file transfer communications

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090129342A1 (en) * 2007-11-16 2009-05-21 Nokia Siemens Networks Oy Mapping quality of service for intersystem handover
CN103945470A (zh) * 2013-01-18 2014-07-23 华为技术有限公司 切换方法、源通信节点和目标通信节点

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8830950B2 (en) * 2007-06-18 2014-09-09 Qualcomm Incorporated Method and apparatus for PDCP reordering at handoff
US8396037B2 (en) * 2008-06-23 2013-03-12 Htc Corporation Method for synchronizing PDCP operations after RRC connection re-establishment in a wireless communication system and related apparatus thereof
CN102238757B (zh) * 2010-04-30 2014-07-23 电信科学技术研究院 一种通过专用数据无线承载进行前转数据传输的方法和设备
JP5175973B2 (ja) * 2011-04-28 2013-04-03 株式会社エヌ・ティ・ティ・ドコモ 移動通信システム及び無線基地局
CN102291763B (zh) * 2011-07-22 2014-06-25 电信科学技术研究院 确定映射关系和上报QoS测量信息的方法、系统及设备
CN102368875B (zh) * 2011-10-18 2017-03-01 电信科学技术研究院 一种建立连接的方法、系统和设备
US8711699B2 (en) * 2011-10-31 2014-04-29 Amazon Technologies, Inc. Prioritizing application data for transmission in a wireless user device
CN102612095B (zh) * 2012-03-05 2014-08-20 电信科学技术研究院 一种ip数据包的传输方法和设备
EP2822235B1 (en) * 2012-03-28 2017-09-06 Huawei Technologies Co., Ltd. Method and device for establishing direct tunnel
US9225449B2 (en) * 2012-05-11 2015-12-29 Intel Corporation Performing a handover in a heterogeneous wireless network
CN109982378A (zh) * 2012-05-21 2019-07-05 三星电子株式会社 用于在移动通信系统中传送和接收数据的方法和设备
CN107018532B (zh) * 2012-05-30 2023-06-02 华为技术有限公司 多流传输的调度方法和设备
CN102843783B (zh) * 2012-07-19 2019-02-05 中兴通讯股份有限公司 承载建立方法和系统
CN104854938B (zh) * 2013-11-15 2021-05-14 荣耀终端有限公司 一种建立无线承载的方法及基站
US9497785B2 (en) * 2014-06-02 2016-11-15 Intel Corporation Techniques for exchanging beamforming information for a dual connection to user equipment
CN105228263B (zh) * 2014-06-30 2020-05-05 中兴通讯股份有限公司 Drb转换方法及装置
CN104363598B (zh) * 2014-11-25 2018-03-23 电信科学技术研究院 一种drb映射方法及装置
WO2016171864A1 (en) * 2015-04-22 2016-10-27 Gieseke & Devrient America, Inc. Device, computer-readable medium, and method for modifying services using advanced data collection capabilities
US10375751B2 (en) * 2015-08-19 2019-08-06 Samsung Electronics Co., Ltd Method and wireless communication system for handling offloading of DRBs to WLAN carrier
CN114885375B (zh) * 2016-08-09 2024-08-09 三星电子株式会社 无线通信系统中管理用户平面操作的方法和装置
EP3516922B1 (en) * 2016-09-30 2021-07-14 Samsung Electronics Co., Ltd. Method and apparatus for establishing dual-connectivity to transmit data in new radio communication architecture
WO2018062949A1 (en) * 2016-09-30 2018-04-05 Samsung Electronics Co., Ltd. Method and apparatus for establishing dual-connectivity to transmit data in new radio communication architecture
GB201621072D0 (en) * 2016-12-12 2017-01-25 Samsung Electronics Co Ltd NR QOS handling

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090129342A1 (en) * 2007-11-16 2009-05-21 Nokia Siemens Networks Oy Mapping quality of service for intersystem handover
CN103945470A (zh) * 2013-01-18 2014-07-23 华为技术有限公司 切换方法、源通信节点和目标通信节点

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ITRI: "Discussion on QoS flow ID", 3GPP TSG-RAN WG2 NR AD HOC, R2-1700255, 19 January 2017 (2017-01-19), XP051210837 *
NOKIA: "QoS flow relocation", 3GPP TSG-RAN WG2 MEETING #97, R2-1700814, 17 February 2017 (2017-02-17), XP051211599 *
See also references of EP3606149A4
ZTE: "Further discussion on the new UP protocol layer for QoS", 3GPP TSG-RAN WG2 MEETING #97 R2-1701119, 17 February 2017 (2017-02-17), XP051211831 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111225423A (zh) * 2018-11-27 2020-06-02 中国移动通信有限公司研究院 一种数据前转的方法和设备
CN111225423B (zh) * 2018-11-27 2022-04-01 中国移动通信有限公司研究院 一种数据前转的方法和设备
CN111586769A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 无线通信系统中的切换方法、装置及系统
CN111586769B (zh) * 2019-02-15 2021-10-15 华为技术有限公司 无线通信系统中的切换方法、装置及系统
US12089092B2 (en) 2019-02-15 2024-09-10 Huawei Technologies Co., Ltd. Handover method, apparatus, and system in wireless communication system

Also Published As

Publication number Publication date
JP2020511898A (ja) 2020-04-16
CN108924876B (zh) 2024-05-10
CN108966282A (zh) 2018-12-07
US11540349B2 (en) 2022-12-27
EP3606149A1 (en) 2020-02-05
RU2019133658A (ru) 2021-04-26
EP3606149B1 (en) 2021-06-09
EP3606149A4 (en) 2020-04-01
CN108966282B (zh) 2019-11-19
JP6882510B2 (ja) 2021-06-02
CN110463256B (zh) 2022-05-31
CN108924876A (zh) 2018-11-30
CN110463256A (zh) 2019-11-15
US10785825B2 (en) 2020-09-22
EP3941110A1 (en) 2022-01-19
US20210045188A1 (en) 2021-02-11
US20200022213A1 (en) 2020-01-16
BR112019019834A2 (pt) 2020-04-22
RU2019133658A3 (zh) 2021-04-26
RU2762681C2 (ru) 2021-12-22

Similar Documents

Publication Publication Date Title
WO2018171791A1 (zh) 数据传输方法、接入网设备、终端及通信系统
US11546811B2 (en) Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
US11696202B2 (en) Communication method, base station, terminal device, and system
WO2018228126A1 (zh) 一种基于dc的切换方法及设备
KR102329925B1 (ko) 4g/5g 동시 등록된 이동 통신 단말을 위한 네트워크 이동시 데이터 동기화 제공 방안
US12101659B2 (en) Radio bearer switching in radio access
US20200178138A1 (en) Communication method, base station, terminal device, and system
WO2020164615A1 (zh) 一种通信方法及相关设备
WO2018228378A1 (zh) 一种通信方法及接入网设备
WO2021097858A1 (zh) 一种通信方法及装置
WO2018059269A1 (zh) 消息的识别方法和装置
WO2021026706A1 (zh) 一种f1接口管理方法及装置
CN104685959B (zh) 具有统一接口的无源无线电链路控制实体
WO2021062803A1 (zh) 一种数据包传输方法及装置
WO2018228311A1 (zh) 数据分流方法和装置
WO2020001256A1 (zh) 一种数据传输方法及装置
WO2020199892A1 (zh) 无线通信系统中的切换方法、装置及系统
WO2021228066A1 (zh) 一种通信方法、装置及存储介质
WO2020088177A1 (zh) 一种通信方法、移动性管理实体、用户设备及服务网关
WO2018228545A1 (zh) 信息处理方法以及相关装置
WO2023246746A1 (zh) 一种通信方法及相关设备
WO2023131094A1 (zh) 通信方法及通信装置
WO2023131091A1 (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: 18770178

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019552519

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019019834

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2018770178

Country of ref document: EP

Effective date: 20191023

ENP Entry into the national phase

Ref document number: 112019019834

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190923