WO2019029703A1 - 数据传输方法和数据传输装置 - Google Patents

数据传输方法和数据传输装置 Download PDF

Info

Publication number
WO2019029703A1
WO2019029703A1 PCT/CN2018/099967 CN2018099967W WO2019029703A1 WO 2019029703 A1 WO2019029703 A1 WO 2019029703A1 CN 2018099967 W CN2018099967 W CN 2018099967W WO 2019029703 A1 WO2019029703 A1 WO 2019029703A1
Authority
WO
WIPO (PCT)
Prior art keywords
qos flow
data packet
base station
access network
data
Prior art date
Application number
PCT/CN2018/099967
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 KR1020207006996A priority Critical patent/KR102345399B1/ko
Priority to ES18843032T priority patent/ES2911651T3/es
Priority to CA3072717A priority patent/CA3072717C/en
Priority to JP2020507598A priority patent/JP6892554B2/ja
Priority to BR112020002788-0A priority patent/BR112020002788A2/pt
Priority to EP22157982.4A priority patent/EP4096299A1/en
Priority to EP18843032.6A priority patent/EP3598838B1/en
Publication of WO2019029703A1 publication Critical patent/WO2019029703A1/zh
Priority to US16/563,302 priority patent/US11109263B2/en
Priority to US17/459,667 priority patent/US11917450B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • the present application relates to the field of communications and, more particularly, to one. Data transmission method and data transmission device.
  • LTE Long Term Evolution
  • the access network element that sends and receives data changes, and the access network element notifies the core network element to change the user plane.
  • Data tunneling to ensure business continuity.
  • the user plane data tunnel of the core network sends an end identifier on the old data tunnel to notify the end of sending the downlink data packet, wherein the user plane data tunnel is established according to the EPS Bearer.
  • a QoS architecture based on a Quality of Service Flow (QoS flow) service flow is introduced, and a Packet Data Unit (Packet Data Unit) is used between the core network element and the access network element.
  • QoS flow Quality of Service Flow
  • Packet Data Unit Packet Data Unit
  • a session establishes a packet tunnel, and one PDU session may contain one or more QoS flows. Therefore, when the terminal moves, it may be that the data tunnel of one or more QoS flows needs to be changed, or the data tunnel of the PDU session needs to be changed. How to set the end identifier of the core network element is a problem that needs to be solved.
  • the application provides a transmission method and a data transmission device, which can avoid the disorder of data packets.
  • a first aspect provides a transmission method, including: a source access network device sends the source access to a target access network device by using a data tunnel between the source access network device and a second PDCP entity of the target access network device a first partial data packet in a first packet data convergence protocol PDCP entity in the network device, the first partial data packet being a data packet of a first quality of service QoS flow in a first protocol data unit PDU session, the first PDU
  • the session includes at least one QoS flow, the at least one QoS flow is in one-to-one correspondence with at least one PDCP entity, the at least one QoS flow includes the first QoS flow, and the at least one PDCP entity includes the first PDCP entity,
  • the first PDCP entity corresponds to the first QoS flow, the first QoS flow is any one of the at least one QoS flow;
  • the source access network device sends a first to the target access network device An indication information, where the first indication information is used to indicate that
  • the first indication information includes a maximum PDCP sequence number in a PDCP sequence number carried by all data packets in the first partial data packet;
  • the first indication information includes a next PDCP sequence number to be allocated; or the first indication information is an end identifier packet generated by the first PDCP entity.
  • the method further includes: determining, by the source access network device, the The first service data adaptation protocol SDAP entity in the source access network device ends transmitting the data packet of the first QoS flow to the first PDCP entity, where the first SDAP entity is to the first PDCP entity
  • the data packet of the first QoS flow that is sent is the first partial data packet, and the first SDAP entity corresponds to the first PDU session.
  • the second indication information is sent by the first SDAP entity according to an end identifier packet received from a core network user plane device.
  • a transmission method comprising: a target access network device receiving a first PDCP by using a data tunnel between a second packet data convergence protocol PDCP entity and a first PDCP entity of a source access network device a first partial data packet sent by the entity, the first partial data packet is a data packet of a first quality of service QoS flow in a first protocol data unit PDU session, and the first PDU session includes at least one QoS flow, the at least one The QoS flow is in one-to-one correspondence with at least one PDCP entity, the at least one QoS flow includes the first QoS flow, and the at least one PDCP entity includes the first PDCP entity, the first PDCP entity and the first Corresponding to the QoS flow, the second PDCP entity corresponding to the first QoS flow, the first QoS flow being any one of the at least one QoS flow; the target access network device receiving the source access The first indication information sent by the network device, where the first
  • the method further includes: the target access network device, after determining, according to the first indication information, that all the data packets in the first partial data packet have been sent to the terminal, sending the information to the terminal A data packet received by a second SDAP entity of the target access network device.
  • the first indication information includes a maximum PDCP sequence number in a PDCP sequence number carried by all the data packets in the first partial data packet; or the first indication information includes a next PDCP to be allocated. a sequence number; or the first indication information is an end identifier packet generated by the first PDCP entity.
  • a third aspect provides a transmission method, including: if it is determined that a terminal does not send a data packet of at least one quality of service QoS flow in a first protocol data unit PDU session to a source access network device, the source access network device Generating trigger information; the source access network device sends the trigger information to the target access network device, where the trigger information is used to indicate that the target access network device sends the core network user plane device to the core network user plane device to be sent by the terminal to a data packet of the at least one QoS flow of the target access network device, the trigger information includes an identifier of the at least one QoS flow and an identifier of the first PDU session, or the trigger information includes the An identifier of the at least one QoS flow and an identifier of the first DRB, the first DRB corresponding to the at least one QoS flow.
  • a fourth aspect provides a transmission method, including: receiving, by a target access network device, trigger information sent by a source access network device, where the trigger information is used to indicate that the target access network device sends a message to a core network user plane device. Transmitting, by the terminal, a data packet of at least one quality of service QoS flow in a first protocol data unit PDU session of the target access network device, where the trigger information includes an identifier of the at least one QoS flow and the first The identifier of the PDU session, or the trigger information includes an identifier of the at least one QoS flow and an identifier of the first data radio bearer DRB, where the first DRB corresponds to the at least one QoS flow; the target access network And transmitting, by the device, the data packet of the at least one QoS flow sent by the terminal to the target access network device to the core network user plane device according to the trigger information.
  • the trigger information is an end identifier packet, or the trigger information is a message between access network devices.
  • a fifth aspect provides a transmission method, including: if a source access network device determines that a terminal receives a data packet of at least one quality of service QoS flow in a first protocol data unit PDU session sent by the source access network device, The source access network device generates trigger information; the source access network device sends the trigger information to the target access network device, where the trigger information is used to indicate that the target access network device starts to send to the terminal.
  • the trigger information includes an identifier of the at least one QoS flow and an identifier of a first data radio bearer DRB, where the first DRB corresponds to the at least one QoS flow.
  • the sixth aspect provides a transmission method, including: the target access network device receives the trigger information sent by the source access network device, where the trigger information is used to indicate that the target access network device starts to send the target connection to the terminal. a data packet of at least one quality of service QoS flow in a first protocol data unit PDU session received by the network access device from the core network user plane device, the trigger information including an identifier of the at least one QoS flow and the first PDU session
  • the identifier, or the trigger information includes an identifier of the at least one QoS flow and an identifier of the first data radio bearer DRB, where the first DRB corresponds to the at least one QoS flow;
  • the target access network device is configured according to And the triggering information, sending, to the terminal, a data packet of the at least one QoS flow received from the core network user plane device.
  • the trigger information is an end identifier packet, or the trigger information is a control plane message between access network devices.
  • a data transmission apparatus comprising means for performing the steps of the transmission method in any of the first to sixth aspects and the implementations thereof.
  • the data transmission device is a communication chip
  • the communication chip may include an input circuit or interface for transmitting information or data, and an output circuit or interface for receiving information or data.
  • the data transmission device is a communication device
  • the communication chip may include a transmitter for transmitting information or data, and a receiver for receiving information or data.
  • a communication device comprising: a processor, a memory for storing a computer program, the processor for calling and running the computer program from a memory, such that the communication device performs first to sixth A transmission method in any of the aspects and possible implementations thereof.
  • the processor is one or more, and the memory is one or more.
  • the memory may be integrated with the processor or the memory may be separate from the processor.
  • the communication device further includes a transmitter (transmitter) and a receiver (receiver).
  • a computer program product comprising: a computer program (which may also be referred to as a code, or an instruction) that, when executed, causes the computer to perform the first aspect to the first A method in any of the six possible implementations.
  • a computer readable medium storing a computer program (which may also be referred to as a code, or an instruction), when executed on a computer, causes the computer to perform the first aspect to the first A method in any of the possible implementations of the two aspects.
  • a computer program which may also be referred to as a code, or an instruction
  • a ninth aspect provides a chip system including a memory and a processor for storing a computer program for calling and running the computer program from the memory, such that the communication device mounted with the chip system performs the above The method of any of the first aspect to the sixth aspect of the possible implementation.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 13 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 14 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 15 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 16 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 17 is a schematic diagram of a data transmission apparatus according to an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of a terminal device provided by the present application.
  • FIG. 19 is a schematic diagram of a data transmission apparatus according to an embodiment of the present application.
  • FIG. 20 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
  • QoS flow quality of service flow
  • FIG. 1 shows the QoS flow architecture at 5G.
  • the base station establishes one or more DRBs for each PDU session of the terminal.
  • the base station maps packets belonging to different PDU sessions to different DRBs.
  • QoS flow is the minimum granularity of QoS differentiation in a PDU session.
  • a PDU session is a link between a terminal and an external data network to provide a packet data unit link service.
  • Each PDU session has a unique identifier, and the unique identifier of the PDU session may be a PDU session identity.
  • QoS flow is a set of data packets in which packets of the same QoS flow have the same QoS characteristics and the same packet forwarding process is obtained in the 3GPP network.
  • the packet processing mechanism on the air interface is defined based on DRB under 5G.
  • a packet served by a DRB has the same packet processing mechanism on the air interface.
  • the base station can establish multiple DRBs to meet QoS flows with different packet processing requirements.
  • the base station maps the downlink packets belonging to the QoS flow to the DRB based on the QFI identifier on the NG-U (ie, the N3 interface) and the corresponding QoS profile.
  • the UE maps the uplink data packets belonging to the QoS flow to the DRB according to the QoS flow to DRB mapping or reflection mapping configured by the base station.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • a terminal in this embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal device, a wireless communication device, a user agent, or User device.
  • the terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), with wireless communication.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the access network device or the base station in the embodiment of the present application may be a device for communicating with the terminal device, and the network device may be a Global System of Mobile communication (GSM) system or a code division multiple access (Code Division Multiple) Base Transceiver Station (BTS) in Access, CDMA), which may also be a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolution in an LTE system.
  • GSM Global System of Mobile communication
  • BTS code division multiple access
  • CDMA Code Division Multiple Access
  • NodeB, NB base station
  • WCDMA Wideband Code Division Multiple Access
  • the base station may also be a wireless controller in a Cloud Radio Access Network (CRAN) scenario, or the network device may be a relay station, an access point, an in-vehicle device, or
  • CRAN Cloud Radio Access Network
  • the embodiment of the present application is not limited to the wearable device and the network device in the future 5G network or the network device in the future evolved PLMN network.
  • the core network device in the embodiment of the present application is composed of a core network control plane device and a core network user plane device.
  • the Next Generation Radio Access Network consists of a gNB and an evolved eNB, wherein the gNB provides an NR control plane and a user plane protocol stack terminated at the terminal.
  • the evolved eNB refers to an evolved LTE base station that is linked to the 5G core network.
  • a gNB and an evolved eNB may be collectively referred to as a base station.
  • the gNB provides at least one of the following functions: access control, link mobility management, radio bearer control, measurement configuration and provisioning, dynamic resource allocation, and the like.
  • Access and Mobility Management Function provides non-access stratum (NAS) security management, access stratum (AS) security control, mobility management, and terminal access authentication. At least one of functions such as registration area management, slice support, and session management function (SMT) selection.
  • NAS non-access stratum
  • AS access stratum
  • SMT session management function
  • the User Plane Function provides at least one of the functions of switching anchor points, routing and forwarding of data packets, and QoS management.
  • SMF provides at least one of functions such as session management, terminal address assignment and management, UPF selection and control.
  • next generation core network control plane devices include but are not limited to AMF and SMF.
  • Next-generation core network user plane devices include, but are not limited to, UPF.
  • the interface between the AMF and the NG-RAN is defined as an N2 interface, and the interface between the UPF and the NG-RAN is defined as an N3 interface.
  • the interface between gNBs is defined as the Xn interface.
  • the start transmission information and the trigger information in the embodiment of the present application may be replaced with each other.
  • the SN may be a secondary base station, and the MN may be a primary base station.
  • the access network device can be replaced with the base station.
  • FIG. 2 is a schematic flow chart of a transmission method according to the present application.
  • the method illustrated in FIG. 2 can be applied to the process of transferring at least one QoS flow (referred to as QoS flow #1) in the first PDU session of the terminal to the target base station.
  • QoS flow #1 in the first PDU session of the terminal is transferred to the target base station (primary base station or secondary base station), and the remaining part of the QoS flow in the first PDU session is still at the source base station (secondary base station) Or secondary base station).
  • the transmission method of the embodiment of the present application is described in detail below with reference to FIG. 2 .
  • the first base station sends a first request message to the core network device.
  • the first request message includes an identifier of the first PDU session and an identifier of the QoS flow #1, and the first request message is used to request to change the user plane routing of the QoS flow #1 to the second base station.
  • the first base station may be the primary base station in a dual link scenario.
  • the secondary base station is the second base station, that is, the first base station and the second base station are different base stations.
  • the primary base station is the target base station
  • the primary base station is the second base station, that is, the first base station and the second base station are the same base station.
  • the core network device is a device that is compatible with the core network user plane device function and the core network control plane device function.
  • the first request message may be a path switch request message.
  • the existing technology can be better compatible.
  • the core network device sends an end identifier packet according to the first request message.
  • the end identifier packet is sent to the second base station.
  • the end identification packet includes an identifier of QoS flow #1 indicating that the core network device ends transmitting a data packet of QoS flow #1 in a source data tunnel of the first PDU session. That is, the end identification packet indicates that the core network user plane no longer sends the QoS flow #1 packet in the source data tunnel.
  • the end identification packet may be an empty data packet.
  • the encapsulation header of the null data packet may carry an end identifier, for example, carrying an end identifier in a header of the General Packet Radio Service Tunnel Protocol User plane (GTPU) or an extension header.
  • GTPU General Packet Radio Service Tunnel Protocol User plane
  • the identifier of the QoS flow #1 may be carried in the encapsulation header of the null data packet.
  • the core network device may send multiple end identification packets to improve the success rate of the source base station correctly receiving the end identification packet.
  • the step S220 is specifically: the core network device sends the end identification packet to the first base station according to the first request message. If the first base station is the target base station of the QoS flow #1, and the first base station and the second base station are the same base station, the step S220 is specifically: the core network device sends the end identifier packet to the second base station or the first base station according to the first request message. .
  • the core network device instructs the access network device to end the QoS flow of the core network user plane device in the source data tunnel by sending the end identification packet. transmission.
  • the switching of the downlink transmission of the QoS flow level or granularity can be realized, thereby further enhancing the flexibility of the system.
  • FIG. 3 is a schematic flow chart of another transmission method according to the present application.
  • the method illustrated in FIG. 3 can be applied to at least one QoS flow in the first PDU session of the terminal (denoted as QoS flow #1) or in the process of transferring all QoS flows to the target base station.
  • QoS flow #1 the QoS flow in the first PDU session of the terminal
  • all QoS flows in the first PDU session of the terminal are transferred to the target base station, or all QoS flows in the first PDU session are to be transferred to the target base station but only QoS flow #1 is successfully received at the target base station.
  • the QoS flow #1 in the first PDU session of the terminal is transferred to the target base station (primary base station or secondary base station), and the remaining part of the QoS flow in the first PDU session is still at the source base station (secondary Base station or secondary base station).
  • the access network device sends a request message #1 to the core network control plane device.
  • Request message #1 includes the identity of the first PDU session.
  • the message of the route change request may further include an identifier of QoS flow #1.
  • the access network device may be a source base station or a target base station.
  • the request message #1 further includes an identifier of the QoS flow #1 for requesting to change the user plane of the QoS flow #1 of the first PDU session. Routed to the target base station.
  • the source base station herein is a primary base station or a secondary base station in a dual link scenario
  • the target base station herein is a secondary base station or a primary base station in a dual link scenario.
  • the route change request message is used to request to switch the data tunnel of the first PDU session to the target base station.
  • the request message #1 may further include an independent indication information (referred to as indication information #1A), and the indication information #1A is used to indicate whether the data tunnel of the first PDU session is switched, or the route of QoS flow# changes happened.
  • indication information #1A an independent indication information
  • the indication information #1A is used to indicate whether the data tunnel of the first PDU session is switched, or the route of QoS flow# changes happened.
  • the switching of the data tunnel of the first PDU session refers to the completion of the data tunnel in the data tunnel corresponding to the first PDU session between the core network user plane device and the source base station.
  • the core network user plane device and the terminal use the data tunnel corresponding to the first PDU session between the core network user plane device and the target base station to transmit data.
  • the change of the user plane route of the QoS flow #1 refers to the QoS flow #1 of the route change transmitted on the data tunnel corresponding to the QoS flow #1 between the core network user plane device and the target base station, and the route is unchanged.
  • the QoS flow in a PDU session continues to be transmitted on the data tunnel corresponding to the first PDU session between the core network user plane device and the source base station.
  • the request message #1 may be a path switch request message.
  • the existing technology can be better compatible.
  • the core network control plane device sends a request message #2 to the core network user plane device.
  • the request message #2 may be the same as or different from the request message #1.
  • the request message #2 is generated by the core network control plane device according to the request message #1, and the request message #2 includes the identifier of the first PDU session.
  • the request message #2 may also include an identifier of the QoS flow #1.
  • the core network user plane device changes the route of the data packet, and sends an end identifier packet to the source base station.
  • the end identifier packet includes an ID of QoS flow #1.
  • the end identifier packet is used to indicate to the source base station that the core network user plane device no longer sends the data packet of the QoS flow #1 to the source base station.
  • the core network user plane device sends the end identification packet to the source base station.
  • the message 1 of the route change request further includes the ID of the QoS flow #1 or the ID of the QoS flow #1 and the indication information #1, and the core network user plane device sends the end identification packet to the source base station.
  • the core network user plane device may send multiple end identifier packets to improve the success rate of the source base station correctly receiving the end identifier packet.
  • the end identification packet may be an empty data packet.
  • the encapsulation header of the null data packet may carry an end identifier, for example, carrying an end identifier in the GTPU header or the extension header.
  • the identifier of the QoS flow #1 may be carried in the encapsulation header of the null data packet.
  • the format of the end identification packet in step S303 may include multiple QoS flow fields, and the multiple QoS flow fields are in one-to-one correspondence with multiple QoS.
  • the end identifier packet sent in step S303 may also be a dedicated end identifier packet. In this case, the end identifier packet may carry the ID of QoS flow #1 or may not carry the ID of QoS flow #1.
  • the core network user plane device may send an end identifier packet #1 to the source base station, where the end identifier packet #1 is used to indicate The core network user plane device no longer sends the data packet of any one of the QoS flows in the first PDU session to the source base station.
  • the end identification packet #1 may further carry an indication information (referred to as indication information #1B), and the indication information #1B is used to indicate that the end identification packet #1 is for all QoS flows in the first PDU session.
  • the core network user plane device may send the end identification packet #2 to the source base station, where the end identifier packet #2 is used.
  • the end identification packet #2 may further carry an indication information (referred to as indication information #1C), and the indication information #1C is used to indicate that the end identification packet #2 is for the QoS flow.
  • end identification packet #1 and the end identification packet #2 are data packets of different structures.
  • the access network device may notify the core network control plane device that the data tunnel of the QoS session to which the QoS flow of the changed route is changed is at the target base station. The routing address and the ID of the target base station.
  • the access network device may only notify the target network base station identifier or the target routing address of the core network control plane device.
  • the routing address includes a transport layer address and a GPRS Tunneling Protocol Tunnel Endpoint Identifier (GTP TE id).
  • GTP TE id GPRS Tunneling Protocol Tunnel Endpoint Identifier
  • the end identifier packet may further carry an indication information for indicating that the end identifier packet is for QoS flow, and may also indicate that it is for a QoS flow group, for example, when the base station requests a route change of a group of QoS flows,
  • the core network user plane device may set an end identification packet to indicate the end of the data packet of the QoS flow group sent in the original data tunnel of the PDU session.
  • the core network user plane device instructs the source base station to end the downlink of the user equipment of the core network to the source base station according to the request message #1 sent by the access network device through the core network control plane device.
  • Downlink transmission of the at least one QoS flow in transmission Thereby, the switching of the downlink transmission of the QoS flow level or granularity can be realized, thereby further enhancing the flexibility of the system.
  • the core network user plane device in FIG. 4 may be an UPF, and the core network control plane device may be an SMF and/or an AMF, but the application embodiment does not limit this.
  • the method illustrated in FIG. 4 may be applied to at least one QoS flow in the first PDU session of the terminal (denoted as QoS flow #1) or in the process of transferring all QoS flows to the target base station.
  • QoS flow #1 the QoS flow #1 in the first PDU session of the terminal is transferred to the target base station (primary base station or secondary base station), and the remaining part of the QoS flow in the first PDU session is still at the source base station. (primary base station or secondary base station).
  • the access network device sends a first request message to the core network control plane device.
  • the first request message is used by the core network control device to request the core network user plane device to change the user plane route to the target base station.
  • the access network device may be a source base station or a target base station.
  • the first request message is sent by the source base station, the first request message is used to request to change the user of at least one QoS flow (referred to as QoS flow #1) in a certain PDU session (referred to as the first PDU session)
  • QoS flow #1 QoS flow
  • the target base station herein is a secondary base station or a primary base station in a multiple connectivity scenario.
  • the route change request message is used to request to switch the data tunnel of the first PDU session to the target base station.
  • the core network control plane device sends a second request message to the core network user plane device according to the first request message, and notifies the core network user plane device to change the route by using the second request message.
  • the core network user plane device sends an end identifier packet to the source base station.
  • the source base station may determine that the end identifier packet indicates that the core network user plane device ends the source data in the first PDU session. The transmission of the QoS flow #1 packet in the tunnel.
  • the method may further include:
  • the source base station may determine that the end identification packet indicates that the core network user plane device ends all in the source data tunnel of the first PDU session. The transmission of data packets for QoS flows.
  • the source base station may determine, according to the type of the message sent by the source network, whether the end packet sent by the core network user plane device ends with QoS flow #1 or the entire first PDU session. If the first request message is a message of the route change request, the end identification packet instructs the core network user plane device to end the transmission of the data packet of the QoS flow #1 in the source data tunnel of the first PDU session. If the first request message is a path change request message, the end identification packet instructs the core network user plane device to end the transmission of data packets of all QoS flows in the source data tunnel of the first PDU session.
  • the access network device is the primary base station
  • the primary base station is the target base station
  • the secondary base station is the source base station
  • the source base station determines, according to the message interaction with the target base station, the target base station sends the message to the core network control plane device.
  • the type of the first request message is the primary base station
  • the target base station sends the message to the core network control plane device.
  • the target base station sends the first request message to the core network control plane device as a path change request message.
  • the target base station sends a message that the type of the first request message is a route change request to the core network control plane device.
  • the source base station may determine, according to different scenarios, whether the end identifier packet corresponds to a QoS flow or a PDU session. For example, in the handover scenario, the determination end identification packet indicates that the core network user plane device ends the transmission of the data packets of all QoS flows in the source data tunnel of the first PDU session. In the dual link scenario, the end identification packet instructs the core network user plane device to end the transmission of the QoS flow #1 packet in the source data tunnel of the first PDU session.
  • the core network user plane device may send multiple end identifier packets to improve the success rate of the source base station correctly receiving the end identifier packet.
  • the end identification packet may be an empty data packet.
  • the encapsulation header of the null data packet may carry an end identifier, for example, carrying an end identifier in the GTPU header or the extension header.
  • the core network user plane The device may indicate to the source base station, by ending the identification packet, that the core network user plane device ends the transmission of the data packet of the entire PDU session in the source data tunnel.
  • the core network user plane device may also indicate to the source base station by using the end identifier packet of the same format.
  • the core network user plane device terminates the transmission of data packets for the entire PDU session in the source data tunnel. Since the core network user plane device adopts a unified format end identification packet, the complexity of processing the end identifier packet of the core network user plane device and the source base station can be reduced.
  • FIG. 5 is a schematic flow chart of another transmission method according to the present application.
  • the core network user plane device in FIG. 5 may be an UPF, and the core network control plane device may be an SMF and/or an AMF.
  • the source base station receives an end identifier packet sent by the terminal or the core network user plane device.
  • the end identification packet includes an identifier of the first PDU session and an identifier of the at least one QoS flow (referred to as QoS flow #1);
  • the source base station releases or terminates the resource corresponding to the QoS flow #1 according to the end identifier packet.
  • the source base station releases the parameters of QoS flow #1 in the context of the terminal.
  • the terminal or core network user plane device can autonomously terminate the transmission of QoS flow #1. For example, when the terminal decides to terminate the uplink transmission of QoS flow #1, the terminal notifies the end of the uplink transmission of the source base station QoS flow #1 by transmitting the end identification packet. After the terminal sends the end identification packet, the data packet of QoS flow #1 will not be sent to the source base station. For example, when the core network user plane device decides to terminate the downlink transmission of QoS flow #1, the core network user plane device notifies the end of the downlink transmission of the source base station QoS flow #1 by sending the end identification packet. After the core network user plane device sends the end identification packet, the data packet of QoS flow #1 will not be sent to the source base station. After receiving the end identification packet, the source base station will not send the data packet of QoS flow #1 to the terminal.
  • the terminal or core network user plane device may send multiple end identification packets to improve the success rate of the source base station correctly receiving the end identification packet.
  • the end identification packet may be an empty data packet.
  • the encapsulation header of the null data packet may carry an end identifier, for example, carrying an end identifier in the GTPU header or the extension header.
  • the ID of the QoS flow #1 can be carried in the encapsulation header of the null data packet.
  • the terminal or the core network user plane device may terminate the transmission of the QoS flow #1 by transmitting an end identification packet including the QoS flow ID.
  • the source base station may release or terminate the resource allocated for QoS flow #1.
  • the source base station can release the QoS parameters of QoS flow #1 in the maintained terminal context.
  • the QoS parameters include, but are not limited to, metric parameters such as delay, packet loss rate, priority, and rate. Thereby, system resources can be saved.
  • FIGS. 6, 7, and 8 a detailed description will be given in connection with the transmission methods used in the inter-system handover process in conjunction with FIGS. 6, 7, and 8. Specifically, the transmission methods shown in FIGS. 6, 7, and 8 can be used in the backhaul of data packets or data.
  • the data backhaul or data packet backhaul refers to that the source base station transmits the data packet received from the core network user plane device or the terminal to the target base station, and the target base station sends the received data from the source base station to the terminal or the core network user plane device. Packet.
  • the first core network control plane device may be an AMF and/or an SMF
  • the second core network control plane device may be an MME
  • the first core network user plane device may be an UPF
  • the second core network user plane device may be an S -GW.
  • FIG. 6 is a schematic flow chart of a transmission method according to the present application.
  • the transmission method of the embodiment of the present application is described in detail with reference to FIG. 6 .
  • the source base station sends a first request message to the first core network control plane device.
  • the first request message includes a backhaul indication, which is used to instruct the first core network user plane device to send the backhaul data packet belonging to the first PDU session to the target base station.
  • the first request message may further include an ID of at least one QoS flow (referred to as QoS flow #1).
  • QoS flow #1 an ID of at least one QoS flow
  • the source base station proposes to transmit the backhaul data packet through QoS flow #1.
  • the backhaul data packet may refer to any data packet received by the source base station from the first core network user plane device (for example, UPF), and all data packets that have not received the acknowledgement received by the terminal, or all A packet that has not been sent to the terminal.
  • UPF first core network user plane device
  • the first core network control plane device sends a first response message to the source base station according to the first request message.
  • the first response message includes an identifier of the at least one first EPS bearer corresponding to the first PDU session and the backhaul indication.
  • the source base station generates transparent container information of the source base station to the target base station according to the first response message.
  • the transparent container information may include wireless related information of the source base station, for example, an E-RAB ID list, E-RABUE history information corresponding to each E-RAB ID, a backhaul indication, and the like.
  • E-RAB and EPS Bearer are one-to-one correspondence. It should be understood that the backhaul indication here indicates that the E-RAB has data to be returned.
  • the source base station sends a handover request message to the core network control plane device, where the handover request message includes the transparent container information.
  • each node for example, the source base station, the target base station, and the like, may perform the handover process according to the prior art, and the embodiments of the present application are not described in detail herein.
  • the source base station can indicate which E-RABs of the target base station have downlink data and need to perform backhaul.
  • FIG. 7 is a schematic flow chart of a transmission method according to the present application. It should be understood that FIG. 7 is a schematic flowchart of a transmission method of an embodiment of the present application, showing detailed communication steps or operations of the method, but the steps or operations are merely examples, and other embodiments of the present application may perform other The operation or the deformation of the various operations in FIG. Moreover, the various steps in FIG. 7 may be performed in a different order than that presented in FIG. 7, and it is possible that not all operations in FIG. 7 are to be performed.
  • the source base station sends a backhaul data packet and a first end identifier packet to the first core network user plane device.
  • the first end identifier packet is received by the source base station from the first core user plane device, and the first end identifier packet may be an empty data packet.
  • the encapsulation header of the null data packet carries an end identifier, for example, carrying an end identifier in the GTPU header or the extension header.
  • the source base station can establish a data tunnel for data backhaul with the first core network user plane device.
  • the data backhaul tunnel is established according to the PDU session, that is, each PDU session establishes a data back to the tunnel for transmitting the backhaul data packet.
  • the data tunnel established according to the PDU session corresponding to the first PDU session may be recorded as: data tunnel #1, then the source base station may send the backhaul data packet to the first core network user plane device through the data tunnel #1 and the first end Identification package.
  • the first end identifier packet may be set by the PDU session, indicating the end of the packet in the session, or set by the QoS flow, indicating the end of the packet in the QoS flow.
  • the first core network user plane device generates a second end identifier packet according to the correspondence between the first session and the first EPS bearer and the first end identifier packet.
  • the second end identifier packet carries the identifier of the first EPS bearer.
  • the first core network user plane device sends a backhaul data packet and a second end identifier packet to the second core network user plane device.
  • a data tunnel for data backhaul is established between the first core network user plane device and the second core network user plane device, and between the second core network user plane device and the target base station according to the EPS bearer.
  • the data tunnel established according to the EPS bearer corresponding to the first PDU session may be recorded as: data tunnel #2, then the first core network user plane device may send a backhaul to the second core network user plane device through the data tunnel #2.
  • the packet and the second end identification packet may be recorded as: data tunnel #2, then the first core network user plane device may send a backhaul to the second core network user plane device through the data tunnel #2.
  • the second core network user plane device sends the backhaul data packet and the second end identifier packet to the target base station.
  • the target base station sends, according to the second end identifier, a data packet received from the second core network user plane device to the terminal after transmitting the return data packet to the terminal.
  • the target base station first sends the received backhaul data packet, and determines, according to the second end identifier packet, that the backhaul data packet on the EPS bearer is sent, and then sends the data packet received from the second core network user plane device (ie, New packet). Thereby, the in-order transmission of the EPS bearer data packets can be guaranteed.
  • the second core network user plane device ie, New packet
  • the target base station after the target base station receives and detects the second end identifier packet, the second end identifier packet may be discarded. Further, the target base station can release the resources of the data tunnel #2.
  • the first core network user plane device sets and sends a second end identifier packet corresponding to the EPS bearer, so that the target base station can first send the backhaul received from the source base station according to the end identifier packet.
  • the new data packet received from the user equipment of the second core network is sent, thereby ensuring the sequential transmission of the data packets carried by the EPS.
  • FIG. 8 is a schematic flow chart of a transmission method according to the present application. It should be understood that FIG. 8 is a schematic flowchart of a transmission method of an embodiment of the present application, showing detailed communication steps or operations of the method, but the steps or operations are merely examples, and other embodiments of the present application may perform other The operation or the deformation of the various operations in FIG. Moreover, the various steps in FIG. 8 may be performed in a different order than that presented in FIG. 8, and it is possible that not all operations in FIG. 8 are to be performed.
  • the source base station sends a backhaul data packet and a first end identifier packet to the first core network user plane device.
  • the first end identifier packet is received by the source base station from the first core user plane device, and the first end identifier packet may be an empty data packet.
  • the encapsulation header of the null data packet may carry an end identifier, for example, carrying an end identifier in the GTPU header or the extension header.
  • the source base station can establish a data tunnel for data backhaul with the first core network user plane device.
  • the data backhaul tunnel is established according to the PDU session, that is, each PDU session establishes a data back to the tunnel for transmitting the backhaul data packet.
  • the data tunnel established according to the PDU session corresponding to the first PDU session may be recorded as: data tunnel #1, then the source base station may send the backhaul data packet to the first core network user plane device through the data tunnel #1 and the first end Identification package.
  • the first core network user plane device sends a backhaul data packet and a new data packet to the second core network user plane device according to the first end identifier packet.
  • a data tunnel is established between the first core network user plane device and the second core network user plane device, and between the second core network user plane device and the target base station according to the EPS bearer, for transmitting from the first core network user.
  • the downlink data ie, the backhaul packet
  • the data tunnel established according to the EPS bearer can be recorded as: Data Tunnel #3.
  • the first core network user plane device determines, according to the first end identifier packet, that the first end identifier packet is discarded after the backhaul data packet is sent through the data tunnel #3. Then, send a new packet through data tunnel #3.
  • the encapsulation header of the backhaul data packet may carry the identifier of the QoS flow, and the first core network user plane device determines the data tunnel #3 according to the identifier of the QoS flow. For example, according to the correspondence between the QoS flow and the EPS Bearer, the data tunnel corresponding to the EPS Bearer is indexed.
  • the second core network user plane device sends the backhaul data packet and the new data packet to the target base station.
  • the target base station sends, to the terminal, a downlink data packet received from the second core network user plane device.
  • the downlink data packet includes a backhaul data packet and a new data packet.
  • the source base station sends the backhaul data packet to the first core network user plane device, and the first core network user plane device first sends the backhaul data packet received from the source base station, and then sends the new data packet.
  • the first core network user plane device and the second core network user plane device, the second core network user plane device and the target base station do not need to establish a downlink data return tunnel, which reduces overhead.
  • the target base station does not distinguish between the backhaul data packet and the new data packet.
  • the data packet that the source base station needs to send to the first PDU session of the target base station which is described below in connection with FIG. 9, 10 and 11, is the data packet that needs to be returned in the data packet of the first PDU session.
  • the data packet that needs to be returned in the data packet of the first PDU session may be any one of the following.
  • the first SDAP entity corresponds to the first PDU session.
  • the data packet that has not received the acknowledgement received by the terminal, the data packet that has not been sent to the terminal, and the data packet that has not been successfully sent by the PDCP entity are all cached in the PDCP entity, and therefore, the source base station needs to send the first PDU session to the target base station.
  • the data packet is the data packet buffered in the first SDAP entity and/or the data packet buffered in the PDCP entity.
  • the data packet that the source base station needs to send to the first PDU session of the target base station is a data packet buffered in the first SDAP entity and a data packet buffered in the PDCP entity. If there is no buffered data packet in the first SDAP entity, the data packet that the source base station needs to send to the first PDU session of the target base station is a data packet buffered in the PDCP entity.
  • FIG. 9 is a schematic flow chart of a transmission method according to the present application. It should be understood that FIG. 9 is a schematic flowchart of a transmission method of an embodiment of the present application, showing detailed communication steps or operations of the method, but the steps or operations are merely examples, and other embodiments of the present application may perform other The operation or the deformation of the various operations in FIG. Moreover, the various steps in FIG. 9 may be performed in a different order than that presented in FIG. 9, and it is possible that not all operations in FIG. 9 are to be performed.
  • the source base station sends a first part of the first PDCP entity to the target base station by using a data tunnel between the first packet data convergence protocol PDCP entity and the second PDCP entity of the target base station.
  • the first partial data packet is a data packet of a first QoS flow (referred to as QoS flow #1) in a first protocol data unit PDU session, the first PDU session includes at least one QoS flow, and the at least one QoS flow One-to-one correspondence with at least one PDCP entity, the at least one QoS flow including the first QoS flow, the at least one PDCP entity including the first PDCP entity, the first PDCP entity and the first QoS flow
  • the first QoS flow is any one of the at least one QoS flow.
  • the source base station sends first indication information to the target base station, where the first indication information is used to indicate end of the first partial data packet in the first PDCP entity.
  • the target base station sends, according to the first indication information, a data packet received from a SDAP entity of the target base station to the terminal after determining that all data packets in the first partial data packet have been sent to the terminal.
  • the first indication information includes a maximum PDCP sequence number in a PDCP sequence number carried by all the data packets in the first partial data packet;
  • the first indication information includes a next PDCP serial number to be allocated.
  • the first indication information is an end identifier packet generated by the first PDCP entity.
  • the method further includes:
  • the first PDCP entity receives the second indication information that is sent by the first SDAP entity of the source base station, where the second indication information is used to indicate that the first SDAP entity ends sending the first to the first PDCP entity.
  • a data packet of the QoS flow wherein the data packet of the first QoS flow sent by the first SDAP entity to the first PDCP entity is the first partial data packet, the first SDAP entity and the The first PDU session corresponds.
  • the second indication information is sent by the SDAP entity according to an end identifier packet received from a core network user plane device.
  • FIG. 10 is a schematic flow chart of a transmission method according to the present application. It should be understood that FIG. 10 is a schematic flowchart of a transmission method of an embodiment of the present application, showing detailed communication steps or operations of the method, but the steps or operations are merely examples, and other embodiments of the present application may perform other The operation or the deformation of the various operations in FIG. Moreover, the various steps in FIG. 10 may be performed in a different order than that presented in FIG. 10, and it is possible that not all operations in FIG. 10 are to be performed.
  • the first SDAP entity of the source base station sends first indication information to the first PDCP entity of the source base station.
  • the first PDU session includes at least one QoS flow, and the at least one QoS flow corresponds to one PDCP entity.
  • the first PDCP in the at least one PDCP entity corresponds to a first QoS flow (referred to as QoS flow #1) in the first PDU session, and the QoS flow #1 may be any one of the first PDU sessions.
  • At least one QoS flow included in the first PDU session further includes other QoS flows except QoS flow #1 (referred to as QoS flow #2 to QoS flow #R, R is greater than or equal to If the number of integers is 2)
  • QoS flow #2 to QoS flow #R R is greater than or equal to If the number of integers is 2)
  • other PDCPs in the at least one PDCP entity corresponding to QoS flow #2 to QoS flow #R are one-to-one.
  • the entity may perform backhaul of the data packets of QoS flow #2 to QoS flow #R with reference to the operation of the first PDCP entity.
  • the first SDAP entity sends the first indication information to the first PDCP entity if the first SDAP entity in the source base station does not cache the data packet or has the buffered data packet but stops sending the data packet to the first PDCP entity.
  • the first indication information is used to indicate that the first SDAP entity no longer sends the data packet of the QoS flow #1 to the first PDCP entity.
  • the first PDCP entity may determine, according to the first indication information, the last data packet sent by the first SDAP entity that it receives.
  • the first indication information may be an end identification packet, and the SDAP header of the end identification packet carries an end identifier.
  • the end identification packet can be an empty data packet.
  • the first PDCP entity sends a QoS flow #1 buffered in the first PDCP entity to the second PDCP entity by using a data tunnel between the first PDCP entity and the second PDCP entity of the target base station (referred to as data tunnel #1).
  • the data packet (denoted as packet #1 to packet #i, i is an integer greater than or equal to 1).
  • the second PDCP entity corresponds to QoS flow #1.
  • first PDCP entity and the second PDCP entity may establish the data tunnel #1 by using the existing technology or a newly proposed method in the future. This application example does not limit this.
  • the source base station sends the second indication information to the target base station according to the first indication information.
  • the second indication information is used to indicate that the first PDCP entity has sent the data packet cached in the QoS flow #1 of the first PDCP entity, that is, the data packet #1 to the data packet #i.
  • the source base station may determine, according to the first indication information, for example, the end identifier packet, the last data packet sent by the first SDAP entity, that is, the data packet #i. Therefore, after transmitting the data packet #i, the source base station sends the second indication information to the source base station, and the second indication information is used to notify the target base station that the source base station has sent the data packet buffered by the first PDCP entity, and then no longer goes to the first The second PDCP entity sends a data packet.
  • the first indication information for example, the end identifier packet
  • the source base station sends the second indication information to the source base station, and the second indication information is used to notify the target base station that the source base station has sent the data packet buffered by the first PDCP entity, and then no longer goes to the first
  • the second PDCP entity sends a data packet.
  • the second indication information may be sent by a message between the Xn interfaces, for example, by a SN STATUS TRANSFER.
  • the first PDCP entity may allocate a PDCP SN for all data packets that are buffered, in which case the second indication information may be a maximum PDCP sequence number of the data packet buffered by the first PDCP entity. That is, PDCP of packet #i. Alternatively, the second indication information may be the next largest serial number to be assigned.
  • the second indication information may be a second end identifier packet, and the second end identifier packet carries an end identifier.
  • the source base station may determine the data buffered by the first PDCP entity according to the first indication information. After the last packet in the packet (ie, packet #i), the second end identification packet is set. And after sending the data packet #i to the second PDCP entity, sending the second end identifier packet.
  • the second end identifier packet may be an empty data packet, and the end identifier may be carried in the GTPU header or the GTPU extension header of the end identifier packet.
  • the target base station may release the resource of the data tunnel #1.
  • S1004 The second PDCP entity sends the data packet #1 to the data packet #i to the terminal.
  • the method may further include:
  • the first SDAP entity sends a first PDU session buffered in the first SDAP entity to the second SDAP entity by using a data tunnel between the first SDAP entity and the second SDAP entity of the target base station (referred to as data tunnel #2).
  • the packet and the first end identification packet are referred to as data tunnel #2.
  • the data packet buffered in the first PDU session of the first SDAP entity is recorded as: data packet (i+1) to data packet M, and M is an integer greater than or equal to 2.
  • the first SDAP entity sends the data packet (i+1) to the data packet M through the data tunnel #2, and after transmitting the data packet M, sends the first end identification packet.
  • the first end identification packet is received by the first SDAP entity from the core network user plane device.
  • the first end identifier packet includes an end identifier, where the first end identifier packet is used to indicate that the first SDAP entity has sent the data packet buffered in the first PDU session of the first SDAP entity.
  • the second SDAP entity corresponds to the first PDU session. After receiving the first end identifier packet, the second SDAP entity may determine that the first SDAP entity has sent the data packet buffered by the first SDAP entity.
  • the second PDCP entity sends, according to the second indication information, a data packet received from the second SDAP entity after the data packet #1 to the data packet #i are sent, and the second SDAP entity corresponds to the first PDU session.
  • the second PDCP entity may determine, according to the second indication information, that the data packet received from the first PDCP entity has been sent to the terminal. Then, the second PDCP entity resends the data packet of the first PDU session received from the second SDAP. In this way, it is ensured that after the data packet that needs to be returned is sent, the data packet after the back-transmission data packet is sent, so that the disorder of the data packet of the first PDU session can be avoided.
  • step S1005 if the first SDAP entity sends the data packet (i+1) to the data packet M through the data tunnel #2, then in step S1006, the second PDCP entity has sent the terminal to the terminal according to the second indication information.
  • the second PDCP entity After receiving the data packet by the PDCP entity, the second PDCP entity sends the data packet (i+1) to the data packet M received from the second SDAP.
  • the second SDAP After the data packet before the first end identifier packet is sent, the second SDAP starts to send the data packet of the QoS flow #1 received from the user plane of the core network to the second PDCP entity. In this way, it is possible to ensure that the data packet after the back-transmitted data packet is transmitted after the transmission of the back-transmitted data packet is received, thereby avoiding the disorder of the data packet of the first PDU session.
  • the mapping relationship between the QoS flow and the DRB in the target base station and the source base station is inconsistent, for example, the QoS flow #1 in the source base station is mapped to the DRB #1 (corresponding to the first PDCP entity), and the QoS flow is in the target base station.
  • the second SDAP entity sends the first PDU in the second PDCP entity and the PDCP entity in the target base station corresponding to QoS flow #2 to QoS flow #R
  • the data packets are sent to the second PDCP and the PDCP entity in the target base station corresponding to the QoS flow #2 to QoS flow #R.
  • FIG. 11 is a schematic flow chart of a transmission method according to the present application. It should be understood that FIG. 11 is a schematic flowchart of a transmission method of an embodiment of the present application, showing detailed communication steps or operations of the method, but the steps or operations are merely examples, and other embodiments of the present application may perform other The operation or the deformation of the various operations in FIG. Moreover, the various steps in FIG. 11 may be performed in a different order than that presented in FIG. 11, and it is possible that not all operations in FIG. 11 are to be performed.
  • the first SDAP of the source base station sends the first PDU session cached by the first SDAP entity to the second SDAP entity by using a data tunnel between the first SDAP entity and the second SDAP entity of the target base station (referred to as data tunnel #3). Packet.
  • the method may further include:
  • At least one PDCP entity of the source base station sends a data packet buffered to the first PDU session of the at least one PDCP entity to the second SDAP entity by using the data tunnel #3;
  • the at least one PDCP entity includes one or more PDCP entities, and the one or more PDCP entities are in one-to-one correspondence with one or more QoS flows in the first PDU session, and the at least one PDCP entity may cache the first one. All packets in the PDU's data packet that need to be returned.
  • the first SDAP sends the data packet of the first PDU session cached by the first SDAP entity to the second SDAP entity through the data tunnel #3.
  • the first SDAP and the at least one PDCP entity send, by using the data tunnel #3, the data packet of the first PDU session cached by the first SDAP entity to the second SDAP entity. a data packet of the first PDU buffered by the at least one PDCP entity.
  • S1103 The source base station sends first indication information to the target base station.
  • the first indication information may be an end identification packet.
  • the source base station sends second indication information to the target base station, where the second indication information may be an end identification packet.
  • the at least one PDCP entity does not cache the data packet
  • the data packet buffered by the first SDAP entity is a data packet that is not assigned a PDCP SN number.
  • the source base station may indicate the end of the sending data packet by sending an end identification packet.
  • all the data packets buffered by the at least one PDCP entity have no unassigned PDCP SN number
  • the data packets buffered by the first SDAP entity are all data packets that are not assigned the PDCP SN number.
  • the source base station may end by sending.
  • the identity packet indicates the end of the sent packet.
  • the first indication information includes a PDCP SN number of a last one of the data packets buffered in the at least one PDCP entity, or a next PDCP SN number to be allocated.
  • the at least one PDCP entity may assign a PDCP SN number to all data packets it caches.
  • the source base station may send an end identification packet to the terminal to indicate the end of the transmission of the data packet buffered by the first SDAP entity, and send the PDCP SN number of the last data packet or the next PDCP SN number to be allocated, indicating The end of the transmission of the buffered data packet in the at least one PDCP entity.
  • S1104 The second SDAP entity sends the data packet received by the data tunnel #3 to the terminal.
  • the second SDAP sends the data packet received by the second SDAP entity to the corresponding PDCP entity according to the corresponding (or mapping) relationship between the QoS flow and the PDCP, and the PDCP entity may further process the data packet by referring to the prior art. Until it is sent to the terminal through the physical layer.
  • the second SDAP entity determines, according to the second indication information, that the data packet received by the data tunnel #3 has been sent, and then sends the data packet received from the core network user plane device.
  • the SDAP entity delivers the data packet that does not carry the PDCP SN number to the PDCP entity.
  • the PDCP entity of the target base station sends the PDCP SDU carrying the PDCP SN number of a certain QoS flow to complete, and then notifies the SDAP entity that the QoS flow packet is sent, and the SDAP starts again.
  • the data packet of the QoS flow that does not carry the PDCP SN number is delivered to the PDCP entity of the corresponding DRB according to the mapping relationship between the QoS flow of the target base station and the DRB.
  • FIG. 12 is a schematic flow chart of a transmission method in accordance with the present application.
  • the method shown in FIG. 12 can be applied to a handover process of a terminal in a dual connection (DC) scenario, and specifically, can be applied to at least one QoS flow in a first PDU session (referred to as QoS flow #1).
  • the uplink transmission scenario from the source base station to the target base station.
  • the source base station may be a primary base station or a secondary base station.
  • the target base station may be a secondary base station or a primary base station, which is not limited in this embodiment of the present application.
  • the source base station generates start transmission information when it is determined that the terminal does not send the data packet of the at least one quality of service QoS flow in the first protocol data unit PDU session to the source base station.
  • the source base station sends the start sending information to a target base station, where the start sending information is used to instruct the target base station to send, to the core network user plane device, the at least one sent by the terminal to the target base station.
  • a data packet of the QoS flow the start transmission information including an identifier of the at least one QoS flow and an identifier of the first PDU session, or the start transmission information includes an identifier of the at least one QoS flow and a first DRB And the identifier of the first DRB corresponding to the at least one QoS flow.
  • the target base station sends, according to the start sending information, a data packet of the at least one QoS flow sent by the terminal to the target base station to the core network user plane device.
  • the start sending information is an end identification packet, or the start sending information is a control plane message.
  • FIG. 13 is a schematic flow chart of a transmission method in accordance with the present application. It should be understood that FIG. 13 is a schematic flowchart of a transmission method of an embodiment of the present application, showing detailed communication steps or operations of the method, but the steps or operations are merely examples, and other embodiments of the present application may perform other The operation or the deformation of the various operations in FIG. Moreover, the various steps in FIG. 13 may be performed in a different order than that presented in FIG. 13, and it is possible that not all operations in FIG. 13 are to be performed.
  • the method shown in FIG. 13 can be applied to a handover process of a terminal in a dual connection (DC) scenario, and specifically, can be applied to at least one QoS flow in a first PDU session (referred to as QoS flow #1).
  • the uplink transmission scenario from the source base station to the target base station.
  • the source base station may be a primary base station or a secondary base station.
  • the target base station may be a secondary base station or a primary base station, which is not limited in this embodiment of the present application.
  • the terminal before the QoS flow #1 is migrated to the target base station, the terminal sends a data packet of the QoS flow #1 to the source base station on the DRB (referred to as DRB #1) between the terminal and the source base station, and the DRB# 1 corresponds to QoS flow #1.
  • DRB #1 the source base station on the DRB
  • the source base station and the target base station can interact according to steps S1301 and S1302.
  • the source base station sends a first request message to the target base station.
  • the first request message is used to request migration of QoS flow #1 to the target base station.
  • the source base station determines to migrate the QoS flow #1 to the target base station
  • the first request message is sent to the target base station, and the target base station is requested to accept the QoS flow #1 by using the first request message.
  • the first request message may be an Xn interface message or carried by an Xn interface message.
  • the first base station sends a first response message to the source base station.
  • the source base station sends a first notification message to the terminal.
  • the first notification message is used to instruct the terminal to send the data packet of the QoS flow #1 to the target base station.
  • the first notification message may be used to instruct the terminal to map the QoS flow #1 to the DRB #2, and send the data packet of the QoS flow #1 to the target base station on the DRB #2.
  • the target base station notifies the terminal to transmit the data packet of the QoS flow #1 to the target base station.
  • the target base station transmits a first notification message to the terminal to notify the terminal to map QoS flow #1 to DRB #2, and to transmit the data packet of QoS flow #1 to the target base station on DRB #2.
  • S1304 The terminal sends a data packet of QoS flow #1 to the target base station.
  • the terminal stops transmitting the data packet of QoS flow #1 to the source base station, and starts transmitting the data packet of QoS flow #1 to the target base station on DRB #1.
  • the data packet of the QoS flow #1 transmitted by the terminal to the source base station is referred to as data packet #1 to data packet #i. That is, the data packets of the QoS flow #1 transmitted by the terminal to the source base station are: data packet #1, data packet #2, ..., and data packet #i, i is an integer greater than or equal to 1.
  • the terminal starts to send the data packet after the data packet #i to the target base station, that is, the terminal sequentially sends the data packet #(i+1) to the target base station, and the data packet #(i+2) , ..., packet #N.
  • N is an integer greater than or equal to 2
  • data packet #N is the last data in the data packet of QoS flow #1 sent by the terminal to the target base station. package.
  • S1305 The terminal sends the end packet information to the source base station.
  • the end packet information is used to indicate information of the last data packet in the data packet of the QoS flow #1 sent by the terminal to the source base station, that is, information of the data packet #i.
  • the end packet information may be an end identification packet.
  • the end identification packet includes an end identifier and identification information of QoS flow #1.
  • the end packet information may also be a PDCP sequence (Sequence, SN) number corresponding to the data packet #i.
  • PDCP sequence Sequence, SN
  • the source base station sends, to the core network user plane device, a data packet of the QoS flow #1 sent by the terminal to the source base station, that is, data packet #1 to data packet #i.
  • the source base station transmits the start transmission information to the target base station after determining to transmit the data packet #1 to the data packet #i according to the end packet information.
  • the start sending information includes an identifier (ID) of the QoS flow #1 and an ID of the first PDU session, or the start sending information includes an ID of the QoS flow #1 and an ID of the DRB #2 (ie, the first DRB). .
  • the start transmission information is used to instruct the target base station to start transmitting the data packet of the QoS flow #1 sent by the terminal to the target base station to the core network user plane device.
  • the source base station may determine, according to an algorithm implementation, a time for sending the start sending information to the target base station, for example, according to the data transmission delay, estimating that the data packet sent by the target base station reaches the core network user plane device before the data packet #i.
  • the target base station sends a data packet of the QoS flow #1 sent by the terminal to the target base station to the core network user plane device according to the start sending information.
  • the source base station After the source base station sends the data packet #i, if the data packet of the QoS flow #1 is not found after the data packet #i is terminated according to the end packet, that is, the terminal does not continue to send the data packet of the QoS flow #1 to the source base station, Then, the start transmission information is sent to the target base station. For example, if the packet #i is followed by the end identification packet, or the PDCP SN number of the transmitted data packet #i is equal to the PDCP SN number sent by the terminal to the source base station, the source base station may determine that there is no QoS flow after the packet #i# 1 packet. At this time, the source base station transmits a start transmission information to the target base station. After receiving the start of transmitting the information, the target base station starts transmitting the data packet #(i+1) to the data packet #N received by the terminal on the DRB #1 to the core network user plane device.
  • the start sending information may be an Xn interface message or carried by an Xn interface message.
  • the start sending information may be end packet information, such as an end identification packet, or a PDCP SN number corresponding to the data packet #i.
  • the source base station may send the end identification packet by using a backhaul data tunnel with the target base station.
  • the source base station may send the end identifier packet received by the terminal to the target base station; the source base station may also generate the end identifier packet by itself, for example, the source base station determines that the terminal does not send the data packet of the QoS flow #1 to the source base station, and may generate the end identifier. package.
  • the start sending information may further carry indication information (indicated as indication information #1) indicating the transmission direction of the data packet of QoS flow #1, and the indication information #1 is used to indicate the transmission direction of the data packet of QoS flow #1.
  • indication information #1 indicates the transmission direction of the data packet of QoS flow #1.
  • the source base station determines, according to the end packet information, that the transmission of the data packet of the QoS flow of the terminal to the source base station to be migrated to the target base station is completed, and sends the received by the terminal to the core network user plane device.
  • the target base station After the data packet of the QoS flow, the target base station starts to send the data packet of the QoS flow that is migrated from the source base station to the target base station to the core network user plane device by starting to send the information, and the target base station starts to send the information to the core network user according to the start.
  • the polygon device transmits the data packet of the QoS flow, thereby being able to avoid the out of order of the QoS flow data packet.
  • FIG. 14 is a schematic flowchart of a transmission method according to another embodiment of the present application.
  • the source base station sends the start sending information to a target base station.
  • the start sending information is used to instruct the target base station to start sending, to the terminal, a data packet of the at least one QoS flow that is received by the target base station from a core network user plane device, where the start sending information includes the at least one An identifier of the QoS flow and an identifier of the first PDU session, or the start transmission information includes an identifier of the at least one QoS flow and an identifier of the first data radio bearer DRB, the first DRB and the at least one The QoS flow corresponds.
  • the target base station sends, according to the start sending information, a data packet of the at least one QoS flow received from the core network user plane device to the terminal.
  • the start sending information is an end identification packet, or the start sending information is a control plane message.
  • FIG. 15 is a schematic flow chart of a transmission method in accordance with the present application. It should be understood that FIG. 15 is a schematic flowchart of a transmission method of an embodiment of the present application, showing detailed communication steps or operations of the method, but the steps or operations are merely examples, and other embodiments of the present application may perform other The operation or the deformation of the various operations in Fig. 15. Moreover, the various steps in FIG. 15 may be performed in a different order than that presented in FIG. 15, and it is possible that not all operations in FIG. 15 are to be performed.
  • the method shown in FIG. 15 can be applied to a handover process of a terminal in a dual connection (DC) scenario, and specifically, can be applied to at least one QoS flow in a first PDU session (referred to as QoS flow #1).
  • QoS flow #1 a first PDU session
  • the source base station may be a primary base station or a secondary base station.
  • the target base station may be a secondary base station or a primary base station, which is not limited in this embodiment of the present application.
  • the terminal before the QoS flow #1 is migrated to the target base station, the terminal sends a data packet of the QoS flow #1 to the source base station on the DRB (referred to as DRB #1) between the terminal and the source base station, and the DRB# 1 corresponds to QoS flow #1.
  • DRB #1 the source base station
  • the source base station and the target base station can interact according to steps S1501 and S1502.
  • the source base station sends a first request message to the target base station.
  • the first request message is used to request migration of QoS flow #1 to the target base station.
  • the source base station determines to migrate the QoS flow #1 to the target base station
  • the first request message is sent to the target base station, and the target base station is requested to accept the QoS flow #1 by using the first request message.
  • the target base station or the source base station sends a route change message to the core network element to notify the change of the target route address of the core network QoS flow #1.
  • the source base station sends an end indication message to the terminal.
  • the source base station stops sending the data packet of the QoS flow #1 to the terminal. And sending an end indication message to the terminal, and the end indication information indicates that the source base station ends the transmission of the data packet of the QoS flow #1.
  • the end indication information may end the identification package.
  • the end identification packet carries the ID of QoS flow #1.
  • the end identification packet can be an empty data packet.
  • the encapsulation header of the null data packet may carry an end identifier, for example, carrying an end identifier in the SDAP or PDCP extension header.
  • the end indication information may be a PDCP SN number corresponding to the data packet #i. If the terminal successfully receives the data packet before the PDCP SN number, it may be determined that all data packets of the QoS flow #1 sent by the source base station have been received.
  • the UPF carries the end identifier of the data packet of the QoS flow in the data packet sent to the MN, indicating the end of the data packet sent by the UPF to the QoS flow of the MN.
  • the UPF may set the end identifier of the QoS flow according to the indication information of the QoS flow migration sent by the MN to the core network.
  • the UPF may further set an end identifier of the QoS flow according to the path switching indication sent by the SN to the core network, where the path switching indication is used to indicate that the UPF may start sending the data packet of the QoS flow to the SN. In this way, the MN determines the end of the packet of QoS flow1 received from the UPF.
  • the data packet of the QoS flow #1 transmitted by the source base station to the terminal on the DRB #1 is denoted as: packet #1 to packet #i. That is, the data packets of the QoS flow #1 transmitted by the source base station to the terminal are: data packet #1, data packet #2, ..., and data packet #i, i is an integer greater than or equal to 1. Then, after transmitting the data packet #i, the source base station sends an end indication message to the terminal. It should be understood that DRB#1 corresponds to QoS flow #1, or has a mapping relationship between the two.
  • the source base station receives feedback information sent by the terminal.
  • the terminal If the terminal successfully receives the data packet #1 to the data packet #i, and determines that all the data packets of the QoS flow #1 sent by the source base station have been successfully received according to the end indication information sent by the source base station, the terminal sends the feedback information to the source base station.
  • the source base station sends the start sending information to the target base station according to the feedback indication information.
  • the start sending information is used to indicate that the target base station sends the data packet of the QoS flow #1 sent by the core network user plane device to the target base station to the terminal.
  • the start transmission information includes an ID of the QoS flow #1 and an ID of the first PDU session, or the start transmission information includes an ID of the QoS flow #1 and an ID of the first DRB (referred to as DRB#2), the DRB#2 Corresponds to QoS flow #1.
  • the data packet of the QoS flow #1 that sends the core network user plane device to the target base station is recorded as: data packet #(i+1) - data packet #N, N is greater than or equal to 2. Integer. That is, the data packets of the QoS flow #1 sent by the core network user plane device to the target base station are: data packet #(i+1), data packet #(i+2), ..., data packet #N.
  • the target base station transmits the data packet #(i+1) to the data packet #N to the terminal according to the start of transmission of the information.
  • the source base station after receiving the feedback information sent by the terminal, the source base station sends the start sending information to the target base station.
  • the target base station may determine that the source base station has sent the data packet of the QoS flow #1 received from the user equipment of the core network, and the terminal has successfully received the data packet, then the target base station starts again. On DRB #1, the packet #(i+1) to packet #N are transmitted to the terminal.
  • the start sending information may be end indication information, such as an end identification packet, or a PDCP SN number corresponding to the data packet #i.
  • the source base station may send the end identification packet by using a backhaul data tunnel with the target base station.
  • the end identification packet can be an empty data packet.
  • the encapsulation header of the null data packet carries an end identifier, for example, carrying an end identifier in the GTPU extension header.
  • the source base station determines, according to the feedback information, that the terminal successfully receives the data packet of the QoS flow sent by the terminal, and then starts to send the information to notify the target base station to start sending the QoS flow received from the user equipment of the core network to the terminal.
  • the data packet, the target base station starts to send the QoS flow data packet to the terminal according to the start of the transmission of the information, thereby avoiding the disorder of the QoS flow data packet.
  • FIG. 16 is a schematic flow chart of a transmission method in accordance with the present application. It should be understood that FIG. 16 is a schematic flowchart of a transmission method of an embodiment of the present application, showing detailed communication steps or operations of the method, but the steps or operations are merely examples, and other embodiments of the present application may perform other The operation or the deformation of the various operations in Fig. 16. Moreover, the various steps in FIG. 16 may be performed in a different order than that presented in FIG. 16, and it is possible that not all operations in FIG. 16 are to be performed.
  • the method shown in FIG. 16 can be applied to a handover process of a terminal in a Double Connection (DC) scenario, and specifically, can be applied to at least one QoS flow in a first PDU session (referred to as QoS flow #1).
  • the source base station may be a primary base station, or may be a secondary base station.
  • the target base station may be a secondary base station or a primary base station, which is not limited in this embodiment of the present application.
  • the terminal before the QoS flow #1 is migrated to the target base station, the terminal sends a data packet of the QoS flow #1 to the source base station on the DRB (referred to as DRB #1) between the terminal and the source base station, and the DRB# 1 corresponds to QoS flow #1.
  • DRB #1 the source base station
  • the source base station and the target base station can interact according to steps S1601 and S1602.
  • the source base station sends a first request message to the target base station.
  • the first request message is used to request migration of QoS flow #1 to the target base station.
  • the source base station determines to migrate the QoS flow #1 to the target base station
  • the first request message is sent to the target base station, and the target base station is requested to accept the QoS flow #1 by using the first request message.
  • the first indication information may be sent to the S1602 by using an Xn interface message, and if the target base station can accept the QoS flow #1, send the first response message to the source base station.
  • S1603 The source base station sends an end indication message to the terminal.
  • the source base station stops sending the data of the QoS flow #1 to the source base station. And transmitting an end indication message to the terminal, and the end indication information indicates that the source base station ends the transmission of the data packet of the QoS flow #1.
  • the end indication information may end the identification package.
  • the end identification packet carries the ID of QoS flow #1.
  • the end identification packet can be an empty data packet.
  • the encapsulation header of the null data packet may carry an end identifier, for example, carrying an end identifier in a SDAP or PDCP header.
  • the end indication information may be a PDCP SN number corresponding to the data packet #i. If the terminal successfully receives the data packet before the PDCP SN number, it may be determined that all data packets of the QoS flow #1 sent by the source base station have been received.
  • the data packet of the QoS flow #1 transmitted by the source base station to the terminal on the DRB #1 is denoted as: packet #1 to packet #i. That is, the data packets of the QoS flow #1 transmitted by the source base station to the terminal are: data packet #1, data packet #2, ..., and data packet #i, i is an integer greater than or equal to 1. Then, after transmitting the data packet #i, the source base station sends an end indication message to the terminal. It should be understood that DRB#1 corresponds to QoS flow #1, or has a mapping relationship between the two.
  • the source base station receives feedback information sent by the terminal.
  • the terminal If the terminal successfully receives the data packet #1 to the data packet #i, and determines that all the data packets of the QoS flow #1 sent by the source base station have been successfully received according to the end indication information sent by the source base station, the terminal sends the feedback information to the source base station.
  • S1605 The target base station sends a data packet of the QoS flow #1 received from the core network user plane device to the terminal. Packet #(i+1) ⁇ packet #N.
  • the data packet of the QoS flow #1 that sends the core network user plane device to the target base station is recorded as: data packet #(i+1) - data packet #N, N is greater than or equal to 2. Integer. That is, the data packets of the QoS flow #1 sent by the core network user plane device to the target base station are: data packet #(i+1), data packet #(i+2), ..., data packet #N.
  • the terminal After receiving the data packet of the QoS flow #1 sent by the source base station and the target base station, the terminal first delivers the data packet of the QoS flow #1 received from the source base station to the upper layer protocol layer, and then delivers the QoS flow received from the target base station. #1 of the packet. That is, the terminal first delivers the packet 1 to the packet #N to the upper layer protocol layer, and then delivers the packet #(i+1) to the packet #N.
  • the terminal may determine the end of the data packet of the QoS flow #1 received from the source base station according to the end indication information sent by the source base station, for example, ending the identification packet.
  • the terminal may deliver the QoS flow data received from the target base station after the data packet of the QoS flow received from the source base station is delivered to the upper layer protocol layer according to the end indication information sent by the source base station. package. Therefore, in the process of QoS flow migrating from the source base station to the target base station, the QoS flow data packet can be sequentially transmitted to ensure the service quality of the service, and the service quality degradation caused by the out of order of the data packet is avoided.
  • FIG. 17 is a schematic diagram of a data transmission device 10 according to an embodiment of the present disclosure. As shown in FIG. 17, the device 10 may be a terminal device, or may be a chip or a circuit, such as a terminal device. Chip or circuit. The terminal device may correspond to the terminal device in the foregoing method.
  • the apparatus 10 can include a processor 11 (i.e., an example of a processing unit) and a memory 12.
  • the memory 12 is for storing instructions for executing the instructions stored by the memory 12 to cause the apparatus 10 to perform the steps performed by the terminal device in the above method.
  • the device 10 may further include an input port 13 (ie, an example of a communication unit) and an output port 14 (ie, another example of a communication unit).
  • the processor 11, memory 12, input port 13 and output port 14 can communicate with one another via internal connection paths to communicate control and/or data signals.
  • the memory 12 is configured to store a computer program, and the processor 11 can be used to call and run the computer program from the memory 12 to control the input port 13 to receive signals, and control the output port 14 to send signals to complete the terminal device in the above method.
  • the memory 12 can be integrated in the processor 11 or can be provided separately from the processor 11.
  • the input port 13 is a receiver
  • the output port 14 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 13 is an input interface
  • the output port 14 is an output interface
  • the functions of the input port 13 and the output port 14 can be implemented by a dedicated chip through a transceiver circuit or a transceiver.
  • the processor 11 can be implemented by a dedicated processing chip, a processing circuit, a processor, or a general purpose chip.
  • the terminal device provided by the embodiment of the present application may be implemented by using a general-purpose computer.
  • the program code that implements the functions of the processor 11, the input port 13, and the output port 14 is stored in the memory 12, and the general purpose processor implements the functions of the processor 11, the input port 13, and the output port 14 by executing the code in the memory 12.
  • modules or units in the communication device 10 listed above are merely exemplary.
  • the modules or units in the communication device 10 may be used to perform various actions or processes performed by the terminal device in any of the above methods. Here, in order to avoid redundancy, a detailed description thereof will be omitted.
  • FIG. 18 is a schematic structural diagram of a terminal device 20 provided by the present application.
  • the terminal device 20 can be used to perform the actions of the terminal device described in any of the above methods.
  • FIG. 4 shows only the main components of the terminal device.
  • the terminal device 20 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 terminal device, executing the software program, and processing the data of the software program, for example, in the embodiment of the indication method for supporting the terminal device to perform the foregoing transmission precoding matrix.
  • the memory is primarily used to store software programs and data, such as the codebooks 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 together with the antenna can also be called a transceiver, and is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves.
  • 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. 18 shows only one memory and processor for ease of illustration. In an actual terminal device, 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 the communication protocol and the communication data, and the central processing unit is mainly used to control and execute the entire terminal device.
  • the processor in FIG. 18 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 device may include a plurality of baseband processors to accommodate different network standards, and the terminal device may include a plurality of central processors to enhance its processing capabilities, and various components of the terminal devices 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 processing unit 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.
  • the antenna and control circuit having the transceiving function can be regarded as the transceiving unit 201 of the terminal device 20, and the processor having the processing function is regarded as the processing unit 202 of the terminal device 20.
  • the terminal device 20 includes a transceiver unit 201 and a processing unit 202.
  • the transceiver unit can also be referred to as a transceiver, a transceiver, a transceiver, and the like.
  • the device for implementing the receiving function in the transceiver unit 201 can be regarded as a receiving unit, and the device for implementing the sending function in the transceiver unit 201 is regarded as a sending unit, that is, the transceiver unit 201 includes a receiving unit and a sending unit.
  • the receiving unit may also be referred to as a receiver, a receiver, a receiving circuit, etc.
  • the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit or the like.
  • FIG. 19 is a schematic diagram 2 of the data transmission device 30 according to the embodiment of the present application.
  • the device 30 may be a network device, or may be a chip or a circuit, such as may be disposed in a network device. Chip or circuit.
  • the network device corresponds to the network device in any of the foregoing methods.
  • the apparatus 30 can include a processor 31 (ie, an example of a processing unit) and a memory 32.
  • the memory 32 is for storing instructions for executing the instructions stored by the memory 32 to cause the apparatus 30 to perform the steps performed by the network device in any of the methods described above.
  • the device 30 may further include an input port 33 (ie, an example of a communication unit) and an output port 33 (ie, another example of the processing unit).
  • the processor 31, memory 32, input port 33, and output port 34 can communicate with one another via internal connection paths to communicate control and/or data signals.
  • the memory 32 is used to store a computer program.
  • the processor 31 can be used to call and run the computer program from the memory 32 to control the input port 33 to receive signals, and control the output port 34 to send signals to complete the terminal in the method 200.
  • the memory 32 can be integrated in the processor 31 or can be provided separately from the processor 31.
  • the control input port 33 receives the signal, and the control output port 34 transmits a signal to complete the steps of the network device in the above method.
  • the memory 32 can be integrated in the processor 31 or can be provided separately from the processor 31.
  • the input port 33 is a receiver
  • the output port 34 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 33 is an input interface
  • the output port 34 is an output interface
  • the device 30 may not include the memory 32, and the processor 31 may read an instruction (program or code) in the memory external to the chip to implement any of the foregoing.
  • the function of the network device in the method may not include the memory 32, and the processor 31 may read an instruction (program or code) in the memory external to the chip to implement any of the foregoing.
  • the function of the network device in the method may not include the memory 32, and the processor 31 may read an instruction (program or code) in the memory external to the chip to implement any of the foregoing.
  • the functions of the input port 33 and the output port 34 can be implemented by a dedicated chip through a transceiver circuit or a transceiver.
  • the processor 31 can be implemented by a dedicated processing chip, a processing circuit, a processor, or a general purpose chip.
  • a network device provided by an embodiment of the present application may be implemented by using a general-purpose computer.
  • the program code that implements the functions of the processor 31, the input port 33, and the output port 34 is stored in a memory, and the general purpose processor implements the functions of the processor 31, the input port 33, and the output port 34 by executing code in the memory.
  • Each module or unit in the communication device 30 can be used to perform various operations or processes performed by the network device in any of the above methods. Here, in order to avoid redundancy, detailed description thereof will be omitted.
  • FIG. 20 is a schematic structural diagram of a network device according to an embodiment of the present disclosure, which may be used to implement the function of a network device in any of the foregoing methods.
  • a base station As shown in FIG. 20, the base station can be applied to the system as shown in FIG. 1.
  • the base station 40 includes one or more radio frequency units, such as a remote radio unit (RRU) 401 and one or more baseband units (BBUs) (also referred to as digital units, DUs) 402. .
  • RRU remote radio unit
  • BBUs baseband units
  • DUs digital units
  • the RRU 401 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 4011 and a radio frequency unit 4012.
  • the RRU 401 part is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals and baseband signals, for example, for transmitting the signaling messages described in the foregoing embodiments to the terminal device.
  • the BBU 402 portion is mainly used for performing baseband processing, controlling a base station, and the like.
  • the RRU 401 and the BBU 402 may be physically disposed together or physically separated, that is, distributed base stations.
  • the BBU 402 is a control center of a base station, 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, spreading, and the like.
  • the BBU (processing unit) 402 can be used to control the base station 40 to perform the operation procedure of the network device in the foregoing method embodiment.
  • the BBU 402 may be composed of one or more boards, and multiple boards may jointly support a single access standard radio access network (such as an LTE system or a 5G system), or may support different ones. Access to the standard wireless access network.
  • the BBU 402 also includes a memory 4021 and a processor 4022.
  • the memory 4021 is used to store necessary instructions and data.
  • the memory 4021 stores the codebook or the like in the above embodiment.
  • the processor 4022 is configured to control the base station to perform necessary actions, for example, to control the base station to perform an operation procedure about the network device in the foregoing method embodiment.
  • the memory 4021 and the processor 4022 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 can be set on each board.
  • SoC System-on-chip
  • all or part of the functions of the 402 part and the 401 part may be implemented by the SoC technology, for example, by a base station function chip.
  • the base station function chip integrates a processor, a memory, an antenna interface and the like.
  • the program of the base station related function is stored in the memory, and the processor executes the program to implement the related functions of the base station.
  • the base station function chip can also read the memory external to the chip to implement related functions of the base station.
  • FIG. 9 the structure of the base station illustrated in FIG. 9 is only one possible form, and should not be construed as limiting the embodiments of the present application. This application does not preclude the possibility of other forms of base station architecture that may arise in the future.
  • the embodiment of the present application further provides a communication system including the foregoing network device and one or more terminal devices.
  • the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and dedicated integration.
  • DSPs digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (ROMM), an erasable programmable read only memory (erasable PROM, EPROM), or an electrical Erase programmable EPROM (EEPROM) or flash memory.
  • the volatile memory can be a random access memory (RAM) that acts as an external cache.
  • RAM random access memory
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • synchronous dynamic randomness synchronous dynamic randomness.
  • Synchronous DRAM SDRAM
  • DDR SDRAM double data rate synchronous DRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory Take memory
  • DR RAM direct memory bus random access memory
  • the above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination.
  • the above-described embodiments may be implemented in whole or in part in the form of a computer program product.
  • the computer program product comprises one or more computer instructions or computer programs.
  • the processes or functions described in accordance with embodiments of the present application 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, 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 contains one or more sets of available media.
  • the usable medium can be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium.
  • the semiconductor medium can be a solid state hard drive.
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a removable hard disk, a read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请提供一种传输方法和数据传输装置，能够避免数据包的乱序。该方法包括：源接入网设备通过其与目标接入网设备的第二PDCP实体之间的数据隧道，向该目标接入网设备发送该源接入网设备中的第一分组数据汇聚协议PDCP实体中的第一部分数据包，该第一部分数据包为第一协议数据单元PDU会话中的第一服务质量QoS流的数据包，该第一PDU会话包括至少一个QoS流，该至少一个QoS流与至少一个PDCP实体对应，该至少一个QoS流包括该第一QoS流，该至少一个PDCP实体包括该第一PDCP实体，该第一PDCP实体与该第一QoS流对应；该源接入网设备向该目标接入网设备发送第一指示信息，该第一指示信息用于指示该第一PDCP实体中的该第一部分数据包已经发送结束。

Description

数据传输方法和数据传输装置
本申请要求于2017年8月11日提交中国专利局、申请号为201710687846.0、发明名称为“数据传输方法和数据传输装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种。数据传输方法和数据传输装置。
背景技术
在长期演进(Long Term Evolution，LTE)通信系统中，终端在接入网侧进行移动时，发送接收数据的接入网网元发生改变，接入网网元通知核心网网元改变用户面的数据隧道，从而保证业务的连续性。而核心网的改变用户面数据隧道会在旧的数据隧道上发送结束标识，通知发送下行数据包的结束，其中，所述用户面数据隧道是按照EPS Bearer建立的。
而在下一代通信系统中，引入基于服务质量流(Quality of Service flow，QoS flow)服务流的QoS架构，在核心网网元和接入网网元之间按照包数据单元(Packet Data Unit，PDU)会话(session)建立数据包隧道，一个PDU会话中可包含一个或多个QoS flow。因此，在终端进行移动时，可能是一个或多个QoS flow的数据隧道需要发生改变，还可能是PDU会话的数据隧道需要改变。核心网网元如何设置结束标识是一个需要解决的问题。
发明内容
本申请提供一种传输方法和数据传输装置，能够避免数据包的乱序。
第一方面，提供一种传输方法，包括：源接入网设备通过其与目标接入网设备的第二PDCP实体之间的数据隧道，向所述目标接入网设备发送所述源接入网设备中的第一分组数据汇聚协议PDCP实体中的第一部分数据包，所述第一部分数据包为第一协议数据单元PDU会话中的第一服务质量QoS流的数据包，所述第一PDU会话包括至少一个QoS流，所述至少一个QoS流与至少一个PDCP实体一一对应，所述至少一个QoS流包括所述第一QoS流，所述至少一个PDCP实体包括所述第一PDCP实体，所述第一PDCP实体与所述第一QoS流对应，所述第一QoS流为所述至少一个QoS流中的任一个；所述源接入网设备向所述目标接入网设备发送第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的所述第一部分数据包已经发送结束。
可选地，所述第一指示信息包括所述第一部分数据包中的所有数据包所携带的 PDCP序列号中的最大PDCP序列号；或者
所述第一指示信息包括下一个待分配的PDCP序列号；或者，所述第一指示信息为所述第一PDCP实体生成的结束标识包。
可选地，在所述源接入网设备向所述目标接入网设备发送所述第一PDCP实体的第一部分数据包之前，所述方法还包括：所述源接入网设备确定所述源接入网设备中的第一服务数据适配协议SDAP实体结束向所述第一PDCP实体发送所述第一QoS流的数据包，其中，所述第一SDAP实体向所述第一PDCP实体发送的所述第一QoS流的数据包为所述第一部分数据包，所述第一SDAP实体与所述第一PDU会话对应。
可选地，所述第二指示信息为所述第一SDAP实体根据从核心网用户面设备接收到的结束标识包发送的。
第二方面，提供一种传输方法，包括：目标接入网设备通过其第二分组数据汇聚协议PDCP实体与源接入网设备的第一PDCP实体之间的数据隧道，接收所述第一PDCP实体发送的第一部分数据包，所述第一部分数据包为第一协议数据单元PDU会话中的第一服务质量QoS流的数据包，所述第一PDU会话包括至少一个QoS流，所述至少一个QoS流与至少一个PDCP实体一一对应，所述至少一个QoS流包括所述第一QoS流，所述至少一个PDCP实体包括所述第一PDCP实体，所述第一PDCP实体与所述第一QoS流对应，所述第二PDCP实体与所述第一QoS流对应，所述第一QoS流为所述至少一个QoS流中的任一个；所述目标接入网设备接收所述源接入网设备发送的第一指示信息，所述第一指示信息用于指示所述第一PDCP实体已发送完所述第一部分数据包。
可选地，所述方法还包括：所述目标接入网设备根据所述第一指示信息，在确定已向终端发送完所述第一部分数据包中的所有数据包后，向终端发送从所述目标接入网设备的第二SDAP实体接收的数据包。
可选地，所述第一指示信息包括所述第一部分数据包中的所有数据包所携带的PDCP序列号中的最大PDCP序列号；或者，所述第一指示信息包括下一个待分配的PDCP序列号；或者，所述第一指示信息为所述第一PDCP实体生成的结束标识包。
第三方面，提供一种传输方法，包括：如果确定终端不再向源接入网设备发送第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，所述源接入网设备生成触发信息；所述源接入网设备向目标接入网设备发送所述触发信息，所述触发信息用于指示所述目标接入网设备向核心网用户面设备发送由所述终端发送至所述目标接入网设备的所述至少一个QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一DRB的标识，所述第一DRB与所述至少一个QoS流对应。
第四方面，提供一种传输方法，包括：目标接入网设备接收源接入网设备发送的触发信息，所述触发信息用于指示所述目标接入网设备向核心网用户面设备发送由所述终端发送至所述目标接入网设备的第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一数据无线承载 DRB的标识，所述第一DRB与所述至少一个QoS流对应；所述目标接入网设备根据所述触发信息，向所述核心网用户面设备发送由所述终端发送至所述目标接入网设备的所述至少一个QoS流的数据包。
可选地，所述触发信息为结束标识包，或所述触发信息为接入网设备间的消息。
第五方面，提供一种传输方法，包括：如果源接入网设备确定终端接收到所述源接入网设备发送的第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，所述源接入网设备生成触发信息；所述源接入网设备向目标接入网设备发送所述触发信息，所述触发信息用于指示所述目标接入网设备开始向所述终端发送所述目标接入网设备从核心网用户面设备接收的所述至少一个QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一数据无线承载DRB的标识，所述第一DRB与所述至少一个QoS流对应。
第六方面，提供一种传输方法，包括：目标接入网设备接收源接入网设备发送的触发信息，所述触发信息用于指示所述目标接入网设备开始向终端发送所述目标接入网设备从核心网用户面设备接收的第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一数据无线承载DRB的标识，所述第一DRB与所述至少一个QoS流对应；所述目标接入网设备根据所述触发信息，向所述终端发送从所述核心网用户面设备接收的所述至少一个QoS流的数据包。
可选地，所述触发信息为结束标识包，或所述触发信息为接入网设备间的控制面消息。
第七方面，提供了一种数据传输装置，包括用于执行上述第一至第六方面中任一方面及其的各实现方式中的传输方法的各步骤的单元。
在一种设计中，该数据传输装置为通信芯片，通信芯片可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
在另一种设计中，所述数据传输装置为通信设备，通信芯片可以包括用于发送信息或数据的发射机，以及用于接收信息或数据的接收机。
第八方面，提供了一种通信设备，包括，处理器，存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该通信装置执行第一至第六方面中任一方面及其可能实现方式中的传输方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
可选的，该通信设备还包括，发射机(发射器)和接收机(接收器)。
第九方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面至第六方面中任一种可能实现方式中的方法。
第十方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第二方面中任一种可能实现方式中的方法。
第九方面，提供了一种芯片系统，包括存储器和处理器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得安装有该芯片系统的通信设备执行上述第一方面至第六方面中任一种可能实现方式中的方法。
附图说明
图1是本申请实施例的通信系统架构示意图。
图2是本申请实施例的传输方法的示意性流程图。
图3是本申请实施例的传输方法的示意性流程图。
图4是本申请实施例的传输方法的示意性流程图。
图5是本申请实施例的传输方法的示意性流程图。
图6是本申请实施例的传输方法的示意性流程图。
图7是本申请实施例的传输方法的示意性流程图。
图8是本申请实施例的传输方法的示意性流程图。
图9是本申请实施例的传输方法的示意性流程图。
图10是本申请实施例的传输方法的示意性流程图。
图11是本申请实施例的传输方法的示意性流程图。
图12是本申请实施例的传输方法的示意性流程图。
图13是本申请实施例的传输方法的示意性流程图。
图14是本申请实施例的传输方法的示意性流程图。
图15是本申请实施例的传输方法的示意性流程图。
图16是本申请实施例的传输方法的示意性流程图。
图17为本申请实施例提供的用于数据传输装置的示意图。
图18为本申请提供的一种终端设备的结构示意图。
图19为本申请实施例提供的数据传输装置的示意图
图20为本申请实施例提供的一种网络设备的结构示意图。
具体实施方式
在下一代通信系统中，一种基于服务质量流(Quality of Service flow，QoS flow)的架构被提出，其将支持保障流速率的QoS flow和不保障流速率的QoS flow。
参见图1，图1是5G下的QoS flow架构。如图1所示，对于每个终端，基站为该终端的每个PDU会话(session)建立一个或者多个DRB。基站将属于不同PDU会话的数据包映射到不同的DRB中。QoS flow是在PDU会话实现QoS区分的最小粒度。PDU会话是终端和外部数据网络之间的链接以提供分组数据单元链接服务。每一PDU会话具有一唯一标识，PDU会话的唯一标识可以是PDU session identity。QoS flow是一组数据包的集合，其中，同一QoS flow的数据包具备相同的QoS特性，在3GPP网络中得到相同的包转发处理。
5G下基于DRB定义了空口上的包处理机制。由一个DRB服务的包在空口上具有相同的包处理机制。基站可建立多个DRBs以满足具有不同包处理需求的QoS flows。
例如，对于下行链路，基站将基于NG-U(即，N3接口)上QFI标识和对应的QoS profile，将属于QoS flow的下行数据包映射到DRB上。对于上行链路，UE根据基站配置的QoS flow到DRB的映射或者反射映射，将属于QoS flow的上行数据包映射到DRB上。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、未来的第五代(5th Generation，5G)系统或新无线(New Radio，NR)等。
本申请实施例中的终端可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端设备、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备等，本申请实施例对此并不限定。
本申请实施例中的接入网设备或基站可以是用于与终端设备通信的设备，该网络设备可以是全球移动通讯(Global System of Mobile communication，GSM)系统或码分多址(Code Division Multiple Access，CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系 统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional NodeB，eNB或eNodeB)，还可以是云无线接入网络(Cloud Radio Access Network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。
本申请实施例中的核心网设备由核心网控制面设备和核心网用户面设备组成。
新无线接入网络(Next Generation Radio Access Network，NG-RAN)由gNB和或演进的eNB组成，其中，gNB提供终止于终端的NR控制面和用户面协议栈。其中演进的eNB是指链接到5G核心网的演进的LTE基站。本申请描述中，gNB和演进的eNB可统一称为基站。
gNB提供下述功能至少之一：接入控制、链接移动性管理、无线承载控制、测量配置和提供、动态资源分配等。
接入移动管理功能：(Access and Mobility Management Function，AMF)提供非接入层(non access stratum，NAS)安全管理、接入层(access stratum，AS)安全控制、移动性管理、终端接入验证、注册区域管理、切片支持、会话管理功能(Session Management function，SMT)选择等功能至少之一。
用户面功能(User Plane Function，UPF)提供切换锚点、数据包的路由转发、QoS管理等功能至少之一。
SMF，提供会话管理、终端地址分配和管理、UPF的选择和控制等功能至少之一。
其中，下一代核心网控制面设备包含但不限于AMF和SMF。下一代核心网用户面设备包含但不限于UPF。
AMF和NG-RAN之间的接口定义为N2接口，UPF和NG-RAN之间的接口定义为N3接口。gNB之间的接口定义为Xn接口。
本申请实施例中的开始发送信息和触发信息可以相互替换。SN可以是辅基站，MN可以说主基站。
下文中，接入网设备可以和基站相互替换。
图2是根据本申请的一个传输方法的示意性流程图。图2所示的方法可以应用于终端的第一PDU会话中的至少一个QoS流(记作QoS flow#1)转移到目标基站的过程中。例如，在双链接场景下，终端的第一PDU会话中的QoS flow#1转移到目标基站(主基站或辅基站)，而该第一PDU会话中剩余部分QoS流仍在源基站(辅基站或辅基站)。下面，结合图2，对本申请实施例的传输方法进行详细描述。
S210，第一基站向核心网设备发送第一请求消息。
第一请求消息包括第一PDU会话的标识和QoS flow#1的标识，第一请求消息用于请求更改所述QoS flow#1的用户面路由至第二基站。
应理解，第一基站可以是双链接场景下的主基站。在主基站为源基站的情况下，辅基站为第二基站，即第一基站和第二基站为不同的基站。在主基站为目标基站的情况下，主基站为第二基站，即第一基站与第二基站为同一基站。
还应理解，核心网设备为兼容核心网用户面设备功能和核心网控制面设备功能的设备。
可选地，所述第一请求消息可以为路径切换请求消息。这样，可以更好的兼容现有技术。
S220，核心网设备根据第一请求消息发送结束标识包。
具体地，若核心网用户面同意将QoS flow#1的用户面路由至第二基站，则向第二基站发送结束标识包。该结束标识包包括QoS flow#1的标识，该结束标识包表示所述核心网设备结束在第一PDU会话的源数据隧道中发送QoS flow#1的数据包。也就是说，该结束标识包表示核心网用户面不再在源数据隧道中发送QoS flow#1的数据包。
所述结束标识包可以为空数据包。此外，该空数据包的封装头中可以携带一个结束标识，例如在通用分组数据隧道协议用户面(General Packet Radio Service tunnel protocol user plane，GTPU)头或扩展头中携带结束标识。该空数据包的封装头中可以携带QoS flow#1的标识。
进一步地，核心网设备可发送多个结束标识包，以提高源基站正确接收结束标识包的成功率。
需要说明的是，若第一基站为QoS flow#1的源基站，那么步骤S220具体为：核心网设备根据第一请求消息向第一基站发送结束标识包。若第一基站为QoS flow#1的目标基站，第一基站与第二基站为同一基站，那么步骤S220具体为：核心网设备根据第一请求消息向第二基站或第一基站发送结束标识包。
本申请实施例的传输方法，核心网设备根据接入网设备发送的第一请求消息，通过发送结束标识包向接入网设备指示核心网用户面设备结束在源数据隧道中的QoS流的下行传输。从而，可以实现QoS流级别或粒度的下行传输的切换，进而能够增强系统的灵活性。
图3是根据本申请的另一传输方法的示意性流程图。图3所示的方法可以应用于终端的第一PDU会话中的至少一个QoS流(记作QoS flow#1)或全部QoS流转移到目标基站的过程中。例如，在切换过程中，终端的第一PDU会话中的全部QoS流转移到目标基站，或者第一PDU会话中的所有QoS流欲转移到目标基站但是只有QoS flow#1在目标基站接纳成功。又如，在双链接场景下，终端的第一PDU会话中的QoS flow#1转移到目标基站(主基站或辅基站)，而该第一PDU会话中剩余部分QoS流仍在源基站(辅基站或辅基站)。
下面，结合图3，对本申请实施例的传输方法进行详细描述。
S301，接入网设备向核心网控制面设备发送请求消息#1。请求消息#1包括第一PDU会话的标识。
可选地，该路由更改请求的消息还可以包括QoS flow#1的标识。
具体地，接入网设备可以是源基站，也可以是目标基站。在路由更改请求的消息1由源基站发送的情况下，该请求消息#1还包括QoS flow#1的标识，该请求消息#1用于请求更改第一PDU会话的QoS flow#1的用户面路由至所述目标基站。应理解，这里的源基站为双链接场景下的主基站或辅基站，相应地，这里的目标基站为双链接场景下的辅基站或主基站。在请求消息#1由目标基站发送的情况下，若该请求消息#1只包括第一PDU会话的标识，则该路由更改的请求消息用于请求切换第一PDU会话的数据隧道至目标基站。
进一步的，该请求消息#1中还可以包含一个独立的指示信息(记作指示信息#1A)，指示信息#1A用于指示是第一PDU会话的数据隧道进行切换，还是QoS flow#的路由发生改变。
应理解，在本申请所描述的所有实施例中，第一PDU会话的数据隧道的切换，是指核心网用户面设备和源基站之间的第一PDU会话对应的数据隧道在数据隧道切换完成后不再使用，在数据隧道切换后，核心网用户面设备和终端使用核心网用户面设备和目标基站之间的与第一PDU会话对应的数据隧道传输数据。QoS flow#1的用户面路由的更改，是指路由改变的QoS flow#1在核心网用户面设备和目标基站之间的与QoS flow#1对应的数据隧道上传输，而路由未改变的第一PDU会话中的QoS流继续在核心网用户面设备和源基站之间的与第一PDU会话对应的数据隧道上传输。
可选地，所述请求消息#1可以为路径切换请求消息。这样，可以更好的兼容现有技术。
S302，核心网控制面设备向核心网用户面设备发送请求消息#2。
请求消息#2可以与请求消息#1相同也可以不同。在请求消息#2可以与请求消息#1不同的情况下，请求消息#2为核心网控制面设备根据请求消息#1生成的，请求消息#2包括第一PDU会话的标识。可选地，请求消息#2还可以包括QoS flow#1的标识。
S303，核心网用户面设备更改数据包的路由，向源基站发送结束标识包。
其中，该结束标识包包括QoS flow#1的ID。该结束标识包用于向源基站指示，核心网用户面设备不再向源基站发送QoS flow#1的数据包。
具体地，若该请求消息#1只包括第一PDU会话的ID或还包括指示信息#1，，则核心网用户面设备向源基站发送该结束标识包。或者，该路由更改请求的消息1还包括QoS flow#1的ID或者还包括QoS flow#1的ID和指示信息#1，，则核心网用户面设备向源基站发送该结束标识包。
进一步地，核心网用户面设备可发送多个结束标识包，以提高源基站正确接收结束标识包的成功率。
所述结束标识包可以为空数据包。此外，该空数据包的封装头中可以携带一个结束标识，例如在GTPU头或扩展头中携带结束标识。该空数据包的封装头中可以携带QoS flow#1的标识。
可选地，步骤S303中的结束标识包的格式可以包括多个QoS流字段，该多个QoS流字段与多个QoS一一对应。本申请实施例中，在步骤S303中发送的结束标识包还可以是专用的结束标识包。在此情况下，该结束标识包可以携带QoS flow#1的ID，也可以不携带QoS flow#1的ID。
比如，若该请求消息#1用于请求切换第一PDU会话的数据隧道至目标基站，那么，核心网用户面设备可以向源基站发送结束标识包#1，该结束标识包#1用于指示核心网用户面设备不再向源基站发送第一PDU会话中任何一个QoS流的数据包。进一步的，结束标识包#1还可以携带一个指示信息(记作指示信息#1B)，指示信息#1B用于指示结束标识包#1是针对第一PDU会话中所有QoS流的。
又如，若该请求消息#1用于请求更改QoS flow#1的数据隧道至目标基站，，那么，核心网用户面设备可以向源基站发送结束标识包#2，该结束标识包#2用于指示核心网用户面设备不再向源基站发送QoS flow#1的数据包。进一步的，结束标识包#2还可以携带一个指示信息(记作指示信息#1C)，指示信息#1C用于指示结束标识包#2是针对QoS流的。
应理解，结束标识包#1和结束标识包#2为不同结构的数据包。
进一步的，在第一次进行QoS流的路由改变时，例如进行QoSflow#1的路由改变时，接入网设备可以通知核心网控制面设备路由改变的QoS流所属PDU会话的数据隧道在目标基站的路由地址以及目标基站的ID。后续进行同一PDU会话中的QoS流的路由改变时，接入网设备可只通知核心网控制面设备目标基站标识或目标路由地址。
上述的路由地址包含传输层地址和通用分组数据隧道协议端点标识(GPRS Tunnelling Protocol Tunnel Endpoint Identifier，GTP TE id)。
进一步的，结束标识包还可以携带一个指示信息，用于指示所述结束标识包是针对QoS flow的，还可以指示是针对QoS flow组的，例如，基站请求一组QoS flow的路由改变，则核心网用户面设备可以设置结束标识包来表示该QoS flow组的数据包在所述PDU session的原数据隧道中发送的结束。
本申请实施例的传输方法，核心网用户面设备根据接入网设备通过核心网控制面设备发送的请求消息#1，通过结束标识包向源基站指示核心网用户面设备结束向源基站的下行传输中该至少一个QoS流的下行传输。从而，可以实现QoS流级别或粒度的下行传输的切换，进而能够增强系统的灵活性。
图4是根据本申请另一传输方法的示意性流程图。图4中的核心网用户面设备可以是UPF，核心网控制面设备可以是SMF和/或AMF，但申请实施例对此不作限定。
图4所示的方法可以应用于终端的第一PDU会话中的至少一个QoS流(记作QoS flow#1)或全部QoS流转移到目标基站的过程中。例如，在切换过程中，终端的第一PDU会话中的全部QoS流转移到目标基站，或者第一PDU会话中的转移到目标基站但是只有QoS flow#1在目标基站接纳成功。又如，在双链接过程中，终端的第一PDU会话中的QoS flow#1转移到目标基站(主基站或辅基站)，而该第一PDU会话中的的剩余部分QoS流仍在源基站(主基站或辅基站)。
下面，结合图4，对本申请实施例的传输方法进行详细描述。
S401，接入网设备向核心网控制面设备发送第一请求消息。
该第一请求消息用于核心网控制设备向核心网用户面设备请求更改用户面路由至目标基站。
应理解，该接入网设备可以是源基站，也可以是目标基站。在第一请求消息由源基站发送的情况下，该第一请求消息用于请求更改某一PDU会话(记作第一PDU会话)中的至少一个QoS流(记作QoS flow#1)的用户面路由至所述目标基站。应理解，这里的源基站为多连接场景下的主基站或辅基站，相应地，这里的目标基站为多连接场景下的辅基站或主基站。在路由更改请求消息由目标基站发送的情况下，该路由更改请求消息用于请求切换第一PDU会话的数据隧道至目标基站。
S402，核心网控制面设备根据第一请求消息向核心网用户面设备发送第二请求消息，通过第二请求消息通知核心网用户面设备更改路由。
S403，核心网用户面设备向源基站发送结束标识包。
S404，在源基站确定对应于该结束标识包的第一请求消息为路由更改请求的消息的情况下，源基站可以确定该结束标识包表示核心网用户面设备结束在第一PDU会话的源数据隧道中的QoS flow#1的数据包的传输。
可选地，该方法还可以包括：
在所源基站确定对应于结束标识包的第一请求消息为路径更改请求消息的情况下，源基站可以确定结束标识包表示核心网用户面设备结束在第一PDU会话的源数据隧道中的所有QoS流的数据包的传输。
具体来讲，源基站可以根据其发送的消息的类型来判断核心网用户面设备发送的结束数据包结束的是QoS flow#1还是整个第一PDU会话。若第一请求消息为路由更改请求的消息，则该结束标识包指示核心网用户面设备结束在第一PDU会话的源数据隧道中的QoS flow#1的数据包的传输。若第一请求消息为路径更改请求消息，则该结束标识包指示核心网用户面设备结束在第一PDU会话的源数据隧道中的所有QoS流的数据包的传输。
其中，在接入网设备为主基站，主基站为目标基站，辅基站为源基站的情况下，源基站根据和目标基站之间的消息交互，来判断目标基站向核心网控制面设备发送的第一请求消息的类型。
例如，若源基站向目标基站发送切换请求的消息，则目标基站向核心网控制面设备发送第一请求消息的类型为路径更改请求消息。
若源基站向目标基站发送终端的部分QoS flow迁移到目标基站的请求消息，则目标基站向核心网控制面设备发送第一请求消息的类型为路由更改请求的消息。
进一步的，源基站可以根据不同的场景来判断结束标识包对应的是QoS flow还是PDU session。例如在切换场景下，判断结束标识包指示核心网用户面设备结束在第一PDU会话的源数据隧道中的所有QoS流的数据包的传输。在双链接场景下，该结束标识包指示核心网用户面设备结束在第一PDU会话的源数据隧道中的QoS flow#1的数据包的传输。
进一步地，核心网用户面设备可发送多个结束标识包，以提高源基站正确接收结束标识包的成功率。
所述结束标识包可以为空数据包。此外，该空数据包的封装头中可以携带一个结束标识，例如在GTPU头或扩展头中携带结束标识。
本申请实施例的传输方法，在源基站或目标基站通过第一请求消息，来请求核心网用户面设备结束源数据隧道中的一个或多个QoS流的数据包的传输时，核心网用户面设备可以通过结束标识包，向源基站指示核心网用户面设备结束源数据隧道中的整个PDU会话的数据包的传输。从而，可以实现QoS流级别或粒度的下行传输的切换，进而能够增强系统的灵活性。
另外，在目标基站通过路径更改请求消息请求结束源数据隧道中的整个PDU会话的所有QoS流的数据包的传输时，核心网用户面设备也可以通过相同格式的结束标识包，向源基站指示核心网用户面设备结束源数据隧道中的整个PDU会话的数据包的传输。由于核心网用户面设备采用统一格式的结束标识包，因此，能够降低核心网用户面设备和源基站对结束标识包的处理复杂度。
图5是根据本申请另一传输方法的示意性流程图。图5中的核心网用户面设备可以是UPF，核心网控制面设备可以是SMF和/或AMF。
下面，结合图5，对本申请实施例的传输方法进行详细描述。
S501，源基站接收终端或核心网用户面设备发送的结束标识包。该结束标识包包括第一PDU会话的标识和至少一个QoS流(记作QoS flow#1)的标识；
S502，源基站根据该结束标识包释放或终止对应于QoS flow#1的资源。
可选地，源基站释放终端的上下文中的QoS flow#1的参数。
具体来讲，终端或核心网用户面设备可以自主决定终止QoS flow#1的传输。例如，终端决定终止QoS flow#1的上行传输时，终端通过发送结束标识包的方式，通知源基站QoS flow#1的上行传输的结束。终端发送结束标识包后，将不再向源基站发送QoS flow#1的数据包。再如，核心网用户面设备决定终止QoS flow#1的下行传输时，核心网用户面设备通过发送结束标识包的方式，通知源基站QoS flow#1的下行传输的结束。核心网用户面设备发送结束标识包后，将不再向源基站发送QoS flow#1的数据包。源基站接收到结束标识包后，将不再向终端发送QoS flow#1的数据包。
可选地，终端或核心网用户面设备可发送多个结束标识包，以提高源基站正确接收结束标识包的成功率。
所述结束标识包可以为空数据包。此外，该空数据包的封装头中可以携带一个结束标识，例如在GTPU头或扩展头中携带结束标识。该空数据包的封装头中可以携带QoS flow#1的ID。
本申请实施例的传输方法，终端或核心网用户面设备可以通过发送包括QoS流ID的结束标识包来终止QoS flow#1的传输。
源基站接收到结束标识包后，可以释放或终止为QoS flow#1分配的资源。
进一步地，源基站可以释放保持的终端上下文中的QoS flow#1的QoS参数。所述QoS参数包含但不限于时延、丢包率、优先级、速率等指标参数。从而，能够节省系统资源。
下面，结合图6、7和8对应用于系统间切换过程中的传输方法进行详细描述。具体地，图6、7和8所示的传输方法可以用于数据包或数据的返传过程中。
所述数据返传或数据包返传，是指源基站将从核心网用户面设备或终端收到的数据包传输到目标基站，目标基站向终端或核心网用户面设备发送从源基站收到的数据包。
下文中，第一核心网控制面设备可以是AMF和/或SMF，第二核心网控制面设备可以是MME，第一核心网用户面设备可以是UPF，第二核心网用户面设备可以是S-GW。
图6是根据本申请的一个传输方法的示意性流程图。以下，结合图6，对本申请实施例的传输方法进行详细描述
S601，源基站向第一核心网控制面设备发送第一请求消息。
第一请求消息包括返传指示，该返传指示用于指示第一核心网用户面设备将属于所述第一PDU会话的返传数据包发送至目标基站。
可选地，第一请求消息还可以包括至少一个QoS流(记作QoS flow#1)的ID。通过该QoS flow#1的ID指示，源基站建议通过QoS flow#1进行返传数据包的传输。
需要说明的是，所述返传数据包可以是指，源基站从第一核心网用户面设备(例如，UPF)接收到的数据包中，所有未收到终端接收确认的数据包，或者所有尚未发送到终端的数据包。
S602，第一核心网控制面设备根据所述第一请求消息，向源基站发送第一响应消息。
所述第一响应消息包括与所述第一PDU会话对应的至少一个第一EPS承载的标识和所述返传指示。
S603，源基站根据第一响应消息生成源基站到目标基站的透明容器信息。
所述透明容器信息，可以包括源基站的无线相关信息，例如，E-RAB ID列表、每一E-RAB ID对应的E-RABUE历史信息，返传指示等。其中，E-RAB和EPS Bearer是一一对应的。应理解这里的返传指示是指示E-RAB有数据需要返传。
S604，源基站向核心网控制面设备发送切换请求消息，该切换请求消息包括所述透明容器信息。
之后，各节点，例如源基站、目标基站等可以按照现有技术执行切换过程，本申请实施例在此不再详述。通过这方式，源基站可以指示目标基站哪些E-RAB存在下行数据需要进行返传。
图7是根据本申请的一个传输方法的示意性流程图。应理解，图7是本申请一个实施例的传输方法的示意性流程图，示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图7中的各种操作的变形。此外，图7中的各个步骤可以分别按照与图7所呈现的不同的顺序来执行，并且有可能并非要执行图7中的全部操作。
以下，结合图7，对本申请实施例的传输方法进行详细描述。
S701，源基站向第一核心网用户面设备发送返传数据包和第一结束标识包。
其中，第一结束标识包为源基站从第一核心用户面设备接收到的，第一结束标识包可以是空数据包。此外，该空数据包的封装头中携带一个结束标识，例如在GTPU头或扩展头中携带结束标识。
具体地，源基站可以和第一核心网用户面设备之间建立用于数据返传的数据隧道。其中，所述数据返传隧道是按照PDU会话建立的，即每一PDU会话建立一条传输返传数据包的数据返隧道。与第一PDU会话对应的按照PDU会话建立的数据隧道可以记作：数据隧道#1，那么，源基站可以通过数据隧道#1向第一核心网用户面设备发送返传数据包和第一结束标识包。
所述第一结束标识包可以是按PDU session设置的，指示所述session中包的结束，或者是按QoS flow设置的，指示所述QoS flow中包的结束。
S702，第一核心网用户面设备根据第一会话与第一EPS承载的对应关系以及第一结束标识包，生成第二结束标识包。第二结束标识包携带所述第一EPS承载的标识。
S703，第一核心网用户面设备向第二核心网用户面设备发送返传数据包和第二结束标识包。
具体地，第一核心网用户面设备和第二核心网用户面设备之间，以及第二核心网用户面设备和目标基站之间按照EPS承载建立用于数据返传的数据隧道。与第一PDU会话对应的按照EPS承载建立的数据隧道可以记作：数据隧道#2，那么，第一核心网用户面设备可以通过数据隧道#2向向第二核心网用户面设备发送返传数据包和第二结束标识包。
S704，第二核心网用户面设备向目标基站发送返传数据包和第二结束标识包。
S705，目标基站根据所述第二结束标识，在向终端发送完返传数据包后，再向终端发送从第二核心网用户面设备接收到的数据包。
具体地，目标基站先发送接收到的返传数据包，根据第二结束标识包判断EPS承载上的返传数据包发送结束后，再发送从第二核心网用户面设备接收的数据包(即新数据包)。从而，能够保证EPS承载数据包的按序传输。
本申请实施例中，目标基站接收并检测到第二结束标识包后，可丢弃第二结束标识包。进一步地，目标基站可释放数据隧道#2的资源。
本申请实施例的传输方法，第一核心网用户面设备通过设置并发送与EPS承载对应的第二结束标识包，使得目标基站能够根据该结束标识包，先发送完从源基站接收的返传数据包后，再发送从二核心网用户面设备接收的新数据包，从而保证了EPS承载的数据包的按序传输。
图8是根据本申请的一个传输方法的示意性流程图。应理解，图8是本申请一个实施例的传输方法的示意性流程图，示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图8中的各种操作的变形。此外，图8中的各个步骤可以分别按照与图8所呈现的不同的顺序来执行，并且有可能并非要执行图8中的全部操作。
以下，结合图8，对本申请实施例的传输方法进行详细描述。
S801，源基站向第一核心网用户面设备发送返传数据包和第一结束标识包。
其中，第一结束标识包为源基站从第一核心用户面设备接收到的，第一结束标识包可以是空数据包。此外，该空数据包的封装头中可以携带一个结束标识，例如在GTPU头或扩展头中携带结束标识。
具体地，源基站可以和第一核心网用户面设备之间建立用于数据返传的数据隧 道。其中，所述数据返传隧道是按照PDU会话建立的，即每一PDU会话建立一条传输返传数据包的数据返隧道。与第一PDU会话对应的按照PDU会话建立的数据隧道可以记作：数据隧道#1，那么，源基站可以通过数据隧道#1向第一核心网用户面设备发送返传数据包和第一结束标识包。
S802，第一核心网用户面设备根据所述第一结束标识包，先后向第二核心网用户面设备发送返传数据包和新数据包。
具体地，第一核心网用户面设备和第二核心网用户面设备之间，以及第二核心网用户面设备和目标基站之间按照EPS承载建立数据隧道，用于传输从第一核心网用户面设备收到的源基站返传的下行数据(即，返传数据包)和新数据包。这里，按照EPS承载建立的数据隧道可以记作：数据隧道#3。第一核心网用户面设备根据第一结束标识包，确定通过数据隧道#3发送完返传数据包后，丢弃该第一结束标识包。然后，再通过数据隧道#3发送新数据包。
进一步的，返传数据包的封装头中可以携带QoS flow的标识,第一核心网用户面设备根据所述QoS flow的标识，确定数据隧道#3。例如，根据QoS flow和EPS Bearer之间的对应关系，索引到EPS Bearer对应的数据隧道。
S803，第二核心网用户面设备先后向目标基站发送返传数据包和新数据包。
S804，目标基站向终端发送从第二核心网用户面设备接收的下行数据包。该下行数据包包括返传数据包和新数据包。
通过本申请实施例的方法，源基站将返传数据包发送到第一核心网用户面设备，第一核心网用户面设备先发送从源基站接收的返传数据包，再发送新数据包，从而保证了EPS承载数据包的按序传输。并且第一核心网用户面设备和第二核心网用户面设备，第二核心网用户面设备和目标基站之间不需要建立下行数据返传的隧道，减少了开销。目标基站不用区分返传数据包和新数据包。
上文描述了系统间切换的数据返传，下文，结合图9、10和11应用于系统间切换过程中的数据返传的传输方法进行详细描述。
首先，需要说明的是，下文中结合图9、10和11所描述的源基站需要发送到目标基站的第一PDU会话的数据包为第一PDU会话的数据包中需要返传的数据包。第一PDU会话的数据包中需要返传的数据包可以是以下中的任一种。
(1)源基站从核心网用户面设备接收到的第一PDU会话的数据包中，所有未收到终端接收确认的数据包和/或尚未发送到终端的数据包。
(2)源基站的第一SDAP实体中缓存的数据包，即SDAP SDU。
(3)源基站的第一SDAP实体中缓存的数据包和PDCP实体未发送成功的数据包。
应理解，第一SDAP实体与第一PDU会话对应。所述未收到终端接收确认的数据包、尚未发送到终端的数据包和PDCP实体未发送成功的数据包都缓存在PDCP实体中，因此，源基站需要发送到目标基站的第一PDU会话的数据包即为第一SDAP实体中缓存的数据包和/或PDCP实体中缓存的数据包。具体地，若第一SDAP实体中有缓存的数据包，则源基站需要发送到目标基站的第一PDU会话的数据包为第一SDAP实体中缓存的数据包和PDCP实体中缓存的数据包，若第一SDAP实体中没有缓存的数据 包，则源基站需要发送到目标基站的第一PDU会话的数据包为PDCP实体中缓存的数据包。
图9是根据本申请的一个传输方法的示意性流程图。应理解，图9是本申请一个实施例的传输方法的示意性流程图，示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图9中的各种操作的变形。此外，图9中的各个步骤可以分别按照与图9所呈现的不同的顺序来执行，并且有可能并非要执行图9中的全部操作。
以下，结合图9，对本申请实施例的一个传输方法进行详细描述。
S901，源基站通过第一分组数据汇聚协议PDCP实体与目标基站的第二PDCP实体之间的数据隧道，向所述目标基站发送第一PDCP实体中的第一部分数据包。
所述第一部分数据包为第一协议数据单元PDU会话中的第一QoS流(记作QoS flow#1)的数据包，所述第一PDU会话包括至少一个QoS流，所述至少一个QoS流与至少一个PDCP实体一一对应，所述至少一个QoS流包括所述第一QoS流，所述至少一个PDCP实体包括所述第一PDCP实体，所述第一PDCP实体与所述第一QoS流对应，所述第一QoS流为所述至少一个QoS流中的任一个。
S902，所述源基站向所述目标基站发送第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中所述第一部分数据包的结束。
S903，所述目标基站根据所述第一指示信息，在确定已向终端发送完所述第一部分数据包中的所有数据包后，向终端发送从所述目标基站的SDAP实体接收的数据包。
可选地，所述第一指示信息包括所述第一部分数据包中的所有数据包所携带的PDCP序列号中的最大PDCP序列号；或者
所述第一指示信息包括下一个待分配的PDCP序列号；或者
所述第一指示信息为所述第一PDCP实体生成的结束标识包。
可选地，在所述源基站＝向所述第二PDCP实体目标基站发送所述第一PDCP实体的第一部分数据包之前，所述方法还包括：
所述第一PDCP实体接收所述源基站的第一SDAP实体发送的第二指示信息，所述第二指示信息用于指示所述第一SDAP实体结束向所述第一PDCP实体发送所述第一QoS流的数据包，其中，所述第一SDAP实体向所述第一PDCP实体发送的所述第一QoS流的数据包为所述第一部分数据包，所述第一SDAP实体与所述第一PDU会话对应。
可选地，所述第二指示信息为所述SDAP实体根据从核心网用户面设备接收到的结束标识包发送的。
图10是根据本申请的一个传输方法的示意性流程图。应理解，图10是本申请一个实施例的传输方法的示意性流程图，示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图10中的各种操作的变形。此外，图10中的各个步骤可以分别按照与图10所呈现的不同的顺序来执行，并且有可能并非要执行图10中的全部操作。
以下，结合图10，对本申请实施例的一个传输方法进行详细描述。
1001，源基站的第一SDAP实体向源基站的第一PDCP实体发送第一指示信息。
其中，第一PDU会话包括至少一个QoS流，该至少一个QoS流与一个PDCP实体对应。所述至少一个PDCP实体中的第一PDCP与第一PDU会话中的第一QoS流(记作QoS flow#1)对应，该QoS flow#1可以是第一PDU会话中的任意一个流。因此，不失一般性地，若第一PDU会话所包括的至少一个QoS流还包括除QoS flow#1外的其他QoS流(记作QoS flow#2～QoS flow#R，R为大于或等于2的整数)，那么，QoS flow#2～QoS flow#R中若存在需要返传的数据包，与QoS flow#2～QoS flow#R一一对应的所述至少一个PDCP实体中的其他PDCP实体可以参照第一PDCP实体的操作，进行QoS flow#2～QoS flow#R的数据包的返传。
具体来讲，若源基站中的第一SDAP实体没有缓存数据包或有缓存数据包但当前停止向第一PDCP实体发送数据包时，第一SDAP实体向第一PDCP实体发送第一指示信息。第一指示信息用于指示第一SDAP实体不再向所述第一PDCP实体发送QoS flow#1的数据包。第一PDCP实体根据第一指示信息，可以确定其接收到的第一SDAP实体发送的最后一个数据包。可选地，第一指示信息可以为结束标识包，所述结束标识包的SDAP头携带结束标识。该结束标识包可以是空的数据包。
S1002，第一PDCP实体通过第一PDCP实体与目标基站的第二PDCP实体之间的数据隧道(记作数据隧道#1)，向第二PDCP实体发送缓存在第一PDCP实体的QoS flow#1的数据包(记作数据包#1～数据包#i，i为大于或等于1的整数)。其中，第二PDCP实体与QoS flow#1对应。
应理解，第一PDCP实体和第二PDCP实体可以采用现有技术或未来新提出的方法建立数据隧道#1，本申请示例对此不作限定。
S1003，源基站根据第一指示信息，向目标基站发送第二指示信息。
其中，第二指示信息用于指示第一PDCP实体已发送完缓存在第一PDCP实体的QoS flow#1的数据包，即数据包#1～数据包#i。
具体来讲，源基站根据第一指示信息，例如结束标识包，可以确定其接收到的第一SDAP实体发送的最后一个数据包，即数据包#i。从而，源基站在发送数据包#i后，向源基站发送第二指示信息，通过第二指示信息告知目标基站，源基站已经发送完第一PDCP实体所缓存的数据包，之后不再向第二PDCP实体发送数据包。
可选地，第二指示信息可以通过Xn接口间的消息来发送，例如通过序列号状态传递(SN STATUS TRANSFER)来发送。
进一步地，第一PDCP实体可以为其所缓存的所有数据包分配PDCP SN，在这种情况下，第二指示信息可以是为所述第一PDCP实体所缓存的数据包的最大PDCP序列号，即数据包#i的PDCP。或者，第二指示信息可以是下一个待分配的最大序列号。
可选地，第二指示信息可以为第二结束标识包，所述第二结束标识包携带结束标识。
具体地，若第一PDCP实体所缓存的数据包包括已分配PDCP SN的数据包和未分配PDCP SN的数据包，则源基站可以根据第一指示信息，在确定第一PDCP实体所缓存的数据包中的最后一个数据包(即，数据包#i)后，设置第二结束标识包。并在向第二PDCP实体发送完数据包#i后，发送该第二结束标识包。该第二结束标识包可以是 空的数据包，该结束标识包的GTPU头或GTPU扩展头中可以携带结束标识。
进一步地，目标基站接收到第二指示信息后，可以释放数据隧道#1的资源。
S1004，第二PDCP实体向终端发送数据包#1～数据包#i。
可选地，若第一SDAP实体中缓存有数据包，该方法还可以包括：
S1005，第一SDAP实体通过第一SDAP实体与目标基站的第二SDAP实体之间的数据隧道(记作数据隧道#2)，向第二SDAP实体发送缓存在第一SDAP实体的第一PDU会话的数据包和第一结束标识包。
以下，为了便于理解和描述，将缓存在第一SDAP实体的第一PDU会话的数据包记作：数据包(i+1)～数据包M，M为大于或等于2的整数。
具体地，第一SDAP实体通过数据隧道#2发送数据包(i+1)～数据包M，并在发送数据包M后，发送第一结束标识包。第一结束标识包为第一SDAP实体从核心网用户面设备接收到的。第一结束标识包包括结束标识，第一结束标识包用于指示第一SDAP实体已发送完缓存在第一SDAP实体的第一PDU会话的数据包。第二SDAP实体与第一PDU会话对应。第二SDAP实体在接收到第一结束标识包后，可确定第一SDAP实体已发送完第一SDAP实体所缓存的数据包。
S1006，第二PDCP实体根据第二指示信息，在确定发送完数据包#1～数据包#i后，发送从第二SDAP实体接收的数据包，第二SDAP实体与第一PDU会话对应。
具体地，第二PDCP实体根据第二指示信息，可以确定已向终端发送完从第一PDCP实体接收的数据包。然后，第二PDCP实体再发送从第二SDAP接收到的第一PDU会话的数据包。这样，能够保证在发送完需要返传的数据包后，再发送返传数据包之后的数据包，从而能够避免第一PDU会话的数据包的乱序问题。
参照步骤S1005，若第一SDAP实体通过数据隧道#2发送了数据包(i+1)～数据包M，那么在S1006步骤中，第二PDCP实体根据第二指示信息已向终端发送完从第一PDCP实体接收的数据包后，第二PDCP实体再发送从第二SDAP接收到的数据包(i+1)～数据包M。第二SDAP在发送第一结束标识包之前的数据包完成后，再开始向第二PDCP实体发送从核心网用户面接收到的QoS flow#1的数据包。这样，能够保证在发送完接收到返传数据包后，再发送返传数据包之后的数据包，从而能够避免第一PDU会话的数据包的乱序问题。
本申请实施例中，若目标基站和源基站中QoS flow和DRB的映射关系不一致，比如，源基站中QoS flow#1映射到DRB#1(对应于第一PDCP实体)，目标基站中QoS flow#1映射到DRB#2(对应于第二PDCP实体)，则第二SDAP实体在第二PDCP实体和与QoS flow#2～QoS flow#R对应的目标基站中的PDCP实体发送完第一PDU会话中所有返传的数据包后，再向第二PDCP和与QoS flow#2～QoS flow#R对应的目标基站中的PDCP实体发送数据包。从而，能够保证QoS流的数据包的按序传输。
图11是根据本申请的一个传输方法的示意性流程图。应理解，图11是本申请一个实施例的传输方法的示意性流程图，示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图11中的各种操作的变形。此外，图11中的各个步骤可以分别按照与图11所呈现的不同的顺序来执行，并且有可能并非要执行图11中的全部操作。
以下，结合图11，对本申请实施例的一个传输方法进行详细描述。
S1101，源基站的第一SDAP通过第一SDAP实体与目标基站的第二SDAP实体之间的数据隧道(记作数据隧道#3)向第二SDAP实体发送第一SDAP实体缓存的第一PDU会话的数据包。
可选地，该方法还可以包括：
S1102，源基站的至少一个PDCP实体通数据隧道#3向第二SDAP实体发送缓存在所述至少一个PDCP实体的第一PDU会话的数据包；
其中，所述至少一个PDCP实体包括一个或多个PDCP实体，该一个或多个PDCP实体与第一PDU会话中的一个或多个QoS流一一对应，所述至少一个PDCP实体可以缓存第一PDU的数据包中所有需要返传的数据包。
具体来讲，在所述至少一个PDCP实体没有缓存数据包的情况下，第一SDAP通过数据隧道#3向第二SDAP实体发送第一SDAP实体缓存的第一PDU会话的数据包。在所述至少一个PDCP实体有缓存数据包的情况下，第一SDAP和所述至少一个PDCP实体通过数据隧道#3向第二SDAP实体发送第一SDAP实体缓存的第一PDU会话的数据包和所述至少一个PDCP实体缓存的第一PDU的数据包。
S1103，所述源基站向所述目标基站发送第一指示信息。
可选地，所述第一指示信息可以是结束标识包。所述源基站向所述目标基站发送第二指示信息，第二指示信息可以是结束标识包。
比如，所述至少一个PDCP实体没有缓存数据包，第一SDAP实体缓存的数据包均为没有分配PDCP SN号的数据包，此时，源基站可以通过发送结束标识包指示发送数据包的结束。
又如，所述至少一个PDCP实体缓存的所有数据包均没有未分配PDCP SN号，第一SDAP实体缓存的数据包均为没有分配PDCP SN号的数据包，此时，源基站可以通过发送结束标识包指示发送数据包的结束。
进一步地，第一指示信息包括所述至少一个PDCP实体中缓存的数据包中的最后一个数据包的PDCP SN号，或下一个待分配的PDCP SN号。
比如，所述至少一个PDCP实体可以为其所缓存的所有数据包分配PDCP SN号。在此情况下，源基站可以向终端发送结束标识包来指示第一SDAP实体缓存的数据包的发送的结束，以及发送最后一个数据包的PDCP SN号或下一个待分配的PDCP SN号，指示所述至少一个PDCP实体中缓存的数据包的发送的结束。
S1104，第二SDAP实体向终端发送通过数据隧道#3所接收到的数据包。
具体地，第二SDAP根据QoS流与PDCP的对应(或映射)关系，将第二SDAP实体接收到的数据包发送到对应的PDCP实体上，PDCP实体可以参照现有技术对数据包进行进一步处理直至通过物理层发送至终端发。
S1105，第二SDAP实体根据第二指示信息确定已发送完通过数据隧道#3所接收到的数据包后，再发送从核心网用户面设备接收到的数据包。
进一步的，若目标基站和源基站中QoS flow和DRB的映射关系不一致，则为了保证QoS flow的数据传输的按序。示例性的，SDAP实体可以在该PDU session对应的所有DRB的PDCP实体发送携带PDCP SN号的PDCP SDU后，再向PDCP实体投递 未携带PDCP SN号的数据包。
进一步的，另一种可行的方式是，目标基站的PDCP实体将包含某一QoS flow的携带PDCP SN号的PDCP SDU发送完成后，通知SDAP实体所述QoS flow数据包发送的完成，SDAP再开始将所述QoS flow的未携带PDCP SN号的数据包根据目标基站的QoS flow和DRB的映射关系，投递到对应DRB的PDCP实体中。
图12是根据本申请的一个传输方法的示意性流程图。图12所示的方法可以应用于双链接(Double Connection，DC)场景下的终端的切换过程中，具体地，可以应用于将第一PDU会话中的至少一个QoS流(记作QoS flow#1)从源基站迁移至目标基站的上行传输场景中。所述源基站可以是主基站，也可以是辅基站，相应地，所述目标基站可以是辅基站，也可以是主基站，本申请实施例对此不作限定。
S1210，源基站在确定终端不再向所述源基站发送第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包的情况下，生成开始发送信息。
S1220，所述源基站向目标基站发送所述开始发送信息，所述开始发送信息用于指示所述目标基站向核心网用户面设备发送由所述终端发送至所述目标基站的所述至少一个QoS流的数据包，所述开始发送信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述开始发送信息包括所述至少一个QoS流的标识和第一DRB的标识，所述第一DRB与所述至少一个QoS流对应。
S1230，目标基站根据所述开始发送信息，向所述核心网用户面设备发送由所述终端发送至所述目标基站的所述至少一个QoS流的数据包。
可选地，所述开始发送信息为结束标识包，或所述开始发送信息为控制面消息。
以下，结合图13所示的传输方法，对图12所示的传输方法进行详细说明。
图13是根据本申请的一个传输方法的示意性流程图。应理解，图13是本申请一个实施例的传输方法的示意性流程图，示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图13中的各种操作的变形。此外，图13中的各个步骤可以分别按照与图13所呈现的不同的顺序来执行，并且有可能并非要执行图13中的全部操作。
图13所示的方法可以应用于双链接(Double Connection，DC)场景下的终端的切换过程中，具体地，可以应用于将第一PDU会话中的至少一个QoS流(记作QoS flow#1)从源基站迁移至目标基站的上行传输场景中。所述源基站可以是主基站，也可以是辅基站，相应地，所述目标基站可以是辅基站，也可以是主基站，本申请实施例对此不作限定。
本申请实施例中，在QoS flow#1迁移至目标基站前，终端在该终端与源基站之间的DRB(记作DRB#1)上向源基站发送QoS flow#1的数据包，DRB#1与QoS flow#1对应。若源基站欲将QoS flow#1迁移至目标基站，源基站和目标基站可以按照步骤S1301和S1302进行交互。
S1301，源基站向目标基站发送第一请求消息。第一请求消息用于请求将QoS flow#1迁移到目标基站。
具体地，源基站确定将QoS flow#1迁移至目标基站时，向目标基站发送第一请求消息，通过第一请求消息请求目标基站接纳QoS flow#1。
可选地，第一请求消息可以是Xn接口消息或者通过Xn接口消息携带。
S1302，目标基站若能接纳QoS flow#1，则向源基站发送第一响应消息。
比如，目标基站判断小区的资源能够提供满足QoS flow#1的资源，则，则向源基站发送第一响应消息。
之后，可以按照本申请实施例的传输方法进行数据包的传输。以下，结合图13进行详细描述。
S1303，源基站向终端发送第一通知消息。第一通知消息用于指示终端向目标基站发送QoS flow#1的数据包。
具体地，第一通知消息可以用于指示终端将QoS flow#1映射到DRB#2，在DRB#2上向目标基站发送QoS flow#1的数据包。
需要说明的是，也可不执行步骤S1303，而由目标基站通知终端向目标基站发送QoS flow#1的数据包。例如，由目标基站向终端发送第一通知消息，以通知终端将QoS flow#1映射到DRB#2，在DRB#2上向目标基站发送QoS flow#1的数据包。
S1304，终端向目标基站发送QoS flow#1的数据包。
具体地，终端在接收到第一通知消息后，停止向源基站发送QoS flow#1的数据包，开始在DRB#1上向目标基站发送QoS flow#1的数据包。
以下，为了便于理解和描述，将终端向源基站发送的QoS flow#1的数据包记作：数据包#1～数据包#i。即，终端向源基站发送的QoS flow#1的数据包依次为：数据包#1，数据包#2，……，数据包#i，i为大于或等于1的整数。
那么，终端在接收到第一通知消息后，开始向目标基站发送数据包#i之后的数据包，即终端依次向目标基站发送数据包#(i+1)，数据包#(i+2)，……，数据包#N。本申请实施例中假设QoS flow#1的数据包的总数为N，N为大于或等于2的整数，数据包#N为终端向目标基站发送的QoS flow#1的数据包中的最后一个数据包。
S1305，终端向源基站发送结束包信息。
其中，结束包信息用于指示终端向源基站发送的QoS flow#1的数据包中的最后一个数据包的信息，即数据包#i的信息。
可选地，该结束包信息可以为结束标识包。该结束标识包包括结束标识和QoS flow#1的标识信息。
可选地，该结束包信息还可以为数据包#i所对应的PDCP序列(Sequence，SN)号。
应理解，本申请实施例并不限定步骤S1304和S1305执行的先后顺序，即，S1304可以先于S1305执行，也可以在S1305之后执行，或者与S1305同时执行。
S1306，源基站向核心网用户面设备发送终端发送至源基站的QoS flow#1的数据包，即，数据包#1～数据包#i。
S1307，源基站根据结束包信息，在确定发送完数据包#1～数据包#i后，向目标基站发送开始发送信息。
其中，开始发送信息包括QoS flow#1的标识(Identity，ID)和第一PDU会话的ID，或者，开始发送信息包括QoS flow#1的ID和DRB#2(即，第一DRB)的ID。
该开始发送信息用于指示目标基站开始向核心网用户面设备发送由终端发送至 目标基站的QoS flow#1的数据包。
进一步的，源基站可根据算法实现确定向目标基站发送开始发送信息的时间，例如根据数据传输时延，估算目标基站发送的数据包在数据包#i之前到达核心网用户面设备。
S1308，目标基站根据开始发送信息，向核心网用户面设备发送由终端发送至目标基站的QoS flow#1的数据包。
具体来讲，源基站在发送数据包#i后，若根据结束包发现数据包#i后没有QoS flow#1的数据包，即终端不再继续向源基站发送QoS flow#1的数据包，则向目标基站发送开始发送信息。例如，若数据包#i后为结束标识包，或者，发送的数据包#i的PDCP SN号等于终端发送给源基站的PDCP SN号，则源基站可以确定数据包#i后没有QoS flow#1的数据包。此时，源基站向目标基站发送开始发送信息。目标基站接收到开始发送信息后，开始向核心网用户面设备发送终端在DRB#1上接收的数据包#(i+1)～数据包#N。
可选地，开始发送信息可以是Xn接口消息或者通过Xn接口消息携带。
进一步地，开始发送信息可以为结束包信息，例如结束标识包，或者数据包#i所对应的PDCP SN号。
其中，源基站可通过和目标基站间的返传数据隧道来发送结束标识包。源基站可将从终端收到的结束标识包发送到目标基站；源基站也可自行生成结束标识包，例如源基站判断终端不再发送QoS flow#1的数据包到源基站，可生成结束标识包。
更进一步地，开始发送信息还可以携带指示QoS flow#1的数据包的传输方向的指示信息(记作指示信息#1)，指示信息#1用于指示QoS flow#1的数据包的传输方向为上行。
本申请实施例的传输方法，源基站根据结束包信息确定终端到源基站的待迁移到目标基站的QoS flow的数据包的发送完成，并向核心网用户面设备发送完从终端接收的所述QoS flow的数据包后，再通过开始发送信息通知目标基站开始向核心网用户面设备发送从源基站迁移到目标基站的QoS flow的数据包，目标基站根据该开始发送信息再开始向核心网用户面设备发送所述QoS flow的数据包，从而能够避免QoS flow的数据包的乱序。
图14是根据本申请另一实施例的传输方法的示意性流程图。
S1410，在确定源基站确定终端接收到所述源基站发送的第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包的情况下，所述源基站生成开始发送信息；
S1420，所述源基站向目标基站发送所述开始发送信息。所述开始发送信息用于指示所述目标基站开始向所述终端发送所述目标基站从核心网用户面设备接收的所述至少一个QoS流的数据包，所述开始发送信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述开始发送信息包括所述至少一个QoS流的标识和第一数据无线承载DRB的标识，所述第一DRB与所述至少一个QoS流对应。
S1430，所述目标基站根据所述开始发送信息，向所述终端发送从所述核心网用户面设备接收的所述至少一个QoS流的数据包。
可选地，所述开始发送信息为结束标识包，或所述开始发送信息为控制面消息。
图15是根据本申请的一个传输方法的示意性流程图。应理解，图15是本申请一个实施例的传输方法的示意性流程图，示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图15中的各种操作的变形。此外，图15中的各个步骤可以分别按照与图15所呈现的不同的顺序来执行，并且有可能并非要执行图15中的全部操作。
图15所示的方法可以应用于双链接(Double Connection，DC)场景下的终端的切换过程中，具体地，可以应用于将第一PDU会话中的至少一个QoS流(记作QoS flow#1)从源基站迁移至目标基站的下行传输场景中。所述源基站可以是主基站，也可以是辅基站，相应地，所述目标基站可以是辅基站，也可以是主基站，本申请实施例对此不作限定。
本申请实施例中，在QoS flow#1迁移至目标基站前，终端在该终端与源基站之间的DRB(记作DRB#1)上向源基站发送QoS flow#1的数据包，DRB#1与QoS flow#1对应。若源基站欲将QoS flow#1迁移至目标基站，源基站和目标基站可以按照步骤S1501和S1502进行交互。
S1501，源基站向目标基站发送第一请求消息。第一请求消息用于请求将QoS flow#1迁移到目标基站。
具体地，源基站确定将QoS flow#1迁移至目标基站时，向目标基站发送第一请求消息，通过第一请求消息请求目标基站接纳QoS flow#1。
S1502，目标基站若能接纳QoS flow#1，则向源基站发送第一响应消息。
之后，可以按照本申请实施例的传输方法进行数据包的传输。以下，结合图15进行详细描述。目标基站或源基站向核心网网元发送路由改变的消息，通知核心网QoS flow#1的目标路由地址的改变。
S1503，源基站向终端发送结束指示信息。
具体地，源基站在确定目标基站能接纳QoS flow#1时，例如，根据步骤S1502中的第一响应消息确定目标基站能接纳QoS flow#1时，停止向终端发送QoS flow#1的数据包，并向终端发送结束指示信息，通过该结束指示信息指示源基站结束QoS flow#1的数据包的传输。
可选地，该结束指示信息可以结束标识包。该结束标识包携带QoS flow#1的ID。
该结束标识包可以是空数据包。此外，该空数据包的封装头中可以携带一个结束标识，例如在SDAP或PDCP扩展头中携带结束标识。
可选地，该结束指示信息可以是数据包#i所对应的PDCP SN号。若终端成功接收该PDCP SN号之前的数据包，则可以确定已经接收了源基站发送的QoS flow#1的所有数据包。
进一步的，UPF在发送给MN的数据包中携带一个QoS flow的数据包的结束标识，表示UPF发送到MN的QoS flow的数据包的结束。UPF可以根据MN发送给核心网的QoS flow迁移的指示信息来设置所述QoS flow的结束标识。进一步的，UPF还可以根据SN发送给核心网的路径切换指示来设置QoS flow的结束标识，所述路径切换指示，用来指示UPF可以开始将所述QoS flow的数据包发送到SN。MN通过这种方式确定从UPF接收的QoS flow1的数据包的结束。
以下，为了便于理解和描述，将源基站在DRB#1上发送给终端的QoS flow#1的数据包记作：数据包#1～数据包#i。即，源基站向终端发送的QoS flow#1的数据包依次为：数据包#1，数据包#2，……，数据包#i，i为大于或等于1的整数。那么，源基站在发送数据包#i后，向终端发送结束指示信息。应理解，DRB#1与的QoS flow#1对应，或者说两者之间具有映射关系。
S1504，源基站接收终端发送的反馈信息。
若终端成功接收到数据包#1～数据包#i，根据源基站发送的结束指示信息，确定已经成功接收源基站发送的QoS flow#1的所有数据包，则终端向源基站发送反馈信息。
S1505，源基站根据该反馈指示信息，向目标基站发送开始发送信息。
该开始发送信息用于指示目标基站向终端发送核心网用户面设备发送至目标基站的QoS flow#1的数据包。该开始发送信息包括QoS flow#1的ID和第一PDU会话的ID，或者，开始发送信息包括QoS flow#1的ID和第一DRB(记作DRB#2)的ID，所述DRB#2与QoS flow#1对应。
以下，为了便于理解和描述，将核心网用户面设备发送至目标基站的QoS flow#1的数据包记作：数据包#(i+1)～数据包#N，N为大于或等于2的整数。即，核心网用户面设备向目标基站发送的QoS flow#1的数据包依次为：数据包#(i+1)，数据包#(i+2)，……，数据包#N。
S1506，目标基站根据开始发送信息，向终端发送数据包#(i+1)～数据包#N。
具体地，在源基站在接收到终端发送的反馈信息后，向目标基站发送开始发送信息。目标基站接收到开始发送信息后，可确定源基站已经发送完从核心网用户面设备接收到的QoS flow#1的数据包，并且终端也已成功接收这些数据包，那么，目标基站再开始在DRB#1上向终端发送数据包#(i+1)～数据包#N。
可选地，开始发送信息可以为结束指示信息，例如结束标识包，或者数据包#i所对应的PDCP SN号。
其中，源基站可通过和目标基站间的返传数据隧道来发送结束标识包。该结束标识包可以是空数据包。此外，该空数据包的封装头中携带一个结束标识，例如在GTPU扩展头中携带结束标识。
本申请实施例的传输方法，源基站根据反馈信息确定终端成功接收其发送的QoS flow的数据包后，再通过开始发送信息通知目标基站开始向终端发送从核心网用户面设备接收到的QoS flow的数据包，目标基站根据该开始发送信息开始向终端发送QoS flow的数据包，从而能够避免QoS flow的数据包的乱序。
图16是根据本申请的一个传输方法的示意性流程图。应理解，图16是本申请一个实施例的传输方法的示意性流程图，示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图16中的各种操作的变形。此外，图16中的各个步骤可以分别按照与图16所呈现的不同的顺序来执行，并且有可能并非要执行图16中的全部操作。
图16所示的方法可以应用于双链接(Double Connection，DC)场景下的终端的切换过程中，具体地，可以应用于将第一PDU会话中的至少一个QoS流(记作QoS flow#1)从源基站迁移至目标基站的下行传输场景中。所述源基站可以是主基站，也可 以是辅基站，相应地，所述目标基站可以是辅基站，也可以是主基站，本申请实施例对此不作限定。
本申请实施例中，在QoS flow#1迁移至目标基站前，终端在该终端与源基站之间的DRB(记作DRB#1)上向源基站发送QoS flow#1的数据包，DRB#1与QoS flow#1对应。若源基站欲将QoS flow#1迁移至目标基站，源基站和目标基站可以按照步骤S1601和S1602进行交互。
S1601，源基站向目标基站发送第一请求消息。第一请求消息用于请求将QoS flow#1迁移到目标基站。
具体地，源基站确定将QoS flow#1迁移至目标基站时，向目标基站发送第一请求消息，通过第一请求消息请求目标基站接纳QoS flow#1。
可选地，第一指示信息可以通过Xn接口消息发送S1602，目标基站若能接纳QoS flow#1，则向源基站发送第一响应消息。
之后，可以按照本申请实施例的传输方法进行数据包的传输。以下，结合图16进行详细描述。
S1603，源基站向终端发送结束指示信息。
具体地，源基站在确定目标基站能接纳QoS flow#1时，例如，根据步骤S1602中的第一响应消息确定目标基站能接纳QoS flow#1时，停止向源基站发送QoS flow#1的数据包，并向终端发送结束指示信息，通过该结束指示信息指示源基站结束QoS flow#1的数据包的传输。
可选地，该结束指示信息可以结束标识包。该结束标识包携带QoS flow#1的ID。
该结束标识包可以是空数据包。此外，该空数据包的封装头中可以携带一个结束标识，例如在SDAP或PDCP头中携带结束标识。
可选地，该结束指示信息可以是数据包#i所对应的PDCP SN号。若终端成功接收该PDCP SN号之前的数据包，则可以确定已经接收了源基站发送的QoS flow#1的所有数据包。
以下，为了便于理解和描述，将源基站在DRB#1上发送给终端的QoS flow#1的数据包记作：数据包#1～数据包#i。即，源基站向终端发送的QoS flow#1的数据包依次为：数据包#1，数据包#2，……，数据包#i，i为大于或等于1的整数。那么，源基站在发送数据包#i后，向终端发送结束指示信息。应理解，DRB#1与的QoS flow#1对应，或者说两者之间具有映射关系。
S1604，源基站接收终端发送的反馈信息。
若终端成功接收到数据包#1～数据包#i，根据源基站发送的结束指示信息，确定已经成功接收源基站发送的QoS flow#1的所有数据包，则终端向源基站发送反馈信息。
S1605，目标基站向终端发送从核心网用户面设备接收到的QoS flow#1的的数据包。数据包#(i+1)～数据包#N。
以下，为了便于理解和描述，将核心网用户面设备发送至目标基站的QoS flow#1的数据包记作：数据包#(i+1)～数据包#N，N为大于或等于2的整数。即，核心网用户面设备向目标基站发送的QoS flow#1的数据包依次为：数据包#(i+1)，数据包#(i+2)，……，数据包#N。
应理解，本申请并不限定步骤S1605和S1604执行的先后顺序，两者可以同时执行，或者任一者在前执行均可。
S1606，终端接收到源基站和目标基站发送的QoS flow#1的数据包后，先向上层协议层投递从源基站接收的QoS flow#1的数据包，再投递从目标基站中接收的QoS flow#1的数据包。即，终端先向上层协议层投递数据包1～数据包#N，再投递数据包#(i+1)～数据包#N。这里，终端可根据源基站发送的结束指示信息，例如结束标识包等方式，确定从源基站中接收的QoS flow#1的数据包的结束。
本申请实施例的传输方法，终端可根据源基站发送的结束指示信息，在向上层协议层投递完从源基站接收的QoS flow的数据包后，再投递从目标基站中接收的QoS flow的数据包。从而，在QoS flow从源基站迁移到目标基站的过程，可以实现QoS flow的数据包的按序传输，保证业务的服务质量，避免由于数据包乱序造成的业务服务质量的下降。根据前述方法，图17为本申请实施例提供的用于数据传输装置10的示意图一，如图17所示，该装置10可以为终端设备，也可以为芯片或电路，比如可设置于终端设备的芯片或电路。其中，该终端设备可以对应上述方法中的终端设备。
该装置10可以包括处理器11(即，处理单元的一例)和存储器12。该存储器12用于存储指令，该处理器11用于执行该存储器12存储的指令，以使该装置10实现上述方法中终端设备执行的步骤。
进一步的，该装置10还可以包括输入口13(即，通信单元的一例)和输出口14(即，通信单元的另一例)。进一步的，该处理器11、存储器12、输入口13和输出口14可以通过内部连接通路互相通信，传递控制和/或数据信号。该存储器12用于存储计算机程序，该处理器11可以用于从该存储器12中调用并运行该计算计程序，以控制输入口13接收信号，控制输出口14发送信号，完成上述方法中终端设备的步骤。该存储器12可以集成在处理器11中，也可以与处理器11分开设置。
可选地，若该装置10为终端设备，该输入口13为接收器，该输出口14为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该装置10为芯片或电路，该输入口13为输入接口，该输出口14为输出接口。
作为一种实现方式，输入口13和输出口14的功能可以考虑通过收发电路或者收发的专用芯片实现。处理器11可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的终端设备。即将实现处理器11、输入口13和输出口14功能的程序代码存储在存储器12中，通用处理器通过执行存储器12中的代码来实现处理器11、输入口13和输出口14的功能。
其中，以上列举的通信装置10中各模块或单元的功能和动作仅为示例性说明，通信装置10中各模块或单元可以用于执行上述任一方法中终端设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
该装置10所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说 明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
图18为本申请提供的一种终端设备20的结构示意图。该终端设备20可以用于执行上述任一方法中描述的终端设备的动作。为了便于说明，图4仅示出了终端设备的主要部件。如图4所示，终端设备20包括处理器、存储器、控制电路、天线以及输入输出装置。
处理器主要用于对通信协议以及通信数据进行处理，以及对整个终端设备进行控制，执行软件程序，处理软件程序的数据，例如用于支持终端设备执行上述传输预编码矩阵的指示方法实施例中所描述的动作。存储器主要用于存储软件程序和数据，例如存储上述实施例中所描述的码本。控制电路主要用于基带信号与射频信号的转换以及对射频信号的处理。控制电路和天线一起也可以叫做收发器，主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。
当终端设备开机后，处理器可以读取存储单元中的软件程序，解释并执行软件程序的指令，处理软件程序的数据。当需要通过无线发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端设备时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。
本领域技术人员可以理解，为了便于说明，图18仅示出了一个存储器和处理器。在实际的终端设备中，可以存在多个处理器和存储器。存储器也可以称为存储介质或者存储设备等，本申请实施例对此不做限制。
作为一种可选的实现方式，处理器可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端设备进行控制，执行软件程序，处理软件程序的数据。图18中的处理器集成了基带处理器和中央处理器的功能，本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独立的处理器，通过总线等技术互联。本领域技术人员可以理解，终端设备可以包括多个基带处理器以适应不同的网络制式，终端设备可以包括多个中央处理器以增强其处理能力，终端设备的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储单元中，由处理器执行软件程序以实现基带处理功能。
示例性的，在本申请实施例中，可以将具有收发功能的天线和控制电路视为终端设备20的收发单元201，将具有处理功能的处理器视为终端设备20的处理单元202。如图4所示，终端设备20包括收发单元201和处理单元202。收发单元也可以称为收发器、收发机、收发装置等。可选的，可以将收发单元201中用于实现接收功能的器件视为接收单元，将收发单元201中用于实现发送功能的器件视为发送单元，即收发单元201包括接收单元和发送单元。示例性的，接收单元也可以称为接收机、接收器、接收电路等，发送单元可以称为发射机、发射器或者发射电路等。
根据前述方法，图19为本申请实施例提供的数据传输装置30的示意图二，如 图19所示，该装置30可以为网络设备，也可以为芯片或电路，如可设置于网络设备内的芯片或电路。其中，该网络设备对应上述任一方法中的网络设备。
该装置30可以包括处理器31(即，处理单元的一例)和存储器32。该存储器32用于存储指令，该处理器31用于执行该存储器32存储的指令，以使该装置30实现前述任一方法中网络设备执行的步骤。
进一步的，该装置30还可以包括输入口33(即，通信单元的一例)和输出口33(即，处理单元的另一例)。再进一步的，该处理器31、存储器32、输入口33和输出口34可以通过内部连接通路互相通信，传递控制和/或数据信号。该存储器32用于存储计算机程序，该处理器31可以用于从该存储器32中调用并运行该计算计程序，以控制输入口33接收信号，控制输出口34发送信号，完成上述方法200中终端设备的步骤。该存储器32可以集成在处理器31中，也可以与处理器31分开设置。
以控制输入口33接收信号，控制输出口34发送信号，完成上述方法中网络设备的步骤。该存储器32可以集成在处理器31中，也可以与处理器31分开设置。
可选地，若该装置30为网络设备，该输入口33为接收器，该输出口34为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该装置30为芯片或电路，该输入口33为输入接口，该输出口34为输出接口。
可选的，若该装置30为芯片或电路，所述装置30也可以不包括存储器32，所述处理器31可以读取该芯片外部的存储器中的指令(程序或代码)以实现前述任一方法中网络设备的功能。
作为一种实现方式，输入口33和输出口34的功能可以考虑通过收发电路或者收发的专用芯片实现。处理器31可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的网络设备。即将实现处理器31、输入口33和输出口34功能的程序代码存储在存储器中，通用处理器通过执行存储器中的代码来实现处理器31、输入口33和输出口34的功能。
该通信装置30中各模块或单元可以用于执行上述任一方法中网络设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
该装置30所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
图20为本申请实施例提供的一种网络设备的结构示意图，可以用于实现上述任一方法中的网络设备的功能。如可以为基站的结构示意图。如图20所示，该基站可应用于如图1所示的系统中。基站40包括一个或多个射频单元，如远端射频单元(remote radio unit,RRU)401和一个或多个基带单元(baseband unit，BBU)(也可称为数字单元，digital unit，DU)402。所述RRU 401可以称为收发单元、收发机、收发电路、或者收发器等等，其可以包括至少一个天线4011和射频单元4012。所述RRU 401部分主要用于射频信号的收发以及射频信号与基带信号的转换，例如用于向终端设备发送上述实施 例中所述的信令消息。所述BBU 402部分主要用于进行基带处理，对基站进行控制等。所述RRU 401与BBU 402可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。
所述BBU 402为基站的控制中心，也可以称为处理单元，主要用于完成基带处理功能，如信道编码，复用，调制，扩频等等。例如该BBU(处理单元)402可以用于控制基站40执行上述方法实施例中关于网络设备的操作流程。
在一个示例中，所述BBU 402可以由一个或多个单板构成，多个单板可以共同支持单一接入制式的无线接入网(如LTE系统，或5G系统)，也可以分别支持不同接入制式的无线接入网。所述BBU 402还包括存储器4021和处理器4022。所述存储器4021用以存储必要的指令和数据。例如存储器4021存储上述实施例中的码本等。所述处理器4022用于控制基站进行必要的动作，例如用于控制基站执行上述方法实施例中关于网络设备的操作流程。所述存储器4021和处理器4022可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
在一种可能的实施方式中，随着片上系统(System-on-chip，SoC)技术的发展，可以将402部分和401部分的全部或者部分功能由SoC技术实现，例如由一颗基站功能芯片实现，该基站功能芯片集成了处理器、存储器、天线接口等器件，基站相关功能的程序存储在存储器中，由处理器执行程序以实现基站的相关功能。可选的，该基站功能芯片也能够读取该芯片外部的存储器以实现基站的相关功能。
应理解，图9示例的基站的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的基站结构的可能。
根据本申请实施例提供的方法，本申请实施例还提供一种通信系统，其包括前述的网络设备和一个或多于一个终端设备。
应理解，本申请实施例中，该处理器可以为中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同 步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术 做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM)、随机存取存储器(RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (26)

  1. 一种传输方法，其特征在于，包括：
    源接入网设备通过其与目标接入网设备的第二PDCP实体之间的数据隧道，向所述目标接入网设备发送所述源接入网设备中的第一分组数据汇聚协议PDCP实体中的第一部分数据包，所述第一部分数据包为第一协议数据单元PDU会话中的第一服务质量QoS流的数据包，所述第一PDU会话包括至少一个QoS流，所述至少一个QoS流与至少一个PDCP实体对应，所述至少一个QoS流包括所述第一QoS流，所述至少一个PDCP实体包括所述第一PDCP实体，所述第一PDCP实体与所述第一QoS流对应；
    所述源接入网设备向所述目标接入网设备发送第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的所述第一部分数据包已经发送结束。
  2. 如权利要求1所述的方法，其特征在于，所述第一指示信息包括所述第一部分数据包中的所有数据包所携带的PDCP序列号中的最大PDCP序列号；或者
    所述第一指示信息包括下一个待分配的PDCP序列号；或者
    所述第一指示信息为所述第一PDCP实体生成的结束标识包。
  3. 如权利要求1或2所述的方法，其特征在于，在所述源接入网设备向所述目标接入网设备发送所述第一PDCP实体的第一部分数据包之前，所述方法还包括：
    所述源接入网设备确定所述源接入网设备中的第一服务数据适配协议SDAP实体结束向所述第一PDCP实体发送所述第一QoS流的数据包，其中，所述第一SDAP实体向所述第一PDCP实体发送的所述第一QoS流的数据包为所述第一部分数据包，所述第一SDAP实体与所述第一PDU会话对应。
  4. 如权利要求3所述的方法，其特征在于，所述第二指示信息为所述第一SDAP实体根据从核心网用户面设备接收到的结束标识包发送的。
  5. 一种传输方法，其特征在于，包括：
    目标接入网设备通过其第二分组数据汇聚协议PDCP实体与源接入网设备的第一PDCP实体之间的数据隧道，接收所述第一PDCP实体发送的第一部分数据包，所述第一部分数据包为第一协议数据单元PDU会话中的第一服务质量QoS流的数据包，所述第一PDU会话包括至少一个QoS流，所述至少一个QoS流与至少一个PDCP实体对应，所述至少一个QoS流包括所述第一QoS流，所述至少一个PDCP实体包括所述第一PDCP实体，所述第一PDCP实体与所述第一QoS流对应，所述第二PDCP实体与所述第一QoS流对应；
    所述目标接入网设备接收所述源接入网设备发送的第一指示信息，所述第一指示信息用于指示所述第一PDCP实体已发送完所述第一部分数据包。
  6. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    所述目标接入网设备根据所述第一指示信息，在确定已向终端发送完所述第一部分数据包中的所有数据包后，向终端发送从所述目标接入网设备的第二SDAP实体接收的数据包。
  7. 如权利要求5或6所述的方法，其特征在于，所述第一指示信息包括所述第一部分数据包中的所有数据包所携带的PDCP序列号中的最大PDCP序列号；或者
    所述第一指示信息包括下一个待分配的PDCP序列号；或者
    所述第一指示信息为所述第一PDCP实体生成的结束标识包。
  8. 一种传输方法，其特征在于，包括：
    如果确定终端不再向源接入网设备发送第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，所述源接入网设备生成触发信息；
    所述源接入网设备向目标接入网设备发送所述触发信息，所述触发信息用于指示所述目标接入网设备向核心网用户面设备发送由所述终端发送至所述目标接入网设备的所述至少一个QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一DRB的标识，所述第一DRB与所述至少一个QoS流对应。
  9. 一种传输方法，其特征在于，包括：
    目标接入网设备接收源接入网设备发送的触发信息，所述触发信息用于指示所述目标接入网设备向核心网用户面设备发送由所述终端发送至所述目标接入网设备的第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一数据无线承载DRB的标识，所述第一DRB与所述至少一个QoS流对应；
    所述目标接入网设备根据所述触发信息，向所述核心网用户面设备发送由所述终端发送至所述目标接入网设备的所述至少一个QoS流的数据包。
  10. 如权利要求8或9所述的方法，其特征在于，所述触发信息为结束标识包，或所述触发信息为接入网设备间的消息。
  11. 一种传输方法，其特征在于，包括：
    如果源接入网设备确定终端接收到所述源接入网设备发送的第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，所述源接入网设备生成触发信息；
    所述源接入网设备向目标接入网设备发送所述触发信息，所述触发信息用于指示所述目标接入网设备开始向所述终端发送所述目标接入网设备从核心网用户面设备接收的所述至少一个QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一数据无线承载DRB的标识，所述第一DRB与所述至少一个QoS流对应。
  12. 一种传输方法，其特征在于，包括：
    目标接入网设备接收源接入网设备发送的触发信息，所述触发信息用于指示所述目标接入网设备开始向终端发送所述目标接入网设备从核心网用户面设备接收的第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一数据无线承载DRB的标识，所述第一DRB与所述至少一个QoS流对应；
    所述目标接入网设备根据所述触发信息，向所述终端发送从所述核心网用户面设备接收的所述至少一个QoS流的数据包。
  13. 如权利要求11或12所述的方法，其特征在于，所述触发信息为结束标识包，或所述触发信息为接入网设备间的控制面消息。
  14. 一种数据传输装置，其特征在于，包括：
    通信单元，用于通过其与目标接入网设备的第二PDCP实体之间的数据隧道，向所述目标接入网设备发送所述装置的第一分组数据汇聚协议PDCP实体中的第一部分数据包，所述第一部分数据包为第一协议数据单元PDU会话中的第一服务质量QoS流的数据包，所述第一PDU会话包括至少一个QoS流，所述至少一个QoS流与至少一个PDCP实体对应，所述至少一个QoS流包括所述第一QoS流，所述至少一个PDCP实体包括所述第一PDCP实体，所述第一PDCP实体与所述第一QoS流对应；
    所述通信单元还用于向所述目标接入网设备发送第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的所述第一部分数据包已经发送结束。
  15. 如权利要求14所述的装置，其特征在于，所述第一指示信息包括所述第一部分数据包中的所有数据包所携带的PDCP序列号中的最大PDCP序列号；或者
    所述第一指示信息包括下一个待分配的PDCP序列号；或者
    所述第一指示信息为所述第一PDCP实体生成的结束标识包。
  16. 如权利要求14或15所述的装置，其特征在于，所述装置还包括：
    确定单元，用于确定所述装置中的第一服务数据适配协议SDAP实体结束向所述第一PDCP实体发送所述第一QoS流的数据包，其中，所述第一SDAP实体向所述第一PDCP实体发送的所述第一QoS流的数据包为所述第一部分数据包，所述第一SDAP实体与所述第一PDU会话对应。
  17. 如权利要求16所述的装置，其特征在于，所述第二指示信息为所述第一SDAP实体根据从核心网用户面设备接收到的结束标识包发送的。
  18. 一种数据传输装置，其特征在于，包括：
    通信单元，用于通过其第二分组数据汇聚协议PDCP实体与源接入网设备的第一PDCP实体之间的数据隧道，接收所述第一PDCP实体发送的第一部分数据包，所述第一部分数据包为第一协议数据单元PDU会话中的第一服务质量QoS流的数据包，所述第一PDU会话包括至少一个QoS流，所述至少一个QoS流与至少一个PDCP实体对应，所述至少一个QoS流包括所述第一QoS流，所述至少一个PDCP实体包括所述第一PDCP实体，所述第一PDCP实体与所述第一QoS流对应，所述第二PDCP实体与所述第一QoS流对应；
    所述通信单元还用于接收所述源接入网设备发送的第一指示信息，所述第一指示信息用于指示所述第一PDCP实体已发送完所述第一部分数据包。
  19. 如权利要求18所述的装置，其特征在于，所述通信单元还用于根据所述第一指示信息，在确定已向终端发送完所述第一部分数据包中的所有数据包后，向终端发送从所述装置的第二SDAP实体接收的数据包。
  20. 如权利要求18或19所述的装置，其特征在于，所述第一指示信息包括所述第一部分数据包中的所有数据包所携带的PDCP序列号中的最大PDCP序列号；或者
    所述第一指示信息包括下一个待分配的PDCP序列号；或者
    所述第一指示信息为所述第一PDCP实体生成的结束标识包。
  21. 一种数据传输装置，其特征在于，包括：
    处理单元，用于如果确定终端不再向所述装置发送第一协议数据单元PDU会话中 的至少一个服务质量QoS流的数据包，则生成触发信息；
    通信单元，用于向目标接入网设备发送所述触发信息，所述触发信息用于指示所述目标接入网设备向核心网用户面设备发送由所述终端发送至所述目标接入网设备的所述至少一个QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一DRB的标识，所述第一DRB与所述至少一个QoS流对应。
  22. 一种数据传输装置，其特征在于，包括：
    通信单元，用于接收源接入网设备发送的触发信息，所述触发信息用于指示所述装置向核心网用户面设备发送由所述终端发送至所述装置的第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一数据无线承载DRB的标识，所述第一DRB与所述至少一个QoS流对应；
    所述通信单元还用于根据所述触发信息，向所述核心网用户面设备发送由所述终端发送至所述装置的所述至少一个QoS流的数据包。
  23. 如权利要求21或22所述的装置，其特征在于，所述触发信息为结束标识包，或所述触发信息为接入网设备间的消息。
  24. 一种数据传输装置，其特征在于，包括：
    处理单元，用于如果确定终端接收到所述源接入网设备发送的第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，则生成触发信息；
    通信单元，用于向目标接入网设备发送所述触发信息，所述触发信息用于指示所述目标接入网设备开始向所述终端发送所述目标接入网设备从核心网用户面设备接收的所述至少一个QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一数据无线承载DRB的标识，所述第一DRB与所述至少一个QoS流对应。
  25. 一种数据传输装置，其特征在于，包括：
    通信单元，用于接收源接入网设备发送的触发信息，所述触发信息用于指示所述装置开始向终端发送所述装置从核心网用户面设备接收的第一协议数据单元PDU会话中的至少一个服务质量QoS流的数据包，所述触发信息包括所述至少一个QoS流的标识和所述第一PDU会话的标识，或者，所述触发信息包括所述至少一个QoS流的标识和第一数据无线承载DRB的标识，所述第一DRB与所述至少一个QoS流对应；
    所述通信单元还用于根据所述触发信息，向所述终端发送从所述核心网用户面设备接收的所述至少一个QoS流的数据包。
  26. 如权利要求24或25所述的装置，其特征在于，所述触发信息为结束标识包，或所述触发信息为接入网设备间的控制面消息。
PCT/CN2018/099967 2017-08-11 2018-08-10 数据传输方法和数据传输装置 WO2019029703A1 (zh)

Priority Applications (9)

Application Number Priority Date Filing Date Title
KR1020207006996A KR102345399B1 (ko) 2017-08-11 2018-08-10 데이터 전송 방법 및 데이터 전송 장치
ES18843032T ES2911651T3 (es) 2017-08-11 2018-08-10 Procedimientos de transmisión de datos, aparatos de transmisión de datos y medios legibles por ordenador no transitorios
CA3072717A CA3072717C (en) 2017-08-11 2018-08-10 Data transmission method and data transmission apparatus
JP2020507598A JP6892554B2 (ja) 2017-08-11 2018-08-10 データ伝送方法およびデータ伝送装置
BR112020002788-0A BR112020002788A2 (pt) 2017-08-11 2018-08-10 método de transmissão de dados e aparelho de transmissão de dados
EP22157982.4A EP4096299A1 (en) 2017-08-11 2018-08-10 Data transmission method and data transmission apparatus
EP18843032.6A EP3598838B1 (en) 2017-08-11 2018-08-10 Data transmission methods, data transmission apparatuses and non-transitory computer readable medium
US16/563,302 US11109263B2 (en) 2017-08-11 2019-09-06 Data transmission method and data transmission apparatus
US17/459,667 US11917450B2 (en) 2017-08-11 2021-08-27 Data transmission method and data transmission apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710687846.0A CN109392025B (zh) 2017-08-11 2017-08-11 数据传输方法和数据传输装置
CN201710687846.0 2017-08-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/563,302 Continuation US11109263B2 (en) 2017-08-11 2019-09-06 Data transmission method and data transmission apparatus

Publications (1)

Publication Number Publication Date
WO2019029703A1 true WO2019029703A1 (zh) 2019-02-14

Family

ID=64322625

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/099967 WO2019029703A1 (zh) 2017-08-11 2018-08-10 数据传输方法和数据传输装置

Country Status (9)

Country Link
US (2) US11109263B2 (zh)
EP (2) EP4096299A1 (zh)
JP (2) JP6892554B2 (zh)
KR (1) KR102345399B1 (zh)
CN (3) CN108882334B (zh)
BR (1) BR112020002788A2 (zh)
CA (1) CA3072717C (zh)
ES (1) ES2911651T3 (zh)
WO (1) WO2019029703A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024093059A1 (en) * 2023-02-24 2024-05-10 Lenovo (Beijing) Limited Network devices, terminal device and methods for communications

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110226344B (zh) * 2017-03-17 2020-11-17 华为技术有限公司 一种发送结束标记的方法及相关设备
US11304108B2 (en) * 2018-02-20 2022-04-12 Nokia Technologies Oy Edge service continuity
CN113630827B (zh) * 2018-04-04 2023-12-29 北京三星通信技术研究有限公司 支持切换的方法及对应的基站和网络节点
US11310707B2 (en) * 2018-04-13 2022-04-19 Qualcomm Incorporated Facilitating quality of service flow remapping utilizing a service data adaptation protocol layer
CN111225423B (zh) * 2018-11-27 2022-04-01 中国移动通信有限公司研究院 一种数据前转的方法和设备
CN111479335A (zh) * 2019-01-24 2020-07-31 华为技术有限公司 一种数据传输的方法和通信装置
CN112105065B (zh) * 2019-06-17 2022-04-05 华为技术有限公司 通信方法和通信装置
CN110445712B (zh) * 2019-07-17 2022-02-25 新华三技术有限公司成都分公司 数据转发方法、装置及系统
CN111083690A (zh) * 2019-08-16 2020-04-28 中兴通讯股份有限公司 用户面功能实体信息的上报方法及装置
CN110536332B (zh) * 2019-08-16 2023-07-21 中兴通讯股份有限公司 冗余会话、无线承载建立方法、装置、节点、终端及介质
CN112449384B (zh) * 2019-08-31 2022-05-24 华为技术有限公司 数据处理方法、装置和系统
CN112469024B (zh) * 2019-09-09 2022-03-29 华为技术有限公司 一种会话管理的方法及装置
JP7402887B2 (ja) * 2019-10-04 2023-12-21 株式会社Ｎｔｔドコモ ユーザプレーン装置、通信システム、及びバッファ方法
EP4061055A4 (en) * 2019-12-11 2022-11-30 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE
WO2021093206A1 (en) * 2020-02-13 2021-05-20 Zte Corporation Methods and devices for data transmission based on switching quality of service flow
CN113316202A (zh) * 2020-02-27 2021-08-27 华为技术有限公司 一种切换方法及通信装置
CN111586780B (zh) * 2020-05-12 2021-03-30 京信通信系统（中国）有限公司 基站切换装置、方法、基站、源基站和存储介质
CN113766580B (zh) * 2020-06-03 2022-06-21 大唐移动通信设备有限公司 4g与5g网络互切换的实现方法、装置及存储介质
CN113784400B (zh) * 2020-06-10 2022-12-13 中国移动通信有限公司研究院 切换方法、处理方法、装置、网络设备及核心网设备
CN113938968B (zh) * 2020-07-14 2023-01-31 维沃移动通信有限公司 数据传输方法、装置及设备
CN114501339B (zh) * 2020-10-23 2022-11-08 大唐移动通信设备有限公司 多媒体广播业务的处理方法、装置及存储介质
CN112867054A (zh) * 2021-02-07 2021-05-28 中国移动通信有限公司研究院 测试方法、装置、测试系统及存储介质
CN114189566B (zh) * 2022-02-14 2022-07-19 阿里巴巴达摩院(杭州)科技有限公司 无线通信方法、网关、设备及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101365239A (zh) * 2007-08-09 2009-02-11 华为技术有限公司 数据转发的方法、演进基站和长期演进网络
CN103888222A (zh) * 2014-03-21 2014-06-25 电信科学技术研究院 一种数据包处理方法及装置
CN106941733A (zh) * 2016-01-04 2017-07-11 中兴通讯股份有限公司 双连接中实现重配置的方法、主服务基站及辅服务基站

Family Cites Families (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100788889B1 (ko) * 2005-06-22 2007-12-27 한국전자통신연구원 서비스 품질을 협상하는 장치 및 방법
CN101132609B (zh) * 2006-08-22 2010-04-21 华为技术有限公司 一种切换过程中转发数据的方法及系统
CN101272315B (zh) * 2007-03-23 2011-04-06 华为技术有限公司 分组数据包传输方法、系统和网络设备
CN101572929B (zh) * 2008-04-29 2011-08-31 电信科学技术研究院 一种在切换过程中传送消息的方法、装置及系统
KR101552303B1 (ko) * 2008-10-30 2015-09-11 삼성전자주식회사 통신 시스템 및 그의 데이터 전송 방법
CN101699898B (zh) * 2009-11-03 2012-11-28 中兴通讯股份有限公司 一种分组业务域传输分组数据的方法和系统
CN102045802A (zh) * 2010-12-22 2011-05-04 华为技术有限公司 Sgw改变的切换过程中的数据发送方法、pgw及基站
US8861475B2 (en) * 2011-05-19 2014-10-14 Telefonaktiebolaget L M Ericsson (Publ) Inter-RAT handover control using sequence numbers
US10200908B2 (en) * 2011-06-16 2019-02-05 Nokia Solutions And Networks Oy Methods, apparatus, a system, and a related computer program product for activation and deactivation of bearers
US8706118B2 (en) * 2011-09-07 2014-04-22 Telefonaktiebolaget L M Ericsson (Publ) 3G LTE intra-EUTRAN handover control using empty GRE packets
EP2815603B1 (en) * 2012-02-17 2019-09-25 Interdigital Patent Holdings, Inc. Hierarchical traffic differentiation to handle congestion and/or manage user quality of experience
US9538563B2 (en) * 2014-10-13 2017-01-03 At&T Intellectual Property I, L.P. System and methods for managing a user data path
KR102319836B1 (ko) * 2014-12-16 2021-11-01 삼성전자 주식회사 무선 통신 시스템에서 기지국과 단말 간 통신 방법을 결정하는 방법 및 장치
WO2016095115A1 (en) * 2014-12-17 2016-06-23 Qualcomm Incorporated Handover using dual active connections
KR102029849B1 (ko) * 2015-01-27 2019-10-08 노키아 솔루션스 앤드 네트웍스 오와이 트래픽 흐름 모니터링
CN104994551A (zh) * 2015-07-14 2015-10-21 武汉邮电科学研究院 一种高速移动场景下lte系统的切换配置方法
CN107027136B (zh) 2016-02-01 2020-11-20 中兴通讯股份有限公司 数据处理的方法及装置
US10524173B2 (en) * 2016-02-24 2019-12-31 Cisco Technology, Inc. System and method to facilitate sharing bearer information in a network environment
GB2551485A (en) * 2016-06-14 2017-12-27 Fujitsu Ltd Providing service data flow description
WO2017222344A1 (en) * 2016-06-23 2017-12-28 Samsung Electronics Co., Ltd. Data transmission supporting method and apparatus
CN109565729B (zh) * 2016-08-08 2021-02-02 诺基亚技术有限公司 用于5g与lte之间的移动性的端标记处理
US10419985B2 (en) * 2016-10-25 2019-09-17 Lg Electronics Inc. Method of supporting access network handover operation of user equipment in wireless communication system and apparatus for the same
GB201621072D0 (en) * 2016-12-12 2017-01-25 Samsung Electronics Co Ltd NR QOS handling
CN106851856B (zh) 2016-12-23 2019-04-09 电信科学技术研究院有限公司 一种基于移动中继的无线通信建立方法及网络设备
KR20180080427A (ko) * 2017-01-03 2018-07-12 한국전자통신연구원 대용량 이동 백홀을 구성하는 방법, 대용량 이동 백홀을 위한 전송 방법 및 장치, 그리고 대용량 이동 백홀을 위한 핸드오버 방법 및 장치
CN116669112A (zh) * 2017-01-26 2023-08-29 中兴通讯股份有限公司 通信方法、网络设备、计算机存储介质
CN110226344B (zh) * 2017-03-17 2020-11-17 华为技术有限公司 一种发送结束标记的方法及相关设备
US20190074894A1 (en) * 2017-09-05 2019-03-07 Hughes Network Systems, Llc Convergent architectures for multi-orbit satellite communications
CN113630827B (zh) * 2018-04-04 2023-12-29 北京三星通信技术研究有限公司 支持切换的方法及对应的基站和网络节点
EP4354912A3 (en) * 2019-08-22 2024-04-24 Ofinno, LLC Policy control for multiple accesses

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101365239A (zh) * 2007-08-09 2009-02-11 华为技术有限公司 数据转发的方法、演进基站和长期演进网络
CN103888222A (zh) * 2014-03-21 2014-06-25 电信科学技术研究院 一种数据包处理方法及装置
CN106941733A (zh) * 2016-01-04 2017-07-11 中兴通讯股份有限公司 双连接中实现重配置的方法、主服务基站及辅服务基站

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Data Forwarding For QoS Flow Remapping During Mobility", R3-171810, 3GPP TSG-RAN WG3 #96, 19 May 2017 (2017-05-19), XP051276591 *
HUAWEI: "Data forwarding with QoS flow relocation", R3-171072, 3GPP TSG-RAN3 MEETING #95BIS, 7 April 2017 (2017-04-07), XP051245796 *
ZTE .: "Further discussion on QoS impact on mobility", R3-170562, 3GPP TSG-RAN WG3 #95, 17 February 2017 (2017-02-17), XP051213143 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024093059A1 (en) * 2023-02-24 2024-05-10 Lenovo (Beijing) Limited Network devices, terminal device and methods for communications

Also Published As

Publication number Publication date
US20190394669A1 (en) 2019-12-26
JP7164670B2 (ja) 2022-11-01
US11109263B2 (en) 2021-08-31
ES2911651T3 (es) 2022-05-20
JP2021132411A (ja) 2021-09-09
EP4096299A1 (en) 2022-11-30
CN108882334A (zh) 2018-11-23
JP2020530705A (ja) 2020-10-22
US11917450B2 (en) 2024-02-27
EP3598838B1 (en) 2022-03-09
BR112020002788A2 (pt) 2020-07-28
EP3598838A1 (en) 2020-01-22
CA3072717C (en) 2023-09-26
US20220060931A1 (en) 2022-02-24
KR102345399B1 (ko) 2021-12-31
CA3072717A1 (en) 2019-02-14
CN109392025B (zh) 2023-09-29
CN109392025A (zh) 2019-02-26
CN117412337A (zh) 2024-01-16
CN108882334B (zh) 2019-11-05
KR20200037381A (ko) 2020-04-08
JP6892554B2 (ja) 2021-06-23
EP3598838A4 (en) 2020-06-03

Similar Documents

Publication Publication Date Title
JP7164670B2 (ja) データ伝送方法およびデータ伝送装置
JP7318779B2 (ja) マスター無線アクセスネットワークノード、ａｍｆ、及びこれらの方法
US11212714B2 (en) Method for supporting handover and corresponding base station and network node
US11206591B2 (en) Method and equipment for handover
WO2017054538A1 (zh) 建立辅助信令链路的方法及其装置、基站及终端
US10772146B2 (en) Multi-connectivity communication method, device, and terminal
WO2013075602A1 (zh) 实现载波聚合的方法、基站和用户设备
EP3664507B1 (en) Communication methods for a master base station and a terminal
WO2021088074A1 (zh) Iab节点双连接建立的方法和通信装置
EP4171122A1 (en) Method for iab network communication, and related device
CN114503669A (zh) 在无线通信系统中支持有条件切换的装置和方法
WO2020164620A1 (zh) 一种终端信息的通信处理方法和相关设备
WO2019184682A1 (zh) 通信方法和通信装置
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2023010367A1 (zh) 终端设备的转移方法、装置和系统
WO2024055172A1 (en) Traffic transferring in user equipment-to-network relay scenario
CN117202402A (zh) 交互方法和相关设备
WO2016101468A1 (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: 18843032

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018843032

Country of ref document: EP

Effective date: 20191018

ENP Entry into the national phase

Ref document number: 2020507598

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 3072717

Country of ref document: CA

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

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20207006996

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 112020002788

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200210