WO2018165982A1 - 一种发送结束标记的方法 - Google Patents

一种发送结束标记的方法 Download PDF

Info

Publication number
WO2018165982A1
WO2018165982A1 PCT/CN2017/077123 CN2017077123W WO2018165982A1 WO 2018165982 A1 WO2018165982 A1 WO 2018165982A1 CN 2017077123 W CN2017077123 W CN 2017077123W WO 2018165982 A1 WO2018165982 A1 WO 2018165982A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
user plane
plane path
source user
path
Prior art date
Application number
PCT/CN2017/077123
Other languages
English (en)
French (fr)
Inventor
朱强华
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP17900529.3A priority Critical patent/EP3589019B1/en
Priority to PCT/CN2017/077123 priority patent/WO2018165982A1/zh
Priority to CN201780084718.5A priority patent/CN110226344B/zh
Publication of WO2018165982A1 publication Critical patent/WO2018165982A1/zh
Priority to US16/573,433 priority patent/US11140602B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H04W40/36—Modification of an existing route due to handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices

Definitions

  • the present application relates to the field of communications, and in particular, to a method for transmitting an end tag, a control plane node, a user plane gateway, an access gateway, and an access network node.
  • the user plane reselection of the user equipment occurs in the handover process, for example, the UE switches from the source base station to the target base station, and at this time, the UE
  • the user plane gateway (service gateway/packet data network gateway) does not change, that is, the user plane gateway on the source user plane path is the same as the user plane gateway on the target user plane path.
  • the user plane gateway immediately sends an end marker on the source user plane path to indicate that the downlink data is sent on the source user plane path. Then, the downlink data sent by the data network is transmitted to the UE through the target user plane path.
  • the core network control plane can select an edge gateway for the local data stream of the UE by path reselection, so that the local data stream is routed to The UE, the user plane gateway, has changed.
  • the local data stream can reach the UE through the Internet; after the path reselection, the local data stream can directly reach the UE through the edge gateway, thereby avoiding the Internet delay and reducing the transmission delay of the local data stream.
  • the local data stream is a data packet sent by the local network.
  • the path reselection process of the UE may include the two scenarios shown in FIG. 1 and FIG.
  • the UE switches from a source access network (AN) node to a target AN node, and switches the UE from a User Plane Gateway (UP GW) to an edge gateway.
  • AN source access network
  • UP GW User Plane Gateway
  • the control plane node selects a more effective data path for the local data stream of the UE, does not change the AN node of the UE, and only changes the user plane gateway in the core network to be closer to the local network.
  • the embodiment of the present application provides a method for sending an end tag, which is used by the user plane gateway to determine when to send an end tag according to the trigger information, so as to perform a sorting process on the downlink data packet received on the target user plane path according to the end tag.
  • a first aspect of the present application provides a method for sending an end tag, which may include: the method may be applied in a process of user plane path switching of a UE, and the control plane CP node selects an edge gateway according to a path switching request or a handover notification.
  • the control plane CP node sends a session update request to the edge gateway; the control plane CP node receives the session update response fed back by the edge gateway, and the session update response includes the identifier ID of the source user plane path of the user equipment UE or the target user plane path of the UE ID, the source user plane path includes a user plane gateway UP GW, the target user plane path includes an edge gateway; the CP node sends a trigger information and an ID of the source user plane path to the UP GW according to the session update response, The trigger information and the ID of the source user plane path are used by the UP GW to send an end tag to the access network AN node on the source user plane path.
  • the source user plane path and the target user plane path are the same as the AN node
  • the source user plane path is a path including the UE, the AN, the UP GW, and the access gateway Access GW
  • the target user plane path includes the UE, the AN, and the edge gateway Edge.
  • GW the path of the Access GW
  • the source user plane path is a path including the UE, the AN1, the UP GW, and the Access GW
  • the target user plane path is the UE.
  • the CP node may send the trigger information and the ID of the source user plane path to the UP GW according to the session update response, and then the UP GW may determine when the sending ends according to the trigger information and the ID of the source user plane path. Marked, thereby reducing the probability of loss of downlink data packets on the source user plane path due to user plane path switching of the UE, and the effective auxiliary AN or target AN performs downlink data packets received on the target user plane path. Sort processing.
  • the trigger information may include at least one of a first service flow template and a timer parameter.
  • the triggering information is further described, and the foregoing provides a plurality of optional implementation manners.
  • the triggering information may include the first service flow template, or the first service flow template and the timer parameter, or The timer parameter, or other indication identifier, etc., the first service flow template is used to identify the end packet.
  • the method may further include: the CP node may select an edge gateway according to the path switching request, the application request, or the user plane report, where the CP node further needs to send a flow switching indication to the AN node.
  • a message, the flow switching indication message includes an ID of the source user plane path, where the flow switching indication message is used to indicate that the AN node determines downlink data received by the AN node on the source user plane path when receiving the end tag. Whether the packet has been successfully sent to the UE.
  • the source node surface path is the first bearer between the AN node and the UE
  • the target user plane path is the AN node.
  • a second bearer is between the UE and the UE.
  • the downlink data packet received by the AN node may include a local data stream or a data stream transmitted by the local network through the Internet, and the Internet data stream is a data packet sent by the Internet, because the present application
  • the embodiment is directed to the path switching of the local data stream, but the AN node cannot identify the local data stream. If the local data stream on the source user plane path is not successfully sent to the UE, the AN node is based on the target user plane path. When the end tag sorts the received downlink data packets, the local data flow on the source user plane path is lost. Therefore, when the AN node receives the flow switching indication message, it can be between the AN node and the UE.
  • the downlink data packet (local data stream and/or Internet data stream) received by the AN node on the source user plane path is successfully transmitted to the UE, and then the AN node is ensured on the path of the source user plane. Local data stream is not available If it is lost, the downlink packets received on the target user plane path are sorted according to the end tag.
  • a branch node may be selected in the core network when the path switching resource is prepared, and the local data stream is identified by the branch node.
  • the shunt node is described by the UP GW.
  • the method may further include: the CP node sending a first flow switching indication message to the AN node, where the first flow switching indication message includes an ID of the source user plane path, where the first flow switching indication message is used to indicate that the AN node is to the UP
  • the GW sends the downlink data packet received by the AN node on the source user plane path; because the AN node cannot identify the local data stream, the CP node sends the first stream handover indication message to the AN node for the AN node to be at the source.
  • the downlink data packet received on the user plane path is forwarded to the UP GW for identification; the CP node also sends a second flow switching indication message to the UP GW, where the second flow switching indication message includes the ID and the path of the source user plane path.
  • a second service flow template the second flow switching indication message is used to indicate, by the UP GW, the downlink data packet received by the UP GW on the source user plane path according to the ID of the second service flow template and the source user plane path.
  • the data packet sent by the local network is identified, and the identified data packet is sent to the edge gateway, where the edge gateway is located on the target user plane path.
  • the source node surface path is the first bearer between the AN node and the UE
  • the target user plane path is the AN node.
  • a second bearer is between the UE and the UE.
  • a split node UP GW is selected for identification, and the CP node sends the first flow switching indication to the AN node.
  • the message is for the AN node to forward the downlink data packet received on the source user plane path to the UP GW for identification.
  • the UP GW does not identify the service flow template of the local data stream, so the CP node sends the message to the UP GW.
  • the AN node can send the local data stream to the UE on the second bearer.
  • the AN node also receives an end tag on the source user plane path.
  • the AN node stops forwarding the downlink data packet received on the source user plane path to the UP GW, and then ends the tag.
  • the UP GW forwards the end tag to the edge gateway, and the edge gateway forwards back to the AN node. Then, the AN node can sort the downlink data packets received on the target user plane path according to the end tag.
  • the solution provided herein is that the AN can identify the local data stream
  • the method may further include: the CP node to the AN node.
  • Sending a flow switching indication message where the flow switching indication message includes an ID of the second service flow template and the source user plane path, where the flow switching indication message is used to indicate that the AN node is based on the second service flow template and the source user plane path
  • the ID identifies the data packet sent by the local network from the downlink data packet received by the AN node on the source user plane path, and sends the identified data packet to the UE through the target DRB, where the target DRB is The transmission path between the UE and the AN node on the target user plane path.
  • the source node surface path is the first bearer between the AN node and the UE
  • the target user plane path is the AN node.
  • a second bearer is between the UE and the UE.
  • the target DRB is the second bearer here.
  • the CP node may send a flow switching indication message to the AN node, where the flow switching indication message includes the second service flow template and the ID of the source user plane path, then the AN node may according to the second service flow.
  • Template And identifying the local data stream from the downlink data packet received on the source user plane path, and sending the identified local data stream to the UE by using the second bearer between the UE and the AN The application embodiment is simple and convenient, and is easy to implement. The delay of forwarding the source user plane path to the branch node for identification is reduced, and the AN node directly recognizes and sends the delay to the UE, and the AN node can effectively target the target user according to the end tag.
  • the downlink packets received on the path are sorted.
  • the second aspect of the embodiment of the present application provides a method for sending an end tag, which may include: the user plane gateway UP GW receives the trigger information sent by the control plane CP node and the identifier ID of the source user plane path of the user equipment UE, the UP GW Located on the source user plane path; the UP GW sends an end tag to the access network AN node on the source user plane path according to the trigger information and the ID of the source user plane path.
  • the source user plane path and the target user plane path are the same as the AN node
  • the source user plane path is a path including the UE, the AN, the UP GW, and the access gateway Access GW
  • the target user plane path includes the UE, the AN, and the edge gateway Edge.
  • GW the path of the Access GW
  • the source user plane path is a path including the UE, the AN1, the UP GW, and the Access GW
  • the target user plane path is the UE.
  • the UP GW receives the trigger information sent by the CP node and the ID of the source user plane path.
  • the UP GW may send an end tag to the AN node. It is.
  • the UP GW may determine when to send an end tag to the AN node according to the trigger information and the ID of the source user plane path, and the end tag may indicate that the local data stream transmitted on the source user plane path has been transmitted, so the UE is lowered.
  • the probability of loss of downstream packets on the source user plane path after the user's face is switched.
  • the trigger information includes at least one of a first service flow template and a timer parameter.
  • the triggering information is further described, and the foregoing provides a plurality of optional implementation manners.
  • the triggering information may include the first service flow template, or the first service flow template and the timer parameter, or The timer parameter, or other indication identifier, etc., the first service flow template is used to identify the end packet.
  • the trigger information includes the first service flow template
  • the UP GW sends an AN node to the source user plane path according to the trigger information and the ID of the source user plane path.
  • the sending end tag may include: when the IP quintuple information of the downlink data packet of the UE received by the UP GW is the same as any one of the IP quintuple information in the first service flow template, the UP GW according to the source The ID of the user plane path on which the end tag is sent to the AN node.
  • the first service flow template includes at least one IP quintuple information, which is used to filter the end data packet.
  • an implementation scheme of the UP GW sending end tag is provided.
  • the UP GW receives the downlink data packet transmitted to the UE on the source user plane path.
  • the trigger information is the first service flow template
  • the UP GW The IP quintuple information of the received downlink data packet may be determined.
  • the end data is received. Packet, then, the UP GW can send an end tag to the AN node to indicate that the local data stream is transmitted on the source user plane path.
  • the trigger information includes the timer parameter
  • the UP GW sends an end to the AN node on the source user plane path according to the trigger information and the ID of the source user plane path.
  • the marking may include: the UP GW setting a timer according to the timer parameter; when the UP GW receives the timer parameter, the UP GW The timer can be started; when the timer expires, the UP GW sends the end tag to the AN node on the source user plane path according to the ID of the source user plane path.
  • the parameters of the timer are usually an empirical value.
  • the UP GW may set a timer according to the timer parameter, and when the timer is set, the timer receives After the downlink data packet, the timer is reset, indicating that there is still data in the source user plane path until the downlink data packet is not received, and the timer expires. Then, the UP GW can send an end tag to the AN node. It indicates that the data packet transmitted on the source user plane path has been transmitted.
  • the trigger information includes the first service flow template and the timer parameter
  • the UP GW is in the source user plane according to the trigger information and the ID of the source user plane path.
  • the sending the end tag to the AN node on the path may include: when the IP quintuple information of the downlink data packet of the UE received by the UP GW is the same as any IP quintuple information in the first service flow template, The UP GW starts a timer, and the timer is set according to the timer parameter; if the UP GW receives the end packet and the timer does not time out, the UP GW restarts the timer, and the IP of the end packet is terminated.
  • the quintuple information is the same as any IP quintuple information in the first service flow template, or if the UP GW receives other downlink data packets, the UP GW restarts the timer; when the timer expires The UP GW sends the end tag to the AN node according to the ID of the source user plane path.
  • the first service flow template includes at least one IP quintuple information, which is used to filter the end data packet.
  • the determining condition of the UP GW sending the end tag includes the first service flow template and the timer parameter, and the timer may be set according to the timer parameter.
  • the inbound gateway sends a plurality of end packets in this embodiment in order to ensure the reliability of the transmitted data.
  • the UP GW receives the first end packet, the UP GW needs to start the timer. Then, if other technical data packets or downlink data packets are received within the timeout period of the timer, the timer needs to be restarted.
  • the timer expires, it indicates that the downlink data packet on the source user plane is transmitted, and the end tag can be sent to the AN node according to the ID of the source user plane path.
  • a branch node may be selected in the core network when the path switching resource is prepared, and the local data stream is identified by the branch node.
  • the offloading node is described by the UP GW.
  • the method may further include: receiving, by the UP GW, a flow switching indication message sent by the CP node, where the flow switching indication message includes an ID of the source user plane path and a second service flow template;
  • the UP GW identifies, according to the ID of the second service flow template and the source user plane path, a data packet sent by the local network from the downlink data packet sent by the AN node on the source user plane path; the UP GW is edge-to-edge
  • the gateway sends the identified data packet, and the edge gateway is located on the target user plane path of the UE.
  • the source node surface path is the first bearer between the AN node and the UE
  • the target user plane path is the AN node.
  • a second bearer is between the UE and the UE.
  • a split node UP GW is selected for identification, and the CP node sends the second stream to the UP GW.
  • the AN node forwards the local data flow to the edge gateway, and the edge gateway forwards the node back to the AN node.
  • the AN node can send the local data stream to the UE on the second bearer. It should be noted that the AN node is at the source. The end tag is also received on the user plane path.
  • the AN node stops forwarding the downlink data packet received on the source user plane path to the UP GW, and then forwards the end tag to the UP GW, and the UP GW will end.
  • the tag is forwarded to the edge gateway, and the edge gateway forwards back to the AN node. Then, the AN node can sort the downlink data packets received on the target user plane path according to the end tag.
  • a third aspect of the embodiments of the present application provides a method for sending an end tag, which may include: the method may be applied in a process of user plane path switching of a UE, where an access gateway Access GW receives a path switch notification, where the path switch notification includes The service flow template, where the path switch notification may further indicate that the Access GW next needs to send a downlink data packet to the edge gateway; the Access GW sends an end data packet to the UP GW according to the service flow template.
  • the first service flow template includes at least one IP quintuple information.
  • the source user plane path and the target user plane path are the same as the AN node
  • the source user plane path is a path including the UE, the AN, the UP GW, and the access gateway Access GW
  • the target user plane path includes the UE, the AN, and the edge gateway Edge.
  • GW the path of the Access GW
  • the source user plane path is a path including the UE, the AN1, the UP GW, and the Access GW
  • the target user plane path is the UE.
  • the path switching notification received by the access gateway includes a service flow template
  • the service flow template includes at least one IP quintuple information
  • the Access GW can determine the end to be sent according to the service flow template.
  • the IP quintuple information of the data packet is used to indicate the last data packet sent on the source user plane path after the user plane path switch of the UE, and the UP GW can send the end tag according to the end data packet.
  • the Access GW receiving the path switch notification may include: the Access GW receiving the path switch notification sent by the edge gateway or the local management unit.
  • the path switching notification may be sent by the edge gateway, or may be sent by the local management unit, and provides several optional implementation manners, which increases the feasibility of the solution.
  • the fourth aspect of the embodiments of the present application provides a method for sending an end tag, which may include: in the embodiment of the present application, when the source user plane path and the target user plane path are the same as the AN node, the source user plane path is The first bearer is between the intermediate node and the UE, and the second bearer is between the AN node and the UE in the target user plane path.
  • the access network AN node receives a flow switching indication message sent by the control plane CP node, where the flow switching indication message includes an identifier ID of the source user plane path of the user equipment UE, where the flow switching indication message is used to indicate that the AN node is in the source user
  • the end tag is received on the surface path, it is determined whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE; it should be noted that the AN node receives the path on the source user plane path.
  • the downlink data packet includes a data packet sent by the Internet and a data packet sent by the local network; when the AN node receives the end tag on the source user plane path, the AN node determines that the AN node receives the path on the source user plane. Whether the downlink data packet has been successfully sent to the UE; if the downlink data packet of the UE received by the AN node on the source user plane path has been successfully sent to the UE, the AN node marks the AN according to the end flag. The node sorts the downlink data packets received on the target user plane path of the UE.
  • the AN node because the embodiment of the present application is directed to the path switching of the local data stream, the AN node cannot identify the local data stream, if the local data stream on the source user plane path is not successfully sent to the UE.
  • the AN node sorts the received downlink data packets according to the end tag on the target user plane path, the local data stream on the source user plane path is lost.
  • Time can be
  • the downlink data packet (local data stream and/or Internet data stream) received by the AN node on the source user plane path is sent on the first bearer between the AN node and the UE, and if both are successfully sent to the UE, the AN node is guaranteed to be The local data stream on the source user plane path is not lost, and the downlink data packets received on the target user plane path are sorted according to the end tag.
  • the method may further include: if at least one data packet in the downlink data packet received by the AN node on the source user plane path is not successfully sent to the UE, The AN node sends the at least one data packet to the UE.
  • the AN node when the AN node receives the end tag, if at least one data packet in the downlink data packet received on the source user plane path is not successfully sent to the UE, the AN node needs to be not The data packet successfully sent to the UE is successfully sent to the UE, which effectively ensures the loss of the downlink data packet sent to the UE on the source user plane path due to the user plane path switching.
  • a fifth aspect of the embodiments of the present application provides a method for sending an end tag, which may include: an access network AN node receives a flow switching indication message from a control plane CP node, where the flow switching indication message includes a source user plane path of the user equipment UE And identifying, by the AN node, the downlink data packet received by the AN node on the path of the source user plane according to the flow switching indication message, where the source user plane path includes a user plane gateway UP GW.
  • the source node surface path is the first bearer between the AN node and the UE
  • the target user plane path is the AN node.
  • a second bearer is between the UE and the UE.
  • the AN node receives the flow switching indication message sent by the CP node, and the AN node may send the downlink data packet received by the AN node on the path of the source user plane according to the flow switching indication message, which is exemplary.
  • the AN node may send the downlink data packet received on the source user plane path to the UE, or the AN node may send the downlink data packet received on the source user plane path to the UP GW, and the AN node may according to the flow switching indication message pair.
  • the downlink data packet received on the source user plane path is processed.
  • a branch node may be selected in the core network when the path switching resource is prepared, and the local data stream is identified by the branch node.
  • the shunt node is described by the UP GW.
  • the flow switching message information is used to indicate that the AN node sends the downlink data packet received by the AN node on the source user plane path to the UP GW; the AN node sends the AN node at the source according to the flow switching indication message.
  • the downlink data packet received on the user plane path may include: the AN node transmitting the downlink data packet received by the AN node on the source user plane path to the UP GW according to the flow switching indication message.
  • a split node UP GW is selected for identification, and the CP node sends a flow switching indication message to the AN node.
  • the UP GW may forward the identified local data stream to the edge gateway, and the edge gateway forwards it back to the AN node.
  • the AN node may send a local data stream to the UE on the second bearer. It should be noted that the AN node also receives an end tag on the source user plane path.
  • the AN node When receiving the end tag, the AN node stops forwarding the downlink data packet received on the source user plane path to the UP GW, and then ends the tag. Forwarded to the UP GW, the UP GW forwards the end tag to the edge gateway, and the edge gateway forwards it back to the AN node. Then, the AN node can face the target user according to the end tag.
  • the downlink packets received on the trail are sorted.
  • the flow switching indication message further includes a service flow indication message, where the flow switching indication message is used to indicate that the AN node receives the local network of the AN node on the source user plane path according to the ID of the service flow template and the source user plane path.
  • the transmitted data packet is sent to the UE by the target DRB, where the target DRB is a transmission path between the UE and the AN node on the target user plane path of the UE; the AN node sends the AN according to the flow switching indication message.
  • the downlink data packet received by the node on the source user plane path of the UE may include: the AN node identifying, according to the service flow template, the data packet sent by the local network; the AN node according to the flow switching indication message and the source user plane The ID of the path, and the identified data packet is sent to the UE through the target DRB.
  • the AN node receives the flow switching indication message sent by the CP node, where the flow switching indication message includes the service flow template and the ID of the source user plane path, then the AN node can be based on the service flow template and the source user.
  • the ID of the plane path identifies the local data stream from the downlink data packet received on the source user plane path, and then sends the identified local data stream to the UE by using the second bearer between the UE and the AN. It is simple and convenient, easy to implement, and reduces the delay of forwarding the source user plane path to the branching node for identification.
  • the AN node directly recognizes and sends it to the UE, and the AN node can effectively receive the target user plane path according to the end tag pair.
  • the downstream packets are sorted.
  • a sixth aspect of the embodiments of the present application provides a control plane CP node, which has a function of determining a transmission end flag according to the trigger information and the source user plane path provided by the above first aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a seventh aspect of the present application provides a user plane gateway UP GW, which has a function of determining a transmission end flag according to the trigger information and the source user plane path provided by the second aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the eighth aspect of the embodiment of the present application provides an access gateway Access GW, which has the function of determining the sending end tag according to the trigger information and the source user plane path provided by the foregoing third aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a ninth aspect of the embodiment of the present application provides an access network AN node, which has a function of determining a transmission end flag according to the trigger information and the source user plane path provided by the foregoing fourth aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • a tenth aspect of the embodiment of the present application provides an access network AN node, which has a function of determining a transmission end tag according to the trigger information and the source user plane path provided by the foregoing fifth aspect.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • control plane node which may include:
  • transceiver a transceiver, a memory and a bus, the transceiver and the memory being connected by the bus;
  • the memory is configured to store an operation instruction
  • the transceiver is configured to receive a session update response, where the session update response includes an identifier ID of a source user plane path of the user equipment UE or an ID of a target user plane path of the UE, where the source user plane path includes a user plane gateway Sending, by the UP GW, trigger information and an ID of the source user plane path to the UP GW, where the trigger information is used by the UP GW to access the network on the source user plane path
  • the AN node sends an end tag.
  • a twelfth aspect of the embodiment of the present application provides a user plane gateway, which may include:
  • transceiver a transceiver, a memory and a bus, the transceiver and the memory being connected by the bus;
  • the memory is configured to store an operation instruction
  • the transceiver is configured to receive trigger information sent by a control plane CP node and an identifier ID of a source user plane path of the user equipment UE, where the UP GW is located on the source user plane path; according to the trigger information and the source The ID of the user plane path sends an end tag to the access network AN node on the source user plane path.
  • a thirteenth aspect of the present application provides an access gateway, which may include:
  • transceiver a transceiver, a memory and a bus, the transceiver and the memory being connected by the bus;
  • the memory is configured to store an operation instruction
  • the transceiver is configured to receive a path switch notification, where the path switch notification includes a service flow template, and send an end data packet to the UP GW according to the service flow template.
  • a fourteenth aspect of the embodiments of the present disclosure provides an access network node, which may include:
  • transceiver a transceiver, a processor, a memory and a bus, the transceiver, the processor and the memory being connected by the bus;
  • the memory is configured to store an operation instruction
  • the processor configured to determine, when the AN node receives the end tag on the source user plane path, whether the downlink data packet received by the AN node on the source user plane path is Successfully sent to the UE;
  • the transceiver is configured to receive a flow switching indication message sent by the control plane CP node, where the flow switching indication message includes an identifier ID of a source user plane path of the user equipment UE, where the flow switching indication message is used to indicate the AN node Determining, after receiving the end tag on the source user plane path, whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE; if the AN node is in the source The downlink data packet of the UE that is received on the user plane path has been successfully sent to the UE, and the transceiver receives the downlink of the AN node on the target user plane path of the UE according to the end flag. The data packets are sorted, or the transceiver sends the end marker.
  • a fifteenth aspect of the embodiments of the present application provides an access network node, which may include:
  • transceiver a transceiver, a memory and a bus, the transceiver and the memory being connected by the bus;
  • the memory is configured to store an operation instruction
  • the transceiver is configured to receive, by the control plane CP node, a flow switching indication message, where the flow switching indication message includes an identifier ID of a source user plane path of the user equipment UE, and send the AN node according to the flow switching indication message
  • a sixteenth aspect of the present application provides a communication system, where the communication system includes a control plane node, a user plane gateway, and an access gateway, and the control plane node is configured to perform the first aspect of the application or any optional implementation of the first aspect.
  • the control plane node in the manner; the user plane gateway is the user plane gateway described in the optional implementation manner of the second aspect or the second aspect of the application; the access gateway is configured to perform the third aspect of the application or An access gateway as described in any of the alternative implementations of the third aspect.
  • a seventeenth aspect of the present application provides a communication system, including a control plane node, a user plane gateway, an access gateway, and an access network node, where the control plane node is configured to perform the first aspect or the first aspect of the present application.
  • a control plane node as described in any of the alternative implementations;
  • the user plane gateway is a user plane gateway configured in the optional implementation manner of the second aspect or the second aspect of the present application;
  • the access network node is configured to perform the access in any of the optional implementation manners of the fourth aspect or the fourth aspect of the application Network node.
  • the eighteenth aspect of the present application provides a communication system, where the communication system includes a control plane node, a user plane gateway, an access gateway, and an access network node, where the control plane node is configured to perform the first aspect or the first aspect of the present application.
  • a control plane node as described in any of the alternative implementations;
  • the user plane gateway is a user plane gateway configured in the optional implementation manner of the second aspect or the second aspect of the present application;
  • the access network node is configured to perform the access in any of the optional implementation manners of the fifth aspect or the fifth aspect of the application Network node.
  • a nineteenth aspect of the present invention provides a storage medium. It should be noted that the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be implemented by software.
  • the computer software product is stored in a storage medium for storing computer software instructions for use in the above apparatus, comprising: for performing the first aspect, the second aspect, the third aspect or the fourth aspect (
  • the fifth aspect is a program designed for a control plane node, a user plane gateway, an access gateway, or an access network node.
  • the storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes.
  • a twentieth aspect of the embodiments of the present invention provides a computer program product comprising instructions, when executed on a computer, causing a computer to perform the method as described in the first aspect of the present application or any of the alternative implementations of the first aspect .
  • a twenty-first aspect of the present invention provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform the method as described in any of the alternative aspects of the second aspect or the second aspect of the present application method.
  • a twenty-second aspect of the embodiments of the present invention provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform the method as described in any of the optional implementations of the third aspect or the third aspect of the present application. method.
  • a twenty-third aspect of the embodiments of the present invention provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform the method as described in any of the fourth aspect or the fourth aspect of the present application. method.
  • a twenty-fourth aspect of the embodiments of the present invention provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform the method as described in any of the alternative implementations of the fifth or fifth aspect of the present application method.
  • the embodiments of the present application have the following beneficial effects:
  • the source user plane path is switched to the target.
  • the user path, the source user plane path contains the UP GW, and the target user plane path contains the edge gateway.
  • the CP node receives the session update response, and sends the trigger information and the identifier ID of the source user plane path to the UP GW according to the session update response, where the trigger information is used by the UP GW to the access network AN node on the source user plane path.
  • the sending end tag, the UP GW determines, according to the received trigger information and the identifier ID of the source user plane path, when the UP GW sends an end tag to the AN node, thereby assisting the sorting process of the downlink data packet received on the target user plane path.
  • the function of the user plane gateway can be enhanced, and most functions of the traditional network element can be reused, and the existing handover process is not required to be widely modified, which is simple and clear, and is easy to implement. Resolve the loss of a small amount of data on the path of the source user plane due to the unreliability of the Internet.
  • the downlink data sent by the local network may be directly sent to the UE through the edge gateway, and does not need to pass the UP GW. Send to the UE to save transmission delay.
  • the downlink data packet received by the AN node includes the data packet sent by the Internet and the data packet sent by the local network. Then, after the user plane path is switched, the local transmission on the source user plane path needs to be performed. The data packet sent by the network is forwarded to the target user plane path and transmitted to the UE.
  • the AN node cannot identify the data packet sent by the local network, and the embodiment of the present application proposes that the local node sends the local network to send.
  • the data packet, or the data packet sent by the local network is identified on the branch node selected by the core network, or directly, on the source user plane path, the AN node successfully sends all the data packets to the UE, and then according to the received end tag.
  • Processing the downlink data packets received on the target user plane path reduces the out-of-order and congestion of the Internet to a certain extent, thereby reducing the impact of sorting the data packets received on the target user plane path.
  • FIG. 1 is a schematic diagram of path reselection performed by UE mobile in the prior art
  • FIG. 2 is a schematic diagram of a path reselection performed by a UE receiving a user plane report in the prior art
  • FIG. 3 is a schematic diagram of a network architecture of an evolved packet system EPS in an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of an evolved universal terrestrial radio access network EUTRAN in an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a next-generation NG mobile communication system according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of an implementation manner of an EPS path in an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a current handover process based on an X2 interface in the embodiment of the present application.
  • FIG. 8 is a schematic diagram of a current handover process based on an S1 interface in the embodiment of the present application.
  • FIG. 9 is a schematic diagram of an existing forwarding end marker end marker in the embodiment of the present application.
  • FIG. 10 is a schematic diagram of a sending end tag in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of an embodiment of a method for sending an end tag according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of another embodiment of a method for sending an end tag according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of another embodiment of a method for sending an end tag according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of another embodiment of a method for sending an end tag according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of another embodiment of a method for sending an end tag according to an embodiment of the present application.
  • 16 is a schematic diagram of another embodiment of a method for sending an end tag in an embodiment of the present application.
  • FIG. 17 is a schematic diagram of another embodiment of a method for sending an end tag according to an embodiment of the present application.
  • FIG. 18 is a schematic diagram of another embodiment of a method for sending an end tag according to an embodiment of the present application.
  • FIG. 19 is a schematic diagram of an embodiment of a control plane CP node according to an embodiment of the present application.
  • FIG. 20 is a schematic diagram of an embodiment of a user plane gateway UP GW according to an embodiment of the present application.
  • FIG. 21 is a schematic diagram of another embodiment of a user plane gateway UP GW according to an embodiment of the present application.
  • FIG. 22 is a schematic diagram of an embodiment of an access gateway Access GW according to an embodiment of the present application.
  • FIG. 23 is a schematic diagram of an embodiment of an access network AN node in an embodiment of the present application.
  • 24 is a schematic diagram of another embodiment of an access network AN node in an embodiment of the present application.
  • 25 is a schematic diagram of another embodiment of a control plane CP node in an embodiment of the present application.
  • FIG. 26 is a schematic diagram of another embodiment of a user plane gateway UP GW according to an embodiment of the present application.
  • FIG. 27 is a schematic diagram of another embodiment of an access gateway Access GW according to an embodiment of the present application.
  • FIG. 28 is a schematic diagram of another embodiment of an access network AN node in an embodiment of the present application.
  • the mobile network that the user equipment (User Equipment, UE) can access includes a 2G, 3G, and 4G network, and provides a transmission channel for the UE's call service, video service, and web service.
  • FIG. 3 it is a schematic diagram of a network architecture of an Evolved Packet System (EPS), and a 4G network is taken as an example to briefly introduce a traditional mobile network.
  • the network elements mainly involved in EPS include UE, evolved universal terrestrial radio access network, mobility management entity, service gateway, packet data network gateway, General Packet Radio System (GPRS) support node, and attribution.
  • GPRS General Packet Radio System
  • User server policy, and accounting rules features.
  • FIG. 4 it is a schematic diagram of an architecture of an Evolved Universal Terrestrial Radio Access Network (EUTRAN).
  • EUTRAN Evolved Universal Terrestrial Radio Access Network
  • EUTRAN Evolved Universal Terrestrial Radio Access Network
  • eNodeBs Evolved NodeBs
  • the eNodeBs can be connected through the X2 interface, and can transmit data based on the X2 interface.
  • the eNodeB is connected to the Serving Gateway (SGW) through the user plane interface S1-U, and uses the GPRS Tunneling Protocol User Plane (GTP-U) to transmit user plane data; through the control plane interface S1-MME and The Mobility Management Entity (MME) is connected, and the S1 interface application protocol (S1-Application Protocol, S1-AP) is used to implement functions such as radio access bearer control, as shown in FIG. 4 above.
  • SGW Serving Gateway
  • GTP-U GPRS Tunneling Protocol User Plane
  • MME Mobility Management Entity
  • S1 interface application protocol S1-Application Protocol, S1-AP
  • MME Mainly responsible for user and session management control plane functions, including non-access stratum (Non Access Stratum, NAS) Signaling and security, management of Tracking Area List, and selection of Packet Date Network Gateway (PDN Gateway, PGW) and SGW.
  • Non-access stratum Non Access Stratum, NAS
  • PGW Packet Date Network Gateway
  • SGW It is mainly responsible for transmitting, forwarding, and routing handover of data of the UE, and is used as a local mobility anchor point when the UE switches between eNodeBs (for each UE, only one SGW is served at each moment).
  • Packet Data Network Gateway As an anchor point of the PDN connection, it is responsible for the Internet Protocol (IP) address allocation of the UE, data packet filtering, rate control, and generation of charging information of the UE.
  • IP Internet Protocol
  • GSM Global System for Mobile Communications
  • EDGE Evolution Enhanced Data Rates for GSM Evolution, EDGE
  • GSM/EDGE Radio Access Network GERAN
  • UTRAN 3G access network Universal Terrestrial Radio Access Network
  • EPS Evolved Packet System
  • the access node of the Evolved Packet Core is responsible for the establishment of the bearer from GERAN and UTRAN to the Evolved Packet Core (EPC) and data forwarding.
  • the Home Subscriber Server stores the subscription data of the mobile subscriber.
  • PCRF Policy and Charging Rules Function
  • FIG. 5 is a schematic diagram of the architecture for the next generation (Next Generation, NG) mobile communication system to the third Generation Partnership Project (3 rd Generation Partnership Project, 3GPP ) standard is widely accepted that progress and recognition of a An example of a system architecture.
  • Next Generation Next Generation
  • 3GPP Third Generation Partnership Project
  • NextGen or NG is the short name of the next generation mobile communication system architecture. It consists of UE, AN, Core network (CN) and Data Network.
  • the UE, AN and core network are the main components of the architecture.
  • the upper AN and the core network can be divided into two parts: the user plane and the control plane.
  • the control plane is responsible for the management of the mobile network
  • the user plane is responsible for the transmission of the service data.
  • the NG2 reference point is located between the AN control plane and the CN control plane
  • the NG3 reference point is located between the AN user plane and the CN user plane
  • the NG6 reference point is located between the CN user plane and the data network.
  • the NextGen UE It is the entrance of the mobile user to interact with the network. It can provide basic computing power, storage capability, display the business window to the user, and accept user input.
  • the NextGen UE will use the next-generation air interface technology to establish signal connections and data connections with the access network to transmit control signals and service data to the mobile network.
  • AN Similar to the base station in the traditional network, it is deployed close to the UE, provides the network access function for authorized users in a specific area, and can transmit user data using different quality transmission tunnels according to the user level and service requirements.
  • the AN can manage its own resources, make reasonable use, provide access services for the UE as needed, and forward control signals and user data between the UE and the CN.
  • CN Responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing functions such as session management, mobility management, policy management, and security authentication for the UE.
  • the UE When the UE is attached, the UE is provided with network access authentication; when the UE has a service request, the network resource is allocated to the UE; when the UE moves, the network resource is updated for the UE; when the UE is idle, the UE is provided with a fast recovery mechanism; Release the network resources for the UE when the UE is attached; at the UE
  • the UE provides data routing functions, such as forwarding uplink data to the data network, or receiving downlink data sent by the UE from the Data Network, and forwarding the data to the AN for transmission to the UE.
  • a data network that provides business services to users.
  • the general client is located at the UE and the server is located at the data network.
  • the data network can be a private network, such as a local area network, or an external network that is not controlled by the operator, such as the Internet Internet, or a proprietary network deployed by the operator, such as to configure the IP Multimedia Network subsystem (IP Multimedia Core). Network Subsystem, IMS) service.
  • IP Multimedia Core IP Multimedia Core
  • IMS IP Multimedia Core
  • IMS IP Multimedia Core
  • the data path of the UE is implemented by using an Evolved Packet System (EPS), as shown in FIG. 6 , which is a schematic diagram of an EPS path implementation.
  • the handover scheme is based on the X2 interface, and is triggered when an X2 interface exists between the source eNB and the target eNB.
  • FIG. 8 it is a schematic diagram of a handover procedure based on the S1 interface, which is triggered when there is no X2 interface between the source eNB and the target eNB, or triggered when the handover process of the X2 interface fails.
  • the source user plane path may be described by using the source path as an abbreviation, and the target user plane path may be referred to by the target path as an abbreviation.
  • eNB1 is the source base station
  • eNB2 is the target base station
  • eNB1 requests eNB2 to prepare the path resource, that is, prepares the target user plane path bearer and forwards the bearer.
  • eNB1 may receive the response message returned by eNB2, and then notify the UE to switch to eNB2; 2.
  • the MME notifies the MME to switch the path and notifies the corresponding path information. 3.
  • the MME notifies the SGW to switch the downlink path. 4.
  • the service gateway After the service gateway switches the path, immediately after the completion, immediately sends a data end tag on the source path. 5.
  • the SGW sends downlink data on the target user plane path. 6.
  • the eNB1 receives the end tag sent by the SGW, and forwards the end flag to the eNB2, thereby assisting the eNB2 to reorder.
  • FIG. 8 it is a schematic diagram of a handover process based on the S1 interface.
  • eNB1 requests MME1 to prepare path resources on eNB2, that is, prepare target user plane path bearer and forward bearer; 2. MME1 forwards the request to MME2 controlling eNB2; 3. MME2 requests eNB2 to prepare target user plane path resource and handover resource; MME2 notifies SGW2 to prepare for handover of resources; 5, after receiving response from MME2, MME1 notifies SGW1 to prepare resources for handover path; 6.
  • MME1 notifies UE to handover to eNB2; 7, UE switches to eNB2; 8, eNB2 notifies MME2, UE switches 9; MME2 notifies SGW2 of the handover path; 10, SGW2 notifies the PGW handover path; 11.
  • PGW handover path transmits downlink data on the target user plane path; 12.
  • SGW2 forwards downlink data to eNB2 on the target user plane path; After the PGW handover path is completed, an end marker is sent on the source user plane path; 14.
  • SGW1 continues to forward the end marker to eNB1; 15. eNB1 sends an end marker along the forwarding path to eNB2; 16.
  • eNB2 receives the end The tag reorders the downlink data of the forwarded source user plane path and the downlink data received on the target user plane path according to the sequence number of the end tag.
  • the UE converts the served eNB1, connects to the eNB2, and establishes a forwarding bearer based on the source user plane path (S1 bearer, RB, etc.) in a 1:1 proportional relationship.
  • the data is then processed in the order of 1, 2, 3, 4, 5, and 6 as shown in the figure.
  • PDCP Packet Data Convergence Protocol
  • eNB1 puts new downlink data sent on the corresponding source user plane path to the forwarding path.
  • the UP gateway SGW/PGW
  • the priority is processed; 5. If the eNB2 is in the Before receiving the forwarded marker, the downlink data sent by the target user plane path is received, first buffered; 6. After receiving the end tag on the forwarding path, the eNB2 receives the maximum sequence number of the PDCP of the end marker (Sequence Number, SN), the downlink data received by the target user plane path is further sorted, so that the end marker can assist the eNB2 in performing downlink data sorting processing.
  • SN Sequence Number
  • the UE switches from the source user plane path to the target user plane path. Because the user plane gateway changes on the target user plane path, that is, the UP GW changes to the edge gateway, then, first, Because there is still residual data left in the Internet, the source user plane gateway cannot determine when to send the end tag. Second, when the local data stream and other data streams coexist in the source user plane path, the AN node cannot determine to switch to the edge gateway. The local data stream sent to the UE again; therefore, the AN node cannot solve the data disorder problem caused by the user plane path reselection.
  • a method for sending an end tag is proposed to solve the problem of out-of-order data outgoing in the process of user plane path reselection.
  • the control plane CP node receives the session update response
  • the CP node sends the trigger information to the UP GW according to the session update response, and then notifies the MANO (the service management unit of the local data network)
  • the path is switched for the local data stream; after the access gateway completes the user plane path switching of the UE, one or more end data packets are sent on the Internet; after the UP GW receives the end data packet, the end data packet corresponds to the trigger information.
  • the local data stream context update is completed, such as a traffic filter template (TFT), a quality of service (QoS), and the like, and then UP.
  • TFT traffic filter template
  • QoS quality of service
  • the GW sends an end marker on the source user plane path.
  • the core network element functions are divided into a control plane function and a user plane function.
  • the core network element functions are divided into CP and UP.
  • UP is mainly responsible for packet data packet forwarding, QoS control, and accounting information statistics.
  • the CP is mainly responsible for sending a packet forwarding policy, a QoS control policy, and a charging information statistics reporting policy to the user plane function.
  • UP is a general term for devices that perform user plane functions. It does not specifically refer to one or some devices. In actual applications, devices that perform user plane functions may not be called “UP”, but other The name is not limited, and is not limited herein. In the present application, the "UP node” is taken as an example for description.
  • CP is a general term for devices that perform control plane functions, and does not specifically refer to one or some devices. In actual applications, devices that perform control plane functions may not be called “CPs". The name is replaced by another name, which is not limited herein. In the present application, the "CP node” is taken as an example for description.
  • the UP and the CP may be a single device, or a set of functional entities on other devices (such as a server), and are not limited herein.
  • a schematic diagram of an embodiment of a method for transmitting an end tag in an embodiment includes:
  • the CP node receives a session update response, where the session update response includes an ID of a source user plane path of the UE or an ID of a target user plane path of the UE, where the source user plane path includes an UP GW.
  • the CP node may send a session update request to the edge gateway, and then receive the session update response sent by the edge gateway.
  • the session update request here may be an Update Bearer Request
  • the session update response may be an Update Bearer Response.
  • the session update response may include an identifier of the source user plane path of the UE or an identifier of the target user plane path of the UE, the source user plane path includes the UP GW, and the target user plane path includes the edge gateway Edge GW.
  • the source user plane path and the target user plane path are the same as the AN node
  • the source user plane path is a path including the UE, the AN node, the UP GW, and the Access GW
  • the target user plane path includes the UE and the AN.
  • the first bearer is between the UE and the AN node
  • the first tunnel is between the AN node and the UP GW
  • the UE and the AN node are on the target user plane path.
  • the second bearer (Second Tunnel), the second node and the Edge GW are second tunnels (Second Tunnel); the Edge GW and the Access GW are external tunnels.
  • the AN1 node is used as the source AN node, and the AN2 node is the target AN node as an example.
  • the source user plane path is a path including the UE, the AN1 node, the UP GW, and the Access GW
  • the target user plane path is a path including the UE, the AN2, the Edge GW, and the Access GW.
  • the first bearer is between the UE and the AN1 node
  • the first tunnel is between the AN1 node and the UP GW
  • the second bearer Second Bearer
  • the GW is a second tunnel (Second Tunnel); the Edge GW and the Access GW are external tunnels.
  • the CP node sends the trigger information and the ID of the source user plane path to the UP GW according to the session update response.
  • the trigger information is used by the UP GW to send an end tag to the AN node on the source user plane path.
  • the trigger information herein may be: at least one of a first service flow template and a timer parameter, where the first service flow template is used to detect the end data packet, and the end data packet is used to indicate the UE user plane path.
  • the trigger information here may also be information such as an indication identifier, and is not limited.
  • the first service flow template is used to filter the end data packet, that is, the UP GW filters the end data packet sent from the Access GW according to the first service flow template, and when the UP GW filters out the end data packet, The UP GW sends an End Marker to the source AN node.
  • the first service flow template may be as shown in Table 1 below, or when the path identifier ID is removed from the table 1, it may also serve as the first service flow template.
  • the timer parameter herein may be an exemplary value, such as 2 ms, then the value of the timer on the UP GW side may be set to 0-2 ms, and the timeout is over 2 ms, and the timer may also be set to 8-10ms, more than 10ms is a timeout, the initial value of the timer can be determined according to the actual situation; the timer parameter can also be the interval parameter, that is, the interval parameter is [a, b], then the initial of the timer can be The value is set to a value, and the timeout value is set to b value.
  • the UP GW when the trigger information is a timer parameter, after the UP GW receives the trigger information sent by the control plane CP node, the UP GW starts the timer immediately. If the UP GW timer expires, the UP GW sends the identifier to the AN1 node. End tag, the UP GW does not need to determine when to send the end tag according to the end packet sent by the access gateway.
  • the UP GW receives the trigger information sent by the CP node and the identifier ID of the source user plane path of the UE, where the UP GW is located on the source user plane path.
  • the trigger information may be at least one of a first service flow template and a timer parameter.
  • the Access GW receives the path switch notification, where the path switch notification includes a service flow template.
  • the Access GW receiving the path switch notification may include: the Access GW receiving the path switch notification sent from the edge gateway or the local management unit.
  • the Access GW sends an end data packet to the UP GW according to the service flow template.
  • the IP quintuple information of the ending data packet may be determined by the first service flow template.
  • step 1105 is an optional step, that is, when the trigger information in the above step includes the first service flow template, step 1105 is necessary.
  • the UP GW sends an end tag to the AN node on the source user plane path according to the trigger information and the ID of the source user plane path.
  • step 1106 can include the following scenarios:
  • the trigger information includes a first service flow template
  • the UP GW When the IP quintuple information of the downlink data packet of the UE received by the UP GW is the same as any IP quintuple information in the first service flow template, the UP GW is on the source user plane path according to the ID of the source user plane path. An end tag is sent to the AN node.
  • the first service flow template here can be understood as an end packet filter. After detecting the end packet coming from the Internet path, the UP GW sends an end tag on the source user plane path and updates the context of the local data stream.
  • the trigger information includes a first service flow template and a timer parameter
  • the UP GW starts a timer, and the timer is set according to the timer parameter; If the UP GW receives After the data packet is terminated and the timer does not expire, the UP GW restarts the timer, and the IP quintuple information of the end packet is the same as any IP quintuple information in the first service flow template; when the timer expires, The UP GW sends an end tag to the AN node according to the ID of the source user plane path.
  • the UP GW After the UP GW detects the end packet sent from the source user plane path according to the first service flow template, the UP GW starts the timer, and if the UP GW receives other subsequent end packets or When receiving a packet sent by the local network, the UP GW resets the timer; if the end packet is not received or the packet sent by the local network causes the timer to expire, the UP GW immediately follows the source user plane path. Send an end tag on it and update the context of the local data stream.
  • the trigger information includes a timer parameter
  • the UP GW sets a timer according to the timer parameter; the UP GW starts a timer; when the timer expires, the UP GW sends an end tag to the AN node on the source user plane path according to the ID of the source user plane path.
  • the time when the timer is started is that when the UP GW receives the timer parameter, the timer is started immediately. If the UP GW receives the data packet sent by the local network within the timer time, the timer is reset; If the UP GW continues to receive the data packet sent by the local network and the timer expires, it indicates that the transmission of the data packet sent by the local network on the source user plane path (Internet) ends, and the end tag is sent and updated on the source user plane path.
  • the context of the local data stream is that when the UP GW receives the timer parameter, the timer is started immediately. If the UP GW receives the data packet sent by the local network within the timer time, the timer is reset; If the UP GW continues to receive the data packet sent by the local network and the timer expires, it indicates that the transmission of the data packet sent by the local network on the source user plane path (Internet) ends, and the end tag is sent and updated on the source user plane path.
  • the UP GW sends an end tag to the AN node according to the trigger information and the ID of the source user plane path, and the AN node receives the end tag, and can be on the target user plane path.
  • the received downlink data packet is sorted, and the sorted downlink data packet is sent to the UE.
  • the UP GW sends an end tag to the AN1 node according to the trigger information and the ID of the source user plane path, and the AN1 node forwards the end tag to the AN2 node, and the AN2 node receives the end tag.
  • the downlink data packet received on the target user plane path may be sorted according to the end tag, and the sorted downlink data packet is sent to the UE.
  • the source user plane path is switched to the target user plane path, the source user plane path includes the UP GW, and the target user plane path includes the edge gateway.
  • the CP node receives the session update response, and sends the trigger information and the identifier ID of the source user plane path to the UP GW according to the session update response.
  • the UP GW determines, according to the received trigger information and the identifier ID of the source user plane path, when the UP GW is directed.
  • the AN node sends an end tag to assist in sorting the downlink packets received on the target user plane path.
  • the function of the user plane gateway can be enhanced, and most functions of the traditional network element can be reused, and the existing handover process is not required to be widely modified, which is simple and clear, and is easy to implement. Resolve the loss of a small amount of data on the path of the source user plane due to the unreliability of the Internet.
  • FIG. 12 is a schematic diagram of another embodiment of a method for sending an end tag in an embodiment of the present application, including:
  • the AN node receives a flow switching indication message sent by the CP node, where the flow switching indication message includes an ID of a source user plane path of the user equipment UE, and the flow switching indication message is used to indicate that the AN node receives the end marking on the source user plane path. It is determined whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE.
  • the CP node may send the foregoing flow switching indication message to the AN node, and then the AN node receives the control plane CP node to send.
  • the flow switching indication message is described.
  • the source user plane path is the same as the AN node in the target user plane path
  • the source user plane path is a path including the UE, the AN node, the UP GW, and the Access GW
  • the target user plane path is Contains the path of the UE, the AN node, the Edge GW, and the Access GW.
  • the first DRB, the AN node, and the UP GW are the main tunnels between the UE and the AN node on the source user plane path
  • the second DRB, the AN node, and the Edge GW are between the UE and the AN node on the target user plane path.
  • the downlink data packets received by the AN node include data packets sent by the local network and/or data packets sent by the Internet. Because the handover of the user plane path of the UE here is a path switch for the local data stream, but the data packet received by the AN node is not only the local data stream, the AN node cannot identify the local data stream received on the source user plane path, If the local data stream on the source user plane path is not successfully sent to the UE, the downlink data packet received on the target user plane path cannot be sorted according to the end marker in time.
  • the AN node may send, according to the flow switching indication message, the downlink data packet (local data stream and/or Internet data stream) received by the AN node on the source user plane path to the UE on the first DRB. .
  • the CP node receives a session update response, where the session update response includes an ID of a source user plane path of the UE or an ID of a target user plane path of the UE, and the source user plane path includes an UP GW.
  • the CP node sends the trigger information and the ID of the source user plane path to the UP GW according to the session update response.
  • the trigger information is used by the UP GW to send an end tag to the AN node on the source user plane path.
  • the UP GW receives the trigger information sent by the CP node and the ID of the source user plane path of the UE, where the UP GW is located on the source user plane path.
  • the Access GW receives a path switch notification, where the path switch notification includes a service flow template.
  • the Access GW sends an end data packet to the UP GW according to the service flow template.
  • the UP GW sends an end tag to the AN node on the source user plane path according to the trigger information and the ID of the source user plane path.
  • the steps 1202-1207 are similar to the steps 1101-1106 shown in FIG. 11, and reference may be made to the steps 1101-1106 in FIG. 11, and details are not described herein again.
  • the AN node determines whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE.
  • the AN node When the AN node receives the end tag sent by the UP GW on the source user plane path, the AN node needs to first determine whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE.
  • the AN node if the AN node receives 10 data packets on the source user plane path, after receiving the end tag, the AN node first determines whether the 10 data packets are successfully sent to the UE.
  • the AN node sorts the downlink data packet received by the AN node on the target user plane path of the UE according to the end marker.
  • the AN node sorts the downlink data packets received by the AN node on the target user plane path of the UE according to the end marker. If at least one data packet in the downlink data packet received by the AN node on the source user plane path is not successfully sent to the UE, The AN node sends at least one data packet to the UE.
  • the AN node has sent the downlink data packet received on the source user plane path to the UE on the first DRB when the end marker is not received, if the AN node receives the downlink data on the source user plane path. If there are 10 packets, then the AN sends the 10 downlink data packets to the UE on the first DRB. If the UE successfully sends the message to the UE, it will receive 10 successful identifiers that the UE feeds back.
  • the AN node When the AN node receives the end tag, if the AN node has received the success indications fed back by the 10 UEs, it proves that the data packets sent by the UE to the UE on the first DRB are successfully sent, then the AN node can end according to the end.
  • the sequence number in the tag sorts the downlink data packets received on the target user plane path, and sends the sorted downlink data packets to the UE on the second DRB.
  • the AN node When the AN node receives the end tag, if the AN node only receives the success indications fed back by the 8 UEs, it proves that the data packets sent by the UE to the UE on the first DRB have not been successfully sent to the UE, and if not yet sent, Then, the remaining two downlink data packets are sent to the UE on the first DRB, and wait for the success indication of the feedback. If the success identifier of the feedback is not received, the UE continues to wait until receiving the feedback from the UE. After two successful identifiers, the AN node can sort the downlink data packets received on the target user plane path according to the sequence number in the end tag, and sequence the downlink data packets on the second DRB to the UE. send.
  • the AN node may send the downlink data packet received on the source user plane path to the UE on the first DRB according to the flow switching indication message, and the UP GW may perform the trigger information according to the trigger information.
  • the ID of the source user plane path sends an end tag to the AN node.
  • the AN node receives the end tag sent by the UP GW, it needs to determine whether the data packet received by the AN node on the source user plane path has been successfully sent to the UE.
  • the local data stream received by the AN node on the source user plane path is successfully sent to the UE.
  • the AN node can sort the downlink data packets received on the target user plane path according to the end tag.
  • the effective transmission of the local data stream received by the AN node on the source user plane path after the user plane path switching of the UE is effectively guaranteed, thereby reducing the data loss caused by the handover of the user plane path of the UE, and further, the AN node according to the The end tag processes the downstream packets received on the target user plane path.
  • FIG. 13 is a schematic diagram of another embodiment of a method for sending an end tag in an embodiment of the present application, including:
  • the access network AN node receives a flow switching indication message from the control plane CP node, where the flow switching indication message includes an identifier ID of the source user plane path of the user equipment UE.
  • the source user plane path is the same as the AN node in the target user plane path
  • the source user plane path is a path including the UE, the AN node, the UP GW, and the Access GW
  • the target user plane path is Contains the path of the UE, the AN node, the Edge GW, and the Access GW.
  • the first DRB, the AN node, and the UP GW are the main tunnels between the UE and the AN node on the source user plane path
  • the second DRB, the AN node, and the Edge GW are between the UE and the AN node on the target user plane path.
  • the role of the flow switching indication message includes but is not limited to the following:
  • the flow switching message information is used to instruct the AN node to send the downlink data packet received by the AN node on the source user plane path to the UP GW;
  • the flow switching indication message further includes a service flow template, and the flow switching indication message is used to indicate that the AN node is based on the service.
  • the ID of the flow template and the source user plane path sends the data packet sent by the local network received by the AN node on the source user plane path to the UE through the target DRB, and the target DRB is between the UE and the AN node on the target user plane path of the UE.
  • the transmission path should be understood.
  • the service flow template here is used to filter the data packet sent by the local data network, that is, the local data stream, and the target DRB can be the second DRB mentioned above.
  • the CP node receives a session update response, where the session update response includes an ID of a source user plane path of the UE or an ID of a target user plane path of the UE, and the source user plane path includes an UP GW.
  • the CP node sends the trigger information and the ID of the source user plane path to the UP GW according to the session update response.
  • the trigger information is used by the UP GW to send an end tag to the AN node on the source user plane path.
  • the UP GW receives the trigger information sent by the CP node and the ID of the source user plane path of the UE, where the UP GW is located on the source user plane path.
  • the Access GW receives the path switch notification, where the path switch notification includes a service flow template.
  • the Access GW sends an end packet to the UP GW according to the service flow template.
  • the UP GW sends an end tag to the AN node on the source user plane path according to the trigger information and the ID of the source user plane path.
  • the steps 1302-1307 are similar to the steps 1101-1106 shown in FIG. 11, and reference may be made to the steps 1101-1106 in FIG. 11, and details are not described herein again.
  • the AN node sends, according to the flow switching indication message, a downlink data packet that is received by the AN node on the source user plane path, where the source user plane path includes the user plane gateway UP GW.
  • the content performed by the AN node is also different, including the following scenarios:
  • the flow switching message information is used to instruct the AN node to send the downlink data packet received by the AN node on the source user plane path to the UP GW.
  • the sending, by the AN node, the downlink data packet received by the AN node on the source user plane path according to the flow switching indication message may include: the AN node sending the downlink data packet received by the AN node on the source user plane path according to the flow switching indication message.
  • the UP GW receives the flow switching indication message sent by the CP node, where the flow switching indication message includes the ID of the source user plane path and the second service flow template. It should be understood that the second service flow template is used to filter the local network.
  • the UP GW identifies the data packet sent by the local network from the downlink data packet sent by the receiving node on the source user plane path according to the ID of the second service flow template and the source user plane path; the UP GW sends the identified packet to the edge gateway.
  • the data packet, the edge gateway is located on the target user plane path of the UE.
  • the edge gateway receives the identified data packet sent by the UP GW and forwards it back to the AN node; the AN node can transmit the identified data packet on the second DRB.
  • the AN node when the AN node receives the end tag sent from the UP GW, it stops forwarding the downlink data packet received by the AN node on the source user plane path to the UP GW, and forwards the end tag back to the UP GW; After the end tag is forwarded to the edge gateway, when the AN node receives the end tag forwarded from the edge gateway, the downlink data packet received on the target user plane path can be sorted according to the end tag.
  • the AN node cannot identify the local data stream, and the offload node UP GW selected by the core network identifies the data packet sent by the local network, and sends the identified data packet to the UE through the second DRB, thereby effectively reducing the cause.
  • the user plane path switching of the UE causes the loss of the local data stream, and the local data stream on the source user plane path can be switched to the target user plane path and transmitted to the UE.
  • the flow switching indication message further includes a service flow template, and the flow switching indication message is used to indicate that the AN node sends the data packet sent by the local network on the source user plane path according to the ID of the service flow template and the source user plane path.
  • the target DRB is transmitted to the UE through the target DRB, which is a transmission path between the UE and the AN node on the target user plane path of the UE.
  • the sending, by the AN node, the downlink data packet received by the AN node on the source user plane path of the UE according to the flow switching indication message may include: the AN node identifies the data packet sent by the local network according to the service flow template; and the AN node according to the flow switching indication The ID of the message and the source user plane path, and the identified data packet is sent to the UE through the target DRB.
  • the AN node can temporarily identify the data packet sent by the local network, and transmit the identified data packet to the UE on the switched target user plane path, and further, when the AN After receiving the end tag, the node may sort the downlink data packets received by the AN node on the target user plane path according to the end tag, and may also send the sequenced downlink data packet to the UE.
  • timings of steps 1308 and 1302-1307 are not limited.
  • the AN node receives the flow switching indication message from the control plane CP node, and the AN node sends the downlink data packet received by the AN node on the source user plane path according to the flow switching indication message.
  • the AN node sends the downlink data packet received by the AN node on the source user plane path according to the flow switching indication message.
  • the AN node can identify the local data received on the source user plane path.
  • the UP GW may send an end tag to the AN node according to the trigger information and the ID of the source user plane path, and when the AN node receives the end tag sent by the UP GW, the end may be terminated.
  • the tag sorts the downstream packets received on the target user plane path.
  • FIG. 14 is a schematic diagram of another embodiment of a method for sending an end tag in an embodiment of the present application, including:
  • the trigger information is first notified to the UP GW (the user plane gateway before the handover path); Then notify MANO, MANO notifies the access gateway of the local data network, activates the transmission of the downlink data on the target user plane path for the local data stream by creating a tunnel or updating the tunnel context, and completes the path switching; the UP GW is based on the trigger information on the source user side.
  • the end tag is sent on the path and the context of the local data stream is updated.
  • a handover resource preparation phase based on an S1 interface or an X2 interface.
  • the UE, the AN1 node, the AN2 node, the CP node, the user plane gateway UP GW, the edge gateway Edge GW, the access gateway Access GW, and the MANO prepare network resources for the UE on the target user plane path in the handover procedure, for example,
  • the network resource may be prepared based on the handover of the X2 interface, or may be the network resource based on the handover of the S1 interface.
  • the AN1 node is used as the source AN node
  • the AN2 node is the target AN node as an example.
  • the source user plane path is a path including the UE, the AN1, the UP GW, and the Access GW
  • the target user plane path is a path including the UE, the AN2, the Edge GW, and the Access GW.
  • the first bearer is between the UE and the first bearer
  • the first tunnel is between the AN1 and the UP GW.
  • the second bearer between the UE and the AN2 is the second bearer (Second Bearer), and between the AN2 and the Edge GW.
  • the second tunnel (Second Tunnel); the Edge GW and the Access GW are external tunnels.
  • the source AN node sends the handover requirement to the UE.
  • the source AN node sends a handover request (Handover Command) to the UE; the UE receives the handover requirement sent by the source AN node; that is, the AN1 node notifies the UE to perform handover of the path.
  • a handover request Handover Command
  • the UE sends a Handover Confirmation message to the target AN node.
  • the AN2 node receives the handover confirmation message sent by the UE.
  • the target AN node sends a handover notification (Handover notify) or a path handover request (Handover Request) to the CP node.
  • Handover notify a handover notification
  • Handover Request a path handover request
  • the AN2 node notifies the CP node that the UE has successfully switched to AN2.
  • the CP node selects an edge gateway according to the handover notification or the path switching request.
  • the CP node selects an edge gateway (Edge GW) included in the target user plane path for the UE according to the handover notification or the path switch request, and activates the path of the Edge GW to the AN2 node for the local data stream; that is, the CP node selects a new edge for the local data stream. Gateway, activate the new user plane path.
  • the local data stream is a data packet sent by the local network. It should be understood that the handover notification or path switching request herein includes the IP address of the UE and the IP address of the edge gateway.
  • the CP node sends a session update request to the edge gateway.
  • the session update request may be an Update Bearer Request, and the update bearer request may also carry the NG3 interface information; the CP node sends an update bearer request to the edge gateway; and the edge gateway receives the update bearer request sent by the CP node. That is, the CP node notifies the edge gateway to create a target user plane path for the local data stream, where the information carried includes but is not limited to the path information of the AN2 node: specifically the IP address and tunnel ID of the AN2 node; the path information of the edge gateway: the edge gateway The IP address and the tunnel ID; the second traffic filter template (TFT) or the second service flow template, the quality of service (QoS) information, and the like.
  • TFT traffic filter template
  • QoS quality of service
  • the second service flow template here is used to filter data packets sent by the local network.
  • the second service flow template is information of a non-access stratum (NAS) layer, and the AN node transmits the second service flow template to the UE, so that the UE prepares the context.
  • NAS non-access stratum
  • the edge gateway sends a session update response to the CP node.
  • the session update response herein may be an update bearer response; the edge gateway sends an Update Bearer Response to the CP node; the control plane CP node receives the session update response sent by the CP node, and the session update response includes the target user of the UE.
  • the identifier of the surface path, the target user plane path includes the edge gateway Edge GW; that is, the CP node receives the acknowledgement message sent by the edge gateway.
  • the CP node sends the trigger information and the ID of the source user plane path to the UP GW according to the session update response.
  • the CP node sends the trigger information and the ID of the source user plane path to the UP GW according to the session update response, and the trigger information and the ID of the source user plane path are used by the UP GW to send an end tag to the source AN node on the source user plane path.
  • the user plane gateway UP GW receives the trigger information sent by the control plane CP node and the ID of the source user plane path, and the UP GW is located on the source user plane path of the user equipment UE.
  • the CP node may also send a second service flow template to the UP GW, where the second service flow template is used to filter the data packets sent by the local network.
  • the trigger information herein may be at least one of a first service flow template and a timer parameter, where the first service flow template is used to detect the end data packet, and the end data packet is used to represent the source user surface path.
  • the last transmitted packet may be several possibilities for the trigger information here: (1) the first business flow template; (2) the first Service flow template and timer parameters; (3) timer parameters.
  • the trigger information here may also be an indication identifier, which is not limited.
  • the first service flow template is different from the second service flow template mentioned above, where the first service flow template is used to filter the end data packet, that is, the UP GW filters according to the first service flow template.
  • the end packet transmitted from the Access GW when the UP GW filters out the end packet, the UP GW sends an End Marker to the source AN node.
  • the second service flow template may also be as shown in Table 2 below, or when the table 2 is deleted from the path identifier ID, it may also be used as the second service flow template:
  • the timer parameter herein may be an exemplary value, such as 2 ms, then the value of the timer on the UP GW side may be set to 0-2 ms, and the timeout is over 2 ms, and the timer may also be set to 8-10ms, more than 10ms is a timeout, the initial value of the timer can be determined according to the actual situation; the timer parameter can also be the interval parameter, that is, the interval parameter is [a, b], then the initial of the timer can be The value is set to a value, and the timeout value is set to b value.
  • the UP GW when the trigger information is a timer parameter, after the UP GW receives the trigger information sent by the control plane CP node, the UP GW starts the timer immediately.
  • the CP node sends a request for updating the context to the UP GW before triggering the local data flow path switching, and carries the trigger information, where the trigger information may be the first service flow template and/or timer parameters, related path information, local data flow TFT, etc. information.
  • the second service flow template may also be referred to as a local data flow TFT, where the second service flow template may also be one or more IP quintuple information, for example (UE IP, 10000, App IP, 80, GTP-U).
  • the CP node may also send a path switch response to the AN2 node, which is used to tell the AN2 node that the downlink can be transmitted to the UE through the AN2 node. The packet is gone.
  • the CP node sends a path switch notification or a path switch request to the MANO.
  • the handover notification or the path switch request includes the IP address of the UE and the IP address of the edge gateway. In actual applications, information such as the IP address of the APP may also be included.
  • the handover notification or the path switch request herein further includes the first service flow template.
  • the MANO sends a path switch notification or a path switch request to the Access GW access gateway.
  • the handover notification or the path switch request may include the Internet Protocol IP address of the user equipment UE and the IP address of the edge gateway; when the trigger information in step 1108 is the first service flow template, or the first service flow template and the timer parameter.
  • the handover notification or path switch request herein also includes the first service flow template.
  • the first service flow template is the same as the first service flow template sent by the control plane CP node to the user plane gateway UP GW, and is used to determine the end data packet, and the edge gateway is located on the target user plane path.
  • the Access GW sends the downlink data packet of the UE to the edge gateway according to the IP address of the UE and the IP address of the edge gateway.
  • the access gateway may determine the target user plane path of the UE according to the IP address of the UE and the IP address of the edge gateway, and complete the handover of the UE user plane path, and the Access GW may send the downlink data packet of the UE on the target user plane path. That is, the Access GW sends the downlink data packet of the UE to the edge gateway.
  • the Access GW sends the downlink data packet of the UE on the source user plane path.
  • the Access GW sends the data packet to the UP GW according to the first service flow template.
  • the UP GW is located on the source user plane path; the UP GW receives the end data packet sent by the Access GW. It should be understood that the IP quintuple information of the end packet sent to the UP GW here is determined by the first service flow template.
  • step 1412 is an optional step, that is, when the trigger information in step 1408 is a timer parameter, step 1412 is optional. That is, in the actual application, (1) when the trigger information is the first service flow template, the Access GW sends an end data packet to the UP GW according to the first service flow template, and the IP quintuple information of the end data packet is first. One of the IP quintuple information included in the business flow template is the same. (2) When the trigger information is the first service flow template and the timer parameter, the Access GW sends multiple end data packets to the UP GW according to the first service flow template, and then the IP quintuple information of the multiple end data packets. The information may be the same or different, but the IP quintuple information of the multiple end packets needs to be included in the first service flow template.
  • the format of the end packet may be (UE IP, 10000, App IP, 80, GTP-U) and/or (UP GW IP, 10000, Edge GW IP, 80, GTP-U) and the like.
  • the key to constructing the end packet is that it can reach the UP GW and can be recognized by the UP GW. Therefore, the CP node sends the first service flow template to the UP GW and the Access GW.
  • the end data packet can also be constructed by a control plane, an edge gateway, etc., as follows: The control plane or the edge gateway generates an empty IP data packet according to the first service flow template, and the IP data packet header uses the first service flow. The IP address and port number in the template are filled, and the IP packet load is filled with a protocol header by using the protocol information in the first service flow template.
  • the UP GW sends an end tag to the AN node on the source user plane path according to the trigger information and the ID of the source user plane path.
  • the end tag is used by the AN node to sort the downlink data packets received on the target user plane path; the access network AN node receives the end tag sent by the UP GW.
  • it may include:
  • the trigger information includes the first service flow template; when the IP quintuple information of the downlink data packet of the UE received by the UP GW is the same as any of the IP quintuple information in the first service flow template, the UP GW is based on the source.
  • the ID of the user plane path, An end tag is sent to the AN node on the source user plane path.
  • the first service flow template here can be simply understood as the end packet filter. After detecting the end packet coming from the Internet path, the UP GW sends an end tag on the source user plane path and updates the context of the local data stream.
  • the trigger information includes the first service flow template and the timer parameter; when the IP quintuple information of the downlink data packet of the UE received by the UP GW is the same as any of the IP quintuple information in the first service flow template, The UP GW starts the timer, and the timer is set according to the timer parameter. If the UP GW receives the end packet and the timer does not expire, the UP GW restarts the timer, and ends the IP quintuple information of the packet with the first Any IP quintuple information in the service flow template is the same; when the timer expires, the UP GW sends an end tag to the AN node according to the ID of the source user plane path.
  • the UP GW After the UP GW detects the end packet sent from the source user plane path according to the first service flow template, the UP GW starts the timer, and if the UP GW receives other subsequent end packets or When receiving a packet sent by the local network, the UP GW resets the timer; if the end packet is not received or the packet sent by the local network causes the timer to expire, the UP GW immediately follows the source user plane path. Send an end tag on it and update the context of the local data stream.
  • the trigger information includes a timer parameter, and the UP GW sets a timer according to the timer parameter; the UP GW starts a timer; when the timer expires, the UP GW sends an AN to the source user plane path according to the ID of the source user plane path.
  • the node sends an end tag.
  • the time when the timer is started is that when the UP GW receives the timer parameter, the timer is started immediately. If the UP GW receives the data packet sent by the local network within the timer time, the timer is reset; If the UP GW continues to receive the data packet sent by the local network and the timer expires, it indicates that the transmission of the data packet sent by the local network on the source user plane path (Internet) ends, and the end tag is sent and updated on the source user plane path.
  • the context of the local data stream is that when the UP GW receives the timer parameter, the timer is started immediately. If the UP GW receives the data packet sent by the local network within the timer time, the timer is reset; If the UP GW continues to receive the data packet sent by the local network and the timer expires, it indicates that the transmission of the data packet sent by the local network on the source user plane path (Internet) ends, and the end tag is sent and updated on the source user plane path.
  • the source AN node sends an end tag to the target AN node.
  • the end AN is forwarded by the source AN node to the target AN node through a forwarding tunnel between the source AN node and the target AN node.
  • the target access network AN node sorts the downlink data packets received on the target user plane path according to the end tag.
  • the target AN node buffers the downlink data packet received on the target user plane path, and after receiving the end tag, can activate the downlink data packet that is sent to the target user plane path. Processing.
  • the UP GW determines whether the UP GW sends the end tag according to the trigger information and the ID of the source user plane path, and the trigger information may be the first service flow template and/or the timer parameter, and the source AN node.
  • the end tag is forwarded to the target AN node, and the target AN node sorts the downlink data packets received on the target user plane path according to the end tag. That is, the enhancement of the end marker forwarding method in the EPS system solves the problem that the UP GW cannot determine when to send the end tag and the order of the downlink data cannot be guaranteed because the residual data still remains in the Internet. It can enhance the function of the user plane gateway, and can reuse most of the functions of the traditional network element. It does not need to modify the existing switching process in a wide range, which is simple and clear, and easy to implement. Resolve the loss of a small amount of data on the source user plane path due to the unreliability of the Internet.
  • FIG. 15 is a schematic diagram of another embodiment of a method for sending an end tag in an embodiment of the present application, including:
  • the trigger information is first notified to the UP GW (the user plane gateway before the handover path); then the edge gateway is notified, and the edge gateway is notified.
  • the access gateway of the local data network is notified to activate the transmission of the downlink data on the target user plane path for the local data stream by creating a tunnel or updating the tunnel context, and completing the path switching; the UP GW sends an end tag on the source user plane path according to the trigger information. And update the context of the local data stream.
  • a handover resource preparation phase based on an S1 interface or an X2 interface.
  • the source AN node sends the handover requirement to the UE.
  • the UE sends a handover confirmation message to the target AN node.
  • the target AN node sends a handover notification or a path switch request to the CP node.
  • the CP node selects an edge gateway according to the handover notification or the path switching request.
  • the steps 1501-1505 are similar to the steps 1401-1405 in FIG. 14, and details are not described herein again.
  • the CP node sends local data flow information to the MANO, and obtains an IP address of the Access GW.
  • the CP node sends the local data stream information to the MANO; the MANO sends the IP address of the Access GW to the CP node according to the local data stream information.
  • the local data flow information includes the local IP address that the UE is using, and the MANO finds the access gateway information of the local network where the local IP address is located according to the local configuration information.
  • the CP node sends the trigger information and the ID of the source user plane path to the UP GW.
  • the CP node sends the trigger information and the ID of the source user plane path to the UP GW, and the ID of the trigger information and the source user plane path is used by the UP GW to send an end tag to the source AN node.
  • the user plane gateway UP GW receives the trigger information sent by the control plane CP node and the ID of the source user plane path, and the UP GW is located on the source user plane path of the user equipment UE.
  • the CP node may also send a second service flow template to the UP GW, where the second service flow template is used to filter the data packets sent by the local network.
  • the trigger information herein may be at least one of a first service flow template and a timer parameter, where the first service flow template is used to detect the end data packet, and is used to indicate the last transmission on the source user plane path. Packet. For details, refer to the description in step 1408 in FIG. 14 , and details are not described herein again.
  • the CP node sends a session update request to the edge gateway.
  • step 1508 is similar to step 1406 in FIG. 14, and details are not described herein again.
  • the edge gateway sends a path switch notification or a path switch request to the Access GW.
  • the handover notification or path switch request herein includes the IP address of the UE and the IP address of the edge gateway. It should be noted that, when the trigger information is the first service flow template, or the first service flow template and the timer parameter, the handover notification or the path switch request herein further includes the first service flow template.
  • the edge gateway sends a session update response to the CP node.
  • the Access GW sends the downlink data packet of the UE to the edge gateway according to the IP address of the UE and the IP address of the edge gateway.
  • the Access GW sends the data packet to the UP GW according to the first service flow template.
  • the UP GW sends an end tag to the source AN node according to the trigger information.
  • the source AN node sends an end tag to the target AN node.
  • the target access network AN node sorts the downlink data packets received on the target user plane path according to the end tag.
  • step 1510 is similar to step 1407 in FIG. 14, and steps 1511-1515 are similar to steps 1411-1415 in FIG. 14, and details are not described herein again.
  • the control plane CP node does not switch the path through the MANO, but notifies the edge gateway to establish a tunnel or update to the access gateway of the local data network.
  • the source user plane gateway is enhanced to support the control plane node to carry the trigger information, and the user plane gateway determines the end of the local data stream on the source user plane path according to the trigger information, to send the end tag and update the user plane context. That is, the UP GW determines when to send the end tag by terminating whether the data packet and/or the timer expires, and the auxiliary target AN node sorts the downlink data received by the target user plane path.
  • the user plane gateway cannot determine when to send the end tag, and cannot guarantee the order of the downlink data, thereby enhancing the user plane.
  • the gateway function can reuse most of the functions of the traditional network element, without extensive modification of the existing switching process, simple and clear, and easy to implement.
  • FIG. 16 is a schematic diagram of another embodiment of a method for sending an end tag according to an embodiment of the present application, including:
  • the AN node cannot identify the local data flow to be switched according to the source user plane path identifier, and cannot assist the AN node to sort the downlink data packets received on the target user plane path, and therefore, is established.
  • the CP node sends a flow switching indication message to the AN node, and the AN node performs a flow switching indication message according to the indication, and detects an event: the data packet before the end tag is received on the original air interface data bearer (sent by the local network) Whether the data packet sent by the data packet and the Internet is successfully transmitted to the UE. If successful, the AN node sorts the downlink data packet received on the target user plane path according to the end tag. As follows:
  • the CP node selects an edge gateway according to the received user plane report/handover request/application request.
  • the CP node receives the handover request sent by the AN node, or receives the application request sent by the MANO, or receives the user plane report sent by the UP GW, and selects an edge gateway for the local data flow, where the edge gateway is located on the target user plane path.
  • the role of the user plane report is that the user plane reports to the CP node, and now there is a local data stream of the UE, then the CP node knows that there is a local data stream message.
  • the source user plane path is a path including the UE, the AN, the UP GW, and the Access GW
  • the target user plane path is a path including the UE, the AN, the Edge GW, and the Access GW.
  • the first wireless data bearer (DRB) between the UE and the AN node on the source user plane path and the second wireless data between the UE and the AN node on the target user plane path are required to be described.
  • the bearers are not the same.
  • the first bearer DRB, the AN node and the UP GW are the primary tunnels between the UE and the AN node; after the path switching of the UE, the second bearer DRB is between the UE and the AN node.
  • the secondary tunnel is a secondary tunnel between the AN node and the Edge GW; the external tunnel is between the Edge GW and the Access GW.
  • the CP node sends a bearer configuration request to the AN node, where the bearer configuration request includes a flow switching indication message.
  • the CP node sends a bearer configuration request to the AN node; the AN node receives the bearer configuration request sent by the CP node, where the bearer configuration request includes the flow switching indication information, the ID of the source user plane path, and the path information of the edge gateway. Information such as the second business flow template.
  • the flow switching indication message is used to indicate that the AN node is receiving When the end tag is reached, it is determined whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE. That is, the CP node notifies the AN node to prepare resources for the target user plane path, and the bearer configuration request carries the path information of the edge gateway, and carries the local data stream reselection path indication.
  • the second service flow template is used to filter the data packets sent by the local network, which is information of a non-access stratum (NAS) layer, and the AN node transmits the second service flow template to the UE to let the UE Prepare the context.
  • NAS non-access stratum
  • the AN node sends a Radio Resource Control (RRC) connection reconfiguration (RRC Connection Reconfiguration) message to the UE.
  • RRC Radio Resource Control
  • the UE sends an RRC Connection Reconfiguration Complete (RRC Connection Reconfiguration Complete) message to the AN node.
  • RRC Connection Reconfiguration Complete RRC Connection Reconfiguration Complete
  • Steps 1603 and 1604 are used for the AN node to prepare the air interface data bearer.
  • the AN node sends a bearer configuration response (Berarer Setup Response) to the CP node.
  • Bearer configuration response Berarer Setup Response
  • the downlink data packet received by the AN node on the source user plane path includes the data packet sent by the local network and the Internet data packet, and the original path switching of the UE is to switch the data packet sent by the local network to the target user plane. Transfer to the UE on the path.
  • the AN node has a receiving flow switching indication message, and the flow switching indication message is used to indicate that the AN node determines whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE when receiving the end tag. Therefore, after the air interface data bearer preparation is completed, the AN node transmits the downlink data packet received on the source user plane path to the UE on the first DRB.
  • the UE sends a Handover Confirmation message to the CP node.
  • the UE After the UE prepares to complete the handover of the local data stream, the UE sends a response message to the control plane.
  • the CP node sends local data flow information to the MANO, and obtains an IP address of the Access GW.
  • the local data flow information includes the local IP address that the UE is using, and the MANO finds the access gateway information of the local network where the local IP address is located according to the local configuration information.
  • the CP node sends the trigger information and the ID of the source user plane path to the UP GW.
  • the ID of the trigger information and the source user plane path is used by the UP GW to send an end tag to the AN node.
  • the CP node may also send a second service flow template to the UP GW, where the second service flow template is used to filter the data packets sent by the local network.
  • the trigger information herein may be at least one of a first service flow template and a timer parameter, where the first service flow template is used to detect the end data packet, and is used to indicate the last transmission on the source user plane path. Packet. For details, refer to the description in step 1408 in FIG. 14 , and details are not described herein again.
  • the CP node sends a session update request to the edge gateway.
  • the session update request herein may be a Bearer Setup Request for the CP node to notify the edge gateway to create a target user plane path for the local data stream.
  • the information carried in the session update request includes, but is not limited to, path information of the AN end: specifically an IP address and a tunnel ID of the AN; path information of the edge gateway: an IP address and a tunnel ID of the edge gateway; and a second flow filter template (Traffic)
  • the Filter Template (TFT) or the name is the second service flow template, and the quality of service (QoS) information.
  • TFT Filter Template
  • QoS quality of service
  • the edge gateway sends a path switch notification to the Access GW.
  • the handover notification herein includes the IP address of the UE and the IP address of the edge gateway. It should be noted that, when the trigger information is the first service flow template, or the first service flow template and the timer parameter, the handover notification or the path switch request further includes the first service flow template, where the first service flow is The template is used to determine the end of the packet.
  • the edge gateway sends a session update response to the CP node.
  • the session update response may be a Bearer Setup Rsponse;
  • the bearer configuration response may include an identifier of a target user plane path of the UE, and the target user plane path includes an edge gateway Edge GW; that is, the CP node receives the edge gateway.
  • the Access GW sends the downlink data packet of the UE to the edge gateway according to the IP address of the UE and the IP address of the edge gateway.
  • the Access GW sends the data packet to the UP GW according to the first service flow template.
  • the UP GW sends an end tag to the access network AN node on the source user plane path according to the trigger information and the ID of the source user plane path.
  • steps 1612-1614 are similar to steps 1411-1413 shown in FIG. 14, and details are not described herein again.
  • the AN node sorts the downlink data packets received on the target user plane path according to the end tag.
  • the AN node determines whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE; if the AN node receives the source user plane path The downlink data packet of the UE has been successfully sent to the UE, and the AN node sorts the downlink data packets received by the AN node on the target user plane path of the UE according to the end marker. If at least one data packet in the downlink data packet received by the AN node on the source user plane path is not successfully sent to the UE, the AN node sends at least one data packet to the UE.
  • the downlink data packet received by the AN node here includes a data packet and an Internet data packet sent by the local network, and the data packet sent by the local network is generated by the local data network and transmitted through the Internet, and the Internet data packet is sent by the Internet.
  • the AN node buffers the downlink data packet received on the target user plane path, that is, the AN node receives the end tag and the original air interface data bearer according to the flow switching indication message. After the data packet is sent, the processing of the downlink data packet from the target user plane path can be activated.
  • the AN node when the end node does not receive the end tag, the AN node has sent the downlink data packet received on the source user plane path to the UE on the first DRB, if the downlink data packet received by the AN node on the source user plane path has 10 Then, the AN sends the 10 downlink data packets to the UE on the first DRB, and if successfully sent to the UE, the UE receives the success identifier fed back by the UE.
  • the AN node When the AN node receives the end tag, if the AN node has received the success indications fed back by the 10 UEs, it proves that the data packets sent by the UE to the UE on the first DRB are successfully sent, then the AN node can end according to the end.
  • the sequence number in the tag sorts the downlink data packets received on the target user plane path, and sends the sorted downlink data packets to the UE on the second DRB.
  • the AN node When the AN node receives the end tag, if the AN node only receives the success indications fed back by the 8 UEs, it proves that the data packets sent by the UE to the UE on the first DRB have not been successfully sent to the UE, and if not yet sent, Then, the remaining two downlink data packets are sent to the UE on the first DRB, and wait for the success indication of the feedback. If the successful identifier is not received, the UE continues to wait until all the packets are successfully sent to the UE. , then, the AN node can The downlink data packets received on the target user plane path are sorted according to the sequence number in the end tag, and the sorted downlink data packets are sent to the UE on the second DRB.
  • the UP GW determines when the UP GW sends an end tag by ending the timeout of the data packet and/or the timer, and the auxiliary target AN node sorts the downlink data packet. Further, the air interface uses the air interface data bearer for the downlink data packet received on the source user plane path. When the path resource on the AN node is created, the flow switching indication message is sent, where the flow switching indication message is used to indicate that the AN node is in the source user.
  • the end tag When the end tag is received on the plane path, it is determined whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE; if successfully sent to the UE, the AN node may follow the end marker to the target user plane path.
  • the received downlink data packet is sorted, that is, the AN node can determine the activation time of the downlink data packet received on the target user plane path, thereby solving the local data flow because the AN node cannot recognize the path to be switched. The resulting out-of-order problem with the packet.
  • FIG. 17 is a schematic diagram of another embodiment of a method for sending an end tag according to an embodiment of the present application, including:
  • the AN node does not need to identify the local data stream, but selects a branch node in the core network when preparing the path resource, and forwards the downlink data packet received by the AN node on the source user plane path to the branch node.
  • the diverting node helps identify the local data stream, it sends the local data stream to the edge gateway, and the edge gateway sends the local data stream to the AN node.
  • the end tag is on the target user plane path.
  • the received downstream data packet is sorted.
  • the shunt node is described as UP GW:
  • the CP node selects an edge gateway according to the received user plane report/handover request/application request.
  • the CP node receives the handover request sent by the AN node, or receives the application request sent by the MANO, or receives the user plane report sent by the UP GW, and selects an edge gateway for the local data flow, where the edge gateway is located on the target user plane path.
  • the role of the user plane report is that the user plane reports to the CP node, indicating that there is a local data stream of the UE on the source user plane path, then the CP node knows that there is a local data stream message.
  • the source user plane path is a path including a UE, an AN node, an UP GW, and an Access GW
  • the target user plane path is a path including a UE, an AN node, an Edge GW, and an Access GW.
  • the first wireless data bearer (DRB) between the UE and the AN node on the source user plane path and the second wireless data between the UE and the AN node on the target user plane path are required to be described.
  • the bearers are not the same.
  • the first bearer DRB, the AN node and the UP GW are the primary tunnels between the UE and the AN node; after the path switching of the UE, the second bearer DRB is between the UE and the AN node.
  • the secondary tunnel is a secondary tunnel between the AN node and the Edge GW; the external tunnel is between the Edge GW and the Access GW.
  • the CP node sends a bearer configuration request to the AN node.
  • the CP node sends a Bearer Setup Request to the AN node.
  • the AN node receives the bearer configuration request sent by the CP node.
  • the bearer configuration request includes the path information of the edge gateway and the second service flow template. That is, the CP node notifies the AN node to prepare resources for the target user plane path, the bearer configuration request carries the path information of the edge gateway, the second service flow template, and the like, and the second service flow template is used to filter the data packet sent by the local network.
  • the second service flow template is information of a non-access stratum (NAS) layer, and the AN node transmits the second service flow template to the UE, so that the UE prepares the context.
  • NAS non-access stratum
  • the AN node sends an RRC connection reconfiguration message to the UE.
  • the UE sends an RRC connection reconfiguration complete message to the AN node.
  • the AN node sends a bearer configuration response to the CP node.
  • the UE sends a path switch confirmation message to the CP node.
  • the CP node sends local data flow information to the MANO, and obtains an IP address of the Access GW.
  • the CP node sends the trigger information and the ID of the source user plane path to the UP GW.
  • the CP node sends a session update request to the edge gateway.
  • the edge gateway sends a path switch notification to the Access GW.
  • the edge gateway sends a session update response to the CP node.
  • the steps 1703-1711 are similar to the steps 1603-1611 shown in FIG. 16, and details are not described herein again.
  • the CP node sends a tunnel update message to the AN node, where the tunnel update message includes a flow switching indication message.
  • the CP node sends a tunnel update message to the AN node, and the AN node receives the tunnel update message sent by the CP node, where the tunnel update message includes a flow switching indication message and an ID of the source user plane path, and the flow switching message information is used to indicate the AN node to
  • the UP GW sends the downlink data packet received by the AN node on the source user plane path.
  • the downlink data packet received at the AN node includes a data packet and an Internet data packet sent by the local network.
  • the Access GW sends the downlink data packet of the UE to the edge gateway according to the IP address of the UE and the IP address of the edge gateway.
  • the Access GW sends the data packet to the UP GW according to the first service flow template.
  • the UP GW sends an end tag to the access network AN node on the source user plane path according to the trigger information and the ID of the source user plane path.
  • steps 1713-1715 are similar to steps 1411-1413 shown in FIG. 14, and details are not described herein again.
  • the AN node sends, according to the flow switching indication message, the downlink data packet received by the AN node on the source user plane path to the UP GW.
  • the AN node when the AN node receives the end tag, it also forwards the end tag to the UP GW, but stops forwarding the downlink data packet on the source user plane gateway received by the AN node to the UP GW.
  • the AN node forwards the 15 data packets to the UP GW through the forwarding tunnel shown in FIG. It should be noted that when the AN node receives the downlink data packet of the UE on the target user plane path, the data packet is buffered, and the data packet is not sorted first.
  • the UP GW identifies, according to the ID of the second service flow template and the source user plane path, the data packet sent by the local network from the downlink data packet sent by the receiving AN node on the source user plane path.
  • the CP node further sends a second service flow template to the UP GW, where the second service flow template is used to identify the data packet sent by the local network;
  • the GW identifies the data packet sent by the local network from the downlink data packet sent by the receiving node on the source user plane path according to the ID of the second service flow template and the source user plane path.
  • the UP GW identifies 10 data packets sent by the local network from the above 15 data packets according to the IDs of the second service flow template and the source user plane path, and then passes the remaining 5 Internet data packets through the UP GW and The forwarding tunnel between the AN nodes is sent to the AN node, and the AN node sends the 5 Internet data packets to the UE on the first DRB.
  • the ID of the source user plane path in the 4G is an EPS Bearer ID
  • the 5G is now a Protocol Data Unit Session Identifier (PDU Session ID).
  • PDU Session ID Protocol Data Unit Session Identifier
  • the UP GW node forwards the identified data packet to the edge gateway.
  • the UP GW forwards the 10 data packets sent by the local network to the edge gateway through a forwarding tunnel between the UP GW and the edge gateway. It should be noted that when the UP GW receives the end tag, the end tag is forwarded to the edge gateway.
  • the edge gateway forwards the received identified data packet to the AN node.
  • the edge gateway forwards the 10 packets sent by the local network to the AN node through the secondary tunnel. It should be noted that when the edge gateway receives the end tag forwarded by the UP GW, the end tag is sent to the AN node.
  • timing of steps 1713-1715 and the timing of steps 1716-1719 are not limited.
  • the AN node sorts the downlink data packets received on the target user plane path according to the end tag.
  • the data packet currently received by the AN node may include: (1) Internet data packets forwarded from the UP GW; (2) data packets sent by the local network forwarded from the edge gateway; (3) at the target user The downlink packet received on the face path; (4) the end tag forwarded from the edge gateway.
  • the AN node sends Internet data packets (5) to the UE on the first DRB, and sends the data packets (10) sent by the local network to the UE on the second DRB, and the AN node pairs the target user plane path according to the end tag.
  • the received downlink data packets are sorted, and the sorted downlink data packets are sent to the UE through the second DRB.
  • the AN node determines whether the Internet data packet sent by the AN node to the UE has been successfully sent. If the AN node successfully transmits, the AN node receives the received data on the target user plane path according to the end tag. The downlink data packet is sorted; if the Internet data packet is not successfully sent, the AN node may continue to send the Internet data packet to the UE. When the transmission succeeds, the AN node performs the downlink data packet received on the target user plane path according to the end tag. Sort.
  • Edge GW different forwarding paths may be established, such as AN-UP GW-Edge GW, AN-UP GW-AN, AN-Edge GW-UP GW, AN-Edge GW-Edge GW, AN-Edge GW-AN-UP GW.
  • Edge GW different forwarding paths may be established, such as AN-UP GW-Edge GW, AN-UP GW-AN, AN-Edge GW-UP GW, AN-Edge GW-Edge GW, AN-Edge GW-AN-UP GW.
  • FIG. 14 will not be described in detail herein.
  • the UP GW determines when the UP GW sends an end tag by terminating whether the data packet and/or the timer expires, and the auxiliary AN node performs a sorting process on the downlink data packet received on the target user plane path.
  • the difference is that the core network UP GW is selected as the offload node, that is, the AN node first forwards the downlink data packet sent from the UP GW to the AN node back to the UP GW until the end maker is received, and the recovery is completed. Normal transmission.
  • the UP GW After detecting the end of the data packet, the UP GW sends an end tag on the source user plane path to stop the transmission of the data packet on the source user plane path until the end marker end tag forwarded by the AN node is received.
  • the UP GW detects the data packet sent by the local network from the forwarded data packet, and forwards it to the Edge GW. After receiving the end marker forwarded by the AN node, the UP GW sends the data packet to the Edge GW. After receiving the end tag, the Edge GW forwards the packet back to the AN node to activate the sorting process of the upstream and downstream packets on the target user plane path.
  • FIG. 18 is a schematic diagram of another embodiment of a method for sending an end tag in the embodiment of the present application, including:
  • the AN node can temporarily support the TFT, that is, the AN node can identify the local data stream in the downlink data packet received from the target user plane path according to the TFT, and send the local data stream to the UE by using the second DRB.
  • the AN node then sorts the downlink datagram packets received on the target user plane path according to the end tag. As follows:
  • the CP node selects an edge gateway according to the received user plane report/handover request/application request.
  • the CP node receives the handover request sent by the AN node, or receives the application request sent by the MANO, or receives the user plane report sent by the UP GW, and selects an edge gateway for the local data flow, where the edge gateway is located on the target user plane path.
  • the role of the user plane report is that the user plane reports to the CP node, and now there is a local data stream of the UE, then the CP node knows that there is a local data stream message.
  • the source user plane path is a path including a UE, an AN node, an UP GW, and an Access GW
  • the target user plane path is a path including a UE, an AN node, an Edge GW, and an Access GW.
  • the second wireless data bearer between the first radio data bearer (DRB) between the UE and the AN and the UE and the AN node on the target user plane path on the source user plane path.
  • the first bearer DRB, the AN node and the UP GW are the primary tunnels between the UE and the AN node; after the path switching of the UE, the second bearer DRB is between the UE and the AN node.
  • the secondary tunnel is a secondary tunnel between the AN node and the Edge GW; the external tunnel is between the Edge GW and the Access GW.
  • the first node sends a Bearer Setup Request (Bearer Setup Request) to the AN node.
  • Bearer Setup Request Bearer Setup Request
  • the bearer configuration request includes flow switching indication information, an ID of the source user plane path, path information of the edge gateway, and a second service flow template.
  • the flow switching indication message is used to instruct the AN node to send, by the target DRB, the data packet sent by the local network received by the AN node on the source user plane path to the UE according to the ID of the service flow template and the source user plane path, where the target DRB is at the UE.
  • the transmission path between the UE and the AN node on the target user plane path, that is, the second DRB, the second service flow template is used to filter the data packets sent by the local network.
  • the CP node notifies the AN node to prepare resources for the target user plane path, and carries the path information of the edge gateway, the ID of the source user plane path, and the local data stream reselection path indication, and the second service flow template.
  • the AN node sends an RRC connection reconfiguration message to the UE.
  • the UE sends an RRC connection reconfiguration complete message to the AN node.
  • the AN node sends a bearer configuration response to the CP node.
  • the UE sends a path switch confirmation message to the CP node.
  • the CP node sends local data flow information to the MANO, and obtains an IP address of the Access GW.
  • the CP node sends the trigger information and the ID of the source user plane path to the UP GW.
  • the CP node sends a session update request to the edge gateway.
  • the edge gateway sends a path switch notification to the Access GW.
  • the edge gateway sends a session update response to the CP node.
  • steps 1803-1811 are similar to the steps 1603-1611 shown in FIG. 16 and will not be further described herein.
  • the Access GW sends the downlink data packet of the UE to the edge gateway according to the IP address of the UE and the IP address of the edge gateway.
  • the Access GW sends the data packet to the UP GW according to the first service flow template.
  • the UP GW sends an end tag to the access network AN node on the source user plane path according to the trigger information and the ID of the source user plane path.
  • steps 1812-1814 are similar to the steps 1411-1413 shown in FIG. 14, and are not described herein again.
  • the AN node identifies the data packet sent by the local network according to the ID of the service flow template and the source user plane path.
  • the AN node identifies the data packet sent by the local network according to the ID of the second service flow template and the source user plane path, and the data packet sent by the local network is sent by the local data network via the Internet.
  • the service flow template includes multiple IP quintuple information, and each data packet includes IP quintuple information, as shown in Table 4 below, an example of the second service flow template:
  • the IP quintuple information in the 15 data packets appears in the second service flow template of Table 1, then these The data packet belongs to the data packet sent by the local network, and the IP quintuple information does not appear in the second service flow template shown in Table 4, and belongs to the Internet data packet. Assume that there are 10 packets transmitted by the AN network and configured by the local network, and there are 5 Internet packets.
  • the AN node sends the identified data packet to the UE by using the target DRB according to the flow switching indication message.
  • the AN node sends the identified data packet to the UE through the target DRB according to the flow switching indication message; that is, the AN node sends 5 Internet data packets to the UE through the first DRB, and passes 10 data packets sent by the local network.
  • the second DRB sends to the UE.
  • timings of steps 1815 and 1816 and 1803-1814 are not limited.
  • the AN node sorts the downlink data packets received on the target user plane path according to the end tag.
  • the AN node first buffers the downlink data packets received on the target user plane path before receiving the end marker. After receiving the end tag, the AN node sorts the downlink data packets received on the user plane path according to the sequence number in the end tag, and then sends the sorted downlink data packet to the UE through the second DRB, and the AN node needs to delete.
  • the second business flow template is a code that specifies the sequence number in the end tag.
  • the UP GW determines when the UP GW sends an end tag by ending the timeout of the data packet and/or the timer, and the auxiliary target AN node sorts the downlink data packet.
  • the air interface uses the air interface data bearer for the local data stream, and the AN node can temporarily support the TFT to identify the local data stream.
  • a flow switching indication message is sent, where the flow switching indication message is used to indicate that the AN node is to be in the AN according to the ID of the service flow template and the source user plane path.
  • the data packet sent by the local network received on the source user plane path is sent to the UE by using the target DRB; then, the AN node may sort the downlink data packet received on the target user plane path according to the received end tag. That is, the AN node can determine the activation time of the downlink data packet received on the target user plane path, thereby solving the disorder problem of the data packet caused by the AN node not being able to recognize the local data stream of the path to be switched.
  • a schematic diagram of an embodiment of a planar CP node comprising:
  • the receiving module 1901 is configured to receive a session update response, where the session update response includes an identifier ID of a source user plane path of the user equipment UE or an ID of a target user plane path of the UE, where the source user plane path includes a user plane gateway UP GW;
  • the sending module 1902 is configured to send, according to the session update response, the trigger information and the ID of the source user plane path to the UP GW, where the trigger information is used by the UP GW to send an end tag to the access network AN node on the source user plane path.
  • the CP node shown in FIG. 19 can be used to perform the method as shown in any of the above-described FIGS. 11-18, and the same or corresponding technical features can be cited in the present embodiment.
  • the trigger information includes at least one of a first service flow template and a timer parameter.
  • the sending module 1902 is further configured to send a flow switching indication message to the AN node, where the flow switching indication message includes an ID of the source user plane path, and the flow switching indication message is used to indicate that the AN node determines that the AN node is in the source user plane when receiving the end tag. Whether the downlink data packet received on the path has been successfully sent to the UE.
  • the sending module 1902 is further configured to send a first flow switching indication message to the AN node, where the first flow switching indication message includes an ID of the source user plane path, where the first flow switching indication message is used to indicate that the AN node sends the AN node to the UP GW.
  • the sending module 1902 is further configured to send a second flow switching indication message to the UP GW, where the second flow switching indication message includes an ID of the source user plane path and a second service flow template, where the second flow switching indication message is used to indicate that the UP GW is configured according to the The ID of the second service flow template and the source user plane path identifies the data packet sent by the local network from the downlink data packet received by the UP GW on the source user plane path, and sends the identified data packet to the edge gateway, and the edge The gateway is on the target user plane path.
  • the sending module 1902 is further configured to send a flow switching indication message to the AN node, where the flow switching indication message includes an ID of the second service flow template and the source user plane path, where the flow switching indication message is used to indicate that the AN node is configured according to the second service flow and
  • the ID of the source user plane path identifies the data packet sent by the local network from the downlink data packet received by the AN node on the source user plane path, and sends the identified data packet to the UE through the target DRB, and the target DRB is the target user.
  • FIG. 20 it is a schematic diagram of an embodiment of a user plane gateway UP GW in the embodiment of the present application, including:
  • the receiving module 2001 is configured to receive the trigger information sent by the control plane CP node, the identifier ID of the source user plane path of the user equipment UE, and the UP GW is located on the source user plane path;
  • the sending module 2002 is configured to send an end tag to the access network AN node on the source user plane path according to the trigger information and the ID of the source user plane path.
  • the UP GW shown in FIG. 20 can be used to perform the method as shown in any of the above-described FIGS. 11-18, and the same or corresponding technical features can be cited in the present embodiment.
  • the trigger information includes at least one of a first service flow template and a timer parameter.
  • the trigger information includes a first service flow template
  • the sending module 2002 is specifically configured to: when the IP quintuple information of the downlink data packet of the UE received by the UP GW is the same as any one of the IP quintuple information in the first service flow template, the sending module is configured according to the ID of the source user plane path. Send an end tag to the AN node on the source user plane path.
  • the trigger information includes a timer parameter
  • the sending module 2002 is configured to: set a timer according to the timer parameter; start a timer; when the timer expires, the sending module sends an end tag to the AN node on the source user plane path according to the ID of the source user plane path.
  • the trigger information includes a first service flow template and a timer parameter
  • the sending module 2002 is configured to: when the IP quintuple information of the downlink data packet of the UE received by the UP GW is the same as any one of the IP quintuple information in the first service flow template, the sending module starts a timer, and the timer is Set according to the timer parameters;
  • the sending module restarts the timer, and the IP quintuple information of the ending packet is the same as any IP quintuple information in the first service flow template.
  • the sending module sends an end tag to the AN node according to the ID of the source user plane path.
  • FIG. 21 it is a schematic diagram of another embodiment of the UP GW in the embodiment of the present application.
  • the UP GW also includes:
  • the receiving module 2001 is further configured to receive a flow switching indication message sent by the CP node, where the flow switching indication message includes an ID of the source user plane path and a second service flow template.
  • the identification module 2003 is further configured to: identify, according to the ID of the second service flow template and the source user plane path, the data packet sent by the local network from the downlink data packet sent by the receiving node on the source user plane path;
  • the sending module 2002 is further configured to send the identified data packet to the edge gateway, where the edge gateway is located on the target user plane path of the UE.
  • FIG. 22 it is a schematic diagram of an embodiment of an access gateway Access GW in the embodiment of the present application, including:
  • the receiving module 2201 is configured to receive a path switch notification, where the path switch notification includes a service flow template.
  • the sending module 2202 is configured to send an end data packet to the UP GW according to the service flow template.
  • the access gateway shown in FIG. 22 can be used to perform the method as shown in any of the above-described FIGS. 11-18, and the same or corresponding technical features can be cited in the present embodiment.
  • the receiving module 2201 is specifically configured to receive a path switch notification sent by the edge gateway or the local management unit.
  • FIG. 23 it is a schematic diagram of an embodiment of an access network AN node in the embodiment of the present application, including:
  • the receiving module 2301 is configured to receive a flow switching indication message sent by the control plane CP node, where the flow switching indication message includes an identifier ID of the source user plane path of the user equipment UE, where the flow switching indication message is used to indicate that the AN node is on the source user plane path. After receiving the end tag, determining whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE;
  • the determining module 2302 is configured to: when the AN node receives the end tag on the source user plane path, the determining module determines whether the downlink data packet received by the AN node on the source user plane path has been successfully sent to the UE;
  • the sending module 2303 is configured to: if the downlink data packet of the UE that is received by the AN node on the source user plane path has been successfully sent to the UE, the sending module receives the downlink data that is received by the AN node on the target user plane path of the UE according to the end tag.
  • the package is sorted.
  • the AN node shown in FIG. 23 can be used to perform the method as shown in any of the above-described FIGS. 11-18, and the same or corresponding technical features can be cited in the present embodiment.
  • the sending module 2203 is further configured to: if the AT node does not successfully send the at least one data packet to the UE in the downlink data packet received by the source node, the sending module sends the at least one data packet to the UE.
  • FIG. 24 it is a schematic diagram of another embodiment of an access network AN node in the embodiment of the present application, including:
  • the receiving module 2401 is configured to receive, by the control plane CP node, a flow switching indication message, where the flow switching indication message includes an identifier ID of a source user plane path of the user equipment UE;
  • the sending module 2402 is configured to send, according to the flow switching indication message, a downlink data packet received by the AN node on the source user plane path, where the source user plane path includes the user plane gateway UP GW.
  • the AN node shown in FIG. 24 can be used to perform the method as shown in any of the above-described FIGS. 11-18, and the same or corresponding technical features can be cited in the present embodiment.
  • the flow switching message information is used to indicate that the AN node sends, to the UP GW, a downlink data packet that is received by the AN node on the source user plane path;
  • the sending module 2402 is specifically configured to send, according to the flow switching indication message, the downlink data packet received by the AN node on the source user plane path to the UP GW.
  • the flow switching indication message further includes a service flow template, where the flow switching indication message is used to instruct the AN node to use the ID node according to the ID of the service flow template and the source user plane path to the AN user.
  • the data packet sent by the local network received on the path is sent to the UE by the target DRB, and the target DRB is the transmission path between the UE and the AN node on the target user plane path of the UE;
  • the sending module 2402 is configured to: identify, according to the service flow template, the data packet sent by the local network, and send the identified data packet to the UE by using the target DRB according to the flow switching indication message and the ID of the source user plane path.
  • FIG. 25 is a schematic diagram of another embodiment of a control plane CP node in the embodiment of the present application.
  • the CP node may vary considerably depending on configuration or performance, and may include one or more central processing units (CPU) 2522 (eg, one or more processors) and memory 2532, one or one
  • CPU central processing units
  • the storage medium 2530 of the application 2542 or the data 2544 is stored above (for example, one or one storage device in Shanghai).
  • the memory 2532 and the storage medium 2530 may be short-term storage or persistent storage.
  • the program stored on the storage medium 2530 may include one or more modules (not shown), each of which may include a series of instruction operations in the CP node.
  • central processor 2522 can be configured to communicate with storage medium 2530 to perform a series of instruction operations in storage medium 2530 on the CP node.
  • the CP node may also include one or more power supplies 2526, one or more wired or wireless network interfaces 2550, one or more input and output interfaces 2558, and/or one or more operating systems 2541, such as Windows ServerTM, Mac OS. XTM, UnixTM, LinuxTM, FreeBSDTM and more.
  • operating systems 2541 such as Windows ServerTM, Mac OS. XTM, UnixTM, LinuxTM, FreeBSDTM and more.
  • the steps performed by the CP node in the above embodiment may be based on the CP node structure shown in FIG.
  • FIG. 26 is a schematic diagram of another embodiment of a user plane gateway UP GW in the embodiment of the present application.
  • the UP GW may vary considerably depending on configuration or performance, and may include one or more central processing units (CPUs) 2622 (eg, one or more processors) and memory 2632, one or one
  • the above storage medium 2642 or storage medium 2630 of data 2644 eg, one or one storage device in Shanghai.
  • the memory 2632 and the storage medium 2630 may be short-term storage or persistent storage.
  • the program stored on storage medium 2630 can include one or more modules (not shown), each of which can include a series of instruction operations in the UP GW.
  • central processor 2622 can be configured to communicate with storage medium 2630 to perform a series of instruction operations in storage medium 2630 on the UP GW.
  • the UP GW may also include one or more power supplies 2626, one or more wired or wireless network interfaces 2650, one or more input and output interfaces 2658, and/or one or more operating systems 2641, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM and more.
  • operating systems 2641 such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM and more.
  • the steps performed by the UP GW in the above embodiment may be based on the UP GW structure shown in FIG.
  • FIG. 27 is a schematic diagram of another embodiment of an access gateway Access GW in the embodiment of the present application.
  • the Access GW may vary greatly depending on configuration or performance, and may include one or more central processing units (CPUs) 2722 (eg, one or more processors) and memory 2732, one or one
  • the storage medium 2730 (for example, one or one storage device in Shanghai) that stores the application 2742 or the data 2744 above.
  • the memory 2732 and the storage medium 2730 may be short-term storage or persistent storage.
  • Save The program stored on storage medium 2730 may include one or more modules (not shown), each of which may include a series of instruction operations in the Access GW.
  • the central processor 2722 can be configured to communicate with the storage medium 2730 to perform a series of instruction operations in the storage medium 2730 on the Access GW.
  • the Access GW may also include one or more power supplies 2727, one or more wired or wireless network interfaces 2750, one or more input and output interfaces 2758, and/or one or more operating systems 2741, such as Windows ServerTM, Mac OS. XTM, UnixTM, LinuxTM, FreeBSDTM and more.
  • operating systems 2741 such as Windows ServerTM, Mac OS. XTM, UnixTM, LinuxTM, FreeBSDTM and more.
  • the steps performed by the Access GW in the above embodiment may be based on the Access GW structure shown in FIG.
  • FIG. 28 is a schematic diagram of another embodiment of an access network AN node in an embodiment of the present application.
  • the AN node may vary considerably depending on configuration or performance, and may include one or more central processing units (CPU) 2822 (eg, one or more processors) and memory 2832, one or one The above storage medium 2842 or storage medium 2830 of data 2844 (for example, one or one storage device in Shanghai).
  • the memory 2832 and the storage medium 2830 may be short-term storage or persistent storage.
  • Programs stored on storage medium 2830 may include one or more modules (not shown), each of which may include a series of instruction operations in an AN node.
  • central processor 2822 can be configured to communicate with storage medium 2830 to perform a series of instruction operations in storage medium 2830 on the AN node.
  • the AN node may also include one or more power supplies 2828, one or more wired or wireless network interfaces 2850, one or more input and output interfaces 2858, and/or one or more operating systems 2841, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM and more.
  • operating systems 2841 such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM and more.
  • the steps performed by the AN node in the above embodiment may be based on the AN node structure shown in FIG.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform a method as shown in any of the above-described FIGS. 11-18, such as a CP node,
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform a method as shown in any of the above-described FIGS. 11-18, such as a CP node.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform a method as shown in any of the above Figures 11-18, such as UP GW,
  • UP GW UP GW
  • a computer program product comprising instructions for causing a computer to perform a method as shown in any of the above-described FIGS. 11-18, such as an access gateway, when operating on a computer
  • FIGS. 11-18 such as an access gateway
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform a method as shown in any of the above-described FIGS. 11-18, such as an AN node,
  • FIGS. 11-18 such as an AN node
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform a method as shown in any of the above-described FIGS. 11-18, such as an AN node,
  • FIGS. 11-18 such as an AN node
  • a computer program product includes one or more computer instructions. Full or partial generation when loading and executing computer program instructions on a computer A process or function in accordance with an embodiment of the present invention.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, computer instructions can be wired from a website site, computer, server or data center (eg Coax, fiber, digital subscriber line (DSL) or wireless (eg, infrared, wireless, microwave, etc.) is transmitted to another website, computer, server, or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • Useful media can be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)).

