WO2018228311A1 - 数据分流方法和装置 - Google Patents

数据分流方法和装置 Download PDF

Info

Publication number
WO2018228311A1
WO2018228311A1 PCT/CN2018/090592 CN2018090592W WO2018228311A1 WO 2018228311 A1 WO2018228311 A1 WO 2018228311A1 CN 2018090592 W CN2018090592 W CN 2018090592W WO 2018228311 A1 WO2018228311 A1 WO 2018228311A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
data
tunnel
qos flow
message
Prior art date
Application number
PCT/CN2018/090592
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 华为技术有限公司
Publication of WO2018228311A1 publication Critical patent/WO2018228311A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • 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
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface

Definitions

  • the present application relates to the field of communications, and in particular, to a data offloading method and apparatus.
  • QoS Quality of Service
  • EPS Evolved Packet System
  • the primary base station needs to notify the core network of the identifier of the EPS bearer corresponding to the migrated data, so that the core network will be migrated.
  • the data carried by the EPS bearer is distributed to the secondary base station.
  • QoS management of data transmission is performed based on QoS flow, and data having the same QoS requirement is transmitted as one QoS flow.
  • the primary base station decides to migrate multiple QoS flows to the secondary base station, the primary base station needs to send the identifier of each QoS flow to the core network.
  • the number of QoS flows is much larger than the number of EPS bearers.
  • the primary base station and the secondary base station need to perform frequent QoS flow migration, the primary base station needs to frequently notify the core network of the migrated QoS flow identifier, which will result in the base station and the core.
  • the signaling overhead between the networks is large, and more tunnels for data transmission need to be established between the core network and the secondary base station, which increases the core network traffic.
  • the embodiment of the present application provides a data offloading method and apparatus, which are used to solve the problem that the first network device needs to frequently notify the core network to be migrated QoS flow when performing QoS flow offloading, so that the first network device and the core network device are The inter-signaling overhead is increased, and more data tunnels need to be established between the core network device and the second network device, which increases the problem of the core network traffic.
  • an embodiment of the present application provides a data offloading method, including:
  • the first network device sends the QoS flow to be offloaded to the second network device by using a data tunnel between the first network device and the second network device.
  • the QoS flow to be offloaded is sent by the first network device to the second network device, and then the QoS flow to be offloaded is sent by the second network device to the terminal device, so that the traffic to be offloaded
  • the QoS flow is offloaded from the first network device to the second network device to the terminal device instead of being directly offloaded from the core network device to the second network device, and the first network device does not need to report the QoS flow to be shunted to the core network device.
  • the identification reduces the signaling overhead between the first network device and the core network device.
  • the QoS flow of the data tunneling offload is not required between the second network device and the core network device, and the interaction between the second network device and the core network device is reduced.
  • the data offloading method further includes:
  • the first network device sends the QoS flow to be offloaded to the second network device by using a data tunnel between the first network device and the second network device, including:
  • the first network device sends the QoS flow to be offloaded to the second network device through the data tunnel corresponding to the packet data unit session to which the QoS flow to be offloaded belongs.
  • the data offloading method further includes:
  • the first network device establishes a public data tunnel between the first network device and the second network device;
  • the first network device sends the QoS flow to be offloaded to the second network device by using a data tunnel between the first network device and the second network device, including:
  • the first network device sends the QoS flow to be offloaded to the second network device through the public data tunnel.
  • the data offloading method further includes:
  • the first network device establishes a data tunnel corresponding to the DRB between the first network device and the second network device according to the data radio bearer DRB corresponding to the QoS flow to be offloaded;
  • the first network device sends the QoS flow to be offloaded to the second network device by using a data tunnel between the first network device and the second network device, including:
  • the first network device sends the QoS flow to be offloaded to the second network device through the data tunnel corresponding to the DRB corresponding to the QoS flow to be offloaded.
  • the method before the first network device establishes a data tunnel corresponding to the DRB between the first network device and the second network device according to the DRB corresponding to the QoS flow to be offloaded, the method further includes:
  • the first network device determines that there is no data tunnel corresponding to the QoS flow to be offloaded.
  • a method of establishing a data tunnel based on different granularities between the first network device and the second network device is provided, so that the establishment of the data tunnel is more flexible.
  • the first network device establishes a data tunnel corresponding to the packet data unit session between the first network device and the second network device, including:
  • the first network device sends a first message to the second network device, where the first message includes an identifier of the packet data unit session and first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the bearer header of the QoS flow of the QoS flow to be offloaded in the data tunnel carries the identifier of the QoS flow to be offloaded.
  • the first network device and the second network device establish a data tunnel based on the PDU session, and each PDU session corresponds to one data tunnel, so that when the first network device forwards data to the second network device, according to The PDU session to which the QoS flow to be offloaded belongs determines the data tunnel.
  • the second network device can determine the PDU session to which the QoS flow belongs according to the data tunnel, and does not need to specifically receive the identifier of the PDU session to which the QoS flow belongs, and perform PDU session division on the received QoS flow.
  • the operation of the second network device is simplified.
  • the first network device establishes a public data tunnel between the first network device and the second network device, including:
  • the first network device sends a first message to the second network device, where the first message includes the first tunnel endpoint information of the public data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the public data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and a public data tunnel.
  • an encapsulation header of a data packet carried in the data tunnel and carrying the QoS flow to be offloaded carries an identifier of the QoS flow to be offloaded and the packet data unit session Logo.
  • the above-mentioned possible design provides a method for establishing a public data tunnel between the first network device and the second network device when the first network device has a QoS flow that needs to be offloaded, so that the first network device goes to the second network.
  • the device forwards data, all QoS flows are transmitted through the public data tunnel.
  • the first network device establishes a data tunnel corresponding to the DRB between the first network device and the second network device according to the DRB corresponding to the QoS flow to be offloaded, including:
  • the first network device sends a first message to the second network device, where the first message includes the identifier of the DRB corresponding to the QoS flow to be offloaded and the first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the above-mentioned possible design provides a method, when the first network device determines that there is a QoS flow that needs to be offloaded, establishing a data tunnel between the first network device and the second network device based on the DRB, so that the first network device is to the second network.
  • each QoS flow is transmitted through the data tunnel indicated by the DRB corresponding to the QoS flow.
  • the second network device can directly determine the DRB corresponding to the QoS flow according to the data tunnel adopted by the received QoS flow, thereby further simplifying the operation of the second network device.
  • the data offloading method further includes:
  • the first network device sends a third message to the second network device, where the third message includes QoS information of the QoS flow to be offloaded, and a mapping relationship between the QoS flow to be offloaded and the DRB;
  • the first network device receives a fourth message from the second network device, and the fourth message includes a QoS flow that the second network device can accept.
  • the third message further includes the DRB corresponding to the QoS flow to be offloaded. Establish instructions.
  • the first network device sends a mapping relationship between the QoS flow and the DRB to the second network device, so that the second network device determines the DRB corresponding to the QoS flow, so that the data packet of the QoS flow is implemented in the second network.
  • the transmission between the device and the terminal device configures the mapping relationship between the QoS flow and the DRB through the first network device, and implements the routing configuration of the QoS flow data packet to the DRB in the second network device.
  • the first network device implements a unified mapping of QoS flow to DRB mapping, which reduces the workload of the second network device.
  • the data offloading method further includes:
  • the first network device sends a third message to the second network device, where the third message includes QoS information of the QoS flow to be offloaded;
  • the first network device receives a fourth message from the second network device, and the fourth message includes a QoS flow that the second network device can accept.
  • the first network device sends the QoS information of the QoS flow to the second network device, so that the second network device determines the DRB corresponding to the QoS flow according to the QoS information of the QoS flow, thereby implementing the QoS flow data packet.
  • the mapping relationship between the QoS flow and the DRB is configured by the second network device, and the routing configuration of the QoS flow data packet to the DRB in the second network device is implemented.
  • the second network device implements a unified mapping of QoS flow to DRB mapping, which reduces the workload of the first network device.
  • the data offloading method further includes:
  • the first network device sends a third message to the second network device, where the third message includes QoS information of the DRB;
  • the first network device receives a fourth message from the second network device, and the fourth message includes a DRB that the second network device can accept.
  • an embodiment of the present application provides a data offloading method.
  • the beneficial effects of the methods provided by the various possible designs of the second aspect described below can be seen in the beneficial effects of the various possible designs of the first aspect described above.
  • the data offloading method comprises:
  • the second network device receives the QoS flow from the first network device by using a data tunnel between the first network device and the second network device;
  • the second network device determines the DRB corresponding to the QoS flow, and sends the QoS flow to the terminal device by using the DRB corresponding to the QoS flow.
  • the data offloading method further includes:
  • the second network device receives the first message from the first network device, where the first message includes the identifier of the packet data unit session to which the QoS flow belongs and the first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the second network device sends a second message to the first network device, where the second message includes second tunnel endpoint information that identifies the corresponding data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the encapsulation header of the data packet carrying the QoS flow carries the identifier of the QoS flow; the second network device determines the DRB corresponding to the QoS flow, including:
  • the second network device determines the DRB corresponding to the QoS flow according to the identifier of the packet data unit session and the identifier of the QoS flow corresponding to the data tunnel.
  • the data offloading method further includes:
  • the second network device receives the first message from the first network device, where the first message includes the first tunnel endpoint information of the public data tunnel;
  • the second network device sends a second message to the first network device, where the second message includes second tunnel endpoint information of the public data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the public data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and a public data tunnel.
  • the encapsulation header of the data packet carrying the QoS flow carries the identifier of the QoS flow and the identifier of the packet data unit session to which the QoS flow belongs.
  • the second network device determines the DRB corresponding to the QoS flow, including:
  • the data offloading method further includes:
  • the second network device receives the first message from the first network device, where the first message includes the identifier of the DRB corresponding to the QoS flow and the first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the second network device sends a second message to the first network device, where the second message includes second tunnel endpoint information that identifies the corresponding data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the second network device determines the DRB corresponding to the QoS flow, including:
  • the second network device determines the DRB corresponding to the QoS flow according to the DRB corresponding to the data tunnel.
  • the data offloading method further includes:
  • the second network device determines whether the QoS flow can be accepted according to the QoS information of the QoS flow and the mapping relationship between the QoS flow and the DRB;
  • the third message further includes the establishment indication information of the DRB corresponding to the QoS flow.
  • the data offloading method further includes:
  • the second network device receives a third message from the first network device, where the third message includes QoS information of the QoS flow;
  • the second network device determines whether the QoS flow can be accepted according to the QoS information of the QoS flow
  • the data offloading method further includes:
  • the second network device receives a third message from the first network device, where the third message includes QoS information of the DRB;
  • the second network device determines whether the DRB can be accepted according to the QoS information of the DRB;
  • the embodiment of the present application provides a data offloading method, including:
  • the second network device sends each QoS flow to the first network device through a data tunnel corresponding to each QoS flow.
  • the embodiment of the present application provides a data offloading device as a first network device, and the data offloading device has a function of implementing the data offloading method.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software herein includes one or more modules corresponding to the functions described above.
  • the data offloading apparatus includes:
  • a splitting module configured to determine a QoS flow to be offloaded in the packet data unit session
  • a sending module configured to send the QoS flow to be offloaded to the second data offloading device by using a data tunnel between the first data offloading device and the second data splitting device.
  • the data splitting device further includes:
  • a data tunnel establishing module configured to establish a data tunnel corresponding to the packet data unit session between the first data offloading device and the second data offloading device;
  • the sending module is specifically configured to send the QoS flow to be offloaded to the second data offloading device by using the data tunnel corresponding to the packet data unit session to which the QoS flow to be offloaded belongs.
  • the data splitting device further includes:
  • a data tunnel establishing module configured to establish a public data tunnel between the first data offloading device and the second data splitting device
  • the sending module is specifically configured to send the QoS flow to be offloaded to the second data offloading device through the public data tunnel.
  • the data splitting device further includes:
  • a data tunnel establishing module configured to establish a data tunnel corresponding to the DRB between the first data offloading device and the second data offloading device according to the data radio bearer DRB corresponding to the QoS flow to be offloaded;
  • the data tunnel establishing module is further configured to determine that there is no data tunnel corresponding to the QoS flow to be offloaded.
  • the data tunnel establishment module is specifically used,
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a data tunnel of the second data offload device The tunnel endpoint identifier on the second data offloading device side.
  • the encapsulation header of the data packet carried in the data tunnel and carrying the QoS flow to be offloaded carries an identifier of the QoS flow to be offloaded.
  • the data tunnel establishment module is specifically used,
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the public data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a common of the second data offload device Tunnel end identifier of the data tunnel on the side of the second data offloading device
  • the encapsulation header of the data packet carried in the data tunnel and carrying the QoS flow to be offloaded carries the identifier of the QoS flow and the identifier of the packet data unit session to which the QoS flow belongs.
  • the data tunnel establishment module is specifically used,
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a data tunnel of the second data offload device The tunnel endpoint identifier on the second data offloading device side.
  • the sending module is further configured to send a third message to the second data offloading device, where the third message includes QoS information of the QoS flow to be offloaded, and a mapping relationship between the QoS flow to be offloaded and the DRB;
  • the receiving module is further configured to receive a fourth message from the second data offloading device, where the fourth message includes a QoS flow that the second data offloading device can accept.
  • the third message further includes the establishment indication information of the DRB corresponding to the QoS flow to be offloaded.
  • the sending module is further configured to send a third message to the second data offloading device, where the third message includes QoS information of the QoS flow to be offloaded;
  • the receiving module is further configured to receive a fourth message from the second data offloading device, where the fourth message includes a QoS flow that the second data offloading device can accept.
  • the sending module is further configured to send a third message to the second data offloading device, where the third message includes the QoS information of the DRB;
  • the receiving module is further configured to receive a fourth message from the second data offloading device, where the fourth message includes a DRB that the second data offloading device can accept.
  • the embodiment of the present application provides a data offloading device, which is a second network device, and the data offloading device has a function of implementing the data offloading method.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software herein includes one or more modules corresponding to the functions described above.
  • the data offloading apparatus includes:
  • a receiving module configured to receive a QoS flow from the first data offloading device by using a data tunnel between the first data offloading device and the second data splitting device;
  • the sending module is configured to determine a DRB corresponding to the QoS flow, and send the QoS flow to the terminal device by using the corresponding DRB.
  • the receiving module is further configured to receive, by the first data offloading device, the first message, where the first message includes an identifier of the packet data unit session to which the QoS flow belongs and a first tunnel that identifies the corresponding data tunnel Endpoint information;
  • the sending module is further configured to send a second message to the first data offloading device, where the second message includes second tunnel endpoint information that identifies the corresponding data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a data tunnel of the second data offload device The tunnel endpoint identifier on the second data offloading device side.
  • the encapsulation header of the data packet carrying the QoS flow carries the identifier of the QoS flow; the sending module is specifically configured to determine according to the identifier of the packet data unit session and the identifier of the QoS flow corresponding to the data tunnel. DRB corresponding to QoS flow.
  • the receiving module is further configured to receive, by the first data offloading device, the first message, where the first message includes the first tunnel endpoint information of the public data tunnel;
  • the sending module is further configured to send a second message to the first data offloading device, where the second message includes second tunnel endpoint information of the public data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the public data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a common of the second data offload device The data tunnel is identified at the tunnel endpoint on the second data offloading device side.
  • the encapsulation header of the data packet carrying the QoS flow carries the identifier of the QoS flow and the identifier of the packet data unit session to which the QoS flow belongs; the sending module is specifically configured to: according to the identifier of the packet data unit session And the identifier of the QoS flow, and determine the DRB corresponding to the QoS flow.
  • the receiving module is further configured to: receive the first message from the first data offloading device, where the first message includes the identifier of the DRB corresponding to the QoS flow and the first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the sending module is further configured to send a second message to the first data offloading device, where the second message includes second tunnel endpoint information that identifies the corresponding data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a data tunnel of the second data offload device The tunnel endpoint identifier on the second data offloading device side.
  • the sending module is specifically configured to determine the DRB corresponding to the QoS flow according to the DRB corresponding to the data tunnel.
  • the receiving module is further configured to receive a third message from the first data offloading device, where the third message includes QoS information of the QoS flow, and a mapping relationship between the QoS flow and the DRB;
  • the sending module is further configured to determine whether the QoS flow can be accepted according to the QoS information of the QoS flow and the mapping relationship between the QoS flow and the DRB;
  • the fifth message is sent to the first data offloading device, where the fifth message is used to indicate that the QoS flow admission fails.
  • the third message further includes the establishment indication information of the DRB corresponding to the QoS flow.
  • the receiving module is further configured to receive a third message from the first data offloading device, where the third message includes QoS information of the QoS flow;
  • the sending module is further configured to determine whether the QoS flow can be accepted according to the QoS information of the QoS flow;
  • the fifth message is sent to the first data offloading device, where the fifth message is used to indicate that the QoS flow admission fails.
  • the receiving module is further configured to: receive a third message from the first data offloading device, where the third message includes QoS information of the DRB;
  • the sending module is further configured to determine whether the DRB can be accepted according to the QoS information of the DRB.
  • the fifth message is sent to the first data offloading device, where the fifth message is used to indicate that the DRB admission fails.
  • the embodiment of the present application provides a data offloading device, as a second network device, the data offloading device has a function of implementing the data offloading method.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software herein includes one or more modules corresponding to the functions described above.
  • the data offloading apparatus includes:
  • a receiving module configured to receive at least one QoS flow in a packet data unit session from the terminal device
  • a sending module configured to send each QoS flow to the first data offloading device by using a data tunnel corresponding to each QoS flow.
  • the embodiment of the present application provides a network device as a first network device, where the network device has a function of implementing the foregoing data offloading method.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software herein includes one or more modules corresponding to the functions described above.
  • the first network device includes:
  • a processor configured to determine a QoS flow to be offloaded in the packet data unit session
  • a transmitter configured to send the QoS flow to be offloaded to the second network device by using a data tunnel between the first network device and the second network device.
  • the first network device further includes: a processor
  • the processor is configured to establish a data tunnel corresponding to the packet data unit session between the first network device and the second network device;
  • the transmitter is specifically configured to send the QoS flow to be offloaded to the second network device by using a data tunnel corresponding to the packet data unit session to which the QoS flow to be offloaded belongs.
  • the first network device further includes: a processor
  • the processor is configured to establish a public data tunnel between the first network device and the second network device;
  • the transmitter is specifically configured to send the QoS flow to be offloaded to the second network device by using a public data tunnel.
  • the first network device further includes: a processor
  • the processor is configured to establish, according to the data radio bearer DRB corresponding to the QoS flow to be offloaded, a data tunnel corresponding to the DRB between the first network device and the second network device;
  • the transmitter is specifically configured to send the QoS flow to be offloaded to the second network device by using the data tunnel corresponding to the DRB corresponding to the QoS flow to be offloaded.
  • the processor is further configured to determine that there is no data tunnel corresponding to the QoS flow to be offloaded.
  • the processor is specifically used,
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the encapsulation header of the data packet carried in the data tunnel and carrying the QoS flow to be offloaded carries an identifier of the QoS flow to be offloaded.
  • the processor is specifically used,
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the public data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and a public data tunnel. Tunnel endpoint identifier on the second network device side
  • the encapsulation header of the data packet carried in the data tunnel and carrying the QoS flow to be offloaded carries the identifier of the QoS flow to be offloaded and the identifier of the packet data unit session to which the QoS flow belongs.
  • the processor is specifically used,
  • the first message includes the identifier of the DRB corresponding to the QoS flow to be offloaded and the first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the transmitter is further configured to send a third message to the second network device, where the third message includes QoS information of the QoS flow to be offloaded, and a mapping relationship between the QoS flow to be offloaded and the DRB;
  • the receiver is further configured to receive a fourth message from the second network device, where the fourth message includes a QoS flow that the second network device can accept.
  • the third message further includes an establishment indication of the DRB corresponding to the QoS flow to be offloaded. information.
  • the transmitter is further configured to send a third message to the second network device, where the third message includes QoS information of the QoS flow to be offloaded;
  • the receiver is further configured to receive a fourth message from the second network device, where the fourth message includes a QoS flow that the second network device can receive.
  • the transmitter is further configured to send a third message to the second network device, where the third message includes QoS information of the DRB;
  • the receiver is further configured to receive a fourth message from the second network device, where the fourth message includes a DRB that the second network device can accept.
  • the embodiment of the present application provides a network device as a second network device, where the network device has a function of implementing the foregoing data offloading method.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software herein includes one or more modules corresponding to the functions described above.
  • the second network device includes:
  • a receiver configured to receive a QoS flow from the first network device by using a data tunnel between the first network device and the second network device;
  • the transmitter is configured to determine the DRB corresponding to the QoS flow, and send the QoS flow to the terminal device through the corresponding DRB.
  • the receiver is further configured to receive the first message from the first network device, where the first message includes an identifier of the packet data unit session to which the QoS flow belongs and a first tunnel endpoint of the data tunnel corresponding to the identifier information;
  • the transmitter is further configured to send a second message to the first network device, where the second message includes second tunnel endpoint information that identifies the corresponding data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the encapsulation header of the data packet carrying the QoS flow carries the identifier of the QoS flow; the transmitter is specifically configured to determine according to the identifier of the packet data unit session and the identifier of the QoS flow corresponding to the data tunnel. DRB corresponding to QoS flow.
  • the receiver is further configured to receive the first message from the first network device, where the first message includes the first tunnel endpoint information of the public data tunnel;
  • the transmitter is further configured to send a second message to the first network device, where the second message includes second tunnel endpoint information of the public data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the public data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and a public data tunnel.
  • the encapsulation header of the data packet carrying the QoS flow carries the identifier of the QoS flow and the identifier of the packet data unit session to which the QoS flow belongs; the transmitter is specifically configured to identify the session according to the packet data unit And the identifier of the QoS flow, and determine the DRB corresponding to the QoS flow.
  • the receiver is further configured to: receive, by the first network device, a first message, where the first message includes an identifier of the DRB corresponding to the QoS flow and the first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the transmitter is further configured to send a second message to the first network device, where the second message includes second tunnel endpoint information that identifies the corresponding data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the transmitter is specifically configured to determine the DRB corresponding to the QoS flow according to the DRB corresponding to the data tunnel.
  • the receiver is further configured to receive a third message from the first network device, where the third message includes QoS information of the QoS flow, and a mapping relationship between the QoS flow and the DRB;
  • the transmitter is further configured to determine whether the QoS flow can be accepted according to the QoS information of the QoS flow and the mapping relationship between the QoS flow and the DRB;
  • the third message further includes the establishment indication information of the DRB corresponding to the QoS flow.
  • the receiver is further configured to receive a third message from the first network device, where the third message includes QoS information of the QoS flow;
  • the transmitter is further configured to determine whether the QoS flow can be accepted according to the QoS information of the QoS flow;
  • the receiver is further configured to receive a third message from the first network device, where the third message includes QoS information of the DRB;
  • the transmitter is further configured to determine whether the DRB can be accepted according to the QoS information of the DRB.
  • the embodiment of the present application provides a network device as a second network device, where the network device has a function of implementing the foregoing data offloading method.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software herein includes one or more modules corresponding to the functions described above.
  • the second network device includes:
  • a receiver configured to receive at least one QoS flow in a packet data unit session from the terminal device
  • the transmitter is configured to send each QoS flow to the first network device by using a data tunnel corresponding to each QoS flow.
  • the embodiment of the present application provides a computer storage medium, configured to store computer software instructions used by the first network device, and includes a program designed to execute the foregoing first aspect.
  • the embodiment of the present application provides a computer storage medium, configured to store computer software instructions used by the second network device, and includes a program designed to execute the second aspect.
  • the embodiment of the present application provides a computer storage medium, configured to store computer software instructions used by the second network device, and includes a program designed to execute the foregoing third aspect.
  • the embodiment of the present application provides a computer program product, comprising instructions, when executed by a computer, causing a computer to perform the functions performed by the first network device in the method in the foregoing first aspect .
  • the embodiment of the present application provides a computer program product, comprising instructions, when executed by a computer, causing a computer to perform the functions performed by the second network device in the method in the second aspect above .
  • the embodiment of the present application provides a computer program product, comprising instructions, when executed by a computer, the computer causing the computer to perform the function performed by the second network device in the method in the foregoing third aspect .
  • the embodiment of the present application further provides a chip system, where the chip system includes a processor, configured to support a network device to implement the functions involved in the foregoing first aspect, for example, generating or processing the foregoing method. Data and / or information.
  • the chip system further includes a memory for storing program instructions and data necessary for the first network device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the embodiment of the present application further provides a chip system, where the chip system includes a processor, configured to support a network device device to implement the functions involved in the foregoing second aspect, for example, generating or processing the foregoing method. Data and/or information involved.
  • the chip system further includes a memory for storing necessary program instructions and data for the second network device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the embodiment of the present application further provides a chip system, where the chip system includes a processor, configured to support a network device to implement the functions involved in the foregoing third aspect, for example, generating or processing the foregoing method. Data and / or information.
  • the chip system further includes a memory for storing necessary program instructions and data for the second network device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the embodiment of the present application further provides a communication system, including a core network device and a first network device in each possible design in the foregoing seventh aspect.
  • the communication system further comprises a second network device of each of the possible designs in the above eighth aspect or the second network device of the above ninth aspect.
  • FIG. 1 shows a network architecture that may be applicable to an embodiment of the present application
  • Embodiment 1 of a data offloading method according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a signaling flow of Embodiment 2 of a data offloading method according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram 1 of a data tunnel structure provided by an embodiment of the present application.
  • FIG. 5 is a second schematic diagram of a data tunnel structure according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram 3 of a data tunnel structure according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of a signaling flow of Embodiment 3 of a data offloading method according to an embodiment of the present disclosure
  • FIG. 8 is a schematic diagram of a signaling flow of Embodiment 4 of a data offloading method according to an embodiment of the present disclosure
  • FIG. 9 is a schematic flowchart of Embodiment 5 of a data offloading method according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of Embodiment 1 of a data offloading apparatus according to an embodiment of the present disclosure
  • FIG. 11 is a schematic structural diagram of Embodiment 2 of a data offloading apparatus according to an embodiment of the present disclosure
  • FIG. 12 is a schematic structural diagram of Embodiment 3 of a data offloading apparatus according to an embodiment of the present disclosure
  • FIG. 13 is a schematic structural diagram of Embodiment 1 of a network device according to an embodiment of the present disclosure
  • FIG. 14 is a schematic structural diagram of Embodiment 2 of a network device according to an embodiment of the present disclosure.
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation of the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • FIG. 1 shows a network architecture that may be applicable to an embodiment of the present application.
  • the network architecture provided by this embodiment includes a core network device 10, a first network device 20, a second network device 30, and at least one terminal device 40.
  • the core network device 10 is a device that provides services for the terminal device.
  • the main functions include: mobility management function, QoS control function, session management function of the terminal device, subscription information management function, and data forwarding.
  • the core network equipment includes the core network control plane equipment, for example, the Next Generation Control Plane (NG-CP), including the Non-Access Stratum (NAS) security management, and the access layer (Access Stratum, AS).
  • NG-CP Next Generation Control Plane
  • NAS Non-Access Stratum
  • AS Access Stratum
  • the functions of security control, mobility management, terminal access authentication, registration area management, session management, terminal address allocation, and management, and the core network control plane device may be composed of one or more network elements.
  • the core network device also includes a core network user plane device, for example, a Next Generation User Plane (NG-UP), an external node including a packet data unit session (PDU session) interconnection, packet routing, and At least one of the functions of forwarding, transmission processing (QoS execution), anchoring of intra-system/inter-system handover, etc.
  • the core network user plane device may be composed of one or more network elements.
  • the PDU session refers to a link between the terminal device and the external data network to provide a PDU link service.
  • An exemplary external data network may refer to an internet network other than the core network.
  • the PDU includes multiple types of data units, and may include, for example, Internet Protocol (IP) packets, unstructured PDUs, Ethernet frames, and the like.
  • IP Internet Protocol
  • the first network device 20 and the second network device 30 are devices that access the terminal device to the wireless network, and may be an evolved base station in an Evolution Long Term Evolution (E-LTE).
  • B referred to as eNB or eNodeB
  • eNB or eNodeB a relay station or an access point
  • gNB next-generation access network device
  • FIG. 1 is a schematic diagram showing a possible schematic diagram.
  • the first network device 20 and the second network device 30 are both base stations as an example.
  • the terminal device may include two medium access control (MAC) entities, where the first network device includes one MAC entity, and the second network device A MAC entity is included, and the first MAC entity of the two MAC entities of the terminal device corresponds to the one MAC entity of the first network device, and the second MAC entity of the two MAC entities of the terminal device corresponds to the second network.
  • MAC medium access control
  • one terminal device can simultaneously access the first network device 20 and the second network device 30 to receive data or transmit data.
  • the terminal device 40 may be a wireless terminal or a wired terminal, the wireless terminal may be a device that provides voice and/or other service data connectivity to the user, a handheld device with wireless connectivity, or other processing device connected to the wireless modem. .
  • the wireless terminal can communicate with one or more core network devices via a Radio Access Network (RAN), and the wireless terminal can be a mobile terminal, such as a mobile phone (or "cellular" phone) and has a mobile terminal.
  • RAN Radio Access Network
  • the computers for example, can be portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices that exchange language and/or data with the wireless access network.
  • the wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a remote terminal.
  • the access terminal, the user terminal (User Terminal), and the user agent (User Agent) are not limited herein.
  • FIG. 1 schematically depicts a possible schematic diagram in which the terminal device is a mobile phone as an example.
  • the core network device 10 transmits data to the first network device 20, and the first network device 20 forwards the received data to the terminal device 40 based on the EPS bearer.
  • the first network device may offload data carried by the part of the EPS bearer to the second network device 30, The data is forwarded by the second network device 30 to the terminal device 40 based on the EPS bearer.
  • the first network device 20 needs to inform the core network device 10 of the offloaded EPS bearers, so that the core network device 10 directly transmits the data based on the offloaded EPS bearers to the second network device 30.
  • the QoS management of the data transmission is performed based on the QoS flow, and the first network device 20 needs to notify the core network device 10 of the identifier of the offloaded QoS flow, but the number of QoS flows is far more than the number of EPS bearers.
  • the first network device 20 needs to frequently notify the core network device 10 of the QoS flow to be migrated, and the identifier is large, which will result in a large signaling overhead between the first network device 20 and the core network device 10.
  • a larger number of data tunnels need to be established between the core network device 10 and the first network device 20, and the traffic volume of the core network device 10 is increased.
  • the present application provides a data offloading method, and the data shunting method provided by the present application is described in detail below using a detailed embodiment.
  • FIG. 2 is a schematic diagram of a signaling flow of Embodiment 1 of a data offloading method according to an embodiment of the present disclosure.
  • the execution body of the method is a first network device and a second network device.
  • the first network device sends the offloaded QoS flow to the second network device by using the data tunnel
  • the second network device sends the offloaded QoS flow to the terminal, thereby preventing the core network device from directly sending the offloaded QoS flow to the first network device.
  • the network device does not need to send the offloaded QoS flow identifier to the core network device, which reduces the signaling overhead between the first network device and the core network device, and avoids establishing a data tunnel between the core network device and the second network device.
  • the data offloading method provided by the embodiment of the present application includes the following steps:
  • the first network device receives, from the core network device, at least one QoS flow in the PDU session of the terminal device, where the first network device determines the QoS flow to be offloaded in the at least one QoS flow in the received PDU session.
  • the first network device receives one or more PDU sessions sent by the core network device, and one PDU session includes at least one QoS flow.
  • the PDU session in the following embodiment of the present application includes at least one QoS flow.
  • the data packet may be carried on at least one QoS flow during the establishment of a PDU session.
  • the two QoS flows received by the first network device may belong to two PDU sessions respectively.
  • the transmission/reception QoS flow in the following embodiments of the present application actually refers to sending/receiving data packets carried on the QoS flow.
  • the sending/receiving PDU session in the following embodiments of the present application actually refers to a data packet carried on the QoS flow during the establishment of the sending/receiving PDU session.
  • data with the same QoS requirements is carried on the same QoS flow.
  • the first network device receives at least one PDU session sent by the core network device.
  • Each PDU session is distinguished by a PDU session identifier, and each QoS flow can be distinguished by using a QoS flow identifier.
  • data for different services has different QoS quality requirements. For example, a bandwidth-guaranteed service needs to ensure sufficient bandwidth and delay-guaranteed services are sensitive to delays and need to ensure a short delay.
  • the first network device needs to forward the received QoS flow to the terminal device.
  • the terminal device may be located far away, and the number of data radio bearers (DRB) channels between the first network device and the terminal device is limited.
  • the first network device may determine the QoS flow to be offloaded in the received QoS flow, and offload the QoS flow to be offloaded to the second network device, and send the QoS flow to the terminal device by the second network device.
  • the QoS flow to be offloaded is a QoS flow transmitted from the first network device to the second network device, and then transmitted by the second network device to the terminal device.
  • the first network sends a QoS flow to be offloaded to the second network device.
  • the first network device sends the QoS flow to be offloaded to the second network device by using a data tunnel between the first network device and the second network device.
  • a data tunnel is established between the first network device and the second network device, and the data tunnel is a channel for transmitting data of the terminal device.
  • a public data tunnel or a plurality of data tunnels of the terminal device may be established between the first network device and the second network device.
  • the first network device and the second network device may also establish respective data tunnels for each PDU session.
  • establishing a data tunnel between the first network device and the second network device may also refer to other granularities. For example, a data tunnel can be established for each QoS flow to be offloaded, and a data tunnel can be established for each DRB where the QoS flow to be offloaded is located.
  • the second network device sends the QoS flow to be offloaded to the terminal device.
  • the second network device receives the QoS flow to be offloaded by the first network device, determines the DRB corresponding to the QoS flow to be offloaded, and sends the QoS flow to be offloaded to the terminal device through the DRB corresponding to the QoS flow to be offloaded.
  • the first network device notifies the second network device to establish a DRB between the second network device and the at least one terminal device, where Multiple QoS flows correspond to one DRB.
  • the first network device may also notify the second network device to establish the DRB.
  • the mapping relationship between the QoS flow and the DRB may be established by the first network device and notified to the second network device.
  • the mapping relationship between the QoS flow and the DRB may also be determined by the second network device.
  • the DRB between the second network device and the terminal device may also be established by the second network device.
  • the terminal device can receive at least one PDU session from the core network, and each PDU session includes at least one QoS flow, and the QoS flow to be offloaded is at least one.
  • each PDU session includes at least one QoS flow
  • the QoS flow to be offloaded is at least one.
  • one QoS flow to be offloaded in one PDU session is taken as an example.
  • the same processing can be performed according to this PDU session.
  • the QoS flows to be offloaded in the same or different PDU sessions are processed separately and processed in the same manner.
  • Various embodiments are illustrated with one of at least one QoS flow to be offloaded, and other QoS flows may be processed the same according to this QoS flow.
  • the embodiment of the present application provides a data offloading method, where the first network device determines the QoS flow to be offloaded in the PDU session, and sends the QoS flow to be offloaded to the second network device through the data tunnel, and the second network device divides the to be offloaded.
  • the QoS flow is sent to the terminal device through the DRB corresponding to the QoS flow to be offloaded.
  • the QoS flow to be offloaded is sent from the first network device to the second network device, and the QoS flow to be offloaded is sent by the second network device to the terminal device, so that the QoS flow to be offloaded is offloaded from the first network device to the first
  • the second network device is not directly distributed to the second network device from the core network device, and the first network device does not need to report the identifier of the QoS flow to be offloaded to the core network device, thereby reducing the first network device and the core network. Signaling overhead between devices.
  • the QoS flow of the data tunneling offload is not required between the second network device and the core network device, and the interaction between the second network device and the core network device is reduced.
  • the data offloading method provided by the embodiment of the present application further includes a data tunnel establishing process, in consideration of the fact that the first network device needs to send the QoS flow in the data tunnel.
  • a method for establishing a data tunnel between a first network device and a second network device will be described in detail below with reference to specific embodiments.
  • the first network device uses a PDU session as a granularity to establish a respective data tunnel for each PDU session.
  • the data offloading method provided in this embodiment further includes:
  • the first network device establishes a data tunnel corresponding to the PDU session between the first network device and the second network device according to the PDU session.
  • the S203 first network device in the foregoing embodiment shown in FIG. 2 sends the QoS flow to be offloaded to the second network device by using the data tunnel between the first network device and the second network device, and specifically includes:
  • the first network device sends the QoS flow to be offloaded to the second network device by using a data tunnel corresponding to the PDU session.
  • the first network device establishes a data tunnel for each PDU session when establishing a data tunnel according to the PDU session.
  • the QoS flows belonging to the same PDU session are sent by the first network device to the second network device by using the same data tunnel.
  • the first network device Before sending the QoS flow to be offloaded, the first network device first determines the PDU session to which the QoS flow belongs, and uses the data tunnel corresponding to the PDU session as the data tunnel used in the QoS flow transmission.
  • FIG. 3 is a schematic diagram of a signaling flow of Embodiment 2 of a data offloading method according to an embodiment of the present disclosure. The process of establishing a data tunnel is described in detail in this embodiment. As shown in FIG. 3, the data offloading method provided in this embodiment includes:
  • the first network device sends a first message to the second network device, where the first message includes an identifier of the PDU session and first tunnel endpoint information of the data tunnel corresponding to the PDU session identifier.
  • the first network device sends a first message to the second network device, where the first message includes an identifier (Identifier) of the PDU session to which the QoS flow to be off belongs, a PDU session ID, and a first corresponding to the PDU session ID.
  • Tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier (TE ID) of the data tunnel on the first network device side.
  • TE ID tunnel endpoint identifier
  • the identifier of the terminal device is also included in the first message.
  • the first network device receives the second message from the second network device, where the second message includes the second tunnel endpoint information of the data tunnel corresponding to the identifier of the PDU session.
  • the second network device after receiving the first message, sends a second message to the first network device if the data tunnel is determined to be established according to the load condition of the second network device.
  • the first network device receives the second message sent by the second network device, where the second message includes the PDU session ID of the PDU session to which the QoS flow to be off belongs and the second tunnel endpoint information corresponding to the PDU session ID, and the second tunnel endpoint information
  • the second message further includes an identifier of the terminal device.
  • the indication information that is not established is sent to the first network device, so that the first network device re-schedules the offloading of the QoS flow.
  • FIG. 4 is a schematic diagram 1 of a data tunnel structure provided by an embodiment of the present application.
  • the first network device establishes two data tunnels, which respectively correspond to one PDU session.
  • the first network device determines, according to the PDU session to which the QoS flow to be offloaded belongs, the data tunnel carrying the PDU session to which the QoS flow belongs, and sends the QoS flow to the second network device through the data tunnel.
  • the QoS flow ID is carried in the encapsulation header of the data packet of the QoS flow to be offloaded.
  • the QoS flow ID is carried in the extension header of the General Packet Radio Service Tunneling Protocol User Plane (GTPU).
  • GTPU General Packet Radio Service Tunneling Protocol User Plane
  • the second network device determines, according to the ID of the PDU session corresponding to the data tunnel, the PDU session to which the QoS flow belongs. Further, the QoS reflection characteristic indication may also be carried in the encapsulation header of the data packet.
  • the QoS reflection characteristic indicates that the terminal device can obtain the identifier of the uplink QoS flow and the packet filter according to the IP5 tuple information and the QoS flow ID of the downlink data packet, and the terminal device generates the uplink QoS flow.
  • the QoS reflection characteristic indication may be that the first network device receives from the core network user plane device.
  • the IP 5-tuple refers to the source address, destination address, source port number, and destination port number of the IP address of the service data flow.
  • the transport protocol can be used to form a service flow template by using specific values of several elements in the 5-tuple group (Traffic Flow Template). , TFT).
  • a data tunnel may be established between a Service Data Adaptation Protocol (SDAP) entity corresponding to a certain PDU session of the first network device and a SDAP entity corresponding to the same PDU session of the second network device. Therefore, the SDAP entity of the first network device can perform data offloading in the PDU session, and the second network device SDAP entity that receives the offloaded data can perform QoS flow to the DRB route.
  • SDAP refers to the protocol layer above the Packet Data Convergence Protocol (PDCP) in the air interface protocol stack, and is responsible for routing the QoS flow to the DRB.
  • PDCP Packet Data Convergence Protocol
  • the SDAP entity (entity) and the PDU session are in one-to-one correspondence. .
  • the first network device before the first network device sends the first message, it is determined that the data tunnel corresponding to the PDU session does not exist. And if the first network device determines that the data tunnel corresponding to the PDU session already exists, sending the identifier of the QoS flow to be offloaded to the second network device, and receiving the admission information or the rejection information fed back by the second network device.
  • the first network device and the second network device establish a data tunnel based on the PDU session, and one PDU session corresponds to one data tunnel, so that when the first network device forwards data to the second network device,
  • the data tunnel is determined according to the PDU session to which the QoS flow to be offloaded belongs.
  • the second network device can determine, according to the data tunnel, the PDU session to which the received QoS flow belongs, without specifically receiving the identifier of the PDU session to which the QoS flow belongs, and receiving the QoS flow.
  • PDU session partitioning simplifies the operation of the second network device.
  • the first network device establishes a public data tunnel between the first network device and the second network device, and all QoS flows to be offloaded are sent to the second through the public data tunnel.
  • Internet equipment Compared with the first possible data tunnel establishment mode, a data tunnel is established for each PDU session. This method can reduce the maintenance cost of the data tunnel by establishing only one common data tunnel.
  • the data offloading method provided in this embodiment further includes:
  • the first network device establishes a common data tunnel between the first network device and the second network device.
  • the S203 first network device in the foregoing embodiment shown in FIG. 2 sends the QoS flow to be offloaded to the second network device by using the data tunnel between the first network device and the second network device, and specifically includes:
  • the first network device sends the QoS flow to be offloaded to the second network device through the public data tunnel.
  • the first network device directly establishes a public data tunnel of the terminal device between the first network device and the second network device, and is used to transmit all QoS flows to be offloaded by the terminal device.
  • a plurality of PDU sessions of one terminal device may be sent by the first network device to the second network device through the public data tunnel.
  • Different terminal devices correspond to different public data tunnels.
  • the data tunnel maintenance process is simplified by establishing a common data tunnel between the first network device and the second network device to reduce the establishment cost of the data tunnel.
  • the process of establishing a public data tunnel provided by this embodiment is described in detail below.
  • the difference between this embodiment and the embodiment shown in FIG. 3 is that the PDU session ID does not need to be carried in the first message and the second message.
  • the data offloading method provided in this embodiment includes:
  • the first network device sends a first message to the second network device, where the first message includes the first tunnel endpoint information of the public data tunnel.
  • the first network device sends a first message to the second network device, where the first message includes the first tunnel endpoint information.
  • the first tunnel endpoint information includes a transport layer address of the first network device and a TE ID of the public data tunnel on the first network device side.
  • the identifier of the terminal device is also included in the first message.
  • the first network device receives the second message from the second network device, where the second message includes the second tunnel endpoint information of the public data tunnel.
  • the second network device after receiving the first message, sends a second message to the first network device if it decides to establish a public data tunnel according to the load condition of the second network device.
  • the first network device receives the second message sent by the second network device, where the second message includes the second tunnel endpoint information, where the second tunnel endpoint information includes the transport layer address of the second network device and the public data tunnel is on the second network device side.
  • TE ID After the first network device and the second network device acquire the first tunnel endpoint information and the second tunnel endpoint information, the establishment of the data tunnel is completed.
  • the second message further includes an identifier of the terminal device.
  • the second network device determines that the data tunnel is not established, sending the indication information that is not established to the first network device, so that the first network device re-plans the offloading of the QoS flow.
  • FIG. 5 is a schematic diagram 2 of a data tunnel structure provided by an embodiment of the present application.
  • the first network device establishes a public data tunnel for transmitting data packets of all PDU sessions.
  • the first network device sends the QoS flow to be offloaded to the second network device through the public data tunnel.
  • the QoS flow ID and the PDU session ID are carried in the encapsulation header of the data packet transmitted in the data tunnel and carried to the QoS flow to be offloaded.
  • the QoS flow ID and the PDU session ID are carried in the extension header of the GTPU.
  • the QoS reflection characteristic indication may also be carried in the encapsulation header of the data packet.
  • a public data tunnel is established between the first network device and the second network device, so that the first network device is in the second
  • all QoS flows are transmitted through the public data tunnel.
  • the first network device establishes a respective data tunnel for each DRB with a DRB granularity.
  • the establishment of the data tunnel in this embodiment adopts a finer granularity, so that the second network device can determine the DRB and the QoS flow corresponding to the QoS flow according to the data tunnel. ID of the PDU session.
  • the data offloading method provided in this embodiment further includes:
  • the first network device establishes a data tunnel corresponding to the DRB between the first network device and the second network device according to the DRB corresponding to the QoS flow to be offloaded.
  • the S203 first network device in the foregoing embodiment shown in FIG. 2 sends the QoS flow to be offloaded to the second network device by using the data tunnel between the first network device and the second network device, and specifically includes:
  • the first network device sends the QoS flow to be offloaded to the second network device by using the data tunnel corresponding to the DRB corresponding to the QoS flow to be offloaded.
  • each QoS flow is sent by the first network device to the second network device by using a different data tunnel according to the corresponding DRB.
  • the first network device establishes a data tunnel for each DRB when establishing a data tunnel according to the DRB.
  • the first network device in this manner adopts a finer granularity, when the first network device has a QoS flow that needs to be offloaded.
  • the DRB corresponding to the QoS flow and the ID of the PDU session to which the received QoS flow belongs further simplify the operation of the second network device.
  • the process of establishing a data tunnel based on the DRB provided in this embodiment is described in detail below.
  • the difference between this embodiment and the foregoing two methods for establishing a data tunnel is that the DRB ID is carried in the first message and the second message.
  • the data offloading method provided in this embodiment includes:
  • the first network device sends the first message to the second network device, where the first message includes the identifier of the DRB corresponding to the QoS flow to be offloaded, and the first tunnel endpoint information of the data tunnel corresponding to the DRB identifier.
  • the first tunnel endpoint information includes a transport layer address of the first network device and a TE ID of the data tunnel on the first network device side.
  • the identifier of the DRB may be a DRB ID, and other identifiers corresponding to the DRB may be used instead of the DRB ID, such as a Radio Access Bearer (RAB) ID.
  • the first message may further include a QoS requirement corresponding to the DRB, where the QoS requirement may be represented by a QoS parameter.
  • the identifier of the terminal device is also included in the first message.
  • the first message further includes an identifier of the PDU session to which the QoS flow to be offloaded belongs, and further, a Service Data Adaptation Protocol (SDAP) entity identifier (entity ID) may be used instead of the PDU session. ID.
  • SDAP Service Data Adaptation Protocol
  • the data offloading method provided in this embodiment further includes:
  • the first network device determines that there is no data tunnel corresponding to the QoS flow to be offloaded.
  • the first network device determines that there is no DRB corresponding to the QoS flow to be offloaded according to the mapping relationship between the established QoS flow and the DRB, and therefore there is no data tunnel corresponding to the DRB to be offloaded.
  • the network device determines the DRB corresponding to the QoS flow to be offloaded, and sends the DRB corresponding to the QoS flow to be offloaded to the second network device, so that the second network device establishes a corresponding data tunnel for the DRB to be offloaded.
  • the QoS flow to be offloaded is not required to be sent to the second network device.
  • the first message is to establish a data tunnel corresponding to the DRB.
  • the first network device receives the second message from the second network device, where the second message includes the second tunnel endpoint information of the data tunnel corresponding to the identifier of the DRB.
  • the second network device sends a second message to the first network device if the data tunnel is determined to be established according to the load condition of the second network device.
  • the first network device receives the second message sent by the second network device, where the second message includes the DRB ID corresponding to the QoS flow ID to be offloaded and the second tunnel endpoint information of the data tunnel corresponding to the DRB ID, where the second tunnel endpoint information includes The transport layer address of the second network device and the TE ID of the data tunnel on the second network device side.
  • the identifier of the DRB may be a DRB ID, and other identifiers corresponding to the DRB may be used instead of the DRB ID, such as a Radio Access Bearer (RAB) ID.
  • the second message further includes an identifier of the terminal device.
  • the first network device when the second network device determines that the data tunnel is not established, the first network device sends the indication information that is not established, so that the first network device re-processes the offloading of the offloaded QoS flow.
  • FIG. 6 is a schematic diagram 3 of a data tunnel structure provided by an embodiment of the present application.
  • the first network device establishes eight data tunnels, one for each DRB.
  • the first network device determines, according to the identifier of the QoS flow to be offloaded, and the mapping relationship between the QoS flow and the DRB, the data tunnel carrying the QoS flow, and passes the QoS flow through the data tunnel. Send to the second network device.
  • the first network device may further determine a data tunnel carrying the QoS flow according to the QoS flow ID of the QoS flow to be offloaded and the associated PDU session ID, and the mapping relationship between the QoS flow and the DRB.
  • the QoS flow ID may be carried in the encapsulation header of the data packet that is transmitted to the QoS flow to be offloaded in the data tunnel, for example, in a General Packet Radio Service Tunneling Protocol User Plane (General Packet Radio Service Tunneling Protocol User Plane, The extension header of the GTPU) carries the QoS flow ID.
  • the QoS reflection characteristic indication may also be carried in the encapsulation header of the data packet. The QoS reflection characteristic indicates that the terminal device can obtain the identifier of the uplink QoS flow and the packet filter according to the IP5 tuple information and the QoS flow ID of the downlink data packet, and the terminal device generates the uplink QoS flow.
  • the QoS reflection characteristic indication may be that the first network device receives from the core network user plane device.
  • the IP 5-tuple refers to the source address, destination address, source port number, and destination port number of the IP address of the service data flow.
  • the transport protocol can be used to form a service flow template by using specific values of several elements in the 5-tuple group (Traffic Flow Template). , TFT).
  • the data tunnel is established based on the DRB between the first network device and the second network device, so that the first network device is in the second
  • each QoS flow is transmitted through the data tunnel indicated by the DRB corresponding to the QoS flow.
  • the second network device can directly determine the DRB corresponding to the QoS flow according to the data tunnel adopted by the received QoS flow, thereby further simplifying the operation of the second network device.
  • each data tunnel can be used for transmitting uplink and downlink data at the same time, and each data tunnel can also be composed of two sub-data tunnels with different transmission directions.
  • the first network device when performing downlink data transmission, is responsible for offloading the PDU session to different SDAP entities. Further, the SDAP entity (corresponding to a session) in the first network device is responsible for performing the offloading of the QoS flow in the corresponding PDU session, for example, offloading part of the QoS flow to the second network device.
  • the terminal device when performing uplink data transmission, sends the QoS flow data to the first network device and the second network device according to the configuration information of the first network device or the second network device, respectively. package.
  • the configuration information includes a mapping relationship between QoS flow and DRB.
  • the second network device sends the data packet of the QoS flow received from the terminal device to the first network device by using a data tunnel between the first network device and the second network device.
  • the QoS flow ID is carried in the encapsulation header of the data packet transmitted in the DRB and the data tunnel, for example, carried in the GTPU extension header.
  • the encapsulation header of the data packet transmitted in the public data tunnel also carries the identifier of the PDU session to which it belongs, for example, the PDU session ID.
  • the first network device sends the data packet of the QoS flow received from the terminal device and the second network device to the core network user plane device. Further, the first network device sends the data packet by using a data channel established by the PDU session between the first network device and the core network device, where the data packet is transmitted in a data tunnel between the first network device and the core network device.
  • the encapsulation header of the data packet carries the QoS flow ID, for example, carried in the GTPU extension header.
  • the data offloading method provided by the embodiment of the present application further includes a DRB establishing process, in which the second network device needs to send the QoS flow to be offloaded in the DRB.
  • a DRB establishing process in which the second network device needs to send the QoS flow to be offloaded in the DRB.
  • FIG. 7 is a schematic diagram of a signaling flow of Embodiment 3 of a data offloading method according to an embodiment of the present disclosure.
  • the first message sent by the first network device includes the QoS information of the QoS flow, the mapping relationship between the DRB and the QoS flow, and the first network device instructs the second network device to perform the DRB according to the configuration.
  • the mapping of QoS flows establishes a DRB.
  • the data offloading method includes:
  • the first network device sends a third message to the second network device, where the third message includes QoS information of the QoS flow to be offloaded, and a mapping relationship between the QoS flow to be offloaded and the DRB.
  • the first network device sends a third message to the second network device, where the third message is used to indicate that the second network device establishes the DRB according to the mapping relationship carried in the third message.
  • the third message may further include a PDU session ID to which the QoS flow to be offloaded belongs.
  • the QoS flow to be offloaded may be distinguished by the QoS flow ID of each QoS flow when the QoS flow to be offloaded is included in the third message.
  • the PDU session to which the QoS flow to be offloaded belongs may be represented by a PDU session ID or a TE ID and transport layer address information corresponding to the PDU session.
  • the QoS information of the QoS flow may use a QoS flow ID to indicate a preset QoS parameter, or the QoS information includes a QoS parameter.
  • the QoS parameters include: delay, packet loss rate, priority, guaranteed rate, maximum rate, Aggregate Maximum Bit Rate (AMBR), slice level AMBR, session level AMBR, At least one of Allocation and Retention Priority (ARP) is assigned.
  • the AMBR is suitable for limiting the maximum rate of multiple non-guaranteed rate services.
  • the QoS information of the QoS flow may be sent by the core network device to the first network device, or may be part of the QoS information of the first network device according to the received QoS flow, and the first network device and the second network device.
  • the load condition is calculated.
  • the first network device may generate one of a terminal device level AMBR, a slice level AMBR or a session level AMBR for the first network device and the second network device according to the AMBR in the QoS information received from the core network or Multiple.
  • the first network device may be the terminal equipment level AMBR of the first network equipment, the AMBR of the slice level, the AMBR of the PDU session level, and the terminal equipment level AMBR of the second network equipment, the AMBR of the slice level, and the AMBR of the PDU session level.
  • One or more notifications to the second network device For example, the second network device can be notified by the third message.
  • the third message further includes a type of the DRB corresponding to the QoS flow to be offloaded, so that the second network device can determine the QoS information of the DRB that needs to be established.
  • the type of the DRB is the bearer type of the DRB, and includes a master cell group bearer (MCG bearer), a master cell group split bearer (MCG split bearer), and a second cell group bearer (Secondary).
  • MCG bearer master cell group bearer
  • MCG split bearer master cell group split bearer
  • SCG split bearer Second Cell Group Split Bearer
  • the primary cell group bearer refers to the bearer protocol stack in the primary cell group.
  • the splitting bearer of the primary cell group means that the bearer protocol stack is split at the primary base station and belongs to the primary cell group and the secondary cell group.
  • the second cell group bearer refers to the bearer protocol stack in the second cell group.
  • the splitting bearer of the second cell group means that the bearer protocol stack is split at the second base station and belongs to the primary cell group and the secondary cell group.
  • the second network device receives the third message from the first network device, where the third message includes QoS information of the QoS flow, and a mapping relationship between the QoS flow and the DRB.
  • the second network device determines whether the QoS flow can be accepted according to the QoS information of the QoS flow and the mapping relationship between the QoS flow and the DRB.
  • the second network device may determine whether the QoS flow can be accepted according to the load condition of the DRB corresponding to the QoS flow.
  • the second network device may perform rate limiting and the like according to the AMBR information included in the QoS information of the QoS flow.
  • the second network device performs routing of the QoS flow data packet to the DRB according to the mapping relationship between the QoS flow and the DRB in the received third message.
  • the QoS flow ID and the QoS reflection characteristic indication are carried in the protocol header of the air interface data packet.
  • the second network device may carry the QoS flow ID in the protocol header of the air interface data packet only when receiving the QoS reflection characteristic indication.
  • a new DRB may be allocated to the QoS flow to be offloaded.
  • the third message may further include the establishment indication information of the DRB corresponding to the QoS flow.
  • the establishing indication information of the DRB may be the configuration information of the DRB or the new DRB ID, and the second network device newly establishes the DRB according to the configuration information of the DRB or the new DRB ID.
  • the configuration information of the DRB includes, but is not limited to, a DRB ID, a PDCP protocol layer configuration, a Radio Link Control Protocol (RLC) configuration, and a logical channel (LCH) configuration.
  • the second network device determines whether the DRB can be accepted according to the load situation.
  • the second network device when the second network device is capable of accepting the QoS flow, the second network device sends a fourth message to the first network device, and the fourth message may illustratively include a QoS flow that the second network device can accept.
  • the second network device When the second network device is unable to receive the QoS flow, the second network device sends a fifth message to the first network device, where the fifth message is used to indicate that the QoS flow admission fails, and the first network device can re-assign the QoS to be offloaded.
  • Flow determines the second network device.
  • the fourth message also includes a QoS flow that cannot be accepted by the second network device, and may further include a reason that the QoS flow cannot be accepted.
  • the first network device may send the content in the first message and the third message together in the same message to the second network device.
  • the first network device sends a mapping relationship between the QoS flow and the DRB to the second network device, so that the second network device determines the DRB corresponding to the QoS flow, so that the data packet of the QoS flow is implemented in the second network device and the terminal device.
  • the transmission between the QoS flow and the DRB is configured by the first network device to implement the routing configuration of the QoS flow data packet to the DRB in the second network device.
  • the first network device implements a unified mapping of QoS flow to DRB mapping, which reduces the workload of the second network device.
  • the embodiment of the present application further proposes a second possible DRB establishment manner.
  • the second network device establishes a mapping relationship between the DRB and the QoS flow.
  • the data offloading method in this embodiment includes:
  • the first network device sends a third message to the second network device, where the third message includes QoS information of the QoS flow.
  • the first network device sends a third message to the second network device, where the third message is used to instruct the second network device to determine the DRB for the QoS flow.
  • the third message carries the identifier of the QoS flow to be offloaded, and the identifier of the QoS flow to be offloaded may indicate the QoS information of the QoS flow to be offloaded.
  • the third message may further include a PDU session ID to which the QoS flow to be offloaded belongs.
  • the second network device receives the third message from the first network device, where the third message includes QoS information of the QoS flow.
  • the second network device determines whether the QoS flow can be accepted according to the QoS information of the QoS flow.
  • the second network device determines whether to accept the QoS flow carried in the third message according to the load condition of the second network device. For example, if the DRB corresponding to the QoS flow is established, determining whether the DRB can accept the QoS flow, and if not, determining, by the second network device, whether the DRB can be established according to the load situation.
  • the second network device when the second network device can receive the QoS flow, the second network device configures a mapping relationship between the QoS flow and the DRB, and sends a fourth message to the first network device, where the fourth message may include the second The QoS flow that the network device can accept.
  • the second network device When the second network device is unable to receive the QoS flow, the second network device sends a fifth message to the first network device, where the fifth message is used to indicate that the QoS flow admission fails, and the first network device can re-assign the QoS to be offloaded.
  • Flow determines the second network device.
  • the fourth message also includes a QoS flow that cannot be accepted by the second network device, and may further include a reason that the QoS flow cannot be accepted.
  • the second network device after configuring the mapping relationship between the QoS flow and the DRB, sends the mapping relationship between the QoS flow and the DRB to the terminal device.
  • the mapping relationship between the QoS flow and the DRB may be sent to the first network device, and the mapping relationship between the QoS flow and the DRB is sent by the first network device to the terminal device.
  • the fourth message may further include configuration information of the DRB corresponding to the QoS flow.
  • the terminal device completes the establishment of the DRB according to the configuration information of the DRB and the mapping relationship between the QoS flow and the DRB.
  • the first network device may send the content in the first message and the third message together in the same message to the second network device.
  • the first network device sends the QoS information of the QoS flow to the second network device, so that the second network device determines the DRB corresponding to the QoS flow according to the QoS information of the QoS flow, so that the data packet of the QoS flow is implemented in the second network.
  • the transmission between the device and the terminal device configures the mapping relationship between the QoS flow and the DRB through the second network device, and implements the routing configuration of the QoS flow data packet to the DRB in the second network device.
  • the second network device implements a unified mapping of QoS flow to DRB mapping, which reduces the workload of the first network device.
  • FIG. 8 is a schematic diagram of a signaling flow of Embodiment 4 of a data offloading method according to an embodiment of the present disclosure.
  • the QoS flow to be offloaded in this embodiment is sent to the second network device by using the data tunnel corresponding to the DRB corresponding to the QoS flow to be offloaded, first The network device has determined the corresponding DRB for the QoS flow, so the first network device directly sends the QoS information of the DRB corresponding to each QoS flow to the second network device, so that the second network device establishes the DRB according to the second network device.
  • the data offloading method in this embodiment includes:
  • the first network device sends a third message to the second network device, where the third message includes the QoS information of the DRB corresponding to the QoS flow to be offloaded.
  • the first network device sends a third message to the second network device, where the third message includes QoS information of the DRB.
  • the first network device determines, in the existing DRB, whether the DRB can receive the QoS flow to be offloaded. If yes, there is no need to establish a DRB for the QoS flow, and the third message does not need to be sent. If it does not exist, the corresponding DRB is determined for the QoS flow to be offloaded, and a corresponding data tunnel is established between the first network device and the second network device, and the corresponding DRB is established between the second network device and the terminal device.
  • the first network device sends a third message to the second network device to establish a QoS flow to be offloaded to determine a corresponding DRB.
  • the QoS information of the DRB includes QoS parameters, and the QoS parameters include: delay, packet loss rate, priority, and the like. Further, the QoS information of the DRB may further include a guaranteed rate and a maximum rate. Further, the QoS information of the DRB may further include an Aggregate Maximum Bit Rate (AMBR), an AMBR of a slice level, an AMBR of a session level, and an Allocation and Retention Priority (ARP). AMBR is suitable for limiting the maximum rate of multiple non-guaranteed rate services.
  • AMBR Aggregate Maximum Bit Rate
  • AMBR Allocation and Retention Priority
  • the QoS information of the QoS flow corresponding to the DRB may also be used to represent the QoS information of the DRB.
  • the second network device receives the third message from the first network device, where the third message includes the QoS information of the DRB, and the second network device determines whether the DRB can be accepted according to the QoS information of the DRB.
  • the second network device determines whether to accept the DRB carried in the third message according to its own load condition.
  • the second network device when the second network device is capable of receiving the DRB, the second network device sends a fourth message to the first network device, and the fourth message may illustratively include a DRB that the second network device can accept.
  • the second network device When the second network device is unable to receive the DRB, the second network device sends a fifth message to the first network device, where the fifth message is used to indicate that the current DRB admission fails, and the first network device may re-determine the QoS flow to be offloaded.
  • the fourth message also includes a DRB that cannot be accepted by the second network device, and may further include a reason that the DRB cannot be accepted.
  • the first network device receives the QoS flow sent by the core network device, and determines the corresponding QoS flow when the QoS flow is sent from the first network device to the second network device to the terminal device.
  • the DRB of the data tunnel therefore, the QoS flow ID can no longer be carried in the QoS flow packet.
  • the first network device determines the mapping relationship between the QoS flow and the DRB, and the second network device does not perform the QoS flow to the DRB route, which reduces the workload of the second network device.
  • the mapping relationship between the QoS flow and the DRB may be sent by the first network device to the terminal device, so that the terminal device determines the DRB corresponding to the uplink QoS flow when transmitting the uplink QoS flow.
  • the second network device may send a mapping relationship between the QoS flow and the DRB to the terminal device, so that the terminal device determines the DRB corresponding to the uplink QoS flow when sending the uplink QoS flow.
  • the first network device is an LTE base station eNB
  • the second network device is a next generation base station gNB
  • the first network device and the second network device are both connected to the core network device in the fourth generation communication system
  • the SDAP protocol layer may not be configured in the second network device.
  • the identifier carried by the QoS flow in the transmission process is generated by the non-access stratum, and the identifier of the QoS flow is usually longer.
  • the QoS flow is transmitted at the access layer, and the QoS flow identifier can be identified by the access layer identifier, thereby reducing the overhead caused by the QoS flow identifier of the air interface.
  • the mapping of the QoS flow identifier between the access layer and the non-access stratum will be described in detail below.
  • the first network device generates an access layer identifier of each QoS flow according to the non-access stratum identifier of each QoS flow, where the QoS flow sent to the second network device carries the QoS flow Access layer identification.
  • the first network device after receiving the QoS flow sent by the core network device, the first network device generates an access layer identifier for each QoS flow, and stores a mapping relationship between the access layer identifier and the non-access stratum identifier.
  • the first network device sends the QoS flow carrying the access layer identifier to the second network device, and the second network device sends the QoS flow carrying the access layer identifier to the terminal device.
  • the first network device may send the mapping relationship between the access layer identifier and the non-access stratum identifier to the second network device and the terminal device.
  • the first network device generates an access layer identifier of each QoS flow according to the non-access stratum identifier of each QoS flow and the PDU session ID to which the QoS flow belongs; wherein, the QoS sent to the second network device The flow carries the access layer identifier of the QoS flow.
  • the first network device after receiving the QoS flow sent by the core network device, the first network device generates an access layer identifier for each QoS flow.
  • the access layer identifier may indicate the non-access stratum identifier of the QoS flow and the identifier of the PDU session to which the QoS flow belongs.
  • the first network device stores a mapping relationship between the access layer identifier and the non-access stratum identifier and the identifier of the PDU session to which the QoS flow belongs.
  • the first network device sends the QoS flow carrying the access layer identifier to the second network device, and the second network device sends the QoS flow carrying the access layer identifier to the terminal device.
  • the first network device may send the mapping relationship between the access layer identifier and the non-access stratum identifier and the identifier of the PDU session to which the QoS flow belongs to the second network device and the terminal device.
  • the second network device may further generate an access layer identifier of each QoS flow according to the non-access stratum identifier of each QoS flow and the PDU session ID to which the QoS flow belongs.
  • the mapping relationship between the access layer identifier of the QoS flow and the non-access stratum identifier may change, and the first network device needs to update the mapping relationship to the terminal device.
  • the updating manner of the mapping relationship between the access layer identifier of the QoS flow and the non-access stratum identifier includes:
  • the first network device sends, to the terminal device, a mapping relationship between the non-access stratum identifier of the updated QoS flow and the access stratum identifier of the QoS flow.
  • the first network device sends the indication information of the updated mapping relationship to the terminal device, where the effective indication information is used to indicate the QoS flow of the updated mapping relationship.
  • the validation indication information includes any one of the following: a sequence number of the first PDCP layer protocol data unit adopting the updated mapping relationship, or a sequence number of the last PDCP layer protocol data unit adopting the unupdated mapping relationship.
  • the first network device sends the mapping relationship between the access layer identifier of the updated QoS flow and the non-access stratum identifier to the terminal device, and sends the updated indication information of the mapping relationship, so that the terminal device according to the effective indication information Determine when to start using the latest mappings.
  • the validation indication information may indicate the sequence number of the first PDCP layer protocol data unit adopting the updated mapping relationship, or the sequence number of the last PDCP layer protocol data unit indicating the unupdated mapping relationship.
  • the terminal device performs handover of the network device
  • the handover of the network device refers to the connection of the terminal device from the connection with the source network device to the connection with the target network device.
  • the first network device may be a source network device or a target network device
  • the second network device may be a source network device or a target network device.
  • the process of switching the network device by the terminal device specifically includes:
  • the source network device sends a message about handover preparation to the target network device.
  • the message prepared by the handover includes a first mapping relationship between the non-access stratum identifier of the QoS flow and the access layer identifier of the QoS flow.
  • the first mapping relationship refers to the mapping relationship between the non-access stratum identifier of the QoS flow configured by the source network device and the access stratum identifier of the QoS flow.
  • the target network device sends a message of the handover preparation confirmation to the source network device, where the message of the handover preparation confirmation includes the second mapping relationship or the difference information between the first mapping relationship and the second mapping relationship.
  • the second mapping relationship refers to the mapping relationship between the non-access stratum identifier of the QoS flow configured by the target network device and the access stratum identifier of the QoS flow.
  • the second mapping relationship may be the same as or different from the first mapping relationship.
  • the source network device sends a message of the handover command to the terminal device, where the message of the handover command includes the second mapping relationship or the difference information between the first mapping relationship and the second mapping relationship, and the terminal device adopts the QoS flow in the target network device.
  • the access layer identifier of the QoS flow is configured by the second mapping relationship between the access layer identifier and the access layer identifier of the QoS flow.
  • FIG. 9 is a schematic flowchart of Embodiment 5 of a data offloading method according to an embodiment of the present disclosure.
  • the execution body of the method is a second network device.
  • the second network device sends the offloaded QoS flow to the first network device through the data tunnel, so as to avoid directly sending the offloaded QoS flow to the core network device, thereby avoiding between the core network device and the second network device.
  • the data offloading method provided by the embodiment of the present application includes the following steps:
  • the second network device receives at least one QoS flow in the packet data unit session from the terminal device.
  • the terminal device when the terminal device performs uplink QoS flow transmission, the number of DRBs established between the terminal device and a network device is limited. Therefore, there may be a situation in which the QoS flow needs to be offloaded, and the terminal device passes the offloaded QoS flow through the terminal.
  • the DRB between the device and the second network device is sent to the second network device, and the second network device sends the offloaded QoS flow to the core network device.
  • the second network device sends each QoS flow to the first network device by using a data tunnel corresponding to each QoS flow.
  • the second network device sends the QoS flow to the first network device by using a data tunnel between the first network device and the second network device, so that the first network device sends the QoS flow to the core network device, which avoids A data tunnel is established between the second network device and the first network device.
  • the data tunnel between the second network device and the first network device, and the manner in which the DRB between the terminal device and the second network device are established may refer to the data tunnel and the DRB.
  • the method of establishing is not described in this application.
  • the DRB with bidirectional characteristics can be used, and the same QoS service is provided in the uplink (UL) and the downlink (DL), and the terminal device obtains the mapping of the uplink QoS flow to the DRB from the downlink data packet.
  • the rule is applied to the uplink according to the mapping rule. For example, the uplink QoS flow is mapped to the same DRB as the downlink QoS flow.
  • the terminal device maps the UL QoS flow to the DRB where the DL QoS flow of the same QoS flow ID is located.
  • the mapping relationship between QoS flow and DRB may be determined by the first network device or the second network device. If the SCG supports reflective mapping, it may cause QoS. The confusion of flow to DRB mapping relationship.
  • the first network device notifies the second network device to map the DL QoS flow1 to the DRB1, but for the uplink, multiple connections may not be adopted, or for the QoS flow1 the first network device decides not to perform the offload, a conflict may occur.
  • the terminal device maps the UL QoS flow1 to DRB1 according to the reflective mapping.
  • the first network device may notify the terminal device to map the UL QoS flow1 into the DRB3 through a Radio Resource Control (RRC) configuration, thereby generating a collision.
  • RRC Radio Resource Control
  • the second network device stipulates that the second network device does not support the reflective mapping.
  • the DRB of the SCG bearer and the SCG split Bearer does not support the reflective mapping.
  • the first network device may indicate that the DRB of the second network device SCG bearer and the SCG split Bearer does not support the reflective mapping, for example, the second network device is indicated by a message of the inter-network device interface (Xn interface).
  • the second network device may not carry relevant information of the reflective mapping, such as a QoS flow ID, or a reflective mapping indicator (RMI), in the air interface data packet.
  • a QoS flow ID QoS flow ID
  • RMI reflective mapping indicator
  • the terminal device receives the downlink data packet of the second network device, and does not perform the related operation of the reflective mapping, for example, does not pass the information such as the QoS flow ID included in the downlink data packet to generate the mapping relationship between the uplink QoS flow and the DRB. Further, the terminal device does not perform the related operation of reading the reflective mapping such as the QoS flow ID at the SDAP layer for the bearer of the second network device, thereby achieving the purpose of saving power.
  • the first network device may notify the terminal device that the related operation of performing the reflective mapping is not performed by means of RRC signaling or the like. For example, the terminal device does not perform a related operation of reading a reflective map such as a QoS flow ID in the SDAP layer.
  • the first network device may notify the terminal device that the SDA bearer is not configured in the DRB corresponding to the SCG bearer and the SCG split bearer by means of RRC signaling. Then, the terminal device does not perform a related operation of reading a reflective mapping such as a QoS flow ID in the SDAP layer.
  • the second network device determines a mapping relationship between QoS flow and DRB in the SCG Bearer or the SCG split Bearer;
  • the first network device notifies the QoS flow group on the second network device, where one or more DL/UL QoS flows are included, where the DL/UL QoS flow is sent on the second network device, and the second network device responsible for mapping the DL/UL QoS flow to SCG Bearer or SCG split Bearer.
  • the first network device also notifies the second network device which UL QoS flows can be in a reflective mapping manner. Further, the first network device further notifies the second network device whether the DRB corresponding to each SCG or SCG split bearer has a reverse mapping feature.
  • the DRB has an inversion feature, and the data packet header in the DRB can carry information such as a QoS flow ID, and is used by the terminal device to generate a mapping relationship between the uplink QoS flow and the DRB. Conversely, there is no inversion feature for DRB.
  • the first network device may also notify the reverse mapping feature of the SDAP entity in the second network device. If the SDAP entity has the reverse mapping feature, the DRB associated with the SDAP entity has the reverse mapping feature.
  • the SDAP entity may associate one or more DRBs and be responsible for mapping the data packets to the associated DRBs.
  • the second network device may determine whether to use the reflective mapping mode or the RRC signaling manner to notify the terminal device of the mapping relationship between the QoS flow and the DRB.
  • the second network device configures the mapping relationship between the QoS flow and the DRB by using a reflective mapping manner or an RRC signaling manner for the QoS flow that can be configured in the reflective mapping manner.
  • the mapping relationship between the QoS flow and the DRB is configured in the RRC signaling manner.
  • the second network device maps the QoS flow of the mapping relationship in the reflective mapping manner to the DRB with the reverse mapping feature.
  • the first network device notifies the second network device that the UL QoS flow may be transmitted in the second network device, and the second network device may determine whether to use the reflective mapping manner or the RRC signaling manner to notify the terminal device of the QoS flow to the DRB mapping. relationship.
  • the second network device can consider that all QoS flows can be configured in a reflective mapping manner, and all DRBs have a reverse mapping feature.
  • the second network device may carry the QoS flow ID and the like in the downlink data, and notify the terminal device to generate the mapping of the uplink QoS flow to the DRB through the reflective mapping manner. relationship.
  • the terminal device reads information such as the QoS flow ID included in the downlink data packet in the SCG bearer or the SCG split Bearer, and generates a mapping relationship between the uplink QoS flow and the DRB by using the reflective mapping manner.
  • the embodiment further provides a technical solution for performing update of the QoS flow to the DRB mapping relationship.
  • QoS flow is remapped between DRBs of the second network device.
  • the second network device configures a new QoS flow to DRB mapping relationship by using an RRC signaling manner or a reflective mapping manner, and the terminal device receives a new QoS flow to DRB mapping relationship, and adopts a new QoS flow to the DRB.
  • the mapping relationship is performed to update the QoS flow to the DRB mapping relationship.
  • the RRC signaling may be sent by using a signaling radio bearer (SRB) between the second network device and the terminal device.
  • SRB signaling radio bearer
  • Another possible update method is: QoS flow is remapped between the DRB of the second network device and the DRB of the first network device.
  • the first network device decides to migrate a certain QoS flow from the second network device to the first network device, and the first network device sends a message to the second network device, indicating that the QoS flow is migrated back to the first network device.
  • the mapping relationship between the new QoS flow and the DRB is configured by RRC signaling or reflective mapping.
  • the DRB is the DRB of the first network device, and the terminal receives the mapping relationship between the new QoS flow and the DRB, and uses the new QoS flow to DRB mapping relationship to perform the update of the QoS flow to the DRB mapping relationship. If the mapping relationship of the QoS flow in the second network device is configured by the reflective mapping mode, the terminal may consider that the mapping relationship between the QoS flow and the DRB configured in the second network device is deactivated and is no longer effective.
  • the first network device decides to migrate a certain QoS flow from the first network device to the second network device, and uses the same configuration manner to configure a new QoS flow to DRB mapping relationship for the terminal.
  • the QoS flow received by the second network device may be from the first network device, or may be directly from the core network device.
  • the network device or the terminal device may perform some or all of the steps in the above embodiments, and the steps or operations are merely examples, and the embodiments of the present invention may also perform other operations or variations of various operations. Further, the various steps may be performed in a different order as presented in the above embodiments, and it is possible that not all of the operations in the above embodiments are performed.
  • a further aspect of the present application further provides a data offloading apparatus, which is configured to perform the data offloading method on the first network device side in the foregoing embodiment, and has the same technical features and technical effects.
  • FIG. 10 is a schematic structural diagram of Embodiment 1 of a data offloading apparatus according to an embodiment of the present disclosure.
  • the data offloading device may be the first network device in any of the above embodiments, and the data offloading device may be implemented by software, hardware or a combination of software and hardware. As shown in FIG. 10, the data offloading device may include: a shunt module 11 and a transmitting module 12.
  • the offloading module 11 is configured to determine a QoS flow to be offloaded in the packet data unit session
  • the sending module 12 is configured to send the QoS flow to be offloaded to the second data offloading device by using a data tunnel between the first data offloading device and the second data splitting device.
  • FIG. 11 is a schematic structural diagram of Embodiment 2 of the data offloading apparatus according to the embodiment of the present application.
  • the data offloading device further includes:
  • a data tunnel establishing module 13 is configured to establish a data tunnel corresponding to the packet data unit session between the first data offloading device and the second data offloading device;
  • the sending module 12 is specifically configured to send the QoS flow to be offloaded to the second data offloading device by using the data tunnel corresponding to the packet data unit session to which the QoS flow to be offloaded belongs.
  • the data offloading device further includes:
  • a data tunnel establishing module 13 is configured to establish a public data tunnel between the first data offloading device and the second data splitting device;
  • the sending module 12 is specifically configured to send the QoS flow to be offloaded to the second data offloading device through the public data tunnel.
  • the data offloading device further includes:
  • the data tunnel establishing module 13 is configured to establish a data tunnel corresponding to the DRB between the first data offloading device and the second data offloading device according to the data radio bearer DRB corresponding to the QoS flow to be offloaded;
  • the sending module 12 is specifically configured to send the QoS flow to be offloaded to the second data offloading device by using the data tunnel corresponding to the DRB corresponding to the QoS flow.
  • the data tunnel establishing module 13 is further configured to: determine that there is no data tunnel corresponding to the QoS flow to be offloaded.
  • the data tunnel establishing module 13 is specifically configured to:
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a data tunnel of the second data offload device The tunnel endpoint identifier on the second data offloading device side.
  • the encapsulation header of the data packet that is transmitted to the QoS flow to be offloaded and transmitted in the data tunnel carries an identifier of the QoS flow.
  • the data tunnel establishing module 13 is specifically configured to:
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the public data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a common of the second data offload device The data tunnel is identified at the tunnel endpoint on the second data offloading device side.
  • the encapsulation header of the data packet that is transmitted to the QoS flow to be offloaded and transmitted in the data tunnel carries the identifier of the QoS flow and the identifier of the packet data unit session to which the QoS flow belongs.
  • the data tunnel establishing module 13 is specifically configured to:
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a data tunnel of the second data offload device The tunnel endpoint identifier on the second data offloading device side.
  • the data offloading device further includes: a receiving module 14;
  • the sending module 12 is further configured to send a third message to the second data offloading device, where the third message includes QoS information of the QoS flow to be offloaded, and a mapping relationship between the QoS flow to be offloaded and the DRB;
  • the receiving module 14 is further configured to receive a fourth message from the second data offloading device, where the fourth message includes a QoS flow that the second data offloading device can accept.
  • the third message further includes the establishment indication information of the DRB corresponding to the QoS flow to be offloaded.
  • the sending module 12 is further configured to send, to the second data offloading device, a third message, where the third message includes QoS information of the QoS flow to be offloaded;
  • the receiving module 14 is further configured to receive a fourth message from the second data offloading device, where the fourth message includes a QoS flow that the second data offloading device can accept.
  • the sending module 12 is further configured to send a third message to the second data offloading device, where the third message includes QoS information of the DRB.
  • the receiving module 14 is further configured to receive a fourth message from the second data offloading device, where the fourth message includes a DRB that the second data offloading device can accept.
  • a further aspect of the present application further provides a data offloading device, which is configured to perform the data splitting method on the second network device side in the foregoing embodiment, and has the same technical features and technical effects.
  • FIG. 12 is a schematic structural diagram of Embodiment 3 of a data offloading apparatus according to an embodiment of the present disclosure.
  • the data offloading device may be the second network device in any of the foregoing embodiments, and the data offloading device may be implemented by software, hardware or a combination of software and hardware.
  • the data offloading device may include: a receiving module 21 and a sending module 22;
  • the receiving module 21 is configured to receive a QoS flow from the first data offloading device by using a data tunnel between the first data offloading device and the second data offloading device;
  • the sending module 22 is configured to determine a DRB corresponding to the QoS flow, and send the QoS flow to the terminal device by using the corresponding DRB.
  • the receiving module 21 is further configured to receive, by the first data offloading device, a first message, where the first message includes an identifier of a packet data unit session to which the QoS flow belongs and first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the sending module 22 is further configured to send a second message to the first data offloading device, where the second message includes second tunnel endpoint information that identifies the corresponding data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a data tunnel of the second data offload device The tunnel endpoint identifier on the second data offloading device side.
  • the encapsulation header of the data packet that carries the QoS flow carries the identifier of the QoS flow; the sending module 22 is specifically configured to determine the QoS flow corresponding to the identifier of the packet data unit session and the identifier of the QoS flow corresponding to the data tunnel. DRB.
  • the receiving module 21 is further configured to receive, by using the first data offloading device, the first message, where the first message includes the first tunnel endpoint information of the public data tunnel;
  • the sending module 22 is further configured to send a second message to the first data offloading device, where the second message includes second tunnel endpoint information of the public data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the public data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a common of the second data offload device The data tunnel is identified at the tunnel endpoint on the second data offloading device side.
  • the encapsulation header of the data packet carrying the QoS flow carries the identifier of the QoS flow and the identifier of the packet data unit session to which the QoS flow belongs; the sending module 22 is specifically configured to: according to the identifier and QoS flow of the packet data unit session The identifier identifies the DRB corresponding to the QoS flow.
  • the receiving module 21 is further configured to: receive the first message from the first data offloading device, where the first message includes the identifier of the DRB corresponding to the QoS flow and the first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the sending module 22 is further configured to send a second message to the first data offloading device, where the second message includes second tunnel endpoint information that identifies the corresponding data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first data offload device and a tunnel endpoint identifier of the data tunnel on the first data offload device side;
  • the second tunnel endpoint information includes a transport layer address and a data tunnel of the second data offload device The tunnel endpoint identifier on the second data offloading device side.
  • the sending module 22 is specifically configured to determine, according to the DRB corresponding to the data tunnel, a DRB corresponding to the QoS flow.
  • the receiving module 21 is further configured to: receive a third message from the first data offloading device, where the third message includes QoS information of the QoS flow, and a mapping relationship between the QoS flow and the DRB;
  • the sending module 22 is further configured to determine whether the QoS flow can be accepted according to the QoS information of the QoS flow and the mapping relationship between the QoS flow and the DRB;
  • the fifth message is sent to the first data offloading device, where the fifth message is used to indicate that the QoS flow admission fails.
  • the third message further includes the establishment indication information of the DRB corresponding to the QoS flow.
  • the receiving module 21 is further configured to receive a third message from the first data offloading device, where the third message includes QoS information of the QoS flow;
  • the sending module 22 is further configured to determine whether the QoS flow can be accepted according to the QoS information of the QoS flow;
  • the fifth message is sent to the first data offloading device, where the fifth message is used to indicate that the QoS flow admission fails.
  • the receiving module 21 is further configured to receive a third message from the first data offloading device, where the third message includes QoS information of the DRB.
  • the sending module 22 is further configured to determine whether the DRB can be accepted according to the QoS information of the DRB.
  • the fifth message is sent to the first data offloading device, where the fifth message is used to indicate that the DRB admission fails.
  • the data offloading device comprises:
  • the receiving module 21 is configured to receive, by the terminal device, at least one QoS flow in the packet data unit session;
  • the sending module 22 is configured to send each QoS flow to the first data offloading device by using a data tunnel corresponding to each QoS flow.
  • a further aspect of the present application further provides a network device, which is configured to perform the data offloading method on the first network device side in the foregoing embodiment, and has the same technical features and technical effects.
  • FIG. 13 is a schematic structural diagram of Embodiment 1 of a network device according to an embodiment of the present disclosure.
  • the network device can include a memory 31, a processor 32, at least one communication bus 33, a transmitter 34, and a receiver 35.
  • the communication bus 33 is used to implement a communication connection between components.
  • the memory 31 may include a high speed RAM memory, and may also include a non-volatile memory NVM, such as at least one disk memory, in which various programs may be stored for performing various processing functions and implementing the method steps of the present embodiment.
  • the transmitter 34 may be a radio frequency processing module or a baseband processing module in the base station
  • the receiver 33 may be a radio frequency processing module or a baseband processing module in the base station.
  • the transmitter 34 and the receiver 33 described above may be provided separately, and may also be integrated to form a transceiver, and both the transmitter 34 and the receiver 33 may be coupled to the processor 32.
  • the processor 35 is configured to determine a QoS flow to be offloaded in the packet data unit session
  • the transmitter 34 is configured to send the QoS flow to be offloaded to the second network device by using a data tunnel between the first network device and the second network device.
  • the processor 32 is configured to establish, between the first network device and the second network device, a data tunnel corresponding to the packet data unit session;
  • the transmitter 34 is specifically configured to send the QoS flow to be offloaded to the second network device by using the data tunnel corresponding to the packet data unit session to which the QoS flow to be offloaded belongs.
  • the processor 32 is configured to establish a public data tunnel between the first network device and the second network device;
  • the transmitter 34 is specifically configured to send the QoS flow to be offloaded to the second network device by using a public data tunnel.
  • the processor 32 is configured to establish, according to the data radio bearer DRB corresponding to the QoS flow to be offloaded, a data tunnel corresponding to the DRB between the first network device and the second network device;
  • the transmitter 34 is specifically configured to send the QoS flow to be offloaded to the second network device by using the data tunnel corresponding to the DRB corresponding to the QoS flow to be offloaded.
  • the processor 32 is further configured to: determine that there is no data tunnel corresponding to the QoS flow to be offloaded.
  • the processor 32 is specifically configured to:
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the encapsulation header of the data packet that is transmitted to the QoS flow to be offloaded and transmitted in the data tunnel carries an identifier of the QoS flow.
  • the processor 32 is specifically configured to:
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the public data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and a public data tunnel. Tunnel endpoint identifier on the second network device side
  • the encapsulation header of the data packet that is transmitted to the QoS flow to be offloaded and transmitted in the data tunnel carries the identifier of the QoS flow and the identifier of the packet data unit session to which the QoS flow belongs.
  • the processor 32 is specifically configured to:
  • the first message includes the identifier of the DRB corresponding to the QoS flow to be offloaded and the first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the sender 34 is further configured to: send, to the second network device, a third message, where the third message includes QoS information of the QoS flow to be offloaded, and a mapping relationship between the QoS flow to be offloaded and the DRB;
  • the receiver 35 is further configured to receive a fourth message from the second network device, where the fourth message includes a QoS flow that the second network device can receive.
  • the third message further includes the establishment indication information of the DRB corresponding to the QoS flow to be offloaded.
  • the transmitter 34 is further configured to send, to the second network device, a third message, where the third message includes QoS information of the QoS flow to be offloaded;
  • the receiver 35 is further configured to receive a fourth message from the second network device, where the fourth message includes a QoS flow that the second network device can receive.
  • the sender 34 is further configured to send, to the second network device, a third message, where the third message includes QoS information of the DRB.
  • the receiver 35 is further configured to receive a fourth message from the second network device, where the fourth message includes a DRB that the second network device can receive.
  • a further aspect of the present application further provides a network device, which is configured to perform the data offloading method on the second network device side in the foregoing embodiment, and has the same technical features and technical effects.
  • FIG. 14 is a schematic structural diagram of Embodiment 2 of a network device according to an embodiment of the present disclosure.
  • the network device can include a memory 41, a processor 42, at least one communication bus 43, a transmitter 44, and a receiver 45.
  • Communication bus 44 is used to implement a communication connection between the components.
  • the memory 41 may include a high speed RAM memory, and may also include a non-volatile memory NVM, such as at least one disk memory, in which various programs may be stored for performing various processing functions and implementing the method steps of the present embodiment.
  • the transmitter 44 may be a radio frequency processing module or a baseband processing module in the base station
  • the receiver 44 may be a radio frequency processing module or a baseband processing module in the base station.
  • the transmitter 44 and the receiver 44 described above may be provided separately, and may also be integrated to form a transceiver, and both the transmitter 44 and the receiver 44 may be coupled to the processor 42.
  • the receiver 45 is configured to receive a QoS flow from the first network device by using a data tunnel between the first network device and the second network device;
  • the transmitter 44 is configured to determine a DRB corresponding to the QoS flow, and send the QoS flow to the terminal device by using the corresponding DRB.
  • the receiver 45 is further configured to: receive, by the first network device, a first message, where the first message includes an identifier of a packet data unit session to which the QoS flow belongs and first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the transmitter 44 is further configured to send a second message to the first network device, where the second message includes second tunnel endpoint information that identifies the corresponding data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the encapsulation header of the data packet that carries the QoS flow carries the identifier of the QoS flow; the transmitter 44 is specifically configured to determine the QoS flow corresponding to the identifier of the packet data unit session and the identifier of the QoS flow corresponding to the data tunnel. DRB.
  • the receiver 45 is further configured to receive the first message from the first network device, where the first message includes the first tunnel endpoint information of the public data tunnel;
  • the transmitter 44 is further configured to send a second message to the first network device, where the second message includes second tunnel endpoint information of the public data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the public data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and a public data tunnel.
  • the encapsulation header of the data packet carrying the QoS flow carries the identifier of the QoS flow and the identifier of the packet data unit session to which the QoS flow belongs; the transmitter 44 is specifically configured to: according to the identifier and QoS flow of the packet data unit session The identifier identifies the DRB corresponding to the QoS flow.
  • the receiver 45 is further configured to: receive the first message from the first network device, where the first message includes the identifier of the DRB corresponding to the QoS flow and the first tunnel endpoint information of the data tunnel corresponding to the identifier;
  • the transmitter 44 is further configured to send a second message to the first network device, where the second message includes second tunnel endpoint information that identifies the corresponding data tunnel;
  • the first tunnel endpoint information includes a transport layer address of the first network device and a tunnel endpoint identifier of the data tunnel on the first network device side;
  • the second tunnel endpoint information includes a transport layer address of the second network device and the data tunnel is in the second Tunnel endpoint ID on the network device side.
  • the transmitter 44 is specifically configured to determine, according to the DRB corresponding to the data tunnel, a DRB corresponding to the QoS flow.
  • the receiver 45 is further configured to: receive, by the first network device, a third message, where the third message includes QoS information of the QoS flow, and a mapping relationship between the QoS flow and the DRB;
  • the transmitter 44 is further configured to determine whether the QoS flow can be accepted according to the QoS information of the QoS flow and the mapping relationship between the QoS flow and the DRB.
  • the third message further includes the establishment indication information of the DRB corresponding to the QoS flow.
  • the receiver 45 is further configured to: receive, by the first network device, a third message, where the third message includes QoS information of the QoS flow;
  • the transmitter 44 is further configured to determine, according to the QoS information of the QoS flow, whether the QoS flow can be accepted;
  • the receiver 45 is further configured to: receive, by the first network device, a third message, where the third message includes QoS information of the DRB;
  • the transmitter 44 is further configured to determine whether the DRB can be accepted according to the QoS information of the DRB.
  • the second network device includes:
  • the receiver 45 is configured to receive, by the terminal device, at least one QoS flow in the packet data unit session;
  • the transmitter 44 is configured to send each QoS flow to the first network device by using a data tunnel corresponding to each QoS flow.
  • a further aspect of the embodiments of the present application further provides a communication system, including a core network device and the first network device described in any of the foregoing embodiments.
  • the communication system further includes the second network device described in any one of the foregoing embodiments.
  • a still further aspect of the present application further provides a computer storage medium, configured to store computer software instructions used by the first network device, including a method for performing the first network device side in any of the foregoing embodiments. program.
  • Embodiments of the present application also provide a computer program product comprising instructions that, when executed by a computer, cause the computer to perform the functions performed by the first network device.
  • the embodiment of the present application further provides a chip system, including a processor, for supporting a first network device to implement the functions involved in any of the foregoing embodiments, for example, generating or processing data involved in the foregoing method. And / or information.
  • the chip system further includes a memory for storing program instructions and data necessary for the first network device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • a still further aspect of the embodiments of the present application further provides a computer storage medium, configured to store computer software instructions used by the second network device, where the method includes the method for performing the second network device side in any of the foregoing embodiments. program.
  • Embodiments of the present application also provide a computer program product comprising instructions that, when executed by a computer, cause the computer to perform functions performed by the second network device.
  • the embodiment of the present application further provides a chip system, including a processor, for supporting a second network device to implement the functions involved in any of the foregoing embodiments, for example, generating or processing data involved in the foregoing method. And / or information.
  • the chip system further includes a memory for storing necessary program instructions and data for the second network device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • each device embodiment may refer to related methods in the related method embodiments. Partial understanding.
  • each module of the core network device and the network device is only a division of logical functions, and may be further divided in actual implementation, for example, multiple units or components may be combined or may be Integrate 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.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in 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 above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

