WO2017054178A1 - 保持业务连续性的方法、控制面网关和移动管理网元 - Google Patents

保持业务连续性的方法、控制面网关和移动管理网元 Download PDF

Info

Publication number
WO2017054178A1
WO2017054178A1 PCT/CN2015/091242 CN2015091242W WO2017054178A1 WO 2017054178 A1 WO2017054178 A1 WO 2017054178A1 CN 2015091242 W CN2015091242 W CN 2015091242W WO 2017054178 A1 WO2017054178 A1 WO 2017054178A1
Authority
WO
WIPO (PCT)
Prior art keywords
plane gateway
request
user plane
user
network element
Prior art date
Application number
PCT/CN2015/091242
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
Priority to EP15905090.5A priority Critical patent/EP3346795B1/en
Priority to EP19178009.7A priority patent/EP3624545B1/en
Priority to JP2018516449A priority patent/JP6699847B2/ja
Priority to PCT/CN2015/091242 priority patent/WO2017054178A1/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202010178324.XA priority patent/CN111510986B/zh
Priority to CN201580028759.3A priority patent/CN107079507B/zh
Priority to RU2018115851A priority patent/RU2686596C1/ru
Priority to BR112018006580-3A priority patent/BR112018006580B1/pt
Priority to KR1020187011731A priority patent/KR102018635B1/ko
Publication of WO2017054178A1 publication Critical patent/WO2017054178A1/zh
Priority to US15/940,348 priority patent/US10638527B2/en
Priority to US16/431,261 priority patent/US10595350B2/en
Priority to US16/730,487 priority patent/US10701744B2/en
Priority to US16/731,701 priority patent/US10827543B2/en
Priority to US17/069,957 priority patent/US11432351B2/en

Links

Images

Classifications

    • 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
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • 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/02—Terminal devices
    • 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/08—Access point devices

Definitions

  • the present invention relates to the field of communications and, more particularly, to a method of maintaining traffic continuity, a control plane gateway, and a mobility management network element.
  • the Distributed Gateway (DGW) architecture is an enhanced network architecture proposed on the existing Evolved Packet System (EPS) network architecture based on the idea that the network control plane function is separated from the user plane function.
  • the DGW architecture includes a Control Plane Gateway (C-GW) and a User Plane Gateway (U-GW).
  • C-GW is a centralized control plane gateway. It can exist in two forms: (1) Integrating the Serving Gateway (S-GW) and the Packet Data Network Gateway (IP) in the existing 3GPP EPS network.
  • P-GW a single network element that controls the surface function; (2) implements the control plane function of the existing S-GW (Control Plane S-GW) and the control plane function of the existing P-GW (Control Plane P-GW) Two independent network elements.
  • the C-GW is used to specifically handle control plane signaling in the 3GPP EPS network, including mobility management, session management, address management, path management, and accounting management.
  • the C-GW implements control and management of user plane data processing through interaction with the U-GW.
  • U-GW is a distributed user plane gateway, which corresponds to the two existing forms of C-GW.
  • U-GW also has two forms of existence: (1) Integrating the service gateway (Serving Gateway, S) in the existing 3GPP EPS network.
  • -GW a single network element with a User Data function of the Packet Data Network Gateway (P-GW); (2) Implementing the User Plane S-GW of the existing S-GW and the existing P - Two independent network elements of the User Plane P-GW of the GW.
  • the U-GW is used to specifically process user plane data in the 3GPP EPS network, including routing forwarding, packet inspection, packet statistics, and quality of service execution.
  • the U-GW implements processing of user plane data under the control and management of the C-GW. Considering the characteristics that the U-GW can be distributed, the U-GW can also be called a Distributed Gateway (D-GW).
  • D-GW Distributed Gateway
  • the service continuity is implemented by the anchor function of the P-GW, that is, the UE in the connected state performing the user plane service is in the process of moving, and the user plane data is always passed through.
  • the former P-GW implements interaction with an external data network. Since the P-GW does not change during the mobile process, the IP address of the user plane is kept unchanged, thereby ensuring the continuity of the user plane service.
  • the U-GW (or D-GW) in the DGW architecture can perform on-demand distributed deployment according to service requirements, enabling local access of users, thereby shortening Round-Trip Time (RTT) of user plane data and improving user experience.
  • RTT Round-Trip Time
  • the location of the U-GW can be moved down to the metropolitan area network or even the base station controller closer to the user.
  • the service range of the S-GW/P-GW is much smaller than that of the centralized deployment in the EPS network, thereby increasing the service U-GW change during UE mobility. Probability.
  • the embodiment of the present invention provides a method for maintaining service continuity, a control plane gateway, and a mobility management network element, which can establish a forwarding U-GW and a source U-GW for the UE, and forward the U-GW and the target base station of the UE.
  • the data forwarding tunnel between the two can ensure the continuity of the service during the UE mobile process and improve the user experience.
  • a method for maintaining service continuity comprising: a control plane gateway receiving current location information of a user equipment sent by a mobility management network element for a user equipment; the control plane gateway according to a current location of the user equipment The information is: selecting, by the user equipment, at least one forwarding user plane gateway; the control plane gateway is between the source user plane gateway serving the user equipment and the forwarding user plane gateway, and the forwarding user plane gateway and the target base station of the user equipment A data forwarding tunnel is established for the user equipment, where the data forwarding tunnel is used to transmit uplink user plane data and/or downlink user plane data of the user equipment during the mobile device.
  • the at least one forwarding user plane gateway is a first user plane gateway, where the control plane gateway is a service control plane gateway after the user equipment moves to the current location area, and The control plane gateway is the same as the service control plane gateway before the user equipment moves to the current location area, where the mobility management network element is the service mobility management network element after the user equipment moves to the current location area; the control plane gateway is serving the user.
  • a data forwarding tunnel is established between the source user plane gateway of the device and the forwarding user plane gateway, and between the forwarding user plane gateway and the target base station of the user equipment, and the specific implementation is:
  • the control plane gateway sends a second request to the first user plane gateway, where the second request is used to request the first user plane gateway to establish a data forwarding tunnel between the first user plane gateway and the target base station, and a data forwarding tunnel between the first user plane gateway and the source user plane gateway, the second request carrying routing information of the target base station, and routing information of the source user plane gateway;
  • the control plane gateway sends a third request to the source user plane gateway, where the third request is used to request the source user plane gateway to establish a data forwarding tunnel between the source user plane gateway and the first user plane gateway, where The third request carries the routing information of the forwarding user plane gateway.
  • the at least one forwarding user plane gateway includes a second user plane gateway and a third user plane gateway, where the control plane gateway moves after the user equipment moves to the current location area.
  • Serving a control plane gateway, and the control plane gateway is the same as the service control plane gateway before the user equipment moves to the current location area
  • the mobility management network element is a service mobility management network element after the user equipment moves to the current location area;
  • the surface gateway establishes a data forwarding tunnel between the source user plane gateway serving the user equipment and the forwarding user plane gateway, and the destination user base station and the target base station of the user equipment, and the specific implementation is:
  • the control plane gateway receives the first request sent by the mobility management network element, where the first request carries routing information of the target base station of the user equipment;
  • the control plane gateway sends a second request to the second user plane gateway, where the second request is used to request the second user plane gateway to establish a data forwarding tunnel between the second user plane gateway and the target base station, and a data forwarding tunnel between the second user plane gateway and the third user plane gateway, where the second request carries routing information of the target base station and routing information of the third user plane gateway;
  • the control plane gateway sends a third request to the third user plane gateway, where the third request is used to request the third user plane gateway to establish data forwarding between the third user plane gateway and the second user plane gateway.
  • a tunnel, and a data forwarding tunnel between the third user plane gateway and the source user plane gateway, the third request carrying routing information of the second user plane gateway, and routing information of the source user plane gateway;
  • the control plane gateway sends a fourth request to the source user plane gateway, where the fourth request is used to request the source user plane gateway to establish a data forwarding tunnel between the source user plane gateway and the third user plane gateway, where The fourth request carries routing information of the third user plane gateway.
  • the at least one forwarding user network Off, the first user plane gateway, the control plane gateway is a service control plane gateway after the user equipment moves to the current location area, and the control plane gateway is different from the service control plane gateway before the user equipment moves to the current location area
  • the mobility management network element is a service mobility management network element after the user equipment moves to the current location area
  • the method further includes: the control plane gateway further receiving routing information of the source user plane gateway sent by the mobility management network element;
  • the control plane gateway establishes a data forwarding tunnel between the source user plane gateway serving the user equipment and the forwarding user plane gateway, and the forwarding user plane gateway and the target base station of the user equipment, which is implemented as :
  • the control plane gateway receives the first request sent by the mobility management network element, where the first request carries routing information of the target base station of the user equipment;
  • the control plane gateway sends a second request to the first user plane gateway, where the second request is used to request the first user plane gateway to establish a data forwarding tunnel between the first user plane gateway and the target base station, and a data forwarding tunnel between the first user plane gateway and the source user plane gateway, the second request carrying routing information of the target base station, and routing information of the source user plane gateway.
  • the at least one forwarding user plane gateway includes a second user plane gateway and a third user plane gateway, where the control plane gateway moves to the service control plane gateway after the user equipment moves to the current location area, and the control plane gateway is different from the user
  • the device moves to the service control plane gateway before the current location area, and the mobility management network element moves the service mobility management network element after the user equipment moves to the current location area;
  • the method further includes: the control plane gateway further receiving routing information of the source user plane gateway sent by the mobility management network element;
  • the control plane gateway establishes a data forwarding tunnel between the source user plane gateway serving the user equipment and the forwarding user plane gateway, and the forwarding user plane gateway and the target base station of the user equipment, which is implemented as :
  • the control plane gateway receives the first request sent by the mobility management network element, where the first request carries routing information of the target base station of the user equipment;
  • the control plane gateway sends a second request to the second user plane gateway, where the second request is used to request the second user plane gateway to establish a data forwarding tunnel between the second user plane gateway and the target base station, and Data forwarding tunnel between the second user plane gateway and the third user plane gateway
  • the second request carries the routing information of the target base station and the routing information of the third user plane gateway
  • the control plane gateway sends a third request to the third user plane gateway, where the third request is used to request the third user plane gateway to establish data forwarding between the third user plane gateway and the second user plane gateway.
  • a tunnel, and a data forwarding tunnel between the third user plane gateway and the source user plane gateway, the third request carrying routing information of the second user plane gateway, and routing information of the source user plane gateway.
  • the method further The method includes: the control plane gateway sends a setup session request to the target user plane gateway, where the setup session request is used to create a bearer context required for user plane data transmission for the user equipment on the target user plane gateway, and each established Each of the bearer contexts includes routing information of the target user plane gateway, where the target user plane gateway is a service user plane gateway corresponding to the current location area of the user equipment.
  • the method further includes: the control plane gateway sending, by the mobility management network element, the route of the target user plane gateway to the target base station information.
  • the method further includes: the control plane gateway passes the mobility management network element Sending routing information of the first user plane gateway to the target base station.
  • the specific implementation is: the first user plane gateway or the control plane gateway A service user plane gateway selected by the user equipment according to current location information of the user equipment.
  • the method further includes: the control plane gateway passes the mobility management network element Sending routing information of the second user plane gateway to the target base station.
  • a method for maintaining service continuity includes: a target mobility management network element receives a forwarding relocation request sent by a source mobility management network element of a service user equipment, where the forwarding relocation request carries the user equipment Current location information; the target mobility management network element selects a target control plane gateway of the user equipment according to the current location information of the user equipment; the target mobility tube The network element sends the current location information of the user equipment to the target control plane gateway, so that the target control plane gateway determines the forwarding user plane gateway of the user equipment according to the current location information of the user equipment; the target mobility management network element The target control plane gateway sends a data forwarding tunnel establishment request, and the data forwarding tunnel establishment request is used to request the target control plane gateway between the forwarding user plane gateway and the source user plane gateway serving the user equipment, and the forwarding user plane gateway A data forwarding tunnel is established for the user equipment with a target base station serving the user equipment.
  • the target control plane gateway is different from the serving control plane gateway before the user equipment moves to the current location area
  • the method further includes: the target mobility management network element is configured to The source mobility management network element sends a change notification message, where the change notification message is used to indicate that the service control plane gateway of the user equipment is changed to the target control plane gateway.
  • the method further includes: the target mobility management network element receiving the acknowledgement message sent by the source mobility management network element according to the change notification message
  • the confirmation message carries routing information of the source user plane gateway of the user equipment.
  • a method for maintaining service continuity includes: a control plane gateway receiving current location information of the user equipment sent by a mobility management network element; the control plane gateway is configured according to current location information of the user equipment The user equipment selects a target user plane gateway; the control plane gateway sends a request message to the mobility management network element, where the request message is used to request the mobility management network element to release the first bearer context and instruct the user equipment to send the second bearer context.
  • a setup request where the first bearer context is a bearer context of the user equipment established on the source user plane gateway of the user equipment, and the second bearer context is that the user equipment is in the target user according to the first bearer context
  • the specific implementation is as follows: the delete bearer request message carries a reactivation request indication, where the reactivation request indication is used to indicate that the mobility management network element requests the user equipment to delete the After the context is carried, the re-establishment request of the bearer context is initiated.
  • a control plane gateway configured to include: a receiving unit, configured to receive current location information of the user equipment sent by the mobility management network element; and a selecting unit, configured to use current location information of the user equipment Selecting at least one forwarding user plane gateway for the user equipment; a tunnel establishing unit, configured between the source user plane gateway serving the user equipment and the forwarding user plane gateway, and the forwarding user plane gateway and the target base station of the user equipment Between, built for the user device
  • the data forwarding tunnel is configured to transmit uplink user plane data and/or downlink user plane data of the user equipment during the mobile device.
  • the at least one forwarding user plane gateway is a first user plane gateway
  • the control plane gateway is a service control plane gateway after the user equipment moves to the current location area
  • the control plane gateway and the user equipment The service control plane gateway before moving to the current location area is the same
  • the mobility management network element is the service mobility management network element after the user equipment moves to the current location area
  • the receiving unit is further configured to receive a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the user equipment;
  • the control plane gateway further includes a sending unit, where the tunnel establishing unit is specifically configured to:
  • the at least one forwarding user plane gateway includes a second user plane gateway and a third user plane gateway, where the control plane gateway moves the user equipment to the service control plane gateway after the current location area, and the control The service gateway is the same as the service control plane gateway before the user equipment moves to the current location area, and the mobility management network element is the service mobility management network element after the user equipment moves to the current location area;
  • the receiving unit is further configured to receive a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the user equipment;
  • the control plane gateway further includes a sending unit, where the tunnel establishing unit is specifically configured to:
  • the second request is used to request the second user plane gateway to establish a data forwarding tunnel between the second user plane gateway and the target base station, and data between the second user plane gateway and the third user plane gateway.
  • Forwarding the tunnel, the second request carries routing information of the target base station, and routing information of the third user plane gateway, where the third request is used to request the third user plane gateway to be established.
  • the third request carries the second user
  • the routing information of the gateway and the routing information of the source user plane gateway is used to request the source user plane gateway to establish a data forwarding tunnel between the source user plane gateway and the third user plane gateway, where the The fourth request carries the routing information of the third user plane gateway.
  • the at least one forwarding user plane gateway is a first user plane gateway
  • the control plane gateway is a service control plane gateway after the user equipment moves to the current location area, and the control plane gateway is different from the user.
  • the device moves to the service control plane gateway before the current location area
  • the mobility management network element moves the service mobility management network element after the user equipment moves to the current location area
  • the receiving unit is further configured to receive routing information of the source user plane gateway sent by the mobility management network element;
  • the receiving unit is further configured to receive a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the user equipment;
  • the control plane gateway further includes a sending unit, where the tunnel establishing unit is specifically configured to:
  • the at least one forwarding user plane gateway includes a second user plane gateway and a third user plane gateway, where the control plane gateway moves the user equipment to the service control plane gateway after the current location area, and the control The face gateway is different from the service control plane gateway before the user equipment moves to the current location area, and the mobility management network element is a service mobility management network element after the user equipment moves to the current location area;
  • the receiving unit is further configured to receive routing information of the source user plane gateway sent by the mobility management network element;
  • the receiving unit is further configured to receive a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the user equipment;
  • the control plane gateway further includes a sending unit, where the tunnel establishing unit is specifically configured to:
  • the sending unit Sending, by the sending unit, a second request to the second user plane gateway, and passing the sending unit Sending a third request to the third user plane gateway, where the second request is used to request the second user plane gateway to establish a data forwarding tunnel between the second user plane gateway and the target base station, and the second user a data forwarding tunnel between the gateway and the third user plane gateway, the second request carries routing information of the target base station, and routing information of the third user plane gateway, where the third request is used to request the third user plane
  • the gateway establishes a data forwarding tunnel between the third user plane gateway and the second user plane gateway, and a data forwarding tunnel between the third user plane gateway and the source user plane gateway, where the third request carries the second The routing information of the user plane gateway and the routing information of the source user plane gateway.
  • the tunnel establishing unit is further configured to send a setup session request to the target user plane gateway, where the setup session request is used to create a user plane data transmission for the user equipment on the target user plane gateway.
  • the bearer context, each of the established bearer contexts includes routing information of the target user plane gateway, where the target user plane gateway is a service user plane gateway corresponding to the current location area of the user equipment.
  • the tunnel establishing unit is further configured to send routing information of the target user plane gateway to the target base station by using the mobility management network element.
  • the tunnel establishing unit is further configured to send routing information of the first user plane gateway to the target base station by using the mobility management network element.
  • the first user plane gateway is also a service user plane gateway selected by the control plane gateway for the user equipment according to the current location information of the user equipment.
  • the tunnel establishing unit is further configured to send routing information of the second user plane gateway to the target base station by using the mobility management network element.
  • a mobility management network element includes: a receiving unit, configured to receive a forwarding relocation request sent by a source mobility management network element of a serving user equipment, where the forwarding relocation request carries the user a current location information of the device, a selection unit, configured to select a target control plane gateway of the user equipment according to current location information of the user equipment, and a sending unit, configured to send current location information of the user equipment to the target control plane gateway, so that Determining, by the target control plane gateway, the forwarding user plane gateway of the user equipment according to the current location information of the user equipment; the sending unit is further configured to send a data forwarding tunnel establishment request to the target control plane gateway, where the data forwarding tunnel establishment request is used for And requesting the target control plane gateway to establish a data forwarding tunnel between the forwarding user plane gateway and the source user plane gateway serving the user equipment, and the forwarding user plane gateway and the target base station serving the user equipment.
  • the target control plane gateway is different from the service control plane gateway before the user equipment moves to the current location area
  • the sending unit is further configured to send a change notification message to the source mobility management network element, the change notification The message is used to indicate that the service control plane gateway of the user equipment is changed to the target control plane gateway.
  • the receiving unit is further configured to receive an acknowledgment message sent by the source mobility management network element according to the change notification message, where the acknowledgment message carries routing information of the source user plane gateway of the user equipment.
  • a control plane gateway includes: the control plane gateway receives current location information of the user equipment sent by the mobility management network element; the control plane gateway is configured according to the current location information of the user equipment.
  • the user equipment selects a target user plane gateway; the control plane gateway sends a request message to the mobility management network element, where the request message is used to request the mobility management network element to release the first bearer context and instruct the user equipment to send the second bearer context.
  • Establishing a request where the first bearer context is a bearer context of the user equipment that is established on the source user plane gateway of the user equipment, and the second bearer context is that the user equipment is in the target user plane according to the first bearer context.
  • the bearer context rebuilt on the gateway.
  • the delete bearer request message carries a reactivation request indication
  • the reactivation request indication is used to instruct the mobile management network element to request the user equipment to initiate the reestablishment request of the bearer context after deleting the bearer context.
  • a control plane gateway including: a memory, a processor, a receiver, and a transmitter, where
  • the memory is used to store a program and provide data and instructions to the processor
  • the processor is configured to execute a program stored in the memory, and is specifically configured to perform the following operations:
  • the tunnel is used to transmit uplink user plane data and/or downlink user plane data of the user equipment during the movement of the user equipment.
  • the at least one forwarding user plane gateway is a first user plane gateway
  • the control plane gateway is a service control plane gateway after the user equipment moves to the current location area
  • the control plane gateway is the same as the service control plane gateway before the user equipment moves to the current location area
  • the mobility management network element is a service mobility management network element after the user equipment moves to the current location area
  • the processor is further configured to receive, by the receiver, a first request sent by the mobility management network element, where the first request carries routing information of the target base station;
  • the processor is specifically used to:
  • the at least one forwarding user plane gateway includes a first user plane gateway and a second user plane gateway, where the control plane gateway moves the user equipment to a service control plane gateway after the current location area, and the The control plane gateway is the same as the service control plane gateway before the user equipment moves to the current location area, and the mobility management network element is the service mobility management network element after the user equipment moves to the current location area;
  • the processor is further configured to receive, by the receiver, a first request sent by the mobility management network element, where the first request carries routing information of the target base station;
  • the processor is configured to establish a data forwarding tunnel for the user equipment between the source user plane gateway and the forwarding user plane gateway, and the forwarding user plane gateway and the target base station by using the transmitter. Specifically used for:
  • the second request is used to request the second user plane gateway to establish a data forwarding tunnel between the second user plane gateway and the target base station, and data between the second user plane gateway and the third user plane gateway.
  • the second request carries the routing information of the target base station, and the routing information of the third user plane gateway, where the third request is used to request the third user plane gateway to establish the a data forwarding tunnel between the three user plane gateway and the second user plane gateway, and a data forwarding tunnel between the third user plane gateway and the source user plane gateway, the third request carrying the second user plane gateway
  • the routing information, and the routing information of the source user plane gateway, the fourth request is used to request the source user plane gateway to establish a data forwarding tunnel between the source user plane gateway and the third user plane gateway, where the fourth request carries Routing information of the third user plane gateway.
  • the at least one forwarding user plane gateway is a first user plane gateway
  • the control plane gateway is a service control plane gateway after the user equipment moves to the current location area
  • the control plane gateway is different from the The user equipment moves to the service control plane gateway before the current location area
  • the mobility management network element moves the service mobility management network element after the user equipment moves to the current location area
  • the processor is further configured to receive, by the receiver, routing information of the source user plane gateway sent by the mobility management network element;
  • the processor is further configured to receive, by the receiver, a first request sent by the mobility management network element, where the first request carries routing information of the target base station;
  • the processor is configured to establish a data forwarding tunnel for the user equipment between the source user plane gateway and the forwarding user plane gateway, and the forwarding user plane gateway and the target base station by using the transmitter. Specifically used for:
  • the at least one forwarding user plane gateway includes a first user plane gateway and a second user plane gateway, where the control plane gateway moves the user equipment to a service control plane gateway after the current location area, and the The control plane gateway is different from the service control plane gateway before the user equipment moves to the current location area, and the mobility management network element is a service mobility management network element after the user equipment moves to the current location area;
  • the processor is further configured to receive, by the receiver, routing information of the source user plane gateway sent by the mobility management network element;
  • the processor is further configured to receive, by the receiver, a first request sent by the mobility management network element, where the first request carries routing information of the target base station;
  • the processor is specifically configured to:
  • the processor is further configured to send a setup session request to the target user plane gateway by using the transmitter, where the setup session request is used to create a user for the user equipment on the target user plane gateway.
  • the bearer context required for the data transmission, each of the established bearer contexts includes routing information of the target user plane gateway, where the target user plane gateway is a service user plane gateway corresponding to the current location area of the user equipment.
  • the processor is further configured to send routing information of the target user plane gateway to the target base station by using the mobility management network element.
  • the processor is further configured to send routing information of the first user plane gateway to the target base station by using the mobility management network element.
  • the first user plane gateway is a service user plane gateway selected by the control plane gateway for the user equipment according to the current location information of the user equipment.
  • the processor is further configured to send routing information of the second user plane gateway to the target base station by using the mobility management network element.
  • a mobile management network element including: a memory, a processor, a receiver, and a transmitter, where
  • the memory is used to store a program and provide data and instructions to the processor
  • the processor is configured to execute a program stored in the memory, and is specifically configured to perform the following operations:
  • the target control plane gateway is different from the service control plane gateway before the user equipment moves to the current location area.
  • the processor is further configured to send, by using the transmitter, a change notification message to the source mobility management network element, where the change notification message is used to indicate that the serving control plane gateway of the user equipment is changed to the target control plane gateway.
  • the processor is further configured to receive, by the receiver, an acknowledgement message sent by the source mobility management network element according to the change notification message, where the acknowledgement message carries routing information of a source user plane gateway of the user equipment. .
  • a control plane gateway including: a memory, a processor, a receiver, and a transmitter, where
  • the memory is used to store a program and provide data and instructions to the processor
  • the processor is configured to execute a program stored in the memory, and is specifically configured to perform the following operations:
  • the bearer context is a bearer context of the user equipment that is established on the source user plane gateway of the user equipment
  • the second bearer context is a bearer context that is reconstructed by the user equipment on the target user plane gateway according to the first bearer context.
  • the request message is a delete bearer request message, where the delete bearer request message carries a reactivation request indication, where the reactivation request indication is used to indicate, by the mobility management network element, that the user equipment is in the first bearer After the context is deleted, the establishment request of the second bearer context is initiated.
  • Method for maintaining business continuity, control plane gateway and mobile management network by selecting a forwarding U-GW for the UE at the control plane gateway, establishing a forwarding data between the U-GW and the source U-GW, and forwarding a data forwarding tunnel between the U-GW and the target base station of the UE, thereby enabling Ensure the continuity of the service during the UE's mobile process and improve the user's service experience.
  • FIG. 1 is a schematic diagram of two network architectures of a distributed gateway according to an embodiment of the present invention.
  • FIG. 2 is a flow chart of a method for maintaining business continuity in an embodiment of the present invention.
  • FIG. 3 is an interaction flowchart of maintaining business continuity according to an embodiment of the present invention.
  • FIG. 5 is still another flow chart of interaction for maintaining business continuity according to an embodiment of the present invention.
  • FIG. 6 is another flow chart of interaction for maintaining business continuity according to an embodiment of the present invention.
  • FIG. 7 is still another flow chart of interaction for maintaining business continuity according to an embodiment of the present invention.
  • FIG. 8 is still another flow chart of interaction for maintaining business continuity according to an embodiment of the present invention.
  • FIG. 9 is a flow chart of another method for maintaining business continuity in an embodiment of the present invention.
  • FIG. 10 is a flow chart of still another method for maintaining business continuity according to an embodiment of the present invention.
  • FIG. 11 is still another flow chart of interaction for maintaining business continuity according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a control plane gateway according to an embodiment of the present invention.
  • FIG. 13 is another schematic structural diagram of a control plane gateway according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a mobility management network element according to an embodiment of the present invention.
  • FIG. 15 is a schematic diagram of still another structure of a control plane gateway according to an embodiment of the present invention.
  • FIG. 16 is a schematic structural diagram of still another control plane gateway according to an embodiment of the present invention.
  • FIG. 17 is another schematic structural diagram of a mobility management network element according to an embodiment of the present invention.
  • FIG. 18 is a schematic diagram of still another structure of a control plane gateway according to an embodiment of the present invention.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • 5G networks 5G networks.
  • the user equipment which may also be referred to as a mobile terminal, may be any one of the following, and the user equipment may be static, mobile, portable, pocket-sized, Handheld, built-in or on-board.
  • User equipment may include, but is not limited to, a station, a mobile station, a subscriber unit, a personal computer, a laptop computer, a tablet computer, Netbook, Cellular Phone, Handheld, Cordless Phone, Personal Digital Assistant (PDA), Data Card, USB Plug-in, Mobile WiFi Hotspot Wearable devices such as MiFi Devices, smart watches/smart glasses, wireless modems (Modem), wireless routers, wireless local loop (WLL) stations, etc.
  • the user equipment may be distributed throughout the wireless network and communicate with one or more core networks through the wireless access network.
  • the base station may be a base station (BTS, Base Transceiver Station) in GSM or CDMA, or a base station (NodeB) in WCDMA, or an evolved base station (eNB or e-NodeB, evolutional Node B) in LTE.
  • BTS Base Transceiver Station
  • NodeB base station
  • eNB evolved base station
  • e-NodeB evolutional Node B
  • the Control Plane Gateway can exist in two forms: (1) Integrating the Serving Gateway (S-GW) and the Packet Data Network Gateway in the existing 3GPP EPS network. , P-GW) a single network element that controls the surface function; (2) implements the control plane function of the existing S-GW (Control Plane S-GW) and the control plane function of the existing P-GW (Control Plane P-GW)
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • P-GW a single network element that controls the surface function
  • the two independent network elements are not limited by the present invention.
  • U-GW User Plane Gateway
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • D-GW Distributed Gateway
  • U-GWs in the same service area can form a U-GW resource pool.
  • the U-GWs in the same U-GW resource pool can communicate directly.
  • Each U-GW resource pool can be configured.
  • a default U-GW is used to implement communication with U-GWs in other U-GW resource pools.
  • FIG. 1 is a schematic diagram of two network architectures of a DGW according to an embodiment of the present invention. Above the dotted line is the DGW architecture 1, and below the dotted line is the DGW architecture 2.
  • C-GW integrates all control plane functions of existing EPS network architecture S-GW and P-GW
  • U-GW integrates all user plane functions of existing EPS network architecture S-GW and P-GW.
  • a new interface such as an S18 interface, is introduced between the C-GW and the U-GW to implement communication between the C-GW and the U-GW.
  • other network elements and interfaces can reuse the existing EPS network architecture.
  • the new S18 interface can reuse the interface protocol between the S-GW and the P-GW, for example, the GTP protocol, or other interface protocols or newly defined protocols, which are not limited in this embodiment of the present invention.
  • the S-GW and the P-GW are separately split into two independent functional network elements (S-GW-C and S-GW-U, P-GW).
  • -C and P-GW-U), S-GW-C and P-GW-C may be collectively referred to as C-GW, and S-GW-U and P-GW-U may be collectively referred to as U-GW.
  • the existing interfaces between the S-GW and the P-GW are also split into a control plane interface and a user plane interface, such as the S5-C and S5-U interfaces in the DGW architecture 2.
  • other network elements and interfaces can reuse the existing EPS network architecture.
  • the new S18 and S19 interfaces can reuse the interface protocol between the S-GW and the P-GW, such as the GTP protocol, or other interface protocols or newly defined protocols, which are not limited in this embodiment of the present invention.
  • the method and the device in the embodiment of the present invention may be applied to the communication system shown in the DGW architecture 1 or the DGW architecture 2 in FIG. 1 .
  • the embodiment of the present invention is shown by the DGW architecture 1 .
  • the C-GW in the embodiment of the present invention is equivalent to the unified network element of the S-GW-C and the P-GW-C in the DGW architecture 2;
  • the GW is equivalent to the unified network element of the S-GW-U and the P-GW-U in the DGW architecture 2.
  • FIG. 2 is a flow chart of a method for maintaining business continuity in an embodiment of the present invention.
  • the method of Figure 2 is performed by a control plane gateway.
  • the method includes:
  • the C-GW receives current location information of the UE that is sent by the mobility management network element.
  • the connected state UE moves in the location of the user plane data transmission, and the moved location area exceeds the service range of the source base station. After the source base station senses that the UE moves out of its service range, it decides to initiate the connection state user plane data service switching. Process.
  • the source base station is a serving base station before the UE moves to the current location area.
  • the idle state UE removes the currently registered location area when the uplink user plane data transmission needs to be sent, such as the currently registered Tracking Area (TA), and the UE initiates a location update procedure, such as tracking domain update (Tracking Area). Update, TAU) process.
  • TA Tracking Area
  • TAU tracking domain update
  • the UE When the idle state UE needs to transmit the uplink user plane data transmission, the UE removes the service area of the current serving base station but does not remove the currently registered location area, such as the currently registered Tracking Area (TA), and the UE initiates a service request. (Service Request) process.
  • TA Tracking Area
  • the mobility management network element may send a service switching notification to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element may send the service switching notification by using an existing message, such as a Create Session Request message or a Modify Bearer Request message or modify an access bearer request (Modify).
  • An access bearers request message or the like; or the mobile management network element may send the service switching notification by using a newly created message, and specifically use which message to send the service switching notification, which is not limited by the present invention.
  • the mobility management network element may send a request message to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element can use existing messages to send Sending the request message, for example, a Create Session Request message or a Modify Bearer Request message or a Modify Access Bearers Request message; or the mobile management network element can use the newly created message.
  • the request message is sent, and the specific message is used to send the request message, which is not limited by the present invention.
  • the mobility management network element may send a request message to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element may send the request message by using an existing message, such as a Create Session Request message or a Modify Bearer Request message or modify an access bearer request (Modify Access).
  • the bearer request message may be sent by the mobile management network element by using a newly created message, and which message is used to send the request message, which is not limited by the present invention.
  • the current location information of the UE includes the Tracking Area Identity (TAI) corresponding to the current location area of the UE and/or the serving base station information corresponding to the current location area of the UE.
  • TAI Tracking Area Identity
  • the UE moves to the TAI corresponding to the current location area, that is, the target TAI of the UE; the UE moves to the serving base station information corresponding to the current location area, that is, the target base station information of the UE.
  • the target base station information may be a target base station identity (ID), a target cell identity (Cell Identity, CI), and the like.
  • the current location area of the UE which is also referred to as the target location area of the UE, that is, the location area where the UE moves out of the service range of the source serving base station, similarly, the current location information of the UE, also referred to as the UE target. location information.
  • the C-GW selects at least one forwarding U-GW for the UE according to current location information of the UE.
  • the current location area of the UE exceeds the service range of the current serving U-GW of the UE, and the C-GW needs to select a suitable forwarding U-GW for the UE according to the current location area of the UE.
  • the C-GW establishes a data forwarding tunnel between the source U-GW serving the UE and the forwarding U-GW, and the forwarding U-GW and the target base station serving the UE.
  • the data forwarding tunnel is configured to transmit uplink user plane data and/or downlink user plane data of the UE during the mobile process of the UE.
  • the mobile process of the UE includes the processes that occur in the foregoing three application scenarios, specifically: the service switching process in the application scenario (1), the location update process in the application scenario (2), and the application scenario (3).
  • Business request process is the process that occur in the foregoing three application scenarios, specifically: the service switching process in the application scenario (1), the location update process in the application scenario (2), and the application scenario (3).
  • the target base station of the UE refers to a base station that provides access services for the UE after the UE moves to the current location area.
  • the data forwarding tunnel is implemented by establishing a user plane bearer context between the source U-GW serving the UE and the forwarding U-GW, and forwarding the U-GW and the target base station of the UE, the user
  • the bearer bearer context includes the routing information required to forward the user plane data.
  • the user plane bearer context established on the source U-GW includes the routing information of the forwarding U-GW and the routing information of the source base station serving the UE.
  • the user plane bearer context established on the forwarding U-GW includes routing information of the source U-GW and routing information of the target base station, and the user plane bearer context established on the target base station includes routing information of the forwarding U-GW.
  • the routing information may include an address (typically an Internet Protocol (IP) address) and tunnel port information (typically, if a GPRS Tunneling Protocol (GTP) protocol is used, the tunnel port information is GTP tunnel port identifier (TEID)).
  • IP Internet Protocol
  • GTP GPRS Tunneling Protocol
  • the forwarding U-GW refers to at least one forwarding U-GW mentioned in step 202.
  • the data forwarding tunnel established by the C-GW between the source U-GW serving the UE and the forwarding U-GW, and between the forwarding U-GW and the target base station of the UE, is the data forwarding tunnel established for the UE.
  • the established data forwarding tunnel path is: source U-GW-U-GW1-target base station; when the at least one forwarding U- The GW has two U-GWs, namely U-GW1 and U-GW2, wherein U-GW1 can communicate with the source U-GW, and U-GW2 can communicate with the target base station, and the established data forwarding tunnel path is: source U- GW-U-GW1 - U-GW2 - target base station; when the at least one forwarding U-GW has 3 or 3 U-GWs or more, and includes U-GW1 capable of communicating with the source U-GW, and capable of The U-GW2 of the target base station communication establishes a data forwarding tunnel path: source U-GW-U-GW1-...-U-GW2-target base station.
  • the data forwarding tunnel of the portion indicated by U-GW1 - ... - U-GW2 is a data forwarding tunnel between the at least
  • the C-GW determines an appropriate forwarding U-GW for the UE according to the current location information after the UE moves, and establishes a forwarding between the U-GW and the source U-GW, and forwards the U-GW and the UE.
  • the data forwarding tunnel between the target base stations can ensure the continuity of the service during the UE mobile process and improve the service experience of the user.
  • the at least one forwarding U-GW has only one, is a first U-GW, and the C-GW is a serving C-GW after the UE moves to a current location area, and the C-GW The GW is the same as the serving C-GW before the UE moves to the current location area, and the mobility management network element is the serving mobility management network element after the UE moves to the current location area.
  • step 203 is specifically implemented as:
  • the C-GW sends a second request to the first U-GW, where the second request is used to request the first U-GW to establish a data forwarding tunnel between the first U-GW and the target base station, and a data forwarding tunnel between the first U-GW and the source U-GW, the second request carrying routing information of the target base station, and routing information of the source U-GW;
  • the C-GW sends a third request to the source U-GW, where the third request is used to request the source U-GW to establish a data forwarding tunnel between the source U-GW and the first U-GW, where The third request carries routing information of the first U-GW.
  • the C-GW is the same as the serving C-GW before the UE moves to the current location area, that is, the serving C-GW does not change during the UE mobile process. It should be understood that the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • the C-GW also receives the second response sent by the first U-GW according to the second request, and the third response sent by the source U-GW according to the third request.
  • the second response is used to confirm that the first U-GW allows to establish a data forwarding tunnel between the first U-GW and the target base station, and data forwarding between the first U-GW and the source U-GW.
  • a tunnel optionally, the second response may carry routing information of the first U-GW, such as an IP address and TEID information;
  • the third response is used to confirm that the source U-GW allows the source U-GW to be established and the A data forwarding tunnel between the first U-GWs.
  • the C-GW may send a first response of the first request to the mobility management network element.
  • an existing message may be used, such as creating an Indirect Data Forwarding Tunnel Request, or using a newly defined message.
  • the present invention does not limit this; further, the first response, the second response, or the third response in this implementation may use an existing message, such as The Create Indirect Data Forwarding Tunnel Response may be used, and the newly defined message may also be used.
  • the physical manifestation of the tunnel is a bearer context
  • the bearer context includes routing information of the opposite end of the tunnel.
  • the control plane gateway needs to separately send the request to the two user plane gateways to establish the bearer context respectively, and then the bearer context includes the routing information of the peer end, so that a tunnel is established between the two user plane gateways.
  • the at least one forwarding U-GW includes a second U-GW and a third U-GW, where the C-GW is a serving C-GW after the UE moves to a current location area, and The C-GW is the same as the serving C-GW before the UE moves to the current location area, the mobility management network element is a serving mobility management network element after the UE moves to the current location area, and the mobility management network element and the UE The service mobility management network elements before moving to the current location area are the same or different.
  • step 203 is specifically implemented as:
  • the C-GW sends a second request to the second U-GW, where the second request is used to request the second U-GW to establish a data forwarding tunnel between the second U-GW and the target base station, and a data forwarding tunnel between the second U-GW and the third U-GW, the second request carrying routing information of the target base station, and routing information of the third U-GW;
  • the C-GW sends a third request to the third U-GW, where the third request is used to request the third U-GW to establish data forwarding between the third U-GW and the second U-GW. a tunnel, and a data forwarding tunnel between the third U-GW and the source U-GW, the third request carrying routing information of the second U-GW, and routing information of the source U-GW;
  • the C-GW sends a fourth request to the source U-GW, where the fourth request is used to request the source U-GW to establish a data forwarding tunnel between the source U-GW and the third U-GW, where The fourth request carries routing information of the third U-GW.
  • the C-GW is the same as the serving C-GW before the UE moves to the current location area, that is, the serving C-GW does not change during the UE mobile process. It should be understood that the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • the C-GW also receives a second response sent by the second U-GW according to the second request, The third response sent by the three U-GW according to the third request, and the fourth response sent by the source U-GW according to the fourth request.
  • the second response is used to confirm that the second U-GW allows to establish a data forwarding tunnel between the second U-GW and the target base station, and data between the second U-GW and the third U-GW. Forwarding the tunnel, optionally, the second response may carry routing information of the second U-GW, such as an IP address and TEID information; the third response is used to confirm the third U-GW and the second U-GW And a data forwarding tunnel between the third U-GW and the source U-GW.
  • the third response may carry routing information of the third U-GW, such as an IP address. And the TEID information; the fourth response is used to confirm that the source U-GW allows to establish a data forwarding tunnel between the source U-GW and the third U-GW.
  • the C-GW may send the first response of the first request to the mobility management network element.
  • first request, the second request, the third request, or the fourth request in this implementation may use an existing message, such as Create Indirect Data Forwarding Tunnel Request, or may be used.
  • the newly defined message is not limited by the present invention; further, the first response, the second response, the third response, or the fourth response in the implementation may use an existing message, such as creating an indirect data forwarding tunnel response ( A newly defined message may also be used, which is not limited by the present invention.
  • the at least one forwarding U-GW determined by the C-GW may also be extended to three or more, and the C-GW sends a data forwarding tunnel establishment request to each forwarding U-GW to establish an originating U-GW, the at least one Forwarding the data forwarding tunnel between the U-GW and the target base station.
  • the at least one forwarding U-GW includes U-GW1, U-GW2, and U-GW3, wherein the U-GW1 can communicate with the source U-GW, and the U-GW3 can communicate with the target U-GW, and the established forwarding The path of the tunnel is: source U-GW-U-GW1-U-GW2-U-GW3-target U-GW.
  • the C-GW further receives routing information of the source U-GW of the UE that is sent by the mobility management network element, where only one of the at least one forwarding U-GW is the first U-GW.
  • the C-GW is a serving C-GW after the UE moves to the current location area, and the C-GW is different from the serving C-GW before the UE moves to the current location area, and the mobility management network element moves for the UE.
  • the service mobility management network element after the current location area is the same or different from the service mobility management network element before the UE moves to the current location area.
  • step 203 is specifically implemented as:
  • the C-GW sends a second request to the first U-GW, where the second request is used to request the first U-GW to establish a data forwarding tunnel between the first U-GW and the target base station, and a data forwarding tunnel between the first U-GW and the source U-GW, the second request carrying routing information of the target base station, and routing information of the source U-GW.
  • the C-GW is different from the serving C-GW before the UE moves to the current location area, that is, the serving C-GW changes during the UE mobile process.
  • the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • the C-GW also receives a second response sent by the first U-GW according to the second request.
  • the second response is used to confirm that the first U-GW allows to establish a data forwarding tunnel between the first U-GW and the target base station, and data forwarding between the first U-GW and the source U-GW.
  • the tunnel optionally, the second response may carry routing information of the first U-GW, such as an IP address and TEID information.
  • the C-GW may send a first response of the first request to the mobility management network element.
  • the serving C-GW of the UE changes in the mobile process in this embodiment, the specific execution subject 203 is the target C-GW, that is, the UE moves to The service C-GW after the current location area. Further, the target C-GW should also send the data forwarding tunnel establishment request to the source U-GW through the mobility management network element, and send the routing information of the first U-GW to the source U-GW.
  • the source C-GW is a serving C-GW before the UE moves to the current location area
  • the source U-GW is a serving U-GW before the UE moves to the current location area.
  • an existing message such as a Create Indirect Data Forwarding Tunnel Request
  • a newly defined message may be used.
  • the first response or the second response in this implementation may use an existing message, such as Create Indirect Data Forwarding Tunnel Response, or use a newly defined message.
  • the invention is not limited thereto.
  • the C-GW further receives routing information of the source U-GW of the UE that is sent by the mobility management network element, where the at least one forwarding U-GW includes a second U-GW and a third a U-GW, where the C-GW is a serving C-GW after the UE moves to the current location area, and the C-GW is different from the serving C-GW before the UE moves to the current location area, where the mobility management network element is The UE moves to the serving mobility management network element after the current location area, and the mobility management network element is the same as or different from the serving mobility management network element before the UE moves to the current location area.
  • step 203 is specifically implemented as:
  • the C-GW sends a second request to the second U-GW, where the second request is used to request the second U-GW to establish a data forwarding tunnel between the second U-GW and the target base station, and a data forwarding tunnel between the second U-GW and the third U-GW, the second request carrying routing information of the target base station, and routing information of the third U-GW;
  • the C-GW sends a third request to the third U-GW, where the third request is used to request the third U-GW to establish data forwarding between the third U-GW and the second U-GW. a tunnel, and a data forwarding tunnel between the third U-GW and the source U-GW, the third request carrying routing information of the second U-GW, and routing information of the source U-GW.
  • the C-GW is different from the serving C-GW before the UE moves to the current location area, that is, the serving C-GW changes during the UE mobile process.
  • the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • the C-GW also receives a second response sent by the second U-GW according to the second request, and a third response sent by the third U-GW according to the third request.
  • the second response is used to confirm that the second U-GW allows a data forwarding tunnel between the second U-GW and the target base station, and data forwarding between the second U-GW and the third U-GW.
  • a tunnel optionally, the second response may carry routing information of the second U-GW, such as an IP address and TEID information; the third response is used to confirm the third U-GW and the second U-GW. And a data forwarding tunnel between the third U-GW and the source U-GW.
  • the third response may carry routing information of the third U-GW, such as an IP address and TEID information.
  • the C-GW may send the first response of the first request to the mobility management network element.
  • the specific execution entity in step 203 of the embodiment is the target C-GW. That is, the UE moves to the serving C-GW after the current location area. Further, the target C-GW should also send the data forwarding tunnel establishment request to the source U-GW through the mobility management network element, and send the routing information of the third U-GW to the source U-GW.
  • the source C-GW is a serving C-GW before the UE moves to the current location area
  • the source U-GW is a serving U-GW before the UE moves to the current location area.
  • an existing message may be used, such as creating an Indirect Data Forwarding Tunnel Request, or using a newly defined message.
  • the first response, the second response, or the third response may use an existing message, such as Create Indirect Data Forwarding Tunnel Response (The newly defined message can also be used, which is not limited by the present invention.
  • the method further includes: the C-GW accessing the target by using the mobility management network element
  • the base station sends the routing information of the first U-GW.
  • the method further includes: the C-GW passes The mobility management network element sends routing information of the second U-GW to the target base station.
  • the method may further include: the C-GW sending a session establishment request to the target U-GW, wherein the session establishment request is used for the target
  • a bearer context required for user plane data transmission is created for the UE on the U-GW, and each bearer context established includes routing information (such as an IP address and TEID information, etc.) of the target U-GW, and the target U-GW It is the service U-GW corresponding to the current location area of the UE.
  • the target U-GW is generally a serving U-GW that provides an optimal data transmission path for the UE in the current location area.
  • the C-GW sends the routing information of the target U-GW to the target base station by using the mobility management network element.
  • the first U-GW when the at least one forwarding U-GW is the first U-GW, the first U-GW may also be the C-GW according to the current UE.
  • the location information is the service U-GW selected by the UE. That is, the first U-GW is the target U-GW.
  • the target D-GW can directly communicate with the source D-GW, that is, the target U-GW simultaneously plays the role of the forwarding U-GW. It can be understood that when the target U-GW cannot directly communicate with the source D-GW, the forwarding U-GW selected by the C-GW is different from the target U-GW.
  • the MME as a mobility management network element.
  • the mobility management network element may also be another device that has the function of the mobile management network element, which is not limited herein.
  • FIG. 3 is an interaction flowchart of maintaining business continuity according to an embodiment of the present invention.
  • the source base station is a serving base station before the UE moves to the current location area;
  • the target base station is a serving base station after the UE moves to the current location area;
  • the serving MME and the serving C-GW to which the UE belongs remain before and after the UE moves.
  • the source U-GW is the serving U-GW before the UE moves to the current location area;
  • the target U-GW is the U-GW after the UE moves to the current location area; and the forwarding U-GW is used after the UE moves to the current location area.
  • U-GW for switching data services.
  • the uplink/downlink user plane data transmission path is the UE-source base station-source U-GW, that is, the transmission path shown by the broken lines L1a and L2a in FIG.
  • the source base station initiates a connection state UE user plane data switching process.
  • the source base station of the UE When the source base station of the UE senses that the UE moves out of the service range of the source base station, and the UE is performing the data service of the user plane, the source base station may decide to initiate a connection state user plane data service switching procedure.
  • the source base station sends a service switching request message to the MME.
  • the service switching request message sent by the source base station to the MME is named as the service switching request message 1.
  • the source base station sends a service switching request message 1 to the current serving MME (ie, the MME of FIG. 3), and carries the current location information of the UE in the message.
  • the current location information of the UE includes the Tracking Area Identity (TAI) corresponding to the current location area of the UE and/or the serving base station information corresponding to the current location area of the UE.
  • TAI Tracking Area Identity
  • the UE moves to the TAI corresponding to the current location area, that is, the target TAI of the UE; the UE moves to the serving base station information corresponding to the current location area, that is, the target base station information of the UE.
  • the target base station information may be a target base station identity (ID), a target cell identity (Cell Identity, CI), and the like.
  • the current location area of the UE is also referred to as the target location area of the UE, that is, the location area where the UE moves out of the service range of the source serving base station.
  • the current location information of the UE is also referred to as the target location information of the UE.
  • the MME sends a service switching notification message to the C-GW.
  • the serving MME of the UE learns that the UE has removed the service range of the current base station (source base station), and then sends a service switching notification message to the current serving C-GW.
  • the service switching notification message carries the current location information of the UE.
  • the traffic switch notification message is intended to inform the C-GW that the UE needs to be handed over to the new target location area.
  • the MME can re-use the existing message, such as a Create Session Request message or a Modify Bearer Request message or a Modify Access Bearers Request message, and carry the UE in these messages.
  • the current location information; the MME may also redefine the new message to send the service switching notification message, which is not limited in this embodiment of the present invention.
  • the C-GW determines the target U-GW and forwards the U-GW.
  • the C-GW may determine, according to the current location information of the UE, whether the current serving U-GW (source U-GW) of the UE needs to be re-allocated, that is, whether the UE removes the source U- GW's range of services. It should be noted that, since the C-GW saves the service area information of each U-GW in its service range in real time, the C-GW can determine whether the UE is based on the current location information of the UE (such as the target TAI or the target base station ID). The service range of the source U-GW is removed.
  • the switching of the data service can be implemented in the source U-GW.
  • the specific implementation refer to the U-GW or the P-GW in the prior art to switch the data service.
  • the method of the present invention is not described herein again.
  • the C-GW determines that the serving U-GW of the UE needs to be re-allocated, the C-GW selects a suitable target U-GW according to the current location information of the UE, and ensures that the target U-GW can provide the UE in the current location area.
  • the best data transmission path as much as possible to reduce the user plane data transmission RTT.
  • the C-GW needs to check whether the target U-GW and the source U-GW can communicate directly. If the target U-GW can directly communicate with the source U-GW, the target U-GW forwards the U-GW, that is, all subsequent steps to forward the U-GW are to the target U-GW; if the target U-GW cannot Directly communicating with the source U-GW, selecting a U-GW that can directly communicate with the source U-GW as the forwarding U-GW according to the UE target location information.
  • the manner in which the target U-GW and the forwarding U-GW are determined in FIG. 4 to FIG. 6 described below is similar.
  • the C-GW selects the default U-GW in the neighboring U-GW pool as the forwarding U-GW that communicates with the target U-GW (which may be referred to as target forwarding).
  • the C-GW may select the default U-GW in the U-GW pool where the source U-GW is located as the forwarding U-GW (which may be referred to as the source forwarding U-GW) that communicates with the source U-GW.
  • the U-GW is forwarded to ensure business continuity during UE mobility.
  • the C-GW returns a handover notification acknowledgement message to the MME.
  • the C-GW replies with the handover notification acknowledgement message to the MME, and carries the address and tunnel port information of the forwarding U-GW selected by the C-GW in the message.
  • Forwarding the address of the U-GW may be an Internet Protocol (IP) address for forwarding the U-GW, and the like; forwarding the tunnel port information of the U-GW according to the MME and the C-GW.
  • IP Internet Protocol
  • the protocol is different, for example, when the GTP protocol is used between the MME and the C-GW, the tunnel port information for forwarding the U-GW may be a GTP Tunnel Endpoint Identifier (TEID), and so on.
  • TEID GTP Tunnel Endpoint Identifier
  • the C-GW may carry the target forwarding U-GW in the UE target location area in the handover notification acknowledgement message. Address and tunnel port information.
  • the existing message may be reused, such as a Create Session Response message or a Modify Bearer Response message or modify the access bearer response (Modify).
  • the Access Bearers Response message may also be used to define a new message, which is not limited in the embodiment of the present invention.
  • the MME sends a service switching request message to the target base station.
  • the service switching request message sent by the MME to the target base station is named as the service switching request message 2.
  • the MME sends the service switching request message 2 to the target base station, and forwards the address of the forwarding U-GW and the tunnel port information sent by the C-GW to the target base station, so that the subsequent uplink data transmission path is switched to the forwarding U-GW.
  • the address of the forwarding U-GW and the tunnel port information may be carried in the service switching request message 2, or may be separately sent.
  • the target base station returns a handover request acknowledgement message to the MME.
  • the handover request acknowledgement message sent by the target base station to the MME is named as the handover request acknowledgement message 2.
  • the target base station may reply the handover request acknowledgement message 2 to the MME, and set its own address (such as an IP address) and tunnel port information (for example). Such as GTP TEID) is sent to the MME. Similarly, the address and tunnel port information of the target base station may be carried in the handover request acknowledgement message 2, or may be sent separately.
  • the MME sends a data forwarding tunnel establishment request to the C-GW.
  • the data forwarding tunnel establishment request sent by the MME to the C-GW is named as the data forwarding tunnel establishment request 1.
  • the MME sends a data forwarding tunnel establishment request 1 to the C-GW, and sends the address of the target base station and the tunnel port information to the C-GW, so as to switch the downlink data transmission path to the target base station.
  • the data forwarding tunnel establishment request may reuse an existing message, such as a Create Indirect Data Forwarding Tunnel Request message or a Modify Bearer Request message, or define a new one.
  • an existing message such as a Create Indirect Data Forwarding Tunnel Request message or a Modify Bearer Request message, or define a new one.
  • the present invention is not limited thereto, and the description is applicable to all embodiments of the present invention.
  • the C-GW sends a data forwarding tunnel establishment request to the forwarding U-GW.
  • the data forwarding tunnel establishment request is different from the other steps of the embodiment of the present invention, and the data forwarding tunnel establishment request corresponding to the corresponding digital identifier is matched, and the data forwarding tunnel establishment request sent by the C-GW to the forwarding U-GW is named as Data forwarding tunnel establishment request 2.
  • the C-GW sends a data forwarding tunnel establishment request 2 to the forwarding U-GW, and sends the address of the target base station and the tunnel port information and the address of the source U-GW and the tunnel port information to the forwarding U-GW.
  • the C-GW should send a data forwarding tunnel establishment request to each forwarding U-GW, and carry the address of the opposite network element and the tunnel port information.
  • the data forwarding tunnel establishment request sent by the source forwarding U-GW carries the address and tunnel port information of the source U-GW and the target forwarding U-GW, and carries the source in the data forwarding tunnel establishment request sent by the target forwarding U-GW. Forwarding the address and tunnel port information of the U-GW and the target base station.
  • the forwarding U-GW returns a data forwarding tunnel establishment response to the C-GW.
  • the data forwarding tunnel is set up to respond to the other steps of the embodiment of the present invention, and the data forwarding tunnel establishment request is matched with the corresponding digital identifier, and the data forwarding tunnel establishment response sent by the forwarding U-GW to the C-GW is named as The data forwarding tunnel establishes a response 2.
  • the data forwarding tunnel establishment response 2 may carry the address of the forwarding U-GW and the tunnel port information.
  • the C-GW should send a data forwarding tunnel establishment request to each forwarding U-GW, and each corresponding forwarding U-GW should reply to the data forwarding tunnel establishment response, indicating that permission is established. Data forwarding tunnel.
  • the response of the data forwarding tunnel establishment request in the present invention is to allow the establishment of a data forwarding tunnel. If there is a response that does not allow the establishment of a data forwarding tunnel, the method of the embodiment of the present invention will not be executed, and the same applies.
  • the data forwarding tunnel establishment response may reuse an existing message, such as creating an Indirect Data Forwarding Tunnel Response message or a Modify Bearer Response message, or may define a new one.
  • the present invention is not limited thereto, and the description is applicable to all embodiments of the present invention.
  • the C-GW sends a data forwarding tunnel establishment request to the source U-GW.
  • the data forwarding tunnel establishment request sent by the C-GW to the source U-GW is named as the data forwarding tunnel establishment request 3.
  • the C-GW sends a data forwarding tunnel establishment request 3 to the source U-GW, and sends the address of the forwarding U-GW and the tunnel port information to the source U-GW.
  • the C-GW sends the address of the source forwarding U-GW and the tunnel port information in the current location area of the UE to the source U-GW.
  • the source U-GW returns a data forwarding tunnel establishment response to the C-GW.
  • the data forwarding tunnel is set up to respond to the other steps of the embodiment of the present invention, and the corresponding data identifier is matched with the corresponding data forwarding tunnel establishment request, and the data forwarding tunnel establishment response sent by the source U-GW to the C-GW is named as The data forwarding tunnel establishes a response 3.
  • the source U-GW returns a data forwarding tunnel establishment response 3 to the C-GW to respond to the data forwarding tunnel establishment request 3 sent by the C-GW, and confirms that the data forwarding tunnel between the forwarding U-GW and the source U-GW is allowed to be established.
  • a data forwarding tunnel is established between the source U-GW and the forwarding U-GW.
  • a data forwarding tunnel is established between the source U-GW and the forwarding U-GW.
  • a plurality of forwarding U-GWs such as a source forwarding U-GW and a destination forwarding U-GW, are determined in step S304, the corresponding establishing source U-GW, the source forwarding U-GW, and the destination forwarding U-GW A data forwarding tunnel between the U-GW and the destination forwarding.
  • the C-GW returns a data forwarding tunnel establishment response to the MME.
  • the data forwarding tunnel is set up to respond to the other steps of the embodiment of the present invention, and the data forwarding tunnel establishment request is matched with the corresponding digital identifier, and the data forwarding tunnel establishment response sent by the C-GW to the MME is named as a data forwarding tunnel. Establish response 1.
  • the C-GW After the data forwarding tunnel is established between the source U-GW and the forwarding U-GW, the C-GW replies to the data forwarding tunnel establishment response 1 to the MME, indicating that the MME data forwarding tunnel has been established, and the service switching can be performed.
  • the MME sends a handover command to the source base station.
  • the MME sends a handover command to the source base station, and carries the address of the forwarding U-GW and the tunnel port information. If a plurality of forwarding U-GWs, such as a source forwarding U-GW and a destination forwarding U-GW, are required, the source forwarding U-GW address and tunnel port information in the source location area of the UE are carried.
  • the source base station performs a data switching process.
  • the source base station continues to perform the existing data switching procedure, and the UE is handed over to the target cell and instructs the UE to access from the target cell.
  • the subsequent steps can reuse the existing handover procedure to implement complete handover from the UE to the target location.
  • the uplink/downlink user plane data transmission path becomes: UE—target base station—forwarding the U-GW—the source U-GW, that is, the dotted lines L3a, L4a, L5a, and L6a in FIG. 3 Transmission path.
  • UE target base station
  • forwarding the U-GW the source U-GW, that is, the dotted lines L3a, L4a, L5a, and L6a in FIG. 3 Transmission path.
  • the path of the data forwarding tunnel passes through all the forwarding U-GWs, for example, if the forwarding U-DW includes the target forwarding U-DW and When the source forwards the U-DW, the transmission path becomes: UE—target base station—target forwarding U-GW—source forwarding U-GW—source U-GW.
  • the data forwarding tunnel established in the embodiment of the present invention is to establish a user plane bearer between the source U-GW serving the UE and the forwarding U-GW, and between the forwarding U-GW and the target base station of the UE.
  • the user plane bearer context includes routing information (such as address and tunnel port information) required for forwarding user plane data, including routing information of the source U-GW, routing information of the forwarding U-GW, and the routing information The routing information of the target base station, the same applies to other embodiments of the present invention.
  • the C-GW determines to forward the U-GW according to the current location information of the UE, and establishes a data forwarding tunnel between the source U-GW and the forwarding U-GW to ensure continuity of services during the UE mobility process. Guarantee the user's business experience.
  • the source base station is a serving base station before the UE moves to the current location area; the target base station is a serving base station after the UE moves to the current location area; the serving MME and the serving C-GW to which the UE belongs remain before and after the UE moves.
  • the source U-GW is the serving U-GW before the UE moves to the current location area; the target U-GW is the U-GW after the UE moves to the current location area; and the forwarding U-GW is used after the UE moves to the current location area.
  • U-GW for switching data services.
  • the uplink/downlink user plane data transmission path is the UE-source base station-source U-GW, that is, the transmission path shown by the broken lines L1b and L2b in FIG.
  • the source base station initiates a connection state UE user plane data switching process.
  • the source base station sends a service switching request message to the MME.
  • the MME sends a service switching notification message to the C-GW.
  • the C-GW determines the target U-GW and forwards the U-GW.
  • steps S401-S404 reference may be made to steps S301-S04 of FIG.
  • the C-GW sends a setup session request to the target U-GW.
  • the C-GW may initiate a setup session request to the target U-GW to establish a bearer context required for user plane data transmission on the target U-GW.
  • the target U-GW sends a session establishment response to the C-GW.
  • the target U-GW establishes a bearer context required for user plane data transmission of the UE according to the establishment session request, where each of the established bearer contexts includes an address of the target U-GW (eg, an IP address, etc.) ) and tunnel port information (such as GTP TEID, etc.).
  • an address of the target U-GW eg, an IP address, etc.
  • tunnel port information such as GTP TEID, etc.
  • the target U-GW may send a session establishment response to the C-GW.
  • the C-GW returns a handover notification acknowledgement message to the MME.
  • the C-GW returns a handover notification acknowledgement message to the MME, and carries the address and tunnel port information of the target U-GW selected by the C-GW in the message.
  • the MME sends a service switching request message to the target base station.
  • the MME sends a service switching request message to the target base station, and carries the address and tunnel port information of the target U-GW sent by the C-GW.
  • the target base station returns a handover request acknowledgement message to the MME.
  • the target base station may return a handover request acknowledgement message to the MME, and send its own address (for example, an IP address) and tunnel port information (for example, a GTP TEID) to the MME.
  • its own address for example, an IP address
  • tunnel port information for example, a GTP TEID
  • the address and tunnel port information of the target base station may be carried in the handover request acknowledgement message, or may be sent separately.
  • the MME sends a data forwarding tunnel establishment request to the C-GW.
  • the C-GW sends a data forwarding tunnel establishment request to the forwarding U-GW.
  • the forwarding U-GW returns a data forwarding tunnel establishment response to the C-GW.
  • the C-GW sends a data forwarding tunnel establishment request to the source U-GW.
  • the source U-GW returns a data forwarding tunnel establishment response to the C-GW.
  • a data forwarding tunnel is established between the source U-GW and the forwarding U-GW.
  • the C-GW returns a data forwarding tunnel establishment response to the MME.
  • the MME sends a handover command to the source base station.
  • steps S410-S417 reference may be made to steps S308-S315 of FIG.
  • the source base station performs a data switching process.
  • the source base station continues to perform the existing data switching procedure, and the UE is handed over to the target cell and instructs the UE to access from the target cell.
  • the subsequent steps can reuse the existing handover procedure to implement complete handover from the UE to the target location.
  • the downlink user plane data transmission path during handover and after handover is: source base station - source U-GW - forwarding U-GW - target base station - UE, that is, transmission shown by broken lines L3b, L4b, L5b and L6b in FIG. Path;
  • the uplink user plane data transmission path during handover and after handover is: UE - target base station - target U-GW, that is, the transmission path shown by the broken lines L7b and L8b in FIG.
  • the C-GW determines whether the U-GW of the service needs to be changed according to the current location information of the UE, and selects to forward the U-GW according to whether the selected target U-GW and the source U-GW can directly communicate with each other.
  • the data forwarding tunnel between the source U-GW and the forwarding U-GW is established to ensure the continuity of the service during the UE mobile process and ensure the user service experience.
  • the C-GW directly initiates a bearer context establishment request of the target U-GW, and the routing information of the target U-GW is sent to the target base station through the MME, so that the uplink data can be directly sent from the target base station to the target U-GW without going through the Forwarding the U-GW and the source U-GW to implement route optimization for uplink data transmission.
  • the interaction procedure of the embodiment shown in FIG. 3 and FIG. 4 is applicable to a scenario in which the serving MME and the serving C-GW of the UE remain unchanged before and after the UE moves. If the serving MME of the UE changes and the serving C-GW does not change before and after the UE moves, it only needs to be shown in the embodiment of the present invention. On the basis of the solution, a signaling interaction is added between the source MME and the target MME, and the interaction process belongs to the prior art, and the present invention is not described herein again.
  • FIG. 5 is still another flow chart of interaction for maintaining business continuity according to an embodiment of the present invention.
  • the source base station is the serving base station before the UE moves to the current location area;
  • the target base station is the serving base station after the UE moves to the current location area;
  • the source MME is the serving MME before the UE moves to the current location area;
  • the target MME is The UE moves to the serving MME after the current location area;
  • the source C-GW is the serving C-GW before the UE moves to the current location area;
  • the target C-GW is the serving C-GW after the UE moves to the current location area;
  • the source U- The GW is the serving U-GW before the UE moves to the current location area;
  • the target U-GW is the U-GW after the UE moves to the current location area;
  • the forwarding U-GW is used to switch the data service after the UE moves to the current location area.
  • U-GW Before the service switching, the uplink/downlink user plane data transmission
  • the source base station initiates a connection state UE user plane data switching process.
  • the source base station of the UE When the source base station of the UE senses that the UE moves out of the service range of the source base station, and the UE is performing the data service of the user plane, the source base station may decide to initiate a connection state user plane data service switching procedure.
  • the source base station sends a service switching request message to the source MME.
  • the service switching request message sent by the source base station to the source MME is named as the service switching request message 1.
  • the source base station sends a service switching request message 1 to the current serving MME (ie, the source MME of FIG. 5), and carries the current location information of the UE in the message.
  • the current location information of the UE includes the TAI corresponding to the current location area of the UE and/or the serving base station information corresponding to the current location area of the UE.
  • the UE moves to the TAI corresponding to the current location area, that is, the target TAI of the UE; the UE moves to the serving base station information corresponding to the current location area, that is, the target base station information of the UE.
  • the target base station information may be a target base station identity (ID), a target cell identity (Cell Identity, CI), and the like.
  • the current location area of the UE which is also referred to as the target location area of the UE, that is, the location area where the UE moves out of the service range of the source serving base station, similarly, the current location information of the UE, also referred to as the UE target. location information.
  • the source MME sends a Forward Relocation Request message to the target MME.
  • the source MME determines whether the UE removes the service range of the source MME according to the current location information of the UE. If the service range of the source MME is removed, the source MME according to the current location information of the UE. Selecting a suitable target MME, sending a Forward Relocation Request message to the target MME, and carrying the current location information of the UE.
  • the target MME is an MME that provides services for the UE after the UE moves to the current location area.
  • the target MME determines the target C-GW.
  • the target MME determines whether the serving C-GW of the current UE needs to be re-allocated according to the current location information of the UE, that is, whether the UE removes the service range of the source C-GW. If re-allocation is required, the target MME selects a suitable one according to the current location information of the UE. The goal of C-GW.
  • the target MME sends a service C-GW change notification message to the source MME.
  • the target MME sends a serving C-GW change notification message to the source MME, in order to notify the source MME that the serving C-GW of the UE needs to be changed.
  • the existing message may be reused, for example, a change notification request (Change Notification Request) message, and a new indication information may be added to the message, and the new message may be redefined.
  • Change Notification Request Change Notification Request
  • the embodiments of the present invention are not limited.
  • the source MME sends a service switching notification message to the source C-GW.
  • the service switching notification message sent by the source MME to the source C-GW is named as the service switching notification message 1.
  • the UE's serving MME learns that the UE has removed the service range of the current base station (source base station), and then sends a service switching notification message 1 to the current serving C-GW (source C- GW), and carries the service C-GW to change the indication information.
  • the source MME may reuse the existing message to send the service switching notification message 1, such as a Create Session Request message or a Modify Bearer Request message or a Modify Access Bearers Request message.
  • the current location information of the UE is carried in the message; the source MME may also re-define the new message to send the service switching notification message 1, which is not limited in this embodiment of the present invention.
  • the source C-GW sends a handover notification acknowledgement to the source MME.
  • the handover request acknowledgement message is different from the other steps of the embodiment of the present invention, and the corresponding service identifier is matched with the corresponding service identifier, and the handover request acknowledgement message sent by the source C-GW to the source MME is named as the handover notification acknowledgement message. 1.
  • the source C-GW may carry the handover notification message 1 (such as the IP address) and the tunnel port information (such as the GTP TEID). ).
  • the source MME replies to the target MME with a C-GW change notification acknowledgement.
  • the source MME replies to the target MME with a C-GW change notification acknowledgement, and carries the address of the source U-GW (such as an IP address) and tunnel port information (such as a GTP TEID).
  • a C-GW change notification acknowledgement carries the address of the source U-GW (such as an IP address) and tunnel port information (such as a GTP TEID).
  • the target MME sends a service switching notification message to the target C-GW.
  • the service switching notification message sent by the target MME to the target C-GW is named as the service switching notification message 2.
  • the target MME sends a service handover notification message 2 to the target C-GW, where the service handover notification message 2 carries the current location information of the UE, including the target TAI and the target base station information (base station ID).
  • the service switching notification message is intended to notify the C-GW that the UE needs to be switched to a new target location area (ie, the current location area of the UE).
  • the target MME may reuse the existing message to send the service handover notification message 2, such as a Create Session Request message or a Modify Bearer Request message or a Modify Access Bearers Request message.
  • the UE target location information is carried in the message; the target MME may also re-define the new message to send the service switching notification message 2, which is not limited in this embodiment of the present invention.
  • the target C-GW determines the target U-GW and forwards the U-GW.
  • the target C-GW After obtaining the handover request, the target C-GW selects an appropriate target U-GW according to the current location information of the UE, and ensures that the target U-GW can provide the best data transmission path for the UE at the target location, as much as possible. Reduce user plane data transfer RTT.
  • the target C-GW needs to check whether the target U-GW can communicate directly with the source U-GW. If the target U-GW can directly communicate with the source U-GW, the target U-GW forwards the U-GW, that is, all subsequent steps to forward the U-GW are to the target U-GW; if the target U-GW cannot Directly communicating with the source U-GW, the target C-GW selects a U-GW that can directly communicate with the source U-GW as the forwarding U-GW according to the current location information of the UE.
  • the target C-GW selects the default U-GW in the neighboring U-GW pool as the target forwarding U-GW. If the default U-GW does not directly communicate with the source U-GW, the target C-GW may select the default U-GW in the U-GW pool where the source U-GW is located as the source forwarding U- The GW, through two forwarding U-GWs, ensures service continuity during UE mobility.
  • the target C-GW sends a handover notification acknowledgement message to the target MME.
  • the handover request acknowledgement message is different from the other steps of the embodiment of the present invention, and the corresponding service identifier is matched with the corresponding service identifier, and the handover request acknowledgement message sent by the target C-GW to the target MME is named as the handover notification acknowledgement message. 2.
  • the target C-GW may reply the handover notification acknowledgement message 2 to the target MME according to the service handover notification message 2 of the target MME, and carry the forwarding U-GW selected by the target C-GW in the message.
  • Address such as IP address
  • tunnel port information such as GTP TEID
  • the target C-GW carries the address and tunnel of the target forwarding U-GW in the current location area of the UE in the handover notification acknowledgement message. Port information.
  • the target C-GW may reuse the existing message, such as a Create Session Response message or a Modify Bearer Response message or modify the access bearer response (Modify).
  • the Access Bearers Response message, or a new message is defined, to send the handover notification acknowledgement message 2, which is not limited in the embodiment of the present invention.
  • the target MME sends a service switching request message to the target base station.
  • the service switching request message sent by the target MME to the target base station is named as the service switching request message 2.
  • the target MME sends the service switching request message 2 to the target base station, and sends the address of the forwarding U-GW and the tunnel port information to the target base station, so that the subsequent uplink data transmission path is switched to the forwarding U-GW.
  • the target base station sends a handover request acknowledgement message to the target MME.
  • the handover request acknowledgement message sent by the target base station to the target MME is named as the handover request acknowledgement message 2.
  • the target base station replies to the handover request acknowledgement message 2 and transmits its own address (such as an IP address) and tunnel port information (such as a GTP TEID) to the target MME.
  • its own address such as an IP address
  • tunnel port information such as a GTP TEID
  • the target MME sends a data forwarding tunnel establishment request to the target C-GW.
  • the data forwarding tunnel establishment request sent by the target MME to the target C-GW is named as the data forwarding tunnel establishment request 1.
  • the target MME sends a data forwarding tunnel establishment request 1 to the target C-GW, and sends the address of the target base station and the tunnel port information to the C-GW, so that the subsequent downlink data transmission path is switched to the destination. On the base station.
  • the target C-GW sends a data forwarding tunnel establishment request to the forwarding U-GW.
  • the data forwarding tunnel establishment request sent by the target C-GW to the forwarding U-GW is named as the data forwarding tunnel establishment request 2.
  • the target C-GW sends a data forwarding tunnel establishment request 2 to the forwarding U-GW, and sends the address of the target base station and the tunnel port information and the address of the source U-GW and the tunnel port information to the forwarding U-GW.
  • the target C-GW should send a data forwarding tunnel establishment request to each forwarding U-GW, and carry the address of the opposite network element and the tunnel port information.
  • the forwarding U-GW returns a data forwarding tunnel establishment response to the target C-GW.
  • the data forwarding tunnel establishment response sent by the forwarding U-GW to the target C-GW is named as data forwarding.
  • the tunnel establishes a response 2.
  • the forwarding U-GW returns a data forwarding tunnel establishment response 2 to the target C-GW in response to the data forwarding tunnel establishment request 2 sent by the target C-GW, confirming that the establishment of the target base station and the forwarding U-GW, and the source U-GW are permitted.
  • the data forwarding tunnel between the forwarding U-GW, and optionally, the data forwarding tunnel establishment response 2 may carry the address of the forwarding U-GW and the tunnel port information.
  • the C-GW shall send a data forwarding tunnel establishment request to each forwarding D-GW, and each corresponding forwarding D-GW shall reply to the data forwarding tunnel establishment response, indicating that permission is established. Data forwarding tunnel.
  • the target C-GW returns a data forwarding tunnel establishment response to the target MME.
  • the data forwarding tunnel establishment response is different from the other steps of the embodiment of the present invention, and the corresponding digital ID is matched with the corresponding data forwarding tunnel establishment request, and the data forwarding tunnel establishment response sent by the target C-GW to the target MME is named as data.
  • Forward tunnel establishment response 1 1.
  • the target C-GW After receiving the data forwarding tunnel establishment response 2, the target C-GW replies to the data forwarding tunnel establishment response 1 to the target MME, and confirms that the data forwarding tunnel between the target base station and the forwarding U-GW is allowed to be established.
  • the target MME sends a forwarding relocation response to the source MME.
  • the target MME may send a forwarding relocation response to the source MME, and carry the address of the forwarding U-GW and the tunnel end. Information.
  • the source MME sends a data forwarding tunnel establishment request to the source C-GW.
  • the data forwarding tunnel establishment request sent by the source MME to the source U-GW is named as the data forwarding tunnel establishment request 3.
  • the source MME sends a data forwarding tunnel establishment request 3 to the source C-GW, and sends the address of the forwarding U-GW and the tunnel port information to the source C-GW.
  • the source C-GW sends a data forwarding tunnel establishment request to the source U-GW.
  • the data forwarding tunnel establishment request sent by the source C-GW to the source U-GW is named as the data forwarding tunnel establishment request 4.
  • the source C-GW sends a data forwarding tunnel establishment request 4 to the source U-GW, and sends the address of the forwarding U-GW and the tunnel port information to the source U-GW.
  • the source U-GW sends a data forwarding tunnel setup response to the source C-GW.
  • the data forwarding tunnel is set up to respond to the other steps of the embodiment of the present invention, and the corresponding data identifier is matched with the corresponding data forwarding tunnel establishment request, and the data forwarding tunnel establishment response response sent by the source U-GW to the source C-GW is named. Establish a response 4 for the data forwarding tunnel.
  • the source U-GW may reply to the data forwarding tunnel establishment response 4, and confirm that the data forwarding tunnel between the forwarding U-GW and the source U-GW is allowed to be established.
  • a data forwarding tunnel is established between the source U-GW and the forwarding U-GW.
  • a data forwarding tunnel is established between the source U-GW and the forwarding U-GW.
  • a plurality of forwarding U-GWs such as a source forwarding U-GW and a target forwarding U-GW, are determined in step S510, the corresponding establishing source U-GW, the source forwarding U-GW, and the source forwarding U-GW A data forwarding tunnel between the U-GW and the destination forwarding.
  • the source C-GW sends a data forwarding tunnel setup response to the source MME.
  • the data forwarding tunnel is set up to respond to the other steps of the embodiment of the present invention, and the data forwarding tunnel establishment request is matched with the corresponding digital identifier, and the data forwarding tunnel establishment response sent by the source C-GW to the source MME is named as data. Forward tunnel establishment response 3.
  • the source C-GW may send a data forwarding tunnel establishment response 3 to the source MME, and confirm that the data forwarding tunnel between the forwarding U-GW and the source U-GW is allowed to be established.
  • the source MME sends a handover command to the source base station.
  • the source MME sends a handover command to the source base station, and carries the address of the forwarding U-GW and the tunnel port information.
  • the address and tunnel port information of the source forwarding U-GW in the source location area of the UE are carried in the handover command.
  • S524 The source base station continues to perform the existing data switching procedure, and the UE is handed over to the target cell and instructs the UE to access from the target cell, and then reuses the existing handover procedure to implement complete handover of the UE to the target location.
  • the uplink/downlink user plane data transmission path becomes: UE—target base station—forwarding the U-GW—the source U-GW, that is, the dotted lines L3c, L4c, L5c, and L6c in FIG. 5 Transmission path.
  • UE target base station
  • forwarding the U-GW the source U-GW, that is, the dotted lines L3c, L4c, L5c, and L6c in FIG. 5 Transmission path.
  • the uplink/downlink user plane data transmission path passes through the source U-GW, but the location of the source U-GW and the forwarding U-GW have been moved closer to each other. The location of the UE, so the distance between the source U-GW and the forwarding U-GW will also be very close, so that the RTT of the user plane data is not significantly increased.
  • the target C-GW determines to forward the U-GW according to the current location information of the UE, and ensures the continuity of the service during the UE mobile process by establishing a data forwarding tunnel between the source U-GW and the forwarding U-GW. To ensure the user's business experience.
  • FIG. 6 is another flow chart of interaction for maintaining business continuity according to an embodiment of the present invention.
  • the source base station is the serving base station before the UE moves to the current location area;
  • the target base station is the serving base station after the UE moves to the current location area;
  • the source MME is the serving MME before the UE moves to the current location area;
  • the target MME is The UE moves to the serving MME after the current location area;
  • the source C-GW is the serving C-GW before the UE moves to the current location area;
  • the target C-GW is the serving C-GW after the UE moves to the current location area;
  • the source U- The GW is the serving U-GW before the UE moves to the current location area;
  • the target U-GW is the U-GW after the UE moves to the current location area;
  • the forwarding U-GW is used to switch the data service after the UE moves to the current location area.
  • U-GW Before the service switching, the uplink/downlink user plane data transmission path
  • the source base station initiates a connection state UE user plane data switching process.
  • the source base station sends a service switching request message.
  • the source MME sends a forward relocation request message.
  • the target MME determines the target C-GW.
  • the target MME sends a service C-GW change notification message to the source MME.
  • the source MME sends a service switching notification message to the source C-GW.
  • the source C-GW sends a handover notification acknowledgement to the source MME.
  • the source MME replies to the target MME with a C-GW change notification acknowledgement.
  • the target MME sends a service switching notification message to the target C-GW.
  • the target C-GW determines the target U-GW and forwards the U-GW.
  • steps S601-S610 reference may be made to steps S501-S510 of FIG.
  • the target C-GW sends a setup session request to the target U-GW.
  • the target C-GW may initiate a setup session request to the target U-GW to establish a bearer context required for user plane data transmission on the target U-GW.
  • the target U-GW sends a session establishment response to the target C-GW.
  • the target U-GW establishes a bearer context required for user plane data transmission of the UE according to the establishment session request, where each of the established bearer contexts includes an address of the target U-GW (eg, an IP address, etc.) ) and tunnel port information (such as GTP TEID, etc.).
  • an address of the target U-GW eg, an IP address, etc.
  • tunnel port information such as GTP TEID, etc.
  • the target U-GW may send a session establishment response to the target C-GW.
  • the target C-GW sends a handover notification acknowledgement message to the target MME.
  • the handover request acknowledgement message is different from the other steps of the embodiment of the present invention, and the corresponding service identifier is matched with the corresponding service identifier, and the handover request acknowledgement message sent by the target C-GW to the target MME is named as the handover notification acknowledgement message. 2.
  • the target C-GW may reply the handover notification acknowledgement message 2 to the target MME according to the service handover notification message 2 of the target MME, and carry the target U-GW selected by the target C-GW in the message.
  • Address such as IP address
  • tunnel port information such as GTP TEID
  • the target MME sends a service switching request message to the target base station.
  • the service switching request message sent by the target MME to the target base station is named as the service switching request message 2.
  • the target MME sends the service switching request message 2 to the target base station, and carries the address and tunnel port information of the target U-GW sent by the target C-GW.
  • the target base station sends a handover request acknowledgement message to the target MME.
  • the handover request acknowledgement message sent by the target base station to the target MME is named as the handover request acknowledgement message 2.
  • the target base station replies to the handover request acknowledgement message 2 and transmits its own address (such as an IP address) and tunnel port information (such as a GTP TEID) to the target MME.
  • its own address such as an IP address
  • tunnel port information such as a GTP TEID
  • the target MME sends a data forwarding tunnel establishment request to the target C-GW.
  • the target C-GW sends a data forwarding tunnel establishment request to the forwarding U-GW.
  • the forwarding U-GW returns a data forwarding tunnel establishment response to the target C-GW.
  • the target C-GW returns a data forwarding tunnel establishment response to the target MME.
  • the target MME sends a forwarding relocation response to the source MME.
  • the source MME sends a data forwarding tunnel establishment request to the source C-GW.
  • the source C-GW sends a data forwarding tunnel establishment request to the source U-GW.
  • the source U-GW sends a data forwarding tunnel setup response to the source C-GW.
  • a data forwarding tunnel is established between the source U-GW and the forwarding U-GW.
  • the source C-GW sends a data forwarding tunnel setup response to the source MME.
  • the source MME sends a handover command to the source base station.
  • S627 The source base station continues to perform the existing data switching procedure, and the UE is handed over to the target cell and instructs the UE to access from the target cell, and then reuses the existing handover procedure to implement complete handover of the UE to the target location.
  • the downlink user plane data transmission path is: source base station - source U-GW - forwarding U-GW - target base station - UE, that is, the transmission shown by the dotted lines L3d, L4d, L5d, and L6d in FIG. Path;
  • the uplink user plane data transmission path during handover and after handover is: UE-target base station-target U-GW, that is, the transmission path shown by the broken lines L7d and L8d in FIG.
  • the target C-GW determines whether the U-GW of the service needs to be changed according to the current location information of the UE, and selects whether to forward the U according to whether the selected target U-GW and the source U-GW can directly communicate with each other.
  • the GW ensures the continuity of the service during the UE mobile process and ensures the user service experience by establishing a data forwarding tunnel between the source U-GW and the forwarding U-GW.
  • the C-GW directly initiates a bearer context establishment request of the target U-GW, and the routing information of the target U-GW is sent to the target base station through the MME, so that the uplink data can be directly sent from the target base station to the target U-GW without going through the Forwarding the U-GW and the source U-GW to implement route optimization for uplink data transmission.
  • the interaction procedure of the embodiment shown in FIG. 5 and FIG. 6 is applicable to a scenario in which the serving MME and the serving C-GW of the UE change before and after the UE moves. If before and after the UE moves, If the serving C-GW of the UE is changed and the serving MME is unchanged, the signaling interaction between the source MME and the target MME is reduced on the basis of the solution shown in the embodiment of the present invention, and the present invention is not described herein again.
  • FIG. 7 is still another flow chart of interaction for maintaining business continuity according to an embodiment of the present invention.
  • the target base station is a serving base station in which the UE is switched from the idle state to the connected state in the current location area;
  • the source U-GW is the serving U-GW before the UE moves to the current location area; and
  • the target U-GW is the UE currently in the current location.
  • the location area is changed from the idle state to the connected service U-GW;
  • the forwarding U-GW is the U-GW for switching the data service after the UE moves to the current location area;
  • the MME is the UE changing from the idle state to the connection in the current location area.
  • the C-GW is a serving C-GW in which the UE transits from the idle state to the connected state in the current location area.
  • the idle UE needs to send uplink user plane data.
  • the UE sends a signaling request to the MME.
  • the UE may initiate a location update procedure by sending a signaling request to the MME.
  • the location update process is a Tracking Area Update (TAU) process
  • the signaling request is a location update request message.
  • the UE may initiate a service request (Service Request) process by sending a signaling request to the MME.
  • Service Request a service request
  • the request be a business request message.
  • the UE may send the signaling request message to the serving MME through the target base station, and the target base station sends the current location information of the UE to the MME.
  • the current location information of the UE includes the Tracking Area Identity (TAI) corresponding to the current location area of the UE and/or the serving base station information corresponding to the current location area of the UE.
  • TAI Tracking Area Identity
  • the UE moves to the TAI corresponding to the current location area, that is, the target TAI of the UE; the UE moves to the serving base station information corresponding to the current location area, that is, the target base station information of the UE.
  • the target base station information may be a target base station identity (ID), a target cell identity (Cell Identity, CI), and the like.
  • ID target base station identity
  • Cell Identity Cell Identity
  • the current location area of the UE is also referred to as the target location area of the UE, that is, the location area where the UE moves out of the service range of the source serving base station.
  • the current location information of the UE is also referred to as the target location information of the UE.
  • the MME sends a request message to the C-GW, and carries the current UE status in the request message. location information.
  • the serving MME of the UE After receiving the location update request message or the service request message, the serving MME of the UE obtains that the UE has removed the service range of the current base station (source base station) according to the current location information of the UE, and sends a request message to the current serving C-GW.
  • the request message is intended to inform the C-GW that the UE moves to a new target location area.
  • the MME can reuse existing messages, such as a Create Session Request message or a Modify Bearer Request message or modify an Access Bearer Request message, or redefine a new message.
  • the embodiment of the invention is not limited thereto.
  • the C-GW determines the target U-GW and forwards the U-GW.
  • the C-GW may determine the target U-GW and the forwarding U-GW according to the current location information of the UE. For the specific implementation, reference may be made to step S304 of the embodiment shown in FIG. 3, and details are not described herein again. .
  • the C-GW returns a request confirmation message to the MME.
  • the C-GW replies with the acknowledgment message to the MME.
  • step S305 of the embodiment shown in FIG. 3 and details are not described herein again.
  • the MME sends an initial context setup request to the target base station.
  • the MME sends an Initial Context Setup Request message to the target base station, and forwards the address of the forwarding U-GW and the tunnel port information sent by the C-GW to the target base station, so that the subsequent uplink data transmission path is switched to the forwarding U. -GW.
  • the target base station returns an initial context setup response message to the MME.
  • the target base station replies to the MME with an Initial Context Setup Response message and sends its own address (eg, IP address) and tunnel port information (eg, GTP TEID) to the MME.
  • IP address e.g., IP address
  • GTP TEID tunnel port information
  • the MME sends a modify bearer request to the C-GW.
  • the MME sends a modify bearer request message to the C-GW, and sends the address of the target base station and the tunnel port information to the C-GW, so as to switch the downlink data transmission path to the target base station.
  • the MME may send a modify access bearer request message and carry the address and tunnel port information of the target base station to the C-GW.
  • the C-GW sends a data forwarding tunnel establishment request to the forwarding U-GW.
  • the forwarding U-GW returns a data forwarding tunnel establishment response to the C-GW.
  • the C-GW sends a data forwarding tunnel establishment request to the source U-GW.
  • the source U-GW returns a data forwarding tunnel setup response to the C-GW.
  • a data forwarding tunnel is established between the source U-GW and the forwarding U-GW.
  • steps S709-S713 For the specific implementation of the steps S709-S713, reference may be made to the steps S309-S313 of the embodiment shown in FIG. 3, and details are not described herein again.
  • the C-GW replies to the MME to modify the bearer response.
  • the C-GW may reply to modify the access bearer response message to the MME.
  • the uplink/downlink user plane data transmission path becomes: UE—target base station—forwarding the U-GW—the source U-GW, that is, the transmission shown by the broken lines L1e, L2e, and L3e in FIG. path.
  • UE target base station
  • forwarding the U-GW the source U-GW, that is, the transmission shown by the broken lines L1e, L2e, and L3e in FIG. path.
  • the uplink/downlink user plane data transmission path passes through the source U-GW, but considering that both the source U-GW and the forwarding U-GW have moved down to a position closer to the UE, the source U- The distance between the GW and the forwarding U-GW will also be very close, so that the RTT of the user plane data is not significantly increased.
  • the path of the data forwarding tunnel passes through all the forwarding U-GWs, for example, if the forwarding U-DW includes the target forwarding U-DW and When the source forwards the U-DW, the transmission path becomes: UE—target base station—target forwarding U-GW—source forwarding U-GW—source U-GW.
  • the C-GW determines to forward the U-GW according to the current location information of the UE, and establishes a data forwarding tunnel between the source U-GW and the forwarding U-GW to ensure continuity of services during the UE mobility process. Guarantee the user's business experience.
  • FIG. 8 is still another flow chart of interaction for maintaining business continuity according to an embodiment of the present invention.
  • the target base station is a serving base station in which the UE is switched from the idle state to the connected state in the current location area;
  • the source U-GW is the serving U-GW before the UE moves to the current location area; and
  • the target U-GW is the UE currently in the current location.
  • the location area is changed from the idle state to the connected service U-GW;
  • the forwarding U-GW is the U-GW for switching the data service after the UE moves to the current location area;
  • the MME is the UE changing from the idle state to the connection in the current location area.
  • the C-GW is a serving C-GW in which the UE transits from the idle state to the connected state in the current location area.
  • the idle state UE needs to send uplink user plane data.
  • the UE sends a signaling request to the MME.
  • step S802 For the specific implementation of step S802, refer to step S702 of FIG. 7, and details are not described herein again.
  • the MME sends an initial context setup request to the target base station.
  • the MME sends an Initial Context Setup Request message to the target base station.
  • This step is an existing step in the existing location update procedure or the service request procedure. Therefore, the MME sends the address of the source U-GW and the tunnel port information. Give the target base station.
  • the target base station returns an initial context setup response message to the MME.
  • the target base station replies to the MME with an Initial Context Setup Response message and sends its own address (eg, IP address) and tunnel port information (eg, GTP TEID) to the MME.
  • IP address e.g., IP address
  • GTP TEID tunnel port information
  • the MME sends a modify bearer request to the C-GW.
  • the MME sends a modify bearer request message to the C-GW, and sends the current location information of the UE and the address of the target base station and the tunnel port information to the C-GW.
  • the MME may send a modify access bearer request message and carry the current location information of the UE and the address and tunnel port information of the target base station to the C-GW.
  • the C-GW determines the target U-GW and forwards the U-GW.
  • the C-GW may determine the target U-GW and the forwarding U-GW according to the current location information of the UE. For specific implementation, refer to step S304 of the embodiment shown in FIG. Let me repeat.
  • the C-GW sends a data forwarding tunnel establishment request to the forwarding U-GW.
  • the forwarding U-GW returns a data forwarding tunnel establishment response to the C-GW.
  • the C-GW sends a data forwarding tunnel establishment request to the source U-GW.
  • the source U-GW returns a data forwarding tunnel establishment response to the C-GW.
  • a data forwarding tunnel is established between the source U-GW and the forwarding U-GW.
  • steps S807-S811 For the specific implementation of the steps S807-S811, reference may be made to the steps S309-S313 of the embodiment shown in FIG. 3, and details are not described herein again.
  • the C-GW replies to the MME to modify the bearer response.
  • the C-GW replies with the modify bearer response message to the MME, and sends the determined forwarding U-GW address and tunnel port information to the MME.
  • the MME may reply to modify the access bearer response message to the MME, and carry the address of the forwarding U-GW and the tunnel port information.
  • the MME sends a UE context modification request to the target base station.
  • the MME sends a UE Context Modification Request message to the target base station, and carries the address of the U-GW and the tunnel port information in the message, so that the subsequent uplink user plane data transmission path is switched to the forwarding U-GW. It should be noted that this step is It is a new step for an existing location update process or business request process.
  • the target base station replies to the MME with a UE context modification response message.
  • the target base station replies to the MME with a UE Context Modification Response (UE Context Modification Response) message.
  • UE Context Modification Response UE Context Modification Response
  • the uplink/downlink user plane data transmission path becomes: UE—target base station—forwarding the U-GW—the source U-GW, that is, the transmission shown by the broken lines L1f, L2f, and L3f in FIG. path.
  • UE target base station
  • forwarding the U-GW the source U-GW, that is, the transmission shown by the broken lines L1f, L2f, and L3f in FIG. path.
  • the uplink/downlink user plane data transmission path passes through the source U-GW, but considering that both the source U-GW and the forwarding U-GW have moved down to a position closer to the UE, the source U- The distance between the GW and the forwarding U-GW will also be very close, so that the RTT of the user plane data is not significantly increased.
  • the path of the data forwarding tunnel passes through all the forwarding U-GWs, for example, if the forwarding U-DW includes the target forwarding U-DW and When the source forwards the U-DW, the transmission path becomes: UE—target base station—target forwarding U-GW—source forwarding U-GW—source U-GW.
  • the C-GW determines to forward the U-GW according to the current location information of the UE, and establishes a data forwarding tunnel between the source U-GW and the forwarding U-GW to ensure continuity of services during the UE mobility process. Guarantee the user's business experience.
  • FIG. 9 is a flow chart of another method for maintaining business continuity in an embodiment of the present invention.
  • the method of Figure 9 is performed by a target mobility management network element.
  • the method includes:
  • the target mobility management network element receives a forwarding relocation request sent by the source mobility management network element of the serving UE.
  • the forwarding relocation request carries current location information of the UE.
  • step 901 For specific implementation of step 901, reference may be made to step 503 of FIG. 5 or step 603 of FIG.
  • the moved location area exceeds the service range of the source mobility management network element (for example, the MME).
  • the source mobility management network element is a serving mobility management network element before the UE moves to the current location area.
  • the target mobility management network element selects a target C-GW of the UE according to current location information of the UE.
  • step 902 For a specific implementation of step 902, reference may be made to step 504 of FIG. 5 or step 604 of FIG.
  • the target mobility management network element sends the current location information of the UE to the target C-GW, so that the target C-GW determines the forwarding U-GW of the UE according to the current location information of the UE.
  • step 902 For specific implementation of step 902, reference may be made to step 509 of FIG. 5 or step 609 of FIG.
  • the target mobility management network element sends a data forwarding tunnel establishment request to the target C-GW.
  • the data forwarding tunnel establishment request is used to request the target control plane gateway between the forwarding U-GW and the source U-GW serving the user equipment, and the forwarding U-GW and the target base station serving the user equipment. Establish a data forwarding tunnel for the user equipment.
  • step 904 For a specific implementation of step 904, reference may be made to step 514 of FIG. 5 or step 616 of FIG.
  • the target mobility management network element determines the target C-GW of the UE according to the current location information of the UE, and then passes the target C-GW to the source U- A data forwarding tunnel is established between the GW and the target base station of the UE for the UE, thereby ensuring service continuity in the UE mobile process and improving the service experience of the user.
  • the target C-GW is different from the serving C-GW before the UE moves to the current location area (ie, the serving C-GW changes during UE moving).
  • the method may further include: the target mobility management network element sends a change notification message to the source mobility management network element, where the change notification message is used to indicate the serving C-GW of the UE Change to the target C-GW.
  • the target mobility management network element sends a change notification message to the source mobility management network element, where the change notification message is used to indicate the serving C-GW of the UE Change to the target C-GW.
  • the method may further include: the target mobility management network element receiving the acknowledgement message sent by the source mobility management network element according to the change notification message, where the acknowledgement message carries the source U-GW of the UE Routing information.
  • the target mobility management network element receiving the acknowledgement message sent by the source mobility management network element according to the change notification message, where the acknowledgement message carries the source U-GW of the UE Routing information.
  • FIG. 10 is a flow chart of still another method for maintaining business continuity according to an embodiment of the present invention.
  • the method of Figure 10 is performed by the C-GW.
  • the method includes:
  • the C-GW receives current location information of the UE sent by the mobility management network element.
  • the connected state UE moves in the location of the user plane data transmission, and the moved location area exceeds the service range of the source base station. After the source base station senses that the UE moves out of its service range, it decides to initiate the connection state user plane data service switching. Process.
  • the source base station is a serving base station before the UE moves to the current location area.
  • the idle state UE removes the currently registered location area when the uplink user plane data transmission needs to be sent, such as the currently registered tracking domain (TA), UE Initiate a location update process, such as a Tracking Area Update (TAU) process.
  • TA tracking domain
  • TAU Tracking Area Update
  • the UE When the idle state UE needs to transmit the uplink user plane data transmission, the UE removes the service area of the current serving base station but does not remove the currently registered location area, such as the currently registered Tracking Area (TA), and the UE initiates a service request. (Service Request) process.
  • TA Tracking Area
  • the mobility management network element may send a service switching notification to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element may send the service switching notification by using an existing message, such as a Create Session Request message or a Modify Bearer Request message or modify an access bearer request (Modify).
  • An access bearers request message or the like; or the mobile management network element may send the service switching notification by using a newly created message, and specifically use which message to send the service switching notification, which is not limited by the present invention.
  • the mobility management network element may send a request message to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element may send the request message by using an existing message, such as a Create Session Request message or a Modify Bearer Request message or modify an access bearer request (Modify Access).
  • the bearer request message may be sent by the mobile management network element by using a newly created message, and which message is used to send the request message, which is not limited by the present invention.
  • the mobility management network element may send a request message to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element may send the request message by using an existing message, such as a Create Session Request message or a Modify Bearer Request message or modify an access bearer request (Modify Access).
  • the bearer request message may be sent by the mobile management network element by using a newly created message, and which message is used to send the request message, which is not limited by the present invention.
  • the C-GW is the C-GW serving the UE.
  • the mobility management network element is a mobility management network element serving the UE.
  • the mobility management network element may be an MME or other network element entity having a mobility management function of the MME.
  • the C-GW selects a target U-GW for the UE according to current location information of the UE.
  • the C-GW sends a request message to the mobility management network element.
  • the request message is used to request the mobility management network element to release the first bearer context and instruct the UE to send a second bearer context setup request, where the first bearer context is the UE established on the source U-GW of the UE. a bearer context, where the second bearer context is a bearer context that is reconstructed by the UE on the target U-GW according to the first bearer context.
  • the request message is a delete bearer request message, where the delete bearer request message carries a reactivation request indication, where the reactivation request indication is used to indicate, by the mobility management network element, that the UE is in the first bearer After the context is deleted, the establishment request of the second bearer context is initiated.
  • both the MME and the UE record the first bearer context established by the UE on the source U-GW.
  • the MME receives the delete bearer request message
  • the MME deletes the first bearer context on the MME and instructs the UE to delete the UE.
  • the first bearer context when the delete bearer request message carries the reactivation request indication, the MME further sends a reactivation request indication to the UE, instructing the UE to retransmit the bearer context according to the content of the first bearer context after deleting the first bearer context Request, request to establish a second bearer context.
  • the second bearer context is a bearer context established on the target U-GW according to the first bearer context.
  • the second bearer context includes an access network name (APN) that is the same as the first bearer context. ).
  • APN access network name
  • the C-GW determines the serving U-GW of the UE according to the current location information of the UE, and triggers the bearer context deactivation process, and carries the re
  • the activation request indication is used to instruct the UE to initiate the re-establishment process of the bearer context, to implement the re-establishment of the bearer resource on the target U-GW, and to ensure the service continuity of the subsequent user number transmission, thereby ensuring the user service experience.
  • FIG. 11 is still another flow chart of interaction for maintaining business continuity according to an embodiment of the present invention.
  • the target base station is a serving base station in which the UE is switched from the idle state to the connected state in the current location area.
  • the target U-GW is a serving U-GW in which the UE is switched from the idle state to the connected state in the current location area
  • the MME is the serving MME in which the UE is switched from the idle state to the connected state in the current location area
  • the C-GW is the current UE.
  • the location area is changed from the idle state to the connected service C-GW.
  • S1101 The UE sends a signaling request to the MME.
  • the UE in the idle state sends signaling to the MME requesting to transition to the connected state because it needs to perform uplink signaling or data transmission.
  • the UE initiates a Service Request process or a Tracking Area Update (TAU) process to implement a transition from an idle state to a connected state.
  • TAU Tracking Area Update
  • the target base station that is, the current serving base station of the UE, reports the current location information of the UE to the current serving MME, and the current location information of the UE may be the current tracking domain identifier (Tracking Area Identity, TAI) and/or current Cell Identity (CI).
  • TAI Track Area Identity
  • CI Current Cell Identity
  • S1102 The MME sends a location update notification message to the C-GW.
  • the MME After receiving the signaling request from the idle state to the connection state, the MME, after receiving the service request (Service Request) message or the TAU request message, determines whether the location of the UE has occurred according to the current location information of the UE reported by the base station. Variety.
  • the MME sends a Location Update Notification message to the C-GW of the UE.
  • the MME determines that the location change of the UE may include the following two scenarios:
  • the MME may determine the location change of the UE by comparing the previously stored location information of the UE with the current location information reported by the target base station;
  • the new MME may consider that the UE location has changed.
  • the MME sends a location update notification message to the serving C-GW, where the notification message carries the current location information of the UE, including the current TAI and/or the current cell identity.
  • the location update notification message is intended to notify the C-GW that the current location area of the UE has changed, so the MME can reuse existing messages, such as a Create Session Request message or a Modify Bearer Request message. Or modify the access bearer request (Modify Access Bearers Request) message, etc., to carry the current location information of the UE; or re-defining the new message to carry the current location information of the UE, which is not limited by the present invention.
  • the MME may determine, according to the current location information of the UE, whether the serving C-GW of the UE needs to be re-allocated, that is, whether the UE removes the service area of the current serving C-GW. If the serving C-GW needs to be re-allocated, the MME selects a new C-GW according to the current location information of the UE. As a serving C-GW, a location update notification message is sent to the new C-GW. Necessarily, the MME may also request the new C-GW to re-establish the bearer context for the UE.
  • the C-GW determines the U-GW.
  • the C-GW determines whether the serving U-GW of the current UE needs to be re-allocated according to the current location information of the UE. If re-allocation is required, the C-GW selects an appropriate target U-GW according to the current location information of the UE, and performs step S1104. If the C-GW is reassigned in S1102, the service U-GW also needs to be reallocated.
  • S1104 The C-GW sends a bearer deletion request to the MME.
  • the C-GW sends a bearer deletion request to the MME to initiate a bearer deactivation procedure to the UE to release all bearer context resources established by the UE on the source U-GW.
  • the delete bearer request message carries a reactivation request indication, and is intended to request the UE to initiate a packet data network (PDN) connection establishment request immediately after deleting all bearer context resources of the source D-GW. Realize the reconstruction of the user plane bearer resources in the target D-GW.
  • PDN packet data network
  • S1105 The MME sends a detach request or a deactivate bearer context request to the UE.
  • the MME After receiving the bearer deletion request of the C-GW, the MME performs different actions according to the current packet data of the UE (Packet Data Network, PDN):
  • the MME initiates a separation process to the UE, and carries a re-attach required indication in the Detach Request;
  • the MME initiates a PDN connection deactivation procedure to the UE, and carries a Reactivation requested indication in the Deactivate Bearer Context Request.
  • S1106 The UE initiates a PDN connection establishment request.
  • the UE initiates a PDN connection establishment request to restore the bearer context that the C-GW requests to delete in step S1104.
  • the PDN connection setup request carries the same APN as the bearer context requested by the C-GW in step S1104.
  • C- The GW uses the selected target D-GW to establish the bearer context of the UE.
  • the attaching process is initiated, and the PDN connection establishing process is carried in the attaching process.
  • the attaching process is initiated, and the PDN connection establishing process is carried in the attaching process.
  • step S1105 If the UE receives the deactivated bearer context request to deactivate a PDN connection in step S1105, a separate PDN connection establishment procedure is initiated, and the specific implementation may refer to the prior art.
  • the uplink/downlink user plane data transmission path becomes: UE_ ⁇
  • the target base station - the target U-GW that is, the transmission path indicated by the broken lines L1g and L2g in FIG.
  • the C-GW determines, according to the current location information of the UE, whether the service U-GW needs to be changed and triggers the PDN connection deactivation process and carries the re
  • the activation request indication is used to request the UE to initiate the PDN connection re-establishment process, and the bearer resource is re-established on the target U-GW to ensure the service continuity of the subsequent user number transmission, thereby ensuring the user service experience.
  • FIG. 12 is a schematic structural diagram of a control plane gateway 1200 according to an embodiment of the present invention.
  • the control plane gateway 1200 can include a receiving unit 1201, a selecting unit 1202, and a tunnel establishing unit 1203, wherein
  • the receiving unit 1201 is configured to receive current location information of the UE that is sent by the mobility management network element.
  • the selecting unit 1202 is configured to select at least one forwarding U-GW for the UE according to the current location information of the UE.
  • the current location area of the UE exceeds the service range of the current serving U-GW of the UE, and the C-GW needs to select a suitable forwarding U-GW for the UE according to the current location area of the UE.
  • a tunnel establishing unit 1203 configured to establish a data forwarding tunnel between the source U-GW serving the UE and the forwarding U-GW, and the forwarding U-GW and the target base station of the UE, where The data forwarding tunnel is configured to transmit uplink user plane data and/or downlink user plane data of the UE during the mobile process of the UE.
  • the mobility management network element may send a service switching notification to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element may send the service switching notification by using an existing message, such as a Create Session Request message or a Modify Bearer Request message or modify an access bearer request (Modify).
  • An access bearers request message or the like; or the mobile management network element may send the service switching notification by using a newly created message, and specifically use which message to send the service switching notification, which is not limited by the present invention.
  • the mobility management network element may send a request message to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element can use existing messages to send Sending the request message, for example, a Create Session Request message or a Modify Bearer Request message or a Modify Access Bearers Request message; or the mobile management network element can use the newly created message.
  • the request message is sent, and the specific message is used to send the request message, which is not limited by the present invention.
  • the mobility management network element may send a request message to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element may send the request message by using an existing message, such as a Create Session Request message or a Modify Bearer Request message or modify an access bearer request (Modify Access).
  • the bearer request message may be sent by the mobile management network element by using a newly created message, and which message is used to send the request message, which is not limited by the present invention.
  • the current location information of the UE includes the Tracking Area Identity (TAI) corresponding to the current location area of the UE and/or the serving base station information corresponding to the current location area of the UE.
  • TAI Tracking Area Identity
  • the UE moves to the TAI corresponding to the current location area, that is, the target TAI of the UE; the UE moves to the serving base station information corresponding to the current location area, that is, the target base station information of the UE.
  • the target base station information may be a target base station identity (ID), a target cell identity (Cell Identity, CI), and the like.
  • the current location area of the UE which is also referred to as the target location area of the UE, that is, the location area where the UE moves out of the service range of the source serving base station, similarly, the current location information of the UE, also referred to as the UE target. location information.
  • the mobile process of the UE includes the processes that occur in the foregoing three application scenarios, specifically: the service switching process in the application scenario (1), the location update process in the application scenario (2), and the application scenario (3).
  • Business request process is the process that occur in the foregoing three application scenarios, specifically: the service switching process in the application scenario (1), the location update process in the application scenario (2), and the application scenario (3).
  • the target base station of the UE refers to a base station that provides access services for the UE after the UE moves to the current location area.
  • the data forwarding tunnel is implemented by establishing a user plane bearer context between the source U-GW serving the UE and the forwarding U-GW, and forwarding the U-GW and the target base station of the UE, the user
  • the bearer bearer context includes the routing information required to forward the user plane data.
  • the user plane bearer context established on the source U-GW includes the routing information of the forwarding U-GW and the routing information of the source base station serving the UE.
  • the user plane bearer context established on the forwarding U-GW includes routing information of the source U-GW and routing information of the target base station, and the target base station
  • the user plane bearer context established on the uplink includes the routing information of the forwarding U-GW.
  • the routing information may include an address (typically an Internet Protocol (IP) address) and tunnel port information (typically, if a GPRS Tunneling Protocol (GTP) protocol is used, the tunnel port information is GTP tunnel port identifier (TEID)).
  • IP Internet Protocol
  • GTP GPRS Tunnel
  • the forwarding U-GW refers to at least one forwarding U-GW selected by the selecting unit 1202.
  • the tunnel establishing unit 1203 establishes a data forwarding tunnel for the UE between the source U-GW serving the UE and the forwarding U-GW, and the forwarding U-GW and the target base station of the UE, which is a tunnel establishing unit.
  • the communication path formed by the source U-GW, the at least one forwarding U-GW, and the target base station establishes a data forwarding tunnel between the two network elements from the source C-GW to the target base station.
  • control plane gateway 1200 determines an appropriate forwarding U-GW for the UE according to the current location information after the UE moves, establishes a forwarding U-GW and the source U-GW, and forwards the U-GW and the UE.
  • the data forwarding tunnel between the target base stations can ensure the continuity of the service during the UE mobile process and improve the user's service experience.
  • control plane gateway may further include a transmitting unit 1204.
  • the at least one forwarding U-GW is a first U-GW, where the control plane gateway is a serving control plane gateway after the UE moves to a current location area, and the control plane gateway and the UE The service control plane gateway before moving to the current location area is the same, and the mobility management network element is a service mobility management network element after the UE moves to the current location area;
  • the receiving unit 1201 is further configured to receive a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the UE;
  • the tunnel establishing unit 1203 is specifically configured to send a second request to the first U-GW by using the sending unit 1204, and send a third request to the source U-GW by using the sending unit 1204, where the second request is used for the request.
  • the first U-GW establishes a data forwarding tunnel between the first U-GW and the target base station, and a data forwarding tunnel between the first U-GW and the source U-GW, where the second request carries the data
  • the routing information of the target base station and the routing information of the source U-GW, the third request is used to request the source U-GW to establish a data forwarding tunnel between the source U-GW and the first U-GW, where the The third request carries the routing information of the first U-GW.
  • control plane gateway 1200 is the same as the serving C-GW before the UE moves to the current location area, that is, the serving C-GW does not change during the UE mobile process. It should be understood that This embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area, or may be the same. different.
  • control plane gateway 1200 also receives a second response sent by the first U-GW according to the second request, and a third response sent by the source U-GW according to the third request.
  • the second response is used to confirm that the first U-GW allows to establish a data forwarding tunnel between the first U-GW and the target base station, and data forwarding between the first U-GW and the source U-GW.
  • a tunnel optionally, the second response may carry routing information of the first U-GW, such as an IP address and TEID information;
  • the third response is used to confirm that the source U-GW allows the source U-GW to be established and the A data forwarding tunnel between the first U-GWs.
  • the control plane gateway 1200 can send a first response to the first request to the mobility management network element.
  • an existing message may be used, such as creating an Indirect Data Forwarding Tunnel Request, or using a newly defined message.
  • the first response, the second response, or the third response may use an existing message, such as Create Indirect Data Forwarding Tunnel Response (The newly defined message can also be used, which is not limited by the present invention.
  • the at least one forwarding U-GW includes a first U-GW and a second U-GW, where the control plane gateway is a serving control plane gateway after the UE moves to a current location area, and The control plane gateway is the same as the service control plane gateway before the UE moves to the current location area, the mobility management network element is a serving mobility management network element after the UE moves to the current location area, and the mobility management network element and the UE The service mobility management network elements before moving to the current location area are the same or different;
  • the receiving unit 1201 is further configured to receive a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the UE;
  • the tunnel establishing unit 1203 is specifically configured to: send a second request to the second U-GW by using the sending unit 1204, and send a third request to the third U-GW by using the sending unit 1204, and send the third request to the source U through the sending unit 1204.
  • the GW sends a fourth request, where the second request is used to request the second U-GW to establish a data forwarding tunnel between the second U-GW and the target base station, and the second U-GW and the second a data forwarding tunnel between the three U-GWs, the second request carrying routing information of the target base station, and routing information of the third U-GW, the third request is used to request the third
  • the U-GW establishes a data forwarding tunnel between the third U-GW and the second U-GW, and a data forwarding tunnel between the third U-GW and the source U-GW, where the third request carries the data
  • the fourth request is used to request the source U-GW to establish a data forwarding tunnel between the source U-GW and the third U-GW.
  • the fourth request carries routing information of the third U-GW.
  • the C-GW is the same as the serving C-GW before the UE moves to the current location area, that is, the serving C-GW does not change during the UE mobile process. It should be understood that the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • control plane gateway 1200 also receives a second response sent by the second U-GW according to the second request, a third response sent by the third U-GW according to the third request, and the source U-GW sends according to the fourth request.
  • the second response is used to confirm that the second U-GW allows to establish a data forwarding tunnel between the second U-GW and the target base station, and data between the second U-GW and the third U-GW.
  • Forwarding the tunnel optionally, the second response may carry routing information of the second U-GW, such as an IP address and TEID information;
  • the third response is used to confirm the third U-GW and the second U-GW And a data forwarding tunnel between the third U-GW and the source U-GW.
  • the third response may carry routing information of the third U-GW, such as an IP address. And the TEID information; the fourth response is used to confirm that the source U-GW allows to establish a data forwarding tunnel between the source U-GW and the third U-GW.
  • the control plane gateway 1200 can send the first response of the first request to the mobility management network element.
  • first request, the second request, the third request, or the fourth request in this implementation may use an existing message, such as Create Indirect Data Forwarding Tunnel Request, or may be used.
  • the newly defined message is not limited by the present invention; further, the first response, the second response, the third response, or the fourth response in the implementation may use an existing message, such as creating an indirect data forwarding tunnel response ( A newly defined message may also be used, which is not limited by the present invention.
  • the at least one forwarding U-GW is a first U-GW
  • the control plane gateway is a serving control plane gateway after the UE moves to a current location area
  • the control The face gateway is different from the service control plane gateway before the UE moves to the current location area
  • the mobility management network element is a serving mobility management network element after the UE moves to the current location area, and the mobility management network element moves to the UE with the UE
  • the service mobility management network elements before the current location area are the same or different;
  • the receiving unit 1201 is further configured to receive routing information of the source U-GW of the UE;
  • the receiving unit 1201 is further configured to receive a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the UE;
  • the tunnel establishing unit 1203 is specifically configured to: send, by the sending unit 1204, a second request to the first U-GW, where the second request is used to request the first U-GW to establish the first U-GW and the target base station.
  • the C-GW is different from the serving C-GW before the UE moves to the current location area, that is, the serving C-GW changes during the UE mobile process.
  • the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • the control plane gateway 1200 also receives a second response sent by the first U-GW according to the second request, and a third response sent by the source U-GW according to the third request.
  • the second response is used to confirm that the first U-GW allows to establish a data forwarding tunnel between the first U-GW and the target base station, and data forwarding between the first U-GW and the source U-GW.
  • a tunnel optionally, the second response may carry routing information of the first U-GW, such as an IP address and TEID information;
  • the third response is used to confirm that the source U-GW allows the source U-GW to be established and the A data forwarding tunnel between the first U-GWs.
  • the control plane gateway 1200 can send a first response to the first request to the mobility management network element.
  • the C-GW is the target C-GW, that is, the UE moves to the serving C-GW after the current location area.
  • the target C-GW should also send the data forwarding tunnel establishment request to the source U-GW through the mobility management network element, and send the routing information of the first U-GW to the source U-GW.
  • the source C-GW is a serving C-GW before the UE moves to the current location area
  • the source U-GW is a serving U-GW before the UE moves to the current location area.
  • an existing message may be used.
  • the Create Indirect Data Forwarding Tunnel Request may be used, and the newly defined message may also be used.
  • the present invention does not limit this; further, the first response or the second response in this implementation may be used.
  • the message, such as the Create Indirect Data Forwarding Tunnel Response may also use a newly defined message, which is not limited by the present invention.
  • the at least one forwarding U-GW includes a first U-GW and a second U-GW, where the control plane gateway is a serving control plane gateway after the UE moves to a current location area, and The control plane gateway is different from the serving control plane gateway before the UE moves to the current location area, where the mobility management network element is a serving mobility management network element after the UE moves to the current location area, and the mobility management network element and the UE
  • the service mobility management network elements before moving to the current location area are the same or different;
  • the receiving unit 1201 is further configured to receive routing information of the source U-GW of the UE;
  • the receiving unit 1201 is further configured to receive a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the UE;
  • the tunnel establishing unit 1203 is specifically configured to send a second request to the second U-GW by using the sending unit 1204, and send a third request to the third U-GW by using the sending unit 1204, where the second request is used for the request.
  • the second U-GW establishes a data forwarding tunnel between the second U-GW and the target base station, and a data forwarding tunnel between the second U-GW and the third U-GW, where the second request carries The routing information of the target base station, and the routing information of the third U-GW, the third request is used to request the third U-GW to establish a data forwarding tunnel between the third U-GW and the second U-GW.
  • a data forwarding tunnel between the third U-GW and the source U-GW, the third request carrying routing information of the second U-GW, and routing information of the source U-GW.
  • the C-GW is different from the serving C-GW before the UE moves to the current location area, that is, the serving C-GW changes during the UE mobile process.
  • the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • control plane gateway 1200 also receives a second response sent by the second U-GW according to the second request, and a third response sent by the third U-GW according to the third request, and the source U-GW according to the fourth request.
  • the second response is used to confirm that the second U-GW allows to establish a data forwarding tunnel between the second U-GW and the target base station, and the second U-GW and the a data forwarding tunnel between the third U-GW.
  • the second response may carry routing information of the second U-GW, such as an IP address and TEID information, and the source U-GW sends the first request according to the fourth request.
  • the third response is used to confirm a data forwarding tunnel between the third U-GW and the second U-GW, and a data forwarding tunnel between the third U-GW and the source U-GW
  • the third response may carry routing information of the third U-GW, such as an IP address and TEID information, where the fourth response is used to confirm that the source U-GW allows the source U-GW to be established and the third Data forwarding tunnel between U-GWs.
  • the control plane gateway 1200 can send the first response of the first request to the mobility management network element.
  • the serving C-GW of the UE changes during the mobile process
  • the C-GW is the target C-GW, that is, the service after the UE moves to the current location area.
  • C-GW the target C-GW
  • the target C-GW should also send the data forwarding tunnel establishment request to the source U-GW through the mobility management network element, and send the routing information of the third U-GW to the source U-GW.
  • the source C-GW is a serving C-GW before the UE moves to the current location area
  • the source U-GW is a serving U-GW before the UE moves to the current location area.
  • an existing message may be used, such as creating an Indirect Data Forwarding Tunnel Request, or using a newly defined message.
  • the first response, the second response, or the third response may use an existing message, such as Create Indirect Data Forwarding Tunnel Response (The newly defined message can also be used, which is not limited by the present invention.
  • the tunnel establishing unit 1203 is further configured to use the mobility management network element to reach the target.
  • the base station sends routing information of the target U-GW.
  • the tunnel establishing unit 1203 is further configured to use the mobility management network element to reach the target.
  • the base station sends the routing information of the first U-GW.
  • the tunnel establishing unit 1203 is further configured to use the mobile
  • the management network element sends the routing information of the second U-GW to the target base station.
  • the tunnel establishing unit 1203 is further configured to send a setup session request to the target U-GW, where the setup session request is used in the directory.
  • a bearer context required for user plane data transmission is created on the U-GW, and each of the established bearer contexts includes routing information of the target U-GW, where the target U-GW is the current location area of the UE.
  • Corresponding service U-GW It can be understood that the target U-GW is generally a serving U-GW that provides an optimal data transmission path for the UE in the current location area.
  • the tunnel establishing unit 1203 is further configured to send routing information of the target U-GW to the target base station by using the mobility management network element.
  • the first U-GW is still the control plane gateway according to the current UE.
  • the location information is the service U-GW selected by the UE. That is, the first U-GW is the target U-GW.
  • the target D-GW can directly communicate with the source D-GW, that is, the target U-GW simultaneously plays the role of the forwarding U-GW. It can be understood that when the target U-GW cannot directly communicate with the source D-GW, the forwarding U-GW selected by the C-GW is different from the target U-GW.
  • the control plane gateway 1200 can also perform the method of FIG. 2 and implement the implementation of the C-GW in the embodiment C-GW and the target C-GW shown in FIG. 2, FIG. 7, and FIG. The functions of the examples are not described herein again.
  • FIG. 14 is a schematic structural diagram of a mobility management network element 1400 according to an embodiment of the present invention.
  • the mobility management network element 1400 can include:
  • the receiving unit 1401 is configured to receive a forwarding relocation request sent by the source mobility management network element serving the UE.
  • the forwarding relocation request carries current location information of the UE.
  • the selecting unit 1402 is configured to select a target C-GW of the UE according to current location information of the UE.
  • the sending unit 1403 is configured to send the current location information of the UE to the target C-GW, so that the target control plane gateway determines the forwarding U-GW of the UE according to the current location information of the UE;
  • the sending unit 1403 is further configured to send a data forwarding tunnel establishment request to the target control plane gateway.
  • the data forwarding tunnel establishment request is used to request the target C-GW to be between the forwarding U-GW and the source U-GW serving the UE, and between the forwarding U-GW and the target base station serving the UE.
  • the UE establishes a data forwarding tunnel.
  • the mobility management network element 1400 determines the target C-GW of the UE according to the current location information of the UE, and then passes the target C-GW to the source U- Establishing a data forwarding tunnel between the GW and the target base station of the UE for the UE, whereby, the business continuity in the UE mobile process can be ensured, and the user's service experience is improved.
  • the target control plane gateway is different from the serving control plane gateway before the UE moves to the current location area (ie, the serving C-GW changes during the UE moving process), and the sending unit 1403 is further configured to perform mobility management to the source.
  • the network element sends a change notification message, and the change notification message is used to indicate that the serving control plane gateway of the UE is changed to the target control plane gateway.
  • the receiving unit 1401 is further configured to receive an acknowledgment message sent by the source mobility management network element according to the change notification message, where the acknowledgment message carries routing information of the source U-GW of the UE.
  • the mobile management network element 1400 can also perform the method of FIG. 9 and implement the functions of the target MME in the embodiment shown in FIG. 5 and FIG.
  • FIG. 15 is a schematic structural diagram of a control plane gateway 1500 according to an embodiment of the present invention.
  • the control plane gateway 1500 includes:
  • the receiving unit 1501 is configured to receive current location information of the UE that is sent by the mobility management network element.
  • the selecting unit 1502 is configured to select a target U-GW for the UE according to the current location information of the UE.
  • the sending unit 1503 is configured to send a request message to the mobility management network element.
  • the request message is used to request the mobility management network element to release the first bearer context and instruct the UE to send a second bearer context setup request, where the first bearer context is the UE established on the source U-GW of the UE. a bearer context, where the second bearer context is a bearer context that is reconstructed by the UE on the target U-GW according to the first bearer context.
  • the location update notification message is intended to notify the C-GW that the current location area of the UE has changed, and the location update notification may reuse an existing message, such as a Create Session Request.
  • the message or the Modify Bearer Request message may also be redefined, and the present invention is not limited thereto.
  • the control plane gateway 1500 determines, according to the current location information of the UE, whether the service U-GW needs to be changed and triggers the bearer context deactivation process and carries the re
  • the activation request indication is used to request the UE to initiate the bearer context re-establishment process, and the bearer resource is reconstructed on the target U-GW to ensure the service continuity of the subsequent user number transmission, thereby ensuring the user service experience.
  • the request message is a delete bearer request message, where the delete bearer request message carries a reactivation request indication, where the reactivation request indication is used to indicate, by the mobility management network element, that the UE is in the first bearer After the context is deleted, the establishment of the second bearer context is initiated. Make a request.
  • both the MME and the UE record the first bearer context established by the UE on the source U-GW.
  • the MME receives the delete bearer request message
  • the MME deletes the first bearer context on the MME and instructs the UE to delete the UE.
  • the first bearer context when the delete bearer request message carries the reactivation request indication, the MME further sends a reactivation request indication to the UE, indicating that the UE retransmits the bearer context establishment based on the content of the first bearer context after deleting the first bearer context Request, request to establish a second bearer context.
  • the second bearer context is a bearer context established on the target U-GW based on the first bearer context.
  • the control plane gateway 1500 can also perform the method of FIG. 10 and implement the functions of the C-GW in the embodiment shown in FIG.
  • FIG. 16 is a schematic structural diagram of a control plane gateway 1600 according to an embodiment of the present invention.
  • Control plane gateway 1600 can include a processor 1602, a memory 1603, a transmitter 1601, and a receiver 1604. In a particular application, the control plane gateway 1600 can be, etc.
  • Bus 1606 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 16, but it does not mean that there is only one bus or one type of bus.
  • transmitter 1601 and receiver 1604 can be coupled to antenna 1605.
  • the memory 1603 is for storing a program.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 1603 can include read only memory and random access memory and provides instructions and data to the processor 1602.
  • the memory 1603 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • the processor 1602 executes the program stored in the memory 1603 and is specifically configured to perform the following operations:
  • the tunnel is used to transmit uplink user plane data and/or downlink user plane data of the UE during the mobile process of the UE.
  • the mobility management network element may send a service switching notification to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element may send the service switching notification by using an existing message, such as a Create Session Request message or a Modify Bearer Request message or modify an access bearer request (Modify).
  • An access bearers request message or the like; or the mobile management network element may send the service switching notification by using a newly created message, and specifically use which message to send the service switching notification, which is not limited by the present invention.
  • the mobility management network element may send a request message to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element may send the request message by using an existing message, such as a Create Session Request message or a Modify Bearer Request message or modify an access bearer request (Modify Access).
  • the bearer request message may be sent by the mobile management network element by using a newly created message, and which message is used to send the request message, which is not limited by the present invention.
  • the mobility management network element may send a request message to the serving C-GW of the UE.
  • the mobility management network element may be an MME or other network element having a mobility management function of the MME.
  • the mobility management network element may send the request message by using an existing message, such as a Create Session Request message or a Modify Bearer Request message or modify an access bearer request (Modify Access).
  • the bearer request message may be sent by the mobile management network element by using a newly created message, and which message is used to send the request message, which is not limited by the present invention.
  • the current location information of the UE includes the Tracking Area Identity (TAI) corresponding to the current location area of the UE and/or the serving base station information corresponding to the current location area of the UE.
  • TAI Tracking Area Identity
  • the UE moves to the TAI corresponding to the current location area, that is, the target TAI of the UE; the UE moves to the serving base station information corresponding to the current location area, that is, the target base station information of the UE.
  • the target base station information may be a target base station identity (ID), a target cell identity (Cell Identity, CI), and the like. It can be understood that the current location area of the UE, also referred to as the target location area of the UE, That is, the location area where the UE moves out of the service range of the source serving base station. Similarly, the current location information of the UE is also referred to as the target location information of the UE.
  • the mobile process of the UE includes the processes that occur in the foregoing three application scenarios, specifically: the service switching process in the application scenario (1), the location update process in the application scenario (2), and the application scenario (3).
  • Business request process is the process that occur in the foregoing three application scenarios, specifically: the service switching process in the application scenario (1), the location update process in the application scenario (2), and the application scenario (3).
  • the target base station of the UE refers to a base station that provides access services for the UE after the UE moves to the current location area.
  • the data forwarding tunnel is implemented by establishing a user plane bearer context between the source U-GW serving the UE and the forwarding U-GW, and forwarding the U-GW and the target base station of the UE, the user
  • the plane bearer context includes the routing information required to forward the user plane data, including the routing information of the source U-GW, the routing information of the forwarding U-GW, and the routing information of the target base station.
  • the routing information may include an address.
  • IP Internet Protocol
  • GTP GPRS Tunneling Protocol
  • the forwarding U-GW refers to at least one forwarding U-GW selected by the processor 1602.
  • the processor 1602 establishes a data forwarding tunnel for the UE between the source U-GW serving the UE and the forwarding U-GW, and the forwarding U-GW and the target base station of the UE, where the processor 1602 is A communication path formed by the source U-GW, the at least one forwarding U-GW, and the target base station establishes a data forwarding tunnel between the two network elements from the source C-GW to the target base station.
  • the method performed by the C-GW disclosed in any of the embodiments of the present invention, or the target C-GW disclosed in any of the embodiments of FIG. 5, may be applied to the processor 1602, or by the processor. 1602 implementation.
  • the processor 1602 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1602 or an instruction in a form of software.
  • the processor 1602 may be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP for short, etc.; or a digital signal processor (DSP), an application specific integrated circuit.
  • ASIC application-the-shelf programmable gate array
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in connection with the embodiments of the present invention may be Directly implemented as a hardware decoding processor, or with a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1603, and the processor 1602 reads the information in the memory 1603 and completes the steps of the above method in combination with its hardware.
  • control plane gateway 1600 determines an appropriate forwarding U-GW for the UE according to the current location information of the UE, and establishes a forwarding U-GW and the source U-GW, and forwards the U-GW and the UE.
  • the data forwarding tunnel between the target base stations can ensure the continuity of the service during the UE mobile process and improve the user's service experience.
  • the at least one forwarding U-GW is a first U-GW, where the control plane gateway is a serving control plane gateway after the UE moves to a current location area, and the control plane gateway and the UE
  • the service control plane gateway before moving to the current location area is the same
  • the mobility management network element is the serving mobility management network element after the UE moves to the current location area, and the mobility management network element and the UE move before the current location area
  • the service mobility management network element is the same or different;
  • the processor 1602 is further configured to receive, by the receiver 1604, a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the UE;
  • the processor 1602 is specifically configured to:
  • control plane gateway 1600 is the same as the serving C-GW before the UE moves to the current location area, that is, the serving C-GW does not change during the UE mobile process. It should be understood that the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • control plane gateway 1600 also receives a second response sent by the first U-GW according to the second request, and a third response sent by the source U-GW according to the third request.
  • the second response is used to confirm that the first U-GW allows to establish a data forwarding tunnel between the first U-GW and the target base station, and data forwarding between the first U-GW and the source U-GW.
  • a tunnel optionally, the second response may carry routing information of the first U-GW, such as an IP address and TEID information;
  • the third response is used to confirm that the source U-GW allows the source U-GW to be established and the A data forwarding tunnel between the first U-GWs.
  • the control plane gateway 1600 can send a first response to the first request to the mobility management network element.
  • an existing message may be used, such as creating an Indirect Data Forwarding Tunnel Request, or using a newly defined message.
  • the first response, the second response, or the third response may use an existing message, such as Create Indirect Data Forwarding Tunnel Response (The newly defined message can also be used, which is not limited by the present invention.
  • the at least one forwarding U-GW includes a first U-GW and a second U-GW, where the control plane gateway is a serving control plane gateway after the UE moves to a current location area, and The control plane gateway is the same as the service control plane gateway before the UE moves to the current location area, the mobility management network element is a serving mobility management network element after the UE moves to the current location area, and the mobility management network element and the UE The service mobility management network elements before moving to the current location area are the same or different;
  • the processor 1602 is further configured to receive, by the receiver 1604, a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the UE;
  • the processor 1602 is specifically configured to:
  • the second request is used to request the second U-GW to establish a data forwarding tunnel between the second U-GW and the target base station, and data between the second U-GW and the third U-GW.
  • the second request carries the routing information of the target base station, and the routing information of the third U-GW, where the third request is used to request the third U-GW to establish the third U-GW and the second a data forwarding tunnel between the U-GW and a data forwarding tunnel between the third U-GW and the source U-GW, the third request carrying routing information of the second U-GW, and the source U- Routing information of the GW, the fourth request is used to request the source U-GW to establish a data forwarding tunnel between the source U-GW and the third U-GW, and the fourth request carries the route of the third U-GW information.
  • control plane gateway 1600 is the same as the serving C-GW before the UE moves to the current location area, that is, the serving C-GW does not change during the UE mobile process. It should be understood that the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • control plane gateway 1600 also receives a second response sent by the second U-GW according to the second request, a third response sent by the third U-GW according to the third request, and the source U-GW sends according to the fourth request.
  • the second response is used to confirm that the second U-GW allows to establish a data forwarding tunnel between the second U-GW and the target base station, and data between the second U-GW and the third U-GW. Forwarding the tunnel, optionally, the second response may carry routing information of the second U-GW, such as an IP address and TEID information; the third response is used to confirm the third U-GW and the second U-GW And a data forwarding tunnel between the third U-GW and the source U-GW.
  • the third response may carry routing information of the third U-GW, such as an IP address. And the TEID information; the fourth response is used to confirm that the source U-GW allows to establish a data forwarding tunnel between the source U-GW and the third U-GW.
  • the control plane gateway 1600 can send the first response of the first request to the mobility management network element.
  • first request, the second request, the third request, or the fourth request in this implementation may use an existing message, such as Create Indirect Data Forwarding Tunnel Request, or may be used.
  • the newly defined message is not limited by the present invention; further, the first response, the second response, the third response, or the fourth response in the implementation may use an existing message, such as creating an indirect data forwarding tunnel response ( A newly defined message may also be used, which is not limited by the present invention.
  • the at least one forwarding U-GW is a first U-GW, where the control plane gateway is a serving control plane gateway after the UE moves to a current location area, and the control plane gateway is different from the control plane gateway.
  • the UE moves to the service control plane gateway before the current location area, the mobile tube
  • the service network element is a serving mobility management network element after the UE moves to the current location area, and the mobility management network element is the same as or different from the service mobility management network element before the UE moves to the current location area;
  • the processor 1602 is further configured to receive, by the receiver 1604, routing information of the source U-GW of the UE;
  • the processor 1602 is further configured to receive, by the receiver 1604, a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the UE;
  • the processor 1602 is specifically configured to:
  • control plane gateway 1600 is different from the serving C-GW before the UE moves to the current location area, that is, the serving C-GW changes during the UE mobile process. It should be understood that the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • the control plane gateway 1600 also receives a second response sent by the first U-GW according to the second request, and a third response sent by the source U-GW according to the third request.
  • the second response is used to confirm that the first U-GW allows to establish a data forwarding tunnel between the first U-GW and the target base station, and data forwarding between the first U-GW and the source U-GW.
  • a tunnel optionally, the second response may carry routing information of the first U-GW, such as an IP address and TEID information;
  • the third response is used to confirm that the source U-GW allows the source U-GW to be established and the A data forwarding tunnel between the first U-GWs.
  • the control plane gateway 1600 can send a first response to the first request to the mobility management network element.
  • the control plane gateway 1600 is the target C-GW, that is, the UE moves to the serving C-GW after the current location area.
  • the processor 1602 should further indicate that the source C-GW sends a data forwarding tunnel establishment request to the source U-GW through the mobility management network element, and sends the routing information of the first U-GW to the source U-GW.
  • the source C-GW is a serving C-GW before the UE moves to the current location area
  • the source U-GW is a serving U-GW before the UE moves to the current location area.
  • an existing message such as a Create Indirect Data Forwarding Tunnel Request
  • a newly defined message may be used.
  • the first response or the second response in this implementation may use an existing message, such as Create Indirect Data Forwarding Tunnel Response, or use a newly defined message.
  • the invention is not limited thereto.
  • the at least one forwarding U-GW includes a first U-GW and a second U-GW, where the control plane gateway is a serving control plane gateway after the UE moves to a current location area, and The control plane gateway is different from the serving control plane gateway before the UE moves to the current location area, where the mobility management network element is a serving mobility management network element after the UE moves to the current location area, and the mobility management network element and the UE
  • the service mobility management network elements before moving to the current location area are the same or different;
  • the processor 1602 is further configured to receive, by the receiver 1604, routing information of the source U-GW of the UE;
  • the processor 1602 is further configured to receive, by the receiver 1604, a first request sent by the mobility management network element, where the first request carries routing information of a target base station of the UE;
  • the processor 1602 is specifically configured to:
  • control plane gateway 1600 is different from the serving C-GW before the UE moves to the current location area, that is, the serving C-GW changes during the UE mobile process. It should be understood that the present embodiment may be applicable to the service mobility management network element changing or not changing the two scenarios during the UE mobile process, that is, the mobility management network element may be the same as the service mobility management network element before the UE moves to the current location area. , can also be different.
  • control plane gateway 1600 also receives a second response sent by the second U-GW according to the second request, and a third response sent by the third U-GW according to the third request, and the source U-GW according to the fourth request.
  • the second response is used to confirm that the second U-GW allows to establish a data forwarding tunnel between the second U-GW and the target base station, and data between the second U-GW and the third U-GW.
  • the second response may carry routing information of the second U-GW, such as an IP address and TEID information, and a fourth response sent by the source U-GW according to the fourth request; the third response is used for Determining a data forwarding tunnel between the third U-GW and the second U-GW, and a data forwarding tunnel between the third U-GW and the source U-GW.
  • the third response may be Carrying the routing information of the third U-GW, such as an IP address and TEID information; the fourth response is used to confirm that the source U-GW allows to establish a data forwarding tunnel between the source U-GW and the third U-GW.
  • the control plane gateway 1600 can send the first response of the first request to the mobility management network element.
  • the control plane gateway 1600 is the target C-GW in this embodiment, that is, the service after the UE moves to the current location area.
  • C-GW the processor 1602 should further indicate that the source C-GW sends a data forwarding tunnel establishment request to the source U-GW through the mobility management network element, and sends the routing information of the third U-GW to the source U-GW.
  • the source C-GW is a serving C-GW before the UE moves to the current location area
  • the source U-GW is a serving U-GW before the UE moves to the current location area.
  • an existing message may be used, such as creating an Indirect Data Forwarding Tunnel Request, or using a newly defined message.
  • the first response, the second response, or the third response may use an existing message, such as Create Indirect Data Forwarding Tunnel Response (The newly defined message can also be used, which is not limited by the present invention.
  • the processor 1602 when the at least one forwarding U-GW is the first U-GW, the processor 1602 is further configured to use the mobile management network element by using the transmitter 1601.
  • the target base station sends routing information of the target U-GW.
  • the processor 1602 when the at least one forwarding U-GW is the first U-GW, the processor 1602 is further configured to send, by the mobility management network element, the target to the target base station. Routing information of the first U-GW.
  • the processor 1602 is further configured to send, by using the mobility management network element, routing information of the second U-GW to the target base station.
  • the processor 1602 is further configured to send, by using the transmitter 1601, a setup session request to the target U-GW, where the setup session request is used in the target U-
  • the bearer context required for the user plane data transmission is created on the GW, and each of the established bearer contexts includes the routing information of the target U-GW, where the target U-GW is a service corresponding to the current location area of the UE.
  • U-GW is generally a serving U-GW that provides an optimal data transmission path for the UE in the current location area.
  • the processor 1602 is further configured to send routing information of the target U-GW to the target base station by using the mobility management network element.
  • the first U-GW is still the current location information of the control plane gateway according to the UE.
  • the target D-GW can directly communicate with the source D-GW, that is, the target U-GW simultaneously plays the role of the forwarding U-GW. It can be understood that when the target U-GW cannot directly communicate with the source D-GW, the forwarding U-GW selected by the C-GW is different from the target U-GW.
  • the control plane gateway 1600 can also perform the method of FIG. 2 and implement the implementation of the C-GW in the embodiment C-GW and the target C-GW shown in FIG. 2, FIG. 7, and FIG. The functions of the examples are not described herein again.
  • FIG. 17 is a schematic structural diagram of a mobility management network element 1700 according to an embodiment of the present invention.
  • the mobility management network element 1700 can include a processor 1702, a memory 1703, a transmitter 1701, and a receiver 1704. In a particular application, the mobility management network element 1700 can be, etc.
  • Bus 1706 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 17, but it does not mean that there is only one bus or one type of bus.
  • transmitter 1701 and receiver 1704 can be coupled to antenna 1705.
  • the memory 1703 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • Memory 1703 can include read only memory and random access memory and provides instructions and data to processor 1702.
  • the memory 1703 may include a high speed RAM memory, and may also include a non-volatile memory, such as at least one Disk storage.
  • the processor 1702 executes the program stored in the memory 1703, and is specifically configured to perform the following operations:
  • the method performed by the mobile management network element disclosed in the embodiment shown in FIG. 9 or the target MME disclosed in the embodiment shown in FIG. 5 and FIG. 6 may be applied to the processor 1702 or implemented by the processor 1702.
  • the processor 1702 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1702 or an instruction in a form of software.
  • the processor 1702 may be a general-purpose processor, including a central processing unit (CPU), a network processor (Network Processor, NP for short, etc.; or a digital signal processor (DSP), an application specific integrated circuit.
  • CPU central processing unit
  • NP Network Processor
  • DSP digital signal processor
  • ASIC application-the-shelf programmable gate array
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1703, and the processor 1702 reads the information in the memory 1703 and completes the steps of the above method in combination with its hardware.
  • the mobility management network element 1700 determines the target C-GW of the UE according to the current location information of the UE, and then passes the target C-GW to the source U- Establishing a data forwarding tunnel between the GW and the target base station of the UE for the UE, whereby, the business continuity in the UE mobile process can be ensured, and the user's service experience is improved.
  • the target control plane gateway is different from the serving control plane gateway before the UE moves to the current location area (ie, the serving C-GW changes during the UE moving), and the processor 1702 is further configured to use the transmitter 1701.
  • the source mobility management network element sends a change notification message, which is used to indicate that the serving control plane gateway of the UE is changed to the target control plane gateway.
  • the processor 1702 is further configured to receive, by the receiver 1704, an acknowledgement message sent by the source mobility management network element according to the change notification message, where the acknowledgement message carries routing information of the source U-GW of the UE.
  • the mobile management network element 1700 can also perform the method of FIG. 9 and implement the functions of the target MME in the embodiment shown in FIG. 5 and FIG.
  • FIG. 18 is a schematic structural diagram of a control plane gateway 1800 according to an embodiment of the present invention.
  • Control plane gateway 1800 can include a processor 1802, a memory 1803, a transmitter 1801, and a receiver 1804. In a particular application, the control plane gateway 1800 can be equal.
  • Receiver 1804, transmitter 1801, processor 1802, and memory 1803 are interconnected by a bus 1806 system.
  • the bus 1806 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 18, but it does not mean that there is only one bus or one type of bus.
  • transmitter 1801 and receiver 1804 can be coupled to antenna 1805.
  • the memory 1803 is configured to store a program.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 1803 can include read only memory and random access memory and provides instructions and data to the processor 1802.
  • the memory 1803 may include a high speed RAM memory and may also include a non-volatile memory such as at least one disk memory.
  • the processor 1802 executes the program stored in the memory 1803, and is specifically configured to perform the following operations:
  • the location update notification message is intended to notify the C-GW that the current location area of the UE has changed, and the location update notification may reuse an existing message, such as a Create Session Request.
  • the message or the Modify Bearer Request message may also be redefined, and the present invention is not limited thereto.
  • the method performed by the C-GW disclosed in any of the embodiments of FIG. 10 and FIG. 11 of the present invention may be applied to the processor 1802 or implemented by the processor 1802.
  • the processor 1802 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1802 or an instruction in a form of software.
  • the processor 1802 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP Processor, etc.), or a digital signal processor (DSP), an application specific integrated circuit. (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1803, and the processor 1802 reads the information in the memory 1803 and completes the steps of the above method in combination with its hardware.
  • the control plane gateway 1800 determines, according to the current location information of the UE, whether the service U-GW needs to be changed and triggers the bearer context deactivation process and carries the re
  • the activation request indication is used to request the UE to initiate the bearer context re-establishment process, and the bearer resource is reconstructed on the target U-GW to ensure the service continuity of the subsequent user number transmission, thereby ensuring the user service experience.
  • the request message is a delete bearer request message, where the delete bearer request message carries a reactivation request indication, where the reactivation request indication is used to indicate, by the mobility management network element, that the UE is in the first bearer After the context is deleted, the establishment request of the second bearer context is initiated.
  • both the MME and the UE record the first bearer context established by the UE on the source U-GW.
  • the MME receives the delete bearer request message
  • the MME deletes the first bearer on the MME.
  • the delete bearer request message carries the reactivation request indication
  • the MME further sends a reactivation request indication to the UE, indicating that the UE is based on the first bearer after deleting the first bearer context
  • the content of the context resends the setup request of the bearer context, requesting to establish a second bearer context.
  • the second bearer context is a bearer context established on the target U-GW based on the first bearer context.
  • the control plane gateway 1800 can also perform the method of FIG. 10 and implement the functions of the C-GW in the embodiment shown in FIG.
  • the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be directed to the embodiments of the present invention.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated in one unit. In the unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing 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. .

Landscapes

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

Abstract

本发明实施例提供了一种保持业务连续性的方法、控制面网关和移动管理网元，该方法包括：C-GW接收移动管理网元发送的UE的当前位置信息；该C-GW根据该UE的当前位置信息为该UE选择至少一个转发D-GW；该C-GW在该UE的源D-GW与该转发D-GW之间，以及该转发D-GW与该UE的目标基站之间，为该UE建立数据转发隧道，其中，该数据转发隧道用于在该UE的移动过程中传输该UE的上行用户面数据和/或下行用户面数据。

Description

保持业务连续性的方法、控制面网关和移动管理网元 技术领域
本发明涉及通信领域，并且更具体地，涉及保持业务连续性的方法、控制面网关和移动管理网元。
背景技术
分布式网关(Distributed Gateway，DGW)架构是基于网络控制面功能与用户面功能分离的思路在已有的演进分组系统(Evolved Packet System，EPS)网络架构上提出的一种增强网络架构。DGW架构中包括控制面网关(Control Plane Gateway，C-GW)与用户面网关(User Plane Gateway，U-GW)。
C-GW是一种集中式控制面网关，可以有两种存在形式：(1)集成了现有3GPP EPS网络中服务网关(Serving Gateway，S-GW)与分组数据网关(Packet Data Network Gateway，P-GW)控制面功能的单一网元；(2)分别实现现有S-GW的控制面功能(Control Plane S-GW)与现有P-GW的控制面功能(Control Plane P-GW)的两个独立网元。C-GW用来专门处理3GPP EPS网络中的控制面信令，包括移动性管理，会话管理，地址管理，路径管理，计费管理等功能。C-GW通过与U-GW之间的交互实现对用户面数据处理的控制与管理。
U-GW是一种分布式用户面网关，对应于C-GW的两种存在形式，U-GW也有两种存在形式：(1)集成了现有3GPP EPS网络中服务网关(Serving Gateway，S-GW)与分组数据网关(Packet Data Network Gateway，P-GW)用户面功能的单一网元；(2)分别实现现有S-GW的用户面功能(User Plane S-GW)与现有P-GW的用户功能(User Plane P-GW)的两个独立网元。U-GW用来专门处理3GPP EPS网络中的用户面数据，包括路由转发、数据包检查、数据包统计以及服务质量执行等功能。U-GW是在C-GW的控制管理下实现对用户面数据的处理。考虑到U-GW可以分布式部署的特性，U-GW也可以称为分布式网关(Distributed Gateway，D-GW)。
现有EPS网络架构中，业务连续性是通过P-GW的锚点功能实现的，即处于连接态进行用户面业务的UE在移动过程中，其用户面数据总是通过当 前的P-GW实现与外部数据网络的交互。由于移动过程中P-GW没有改变，从而保证用户面IP地址不变，进而保证了用户面业务的连续性。
DGW架构中的U-GW(或者D-GW)可以根据业务需求进行按需分布式部署，实现用户的本地接入，从而缩短用户面数据的往返路由时间(Round-Trip Time，RTT)，提升用户体验。在部署时，U-GW的位置可以下移到更靠近用户的城域网甚至基站控制器。随着U-GW位置的下移，其服务范围相比较EPS网络中集中式部署的S-GW/P-GW的服务范围要小很多，从而增大了UE移动过程中服务U-GW改变的概率。
由此可见，DGW架构中，如何保证UE移动过程中的业务连续性，是一个更为突出的问题。
发明内容
本发明实施例提供一种保持业务连续性的方法、控制面网关和移动管理网元，能够为UE建立转发U-GW与源U-GW之间，以及转发U-GW与UE的目标基站之间的数据转发隧道，从而能够保证UE移动过程中的业务连续性，提高用户的业务体验。
第一方面，提出了一种保持业务连续性的方法，该方法包括：控制面网关接收移动管理网元为用户设备发送的用户设备的当前位置信息；该控制面网关根据该用户设备的当前位置信息为该用户设备选择至少一个转发用户面网关；该控制面网关在服务该用户设备的源用户面网关与该转发用户面网关之间，以及该转发用户面网关与该用户设备的目标基站之间，为该用户设备建立数据转发隧道，其中，该数据转发隧道用于在该用户设备的移动过程中传输该用户设备的上行用户面数据和/或下行用户面数据。
结合第一方面，在第一种可能的实现方式中，该至少一个转发用户面网关为第一用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关与该用户设备移动到当前位置区域之前的服务控制面网关相同，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；控制面网关在服务该用户设备的源用户面网关与该转发用户面网关之间，以及该转发用户面网关与该用户设备的目标基站之间，为该用户设备建立数据转发隧道，具体实现为：
该控制面网关接收该移动管理网元发送的第一请求，该第一请求携带该 用户设备的目标基站的路由信息；
该控制面网关向该第一用户面网关发送第二请求，其中，该第二请求用于请求该第一用户面网关建立该第一用户面网关与该目标基站之间的数据转发隧道，以及该第一用户面网关与该源用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源用户面网关的路由信息；
该控制面网关向该源用户面网关发送第三请求，其中，该第三请求用于请求该源用户面网关建立该源用户面网关与该第一用户面网关之间的数据转发隧道，该第三请求携带该转发用户面网关的路由信息。
结合第一方面，在第二种可能的实现方式中，该至少一个转发用户面网关包括第二用户面网关和第三用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关与该用户设备移动到当前位置区域之前的服务控制面网关相同，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；控制面网关在服务该用户设备的源用户面网关与该转发用户面网关之间，以及该转发用户面网关与该用户设备的目标基站之间，为该用户设备建立数据转发隧道，具体实现为：
该控制面网关接收该移动管理网元发送的第一请求，该第一请求携带该用户设备的目标基站的路由信息；
该控制面网关向该第二用户面网关发送第二请求，其中，该第二请求用于请求该第二用户面网关建立该第二用户面网关与该目标基站之间的数据转发隧道，以及该第二用户面网关与该第三用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三用户面网关的路由信息；
该控制面网关向该第三用户面网关发送第三请求，其中，该第三请求用于请求该第三用户面网关建立该第三用户面网关与该第二用户面网关之间的数据转发隧道，以及该第三用户面网关与该源用户面网关之间的数据转发隧道，该第三请求携带该第二用户面网关的路由信息，以及该源用户面网关的路由信息；
该控制面网关向该源用户面网关发送第四请求，其中，该第四请求用于请求该源用户面网关建立该源用户面网关与该第三用户面网关之间的数据转发隧道，该第四请求携带该第三用户面网关的路由信息。
结合第一方面，在第三种可能的实现方式中，该至少一个转发用户面网 关为第一用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关不同于该用户设备移动到当前位置区域之前的服务控制面网关，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；
该方法还包括：该控制面网关还接收移动管理网元发送的该源用户面网关的路由信息；
控制面网关在服务该用户设备的源用户面网关与该转发用户面网关之间，以及该转发用户面网关与该用户设备的目标基站之间，为该用户设备建立数据转发隧道，具体实现为：
该控制面网关接收该移动管理网元发送的第一请求，该第一请求携带该用户设备的目标基站的路由信息；
该控制面网关向该第一用户面网关发送第二请求，其中，该第二请求用于请求该第一用户面网关建立该第一用户面网关与该目标基站之间的数据转发隧道，以及该第一用户面网关与该源用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源用户面网关的路由信息。
结合第一方面，在第四种可能的实现方式中，
，该至少一个转发用户面网关包括第二用户面网关和第三用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关不同于该用户设备移动到当前位置区域之前的服务控制面网关，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；
该方法还包括：该控制面网关还接收移动管理网元发送的该源用户面网关的路由信息；
控制面网关在服务该用户设备的源用户面网关与该转发用户面网关之间，以及该转发用户面网关与该用户设备的目标基站之间，为该用户设备建立数据转发隧道，具体实现为：
该控制面网关接收该移动管理网元发送的第一请求，该第一请求携带该用户设备的目标基站的路由信息；
该控制面网关向该第二用户面网关发送第二请求，其中，该第二请求用于请求该第二用户面网关建立该第二用户面网关与该目标基站之间的数据转发隧道，以及该第二用户面网关与该第三用户面网关之间的数据转发隧 道，该第二请求携带该目标基站的路由信息，以及第三用户面网关的路由信息；
该控制面网关向该第三用户面网关发送第三请求，其中，该第三请求用于请求该第三用户面网关建立该第三用户面网关与该第二用户面网关之间的数据转发隧道，以及该第三用户面网关与该源用户面网关之间的数据转发隧道，该第三请求携带该第二用户面网关的路由信息，以及该源用户面网关的路由信息。
结合第一方面或第一方面的第一种可能的实现方式至第一方面的第四种可能的实现方式中任一种可能的实现方式，在第五种可能的实现方式中，该方法还包括：该控制面网关向目标用户面网关发送建立会话请求，其中，该建立会话请求用于在该目标用户面网关上为该用户设备创建用户面数据传输所需的承载上下文，所建立的每个该承载上下文都包含该目标用户面网关的路由信息，该目标用户面网关是该用户设备的当前位置区域对应的服务用户面网关。
结合第一方面的第五种可能的实现方式，在第六种可能的实现方式中，该方法还包括：该控制面网关通过该移动管理网元向该目标基站发送该目标用户面网关的路由信息。
结合第一方面的第一种可能的实现方式或第一方面的第三种可能的实现方式，在第七种可能的实现方式中，该方法还包括：该控制面网关通过该移动管理网元向该目标基站发送该第一用户面网关的路由信息。
结合第一方面的第一种可能的实现方式或第一方面的第三种可能的实现方式，在第八种可能的实现方式中，具体实现为：该第一用户面网关还是该控制面网关根据该用户设备的当前位置信息为该用户设备选择的服务用户面网关。
结合第一方面的第二种可能的实现方式或第一方面的第四种可能的实现方式，在第九种可能的实现方式中，该方法还包括：该控制面网关通过该移动管理网元向该目标基站发送该第二用户面网关的路由信息。
第二方面，提出了一种保持业务连续性的方法，该方法包括：目标移动管理网元接收服务用户设备的源移动管理网元发送的转发重定位请求，该转发重定位请求携带该用户设备的当前位置信息；该目标移动管理网元根据该用户设备的当前位置信息选择该用户设备的目标控制面网关；该目标移动管 理网元向该目标控制面网关发送该用户设备的当前位置信息，以便该目标控制面网关根据该用户设备的当前位置信息确定该用户设备的转发用户面网关；该目标移动管理网元向该目标控制面网关发送数据转发隧道建立请求，该数据转发隧道建立请求用于请求该目标控制面网关在该转发用户面网关与服务该用户设备的源用户面网关之间，以及该转发用户面网关与服务该用户设备的目标基站之间为该用户设备建立数据转发隧道。
结合第二方面，在第一种可能的实现方式中，该目标控制面网关与该用户设备移动到当前位置区域之前的服务控制面网关不同，该方法还包括：该目标移动管理网元向该源移动管理网元发送改变通知消息，该改变通知消息用于指示该用户设备的服务控制面网关变更为该目标控制面网关。
结合第二方面的第一种可能的实现方式，在第二种可能的实现方式中，该方法还包括：该目标移动管理网元接收该源移动管理网元根据该改变通知消息发送的确认消息，该确认消息携带该用户设备的源用户面网关的路由信息。
第三方面，提出了一种保持业务连续性的方法，该方法包括：控制面网关接收移动管理网元发送的该用户设备的当前位置信息；该控制面网关根据该用户设备的当前位置信息为该用户设备选择目标用户面网关；该控制面网关向该移动管理网元发送请求消息，该请求消息用于请求该移动管理网元释放释放第一承载上下文并指示该用户设备发送第二承载上下文的建立请求，其中，该第一承载上下文是建立在该用户设备的源用户面网关上的该用户设备的承载上下文，该第二承载上下文是该用户设备根据该第一承载上下文在该目标用户面网关上重建的承载上下文。
结合第三方面，在第一种可能的实现方式中，具体实现为：该删除承载请求消息携带重新激活请求指示，该重新激活请求指示用于指示该移动管理网元请求该用户设备在删除该承载上下文后，发起该承载上下文的重新建立请求。
第四方面，提出了一种控制面网关，该控制面网关包括：接收单元，用于接收移动管理网元发送的用户设备的当前位置信息；选择单元，用于根据该用户设备的当前位置信息为该用户设备选择至少一个转发用户面网关；隧道建立单元，用于在服务该用户设备的源用户面网关与该转发用户面网关之间，以及该转发用户面网关与该用户设备的目标基站之间，为该用户设备建 立数据转发隧道，其中，该数据转发隧道用于在该用户设备的移动过程中传输该用户设备的上行用户面数据和/或下行用户面数据。
在一个可能的设计中，该至少一个转发用户面网关为第一用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关与该用户设备移动到当前位置区域之前的服务控制面网关相同，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；
该接收单元还用于接收该移动管理网元发送的第一请求，该第一请求携带该用户设备的目标基站的路由信息；
该控制面网关还包括发送单元，该隧道建立单元具体用于：
通过该发送单元向该第一用户面网关发送第二请求，并通过该发送单元向该源用户面网关发送第三请求，其中，该第二请求用于请求该第一用户面网关建立该第一用户面网关与该目标基站之间的数据转发隧道，以及该第一用户面网关与该源用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源用户面网关的路由信息，该第三请求用于请求该源用户面网关建立该源用户面网关与该第一用户面网关之间的数据转发隧道，该第三请求携带该转发用户面网关的路由信息。
在一个可能的设计中，该至少一个转发用户面网关包括第二用户面网关和第三用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关与该用户设备移动到当前位置区域之前的服务控制面网关相同，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；
该接收单元还用于接收该移动管理网元发送的第一请求，该第一请求携带该用户设备的目标基站的路由信息；
该控制面网关还包括发送单元，该隧道建立单元具体用于：
通过该发送单元向该第二用户面网关发送第二请求，并通过该发送单元向该第三用户面网关发送第三请求，并通过该发送单元向该源用户面网关发送第四请求，其中，该第二请求用于请求该第二用户面网关建立该第二用户面网关与该目标基站之间的数据转发隧道，以及该第二用户面网关与该第三用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三用户面网关的路由信息，该第三请求用于请求该第三用户面网关建 立该第三用户面网关与该第二用户面网关之间的数据转发隧道，以及该第三用户面网关与该源用户面网关之间的数据转发隧道，该第三请求携带该第二用户面网关的路由信息，以及该源用户面网关的路由信息，该第四请求用于请求该源用户面网关建立该源用户面网关与该第三用户面网关之间的数据转发隧道，该第四请求携带该第三用户面网关的路由信息。
在一个可能的设计中，该至少一个转发用户面网关为第一用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关不同于该用户设备移动到当前位置区域之前的服务控制面网关，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；
该接收单元还用于接收移动管理网元发送的该源用户面网关的路由信息；
该接收单元还用于接收该移动管理网元发送的第一请求，该第一请求携带该用户设备的目标基站的路由信息；
该控制面网关还包括发送单元，该隧道建立单元具体用于：
通过该发送单元向该第一用户面网关发送第二请求，其中，该第二请求用于请求该第一用户面网关建立该第一用户面网关与该目标基站之间的数据转发隧道，以及该第一用户面网关与该源用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源用户面网关的路由信息。
在一个可能的设计中，该至少一个转发用户面网关包括第二用户面网关和第三用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关不同于该用户设备移动到当前位置区域之前的服务控制面网关，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；
该接收单元还用于接收移动管理网元发送的该源用户面网关的路由信息；
该接收单元还用于接收该移动管理网元发送的第一请求，该第一请求携带该用户设备的目标基站的路由信息；
该控制面网关还包括发送单元，该隧道建立单元具体用于：
通过该发送单元向该第二用户面网关发送第二请求，并通过该发送单元 向该第三用户面网关发送第三请求，其中，该第二请求用于请求该第二用户面网关建立该第二用户面网关与该目标基站之间的数据转发隧道，以及该第二用户面网关与该第三用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三用户面网关的路由信息，该第三请求用于请求该第三用户面网关建立该第三用户面网关与该第二用户面网关之间的数据转发隧道，以及该第三用户面网关与该源用户面网关之间的数据转发隧道，该第三请求携带该第二用户面网关的路由信息，以及该源用户面网关的路由信息。
在一个可能的设计中，该隧道建立单元还用于向目标用户面网关发送建立会话请求，其中，该建立会话请求用于在该目标用户面网关上为该用户设备创建用户面数据传输所需的承载上下文，所建立的每个该承载上下文都包含该目标用户面网关的路由信息，该目标用户面网关是该用户设备的当前位置区域对应的服务用户面网关。
在一个可能的设计中，该隧道建立单元还用于通过该移动管理网元向该目标基站发送该目标用户面网关的路由信息。
在一个可能的设计中，该隧道建立单元还用于通过该移动管理网元向该目标基站发送该第一用户面网关的路由信息。
在一个可能的设计中，该第一用户面网关还是该控制面网关根据该用户设备的当前位置信息为该用户设备选择的服务用户面网关。
在一个可能的设计中，该隧道建立单元还用于通过该移动管理网元向该目标基站发送该第二用户面网关的路由信息。
第五方面，提出了一种移动管理网元，该移动管理网元包括：接收单元，用于接收服务用户设备的源移动管理网元发送的转发重定位请求，该转发重定位请求携带该用户设备的当前位置信息；选择单元，用于根据该用户设备的当前位置信息选择该用户设备的目标控制面网关；发送单元，用于向该目标控制面网关发送该用户设备的当前位置信息，以便该目标控制面网关根据该用户设备的当前位置信息确定该用户设备的转发用户面网关；该发送单元还用于向该目标控制面网关发送数据转发隧道建立请求，该数据转发隧道建立请求用于请求该目标控制面网关在该转发用户面网关与服务该用户设备的源用户面网关之间，以及该转发用户面网关与服务该用户设备的目标基站之间为该用户设备建立数据转发隧道。
在一个可能的设计中，该目标控制面网关与该用户设备移动到当前位置区域之前的服务控制面网关不同，该发送单元还用于向该源移动管理网元发送改变通知消息，该改变通知消息用于指示该用户设备的服务控制面网关变更为该目标控制面网关。
在一个可能的设计中，该接收单元还用于接收该源移动管理网元根据该改变通知消息发送的确认消息，该确认消息携带该用户设备的源用户面网关的路由信息。
第六方面，提出了一种控制面网关，该控制面网关包括：控制面网关接收移动管理网元发送的该用户设备的当前位置信息；该控制面网关根据该用户设备的当前位置信息为该用户设备选择目标用户面网关；该控制面网关向该移动管理网元发送请求消息，该请求消息用于请求该移动管理网元释放释放第一承载上下文并指示该用户设备发送第二承载上下文的建立请求，其中，该第一承载上下文是建立在该用户设备的源用户面网关上的该用户设备的承载上下文，该第二承载上下文是该用户设备根据该第一承载上下文在该目标用户面网关上重建的承载上下文。
在一个可能的设计中，该删除承载请求消息携带重新激活请求指示，该重新激活请求指示用于指示该移动管理网元请求该用户设备在删除该承载上下文后，发起该承载上下文的重新建立请求。
第七方面，提出了一种控制面网关，包括：存储器、处理器、接收机和发射机，其中，
该存储器用于存放程序，并向该处理器提供数据和指令；
该处理器用于执行该存储器所存放的程序，并具体用于执行以下操作：
通过该接收机接收移动管理网元发送的用户设备的当前位置信息；
根据该用户设备的当前位置信息为该用户设备选择至少一个转发用户面网关；
在服务该用户设备的源用户面网关与该转发用户面网关之间，以及该转发用户面网关与服务该用户设备的目标基站之间，为该用户设备建立数据转发隧道，其中，该数据转发隧道用于在该用户设备的移动过程中传输该用户设备的上行用户面数据和/或下行用户面数据。
在一种可能的设计中，该至少一个转发用户面网关为第一用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且 该控制面网关与该用户设备移动到当前位置区域之前的服务控制面网关相同，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；
该处理器还用于通过该接收机接收该移动管理网元发送的第一请求，该第一请求携带该目标基站的路由信息；
在用于通过该发射机在该源用户面网关与该转发用户面网关之间，和/或该转发用户面网关与该目标基站之间，为该用户设备建立数据转发隧道的过程中，该处理器具体用于：
通过该发射机向该第一用户面网关发送第二请求，并通过该发射机向该源用户面网关发送第三请求，其中，该第二请求用于请求该第一用户面网关建立该第一用户面网关与该目标基站之间的数据转发隧道，以及该第一用户面网关与该源用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源用户面网关的路由信息，该第三请求用于请求该源用户面网关建立该源用户面网关与该第一用户面网关之间的数据转发隧道，该第三请求携带该第一用户面网关的路由信息。
在一种可能的设计中，该至少一个转发用户面网关包括第一用户面网关和第二用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关与该用户设备移动到当前位置区域之前的服务控制面网关相同，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；
该处理器还用于通过该接收机接收该移动管理网元发送的第一请求，该第一请求携带该目标基站的路由信息；
在用于通过该发射机在该源用户面网关与该转发用户面网关之间，以及该转发用户面网关与该目标基站之间，为该用户设备建立数据转发隧道的过程中，该处理器具体用于：
通过该发射机向该第二用户面网关发送第二请求，并通过该发射机向该第三用户面网关发送第三请求，并通过该发射机向该源用户面网关发送第四请求，其中，该第二请求用于请求该第二用户面网关建立该第二用户面网关与该目标基站之间的数据转发隧道，以及该第二用户面网关与该第三用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三用户面网关的路由信息，该第三请求用于请求该第三用户面网关建立该第 三用户面网关与该第二用户面网关之间的数据转发隧道，以及该第三用户面网关与该源用户面网关之间的数据转发隧道，该第三请求携带该第二用户面网关的路由信息，以及该源用户面网关的路由信息，该第四请求用于请求该源用户面网关建立该源用户面网关与该第三用户面网关之间的数据转发隧道，该第四请求携带该第三用户面网关的路由信息。
在一种可能的设计中，该至少一个转发用户面网关为第一用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关不同于该用户设备移动到当前位置区域之前的服务控制面网关，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；
该处理器还用于通过该接收机接收移动管理网元发送的该源用户面网关的路由信息；
该处理器还用于通过该接收机接收该移动管理网元发送的第一请求，该第一请求携带该目标基站的路由信息；
在用于通过该发射机在该源用户面网关与该转发用户面网关之间，以及该转发用户面网关与该目标基站之间，为该用户设备建立数据转发隧道的过程中，该处理器具体用于：
通过该发射机向该第一用户面网关发送第二请求，其中，该第二请求用于请求该第一用户面网关建立该第一用户面网关与该目标基站之间的数据转发隧道，以及该第一用户面网关与该源用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源用户面网关的路由信息。
在一种可能的设计中，该至少一个转发用户面网关包括第一用户面网关和第二用户面网关，该控制面网关为该用户设备移动到当前位置区域之后的服务控制面网关，且该控制面网关不同于该用户设备移动到当前位置区域之前的服务控制面网关，该移动管理网元为该用户设备移动到当前位置区域之后的服务移动管理网元；
该处理器还用于通过该接收机接收移动管理网元发送的该源用户面网关的路由信息；
该处理器还用于通过该接收机接收该移动管理网元发送的第一请求，该第一请求携带该目标基站的路由信息；
在用于通过该发射机在该源用户面网关与该转发用户面网关之间，以及 该转发用户面网关与该目标基站之间，为该用户设备建立数据转发隧道的过程中，该处理器具体用于：
通过该发射机向该第二用户面网关发送第二请求，并通过该发射机向该第三用户面网关发送第三请求，其中，该第二请求用于请求该第二用户面网关建立该第二用户面网关与该目标基站之间的数据转发隧道，以及该第二用户面网关与该第三用户面网关之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三用户面网关的路由信息，该第三请求用于请求该第三用户面网关建立该第三用户面网关与该第二用户面网关之间的数据转发隧道，以及该第三用户面网关与该源用户面网关之间的数据转发隧道，该第三请求携带该第二用户面网关的路由信息，以及该源用户面网关的路由信息。
在一种可能的设计中，该处理器还用于通过该发射机向该目标用户面网关发送建立会话请求，其中，该建立会话请求用于在该目标用户面网关上为该用户设备创建用户面数据传输所需的承载上下文，所建立的每个该承载上下文都包含该目标用户面网关的路由信息，该目标用户面网关是该用户设备的当前位置区域对应的服务用户面网关。
在一种可能的设计中，该处理器还用于通过该移动管理网元向该目标基站发送该目标用户面网关的路由信息。
在一种可能的设计中，该处理器还用于通过该移动管理网元向该目标基站发送该第一用户面网关的路由信息。
在一种可能的设计中，该第一用户面网关是该控制面网关根据该用户设备的当前位置信息为该用户设备选择的服务用户面网关。
在一种可能的设计中，该处理器还用于通过该移动管理网元向该目标基站发送该第二用户面网关的路由信息。
第八方面，提出了一种移动管理网元，包括：存储器、处理器、接收机和发射机，其中，
该存储器用于存放程序，并向该处理器提供数据和指令；
该处理器用于执行该存储器所存放的程序，并具体用于执行以下操作：
通过该接收机接收服务用户设备的源移动管理网元发送的转发重定位请求，该转发重定位请求携带该用户设备的当前位置信息；
根据该用户设备的当前位置信息选择该用户设备的目标控制面网关；
通过该发射机向该目标控制面网关发送该用户设备的当前位置信息，以便该目标控制面网关根据该用户设备的当前位置信息确定该用户设备的转发用户面网关；
通过该发射机向该目标控制面网关发送数据转发隧道建立请求，该数据转发隧道建立请求用于请求该目标控制面网关在该转发用户面网关与服务该用户设备的源用户面网关之间，以及该转发用户面网关与服务该用户设备的目标基站之间为该用户设备建立数据转发隧道。
在一种可能的设计中，该目标控制面网关与该用户设备移动到当前位置区域之前的服务控制面网关不同，
该处理器还用于通过该发射机向该源移动管理网元发送改变通知消息，该改变通知消息用于指示该用户设备的服务控制面网关变更为该目标控制面网关。
在一种可能的设计中，该处理器还用于通过该接收机接收该源移动管理网元根据该改变通知消息发送的确认消息，该确认消息携带该用户设备的源用户面网关的路由信息。
第九方面，提出了一种控制面网关，包括：存储器、处理器、接收机和发射机，其中，
该存储器用于存放程序，并向该处理器提供数据和指令；
该处理器用于执行该存储器所存放的程序，并具体用于执行以下操作：
通过该接收机接收移动管理网元发送的该用户设备的当前位置信息；
根据该用户设备的当前位置信息为该用户设备选择目标用户面网关；
通过该发射机向该移动管理网元发送请求消息，该请求消息用于请求该移动管理网元释放释放第一承载上下文并指示该用户设备发送第二承载上下文的建立请求，其中，该第一承载上下文是建立在该用户设备的源用户面网关上的该用户设备的承载上下文，该第二承载上下文是该用户设备根据该第一承载上下文在该目标用户面网关上重建的承载上下文。
在一种可能的设计中，该请求消息为删除承载请求消息，该删除承载请求消息携带重新激活请求指示，该重新激活请求指示用于通过该移动管理网元指示该用户设备在该第一承载上下文删除后，发起该第二承载上下文的建立请求。
根据本发明实施例的保持业务连续性的方法、控制面网关和移动管理网 元，通过在控制面网关为UE选择转发U-GW，并为UE建立转发U-GW与源U-GW之间，以及转发U-GW与UE的目标基站之间的数据转发隧道，从而能够保证UE移动过程中的业务连续性，提高用户的业务体验。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例分布式网关的两种网络架构示意图。
图2是本发明实施例保持业务持续性的一种方法流程图。
图3是本发明实施例保持业务连续性的一种交互流程图。
图4是本发明实施例保持业务连续性的另一种交互流程图。
图5是本发明实施例保持业务连续性的再一种交互流程图。
图6是本发明实施例保持业务连续性的再一种交互流程图。
图7是本发明实施例保持业务连续性的再一种交互流程图。
图8是本发明实施例保持业务连续性的再一种交互流程图。
图9是本发明实施例保持业务持续性的另一种方法流程图。
图10是本发明实施例保持业务持续性的再一种方法流程图。
图11是本发明实施例保持业务连续性的再一种交互流程图。
图12是本发明实施例控制面网关的一种结构示意图。
图13是本发明实施例控制面网关的另一种结构示意图。
图14是本发明实施例移动管理网元的一种结构示意图。
图15是本发明实施例控制面网关的再一种结构示意图。
图16是本发明实施例控制面网关的再一种结构示意图。
图17是本发明实施例移动管理网元的另一种结构示意图。
图18是本发明实施例控制面网关的再一种结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是 全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明的技术方案，可以应用于各种通信系统，例如：全球移动通讯系统(GSM，Global System of Mobile communication)，码分多址(CDMA，Code Division Multiple Access)系统，宽带码分多址(WCDMA，Wideband Code Division Multiple Access Wireless)，通用分组无线业务(GPRS，General Packet Radio Service)，长期演进(LTE，Long Term Evolution)以及5G网络等。
在本发明实施例中，用户设备UE(User Equipment)，也可称之为移动终端(Mobile Terminal)，可以为以下任意一种，并且用户设备可以是静态的、移动的、便携式、袖珍式、手持式、计算机内置的或者车载的。用户设备可以包括但不限于：站台(Station)、移动台(Mobile Station)、用户单元(Subscriber Unit)、个人电脑(Personal Computer)、膝上型电脑(Laptop Computer)、平板电脑(Tablet Computer)、上网本(Netbook)、蜂窝电话(Cellular Phone)、手持设备(Handheld)、无绳电话(Cordless Phone)、个人数字助理(PDA，Personal Digital Assistant)、数据卡(Data Card)、USB插入设备、移动WiFi热点设备(MiFi Devices)、智能手表/智能眼镜等可穿戴设备(Wearable Devices)、无线调制解调器(Modem)、无线路由器、无线本地环路(WLL，Wireless Local Loop)台等。上述用户设备可以分布于整个无线网络中，通过无线接入网与一个或多个核心网进行通信。
基站，可以是GSM或CDMA中的基站(BTS，Base Transceiver Station)，也可以是WCDMA中的基站(NodeB)，还可以是LTE中的演进型基站(eNB或e-NodeB，evolutional Node B)，本发明并不限定，但为描述方便，下述实施例以eNB为例进行说明。
控制面网关(Control plane Gateway，C-GW)，可以有两种存在形式：(1)集成了现有3GPP EPS网络中服务网关(Serving Gateway，S-GW)与分组数据网关(Packet Data Network Gateway，P-GW)控制面功能的单一网元；(2)分别实现现有S-GW的控制面功能(Control Plane S-GW)与现有P-GW的控制面功能(Control Plane P-GW)的两个独立网元，本发明对此并不限定。
用户面网关(User Plane Gateway，U-GW)，对应于C-GW的两种存在形式，也有两种存在形式：(1)集成了现有3GPP EPS网络中服务网关 (Serving Gateway，S-GW)与分组数据网关(Packet Data Network Gateway，P-GW)用户面功能的单一网元；(2)分别实现现有S-GW的用户面功能(User Plane S-GW)与现有P-GW的用户功能(User Plane P-GW)的两个独立网元，本发明对此并不限定。考虑到U-GW可以分布式部署的特性，U-GW也可以称为分布式网关(Distributed Gateway，D-GW)。
处于相同服务区域内的多个U-GW，可以组成一个U-GW资源池，同一个U-GW资源池中的U-GW之间可以直接通信，每个U-GW资源池中，可以配置一个缺省U-GW，用来实现与其它U-GW资源池中U-GW之间的通信。
图1是本发明实施例DGW的两种网络架构示意图。虚线之上为DGW架构1，虚线之下为DGW架构2。
DGW架构1中，C-GW集成了现有EPS网络架构S-GW与P-GW的所有控制面功能，U-GW集成了现有EPS网络架构S-GW与P-GW的所有用户面功能，在C-GW与U-GW两个网元之间引入一个新的接口，比如S18接口，实现C-GW与U-GW之间的通信。该网络架构中，其它的网元与接口可以重用现有EPS网络架构。新增的S18接口可以重用S-GW与P-GW之间的接口协议，比如：GTP协议，或者是其它接口协议或新定义的协议，本发明实施例对此不做限定。
DGW架构2中，现有EPS网络架构中S-GW与P-GW被分别拆分成控制面与用户面两个独立功能网元(S-GW-C与S-GW-U，P-GW-C与P-GW-U)，S-GW-C与P-GW-C可以统称为C-GW，S-GW-U与P-GW-U可以统称为U-GW。S-GW与P-GW之间已有的接口也一并被拆分为控制面接口与用户面接口，比如DGW架构2中的S5-C与S5-U接口。在S-GW-C与S-GW-U两个网元之间引入一个新的接口，比如S18接口，实现S-GW-C与S-GW-U之间的通信，在P-GW-C与P-GW-U两个网元之间引入一个新的接口，比如S19接口，实现P-GW-C与P-GW-U之间的通信。该网络架构中，其它的网元与接口可以重用现有EPS网络架构。新增的S18、S19接口可以重用S-GW与P-GW之间的接口协议，比如：GTP协议，或者是其它接口协议或新定义的协议，本发明实施例对此不做限定。
本发明实施例的方法和装置，可以应用于如图1中DGW架构1或DGW架构2所示的通信系统中，为描述方便，本发明实施例以DGW架构1所示 的通信系统为例，对于DGW架构2所示的通信系统，本发明实施例中的C-GW相当于DGW架构2中S-GW-C与P-GW-C的合一网元；U-GW相当于DGW架构2中S-GW-U与P-GW-U的合一网元。
图2是本发明实施例保持业务持续性的方法流程图。图2的方法由控制面网关执行。该方法包括:
201，C-GW接收移动管理网元发送的UE的当前位置信息。
本发明实施例可以适用于如下任意一种应用场景中：
(1)连接态UE在进行用户面数据传输时发生了位置移动，移动后的位置区域超出源基站的服务范围，源基站在感知UE移出其服务范围后，决定发起连接态用户面数据业务切换流程。源基站为UE移动到当前位置区域之前的服务基站。
(2)空闲态UE在需要发送上行用户面数据传输时，移出了当前注册的位置区域，比如当前注册的跟踪域(Tracking Area，TA)，UE发起位置更新流程，比如跟踪域更新(Tracking Area Update，TAU)流程。
(3)空闲态UE在需要发送上行用户面数据传输时，移出了当前服务基站的服务区域但没有移出当前注册的位置区域，比如当前注册的跟踪域(Tracking Area，TA)，UE发起业务请求(Service Request)流程。
在应用场景(1)中，移动管理网元在收到源基站发送的用户面数据切换请求后，可向UE的服务C-GW发送业务切换通知。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发送该业务切换通知，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息等；或者，移动管理网元可以用新建的消息发送该业务切换通知，具体使用哪个消息来发送该业务切换通知，本发明不做限定。
在应用场景(2)中，移动管理网元在接收到该UE发送的位置更新请求后，或者为该UE成功建立空口承载上下文后，可向UE的服务C-GW发送请求消息。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发 送该请求消息，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息；或者，移动管理网元可以用新建的消息发送该请求消息，具体使用哪个消息来发送该请求消息，本发明不做限定。
在应用场景(3)中，移动管理网元在接收到该UE发送的业务请求后，或者为该UE成功建立空口承载上下文后，可向UE的服务C-GW发送请求消息。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发送该请求消息，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息；或者，移动管理网元可以用新建的消息发送该请求消息，具体使用哪个消息来发送该请求消息，本发明不做限定。
UE的当前位置信息，包括UE的当前位置区域所对应的跟踪域标识(Tracking Area Identity，TAI)和/或UE的当前位置区域所对应的服务基站信息等。UE移动到当前位置区域所对应的TAI，即为UE的目标TAI；UE移动到当前位置区域所对应的服务基站信息，即为UE的目标基站信息。目标基站信息，可以是目标基站标识(Identity，ID)、目标小区标识(Cell Identity，CI)，等等。可理解的，UE的当前位置区域，也称为UE的目标位置区域，也即UE移出源服务基站的服务范围后所在的位置区域，类似地，UE的当前位置信息，也称为UE的目标位置信息。
202，该C-GW根据该UE的当前位置信息为该UE选择至少一个转发U-GW。
本发明实施例中，UE的当前位置区域超出UE当前的服务U-GW的服务范围，C-GW需要根据UE的当前位置区域为UE选择合适的转发U-GW。
203，该C-GW在服务该UE的源U-GW与该转发U-GW之间，以及该转发U-GW与服务该UE的目标基站之间，为该UE建立数据转发隧道。
其中，该数据转发隧道用于在该UE的移动过程中传输该UE的上行用户面数据和/或下行用户面数据。
应理解，该UE的移动过程包括上述三种应用场景中发生的流程，具体为：应用场景(1)中的业务切换流程，应用场景(2)中的位置更新流程，应用场景(3)中的业务请求流程。
应理解，UE的目标基站，是指UE移动到当前位置区域后，为该UE提供接入服务的基站。
应理解，该数据转发隧道是通过在服务该UE的源U-GW与该转发U-GW之间，以及转发U-GW与该UE的目标基站之间建立用户面承载上下文实现的，该用户面承载上下文包含了转发用户面数据所需的路由信息，具体地，该源U-GW上建立的用户面承载上下文包括该转发U-GW的路由信息以及服务该UE的源基站的路由信息，该转发U-GW上建立的用户面承载上下文包括该源U-GW的路由信息以及该目标基站的路由信息，该目标基站上建立的用户面承载上下文包括该转发U-GW的路由信息。进一步地，该路由信息可以包括地址(典型地为互联网协议(Internet Protocol，IP)地址)与隧道端口信息(典型地，若使用GPRS隧道协议(GPRS Tunnelling Protocol，GTP)协议，则隧道端口信息为GTP隧道端口标识(Tunnel Endpoint Identifier，TEID))。
应理解，该转发U-GW，是指步骤202中提到的至少一个转发U-GW。该C-GW在服务该UE的源U-GW与该转发U-GW之间，以及该转发U-GW与该UE的目标基站之间，为该UE建立的数据转发隧道，是指该C-GW在源U-GW、该至少一个转发U-GW与该目标基站三者之间构成的通信路径，建立起从源C-GW到目标基站两个网元之间的数据转发隧道。
例如，当该至少一个转发U-GW只有一个U-GW，为U-GW1时，则建立的数据转发隧道路径为：源U-GW—U-GW1—目标基站；当该至少一个转发U-GW有2个U-GW，为U-GW1和U-GW2，其中U-GW1能够与源U-GW通信，U-GW2能够与目标基站通信，则建立的数据转发隧道路径为：源U-GW—U-GW1—U-GW2—目标基站；当该至少一个转发U-GW有3个或3个U-GW以上，且其中包括能够与源U-GW通信的U-GW1，以及能够与目标基站通信的U-GW2，则建立的数据转发隧道路径为：源U-GW—U-GW1—……—U-GW2—目标基站。U-GW1—……—U-GW2所示部分的数据转发隧道为该至少一个转发U-GW之间的数据转发隧道。
本发明实施例中，C-GW根据UE移动后的当前位置信息，为UE确定合适的转发U-GW，并建立转发U-GW与源U-GW之间，以及转发U-GW与UE的目标基站之间的数据转发隧道，从而能够保证UE移动过程中的业务连续性，提高用户的业务体验。
可选地，作为一个实施例，该至少一个转发U-GW只有一个，为第一U-GW，并且该C-GW为该UE移动到当前位置区域之后的服务C-GW，且该C-GW与该UE移动到当前位置区域之前的服务C-GW相同，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元。此时，步骤203具体实现为：
该C-GW接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
该C-GW向该第一U-GW发送第二请求，其中，该第二请求用于请求该第一U-GW建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源U-GW的路由信息；
该C-GW向该源U-GW发送第三请求，其中，该第三请求用于请求该源U-GW建立该源U-GW与该第一U-GW之间的数据转发隧道，该第三请求携带该第一U-GW的路由信息。
应理解，本实施例中，该C-GW与该UE移动到当前位置区域之前的服务C-GW相同，即服务C-GW在UE移动过程中没有改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
当然，应理解，C-GW还会接收第一U-GW根据第二请求发送的第二响应，以及源U-GW根据第三请求发送的第三响应。其中，第二响应用于确认第一U-GW允许建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第一U-GW的路由信息，比如IP地址与TEID信息；该第三响应用于确认该源U-GW允许建立该源U-GW与该第一U-GW之间的数据转发隧道。在接收到第二响应和第三响应后，C-GW可向移动管理网元发送第一请求的第一响应。
需要说明的是，本实施中第一请求，第二请求或第三请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应，第二响应或第三响应，可以使用已有的消息，比如 创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
此外，应理解，隧道的物理体现是承载上下文，承载上下文中包括了该隧道对端的路由信息。控制面网关需要分别发送请求到两个用户面网关，分别建立承载上下文，然后承载上下文中包括了对端的路由信息，这样就在两个用户面网关之间建立了隧道。
可选地，作为另一个实施例，该至少一个转发U-GW包括第二U-GW和第三U-GW，该C-GW为该UE移动到当前位置区域之后的服务C-GW，且该C-GW与该UE移动到当前位置区域之前的服务C-GW相同，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元，且该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元相同或不同。此时，步骤203具体实现为：
该C-GW接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
该C-GW向该第二U-GW发送第二请求，其中，该第二请求用于请求该第二U-GW建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三U-GW的路由信息；
该C-GW向该第三U-GW发送第三请求，其中，该第三请求用于请求该第三U-GW建立该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，该第三请求携带该第二U-GW的路由信息，以及该源U-GW的路由信息；
该C-GW向该源U-GW发送第四请求，其中，该第四请求用于请求该源U-GW建立该源U-GW与该第三U-GW之间的数据转发隧道，该第四请求携带该第三U-GW的路由信息。
应理解，本实施例中，该C-GW与该UE移动到当前位置区域之前的服务C-GW相同，即服务C-GW在UE移动过程中没有改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
类似地，C-GW还会接收第二U-GW根据第二请求发送的第二响应，第 三U-GW根据第三请求发送的第三响应，以及源U-GW根据第四请求发送的第四响应。其中，第二响应用于确认第二U-GW允许建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第二U-GW的路由信息，比如IP地址与TEID信息；该第三响应用于确认该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，可选地，该第三响应可以携带该第三U-GW的路由信息，比如IP地址与TEID信息；该第四响应用于确认该源U-GW允许建立该源U-GW与该第三U-GW之间的数据转发隧道。在接收到第二响应、第三响应及第四响应后，C-GW可向移动管理网元发送第一请求的第一响应。
需要说明的是，本实施中第一请求，第二请求，第三请求或第四请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应，第二响应，第三响应或第四响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
C-GW确定的至少一个转发U-GW还可以推广到3个或更多个，C-GW通过向每个转发U-GW发送数据转发隧道建立请求，以建立起源U-GW、该至少一个转发U-GW以及目标基站之间的数据转发隧道。例如，该至少一个转发U-GW包括U-GW1、U-GW2和U-GW3，其中，U-GW1能够与源U-GW通信，U-GW3能够与目标U-GW通信，所建立的转发隧道的路径为：源U-GW—U-GW1—U-GW2—U-GW3—目标U-GW。
可选地，作为再一个实施例，该C-GW还接收该移动管理网元发送的该UE的源U-GW的路由信息，该至少一个转发U-GW只有一个，为第一U-GW，该C-GW为该UE移动到当前位置区域之后的服务C-GW，且该C-GW不同于该UE移动到当前位置区域之前的服务C-GW，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元，且该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元相同或不同。此时，步骤203具体实现为：
该C-GW接收该移动管理网元发送的第一请求，该第一请求携带该UE 的目标基站的路由信息；
该C-GW向该第一U-GW发送第二请求，其中，该第二请求用于请求该第一U-GW建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源U-GW的路由信息。
应理解，本实施例中，该C-GW不同于该UE移动到当前位置区域之前的服务C-GW，即服务C-GW在UE移动过程中改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
类似地，C-GW还会接收第一U-GW根据第二请求发送的第二响应。其中，第二响应用于确认第一U-GW允许建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第一U-GW的路由信息，比如IP地址与TEID信息。在接收到第二响应后，C-GW可向移动管理网元发送第一请求的第一响应。
当然，应理解，本发明实施例中，由于本实施例中UE的服务C-GW在移动过程中发生了改变，故本实施例步骤203具体执行主体为目标C-GW，即该UE移动到当前位置区域之后的服务C-GW。进一步地，该目标C-GW还应通过移动管理网元指示源C-GW向源U-GW发送数据转发隧道建立请求，并将第一U-GW的路由信息发送给源U-GW。其中，源C-GW为该UE移动到当前位置区域之前的服务C-GW，源U-GW为该UE移动到当前位置区域之前的服务U-GW。
需要说明的是，本实施中第一请求或第二请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应或第二响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
可选地，作为再一个实施例，该C-GW还接收该移动管理网元发送的该UE的源U-GW的路由信息，该至少一个转发U-GW包括第二U-GW和第三 U-GW，该C-GW为该UE移动到当前位置区域之后的服务C-GW，且该C-GW不同于该UE移动到当前位置区域之前的服务C-GW，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元，且该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元相同或不同。此时，步骤203具体实现为：
该C-GW接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
该C-GW向该第二U-GW发送第二请求，其中，该第二请求用于请求该第二U-GW建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三U-GW的路由信息；
该C-GW向该第三U-GW发送第三请求，其中，该第三请求用于请求该第三U-GW建立该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，该第三请求携带该第二U-GW的路由信息，以及该源U-GW的路由信息。
应理解，本实施例中，该C-GW不同于该UE移动到当前位置区域之前的服务C-GW，即服务C-GW在UE移动过程中改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
类似地，C-GW还会接收第二U-GW根据第二请求发送的第二响应，以及第三U-GW根据第三请求发送的第三响应。其中，第二响应用于确认第二U-GW允许该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第二U-GW的路由信息，比如IP地址与TEID信息；该第三响应用于确认该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，可选地，该第三响应可以携带该第三U-GW的路由信息，比如IP地址与TEID信息。在接收到第二响应及第三响应后，C-GW可向移动管理网元发送第一请求的第一响应。
当然，应理解，本发明实施例中，由于本实施例中UE的服务C-GW在移动过程中发生了改变，故本实施例步骤203具体执行主体为目标C-GW， 即该UE移动到当前位置区域之后的服务C-GW。进一步地，该目标C-GW还应通过移动管理网元指示源C-GW向源U-GW发送数据转发隧道建立请求，并将第三U-GW的路由信息发送给源U-GW。其中，源C-GW为该UE移动到当前位置区域之前的服务C-GW，源U-GW为该UE移动到当前位置区域之前的服务U-GW。
需要说明的是，本实施中第一请求，第二请求或第三请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应，第二响应或第三响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
可选地，在图2的上述四个具体实施例中，当该至少一个转发U-GW为第一U-GW时，该方法还包括：该C-GW通过该移动管理网元向该目标基站发送该第一U-GW的路由信息。
或者，可选地，在图2的上述四个具体实施例中，当该至少一个转发U-GW为第二U-GW和第三U-GW时，该方法还包括：该C-GW通过该移动管理网元向该目标基站发送该第二U-GW的路由信息。
或者，可选地，在图2的上述四个具体实施例中，该方法还可包括：该C-GW向该目标U-GW发送会话建立请求，其中，该会话建立请求用于在该目标U-GW上为该UE创建用户面数据传输所需的承载上下文，所建立的每个承载上下文都包含该目标U-GW的路由信息(例如IP地址与TEID信息等)，该目标U-GW是该UE的当前位置区域对应的服务U-GW。可理解的，该目标U-GW通常是为该UE在该当前位置区域提供最优数据传输路径的服务U-GW。进一步地，该C-GW通过该移动管理网元向该目标基站发送该目标U-GW的路由信息。
可选地，在图2的上述四个具体实施例中，当该至少一个转发U-GW为第一U-GW时，该第一U-GW还可以是该C-GW根据该UE的当前位置信息为该UE选择的服务U-GW。也就是说，该第一U-GW为目标U-GW。此时，该目标D-GW能够与该源D-GW直接通信，也即该目标U-GW同时扮演了该转发U-GW的角色。可理解的，当该目标U-GW不能与该源D-GW直接通信时，该C-GW选择的转发U-GW与该目标U-GW不同。
下面，将结合具体的实施例，对本发明实施例的方法作进一步的描述。为方便描述，下述实施例以MME作为移动管理网元。当然，在具体的应用中，移动管理网元还可以是其它具备移动管理网元功能的设备，本发明实施例在此不作限制。
图3是本发明实施例保持业务连续性的一种交互流程图。在图3中，源基站为UE移动到当前位置区域前的服务基站；目标基站为UE移动到当前位置区域后的服务基站；UE所属的服务MME和服务C-GW在UE的移动前后保持不变；源U-GW为UE移动到当前位置区域前的服务U-GW；目标U-GW为UE移动到当前位置区域后的U-GW；转发U-GW为UE移动到当前位置区域后用于切换数据业务的U-GW。在业务切换之前，上行/下行用户面数据传输路径为UE—源基站—源U-GW，即图3中的虚线L1a和L2a所示的传输路径。
本发明实施例业务切换的具体流程如下：
S301，源基站发起连接态UE用户面数据切换流程。
当UE的源基站感知到UE移动出源基站的服务范围，且UE正在进行用户面的数据业务时，源基站可决定发起连接态用户面数据业务切换流程。
S302，源基站向MME发送业务切换请求消息。
为区别于本发明实施例其它步骤的业务切换请求消息，将源基站发送给MME的业务切换请求消息命名为业务切换请求消息1。
源基站发送业务切换请求消息1给当前的服务MME(即图3的MME)，在该消息中携带UE的当前位置信息。UE的当前位置信息，包括UE的当前位置区域所对应的跟踪域标识(Tracking Area Identity，TAI)和/或UE的当前位置区域所对应的服务基站信息等。UE移动到当前位置区域所对应的TAI，即为UE的目标TAI；UE移动到当前位置区域所对应的服务基站信息，即为UE的目标基站信息。目标基站信息，可以是目标基站标识(Identity，ID)、目标小区标识(Cell Identity，CI)，等等。UE的当前位置区域，也称为UE的目标位置区域，也即UE移出源服务基站的服务范围后所在的位置区域，类似地，UE的当前位置信息，也称为UE的目标位置信息。
S303，MME向C-GW发送业务切换通知消息。
UE的服务MME在接收到业务切换请求消息1后，获知UE移出了当前基站(源基站)的服务范围，则发送业务切换通知消息给当前的服务C-GW。 其中，该业务切换通知消息中携带了UE的当前位置信息。该业务切换通知消息旨在通知C-GW，UE需要被切换到新的目标位置区域。MME可以重用已有的消息，比如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息，并在这些消息中携带UE的当前位置信息；MME也可以重新定义新的消息以发送该业务切换通知消息，对此本发明实施例不做限定。
S304，C-GW确定目标U-GW和转发U-GW。
C-GW在接收到MME发送的业务切换通知消息后，可根据UE的当前位置信息确定UE当前的服务U-GW(源U-GW)是否需要重新分配，即确定UE是否移出了源U-GW的服务范围。需要说明的是，由于C-GW实时保存有其服务范围内每个U-GW的服务区域信息，故C-GW可以根据UE当前的位置信息(比如目标TAI或目标基站ID)来判断UE是否移出了源U-GW的服务范围。
如果UE未移动出源U-GW的服务范围，则其数据业务的切换在源U-GW内即可实现，其具体实现可参考现有技术中U-GW或P-GW对数据业务进行切换的方法，本发明实施例在此不再赘述。
如果C-GW判断UE的服务U-GW需要重新分配，则C-GW根据UE的当前位置信息选择一个合适的目标U-GW，确保该目标U-GW能够为UE在所述当前位置区域提供最佳的数据传输路径，尽可能地减少用户面数据传输RTT。
进一步地，C-GW需要检查该目标U-GW与源U-GW之间是否可以直接通信。如果目标U-GW可以与源U-GW直接通信，则目标U-GW就是转发U-GW，也即后续所有到转发U-GW的步骤都是到目标U-GW；如果目标U-GW不能与源U-GW直接通信，则根据UE目标位置信息选择一个与源U-GW可以直接通信的U-GW作为转发U-GW。下述图4-图6中确定目标U-GW与转发U-GW的方式与此类似。
需要说明的是，为保证特殊场景下业务的连续性，转发U-GW可以多于一个。典型地，如果UE移动到邻近的U-GW pool，则C-GW选择该邻近U-GW pool中的缺省U-GW作为与目标U-GW通信的转发U-GW(可称为目标转发U-GW)。如果该缺省U-GW与源U-GW之间也不能直接通信，进 一步地，C-GW可以选择源U-GW所在的U-GW pool中的缺省U-GW作为与源U-GW通信的转发U-GW(可称为源转发U-GW)，通过两个转发U-GW来确保UE移动过程中的业务连续性。
S305，C-GW向MME回复切换通知确认消息。
C-GW回复切换通知确认消息给MME，并在该消息中携带C-GW所选择的转发U-GW的地址与隧道端口信息。
转发U-GW的地址，例如，可以为转发U-GW的互联网协议(Internet Protocol，IP)地址，等等；转发U-GW的隧道端口信息，可根据MME与C-GW之间所使用的协议不同而不同，例如，当MME与C-GW之间使用GTP协议时，转发U-GW的隧道端口信息可以是GTP隧道端口标识(Tunnel Endpoint Identifier，TEID)，等等。
此外，如果步骤S304中确定多个转发U-GW，例如源转发U-GW和目标转发U-GW，则C-GW可在切换通知确认消息中携带处于UE目标位置区域的目标转发U-GW的地址与隧道端口信息。需要说明的是，在向MME回复切换通知确认消息时，可以重用已有的消息，比如建立会话响应(Create Session Response)消息或修改承载响应(Modify Bearer Response)消息或修改接入承载响应(Modify Access Bearers Response)消息，也可以定义新的消息，本发明实施例不做限定。
S306，MME发送业务切换请求消息给目标基站。
为区别于本发明实施例其它步骤的业务切换请求消息，将MME发送给目标基站的业务切换请求消息命名为业务切换请求消息2。
MME发送业务切换请求消息2给目标基站，并将C-GW发送的转发U-GW的地址与隧道端口信息转发给目标基站，以备后续上行数据传输路径切换到转发U-GW上。其中，转发U-GW的地址与隧道端口信息可携带在业务切换请求消息2中发送，也可单独发送。
S307，目标基站向MME回复切换请求确认消息。
为区别于本发明实施例其它步骤的切换请求确认消息，并与其所对应的业务切换请求消息匹配相应的数字标识，将目标基站发送给MME的切换请求确认消息命名为切换请求确认消息2。
目标基站收到MME发送的业务切换请求消息2后，可向MME回复切换请求确认消息2，并将其自身的地址(例如IP地址)与隧道端口信息(例 如GTP TEID)发送给MME。类似地，目标基站的地址与隧道端口信息可携带在切换请求确认消息2中发送，也可单独发送。
S308，MME向C-GW发送数据转发隧道建立请求。
为区别于本发明实施例其它步骤的数据转发隧道建立请求，将MME发送给C-GW的数据转发隧道建立请求命名为数据转发隧道建立请求1。
MME向C-GW发送数据转发隧道建立请求1，并将目标基站的地址与隧道端口信息发送给C-GW，以备后续将下行数据传输路径切换到目标基站上。
需要说明的是，该数据转发隧道建立请求可以重用已有的消息，例如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)消息或修改承载请求(Modify Bearer Request)消息，也可以定义新的消息，本发明对此不做限定，该说明适用于本发明所有实施例。
S309，C-GW向转发U-GW发送数据转发隧道建立请求。
为区别于本发明实施例其它步骤的数据转发隧道建立请求，并与其所对应的数据转发隧道建立请求匹配相应的数字标识，将C-GW发送给转发U-GW的数据转发隧道建立请求命名为数据转发隧道建立请求2。
C-GW向转发U-GW发送数据转发隧道建立请求2，并将目标基站的地址与隧道端口信息与源U-GW的地址与隧道端口信息发送给转发U-GW。
此外，如果步骤S304中需要多个转发U-GW，例如源转发U-GW(即前文提到的第三U-GW)和目标转发U-GW(即前文提到的第二U-GW)，则C-GW应该向每个转发U-GW发送数据转发隧道建立请求，并携带对端网元的地址与隧道端口信息。例如，向源转发U-GW发送的数据转发隧道建立请求中携带源U-GW和目标转发U-GW的地址与隧道端口信息，向目标转发U-GW发送的数据转发隧道建立请求中携带源转发U-GW和目标基站的地址与隧道端口信息。
S310，转发U-GW向C-GW回复数据转发隧道建立响应。
为区别于本发明实施例其它步骤的数据转发隧道建立响应，并与其所对应的数据转发隧道建立请求匹配相应的数字标识，将转发U-GW发送给C-GW的数据转发隧道建立响应命名为数据转发隧道建立响应2。
转发U-GW向C-GW回复数据转发隧道建立响应2，以响应C-GW发送的数据转发隧道建立请求2，确认允许建立目标基站与转发U-GW之间，以 及源U-GW与转发U-GW之间的数据转发隧道，可选地，该数据转发隧道建立响应2可以携带该转发U-GW的地址与隧道端口信息。
如果步骤S304中需要多个转发U-GW，C-GW应该向每个转发U-GW发送数据转发隧道建立请求，相应的每个转发U-GW都应回复数据转发隧道建立响应，指示允许建立数据转发隧道。
应理解，本发明中的数据转发隧道建立请求的响应都是允许建立数据转发隧道。如果存在不允许建立数据转发隧道的响应，本发明实施例的方法将不再执行，下同。
需要说明的是，该数据转发隧道建立响应可以重用已有的消息，例如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)消息或修改承载响应(Modify Bearer Response)消息，也可以定义新的消息，本发明对此不做限定，该说明适用于本发明所有实施例。
S311，C-GW向源U-GW发送数据转发隧道建立请求。
为区别于本发明实施例其它步骤的数据转发隧道建立请求，将C-GW发送给源U-GW的数据转发隧道建立请求命名为数据转发隧道建立请求3。
C-GW向源U-GW发送数据转发隧道建立请求3，并将转发U-GW的地址与隧道端口信息发送给源U-GW。
如果步骤S304中确定多个转发U-GW，则C-GW将处于UE当前位置区域的源转发U-GW的地址与隧道端口信息发送给源U-GW。
S312，源U-GW向C-GW回复数据转发隧道建立响应。
为区别于本发明实施例其它步骤的数据转发隧道建立响应，并与其所对应的数据转发隧道建立请求匹配相应的数字标识，将源U-GW发送给C-GW的数据转发隧道建立响应命名为数据转发隧道建立响应3。
源U-GW向C-GW回复数据转发隧道建立响应3，以响应C-GW发送的数据转发隧道建立请求3，确认允许建立转发U-GW与源U-GW之间的数据转发隧道。
S313，源U-GW与转发U-GW之间建立数据转发隧道。
在获得对端U-GW的地址与隧道端口信息后，源U-GW与转发U-GW之间建立数据转发隧道。
当然，应理解，如果步骤S304中确定多个转发U-GW，例如源转发U-GW和目标转发U-GW，则相应的建立源U-GW与源转发U-GW、目标转发U-GW 与目标转发U-GW之间的数据转发隧道。
S314，C-GW向MME回复数据转发隧道建立响应。
为区别于本发明实施例其它步骤的数据转发隧道建立响应，并与其所对应的数据转发隧道建立请求匹配相应的数字标识，将C-GW发送给MME的数据转发隧道建立响应命名为数据转发隧道建立响应1。
源U-GW与转发U-GW之间建立数据转发隧道后，C-GW回复数据转发隧道建立响应1给MME，指示MME数据转发隧道已经建立，可以进行业务切换。
S315，MME发送切换命令给源基站。
MME发送切换命令给源基站，并携带转发U-GW的地址与隧道端口信息。如果需要多个转发U-GW，例如源转发U-GW和目标转发U-GW，则携带处于UE源位置区域的源转发U-GW的地址与隧道端口信息。
S316，源基站执行数据切换流程
源基站继续执行已有的数据切换流程，将UE切换到目标小区并指示UE从目标小区进行接入，后续步骤可重用已有的切换流程，实现UE到目标位置的完整切换。
在切换过程中与切换完成后上行/下行用户面数据传输路径变成：UE—目标基站—转发U-GW—源U-GW，即图3中的虚线L3a、L4a、L5a和L6a所示的传输路径。需要说明的是，在切换前、中、后，上行/下行用户面数据传输路径都经过了源U-GW，但是考虑到源U-GW与转发U-GW的位置均已经下移到更靠近UE的位置，故源U-GW与转发U-GW之间的距离也会很近，从而不会显著增加用户面数据的RTT。当C-GW确定两个或两个以上的U-GW作为转发U-GW时，其数据转发隧道的路径经过所有的转发U-GW，例如，如果转发U-DW包括目标转发U-DW和源转发U-DW，则传输路径变成：UE—目标基站—目标转发U-GW—源转发U-GW—源U-GW。
应理解，本发明实施例中建立的数据转发隧道是通过在服务该UE的源U-GW与该转发U-GW之间，以及转发U-GW与该UE的目标基站之间建立用户面承载上下文实现的，该用户面承载上下文包含了转发用户面数据所需的路由信息(比如，地址与隧道端口信息)，包括该源U-GW的路由信息，该转发U-GW的路由信息和该目标基站的路由信息，这个同样适用于本发明其它的实施例。
本发明实施例中，C-GW根据UE的当前位置信息确定转发U-GW，并通过建立源U-GW与转发U-GW之间的数据转发隧道来保证UE移动过程中业务的连续性，保证用户业务体验。
图4是本发明实施例保持业务连续性的另一种交互流程图。在图4中，源基站为UE移动到当前位置区域前的服务基站；目标基站为UE移动到当前位置区域后的服务基站；UE所属的服务MME和服务C-GW在UE的移动前后保持不变；源U-GW为UE移动到当前位置区域前的服务U-GW；目标U-GW为UE移动到当前位置区域后的U-GW；转发U-GW为UE移动到当前位置区域后用于切换数据业务的U-GW。在业务切换之前，上行/下行用户面数据传输路径为UE—源基站—源U-GW，即图4中的虚线L1b和L2b所示的传输路径。
S401，源基站发起连接态UE用户面数据切换流程。
S402，源基站向MME发送业务切换请求消息。
S403，MME向C-GW发送业务切换通知消息。
S404，C-GW确定目标U-GW和转发U-GW。
步骤S401-S404的具体实现可参考图3的步骤S301-S04。
S405，C-GW向目标U-GW发送建立会话请求。
C-GW在选择合适的目标U-GW后，可向目标U-GW发起建立会话请求，以在目标U-GW上为UE建立用户面数据传输所需的承载上下文。
S406，目标U-GW向C-GW发送会话建立响应。
目标U-GW根据建立会话请求，为UE建立该UE的用户面数据传输所需的承载上下文，其中，所建立的每个所述承载上下文都包含了目标U-GW的地址(例如IP地址等)与隧道端口信息(例如GTP TEID等)。
承载建立完毕后，目标U-GW可向C-GW发送会话建立响应。
S407，C-GW向MME回复切换通知确认消息。
C-GW回复切换通知确认消息给MME，并在该消息中携带C-GW所选择的目标U-GW的地址与隧道端口信息。
S408，MME发送业务切换请求消息给目标基站。
MME发送业务切换请求消息给目标基站，并携带C-GW发送的目标U-GW的地址与隧道端口信息。
S409，目标基站向MME回复切换请求确认消息。
目标基站收到MME发送的业务切换请求消息后，可向MME回复切换请求确认消息，并将其自身的地址(例如IP地址)与隧道端口信息(例如GTP TEID)发送给MME。类似地，目标基站的地址与隧道端口信息可携带在切换请求确认消息中发送，也可单独发送。
S410，MME向C-GW发送数据转发隧道建立请求。
S411，C-GW向转发U-GW发送数据转发隧道建立请求。
S412，转发U-GW向C-GW回复数据转发隧道建立响应。
S413，C-GW向源U-GW发送数据转发隧道建立请求。
S414，源U-GW向C-GW回复数据转发隧道建立响应。
S415，源U-GW与转发U-GW之间建立数据转发隧道。
S416，C-GW向MME回复数据转发隧道建立响应。
S417，MME发送切换命令给源基站。
步骤S410-S417的具体实现可参考图3的步骤S308-S315。
S418，源基站执行数据切换流程。
源基站继续执行已有的数据切换流程，将UE切换到目标小区并指示UE从目标小区进行接入，后续步骤可重用已有的切换流程，实现UE到目标位置的完整切换。
切换过程中与切换完成后下行用户面数据传输路径为：源基站—源U-GW—转发U-GW—目标基站—UE，即图4中的虚线L3b、L4b、L5b和L6b所示的传输路径；切换过程中与切换完成后上行用户面数据传输路径为：UE—目标基站—目标U-GW，即图4中的虚线L7b和L8b所示的传输路径。
本发明实施例中，C-GW根据UE的当前位置信息决定服务的U-GW是否需要改变并根据所选择的目标U-GW与源U-GW之间是否可以直接通信来选择转发U-GW，通过建立源U-GW与转发U-GW之间的数据转发隧道来保证UE移动过程中业务的连续性，保证用户业务体验。同时，C-GW直接发起目标U-GW的承载上下文建立请求，并将目标U-GW的路由信息通过MME告诉目标基站，使得上行数据可以直接从目标基站发送给目标U-GW，无需再经过转发U-GW与源U-GW，实现了上行数传的路由优化。
应理解，图3、图4所示实施例的交互流程适用于UE的服务MME和服务C-GW在UE移动前后保持不变的场景。如果在UE发生移动的前后，UE的服务MME发生变化而服务C-GW不变，则只需在本发明实施例所示 方案的基础上，在源MME与目标MME之间增加信令交互，其交互过程属于已有技术，本发明在此不再赘述。
图5是本发明实施例保持业务连续性的再一种交互流程图。在图5中，源基站为UE移动到当前位置区域前的服务基站；目标基站为UE移动到当前位置区域后的服务基站；源MME为UE移动到当前位置区域前的服务MME；目标MME为UE移动到当前位置区域后的服务MME；源C-GW为UE移动到当前位置区域前的服务C-GW；目标C-GW为UE移动到当前位置区域后的服务C-GW；源U-GW为UE移动到当前位置区域前的服务U-GW；目标U-GW为UE移动到当前位置区域后的U-GW；转发U-GW为UE移动到当前位置区域后用于切换数据业务的U-GW。在业务切换之前，上行/下行用户面数据传输路径为UE—源基站—源U-GW，即图5中的虚线L1c和L2c所示的传输路径。
本发明实施例业务切换的具体流程如下：
S501，源基站发起连接态UE用户面数据切换流程。
当UE的源基站感知到UE移动出源基站的服务范围，且UE正在进行用户面的数据业务时，源基站可决定发起连接态用户面数据业务切换流程。
S502，源基站向源MME发送业务切换请求消息。
为区别于本发明实施例其它步骤的业务切换请求消息，将源基站发送给源MME的业务切换请求消息命名为业务切换请求消息1。
源基站发送业务切换请求消息1给当前的服务MME(即图5的源MME)，在该消息中携带UE的当前位置信息。UE的当前位置信息，包括UE的当前位置区域所对应的TAI和/或UE的当前位置区域所对应的服务基站信息等。UE移动到当前位置区域所对应的TAI，即为UE的目标TAI；UE移动到当前位置区域所对应的服务基站信息，即为UE的目标基站信息。目标基站信息，可以是目标基站标识(Identity，ID)、目标小区标识(Cell Identity，CI)，等等。可理解的，UE的当前位置区域，也称为UE的目标位置区域，也即UE移出源服务基站的服务范围后所在的位置区域，类似地，UE的当前位置信息，也称为UE的目标位置信息。
S503，源MME向目标MME发送转发重定位请求消息。
源MME根据UE的当前位置信息决定UE是否移出了源MME的服务范围，如果移出了源MME的服务范围，源MME根据UE的当前位置信息 选择合适的目标MME，向目标MME发送转发重定位请求消息，并携带UE的当前位置信息。其中，目标MME即为UE移动到当前位置区域后为该UE提供服务的MME。
S504，目标MME确定目标C-GW。
目标MME根据UE的当前位置信息决定当前UE的服务C-GW是否需要重新分配，即UE是否移出了源C-GW的服务范围，如果需要重分配，目标MME根据UE的当前位置信息选择一个合适的目标C-GW。
S505，目标MME向源MME发送服务C-GW改变通知消息
目标MME向源MME发送服务C-GW改变通知消息，旨在通知源MME该UE的服务C-GW需要改变。在向源MME发送服务C-GW改变通知消息时，可以重用已有的消息，例如改变通知请求(Change Notification Request)消息，并在消息中增加新的指示信息，也可以重新定义新的消息，本发明实施例不做限定。
S506，源MME向源C-GW发送业务切换通知消息。
为区别于本发明实施例其它步骤的业务切换通知消息，将源MME发送给源C-GW的业务切换通知消息命名为业务切换通知消息1。
UE的服务MME(源MME)在接收到业务切换请求消息1后，获知UE移出了当前基站(源基站)的服务范围，则发送业务切换通知消息1给当前的服务C-GW(源C-GW)，并携带服务C-GW改变指示信息。源MME可以重用已有的消息以发送该业务切换通知消息1，比如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息，并在这些消息中携带UE的当前位置信息；源MME也可以重新定义新的消息以发送该业务切换通知消息1，对此本发明实施例不做限定。
S507，源C-GW向源MME发送切换通知确认。
为区别于本发明实施例其它步骤的切换请求确认消息，并与其所对应的业务切换请求消息匹配相应的数字标识，将源C-GW发送给源MME的切换请求确认消息命名为切换通知确认消息1。
源C-GW根据源MME发送的业务切换通知消息1后，可向源MME回复切换通知确认消息1，并携带源U-GW的地址(如IP地址等)与隧道端口信息(如GTP TEID等)。
S508，源MME向目标MME回复C-GW改变通知确认。
源MME向目标MME回复C-GW改变通知确认，并携带源U-GW的地址(如IP地址)与隧道端口信息(如GTP TEID)。
S509，目标MME向目标C-GW发送业务切换通知消息。
为区别于本发明实施例其它步骤的业务切换通知消息，将目标MME发送给目标C-GW的业务切换通知消息命名为业务切换通知消息2。
目标MME向目标C-GW发送业务切换通知消息2，该业务切换通知消息2中携带了UE的当前位置信息，包括目标TAI和目标基站信息(基站ID)等。需要说明的是，该业务切换通知消息旨在通知C-GW，UE需要被切换到新的目标位置区域(即UE的当前位置区域)。目标MME可以重用已有的消息以发送业务切换通知消息2，比如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息，并在这些消息中携带UE目标位置信息；目标MME也可以重新定义新的消息以发送业务切换通知消息2，对此本发明实施例不做限定。
S510，目标C-GW确定目标U-GW和转发U-GW。
在获知切换请求后，目标C-GW根据UE的当前位置信息选择一个合适的目标U-GW，确保该目标U-GW能够为UE在所述目标位置提供最佳的数据传输路径，尽可能地减少用户面数据传输RTT。
此外，目标C-GW需要检查该目标U-GW与源U-GW之间是否可以直接通信。如果目标U-GW可以与源U-GW直接通信，则目标U-GW就是转发U-GW，也即后续所有到转发U-GW的步骤都是到目标U-GW；如果目标U-GW不能与源U-GW直接通信，则目标C-GW根据UE的当前位置信息选择一个与源U-GW可以直接通信的U-GW作为转发U-GW。
需要说明的是，为保证特殊场景下业务的连续性，转发U-GW可以多于一个。典型地，如果UE移动到邻近的U-GW pool，则目标C-GW选择该邻近U-GW pool中的缺省U-GW作为目标转发U-GW。如果该缺省U-GW与源U-GW之间也不能直接通信，进一步地，目标C-GW可以选择源U-GW所在的U-GW pool中的缺省U-GW作为源转发U-GW，通过两个转发U-GW来确保UE移动过程中的业务连续性。
S511，目标C-GW向目标MME发送切换通知确认消息。
为区别于本发明实施例其它步骤的切换请求确认消息，并与其所对应的业务切换请求消息匹配相应的数字标识，将目标C-GW发送给目标MME的切换请求确认消息命名为切换通知确认消息2。
目标C-GW在确定转发U-GW后，可根据目标MME的业务切换通知消息2，回复切换通知确认消息2给目标MME，并在该消息中携带目标C-GW所选择的转发U-GW的地址(如IP地址)与隧道端口信息(如GTP TEID)。
如果有多个转发U-GW，例如源转发U-GW和目标转发U-GW，则目标C-GW在切换通知确认消息中携带处于UE的当前位置区域的目标转发U-GW的地址与隧道端口信息。在向目标MME发送切换通知确认消息时，目标C-GW可以重用已有的消息，比如建立会话响应(Create Session Response)消息或修改承载响应(Modify Bearer Response)消息或修改接入承载响应(Modify Access Bearers Response)消息，或定义新的消息，以发送切换通知确认消息2，本发明实施例不做限定。
S512，目标MME发送业务切换请求消息给目标基站。
为区别于本发明实施例其它步骤的业务切换请求消息，将目标MME发送给目标基站的业务切换请求消息命名为业务切换请求消息2。
目标MME发送业务切换请求消息2给目标基站，并将转发U-GW的地址与隧道端口信息发送给目标基站，以备后续上行数据传输路径切换到转发U-GW上。
S513，目标基站向目标MME发送切换请求确认消息。
为区别于本发明实施例其它步骤的切换请求确认消息，并与其所对应的业务切换请求消息匹配相应的数字标识，将目标基站发送给目标MME的切换请求确认消息命名为切换请求确认消息2。
目标基站回复切换请求确认消息2，并将其自身的地址(比如IP地址)与隧道端口信息(比如GTP TEID)发送给目标MME。
S514，目标MME向目标C-GW发送数据转发隧道建立请求。
为区别于本发明实施例其它步骤的数据转发隧道建立请求，将目标MME发送给目标C-GW的数据转发隧道建立请求命名为数据转发隧道建立请求1。
目标MME向目标C-GW发送数据转发隧道建立请求1，并将目标基站的地址与隧道端口信息发送给C-GW，以备后续下行数据传输路径切换到目 标基站上。
S515，目标C-GW向转发U-GW发送数据转发隧道建立请求。
为区别于本发明实施例其它步骤的数据转发隧道建立请求，将目标C-GW发送给转发U-GW的数据转发隧道建立请求命名为数据转发隧道建立请求2。
目标C-GW向转发U-GW发送数据转发隧道建立请求2，并将目标基站的地址与隧道端口信息与源U-GW的地址与隧道端口信息发送给转发U-GW。
如果需要多个转发U-GW，则目标C-GW应该向每个转发U-GW发送数据转发隧道建立请求，并携带对端网元的地址与隧道端口信息。
S516，转发U-GW向目标C-GW回复数据转发隧道建立响应。
为区别于本发明实施例其它步骤的数据转发隧道建立响应，并与其所对应的数据转发隧道建立请求相对应，将转发U-GW发送给目标C-GW的数据转发隧道建立响应命名为数据转发隧道建立响应2。
转发U-GW向目标C-GW回复数据转发隧道建立响应2，以响应目标C-GW发送的数据转发隧道建立请求2，确认允许建立目标基站与转发U-GW之间，以及源U-GW与转发U-GW之间的数据转发隧道，可选地，该数据转发隧道建立响应2可以携带该转发U-GW的地址与隧道端口信息。
如果步骤S510中需要多个转发D-GW，C-GW应该向每个转发D-GW发送数据转发隧道建立请求，相应的每个转发D-GW都应回复数据转发隧道建立响应，指示允许建立数据转发隧道。
S517，目标C-GW向目标MME回复数据转发隧道建立响应。
为区别于本发明实施例其它步骤的数据转发隧道建立响应，并与其所对应的数据转发隧道建立请求匹配相应的数字标识，将目标C-GW发送给目标MME的数据转发隧道建立响应命名为数据转发隧道建立响应1。
目标C-GW在收到数据转发隧道建立响应2后，回复数据转发隧道建立响应1给目标MME，确认允许建立目标基站与转发U-GW之间的数据转发隧道。
S518，目标MME向源MME发送转发重定位响应。
目标MME在确定可以建立目标基站与转发U-GW的数据转发隧道之后，可向源MME发送转发重定位响应，并携带转发U-GW的地址与隧道端 口信息。
S519，源MME向源C-GW发送数据转发隧道建立请求。
为区别于本发明实施例其它步骤的数据转发隧道建立请求，将源MME发送给源U-GW的数据转发隧道建立请求命名为数据转发隧道建立请求3。
源MME向源C-GW发送数据转发隧道建立请求3，并将转发U-GW的地址与隧道端口信息发送给源C-GW。
S520，源C-GW向源U-GW发送数据转发隧道建立请求。
为区别于本发明实施例其它步骤的数据转发隧道建立请求，将源C-GW发送给源U-GW的数据转发隧道建立请求命名为数据转发隧道建立请求4。
源C-GW向源U-GW发送数据转发隧道建立请求4，并将转发U-GW的地址与隧道端口信息发送给源U-GW。
S521，源U-GW向源C-GW发送数据转发隧道建立响应。
为区别于本发明实施例其它步骤的数据转发隧道建立响应，并与其所对应的数据转发隧道建立请求匹配相应的数字标识，将源U-GW发送给源C-GW的数据转发隧道建立响应命名为数据转发隧道建立响应4。
源U-GW在接收到源C-GW发送的数据转发隧道建立请求4后，可回复数据转发隧道建立响应4，确认允许建立转发U-GW与源U-GW之间的数据转发隧道。
S522，源U-GW与转发U-GW之间建立数据转发隧道。
在获得对端U-GW的地址与隧道端口信息后，源U-GW与转发U-GW之间建立数据转发隧道。
当然，应理解，如果步骤S510中确定多个转发U-GW，例如源转发U-GW和目标转发U-GW，则相应的建立源U-GW与源转发U-GW、源转发U-GW与目标转发U-GW之间的数据转发隧道。
S523，源C-GW发送数据转发隧道建立响应给源MME。
为区别于本发明实施例其它步骤的数据转发隧道建立响应，并与其所对应的数据转发隧道建立请求匹配相应的数字标识，将源C-GW发送给源MME的数据转发隧道建立响应命名为数据转发隧道建立响应3。
源C-GW收到数据转发隧道建立响应4后，可向源MME发送数据转发隧道建立响应3，确认允许建立转发U-GW与源U-GW之间的数据转发隧道。
S524，源MME发送切换命令给源基站。
源MME发送切换命令给源基站，并携带转发U-GW的地址与隧道端口信息。
如果需要多个转发U-GW，则在切换命令中携带处于UE源位置区域的源转发U-GW的地址与隧道端口信息。
S524，源基站继续执行已有的数据切换流程，将UE切换到目标小区并指示UE从目标小区进行接入，后续重用已有的切换流程实现UE到目标位置的完整切换。
在切换过程中与切换完成后上行/下行用户面数据传输路径变成：UE—目标基站—转发U-GW—源U-GW，即图5中的虚线L3c、L4c、L5c和L6c所示的传输路径。需要说明的是，在切换前、中、后，上行/下行用户面数据传输路径都经过了源U-GW，但是考虑到源U-GW与转发U-GW的位置均已经下移到更靠近UE的位置，故源U-GW与转发U-GW之间的距离也会很近，从而不会显著增加用户面数据的RTT。
本发明实施例中，目标C-GW根据UE的当前位置信息确定转发U-GW，并通过建立源U-GW与转发U-GW之间的数据转发隧道来保证UE移动过程中业务的连续性，保证用户业务体验。
图6是本发明实施例保持业务连续性的再一种交互流程图。在图6中，源基站为UE移动到当前位置区域前的服务基站；目标基站为UE移动到当前位置区域后的服务基站；源MME为UE移动到当前位置区域前的服务MME；目标MME为UE移动到当前位置区域后的服务MME；源C-GW为UE移动到当前位置区域前的服务C-GW；目标C-GW为UE移动到当前位置区域后的服务C-GW；源U-GW为UE移动到当前位置区域前的服务U-GW；目标U-GW为UE移动到当前位置区域后的U-GW；转发U-GW为UE移动到当前位置区域后用于切换数据业务的U-GW。在业务切换之前，上行/下行用户面数据传输路径为UE—源基站—源U-GW，即如图6中的虚线L1和L2所示的传输路径。
本发明实施例业务切换的具体流程如下：
S601，源基站发起连接态UE用户面数据切换流程。
S602，源基站发送业务切换请求消息。
S603，源MME发送转发重定位请求消息。
S604，目标MME确定目标C-GW。
S605，目标MME向源MME发送服务C-GW改变通知消息
S606，源MME向源C-GW发送业务切换通知消息。
S607，源C-GW向源MME发送切换通知确认。
S608，源MME向目标MME回复C-GW改变通知确认。
S609，目标MME向目标C-GW发送业务切换通知消息。
S610，目标C-GW确定目标U-GW和转发U-GW。
步骤S601-S610的具体实现可参考图5的步骤S501-S510。
S611，目标C-GW向目标U-GW发送建立会话请求。
目标C-GW在选择合适的目标U-GW后，可向目标U-GW发起建立会话请求，以在目标U-GW上为UE建立用户面数据传输所需的承载上下文。
S612，目标U-GW向目标C-GW发送会话建立响应。
目标U-GW根据建立会话请求，为UE建立该UE的用户面数据传输所需的承载上下文，其中，所建立的每个所述承载上下文都包含了目标U-GW的地址(例如IP地址等)与隧道端口信息(例如GTP TEID等)。
承载建立完毕后，目标U-GW可向目标C-GW发送会话建立响应。
S613，目标C-GW向目标MME发送切换通知确认消息。
为区别于本发明实施例其它步骤的切换请求确认消息，并与其所对应的业务切换请求消息匹配相应的数字标识，将目标C-GW发送给目标MME的切换请求确认消息命名为切换通知确认消息2。
目标C-GW在确定转发U-GW后，可根据目标MME的业务切换通知消息2，回复切换通知确认消息2给目标MME，并在该消息中携带目标C-GW所选择的目标U-GW的地址(如IP地址)与隧道端口信息(如GTP TEID)。
S614，目标MME发送业务切换请求消息给目标基站。
为区别于本发明实施例其它步骤的业务切换请求消息，将目标MME发送给目标基站的业务切换请求消息命名为业务切换请求消息2。
目标MME发送业务切换请求消息2给目标基站，并携带目标C-GW发送的目标U-GW的地址与隧道端口信息。
S615，目标基站向目标MME发送切换请求确认消息。
为区别于本发明实施例其它步骤的切换请求确认消息，并与其所对应的业务切换请求消息匹配相应的数字标识，将目标基站发送给目标MME的切换请求确认消息命名为切换请求确认消息2。
目标基站回复切换请求确认消息2，并将其自身的地址(比如IP地址)与隧道端口信息(比如GTP TEID)发送给目标MME。
S616，目标MME向目标C-GW发送数据转发隧道建立请求。
S617，目标C-GW向转发U-GW发送数据转发隧道建立请求。
S618，转发U-GW向目标C-GW回复数据转发隧道建立响应。
S619，目标C-GW向目标MME回复数据转发隧道建立响应。
S620，目标MME向源MME发送转发重定位响应。
S621，源MME向源C-GW发送数据转发隧道建立请求。
S622，源C-GW向源U-GW发送数据转发隧道建立请求。
S623，源U-GW向源C-GW发送数据转发隧道建立响应。
S624，源U-GW与转发U-GW之间建立数据转发隧道。
S625，源C-GW发送数据转发隧道建立响应给源MME。
S626，源MME发送切换命令给源基站。
步骤S616-S626的具体实现可参考图5的步骤S514-S524。
S627，源基站继续执行已有的数据切换流程，将UE切换到目标小区并指示UE从目标小区进行接入，后续重用已有的切换流程实现UE到目标位置的完整切换。
切换过程中与切换完成后下行用户面数据传输路径为：源基站—源U-GW—转发U-GW—目标基站—UE，即图6中的虚线L3d、L4d、L5d和L6d所示的传输路径；切换过程中与切换完成后上行用户面数据传输路径为：UE—目标基站—目标U-GW，即图6中的虚线L7d和L8d所示的传输路径。
本发明方案实施例中，目标C-GW根据UE的当前位置信息决定服务的U-GW是否需要改变并根据所选择的目标U-GW与源U-GW之间是否可以直接通信来选择转发U-GW，通过建立源U-GW与转发U-GW之间的数据转发隧道来保证UE移动过程中业务的连续性，保证用户业务体验。同时，C-GW直接发起目标U-GW的承载上下文建立请求，并将目标U-GW的路由信息通过MME告诉目标基站，使得上行数据可以直接从目标基站发送给目标U-GW，无需再经过转发U-GW与源U-GW，实现了上行数传的路由优化。
应理解，图5、图6所示实施例的交互流程适用于UE的服务MME和服务C-GW在UE移动前后均发生变化的场景。如果在UE发生移动的前后， UE的服务C-GW发生变化而服务MME不变，则只需在本发明实施例所示方案的基础上，减少源MME与目标MME之间的信令交互，本发明在此不再赘述。
图7是本发明实施例保持业务持续性的再一种交互流程图。在图7中，目标基站为UE在当前位置区域由空闲态转为连接态的服务基站；源U-GW为UE移动到当前位置区域前的服务U-GW；目标U-GW为UE在当前位置区域由空闲态转为连接态的服务U-GW；转发U-GW为UE移动到当前位置区域后用于切换数据业务的U-GW；MME为UE在当前位置区域由空闲态转为连接态的服务MME；C-GW为UE在当前位置区域由空闲态转为连接态的服务C-GW。
本发明实施例的具体流程如下：
S701，空闲态UE需要发送上行用户面数据。
S702，UE向MME发送信令请求。
如果空闲态UE移出了当前注册的位置区域(例如，当前注册的跟踪域(Tracking Area，TA))，此时UE可通过向MME发送信令请求，以发起位置更新流程。例如，该位置更新流程为跟踪域更新(Tracking Area Update，TAU)流程)，则该信令请求为位置更新请求消息。
如果空闲态UE移出了当前服务基站的服务区域但没有移出当前注册的位置区域(例如，当前注册的TA)，UE可通过向MME发送信令请求以发起业务请求(Service Request)流程，该信令请求为业务请求消息。
具体地，UE可将该信令请求消息通过目标基站发送给服务MME，目标基站将UE的当前位置信息发送给MME。
UE的当前位置信息，包括UE的当前位置区域所对应的跟踪域标识(Tracking Area Identity，TAI)和/或UE的当前位置区域所对应的服务基站信息等。UE移动到当前位置区域所对应的TAI，即为UE的目标TAI；UE移动到当前位置区域所对应的服务基站信息，即为UE的目标基站信息。目标基站信息，可以是目标基站标识(Identity，ID)、目标小区标识(Cell Identity，CI)，等等。UE的当前位置区域，也称为UE的目标位置区域，也即UE移出源服务基站的服务范围后所在的位置区域，类似地，UE的当前位置信息，也称为UE的目标位置信息。
S703，MME向C-GW发送请求消息并在该请求消息中携带UE的当前 位置信息。
UE的服务MME在接收到位置更新请求消息或业务请求消息后，根据UE的当前位置信息获知UE移出了当前基站(源基站)的服务范围，则发送请求消息给当前的服务C-GW。该请求消息旨在通知C-GW，UE移动到新的目标位置区域。MME可以重用已有的消息，比如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息，也可以重新定义新的消息，对此本发明实施例不做限定。
S704，C-GW确定目标U-GW和转发U-GW。
C-GW在接收到MME发送的请求消息后，可根据UE的当前位置信息确定目标U-GW和转发U-GW，具体实现可参考图3所示实施例的步骤S304，在此不再赘述。
S705，C-GW向MME回复请求确认消息。
C-GW回复请求确认消息给MME，具体实现可参考图3所示实施例的步骤S305，在此不再赘述。
S706，MME发送初始上下文建立请求给目标基站。
MME发送初始上下文建立请求(Initial Context Setup Request)消息给目标基站，并将C-GW发送的转发U-GW的地址与隧道端口信息转发给目标基站，以备后续上行数据传输路径切换到转发U-GW上。
S707，目标基站向MME回复初始上下文建立响应消息。
目标基站向MME回复初始上下文建立响应(Initial Context Setup Response)消息，并将其自身的地址(例如IP地址)与隧道端口信息(例如GTP TEID)发送给MME。
S708，MME向C-GW发送修改承载请求。
MME向C-GW发送修改承载请求消息，并将目标基站的地址与隧道端口信息发送给C-GW，以备后续将下行数据传输路径切换到目标基站上。可选地，该步骤中，MME可以发送修改接入承载请求消息并携带目标基站的地址与隧道端口信息给C-GW。
S709，C-GW向转发U-GW发送数据转发隧道建立请求。
S710，转发U-GW向C-GW回复数据转发隧道建立响应。
S711，C-GW向源U-GW发送数据转发隧道建立请求。
S712，源U-GW向C-GW回复数据转发隧道建立响应。
S713，源U-GW与转发U-GW之间建立数据转发隧道。
步骤S709-S713的具体实现可参考图3所示实施例步骤S309-S313，在此不再赘述。
S714，C-GW向MME回复修改承载响应。
可选地，与步骤S708对应，C-GW可以回复修改接入承载响应消息给MME。
在位置更新流程或业务请求流程中上行/下行用户面数据传输路径变成：UE—目标基站—转发U-GW—源U-GW，即图7中的虚线L1e、L2e和L3e所示的传输路径。需要说明的是，上行/下行用户面数据传输路径都经过了源U-GW，但是考虑到源U-GW与转发U-GW的位置均已经下移到更靠近UE的位置，故源U-GW与转发U-GW之间的距离也会很近，从而不会显著增加用户面数据的RTT。当C-GW确定两个或两个以上的U-GW作为转发U-GW时，其数据转发隧道的路径经过所有的转发U-GW，例如，如果转发U-DW包括目标转发U-DW和源转发U-DW，则传输路径变成：UE—目标基站—目标转发U-GW—源转发U-GW—源U-GW。
本发明实施例中，C-GW根据UE的当前位置信息确定转发U-GW，并通过建立源U-GW与转发U-GW之间的数据转发隧道来保证UE移动过程中业务的连续性，保证用户业务体验。
图8是本发明实施例保持业务持续性的再一种交互流程图。在图8中，目标基站为UE在当前位置区域由空闲态转为连接态的服务基站；源U-GW为UE移动到当前位置区域前的服务U-GW；目标U-GW为UE在当前位置区域由空闲态转为连接态的服务U-GW；转发U-GW为UE移动到当前位置区域后用于切换数据业务的U-GW；MME为UE在当前位置区域由空闲态转为连接态的服务MME；C-GW为UE在当前位置区域由空闲态转为连接态的服务C-GW。
本发明实施例的具体流程如下：
S801，空闲态UE需要发送上行用户面数据。
S802，UE向MME发送信令请求。
步骤S802的具体实现可参考图7的步骤S702，在此不再赘述。
S803，MME发送初始上下文建立请求给目标基站。
MME发送初始上下文建立请求(Initial Context Setup Request)消息给目标基站，该步骤为现有位置更新流程或业务请求流程中的已有步骤，故这里MME将源U-GW的地址与隧道端口信息发送给目标基站。
S804，目标基站向MME回复初始上下文建立响应消息。
目标基站向MME回复初始上下文建立响应(Initial Context Setup Response)消息，并将其自身的地址(例如IP地址)与隧道端口信息(例如GTP TEID)发送给MME。
S805，MME向C-GW发送修改承载请求。
MME向C-GW发送修改承载请求消息，并将UE的当前位置信息和目标基站的地址与隧道端口信息发送给C-GW。可选地，该步骤中，MME可以发送修改接入承载请求消息并携带UE的当前位置信息和目标基站的地址与隧道端口信息给C-GW。
S806，C-GW确定目标U-GW和转发U-GW。
C-GW在接收到MME发送的修改承载请求消息后，可根据UE的当前位置信息确定目标U-GW和转发U-GW，具体实现可参考图3所示实施例的步骤S304，在此不再赘述。
S807，C-GW向转发U-GW发送数据转发隧道建立请求。
S808，转发U-GW向C-GW回复数据转发隧道建立响应。
S809，C-GW向源U-GW发送数据转发隧道建立请求。
S810，源U-GW向C-GW回复数据转发隧道建立响应。
S811，源U-GW与转发U-GW之间建立数据转发隧道。
步骤S807-S811的具体实现可参考图3所示实施例步骤S309-S313，在此不再赘述。
S812，C-GW向MME回复修改承载响应。
C-GW向MME回复修改承载响应消息，并将确定的转发U-GW的地址与隧道端口信息发送给MME。可选地，与步骤S805对应，MME可以回复修改接入承载响应消息给MME，并携带转发U-GW的地址与隧道端口信息。
S813，MME发送UE上下文修改请求给目标基站。
MME发送UE上下文修改请求(UE Context Modification Request)消息给目标基站，并在该消息中携带转发U-GW的地址与隧道端口信息，以便后续上行用户面数据传输路径切换到该转发U-GW。需要说明的是，该步骤相 对于现有位置更新流程或业务请求流程是个新增的步骤。
S814，目标基站向MME回复UE上下文修改响应消息。
目标基站向MME回复UE上下文修改响应(UE Context Modification Response)消息。
在位置更新流程或业务请求流程中上行/下行用户面数据传输路径变成：UE—目标基站—转发U-GW—源U-GW，即图8中的虚线L1f、L2f和L3f所示的传输路径。需要说明的是，上行/下行用户面数据传输路径都经过了源U-GW，但是考虑到源U-GW与转发U-GW的位置均已经下移到更靠近UE的位置，故源U-GW与转发U-GW之间的距离也会很近，从而不会显著增加用户面数据的RTT。当C-GW确定两个或两个以上的U-GW作为转发U-GW时，其数据转发隧道的路径经过所有的转发U-GW，例如，如果转发U-DW包括目标转发U-DW和源转发U-DW，则传输路径变成：UE—目标基站—目标转发U-GW—源转发U-GW—源U-GW。
本发明实施例中，C-GW根据UE的当前位置信息确定转发U-GW，并通过建立源U-GW与转发U-GW之间的数据转发隧道来保证UE移动过程中业务的连续性，保证用户业务体验。
图9是本发明实施例保持业务持续性的另一种方法流程图。图9的方法目标移动管理网元执行。该方法包括:
901，目标移动管理网元接收服务UE的源移动管理网元发送的转发重定位请求。
其中，该转发重定位请求携带该UE的当前位置信息。
步骤901的具体实现可参考图5的步骤503或图6的步骤603。
本发明实施例的应用场景中，UE在进行业务通信时，移动后的位置区域超出源移动管理网元(例如，MME)的服务范围。源移动管理网元为UE移动到当前位置区域之前的服务移动管理网元。
902，该目标移动管理网元根据该UE的当前位置信息选择该UE的目标C-GW。
步骤902的具体实现可参考图5的步骤504或图6的步骤604。
903，该目标移动管理网元向该目标C-GW发送该UE的当前位置信息，以便该目标C-GW根据该UE的当前位置信息确定该UE的转发U-GW。
步骤902的具体实现可参考图5的步骤509或图6的步骤609。
904，该目标移动管理网元向该目标C-GW发送数据转发隧道建立请求。
其中，该数据转发隧道建立请求用于请求该目标控制面网关在该转发U-GW与服务该用户设备的源U-GW之间，以及该转发U-GW与服务该用户设备的目标基站之间为该用户设备建立数据转发隧道。
步骤904的具体实现可参考图5的步骤514或图6的步骤616。
本发明实施例中，目标移动管理网元在UE移动出源移动管理网元的服务范围后，根据UE的当前位置信息确定UE的目标C-GW，进而通过目标C-GW在该源U-GW与UE的目标基站之间为该UE建立数据转发隧道，从而能够保证UE移动过程中的业务连续性，提高用户的业务体验。
可选地，作为一个实施例，该目标C-GW与该UE移动到当前位置区域之前的服务C-GW不同(即服务C-GW在UE移动过程中发生改变)。此时，在步骤902之后，步骤903之前，该方法还可包括：该目标移动管理网元向该源移动管理网元发送改变通知消息，该改变通知消息用于指示该UE的服务C-GW变更为该目标C-GW。具体实现可参考图5的步骤505或图6的步骤605。
进一步地，在步骤903之前，该方法还可包括：该目标移动管理网元接收该源移动管理网元根据该改变通知消息发送的确认消息，其中，该确认消息携带该UE的源U-GW的路由信息。具体实现可参考图5的步骤508或图6的步骤608。
本发明实施例中，移动管理网元的具体实现可参考图5或图6所示的目标MME执行的方法，本发明实施例在此不再赘述。
图10是本发明实施例保持业务持续性的再一种方法流程图。图10的方法由C-GW执行。该方法包括:
1001，C-GW接收移动管理网元发送的UE的当前位置信息。
本发明实施例可以适用于如下任意一种应用场景中：
(1)连接态UE在进行用户面数据传输时发生了位置移动，移动后的位置区域超出源基站的服务范围，源基站在感知UE移出其服务范围后，决定发起连接态用户面数据业务切换流程。源基站为UE移动到当前位置区域之前的服务基站。
(2)空闲态UE在需要发送上行用户面数据传输时，移出了当前注册的位置区域，比如当前注册的跟踪域(Tracking Area，TA)，UE 发起位置更新流程，比如跟踪域更新(Tracking Area Update，TAU)流程。
(3)空闲态UE在需要发送上行用户面数据传输时，移出了当前服务基站的服务区域但没有移出当前注册的位置区域，比如当前注册的跟踪域(Tracking Area，TA)，UE发起业务请求(Service Request)流程。
在应用场景(1)中，移动管理网元在收到源基站发送的用户面数据切换请求后，可向UE的服务C-GW发送业务切换通知。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发送该业务切换通知，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息等；或者，移动管理网元可以用新建的消息发送该业务切换通知，具体使用哪个消息来发送该业务切换通知，本发明不做限定。
在应用场景(2)中，移动管理网元在接收到该UE发送的位置更新请求后，或者为该UE成功建立空口承载上下文后，可向UE的服务C-GW发送请求消息。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发送该请求消息，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息；或者，移动管理网元可以用新建的消息发送该请求消息，具体使用哪个消息来发送该请求消息，本发明不做限定。
在应用场景(3)中，移动管理网元在接收到该UE发送的业务请求后，或者为该UE成功建立空口承载上下文后，可向UE的服务C-GW发送请求消息。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发送该请求消息，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息；或者，移动管理网元可以用新建的消息发送该请求消息，具体使用哪个消息来发送该请求消息，本发明不做限定。
应理解，该C-GW是服务该UE的C-GW。
应理解，该移动管理网元是服务该UE的移动管理网元。在具体的应用中，该移动管理网元可以是MME，或者具备MME的移动管理功能的其它网元实体。
1002，该C-GW根据该UE的当前位置信息为该UE选择目标U-GW；
1003，该C-GW向该移动管理网元发送请求消息。
该请求消息用于请求该移动管理网元释放第一承载上下文并指示该UE发送第二承载上下文的建立请求，其中，该第一承载上下文是建立在该UE的源U-GW上的该UE的承载上下文，该第二承载上下文是该UE根据该第一承载上下文在该目标U-GW上重建的承载上下文。
可选地，作为一个实施例，该请求消息为删除承载请求消息，该删除承载请求消息携带重新激活请求指示，该重新激活请求指示用于通过该移动管理网元指示该UE在该第一承载上下文删除后，发起该第二承载上下文的建立请求。
应理解，MME和UE都记录着UE在源U-GW上建立的第一承载上下文，当MME接收到删除承载请求消息后，会删除MME上的第一承载上下文，并指示UE删除UE上的第一承载上下文；该删除承载请求消息携带重新激活请求指示时，MME还向UE发送重新激活请求指示，指示UE在删除第一承载上下文后，根据第一承载上下文的内容重新发送承载上下文的建立请求，请求建立第二承载上下文。其中，该第二承载上下文是根据第一承载上下文在目标U-GW上建立的承载上下文，典型地，该第二承载上下文包含与第一承载上下文相同的接入网名称(Access Point Name，APN)。
本发明实施例中，在UE从空闲态变为连接态并发送用户面数据之前，C-GW根据UE的当前位置信息确定UE的服务U-GW，并触发承载上下文去激活流程，并携带重新激活请求指示以指示UE发起承载上下文的重新建立流程，实现承载资源在目标U-GW上的重建，保证后续用户数传的业务连续性，从而保证用户业务体验。
下面，将结合具体的实施例，对本发明实施例的方法作进一步的描述。
图11是本发明实施例保持业务连续性的再一种交互流程图。在图11中，目标基站为UE在当前位置区域由空闲态转为连接态的服务基站。目标U-GW为UE在当前位置区域由空闲态转为连接态的服务U-GW，MME为UE在当前位置区域由空闲态转为连接态的服务MME，C-GW为UE在当前 位置区域由空闲态转为连接态的服务C-GW。
本发明实施例具体流程如下：
S1101，UE向MME发送信令请求。
处于空闲态的UE因为需要进行上行信令或数据的传输，向MME发送信令，请求转变为连接态。UE会发起业务请求(Service Request)流程或跟踪域更新(Tracking Area Update，TAU)流程实现从空闲态到连接态的转变。
在从空闲态到连接态的转变过程中，目标基站，即UE当前服务基站，将UE的当前位置信息上报给当前服务MME，UE的当前位置信息可以为当前的跟踪域标识(Tracking Area Identity，TAI)和/或当前的小区标识(Cell Identity，CI)。
S1102，MME向C-GW发送位置更新通知消息。
MME在接收到UE发送的从空闲态到连接态转变信令请求后，比如接收到业务请求(Service Request)消息或TAU请求消息后，根据基站上报的UE当前位置信息判断UE的位置是否发生了变化。
如果未发生变化，则按照现有技术的方法执行，本发明实施例在此不再赘述。如果发生变化，则MME向UE的C-GW发送位置更新通知消息。此处，MME判断UE的位置变化可包括以下两种场景：
(a)若服务MME没有改变，则MME可以通过对比之前保存的该UE的位置信息与目标基站上报的当前位置信息来判断UE的位置变化；
(b)若MME发生了变化，即该步骤中接受信令请求的是新MM E，则新MME可以认为UE位置发生了变化。
MME发送位置更新通知消息给服务C-GW，该通知消息中携带了UE的当前位置信息，包括当前TAI和/或当前小区标识等。该位置更新通知消息旨在通知C-GW，UE当前的位置区域发生了改变，故MME可以重用已有的消息，比如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息等，来携带UE的当前位置信息；也可以重新定义新的消息来携带UE的当前位置信息，对此本发明不做限定。
此外，MME可以根据UE的当前位置信息判断UE的服务C-GW是否需要重新分配，也即UE是否移出了当前服务C-GW的服务区域。若服务C-GW需要重新分配，则MME根据UE的当前位置信息选择一个新的C-GW 作为服务C-GW，并将位置更新通知消息发送给该新C-GW。必要地，MME还可以请求新C-GW为该UE重建承载上下文。
S1103，C-GW确定U-GW。
C-GW根据UE当前位置信息决定当前UE的服务U-GW是否需要重新分配.若需要重新分配，则C-GW根据UE当前位置信息选择一个合适的目标U-GW，并执行步骤S1104。若在S1102中，C-GW进行了重新分配，则通常地，服务U-GW也需要进行重新分配。
S1104，C-GW向MME发送承载删除请求。
C-GW通过向MME发送承载删除请求，发起到UE的承载去激活流程以释放UE建立在源U-GW上的所有承载上下文资源。此外，该删除承载请求消息携带重新激活请求(Reactivation requested)指示，旨在请求UE在删除源D-GW的所有承载上下文资源后，马上发起分组数据网络(Packet Data Network，PDN)连接建立请求，实现用户面承载资源在目标D-GW的重建。
S1105，MME向UE发送分离请求或去激活承载上下文请求。
MME在收到C-GW的承载删除请求后，根据当前UE的分组数据网络(Packet Data Network，PDN)连接信息执行不同的动作：
(a)若当前UE只有一个PDN连接，则MME发起到UE的分离流程，并在分离请求(Detach Request)中携带重新附着(re-attach required)指示；
(b)若当前UE有多个PDN连接，则MME发起到UE的PDN连接去激活流程，并在去激活承载上下文请求(Deactivate Bearer Context Request)中携带重新激活请求(Reactivation requested)指示。
S1106，UE发起PDN连接建立请求。
UE发起PDN连接建立请求，以恢复步骤S1104中C-GW请求删除的承载上下文，该PDN连接建立请求携带了与步骤S1104中C-GW请求删除的承载上下文相同的APN，在该流程中C-GW使用选择的目标D-GW来建立该UE的承载上下文。
如果步骤S1105中UE收到MME发送的分离请求，则发起附着流程，在附着流程中捎带了PDN连接建立流程，其具体实现可参考现有技术。
如果步骤S1105中UE收到去激活承载上下文请求以去激活一个PDN连接，则发起单独的PDN连接建立流程，其具体实现可参考现有技术。
在PDN连接建立流程中，上行/下行用户面数据传输路径变成：UE—目 标基站—目标U-GW，即图11中的虚线L1g和L2g所示的传输路径。
本发明实施例中，在UE从空闲态变为连接态，并发送用户面数据之前，C-GW根据UE的当前位置信息决定服务U-GW是否需要改变并触发PDN连接去激活流程并携带重新激活请求指示以请求UE马上发起PDN连接重新建立流程，实现承载资源在目标U-GW上的重建，保证后续用户数传的业务连续性，从而保证用户业务体验。
图12是本发明实施例控制面网关1200的结构示意图。如图12所示，控制面网关1200可包括接收单元1201、选择单元1202和隧道建立单元1203，其中
接收单元1201，用于接收移动管理网元发送的UE的当前位置信息。
选择单元1202，用于根据该UE的当前位置信息为该UE选择至少一个转发U-GW。
本发明实施例中，UE的当前位置区域超出UE当前的服务U-GW的服务范围，C-GW需要根据UE的当前位置区域为UE选择合适的转发U-GW。
隧道建立单元1203，用于在服务该UE的源U-GW与该转发U-GW之间，以及该转发U-GW与该UE的目标基站之间，为该UE建立数据转发隧道，其中，该数据转发隧道用于在该UE的移动过程中传输该UE的上行用户面数据和/或下行用户面数据。
本发明实施例的适用场景可参考图2所示实施例的应用场景。
在应用场景(1)中，移动管理网元在收到源基站发送的用户面数据切换请求后，可向UE的服务C-GW发送业务切换通知。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发送该业务切换通知，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息等；或者，移动管理网元可以用新建的消息发送该业务切换通知，具体使用哪个消息来发送该业务切换通知，本发明不做限定。
在应用场景(2)中，移动管理网元在接收到该UE发送的位置更新请求后，或者为该UE成功建立空口承载上下文后，可向UE的服务C-GW发送请求消息。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发 送该请求消息，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息；或者，移动管理网元可以用新建的消息发送该请求消息，具体使用哪个消息来发送该请求消息，本发明不做限定。
在应用场景(3)中，移动管理网元在接收到该UE发送的业务请求后，或者为该UE成功建立空口承载上下文后，可向UE的服务C-GW发送请求消息。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发送该请求消息，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息；或者，移动管理网元可以用新建的消息发送该请求消息，具体使用哪个消息来发送该请求消息，本发明不做限定。
UE的当前位置信息，包括UE的当前位置区域所对应的跟踪域信息(Tracking Area Identity，TAI)和/或UE的当前位置区域所对应的服务基站信息等。UE移动到当前位置区域所对应的TAI，即为UE的目标TAI；UE移动到当前位置区域所对应的服务基站信息，即为UE的目标基站信息。目标基站信息，可以是目标基站标识(Identity，ID)、目标小区标识(Cell Identity，CI)，等等。可理解的，UE的当前位置区域，也称为UE的目标位置区域，也即UE移出源服务基站的服务范围后所在的位置区域，类似地，UE的当前位置信息，也称为UE的目标位置信息。
应理解，该UE的移动过程包括上述三种应用场景中发生的流程，具体为：应用场景(1)中的业务切换流程，应用场景(2)中的位置更新流程，应用场景(3)中的业务请求流程。
应理解，UE的目标基站，是指UE移动到当前位置区域后，为该UE提供接入服务的基站。
应理解，该数据转发隧道是通过在服务该UE的源U-GW与该转发U-GW之间，以及转发U-GW与该UE的目标基站之间建立用户面承载上下文实现的，该用户面承载上下文包含了转发用户面数据所需的路由信息，具体地，该源U-GW上建立的用户面承载上下文包括该转发U-GW的路由信息以及服务该UE的源基站的路由信息，该转发U-GW上建立的用户面承载上下文包括该源U-GW的路由信息以及该目标基站的路由信息，该目标基站 上建立的用户面承载上下文包括该转发U-GW的路由信息。进一步地，该路由信息可以包括地址(典型地为互联网协议(Internet Protocol，IP)地址)与隧道端口信息(典型地，若使用GPRS隧道协议(GPRS Tunnelling Protocol，GTP)协议，则隧道端口信息为GTP隧道端口标识(Tunnel Endpoint Identifier，TEID))。
应理解，该转发U-GW，是指选择单元1202选择的至少一个转发U-GW。隧道建立单元1203在服务该UE的源U-GW与该转发U-GW之间，以及该转发U-GW与该UE的目标基站之间，为该UE建立数据转发隧道，是指隧道建立单元1203在源U-GW、该至少一个转发U-GW、该目标基站三者构成的通信路径，建立起从源C-GW到目标基站两个网元之间的数据转发隧道。
本发明实施例中，控制面网关1200根据UE移动后的当前位置信息，为UE确定合适的转发U-GW，并建立转发U-GW与源U-GW之间，以及转发U-GW与UE的目标基站之间的数据转发隧道，从而能够保证UE移动过程中的业务连续性，提高用户的业务体验。
此外，如图13所示，控制面网关还可包括发送单元1204。
可选地，作为一个实施例，该至少一个转发U-GW为第一U-GW，该控制面网关为该UE移动到当前位置区域之后的服务控制面网关，且该控制面网关与该UE移动到当前位置区域之前的服务控制面网关相同，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元；
接收单元1201还用于接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
该隧道建立单元1203具体用于：通过发送单元1204向该第一U-GW发送第二请求，并通过发送单元1204向该源U-GW发送第三请求，其中，该第二请求用于请求该第一U-GW建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源U-GW的路由信息，该第三请求用于请求该源U-GW建立该源U-GW与该第一U-GW之间的数据转发隧道，该第三请求携带该第一U-GW的路由信息。
应理解，本实施例中，控制面网关1200与该UE移动到当前位置区域之前的服务C-GW相同，即服务C-GW在UE移动过程中没有改变。应理解， 本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
当然，应理解，控制面网关1200还会接收第一U-GW根据第二请求发送的第二响应，以及源U-GW根据第三请求发送的第三响应。其中，第二响应用于确认第一U-GW允许建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第一U-GW的路由信息，比如IP地址与TEID信息；该第三响应用于确认该源U-GW允许建立该源U-GW与该第一U-GW之间的数据转发隧道。在接收到第二响应和第三响应后，控制面网关1200可向移动管理网元发送第一请求的第一响应。
需要说明的是，本实施中第一请求，第二请求或第三请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应，第二响应或第三响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
可选地，作为另一个实施例，该至少一个转发U-GW包括第一U-GW和第二U-GW，该控制面网关为该UE移动到当前位置区域之后的服务控制面网关，且该控制面网关与该UE移动到当前位置区域之前的服务控制面网关相同，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元，且该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元相同或不同；
接收单元1201还用于接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
隧道建立单元1203具体用于：通过发送单元1204向该第二U-GW发送第二请求，并通过发送单元1204向该第三U-GW发送第三请求，并通过发送单元1204向该源U-GW发送第四请求，其中，该第二请求用于请求该第二U-GW建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三U-GW的路由信息，该第三请求用于请求该第三 U-GW建立该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，该第三请求携带该第二U-GW的路由信息，以及该源U-GW的路由信息，该第四请求用于请求该源U-GW建立该源U-GW与该第三U-GW之间的数据转发隧道，该第四请求携带该第三U-GW的路由信息。
应理解，本实施例中，该C-GW与该UE移动到当前位置区域之前的服务C-GW相同，即服务C-GW在UE移动过程中没有改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
类似地，控制面网关1200还会接收第二U-GW根据第二请求发送的第二响应，第三U-GW根据第三请求发送的第三响应，以及源U-GW根据第四请求发送的第四响应。其中，第二响应用于确认第二U-GW允许建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第二U-GW的路由信息，比如IP地址与TEID信息；该第三响应用于确认该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，可选地，该第三响应可以携带该第三U-GW的路由信息，比如IP地址与TEID信息；该第四响应用于确认该源U-GW允许建立该源U-GW与该第三U-GW之间的数据转发隧道。在接收到第二响应、第三响应及第四响应后，控制面网关1200可向移动管理网元发送第一请求的第一响应。
需要说明的是，本实施中第一请求，第二请求，第三请求或第四请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应，第二响应，第三响应或第四响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
可选地，作为再一个实施例，该至少一个转发U-GW为第一U-GW，该控制面网关为该UE移动到当前位置区域之后的服务控制面网关，且该控制 面网关不同于该UE移动到当前位置区域之前的服务控制面网关，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元，且该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元相同或不同；
接收单元1201还用于接收该UE的源U-GW的路由信息；
接收单元1201还用于接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
隧道建立单元1203具体用于：通过发送单元1204向该第一U-GW发送第二请求，其中，该第二请求用于请求该第一U-GW建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源U-GW的路由信息。
应理解，本实施例中，该C-GW不同于该UE移动到当前位置区域之前的服务C-GW，即服务C-GW在UE移动过程中改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
类似地，控制面网关1200还会接收第一U-GW根据第二请求发送的第二响应，以及源U-GW根据第三请求发送的第三响应。其中，第二响应用于确认第一U-GW允许建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第一U-GW的路由信息，比如IP地址与TEID信息；该第三响应用于确认该源U-GW允许建立该源U-GW与该第一U-GW之间的数据转发隧道。在接收到第二响应和第三响应后，控制面网关1200可向移动管理网元发送第一请求的第一响应。
当然，应理解，由于本实施例中UE的服务C-GW在移动过程中发生了改变，故该C-GW为目标C-GW，即该UE移动到当前位置区域之后的服务C-GW。进一步地，该目标C-GW还应通过移动管理网元指示源C-GW向源U-GW发送数据转发隧道建立请求，并将第一U-GW的路由信息发送给源U-GW。其中，源C-GW为该UE移动到当前位置区域之前的服务C-GW，源U-GW为该UE移动到当前位置区域之前的服务U-GW。
需要说明的是，本实施中第一请求或第二请求，可以使用已有的消息， 比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应或第二响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
可选地，作为再一个实施例，该至少一个转发U-GW包括第一U-GW和第二U-GW，该控制面网关为该UE移动到当前位置区域之后的服务控制面网关，且该控制面网关不同于该UE移动到当前位置区域之前的服务控制面网关，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元，且该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元相同或不同；
接收单元1201还用于接收该UE的源U-GW的路由信息；
接收单元1201还用于接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
隧道建立单元1203具体用于：通过发送单元1204向该第二U-GW发送第二请求，并通过发送单元1204向该第三U-GW发送第三请求，其中，该第二请求用于请求该第二U-GW建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三U-GW的路由信息，该第三请求用于请求该第三U-GW建立该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，该第三请求携带该第二U-GW的路由信息，以及该源U-GW的路由信息。
应理解，本实施例中，该C-GW不同于该UE移动到当前位置区域之前的服务C-GW，即服务C-GW在UE移动过程中改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
类似地，控制面网关1200还会接收第二U-GW根据第二请求发送的第二响应，以及第三U-GW根据第三请求发送的第三响应，以及源U-GW根据第四请求发送的第四响应。其中，第二响应用于确认第二U-GW允许建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该 第三U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第二U-GW的路由信息，比如IP地址与TEID信息，源U-GW根据第四请求发送的第四响应；该第三响应用于确认该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，可选地，该第三响应可以携带该第三U-GW的路由信息，比如IP地址与TEID信息；该第四响应用于确认该源U-GW允许建立该源U-GW与该第三U-GW之间的数据转发隧道。在接收到第二响应、及第三响应及第四响应后，控制面网关1200可向移动管理网元发送第一请求的第一响应。
当然，应理解，由于本实施例中UE的服务C-GW在移动过程中发生了改变，故本实施例中该C-GW为目标C-GW，即该UE移动到当前位置区域之后的服务C-GW。进一步地，该目标C-GW还应通过移动管理网元指示源C-GW向源U-GW发送数据转发隧道建立请求，并将第三U-GW的路由信息发送给源U-GW。其中，源C-GW为该UE移动到当前位置区域之前的服务C-GW，源U-GW为该UE移动到当前位置区域之前的服务U-GW。
需要说明的是，本实施中第一请求，第二请求或第三请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应，第二响应或第三响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。可选地，在图13所示的上述四个具体实施例中，当该至少一个转发U-GW为第一U-GW时，隧道建立单元1203还用于通过该移动管理网元向该目标基站发送该目标U-GW的路由信息。
可选地，在图13所示的上述四个具体实施例中，当该至少一个转发U-GW为第一U-GW时，隧道建立单元1203还用于通过该移动管理网元向该目标基站发送该第一U-GW的路由信息。
可选地，在图13所示的上述四个具体实施例中，当该至少一个转发U-GW为第二U-GW和第三U-GW时，隧道建立单元1203还用于通过该移动管理网元向该目标基站发送该第二U-GW的路由信息。
可选地，在图13所示的上述四个具体实施例中，隧道建立单元1203还用于向该目标U-GW发送建立会话请求，其中，该建立会话请求用于在该目 标U-GW上为该UE创建用户面数据传输所需的承载上下文，所建立的每个该承载上下文都包含该目标U-GW的路由信息，该目标U-GW是该UE的当前位置区域对应的服务U-GW。可理解的，该目标U-GW通常是为该UE在该当前位置区域提供最优数据传输路径的服务U-GW。进一步地，隧道建立单元1203还用于通过该移动管理网元向该目标基站发送该目标U-GW的路由信息。
可选地，在图13所示的上述四个具体实施例中，当该至少一个转发U-GW为第一U-GW时，该第一U-GW还是该控制面网关根据该UE的当前位置信息为该UE选择的服务U-GW。也就是说，该第一U-GW为目标U-GW。此时，该目标D-GW能够与该源D-GW直接通信，也即该目标U-GW同时扮演了该转发U-GW的角色。可理解的，当该目标U-GW不能与该源D-GW直接通信时，该C-GW选择的转发U-GW与该目标U-GW不同。
控制面网关1200还可执行图2的方法，并实现C-GW在图2-图4、图7、图8所示实施例C-GW及目标C-GW在图5、图6所示实施例的功能，本发明实施例在此不再赘述。
图14是本发明实施例移动管理网元1400的结构示意图。移动管理网元1400可包括：
接收单元1401，用于接收服务UE的源移动管理网元发送的转发重定位请求。
其中，该转发重定位请求携带该UE的当前位置信息。
选择单元1402，用于根据该UE的当前位置信息选择该UE的目标C-GW。
发送单元1403，用于向该目标C-GW发送该UE的当前位置信息，以便该目标控制面网关根据该UE的当前位置信息确定该UE的转发U-GW；
发送单元1403还用于向该目标控制面网关发送数据转发隧道建立请求。
其中，该数据转发隧道建立请求用于请求该目标C-GW在该转发U-GW与服务该UE的源U-GW之间，以及该转发U-GW与服务该UE的目标基站之间为该UE建立数据转发隧道。
本发明实施例中，移动管理网元1400在UE移动出源移动管理网元的服务范围后，根据UE的当前位置信息确定UE的目标C-GW，进而通过目标C-GW在该源U-GW与UE的目标基站之间为该UE建立数据转发隧道， 从而能够保证UE移动过程中的业务连续性，提高用户的业务体验。
可选地，该目标控制面网关与该UE移动到当前位置区域之前的服务控制面网关不同(即服务C-GW在UE移动过程中发生改变)，发送单元1403还用于向该源移动管理网元发送改变通知消息，该改变通知消息用于指示该UE的服务控制面网关变更为该目标控制面网关。
进一步地，接收单元1401还用于接收该源移动管理网元根据该改变通知消息发送的确认消息，该确认消息携带该UE的源U-GW的路由信息。
移动管理网元1400还可执行图9的方法，并实现目标MME在图5、图6所示实施例的功能，本发明实施例在此不再赘述。
图15是本发明实施例控制面网关1500的结构示意图。控制面网关1500包括：
接收单元1501，用于接收移动管理网元发送的该UE的当前位置信息。
选择单元1502，用于根据该UE的当前位置信息为该UE选择目标U-GW。
发送单元1503，用于向该移动管理网元发送请求消息。
该请求消息用于请求该移动管理网元释放第一承载上下文并指示该UE发送第二承载上下文的建立请求，其中，该第一承载上下文是建立在该UE的源U-GW上的该UE的承载上下文，该第二承载上下文是该UE根据该第一承载上下文在该目标U-GW上重建的承载上下文。
应理解，本发明实施例中，该位置更新通知消息旨在通知C-GW，UE当前的位置区域发生了改变，该位置更新通知可以重用已有的消息，比如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息，也可以重新定义新的消息，对此本发明不做限定。
本发明实施例中，在UE从空闲态变为连接态并发送用户面数据之前，控制面网关1500根据UE的当前位置信息决定服务U-GW是否需要改变并触发承载上下文去激活流程并携带重新激活请求指示以请求UE马上发起承载上下文重新建立流程，实现承载资源在目标U-GW上的重建，保证后续用户数传的业务连续性，从而保证用户业务体验。
可选地，作为一个实施例，该请求消息为删除承载请求消息，该删除承载请求消息携带重新激活请求指示，该重新激活请求指示用于通过该移动管理网元指示该UE在该第一承载上下文删除后，发起该第二承载上下文的建 立请求。
应理解，MME和UE都记录着UE在源U-GW上建立的第一承载上下文，当MME接收到删除承载请求消息后，会删除MME上的第一承载上下文，并指示UE删除UE上的第一承载上下文；该删除承载请求消息携带重新激活请求指示时，MME还向UE发送重新激活请求指示，指示UE在删除第一承载上下文后，基于第一承载上下文的内容重新发送承载上下文的建立请求，请求建立第二承载上下文。其中，该第二承载上下文是基于第一承载上下文在目标U-GW上建立的承载上下文。
控制面网关1500还可执行图10的方法，并实现C-GW在图11所示实施例的功能，本发明实施例在此不再赘述。
图16是本发明实施例控制面网关1600的结构示意图。控制面网关1600可包括处理器1602、存储器1603、发射机1601和接收机1604。在具体的应用中，该控制面网关1600可以是等。
接收机1604、发射机1601、处理器1602和存储器1603通过总线1606系统相互连接。总线1606可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图16中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。具体的应用中，发射机1601和接收机1604可以耦合到天线1605。
存储器1603，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器1603可以包括只读存储器和随机存取存储器，并向处理器1602提供指令和数据。存储器1603可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
处理器1602，执行存储器1603所存放的程序，并具体用于执行以下操作：
通过接收机1604接收移动管理网元发送的UE的当前位置信息；
根据该UE的当前位置信息为该UE选择至少一个转发U-GW；
通过发射机1601在服务该UE的源U-GW与该转发U-GW之间，以及该转发U-GW与该UE的目标基站之间，为该UE建立数据转发隧道，其中，该数据转发隧道用于在该UE的移动过程中传输该UE的上行用户面数据和/或下行用户面数据。
本发明实施例的适用场景可参考图2所示实施例的应用场景。
在应用场景(1)中，移动管理网元在收到源基站发送的用户面数据切换请求后，可向UE的服务C-GW发送业务切换通知。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发送该业务切换通知，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息等；或者，移动管理网元可以用新建的消息发送该业务切换通知，具体使用哪个消息来发送该业务切换通知，本发明不做限定。
在应用场景(2)中，移动管理网元在接收到该UE发送的位置更新请求后，或者为该UE成功建立空口承载上下文后，可向UE的服务C-GW发送请求消息。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发送该请求消息，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息；或者，移动管理网元可以用新建的消息发送该请求消息，具体使用哪个消息来发送该请求消息，本发明不做限定。
在应用场景(3)中，移动管理网元在接收到该UE发送的业务请求后，或者为该UE成功建立空口承载上下文后，可向UE的服务C-GW发送请求消息。应理解，该移动管理网元可以是MME，或其它具备MME的移动管理功能的网元。在具体的应用中，移动管理网元可以用现有的消息发送该请求消息，例如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息或修改接入承载请求(Modify Access Bearers Request)消息；或者，移动管理网元可以用新建的消息发送该请求消息，具体使用哪个消息来发送该请求消息，本发明不做限定。
UE的当前位置信息，包括UE的当前位置区域所对应的跟踪域信息(Tracking Area Identity，TAI)和/或UE的当前位置区域所对应的服务基站信息等。UE移动到当前位置区域所对应的TAI，即为UE的目标TAI；UE移动到当前位置区域所对应的服务基站信息，即为UE的目标基站信息。目标基站信息，可以是目标基站标识(Identity，ID)、目标小区标识(Cell Identity，CI)，等等。可理解的，UE的当前位置区域，也称为UE的目标位置区域， 也即UE移出源服务基站的服务范围后所在的位置区域，类似地，UE的当前位置信息，也称为UE的目标位置信息。
应理解，该UE的移动过程包括上述三种应用场景中发生的流程，具体为：应用场景(1)中的业务切换流程，应用场景(2)中的位置更新流程，应用场景(3)中的业务请求流程。
应理解，UE的目标基站，是指UE移动到当前位置区域后，为该UE提供接入服务的基站。
应理解，该数据转发隧道是通过在服务该UE的源U-GW与该转发U-GW之间，以及转发U-GW与该UE的目标基站之间建立用户面承载上下文实现的，该用户面承载上下文包含了转发用户面数据所需的路由信息，包括该源U-GW的路由信息，该转发U-GW的路由信息和该目标基站的路由信息，具体地，该路由信息可以包括地址(典型地为互联网协议(Internet Protocol，IP)地址)与隧道端口信息(典型地，若使用GPRS隧道协议(GPRS Tunnelling Protocol，GTP)协议，则隧道端口信息为GTP隧道端口标识(Tunnel Endpoint Identifier，TEID))。
应理解，该转发U-GW，是指处理器1602选择的至少一个转发U-GW。处理器1602在服务该UE的源U-GW与该转发U-GW之间，以及该转发U-GW与该UE的目标基站之间，为该UE建立数据转发隧道，是指处理器1602在源U-GW、该至少一个转发U-GW、该目标基站三者构成的通信路径，建立起从源C-GW到目标基站两个网元之间的数据转发隧道。
上述如本发明图2-4中任一实施例揭示的C-GW或图5、6中任一实施例揭示的目标C-GW执行的方法，可以应用于处理器1602中，或者由处理器1602实现。处理器1602可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1602中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1602可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以 直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1603，处理器1602读取存储器1603中的信息，结合其硬件完成上述方法的步骤。
本发明实施例中，控制面网关1600根据UE移动后的当前位置信息，为UE确定合适的转发U-GW，并建立转发U-GW与源U-GW之间，以及转发U-GW与UE的目标基站之间的数据转发隧道，从而能够保证UE移动过程中的业务连续性，提高用户的业务体验。
可选地，作为一个实施例，该至少一个转发U-GW为第一U-GW，该控制面网关为该UE移动到当前位置区域之后的服务控制面网关，且该控制面网关与该UE移动到当前位置区域之前的服务控制面网关相同，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元，且该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元相同或不同；
处理器1602还用于通过接收机1604接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
在用于通过发射机1601在服务该UE的源U-GW与该转发U-GW之间，和/或该转发U-GW与该UE的目标基站之间，为该UE建立数据转发隧道的过程中，处理器1602具体用于：
通过发射机1601向该第一U-GW发送第二请求，并通过发射机1601向该源U-GW发送第三请求，其中，该第二请求用于请求该第一U-GW允许建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源U-GW的路由信息，该第三请求用于请求该源U-GW建立该源U-GW与该第一U-GW之间的数据转发隧道，该第三请求携带该第一U-GW的路由信息。
应理解，本实施例中，控制面网关1600与该UE移动到当前位置区域之前的服务C-GW相同，即服务C-GW在UE移动过程中没有改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
当然，应理解，控制面网关1600还会接收第一U-GW根据第二请求发送的第二响应，以及源U-GW根据第三请求发送的第三响应。其中，第二响应用于确认第一U-GW允许建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第一U-GW的路由信息，比如IP地址与TEID信息；该第三响应用于确认该源U-GW允许建立该源U-GW与该第一U-GW之间的数据转发隧道。在接收到第二响应和第三响应后，控制面网关1600可向移动管理网元发送第一请求的第一响应。
需要说明的是，本实施中第一请求，第二请求或第三请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应，第二响应或第三响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
可选地，作为另一个实施例，该至少一个转发U-GW包括第一U-GW和第二U-GW，该控制面网关为该UE移动到当前位置区域之后的服务控制面网关，且该控制面网关与该UE移动到当前位置区域之前的服务控制面网关相同，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元，且该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元相同或不同；
处理器1602还用于通过接收机1604接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
在用于通过发射机1601在服务该UE的源U-GW与该转发U-GW之间，以及该转发U-GW与该UE的目标基站之间，为该UE建立数据转发隧道的过程中，处理器1602具体用于：
通过发射机1601向该第二U-GW发送第二请求，并通过发射机1601向该第三U-GW发送第三请求，并通过发射机1601向该源U-GW发送第四请求，其中，该第二请求用于请求该第二U-GW建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三U-GW的路由信息，该第三请求用于请求该第三U-GW建立该第三U-GW与该第二 U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，该第三请求携带该第二U-GW的路由信息，以及该源U-GW的路由信息，该第四请求用于请求该源U-GW建立该源U-GW与该第三U-GW之间的数据转发隧道，该第四请求携带该第三U-GW的路由信息。
应理解，本实施例中，控制面网关1600与该UE移动到当前位置区域之前的服务C-GW相同，即服务C-GW在UE移动过程中没有改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
类似地，控制面网关1600还会接收第二U-GW根据第二请求发送的第二响应，第三U-GW根据第三请求发送的第三响应，以及源U-GW根据第四请求发送的第四响应。其中，第二响应用于确认第二U-GW允许建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第二U-GW的路由信息，比如IP地址与TEID信息；该第三响应用于确认该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，可选地，该第三响应可以携带该第三U-GW的路由信息，比如IP地址与TEID信息；该第四响应用于确认该源U-GW允许建立该源U-GW与该第三U-GW之间的数据转发隧道。在接收到第二响应、第三响应及第四响应后，控制面网关1600可向移动管理网元发送第一请求的第一响应。
需要说明的是，本实施中第一请求，第二请求，第三请求或第四请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应，第二响应，第三响应或第四响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
可选地，作为再一个实施例，该至少一个转发U-GW为第一U-GW，该控制面网关为该UE移动到当前位置区域之后的服务控制面网关，且该控制面网关不同于该UE移动到当前位置区域之前的服务控制面网关，该移动管 理网元为该UE移动到当前位置区域之后的服务移动管理网元，且该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元相同或不同；
处理器1602还用于通过接收机1604接收该UE的源U-GW的路由信息；
处理器1602还用于通过接收机1604接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
在用于通过发射机1601在服务该UE的源U-GW与该转发U-GW之间，以及该转发U-GW与该UE的目标基站之间，为该UE建立数据转发隧道的过程中，处理器1602具体用于：
通过发射机1601向该第一U-GW发送第二请求，其中，该第二请求用于请求该第一U-GW建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及该源U-GW的路由信息。
应理解，本实施例中，控制面网关1600不同于该UE移动到当前位置区域之前的服务C-GW，即服务C-GW在UE移动过程中改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
类似地，控制面网关1600还会接收第一U-GW根据第二请求发送的第二响应，以及源U-GW根据第三请求发送的第三响应。其中，第二响应用于确认第一U-GW允许建立该第一U-GW与该目标基站之间的数据转发隧道，以及该第一U-GW与该源U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第一U-GW的路由信息，比如IP地址与TEID信息；该第三响应用于确认该源U-GW允许建立该源U-GW与该第一U-GW之间的数据转发隧道。在接收到第二响应和第三响应后，控制面网关1600可向移动管理网元发送第一请求的第一响应。
当然，应理解，由于本实施例中UE的服务C-GW在移动过程中发生了改变，故控制面网关1600为目标C-GW，即该UE移动到当前位置区域之后的服务C-GW。进一步地，处理器1602还应通过移动管理网元指示源C-GW向源U-GW发送数据转发隧道建立请求，并将第一U-GW的路由信息发送给源U-GW。其中，源C-GW为该UE移动到当前位置区域之前的服务C-GW，源U-GW为该UE移动到当前位置区域之前的服务U-GW。
需要说明的是，本实施中第一请求或第二请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应或第二响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
可选地，作为再一个实施例，该至少一个转发U-GW包括第一U-GW和第二U-GW，该控制面网关为该UE移动到当前位置区域之后的服务控制面网关，且该控制面网关不同于该UE移动到当前位置区域之前的服务控制面网关，该移动管理网元为该UE移动到当前位置区域之后的服务移动管理网元，且该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元相同或不同；
处理器1602还用于通过接收机1604接收该UE的源U-GW的路由信息；
处理器1602还用于通过接收机1604接收该移动管理网元发送的第一请求，该第一请求携带该UE的目标基站的路由信息；
在用于通过发射机1601在服务该UE的源U-GW与该转发U-GW之间，以及该转发U-GW与该UE的目标基站之间，为该UE建立数据转发隧道的过程中，处理器1602具体用于：
通过发射机1601向该第二U-GW发送第二请求，并通过发射机1601向该第三U-GW发送第三请求，其中，该第二请求用于请求该第二U-GW建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，该第二请求携带该目标基站的路由信息，以及第三U-GW的路由信息，该第三请求用于请求该第三U-GW建立该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，该第三请求携带该第二U-GW的路由信息，以及该源U-GW的路由信息。
应理解，本实施例中，控制面网关1600不同于该UE移动到当前位置区域之前的服务C-GW，即服务C-GW在UE移动过程中改变。应理解，本实施例可以适用于服务移动管理网元在UE移动过程中改变或没有改变两种场景，即该移动管理网元与该UE移动到当前位置区域之前的服务移动管理网元可以相同，也可以不同。
类似地，控制面网关1600还会接收第二U-GW根据第二请求发送的第二响应，以及第三U-GW根据第三请求发送的第三响应，以及源U-GW根据第四请求发送的第四响应。其中，第二响应用于确认第二U-GW允许建立该第二U-GW与该目标基站之间的数据转发隧道，以及该第二U-GW与该第三U-GW之间的数据转发隧道，可选地，该第二响应可以携带该第二U-GW的路由信息，比如IP地址与TEID信息，源U-GW根据第四请求发送的第四响应；该第三响应用于确认该第三U-GW与该第二U-GW之间的数据转发隧道，以及该第三U-GW与该源U-GW之间的数据转发隧道，可选地，该第三响应可以携带该第三U-GW的路由信息，比如IP地址与TEID信息；该第四响应用于确认该源U-GW允许建立该源U-GW与该第三U-GW之间的数据转发隧道。在接收到第二响应、及第三响应及第四响应后，控制面网关1600可向移动管理网元发送第一请求的第一响应。
当然，应理解，由于本实施例中UE的服务C-GW在移动过程中发生了改变，故本实施例中控制面网关1600为目标C-GW，即该UE移动到当前位置区域之后的服务C-GW。进一步地，处理器1602还应通过移动管理网元指示源C-GW向源U-GW发送数据转发隧道建立请求，并将第三U-GW的路由信息发送给源U-GW。其中，源C-GW为该UE移动到当前位置区域之前的服务C-GW，源U-GW为该UE移动到当前位置区域之前的服务U-GW。
需要说明的是，本实施中第一请求，第二请求或第三请求，可以使用已有的消息，比如创建间接数据转发隧道请求(Create Indirect Data Forwarding Tunnel Request)，也可以使用新定义的消息，本发明对此不做限定；进一步地，本实施中第一响应，第二响应或第三响应，可以使用已有的消息，比如创建间接数据转发隧道响应(Create Indirect Data Forwarding Tunnel Response)，也可以使用新定义的消息，本发明对此不做限定。
可选地，在图16的上述四个具体实施例中，当该至少一个转发U-GW为第一U-GW时，处理器1602还用于通过发射机1601，经由该移动管理网元向该目标基站发送该目标U-GW的路由信息。
可选地，在图16的上述四个具体实施例中，当该至少一个转发U-GW为第一U-GW时，处理器1602还用于通过该移动管理网元向该目标基站发送该第一U-GW的路由信息。
可选地，在图16的上述四个具体实施例中，当该至少一个转发U-GW 为第二U-GW和第三U-GW时，处理器1602还用于通过该移动管理网元向该目标基站发送该第二U-GW的路由信息。
可选地，在图16的上述四个具体实施例中，处理器1602还用于通过发射机1601向该目标U-GW发送建立会话请求，其中，该建立会话请求用于在该目标U-GW上为该UE创建用户面数据传输所需的承载上下文，所建立的每个该承载上下文都包含该目标U-GW的路由信息，该目标U-GW是该UE的当前位置区域对应的服务U-GW。可理解的，该目标U-GW通常是为该UE在该当前位置区域提供最优数据传输路径的服务U-GW。进一步地，处理器1602还用于通过该移动管理网元向该目标基站发送该目标U-GW的路由信息。
可选地，在图16的上述四个具体实施例中，当该至少一个转发U-GW为第一U-GW时，该第一U-GW还是该控制面网关根据该UE的当前位置信息为该UE选择的服务U-GW。也就是说，该第一U-GW为目标U-GW。此时，该目标D-GW能够与该源D-GW直接通信，也即该目标U-GW同时扮演了该转发U-GW的角色。可理解的，当该目标U-GW不能与该源D-GW直接通信时，该C-GW选择的转发U-GW与该目标U-GW不同。
控制面网关1600还可执行图2的方法，并实现C-GW在图2-图4、图7、图8所示实施例C-GW及目标C-GW在图5、图6所示实施例的功能，本发明实施例在此不再赘述。
图17是本发明实施例移动管理网元1700的结构示意图。移动管理网元1700可包括处理器1702、存储器1703、发射机1701和接收机1704。在具体的应用中，该移动管理网元1700可以是等。
接收机1704、发射机1701、处理器1702和存储器1703通过总线1706系统相互连接。总线1706可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图17中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。具体的应用中，发射机1701和接收机1704可以耦合到天线1705。
存储器1703，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器1703可以包括只读存储器和随机存取存储器，并向处理器1702提供指令和数据。存储器1703可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一 个磁盘存储器。
处理器1702，执行存储器1703所存放的程序，并具体用于执行以下操作：
通过接收机1704接收服务UE的源移动管理网元发送的转发重定位请求，该转发重定位请求携带该UE的当前位置信息；
根据该UE的当前位置信息选择该UE的目标C-GW；
通过发射机1701向该C-GW发送该UE的当前位置信息，以便该C-GW根据该UE的当前位置信息确定该UE的转发U-GW；
通过发射机1701向该目标控制面网关发送数据转发隧道建立请求，该数据转发隧道建立请求用于请求该目标C-GW在该转发U-GW与服务该UE的源U-GW之间，以及该转发U-GW与服务该UE的目标基站之间为该UE建立数据转发隧道。
上述如本发明图9所示实施例揭示的移动管理网元或图5、6所示实施例揭示的目标MME执行的方法可以应用于处理器1702中，或者由处理器1702实现。处理器1702可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1702中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1702可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1703，处理器1702读取存储器1703中的信息，结合其硬件完成上述方法的步骤。
本发明实施例中，移动管理网元1700在UE移动出源移动管理网元的服务范围后，根据UE的当前位置信息确定UE的目标C-GW，进而通过目标C-GW在该源U-GW与UE的目标基站之间为该UE建立数据转发隧道， 从而能够保证UE移动过程中的业务连续性，提高用户的业务体验。
可选地，该目标控制面网关与该UE移动到当前位置区域之前的服务控制面网关不同(即服务C-GW在UE移动过程中发生改变)，处理器1702还用于通过发射机1701向该源移动管理网元发送改变通知消息，该改变通知消息用于指示该UE的服务控制面网关变更为该目标控制面网关。
进一步地，处理器1702还用于通过接收机1704接收该源移动管理网元根据该改变通知消息发送的确认消息，该确认消息携带该UE的源U-GW的路由信息。
移动管理网元1700还可执行图9的方法，并实现目标MME在图5、图6所示实施例的功能，本发明实施例在此不再赘述。
图18是本发明实施例控制面网关1800的结构示意图。控制面网关1800可包括处理器1802、存储器1803、发射机1801和接收机1804。在具体的应用中，该控制面网关1800可以是等。
接收机1804、发射机1801、处理器1802和存储器1803通过总线1806系统相互连接。总线1806可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图18中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。具体的应用中，发射机1801和接收机1804可以耦合到天线1805。
存储器1803，用于存放程序。具体地，程序可以包括程序代码，所述程序代码包括计算机操作指令。存储器1803可以包括只读存储器和随机存取存储器，并向处理器1802提供指令和数据。存储器1803可能包含高速RAM存储器，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。
处理器1802，执行存储器1803所存放的程序，并具体用于执行以下操作：
通过接收机1804接收移动管理网元发送的该UE的当前位置信息；
根据该UE的当前位置信息为该UE选择目标U-GW；
通过发射机1801向该移动管理网元发送请求消息，该请求消息用于请求该移动管理网元释放第一承载上下文并指示该UE发送第二承载上下文的建立请求，其中，该第一承载上下文是建立在该UE的源U-GW上的该UE的承载上下文，该第二承载上下文是该UE根据该第一承载上下文在该目标 U-GW上重建的承载上下文。
应理解，本发明实施例中，该位置更新通知消息旨在通知C-GW，UE当前的位置区域发生了改变，该位置更新通知可以重用已有的消息，比如建立会话请求(Create Session Request)消息或修改承载请求(Modify Bearer Request)消息，也可以重新定义新的消息，对此本发明不做限定。
上述如本发明图10、11中任一实施例揭示的C-GW执行的方法可以应用于处理器1802中，或者由处理器1802实现。处理器1802可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1802中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1802可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1803，处理器1802读取存储器1803中的信息，结合其硬件完成上述方法的步骤。
本发明实施例中，在UE从空闲态变为连接态并发送用户面数据之前，控制面网关1800根据UE的当前位置信息决定服务U-GW是否需要改变并触发承载上下文去激活流程并携带重新激活请求指示以请求UE马上发起承载上下文重新建立流程，实现承载资源在目标U-GW上的重建，保证后续用户数传的业务连续性，从而保证用户业务体验。
可选地，作为一个实施例，该请求消息为删除承载请求消息，该删除承载请求消息携带重新激活请求指示，该重新激活请求指示用于通过该移动管理网元指示该UE在该第一承载上下文删除后，发起该第二承载上下文的建立请求。
应理解，MME和UE都记录着UE在源U-GW上建立的第一承载上下文，当MME接收到删除承载请求消息后，会删除MME上的第一承载上下 文，并指示UE删除UE上的第一承载上下文；该删除承载请求消息携带重新激活请求指示时，MME还向UE发送重新激活请求指示，指示UE在删除第一承载上下文后，基于第一承载上下文的内容重新发送承载上下文的建立请求，请求建立第二承载上下文。其中，该第二承载上下文是基于第一承载上下文在目标U-GW上建立的承载上下文。
控制面网关1800还可执行图10的方法，并实现C-GW在图11所示实施例的功能，本发明实施例在此不再赘述。
应理解，在本发明的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本发明实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一 个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (45)

  1. 一种保持业务连续性的方法，其特征在于，包括：
    控制面网关接收移动管理网元发送的用户设备的当前位置信息；
    所述控制面网关根据所述用户设备的当前位置信息为所述用户设备选择至少一个转发用户面网关；
    所述控制面网关在服务所述用户设备的源用户面网关与所述转发用户面网关之间，以及所述转发用户面网关与服务所述用户设备的目标基站之间，为所述用户设备建立数据转发隧道，其中，所述数据转发隧道用于在所述用户设备的移动过程中传输所述用户设备的上行用户面数据和/或下行用户面数据。
  2. 如权利要求1所述的方法，其特征在于，
    所述至少一个转发用户面网关为第一用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关与所述用户设备移动到当前位置区域之前的服务控制面网关相同，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元，
    所述控制面网关在服务所述用户设备的源用户面网关与所述转发用户面网关之间，以及所述转发用户面网关与服务所述用户设备的目标基站之间，为所述用户设备建立数据转发隧道包括：
    所述控制面网关接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    所述控制面网关向所述第一用户面网关发送第二请求，所述第二请求用于请求所述第一用户面网关建立所述第一用户面网关与所述目标基站之间的数据转发隧道，以及所述第一用户面网关与所述源用户面网关之间的数据转发隧道，其中，所述第二请求携带所述目标基站的路由信息以及所述源用户面网关的路由信息；
    所述控制面网关向所述源用户面网关发送第三请求，所述第三请求用于请求所述源用户面网关建立所述源用户面网关与所述第一用户面网关之间的数据转发隧道，其中，所述第三请求携带所述第一用户面网关的路由信息。
  3. 如权利要求1所述的方法，其特征在于，
    所述至少一个转发用户面网关包括第二用户面网关和第三用户面网关， 所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关与所述用户设备移动到当前位置区域之前的服务控制面网关相同，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元，
    所述控制面网关在服务所述用户设备的源用户面网关与所述转发用户面网关之间，以及所述转发用户面网关与服务所述用户设备的目标基站之间，为所述用户设备建立数据转发隧道包括：
    所述控制面网关接收所述移动管理网元发送的第一请求，所述第一请求携带所述用户设备的目标基站的路由信息；
    所述控制面网关向所述第二用户面网关发送第二请求，所述第二请求用于请求所述第二用户面网关建立所述第二用户面网关与所述目标基站之间的数据转发隧道，以及所述第二用户面网关与所述第三用户面网关之间的数据转发隧道，其中，所述第二请求携带所述目标基站的路由信息以及所述第三用户面网关的路由信息；
    所述控制面网关向所述第三用户面网关发送第三请求，所述第三请求用于请求所述第三用户面网关建立所述第三用户面网关与所述第二用户面网关之间的数据转发隧道，以及所述第三用户面网关与所述源用户面网关之间的数据转发隧道，其中，所述第三请求携带所述第二用户面网关的路由信息以及所述源用户面网关的路由信息；
    所述控制面网关向所述源用户面网关发送第四请求，所述第四请求用于请求所述源用户面网关建立所述源用户面网关与所述第三用户面网关之间的数据转发隧道，其中，所述第四请求携带所述第三用户面网关的路由信息。
  4. 如权利要求1所述的方法，其特征在于，
    所述至少一个转发用户面网关为第一用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关不同于所述用户设备移动到当前位置区域之前的服务控制面网关，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元，
    所述方法还包括：所述控制面网关还接收移动管理网元发送的所述源用户面网关的路由信息；
    所述控制面网关在服务所述用户设备的源用户面网关与所述转发用户面网关之间，以及所述转发用户面网关与服务所述用户设备的目标基站之 间，为所述用户设备建立数据转发隧道包括：
    所述控制面网关接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    所述控制面网关向所述第一用户面网关发送第二请求，所述第二请求用于请求所述第一用户面网关建立所述第一用户面网关与所述目标基站之间的数据转发隧道，以及所述第一用户面网关与所述源用户面网关之间的数据转发隧道，其中，所述第二请求携带所述目标基站的路由信息以及所述源用户面网关的路由信息。
  5. 如权利要求1所述的方法，其特征在于，
    所述至少一个转发用户面网关包括第二用户面网关和第三用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关不同于所述用户设备移动到当前位置区域之前的服务控制面网关，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元；
    所述方法还包括：所述控制面网关还接收移动管理网元发送的所述源用户面网关的路由信息；
    所述控制面网关在服务所述用户设备的源用户面网关与所述转发用户面网关之间，以及所述转发用户面网关与服务所述用户设备的目标基站之间，为所述用户设备建立数据转发隧道包括：
    所述控制面网关接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    所述控制面网关向所述第二用户面网关发送第二请求，所述第二请求用于请求所述第二用户面网关建立所述第二用户面网关与所述目标基站之间的数据转发隧道，以及所述第二用户面网关与所述第三用户面网关之间的数据转发隧道，其中，所述第二请求携带所述目标基站的路由信息以及第三用户面网关的路由信息；
    所述控制面网关向所述第三用户面网关发送第三请求，所述第三请求用于请求所述第三用户面网关建立所述第三用户面网关与所述第二用户面网关之间的数据转发隧道，以及所述第三用户面网关与所述源用户面网关之间的数据转发隧道，其中，所述第三请求携带所述第二用户面网关的路由信息以及所述源用户面网关的路由信息。
  6. 如权利要求1至5任一项所述的方法，其特征在于，所述方法还包括：
    所述控制面网关向目标用户面网关发送建立会话请求，所述建立会话请求用于在所述目标用户面网关上为所述用户设备创建用户面数据传输所需的承载上下文，其中，所建立的每个所述承载上下文包含所述目标用户面网关的路由信息，
    所述目标用户面网关是所述用户设备的当前位置区域对应的服务用户面网关。
  7. 如权利要求6所述的方法，其特征在于，所述方法还包括：
    所述控制面网关通过所述移动管理网元向所述目标基站发送所述目标用户面网关的路由信息。
  8. 如权利要求2或4所述的方法，其特征在于，所述方法还包括：
    所述控制面网关通过所述移动管理网元向所述目标基站发送所述第一用户面网关的路由信息。
  9. 如权利要求2或4或8所述的方法，其特征在于，
    所述第一用户面网关是所述控制面网关根据所述用户设备的当前位置信息为所述用户设备选择的服务用户面网关。
  10. 如权利要求3或5所述的方法，其特征在于，所述方法还包括：
    所述控制面网关通过所述移动管理网元向所述目标基站发送所述第二用户面网关的路由信息。
  11. 一种保持业务连续性的方法，其特征在于，包括：
    目标移动管理网元接收服务用户设备的源移动管理网元发送的转发重定位请求，所述转发重定位请求携带所述用户设备的当前位置信息；
    所述目标移动管理网元根据所述用户设备的当前位置信息选择所述用户设备的目标控制面网关；
    所述目标移动管理网元向所述目标控制面网关发送所述用户设备的当前位置信息，以便所述目标控制面网关根据所述用户设备的当前位置信息确定所述用户设备的转发用户面网关；
    所述目标移动管理网元向所述目标控制面网关发送数据转发隧道建立请求，所述数据转发隧道建立请求用于请求所述目标控制面网关在所述转发用户面网关与服务所述用户设备的源用户面网关之间，以及所述转发用户面 网关与服务所述用户设备的目标基站之间为所述用户设备建立数据转发隧道。
  12. 如权利要求11所述的方法，其特征在于，所述目标控制面网关与所述用户设备移动到当前位置区域之前的服务控制面网关不同，所述方法还包括：
    所述目标移动管理网元向所述源移动管理网元发送改变通知消息，所述改变通知消息用于指示所述用户设备的服务控制面网关变更为所述目标控制面网关。
  13. 如权利要求12所述的方法，其特征在于，所述方法还包括：
    所述目标移动管理网元接收所述源移动管理网元根据所述改变通知消息发送的确认消息，所述确认消息携带所述源用户面网关的路由信息。
  14. 一种保持业务连续性的方法，其特征在于，包括：
    控制面网关接收移动管理网元发送的用户设备的当前位置信息；
    所述控制面网关根据所述用户设备的当前位置信息为所述用户设备选择目标用户面网关；
    所述控制面网关向所述移动管理网元发送请求消息，所述请求消息用于请求所述移动管理网元释放第一承载上下文并指示所述用户设备发送第二承载上下文的建立请求，其中，所述第一承载上下文是建立在所述用户设备的源用户面网关上的所述用户设备的承载上下文，所述第二承载上下文是所述用户设备根据所述第一承载上下文在所述目标用户面网关上重建的承载上下文。
  15. 如权利要求14所述的方法，其特征在于，
    所述请求消息为删除承载请求消息，所述删除承载请求消息携带重新激活请求指示，所述重新激活请求指示用于通过所述移动管理网元指示所述用户设备在所述第一承载上下文删除后，发起所述第二承载上下文的建立请求。
  16. 一种控制面网关，其特征在于，包括：
    接收单元，用于接收移动管理网元发送的用户设备的当前位置信息；
    选择单元，用于根据所述用户设备的当前位置信息为所述用户设备选择至少一个转发用户面网关；
    隧道建立单元，用于在服务所述用户设备的源用户面网关与所述转发用 户面网关之间，以及所述转发用户面网关与服务所述用户设备的目标基站之间，为所述用户设备建立数据转发隧道，其中，所述数据转发隧道用于在所述用户设备的移动过程中传输所述用户设备的上行用户面数据和/或下行用户面数据。
  17. 如权利要求16所述的控制面网关，其特征在于，所述至少一个转发用户面网关为第一用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关与所述用户设备移动到当前位置区域之前的服务控制面网关相同，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元，
    所述接收单元还用于接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    所述控制面网关还包括发送单元，所述隧道建立单元具体用于：
    通过所述发送单元向所述第一用户面网关发送第二请求，并通过所述发送单元向所述源用户面网关发送第三请求，其中，所述第二请求用于请求所述第一用户面网关建立所述第一用户面网关与所述目标基站之间的数据转发隧道，以及所述第一用户面网关与所述源用户面网关之间的数据转发隧道，所述第二请求携带所述目标基站的路由信息，以及所述源用户面网关的路由信息，所述第三请求用于请求所述源用户面网关建立所述源用户面网关与所述第一用户面网关之间的数据转发隧道，所述第三请求携带所述第一用户面网关的路由信息。
  18. 如权利要求16所述的控制面网关，其特征在于，所述至少一个转发用户面网关包括第一用户面网关和第二用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关与所述用户设备移动到当前位置区域之前的服务控制面网关相同，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元，
    所述接收单元还用于接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    所述控制面网关还包括发送单元，所述隧道建立单元具体用于：
    通过所述发送单元向所述第二用户面网关发送第二请求，并通过所述发送单元向所述第三用户面网关发送第三请求，并通过所述发送单元向所述源用户面网关发送第四请求，其中，所述第二请求用于请求所述第二用户面网 关建立所述第二用户面网关与所述目标基站之间的数据转发隧道，以及所述第二用户面网关与所述第三用户面网关之间的数据转发隧道，所述第二请求携带所述目标基站的路由信息，以及所述第三用户面网关的路由信息，所述第三请求用于请求所述第三用户面网关建立所述第三用户面网关与所述第二用户面网关之间的数据转发隧道，以及所述第三用户面网关与所述源用户面网关之间的数据转发隧道，所述第三请求携带所述第二用户面网关的路由信息，以及所述源用户面网关的路由信息，所述第四请求用于请求所述源用户面网关建立所述源用户面网关与所述第三用户面网关之间的数据转发隧道，所述第四请求携带所述第三用户面网关的路由信息。
  19. 如权利要求16所述的控制面网关，其特征在于，所述至少一个转发用户面网关为第一用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关不同于所述用户设备移动到当前位置区域之前的服务控制面网关，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元，
    所述接收单元还用于接收所述源用户面网关的路由信息；
    所述接收单元还用于接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    所述控制面网关还包括发送单元，所述隧道建立单元具体用于：
    通过所述发送单元向所述第一用户面网关发送第二请求，其中，所述第二请求用于请求所述第一用户面网关建立所述第一用户面网关与所述目标基站之间的数据转发隧道，以及所述第一用户面网关与所述源用户面网关之间的数据转发隧道，所述第二请求携带所述目标基站的路由信息，以及所述源用户面网关的路由信息。
  20. 如权利要求16所述的控制面网关，其特征在于，所述至少一个转发用户面网关包括第一用户面网关和第二用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关不同于所述用户设备移动到当前位置区域之前的服务控制面网关，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元，
    所述接收单元还用于接收所述源用户面网关的路由信息；
    所述接收单元还用于接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    所述控制面网关还包括发送单元，所述隧道建立单元具体用于：
    通过所述发送单元向所述第二用户面网关发送第二请求，并通过所述发送单元向所述第三用户面网关发送第三请求，其中，所述第二请求用于请求所述第二用户面网关建立所述第二用户面网关与所述目标基站之间的数据转发隧道，以及所述第二用户面网关与所述第三用户面网关之间的数据转发隧道，所述第二请求携带所述目标基站的路由信息，以及所述第三用户面网关的路由信息，所述第三请求用于请求所述第三用户面网关建立所述第三用户面网关与所述第二用户面网关之间的数据转发隧道，以及所述第三用户面网关与所述源用户面网关之间的数据转发隧道，所述第三请求携带所述第二用户面网关的路由信息，以及所述源用户面网关的路由信息。
  21. 如权利要求16至20任一项所述的控制面网关，其特征在于，
    所述隧道建立单元还用于向所述用户设备的目标用户面网关发送建立会话请求，所述建立会话请求用于在所述目标用户面网关上为所述用户设备创建用户面数据传输所需的承载上下文，其中，所建立的每个所述承载上下文包含所述目标用户面网关的路由信息，所述目标用户面网关是所述用户设备的当前位置区域对应的服务用户面网关。
  22. 如权利要求21所述的控制面网关，其特征在于，
    所述隧道建立单元还用于通过所述移动管理网元向所述目标基站发送所述目标用户面网关的路由信息。
  23. 如权利要求17或19所述的控制面网关，其特征在于，
    所述隧道建立单元还用于通过所述移动管理网元向所述目标基站发送所述第一用户面网关的路由信息。
  24. 如权利要求17或19或23所述的控制面网关，其特征在于，
    所述第一用户面网关是所述控制面网关根据所述用户设备的当前位置信息为所述用户设备选择的服务用户面网关。
  25. 如权利要求18或20所述的控制面网关，其特征在于，
    所述隧道建立单元还用于通过所述移动管理网元向所述目标基站发送所述第二用户面网关的路由信息。
  26. 一种移动管理网元，其特征在于，包括：
    接收单元，用于接收服务用户设备的源移动管理网元发送的转发重定位请求，所述转发重定位请求携带所述用户设备的当前位置信息；
    选择单元，用于根据所述用户设备的当前位置信息选择所述用户设备的目标控制面网关；
    发送单元，用于向所述目标控制面网关发送所述用户设备的当前位置信息，以便所述目标控制面网关根据所述用户设备的当前位置信息确定所述用户设备的转发用户面网关；
    所述发送单元还用于向所述目标控制面网关发送数据转发隧道建立请求，所述数据转发隧道建立请求用于请求所述目标控制面网关在所述转发用户面网关与服务所述用户设备的源用户面网关之间，以及所述转发用户面网关与服务所述用户设备的目标基站之间为所述用户设备建立数据转发隧道。
  27. 如权利要求26所述的移动管理网元，其特征在于，所述目标控制面网关与所述用户设备移动到当前位置区域之前的服务控制面网关不同，
    所述发送单元还用于向所述源移动管理网元发送改变通知消息，所述改变通知消息用于指示所述用户设备的服务控制面网关变更为所述目标控制面网关。
  28. 如权利要求27所述的移动管理网元，其特征在于，
    所述接收单元还用于接收所述源移动管理网元根据所述改变通知消息发送的确认消息，所述确认消息携带所述源用户面网关的路由信息。
  29. 一种控制面网关，其特征在于，包括：
    接收单元，用于接收移动管理网元发送的用户设备的当前位置信息；
    选择单元，用于根据所述用户设备的当前位置信息为所述用户设备选择目标用户面网关；
    发送单元，用于向所述移动管理网元发送请求消息，所述请求消息用于请求所述移动管理网元释放释放第一承载上下文并指示所述用户设备发送第二承载上下文的建立请求，其中，所述第一承载上下文是建立在所述用户设备的源用户面网关上的所述用户设备的承载上下文，所述第二承载上下文是所述用户设备根据所述第一承载上下文在所述目标用户面网关上重建的承载上下文。
  30. 如权利要求29所述的控制面网关，其特征在于，
    所述请求消息为删除承载请求消息，所述删除承载请求消息携带重新激活请求指示，所述重新激活请求指示用于通过所述移动管理网元指示所述用户设备在所述第一承载上下文删除后，发起所述第二承载上下文的建立请 求。
  31. 一种控制面网关，其特征在于，包括：存储器、处理器、接收机和发射机，其中，
    所述存储器用于存放程序，并向所述处理器提供数据和指令；
    所述处理器用于执行所述存储器所存放的程序，并具体用于执行以下操作：
    通过所述接收机接收移动管理网元发送的用户设备的当前位置信息；
    根据所述用户设备的当前位置信息为所述用户设备选择至少一个转发用户面网关；
    在服务所述用户设备的源用户面网关与所述转发用户面网关之间，以及所述转发用户面网关与服务所述用户设备的目标基站之间，为所述用户设备建立数据转发隧道，其中，所述数据转发隧道用于在所述用户设备的移动过程中传输所述用户设备的上行用户面数据和/或下行用户面数据。
  32. 如权利要求31所述的控制面网关，其特征在于，所述至少一个转发用户面网关为第一用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关与所述用户设备移动到当前位置区域之前的服务控制面网关相同，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元；
    所述处理器还用于通过所述接收机接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    在用于通过所述发射机在所述源用户面网关与所述转发用户面网关之间，和/或所述转发用户面网关与所述目标基站之间，为所述用户设备建立数据转发隧道的过程中，所述处理器具体用于：
    通过所述发射机向所述第一用户面网关发送第二请求，并通过所述发射机向所述源用户面网关发送第三请求，其中，所述第二请求用于请求所述第一用户面网关建立所述第一用户面网关与所述目标基站之间的数据转发隧道，以及所述第一用户面网关与所述源用户面网关之间的数据转发隧道，所述第二请求携带所述目标基站的路由信息，以及所述源用户面网关的路由信息，所述第三请求用于请求所述源用户面网关建立所述源用户面网关与所述第一用户面网关之间的数据转发隧道，所述第三请求携带所述第一用户面网关的路由信息。
  33. 如权利要求31所述的控制面网关，其特征在于，所述至少一个转发用户面网关包括第一用户面网关和第二用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关与所述用户设备移动到当前位置区域之前的服务控制面网关相同，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元；
    所述处理器还用于通过所述接收机接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    在用于通过所述发射机在所述源用户面网关与所述转发用户面网关之间，以及所述转发用户面网关与所述目标基站之间，为所述用户设备建立数据转发隧道的过程中，所述处理器具体用于：
    通过所述发射机向所述第二用户面网关发送第二请求，并通过所述发射机向所述第三用户面网关发送第三请求，并通过所述发射机向所述源用户面网关发送第四请求，其中，所述第二请求用于请求所述第二用户面网关建立所述第二用户面网关与所述目标基站之间的数据转发隧道，以及所述第二用户面网关与所述第三用户面网关之间的数据转发隧道，所述第二请求携带所述目标基站的路由信息，以及第三用户面网关的路由信息，所述第三请求用于请求所述第三用户面网关建立所述第三用户面网关与所述第二用户面网关之间的数据转发隧道，以及所述第三用户面网关与所述源用户面网关之间的数据转发隧道，所述第三请求携带所述第二用户面网关的路由信息，以及所述源用户面网关的路由信息，所述第四请求用于请求所述源用户面网关建立所述源用户面网关与所述第三用户面网关之间的数据转发隧道，所述第四请求携带所述第三用户面网关的路由信息。
  34. 如权利要求31所述的控制面网关，其特征在于，所述至少一个转发用户面网关为第一用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关不同于所述用户设备移动到当前位置区域之前的服务控制面网关，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元；
    所述处理器还用于通过所述接收机接收所述源用户面网关的路由信息；
    所述处理器还用于通过所述接收机接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    在用于通过所述发射机在所述源用户面网关与所述转发用户面网关之 间，以及所述转发用户面网关与所述目标基站之间，为所述用户设备建立数据转发隧道的过程中，所述处理器具体用于：
    通过所述发射机向所述第一用户面网关发送第二请求，其中，所述第二请求用于请求所述第一用户面网关建立所述第一用户面网关与所述目标基站之间的数据转发隧道，以及所述第一用户面网关与所述源用户面网关之间的数据转发隧道，所述第二请求携带所述目标基站的路由信息，以及所述源用户面网关的路由信息。
  35. 如权利要求31所述的控制面网关，其特征在于，所述至少一个转发用户面网关包括第一用户面网关和第二用户面网关，所述控制面网关为所述用户设备移动到当前位置区域之后的服务控制面网关，且所述控制面网关不同于所述用户设备移动到当前位置区域之前的服务控制面网关，所述移动管理网元为所述用户设备移动到当前位置区域之后的服务移动管理网元；
    所述处理器还用于通过所述接收机接收所述源用户面网关的路由信息；
    所述处理器还用于通过所述接收机接收所述移动管理网元发送的第一请求，所述第一请求携带所述目标基站的路由信息；
    在用于通过所述发射机在所述源用户面网关与所述转发用户面网关之间，以及所述转发用户面网关与所述目标基站之间，为所述用户设备建立数据转发隧道的过程中，所述处理器具体用于：
    通过所述发射机向所述第二用户面网关发送第二请求，并通过所述发射机向所述第三用户面网关发送第三请求，其中，所述第二请求用于请求所述第二用户面网关建立所述第二用户面网关与所述目标基站之间的数据转发隧道，以及所述第二用户面网关与所述第三用户面网关之间的数据转发隧道，所述第二请求携带所述目标基站的路由信息，以及第三用户面网关的路由信息，所述第三请求用于请求所述第三用户面网关建立所述第三用户面网关与所述第二用户面网关之间的数据转发隧道，以及所述第三用户面网关与所述源用户面网关之间的数据转发隧道，所述第三请求携带所述第二用户面网关的路由信息，以及所述源用户面网关的路由信息。
  36. 如权利要求31至35任一项所述的控制面网关，其特征在于，所述处理器还用于通过所述发射机向所述目标用户面网关发送建立会话请求，其中，所述建立会话请求用于在所述目标用户面网关上为所述用户设备创建用户面数据传输所需的承载上下文，所建立的每个所述承载上下文都包含所述 目标用户面网关的路由信息，所述目标用户面网关是所述用户设备的当前位置区域对应的服务用户面网关。
  37. 如权利要求36所述的控制面网关，其特征在于，所述处理器还用于通过所述移动管理网元向所述目标基站发送所述目标用户面网关的路由信息。
  38. 如权利要求32或34所述的控制面网关，其特征在于，
    所述处理器还用于通过所述移动管理网元向所述目标基站发送所述第一用户面网关的路由信息。
  39. 如权利要求32或34或38所述的控制面网关，其特征在于，
    所述第一用户面网关是所述控制面网关根据所述用户设备的当前位置信息为所述用户设备选择的服务用户面网关。
  40. 如权利要求33或35所述的控制面网关，其特征在于，
    所述处理器还用于通过所述移动管理网元向所述目标基站发送所述第二用户面网关的路由信息。
  41. 一种移动管理网元，其特征在于，包括：存储器、处理器、接收机和发射机，其中，
    所述存储器用于存放程序，并向所述处理器提供数据和指令；
    所述处理器用于执行所述存储器所存放的程序，并具体用于执行以下操作：
    通过所述接收机接收服务用户设备的源移动管理网元发送的转发重定位请求，所述转发重定位请求携带所述用户设备的当前位置信息；
    根据所述用户设备的当前位置信息选择所述用户设备的目标控制面网关；
    通过所述发射机向所述目标控制面网关发送所述用户设备的当前位置信息，以便所述目标控制面网关根据所述用户设备的当前位置信息确定所述用户设备的转发用户面网关；
    通过所述发射机向所述目标控制面网关发送数据转发隧道建立请求，所述数据转发隧道建立请求用于请求所述目标控制面网关在所述转发用户面网关与服务所述用户设备的源用户面网关之间，以及所述转发用户面网关与服务所述用户设备的目标基站之间为所述用户设备建立数据转发隧道。
  42. 如权利要求41所述的移动管理网元，其特征在于，所述目标控制 面网关与所述用户设备移动到当前位置区域之前的服务控制面网关不同，
    所述处理器还用于通过所述发射机向所述源移动管理网元发送改变通知消息，所述改变通知消息用于指示所述用户设备的服务控制面网关变更为所述目标控制面网关。
  43. 如权利要求42所述的移动管理网元，其特征在于，
    所述处理器还用于通过所述接收机接收所述源移动管理网元根据所述改变通知消息发送的确认消息，所述确认消息携带所述用户设备的源用户面网关的路由信息。
  44. 一种控制面网关，其特征在于，包括：存储器、处理器、接收机和发射机，其中，
    所述存储器用于存放程序，并向所述处理器提供数据和指令；
    所述处理器用于执行所述存储器所存放的程序，并具体用于执行以下操作：
    通过所述接收机接收移动管理网元发送的用户设备的当前位置信息；
    根据所述用户设备的当前位置信息为所述用户设备选择目标用户面网关；
    通过所述发射机向所述移动管理网元发送请求消息，所述请求消息用于请求所述移动管理网元释放释放第一承载上下文并指示所述用户设备发送第二承载上下文的建立请求，其中，所述第一承载上下文是建立在所述用户设备的源用户面网关上的所述用户设备的承载上下文，所述第二承载上下文是所述用户设备根据所述第一承载上下文在所述目标用户面网关上重建的承载上下文。
  45. 如权利要求44所述的控制面网关，其特征在于，
    所述请求消息为删除承载请求消息，所述删除承载请求消息携带重新激活请求指示，所述重新激活请求指示用于通过所述移动管理网元指示所述用户设备在所述第一承载上下文删除后，发起所述第二承载上下文的建立请求。
PCT/CN2015/091242 2015-09-30 2015-09-30 保持业务连续性的方法、控制面网关和移动管理网元 WO2017054178A1 (zh)

Priority Applications (14)

Application Number Priority Date Filing Date Title
CN201580028759.3A CN107079507B (zh) 2015-09-30 2015-09-30 保持业务连续性的方法、控制面网关和移动管理网元
JP2018516449A JP6699847B2 (ja) 2015-09-30 2015-09-30 サービス継続性保証方法、制御プレーンゲートウェイ、およびモビリティ管理ネットワーク要素
PCT/CN2015/091242 WO2017054178A1 (zh) 2015-09-30 2015-09-30 保持业务连续性的方法、控制面网关和移动管理网元
BR112018006580-3A BR112018006580B1 (pt) 2015-09-30 Método de garantia de continuidade de serviço, porta de comunicação de plano de controle e elemento de rede de gerenciamento de mobilidade
CN202010178324.XA CN111510986B (zh) 2015-09-30 2015-09-30 保持业务连续性的方法、控制面网关和移动管理网元
EP19178009.7A EP3624545B1 (en) 2015-09-30 2015-09-30 Communication system and method for ensuring service continuity
RU2018115851A RU2686596C1 (ru) 2015-09-30 2015-09-30 Способ обеспечения непрерывности обслуживания, шлюз плоскости управления и сетевой элемент управления мобильностью
EP15905090.5A EP3346795B1 (en) 2015-09-30 2015-09-30 Method for maintaining service continuity, control plane gateway and mobile management network element
KR1020187011731A KR102018635B1 (ko) 2015-09-30 2015-09-30 서비스 연속성 보장 방법, 제어 평면 게이트웨이, 및 이동성 관리 네트워크 엘리먼트
US15/940,348 US10638527B2 (en) 2015-09-30 2018-03-29 Service continuity ensuring method, control plane gateway, and mobility management network element
US16/431,261 US10595350B2 (en) 2015-09-30 2019-06-04 Service continuity ensuring method, control plane gateway, and mobility management network element
US16/730,487 US10701744B2 (en) 2015-09-30 2019-12-30 Service continuity ensuring method, control plane gateway, and mobility management network element
US16/731,701 US10827543B2 (en) 2015-09-30 2019-12-31 Service continuity ensuring method, control plane gateway, and mobility management network element
US17/069,957 US11432351B2 (en) 2015-09-30 2020-10-14 Service continuity ensuring method, control plane gateway, and mobility management network element

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/091242 WO2017054178A1 (zh) 2015-09-30 2015-09-30 保持业务连续性的方法、控制面网关和移动管理网元

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/940,348 Continuation US10638527B2 (en) 2015-09-30 2018-03-29 Service continuity ensuring method, control plane gateway, and mobility management network element

Publications (1)

Publication Number Publication Date
WO2017054178A1 true WO2017054178A1 (zh) 2017-04-06

Family

ID=58422520

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/091242 WO2017054178A1 (zh) 2015-09-30 2015-09-30 保持业务连续性的方法、控制面网关和移动管理网元

Country Status (7)

Country Link
US (5) US10638527B2 (zh)
EP (2) EP3624545B1 (zh)
JP (1) JP6699847B2 (zh)
KR (1) KR102018635B1 (zh)
CN (2) CN107079507B (zh)
RU (1) RU2686596C1 (zh)
WO (1) WO2017054178A1 (zh)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017004771A1 (zh) * 2015-07-06 2017-01-12 华为技术有限公司 增强多媒体广播组播业务eMBMS系统及其管理方法
WO2017054178A1 (zh) 2015-09-30 2017-04-06 华为技术有限公司 保持业务连续性的方法、控制面网关和移动管理网元
CN107241369B (zh) * 2016-03-28 2020-06-16 电信科学技术研究院 一种数据传输的方法、装置及会话管理功能实体设备
US10455459B2 (en) * 2016-08-23 2019-10-22 Lg Electronics Inc. Method and apparatus for establishing session for data transmission and reception in wireless communication system
KR102503538B1 (ko) * 2016-11-28 2023-02-24 삼성전자 주식회사 무선 통신 시스템에서, 게이트웨이의 네트워크 할당 방법 및 이를 위한 게이트웨이, 이동 관리 엔티티의 네트워크 할당 방법 및 이를 위한 이동 관리 엔티티, 단말의 네트워크 연결 방법 및 이를 위한 단말
WO2018149496A1 (en) * 2017-02-16 2018-08-23 Telefonaktiebolaget Lm Ericsson (Publ) Mechanisms for locating wireless devices
EP3574664B1 (en) 2017-03-16 2021-06-23 Samsung Electronics Co., Ltd. Network-initiated pdu session connection update method between terminal and network
CN112187650A (zh) * 2017-11-28 2021-01-05 华为技术有限公司 报文转发的方法、控制面网关和用户面网关
KR102372494B1 (ko) 2018-03-30 2022-03-10 삼성전자 주식회사 무인증으로 접속한 단말에 대한 셀룰라 네트워크 접속 해지 방법 및 장치
CN110662308B (zh) * 2018-06-30 2021-11-09 华为技术有限公司 一种通信方法及装置
US10785813B2 (en) * 2018-07-23 2020-09-22 International Business Machines Corporation Mobile communication network attachment to Wi-Fi
CN111181747B (zh) * 2018-11-09 2023-05-02 中兴通讯股份有限公司 一种网关协同实现方法、装置、IoT网关及存储介质
US20210337611A1 (en) * 2020-04-27 2021-10-28 Cisco Technology, Inc. Optimized serving gateway node selection for interworking networks
CN115250209A (zh) * 2021-04-08 2022-10-28 华为技术有限公司 一种控制用户设备接入网络的方法、装置及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090252133A1 (en) * 2008-04-07 2009-10-08 Hitachi Communication Technologies, Ltd. Mobile communication system and access gateway having plural user plane agws
CN104380834A (zh) * 2012-04-02 2015-02-25 诺基亚通信公司 用于移动通信网络架构优化的网关选择
CN104735808A (zh) * 2013-12-19 2015-06-24 中兴通讯股份有限公司 一种分布式网络中处理业务的方法及装置
US20150189689A1 (en) * 2013-12-31 2015-07-02 Alcatel-Lucent Usa, Inc. Methods And Systems For Optimizing Short Data Burst Services Over An LTE Network

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1956424A (zh) * 2005-10-26 2007-05-02 德赛电子(惠州)有限公司 基于分布式网关的通信方法及应用
CN101188542A (zh) * 2006-11-17 2008-05-28 华为技术有限公司 建立ip隧道的方法及系统及分发ip地址的装置
US8064403B2 (en) * 2007-08-17 2011-11-22 Research In Motion Limited Mobility mechanism for service continuity
JP5268848B2 (ja) * 2009-09-29 2013-08-21 三菱電機株式会社 通信システムおよびデータ転送方法
CN102123161B (zh) * 2010-01-08 2013-07-17 中国移动通信集团公司 一种分布式移动性管理的方法及分布式移动性管理系统
US8881236B2 (en) 2011-02-04 2014-11-04 Futurewei Technologies, Inc. Method and apparatus for a control plane to manage domain-based security and mobility in an information centric network
CN108307375A (zh) * 2011-11-29 2018-07-20 交互数字专利控股公司 用于ip移动性管理的方法
EP2820803B1 (en) * 2012-02-28 2020-08-26 Nokia Solutions and Networks Oy Data forwarding in a mobile communications network system with centralized gateway apparatus controlling distributed gateway elements
PT2854475T (pt) * 2012-06-29 2019-02-04 Huawei Tech Co Ltd Sistema de gateway, dispositivo e método de comunicação
WO2014008427A1 (en) * 2012-07-05 2014-01-09 Interdigital Patent Holdings, Inc. Systems and methods for pre-registration to enable mobility management
US9065699B2 (en) * 2012-11-30 2015-06-23 Cognosos, Inc. Methods and systems for a distributed radio communications network
US9706465B2 (en) * 2012-11-30 2017-07-11 Interdigital Patent Holdings, Inc. Systems and/or methods for anchor node selection in networks using distributed mobility management (DMM)
WO2014085761A2 (en) * 2012-11-30 2014-06-05 Interdigital Patent Holdings, Inc. Distributed mobility management technology in a network environment
CN105122777B (zh) * 2013-02-15 2018-12-14 交互数字专利控股公司 网络控制的wtru地址/锚点选择的方法
EP3022968A1 (en) * 2013-07-17 2016-05-25 Interdigital Patent Holdings, Inc. Software defined networking distributed and dynamic mobility management
US9596628B2 (en) * 2013-10-31 2017-03-14 Intel Corporation Gateway arrangements for wireless communication networks
CN104661205B (zh) * 2013-11-22 2019-12-03 中兴通讯股份有限公司 一种网关更新信息通知方法及控制器
CN104684044B (zh) 2013-11-29 2019-04-16 中兴通讯股份有限公司 一种路径建立的方法、控制器及移动性管理实体
KR102219415B1 (ko) * 2014-01-20 2021-02-25 삼성전자 주식회사 Lte 망에서 최적 데이터 경로를 위한 mme와 로컬 서버, 이들 간 인터페이스 및 데이터 송수신 방법
WO2017054178A1 (zh) 2015-09-30 2017-04-06 华为技术有限公司 保持业务连续性的方法、控制面网关和移动管理网元

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090252133A1 (en) * 2008-04-07 2009-10-08 Hitachi Communication Technologies, Ltd. Mobile communication system and access gateway having plural user plane agws
CN104380834A (zh) * 2012-04-02 2015-02-25 诺基亚通信公司 用于移动通信网络架构优化的网关选择
CN104735808A (zh) * 2013-12-19 2015-06-24 中兴通讯股份有限公司 一种分布式网络中处理业务的方法及装置
US20150189689A1 (en) * 2013-12-31 2015-07-02 Alcatel-Lucent Usa, Inc. Methods And Systems For Optimizing Short Data Burst Services Over An LTE Network

Also Published As

Publication number Publication date
CN107079507B (zh) 2020-04-14
US20200137813A1 (en) 2020-04-30
US10827543B2 (en) 2020-11-03
US11432351B2 (en) 2022-08-30
KR20180061265A (ko) 2018-06-07
KR102018635B1 (ko) 2019-09-05
US10595350B2 (en) 2020-03-17
US10701744B2 (en) 2020-06-30
BR112018006580A2 (zh) 2018-10-09
CN111510986A (zh) 2020-08-07
EP3346795B1 (en) 2019-06-19
JP2018530253A (ja) 2018-10-11
US20200137812A1 (en) 2020-04-30
EP3624545B1 (en) 2021-12-01
US10638527B2 (en) 2020-04-28
US20180220479A1 (en) 2018-08-02
EP3346795A4 (en) 2018-07-11
US20210029760A1 (en) 2021-01-28
US20190289652A1 (en) 2019-09-19
CN111510986B (zh) 2023-06-27
CN107079507A (zh) 2017-08-18
EP3624545A1 (en) 2020-03-18
EP3346795A1 (en) 2018-07-11
RU2686596C1 (ru) 2019-04-29
JP6699847B2 (ja) 2020-05-27

Similar Documents

Publication Publication Date Title
WO2017054178A1 (zh) 保持业务连续性的方法、控制面网关和移动管理网元
US10873886B2 (en) Mobile edge platform switching method, apparatus, and system
CN109155739B (zh) 切换过程中的通信方法和装置
JP2019521588A (ja) 通信制御方法および関連するネットワーク要素
US10841848B2 (en) Communication method, user equipment, base station, control plane network element, and communications system
KR101175219B1 (ko) 베어러 삭제 방법과 장치
JP2017513355A (ja) デュアルコネクティビティ動作におけるベアラのためのサービングゲートウェイのアップリンクユーザプレーン終端点切換え
WO2017029909A1 (ja) 無線通信システム、ゲートウェイ装置、移動管理エンティティ及び通信制御方法
KR102355153B1 (ko) 통신 방법, 액세스 네트워크 디바이스 및 단말기 디바이스
WO2017049458A1 (zh) 一种控制方法及本地控制面设备
JP6827520B2 (ja) サービス継続性保証方法、制御プレーンゲートウェイ、およびモビリティ管理ネットワーク要素
WO2018148861A1 (zh) 下行数据的传输方法及装置
WO2024094479A1 (en) Method, apparatus and computer program
BR112018006580B1 (pt) Método de garantia de continuidade de serviço, porta de comunicação de plano de controle e elemento de rede de gerenciamento de mobilidade

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2018516449

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2015905090

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112018006580

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20187011731

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2018115851

Country of ref document: RU

ENP Entry into the national phase

Ref document number: 112018006580

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20180329