Landscapes

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

Abstract

本申请实施例中提出了一种发送结束标记的方法，用于用户面网关根据触发信息，确定何时发送结束标记，再根据结束标记对目标用户面路径上接收的下行数据包进行排序处理。所述方法包括：用户面网关UP GW接收控制面CP节点发送的触发信息和用户设备UE的源用户面路径的标识ID，所述UP GW位于所述源用户面路径上；所述UP GW根据所述触发信息和所述源用户面路径的ID，在所述源用户面路径上向接入网AN节点发送结束标记。本申请实施例还提供了一种控制面CP节点、用户面网关UP GW、接入网关和接入网AN节点。

Description

一种发送结束标记的方法 技术领域
本申请涉及通信领域，尤其涉及一种发送结束标记的方法、控制面节点、用户面网关、接入网关以及接入网节点。
背景技术
在传统的演进分组系统(Evolved Packet System，EPS)，用户设备(User Equipment，UE)的用户面路径重选发生在切换过程中，例如，UE从源基站切换到目标基站，此时，UE的用户面网关(服务网关/分组数据网络网关)并不发生变化，即源用户面路径上的用户面网关与目标用户面路径上的用户面网关相同。为了辅助UE的目标基站对下行数据的排序，在切换完成后，该用户面网关会立刻在源用户面路径上发送一个结束标记(end marker)，以表示下行数据在源用户面路径上发送结束，然后将数据网络发送的下行数据通过目标用户面路径传输给UE。
在5G移动网络中，为了获取低时延、高带宽的用户面路径(数据路径)，核心网控制面可以通过路径重选，为UE的本地数据流选择一个边缘网关，使本地数据流路由到UE，即用户面网关发生了变化。例如，在路径重选之前，本地数据流通过互联网才能够到达UE；路径重选之后，本地数据流可以直接通过边缘网关到达UE，从而避免了互联网时延，降低了本地数据流的传输时延。其中，本地数据流是由本地网络发送的数据包。具体地，UE的路径重选过程可以包括图1和图2所示的两种场景。如图1所示，UE从源接入网(Access Network，AN)节点切换到目标AN节点，并且将UE从用户面网关(User Plane Gateway，UP GW)切换为边缘网关。如图2所示，控制面节点为UE的本地数据流选择一个更有效的数据路径，不改变UE的AN节点，只改变核心网中的用户面网关，使其更靠近本地网络。
但是，在图1和图2所示的场景中，仍然存在下行数据的排序问题，粗略估计在图1场景下互联网中有50Mb的残留数据，在图2场景下互联网中会有15Mb的残留数据(EPS系统是5Mb)，这对会话和业务连续性的移动边缘计算(Mobile Edge Computing，MEC)业务，如车辆网，增强现实技术(Augmented Reality，AR)，移动游戏，产生很大的影响。但是因为UE的网关发生了改变，源用户面网关不知道在互联网中的残留数据何时发送结束，因此无法确定何时发送结束标记，以表示(包括互联网)本地数据流在源用户面路径上发送结束。例如，若在互联网中的残留数据还没发送完毕时发送结束标记，那么就会丢失这部分残留数据，进而对UE在目标用户面路径上下行数据的排序造成了一定困难。
发明内容
本申请实施例提供了一种发送结束标记的方法，用于用户面网关根据触发信息，确定何时发送结束标记，从而根据结束标记对目标用户面路径上接收的下行数据包进行排序处理。
本申请实施例的第一方面提供一种发送结束标记的方法，可以包括：该方法可以应用在UE的用户面路径切换的过程中，控制面CP节点根据路径切换请求或切换通知等选择边缘网关，控制面CP节点向边网关发送会话更新请求；控制面CP节点接收边缘网关反馈的会话更新响应，该会话更新响应包括用户设备UE的源用户面路径的标识ID或该UE的目标用户面路径的ID，该源用户面路径包含用户面网关UP GW，该目标用户面路径包括边缘网关；该CP节点根据该会话更新响应，向该UP GW发送触发信息和该源用户面路径的ID，该触发信息和该源用户面路径的ID用于该UP GW在该源用户面路径上向接入网AN节点发送结束标记。当源用户面路径和目标用户面路径的AN节点相同时，源用户面路径为包含UE，AN，UP GW，接入网关Access GW的路径，目标用户面路径为包含UE，AN，边缘网关Edge GW，Access GW的路径；当源用户面路径和目标用户面路径的AN节点不相同时，源用户面路径为包含UE，AN1，UP GW，Access GW的路径，目标用户面路径为包含UE，AN2，Edge GW，Access GW的路径。
在本申请实施例中，CP节点可以根据会话更新响应，向UP GW发送触发信息和源用户面路径的ID，那么，UP GW就可以根据触发信息和源用户面路径的ID确定何时发送结束标记了，从而，降低了因为UE的用户面路径切换造成的在源用户面路径上的下行数据包的丢失概率，有效的辅助AN或目标AN对在目标用户面路径上接收的下行数据包进行排序处理。
可选的，在本申请的一些实施例中，该触发信息可以包括第一业务流样板和定时器参数中的至少一种。
在本申请实施例中，对触发信息做了进一步的说明，提供可几种可选的实现方式，触发信息可以包括第一业务流样板，或者，第一业务流样板和定时器参数，或者，定时器参数，或者，其他的指示标识等，第一业务流样板是用来识别结束数据包的。
可选的，在本申请的一些实施例中，该方法还可以包括：CP节点可以根据路径切换请求、应用请求或者用户面报告选择边缘网关，该CP节点还需要向该AN节点发送流切换指示消息，该流切换指示消息包含该源用户面路径的ID，该流切换指示消息用于指示该AN节点在接收到该结束标记时确定该AN节点在该源用户面路径上接收到的下行数据包是否已成功发送给该UE。本申请实施例可以应用的是源用户面路径和目标用户面路径的AN节点相同的情况下，在源用户面路径中AN节点和UE之间为第一承载，在目标用户面路径中AN节点和UE之间为第二承载。
应理解，在AN节点收到的下行数据包中可以包括本地数据流或者互联网数据流，本地数据流是由本地网络通过互联网发送的数据包，互联网数据流是互联网发送的数据包，因为本申请实施例针对的是本地数据流的路径切换，但是，AN节点无法识别出本地数据流，如果在源用户面路径上的本地数据流没有成功发送给UE的话，AN节点在目标用户面路径上根据结束标记对收到的下行数据包进行排序的时候，就会丢失在源用户面路径上的本地数据流，所以，当AN节点收到流切换指示消息的时候，可以在AN节点和UE之间的第一承载上发送AN节点在源用户面路径上接收的下行数据包(本地数据流和/互联网数据流)，如果都成功发送给UE，那么，保证了AN节点在源用户面路径上的本地数据流没有 丢失，再根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理。
可选的，在本申请的一些实施例中，因为AN节点无法识别本地数据流，所以，在准备路径切换资源的时候可以在核心网选择一个分流节点，由分流节点来识别本地数据流，这里分流节点以UP GW来进行说明。该方法还可以包括：该CP节点向该AN节点发送第一流切换指示消息，该第一流切换指示消息包含该源用户面路径的ID，该第一流切换指示消息用于指示该AN节点向该UP GW发送该AN节点在该源用户面路径上接收到的下行数据包；因为AN节点无法识别本地数据流，所以，CP节点向AN节点发送第一流切换指示消息是用于AN节点可以将在源用户面路径上接收的下行数据包转发给UP GW去识别；该CP节点还会向该UP GW发送第二流切换指示消息，该第二流切换指示消息包含该源用户面路径的ID和第二业务流样板，该第二流切换指示消息用于指示该UP GW根据该第二业务流样板和该源用户面路径的ID，从该UP GW在该源用户面路径上接收的下行数据包中识别出本地网络发送的数据包，并将该识别出的数据包发送给边缘网关，该边缘网关位于该目标用户面路径上。本申请实施例可以应用的是源用户面路径和目标用户面路径的AN节点相同的情况下，在源用户面路径中AN节点和UE之间为第一承载，在目标用户面路径中AN节点和UE之间为第二承载。
在本申请实施例中，因为AN节点无法从源用户面路径接收的下行数据包中识别出本地数据流，所以，选择一个分流节点UP GW来进行识别，CP节点向AN节点发送第一流切换指示消息，是为了让AN节点将在源用户面路径上接收的下行数据包转发给UP GW进行识别，但是，UP GW上没有识别本地数据流的业务流样板，所以，CP节点会向UP GW发送第二流切换指示消息，第二流切换指示消息包括第二业务流样板和源用户面路径的ID，AN节点识别出本地数据流后，再将本地数据流转发给边缘网关，由边缘网关转发回AN节点，这下，AN节点可以在第二承载上向UE发送本地数据流了。需要说明的是，AN节点在源用户面路径上还会收到结束标记，当收到结束标记时，AN节点停止向UP GW转发在源用户面路径上接收的下行数据包，再将结束标记转发给UP GW，UP GW将结束标记转发给边缘网关，边缘网关转发回AN节点，那么，AN节点就可以根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理了。
可选的，在本申请的一些实施例中，因为AN节点无法识别本地数据流，所以，这里所提供的方案就是AN可以识别本地数据流，该方法还可以包括：该CP节点向该AN节点发送流切换指示消息，该流切换指示消息包含第二业务流样板和该源用户面路径的ID，该流切换指示消息用于指示该AN节点根据该第二业务流样板和该源用户面路径的ID从该AN节点在该源用户面路径上接收的下行数据包中识别出本地网络发送的数据包，并将该识别出的数据包通过目标DRB发送给该UE，该目标DRB为在该目标用户面路径上该UE与该AN节点之间的传输路径。本申请实施例可以应用的是源用户面路径和目标用户面路径的AN节点相同的情况下，在源用户面路径中AN节点和UE之间为第一承载，在目标用户面路径中AN节点和UE之间为第二承载。那么，目标DRB就是这里的第二承载。
在本申请实施例中，CP节点可以向AN节点发送流切换指示消息，该流切换指示消息包含第二业务流样板和该源用户面路径的ID，那么，AN节点就可以根据第二业务流样板 和源用户面路径的ID从在源用户面路径上接收的下行数据包中识别出本地数据流了，再将识别出的本地数据流通过UE和AN之间的第二承载向UE发送，本申请实施例简单便捷，容易实现，降低了将源用户面路径转发给分流节点进行识别的时延，由AN节点直接进行识别并发送给UE，AN节点可以有效的根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理了。
本申请实施例第二方面提供了一种发送结束标记的方法，可以包括：用户面网关UP GW接收控制面CP节点发送的触发信息和用户设备UE的源用户面路径的标识ID，该UP GW位于该源用户面路径上；该UP GW根据该触发信息和该源用户面路径的ID，在该源用户面路径上向接入网AN节点发送结束标记。当源用户面路径和目标用户面路径的AN节点相同时，源用户面路径为包含UE，AN，UP GW，接入网关Access GW的路径，目标用户面路径为包含UE，AN，边缘网关Edge GW，Access GW的路径；当源用户面路径和目标用户面路径的AN节点不相同时，源用户面路径为包含UE，AN1，UP GW，Access GW的路径，目标用户面路径为包含UE，AN2，Edge GW，Access GW的路径。
在本申请实施例中，UP GW接收CP节点发送的触发信息和源用户面路径的ID，当UP GW处的一些条件达到触发信息的要求时，那么，UP GW就可以向AN节点发送结束标记了。UP GW可以根据触发信息和源用户面路径的ID，确定了何时向AN节点发送结束标记，而结束标记可以说明在源用户面路径上传输的本地数据流已经传输完毕，所以，降低了UE的用户面路劲切换后，在源用户面路径上的下行数据包的丢失概率。
可选的，在本申请的一些实施例中，该触发信息包括第一业务流样板和定时器参数中的至少一种。
在本申请实施例中，对触发信息做了进一步的说明，提供可几种可选的实现方式，触发信息可以包括第一业务流样板，或者，第一业务流样板和定时器参数，或者，定时器参数，或者，其他的指示标识等，第一业务流样板是用来识别结束数据包的。
可选的，在本申请的一些实施例中，该触发信息包括该第一业务流样板；该UP GW根据该触发信息和该源用户面路径的ID，在该源用户面路径上向AN节点发送结束标记，可以包括：当该UP GW接收的该UE的下行数据包的IP五元组信息与该第一业务流样板中的任一IP五元组信息相同时，该UP GW根据该源用户面路径的ID，在该源用户面路径上向该AN节点发送该结束标记。第一业务流样板包括至少一个IP五元组信息，是用来过滤结束数据包的。
在本申请实施例中，提供了UP GW发送结束标记的一个实现方案，UP GW会在源用户面路径上接收传输给UE的下行数据包，当触发信息为第一业务流样板时，UP GW可以判断接收的下行数据包的IP五元组信息，当接收的下行数据包的IP五元组信息与第一业务流样板中的任一IP五元组信息相同时，说明接收的是结束数据包，那么，UP GW就可以向AN节点发送结束标记了，用于表示在源用户面路径上本地数据流传输完毕。
可选的，在本申请的一些实施例中，该触发信息包括该定时器参数，该UP GW根据该触发信息和该源用户面路径的ID，在该源用户面路径上向AN节点发送结束标记，可以包括：该UP GW根据该定时器参数设置定时器；UP GW接收到定时器参数时，该UP GW 就可以启动该定时器；当该定时器超时时，该UP GW根据该源用户面路径的ID，在该源用户面路径上向该AN节点发送该结束标记。应理解，定时器的参数通常是一个经验值。
在本申请实施例中，提供了UP GW发送结束标记的另一个实现方案，UP GW收到定时器参数后，可以根据定时器参数设置定时器，当在定时器设置的时间内，定时器收到下行数据包后，重设定时器，说明在源用户面路径上还有数据在传输，直到没有收到下行数据包，导致定时器超时，那么，UP GW就可以向AN节点发送结束标记了，说明在源用户面路径上传输的数据包已传输完毕。
可选的，在本申请的一些实施例中，该触发信息包括该第一业务流样板和该定时器参数；该UP GW根据该触发信息和该源用户面路径的ID，在该源用户面路径上向AN节点发送结束标记，可以包括：当该UP GW接收的该UE的下行数据包的IP五元组信息与该第一业务流样板中的任一IP五元组信息相同时，该UP GW启动定时器，该定时器是根据该定时器参数设置的；若该UP GW接收到结束数据包，且该定时器未超时，则该UP GW重启该定时器，该结束数据包的IP五元组信息与该第一业务流样板中的任一IP五元组信息相同，或者，若UP GW收到其他的下行数据包，则该UP GW重启该定时器；当该定时器超时时，该UP GW根据该源用户面路径的ID，向该AN节点发送该结束标记。第一业务流样板包括至少一个IP五元组信息，是用来过滤结束数据包的。
在本申请实施例中，提供了UP GW发送结束标记的另一个实现方案，这里UP GW发送结束标记的确定条件有第一业务流样板和定时器参数，可以根据定时器参数设置定时器，接入网关在这个实施例中发送的结束数据包有多个，为了确保传输数据的可靠性。当UP GW接收第一个结束数据包时，UP GW需要启动定时器，然后，在定时器未超时的时间内，若收到其他的技术数据包或者下行数据包时，需要重启定时器，说明在源用户面路径上还有下行数据包在传输；当定时器超时时，说明在源用户面上的下行数据包传输完毕，可以根据源用户面路径的ID向AN节点发送结束标记了。
可选的，在本申请的一些实施例中，因为AN节点无法识别本地数据流，所以，在准备路径切换资源的时候可以在核心网选择一个分流节点，由分流节点来识别本地数据流，这里分流节点以UP GW来进行说明，该方法还可以包括：该UP GW接收该CP节点发送的流切换指示消息，该流切换指示消息包括该源用户面路径的ID和第二业务流样板；该UP GW根据该第二业务流样板和该源用户面路径的ID，从在该源用户面路径上接收该AN节点发送的下行数据包中识别出本地网络发送的数据包；该UP GW向边缘网关发送该识别出的数据包，该边缘网关位于该UE的目标用户面路径上。本申请实施例可以应用的是源用户面路径和目标用户面路径的AN节点相同的情况下，在源用户面路径中AN节点和UE之间为第一承载，在目标用户面路径中AN节点和UE之间为第二承载。
在本申请实施例中，因为AN节点无法从源用户面路径接收的下行数据包中识别出本地数据流，所以，选择一个分流节点UP GW来进行识别，CP节点会向UP GW发送第二流切换指示消息，第二流切换指示消息包括第二业务流样板和源用户面路径的ID，AN节点识别出本地数据流后，再将本地数据流转发给边缘网关，由边缘网关转发回AN节点，这下，AN节点可以在第二承载上向UE发送本地数据流了。需要说明的是，AN节点在源 用户面路径上还会收到结束标记，当收到结束标记时，AN节点停止向UP GW转发在源用户面路径上接收的下行数据包，再将结束标记转发给UP GW，UP GW将结束标记转发给边缘网关，边缘网关转发回AN节点，那么，AN节点就可以根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理了。
本申请实施例第三方面提供了一种发送结束标记的方法，可以包括：该方法可以应用在UE的用户面路径切换的过程中，接入网关Access GW接收路径切换通知，该路径切换通知包括业务流样板，这里的路径切换通知还可以指示Access GW接下来需要向边缘网关发送下行数据包了；该Access GW根据该业务流样板，向UP GW发送结束数据包。第一业务流样板包括至少一个IP五元组信息。当源用户面路径和目标用户面路径的AN节点相同时，源用户面路径为包含UE，AN，UP GW，接入网关Access GW的路径，目标用户面路径为包含UE，AN，边缘网关Edge GW，Access GW的路径；当源用户面路径和目标用户面路径的AN节点不相同时，源用户面路径为包含UE，AN1，UP GW，Access GW的路径，目标用户面路径为包含UE，AN2，Edge GW，Access GW的路径。
在本申请实施例中，接入网关接收的路径切换通知中包括业务流样板，而业务流样板包括至少一个IP五元组信息，那么，Access GW就可以根据业务流样板来确定需要发送的结束数据包的IP五元组信息了，用于表示UE的用户面路径切换后，在源用户面路径上最后发送的数据包，UP GW就可以根据结束数据包发送结束标记了。
可选的，在本申请的一些实施例中，该Access GW接收路径切换通知，可以包括：该Access GW接收从边缘网关或本地管理单元发送的该路径切换通知。在本申请实施例中，路径切换通知可以是边缘网关发送的，也可以是本地管理单元发送的，提供了几种可选的实现方式，增加了方案的可行性。
本申请实施例第四方面提供了一种发送结束标记的方法，可以包括：本申请实施例可以应用的是源用户面路径和目标用户面路径的AN节点相同的情况下，在源用户面路径中AN节点和UE之间为第一承载，在目标用户面路径中AN节点和UE之间为第二承载。接入网AN节点接收控制面CP节点发送的流切换指示消息，该流切换指示消息包含用户设备UE的源用户面路径的标识ID，该流切换指示消息用于指示该AN节点在该源用户面路径上接收到结束标记时确定该AN节点在该源用户面路径上接收到的下行数据包是否已成功发送给该UE；需要说明的是，AN节点在该源用户面路径上接收到的下行数据包包括互联网发送的数据包和本地网络发送的数据包；当该AN节点在该源用户面路径上接收到该结束标记时，该AN节点确定该AN节点在该源用户面路径上接收的下行数据包是否已成功发送给该UE；若该AN节点在该源用户面路径上接收到的该UE的下行数据包已成功发送给该UE，则该AN节点根据该结束标记对该AN节点在该UE的目标用户面路径上接收的下行数据包进行排序。
在本申请实施例中，因为本申请实施例针对的是本地数据流的路径切换，但是，AN节点无法识别出本地数据流，如果在源用户面路径上的本地数据流没有成功发送给UE的话，AN节点在目标用户面路径上根据结束标记对收到的下行数据包进行排序的时候，就会丢失在源用户面路径上的本地数据流，所以，当AN节点收到流切换指示消息的时候，可以在 AN节点和UE之间的第一承载上发送AN节点在源用户面路径上接收的下行数据包(本地数据流和/互联网数据流)，如果都成功发送给UE，那么，保证了AN节点在源用户面路径上的本地数据流没有丢失，再根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理。
可选的，在本申请的一些实施例中，该方法还可以包括：若该AN节点在该源用户面路径上接收到的下行数据包中存在至少一个数据包未成功发送给该UE，则该AN节点向该UE发送该至少一个数据包。
在本申请实施例中，当AN节点收到结束标记的时候，若在源用户面路径上接收到的下行数据包中存在至少一个数据包未成功发送给该UE，那么，AN节点需要将未成功发送给UE的数据包向UE成功发送，有效保障了因用户面路径切换造成的在源用户面路径上发送给UE的下行数据包的丢失。
本申请实施例第五方面提供了一种发送结束标记的方法，可以包括：接入网AN节点从控制面CP节点接收流切换指示消息，该流切换指示消息包含用户设备UE的源用户面路径的标识ID；该AN节点根据该流切换指示消息，发送该AN节点在该源用户面路径上接收的下行数据包，该源用户面路径包括用户面网关UP GW。本申请实施例可以应用的是源用户面路径和目标用户面路径的AN节点相同的情况下，在源用户面路径中AN节点和UE之间为第一承载，在目标用户面路径中AN节点和UE之间为第二承载。
在本申请实施例中，AN节点接收CP节点发送的流切换指示消息，该AN节点可以根据该流切换指示消息，发送该AN节点在该源用户面路径上接收的下行数据包，示例性的，可以是AN节点向UE发送在源用户面路径上接收的下行数据包，还可以是AN节点向UP GW发送在源用户面路径上接收的下行数据包，AN节点可以根据流切换指示消息对在源用户面路径上接收的下行数据包进行处理。
可选的，在本申请的一些实施例中，因为AN节点无法识别本地数据流，所以，在准备路径切换资源的时候可以在核心网选择一个分流节点，由分流节点来识别本地数据流，这里分流节点以UP GW来进行说明。该流切换消息信息用于指示该AN节点向该UP GW发送该AN节点在该源用户面路径上接收到的下行数据包；该AN节点根据该流切换指示消息，发送该AN节点在该源用户面路径上接收的下行数据包，可以包括：该AN节点根据该流切换指示消息，将该AN节点在该源用户面路径上接收到的下行数据包发送给该UP GW。
在本申请实施例中，因为AN节点无法从源用户面路径接收的下行数据包中识别出本地数据流，所以，选择一个分流节点UP GW来进行识别，CP节点向AN节点发送流切换指示消息，是为了让AN节点将在源用户面路径上接收的下行数据包转发给UP GW进行识别，UP GW可以将识别出来的本地数据流转发送给边缘网关，边缘网关再将其转发回AN节点，AN节点可以在第二承载上向UE发送本地数据流。需要说明的是，AN节点在源用户面路径上还会收到结束标记，当收到结束标记时，AN节点停止向UP GW转发在源用户面路径上接收的下行数据包，再将结束标记转发给UP GW，UP GW将结束标记转发给边缘网关，边缘网关转发回AN节点，那么，AN节点就可以根据结束标记对在目标用户面路 径上接收的下行数据包进行排序处理了。
可选的，在本申请的一些实施例中，因为AN节点无法识别本地数据流，所以，这里所提供的方案就是AN可以识别本地数据流。该流切换指示消息还包含业务流样板，该流切换指示消息用于指示该AN节点根据该业务流样板和该源用户面路径的ID将该AN节点在该源用户面路径上接收的本地网络发送的数据包通过目标DRB发送给该UE，该目标DRB为在该UE的目标用户面路径上该UE与该AN节点之间的传输路径；该AN节点根据该流切换指示消息，发送该AN节点在UE的源用户面路径上接收的下行数据包，可以包括：该AN节点根据该业务流样板，识别出本地网络发送的数据包；该AN节点根据该流切换指示消息和该源用户面路径的ID，将该识别出的数据包通过该目标DRB发送给该UE。
在本申请实施例中，AN节点接收CP节点发送的流切换指示消息，该流切换指示消息包含业务流样板和该源用户面路径的ID，那么，AN节点就可以根据业务流样板和源用户面路径的ID从在源用户面路径上接收的下行数据包中识别出本地数据流了，再将识别出的本地数据流通过UE和AN之间的第二承载向UE发送，本申请实施例简单便捷，容易实现，降低了将源用户面路径转发给分流节点进行识别的时延，由AN节点直接进行识别并发送给UE，AN节点可以有效的根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理了。
本申请实施例第六方面提供一种控制面CP节点，具有实现对应于上述第一方面提供的根据触发信息和源用户面路径确定发送结束标记的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
本申请实施例第七方面提供一种用户面网关UP GW，具有实现对应于上述第二方面提供的根据触发信息和源用户面路径确定发送结束标记的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
本申请实施例第八方面提供一种接入网关Access GW，具有实现对应于上述第三方面提供的根据触发信息和源用户面路径确定发送结束标记的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
本申请实施例第九方面提供一种接入网AN节点，具有实现对应于上述第四方面提供的根据触发信息和源用户面路径确定发送结束标记的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
本申请实施例第十方面提供一种接入网AN节点，具有实现对应于上述第五方面提供的根据触发信息和源用户面路径确定发送结束标记的功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
本申请实施例第十一方面提供一种控制面节点，可以包括：
收发器，存储器和总线，该收发器和该存储器通过该总线连接；
该存储器，用于存储操作指令；
该收发器，用于接收会话更新响应，所述会话更新响应包括用户设备UE的源用户面路径的标识ID或所述UE的目标用户面路径的ID，所述源用户面路径包含用户面网关UP GW；根据所述会话更新响应，向所述UP GW发送触发信息和所述源用户面路径的ID，所述触发信息用于所述UP GW在所述源用户面路径上向接入网AN节点发送结束标记。
本申请实施例第十二方面提供一种用户面网关，可以包括：
收发器，存储器和总线，该收发器和该存储器通过该总线连接；
该存储器，用于存储操作指令；
该收发器，用于接收控制面CP节点发送的触发信息和用户设备UE的源用户面路径的标识ID，所述UP GW位于所述源用户面路径上；根据所述触发信息和所述源用户面路径的ID，在所述源用户面路径上向接入网AN节点发送结束标记。
本申请实施例第十三方面提供一种接入网关，可以包括：
收发器，存储器和总线，该收发器和该存储器通过该总线连接；
该存储器，用于存储操作指令；
该收发器，用于接收路径切换通知，所述路径切换通知包括业务流样板；根据所述业务流样板，向UP GW发送结束数据包。
本申请实施例第十四方面提供一种接入网节点，可以包括：
收发器，处理器，存储器和总线，该收发器、该处理器和该存储器通过该总线连接；
该存储器，用于存储操作指令；
该处理器，用于当所述AN节点在所述源用户面路径上接收到所述结束标记时，所述确定模块确定所述AN节点在所述源用户面路径上接收的下行数据包是否已成功发送给所述UE；
该收发器，用于接收控制面CP节点发送的流切换指示消息，所述流切换指示消息包含用户设备UE的源用户面路径的标识ID，所述流切换指示消息用于指示所述AN节点在所述源用户面路径上接收到结束标记时确定所述AN节点在所述源用户面路径上接收到的下行数据包是否已成功发送给所述UE；若所述AN节点在所述源用户面路径上接收到的所述UE的下行数据包已成功发送给所述UE，则所述收发器根据所述结束标记对所述AN节点在所述UE的目标用户面路径上接收的下行数据包进行排序，或者，所述收发器发送所述结束标记。
本申请实施例第十五方面提供一种接入网节点，可以包括：
收发器，存储器和总线，该收发器和该存储器通过该总线连接；
该存储器，用于存储操作指令；
该收发器，用于从控制面CP节点接收流切换指示消息，所述流切换指示消息包含用户设备UE的源用户面路径的标识ID；根据所述流切换指示消息，发送所述AN节点在所述源用户面路径上接收的下行数据包，所述源用户面路径包括用户面网关UP GW。
本申请实施例第十六方面提供一种通信系统，该通信系统包括控制面节点、用户面网关和接入网关，该控制面节点为执行本申请第一方面或第一方面任一可选实现方式中所述的控制面节点；该用户面网关为执行本申请第二方面或第二方面任一可选实现方式中所述的用户面网关；该接入网关为执行本申请第三方面或第三方面任一可选实现方式中所述的接入网关。
本申请实施例第十七方面提供一种通信系统，该通信系统包括控制面节点、用户面网关、接入网关和接入网节点，该控制面节点为执行本申请第一方面或第一方面任一可选实现方式中所述的控制面节点；该用户面网关为执行本申请第二方面或第二方面任一可选实现方式中所述的用户面网关；该接入网关为执行本申请第三方面或第三方面任一可选实现方式中所述的接入网关；该接入网节点为执行本申请第四方面或第四方面任一可选实现方式中所述的接入网节点。
本申请实施例第十八方面提供一种通信系统，该通信系统包括控制面节点、用户面网关、接入网关和接入网节点，该控制面节点为执行本申请第一方面或第一方面任一可选实现方式中所述的控制面节点；该用户面网关为执行本申请第二方面或第二方面任一可选实现方式中所述的用户面网关；该接入网关为执行本申请第三方面或第三方面任一可选实现方式中所述的接入网关；该接入网节点为执行本申请第五方面或第五方面任一可选实现方式中所述的接入网节点。
本发明实施例第十九方面提供一种存储介质，需要说明的是，本发的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产口的形式体现出来，该计算机软件产品存储在一个存储介质中，用于储存为上述设备所用的计算机软件指令，其包含用于执行上述第一方面、第二方面、第三方面或第四方面(第五方面)为控制面节点、用户面网关、接入网关或接入网节点所设计的程序。
该存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本发明实施例第二十方面提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如本申请第一方面或第一方面任一可选实现方式中所述的方法。
本发明实施例第二十一方面提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如本申请第二方面或第二方面任一可选实现方式中所述的方法。
本发明实施例第二十二方面提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如本申请第三方面或第三方面任一可选实现方式中所述的方法。
本发明实施例第二十三方面提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如本申请第四方面或第四方面任一可选实现方式中所述的方法。
本发明实施例第二十四方面提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如本申请第五方面或第五方面任一可选实现方式中所述的方法。
本申请实施例提供的技术方案中，本申请实施例具有以下有益效果：
在本申请实施例中，在UE的用户面路径重选过程中，从源用户面路径切换为目标用 户面路径，源用户面路径包含UP GW，目标用户面路径包含边缘网关。CP节点接收会话更新响应，根据该会话更新响应向UP GW发送触发信息和源用户面路径的标识ID，该触发信息用于所述UP GW在所述源用户面路径上向接入网AN节点发送结束标记，UP GW根据接收的触发信息和源用户面路径的标识ID，来确定UP GW何时向AN节点发送结束标记，进而辅助在目标用户面路径上接收的下行数据包进行排序处理。本申请实施例中可以增强用户面网关的功能，还可以重用传统网元的大部分功能，不需要对现有的切换流程进行大范围修改，简单清晰，容易实施。解决由于互联网的不可靠性，降低了源用户面路径上少量数据的丢失。
进一步的，当UE的用户面路径切换为目标用户面路径，目标用户面路径包括边缘网关时，那么，由本地网络发送的下行数据就可以直接通过边缘网关向UE发送了，不需要通过UP GW向UE发送，从而节省传输时延。但是，在源用户面路径上，AN节点接收的下行数据包中包括互联网发送的数据包和本地网络发送的数据包，那么，用户面路径切换后，需要把在源用户面路径上传输的本地网络发送的数据包转发到目标用户面路径上传输给UE，但是，在现有技术中，AN节点无法识别出本地网络发送的数据包，本申请实施例提出了在AN节点识别出本地网络发送的数据包，或者，在核心网选择的分流节点上识别出本地网络发送的数据包，或者，直接保证在源用户面路径上，AN节点向UE成功发送所有数据包，再根据接收的结束标记对目标用户面路径上接收的下行数据包进行处理，一定程度上减弱了互联网的乱序和拥塞，进而减少了对在目标用户面路径上接收的数据包进行排序带来的影响。
附图说明
图1为本现有技术中UE移动进行路径重选的示意图；
图2为本现有技术中UE收到用户面报告进行路径重选的示意图；
图3为本申请实施例中演进分组系统EPS的一个网络架构示意图；
图4为本申请实施例中演进的通用陆地无线接入网EUTRAN的一个架构示意图；
图5为本申请实施例中下一代NG移动通信系统的一个架构示意图；
图6为本申请实施例中EPS路径实现方式的示意图；
图7为本申请实施例中现有基于X2接口的切换流程示意图；
图8为本申请实施例中现有基于S1接口的切换流程示意图；
图9为本申请实施例中现有转发结束标记end marker的示意图；
图10为本申请实施例中发送结束标记的示意图；
图11为本申请实施例中发送结束标记的方法的一个实施例示意图；
图12为本申请实施例中发送结束标记的方法的另一个实施例示意图；
图13为本申请实施例中发送结束标记的方法的另一个实施例示意图；
图14为本申请实施例中发送结束标记的方法的另一个实施例示意图；
图15为本申请实施例中发送结束标记的方法的另一个实施例示意图；
图16为本申请实施例中发送结束标记的方法的另一个实施例示意图；
图17为本申请实施例中发送结束标记的方法的另一个实施例示意图；
图18为本申请实施例中发送结束标记的方法的另一个实施例示意图；
图19为本申请实施例中控制面CP节点的一个实施例示意图；
图20为本申请实施例中用户面网关UP GW的一个实施例示意图；
图21为本申请实施例中用户面网关UP GW的另一个实施例示意图；
图22为本申请实施例中接入网关Access GW的一个实施例示意图；
图23为本申请实施例中接入网AN节点的一个实施例示意图；
图24为本申请实施例中接入网AN节点的另一个实施例示意图；
图25为本申请实施例中控制面CP节点的另一个实施例示意图；
图26为本申请实施例中用户面网关UP GW的另一个实施例示意图；
图27为本申请实施例中接入网关Access GW的另一个实施例示意图；
图28为本申请实施例中接入网AN节点的另一个实施例示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
首先，对传统通信系统架构和下一代通信系统架构进行简要说明。
用户设备(User Equipment，UE)可接入的移动网络包括2G、3G、4G网络，为UE的通话业务、视频业务、网页业务等提供传输通道。
如图3所示，为演进分组系统(Evolved Packet System，EPS)的网络架构示意图，以4G网络为例简单介绍传统移动网络。其中，EPS主要涉及的网元包括UE、演进的通用陆地无线接入网、移动性管理实体、服务网关、分组数据网络网关、服务通用无线分组系统(General Packet Radio System，GPRS)支持节点、归属用户服务器、策略和计费规则功能。如图4所示，为演进的通用陆地无线接入网(Evolved Universal Terrestrial Radio Access Network，EUTRAN)的架构示意图。
上述图3中所涉及的网络实体的功能做一个简要的说明，如下：
演进的通用陆地无线接入网(Evolved Universal Terrestrial Radio Access Network，EUTRAN)：由多个演进型基站(Evolved NodeB，eNodeB)组成的网络，实现无线物理层功能、资源调度和无线资源管理、无线接入控制以及移动性管理功能。eNodeB之间可以通过X2接口相连，可以基于X2接口来传输数据。eNodeB通过用户面接口S1-U和服务网关(Serving Gateway，SGW)相连，使用GPRS隧道协议用户面(GPRS Tunneling Protocol User Plane，GTP-U)来传送用户面数据；通过控制面接口S1-MME和移动性管理实体(Mobility Management Entity，MME)相连，采用S1接口应用协议(S1-Application Protocol，S1-AP)实现无线接入承载控制等功能，如上述图4所示。
MME：主要负责用户及会话管理的控制平面功能，包括非接入层(Non Access Stratum， NAS)信令及安全，跟踪区列表(Tracking Area List)的管理，以及分组数据网络网关(Packet Date Network Gateway，PDN Gateway，PGW)与SGW的选择等。
SGW：主要负责对UE的数据进行传输、转发以及路由切换等，并作为UE在eNodeB之间切换时的本地移动性锚定点(对于每一个UE，每个时刻仅有一个SGW为之服务)。
分组数据网络网关(Packet Date Network Gateway，PGW)：作为PDN连接的锚定点，负责UE的互联网协议(Internet Protocol，IP)地址分配，UE的数据报文过滤、速率控制、生成计费信息等。
服务通用无线分组业务支持节点(Serving GPRS Supporting Node，SGSN)：为2G接入网全球移动通信系统(Global System for Mobile Communications，GSM)/GSM演进增强数据速率(Enhanced Data rates for GSM Evolution，EDGE)无线接入网络(GSM/EDGE Radio Access Network，GERAN)，3G接入网通用陆地无线接入网(Universal Terrestrial Radio Access Network，UTRAN)与演进分组系统(Evolved Packet System，EPS)核心网演进分组核心网(Evolved Packet Core，EPC)的接入节点，负责从GERAN、UTRAN到演进分组核心网(Evolved Packet Core，EPC)承载的建立和数据的转发。
归属用户服务器(Home Subscriber Server，HSS)，存储移动用户的签约数据。
策略和计费规则功能(Policy and Charging Rules Function，PCRF)：负责计费管理和策略控制，包括策略与计费控制(Policy and Charging Control，PCC)规则，服务质量(Quality of Service，QoS)规则。
如图5所示，是对下一代(Next Generation，NG)移动通信系统的架构示意图，以第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)标准进展中被大家广泛接受和认可的一种系统架构进行示例。
NextGen或NG是下一代移动通信系统架构简称，由UE，AN，核心网(Core network，CN)和数据网络(Data Network)构成，其中，UE、AN、核心网是构成架构的主要成分，逻辑上AN、核心网可以分为用户面和控制面两部分，控制面负责移动网络的管理，用户面负责业务数据的传输。在上述图5中，NG2参考点位于AN控制面和CN控制面之间，NG3参考点位于AN用户面和CN用户面之间，NG6参考点位于CN用户面和数据网络之间。
UE：是移动用户与网络交互的入口，能够提供基本的计算能力，存储能力，向用户显示业务窗口，接受用户操作输入。NextGen UE会采用下一代空口技术，与接入网建立信号连接、数据连接，从而传输控制信号和业务数据到移动网络。
AN：类似于传统网络里面的基站，部署在靠近UE的位置，为特定区域的授权用户提供入网功能，并能够根据用户的级别、业务的需求等使用不同质量的传输隧道传输用户数据。AN能够管理自身的资源，合理利用，按需为UE提供接入服务，把控制信号和用户数据在UE和CN之间转发。
CN：负责维护移动网络的签约数据，管理移动网络的网元，为UE提供会话管理、移动性管理、策略管理、安全认证等功能。在UE附着的时候，为UE提供入网认证；在UE有业务请求时，为UE分配网络资源；在UE移动的时候，为UE更新网络资源；在UE空闲的时候，为UE提供快恢复机制；在UE去附着的时候，为UE释放网络资源；在UE 有业务数据时，为UE提供数据路由功能，如转发上行数据到数据网络；或者从Data Network接收为UE发送的下行数据，转发到AN，从而发送给UE。
Data Network：是为用户提供业务服务的数据网络，一般客户端位于UE，服务端位于数据网络。数据网络可以是私有网络，如局域网，也可以是不受运营商管控的外部网络，如互联网Internet，还可以是运营商共同部署的专有网络，如为了配置IP多媒体网络子系统(IP Multimedia Core Network Subsystem，IMS)服务。
其次，下面介绍数据路径的实现和UE切换过程中结束标记的转发。
在传统移动网络中，UE的数据路径用演进分组系统(Evolved Packet System，EPS)承载实现，如图6所示，为EPS路径实现方式的示意图。承载是端到端的建立，其中无线承载(Radio bearer)：S1bearer：S5/S8bearer＝1:1:1，在EPS系统中有明确的对应关系。在UE切换过程中，有基于X2接口的切换和基于S1接口的切换，其中，如图7所示，是基于X2接口的切换流程示意图，在源eNB和目标eNB之间存在X2接口的时候触发；如图8所示，是基于S1接口的切换流程示意图，在源eNB和目标eNB之间不存在X2接口的时候触发，或者基于X2接口的切换流程失败的时候触发。在本申请实施例的描述中，源用户面路径可以以源路径为简称进行说明，目标用户面路径可以以目标路径为简称进行说明。
如上述图7所示，是基于X2接口的切换流程示意图。eNB1为源基站，eNB2为目标基站，1、eNB1请求eNB2准备路径资源，即准备目标用户面路径承载和转发承载，成功后，eNB1可以收到eNB2返回的响应消息，然后通知UE切换到eNB2；2、eNB2发现UE切换过来后，通知MME切换路径，并通知相应的路径信息；3、MME通知SGW切换下行路径；4、服务网关切换路径，完成后，立刻在源路径上发送一个数据结束标记；5、SGW在目标用户面路径上发送下行数据；6、eNB1接收到SGW发送的结束标记，将这个结束标记转发给eNB2，从而辅助eNB2重排序。
如上述图8所示，是基于S1接口的切换流程示意图。1、eNB1请求MME1在eNB2上准备路径资源，即准备目标用户面路径承载和转发承载；2、MME1向控制eNB2的MME2转发请求；3、MME2请求eNB2准备目标用户面路径资源和切换资源；4、MME2通知SGW2准备切换资源；5、MME1收到MME2的响应后，通知SGW1准备切换路径的资源；6、MME1通知UE切换到eNB2；7、UE切换到eNB2；8、eNB2通知MME2，UE切换完成；9、MME2通知SGW2切换路径；10、SGW2通知PGW切换路径；11、PGW切换路径，在目标用户面路径上发送下行数据；12、SGW2在目标用户面路径上转发下行数据到eNB2；13、PGW切换路径，完成后，立刻在源用户面路径上发送一个结束标记；14、SGW1继续把结束标记转发到eNB1；15、eNB1沿着转发路径发送结束标记到eNB2；16、eNB2接收到结束标记，根据结束标记的序列号对转发的源用户面路径路径的下行数据和目标用户面路径上接收的下行数据进行重排序。
如图9所示，为转发结束标记(end marker)的示意图，核心网控制面(Control Plane，CP)节点MME知道这种对应关系，即Radio bearer：S1bearer：S5/S8bearer：转发承载＝1:1:1:1，会基于每条EPS承载建立转发路径；核心网用户面(User Plane，UP)网关SGW/PGW在切换路径时，在每条UE的源用户面路径上，即承载上发送结束标记，源eNB 会沿着转发路径把结束标记发送给目标eNB，辅助其排序。在图7所示的UE切换过程中，UE会转换服务的eNB1，连接到eNB2，并且以1:1的比例关系，建立基于源用户面路径(S1承载，RB等)的转发承载。之后会依照图中所示的1、2、3、4、5、6的顺序处理数据。1、在转发路径上优先传输eNB1中尚未传输完成的分组数据汇聚层协议(Packet Data Convergence Protocol，PDCP)数据包；2、eNB1把对应源用户面路径上发送过来的新下行数据放到转发路径上；3、UE路径切换完成后，UP网关(SGW/PGW)在源用户面路径上发送结束标记；4、eNB2上的转发承载收到转发过来的数据后，优先处理；5、eNB2如果在收到转发的end marker之前收到目标用户面路径发送来的下行数据，先进行缓冲；6、eNB2收到转发路径上的结束标记后，再根据end marker的PDCP的最大序列号(Sequence Number，SN)，继续对目标用户面路径接收的下行数据进行排序处理，从而end marker能够辅助eNB2进行下行数据的排序处理。
最后，对5G用户面路径重选说明如下。
在5G的用户面路径切换过程中，UE从源用户面路径切换为目标用户面路径，因为在目标用户面路径上用户面网关的改变，即由UP GW变为边缘网关，那么，第一，因为在互联网中仍然留有残存数据，源用户面网关无法确定何时发送结束标记；第二，当源用户面路径中本地数据流和其他数据流共存时，AN节点无法确定要切换成边缘网关的再向UE发送的本地数据流；所以AN节点无法解决用户面路径重选带来的数据乱序问题。
本申请实施例中将提出一种发送结束标记的方法，用以解决用户面路径重选过程中下行数据乱序的问题。如图10所示，在一种可能的实现方式中，控制面CP节点收到会话更新响应时，CP节点根据会话更新响应向UP GW发送触发信息，然后通知MANO(本地数据网络的业务管理单元)为本地数据流切换路径；接入网关完成UE的用户面路径切换后，在互联网上发送一个或者多个结束数据包；UP GW收到结束数据包后，因为该结束数据包与触发信息对应，所以，根据该触发信息和结束数据包激活触发器，完成本地数据流上下文的更新，如流过滤器模板(Traffic Filter Template，TFT)，服务质量(Quality of Service，QoS)等信息，然后UP GW在源用户面路径上发送结束标记(end marker)。
需要说明的是，核心网网元功能分为控制面功能和用户面功能。核心网网元功能分为CP与UP。UP主要负责分组数据包的转发、QoS控制、计费信息统计等。CP主要负责向用户面功能下发数据包转发策略、QoS控制策略、计费信息统计上报策略等。
“UP”只是对执行用户面功能的设备的统称，并不特指某个或某些设备，在实际应用中，也可能对执行用户面功能的设备不称之为“UP”，而以其他名称代替，具体此处不做限定，本申请中以“UP节点”为例进行说明。
同理，“CP”只是对执行控制面功能的设备的统称，并不特指某个或某些设备，在实际应用中，也可能对执行控制面功能的设备不称之为“CP”，而以其他名称代替，具体此处不做限定，本申请中以“CP节点”为例进行说明。
在实际应用中，UP和CP既可以是单独的设备，也可以是其他设备(诸如服务器等)上的一组功能实体，具体此处不做限定。
下面以实施例的方式，对本申请技术方案做进一步的说明，如图11所示，为本申请实 施例中发送结束标记的方法的一个实施例示意图，包括：
1101、CP节点接收会话更新响应，会话更新响应包括UE的源用户面路径的ID或UE的目标用户面路径的ID，源用户面路径包含UP GW。
在CP节点接收会话更新响应之前，CP节点可以向边缘网关发送会话更新请求，再接收边缘网关发送的会话更新响应。示例性的，这里的会话更新请求可以为更新承载请求(Update Bearer Request)，会话更新响应可以为更新承载响应(Update Bearer Response)。会话更新响应可以包括UE的源用户面路径的标识或者UE的目标用户面路径的标识，源用户面路径包含UP GW，目标用户面路径包含边缘网关Edge GW。
本申请实施例中，若源用户面路径和目标用户面路径的AN节点相同，则源用户面路径为包含UE、AN节点、UP GW和Access GW的路径，目标用户面路径为包含UE、AN节点、Edge GW和Access GW的路径。在源用户面路径上UE和AN节点之间为第一承载(First Bearer)、AN节点和UP GW之间为第一隧道(First Tunnel)；在目标用户面路径上UE和AN节点之间为第二承载(Second Bearer)、AN节点和Edge GW之间为第二隧道(Second Tunnel)；Edge GW和Access GW之间为外部隧道(External Tunnel)。
若源用户面路径和目标用户面路径的AN节点不相同，可以以AN1节点为源AN节点，AN2节点为目标AN节点为例进行说明。其中，源用户面路径为包含UE、AN1节点、UP GW和Access GW的路径，目标用户面路径为包含UE、AN2、Edge GW和Access GW的路径。UE和AN1节点之间为第一承载(First Bearer)、AN1节点和UP GW之间为第一隧道(First Tunnel)；UE和AN2节点之间为第二承载(Second Bearer)、AN2节点和Edge GW之间为第二隧道(Second Tunnel)；Edge GW和Access GW之间为外部隧道(External Tunnel)。
1102、CP节点根据会话更新响应，向UP GW发送触发信息和源用户面路径的ID，触发信息用于UP GW在源用户面路径上向AN节点发送结束标记。
示例性的，这里的触发信息可以为：第一业务流样板和定时器参数中的至少一种，第一业务流样板是用来检测结束数据包的，结束数据包用来表示UE用户面路径切换后，在源用户面路径上传输的最后一个数据包。即这里的触发信息可以有几下几种可能性，分别为：(1)第一业务流样板；(2)第一业务流样板和定时器参数；(3)定时器参数。这里的触发信息还可以是指示标识等信息，具体不做限定。需要说明的是，这里的第一业务流样板是用来过滤结束数据包的，即UP GW根据第一业务流样板过滤从Access GW发送的结束数据包，当UP GW过滤出结束数据包时，UP GW向源AN节点发送结束标记(End Marker)。
例如，第一业务流样板可以如下表1所示，或者，当表1去掉路径标识ID那一栏，也可以以作为第一业务流样板。
Figure PCTCN2017077123-appb-000001
Figure PCTCN2017077123-appb-000002
表1
进一步的，这里的定时器参数可以是一个示例性的值，如2ms，那么，在UP GW侧的定时器的值可以设置为0—2ms，超过2ms就属于超时，也可以将定时器设置为8—10ms，超过10ms属于超时，定时器的初始值具体可以根据实际情况而定；定时器参数还可以是区间参数，即这个区间参数为[a，b]，那么，可以将定时器的初始值设置为a值，超时值设置为b值，当定时器超过b值时，属于超时；定时器参数还可以是a和b值，其中，a值属于定时器的初始值，超时值为a+b＝c值，那么，定时器超过c值时，属于超时。
还需要说明的是，当触发信息为定时器参数时，UP GW接收控制面CP节点发送的触发信息后，UP GW会立即启动定时器，若UP GW定时器超时，则UP GW向AN1节点发送结束标记，UP GW不需要根据接入网关发送的结束数据包来确定何时发送结束标记。
1103、UP GW接收CP节点发送的触发信息和UE的源用户面路径的标识ID，UP GW位于源用户面路径上。
示例性的，触发信息可以为第一业务流样板和定时器参数中的至少一种。
1104、Access GW接收路径切换通知，路径切换通知包括业务流样板。
示例性的，Access GW接收路径切换通知，可以包括：Access GW接收从边缘网关或本地管理单元发送的路径切换通知。
1105、Access GW根据业务流样板，向UP GW发送结束数据包。
其中，该结束数据包的IP五元组信息可以由第一业务流样板确定。
需要说明的是，步骤1105是可选的步骤，即当上述步骤中的触发信息包括第一业务流样板时，步骤1105是必要的。
1106、UP GW根据触发信息和源用户面路径的ID，在源用户面路径上向AN节点发送结束标记。
示例性的，步骤1106可以包括以下场景：
(1)触发信息包括第一业务流样板；
当UP GW接收的UE的下行数据包的IP五元组信息与第一业务流样板中的任一IP五元组信息相同时，UP GW根据源用户面路径的ID，在源用户面路径上向AN节点发送结束标记。
这里的第一业务流样板可以理解为结束数据包过滤器，UP GW检测到互联网路径过来的结束数据包后，在源用户面路径上发送结束标记，并更新本地数据流的上下文。
(2)触发信息包括第一业务流样板和定时器参数；
当UP GW接收的UE的下行数据包的IP五元组信息与第一业务流样板中的任一IP五元组信息相同时，UP GW启动定时器，定时器是根据定时器参数设置的；若UP GW接收 到结束数据包，且定时器未超时，则UP GW重启定时器，结束数据包的IP五元组信息与第一业务流样板中的任一IP五元组信息相同；当定时器超时时，UP GW根据源用户面路径的ID，向AN节点发送结束标记。
即UP GW根据第一业务流样板，检测到从源用户面路径发送过来的结束数据包后，启动定时器，在定时器未超时这段时间内，如果UP GW收到其他后续结束数据包或者收到由本地网络发送的数据包时，UP GW重设定时器；若果未收到结束数据包或者由本地网络发送的数据包，导致定时器超时，则UP GW立刻在源用户面路径上发送结束标记，并更新本地数据流的上下文。
(3)触发信息包括定时器参数；
UP GW根据定时器参数设置定时器；UP GW启动定时器；当定时器超时时，UP GW根据源用户面路径的ID，在源用户面路径上向AN节点发送结束标记。
这里启动定时器的时间是当UP GW接收到定时器参数后，立刻启动定时器，UP GW在定时器的时间内如果收到由本地网络发送的数据包，就会重设定时器；如果UP GW持续没有收到由本地网络发送的数据包导致定时器超时，那么表示源用户面路径(互联网)上由本地网络发送的数据包传输结束，在源用户面路径上发送结束标记，并更新本地数据流的上下文。
当源用户面路径和目标用户面路径的AN节点相同时，UP GW根据触发信息和源用户面路径的ID向AN节点发送结束标记，AN节点收到结束标记，就可以对目标用户面路径上接收的下行数据包进行排序处理了，再将排序后的下行数据包发送给UE。
当源用户面路径和目标用户面路径的AN节点不相同时，UP GW根据触发信息和源用户面路径的ID向AN1节点发送结束标记，AN1节点再将结束标记转发给AN2节点，AN2节点收到结束标记后，可以根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理，再将排序后的下行数据包发送给UE。
在本申请实施例中，在UE的用户面路径重选过程中，从源用户面路径切换为目标用户面路径，源用户面路径包含UP GW，目标用户面路径包含边缘网关。CP节点接收会话更新响应，根据该会话更新响应向UP GW发送触发信息和源用户面路径的标识ID，UP GW根据接收的触发信息和源用户面路径的标识ID，来确定UP GW何时向AN节点发送结束标记，进而辅助在目标用户面路径上接收的下行数据包进行排序处理。本申请实施例中可以增强用户面网关的功能，还可以重用传统网元的大部分功能，不需要对现有的切换流程进行大范围修改，简单清晰，容易实施。解决由于互联网的不可靠性，降低了源用户面路径上少量数据的丢失。
如图12所示，为本申请实施例中发送结束标记的方法的另一个实施例示意图，包括：
1201、AN节点接收CP节点发送的流切换指示消息，流切换指示消息包含用户设备UE的源用户面路径的ID，流切换指示消息用于指示AN节点在源用户面路径上接收到结束标记时确定AN节点在源用户面路径上接收到的下行数据包是否已成功发送给UE。
示例地，在CP节点根据用户面报告、切换请求或者应用请求选择边缘网关后，CP节点可以向AN节点发送上述流切换指示消息，那么，AN节点接收控制面CP节点发送的上 述流切换指示消息。
需要说明的是，本实施例中源用户面路径和目标用户面路径中的AN节点相同，那么，源用户面路径为包含UE、AN节点、UP GW和Access GW的路径，目标用户面路径为包含UE、AN节点、Edge GW和Access GW的路径。在源用户面路径上UE和AN节点之间为第一DRB、AN节点和UP GW之间为主要隧道；在目标用户面路径上UE和AN节点之间为第二DRB、AN节点和Edge GW之间为次要隧道(Second Tunnel)；Edge GW和Access GW之间为外部隧道(External Tunnel)。
应理解，AN节点收到的下行数据包包括本地网络发送的数据包和/或互联网发送的数据包。因为这里的UE的用户面路径的切换是针对本地数据流的路径切换，但是在AN节点接收的数据包不止本地数据流，AN节点没法识别出在源用户面路径上接收的本地数据流，若在源用户面路径上的本地数据流没有成功发送给UE，就不能及时根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理了。所以，AN节点收到流切换指示消息后，可以根据流切换指示消息在第一DRB上向UE发送AN节点在源用户面路径上接收的下行数据包(本地数据流和/或互联网数据流)。
1202、CP节点接收会话更新响应，会话更新响应包括UE的源用户面路径的ID或UE的目标用户面路径的ID，源用户面路径包含UP GW。
1203、CP节点根据会话更新响应，向UP GW发送触发信息和源用户面路径的ID，触发信息用于UP GW在源用户面路径上向AN节点发送结束标记。
1204、UP GW接收CP节点发送的触发信息和UE的源用户面路径的ID，UP GW位于源用户面路径上。
1205、Access GW接收路径切换通知，路径切换通知包括业务流样板。
1206、Access GW根据业务流样板，向UP GW发送结束数据包。
1207、UP GW根据触发信息和源用户面路径的ID，在源用户面路径上向AN节点发送结束标记。
在本申请实施例中，步骤1202-1207与图11所示的步骤1101-1106类似，可以参考图11中的步骤1101-1106，此处不再赘述。
1208、当AN节点在源用户面路径上接收到结束标记时，AN节点确定AN节点在源用户面路径上接收的下行数据包是否已成功发送给UE。
当AN节点在源用户面路径上接收到UP GW发送的结束标记时，AN节点需要先确定AN节点在源用户面路径上接收的下行数据包是否已成功发送给UE。
示例性的，若AN节点在源用户面路径上接收的数据包有10个，那么，AN节点在收到结束标记后，得先确定这10个数据包是否都成功发送给UE。
1209、若AN节点在源用户面路径上接收到的UE的下行数据包已成功发送给UE，则AN节点根据结束标记对AN节点在UE的目标用户面路径上接收的下行数据包进行排序。
若AN节点在源用户面路径上接收到的UE的下行数据包已成功发送给UE，则AN节点根据结束标记对AN节点在UE的目标用户面路径上接收的下行数据包进行排序。若AN节点在源用户面路径上接收到的下行数据包中存在至少一个数据包未成功发送给UE，则 AN节点向UE发送至少一个数据包。
示例性的，应理解，AN节点在未接收结束标记时，已经在第一DRB上向UE发送在源用户面路径上接收的下行数据包，若AN节点在源用户面路径上接收的下行数据包有10个，那么，AN将这10个下行数据包在第一DRB上向UE发送，若成功发送给UE，会收到UE反馈的10个成功标识。
当AN节点接收到结束标记时，若AN节点已经收到10个UE反馈的成功标识，则证明UE在第一DRB上向UE发送的数据包都成功发送了，那么，AN节点就可以根据结束标记中的序列号对目标用户面路径上接收到的下行数据包进行排序处理了，并将排序后的下行数据包在第二DRB上向UE发送。
当AN节点接收到结束标记时，若AN节点只收到8个UE反馈的成功标识，则证明UE在第一DRB上向UE发送的数据包还没有全部成功发送给UE，若还没发送，则将剩余的2个下行数据包在第一DRB上向UE发送，并等待反馈的成功标识，若已发送，只是还未收到UE反馈的成功标识，则继续等待，直到收到UE反馈的2个成功标识，那么，AN节点就可以根据结束标记中的序列号对目标用户面路径上接收到的下行数据包进行排序处理了，并将排序后的下行数据包在第二DRB上向UE发送。
在本申请实施例中，AN节点收到流切换指示消息后，可以根据流切换指示消息在第一DRB上向UE发送在源用户面路径上接收的下行数据包，UP GW可以根据触发信息和源用户面路径的ID，向AN节点发送结束标记，当AN节点收到UP GW发送的结束标记时，需先确定AN节点在源用户面路径上接收的数据包是否已成功发送给UE，即保证AN节点在源用户面路径上接收的本地数据流成功发送给UE，那么，AN节点可以根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理了。有效保障了UE的用户面路径切换后，AN节点在源用户面路径上接收的本地数据流的成功发送，进而，减少因UE的用户面路径的切换，造成的数据丢失，进而，AN节点根据结束标记对在目标用户面路径上接收的下行数据包进行处理。
如图13所示，为本申请实施例中发送结束标记的方法的另一个实施例示意图，包括：
1301、接入网AN节点从控制面CP节点接收流切换指示消息，流切换指示消息包含用户设备UE的源用户面路径的标识ID。
需要说明的是，本实施例中源用户面路径和目标用户面路径中的AN节点相同，那么，源用户面路径为包含UE、AN节点、UP GW和Access GW的路径，目标用户面路径为包含UE、AN节点、Edge GW和Access GW的路径。在源用户面路径上UE和AN节点之间为第一DRB、AN节点和UP GW之间为主要隧道；在目标用户面路径上UE和AN节点之间为第二DRB、AN节点和Edge GW之间为次要隧道(Second Tunnel)；Edge GW和Access GW之间为外部隧道(External Tunnel)。
示例性的，流切换指示消息的作用包含但不限于以下所说的几种：
(1)流切换消息信息用于指示AN节点向UP GW发送AN节点在源用户面路径上接收到的下行数据包；
(2)流切换指示消息还包含业务流样板，流切换指示消息用于指示AN节点根据业务 流样板和源用户面路径的ID将AN节点在源用户面路径上接收的本地网络发送的数据包通过目标DRB发送给UE，目标DRB为在UE的目标用户面路径上UE与AN节点之间的传输路径；应理解，这里的业务流样板用来过滤本地数据网络发送的数据包，即本地数据流，目标DRB可以为上述所说的第二DRB。
1302、CP节点接收会话更新响应，会话更新响应包括UE的源用户面路径的ID或UE的目标用户面路径的ID，源用户面路径包含UP GW。
1303、CP节点根据会话更新响应，向UP GW发送触发信息和源用户面路径的ID，触发信息用于UP GW在源用户面路径上向AN节点发送结束标记。
1304、UP GW接收CP节点发送的触发信息和UE的源用户面路径的ID，UP GW位于源用户面路径上。
1305、Access GW接收路径切换通知，路径切换通知包括业务流样板。
1306、Access GW根据业务流样板，向UP GW发送结束数据包。
1307、UP GW根据触发信息和源用户面路径的ID，在源用户面路径上向AN节点发送结束标记。
在本申请实施例中，步骤1302-1307与图11所示的步骤1101-1106类似，可以参考图11中的步骤1101-1106，此处不再赘述。
1308、AN节点根据流切换指示消息，发送AN节点在源用户面路径上接收的下行数据包，源用户面路径包括用户面网关UP GW。
由于流切换指示信息的作用不同，那么，AN节点执行的内容也不同，具体包括如下场景：
(1)流切换消息信息用于指示AN节点向UP GW发送AN节点在源用户面路径上接收到的下行数据包。
AN节点根据流切换指示消息，发送AN节点在源用户面路径上接收的下行数据包，可以包括：AN节点根据流切换指示消息，将AN节点在源用户面路径上接收到的下行数据包发送给UP GW。
在实际应用中，UP GW接收CP节点发送的流切换指示消息，流切换指示消息包括源用户面路径的ID和第二业务流样板；应理解，这里的第二业务流样板用来过滤本地网络发送的数据包。UP GW根据第二业务流样板和源用户面路径的ID，从在源用户面路径上接收AN节点发送的下行数据包中识别出本地网络发送的数据包；UP GW向边缘网关发送识别出的数据包，边缘网关位于UE的目标用户面路径上。边缘网关接收UP GW发送的识别出的数据包，再将其转发回AN节点；AN节点可以在第二DRB上传输识别出的数据包。
需要说明的是，当AN节点接收从UP GW发送的结束标记时，停止向UP GW转发AN节点在源用户面路径上接收的下行数据包，并将该结束标记转发回UP GW；UP GW收到结束标记后，转发给边缘网关，当AN节点接收从边缘网关转发回来的结束标记时，就可以根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理了。
应理解，AN节点不能识别出本地数据流，通过核心网选择的分流节点UP GW来识别出本地网络发送的数据包，并将识别出的数据包通过第二DRB发送给UE，有效减少了因 UE的用户面路径切换导致本地数据流的丢失，并可以将源用户面路径上的本地数据流切换到目标用户面路径上传输给UE。
(2)流切换指示消息还包含业务流样板，流切换指示消息用于指示AN节点根据业务流样板和源用户面路径的ID将AN节点在源用户面路径上接收的本地网络发送的数据包通过目标DRB发送给UE，目标DRB为在UE的目标用户面路径上UE与AN节点之间的传输路径。
AN节点根据流切换指示消息，发送AN节点在UE的源用户面路径上接收的下行数据包，可以包括：AN节点根据业务流样板，识别出本地网络发送的数据包；AN节点根据流切换指示消息和源用户面路径的ID，将识别出的数据包通过目标DRB发送给UE。
应理解，在这种可选的实现方案中，AN节点暂时可以识别由本地网络发送的数据包，并将识别出的数据包在切换后的目标用户面路径上向UE传输，进而，当AN节点收到结束标记后，可以根据结束标记对AN节点在目标用户面路径上接收的下行数据包进行排序处理了，还可以将排序处理后的下行数据包发送给UE。
需要说明的是，步骤1308与1302-1307的时序不做限定。
在本申请实施例中，AN节点从控制面CP节点接收流切换指示消息，AN节点根据流切换指示消息，发送AN节点在源用户面路径上接收的下行数据包。示例性的实现可以参见上述的说明，一种是通过分流节点UP GW识别出在源用户面路径上接收的本地数据流，一种是AN节点可以识别出在源用户面路径上接收的本地数据流，并将识别出的本地数据流向UE发送，UP GW可以根据触发信息和源用户面路径的ID，向AN节点发送结束标记，当AN节点收到UP GW发送的结束标记时，可以根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理了。
如图14所示，为本申请实施例中发送结束标记的方法的另一个实施例示意图，包括：
在本申请实施例中，在控制面通知管理和编排(management and orchestration，MANO)网元为本地数据流切换路径前，首先要把触发信息通知给UP GW(切换路径前的用户面网关)；然后通知MANO，MANO通知本地数据网络的接入网关，通过创建隧道或者更新隧道上下文为本地数据流激活在目标用户面路径上下行数据的传输，完成路径切换；UP GW根据触发信息在源用户面路径上发送结束标记，并更新本地数据流的上下文。如下所示：
1401、基于S1接口或者X2接口的切换资源准备阶段。
UE、AN1节点、AN2节点、CP节点、用户面网关UP GW、边缘网关Edge GW、接入网关Access GW和MANO会为UE在切换流程中的目标用户面路径上准备网络资源，示例性的，可以是基于X2接口的切换准备网络资源，还可以是基于S1接口的切换准备网络资源。本申请实施例中，可以以AN1节点为源AN节点，AN2节点为目标AN节点为例进行说明。其中，源用户面路径为包含UE、AN1、UP GW和Access GW的路径，目标用户面路径为包含UE、AN2、Edge GW和Access GW的路径。UE和AN1之间为第一承载(First Bearer)、AN1和UP GW之间为第一隧道(First Tunnel)；UE和AN2之间为第二承载(Second Bearer)、AN2和Edge GW之间为第二隧道(Second Tunnel)；Edge GW和Access GW之间为外部隧道(External Tunnel)。
1402、源AN节点将切换需求发送给UE。
源AN节点向UE发送切换需求(Handover Command)；UE接收源AN节点发送的切换需求；即AN1节点通知UE进行路径的切换。
1403、UE将切换确认(Handover Confirmation)消息发送给目标AN节点。
即UE路径切换完成后，AN2节点收到UE发送的切换确认消息。
1404、目标AN节点将切换通知(Handover notify)或者路径切换请求(Handover Request)发送给CP节点；
即AN2节点通知CP节点，UE已经成功切换到AN2。
1405、CP节点根据切换通知或者路径切换请求选择边缘网关。
CP节点根据切换通知或者路径切换请求，为UE选择目标用户面路径包含的边缘网关(Edge GW)，为本地数据流激活Edge GW到AN2节点的路径；即CP节点为本地数据流选择新的边缘网关，激活新的用户面路径。其中，本地数据流是由本地网络发送的数据包，应理解，这里的切换通知或者路径切换请求包括UE的IP地址和边缘网关的IP地址。
1406、CP节点将会话更新请求发送给边缘网关。
应理解，这里的会话更新请求可以是更新承载请求(Update Bearer Request)，更新承载请求还可以携带NG3接口信息；CP节点向边缘网关发送更新承载请求；边缘网关接收CP节点发送的更新承载请求。即CP节点通知边缘网关为本地数据流创建目标用户面路径，其中携带的信息包括但不限于AN2节点的路径信息：具体为AN2节点的IP地址和隧道ID；边缘网关的路径信息：边缘网关的IP地址和隧道ID；第二流过滤器模板(Traffic Filter Template，TFT)或者称呼为第二业务流样板，服务质量(Quality of Service，QoS)信息等。需要说明的是，这里的第二业务流样板是用来过滤由本地网络发送的数据包的。在实际应用中，第二业务流样板是非接入(Non-access stratum，NAS)层的信息，AN节点会将第二业务流样板传给UE，让UE准备上下文。
1407、边缘网关将会话更新响应发送给CP节点。
应理解，这里的会话更新响应可以是更新承载响应；边缘网关向CP节点发送更新承载响应(Update Bearer Response)；控制面CP节点接收CP节点发送的会话更新响应，会话更新响应包括UE的目标用户面路径的标识，目标用户面路径包含边缘网关Edge GW；即CP节点收到边缘网关发送的确认消息。
1408、CP节点根据会话更新响应，将触发信息和源用户面路径的ID发送给UP GW。
CP节点根据会话更新响应，向UP GW发送触发信息和源用户面路径的ID，触发信息和和源用户面路径的ID用于UP GW在源用户面路径上向源AN节点发送结束标记。用户面网关UP GW接收控制面CP节点发送的触发信息和源用户面路径的ID，UP GW位于用户设备UE的源用户面路径上。其中，CP节点还可以向UP GW发送第二业务流样板，这里的第二业务流样板是用来过滤由本地网络发送的数据包的。
示例性的，这里的触发信息可以是第一业务流样板和定时器参数中的至少一种，第一业务流样板是用来检测结束数据包的，结束数据包用来表示在源用户面路径上最后传输的数据包。即这里的触发信息有几下几种可能性，分别为：(1)第一业务流样板；(2)第一 业务流样板和定时器参数；(3)定时器参数。这里的触发信息还可以是指示标识，具体不做限定。需要说明的是，这里的第一业务流样板与上述所说的第二业务流样板不同，这里的第一业务流样板是用来过滤结束数据包的，即UP GW根据第一业务流样板过滤从Access GW发送的结束数据包，当UP GW过滤出结束数据包时，UP GW向源AN节点发送结束标记(End Marker)。
示例性的，第二业务流样板还可以如下表2所示，或者，当表2去掉路径标识ID那一栏，也可以以作为第二业务流样板：
Figure PCTCN2017077123-appb-000003
表2
进一步的，这里的定时器参数可以是一个示例性的值，如2ms，那么，在UP GW侧的定时器的值可以设置为0—2ms，超过2ms就属于超时，也可以将定时器设置为8—10ms，超过10ms属于超时，定时器的初始值具体可以根据实际情况而定；定时器参数还可以是区间参数，即这个区间参数为[a，b]，那么，可以将定时器的初始值设置为a值，超时值设置为b值，当定时器超过b值时，属于超时；定时器参数还可以是a和b值，其中，a值属于定时器的初始值，超时值为a+b＝c值，那么，定时器超过c值时，属于超时。
还需要说明的是，当触发信息为定时器参数时，UP GW接收控制面CP节点发送的触发信息后，UP GW会立即启动定时器。
CP节点在触发本地数据流路径切换之前，向UP GW发送更新上下文的请求，携带触发信息，触发信息可以为第一业务流样板和/或定时器参数，相关的路径信息，本地数据流TFT等信息。第二业务流样板也可以称呼为本地数据流TFT，其中，第二业务流样板还可以为一个或多个IP五元组信息，例如(UE IP，10000，App IP，80，GTP-U)和/或(UP GW IP，10000，Edge GW IP，80，GTP-U)，可选的，CP节点还可以向AN2节点发送路径切换响应，用于告诉AN2节点可以通过AN2节点向UE传输下行数据包了。
1409、CP节点将路径切换通知或者路径切换请求发送给MANO。
应理解，这里的切换通知或者路径切换请求包括UE的IP地址和边缘网关的IP地址，在实际应用中，还可以包括APP的IP地址等信息。
需要说明的是，当触发信息为第一业务流样板，或者，第一业务流样板和定时器参数时，那么，这里的切换通知或者路径切换请求还包括第一业务流样板。
1410、MANO将路径切换通知或者路径切换请求发给Access GW接入网关。
其中，切换通知或者路径切换请求可以包括用户设备UE的互连网协议IP地址和边缘网关的IP地址；当步骤1108中的触发信息为第一业务流样板，或者，第一业务流样板和定时器参数时，这里的切换通知或者路径切换请求还包括第一业务流样板。其中，这里的第一业务流样板与控制面CP节点向用户面网关UP GW发送的第一业务流样板相同，是用来确定结束数据包的，边缘网关位于目标用户面路径上。
1411、Access GW根据UE的IP地址和边缘网关的IP地址，向边缘网关发送UE的下行数据包。
例如，接入网关可以根据UE的IP地址和边缘网关的IP地址，确定UE的目标用户面路径，完成UE用户面路径的切换，Access GW可以在目标用户面路径上发送UE的下行数据包，即Access GW向边缘网关发送UE的下行数据包。
需要说明的是，在用户面路径切换之前，Access GW还是在源用户面路径上发送UE的下行数据包。
1412、Access GW根据第一业务流样板，将数据包发送给UP GW。
其中，UP GW位于源用户面路径上；UP GW接收Access GW发送的结束数据包。应理解，这里向UP GW发送的结束数据包的IP五元组信息是由第一业务流样板确定的。
需要说明的是，步骤1412是可选的步骤，即当步骤1408中的触发信息为定时器参数时，步骤1412可选。即在实际应用中，(1)当触发信息为第一业务流样板时，Access GW根据第一业务流样板向UP GW发送一个结束数据包，这个结束数据包的IP五元组信息与第一业务流样板中包括的其中一个IP五元组信息相同。(2)当触发信息为第一业务流样板和定时器参数时，Access GW根据第一业务流样板向UP GW发送多个结束数据包，那么，这多个结束数据包的IP五元组信息可以相同，也可以不同，但这多个结束数据包的IP五元组信息都需要被包含在第一业务流样板中。
需要说明的是，步骤1411和1412的时序具体不做限定。结束数据包的格式可以是(UE IP，10000，App IP，80，GTP-U)和/或(UP GW IP，10000，Edge GW IP，80，GTP-U)等。构造结束数据包关键是要其能够到达UP GW，并能够被UP GW识别，所以，CP节点会将第一业务流样板发送给UP GW和Access GW。而且，这里结束数据包还可以由控制面、边缘网关等构造，具体如下所示：控制面或者边缘网关根据第一业务流样板，生成一个空的IP数据包，IP数据包头用第一业务流样板中的IP地址和端口号填充，IP数据包负载用第一业务流样板中的协议信息，填充一个协议头。
1413、UP GW根据触发信息和源用户面路径的ID，在源用户面路径上将结束标记发送给AN节点。
其中，结束标记用于AN节点对目标用户面路径上接收的下行数据包进行排序；接入网AN节点接收UP GW发送的结束标记。
示例性的，可以包括：
(1)触发信息包括第一业务流样板；当UP GW接收的UE的下行数据包的IP五元组信息与第一业务流样板中的任一IP五元组信息相同时，UP GW根据源用户面路径的ID， 在源用户面路径上向AN节点发送结束标记。
这里的第一业务流样板简单的可以理解为结束数据包过滤器，UP GW检测到互联网路径过来的结束数据包后，在源用户面路径上发送结束标记，并更新本地数据流的上下文。
(2)触发信息包括第一业务流样板和定时器参数；当UP GW接收的UE的下行数据包的IP五元组信息与第一业务流样板中的任一IP五元组信息相同时，UP GW启动定时器，定时器是根据定时器参数设置的；若UP GW接收到结束数据包，且定时器未超时，则UP GW重启定时器，结束数据包的IP五元组信息与第一业务流样板中的任一IP五元组信息相同；当定时器超时时，UP GW根据源用户面路径的ID，向AN节点发送结束标记。
即UP GW根据第一业务流样板，检测到从源用户面路径发送过来的结束数据包后，启动定时器，在定时器未超时这段时间内，如果UP GW收到其他后续结束数据包或者收到由本地网络发送的数据包时，UP GW重设定时器；若果未收到结束数据包或者由本地网络发送的数据包，导致定时器超时，则UP GW立刻在源用户面路径上发送结束标记，并更新本地数据流的上下文。
(3)触发信息包括定时器参数，UP GW根据定时器参数设置定时器；UP GW启动定时器；当定时器超时时，UP GW根据源用户面路径的ID，在源用户面路径上向AN节点发送结束标记。
这里启动定时器的时间是当UP GW接收到定时器参数后，立刻启动定时器，UP GW在定时器的时间内如果收到由本地网络发送的数据包，就会重设定时器；如果UP GW持续没有收到由本地网络发送的数据包导致定时器超时，那么表示源用户面路径(互联网)上由本地网络发送的数据包传输结束，在源用户面路径上发送结束标记，并更新本地数据流的上下文。
1414、源AN节点将结束标记发送给目标AN节点。
例如，由源AN节点通过源AN节点和目标AN节点之间的转发隧道，将结束标记转发给目标AN节点。
1415、目标接入网AN节点根据结束标记，对在目标用户面路径上接收到的下行数据包进行排序。
需要说明的是，目标AN节点在接收到结束标记之前，对在目标用户面路径上收到的下行数据包进行缓冲，在收到结束标记后，才能激活对目标用户面路径过来的下行数据包的处理。
在本申请实施例中，UP GW根据触发信息和源用户面路径的ID，来通过确定UP GW何时发送结束标记，触发信息可以为第一业务流样板和/或定时器参数，源AN节点再将结束标记转发给目标AN节点，目标AN节点根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理。即通过EPS系统中end marker转发方法的增强，来解决因为互联网中仍然留有的残存数据，UP GW无法确定何时发送结束标记，不能保证下行数据的有序性的问题，本申请实施例中可以增强用户面网关的功能，还可以重用传统网元的大部分功能，不需要对现有的切换流程进行大范围修改，简单清晰，容易实施。解决由于互联网的不可靠性，降低了在源用户面路径上少量数据的丢失。
如图15所示，为本申请实施例中发送结束标记的方法的另一个实施例示意图，包括：
在控制面通知管理和编排(management and orchestration，MANO)网元为本地数据流切换路径前，首先要把触发信息通知给UP GW(切换路径前的用户面网关)；然后通知边缘网关，边缘网关通知本地数据网络的接入网关，通过创建隧道或者更新隧道上下文为本地数据流激活在目标用户面路径上下行数据的传输，完成路径切换；UP GW根据触发信息在源用户面路径上发送结束标记，并更新本地数据流的上下文。如下所示：
1501、基于S1接口或者X2接口的切换资源准备阶段。
1502、源AN节点将切换需求发送给UE。
1503、UE将切换确认消息发送给目标AN节点。
1504、目标AN节点将切换通知或者路径切换请求发送给CP节点。
1505、CP节点根据切换通知或者路径切换请求选择边缘网关。
在本申请实施例中，步骤1501-1505与图14中的步骤1401-1405类似，此处不再赘述。
1506、CP节点向MANO发送本地数据流信息，获取Access GW的IP地址。
CP节点向MANO发送本地数据流信息；MANO根据本地数据流信息向CP节点发送Access GW的IP地址。其中，本地数据流信息包含UE正在使用的本地IP地址，MANO根据本地配置信息，找到本地IP地址所在的本地网络的接入网关信息。
1507、CP节点将触发信息和源用户面路径的ID发送给UP GW。
CP节点向UP GW发送触发信息和源用户面路径的ID，触发信息和源用户面路径的ID用于UP GW向源AN节点发送结束标记。用户面网关UP GW接收控制面CP节点发送的触发信息和源用户面路径的ID，UP GW位于用户设备UE的源用户面路径上。其中，CP节点还可以向UP GW发送第二业务流样板，这里的第二业务流样板是用来过滤由本地网络发送的数据包的。
示例性的，这里的触发信息可以是第一业务流样板和定时器参数中的至少一种，第一业务流样板是用来检测结束数据包的，用来表示在源用户面路径上最后传输的数据包。详细可以参考图14中的步骤1408中的描述，此处不再赘述。
1508、CP节点将会话更新请求发送给边缘网关。
在本申请实施例中，步骤1508与图14中的步骤1406类似，此处不再赘述。
1509、边缘网关将路径切换通知或者路径切换请求发送给Access GW。
应理解，这里的切换通知或者路径切换请求包括UE的IP地址和边缘网关的IP地址。需要说明的是，当触发信息为第一业务流样板，或者，第一业务流样板和定时器参数时，那么，这里的切换通知或者路径切换请求还包括第一业务流样板。
1510、边缘网关将会话更新响应发送给CP节点。
1511、Access GW根据UE的IP地址和边缘网关的IP地址，向边缘网关发送UE的下行数据包。
1512、Access GW根据第一业务流样板，将数据包发送给UP GW。
1513、UP GW根据触发信息，将结束标记发送给源AN节点。
1514、源AN节点将结束标记发送给目标AN节点。
1515、目标接入网AN节点根据结束标记，对在目标用户面路径上接收到的下行数据包进行排序。
在本申请实施例中，步骤1510与图14中的步骤1407类似，步骤1511-1515与图14中的步骤1411-1415类似，此处不再赘述。
在本申请实施例中，与图14所示的实施例相比，区别在于控制面CP节点不通过MANO切换路径，而是通知边缘网关，建立到本地数据网络的接入网关的隧道或者更新已有隧道的上下文，来完成本地数据流路径的切换。对源用户面网关进行增强，支持控制面节点携带触发信息，用户面网关根据触发信息确定本地数据流在源用户面路径上的结束，来发送结束标记并更新用户面上下文。即UP GW通过结束数据包和/或定时器是否超时来确定何时发送结束标记，辅助目标AN节点对目标用户面路径接收的下行数据排序处理。即通过EPS系统中end marker转发方法的增强，来解决因为互联网中仍然留有残存数据，用户面网关无法确定何时发送结束标记，不能保证下行数据的有序性的问题，从而增强了用户面网关功能，可以重用传统网元的大部分功能，不需要对现有的切换流程进行大范围修改，简单清晰，容易实施。
如图16所示，为本申请实施例中发送结束标记的方法的另一个实施例示意图，包括：
在本申请实施例中，此时AN节点不能够根据源用户面路径标识识别要切换路径的本地数据流，无法辅助AN节点对目标用户面路径上接收的下行数据包进行排序，因此，在建立目标用户面路径的时候，CP节点要向AN节点发送流切换指示消息，AN节点根据此指示流切换指示消息，检测事件：原空口数据承载上收到结束标记之前的数据包(本地网络发送的数据包和互联网发送的数据包)是否向UE成功发送完毕，若成功，则AN节点再根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理。如下所示：
1601、CP节点根据接收的用户面报告/切换请求/应用请求选择边缘网关。
CP节点收到AN节点发送的切换请求，或者收到MANO发送的应用请求，或者收到UP GW发送的用户面报告后，为本地数据流选择边缘网关，其中，边缘网关位于目标用户面路径上。例如：用户面报告的作用是用户面报告给CP节点，现在有UE的本地数据流，那么，CP节点就知道有本地数据流这个消息了。其中，源用户面路径为包含UE、AN、UP GW和Access GW的路径，目标用户面路径为包含UE、AN、Edge GW和Access GW的路径。其中，需要说明的是，在源用户面路径上UE和AN节点之间的第一无线数据承载(Data Radio Bearer，DRB)和目标用户面路径上的UE和AN节点之间的第二无线数据承载不相同。UE的路径切换之前，UE和AN节点之间为第一承载DRB、AN节点和UP GW之间为主要隧道(Primary Tunnel)；UE的路径切换之后，UE和AN节点之间为第二承载DRB、AN节点和Edge GW之间为次要隧道(Secondary Tunnel)；Edge GW和Access GW之间为外部隧道。
1602、CP节点将承载配置请求发送给AN节点，承载配置请求包括流切换指示消息。
CP节点向AN节点发送承载配置请求(Bearer Setup Request)；AN节点接收CP节点发送的承载配置请求；其中，该承载配置请求包括流切换指示信息、源用户面路径的ID、边缘网关的路径信息、第二业务流样板等信息。流切换指示消息用于指示AN节点在接收 到结束标记时确定AN节点在源用户面路径上接收到的下行数据包是否已成功发送给UE。即CP节点通知AN节点为目标用户面路径准备资源，承载配置请求携带边缘网关的路径信息，同时携带本地数据流重选路径指示。在实际应用中，第二业务流样板用来过滤本地网络发送的数据包，是非接入(Non-access stratum，NAS)层的信息，AN节点会将第二业务流样板传给UE，让UE准备上下文。
1603、AN节点将无线资源控制(Radio Resource Control，RRC)连接重配(RRC Connection Reconfiguration)消息发送给UE。
1604、UE将RRC连接重配完成(RRC Connection Reconfiguration Complete)消息发送给AN节点；
步骤1603和1604用于AN节点准备空口数据承载。
1605、AN节点将承载配置响应(Berarer Setup Response)发送给CP节点。
需要说明的是，AN节点在源用户面路径上接收的下行数据包中包括由本地网络发送的数据包和互联网数据包，本来UE的路径切换是将由本地网络发送的数据包切换到目标用户面路径上向UE传输。但是，AN节点有接收流切换指示消息，流切换指示消息用于指示AN节点在接收到结束标记时确定AN节点在源用户面路径上接收到的下行数据包是否已成功发送给UE。所以，AN节点可以空口数据承载准备完成后，将在源用户面路径上接收的下行数据包在第一DRB上传输给UE。
1606、UE将路径切换确认(Handover Confirmation)消息发送给CP节点。
即UE准备完成本地数据流的切换后，向控制面发送响应消息。
1607、CP节点向MANO发送本地数据流信息，获取Access GW的IP地址；
其中，本地数据流信息包含UE正在使用的本地IP地址，MANO根据本地配置信息，找到本地IP地址所在的本地网络的接入网关信息。
1608、CP节点将触发信息和源用户面路径的ID发送给UP GW。
其中，触发信息和源用户面路径的ID用于UP GW向AN节点发送结束标记。其中，CP节点还可以向UP GW发送第二业务流样板，这里的第二业务流样板是用来过滤由本地网络发送的数据包的。
示例性的，这里的触发信息可以是第一业务流样板和定时器参数中的至少一种，第一业务流样板是用来检测结束数据包的，用来表示在源用户面路径上最后传输的数据包。详细可以参考图14中的步骤1408中的描述，此处不再赘述。
1609、CP节点将会话更新请求发送给边缘网关。
应理解，这里的会话更新请求可以是承载配置请求(Bearer Setup Request)，用于CP节点通知边缘网关为本地数据流创建目标用户面路径。其中，会话更新请求携带的信息包括但不限于AN端的路径信息：具体为AN的IP地址和隧道ID；边缘网关的路径信息：边缘网关的IP地址和隧道ID；第二流过滤器模板(Traffic Filter Template，TFT)或者称呼为第二业务流样板，服务质量(Quality of Service，QoS)信息等。需要说明的是，这里的第二业务流样板是用来过滤由本地网络发送的数据包的。
1610、边缘网关将路径切换通知发送给Access GW。
应理解，这里的切换通知包括UE的IP地址和边缘网关的IP地址。需要说明的是，当触发信息为第一业务流样板，或者，第一业务流样板和定时器参数时，这里的切换通知或者路径切换请求还包括第一业务流样板，这里的第一业务流样板是用来确定结束数据包的。
1611、边缘网关将会话更新响应发送给CP节点。
应理解，这里的会话更新响应可以是承载配置响应(Berarer Setup Rsponse)；承载配置响应可以包括UE的目标用户面路径的标识，目标用户面路径包含边缘网关Edge GW；即CP节点收到边缘网关发送的确认消息。
1612、Access GW根据UE的IP地址和边缘网关的IP地址，向边缘网关发送UE的下行数据包。
1613、Access GW根据第一业务流样板，将数据包发送给UP GW。
1614、UP GW根据触发信息和源用户面路径的ID，在源用户面路径上将结束标记发送给接入网AN节点。
在本申请实施例中，步骤1612-1614和图14所示的步骤1411-1413类似，此处不再赘述。
1615、AN节点根据结束标记，对在目标用户面路径上接收到的下行数据包进行排序。
当AN节点在源用户面路径上接收到结束标记时，AN节点确定AN节点在源用户面路径上接收的下行数据包是否已成功发送给UE；若AN节点在源用户面路径上接收到的UE的下行数据包已成功发送给UE，则AN节点根据结束标记对AN节点在UE的目标用户面路径上接收的下行数据包进行排序。若AN节点在源用户面路径上接收到的下行数据包中存在至少一个数据包未成功发送给UE，则AN节点向UE发送至少一个数据包。
应理解，这里AN节点接收的下行数据包包括由本地网络发送的数据包和互联网数据包，由本地网络发送的数据包是由本地数据网络生成通过互联网发送的，互联网数据包是互联网发送的。需要说明的是，AN节点在接收到结束标记之前，对在目标用户面路径上收到的下行数据包进行缓冲，即AN节点根据流切换指示消息，要在收到结束标记和原空口数据承载上的数据包发送完毕后，才能激活对目标用户面路径过来的下行数据包的处理。
示例性的，AN节点在未接收结束标记时，已经在第一DRB上向UE发送在源用户面路径上接收的下行数据包，若AN节点在源用户面路径上接收的下行数据包有10个，那么，AN将这10个下行数据包在第一DRB上向UE发送，若成功发送给UE，会收到UE反馈的成功标识。
当AN节点接收到结束标记时，若AN节点已经收到10个UE反馈的成功标识，则证明UE在第一DRB上向UE发送的数据包都成功发送了，那么，AN节点就可以根据结束标记中的序列号对目标用户面路径上接收到的下行数据包进行排序处理了，并将排序后的下行数据包在第二DRB上向UE发送。
当AN节点接收到结束标记时，若AN节点只收到8个UE反馈的成功标识，则证明UE在第一DRB上向UE发送的数据包还没有全部成功发送给UE，若还没发送，则将剩余的2个下行数据包在第一DRB上向UE发送，并等待反馈的成功标识，若已发送，只是还未收到UE反馈的成功标识，则继续等待，直到全部成功发送给UE，那么，AN节点就可 以根据结束标记中的序列号对目标用户面路径上接收到的下行数据包进行排序处理了，并将排序后的下行数据包在第二DRB上向UE发送。
在本申请实施例中，UP GW通过结束数据包和/或定时器是否超时，确定UP GW何时发送结束标记，辅助目标AN节点对下行数据包进行排序。进一步的，在空口为在源用户面路径接收的下行数据包使用空口数据承载，在创建AN节点上的路径资源时，发送流切换指示消息，该流切换指示消息用于指示AN节点在源用户面路径上接收到结束标记时确定AN节点在源用户面路径上接收到的下行数据包是否已成功发送给UE；若成功发送给UE，那么，AN节点可以根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理了，即AN节点能够确定对在目标用户面路径上接收的下行数据包的激活时间，从而解决因为AN节点不能够识别出要切换路径的本地数据流，而导致的数据包的乱序问题。
如图17所示，为本申请实施例中发送结束标记的方法的另一个实施例示意图，包括：
在本申请实施例中，AN节点不用识别本地数据流，而是在准备路径资源的时候在核心网选择一个分流节点，把AN节点在源用户面路径上接收的下行数据包转发到该分流节点，让分流节点帮忙识别出来本地数据流后，再用转发路径发送到边缘网关，边缘网关再将本地数据流发送给AN节点，待收到结束标记后，根据结束标记对在目标用户面路径上接收的下行数据包进行排序处理。如下所示，以分流节点为UP GW进行说明：
1701、CP节点根据接收的用户面报告/切换请求/应用请求选择边缘网关。
CP节点收到AN节点发送的切换请求，或者收到MANO发送的应用请求，或者收到UP GW发送的用户面报告后，为本地数据流选择边缘网关，其中，边缘网关位于目标用户面路径上。例如：用户面报告的作用是用户面报告给CP节点，表示在源用户面路径上有UE的本地数据流，那么，CP节点就知道有本地数据流这个消息了。其中，源用户面路径为包含UE、AN节点、UP GW和Access GW的路径，目标用户面路径为包含UE、AN节点、Edge GW和Access GW的路径。其中，需要说明的是，在源用户面路径上UE和AN节点之间的第一无线数据承载(Data Radio Bearer，DRB)和目标用户面路径上的UE和AN节点之间的第二无线数据承载不相同。UE的路径切换之前，UE和AN节点之间为第一承载DRB、AN节点和UP GW之间为主要隧道(Primary Tunnel)；UE的路径切换之后，UE和AN节点之间为第二承载DRB、AN节点和Edge GW之间为次要隧道(Secondary Tunnel)；Edge GW和Access GW之间为外部隧道。
1702、CP节点将承载配置请求发送给AN节点。
CP节点向AN节点发送承载配置请求(Bearer Setup Request)；AN节点接收CP节点发送的承载配置请求；其中，该承载配置请求包括边缘网关的路径信息、第二业务流样板等信息。即CP节点通知AN节点为目标用户面路径准备资源，承载配置请求携带边缘网关的路径信息，第二业务流样板等信息，第二业务流样板是用来过滤由本地网络发送的数据包的。在实际应用中，第二业务流样板是非接入(Non-access stratum，NAS)层的信息，AN节点会将第二业务流样板传给UE，让UE准备上下文。
1703、AN节点将RRC连接重配消息发送给UE。
1704、UE将RRC连接重配完成消息发送给AN节点。
1705、AN节点将承载配置响应发送给CP节点。
1706、UE将路径切换确认消息发送给CP节点。
1707、CP节点向MANO发送本地数据流信息，获取Access GW的IP地址。
1708、CP节点将触发信息和源用户面路径的ID发送给UP GW。
1709、CP节点将会话更新请求发送给边缘网关。
1710、边缘网关将路径切换通知发送给Access GW。
1711、边缘网关将会话更新响应发送给CP节点。
在本申请实施例中，步骤1703-1711与图16所示的步骤1603-1611类似，此处不再赘述。
1712、CP节点将隧道更新消息发送给AN节点，隧道更新消息包括流切换指示消息。
CP节点向AN节点发送隧道更新消息，AN节点接收CP节点发送的隧道更新消息；其中，该隧道更新消息包括流切换指示消息和源用户面路径的ID，流切换消息信息用于指示AN节点向UP GW发送AN节点在源用户面路径上接收到的下行数据包。其中，在AN节点处收到的下行数据包包括由本地网络发送的数据包和互联网数据包。
1713、Access GW根据UE的IP地址和边缘网关的IP地址，向边缘网关发送UE的下行数据包。
1714、Access GW根据第一业务流样板，将数据包发送给UP GW。
1715、UP GW根据触发信息和源用户面路径的ID，在源用户面路径上将结束标记发送给接入网AN节点。
在本申请实施例中，需要说明的是，步骤1713-1715与图14所示的步骤1411-1413类似，此处不再赘述。
1716、AN节点根据流切换指示消息，将AN节点在源用户面路径上接收到的下行数据包发送给UP GW。
需要说明的是，当AN节点收到结束标记时，也将结束标记向UP GW转发，但是停止向UP GW转发AN节点收到的源用户面网关上的下行数据包。
示例性的，若AN节点接收的数据包中总共有15个，那么，AN节点将这15个数据包通过图14中所示的转发隧道转发给UP GW。需要说明的是，当AN节点在目标用户面路径上接收到UE的下行数据包时，缓冲这些数据包，先不对其进行排序处理。
1717、UP GW根据第二业务流样板和源用户面路径的ID，从在源用户面路径上接收AN节点发送的下行数据包中识别出本地网络发送的数据包。
需要说明的是，在本申请实施例中的步骤1708中，CP节点还会向UP GW发送第二业务流样板，该第二业务流样板用来识别由本地网络发送的数据包；那么，UP GW根据第二业务流样板和源用户面路径的ID，从在源用户面路径上接收AN节点发送的下行数据包中识别出本地网络发送的数据包。
即UP GW根据第二业务流样板和源用户面路径的ID，从上述的15个数据包中识别出10个由本地网络发送的数据包，再将剩余的5个互联网数据包通过UP GW和AN节点之间的转发隧道发送给AN节点，AN节点在第一DRB上向UE发送这5个互联网数据包。
需要说明的是，在4G里面源用户面路径的ID就是一个EPS Bearer ID，在5G里面现在是一个分组数据单元的会话ID(Protocol Data Unit Session Identifier，PDU Session ID)。在上下文中保存有路径ID和具体实现的接口的对应关系。示例性的，如下表3所示：
Figure PCTCN2017077123-appb-000004
表3
1718、UP GW节点将识别出的数据包转发给边缘网关。
示例性的，UP GW通过UP GW和边缘网关之间的转发隧道将这10个由本地网络发送的数据包转发给边缘网关。需要说明的是，当UP GW收到结束标记时，将结束标记转发给边缘网关。
1719、边缘网关将接收的识别出的数据包转发给AN节点。
示例性的，边缘网关再将这10个由本地网络发送的数据包通过次要隧道向AN节点转发。需要说明的是，当边缘网关收到UP GW转发的结束标记时，将结束标记发送给AN节点。
需要说明的是，步骤1713-1715的时序与步骤1716-1719的时序不做限定。
1720、AN节点根据结束标记，对在目标用户面路径上接收到的下行数据包进行排序。
应理解，AN节点现在收到的数据包可以包括：(1)从UP GW转发回来的互联网数据包；(2)从边缘网关转发回来的由本地网络发送的数据包；(3)在目标用户面路径上接收的下行数据包；(4)从边缘网关转发回来的结束标记。
AN节点在第一DRB上向UE发送互联网数据包(5个)，在第二DRB上向UE发送由本地网络发送的数据包(10个)，AN节点根据结束标记，对在目标用户面路径上接收到的下行数据包进行排序，再将排序后的下行数据包通过第二DRB向UE发送。
进一步的，还可以是，AN节点收到结束标记时，确定AN节点向UE发送的互联网数据包是否已成功发送，若成功发送，则AN节点根据结束标记，对在目标用户面路径上接收的下行数据包进行排序；若未成功发送互联网数据包，则AN节点可以继续向UE发送互联网数据包，当发送成功时，AN节点根据结束标记，对在目标用户面路径上接收的下行数据包进行排序。
需要说明的是，在本申请实施例中，有很多不同的实现方式，如可以选择其他核心网分流单元：Edge GW；可以建立不同的转发路径，如AN—UP GW—Edge GW，AN—UP  GW—AN，AN—Edge GW—UP GW，AN—Edge GW—Edge GW，AN—Edge GW—AN—UP GW，详细可参考图14所示的实施例，此处不再详细说明。
在本申请实施例中，UP GW通过结束数据包和/或定时器是否超时，确定UP GW何时发送结束标记，辅助AN节点对在目标用户面路径上接收的下行数据包进行排序处理。图13相比，不同之处在于选择核心网UP GW作为分流节点，即AN节点首先把从UP GW发送给AN节点的下行数据包转发回UP GW，直到收到结束标记(end maker)，恢复正常传输。UP GW检测到结束数据包后，在源用户面路径上发送结束标记，停止数据包在源用户面路径上的发送，直到收到AN节点转发回来的end marker结束标记。UP GW从转发数据包中检测出由本地网络发送的数据包，转发到Edge GW，UP GW收到AN节点转发回来的end marker后，发送给Edge GW。Edge GW收到结束标记后，转发回AN节点，激活对目标用户面路径上下行数据包的排序处理。
如图18所示，为本申请实施例中发送结束标记的方法的另一个实施例示意图，包括：
在本申请实施例中，AN节点可以暂时支持TFT，即AN节点可以根据TFT识别出从目标用户面路径上接收的下行数据包中的本地数据流，将本地数据流通过第二DRB向UE发送，AN节点再根据结束标记对目标用户面路径上接收的下行数据报包进行排序处理。如下所示：
1801、CP节点根据接收的用户面报告/切换请求/应用请求选择边缘网关。
CP节点收到AN节点发送的切换请求，或者收到MANO发送的应用请求，或者收到UP GW发送的用户面报告后，为本地数据流选择边缘网关，其中，边缘网关位于目标用户面路径上。例如：用户面报告的作用是用户面报告给CP节点，现在有UE的本地数据流，那么，CP节点就知道有本地数据流这个消息了。其中，源用户面路径为包含UE、AN节点、UP GW和Access GW的路径，目标用户面路径为包含UE、AN节点、Edge GW和Access GW的路径。其中，需要说明的是，在源用户面路径上UE和AN之间的第一无线数据承载(Data Radio Bearer，DRB)和目标用户面路径上的UE和AN节点之间的第二无线数据承载不相同。UE的路径切换之前，UE和AN节点之间为第一承载DRB、AN节点和UP GW之间为主要隧道(Primary Tunnel)；UE的路径切换之后，UE和AN节点之间为第二承载DRB、AN节点和Edge GW之间为次要隧道(Secondary Tunnel)；Edge GW和Access GW之间为外部隧道。
1802、CP节点将承载配置请求(Bearer Setup Request)发送给AN节点。
其中，该承载配置请求包括流切换指示信息、源用户面路径的ID、边缘网关的路径信息、第二业务流样板。流切换指示消息用于指示AN节点根据业务流样板和源用户面路径的ID将AN节点在源用户面路径上接收的本地网络发送的数据包通过目标DRB发送给UE，目标DRB为在UE的目标用户面路径上UE与AN节点之间的传输路径，即第二DRB，第二业务流样板是用来过滤由本地网络发送的数据包的。
CP节点通知AN节点为目标用户面路径准备资源，承载配置请求携带边缘网关的路径信息，源用户面路径的ID，同时携带本地数据流重选路径指示，第二业务流样板。
1803、AN节点将RRC连接重配消息发送给UE。
1804、UE将RRC连接重配完成消息发送给AN节点。
1805、AN节点将承载配置响应发送给CP节点。
1806、UE将路径切换确认消息发送给CP节点。
1807、CP节点向MANO发送本地数据流信息，获取Access GW的IP地址。
1808、CP节点将触发信息和源用户面路径的ID发送给UP GW。
1809、CP节点将会话更新请求发送给边缘网关。
1810、边缘网关将路径切换通知发送给Access GW。
1811、边缘网关将会话更新响应发送给CP节点。
在本申请实施例中，需要说明的是，步骤1803-1811与图16所示的步骤1603-1611类似，此处不再赘述。
1812、Access GW根据UE的IP地址和边缘网关的IP地址，向边缘网关发送UE的下行数据包。
1813、Access GW根据第一业务流样板，将数据包发送给UP GW。
1814、UP GW根据触发信息和源用户面路径的ID，在源用户面路径上将结束标记发送给接入网AN节点。
在本申请实施例中，需要说明的是，步骤1812-1814与图14所示的步骤1411-1413类似，此处不再赘述。
1815、AN节点根据业务流样板和源用户面路径的ID识别出本地网络发送的数据包。
AN节点根据第二业务流样板和源用户面路径的ID识别出由本地网络发送的数据包，该由本地网络发送的数据包是由本地数据网络通过互联网发送的。示例性的，因为业务流样板包括多个IP五元组信息，而每个数据包都包括IP五元组信息，如下表4所示，为第二业务流样板的示例说明：
Figure PCTCN2017077123-appb-000005
表4
若AN节点当前收到的数据包有15个，其中，根据上述表4所示，当这15个数据包中的IP五元组信息出现在表1的第二业务流样板中，那么，这些数据包属于由本地网络发送的数据包，IP五元组信息未出现在表4所示的第二业务流样板中，属于互联网数据包。假设，AN节点识别出的由本地网络发送的数据包有10个，互联网数据包有5个。
1816、AN节点根据流切换指示消息，将识别出的数据包通过目标DRB发送给UE。
AN节点根据流切换指示消息，将识别出的数据包通过目标DRB发送给UE；即AN节点将5个互联网数据包通过第一DRB向UE发送，将10个由本地网络发送的数据包通过第二DRB向UE发送。
需要说明的是，步骤1815和1816与1803-1814的时序不做限定。
1817、AN节点根据结束标记，对在目标用户面路径上接收到的下行数据包进行排序。
应理解，AN节点在接收结束标记之前，对在目标用户面路径上接收的下行数据包先进行缓冲。AN节点接收到结束标记后，根据结束标记中的序列号对在用户面路径上接收的下行数据包进行排序，进而将排序后的下行数据包通过第二DRB向UE发送，以及AN节点需要删除第二业务流样板。
在本申请实施例中，UP GW通过结束数据包和/或定时器是否超时，确定UP GW何时发送结束标记，辅助目标AN节点对下行数据包进行排序。进一步的，在空口为本地数据流单独使用空口数据承载，AN节点能够暂时支持TFT，识别本地数据流。在创建AN节点上的路径资源时，发送流切换指示消息，所述流切换指示消息用于指示所述AN节点根据所述业务流样板和所述源用户面路径的ID将所述AN节点在所述源用户面路径上接收的本地网络发送的数据包通过目标DRB发送给所述UE；那么，AN节点可以根据接收的结束标记对在目标用户面路径上接收的下行数据包进行排序处理了，即AN节点能够确定对在目标用户面路径上接收的下行数据包的激活时间，从而解决因为AN节点不能够识别出要切换路径的本地数据流，而导致的数据包的乱序问题。
上面对本申请实施例中的发送结束标记的方法进行了说明，下面对本申请实施例中CP节点、UP GW、Access GW和AN节点分别进行说明，如图19所示，为本申请实施例中控制面CP节点的一个实施例示意图，包括：
接收模块1901，用于接收会话更新响应，会话更新响应包括用户设备UE的源用户面路径的标识ID或UE的目标用户面路径的ID，源用户面路径包含用户面网关UP GW；
发送模块1902，用于根据会话更新响应，向UP GW发送触发信息和源用户面路径的ID，触发信息用于UP GW在源用户面路径上向接入网AN节点发送结束标记。
如图19所示的CP节点，可用于执行如上述图11-18任一所示的方法，其相同或相应的技术特征可援引在本实施例中。
可选的，在本申请的一些实施例中，触发信息包括第一业务流样板和定时器参数中的至少一种。
可选的，在本申请的一些实施例中，
发送模块1902，还用于向AN节点发送流切换指示消息，流切换指示消息包含源用户面路径的ID，流切换指示消息用于指示AN节点在接收到结束标记时确定AN节点在源用户面路径上接收到的下行数据包是否已成功发送给UE。
可选的，在本申请的一些实施例中，
发送模块1902，还用于向AN节点发送第一流切换指示消息，第一流切换指示消息包含源用户面路径的ID，第一流切换指示消息用于指示AN节点向UP GW发送AN节点在 源用户面路径上接收到的下行数据包；
发送模块1902，还用于向UP GW发送第二流切换指示消息，第二流切换指示消息包含源用户面路径的ID和第二业务流样板，第二流切换指示消息用于指示UP GW根据第二业务流样板和源用户面路径的ID，从UP GW在源用户面路径上接收的下行数据包中识别出本地网络发送的数据包，并将识别出的数据包发送给边缘网关，边缘网关位于目标用户面路径上。
可选的，在本申请的一些实施例中，
发送模块1902，还用于向AN节点发送流切换指示消息，流切换指示消息包含第二业务流样板和源用户面路径的ID，流切换指示消息用于指示AN节点根据第二业务流样板和源用户面路径的ID从AN节点在源用户面路径上接收的下行数据包中识别出本地网络发送的数据包，并将识别出的数据包通过目标DRB发送给UE，目标DRB为在目标用户面路径上UE与AN节点之间的传输路径。
如图20所示，为本申请实施例中用户面网关UP GW的一个实施例示意图，包括：
接收模块2001，用于接收控制面CP节点发送的触发信息/用户设备UE的源用户面路径的标识ID，UP GW位于源用户面路径上；
发送模块2002，用于根据触发信息和源用户面路径的ID，在源用户面路径上向接入网AN节点发送结束标记。
如图20所示的UP GW，可用于执行如上述图11-18任一所示的方法，其相同或相应的技术特征可援引在本实施例中。
可选的，在本申请的一些实施例中，触发信息包括第一业务流样板和定时器参数中的至少一种。
可选的，在本申请的一些实施例中，触发信息包括第一业务流样板；
发送模块2002，具体用于当UP GW接收的UE的下行数据包的IP五元组信息与第一业务流样板中的任一IP五元组信息相同时，发送模块根据源用户面路径的ID，在源用户面路径上向AN节点发送结束标记。
可选的，在本申请的一些实施例中，触发信息包括定时器参数，
发送模块2002，具体用于根据定时器参数设置定时器；启动定时器；当定时器超时时，发送模块根据源用户面路径的ID，在源用户面路径上向AN节点发送结束标记。
可选的，在本申请的一些实施例中，触发信息包括第一业务流样板和定时器参数；
发送模块2002，具体用于当UP GW接收的UE的下行数据包的IP五元组信息与第一业务流样板中的任一IP五元组信息相同时，发送模块启动定时器，定时器是根据定时器参数设置的；
若UP GW接收到结束数据包，且定时器未超时，则发送模块重启定时器，结束数据包的IP五元组信息与第一业务流样板中的任一IP五元组信息相同；
当定时器超时时，发送模块根据源用户面路径的ID，向AN节点发送结束标记。
可选的，在本申请的一些实施例中，在上述图20所示的基础上，如图21所示，为本申请实施例中UP GW的另一个实施例示意图。UP GW还包括：
接收模块2001，还用于接收CP节点发送的流切换指示消息，流切换指示消息包括源用户面路径的ID和第二业务流样板；
识别模块2003，还用于根据第二业务流样板和源用户面路径的ID，从在源用户面路径上接收AN节点发送的下行数据包中识别出本地网络发送的数据包；
发送模块2002，还用于向边缘网关发送识别出的数据包，边缘网关位于UE的目标用户面路径上。
如图22所示，为本申请实施例中接入网关Access GW的一个实施例示意图，包括：
接收模块2201，用于接收路径切换通知，路径切换通知包括业务流样板；
发送模块2202，用于根据业务流样板，向UP GW发送结束数据包。
如图22所示的接入网关，可用于执行如上述图11-18任一所示的方法，其相同或相应的技术特征可援引在本实施例中。
可选的，在本申请的一些实施例中，
接收模块2201，具体用于接收从边缘网关或本地管理单元发送的路径切换通知。
如图23所示，为本申请实施例中接入网AN节点的一个实施例示意图，包括：
接收模块2301，用于接收控制面CP节点发送的流切换指示消息，流切换指示消息包含用户设备UE的源用户面路径的标识ID，流切换指示消息用于指示AN节点在源用户面路径上接收到结束标记时确定AN节点在源用户面路径上接收到的下行数据包是否已成功发送给UE；
确定模块2302，用于当AN节点在源用户面路径上接收到结束标记时，确定模块确定AN节点在源用户面路径上接收的下行数据包是否已成功发送给UE；
发送模块2303，用于若AN节点在源用户面路径上接收到的UE的下行数据包已成功发送给UE，则发送模块根据结束标记对AN节点在UE的目标用户面路径上接收的下行数据包进行排序。
如图23所示的AN节点，可用于执行如上述图11-18任一所示的方法，其相同或相应的技术特征可援引在本实施例中。
可选的，在本申请的一些实施例中，
发送模块2203，还用于若AN节点在源用户面路径上接收到的下行数据包中存在至少一个数据包未成功发送给UE，则发送模块向UE发送至少一个数据包。
如图24所示，为本申请实施例中接入网AN节点的另一个实施例示意图，包括：
接收模块2401，用于从控制面CP节点接收流切换指示消息，流切换指示消息包含用户设备UE的源用户面路径的标识ID；
发送模块2402，用于根据流切换指示消息，发送AN节点在源用户面路径上接收的下行数据包，源用户面路径包括用户面网关UP GW。
如图24所示的AN节点，可用于执行如上述图11-18任一所示的方法，其相同或相应的技术特征可援引在本实施例中。
可选的，在本申请的一些实施例中，流切换消息信息用于指示AN节点向UP GW发送AN节点在源用户面路径上接收到的下行数据包；
发送模块2402，具体用于根据流切换指示消息，将AN节点在源用户面路径上接收到的下行数据包发送给UP GW。
可选的，在本申请的一些实施例中，流切换指示消息还包含业务流样板，流切换指示消息用于指示AN节点根据业务流样板和源用户面路径的ID将AN节点在源用户面路径上接收的本地网络发送的数据包通过目标DRB发送给UE，目标DRB为在UE的目标用户面路径上UE与AN节点之间的传输路径；
发送模块2402，具体用于根据业务流样板，识别出本地网络发送的数据包；根据流切换指示消息和源用户面路径的ID，将识别出的数据包通过目标DRB发送给UE。
如图25所示，为本申请实施例中控制面CP节点的另一个实施例示意图。
该CP节点可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上中央处理器(central processing units，CPU)2522(例如，一个或一个以上处理器)和存储器2532，一个或一个以上存储应用程序2542或数据2544的存储介质2530(例如一个或一个以上海量存储设备)。其中，存储器2532和存储介质2530可以是短暂存储或持久存储。存储在存储介质2530的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对CP节点中的一系列指令操作。更进一步地，中央处理器2522可以设置为与存储介质2530通信，在CP节点上执行存储介质2530中的一系列指令操作。
CP节点还可以包括一个或一个以上电源2526，一个或一个以上有线或无线网络接口2550，一个或一个以上输入输出接口2558，和/或，一个或一个以上操作系统2541，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM等等。
上述实施例中由CP节点所执行的步骤可以基于该图25所示的CP节点结构。
如图26所示，为本申请实施例中用户面网关UP GW的另一个实施例示意图。
该UP GW可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上中央处理器(central processing units，CPU)2622(例如，一个或一个以上处理器)和存储器2632，一个或一个以上存储应用程序2642或数据2644的存储介质2630(例如一个或一个以上海量存储设备)。其中，存储器2632和存储介质2630可以是短暂存储或持久存储。存储在存储介质2630的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对UP GW中的一系列指令操作。更进一步地，中央处理器2622可以设置为与存储介质2630通信，在UP GW上执行存储介质2630中的一系列指令操作。
UP GW还可以包括一个或一个以上电源2626，一个或一个以上有线或无线网络接口2650，一个或一个以上输入输出接口2658，和/或，一个或一个以上操作系统2641，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM等等。
上述实施例中由UP GW所执行的步骤可以基于该图26所示的UP GW结构。
如图27所示，为本申请实施例中接入网关Access GW的另一个实施例示意图。
该Access GW可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上中央处理器(central processing units，CPU)2722(例如，一个或一个以上处理器)和存储器2732，一个或一个以上存储应用程序2742或数据2744的存储介质2730(例如一个或一个以上海量存储设备)。其中，存储器2732和存储介质2730可以是短暂存储或持久存储。存 储在存储介质2730的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对Access GW中的一系列指令操作。更进一步地，中央处理器2722可以设置为与存储介质2730通信，在Access GW上执行存储介质2730中的一系列指令操作。
Access GW还可以包括一个或一个以上电源2727，一个或一个以上有线或无线网络接口2750，一个或一个以上输入输出接口2758，和/或，一个或一个以上操作系统2741，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM等等。
上述实施例中由Access GW所执行的步骤可以基于该图27所示的Access GW结构。
如图28所示，为本申请实施例中接入网AN节点的另一个实施例示意图。
该AN节点可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上中央处理器(central processing units，CPU)2822(例如，一个或一个以上处理器)和存储器2832，一个或一个以上存储应用程序2842或数据2844的存储介质2830(例如一个或一个以上海量存储设备)。其中，存储器2832和存储介质2830可以是短暂存储或持久存储。存储在存储介质2830的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对AN节点中的一系列指令操作。更进一步地，中央处理器2822可以设置为与存储介质2830通信，在AN节点上执行存储介质2830中的一系列指令操作。
AN节点还可以包括一个或一个以上电源2828，一个或一个以上有线或无线网络接口2850，一个或一个以上输入输出接口2858，和/或，一个或一个以上操作系统2841，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM等等。
上述实施例中由AN节点所执行的步骤可以基于该图28所示的AN节点结构。
可选的，在本申请的一些实施例中，提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如CP节点在上述图11-18任一所示的方法，其相同或相应的技术特征可援引在本实施例中。
可选的，在本申请的一些实施例中，提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如UP GW在上述图11-18任一所示的方法，其相同或相应的技术特征可援引在本实施例中。
可选的，在本申请的一些实施例中，提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如接入网关在上述图11-18任一所示的方法，其相同或相应的技术特征可援引在本实施例中。
可选的，在本申请的一些实施例中，提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如AN节点在上述图11-18任一所示的方法，其相同或相应的技术特征可援引在本实施例中。
可选的，在本申请的一些实施例中，提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如AN节点在上述图11-18任一所示的方法，其相同或相应的技术特征可援引在本实施例中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生 按照本发明实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。