Landscapes

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

Abstract

本申请提供一种数据分流方法和装置。该方法包括：第一网络设备确定分组数据单元会话中待分流的QoS flow；所述第一网络设备将所述待分流的QoS flow通过所述第一网络设备和第二网络设备之间的数据隧道发送至所述第二网络设备。通过将待分流的QoS flow由第一网络设备发送至第二网络设备，再将待分流的QoS flow由第二网络设备发送至终端设备，使得待分流的QoS flow从第一网络设备分流到第二网络设备再到终端设备，减少了第一网络设备与核心网设备之间的信令开销。第二网络设备与核心网络设备之间无需建立数据隧道，减少了第二网络设备与核心网设备之间的交互。

Description

数据分流方法和装置
本申请要求于2017年06月16日提交中国专利局、申请号为201710459808.X、申请名称为“数据分流方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种数据分流方法和装置。
背景技术
长期演进(Long Term Evolution，LTE)通信系统中，数据传输的服务质量(Quality of Service，QoS)管理是基于演进分组系统(Evolved Packet System，EPS)承载进行的，不同EPS承载具有不同的QoS。
当一个基站上传输的数据量过大时，可选择将该基站上的部分EPS承载所述承载的数据进行迁移，对部分EPS承载上的数据进行分流。LTE系统中在进行数据分流时，主基站在确定了待分流至辅基站的数据对应的EPS承载后，需将被迁移的数据对应的EPS承载的标识告知核心网，以使核心网将被迁移的EPS承载所承载的数据分发给辅基站。
在5G通信系统中，数据传输的QoS管理是基于服务质量流(QoS flow)进行的，具有相同QoS要求的数据作为一个QoS flow发送。当主基站决定将多个QoS flow迁移至辅基站时，主基站需将各个QoS flow的标识发送给核心网。而QoS flow的数量远大于EPS承载的数量，当主基站与辅基站之间需要频繁的进行QoS flow的迁移时，主基站需要频繁通知核心网被迁移的QoS flow的标识，将会导致基站与核心网之间信令开销较大，并且核心网与辅基站之间还需要建立较多的数据传输的隧道，增加了核心网业务量。
发明内容
本申请实施例提供一种数据分流方法和装置，用以解决第一网络设备在进行QoS flow分流时，需频繁通知核心网被迁移的QoS flow的标识，导致第一网络设备与核心网设备之间信令开销增大，且还需在核心网设备与第二网络设备之间建立较多的数据隧道，增加了核心网业务量的问题。
第一方面，本申请实施例提供一种数据分流方法，包括：
第一网络设备确定分组数据单元会话中待分流的QoS flow；
第一网络设备将待分流的QoS flow通过第一网络设备和第二网络设备之间的数据隧道发送至第二网络设备。
上述第一方面所提供的数据分流方法，通过将待分流的QoS flow由第一网络设备发送至第二网络设备，再将待分流的QoS flow由第二网络设备发送至终端设备，使得待分流的 QoS flow从第一网络设备分流到第二网络设备再到终端设备，而不是从核心网设备直接分流至第二网络设备，第一网络设备无需再向核心网设备报告需分流的QoS flow的标识，减少了第一网络设备与核心网设备之间的信令开销。同时，第二网络设备与核心网络设备之间无需建立数据隧道传输分流的QoS flow，减少了第二网络设备与核心网设备之间的交互。
在一种可能的设计中，数据分流方法还包括：
第一网络设备在第一网络设备与第二网络设备之间建立分组数据单元会话对应的数据隧道；
其中，第一网络设备将待分流的QoS flow通过第一网络设备和第二网络设备之间的数据隧道发送至第二网络设备，包括：
第一网络设备将待分流的QoS flow通过待分流的QoS flow所属的分组数据单元会话所对应的数据隧道发送至第二网络设备。
在一种可能的设计中，数据分流方法还包括：
第一网络设备在第一网络设备与第二网络设备之间建立一条公共数据隧道；
其中，第一网络设备将待分流的QoS flow通过第一网络设备和第二网络设备之间的数据隧道发送至第二网络设备，包括：
第一网络设备将待分流的QoS flow通过公共数据隧道发送至第二网络设备。
在一种可能的设计中，数据分流方法还包括：
第一网络设备根据待分流的QoS flow对应的数据无线承载DRB，在第一网络设备与第二网络设备之间建立DRB对应的数据隧道；
其中，第一网络设备将待分流的QoS flow通过第一网络设备和第二网络设备之间的数据隧道发送至第二网络设备，包括：
第一网络设备将待分流的QoS flow通过待分流的QoS flow对应的DRB所对应的数据隧道发送至第二网络设备。
在一种可能的设计中，第一网络设备根据待分流的QoS flow对应的DRB，在第一网络设备与第二网络设备之间建立DRB对应的数据隧道之前，方法还包括：
第一网络设备确定不存在待分流的QoS flow对应的数据隧道。
上述各可能的设计中，提供了在第一网络设备和第二网络设备之间基于不同的粒度建立数据隧道的方法，使得数据隧道的建立更具灵活性。
在一种可能的设计中，第一网络设备在第一网络设备与第二网络设备之间建立分组数据单元会话对应的数据隧道，包括：
第一网络设备向第二网络设备发送第一消息，第一消息包括分组数据单元会话的标识和标识对应的数据隧道的第一隧道端点信息；
第一网络设备从第二网络设备上接收第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
在一种可能的设计中，在数据隧道中传输的承载在待分流的QoS flow的数据包的封装头中携带有待分流的QoS flow的标识。
上述可能的设计所提供的方法，第一网络设备与第二网络设备之间基于PDU session建立数据隧道，各PDU session对应一个数据隧道，使得第一网络设备向第二网络设备转发数据时，根据待分流的QoS flow所属的PDU session确定数据隧道。通过为各PDU session建立数据隧道，可使得第二网络设备根据数据隧道确定QoS flow所属的PDU session，无需再专门接收QoS flow所属的PDU session的标识，对接收到的QoS flow进行PDU session划分，简化了第二网络设备的操作。
在一种可能的设计中，第一网络设备在第一网络设备与第二网络设备之间建立一条公共数据隧道，包括：
第一网络设备向第二网络设备发送第一消息，第一消息包括公共数据隧道的第一隧道端点信息；
第一网络设备从第二网络设备上接收第二消息，第二消息包括公共数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和公共数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和公共数据隧道在第二网络设备侧的隧道端点标识。
在一种可能的设计中，在所述数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有所述待分流的QoS flow的标识和所述分组数据单元会话的标识。
上述可能的设计所提供的方法，当第一网络设备在存在需要分流的QoS flow时，在第一网络设备和第二网络设备之间建立一条公共数据隧道，使得第一网络设备向第二网络设备转发数据时，将所有QoS flow均通过该公共数据隧道传输。通过仅建立一条公共数据隧道，可降低数据隧道的建立成本，简化数据隧道的维护过程。
在一种可能的设计中，第一网络设备根据待分流的QoS flow对应的DRB，在第一网络设备与第二网络设备之间建立DRB对应的数据隧道，包括：
第一网络设备向第二网络设备发送第一消息，第一消息包括待分流的QoS flow对应的DRB的标识和标识对应的数据隧道的第一隧道端点信息；
第一网络设备从第二网络设备上接收第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
上述可能的设计所提供的方法，当第一网络设备确定存在需要分流的QoS flow时，在第一网络设备和第二网络设备之间基于DRB建立数据隧道，使得第一网络设备向第二网络设备转发数据时，将各QoS flow通过QoS flow对应的DRB所指示的数据隧道传输。通过为各DRB建立各自的数据隧道，使得第二网络设备可直接根据接收到的QoS flow所采用的数据隧道确定QoS flow对应的DRB，进一步简化了第二网络设备的工作。
在一种可能的设计中，数据分流方法还包括：
第一网络设备向第二网络设备发送第三消息，第三消息包括待分流的QoS flow的QoS信息，以及待分流的QoS flow与DRB的映射关系；
第一网络设备从第二网络设备上接收第四消息，第四消息包括第二网络设备能够接纳 的QoS flow。
在一种可能的设计中，若第一网络设备根据待分流的QoS flow的标识，确定不存在待分流的QoS flow对应的DRB，则第三消息中还包括待分流的QoS flow对应的DRB的建立指示信息。
上述可能的设计所提供的方法，第一网络设备向第二网络设备发送QoS flow和DRB的映射关系，使得第二网络设备确定QoS flow对应的DRB，从而实现QoS flow的数据包在第二网络设备和终端设备之间的传输，通过第一网络设备配置QoS flow到DRB的映射关系，实现第二网络设备中QoS flow的数据包到DRB的路由配置。第一网络设备实现了统一的QoS flow到DRB的映射关系的配置，减少了第二网络设备的工作量。
在一种可能的设计中，数据分流方法还包括：
第一网络设备向第二网络设备发送第三消息，第三消息包括待分流的QoS flow的QoS信息；
第一网络设备从第二网络设备上接收第四消息，第四消息包括第二网络设备能够接纳的QoS flow。
上述可能的设计所提供的方法，第一网络设备向第二网络设备发送QoS flow的QoS信息，使得第二网络设备根据QoS flow的QoS信息确定QoS flow对应的DRB，从而实现QoS flow的数据包在第二网络设备和终端设备之间的传输，通过第二网络设备配置QoS flow到DRB的映射关系，实现第二网络设备中QoS flow的数据包到DRB的路由配置。第二网络设备实现了统一的QoS flow到DRB的映射关系的配置，减少了第一网络设备的工作量。
在一种可能的设计中，数据分流方法还包括：
第一网络设备向第二网络设备发送第三消息，第三消息包括DRB的QoS信息；
第一网络设备从第二网络设备上接收第四消息，第四消息包括第二网络设备能够接纳的DRB。
上述可能的设计所提供的方法，第一网络设备接收核心网设备发送的QoS flow，将QoS flow从第一网络设备发送至第二网络设备再到终端设备时，为每个QoS flow确定对应的数据隧道的DRB，因此，QoS flow的数据包中可不再携带QoS flow ID。本实施例中，第一网络设备决定QoS flow到DRB的映射关系，第二网络设备不再执行QoS flow到DRB的路由，减少了第二网络设备的工作量。
第二方面，本申请实施例提供一种数据分流方法。下述第二方面的各可能的设计所提供的方法的有益效果，可以参见上述第一方面的各可能的设计所带来的有益效果。
在第二方面的一种可能的设计中，数据分流方法包括：
第二网络设备通过第一网络设备和第二网络设备之间数据隧道从第一网络设备上接收QoS flow；
第二网络设备确定QoS flow对应的DRB，将QoS flow通过所述QoS flow对应的DRB发送至终端设备。
在一种可能的设计中，数据分流方法还包括：
第二网络设备从第一网络设备上接收第一消息，第一消息包括QoS flow所属的分组数 据单元会话的标识和标识对应的数据隧道的第一隧道端点信息；
第二网络设备向第一网络设备发送第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
在一种可能的设计中，承载到QoS flow的数据包的封装头中携带有QoS flow的标识；第二网络设备确定QoS flow对应的DRB，包括：
第二网络设备根据数据隧道对应的分组数据单元会话的标识、QoS flow的标识，确定QoS flow对应的DRB。
在一种可能的设计中，数据分流方法还包括：
第二网络设备从第一网络设备上接收第一消息，第一消息包括公共数据隧道的第一隧道端点信息；
第二网络设备向第一网络设备发送第二消息，第二消息包括公共数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和公共数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和公共数据隧道在第二网络设备侧的隧道端点标识。
在一种可能的设计中，承载到QoS flow的数据包的封装头中携带有QoS flow的标识和QoS flow所属的分组数据单元会话的标识；第二网络设备确定QoS flow对应的DRB，包括：
第二网络设备根据分组数据单元会话的标识和QoS flow的标识，确定QoS flow对应的DRB。
在一种可能的设计中，数据分流方法还包括：
第二网络设备从第一网络设备上接收第一消息，第一消息包括QoS flow对应的DRB的标识和标识对应的数据隧道的第一隧道端点信息；
第二网络设备向第一网络设备发送第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
在一种可能的设计中，第二网络设备确定QoS flow对应的DRB，包括：
第二网络设备根据数据隧道对应的DRB，确定QoS flow对应的DRB。
在一种可能的设计中，数据分流方法还包括：
第二网络设备从第一网络设备上接收第三消息，第三消息包括QoS flow的QoS信息，以及QoS flow与DRB的映射关系；
第二网络设备根据QoS flow的QoS信息，以及QoS flow与DRB的映射关系，确定能否接纳QoS flow；
若能，则向第一网络设备发送第四消息，第四消息用于指示第二网络设备接纳的QoS  flow；
若否，则向第一网络设备发送第五消息，第五消息用于指示QoS flow接纳失败。
在一种可能的设计中，第三消息还包括QoS flow对应的DRB的建立指示信息。
在一种可能的设计中，数据分流方法还包括：
第二网络设备从第一网络设备上接收第三消息，第三消息包括QoS flow的QoS信息；
第二网络设备根据QoS flow的QoS信息，确定能否接纳QoS flow；
若能，则配置QoS flow与DRB的映射关系，并向第一网络设备发送第四消息，第四消息用于指示第二网络设备接纳的QoS flow；
若否，则向第一网络设备发送第五消息，第五消息用于指示QoS flow接纳失败。
在一种可能的设计中，数据分流方法还包括：
第二网络设备从第一网络设备上接收第三消息，第三消息包括DRB的QoS信息；
第二网络设备根据DRB的QoS信息，确定能否接纳DRB；
若能，则向第一网络设备发送第四消息，第四消息包括第二网络设备接纳的DRB；
若否，则向第一网络设备发送第五消息，第五消息用于指示DRB接纳失败。
第三方面，本申请实施例提供一种数据分流方法，包括：
第二网络设备从终端设备上接收分组数据单元会话中的至少一个QoS flow；
第二网络设备将各QoS flow通过各QoS flow对应的数据隧道发送至第一网络设备。
上述第三方面所提供的方法的有益效果，可以参见上述第一方面提供的方法所带来的有益效果。
第四方面，为了实现上述第一方面的数据分流方法，本申请实施例提供了一种数据分流装置，作为第一网络设备，该数据分流装置具有实现上述数据分流方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。这里的硬件或软件包括一个或多个与上述功能相对应的模块。
在第四方面的一种可能的实现方式中，数据分流装置包括：
分流模块，用于确定分组数据单元会话中待分流的QoS flow；
发送模块，用于将待分流的QoS flow通过第一数据分流装置和第二数据分流装置之间的数据隧道发送至第二数据分流装置。
在一种可能的设计中，数据分流装置还包括：
数据隧道建立模块，用于在第一数据分流装置与第二数据分流装置之间建立分组数据单元会话对应的数据隧道；
其中，发送模块具体用于，将待分流的QoS flow通过待分流的QoS flow所属的分组数据单元会话所对应的数据隧道发送至第二数据分流装置。
在一种可能的设计中，数据分流装置还包括：
数据隧道建立模块，用于在第一数据分流装置与第二数据分流装置之间建立一条公共数据隧道；
其中，发送模块具体用于，将待分流的QoS flow通过公共数据隧道发送至第二数据分流装置。
在一种可能的设计中，数据分流装置还包括：
数据隧道建立模块，用于根据待分流的QoS flow对应的数据无线承载DRB，在第一数据分流装置与第二数据分流装置之间建立DRB对应的数据隧道；
其中，发送模块具体用于，将待分流的QoS flow通过待分流的QoS flow对应的DRB所对应的数据隧道发送至第二数据分流装置。
在一种可能的设计中，数据隧道建立模块还用于，确定不存在待分流的QoS flow对应的数据隧道。
在一种可能的设计中，数据隧道建立模块具体用于，
向第二数据分流装置发送第一消息，第一消息包括分组数据单元会话的标识和标识对应的数据隧道的第一隧道端点信息；
从第二数据分流装置上接收第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和数据隧道在第二数据分流装置侧的隧道端点标识。
在一种可能的设计中，在数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有待分流的QoS flow的标识。
在一种可能的设计中，数据隧道建立模块具体用于，
向第二数据分流装置发送第一消息，第一消息包括公共数据隧道的第一隧道端点信息；
从第二数据分流装置上接收第二消息，第二消息包括公共数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和公共数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和公共数据隧道在第二数据分流装置侧的隧道端点标识
在一种可能的设计中，在数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有QoS flow的标识和QoS flow所属的分组数据单元会话的标识。
在一种可能的设计中，数据隧道建立模块具体用于，
向第二数据分流装置发送第一消息，第一消息包括待分流的QoS flow对应的DRB的标识和标识对应的数据隧道的第一隧道端点信息；
从第二数据分流装置上接收第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和数据隧道在第二数据分流装置侧的隧道端点标识。
在一种可能的设计中，发送模块还用于，向第二数据分流装置发送第三消息，第三消息包括待分流的QoS flow的QoS信息，以及待分流的QoS flow与DRB的映射关系；
接收模块还用于，从第二数据分流装置上接收第四消息，第四消息包括第二数据分流装置能够接纳的QoS flow。
在一种可能的设计中，若根据待分流的QoS flow的标识，确定不存在待分流的QoS  flow对应的DRB，则第三消息中还包括待分流的QoS flow对应的DRB的建立指示信息。
在一种可能的设计中，发送模块还用于，向第二数据分流装置发送第三消息，第三消息包括待分流的QoS flow的QoS信息；
接收模块，还用于从第二数据分流装置上接收第四消息，第四消息包括第二数据分流装置能够接纳的QoS flow。
在一种可能的设计中，发送模块还用于，向第二数据分流装置发送第三消息，第三消息包括DRB的QoS信息；
接收模块还用于，从第二数据分流装置上接收第四消息，第四消息包括第二数据分流装置能够接纳的DRB。
上述第四方面以及第四方面的各可能的设计所提供的方法的有益效果，可以参见上述第一方面的各可能的设计所带来的有益效果，在此不再赘述。
第五方面，为了实现上述第二方面的数据分流方法，本申请实施例提供了一种数据分流装置，作为第二网络设备，该数据分流装置具有实现上述数据分流方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。这里的硬件或软件包括一个或多个与上述功能相对应的模块。
在第五方面的一种可能的实现方式中，数据分流装置包括：
接收模块，用于通过第一数据分流装置和第二数据分流装置之间数据隧道从第一数据分流装置上接收QoS flow；
发送模块，用于确定QoS flow对应的DRB，将QoS flow通过对应的DRB发送至终端设备。
在一种可能的设计中，接收模块还用于，从第一数据分流装置上接收第一消息，第一消息包括QoS flow所属的分组数据单元会话的标识和标识对应的数据隧道的第一隧道端点信息；
发送模块还用于，向第一数据分流装置发送第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和数据隧道在第二数据分流装置侧的隧道端点标识。
在一种可能的设计中，承载到QoS flow的数据包的封装头中携带有QoS flow的标识；发送模块具体用于，根据数据隧道对应的分组数据单元会话的标识、QoS flow的标识，确定QoS flow对应的DRB。
在一种可能的设计中，接收模块还用于，从第一数据分流装置上接收第一消息，第一消息包括公共数据隧道的第一隧道端点信息；
发送模块还用于，向第一数据分流装置发送第二消息，第二消息包括公共数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和公共数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和公共数据隧道在第二数据分流装置侧的隧道端点标识。
在一种可能的设计中，承载到QoS flow的数据包的封装头中携带有QoS flow的标识 和QoS flow所属的分组数据单元会话的标识；发送模块具体用于，根据分组数据单元会话的标识和QoS flow的标识，确定QoS flow对应的DRB。
在一种可能的设计中，接收模块还用于，从第一数据分流装置上接收第一消息，第一消息包括QoS flow对应的DRB的标识和标识对应的数据隧道的第一隧道端点信息；
发送模块还用于，向第一数据分流装置发送第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和数据隧道在第二数据分流装置侧的隧道端点标识。
在一种可能的设计中，发送模块具体用于，根据数据隧道对应的DRB，确定QoS flow对应的DRB。
在一种可能的设计中，接收模块还用于，从第一数据分流装置上接收第三消息，第三消息包括QoS flow的QoS信息，以及QoS flow与DRB的映射关系；
发送模块还用于，根据QoS flow的QoS信息，以及QoS flow与DRB的映射关系，确定能否接纳QoS flow；
若能，则向第一数据分流装置发送第四消息，第四消息用于指示第二数据分流装置接纳的QoS flow；
若否，则向第一数据分流装置发送第五消息，第五消息用于指示QoS flow接纳失败。
在一种可能的设计中，第三消息还包括QoS flow对应的DRB的建立指示信息。
在一种可能的设计中，接收模块还用于，从第一数据分流装置上接收第三消息，第三消息包括QoS flow的QoS信息；
发送模块还用于，根据QoS flow的QoS信息，确定能否接纳QoS flow；
若能，则配置QoS flow与DRB的映射关系，并向第一数据分流装置发送第四消息，第四消息用于指示第二数据分流装置接纳的QoS flow；
若否，则向第一数据分流装置发送第五消息，第五消息用于指示QoS flow接纳失败。
在一种可能的设计中，接收模块还用于，从第一数据分流装置上接收第三消息，第三消息包括DRB的QoS信息；
发送模块还用于，根据DRB的QoS信息，确定能否接纳DRB；
若能，则向第一数据分流装置发送第四消息，第四消息包括第二数据分流装置接纳的DRB；
若否，则向第一数据分流装置发送第五消息，第五消息用于指示DRB接纳失败。
上述第五方面以及第五方面的各可能的设计所提供的方法的有益效果，可以参见上述第二方面的各可能的设计所带来的有益效果，在此不再赘述。
第六方面，为了实现上述第三方面的数据分流方法，本申请实施例提供了一种数据分流装置，作为第二网络设备，该数据分流装置具有实现上述数据分流方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。这里的硬件或软件包括一个或多个与上述功能相对应的模块。
在第六方面的一种可能的实现方式中，数据分流装置包括：
接收模块，用于从终端设备上接收分组数据单元会话中的至少一个QoS flow；
发送模块，用于将各QoS flow通过各QoS flow对应的数据隧道发送至第一数据分流装置。
上述第六方面所提供的方法的有益效果，可以参见上述第三方面提供的方法所带来的有益效果。
第七方面，为了实现上述第一方面的数据分流方法，本申请实施例提供了一种网络设备，作为第一网络设备，该网络设备具有实现上述数据分流方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。这里的硬件或软件包括一个或多个与上述功能相对应的模块。
在第七方面的一种可能的实现方式中，第一网络设备包括：
处理器，用于确定分组数据单元会话中待分流的QoS flow；
发送器，用于将待分流的QoS flow通过第一网络设备和第二网络设备之间的数据隧道发送至第二网络设备。
在一种可能的设计中，第一网络设备还包括：处理器；
处理器用于在第一网络设备与第二网络设备之间建立分组数据单元会话对应的数据隧道；
其中，发送器具体用于，将待分流的QoS flow通过待分流的QoS flow所属的分组数据单元会话所对应的数据隧道发送至第二网络设备。
在一种可能的设计中，第一网络设备还包括：处理器；
处理器用于在第一网络设备与第二网络设备之间建立一条公共数据隧道；
其中，发送器具体用于，将待分流的QoS flow通过公共数据隧道发送至第二网络设备。
在一种可能的设计中，第一网络设备还包括：处理器；
处理器用于根据待分流的QoS flow对应的数据无线承载DRB，在第一网络设备与第二网络设备之间建立DRB对应的数据隧道；
其中，发送器具体用于，将待分流的QoS flow通过待分流的QoS flow对应的DRB所对应的数据隧道发送至第二网络设备。
在一种可能的设计中，处理器还用于，确定不存在待分流的QoS flow对应的数据隧道。
在一种可能的设计中，处理器具体用于，
向第二网络设备发送第一消息，第一消息包括分组数据单元会话的标识和标识对应的数据隧道的第一隧道端点信息；
从第二网络设备上接收第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
在一种可能的设计中，在数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有待分流的QoS flow的标识。
在一种可能的设计中，处理器具体用于，
向第二网络设备发送第一消息，第一消息包括公共数据隧道的第一隧道端点信息；
从第二网络设备上接收第二消息，第二消息包括公共数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和公共数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和公共数据隧道在第二网络设备侧的隧道端点标识
在一种可能的设计中，在数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有待分流的QoS flow的标识和QoS flow所属的分组数据单元会话的标识。
在一种可能的设计中，处理器具体用于，
向第二网络设备发送第一消息，第一消息包括待分流的QoS flow对应的DRB的标识和标识对应的数据隧道的第一隧道端点信息；
从第二网络设备上接收第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
在一种可能的设计中，发送器还用于，向第二网络设备发送第三消息，第三消息包括待分流的QoS flow的QoS信息，以及待分流的QoS flow与DRB的映射关系；
接收器还用于，从第二网络设备上接收第四消息，第四消息包括第二网络设备能够接纳的QoS flow。
在一种可能的设计中，若处理器根据待分流的QoS flow的标识，确定不存在待分流的QoS flow对应的DRB，则第三消息中还包括待分流的QoS flow对应的DRB的建立指示信息。
在一种可能的设计中，发送器还用于，向第二网络设备发送第三消息，第三消息包括待分流的QoS flow的QoS信息；
接收器，还用于从第二网络设备上接收第四消息，第四消息包括第二网络设备能够接纳的QoS flow。
在一种可能的设计中，发送器还用于，向第二网络设备发送第三消息，第三消息包括DRB的QoS信息；
接收器还用于，从第二网络设备上接收第四消息，第四消息包括第二网络设备能够接纳的DRB。
上述第七方面以及第七方面的各可能的设计所提供的方法的有益效果，可以参见上述第一方面的各可能的设计所带来的有益效果，在此不再赘述。
第八方面，为了实现上述第二方面的数据分流方法，本申请实施例提供了网络设备，作为第二网络设备，该网络设备具有实现上述数据分流方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。这里的硬件或软件包括一个或多个与上述功能相对应的模块。
在第八方面的一种可能的实现方式中，第二网络设备包括：
接收器，用于通过第一网络设备和第二网络设备之间数据隧道从第一网络设备上接收QoS flow；
发送器，用于确定QoS flow对应的DRB，将QoS flow通过对应的DRB发送至终端 设备。
在一种可能的设计中，接收器还用于，从第一网络设备上接收第一消息，第一消息包括QoS flow所属的分组数据单元会话的标识和标识对应的数据隧道的第一隧道端点信息；
发送器还用于，向第一网络设备发送第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
在一种可能的设计中，承载到QoS flow的数据包的封装头中携带有QoS flow的标识；发送器具体用于，根据数据隧道对应的分组数据单元会话的标识、QoS flow的标识，确定QoS flow对应的DRB。
在一种可能的设计中，接收器还用于，从第一网络设备上接收第一消息，第一消息包括公共数据隧道的第一隧道端点信息；
发送器还用于，向第一网络设备发送第二消息，第二消息包括公共数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和公共数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和公共数据隧道在第二网络设备侧的隧道端点标识。
在一种可能的设计中，承载到QoS flow的数据包的封装头中携带有QoS flow的标识和QoS flow所属的分组数据单元会话的标识；发送器具体用于，根据分组数据单元会话的标识和QoS flow的标识，确定QoS flow对应的DRB。
在一种可能的设计中，接收器还用于，从第一网络设备上接收第一消息，第一消息包括QoS flow对应的DRB的标识和标识对应的数据隧道的第一隧道端点信息；
发送器还用于，向第一网络设备发送第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
在一种可能的设计中，发送器具体用于，根据数据隧道对应的DRB，确定QoS flow对应的DRB。
在一种可能的设计中，接收器还用于，从第一网络设备上接收第三消息，第三消息包括QoS flow的QoS信息，以及QoS flow与DRB的映射关系；
发送器还用于，根据QoS flow的QoS信息，以及QoS flow与DRB的映射关系，确定能否接纳QoS flow；
若能，则向第一网络设备发送第四消息，第四消息用于指示第二网络设备接纳的QoS flow；
若否，则向第一网络设备发送第五消息，第五消息用于指示QoS flow接纳失败。
在一种可能的设计中，第三消息还包括QoS flow对应的DRB的建立指示信息。
在一种可能的设计中，接收器还用于，从第一网络设备上接收第三消息，第三消息包 括QoS flow的QoS信息；
发送器还用于，根据QoS flow的QoS信息，确定能否接纳QoS flow；
若能，则配置QoS flow与DRB的映射关系，并向第一网络设备发送第四消息，第四消息用于指示第二网络设备接纳的QoS flow；
若否，则向第一网络设备发送第五消息，第五消息用于指示QoS flow接纳失败。
在一种可能的设计中，接收器还用于，从第一网络设备上接收第三消息，第三消息包括DRB的QoS信息；
发送器还用于，根据DRB的QoS信息，确定能否接纳DRB；
若能，则向第一网络设备发送第四消息，第四消息包括第二网络设备接纳的DRB；
若否，则向第一网络设备发送第五消息，第五消息用于指示DRB接纳失败。
上述第八方面以及第八方面的各可能的设计所提供的方法的有益效果，可以参见上述第二方面的各可能的设计所带来的有益效果，在此不再赘述。
第九方面，为了实现上述第三方面的数据分流方法，本申请实施例提供了一种网络设备，作为第二网络设备，该网络设备具有实现上述数据分流方法的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。这里的硬件或软件包括一个或多个与上述功能相对应的模块。
在第九方面的一种可能的实现方式中，第二网络设备包括：
接收器，用于从终端设备上接收分组数据单元会话中的至少一个QoS flow；
发送器，用于将各QoS flow通过各QoS flow对应的数据隧道发送至第一网络设备。
上述第九方面所提供的方法的有益效果，可以参见上述第三方面提供的方法所带来的有益效果。
第十方面，本申请实施例提供了一种计算机存储介质，用于储存上述第一网络设备所用的计算机软件指令，其包含用于执行上述第一方面所设计的程序。
第十一方面，本申请实施例提供了一种计算机存储介质，用于储存上述第二网络设备所用的计算机软件指令，其包含用于执行上述第二方面所设计的程序。
第十二方面，本申请实施例提供了一种计算机存储介质，用于储存上述第二网络设备所用的计算机软件指令，其包含用于执行上述第三方面所设计的程序。
第十三方面，本申请实施例提供一种计算机程序产品，其包含指令，当计算机程序被计算机所执行时，该指令使得计算机执行上述第一方面中的方法中第一网络设备所执行的功能。
第十四方面，本申请实施例提供一种计算机程序产品，其包含指令，当计算机程序被计算机所执行时，该指令使得计算机执行上述第二方面中的方法中第二网络设备所执行的功能。
第十五方面，本申请实施例提供一种计算机程序产品，其包含指令，当计算机程序被计算机所执行时，该指令使得计算机执行上述第三方面中的方法中第二网络设备所执行的功能。
第十六方面，本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持网络设备实现上述第一方面中所涉及的功能，例如，生成或处理上述方法中所 涉及的数据和/或信息。在一种可能的设计中，该芯片系统还包括存储器，所述存储器，用于保存第一网络设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
第十七方面，本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持网络设备设备实现上述第二方面中所涉及的功能，例如，生成或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，该芯片系统还包括存储器，所述存储器，用于保存第二网络设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
第十八方面，本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持网络设备实现上述第三方面中所涉及的功能，例如，生成或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，该芯片系统还包括存储器，所述存储器，用于保存第二网络设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
第十九方面，本申请实施例还提供了一种通信系统，包括核心网设备和上述第七方面中各可能的设计中的第一网络设备。
在一种可能的设计中，通信系统还包括上述第八方面中各可能的设计中的第二网络设备或上述第九方面中的第二网络设备。
附图说明
图1示出了本申请实施例可能适用的一种网络架构；
图2为本申请实施例提供的数据分流方法实施例一的信令流程示意图；
图3为本申请实施例提供的数据分流方法实施例二的信令流程示意图；
图4为本申请实施例提供的数据隧道结构示意图一；
图5为本申请实施例提供的数据隧道结构示意图二；
图6为本申请实施例提供的数据隧道结构示意图三；
图7为本申请实施例提供的数据分流方法实施例三的信令流程示意图；
图8为本申请实施例提供的数据分流方法实施例四的信令流程示意图；
图9为本申请实施例提供的数据分流方法实施例五的流程示意图；
图10为本申请实施例提供的数据分流装置实施例一的结构示意图；
图11为本申请实施例提供的数据分流装置实施例二的结构示意图；
图12为本申请实施例提供的数据分流装置实施例三的结构示意图；
图13为本申请实施例提供的网络设备实施例一的结构示意图；
图14为本申请实施例提供的网络设备实施例二的结构示意图。
具体实施方式
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对 于类似的技术问题，同样适用。
下面结合图1对本申请实施例的可能的网络架构进行介绍。图1示出了本申请实施例可能适用的一种网络架构。如图1所示，本实施例提供的网络架构包括核心网设备10、第一网络设备20、第二网络设备30和至少一个终端设备40。
其中，核心网设备10是一种为终端设备提供服务的设备，主要功能包括：移动性管理功能、QoS控制功能、终端设备的会话管理功能、签约信息管理功能，以及数据转发等功能。核心网设备包括核心网控制面设备，例如，下一代控制平面(Next Generation Control Plane，NG-CP)，包含非接入层(Non Access Stratum，NAS)安全管理、接入层(Access Stratum，AS)安全控制、移动性管理、终端接入验证、注册区域管理、session管理、终端地址分配和管理等功能，核心网控制面设备可由一个或多个网元组成。核心网设备还包括核心网用户面设备，例如，下一代用户平面(Next Generation User Plane，NG-UP)，包含分组数据单元会话(Packet Data Unit session，PDU session)互联的外部节点、包路由和转发、传输处理(QoS执行)、系统内/系统间切换的锚点等其中至少一项功能，核心网用户面设备可由一个或多个网元组成。其中，PDU session是指在终端设备和外部数据网络之间的链接以提供PDU链接服务。外部数据网络示例性的可以指核心网之外的互联网网络。PDU包含多种类型的数据单元，例如可包含网络间互连协议(Internet Protocol，IP)数据包(IP packets)，非可信的PDU(unstructured PDUs)、以太网帧(Ethernet frames)等。
第一网络设备20和第二网络设备30是一种将终端设备接入到无线网络的设备，可以是演进型长期演进(Evolutional Long Term Evolution，简称E-LTE)中的演进型基站(Evolutional Node B，简称eNB或eNodeB)，或者中继站或接入点，或者下一代接入网设备gNB(5G基站)，或者能够接入5G通信系统中的基站等，在此并不限定。图1示意性的绘出了一种可能的示意，以第一网络设备20和第二网络设备30均为基站为例进行了绘示。
可选地，在一种双连接场景下，这种情况下，终端设备可以包含两个媒体接入控制(medium access control,MAC)实体，第一网络设备中包含一个MAC实体，第二网络设备中包含一个MAC实体，终端设备的这两个MAC实体中的第一MAC实体对应第一网络设备中这一个MAC实体，终端设备的这两个MAC实体中第二MAC实体对应第二网络中的这一个MAC实体。通过这种实现方式，一个终端设备可以同时接入到第一网络设备20和第二网络设备30上接收数据或发送数据。终端设备40可以是无线终端也可以是有线终端，无线终端可以是指向用户提供语音和/或其他业务数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(Radio Access Network，简称RAN)与一个或多个核心网设备进行通信，无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication Service，简称PCS)电话、无绳电话、会话发起协议(Session Initiation Protocol，简称SIP)话机、无线本地环路(Wireless Local Loop，简称WLL)站、个人数字助理(Personal Digital Assistant，简称PDA)等设备。无线终端也可以称为系统、订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile  Station)、移动台(Mobile)、远程站(Remote Station)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户代理(User Agent)，在此不作限定。图1示意性的绘出了一种可能的示意，以该终端设备为移动电话为例进行了绘示。
LTE通信系统中，核心网设备10向第一网络设备20发送数据，第一网络设备20将接收到的数据基于EPS承载转发给终端设备40。当第一网络设备20上的EPS承载量过大，例如，通过第一网络设备传输的数据量过大时，第一网络设备可将部分EPS承载所承载的数据分流至第二网络设备30，由第二网络设备30基于EPS承载将数据转发给终端设备40。第一网络设备20需将分流的EPS承载告知核心网设备10，以使核心网设备10将基于该些分流的EPS承载的数据直接发送至第二网络设备30。但是在5G通信系统中，数据传输的QoS管理是基于QoS flow进行的，第一网络设备20需将分流的QoS flow的标识告知核心网设备10，但是QoS flow的数量远多于EPS承载的数量，第一网络设备20需要频繁通知核心网设备10被迁移的QoS flow的标识，且标识量较大，将会导致第一网络设备20与核心网设备10之间信令开销较大。并且核心网设备10与第一网络设备20之间还需要建立较多的数据隧道，增加了核心网设备10的业务量。
为解决上述问题，本申请一方面提供一种数据分流方法，下面采用详细的实施例，对本申请提供的数据分流方法进行详细说明。
图2为本申请实施例提供的数据分流方法实施例一的信令流程示意图。该方法的执行主体为第一网络设备和第二网络设备。本实施例中第一网络设备将分流的QoS flow通过数据隧道发送至第二网络设备，第二网络设备将分流的QoS flow发送至终端，避免了核心网设备将分流的QoS flow直接发送至第二网络设备，因此无需向核心网设备发送分流的QoS flow标识，降低了第一网络设备与核心网设备之间的信令开销，避免了在核心网设备与第二网络设备之间建立数据隧道。如图2所示，本申请实施例提供的数据分流方法包括如下步骤：
S201、确定分组数据单元会话中待分流的QoS flow。
可选地，第一网络设备从核心网设备上接收终端设备的PDU session中的至少一个QoS flow，第一网络设备在接收到的PDU session中的至少一个QoS flow中确定待分流的QoS flow。
示例性的，第一网络设备接收核心网设备发送的一个或多个PDU session，一个PDU session包括至少一个QoS flow。可选地，本申请以下实施例中的PDU session包括至少一个QoS flow，示例性的可以指，在一个PDU session的建立过程中，将数据包承载在至少一个QoS flow上传输。第一网络设备接收到的两个QoS flow可能分别属于两个PDU session。本申请以下各实施例中的发送/接收Qos flow，实际上是指发送/接收这个Qos flow上承载的数据包。本申请以下各实施例中的发送/接收PDU session，实际上是指发送/接收PDU session建立过程中，承载在QoS flow上的数据包。一个PDU session内，具备相同QoS需求的数据的承载在同一个QoS flow上。示例性的，第一网络设备接收核心网设备发送的至少一个PDU session。各PDU session使用PDU session标识区分、各QoS flow可使用QoS flow标识区分。示例性的，不同业务 的数据对QoS质量要求不同。例如、带宽保证的业务需要保证足够的带宽、时延保证的业务对时延敏感需要保证时延较短。
示例性的，第一网络设备需将接收到的QoS flow转发给终端设备。但是可能存在第一网络设备自身负荷较重，终端设备位置较远，第一网络设备与终端设备之间的数据无线承载(Data Radio Bear，DRB)通道数量有限等情况。此时，第一网络设备可在接收到的QoS flow中确定待分流的QoS flow，将待分流的QoS flow分流至第二网络设备，由第二网络设备将QoS flow发送至终端设备。待分流的QoS flow为从第一网络设备传输到第二网络设备，再由第二网络设备发送到终端设备的QoS flow。
S202、第一网络向第二网络设备发送待分流的QoS flow。
可选地，第一网络设备将待分流的QoS flow通过第一网络设备和第二网络设备之间的数据隧道发送至第二网络设备。
示例性的，第一网络设备与第二网络设备之间建立有数据隧道，数据隧道为用于传输终端设备的数据的通道。第一网络设备与第二网络设备之间可以建立一条终端设备的公共数据隧道或多条数据隧道。示例性的，由于核心网设备与第一网络设备之间为每个PDU session建立各自的数据隧道，则第一网络设备与第二网络设备之间也可为每个PDU session建立各自的数据隧道。可选的，第一网络设备与第二网络设备之间建立数据隧道是还可参照其他粒度。例如，可为每一个待分流的QoS flow建立一个数据隧道，还可以按照待分流的QoS flow所在的每个DRB分别建立一个数据隧道。
S203、第二网络设备向终端设备发送待分流的QoS flow。
可选地，第二网络设备接收第一网络设备发送的待分流的QoS flow，确定待分流的QoS flow对应的DRB，将待分流的QoS flow通过待分流的QoS flow对应的DRB发送至终端设备。
示例性的，第一网络设备在向第二网络设备发送待分流的QoS flow时，第一网络设备通知第二网络设备在第二网络设备与至少一个终端设备之间建立DRB，其中，一个或多个QoS flow对应一个DRB。可选的，还可由第一网络设备通知第二网络设备建立DRB。其中，QoS flow与DRB的映射关系，可由第一网络设备建立，并通知到第二网络设备。QoS flow与DRB的映射关系，还可以由第二网络设备决定，此时，也可由第二网络设备建立第二网络设备和终端设备之间的DRB。
终端设备从核心网可以接收到至少一个PDU session，每个PDU session中包含至少一个QoS flow，待分流的QoS flow为至少一个。为了便于理解本申请技术方案，本申请各实施例中以一个PDU session中的一个待分流的QoS flow为例。其他PDU session时，可按照这个PDU session进行相同处理。对于相同或不同的PDU session中的每个待分流的QoS flow分别进行处理，且处理方式相同。各个实施例以待分流的至少一个QoS flow中的一个进行说明，其它QoS flow可按照这个QoS flow进行相同处理。
本申请实施例提供一种数据分流方法，第一网络设备确定PDU session中的待分流的QoS flow，将待分流的QoS flow通过数据隧道发送至第二网络设备，第二网络设备将该待分流的QoS flow通过该待分流的QoS flow对应的DRB发送至终端设备。通过将待分流的QoS flow由第一网络设备发送至第二网络设备，再将待分流的QoS flow由第二网络设备发 送至终端设备，使得待分流的QoS flow从第一网络设备分流到第二网络设备再到终端设备，而不是从核心网设备直接分流至第二网络设备，第一网络设备无需再向核心网设备报告需分流的QoS flow的标识，减少了第一网络设备与核心网设备之间的信令开销。同时，第二网络设备与核心网络设备之间无需建立数据隧道传输分流的QoS flow，减少了第二网络设备与核心网设备之间的交互。
进一步的，在图1和图2所示实施例的基础上，考虑到第一网络设备需在数据隧道中发送QoS flow，因此本申请实施例提供的数据分流方法还包括数据隧道的建立过程。下面结合具体实施例，对在第一网络设备与第二网络设备之间建立数据隧道的方法进行详细说明。
第一种可能的数据隧道建立方式中，第一网络设备以PDU session为粒度，为每个PDU session建立各自的数据隧道。
可选地，本实施例提供的数据分流方法还包括：
第一网络设备根据PDU session，在第一网络设备与第二网络设备之间建立PDU session对应的数据隧道。
其中，上述图2所示实施例中的S203第一网络设备将待分流的QoS flow通过第一网络设备和第二网络设备之间的数据隧道发送至第二网络设备，具体包括：
第一网络设备将所述待分流的QoS flow通过PDU session对应的数据隧道发送至第二网络设备。
示例性的，第一网络设备在根据PDU session建立数据隧道时，为每一个PDU session建立一条数据隧道。属于同一PDU session的QoS flow采用同一数据隧道由第一网络设备发送至第二网络设备。第一网络设备在发送待分流的QoS flow前，首先确定QoS flow所属的PDU session，将PDU session对应的数据隧道作为该QoS flow传输时所采用的数据隧道。
可选的，图3为本申请实施例提供的数据分流方法实施例二的信令流程示意图。本实施例中对建立数据隧道的过程进行详细说明。如图3所示，本实施例提供的数据分流方法包括：
S301、发送第一消息。
可选地，第一网络设备向第二网络设备发送第一消息，第一消息包括PDU session的标识和所述PDU Session标识对应的数据隧道的第一隧道端点信息。
示例性的，第一网络设备向第二网络设备发送第一消息，第一消息中包含待分流的QoS flow所属的PDU session的标识(Identifier)，PDU session ID，以及PDU session ID对应的第一隧道端点信息。第一隧道端点信息包括第一网络设备的传输层地址和该数据隧道在第一网络设备侧的隧道端点标识(Tunnel Endpoint Identifier，TE ID)。可选的，第一消息中还包括终端设备的标识。
S302、接收第二消息。
可选地，第一网络设备从第二网络设备上接收第二消息，第二消息包括PDU session的标识对应的数据隧道的第二隧道端点信息。
示例性的，第二网络设备在接收到第一消息后，根据第二网络设备的负载情况，若决 定建立数据隧道，则向第一网络设备发送第二消息。第一网络设备接收第二网络设备发送的第二消息，第二消息中包括待分流的QoS flow所属的PDU session的PDU session ID以及PDU session ID对应的第二隧道端点信息，第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的TE ID。第一网络设备和第二网络设备在获取到第一隧道端点信息和第二隧道端点信息之后，完成了数据隧道的建立。可选的，第二消息中还包括终端设备的标识。
可选的，当第二网络设备决定不建立数据隧道时，则向第一网络设备发送不建立的指示信息，使得第一网络设备重新对QoS flow的分流进行规划。
示例性的，图4为本申请实施例提供的数据隧道结构示意图一。如图4所示，第一网络设备建立两条数据隧道，分别对应一个PDU session。
示例性的，第一网络设备根据待分流的QoS flow所属的PDU session，确定承载QoS flow所属的PDU session的数据隧道，并将该QoS flow通过该数据隧道发送至第二网络设备。其中，在数据隧道中传输的承载在待分流的QoS flow的数据包的封装头中携带QoS flow ID。例如在通用分组业务用户面隧道(General Packet Radio Service Tunneling Protocol User Plane，GTPU)的扩展头中携带QoS flow ID。其中，第二网络设备根据数据隧道对应的PDU session的ID，确定QoS flow所属的PDU session。进一步的，还可在数据包的封装头中携带QoS反射特性指示。QoS反射特性指示是指终端设备可根据该下行数据包的IP5元组信息和QoS flow ID，得到上行QoS flow的标识和包过滤器，用于终端设备产生上行的QoS flow。其中，QoS反射特性指示可以是第一网络设备从核心网用户面设备接收的。IP 5元组是指业务数据流的IP的源地址、目标地址、源端口号、目的端口号，传输协议，可采用5元组中若干元素的特定取值来构成业务流模板(Traffic Flow Template，TFT)。
可选的，可在第一网络设备的某一PDU session对应的分组数据适配协议(Service Data Adaptation Protocol，SDAP)实体和第二网络设备的同一PDU session对应的SDAP实体之间建立数据隧道，从而使得第一网络设备的SDAP实体可以进行PDU session内的数据分流，接收分流数据的第二网络设备SDAP实体可进行QoS flow到DRB的路由。其中，SDAP是指在空口协议栈中分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)之上的协议层，负责进行QoS flow到DRB的路由，SDAP实体(entity)与PDU session是一一对应的。
可选的，在第一网络设备在发送第一消息前，确定不存在PDU session对应的数据隧道。若第一网络设备确定已经存在PDU session对应的数据隧道，则向第二网络设备发送待分流的QoS flow的标识，并接收第二网络设备反馈的接纳信息或拒绝信息。
本实施例提供的数据分流方法中，第一网络设备与第二网络设备之间基于PDU session建立数据隧道，一个PDU session对应一个数据隧道，使得第一网络设备向第二网络设备转发数据时，根据待分流的QoS flow所属的PDU session确定数据隧道。通过为各PDU session分别建立一个数据隧道，可使得第二网络设备根据数据隧道确定接收到的QoS flow所属的PDU session，无需再专门接收QoS flow所属的PDU session的标识，对接收到的QoS flow进行PDU session划分，简化了第二网络设备的操作。
第二种可能的数据隧道建立方式中，第一网络设备在第一网络设备与第二网络设备之 间建立一条公共数据隧道，所有的待分流的QoS flow均通过该公共数据隧道发送至第二网络设备。与第一种可能的数据隧道建立方式中提供的为每个PDU session建立一条数据隧道相比，本方式通过仅建立一条公共数据隧道，可减少数据隧道的维护成本。
可选地，本实施例提供的数据分流方法还包括：
第一网络设备在第一网络设备与第二网络设备之间建立一条公共数据隧道。
其中，上述图2所示实施例中的S203第一网络设备将待分流的QoS flow通过第一网络设备和第二网络设备之间的数据隧道发送至第二网络设备，具体包括：
第一网络设备将待分流的QoS flow通过公共数据隧道发送至第二网络设备。
示例性的，第一网络设备直接在第一网络设备与第二网络设备之间建立一条终端设备的公共数据隧道，用于传输该终端设备的所有待分流的QoS flow。一个终端设备的多个PDU session均可通过该公共数据隧道由第一网络设备发送至第二网络设备。不同终端设备对应不同的公共数据隧道。通过在第一网络设备和第二网络设备之间建立一条公共数据隧道，以降低数据隧道的建立成本，简化数据隧道的维护过程。
下面对本实施例提供的建立公共数据隧道的过程进行详细说明。本实施例与图3所示实施例的区别在于第一消息和第二消息中无需携带PDU session ID。本实施例提供的数据分流方法包括：
S401、发送第一消息。
可选地，第一网络设备向第二网络设备发送第一消息，第一消息包括公共数据隧道的第一隧道端点信息。
示例性的，第一网络设备向第二网络设备发送第一消息，第一消息中包含第一隧道端点信息。第一隧道端点信息包括所述第一网络设备的传输层地址和公共数据隧道在第一网络设备侧的TE ID。可选的，第一消息中还包括终端设备的标识。
S402、接收第二消息。
可选地，第一网络设备从第二网络设备上接收第二消息，第二消息包括公共数据隧道的第二隧道端点信息。
示例性的，第二网络设备在接收到第一消息后，根据第二网络设备的负载情况，若决定建立公共数据隧道，则向第一网络设备发送第二消息。第一网络设备接收第二网络设备发送的第二消息，第二消息中包括第二隧道端点信息，第二隧道端点信息包括第二网络设备的传输层地址和公共数据隧道在第二网络设备侧的TE ID。第一网络设备和第二网络设备在获取到第一隧道端点信息和第二隧道端点信息之后，完成了数据隧道的建立。可选的，第二消息中还包括终端设备的标识。
可选的，当第二网络设备决定不建立数据隧道是，则向第一网络设备发送不建立的指示信息，使得第一网络设备重新对QoS flow的分流进行规划。
示例性的，图5为本申请实施例提供的数据隧道结构示意图二。如图5所示，第一网络设备建立一条公共数据隧道，用于传输所有PDU session的数据包。
示例性的，在数据隧道建立成功之后，第一网络设备将待分流的QoS flow通过公共数据隧道发送至第二网络设备。在数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带QoS flow ID和PDU session ID。例如在GTPU的扩展头中携带QoS flow ID 和PDU session ID。进一步的，还可在数据包的封装头中携带QoS反射特性指示。
本实施例提供的数据分流方法中，当第一网络设备在存在需要分流的QoS flow时，在第一网络设备和第二网络设备之间建立一条公共数据隧道，使得第一网络设备向第二网络设备转发数据时，将所有QoS flow均通过该公共数据隧道传输。通过仅建立一条公共数据隧道，可降低数据隧道的建立成本，简化数据隧道的维护过程。
第三种可能的数据隧道建立方式中，第一网络设备以DRB为粒度，为每个DRB建立各自的数据隧道。与上述第一和第二种可能的数据隧道建立方式相比，本实施例中数据隧道的建立采用更细的粒度，使得第二网络设备可根据数据隧道确定QoS flow对应的DRB和QoS flow所属的PDU session的ID。
可选地，本实施例提供的数据分流方法还包括：
第一网络设备根据待分流的QoS flow对应的DRB，在第一网络设备与第二网络设备之间建立DRB对应的数据隧道。
其中，上述图2所示实施例中的S203第一网络设备将待分流的QoS flow通过第一网络设备和第二网络设备之间的数据隧道发送至第二网络设备，具体包括：
第一网络设备将待分流的QoS flow通过所述待分流的QoS flow对应的DRB所对应的数据隧道发送至第二网络设备。
示例性的，各QoS flow根据所对应的DRB的不同，采用不同的数据隧道由第一网络设备发送至第二网络设备。第一网络设备在根据DRB建立数据隧道时，为每一个DRB建立一条数据隧道。与第一种可能的数据隧道建立方式和第二种可能的数据隧道建立方式相比，本方式中第一网络设备采用了更细的粒度，当第一网络设备在存在需要分流的QoS flow时，在第一网络设备和第二网络设备之间建立各待分流的QoS flow对应的DRB对应的数据隧道，使得第二网络设备可根据接收到的QoS flow所采用的数据隧道确定所述接收到的QoS flow对应的DRB和所述接收到的QoS flow所属的PDU session的ID，进一步简化了第二网络设备的工作。
下面对本实施例提供的基于DRB建立数据隧道的过程进行详细说明。本实施例与上述两种建立数据隧道的方法的区别在于第一消息和第二消息中携带的是DRB ID。本实施例提供的数据分流方法包括：
S501、发送第一消息。
可选地，第一网络设备向第二网络设备发送第一消息，第一消息中包含待分流的QoS flow对应的DRB的标识，以及DRB标识对应的数据隧道的第一隧道端点信息。
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的TE ID。进一步的，DRB的标识可以是DRB ID，还可采用其他与DRB一一对应的标识来代替DRB ID，例如无线接入承载(Radio Access Bearer，RAB)ID。进一步的，第一消息还可包含DRB对应的QoS需求，其中QoS需求可用QoS参数来表示。可选的，第一消息中还包括终端设备的标识。
可选的，第一消息中还包含待分流的QoS flow所属的PDU session的标识，进一步的，还可采用分组数据适配协议(Service Data Adaptation Protocol，SDAP)实体标识(entity ID)代替PDU session ID。
可选的，在S501之前，本实施例提供的数据分流方法还包括：
S500、第一网络设备确定不存在待分流的QoS flow对应的数据隧道。
示例性的，第一网络设备根据已经建立的QoS flow与DRB的映射关系，确定不存在待分流的QoS flow对应的DRB，因此也不存在该待分流的DRB对应的数据隧道，故此时第一网络设备确定待分流的QoS flow对应的DRB，并向第二网络设备发送待分流的QoS flow对应的DRB，以使第二网络设备为该待分流的DRB建立对应的数据隧道。
可选的，当第一网络设备根据已经建立的QoS flow与DRB的映射关系，为待分流的QoS flow确定已经存在的DRB为待分流的QoS flow对应的DRB，则无需向第二网络设备发送第一消息以建立DRB对应的数据隧道。
S502、接收第二消息。
可选地，第一网络设备从第二网络设备上接收第二消息，第二消息包括DRB的标识对应的数据隧道的第二隧道端点信息。
可选地，第二网络设备在接收到第一消息后，根据第二网络设备的负载情况，若决定建立数据隧道，则向第一网络设备发送第二消息。第一网络设备接收第二网络设备发送的第二消息，第二消息中包括待分流的QoS flow ID对应的DRB ID以及DRB ID对应的数据隧道的第二隧道端点信息，第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的TE ID。进一步的，DRB的标识可以是DRB ID，还可采用其他与DRB一一对应的标识来代替DRB ID，例如无线接入承载(Radio Access Bearer，RAB)ID。可选的，第二消息中还包括终端设备的标识。
可选的，当第二网络设备决定不建立数据隧道时，则向第一网络设备发送不建立的指示信息，使得第一网络设备重新对待分流的QoS flow的分流进行规划。
示例性的，图6为本申请实施例提供的数据隧道结构示意图三。如图6所示，第一网络设备建立8条数据隧道，分别对应一个DRB。
示例性的，在数据隧道建立成功之后，第一网络设备根据待分流的QoS flow的标识，以及QoS flow和DRB的映射关系，确定承载QoS flow的数据隧道，并将该QoS flow通过该数据隧道发送至第二网络设备。
进一步的，第一网络设备还可根据待分流的QoS flow的QoS flow ID以及所属的PDU session ID，以及QoS flow和DRB的映射关系，确定承载QoS flow的数据隧道。
可选的，在数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中可携带QoS flow ID，例如在通用分组业务用户面隧道(General Packet Radio Service Tunneling Protocol User Plane，GTPU)的扩展头中携带QoS flow ID。进一步的，还可在数据包的封装头中携带QoS反射特性指示。QoS反射特性指示是指终端设备可根据该下行数据包的IP5元组信息和QoS flow ID，得到上行QoS flow的标识和包过滤器，用于终端设备产生上行的QoS flow。其中，QoS反射特性指示可以是第一网络设备从核心网用户面设备接收的。IP 5元组是指业务数据流的IP的源地址、目标地址、源端口号、目的端口号，传输协议，可采用5元组中若干元素的特定取值来构成业务流模板(Traffic Flow Template，TFT)。
本实施例提供的数据分流方法中，当第一网络设备确定存在需要分流的QoS flow时，在第一网络设备和第二网络设备之间基于DRB建立数据隧道，使得第一网络设备向第二网络设备转发数据时，将各QoS flow通过QoS flow对应的DRB所指示的数据隧道传输。 通过为各DRB建立各自的数据隧道，使得第二网络设备可直接根据接收到的QoS flow所采用的数据隧道确定QoS flow对应的DRB，进一步简化了第二网络设备的工作。
示例性的，在上述任一实施例中，各数据隧道可以同时用于传输上行下行数据，各数据隧道也可以由两条传输方向不同的子数据隧道构成。
示例性的，在上述任一实施中，在进行下行数据传输时，第一网络设备负责将PDU session分流至不同的SDAP实体。进一步的，第一网络设备中的SDAP实体(对应一个session)负责进行对应的PDU session中的QoS flow的分流，例如，将部分QoS flow分流到第二网络设备。
示例性的，在上述任一实施中，在进行上行数据传输时，终端设备根据第一网络设备或第二网络设备的配置信息，分别向第一网络设备和第二网络设备发送QoS flow的数据包。其中，配置信息中包括QoS flow与DRB的映射关系等。第二网络设备通过第一网络设备和第二网络设备之间的数据隧道，将从终端设备接收的QoS flow的数据包发送到第一网络设备。其中，在DRB和数据隧道中传输的数据包的封装头中携带QoS flow ID，例如在GTPU扩展头中携带。若是第一网络设备和第二网络设备之间是一条公共数据隧道，则在公共数据隧道中传输的数据包的封装头中还携带所属的PDU session的标识，例如，PDU session ID。第一网络设备将从终端设备和第二网络设备接收到的QoS flow的数据包发送到核心网用户面设备。进一步的，第一网络设备通过第一网络设备和核心网设备之间的按照PDU session建立的数据通道进行数据包的发送，其中在第一网络设备与核心网设备之间的数据隧道中传输的数据包的封装头中携带QoS flow ID，例如在GTPU扩展头中携带。
进一步的，在上述任一实施例的基础上，考虑到第二网络设备需在DRB中发送待分流的QoS flow，因此本申请实施例提供的数据分流方法还包括DRB的建立过程。下面结合具体实施例，对在第二网络设备与终端设备之间建立DRB的方法进行详细说明。
第一种可能的DRB建立方式：
在上述第一种或第二种可能的数据隧道建立方式的基础上，本申请实施例提供一种可能的DRB建立方式如图7所示。图7为本申请实施例提供的数据分流方法实施例三的信令流程示意图。本实施例提供的DRB建立方法中，第一网络设备发送的第一消息中包括QoS flow的QoS信息、DRB与QoS flow的映射关系，第一网络设备指示第二网络设备根据配置好的DRB与QoS flow的映射关系建立DRB。如图7所示，数据分流方法包括：
S701、发送第三消息。
可选地，第一网络设备向第二网络设备发送第三消息，第三消息包括待分流的QoS flow的QoS信息以及待分流的QoS flow与DRB的映射关系。
示例性的，第一网络设备向第二网络设备发送第三消息，第三消息用于指示第二网络设备根据第三消息中携带的映射关系建立DRB。进一步的，第三消息中还可包含待分流的QoS flow所属的PDU session ID。其中，当第三消息中包括多个待分流的QoS flow时，待分流的QoS flow可采用各QoS flow的QoS flow ID来区分。各待分流的QoS flow所属的 PDU session可采用PDU session ID，或者PDU session对应的TE ID和传输层地址信息来表示。
其中，QoS flow的QoS信息可以采用QoS flow ID来指示预设的QoS参数，或QoS信息包含QoS参数。示例性的，QoS参数包括：时延、丢包率、优先级、保证速率、最大速率、终端设备级聚合最大比特速率(Aggregate Maximum Bit Rate，AMBR)、slice级的AMBR、会话级的AMBR、分配保留优先级(Allocation and Retention Priority，ARP)中的至少一项。其中AMBR适用于限制多个非保证速率业务的最大速率。
示例性的，QoS flow的QoS信息可以是核心网设备发送给第一网络设备的，也可以是第一网络设备根据接收到的QoS flow的部分QoS信息以及第一网络设备和第二网络设备的负载情况计算得到。例如，第一网络设备可根据从核心网收到的QoS信息中的AMBR来为第一网络设备和第二网络设备生成终端设备级AMBR、slice级的AMBR或会话级的AMBR中的一项或多项。第一网络设备可将第一网络设备的终端设备级AMBR、slice级的AMBR、PDU session级的AMBR、及第二网络设备的终端设备级AMBR、slice级的AMBR、PDU session级的AMBR中的一项或多项通知到第二网络设备。例如，可通过第三消息通知第二网络设备。
进一步的，第三消息中还包含待分流的QoS flow对应的DRB的类型，从而可使得第二网络设备确定需要建立的DRB的QoS信息。
其中，DRB的类型是指DRB的承载类型，包含主小区组承载(Master Cell Group Bearer，MCG bearer)、主小区组分裂承载(master cell group splitbearer，MCG split Bearer)、第二小区组承载(Secondary Cell Group Bearer，SCG bearer)、第二小区组分裂承载(Secondary Cell Group Split Bearer，SCG split bearer)。
其中，主小区组承载是指承载的协议栈在主小区组。主小区组分裂承载是指承载的协议栈在主基站分裂并属于主小区组和辅小区组。第二小区组承载是指承载的协议栈在第二小区组。第二小区组分裂承载是指承载的协议栈在第二基站分裂并属于属于主小区组和辅小区组。
S702、确定能否接纳所述待分流的QoS flow；若能，则执行S703；若否，则执行S704。
可选地，第二网络设备从第一网络设备上接收第三消息，第三消息包括QoS flow的QoS信息，以及QoS flow与DRB的映射关系。第二网络设备根据QoS flow的QoS信息，以及QoS flow与DRB的映射关系，确定能否接纳QoS flow。
示例性的，第二网络设备在接收到第三消息后，第二网络设备可根据QoS flow对应的DRB的负载情况，确定能否接纳该QoS flow。
示例性的，第二网络设备在接收到第三消息后，可根据QoS flow的QoS信息中所包括的AMBR信息进行速率限制等操作。第二网络设备根据接收到的第三消息中的QoS flow与DRB的映射关系，进行QoS flow的数据包到DRB的路由。第二网络设备在DRB中发送QoS flow的数据包时，在空口数据包的协议头中携带QoS flow ID和QoS反射特性指示。进一步的，第二网络设备可只在接收到QoS反射特性指示时，才在空口数据包的协议头中携带QoS flow ID。
可选的，当第一网络设备在已有的DRB中确定没有适合的DRB来承载待分流的QoS flow，可为该待分流的QoS flow分配新的DRB。其中，第三消息中还可包括QoS flow对 应的DRB的建立指示信息。DRB的建立指示信息具体可以为DRB的配置信息或新的DRB ID，第二网络设备根据DRB的配置信息或新的DRB ID新建立DRB。DRB的配置信息包含但不限于DRB ID、PDCP协议层配置、无线链路控制层协议(Radio Link Control Protocol，RLC)配置，逻辑信道(Logic Channel，LCH)配置。
可选的，当第三消息中包括DRB的建立指示信息时，第二网络设备根据负载情况，确定能否接纳该DRB。
S703、向第一网络设备发送第四消息，第四消息用于指示第二网络设备接纳的QoS flow。
S704、向第一网络设备发送第五消息，第五消息用于指示QoS flow接纳失败。
示例性的，当第二网络设备能够接纳QoS flow，则第二网络设备向第一网络设备发送第四消息，第四消息中示例性的可以包括第二网络设备能够接纳的QoS flow。当第二网络设备不能够接纳QoS flow，则第二网络设备向第一网络设备发送第五消息，第五消息用于指示本次QoS flow接纳失败，第一网络设备可重新为待分流的QoS flow确定第二网络设备。可选的，第四消息中也包括第二网络设备无法接纳的QoS flow，还可以进一步包括无法接纳该QoS flow的原因。
可选的，第一网络设备可将第一消息与第三消息中的内容携带在同一个消息中一起发送给第二网络设备。
本实施例中，第一网络设备向第二网络设备发送QoS flow和DRB的映射关系，使得第二网络设备确定QoS flow对应的DRB，从而实现QoS flow的数据包在第二网络设备和终端设备之间的传输，通过第一网络设备配置QoS flow到DRB的映射关系，实现第二网络设备中QoS flow的数据包到DRB的路由配置。第一网络设备实现了统一的QoS flow到DRB的映射关系的配置，减少了第二网络设备的工作量。
第二种可能的DRB建立方式：
在上述第一种或第二种可能的数据隧道建立方式的基础上，本申请实施例还提出第二种可能的DRB建立方式。与第一种可能的DRB建立方式不同的是，本实施例中第二网络设备自行建立DRB与QoS flow的映射关系。本实施例中数据分流方法包括：
S801、发送第三消息。
可选地，第一网络设备向第二网络设备发送第三消息，第三消息包括QoS flow的QoS信息。
示例性的，第一网络设备向第二网络设备发送第三消息，第三消息用于指示第二网络设备为QoS flow确定DRB。可选的，第三消息携带有待分流的QoS flow的标识，待分流的QoS flow的标识可指示待分流的QoS flow的QoS信息。进一步的，第三消息中还可包含待分流的QoS flow所属的PDU session ID。
S802、确定能否接纳所述待分流的QoS flow；若能，则执行S803；若否，则执行S804。
可选地，第二网络设备从第一网络设备上接收第三消息，第三消息包括QoS flow的QoS信息。第二网络设备根据QoS flow的QoS信息，确定能否接纳QoS flow。
示例性的，第二网络设备在接收到第三消息后，根据自身的负荷情况，确定是否接纳第三消息中携带的QoS flow。可选地，若QoS flow对应的DRB已建立，则确定该DRB 能否接纳该QoS flow，若否，则第二网络设备根据负荷情况，确定能否建立该DRB。
S803、配置QoS flow与DRB的映射关系，并向第一网络设备发送第四消息，第四消息用于指示第二网络设备接纳的QoS flow。
S804、向第一网络设备发送第五消息，第五消息用于指示QoS flow接纳失败。
示例性的，当第二网络设备能够接纳QoS flow，则第二网络设备配置QoS flow与DRB的映射关系，并向第一网络设备发送第四消息，第四消息中示例性的可以包括第二网络设备能够接纳的QoS flow。当第二网络设备不能够接纳QoS flow，则第二网络设备向第一网络设备发送第五消息，第五消息用于指示本次QoS flow接纳失败，第一网络设备可重新为待分流的QoS flow确定第二网络设备。可选的，第四消息中也包括第二网络设备无法接纳的QoS flow，还可以进一步包括无法接纳该QoS flow的原因。
可选的，第二网络设备在配置QoS flow和DRB的映射关系后，还将QoS flow和DRB的映射关系发送至终端设备。可选的，还可将QoS flow和DRB的映射关系发送至第一网络设备，由第一网络设备将QoS flow和DRB的映射关系发送至终端设备。可选的，第四消息中还可包括QoS flow对应的DRB的配置信息。终端设备根据DRB的配置信息，以及QoS flow和DRB的映射关系，完成DRB的建立。
可选的，第一网络设备可将第一消息与第三消息中的内容携带在同一个消息中一起发送给第二网络设备。
本实施例中，第一网络设备向第二网络设备发送QoS flow的QoS信息，使得第二网络设备根据QoS flow的QoS信息确定QoS flow对应的DRB，从而实现QoS flow的数据包在第二网络设备和终端设备之间的传输，通过第二网络设备配置QoS flow到DRB的映射关系，实现第二网络设备中QoS flow的数据包到DRB的路由配置。第二网络设备实现了统一的QoS flow到DRB的映射关系的配置，减少了第一网络设备的工作量。
第三种可能的DRB建立方式：
在上述第三种可能的数据隧道建立方式的基础上，本申请实施例还提出第三种可能的DRB建立方式如图8所示。图8为本申请实施例提供的数据分流方法实施例四的信令流程示意图。与第一种、第二种可能的DRB建立方式不同的是，本实施例中待分流的QoS flow通过该待分流的QoS flow对应的DRB所对应的数据隧道发送至第二网络设备，第一网络设备已经为该QoS flow确定对应的DRB，故第一网络设备将各QoS flow对应的DRB的QoS信息，直接发送给第二网络设备，以使第二网络设备根据建立该DRB。如图8所示，本实施例中数据分流方法包括：
S901、发送第三消息。
可选地，第一网络设备向第二网络设备发送第三消息，第三消息包括所述待分流的QoS flow对应的DRB的QoS信息。
示例性的，第一网络设备向第二网络设备发送第三消息，第三消息包括DRB的QoS信息。可选地，第一网络设备在已有的DRB中，确定是否存在DRB能够接纳待分流QoS flow，若存在，则无需再为该QoS flow建立DRB，则无需发送第三消息。当不存在，则需为待分流的QoS flow确定对应的DRB，并在第一网络设备和第二网络设备之间建立对 应的数据隧道，在第二网络设备和终端设备建立对应的DRB，此时，第一网络设备向第二网络设备发送第三消息，以建立待分流的QoS flow确定对应的DRB。
示例性的，DRB的QoS信息包含QoS参数，QoS参数包括：时延、丢包率、优先级等。进一步的，DRB的QoS信息还可包含保证速率、最大速率。进一步的，DRB的QoS信息还可包含终端设备级聚合最大比特速率(Aggregate Maximum Bit Rate，AMBR)、slice级的AMBR、会话级的AMBR、分配保留优先级(Allocation and Retention Priority，ARP)等其中AMBR适用于限制多个非保证速率业务的最大速率。
示例性的，还可采用DRB所对应的QoS flow的QoS信息来表示DRB的QoS信息。
S902、确定能否接纳DRB；若能，则执行S903；若否，则执行S904。
可选地，第二网络设备从第一网络设备上接收第三消息，第三消息包括DRB的QoS信息，第二网络设备根据DRB的QoS信息，确定能否接纳DRB。
示例性的，第二网络设备在接收到第三消息后，根据自身的负荷情况，确定是否接纳第三消息中携带的DRB。
S903、向第一网络设备发送第四消息，第四消息用于指示第二网络设备接纳的DRB。
S904、向第一网络设备发送第五消息，第五消息用于指示DRB接纳失败。
示例性的，当第二网络设备能够接纳DRB，则第二网络设备向第一网络设备发送第四消息，第四消息中示例性的可以包括第二网络设备能够接纳的DRB。当第二网络设备不能够接纳DRB，则第二网络设备向第一网络设备发送第五消息，第五消息用于指示本次DRB接纳失败，第一网络设备可重新为待分流的QoS flow确定第二网络设备。可选的，第四消息中也包括第二网络设备无法接纳的DRB，还可以进一步包括无法接纳该DRB的原因。
示例性的，在本实施例中，第一网络设备接收核心网设备发送的QoS flow，将QoS flow从第一网络设备发送至第二网络设备再到终端设备时，为每个QoS flow确定对应的数据隧道的DRB，因此，QoS flow的数据包中可不再携带QoS flow ID。本实施例中，第一网络设备决定QoS flow到DRB的映射关系，第二网络设备不再执行QoS flow到DRB的路由，减少了第二网络设备的工作量。
在上述任一实施例的基础上，可以由第一网络设备向终端设备发送QoS flow与DRB的映射关系，以使终端设备在发送上行QoS flow时，确定上行QoS flow对应的DRB。进一步的，还可以是第二网络设备向终端设备发送QoS flow与DRB的映射关系，以使终端设备在发送上行QoS flow时，确定上行QoS flow对应的DRB。
示例性的，若第一网络设备为LTE基站eNB，第二网络设备为下一代基站gNB，并且第一网络设备和第二网络设备都连接到第四代通信系统中的核心网设备，那么第二网络设备中可不配置SDAP协议层。
可选的，在上述任一实施例的基础上，QoS flow在传输过程中携带的标识由非接入层生成，QoS flow的标识通常较长。但是，当第二网络设备将QoS flow转发至终端设备时，QoS flow在接入层传输，QoS flow的标识可采用接入层标识，从而减小空口由于QoS flow的标识带来的开销。下面对QoS flow的标识在接入层与非接入层之间的映射进行详细说明。
一种可行的实现方式中，第一网络设备根据各QoS flow的非接入层标识，生成各QoS  flow的接入层标识；其中，发送至第二网络设备的QoS flow中携带有QoS flow的接入层标识。
可选地，第一网络设备在接收到核心网设备发送的QoS flow后，为各QoS flow生成接入层标识，并存储接入层标识和非接入层标识的映射关系。第一网络设备将携带有接入层标识的QoS flow发送至第二网络设备，第二网络设备将携带有接入层标识的QoS flow发送至终端设备。第一网络设备可将接入层标识和非接入层标识的映射关系发送至第二网络设备和终端设备。
另一种可行的实现方式中，第一网络设备根据各QoS flow的非接入层标识和所属的PDU session ID，生成各QoS flow的接入层标识；其中，发送至第二网络设备的QoS flow中携带有QoS flow的接入层标识。
可选地，第一网络设备在接收到核心网设备发送的QoS flow后，为各QoS flow生成接入层标识。接入层标识可指示QoS flow的非接入层标识以及QoS flow所属的PDU session的标识。第一网络设备并存储接入层标识与非接入层标识、QoS flow所属的PDU session的标识的映射关系。第一网络设备将携带有接入层标识的QoS flow发送至第二网络设备，第二网络设备将携带有接入层标识的QoS flow发送至终端设备。第一网络设备可将接入层标识与非接入层标识、QoS flow所属的PDU session的标识的映射关系发送至第二网络设备和终端设备。
再一种可行的实现方式中，还可以由第二网络设备根据各QoS flow的非接入层标识和所属的PDU session ID，生成各QoS flow的接入层标识。
可选的，在上述任一实施例的基础上，QoS flow的接入层标识与非接入层标识的映射关系可能发生变化，第一网络设备需向终端设备更新映射关系。可选地，QoS flow的接入层标识与非接入层标识的映射关系的更新方式包括：
S1001、第一网络设备向终端设备发送更新的QoS flow的非接入层标识与QoS flow的接入层标识的映射关系。
S1002、第一网络设备向终端设备发送更新的映射关系的生效指示信息，生效指示信息用于指示采用更新的映射关系的QoS flow。
其中，生效指示信息包括如下中的任一项：采用更新的映射关系的第一个PDCP层协议数据单元的序号，或者采用未更新的映射关系的最后一个PDCP层协议数据单元的序号。
可选地，第一网络设备向终端设备发送更新的QoS flow的接入层标识与非接入层标识的映射关系，并发送更新的映射关系的生效指示信息，以使终端设备根据生效指示信息确定何时开始使用最新的映射关系。示例性的，生效指示信息可以指示采用更新的映射关系的第一个PDCP层协议数据单元的序号，或者指示采用未更新的映射关系的最后一个PDCP层协议数据单元的序号。
可选的，在上述任一实施例的基础上，可能存在终端设备进行网络设备的切换的情况，网络设备的切换指终端设备从与源网络设备连接切换到与目标网络设备连接。
示例性的，第一网络设备可以为源网络设备或目标网络设备，第二网络设备可以为源网络设备或目标网络设备。
终端设备进行网络设备的切换过程具体包括：
S1101、源网络设备向目标网络设备发送切换准备的消息；切换准备的消息中包含QoS flow的非接入层标识与QoS flow的接入层标识的第一映射关系。第一映射关系是指源网络设备配置的QoS flow的非接入层标识与QoS flow的接入层标识的映射关系。
S1102、目标网络设备向源网络设备发送切换准备确认的消息，切换准备确认的消息中包含第二映射关系或第一映射关系与第二映射关系的区别信息。第二映射关系是指目标网络设备配置的QoS flow的非接入层标识与QoS flow的接入层标识的映射关系。其中，第二映射关系可与第一映射关系相同或不同。
S1103、源网络设备发送切换命令的消息到终端设备，切换命令的消息中包含第二映射关系或第一映射关系与第二映射关系的区别信息，终端设备在目标网络设备中采用QoS flow的非接入层标识与QoS flow的接入层标识的第二映射关系来配置QoS flow的接入层标识。
本申请另一方面还提供一种数据分流方法，应用于上述数据传输时的数据分流。图9为本申请实施例提供的数据分流方法实施例五的流程示意图。该方法的执行主体为第二网络设备。本实施例中第二网络设备将分流的QoS flow通过数据隧道发送至第一网络设备，避免了直接将分流的QoS flow发送至核心网设备，避免了在核心网设备与第二网络设备之间建立数据隧道。如图9所示，本申请实施例提供的数据分流方法包括如下步骤：
S1201、第二网络设备从终端设备上接收分组数据单元会话中的至少一个QoS flow。
示例性的，终端设备在进行上行QoS flow传输时，由于终端设备与一个网络设备之间建立的DRB数量有限，因此，可能存在需要将QoS flow分流的情况，终端设备将分流的QoS flow通过终端设备与第二网络设备之间的DRB发送至第二网络设备，由第二网络设备将分流的QoS flow发送至核心网设备。
S1202、第二网络设备将各QoS flow通过各QoS flow对应的数据隧道发送至第一网络设备。
示例性的，第二网络设备将QoS flow通过第一网络设备与第二网络设备之间的数据隧道发送至第一网络设备，以使得第一网络设备将QoS flow发送至核心网设备，避免了第二网络设备与第一网络设备之间建立数据隧道。
示例性的，本申请实施例中的，第二网络设备与第一网络设备之间的数据隧道，以及终端设备与第二网络设备之间的DRB的建立方式可以参考上述的数据隧道、DRB的建立方法，本申请对此不再赘述。
在5G通信系统中，可以采用具有双向特性的DRB，在上行(Uplink，UL)和下行方向(Downlink，DL)提供相同的QoS服务，终端设备从下行数据包中得到上行QoS flow到DRB的映射规则，将根据该映射规则应用到上行方向上，例如，上行QoS flow映射到与下行QoS flow相同的DRB上。终端设备将UL QoS flow映射到相同QoS flow ID的DL QoS flow所在的DRB。
在多连接网络中，如SCG bearer和SCG split bearer，其QoS flow到DRB的映射关系，可能由第一网络设备或第二网络设备确定，若SCG支持反转(reflective)映射，那么可能导致QoS flow到DRB映射关系的混乱。
例如，第一网络设备通知第二网络设备将DL QoS flow1映射到DRB1，但是对于上行，可能不会采用多连接，或者对于QoS flow1第一网络设备决定不做分流，那么会产生冲突。终端设备会根据reflective映射得到UL QoS flow1映射到DRB1中。第一网络设备可能会通过无线资源控制(Radio Resource Control，RRC)配置通知终端设备将UL QoS flow1映射到DRB3中，从而产生冲突。
本实施例提供以下可能的技术方案，解决上述冲突问题：
第一种可行的技术方案：
S1301、规定第二网络设备不支持reflective映射，例如，SCG bearer和SCG split Bearer的DRB不支持reflective映射。进一步的，第一网络设备可以指示第二网络设备SCG bearer和SCG split Bearer的DRB不支持reflective映射，例如通过网络设备间接口(Xn接口)的消息来指示第二网络设备。第二网络设备在空口数据包中可不携带reflective映射的相关信息，例如QoS flow ID，或者反转映射指示(reflective mapping indicator，RMI)。
S1302、终端设备接收第二网络设备的下行数据包，不执行reflective映射的相关操作，例如，不通过下行数据包中包含的QoS flow ID等信息，来产生上行QoS flow到DRB的映射关系。进一步，终端设备对于第二网络设备的bearer，不执行在SDAP层读取QoS flow ID等reflective映射的相关操作，可以达到节约电能的目的。
进一步的，第一网络设备可通过RRC信令等方式通知终端设备不进行执行reflective映射的相关操作。例如，终端设备不进行在SDAP层中读取QoS flow ID等reflective映射的相关操作。
进一步的，第一网络设备可通过RRC信令等方式通知终端设备SCG bearer和SCG split Bearer对应的DRB中不配置SDAP协议头。则终端设备不进行在SDAP层中读取QoS flow ID等reflective映射的相关操作。
第二种可行的技术方案：
第二网络设备决定SCG Bearer或SCG split Bearer中的QoS flow到DRB的映射关系；
S1401、第一网络设备通知分流到第二网络设备上的QoS flow组，其中包含一个或多个DL/UL QoS flow，所述DL/UL QoS flow在第二网络设备上发送，第二网络设备负责将所述DL/UL QoS flow映射到SCG Bearer或SCG split Bearer中。第一网络设备还通知第二网络设备哪些UL QoS flow可以采用reflective映射方式。进一步的，第一网络设备还通知第二网络设备每一SCG或SCG split bearer对应的DRB是否具备反转映射特性。所述DRB具备反转特性是指，DRB中的数据包头可携带QoS flow ID等信息，用于终端设备产生上行QoS flow到DRB的映射关系。反之，为DRB不具备反转特性。进一步的，第一网络设备还可以通知第二网络设备中的SDAP实体的反转映射特性，若SDAP实体具备反转映射特性，则该SDAP实体关联的DRB都具备反转映射特性。其中，SDAP实体可关联一个或多个DRB，并负责数据包到关联DRB的映射。第二网络设备可决定采用reflective映射方式还是RRC信令方式通知终端设备QoS flow到DRB的映射关系。可选地，第二网络设备对可采用reflective映射方式配置映射关系的QoS flow采用reflective映射方式或RRC信令方式配置QoS flow到DRB的映射关系。对于不能采用reflective映射方式配置映射关系的QoS flow采用RRC信令方式配置QoS flow到DRB的映射关系。第二网络设备将采用reflective映射方式配置映射关系的 QoS flow映射到具备反转映射特性的DRB中。
可选的，第一网络设备通知第二网络设备在UL QoS flow可以在第二网络设备中传输，第二网络设备可决定采用reflective映射方式还是RRC信令方式通知终端设备QoS flow到DRB的映射关系。第二网络设备可认为所有QoS flow均可采用reflective映射方式配置映射关系，所有DRB均具备反转映射特性。
S1402、对于采用reflective映射方式配置QoS flow到DRB映射关系的QoS flow，第二网络设备可在下行数据中携带QoS flow ID等信息，通过reflective映射方式来通知终端设备产生上行QoS flow到DRB的映射关系。
S1403、终端设备读取SCG bearer或SCG split Bearer中的下行数据包中包含的QoS flow ID等信息，通过reflective映射方式来产生上行QoS flow到DRB的映射关系。
进一步的，本实施例还提供一种技术方案，用于进行QoS flow到DRB映射关系的更新。
一种可能更新方式：QoS flow在第二网络设备的DRB之间进行重映射。
可选地，第二网络设备通过RRC信令方式或reflective映射方式配置新的QoS flow到DRB的映射关系，终端设备收到新的QoS flow到DRB的映射关系，采用新的QoS flow到DRB的映射关系，执行QoS flow到DRB映射关系的更新。其中所述的RRC信令，可采用第二网络设备和终端设备之间的信令无线承载(signaling radio bearer，SRB)发送。
另一种可能更新方式：QoS flow在第二网络设备的DRB和第一网络设备的DRB之间进行重映射。
可选地，第一网络设备决定将某一QoS flow从第二网络设备迁移回第一网络设备，则第一网络设备发送消息到第二网络设备，指示将该QoS flow迁移回第一网络设备。
示例性的，通过RRC信令方式或reflective映射方式配置新的QoS flow到DRB的映射关系。其中DRB为第一网络设备的DRB，终端收到新的QoS flow到DRB的映射关系，采用新的QoS flow到DRB的映射关系，执行QoS flow到DRB映射关系的更新。若QoS flow在第二网络设备中的映射关系是通过reflective映射方式配置的，则终端可认为所述在第二网络设备中配置的QoS flow到DRB的映射关系是去激活的，不再生效。
同样的，第一网络设备决定将某一QoS flow从第一网络设备迁移到第二网络设备，采用同样的配置方式来为终端配置新的QoS flow到DRB的映射关系。
可选的，第二网络设备接收到的QoS flow可能来自第一网络设备，也可能直接来自由核心网设备。
网络设备或终端设备可以执行上述实施例中的部分或全部步骤，这些步骤或操作仅是示例，本发明实施例还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照上述实施例呈现的不同的顺序来执行，并且有可能并非要执行上述实施例中的全部操作。
本申请实施例再一方面还提供一种数据分流装置，用于执行上述实施例中的第一网络设备侧的数据分流方法，具有相同的技术特征和技术效果。
图10为本申请实施例提供的数据分流装置实施例一的结构示意图。该数据分流装置可以为上述任一实施例中的第一网络设备，该数据分流装置可以通过软件、硬件或者软硬件结合的方式实现。如图10所示，该数据分流装置可以包括：分流模块11和 发送模块12。
分流模块11，用于确定分组数据单元会话中待分流的QoS flow；
发送模块12，用于将待分流的QoS flow通过第一数据分流装置和第二数据分流装置之间的数据隧道发送至第二数据分流装置。
可选的，在图10所示实施例的基础上，图11为本申请实施例提供的数据分流装置实施例二的结构示意图。如图11所示，数据分流装置还包括：
数据隧道建立模块13，用于在第一数据分流装置与第二数据分流装置之间建立分组数据单元会话对应的数据隧道；
其中，发送模块12具体用于，将待分流的QoS flow通过待分流的QoS flow所属的分组数据单元会话所对应的数据隧道发送至第二数据分流装置。
可选的，参照图11，数据分流装置还包括：
数据隧道建立模块13，用于在第一数据分流装置与第二数据分流装置之间建立一条公共数据隧道；
其中，发送模块12具体用于，将待分流的QoS flow通过公共数据隧道发送至第二数据分流装置。
可选的，参照图11，数据分流装置还包括：
数据隧道建立模块13，用于根据待分流的QoS flow对应的数据无线承载DRB，在第一数据分流装置与第二数据分流装置之间建立DRB对应的数据隧道；
其中，发送模块12具体用于，将待分流的QoS flow通过QoS flow对应的DRB所对应的数据隧道发送至第二数据分流装置。
可选的，数据隧道建立模块13还用于，确定不存在待分流的QoS flow对应的数据隧道。
可选的，数据隧道建立模块13具体用于，
向第二数据分流装置发送第一消息，第一消息包括待分流的QoS flow所属的分组数据单元会话的标识和标识对应的数据隧道的第一隧道端点信息；
从第二数据分流装置上接收第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和数据隧道在第二数据分流装置侧的隧道端点标识。
可选的，在数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有QoS flow的标识。
可选的，数据隧道建立模块13具体用于，
向第二数据分流装置发送第一消息，第一消息包括公共数据隧道的第一隧道端点信息；
从第二数据分流装置上接收第二消息，第二消息包括公共数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和公共数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和公共数据隧道在第二数据分流装置侧的隧道端点标识。
可选的，在数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有QoS flow的标识和QoS flow所属的分组数据单元会话的标识。
可选的，数据隧道建立模块13具体用于，
向第二数据分流装置发送第一消息，第一消息包括待分流的QoS flow对应的DRB的标识和标识对应的数据隧道的第一隧道端点信息；
从第二数据分流装置上接收第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和数据隧道在第二数据分流装置侧的隧道端点标识。
可选的，如图11所示，数据分流装置还包括：接收模块14；
发送模块12还用于，向第二数据分流装置发送第三消息，第三消息包括待分流的QoS flow的QoS信息，以及待分流的QoS flow与DRB的映射关系；
接收模块14还用于，从第二数据分流装置上接收第四消息，第四消息包括第二数据分流装置能够接纳的QoS flow。
可选的，若根据待分流的QoS flow的标识，确定不存在待分流的QoS flow对应的DRB，则第三消息中还包括待分流的QoS flow对应的DRB的建立指示信息。
可选的，发送模块12还用于，向第二数据分流装置发送第三消息，第三消息包括待分流的QoS flow的QoS信息；
接收模块14，还用于从第二数据分流装置上接收第四消息，第四消息包括第二数据分流装置能够接纳的QoS flow。
可选的，发送模块12还用于，向第二数据分流装置发送第三消息，第三消息包括DRB的QoS信息；
接收模块14还用于，从第二数据分流装置上接收第四消息，第四消息包括第二数据分流装置能够接纳的DRB。
本申请实施例又一方面还提供一种数据分流装置，用于执行上述实施例中的第二网络设备侧的数据分流方法，具有相同的技术特征和技术效果。
图12为本申请实施例提供的数据分流装置实施例三的结构示意图。该数据分流装置可以为上述任一实施例中的第二网络设备，该数据分流装置可以通过软件、硬件或者软硬件结合的方式实现。如图12所示，该数据分流装置可以包括：接收模块21和发送模块22；
接收模块21，用于通过第一数据分流装置和第二数据分流装置之间数据隧道从第一数据分流装置上接收QoS flow；
发送模块22，用于确定QoS flow对应的DRB，将QoS flow通过对应的DRB发送至终端设备。
可选的，接收模块21还用于，从第一数据分流装置上接收第一消息，第一消息包括QoS flow所属的分组数据单元会话的标识和标识对应的数据隧道的第一隧道端点信息；
发送模块22还用于，向第一数据分流装置发送第二消息，第二消息包括标识对应的 数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和数据隧道在第二数据分流装置侧的隧道端点标识。
可选的，承载到QoS flow的数据包的封装头中携带有QoS flow的标识；发送模块22具体用于，根据数据隧道对应的分组数据单元会话的标识、QoS flow的标识，确定QoS flow对应的DRB。
可选的，接收模块21还用于，从第一数据分流装置上接收第一消息，第一消息包括公共数据隧道的第一隧道端点信息；
发送模块22还用于，向第一数据分流装置发送第二消息，第二消息包括公共数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和公共数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和公共数据隧道在第二数据分流装置侧的隧道端点标识。
可选的，承载到QoS flow的数据包的封装头中携带有QoS flow的标识和QoS flow所属的分组数据单元会话的标识；发送模块22具体用于，根据分组数据单元会话的标识和QoS flow的标识，确定QoS flow对应的DRB。
可选的，接收模块21还用于，从第一数据分流装置上接收第一消息，第一消息包括QoS flow对应的DRB的标识和标识对应的数据隧道的第一隧道端点信息；
发送模块22还用于，向第一数据分流装置发送第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一数据分流装置的传输层地址和数据隧道在第一数据分流装置侧的隧道端点标识；第二隧道端点信息包括第二数据分流装置的传输层地址和数据隧道在第二数据分流装置侧的隧道端点标识。
可选的，发送模块22具体用于，根据数据隧道对应的DRB，确定QoS flow对应的DRB。
可选的，接收模块21还用于，从第一数据分流装置上接收第三消息，第三消息包括QoS flow的QoS信息，以及QoS flow与DRB的映射关系；
发送模块22还用于，根据QoS flow的QoS信息，以及QoS flow与DRB的映射关系，确定能否接纳QoS flow；
若能，则向第一数据分流装置发送第四消息，第四消息用于指示第二数据分流装置接纳的QoS flow；
若否，则向第一数据分流装置发送第五消息，第五消息用于指示QoS flow接纳失败。
可选的，第三消息还包括QoS flow对应的DRB的建立指示信息。
可选的，接收模块21还用于，从第一数据分流装置上接收第三消息，第三消息包括QoS flow的QoS信息；
发送模块22还用于，根据QoS flow的QoS信息，确定能否接纳QoS flow；
若能，则配置QoS flow与DRB的映射关系，并向第一数据分流装置发送第四消息，第四消息用于指示第二数据分流装置接纳的QoS flow；
若否，则向第一数据分流装置发送第五消息，第五消息用于指示QoS flow接纳失败。
可选的，接收模块21还用于，从第一数据分流装置上接收第三消息，第三消息包括DRB的QoS信息；
发送模块22还用于，根据DRB的QoS信息，确定能否接纳DRB；
若能，则向第一数据分流装置发送第四消息，第四消息包括第二数据分流装置接纳的DRB；
若否，则向第一数据分流装置发送第五消息，第五消息用于指示DRB接纳失败。
可选的，数据分流装置包括：
接收模块21，用于从终端设备上接收分组数据单元会话中的至少一个QoS flow；
发送模块22，用于将各QoS flow通过各QoS flow对应的数据隧道发送至第一数据分流装置。
本申请实施例又一方面还提供一种网络设备，用于执行上述实施例中的第一网络设备侧的数据分流方法，具有相同的技术特征和技术效果。
图13为本申请实施例提供的网络设备实施例一的结构示意图。该网络设备可以包括存储器31、处理器32、至少一个通信总线33、发送器34和接收器35。通信总线33用于实现元件之间的通信连接。存储器31可能包含高速RAM存储器，也可能还包括非易失性存储NVM，例如至少一个磁盘存储器，存储器31中可以存储各种程序，用于完成各种处理功能以及实现本实施例的方法步骤。本实施例中，发送器34可以为基站中的射频处理模块或者基带处理模块，接收器33可以为基站中的射频处理模块或者基带处理模块。上述发送器34和接收器33可以分开设置，还可以集成在一起设置构成一个收发器，该发送器34和接收器33均可以耦合至所述处理器32。
具体的，本实施例中，处理器35，用于确定分组数据单元会话中待分流的QoS flow；
发送器34，用于将待分流的QoS flow通过第一网络设备和第二网络设备之间的数据隧道发送至第二网络设备。
可选的，处理器32用于在第一网络设备与第二网络设备之间建立分组数据单元会话对应的数据隧道；
其中，发送器34具体用于，将待分流的QoS flow通过待分流的QoS flow所属的分组数据单元会话所对应的数据隧道发送至第二网络设备。
可选的，处理器32用于在第一网络设备与第二网络设备之间建立一条公共数据隧道；
其中，发送器34具体用于，将待分流的QoS flow通过公共数据隧道发送至第二网络设备。
可选的，处理器32用于根据待分流的QoS flow对应的数据无线承载DRB，在第一网络设备与第二网络设备之间建立DRB对应的数据隧道；
其中，发送器34具体用于，将待分流的QoS flow通过待分流的QoS flow对应的DRB所对应的数据隧道发送至第二网络设备。
可选的，处理器32还用于，确定不存在待分流的QoS flow对应的数据隧道。
可选的，处理器32具体用于，
向第二网络设备发送第一消息，第一消息包括分组数据单元会话的标识和标识对应的数据隧道的第一隧道端点信息；
从第二网络设备上接收第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
可选的，在数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有QoS flow的标识。
可选的，处理器32具体用于，
向第二网络设备发送第一消息，第一消息包括公共数据隧道的第一隧道端点信息；
从第二网络设备上接收第二消息，第二消息包括公共数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和公共数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和公共数据隧道在第二网络设备侧的隧道端点标识
可选的，在数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有QoS flow的标识和QoS flow所属的分组数据单元会话的标识。
可选的，处理器32具体用于，
向第二网络设备发送第一消息，第一消息包括待分流的QoS flow对应的DRB的标识和标识对应的数据隧道的第一隧道端点信息；
从第二网络设备上接收第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
可选的，发送器34还用于，向第二网络设备发送第三消息，第三消息包括待分流的QoS flow的QoS信息，以及待分流的QoS flow与DRB的映射关系；
接收器35还用于，从第二网络设备上接收第四消息，第四消息包括第二网络设备能够接纳的QoS flow。
可选的，若处理器32根据待分流的QoS flow的标识，确定不存在待分流的QoS flow对应的DRB，则第三消息中还包括待分流的QoS flow对应的DRB的建立指示信息。
可选的，发送器34还用于，向第二网络设备发送第三消息，第三消息包括待分流的QoS flow的QoS信息；
接收器35，还用于从第二网络设备上接收第四消息，第四消息包括第二网络设备能够接纳的QoS flow。
可选的，发送器34还用于，向第二网络设备发送第三消息，第三消息包括DRB的QoS信息；
接收器35还用于，从第二网络设备上接收第四消息，第四消息包括第二网络设备能够接纳的DRB。
本申请实施例又一方面还提供一种网络设备，用于执行上述实施例中的第二网络设备侧的数据分流方法，具有相同的技术特征和技术效果。
图14为本申请实施例提供的网络设备实施例二的结构示意图。该网络设备可以包括存储器41、处理器42、至少一个通信总线43、发送器44和接收器45。通信总线44用于实现元件之间的通信连接。存储器41可能包含高速RAM存储器，也可能还包括非易失性存储NVM，例如至少一个磁盘存储器，存储器41中可以存储各种程序，用于完成各种处理功能以及实现本实施例的方法步骤。本实施例中，发送器44可以为基站中的射频处理模块或者基带处理模块，接收器44可以为基站中的射频处理模块或者基带处理模块。上述发送器44和接收器44可以分开设置，还可以集成在一起设置构成一个收发器，该发送器44和接收器44均可以耦合至所述处理器42。
具体的，本实施例中，接收器45，用于通过第一网络设备和第二网络设备之间数据隧道从第一网络设备上接收QoS flow；
发送器44，用于确定QoS flow对应的DRB，将QoS flow通过对应的DRB发送至终端设备。
可选的，接收器45还用于，从第一网络设备上接收第一消息，第一消息包括QoS flow所属的分组数据单元会话的标识和标识对应的数据隧道的第一隧道端点信息；
发送器44还用于，向第一网络设备发送第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
可选的，承载到QoS flow的数据包的封装头中携带有QoS flow的标识；发送器44具体用于，根据数据隧道对应的分组数据单元会话的标识、QoS flow的标识，确定QoS flow对应的DRB。
可选的，接收器45还用于，从第一网络设备上接收第一消息，第一消息包括公共数据隧道的第一隧道端点信息；
发送器44还用于，向第一网络设备发送第二消息，第二消息包括公共数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和公共数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和公共数据隧道在第二网络设备侧的隧道端点标识。
可选的，承载到QoS flow的数据包的封装头中携带有QoS flow的标识和QoS flow所属的分组数据单元会话的标识；发送器44具体用于，根据分组数据单元会话的标识和QoS flow的标识，确定QoS flow对应的DRB。
可选的，接收器45还用于，从第一网络设备上接收第一消息，第一消息包括QoS flow对应的DRB的标识和标识对应的数据隧道的第一隧道端点信息；
发送器44还用于，向第一网络设备发送第二消息，第二消息包括标识对应的数据隧道的第二隧道端点信息；
其中，第一隧道端点信息包括第一网络设备的传输层地址和数据隧道在第一网络设备侧的隧道端点标识；第二隧道端点信息包括第二网络设备的传输层地址和数据隧道在第二网络设备侧的隧道端点标识。
可选的，发送器44具体用于，根据数据隧道对应的DRB，确定QoS flow对应的DRB。
可选的，接收器45还用于，从第一网络设备上接收第三消息，第三消息包括QoS flow的QoS信息，以及QoS flow与DRB的映射关系；
发送器44还用于，根据QoS flow的QoS信息，以及QoS flow与DRB的映射关系，确定能否接纳QoS flow；
若能，则向第一网络设备发送第四消息，第四消息用于指示第二网络设备接纳的QoS flow；
若否，则向第一网络设备发送第五消息，第五消息用于指示QoS flow接纳失败。
可选的，第三消息还包括QoS flow对应的DRB的建立指示信息。
可选的，接收器45还用于，从第一网络设备上接收第三消息，第三消息包括QoS flow的QoS信息；
发送器44还用于，根据QoS flow的QoS信息，确定能否接纳QoS flow；
若能，则配置QoS flow与DRB的映射关系，并向第一网络设备发送第四消息，第四消息用于指示第二网络设备接纳的QoS flow；
若否，则向第一网络设备发送第五消息，第五消息用于指示QoS flow接纳失败。
可选的，接收器45还用于，从第一网络设备上接收第三消息，第三消息包括DRB的QoS信息；
发送器44还用于，根据DRB的QoS信息，确定能否接纳DRB；
若能，则向第一网络设备发送第四消息，第四消息包括第二网络设备接纳的DRB；
若否，则向第一网络设备发送第五消息，第五消息用于指示DRB接纳失败。
可选的，第二网络设备包括：
接收器45，用于从终端设备上接收分组数据单元会话中的至少一个QoS flow；
发送器44，用于将各QoS flow通过各QoS flow对应的数据隧道发送至第一网络设备。
本申请实施例又一方面还提供了一种通信系统，包括核心网设备和上述任一实施例中所述的第一网络设备。
可选的，通信系统还包括上述任一实施例中所述的第二网络设备。
本申请实施例又一方面还提供了一种计算机存储介质，用于储存上述第一网络设备所用的计算机软件指令，其包含用于执行上述任一实施例中的第一网络设备侧的方法的程序。本申请实施例还提供一种计算机程序产品，其包含指令，当计算机程序被计算机所执行时，该指令使得计算机执行上述第一网络设备所执行的功能。
本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持第一网络设备实现上述任一实施例中所涉及的功能，例如，生成或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，该芯片系统还包括存储器，所述存储器，用于保存第一网络设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请实施例又一方面还提供了一种计算机存储介质，用于储存上述第二网络设 备所用的计算机软件指令，其包含用于执行上述任一实施例中的第二网络设备侧的方法的程序。本申请实施例还提供一种计算机程序产品，其包含指令，当计算机程序被计算机所执行时，该指令使得计算机执行第二网络设备所执行的功能。
本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持第二网络设备实现上述任一实施例中所涉及的功能，例如，生成或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，该芯片系统还包括存储器，所述存储器，用于保存第二网络设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本发明各方法实施例之间相关部分可以相互参考；各装置实施例所提供的装置用于执行对应的方法实施例所提供的方法，故各装置实施例可以参考相关的方法实施例中的相关部分进行理解。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关硬件来完成，所述的程序可以存储于一个设备的可读存储介质中，该程序在执行时，包括上述全部或部分步骤，所述的存储介质，如：FLASH、EEPROM等。
另外，需要说明的是，应理解以上核心网设备、网络设备的各个模块的划分仅仅是一种逻辑功能的划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。

Claims (30)

  1. 一种数据分流方法，其特征在于，包括：
    第一网络设备确定分组数据单元会话中待分流的QoS flow；
    所述第一网络设备将所述待分流的QoS flow通过所述第一网络设备和第二网络设备之间的数据隧道发送至所述第二网络设备。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备在所述第一网络设备与所述第二网络设备之间建立所述分组数据单元会话对应的数据隧道；
    其中，所述第一网络设备将所述待分流的QoS flow通过所述第一网络设备和第二网络设备之间的数据隧道发送至所述第二网络设备，包括：
    所述第一网络设备将所述待分流的QoS flow通过所述分组数据单元会话所对应的数据隧道发送至第二网络设备。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备在所述第一网络设备与所述第二网络设备之间建立一条公共数据隧道；
    其中，所述第一网络设备将所述待分流的QoS flow通过所述第一网络设备和所述第二网络设备之间的数据隧道发送至所述第二网络设备，包括：
    所述第一网络设备将所述待分流的QoS flow通过所述公共数据隧道发送至所述第二网络设备。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备根据所述待分流的QoS flow对应的数据无线承载DRB，在所述第一网络设备与所述第二网络设备之间建立所述DRB对应的数据隧道；
    其中，所述第一网络设备将所述待分流的QoS flow通过所述第一网络设备和第二网络设备之间的数据隧道发送至所述第二网络设备，包括：
    所述第一网络设备将所述待分流的QoS flow通过所述待分流的QoS flow对应的DRB所对应的数据隧道发送至所述第二网络设备。
  5. 根据权利要求2所述的方法，其特征在于，所述第一网络设备在所述第一网络设备与所述第二网络设备之间建立所述分组数据单元会话对应的数据隧道，包括：
    所述第一网络设备向所述第二网络设备发送第一消息，所述第一消息包括所述分组数据单元会话的标识和所述标识对应的数据隧道的第一隧道端点信息；
    所述第一网络设备从所述第二网络设备上接收第二消息，所述第二消息包括所述标识对应的数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述数据隧道在所述第二网络设备侧的隧道端点标识。
  6. 根据权利要求1、2或5中任一项所述的方法，其特征在于，在所述数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有所述待分流的QoS flow的标识。
  7. 根据权利要求3所述的方法，其特征在于，所述第一网络设备在所述第一网络设备与所述第二网络设备之间建立一条公共数据隧道，包括：
    所述第一网络设备向所述第二网络设备发送第一消息，所述第一消息包括所述公共数据隧道的第一隧道端点信息；
    所述第一网络设备从所述第二网络设备上接收第二消息，所述第二消息包括所述公共数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述公共数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述公共数据隧道在所述第二网络设备侧的隧道端点标识。
  8. 根据权利要求1、3或7中任一项所述的方法，其特征在于，在所述数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有所述待分流的QoS flow的标识和所述分组数据单元会话的标识。
  9. 根据权利要求4所述的方法，其特征在于，所述第一网络设备根据所述待分流的QoS flow对应的DRB，在所述第一网络设备与所述第二网络设备之间建立所述DRB对应的数据隧道，包括：
    所述第一网络设备向所述第二网络设备发送第一消息，所述第一消息包括所述待分流的QoS flow对应的DRB的标识和所述标识对应的数据隧道的第一隧道端点信息；
    所述第一网络设备从所述第二网络设备上接收第二消息，所述第二消息包括所述标识对应的数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述数据隧道在所述第二网络设备侧的隧道端点标识。
  10. 一种数据分流方法，其特征在于，包括：
    第二网络设备通过第一网络设备和所述第二网络设备之间数据隧道从所述第一网络设备上接收QoS flow；
    所述第二网络设备确定所述QoS flow对应的DRB，将所述QoS flow通过所述QoS flow对应的DRB发送至终端设备。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备从所述第一网络设备上接收第一消息，所述第一消息包括所述QoS flow所属的分组数据单元会话的标识和所述标识对应的数据隧道的第一隧道端点信息；
    所述第二网络设备向所述第一网络设备发送第二消息，所述第二消息包括所述标识对应的数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述数据隧道在所述第二网络设备侧的隧道端点标识。
  12. 根据权利要求11所述的方法，其特征在于，承载到所述QoS flow的数据包的封装头中携带有所述QoS flow的标识；所述第二网络设备确定所述QoS flow对应的DRB，包括：
    所述第二网络设备根据所述数据隧道对应的分组数据单元会话的标识、所述QoS flow 的标识，确定所述QoS flow对应的DRB。
  13. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备从所述第一网络设备上接收第一消息，所述第一消息包括公共数据隧道的第一隧道端点信息；
    所述第二网络设备向所述第一网络设备发送第二消息，所述第二消息包括所述公共数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述公共数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述公共数据隧道在所述第二网络设备侧的隧道端点标识。
  14. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备从所述第一网络设备上接收第一消息，所述第一消息包括所述QoS flow对应的DRB的标识和所述标识对应的数据隧道的第一隧道端点信息；
    所述第二网络设备向所述第一网络设备发送第二消息，所述第二消息包括所述标识对应的数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述数据隧道在所述第二网络设备侧的隧道端点标识。
  15. 一种数据分流方法，其特征在于，包括：
    第二网络设备从终端设备上接收分组数据单元会话中的QoS flow；
    所述第二网络设备将所述QoS flow通过所述QoS flow对应的数据隧道发送至第一网络设备。
  16. 一种数据分流装置，所述数据分流装置为第一网络设备，其特征在于，所述装置包括：
    分流模块，用于确定分组数据单元会话中待分流的QoS flow；
    发送模块，用于将所述待分流的QoS flow通过所述第一网络设备和第二网络设备之间的数据隧道发送至所述第二网络设备。
  17. 根据权利要求16所述的装置，其特征在于，所述装置还包括：
    数据隧道建立模块，用于在所述第一网络设备与所述第二网络设备之间建立所述分组数据单元会话对应的数据隧道；
    其中，发送模块具体用于，将所述待分流的QoS flow通过所述分组数据单元会话所对应的数据隧道发送至第二网络设备。
  18. 根据权利要求16所述的装置，其特征在于，所述装置还包括：
    数据隧道建立模块，用于在所述第一网络设备与所述第二网络设备之间建立一条公共数据隧道；
    其中，发送模块具体用于，将所述待分流的QoS flow通过所述公共数据隧道发送至所述第二网络设备。
  19. 根据权利要求16所述的装置，其特征在于，所述装置还包括：
    数据隧道建立模块，用于根据所述待分流的QoS flow对应的数据无线承载DRB，在所述第一网络设备与所述第二网络设备之间建立所述DRB对应的数据隧道；
    其中，发送模块具体用于，将所述待分流的QoS flow通过所述待分流的QoS flow对应的DRB所对应的数据隧道发送至所述第二网络设备。
  20. 根据权利要求17所述的装置，其特征在于，所述数据隧道建立模块具体用于，向所述第二网络设备发送第一消息，所述第一消息包括所述分组数据单元会话的标识和所述标识对应的数据隧道的第一隧道端点信息；
    从所述第二网络设备上接收第二消息，所述第二消息包括所述标识对应的数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述数据隧道在所述第二网络设备侧的隧道端点标识。
  21. 根据权利要求16、17或20中任一项所述的装置，其特征在于，在所述数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有所述QoS flow的标识。
  22. 根据权利要求18所述的装置，其特征在于，所述数据隧道建立模块具体用于，向所述第二网络设备发送第一消息，所述第一消息包括所述公共数据隧道的第一隧道端点信息；
    从所述第二网络设备上接收第二消息，所述第二消息包括所述公共数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述公共数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述公共数据隧道在所述第二网络设备侧的隧道端点标识。
  23. 根据权利要求16、18或22中任一项所述的装置，其特征在于，在所述数据隧道中传输的承载到所述待分流的QoS flow的数据包的封装头中携带有所述QoS flow的标识和所述分组数据单元会话的标识。
  24. 根据权利要求19所述的装置，其特征在于，所述数据隧道建立模块具体用于，向所述第二网络设备发送第一消息，所述第一消息包括所述待分流的QoS flow对应的DRB的标识和所述标识对应的数据隧道的第一隧道端点信息；
    从所述第二网络设备上接收第二消息，所述第二消息包括所述标识对应的数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述数据隧道在所述第二网络设备侧的隧道端点标识。
  25. 一种数据分流装置，所述数据分流装置为第二网络设备，其特征在于，所述装置包括：
    接收模块，用于通过第一网络设备和所述第二网络设备之间数据隧道从所述第一网络设备上接收QoS flow；
    发送模块，用于在所述QoS flow对应的DRB，将所述QoS flow通过所述QoS flow对应的DRB发送至终端设备。
  26. 根据权利要求25所述的装置，其特征在于，所述接收模块还用于，从所述第一网络设备上接收第一消息，所述第一消息包括所述QoS flow所属的分组数据单元会话的标 识和所述标识对应的数据隧道的第一隧道端点信息；
    所述发送模块还用于，向所述第一网络设备发送第二消息，所述第二消息包括所述标识对应的数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述数据隧道在所述第二网络设备侧的隧道端点标识。
  27. 根据权利要求25所述的装置，其特征在于，承载到所述QoS flow的数据包的封装头中携带有所述QoS flow的标识；所述发送模块具体用于，根据所述数据隧道对应的分组数据单元会话的标识、所述QoS flow的标识，确定所述QoS flow对应的DRB。
  28. 根据权利要求25所述的装置，其特征在于，所述接收模块还用于，从所述第一网络设备上接收第一消息，所述第一消息包括公共数据隧道的第一隧道端点信息；
    所述发送模块还用于，向所述第一网络设备发送第二消息，所述第二消息包括所述公共数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述公共数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述公共数据隧道在所述第二网络设备侧的隧道端点标识。
  29. 根据权利要求25所述的装置，其特征在于，所述发送模块还用于，从所述第一网络设备上接收第一消息，所述第一消息包括所述QoS flow对应的DRB的标识和所述标识对应的数据隧道的第一隧道端点信息；
    所述发送模块还用于，向所述第一网络设备发送第二消息，所述第二消息包括所述标识对应的数据隧道的第二隧道端点信息；
    其中，所述第一隧道端点信息包括所述第一网络设备的传输层地址和所述数据隧道在所述第一网络设备侧的隧道端点标识；所述第二隧道端点信息包括所述第二网络设备的传输层地址和所述数据隧道在所述第二网络设备侧的隧道端点标识。
  30. 一种数据分流装置，所述数据分流装置为第二网络设备，其特征在于，所述装置包括：
    接收模块，用于从终端设备上接收分组数据单元会话中的QoS flow；
    发送模块，用于将所述QoS flow通过所述QoS flow对应的数据隧道发送至第一网络设备。