Claims (36)

  1. 一种发送结束标记的方法，其特征在于，包括：
    控制面CP节点接收会话更新响应，所述会话更新响应包括用户设备UE的源用户面路径的标识ID或所述UE的目标用户面路径的ID，所述源用户面路径包含用户面网关UP GW；
    所述CP节点根据所述会话更新响应，向所述UP GW发送触发信息和所述源用户面路径的ID，所述触发信息用于所述UP GW在所述源用户面路径上向接入网AN节点发送结束标记。
  2. 根据权利要求1所述的方法，其特征在于，所述触发信息包括第一业务流样板和定时器参数中的至少一种。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述CP节点向所述AN节点发送流切换指示消息，所述流切换指示消息包含所述源用户面路径的ID，所述流切换指示消息用于指示所述AN节点在接收到所述结束标记时确定所述AN节点在所述源用户面路径上接收到的下行数据包是否已成功发送给所述UE。
  4. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述CP节点向所述AN节点发送第一流切换指示消息，所述第一流切换指示消息包含所述源用户面路径的ID，所述第一流切换指示消息用于指示所述AN节点向所述UP GW发送所述AN节点在所述源用户面路径上接收到的下行数据包；
    所述CP节点向所述UP GW发送第二流切换指示消息，所述第二流切换指示消息包含所述源用户面路径的ID和第二业务流样板，所述第二流切换指示消息用于指示所述UP GW根据所述第二业务流样板和所述源用户面路径的ID，从所述UP GW在所述源用户面路径上接收的下行数据包中识别出本地网络发送的数据包，并将所述识别出的数据包发送给边缘网关，所述边缘网关位于所述目标用户面路径上。
  5. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述CP节点向所述AN节点发送流切换指示消息，所述流切换指示消息包含第二业务流样板和所述源用户面路径的ID，所述流切换指示消息用于指示所述AN节点根据所述第二业务流样板和所述源用户面路径的ID从所述AN节点在所述源用户面路径上接收的下行数据包中识别出本地网络发送的数据包，并将所述识别出的数据包通过目标DRB发送给所述UE，所述目标DRB为在所述目标用户面路径上所述UE与所述AN节点之间的传输路径。
  6. 一种发送结束标记的方法，其特征在于，包括：
    用户面网关UP GW接收控制面CP节点发送的触发信息和用户设备UE的源用户面路径的标识ID，所述UP GW位于所述源用户面路径上；
    所述UP GW根据所述触发信息和所述源用户面路径的ID，在所述源用户面路径上向接入网AN节点发送结束标记。
  7. 根据权利要求6所述的方法，其特征在于，所述触发信息包括第一业务流样板和定时器参数中的至少一种。
  8. 根据权利要求7所述的方法，其特征在于，所述触发信息包括所述第一业务流样板；
    所述UP GW根据所述触发信息和所述源用户面路径的ID，在所述源用户面路径上向AN节点发送结束标记，包括：
    当所述UP GW接收的所述UE的下行数据包的IP五元组信息与所述第一业务流样板中的任一IP五元组信息相同时，所述UP GW根据所述源用户面路径的ID，在所述源用户面路径上向所述AN节点发送所述结束标记。
  9. 根据权利要求7所述的方法，其特征在于，所述触发信息包括所述定时器参数，所述UP GW根据所述触发信息和所述源用户面路径的ID，在所述源用户面路径上向AN节点发送结束标记，包括：
    所述UP GW根据所述定时器参数设置定时器；
    所述UP GW启动所述定时器；
    当所述定时器超时时，所述UP GW根据所述源用户面路径的ID，在所述源用户面路径上向所述AN节点发送所述结束标记。
  10. 根据权利要求7所述的方法，其特征在于，所述触发信息包括所述第一业务流样板和所述定时器参数；
    所述UP GW根据所述触发信息和所述源用户面路径的ID，在所述源用户面路径上向AN节点发送结束标记，包括：
    当所述UP GW接收的所述UE的下行数据包的IP五元组信息与所述第一业务流样板中的任一IP五元组信息相同时，所述UP GW启动定时器，所述定时器是根据所述定时器参数设置的；
    若所述UP GW接收到结束数据包，且所述定时器未超时，则所述UP GW重启所述定时器，所述结束数据包的IP五元组信息与所述第一业务流样板中的任一IP五元组信息相同；
    当所述定时器超时时，所述UP GW根据所述源用户面路径的ID，向所述AN节点发送所述结束标记。
  11. 根据权利要求6-10任一所述的方法，其特征在于，所述方法还包括：
    所述UP GW接收所述CP节点发送的流切换指示消息，所述流切换指示消息包括所述源用户面路径的ID和第二业务流样板；
    所述UP GW根据所述第二业务流样板和所述源用户面路径的ID，从在所述源用户面路径上接收所述AN节点发送的下行数据包中识别出本地网络发送的数据包；
    所述UP GW向边缘网关发送所述识别出的数据包，所述边缘网关位于所述UE的目标用户面路径上。
  12. 一种发送结束标记的方法，其特征在于，包括：
    接入网关Access GW接收路径切换通知，所述路径切换通知包括业务流样板；
    所述Access GW根据所述业务流样板，向UP GW发送结束数据包。
  13. 根据权利要求12所述的方法，其特征在于，所述Access GW接收路径切换通知，包括：
    所述Access GW接收从边缘网关或本地管理单元发送的所述路径切换通知。
  14. 一种发送结束标记的方法，其特征在于，包括：
    接入网AN节点接收控制面CP节点发送的流切换指示消息，所述流切换指示消息包含用户设备UE的源用户面路径的标识ID，所述流切换指示消息用于指示所述AN节点在所述源用户面路径上接收到结束标记时确定所述AN节点在所述源用户面路径上接收到的下行数据包是否已成功发送给所述UE；
    当所述AN节点在所述源用户面路径上接收到所述结束标记时，所述AN节点确定所述AN节点在所述源用户面路径上接收的下行数据包是否已成功发送给所述UE；
    若所述AN节点在所述源用户面路径上接收到的所述UE的下行数据包已成功发送给所述UE，则所述AN节点根据所述结束标记对所述AN节点在所述UE的目标用户面路径上接收的下行数据包进行排序。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    若所述AN节点在所述源用户面路径上接收到的下行数据包中存在至少一个数据包未成功发送给所述UE，则所述AN节点向所述UE发送所述至少一个数据包。
  16. 一种发送结束标记的方法，其特征在于，包括：
    接入网AN节点从控制面CP节点接收流切换指示消息，所述流切换指示消息包含用户设备UE的源用户面路径的标识ID；
    所述AN节点根据所述流切换指示消息，发送所述AN节点在所述源用户面路径上接收的下行数据包，所述源用户面路径包括用户面网关UP GW。
  17. 根据权利要求16所述的方法，其特征在于，所述流切换消息信息用于指示所述AN节点向所述UP GW发送所述AN节点在所述源用户面路径上接收到的下行数据包；
    所述AN节点根据所述流切换指示消息，发送所述AN节点在所述源用户面路径上接收的下行数据包，包括：
    所述AN节点根据所述流切换指示消息，将所述AN节点在所述源用户面路径上接收到的下行数据包发送给所述UP GW。
  18. 根据权利要求16所述的方法，其特征在于，所述流切换指示消息还包含业务流样板，所述流切换指示消息用于指示所述AN节点根据所述业务流样板和所述源用户面路径的ID将所述AN节点在所述源用户面路径上接收的本地网络发送的数据包通过目标DRB发送给所述UE，所述目标DRB为在所述UE的目标用户面路径上所述UE与所述AN节点之间的传输路径；
    所述AN节点根据所述流切换指示消息，发送所述AN节点在UE的源用户面路径上接收的下行数据包，包括：
    所述AN节点根据所述业务流样板，识别出本地网络发送的数据包；
    所述AN节点根据所述流切换指示消息和所述源用户面路径的ID，将所述识别出的数据包通过所述目标DRB发送给所述UE。
  19. 一种控制面CP节点，其特征在于，包括：
    接收模块，用于接收会话更新响应，所述会话更新响应包括用户设备UE的源用户面 路径的标识ID或所述UE的目标用户面路径的ID，所述源用户面路径包含用户面网关UP GW；
    发送模块，用于根据所述会话更新响应，向所述UP GW发送触发信息和所述源用户面路径的ID，所述触发信息用于所述UP GW在所述源用户面路径上向接入网AN节点发送结束标记。
  20. 根据权利要求19所述的CP网元，其特征在于，所述触发信息包括第一业务流样板和定时器参数中的至少一种。
  21. 根据权利要求19或20任一所述的CP节点，其特征在于，
    所述发送模块，还用于向所述AN节点发送流切换指示消息，所述流切换指示消息包含所述源用户面路径的ID，所述流切换指示消息用于指示所述AN节点在接收到所述结束标记时确定所述AN节点在所述源用户面路径上接收到的下行数据包是否已成功发送给所述UE。
  22. 根据权利要求19或20任一所述的CP节点，其特征在于，
    所述发送模块，还用于向所述AN节点发送第一流切换指示消息，所述第一流切换指示消息包含所述源用户面路径的ID，所述第一流切换指示消息用于指示所述AN节点向所述UP GW发送所述AN节点在所述源用户面路径上接收到的下行数据包；
    所述发送模块，还用于向所述UP GW发送第二流切换指示消息，所述第二流切换指示消息包含所述源用户面路径的ID和第二业务流样板，所述第二流切换指示消息用于指示所述UP GW根据所述第二业务流样板和所述源用户面路径的ID，从所述UP GW在所述源用户面路径上接收的下行数据包中识别出本地网络发送的数据包，并将所述识别出的数据包发送给边缘网关，所述边缘网关位于所述目标用户面路径上。
  23. 根据权利要求19或20任一所述的CP节点，其特征在于，
    所述发送模块，还用于向所述AN节点发送流切换指示消息，所述流切换指示消息包含第二业务流样板和所述源用户面路径的ID，所述流切换指示消息用于指示所述AN节点根据所述第二业务流样板和所述源用户面路径的ID从所述AN节点在所述源用户面路径上接收的下行数据包中识别出本地网络发送的数据包，并将所述识别出的数据包通过目标DRB发送给所述UE，所述目标DRB为在所述目标用户面路径上所述UE与所述AN节点之间的传输路径。
  24. 一种用户面网关UP GW，其特征在于，包括：
    接收模块，用于接收控制面CP节点发送的触发信息和用户设备UE的源用户面路径的标识ID，所述UP GW位于所述源用户面路径上；
    发送模块，用于根据所述触发信息和所述源用户面路径的ID，在所述源用户面路径上向接入网AN节点发送结束标记。
  25. 根据权利要求24所述的UP GW，其特征在于，所述触发信息包括第一业务流样板和定时器参数中的至少一种。
  26. 根据权利要求25所述的UP GW，其特征在于，所述触发信息包括所述第一业务流样板；
    所述发送模块，具体用于当所述UP GW接收的所述UE的下行数据包的IP五元组信息与所述第一业务流样板中的任一IP五元组信息相同时，所述发送模块根据所述源用户面路径的ID，在所述源用户面路径上向所述AN节点发送所述结束标记。
  27. 根据权利要求25所述的UP GW，其特征在于，所述触发信息包括所述定时器参数，
    所述发送模块，具体用于根据所述定时器参数设置定时器；启动所述定时器；当所述定时器超时时，所述发送模块根据所述源用户面路径的ID，在所述源用户面路径上向所述AN节点发送所述结束标记。
  28. 根据权利要求25所述的UP GW，其特征在于，所述触发信息包括所述第一业务流样板和所述定时器参数；
    所述发送模块，具体用于当所述UP GW接收的所述UE的下行数据包的IP五元组信息与所述第一业务流样板中的任一IP五元组信息相同时，所述发送模块启动定时器，所述定时器是根据所述定时器参数设置的；
    若所述UP GW接收到结束数据包，且所述定时器未超时，则所述发送模块重启所述定时器，所述结束数据包的IP五元组信息与所述第一业务流样板中的任一IP五元组信息相同；
    当所述定时器超时时，所述发送模块根据所述源用户面路径的ID，向所述AN节点发送所述结束标记。
  29. 根据权利要求24-28任一所述的UP GW，其特征在于，所述UP GW还包括：
    所述接收模块，还用于接收所述CP节点发送的流切换指示消息，所述流切换指示消息包括所述源用户面路径的ID和第二业务流样板；
    识别模块，还用于根据所述第二业务流样板和所述源用户面路径的ID，从在所述源用户面路径上接收所述AN节点发送的下行数据包中识别出本地网络发送的数据包；
    所述发送模块，还用于向边缘网关发送所述识别出的数据包，所述边缘网关位于所述UE的目标用户面路径上。
  30. 一种接入网关Access GW，其特征在于，包括：
    接收模块，用于接收路径切换通知，所述路径切换通知包括业务流样板；
    发送模块，用于根据所述业务流样板，向UP GW发送结束数据包。
  31. 根据权利要求30所述的Access GW，其特征在于，
    所述接收模块，具体用于接收从边缘网关或本地管理单元发送的所述路径切换通知。
  32. 一种接入网AN节点，其特征在于，包括：
    接收模块，用于接收控制面CP节点发送的流切换指示消息，所述流切换指示消息包含用户设备UE的源用户面路径的标识ID，所述流切换指示消息用于指示所述AN节点在所述源用户面路径上接收到结束标记时确定所述AN节点在所述源用户面路径上接收到的下行数据包是否已成功发送给所述UE；
    确定模块，用于当所述AN节点在所述源用户面路径上接收到所述结束标记时，所述确定模块确定所述AN节点在所述源用户面路径上接收的下行数据包是否已成功发送给所 述UE；
    发送模块，用于若所述AN节点在所述源用户面路径上接收到的所述UE的下行数据包已成功发送给所述UE，则所述发送模块根据所述结束标记对所述AN节点在所述UE的目标用户面路径上接收的下行数据包进行排序。
  33. 根据权利要求32所述的AN节点，其特征在于，
    所述发送模块，还用于若所述AN节点在所述源用户面路径上接收到的下行数据包中存在至少一个数据包未成功发送给所述UE，则所述发送模块向所述UE发送所述至少一个数据包。
  34. 一种接入网AN节点，其特征在于，包括：
    接收模块，用于从控制面CP节点接收流切换指示消息，所述流切换指示消息包含用户设备UE的源用户面路径的标识ID；
    发送模块，用于根据所述流切换指示消息，发送所述AN节点在所述源用户面路径上接收的下行数据包，所述源用户面路径包括用户面网关UP GW。
  35. 根据权利要求34所述的AN节点，其特征在于，所述流切换消息信息用于指示所述AN节点向所述UP GW发送所述AN节点在所述源用户面路径上接收到的下行数据包；
    所述发送模块，具体用于根据所述流切换指示消息，将所述AN节点在所述源用户面路径上接收到的下行数据包发送给所述UP GW。
  36. 根据权利要求34所述的AN节点，其特征在于，所述流切换指示消息还包含业务流样板，所述流切换指示消息用于指示所述AN节点根据所述业务流样板和所述源用户面路径的ID将所述AN节点在所述源用户面路径上接收的本地网络发送的数据包通过目标DRB发送给所述UE，所述目标DRB为在所述UE的目标用户面路径上所述UE与所述AN节点之间的传输路径；
    所述发送模块，具体用于根据所述业务流样板，识别出本地网络发送的数据包；根据所述流切换指示消息和所述源用户面路径的ID，将所述识别出的数据包通过所述目标DRB发送给所述UE。