PCT/CN2018/090592 2017-06-16 2018-06-11 数据分流方法和装置 WO2018228311A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710459808.XA CN109246756A (zh) 2017-06-16 2017-06-16 数据分流方法和装置
CN201710459808.X 2017-06-16

Publications (1)

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

Family

ID=64659548

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/090592 WO2018228311A1 (zh) 2017-06-16 2018-06-11 数据分流方法和装置

Country Status (2)

Country Link
CN (1) CN109246756A (zh)
WO (1) WO2018228311A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111510949B (zh) * 2019-01-30 2023-05-05 中国移动通信有限公司研究院 一种数据传输方法、装置和存储介质
CN112788680B (zh) * 2019-11-07 2022-07-29 华为技术有限公司 一种数据传输的方法及相关设备
CN114698145A (zh) * 2020-12-29 2022-07-01 华为技术有限公司 用于传输数据的方法和装置
CN115988568B (zh) * 2023-03-14 2023-08-15 阿里巴巴（中国）有限公司 专网设备、数据处理方法、车辆控制方法及设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102984759A (zh) * 2011-09-06 2013-03-20 华为技术有限公司 数据传输方法和设备
US20130265879A1 (en) * 2012-04-05 2013-10-10 Zu Qiang Qci based offloading
CN103945461A (zh) * 2013-01-23 2014-07-23 中兴通讯股份有限公司 数据多流传输方法及装置
WO2015143607A1 (zh) * 2014-03-24 2015-10-01 华为技术有限公司 回程链路的承载分流方法及网络设备
WO2016120691A1 (en) * 2015-01-29 2016-08-04 Huawei Technologies Co., Ltd. Method,apparatus and machine readable medium for traffic engineering in communications network having quality of service flows and best effort flows

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102984759A (zh) * 2011-09-06 2013-03-20 华为技术有限公司 数据传输方法和设备
US20130265879A1 (en) * 2012-04-05 2013-10-10 Zu Qiang Qci based offloading
CN103945461A (zh) * 2013-01-23 2014-07-23 中兴通讯股份有限公司 数据多流传输方法及装置
WO2015143607A1 (zh) * 2014-03-24 2015-10-01 华为技术有限公司 回程链路的承载分流方法及网络设备
WO2016120691A1 (en) * 2015-01-29 2016-08-04 Huawei Technologies Co., Ltd. Method,apparatus and machine readable medium for traffic engineering in communications network having quality of service flows and best effort flows

Also Published As

Publication number Publication date
CN109246756A (zh) 2019-01-18

Similar Documents

Publication Publication Date Title
US10869324B2 (en) Communication method based on a CU-DU architecture
EP3606149B1 (en) Data transmission method, access network device, terminal and communications system
CN110235463B (zh) 在无线通信系统中执行反映服务质量(QoS)的方法及其设备
EP3793240A1 (en) Configuration method, data transmission method and apparatus
WO2019242747A1 (zh) 数据包的发送、接收方法及装置和数据包的传输系统
KR102463964B1 (ko) 전송 방법 및 네트워크 장치
US20200100102A1 (en) Method and apparatus for supporting security for cu-cp and cu-up separation in wireless communication system
WO2017054538A1 (zh) 建立辅助信令链路的方法及其装置、基站及终端
WO2018228311A1 (zh) 数据分流方法和装置
EP3637846A1 (en) Method and device for use in configuring novel quality of service architecture in dual connectivity system
JP7038815B2 (ja) 通信方法および通信デバイス
WO2017020253A1 (zh) 用于辅基站切换的方法、网络设备和用户设备
US20200178138A1 (en) Communication method, base station, terminal device, and system
WO2014012410A1 (zh) 一种数据传输方法、装置及通信系统
CN109587825B (zh) 建立连接的方法、请求辅助小区组配置的方法及相应的基站
JP2021510283A (ja) ノードおよび通信方法
WO2016191963A1 (zh) 一种建立承载的方法、用户设备及基站
US11528773B2 (en) Terminal apparatus, base station apparatus, communication method, and integrated circuits for configuring a service data adaptation protocol function
WO2020001064A1 (zh) 数据处理方法及装置
US20220225209A1 (en) Data packet transmission method and apparatus
WO2018059269A1 (zh) 消息的识别方法和装置
WO2020063867A1 (zh) 一种切换方法及基站
WO2021026706A1 (zh) 一种f1接口管理方法及装置
CN113473525B (zh) 一种数据传输的方法及装置
WO2020042986A1 (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: 18818250

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18818250

Country of ref document: EP

Kind code of ref document: A1