PCT/CN2017/077123 2017-03-17 2017-03-17 一种发送结束标记的方法 WO2018165982A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP17900529.3A EP3589019B1 (en) 2017-03-17 2017-03-17 Methods and devices for sending end marker
PCT/CN2017/077123 WO2018165982A1 (zh) 2017-03-17 2017-03-17 一种发送结束标记的方法
CN201780084718.5A CN110226344B (zh) 2017-03-17 2017-03-17 一种发送结束标记的方法及相关设备
US16/573,433 US11140602B2 (en) 2017-03-17 2019-09-17 End marker sending method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/077123 WO2018165982A1 (zh) 2017-03-17 2017-03-17 一种发送结束标记的方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/573,433 Continuation US11140602B2 (en) 2017-03-17 2019-09-17 End marker sending method

Publications (1)

Publication Number Publication Date
WO2018165982A1 true WO2018165982A1 (zh) 2018-09-20

Family

ID=63522785

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077123 WO2018165982A1 (zh) 2017-03-17 2017-03-17 一种发送结束标记的方法

Country Status (4)

Country Link
US (1) US11140602B2 (zh)
EP (1) EP3589019B1 (zh)
CN (1) CN110226344B (zh)
WO (1) WO2018165982A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111132195A (zh) * 2019-12-19 2020-05-08 京信通信技术(广州)有限公司 数据倒换方法、装置、计算机设备和存储介质
CN112105065A (zh) * 2019-06-17 2020-12-18 华为技术有限公司 通信方法和通信装置
CN112449384A (zh) * 2019-08-31 2021-03-05 华为技术有限公司 数据处理方法、装置和系统

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108882334B (zh) * 2017-08-11 2019-11-05 华为技术有限公司 一种数据传输方法、核心网用户面设备和源基站
KR102479660B1 (ko) * 2018-03-12 2022-12-20 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 Ue 정책의 업데이트 방법 및 장치, 컴퓨터 저장매체
WO2020200287A1 (en) * 2019-04-02 2020-10-08 Huawei Technologies Co., Ltd. Method, apparatus and systems for supporting packet delivery
CN111163017B (zh) * 2019-12-30 2023-10-24 京信网络系统股份有限公司 数据传输方法、装置、基站设备和计算机可读存储介质
CN113051198A (zh) * 2021-03-08 2021-06-29 惠州Tcl移动通信有限公司 一种移动终端模块处理方法、装置、移动终端及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572928A (zh) * 2008-04-30 2009-11-04 华为技术有限公司 一种切换方法及通讯系统以及相关设备
US20100111041A1 (en) * 2008-10-30 2010-05-06 Samsung Electronics Co. Ltd. Communication system and data transmission method thereof
CN102045802A (zh) * 2010-12-22 2011-05-04 华为技术有限公司 Sgw改变的切换过程中的数据发送方法、pgw及基站

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7350070B2 (en) * 2004-04-12 2008-03-25 Hewlett-Packard Development Company, L.P. Method and system for cryptographically secure hashed end marker of streaming data
CN101932010A (zh) * 2009-06-25 2010-12-29 中兴通讯股份有限公司 用于确定上行反传结束时间的方法和装置
US8902852B2 (en) * 2011-05-19 2014-12-02 Telefonaktiebolaget L M Ericsson (Publ) Inter-rat handover control using empty GRE packets
US8861475B2 (en) * 2011-05-19 2014-10-14 Telefonaktiebolaget L M Ericsson (Publ) Inter-RAT handover control using sequence numbers
US8706118B2 (en) * 2011-09-07 2014-04-22 Telefonaktiebolaget L M Ericsson (Publ) 3G LTE intra-EUTRAN handover control using empty GRE packets
JP2014199980A (ja) * 2013-03-29 2014-10-23 株式会社Ｎｔｔドコモ Ｐｄｎゲートウェイ装置及び移動通信方法
MX362900B (es) * 2014-06-12 2019-02-25 Huawei Tech Co Ltd Dispositivo de control de transferencia de portadora y método de control.
US9538563B2 (en) * 2014-10-13 2017-01-03 At&T Intellectual Property I, L.P. System and methods for managing a user data path
EP3355618B1 (en) * 2015-10-29 2020-02-26 Huawei Technologies Co., Ltd. Method and device for determining bearer by mobile edge computing
US10524173B2 (en) * 2016-02-24 2019-12-31 Cisco Technology, Inc. System and method to facilitate sharing bearer information in a network environment
WO2018030982A1 (en) * 2016-08-08 2018-02-15 Nokia Technologies Oy End marker handling for mobility between 5g and lte
EP3826362B1 (en) * 2016-11-04 2022-03-02 Huawei Technologies Co., Ltd. Method for sending end marker, device, and system
US10716045B2 (en) * 2017-01-24 2020-07-14 Telefonaktiebolaget Lm Ericsson (Publ) Lossless handover for mobility with location identifier separation protocol in 3rd generation partnership project networks
CN108933763B (zh) * 2017-05-25 2020-01-03 华为技术有限公司 一种数据报文发送方法、网络设备、控制设备及网络系统
CN108882334B (zh) * 2017-08-11 2019-11-05 华为技术有限公司 一种数据传输方法、核心网用户面设备和源基站
US10419982B1 (en) * 2018-03-14 2019-09-17 Cisco Technology, Inc. Methods and apparatus for providing end marker functionality in mobile networks having SRv6-configured mobile user planes

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572928A (zh) * 2008-04-30 2009-11-04 华为技术有限公司 一种切换方法及通讯系统以及相关设备
US20100111041A1 (en) * 2008-10-30 2010-05-06 Samsung Electronics Co. Ltd. Communication system and data transmission method thereof
CN102045802A (zh) * 2010-12-22 2011-05-04 华为技术有限公司 Sgw改变的切换过程中的数据发送方法、pgw及基站

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Technical Specification Group Services and System Aspects; Architecture Enhancements for Control and User Plane Separation of EPC Nodes", 3GPPTS 23.214 V14.2.0 (2017-03, 13 March 2017 (2017-03-13), pages 1 - 78, XP055540855 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112105065A (zh) * 2019-06-17 2020-12-18 华为技术有限公司 通信方法和通信装置
CN112449384A (zh) * 2019-08-31 2021-03-05 华为技术有限公司 数据处理方法、装置和系统
CN112449384B (zh) * 2019-08-31 2022-05-24 华为技术有限公司 数据处理方法、装置和系统
CN111132195A (zh) * 2019-12-19 2020-05-08 京信通信技术(广州)有限公司 数据倒换方法、装置、计算机设备和存储介质
CN111132195B (zh) * 2019-12-19 2022-05-03 京信网络系统股份有限公司 数据倒换方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
US20200015138A1 (en) 2020-01-09
EP3589019A4 (en) 2020-01-08
EP3589019A1 (en) 2020-01-01
US11140602B2 (en) 2021-10-05
CN110226344B (zh) 2020-11-17
EP3589019B1 (en) 2021-05-12
CN110226344A (zh) 2019-09-10

Similar Documents

Publication Publication Date Title
WO2018165982A1 (zh) 一种发送结束标记的方法
JP7395539B2 (ja) デュアルアクティブ接続を使用したハンドオーバ
JP7284789B2 (ja) シームレスのハンドオーバーをサポートする方法及びｅｎｂ装置
CN112740824B (zh) 恢复请求随后释放和重定向
JP5993524B2 (ja) 補助ベアラを確立するノードおよび方法
EP3461071B1 (en) Communication control method, and related network element
US9913174B2 (en) Method, device and system for implementing optimized inter-rat handover
EP3100516B1 (en) Efficient session management method and apparatus guaranteeing terminal mobility
WO2011109938A1 (zh) 无线接入网元信息上报方法、设备和系统
EP3261386A1 (en) Service processing method, related device and system
WO2018035741A1 (zh) 策略控制方法、网元、系统及存储介质
WO2015188357A1 (zh) 一种控制承载切换的设备和控制方法
US9860792B2 (en) Network device for supporting gateway change in mobile communication system, and method for operating same
KR20150135035A (ko) 무선 랜으로 미디어 전송 시 사용자 체감 서비스 품질을 높이는 방법 및 장치
US20180255481A1 (en) Service flow transmission method and apparatus
EP3379780B1 (en) Methods and apparatuses for transmitting control message in software defined network-based mobile communication system
WO2012130018A1 (zh) 一种ip分流连接移动性支持的方法及系统
KR102047821B1 (ko) 다운링크 데이터 통지 메시지 전송 방법 및 장치
US20230403623A1 (en) Managing sidelink information, configuration, and communication
TW202220489A (zh) 多重連接通訊中之重新配置程序
WO2012103773A1 (zh) 中继系统的过载控制方法及系统
WO2016107405A1 (zh) 业务流传输路径优化方法、装置及mme
WO2018127182A1 (zh) 一种系统间信息交互方法，无线通信系统和用户设备
WO2014056380A1 (zh) 一种异系统载波聚合的方法、装置及系统
CN116074904A (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: 17900529

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017900529

Country of ref document: EP

Effective date: 20190926