WO2016070333A1 - 一种移动性管理的方法、装置及系统 - Google Patents

一种移动性管理的方法、装置及系统 Download PDF

Info

Publication number
WO2016070333A1
WO2016070333A1 PCT/CN2014/090274 CN2014090274W WO2016070333A1 WO 2016070333 A1 WO2016070333 A1 WO 2016070333A1 CN 2014090274 W CN2014090274 W CN 2014090274W WO 2016070333 A1 WO2016070333 A1 WO 2016070333A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
user equipment
base station
address
mobility management
Prior art date
Application number
PCT/CN2014/090274
Other languages
English (en)
French (fr)
Inventor
靳维生
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2014/090274 priority Critical patent/WO2016070333A1/zh
Priority to EP14905481.9A priority patent/EP3209043B1/en
Priority to CN201480033896.1A priority patent/CN105874830B/zh
Publication of WO2016070333A1 publication Critical patent/WO2016070333A1/zh
Priority to US15/586,151 priority patent/US20170238215A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H04W36/28—Reselection being triggered by specific parameters by agreed or negotiated communication parameters involving a plurality of connections, e.g. multi-call or multi-bearer connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • 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
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • 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
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • 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

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, device, and system for mobility management.
  • MPTCP Multi-Path Transmission Control Protocol
  • TCP Transmission Control Protocol
  • IP Internet Protocol
  • the MPTCP layer is responsible for selecting sub-package packets for service data flows, routing and Scheduling. Each sub-stream associates and manages multiple TCP sub-streams and transmits data concurrently to improve bandwidth utilization and transmission performance.
  • the socket and application layer do not care about the specific TCP sub-flows that transmit service data streams.
  • Embodiments of the present invention provide a method, apparatus, and system for mobility management, which can effectively ensure normal communication between a user equipment and a base station without passing through an anchor device.
  • a mobility management system includes: a user equipment, a first base station, a second base station, a first gateway, a second gateway, and a communication peer, where the first base station is connected to the first gateway, where The second base station is connected to the second gateway;
  • the user equipment is configured to establish a first substream with the communication peer end, where the first substream is a substream established by the user equipment by using a first internetworking protocol IP address and the communication peer end,
  • the first IP address is an IP address allocated by the first gateway to the user equipment;
  • the user equipment When the user equipment is switched by the first base station to the second base station, the user equipment is further configured to acquire a second IP address when the second gateway is not the same gateway as the first gateway, The second IP address is an IP address allocated by the second gateway to the user equipment;
  • the user equipment is further configured to establish a second substream with the communication peer after acquiring the second IP address, where the second substream uses the second IP address and the user equipment a substream established by the communication peer;
  • the communication peer is configured to revoke the first substream after the second substream is established
  • the first gateway is further configured to release the first IP address after the first subflow is revoked.
  • the user equipment is further configured to: after the revoking the first subflow, release the first IP address, and send an indication message for releasing the first IP address to the first gateway;
  • the first gateway is configured to release the first IP address after receiving the indication message that is released by the user equipment to release the first IP address.
  • the first base station and the second base station are configured to establish a data forwarding tunnel, where the data forwarding tunnel is a data forwarding channel between the first base station and the second base station;
  • the user equipment and the communication peer end are further configured to transmit data of the first substream by using the data forwarding tunnel.
  • the data forwarding tunnel includes:
  • the second base station is further configured to delete the data forwarding tunnel after the first substream is revoked.
  • the user equipment sends a request message for obtaining an IP address to the second gateway, and receives the second IP address sent by the second gateway. .
  • the mobility management system further includes a second mobility management entity, the second mobility management entity is configured to manage the second base station and the second gateway;
  • the user equipment When the user equipment is handed over by the first base station to the second base station, the user equipment sends the first IP address or the first gateway identifier to the second mobility management entity, where a gateway identifier is used to indicate the first gateway;
  • the second mobility management entity Determining, by the second mobility management entity, whether the first IP address is an IP address allocated by the second gateway for the user equipment, or whether the first gateway identifier is the same as a second gateway identifier, where The second gateway identifier is used to indicate the second gateway;
  • the second mobility management entity If the first IP address is not an IP address assigned by the second gateway to the user equipment, or the first gateway identifier is different from the second gateway identifier, the second mobility management entity is The second gateway requests the user equipment to allocate an IP address, and sends the second IP address received from the second gateway to the user equipment.
  • the user equipment When the user equipment is switched by the first base station to the second base station, the user equipment sends a second gateway identifier to the first base station, where the second gateway identifier is used to indicate the second gateway;
  • the first base station sends a judgment indication message to the user equipment, where the judgment indication message is used to indicate the second gateway and the first The gateway is not the same gateway;
  • the user equipment After receiving the determination indication message, the user equipment sends a request message for obtaining an IP address to the second gateway, and receives the second IP address sent by the second gateway.
  • the mobility management system further includes a second mobility management entity, the second mobility management entity is configured to manage the second base station and the second gateway;
  • the user equipment is further configured to: when the user equipment moves from the first base station to the second base station in an idle state, send a location update to the second mobility management entity. Request message
  • the second mobility management entity is configured to send a location update confirmation message to the user equipment.
  • the user equipment moves from the first base station to the second base station in an idle state, and enters an idle state after completing the location update by connecting the second base station;
  • the mobility management system further includes a first mobility management entity, where the first mobility management entity is configured to manage the first base station and the first gateway;
  • the first gateway is further configured to send a downlink data notification of the user equipment to the first mobility management entity after the user equipment enters an idle state;
  • the first mobility management entity is further configured to receive a downlink data notification of the user equipment from the first gateway, and page the user equipment after receiving the downlink data notification of the user equipment;
  • the user equipment is further configured to respond to the paging of the second mobility management entity.
  • the first gateway is further configured to buffer downlink data.
  • the first mobility management entity is further configured to: after the user equipment responds to the paging, request the downlink data from the first gateway, receive the downlink data sent by the first gateway, and The downlink data received by the first gateway is sent to the user equipment.
  • the first gateway is further configured to buffer downlink data.
  • the first mobility management entity is further configured to establish a downlink data forwarding tunnel after the user equipment responds to the paging;
  • the first gateway is further configured to send the downlink data to the user equipment by using the downlink data forwarding tunnel.
  • the user equipment moves from the first base station to the second base station in an idle state, and enters an idle state after completing the location update by connecting the second base station;
  • the mobility management system further includes a first mobility management entity and a second mobility management entity, the first mobility management entity configured to manage the first base station and the first gateway, the second mobility a sex management entity for managing the second base station and the second gateway;
  • the second mobility management entity is further configured to register, by the first mobility management entity, a downlink data notification of the user equipment;
  • the first gateway is further configured to send a downlink data notification of the user equipment to the first mobility management entity after the user equipment enters an idle state;
  • the first mobility management entity is further configured to: after confirming the registration of the second mobility management entity, send a downlink data notification of the user equipment to the second mobility management entity;
  • the second mobility management entity is further configured to page the user equipment after receiving the downlink data notification of the user equipment;
  • the user equipment is further configured to respond to the paging of the second mobility management entity.
  • the first gateway is further configured to buffer downlink data.
  • the second mobility management entity is further configured to request, by the first mobility management entity, the downlink data after the user equipment responds to the paging;
  • the first mobility management entity is further configured to forward the downlink data sent by the first gateway to the second mobility management entity;
  • the second mobility management entity is further configured to send the downlink data to the user equipment.
  • the first gateway is further configured to buffer downlink data.
  • the second mobility management entity is further configured to: after the user equipment responds to the paging Establishing a downlink data forwarding tunnel by using the first mobility management entity;
  • the first gateway is further configured to send the downlink data to the user equipment by using the downlink data forwarding tunnel.
  • the mobility management system further includes: a first mobility management entity, an online charging system OCS, and a policy and charging rule function PCRF.
  • the first mobility management entity is configured to acquire the available quota of the user equipment from the online charging system, and send the available quota of the user equipment to the first gateway;
  • the first mobility management entity is further configured to: obtain the charging rule of the user equipment from the policy and charging rule function, and send the charging rule of the user equipment to the first gateway;
  • the first gateway is further configured to: when the user equipment communicates with the communication peer end by using the first sub-flow, deducting the available quota of the user equipment according to the charging rule of the user equipment, And transmitting the available credit balance of the user equipment to the online charging system.
  • the mobility management system further includes: a first mobility management entity and an offline charging system OFCS.
  • the first gateway is further configured to send, to the first mobility management entity, a CDR of the user equipment at the first gateway;
  • the first mobility management entity is configured to send the CDR of the user equipment at the first gateway to an offline charging system.
  • a user equipment including a processor, a memory, and a bus, wherein the processor and the memory are connected to each other through the bus;
  • the processor is configured to establish a first substream with a communication peer, where the first substream is a substream established by the user equipment by using a first internetworking protocol IP address and the communication peer end, where The first IP address is an IP address assigned by the first gateway to the user equipment, and the first gateway is connected to the first base station;
  • the processor is further configured to obtain a second IP address, where the second IP address is an IP address allocated by the second gateway to the user equipment;
  • the processor is further configured to establish a second substream with the communication peer, where the second substream is a substream established by the user equipment by using the second IP address and the communication peer end;
  • the processor is further configured to revoke the first substream.
  • the processor is further configured to: after the revoking the first substream, release the first IP address, and generate an indication message indicating that the first gateway releases the first IP address;
  • the user equipment further includes a transmitter, configured to send, to the first gateway, an indication message indicating that the first gateway releases the first IP address.
  • the processor is further configured to transmit data of the first substream by using a data forwarding tunnel, where the data forwarding tunnel is a data forwarding channel between the first base station and the second base station.
  • the data forwarding tunnel includes:
  • the processor is further configured to release the first IP address
  • the processor is further configured to generate an indication message indicating that the first substream has been revoked
  • the user equipment further includes a transmitter, configured to send, to the second base station, an indication message indicating that the first sub-flow has been revoked, so that the second base station deletes the data forwarding tunnel.
  • the user equipment further includes a receiver
  • the receiver is configured to receive a first gateway identifier sent by the first base station, where the first gateway identifier is used to indicate a first gateway;
  • the receiver is further configured to receive a second gateway identifier sent by the second base station, where the second gateway identifier is used to indicate a second gateway;
  • the processor is further configured to determine whether the second gateway identifier is the same as the first gateway identifier, and if the second gateway identifier is different from the first gateway identifier, generate a request message for obtaining an IP address;
  • the user equipment further includes a sender, configured to send the request message for obtaining an IP address to the second gateway;
  • the receiver is further configured to receive the second IP address sent by the second gateway.
  • the user equipment further includes a transmitter and a receiver
  • the transmitter is configured to send the first IP address or the first gateway identifier to the second mobility management entity when the user equipment is switched by the first base station to the second base station, so as to facilitate Determining, by the second mobility management entity, whether the second gateway and the first gateway are the same gateway according to the first IP address or the first gateway identifier, and the second gateway and the first gateway
  • the user equipment is requested to allocate an IP address to the second gateway, and the second IP address received from the second gateway is sent to the user equipment, where the first gateway identifier is used for Instructing a first gateway, where the second mobility management entity is configured to manage the second base station and the second gateway;
  • the receiver is configured to receive the second IP address sent by the second mobility management entity.
  • the user equipment further includes a transmitter and a receiver
  • the transmitter is configured to send, when the user equipment is switched by the first base station to the second base station, a second gateway identifier to the first base station, to facilitate the Determining, by the base station, whether the second gateway is the same gateway as the first gateway, and the second gateway identifier is used to indicate the second gateway;
  • the receiver is configured to receive a judgment indication message sent by the first base station, where the judgment indication message is used to indicate that the second gateway is not the same gateway as the first gateway;
  • the processor is further configured to generate a request message for obtaining an IP address
  • the transmitter is further configured to send the request message for obtaining an IP address to the second gateway;
  • the receiver is further configured to receive the second IP address sent by the second gateway.
  • the processor is further configured to generate a location update request message when the user equipment moves from the first base station to the second base station in an idle state;
  • the user equipment further includes a receiver and a transmitter,
  • the transmitter is configured to send the location update request message to a second mobility management entity, where the second mobility management entity is configured to manage the second base station and the second gateway;
  • the receiver is configured to receive a location update confirmation message sent by the second mobility management entity.
  • the processor is further configured to control the user equipment to enter an idle state
  • the receiver is further configured to receive a paging of the first mobility management entity when the user equipment is in an idle state, where the first mobility management entity is configured to manage the first base station and the first gateway ;
  • the processor is further configured to generate a paging response message
  • the transmitter is configured to send the paging response message to the first mobility management entity
  • the receiver is further configured to receive the second mobile when the user equipment is in an idle state Paging of the management entity, the second mobility management entity is configured to manage the second base station and the second gateway.
  • the transmitter is configured to send the paging response message to the second mobility management entity.
  • the receiver is further configured to receive the downlink data.
  • a first base station includes a processor, a memory, a transmitter, a receiver, and a bus, and the processor, the memory, the transmitter, and the receiver are connected to each other through the bus;
  • the processor is configured to generate a data forwarding tunnel setup request message, the second, before the second substream is established, when the user equipment is switched by the first base station to the second base station.
  • the sub-flow is a sub-flow established by the user equipment with the second internet protocol IP address and the communication peer, the second IP address is an IP address assigned by the second gateway to the user equipment, and the second gateway is The second base station is connected, the data forwarding tunnel is a data forwarding channel between the first base station and the second base station, and the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or the data forwarding
  • the tunnel includes the downlink data forwarding tunnel and the uplink data forwarding tunnel, where the data forwarding channel is used to transmit data of the first substream, where the first substream is used by the user equipment by the first base station Before the second base station is switched, the first IP address is used to establish a sub-flow with the communication peer, and the first IP address is an IP address allocated by the first gateway to the user equipment,
  • the transmitter is configured to send, to the second base station, the establishment request message of the data forwarding tunnel;
  • the receiver is configured to receive a setup confirmation message of the data forwarding tunnel sent by the second base station;
  • the receiver is further configured to receive a deletion request message of the data forwarding tunnel sent by the second base station;
  • the transmitter is further configured to send, to the second base station, a deletion confirmation message of the data forwarding tunnel;
  • the processor is further configured to release the data forwarding tunnel and generate a first IP release indication message
  • the transmitter is further configured to send the first IP release indication message to the first gateway.
  • the receiver is further configured to receive a second gateway identifier sent by the user equipment, where the second gateway identifier is used to indicate a second gateway;
  • the processor is further configured to determine, according to the second gateway identifier, whether the second gateway and the first gateway are the same gateway, and when the second gateway is not the same gateway as the first gateway, generate Determining an indication message, where the determining indication message is used to indicate that the second gateway is not the same gateway as the first gateway;
  • the transmitter is further configured to send the judgment indication message to the user equipment, so that the user equipment sends a request message for obtaining an IP address to the second gateway, and receives the information sent by the second gateway. Said second IP address.
  • a fourth base station comprising: a processor, a memory, a transmitter, a receiver, and a bus, wherein the processor, the memory, the transmitter, and the receiver are connected to each other through the bus;
  • the receiver is configured to: when the user equipment is switched by the first base station to the second base station, receive the establishment of a data forwarding tunnel sent by the first base station before the second substream is established. a request message, the second sub-flow is a sub-flow established by the user equipment with a second internet protocol IP address and a communication peer, and the second IP address is an IP address assigned by the second gateway to the user equipment
  • the second gateway is connected to the second base station, where the data forwarding tunnel is a data forwarding channel between the first base station and the second base station, and the data forwarding tunnel includes a downlink data forwarding tunnel or uplink data forwarding.
  • the tunnel, or the data forwarding tunnel includes the downlink data forwarding tunnel and the uplink data forwarding tunnel, where the data forwarding channel is used to transmit data of the first substream, where the first substream is the user equipment From the first base station to the Before the second base station is switched, the first IP address is used to establish a sub-flow with the communication peer, and the first IP address is an IP address allocated by the first gateway to the user equipment, the first gateway and the first gateway The first base station is connected;
  • the processor is configured to generate a setup confirmation message of the data forwarding tunnel
  • the transmitter is configured to send, to the first base station, a setup confirmation message of the data forwarding tunnel
  • the processor is further configured to generate a delete request message of the data forwarding tunnel after the first substream is revoked;
  • the transmitter is further configured to send, to the first base station, a deletion request message of the data forwarding tunnel;
  • the receiver is further configured to receive a deletion confirmation message of the data forwarding tunnel sent by the first base station;
  • the processor is further configured to release the data forwarding tunnel.
  • a fifth aspect is a user equipment, including: a multipath control unit and a transceiver unit,
  • the multipath control unit is configured to establish a first substream with the communication peer when the user equipment is connected to the first base station, where the first substream uses the first internet interconnection protocol IP for the user equipment And the first network gateway protocol IP address is an IP address assigned by the first gateway to the user equipment, and the first gateway is connected to the first base station;
  • the transceiver unit is configured to obtain a second IP address, where the second IP address is an IP address allocated by the second gateway to the user equipment;
  • the multi-path control unit is further configured to establish a second sub-flow with the communication peer, where the second sub-flow is a sub-flow established by the user equipment by using the second IP address and the communication peer ;
  • the multipath control unit is further configured to revoke the first substream after the second subflow is established.
  • a multipath control unit configured to release after the revoking the first substream Determining, by the first IP address, an indication message indicating that the first gateway releases the first IP address
  • the transceiver unit is further configured to send, to the first gateway, an indication message indicating that the first gateway releases the first IP address.
  • the transceiver unit is further configured to transmit data of the first substream by using a data forwarding tunnel, where the data forwarding tunnel is a data forwarding channel between the first base station and the second base station.
  • the multipath control unit is further configured to release the first IP address
  • the multipath control unit is further configured to generate an indication message that the first substream has been revoked
  • the transceiver unit is further configured to send, to the second base station, an indication message that the first sub-flow has been revoked, so that the second base station deletes the data forwarding tunnel.
  • the transceiver unit is further configured to: when the user equipment is connected to the first base station, receive the first gateway identifier sent by the first base station, where the first gateway identifier is used to indicate the first gateway;
  • the transceiver unit is further configured to: when the user equipment is switched by the first base station to the second base station, receive a second gateway identifier sent by the second base station, where the second gateway identifier is used to indicate Second gateway;
  • the multi-path control unit is further configured to determine whether the second gateway identifier is the same as the first gateway identifier, and if the second gateway identifier is different from the first gateway identifier, generate a request for obtaining an IP address.
  • the transceiver unit is further configured to send the request message for obtaining an IP address to the second gateway;
  • the transceiver unit is further configured to receive the second IP address sent by the second gateway.
  • the transceiver unit is further configured to: when the user equipment is switched by the first base station to the second base station, send the first IP address or the first gateway identifier to the second mobility management entity, so that Determining, by the second mobility management entity, whether the second gateway and the first gateway are the same gateway according to the first IP address or the first gateway identifier, and at the second gateway and the first When the gateway is not the same gateway, the user equipment is requested to allocate an IP address to the second gateway, and the second IP address received from the second gateway is sent to the user equipment, where the first gateway identifier is used. Instructing the first gateway, the second mobility management entity is configured to manage the second base station and the second gateway;
  • the transceiver unit is further configured to receive the second IP address sent by the second mobility management entity.
  • the transceiver unit is further configured to: when the user equipment is handed over by the first base station to the second base station, send a second gateway identifier to the first base station, so that the first base station determines Whether the second gateway is the same gateway as the first gateway, and the second gateway identifier is used to indicate the second gateway;
  • the transceiver unit is further configured to receive a judgment indication message sent by the first base station, where the judgment indication message is used to indicate that the second gateway is not the same gateway as the first gateway;
  • the multipath control unit is further configured to generate a request message for obtaining an IP address
  • the transceiver unit is further configured to send the request message for obtaining an IP address to the second gateway;
  • the transceiver unit is further configured to receive the second IP address sent by the second gateway.
  • the user equipment further includes a handover control unit,
  • the handover control unit is configured to generate a location update request message when the user equipment moves from the first base station to the second base station in an idle state;
  • the transceiver unit is further configured to send the location update request message to the second mobility management entity;
  • the transceiver unit is further configured to receive a location update confirmation message sent by the second mobility management entity, where the second mobility management entity is configured to manage the second base station and the second gateway.
  • the switching control unit is further configured to control the user equipment to enter an idle state
  • the transceiver unit is further configured to receive a paging of the first mobility management entity when the user equipment is in an idle state, where the first mobility management entity is configured to manage the first base station and the first gateway ;
  • the handover control unit is further configured to respond to the paging of the first mobility management entity
  • the transceiver unit is further configured to receive downlink data that is cached and forwarded by the first gateway;
  • the transceiver unit is further configured to receive a paging of a second mobility management entity when the user equipment is in an idle state, where the first mobility management entity is configured to manage the first base station and the first gateway .
  • the handover control unit is further configured to respond to the paging of the second mobility management entity.
  • the transceiver unit is further configured to receive the downlink data.
  • a first base station comprising: a control unit, a sending unit, and a receiving unit;
  • the control unit is configured to: when the user equipment is used by the first base station When the second base station is switched, the data forwarding tunnel establishment request message is generated before the second substream is established, and the second substream is a substream established by the user equipment by using the second internet protocol IP address and the communication peer end.
  • the second IP address is an IP address assigned by the second gateway to the user equipment, the second gateway is connected to the second base station, and the data forwarding tunnel is between the first base station and the second base station.
  • the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or the data forwarding tunnel includes the downlink data forwarding tunnel and the uplink data forwarding tunnel, where the data forwarding channel is used for transmission.
  • the first IP address is an IP address assigned by the first gateway to the user equipment, and the first gateway is connected to the first base station;
  • the sending unit is configured to send, by the second base station, an establishment request message of the data forwarding tunnel
  • the receiving unit is configured to receive a setup confirmation message of the data forwarding tunnel sent by the second base station;
  • the receiving unit is further configured to receive a deletion request message of the data forwarding tunnel sent by the second base station;
  • the control unit is further configured to generate a deletion confirmation message of the data forwarding tunnel
  • the sending unit is further configured to send a deletion confirmation message of the data forwarding tunnel to the second base station;
  • the control unit is further configured to release the data forwarding tunnel and generate a first IP release indication message
  • the sending unit is further configured to send the first IP release indication message to the first gateway.
  • the receiving unit is further configured to receive a second gateway identifier sent by the user equipment, where the second gateway identifier is used to indicate a second gateway;
  • the control unit is further configured to determine the second network according to the second gateway identifier And determining whether the first gateway is the same gateway, and when the second gateway is not the same gateway as the first gateway, generating a determination indication message, where the determining indication message is used to indicate the second gateway and the Said that the first gateway is not the same gateway;
  • the sending unit is further configured to send a judgment indication message to the user equipment, so that the user equipment sends a request message for obtaining an IP address to the second gateway, and receives the first message sent by the second gateway. Two IP addresses.
  • a second base station comprising: a control unit, a sending unit, and a receiving unit;
  • the receiving unit is configured to: when the user equipment is switched by the first base station to the second base station, receive a data forwarding tunnel establishment request message sent by the first base station, before the second substream is established, where The second substream is a substream established by the user equipment using a second internet protocol IP address and a communication peer, and the second IP address is an IP address assigned by the second gateway to the user equipment, where the The second gateway is connected to the second base station, where the data forwarding tunnel is a data forwarding channel between the first base station and the second base station, and the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or The data forwarding tunnel includes the downlink data forwarding tunnel and the uplink data forwarding tunnel, and the data forwarding channel is configured to transmit data of the first substream, where the first substream is the user equipment Before the base station switches to the second base station, using the first IP address and the sub-flow established by the communication peer, the first IP address is an IP allocated by the first gateway to the user equipment. Address, the
  • the control unit is configured to generate a setup confirmation message of the data forwarding tunnel
  • the sending unit is configured to send, to the first base station, a setup confirmation message of the data forwarding tunnel
  • the control unit is further configured to: after the first substream is revoked, generate a delete request message of the data forwarding tunnel;
  • the sending unit is further configured to send, to the first base station, a deletion request message of the data forwarding tunnel;
  • the receiving unit is further configured to receive the data forwarding sent by the first base station Tunnel deletion confirmation message
  • the control unit is further configured to release the data forwarding tunnel.
  • a mobility management method is characterized in that
  • the user equipment establishes a first substream with the communication peer, and the first substream is a substream established by the user equipment by using the first internetworking protocol IP address and the communication peer, where the first IP address is The IP address assigned by the first gateway to the user equipment;
  • the user equipment When the user equipment is switched by the first base station to the second base station, when the second gateway is not the same gateway as the first gateway, the user equipment acquires a second IP address, where the The second IP address is an IP address allocated by the second gateway to the user equipment;
  • the second substream is established with the communication peer, and the second substream is established by the user equipment by using the second IP address and the communication peer.
  • the first substream is revoked
  • the first gateway releases the first IP address after the first substream is revoked.
  • the user equipment releases the first IP address after the first substream is revoked, and instructs the first gateway to release the first IP address.
  • the user equipment is switched by the first base station to the second base station, and the user equipment is switched by the first base station to the second base station during ongoing communication with the communication peer end. ;
  • the method further includes:
  • the first base station and the second base station establish a data forwarding tunnel, where the data forwarding tunnel is a data forwarding channel between the first base station and the second base station;
  • the user equipment and the communication peer end transmit data of the first substream through the data forwarding tunnel.
  • the data forwarding tunnel includes:
  • the method further includes:
  • the second base station deletes the data forwarding tunnel.
  • the acquiring, by the user equipment, the second IP address includes:
  • the user equipment sends a request message for obtaining an IP address to the second gateway, and receives the second IP address sent by the second gateway. .
  • the acquiring, by the user equipment, the second IP address includes:
  • the mobility management system further includes a second mobility management entity
  • the user equipment When the user equipment is handed over by the first base station to the second base station, the user equipment sends the first IP address or the first gateway identifier to the second mobility management entity, where a gateway identifier is used to indicate the first gateway;
  • the second mobility management entity If the first IP address is not an IP address assigned by the second gateway to the user equipment, or the first gateway identifier is different from the second gateway identifier, the second mobility management entity is The second gateway requests the user equipment to allocate an IP address, and sends the second IP address received from the second gateway to the user equipment.
  • the acquiring, by the user equipment, the second IP address includes:
  • the user equipment When the user equipment is switched by the first base station to the second base station, the user equipment sends a second gateway identifier to the first base station, where the second gateway identifier is used to indicate the second gateway;
  • the first base station sends a judgment indication message to the user equipment, where the first gateway identifier is used to indicate the first gateway, and the determination indication message indicates The second gateway is not the same gateway as the first gateway;
  • the user equipment After receiving the determination indication message, the user equipment sends a request message for obtaining an IP address to the second gateway, and receives the second IP address sent by the second gateway.
  • the user equipment is handed over by the first base station to the second base station, including: the user equipment moves from the first base station to the second base station in an idle state, and sends a location to the second mobility management entity. And updating a request message, and receiving a location update acknowledgement message sent by the second mobility management entity, where the second mobility management entity is configured to manage the second base station and the second gateway.
  • the method further includes:
  • the first gateway After the user equipment enters an idle state, the first gateway sends a downlink data notification of the user equipment to the first mobility management entity, where the first mobility management An entity is configured to manage the first base station and the first gateway;
  • the user equipment is responsive to a page of the first mobility management entity.
  • the method further includes:
  • the first gateway buffers downlink data
  • the method further includes:
  • the first mobility management entity After the user equipment responds to the paging, the first mobility management entity requests the downlink data from the first gateway, receives the downlink data sent by the first gateway, and sends the downlink data from the first gateway. The received downlink data is sent to the user equipment.
  • the method further includes:
  • the first gateway buffers downlink data
  • the method further includes:
  • the first mobility management entity establishes a downlink data forwarding tunnel
  • the first gateway sends the downlink data to the user equipment by using the downlink data forwarding tunnel.
  • the user equipment moves from the first base station to the second base station in an idle state to perform location update, and enters an idle state after receiving a location update acknowledgement message sent by the second base station;
  • the second mobility management entity After the user equipment enters an idle state, the second mobility management entity registers a downlink data notification of the user equipment with the first mobility management entity, where the second mobility management entity is configured to manage the second base station and the a second gateway, the first mobility management entity is configured to manage the first base station and the first gateway;
  • the first mobility management entity After confirming the registration of the second mobility management entity, the first mobility management entity sends a downlink data notification of the user equipment to the second mobility management entity;
  • the second mobility management entity pages the user equipment after receiving the downlink data notification of the user equipment;
  • the user equipment is responsive to a page of the second mobility management entity.
  • the method further includes:
  • the first gateway buffers downlink data
  • the method further includes:
  • the second mobility management entity requests the downlink data by using the first mobility management entity
  • the second mobility management entity sends the downlink data to the user equipment.
  • the method further includes:
  • the first gateway buffers downlink data
  • the The method also includes:
  • the second mobility management entity establishes a downlink data forwarding tunnel by using the first mobility management entity
  • the first gateway sends the downlink data to the user equipment by using the downlink data forwarding tunnel.
  • the method further includes:
  • the first gateway acquires a charging rule of the user equipment and an available quota of the user equipment;
  • the first gateway deducts the available quota of the user equipment according to the charging rule of the user equipment when the user equipment communicates with the communication peer by using the first substream;
  • the first gateway sends the available credit balance of the user equipment to the online charging system.
  • the method further includes:
  • the first mobility management entity sends the CDR of the user equipment at the first gateway to an offline charging system.
  • a ninth aspect a mobility management method, applied to a user equipment,
  • the user equipment When the user equipment is connected to the first base station, the user equipment establishes a first substream with the communication peer, and the first substream uses the first internetworking protocol IP address and the communication for the user equipment
  • the first IP address is the IP address assigned by the first gateway to the user equipment, and the first gateway is connected to the first base station;
  • the user equipment When the user equipment is switched by the first base station to the second base station, when the second gateway is not the same gateway as the first gateway, the user equipment acquires a second IP address, the second IP address.
  • the address is an IP allocated by the second gateway to the user equipment. address;
  • the user equipment establishes a second sub-flow with the communication peer, where the second sub-flow is a sub-flow established by the user equipment by using the second IP address and the communication peer;
  • the user equipment revokes the first substream after the second substream is established.
  • the user equipment After the user equipment revokes the first substream, the user equipment releases the first IP address, and instructs the first gateway to release the first IP address.
  • the user equipment is switched by the first base station to the second base station, and the user equipment is switched by the first base station to the second base station during ongoing communication with the communication peer end. ;
  • the method further includes:
  • the user equipment establishes a data forwarding tunnel with the communication peer end, and transmits data of the first substream by using the data forwarding tunnel, where the data forwarding tunnel is the first base station and the second base station Data forwarding channel between.
  • the data forwarding tunnel includes:
  • the method further includes:
  • the user equipment releases the first IP address, and instructs the first gateway to release the first IP address
  • the user equipment indicates to the second base station that the first sub-flow has been revoked, so that the second base station deletes the data forwarding tunnel.
  • the user setting Get the second IP address including:
  • the user equipment sends a request message for obtaining an IP address to the second gateway, and receives the second IP address sent by the second gateway. .
  • the second mobility management entity is configured to manage the second base station and the second gateway.
  • the user equipment When the user equipment is handed over by the first base station to the second base station, the user equipment sends a second gateway identifier to the first base station, so that the first base station determines the second gateway. Whether the first gateway is the same gateway, and the second gateway identifier is used to indicate the second gateway;
  • the determination indication message sent by the first base station, sending a request message for obtaining an IP address to the second gateway, and receiving the sending request by the second gateway
  • the second IP address, the judgment indication message is used to indicate that the second gateway is not the same gateway as the first gateway.
  • the user equipment is handed over by the first base station to the second base station, including: the user equipment moves from the first base station to the second base station in an idle state, and sends a location to the second mobility management entity. And updating a request message, and receiving a location update acknowledgement message sent by the second mobility management entity, where the second mobility management entity is configured to manage the second base station and the second gateway.
  • the method further includes:
  • the user equipment enters an idle state
  • the user equipment After receiving the paging of the first mobility management entity in an idle state, the user equipment responds to the paging of the first mobility management entity, and receives downlink data buffered and forwarded by the first gateway, where the first a mobility management entity is configured to manage the first base station and the first gateway;
  • the first mobility management entity is configured to manage the first base station and the first gateway.
  • a mobility management method is applied to a first base station, when the user equipment is switched by the first base station to the second base station, before the second substream is established, the first base station Sending a setup request message of the data forwarding tunnel to the second base station, and receiving an establishment confirmation message of the data forwarding tunnel sent by the second base station,
  • the second sub-flow is a sub-flow established by the user equipment with the second internet protocol IP address and the communication peer, and the second IP address is an IP address assigned by the second gateway to the user equipment,
  • the second gateway is connected to the second base station, where the data forwarding tunnel is a data forwarding channel between the first base station and the second base station, and the data is
  • the forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or the data forwarding tunnel includes the downlink data forwarding tunnel and the uplink data forwarding tunnel, where the data forwarding channel is used to transmit data of the first substream.
  • the first sub-flow is a sub-flow established by the user equipment with the communication peer before using the first base station to switch to the second base station, where the first IP address is An IP address assigned by the gateway to the user equipment, where the first gateway is connected to the first base station;
  • the method further includes:
  • the first base station When the second gateway is not the same gateway as the first gateway, the first base station sends a determination indication message to the user equipment, so that the user equipment sends a request for obtaining an IP address to the second gateway. And receiving the second IP address sent by the second gateway, where the determining indication message is used to indicate that the second gateway is not the same gateway as the first gateway.
  • a mobility management method is applied to a second base station
  • the second base station When the user equipment is switched by the first base station to the second base station, before the second substream is established, the second base station receives a data forwarding tunnel setup request message sent by the first base station, and Sending a setup confirmation message of the data forwarding tunnel to the first base station,
  • the second sub-flow is a sub-flow established by the user equipment with the second internet protocol IP address and the communication peer, and the second IP address is an IP address assigned by the second gateway to the user equipment
  • the second gateway is connected to the second base station, where the data forwarding tunnel is a data forwarding channel between the first base station and the second base station, and the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or
  • the data forwarding tunnel includes the downlink data forwarding tunnel and the uplink data forwarding tunnel, and the data forwarding channel is configured to transmit data of the first substream, where the first substream is the user equipment Before the first base station switches to the second base station, the first IP address is used to establish a sub-flow with the communication peer, and the first IP address is an IP address allocated by the first gateway to the user equipment,
  • the first gateway is connected to the first base station;
  • the data request forwarding message of the data forwarding tunnel is sent to the first base station, and the deletion confirmation message of the data forwarding tunnel sent by the first base station is received;
  • the method, device and system for mobility management provided by the embodiments of the present invention dynamically allocate IP addresses to user equipments by using the first gateway and the second gateway.
  • the data aggregation type anchor device in the mobile network architecture uniformly allocates an IP address to the user equipment, and the anchor device has a huge pressure. Once the anchor device has a problem, the normal operation of the entire service network is affected, causing the user to The equipment business was interrupted.
  • the method, device and system for mobility management provided by the embodiment of the present invention, when the user equipment is switched from the first gateway to the second gateway, the user equipment and the communication peer establish a second substream by using the second IP address, Before the second substream is established, the user equipment communicates with the communication peer through the first substream, and after the second substream is established, the first substream is revoked. Therefore, the normal communication between the user equipment and the base station is effectively ensured without passing through the anchor device, and the business continuity between the user equipment and the communication peer is ensured.
  • FIG. 1 is a schematic structural diagram of a mobility management system according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a user equipment according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a first base station according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a second base station according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of another user equipment according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of another first base station according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of another second base station according to another embodiment of the present invention.
  • FIG. 8 is a schematic flowchart diagram of a mobility management method according to an embodiment of the present invention.
  • Embodiments of the present invention provide a method, apparatus, and system for mobility management.
  • the LTE (Long Term Evolution) cellular network is taken as an example for description.
  • the LTE cellular network includes: a first base station, a second base station, a first gateway, a second gateway, a first Mobility Management Entity (MME), a second mobility management entity, a user equipment, and a communication peer, where The first base station is connected to the first gateway, the second base station is connected to the second gateway, the first mobility management entity is configured to manage the first base station and the first gateway, and the second mobility management entity is configured to manage the a second base station and the second gateway.
  • MME Mobility Management Entity
  • a gateway may be connected to multiple base stations.
  • the first base station is a base station connected to the first gateway
  • the second base station is a second base station.
  • the base station, and the first gateway and the second gateway are not the same gateway.
  • the first gateway allocates a first IP address to the user equipment, and the user equipment uses the first IP address and the communication peer end.
  • TCP Transmission Control Protocol
  • the user equipment is switched from the first base station to the second base station, because the second gateway is not the same gateway as the first gateway, the first IP address does not belong to the management scope of the second gateway, so the second gateway needs to allocate a new user equipment. IP address, the user equipment establishes communication with the communication peer using the new IP address.
  • the IP address assigned by the second gateway to the user equipment is the second IP address.
  • the user equipment After obtaining the second IP address, the user equipment establishes a TCP connection with the communication peer by using the second IP address.
  • the TCP connection established by the user equipment with the communication peer is the first substream
  • the TCP connection established by the user equipment with the communication peer using the second IP address is the second substream.
  • the embodiment of the present invention is an example of an application scenario in which an MPTCP substream is established by using an MPTCP technology, and a system, an apparatus, and a method for mobility management are described.
  • the embodiment of the present invention provides a mobility management system 100.
  • the user equipment 1001, the first base station 1002, the second base station 1003, the first gateway 1004, the second gateway 1005, and the communication peer 1006 are first.
  • the base station 1002 is connected to the first gateway 1004, and the second base station 1003 is connected to the second gateway 1005.
  • the mobility management system 100 further includes a first mobility management entity 1007 and a second mobility management entity 1008, where the first mobility management entity 1007 is configured to manage the first base station 1002 and the first gateway 1004, and the second mobility The sex management entity 1008 is configured to manage the second base station 1003 and the second gateway 1005.
  • the user equipment 1001 is configured to establish a first MPTCP (Multi-Path Transmission Control Protocol) sub-flow with the communication peer 1006, where the first MPTCP sub-flow uses the first Internet interconnection for the user equipment 1001.
  • the protocol IP address is associated with the MPTCP substream established by the communication peer 1006.
  • the first IP address is the IP address assigned by the first gateway 1004 to the user equipment 1001.
  • the communication peer 1006 may be a server, a user terminal, or an MPTCP proxy and a server that support the MPTCP technology, and the first gateway and the second gateway may be a distributed local gateway.
  • the user equipment 1001 When the user equipment 1001 is switched by the first base station 1002 to the second base station 1003, the user equipment 1001 is further configured to acquire a second IP address when the second gateway 1005 and the first gateway 1004 are not the same gateway, and the second IP address is
  • the second gateway 1005 is a user equipment. 1001 assigned IP address.
  • the user equipment 1001 is further configured to establish a second MPTCP sub-flow with the communication peer 1006 after acquiring the second IP address, where the second MPTCP sub-flow is an MPTCP sub-flow established by the user equipment 1001 using the second IP address and the communication peer 1006. .
  • the communication peer 1006 is configured to cancel the first MPTCP substream after the second MPTCP substream is established.
  • the first gateway 1004 is further configured to release the first IP address after the first MPTCP subflow is revoked.
  • the first gateway 1004 releases the first IP address, that is, releases the binding between the first IP address and the user equipment 1001. After the first gateway 1004 releases the first IP address, the first IP address may be assigned to other user equipments.
  • the mobility management system in the prior art uniformly allocates an IP address to the user equipment through the data aggregation type anchor device in the mobile network architecture, and the anchor device has a huge pressure. Once the anchor device has a problem, the entire service network is affected. Normal operation causes the user equipment service to be interrupted.
  • the mobility management system provided by the embodiment of the present invention dynamically allocates an IP address to the user equipment by using the first gateway and the second gateway. When the user equipment is switched from the first gateway to the second gateway, the user equipment and the communication peer pass the MPTCP. The second MPMS substream is established by using the second IP address.
  • the user equipment Before the second MPTCP substream is established, the user equipment communicates with the communication peer through the first MPTCP substream, and after the second MPTCP subflow is established, the first MPTCP subflow. Thereby, normal communication between the user equipment and the base station is ensured, and business continuity between the user equipment and the communication peer end is ensured.
  • the user equipment 1001 is further configured to: after the first MPTCP sub-flow is revoked, release the first IP address, and send an indication message for releasing the first IP address to the first gateway 1004, so that the first gateway 1004 is receiving. After the user equipment 1001 sends an indication message for releasing the first IP address, the first IP address is released. Specifically, the user equipment 1001 may send an indication message for releasing the first IP address to the first gateway 1004 by using the first base station 1002 or the first mobility management entity 1007.
  • the user equipment 1001 releases the first IP address, that is, the first IP address is no longer occupied.
  • the first base station 1002 and the second base station 1003 are configured to establish a data forwarding tunnel, where the data forwarding tunnel is data between the first base station 1002 and the second base station 1003. Forwarding channel.
  • the user equipment 1001 and the communication peer 1006 are further configured to transmit data of the first MPTCP substream through a data forwarding tunnel.
  • the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or the data forwarding tunnel includes a downlink data forwarding tunnel and an uplink data forwarding tunnel.
  • the second base station 1003 is further configured to delete the data forwarding tunnel after the first MPTCP subflow is revoked.
  • the second gateway 1005 is not the same gateway as the first gateway 1004, the second IP address is obtained, including:
  • the gateway identifier may be a local network (Local Network) ID, or the gateway identifier may also be a local gateway (Local Gateway) ID.
  • the second gateway identifier sent by the second base station 1003 is received.
  • the user equipment 1001 sends a request message for obtaining an IP address to the second gateway 1005, and receives a second IP address sent by the second gateway 1005.
  • the second gateway 1005 is not the same gateway as the first gateway 1004, the second IP address is obtained, including:
  • the user equipment 1001 When the user equipment 1001 is handed over by the first base station 1002 to the second base station 1003, the user equipment 1001 transmits the first IP address or the first gateway identifier to the second mobility management entity 1008.
  • the second mobility management entity 1008 determines whether the first IP address is an IP address assigned by the second gateway 1005 to the user equipment 1001, or whether the first gateway identifier is the same as the second gateway identifier.
  • the second mobility management entity 1008 requests the second gateway 1005 to allocate the user equipment 1001. IP address and will The second IP address received from the second gateway 1005 is sent to the user equipment 1001. Further optionally, when the first gateway 1004 and the second gateway 1005 are managed by the same mobility management entity, the first mobility management entity 1007 and the second mobility management entity 1008 may be the same mobility management entity.
  • the second gateway 1005 is not the same gateway as the first gateway 1004, the second IP address is obtained, including:
  • the user equipment 1001 When the user equipment 1001 is handed over by the first base station 1002 to the second base station 1003, the user equipment 1001 transmits the second gateway identifier to the first base station 1002.
  • the first base station 1002 sends a determination indication message to the user equipment 1001, where the determination indication message is used to indicate that the second gateway 1005 and the first gateway 1004 are not the same gateway.
  • the user equipment 1001 After receiving the determination indication message, the user equipment 1001 sends a request message for obtaining an IP address to the second gateway 1005, and receives a second IP address sent by the second gateway 1005.
  • the user equipment 1001 is further configured to send a location update request message to the second mobility management entity 1008 when the user equipment 1001 is switched by the first base station 1002 to the second base station 1003 in an idle state.
  • the second mobility management entity 1008 is configured to send a location update confirmation message to the user equipment.
  • the user equipment 1001 when the user equipment 1001 moves from the first base station to the second base station in an idle state, after the second base station 1003 is connected to complete the location update, the user equipment 1001 enters an idle state.
  • the first mobility management entity 1006 is further configured to receive the downlink data notification of the user equipment 1001 sent by the first gateway 1004 after the user equipment 1001 enters the idle state.
  • the first mobility management entity 1006 is further configured to receive the downlink data notification of the user equipment 1001 from the first gateway 1004, and page the user equipment 1001 after receiving the downlink data notification of the user equipment 1001.
  • the user equipment 1001 is further configured to respond to the paging of the first mobility management entity 1006.
  • the first gateway 1004 is further configured to cache downlink data.
  • the first mobility management entity 1006 is further configured to: after the user equipment 1001 responds to the paging, request downlink data from the first gateway 1004, receive downlink data sent by the first gateway 1004, and send downlink data received from the first gateway 1004. To the user equipment 1001.
  • the first mobility management entity 1006 is further configured to establish a downlink data forwarding tunnel after the user equipment 1001 responds to the paging;
  • the first gateway 1004 is further configured to send downlink data to the user equipment 1001 by using a downlink data forwarding tunnel.
  • the user equipment 1001 when the user equipment 1001 moves from the first base station to the second base station in an idle state, after the second base station 1003 is connected to complete the location update, the user equipment 1001 enters an idle state.
  • the second mobility management entity 1007 is further configured to register the downlink data notification of the user equipment 1001 with the first mobility management entity 1006.
  • the first gateway 1004 is further configured to send the downlink data notification of the user equipment 1001 to the first mobility management entity 1006 after the user equipment 1001 enters the idle state.
  • the first mobility management entity 1006 is further configured to send the downlink data notification of the user equipment 1001 to the second mobility management entity 1007 after confirming the registration of the first mobility management entity 1006.
  • the second mobility management entity 1007 is further configured to page the user equipment 1001 after receiving the downlink data notification of the user equipment 1001.
  • the user equipment 1001 is further configured to respond to the paging of the second mobility management entity 1007.
  • the second mobility management entity 1007 is further configured to request downlink data by using the first mobility management entity 1006 after the user equipment 1001 responds to the paging.
  • the first mobility management entity 1006 is further configured to forward the downlink data sent by the first gateway 1004 to the second mobility management entity 1007.
  • the second mobility management entity 1007 is further configured to send downlink data to the user equipment 1001.
  • the second mobility management entity 1007 is further configured to establish a downlink data forwarding tunnel by using the first mobility management entity 1006 after the user equipment 1001 responds to the paging.
  • the first gateway 1004 is further configured to send downlink data to the user equipment 1001 by using a downlink data forwarding tunnel.
  • the downlink data forwarding tunnel may be a data forwarding tunnel between the first gateway 1004 and the second gateway 1005.
  • the first gateway 1004 sends the downlink data to the second gateway 1005 through the downlink data forwarding tunnel.
  • the downlink data is transmitted to the user equipment 1001 through the second base station 1003.
  • the downlink data forwarding tunnel may be a data forwarding tunnel between the first gateway 1004 and the second base station 1003.
  • the first gateway 1004 transmits the downlink data to the second base station 1003 through the data forwarding tunnel, and the second base station 1003
  • the downlink data is transmitted to the user equipment 1001.
  • the mobility management system 100 further includes an online charging system (OCS) 1009 and a Policy Control and Charging Rule Function (PCRF) 1010.
  • OCS online charging system
  • PCRF Policy Control and Charging Rule Function
  • the first mobility management entity 1006 is further configured to acquire the available quota of the user equipment 1001 from the line charging system 1009, and send the available quota of the user equipment 1001 to the first gateway 1004.
  • the first mobility management entity 1006 is further configured to acquire the charging rule of the user equipment 1001 from the policy and charging rule function 1010, and send the charging rule of the user equipment 1001 to the first gateway 1004.
  • the first gateway 1004 is further configured to deduct the available quota of the user equipment 1001 according to the charging rule of the user equipment 1001, and send the available credit balance of the user equipment 1001 to the online charging system 1009.
  • the mobility management system 100 further includes an Off-Line Charging System (OFCS) 1011.
  • OFCS Off-Line Charging System
  • the first gateway 1004 is further configured to send the CDR of the user equipment 1001 at the first gateway 1004 to the first mobility management entity 1006.
  • the first mobility management entity 1006 is further configured to send the CDR of the user equipment 1001 at the first gateway 1004 to the offline charging system 1011.
  • the mobility management system provided by the embodiment of the present invention dynamically allocates an IP address to the user equipment through the first gateway and the second gateway.
  • the data aggregation type anchor device in the mobile network architecture uniformly allocates an IP address to the user equipment, and the anchor device pressure is huge. Once there is a problem with the anchor device, it will affect the normal operation of the entire service network and cause the user equipment service to be interrupted.
  • the mobility management system provided by the embodiment of the present invention when the user equipment is switched from the first gateway to the second gateway, the user equipment and the communication peer establish a second MPTCP substream by using the second IP address through the MPTCP technology.
  • the user equipment Before the establishment of the second MPTCP substream, the user equipment communicates with the communication peer through the first MPTCP substream, and after the second MPTCP substream is established, the first MPTCP substream is revoked. Thereby, normal communication between the user equipment and the base station is ensured, and business continuity between the user equipment and the communication peer end is ensured.
  • An embodiment of the present invention provides a user equipment 20, which is shown in FIG. 2, and includes a processor 2001, a memory 2002, and a bus 2003.
  • the processor 2001 and the memory 2002 are connected to each other through a bus 2003.
  • the user equipment 20 further includes a receiver 2004 and a transmitter 2005.
  • the receiver 2004 and the transmitter 2005 are interconnected with the processor 2001 and the memory 2002 via a bus 2003.
  • the bus 2003 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component) bus, or an EISA (Extended Industry Standard Architecture) bus.
  • the bus 2003 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 2, but it does not mean that there is only one bus or one type of bus. among them:
  • the memory 2002 is used to execute the application code of the inventive scheme, and the application code for executing the inventive scheme is stored in a memory and controlled by the processor 2001 for execution.
  • the memory can be a read only memory ROM or other type of static storage device that can store static information and instructions, a random access memory RAM or other type of dynamic storage device that can store information and instructions, or can be electrically erasable or programmable.
  • These memories are connected to the processor via a bus.
  • the processor 2001 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more configured to implement the embodiments of the present invention. Integrated circuits.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the processor 2001 is configured to call the program code in the memory 2002. In a possible implementation manner, when the application program is executed by the processor 2001, the following functions are implemented.
  • the processor 2001 is configured to establish a first multi-path transmission control protocol MPTCP sub-flow with the communication peer, where the first MPTCP sub-flow is an MPTCP sub-flow established by the user equipment 20 using the first Internet Protocol IP address and the communication peer.
  • the first IP address is an Internet Protocol (IP) IP address assigned by the first gateway to the user equipment 20, and the first gateway is connected to the first base station.
  • IP Internet Protocol
  • the processor 2001 is further configured to obtain a second IP address, where the second IP address is an IP address allocated by the second gateway to the user equipment 20.
  • the processor 2001 is further configured to establish a second MPTCP substream with the communication peer, where the second MPTCP substream is an MPTCP substream established by the user equipment 20 using the second IP address and the communication peer.
  • the processor 2001 is further configured to cancel the first MPTCP substream.
  • the user equipment provided by the embodiment of the present invention acquires an IP address when the first gateway switches to the second gateway, and establishes a second MPTCP substream by using the second IP address with the communication peer through the MPTCP technology, in the second MPTCP sub- Before the flow is established, the user equipment communicates with the communication peer through the first MPTCP substream, and after the second MPTCP subflow is established, the first MPTCP subflow is revoked. Thereby, normal communication between the user equipment and the base station is ensured, and business continuity between the user equipment and the communication peer end is ensured.
  • the processor 2001 is further configured to: after the first MPTCP substream is revoked, release the first IP address, and generate an indication message for releasing the first IP address, where the indication message for releasing the first IP address is used to indicate A gateway releases the first IP address.
  • the transmitter 2005 is configured to send, to the first gateway, an indication for releasing the first IP address. interest. Specifically, the transmitter 2005 may send, by using the first base station or the first mobility management entity, an indication message for releasing the first IP address to the first gateway.
  • the processor 2001 is further configured to transmit data of the first MPTCP substream by using a data forwarding tunnel, where the data forwarding tunnel is a data forwarding channel between the first base station and the second base station.
  • the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or the data forwarding tunnel includes a downlink data forwarding tunnel and an uplink data forwarding tunnel.
  • the processor 2001 is further configured to release the first IP address.
  • the processor 2001 is further configured to generate an indication message indicating that the first MPTCP subflow has been revoked.
  • the transmitter 2005 is further configured to send, to the second base station, an indication message indicating that the first MPTCP sub-flow has been revoked, so that the second base station deletes the data forwarding tunnel.
  • the receiver 2004 is configured to receive a first gateway identifier sent by the first base station, where the first gateway identifier is used to indicate the first gateway.
  • the receiver 2004 is further configured to receive a second gateway identifier sent by the second base station, where the second gateway identifier is used to indicate the second gateway.
  • the processor 2001 is further configured to determine whether the second gateway identifier is the same as the first gateway identifier, and if the second gateway identifier is different from the first gateway identifier, generate a request message for obtaining an IP address.
  • the transmitter 2005 is configured to send a request message for obtaining an IP address to the second gateway.
  • the receiver 2004 is further configured to receive a second IP address sent by the second gateway.
  • the transmitter 2005 is further configured to: when the user equipment 20 is switched by the first base station to the second base station, send the first IP address or the first gateway identifier to the second mobility management entity, so as to facilitate the second mobility.
  • the sex management entity determines whether the second gateway and the first gateway are the same gateway according to the first IP address or the first gateway identifier, and requests the user equipment 20 to allocate an IP address to the second gateway when the second gateway is not the same gateway as the first gateway.
  • the address, the second IP address received from the second gateway is sent to the user equipment 20, and the second mobility management entity is configured to manage the second base station and the second gateway.
  • the receiver 2004 is further configured to receive a second IP address sent by the second mobility management entity.
  • the transmitter 2005 is further configured to: when the user equipment 20 is switched by the first base station to the second base station, send the second gateway identifier to the first base station, so that the first base station determines the second gateway and the first gateway. Whether it is the same gateway.
  • the receiver 2004 is further configured to receive a determination indication message sent by the first base station, where the determination indication message is used to indicate that the second gateway is not the same gateway as the first gateway.
  • the processor 2001 is further configured to generate a request message for obtaining an IP address.
  • the transmitter 2005 is further configured to send a request message for obtaining an IP address to the second gateway.
  • the receiver 2004 is further configured to receive a second IP address sent by the second gateway.
  • the processor 2001 is further configured to generate a location update request message when the user equipment 20 moves from the first base station to the second base station in an idle state.
  • the transmitter 2005 is further configured to send a location update request message to the second mobility management entity, where the second mobility management entity is configured to manage the second base station and the second gateway.
  • the receiver 2004 is further configured to receive a location update confirmation message sent by the second mobility management entity.
  • the processor 2001 is further configured to control the user equipment 20 to enter an idle state.
  • the receiver 2004 is further configured to receive a paging of the first mobility management entity when the user equipment 20 is in an idle state, where the first mobility management entity is configured to manage the first base station and the first gateway.
  • the processor 2001 is further configured to generate a paging response message.
  • the transmitter 2005 is further configured to send a paging response message to the first mobility management entity.
  • the receiver 2004 is further configured to receive downlink data that is buffered and forwarded by the first gateway.
  • the receiver 2004 is further configured to receive a paging of the second mobility management entity when the user equipment 20 is in an idle state, where the first mobility management entity is configured to manage the first base station and the first gateway.
  • the transmitter 2005 is further configured to send a paging response message to the second mobility management entity.
  • the transmitter 2005 is further configured to receive downlink data.
  • the user equipment provided by the embodiment of the present invention acquires an IP address when the first gateway switches to the second gateway, and establishes a second MPTCP substream by using the second IP address with the communication peer through the MPTCP technology, in the second MPTCP sub- Before the flow is established, the user equipment communicates with the communication peer through the first MPTCP substream, and after the second MPTCP subflow is established, the first MPTCP subflow is revoked. Thereby, normal communication between the user equipment and the base station is ensured, and business continuity between the user equipment and the communication peer end is ensured.
  • the embodiment of the present invention provides a first base station 30.
  • the processor 3001 includes a processor 3001, a memory 3002, and a bus 3003.
  • the processor 3001, the memory 3002, the receiver 3004, and the transmitter 3005 are connected to each other through a bus 3003.
  • the bus 3003 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component) bus, or an EISA (Extended Industry Standard Architecture) bus.
  • the bus 3003 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 2, but it does not mean that there is only one bus or one type of bus. among them:
  • the memory 3002 is for executing application code of the inventive scheme, and the application code for executing the inventive scheme is stored in a memory and controlled by the processor 3001 for execution.
  • the memory can be a read only memory ROM or other type of static storage device that can store static information and instructions, a random access memory RAM or other type of dynamic storage device that can store information and instructions, or can be electrically erasable or programmable.
  • These memories are connected to the processor via a bus.
  • the processor 3001 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more configured to implement the embodiments of the present invention. Integrated circuits.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the processor 3001 is configured to call the program code in the memory 3002. In a possible implementation manner, when the application program is executed by the processor 3001, the following functions are implemented.
  • the processor 3001 is configured to: when the user equipment is switched by the first base station 30 to the second base station, generate a data forwarding tunnel establishment request message, where the second MPTCP sub-flow is before the second multi-path transmission control protocol MPTCP sub-flow is established.
  • the user equipment uses the second Internet Protocol IP address to establish an MPTCP sub-flow with the communication peer, the second IP address is the IP address assigned by the second gateway to the user equipment, the second gateway is connected to the second base station, and the data forwarding tunnel is the first a data forwarding channel between the base station 30 and the second base station, the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or the data forwarding tunnel includes a downlink data forwarding tunnel and an uplink data forwarding tunnel, and the data forwarding channel is used for transmitting Data of an MPTCP substream, the first MPTCP substream is an MPTCP substream established by the user equipment using the first IP address and the communication peer before the user equipment switches from the first base station 30 to the second base station, and the first IP address is the first The gateway allocates an IP address to the user equipment, and the first gateway is connected to the first base station 30.
  • the transmitter 3005 is configured to send a data forwarding tunnel setup request message to the second base station.
  • the receiver 3004 is configured to receive a setup confirmation message of the data forwarding tunnel sent by the second base station.
  • the receiver 3004 is further configured to receive a delete request message of the data forwarding tunnel sent by the second base station.
  • the transmitter 3005 is further configured to send a deletion confirmation message of the data forwarding tunnel to the second base station.
  • the processor 3001 is further configured to release the data forwarding tunnel and generate a first IP release indication message.
  • the transmitter 3005 is further configured to send a first IP release indication message to the first gateway.
  • the receiver 3004 is further configured to receive the second gateway identifier sent by the user equipment.
  • the processor 3001 is further configured to determine, according to the second gateway identifier, whether the second gateway is the same gateway as the first gateway, and when the second gateway is not the same gateway as the first gateway, generate a determination indication message, where the determination indication message is used to indicate The second gateway is not the same gateway as the first gateway.
  • the transmitter 3005 is further configured to send a judgment indication message to the user equipment, so that the user equipment sends a request message for obtaining an IP address to the second gateway, and receives a second IP address sent by the second gateway.
  • the first base station provided by the embodiment of the present invention determines that the first gateway and the second gateway are not the same gateway when the user equipment is switched from the first gateway to the second gateway, and is established before the second MPTCP subflow is established.
  • the data forwarding tunnel of the second base station is used to transmit data of the first MPTCP substream, thereby ensuring normal communication between the user equipment and the base station, and ensuring service continuity between the user equipment and the communication peer end.
  • the processor 4001 includes a processor 4001, a memory 4002, and a bus 4003.
  • the processor 4001, the memory 4002, the receiver 4004, and the transmitter 4005 are connected to each other through a bus 4003.
  • the bus 4003 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component) bus, or an EISA (Extended Industry Standard Architecture) bus.
  • the bus 4003 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 2, but it does not mean that there is only one bus or one type of bus. among them:
  • the memory 4002 is for executing application code of the inventive scheme, and the application code for executing the inventive scheme is stored in a memory and controlled by the processor 4001 for execution.
  • the memory can be a read only memory ROM or other type of static storage device that can store static information and instructions, a random access memory RAM or can store information. And other types of dynamic storage devices, and may also be electrically erasable programmable read only memory EEPROM, CD-ROM or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc., disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto. These memories are connected to the processor via a bus.
  • the processor 4001 may be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more configured to implement the embodiments of the present invention. Integrated circuits.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the processor 4001 is configured to call the program code in the memory 4002. In a possible implementation manner, when the application program is executed by the processor 4001, the following functions are implemented.
  • the receiver 4004 is configured to: when the user equipment is switched by the first base station to the second base station 40, receive a data forwarding tunnel establishment request message sent by the first base station, before the second multipath transmission control protocol MPTCP subflow is established, where
  • the second MPTCP substream is an MPTCP substream established by the user equipment using the second internet protocol IP address and the communication peer end, the second IP address is an IP address assigned by the second gateway to the user equipment, and the second gateway is connected to the second base station 40.
  • the data forwarding tunnel is a data forwarding channel between the first base station and the second base station 40.
  • the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or the data forwarding tunnel includes a downlink data forwarding tunnel and an uplink data forwarding tunnel.
  • the forwarding channel is configured to transmit data of the first MPTCP substream, where the first MPTCP substream is an MPTCP substream established by the user equipment using the first IP address and the communication peer before being switched by the first base station to the second base station 40.
  • An IP address is an IP address assigned by the first gateway to the user equipment, and the first gateway is connected to the first base station.
  • the processor 4001 is configured to generate a setup confirmation message of the data forwarding tunnel.
  • the transmitter 4005 is configured to send a setup confirmation message of the data forwarding tunnel to the first base station.
  • the processor 4001 is further configured to generate data forwarding after the first MPTCP substream is revoked. Tunnel delete request message.
  • the transmitter 4005 is further configured to send a delete request message of the data forwarding tunnel to the first base station.
  • the receiver 4004 is further configured to receive a deletion confirmation message of the data forwarding tunnel sent by the first base station.
  • the processor 4001 is further configured to release a data forwarding tunnel.
  • the second base station provided by the embodiment of the present invention, when the user equipment is switched from the first gateway to the second gateway, establishes a data forwarding tunnel with the first base station for transmitting the first MPTCP before the second MPTCP substream is established.
  • the data of the substream ensures normal communication between the user equipment and the base station, and ensures business continuity between the user equipment and the communication peer.
  • Another embodiment of the present invention provides another user equipment 50.
  • the multi-path control unit 501 and the transceiver unit 502 are included.
  • the multipath control unit 501 is configured to establish a first multipath transmission control protocol MPTCP subflow with the communication peer when the user equipment 50 is connected to the first base station, where the first MPTCP substream uses the first internet interconnection for the user equipment 50.
  • the protocol IP address is associated with the MPTCP sub-flow established by the communication peer.
  • the first Internet Protocol IP address is the IP address assigned by the first gateway to the user equipment 50, and the first gateway is connected to the first base station.
  • the transceiver unit 502 is configured to obtain a second IP address, where the second IP address is an IP address allocated by the second gateway to the user equipment 50.
  • the multi-path control unit 501 is further configured to establish a second MPTCP sub-flow with the communication peer, where the second MPTCP sub-flow is an MPTCP sub-flow established by the user equipment 50 with the second IP address and the communication peer.
  • the multipath control unit 501 is further configured to cancel the first MPTCP substream after the second MPTCP substream is established.
  • the multi-path control unit 501 is further configured to: after the first sub-flow is revoked, release the first IP address, and generate an indication message for releasing the first IP address, where the indication message for releasing the first IP address is used for Instructing the first gateway to release the first IP address.
  • the transceiver unit 502 is further configured to send, to the first gateway, an indication for releasing the first IP address. Message.
  • the transceiver unit 502 is further configured to transmit data of the first MPTCP substream by using a data forwarding tunnel, where the data forwarding tunnel is a data forwarding channel between the first base station and the second base station.
  • the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or the data forwarding tunnel includes a downlink data forwarding tunnel and an uplink data forwarding tunnel.
  • the multi-path control unit 501 is further configured to release the first IP address.
  • the multipath control unit 501 is further configured to generate an indication message that the first MPTCP subflow has been revoked.
  • the transceiver unit 502 is further configured to send, to the second base station, an indication message that the first MPTCP sub-flow has been revoked, so that the second base station deletes the data forwarding tunnel.
  • the transceiver unit 502 is further configured to: when the user equipment 50 is connected to the first base station, receive the first gateway identifier sent by the first base station.
  • the transceiver unit 502 is further configured to receive the second gateway identifier sent by the second base station when the user equipment 50 is switched by the first base station to the second base station.
  • the multi-path control unit 501 is further configured to determine whether the second gateway identifier is the same as the first gateway identifier, and if the second gateway identifier is different from the first gateway identifier, generate a request message for obtaining an IP address.
  • the transceiver unit 502 is further configured to send a request message for obtaining an IP address to the second gateway.
  • the transceiver unit 502 is further configured to receive a second IP address sent by the second gateway.
  • the transceiver unit 502 is further configured to: when the user equipment 50 is switched by the first base station to the second base station, send the first IP address or the first gateway identifier to the second mobility management entity, so as to facilitate the second mobility.
  • the sex management entity determines whether the second gateway and the first gateway are the same gateway according to the first IP address or the first gateway identifier, and requests the user equipment 50 to allocate an IP address to the second gateway when the second gateway is not the same gateway as the first gateway.
  • the address, the second IP address received from the second gateway is sent to the user equipment 50, and the second mobility management entity is configured to manage the second base station and the second gateway.
  • the transceiver unit 502 is further configured to receive a second IP address sent by the second mobility management entity.
  • the transceiver unit 502 is further configured to: when the user equipment 50 is switched by the first base station to the second base station, send the second gateway identifier to the first base station, so that the first base station determines the second gateway and the first gateway. Whether it is the same gateway.
  • the transceiver unit 502 is further configured to receive a determination indication message sent by the first base station, where the determination indication message is used to indicate that the second gateway is not the same gateway as the first gateway.
  • the multipath control unit 501 is further configured to generate a request message for obtaining an IP address.
  • the transceiver unit 502 is further configured to send a request message for obtaining an IP address to the second gateway.
  • the transceiver unit 502 is further configured to receive a second IP address sent by the second gateway.
  • the user equipment 50 further includes a handover control unit 503, configured to generate a location update request message when the user equipment 50 moves from the first base station to the second base station in an idle state.
  • a handover control unit 503 configured to generate a location update request message when the user equipment 50 moves from the first base station to the second base station in an idle state.
  • the transceiver unit 502 is further configured to send a location update request message to the second mobility management entity.
  • the transceiver unit 502 is further configured to receive a location update confirmation message sent by the second mobility management entity, where the second mobility management entity is configured to manage the second base station and the second gateway.
  • the multi-path control unit 501 is further configured to control the user equipment 50 to enter an idle state.
  • the transceiver unit 502 is further configured to receive a paging of the first mobility management entity when the user equipment 50 is in an idle state, where the first mobility management entity is configured to manage the first base station and the first gateway.
  • the handover control unit 503 is further configured to respond to the paging of the first mobility management entity.
  • the transceiver unit 502 is further configured to receive downlink data that is buffered and forwarded by the first gateway.
  • the transceiver unit 502 is further configured to receive a paging of the second mobility management entity when the user equipment 50 is in an idle state, where the first mobility management entity is configured to manage the first base station and the first gateway.
  • the handover control unit 503 is further configured to respond to the paging of the second mobility management entity.
  • the transceiver unit 502 is further configured to receive downlink data.
  • the user equipment provided by the embodiment of the present invention acquires an IP address when the first gateway switches to the second gateway, and establishes a second MPTCP substream by using the second IP address with the communication peer through the MPTCP technology, in the second MPTCP sub- Before the flow is established, the user equipment communicates with the communication peer through the first MPTCP substream, and after the second MPTCP subflow is established, the first MPTCP subflow is revoked. Thereby, normal communication between the user equipment and the base station is ensured, and business continuity between the user equipment and the communication peer end is ensured.
  • An embodiment of the present invention provides another first base station 60. Referring to FIG. 6, the control unit 601, the sending unit 602, and the receiving unit 603 are provided.
  • the control unit 601 is configured to: when the user equipment is switched by the first base station 60 to the second base station, generate a data forwarding tunnel establishment request message, where the second MPTCP sub-flow is before the second multi-path transmission control protocol MPTCP sub-flow is established.
  • the user equipment uses the second Internet Protocol IP address to establish an MPTCP sub-flow with the communication peer, the second IP address is the IP address assigned by the second gateway to the user equipment, the second gateway is connected to the second base station, and the data forwarding tunnel is the first a data forwarding channel between the base station 60 and the second base station, the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or the data forwarding tunnel includes a downlink data forwarding tunnel and an uplink data forwarding tunnel, and the data forwarding channel is used for transmission.
  • the first MPTCP substream is an MPTCP substream established by the user equipment using the first IP address and the communication peer before the user equipment switches from the first base station 60 to the second base station, and the first IP address is the first
  • the gateway allocates an IP address to the user equipment, and the first gateway is connected to the first base station 60.
  • the sending unit 602 is configured to send, by the second base station, a data forwarding tunnel setup request message.
  • the receiving unit 603 is configured to receive a setup confirmation message of the data forwarding tunnel sent by the second base station.
  • the receiving unit 603 is further configured to receive a delete request message of the data forwarding tunnel sent by the second base station.
  • the control unit 601 is further configured to generate a deletion confirmation message of the data forwarding tunnel.
  • the sending unit 602 is further configured to send a deletion confirmation message of the data forwarding tunnel to the second base station.
  • the control unit 601 is further configured to release the data forwarding tunnel and generate a first IP release indication message.
  • the sending unit 602 is further configured to send a first IP release indication message to the first gateway.
  • the receiving unit 603 is further configured to receive the second gateway identifier sent by the user equipment.
  • the control unit 601 is further configured to determine, according to the second gateway identifier, whether the second gateway is the same gateway as the first gateway, and generate a determination indication message when the second gateway is not the same gateway as the first gateway, and the determining indication message is used to indicate The second gateway is not the same gateway as the first gateway.
  • the sending unit 602 is further configured to send a judgment indication message to the user equipment, so that the user equipment sends a request message for obtaining an IP address to the second gateway, and receives a second IP address sent by the second gateway.
  • the first base station provided by the embodiment of the present invention determines that the first gateway and the second gateway are not the same gateway when the user equipment is switched from the first gateway to the second gateway, and is established before the second MPTCP subflow is established.
  • the data forwarding tunnel of the second base station is used to transmit data of the first MPTCP substream, thereby ensuring normal communication between the user equipment and the base station, and ensuring service continuity between the user equipment and the communication peer end.
  • An embodiment of the present invention provides another second base station 70, including a control unit 701, a sending unit 702, and a receiving unit 703.
  • the receiving unit 703 is configured to: when the user equipment is switched by the first base station to the second base station 70, receive a data forwarding tunnel setup request message sent by the first base station, before the second multipath transmission control protocol MPTCP subflow is established, where
  • the second MPTCP substream is an MPTCP substream established by the user equipment using the second internet protocol IP address and the communication peer end, the second IP address is an IP address assigned by the second gateway to the user equipment, and the second gateway is connected to the second base station 70.
  • the data forwarding tunnel is a data forwarding channel between the first base station and the second base station 70, and the data forwarding tunnel includes a downlink data forwarding tunnel or an uplink data forwarding tunnel, or the data forwarding tunnel includes a downlink data forwarding tunnel and uplink data.
  • the data forwarding channel is configured to transmit data of the first MPTCP substream
  • the first MPTCP substream is an MPTCP established by the user equipment using the first IP address and the communication peer before being switched by the first base station to the second base station 70.
  • the sub-flow, the first IP address is an IP address assigned by the first gateway to the user equipment, and the first gateway is connected to the first base station.
  • the control unit 701 is configured to generate a setup confirmation message of the data forwarding tunnel.
  • the sending unit 702 is configured to send a setup confirmation message of the data forwarding tunnel to the first base station.
  • the control unit 701 is further configured to generate a delete request message of the data forwarding tunnel after the first MPTCP substream is revoked.
  • the sending unit 702 is further configured to send a delete request message of the data forwarding tunnel to the first base station.
  • the receiving unit 703 is further configured to receive a deletion confirmation message of the data forwarding tunnel sent by the first base station.
  • the control unit 701 is further configured to release the data forwarding tunnel.
  • the second base station provided by the embodiment of the present invention, when the user equipment is switched from the first gateway to the second gateway, establishes a data forwarding tunnel with the first base station for transmitting the first MPTCP before the second MPTCP substream is established.
  • the data of the substream ensures normal communication between the user equipment and the base station, and ensures business continuity between the user equipment and the communication peer.
  • an embodiment of the present invention provides a mobility management method applied to a mobility management system in a cellular network.
  • the mobility management system includes a user equipment, a first base station, a second base station, a first gateway, a second gateway, and a communication peer.
  • the first base station is connected to the first gateway, and the second base station is connected to the second gateway.
  • TCP Transmission Control Protocol
  • the second gateway When the user equipment is switched from the first base station to the second base station, because the second gateway does not manage the IP address assigned by the first gateway, the user equipment cannot establish the IP address assigned by the first gateway through the second gateway and the communication peer. TCP connection, so the second gateway assigns a new IP address to the user equipment. In order for the user equipment to establish a TCP connection with the communication peer using the new IP address.
  • the new IP address assigned by the second gateway to the user equipment is the second IP address.
  • the TCP connection established by the user equipment with the communication peer is the first substream
  • the TCP connection established by the user equipment with the communication peer using the second IP address is the second substream.
  • an application scenario of establishing an MPTCP substream by using a Multi-Path Transmission Control Protocol is taken as an example to describe a mobility management method.
  • MPTCP Multi-Path Transmission Control Protocol
  • the mobility management method provided by the present invention is also applicable to an application scenario in which a sub-flow is established by using other technical means, for example, a sub-flow is established by using a Multi-Path Real-time Transport Protocol (MPRTP) technology.
  • MPRTP Multi-Path Real-time Transport Protocol
  • the present invention does not limit the specific technical means for establishing a substream.
  • the mobility management method provided by the embodiment of the present invention includes the following steps:
  • the user equipment establishes a first substream with the communication peer.
  • the first sub-flow may be a first MPTCP (Multi-Path Transmission Control Protocol) sub-stream
  • the first MPTCP sub-flow uses the first Internet Protocol IP address and the communication pair for the user equipment.
  • the MPTCP substream established by the end.
  • the first IP (Internet Protocol) address is an IP address assigned by the first gateway to the user equipment.
  • the MPTCP layer is added between the socket (socket) and TCP layers of the TCP (Transmission Control Protocol)/IP (Internet Protocol) protocol stack architecture, and the MPTCP layer is used.
  • the communication parties can use different IP address pairs to establish a TCP sub-flow connection, and each TCP sub-flow is an MPTCP sub-flow.
  • the mobility management method provided by the present invention is described by taking an LTE (Long Term Evolution) wireless cellular network as an example.
  • the user equipment and the communication peer end may be a user terminal, a server, or an MPTCP proxy and a server that support the MPTCP technology, and the first gateway and the second gateway are distributed local gateways.
  • the user equipment After accessing the first base station, the user equipment acquires the first IP address from the first gateway, and uses the first IP address to establish a first MPTCP substream with the communication peer through the MPTCP technology.
  • the user equipment obtains the first IP address in two ways.
  • the first The user equipment sends a DHCP (Dynamic Host Configuration Protocol) message to the first gateway to request an IP address from the first gateway, and the first gateway sends the first IP address to the user equipment by using a DHCP message.
  • the user equipment sends a NAS (Non Access Stratum) message requesting IP address to the first mobility management entity, and the first mobility management entity allocates the first gateway to the user equipment by using the NAS message.
  • An IP address is sent to the user equipment.
  • the first MPTCP substream is established with the communication peer through the MPTCP technology.
  • the user equipment sends a request for establishing a first MPTCP substream to the communication peer end, and after receiving the request for establishing the first MPTCP substream, the communication peer end returns an acknowledgement message to the user equipment, and after receiving the acknowledgement message, the user equipment receives the acknowledgement message.
  • the acknowledgment message of the first MPTCP substream establishment is sent to the communication terminal, whereby the establishment of the first MPTCP substream is completed.
  • the user equipment When the user equipment is switched from the first base station to the second base station, when the second gateway is not the same gateway as the first gateway, the user equipment acquires the second IP address.
  • the second IP address is an IP address assigned by the second gateway to the user equipment. If the second gateway is not the same gateway as the first gateway, the user equipment needs to acquire a new IP address from the second gateway in the process of the first base station switching to the second base station. After the handover is completed, the second IP address assigned by the second gateway is used to communicate with the communication peer.
  • the user equipment is in an idle state before being switched by the first base station to the second base station.
  • the user equipment moves from the first base station to the second base station in an idle state, there may be two ways to obtain the second IP address.
  • the first gateway identifier sent by the first base station is received, where the first gateway identifier is used to indicate the first gateway.
  • a second gateway identifier where the second gateway identifier is used to indicate the second gateway, when the user equipment moves from the first base station to the second base station and is connected to the second base station.
  • the user equipment determines the second gateway identifier and the first gateway identifier. If the second gateway identifier is different from the first gateway identifier, the user equipment sends a request message for obtaining the IP address to the second gateway, and the second gateway determines whether the message is based on the context record.
  • the user device has been assigned an IP address if it has been assigned to the user device. If the IP address is used, the user equipment is denied the request for obtaining the new IP address, and the user equipment is instructed to use the IP address assigned by the second gateway to the user equipment. If the second gateway does not assign the IP address to the user equipment, the second gateway sends the user equipment to the user equipment. The second IP address, the user equipment receives the second IP address sent by the second gateway, that is, the process of obtaining the second IP address is completed.
  • the first base station and the second base station may send the respective gateway identifiers to the user equipment by using a broadcast.
  • the gateway identifier may be a local network (Local Network) ID, or the gateway identifier may also be a local gateway (Local Gateway) ID.
  • the request message for obtaining an IP address may be a DHCP request.
  • the location update (TAU) request message is sent to the second mobility management entity, and the first The IP address or first gateway identity is sent to the second mobility management entity.
  • the second mobility management entity determines whether the first IP address is an IP address assigned by the second gateway to the user equipment, or whether the first gateway identifier is the same as the second gateway identifier. If the first IP address is not the IP address assigned by the second gateway to the user equipment, or the first gateway identifier is different from the second gateway identifier, the second mobility management entity determines that the first gateway and the second gateway are not the same gateway.
  • the second mobility management entity determines that the first gateway and the second gateway are not the same gateway, it is determined according to the context record whether the second gateway has assigned an IP address to the user equipment, and if the second gateway has already assigned an IP address to the user equipment, The second mobility management entity rejects the request of the user equipment to acquire the new IP address, and indicates that the user equipment uses the IP address that the second gateway has allocated for the user equipment, and if the second gateway does not allocate the IP address for the user equipment, the second mobility The management entity requests the user equipment to allocate an IP address to the second gateway, and sends the second IP address received from the second gateway to the user equipment.
  • the second mobility management entity may send the second IP address to the user equipment by using the NAS message.
  • the second mobility management entity includes the second IP address in the location update acknowledgement (TAU Accept) message.
  • TAU Accept Sending to the user equipment, the user equipment receives the second IP address sent by the second mobility management entity, that is, completes the acquisition process of the second IP address.
  • the first gateway and the second gateway may be entered by the same mobility management entity Row management, at this time, the first mobility management entity and the second mobility management entity may be the same mobility management entity.
  • the user equipment may be instructed to request an IP address from the second gateway to complete the second IP address acquisition process.
  • the first gateway and the second gateway are connected to the same mobility management entity
  • the first mobility management entity and the second mobility management entity are the same mobility management entity.
  • the user equipment After acquiring the second IP address, the user equipment establishes a second substream with the communication peer.
  • the second MPTCP substream is an MPTCP substream established by the user equipment using the second IP address and the communication peer.
  • the MPTCP technology adds an MPTCP layer between the socket (socket) of the TCP (Transmission Control Protocol)/IP protocol stack architecture and the TCP layer, and the MPTCP layer manages multiple sub-TCP modules, so that the user equipment and the communication pair
  • the terminal can establish one or more MPTCP sub-flow connections using different IP address pairs.
  • the user equipment sets an option for the MPTCP in the TCP message sent to the communication peer, and initiates a request to add the second MPTCP substream.
  • the user equipment by setting the MP_CAPABLE (Multipath Capable Multipath Available) identifier, queries the communication peer to determine whether the second MP TCP substream can be established, and after receiving the ACK (Acknowledgement) message of the MP_CAPABLE returned by the communication peer. Then, the second IP address is used to send a TCP message with the MP_JOIN (Join Connection) flag set to the communication peer.
  • the MP_JOIN Joint Connection
  • the communication peer cancels the first substream.
  • the user equipment and the communication peer communicate through the second MPTCP substream, thus canceling the first MPTCP substream.
  • the user equipment sends a TCP message carrying the REMOVE_ADDR (Remove Address) option to the communication peer by using the second MPTCP sub-flow, and sends a request to cancel the first MPTCP sub-flow to the communication peer, where The first IP address is included in the REMOVE_ADDR option.
  • REMOVE_ADDR Remove Address
  • the user equipment sends, by using the first MPTCP sub-flow, a TCP message with a F bit of 1 identified by a DSS (Data Sequence Information Number) to the communication peer end, where the F bit of the DSS identifier is a DATA_FIN bit, and the DATA_FIN position 1 represents the completion of the data transfer, requesting to revoke the first MPTCP substream.
  • DSS Data Sequence Information Number
  • the user equipment sends a TCP message carrying the MP_FASTCLOSE (Multipath Fastclose) option to the communication peer through the first MPTCP substream, requesting to cancel the first MPTCP substream.
  • MP_FASTCLOSE Multipath Fastclose
  • the first gateway releases the first IP address after the first substream is revoked.
  • the user equipment releases the first IP address and instructs the first gateway to release the first IP address. Specifically, the user equipment may send, by using the first base station or the first mobility management entity, an indication message for releasing the first IP address to the first gateway.
  • the user equipment releases the first IP address, that is, the first IP address is no longer occupied.
  • the first gateway releases the first IP address, that is, the binding between the first IP address and the user equipment is released. After releasing the first IP address, the first gateway may allocate the first IP address to other user equipments.
  • the user equipment simultaneously releases the RRC (Radio Resource Control) resource and the first IP address, and enters an idle state.
  • RRC Radio Resource Control
  • the mobility management method provided by the embodiment of the present invention dynamically allocates an IP address to a user equipment by using the first gateway and the second gateway.
  • the data aggregation type anchor device in the mobile network architecture uniformly allocates an IP address to the user equipment, and the anchor device has a huge pressure. Once the anchor device has a problem, the normal operation of the entire service network is affected, causing the user to The equipment business was interrupted.
  • the mobility management method provided by the embodiment of the present invention when the user equipment is switched from the first gateway to the second gateway, the user equipment and the communication peer establish a second MPTCP substream by using the second IP address by using the MPTCP technology.
  • the user equipment Before the establishment of the second MPTCP substream, the user equipment communicates with the communication peer through the first MPTCP substream, and after the second MPTCP substream is established, the first MPTCP substream is revoked. Thereby ensuring the user Normal communication between the device and the base station, and ensuring business continuity between the user equipment and the communication peer.
  • an embodiment of the present invention provides another mobility management method applied to a mobility management system in a cellular network.
  • the user equipment is switched by the first base station to the second base station in an idle state, and the second IP address is obtained after being connected to the second base station.
  • the user equipment is switched from the first base station to the second base station in the idle state, and enters an idle state after being connected to the second base station.
  • the user equipment initiates a service request or needs to send downlink data to the user equipment, the user equipment acquires Second IP address.
  • the steps in this embodiment are the same as the corresponding steps in the embodiment corresponding to FIG. 8. The same parts are not described in detail here. The specific steps are as follows:
  • the user equipment establishes a first substream of the communication peer.
  • the user equipment When the user equipment is switched from the first base station to the second base station, when the second gateway is not the same gateway as the first gateway, the user equipment acquires the second IP address.
  • the user equipment is in an idle state before being switched by the first base station to the second base station.
  • the user equipment sends a location update request message to the second mobility management entity, and simultaneously sets the first IP address or the first
  • the gateway identity is sent to the second mobility management entity.
  • the second mobility management entity determines whether the first gateway and the second gateway are unified gateways according to the first IP address or the first gateway identifier, and determines whether a new IP address needs to be allocated to the user equipment.
  • the second mobility management entity does not apply for an IP address to the user equipment, but only sends a location update acknowledgement (TAU Accept) message to the user equipment. After receiving the location update confirmation message, the user equipment enters an idle state.
  • TAU Accept location update acknowledgement
  • the second IP address can be obtained in three ways.
  • the user equipment sends a service request to the second base station, the second base station forwards the service request to the second mobility management entity, and the second mobility management entity goes to the second
  • the gateway applies for an IP address for the user equipment. And transmitting the second IP address received from the second gateway to the user equipment.
  • the user equipment receives the second IP address and completes the acquisition process of the second IP address.
  • the first gateway receives the downlink data sent by the communication peer to the user equipment
  • the downlink data is buffered, and the downlink data notification is sent to the first mobility management entity (DDN, Downlink). Data Notification).
  • the first mobility management entity pages the user equipment.
  • the first mobility management entity After the user equipment responds to the paging of the first mobility management entity, the first mobility management entity requests a new IP address from the second gateway for the user equipment, and sends the second IP address received from the second gateway to the second gateway through the NAS message. User equipment. At the same time, the first mobility management entity requests the first gateway to buffer the downlink data buffered by the first gateway, and sends the downlink data received from the first gateway to the user equipment by using the NAS message. Optionally, the first mobility management entity may send the second IP address and the downlink data to the user equipment at the same time.
  • the first mobility management entity requests a new IP address from the second gateway for the user equipment, and receives the second IP address from the second gateway by using the NAS message. Send to user device.
  • the first mobility management entity establishes a downlink data forwarding tunnel, so that the first gateway sends downlink data to the user equipment through the downlink data forwarding tunnel.
  • the downlink data forwarding tunnel may be a data forwarding tunnel between the first gateway and the second gateway, where the first gateway sends the downlink data to the second gateway through the downlink data forwarding tunnel, and the second gateway passes the second base station. Send downlink data to the user equipment.
  • the downlink data forwarding tunnel may also be a data forwarding tunnel between the first gateway and the second base station.
  • the first gateway sends the downlink data to the second base station through the data forwarding tunnel
  • the second base station sends the downlink data to the user equipment. .
  • the third way to obtain the second IP address After transmitting the location update confirmation message to the user equipment, the second mobility management entity registers the downlink data notification of the user equipment with the first mobility management entity. After confirming the registration of the second mobility management entity, the first mobility management entity sends the downlink data notification of the user equipment to the second mobility management entity if receiving the downlink data notification sent by the first gateway. After receiving the downlink data notification, the second mobility management entity pages the user equipment.
  • the physical entity is configured to manage the second base station and the second gateway, where the first mobility management entity is configured to manage the first base station and the first gateway.
  • the second mobility management entity After the user equipment responds to the paging of the first mobility management entity, the second mobility management entity requests a new IP address from the second gateway for the user equipment, and sends the second IP address received from the second gateway to the second gateway through the NAS message. User equipment. At the same time, the second mobility management entity requests downlink data from the first gateway by using the first mobility management entity. After receiving the downlink data sent by the first mobility management entity by the first gateway, the second mobility management entity sends the downlink data to the user equipment by using the NAS message. Optionally, the second mobility management entity may send the second IP address and the downlink data to the user equipment at the same time.
  • the second mobility management entity requests a new IP address from the second gateway for the user equipment, and receives the second IP address from the second gateway through the NAS message. Send to user device.
  • the second mobility management entity establishes a downlink data forwarding tunnel by using the first mobility management entity, so that the first gateway sends the buffered downlink data to the user equipment through the downlink data forwarding tunnel.
  • the downlink data forwarding tunnel may be The data forwarding tunnel between the first gateway and the second gateway. The first gateway sends the downlink data to the second gateway through the downlink data forwarding tunnel, and the second gateway sends the downlink data to the user equipment by using the second base station.
  • the downlink data forwarding tunnel may also be a data forwarding tunnel between the first gateway and the second base station.
  • the first gateway sends the downlink data to the second base station through the data forwarding tunnel
  • the second base station sends the downlink data to the user equipment. .
  • the user equipment establishes a second subflow with the communication peer after acquiring the second IP address.
  • the communication peer cancels the first substream after the second substream is established.
  • step 804 in the embodiment corresponding to FIG. 8 after the second MPTCP substream is established, the user equipment sends data to the communication peer through the second MPTCP sub-flow, and no longer sends data to the communication peer through the first MPTCP sub-flow, and thus is revoked.
  • the first MPTCP substream After the second MPTCP substream is established, the user equipment sends data to the communication peer through the second MPTCP sub-flow, and no longer sends data to the communication peer through the first MPTCP sub-flow, and thus is revoked.
  • the first MPTCP substream The first MPTCP substream.
  • the first gateway releases the first IP address after the first substream is revoked.
  • the user equipment After the first MPTCP subflow is revoked, the user equipment indicates that the first mobility management entity has revoked the first MPTCP subflow, and the first mobility management entity forwards the downlink number to the user equipment. After that, if the downlink data notification of the new user equipment is not received after the preset timer expires, the first gateway is instructed to release the first IP address, the downlink data forwarding tunnel, the context (Context) and the like.
  • the mobility management method provided by the embodiment of the present invention dynamically allocates an IP address to a user equipment by using the first gateway and the second gateway.
  • the data aggregation type anchor device in the mobile network architecture uniformly allocates an IP address to the user equipment, and the anchor device has a huge pressure. Once the anchor device has a problem, the normal operation of the entire service network is affected, causing the user to The equipment business was interrupted.
  • the mobility management method provided by the embodiment of the present invention when the user equipment is switched from the first gateway to the second gateway, the user equipment and the communication peer establish a second MPTCP substream by using the second IP address by using the MPTCP technology.
  • the user equipment Before the establishment of the second MPTCP substream, the user equipment communicates with the communication peer through the first MPTCP substream, and transmits the downlink data of the user equipment through the downlink data forwarding tunnel, and after the second MPTCP substream is established, the first MPTCP subflow is revoked. . Thereby, normal communication between the user equipment and the base station is ensured, and business continuity between the user equipment and the communication peer end is ensured.
  • an embodiment of the present invention provides another mobility management method applied to a mobility management system in a cellular network.
  • the user equipment is switched by the first base station to the second base station in an idle state, and the second IP address is obtained after being connected to the second base station.
  • the user equipment is communicating with the communication peer through the first MPTCP substream before being switched by the first base station to the second base station, and is performed by the first base station in the process of the user equipment communicating with the communication peer end.
  • the second base station is switched, it is necessary to ensure that the service connection of the user equipment is not interrupted.
  • the steps in this embodiment are the same as the corresponding steps in the embodiment corresponding to FIG. 8. The same parts are not described in detail here. The specific steps are as follows:
  • the user equipment is established in a first substream of the communication peer end.
  • 1002 When the user equipment is switched from the first base station to the second base station, when the second gateway is not the same gateway as the first gateway, the user equipment acquires the second IP address.
  • the user equipment is switched by the first base station to the second base station in the process of communicating with the communication peer end, and the second gateway is not the same gateway as the first gateway.
  • the data forwarding tunnel is established, and the user equipment continues to communicate with the communication peer through the data forwarding tunnel while acquiring the second IP address, that is, transmitting the first through the data forwarding tunnel.
  • the data of the MPTCP substream avoids the problem of service interruption during the handover process.
  • the data forwarding tunnel may include one of a downlink data forwarding tunnel and an uplink data forwarding tunnel, or both.
  • the case where the data forwarding tunnel includes the downlink data forwarding tunnel and the uplink data forwarding tunnel is taken as an example, the process of establishing the data forwarding tunnel, and the process of transmitting the data of the first MPTCP substream through the data forwarding tunnel are described.
  • this embodiment provides two methods for establishing a data forwarding tunnel.
  • a data forwarding tunnel is established through an X2 interface switch.
  • the first base station sends the IP address of the uplink data forwarding tunnel and the TEID (Tunnel End ID) to the second base station by using a Handover Request message.
  • the second base station After receiving the Handover Request message, the second base station sends the IP address and TEID of the downlink data forwarding tunnel to the first base station through a Handover Request Ack message, thereby establishing a data forwarding tunnel.
  • a data forwarding tunnel is established by switching through the S1 interface.
  • the first base station sends the IP address and TEID of the uplink data forwarding tunnel to the first mobility management entity by using a Handover Required message, and is forwarded to the second mobility management entity by the first mobility management entity.
  • the mobility management entity sends the IP address and TEID of the uplink data forwarding tunnel to the second base station through a Handover Request message.
  • the second base station After receiving the Handover Request message, the second base station returns a Handover Request Ack message to the first base station, thereby establishing a data forwarding tunnel.
  • the user equipment and the communication peer end transmit data of the first MPTCP substream through the data forwarding tunnel.
  • the data of the first MPTCP substream includes the downlink data of the first MPTCP substream and the uplink data of the first MPTCP substream, where the downlink data of the first MPTCP substream is data whose destination address is the first IP address, and the first MPTCP.
  • the uplink data of the substream is data sent by the user equipment to the communication peer.
  • the first base station After receiving the downlink data of the first MPTCP substream, the first base station sends the downlink data of the first MPTCP substream to the second base station by using the data forwarding tunnel after the downlink data of the first MPTCP substream is received, and is sent by the second base station. To the user device.
  • the second base station After acquiring the second IP address, the second base station sends the data packet whose source is not the second IP address as the uplink data packet of the first MPTCP sub-flow to the first data packet through the data forwarding tunnel after acquiring the second IP address.
  • the base station is sent by the first base station to the communication peer.
  • the embodiment provides a manner in which the two second base stations obtain the second IP address, which are respectively applied to the scenario where the user equipment obtains the second IP address through the DHCP message. And a scenario in which the second mobility management entity requests the second gateway to allocate an IP address to the user equipment.
  • the user equipment determines that the first gateway and the second gateway are not the same gateway by receiving the first gateway identifier and the second gateway identifier, and requests a new IP address from the second gateway. Get the second IP address. Or the user equipment sends the second gateway identifier to the first base station, where the first base station determines the second gateway identifier and the first gateway identifier, and if the second gateway identifier is different from the first gateway identifier, the first base station sends the user equipment to the user equipment. And sending a judgment indication message, where the judgment indication message is used to indicate that the second gateway is not the same gateway as the first gateway. After receiving the judgment indication message, the user equipment acquires the second IP address by requesting the new IP address from the second gateway.
  • the user equipment After acquiring the second IP address, the user equipment sends the second IP address to the second base station by using an RRC message, or the user equipment sends the second IP address to the second mobility management entity by using the NAS message, by the second mobility management.
  • the entity sends the second IP address to the second base station through the S1 message.
  • the second base station sends the data packet of the first IP address sent by the user equipment to the first base station through the data forwarding tunnel, and the first base station sends the data packet to the communication peer end.
  • the user equipment sends the first IP address or the first gateway identifier to the second mobility management entity, and is determined by the second mobility management entity.
  • the first gateway is not the same gateway as the second gateway, and then the second mobility management entity requests a new IP address for the user equipment from the second gateway, and sends the second IP address received from the second gateway to the user through the NAS message.
  • the device is simultaneously sent to the second base station through the S1 message, thereby completing the use The process of acquiring the second IP address by the user equipment and the second base station.
  • the second base station sends the data packet of the first IP address sent by the user equipment to the first base station through the data forwarding tunnel, and the first base station sends the data packet to the communication peer end.
  • the second mobility management entity requests the second gateway to allocate an IP address to the user equipment
  • the user equipment sends the first IP address or the first gateway identifier to the second mobility management entity, and adopts the second mobility management.
  • the entity determines that the first gateway is not the same gateway as the second gateway, and then the second mobility management entity requests a new IP address from the second gateway for the user equipment, and the second gateway sends the second IP address to the second mobility management entity.
  • the second mobility management entity is requested to establish a bearer between the user equipment and the second base station by using a Bearer Creat Request message.
  • the second mobility management entity binds the newly created bearer with the second IP address and sends it to the user equipment through the NAS message. Thereby, the process of the user equipment acquiring the second IP address is completed.
  • the user equipment sends the uplink data
  • the data packet whose source address is the second IP address is sent through the newly created bearer
  • the data packet whose source address is the first IP address is sent through the existing bearer.
  • the second base station sends the data packet sent by the user equipment through the existing bearer to the first base station through the data forwarding tunnel, and is sent by the first base station to the communication peer end.
  • the user equipment After acquiring the second IP address, the user equipment establishes a second substream with the communication peer.
  • the communication peer cancels the first substream.
  • step 804 in the embodiment corresponding to FIG. 8 after the second MPTCP substream is established, the user equipment sends data to the communication peer through the second MPTCP sub-flow, and no longer sends data to the communication peer through the first MPTCP sub-flow, and thus is revoked.
  • the first MPTCP substream After the second MPTCP substream is established, the user equipment sends data to the communication peer through the second MPTCP sub-flow, and no longer sends data to the communication peer through the first MPTCP sub-flow, and thus is revoked.
  • the first MPTCP substream The first MPTCP substream.
  • the first gateway releases the first IP address after the first subflow is revoked.
  • the user equipment instructs the first gateway to release the first IP address by using the first mobility management entity, and the user equipment instructs the second base station to delete the data forwarding tunnel.
  • the user equipment indicates, by using an RRC message, that the first MPTCP sub-flow has been revoked by the second base station, or that the user equipment indicates, by using the NAS message, that the second mobility management entity has revoked the first MPTCP sub-flow, and the second mobility management entity indicates the second base station
  • An MPTCP subflow has been revoked.
  • the first base station After receiving the indication that the first MPTCP sub-flow has been revoked, the first base station sends a request message for deleting the data forwarding tunnel, and the first base station returns the deletion data forwarding to the second base station after receiving the request message for deleting the data forwarding tunnel. Confirmation message for the tunnel.
  • the first base station and the second base station release a data forwarding tunnel, and the first base station deletes a context (Context) and an access network resource of the user equipment.
  • the user equipment indicates, by using an RRC message, that the first MPTCP substream of the second base station has been revoked, or the user equipment indicates, by using the NAS message, the first mobility sub-flow of the second mobility management entity.
  • the second mobility management entity indicates that the second base station first MPTCP sub-flow has been revoked.
  • the second base station After receiving the indication that the first MPTCP sub-flow has been revoked, the second base station sends an indication message to the first mobility management entity by using the second mobility management entity.
  • the second mobility management entity instructs the second gateway to release the data forwarding tunnel
  • the first mobility management entity instructs the first gateway and the first base station to release the data forwarding tunnel
  • the first base station simultaneously deletes the context of the user equipment and the access network resource.
  • an embodiment of the present invention further provides a method for charging a user equipment.
  • the user equipment communicates with the communication peer through the first substream
  • the user equipment is charged by the first gateway
  • the second gateway calculates the user equipment. fee.
  • an application scenario in which the first gateway performs charging for the user equipment is taken as an example for description.
  • the first gateway acquires the charging rule of the user equipment and the available quota of the user equipment, and The available amount of the user equipment is deducted according to the charging rule of the user equipment, and then the available credit balance of the user equipment is sent to the online charging system.
  • the available amount of the user equipment is the available amount of the account of the user equipment, and the available amount may be the User equipment credit (Credit) or quota (Quota).
  • the first mobility management entity when the user equipment is connected to the first gateway, the first mobility management entity is requested to apply the charging rule of the user equipment and the available quota of the user equipment.
  • the charging rule of the user equipment obtained by the first mobility management entity from the policy and charging rule function is sent to the first gateway, and the first mobility management entity acquires the available balance of the user equipment from the online charging system and sends the first to the first Gateway.
  • the first gateway deducts the available amount of the user equipment according to the charging rule of the user equipment. If the user equipment's available credits are all deducted, the first gateway re-requests the first mobility management entity for the user equipment's available credit. After the first substream is revoked, the first gateway returns the balance of the user equipment's available credits to the online charging system through the mobility management entity.
  • the first gateway sends the CDR (Call Detail Record) of the user equipment at the first gateway to the first mobility management entity. ).
  • the first mobility management entity sends the CDR of the user equipment at the first gateway to the offline charging system.
  • the first mobility management entity may manage multiple gateways, and the first gateway may be one or more of the gateways managed by the first mobility management entity.
  • the mobility management method provided by the embodiment of the present invention dynamically allocates an IP address to a user equipment by using the first gateway and the second gateway.
  • the data aggregation type anchor device in the mobile network architecture uniformly allocates an IP address to the user equipment, and the anchor device has a huge pressure. Once the anchor device has a problem, the normal operation of the entire service network is affected, causing the user to The equipment business was interrupted.
  • the mobility management method provided by the embodiment of the present invention when the user equipment is switched from the first gateway to the second gateway, the user equipment and the communication peer establish a second MPTCP substream by using the second IP address by using the MPTCP technology.
  • the user equipment Before the second MPTCP substream is established, the user equipment communicates with the communication peer through the first MPTCP substream, and receives the downlink data and sends the uplink data through the data forwarding tunnel. After the second MPTCP substream is established, the first MPTCP subflow is cancelled. . Thereby, normal communication between the user equipment and the base station is ensured, and business continuity between the user equipment and the communication peer end is ensured.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a computer.
  • the computer readable medium may include a RAM (Random Access Memory), a ROM (Read Only Memory), and an EEPROM (Electrically Erasable Programmable Read Only Memory).
  • CD-ROM Compact Disc Read Only Memory
  • CD-ROM Compact Disc Read Only Memory
  • Any connection may suitably be a computer readable medium.
  • coaxial cable, fiber optic cable, twisted pair, DSL (Digital Subscriber Line), or wireless technologies such as infrared, radio, and microwave
  • coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, wireless and microwave are included in the fixing of the associated medium.
  • the disc and the disc include a CD (Compact Disc), a laser disc, a compact disc, a DVD disc (Digital Versatile Disc), a floppy disc, and a Blu-ray disc, wherein the disc is usually magnetically copied,
  • the disc uses a laser to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media.

Abstract

本发明的实施例提供一种移动性管理的方法、装置及系统，涉及通信领域，能够在不通过锚点设备的情况下有效保证用户设备和基站的正常通信，并保证用户设备与通信对端之间的业务连续性。具体方案为：用户设备建立于通信对端的第一子流，在用户设备由第一基站向第二基站切换时，当第二网关与第一网关不是同一网关时，用户设备获取第二IP地址，用户设备在获取第二IP地址后与通信对端建立第二子流，通信对端在第二子流建立之后，撤销第一子流，第一网关在第一子流撤销之后释放第一IP地址。本发明用于无线网络中的移动性管理。

Description

一种移动性管理的方法、装置及系统 技术领域
本发明涉及通信技术领域，尤其涉及一种移动性管理的方法、装置及系统。
背景技术
当前的通信技术发展出各种各样的接入技术，比如蜂窝网络的2G/3G/4G接入技术、WLAN(Wireless Local Area Networks，无线局域网)接入技术、光纤接入技术以及蓝牙接入技术等。在一个通信终端中可以集成多种接入技术，如何有效利用通信终端(如用户终端)中的各种接入技术提升通信效率和用户体验是当前技术热点之一。
在实现多路接入的技术中，MPTCP(Multi-Path Transmission Control Protocol，多路径传输控制协议)技术是发展的比较成熟的一种，可以分发数据包通过多种接入技术的通路在用户终端和网络之间进行传递。在TCP(Transmission Control Protocol，传输控制协议)/IP(Internet Protocol，网络互连协议)协议栈架构的socket(套接字)和TCP层之间，增加MPTCP层，由它负责管理多个子TCP模块。通信双方可以使用不同的地址对，建立TCP子流连接，这些TCP子流可以在一个或者多个接入技术的网络上传输，MPTCP层负责选择对业务数据流的分包组包，选路和调度。每个子流通过关联和管理多条TCP子流，并发传输数据，提高带宽利用率和传输性能，socket和应用层不用关心传输业务数据流的具体TCP子流。
在单接入技术下，比如蜂窝网络，当通信双方中的一方在蜂窝网络中移动时，如果其IP地址发生改变，则导致通信双方的TCP连接中断。因此现有的蜂窝网络中，为保证基于TCP的业务的连续性，避免发生数据传输中断，需要部署保持IP地址不变的锚点设备。随着智能终端和移动应用的迅速普及带来的移动互联网的快速发展，移动网络趋于分布式部署。同时，大数据量的移动互联网通信，使得原有移动网络架构中的数据汇聚式的锚点设备压力巨大，一旦 锚点设备出现问题，进而影响整个业务网络的正常运行。
发明内容
本发明的实施例提供一种移动性管理的方法、装置及系统，能够在不通过锚点设备的情况下有效保证用户设备和基站的正常通信。
为达到上述目的，本发明的实施例采用如下技术方案：
第一方面，一种移动性管理系统，包括：用户设备，第一基站，第二基站，第一网关，第二网关及通信对端，所述第一基站与所述第一网关连接，所述第二基站与所述第二网关连接；
所述用户设备，用于建立与所述通信对端的第一子流，所述第一子流为所述用户设备使用第一网际互连协议IP地址与所述通信对端建立的子流，所述第一IP地址是所述第一网关为所述用户设备分配的IP地址；
当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备，还用于当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，所述第二IP地址为所述第二网关为所述用户设备分配的IP地址；
所述用户设备，还用于在获取所述第二IP地址后与所述通信对端建立第二子流，所述第二子流为所述用户设备使用所述第二IP地址与所述通信对端建立的子流；
所述通信对端，用于在所述第二子流建立之后，撤销所述第一子流；
所述第一网关，还用于在所述第一子流撤销之后释放所述第一IP地址。
结合第一方面，在第一种可能的实现方式中，
所述用户设备，还用于在所述撤销所述第一子流之后，释放所述第一IP地址，并向所述第一网关发送释放所述第一IP地址的指示消息；
所述第一网关，用于在接收所述用户设备发送的所述释放所述第一IP地址的指示消息后，释放所述第一IP地址。
结合第一方面，在第二种可能的实现方式中，
所述第一基站及所述第二基站，用于建立数据转发隧道，所述数据转发隧道为所述第一基站及所述第二基站之间的数据转发通道；
所述用户设备及所述通信对端，还用于通过所述数据转发隧道传输所述第一子流的数据。
结合第一方面的第二种可能的实现方式，在第三种可能的实现方式中，
所述数据转发隧道，包括：
下行数据转发隧道或上行数据转发隧道；
或者，下行数据转发隧道和上行数据转发隧道。
结合第一方面的第二种可能的实现方式或者第一方面的第三种可能的实现方式，在第四种可能的实现方式中，
所述第二基站，还用于在所述第一子流撤销后，删除所述数据转发隧道。
结合第一方面，在第五种可能的实现方式中，
所述当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，包括：
当所述用户设备与第一基站连接时，接收所述第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关；
当所述用户设备由所述第一基站向所述第二基站切换时，接收所述第二基站发送的第二网关标识，所述第二网关标识用于指示第二网关；
如果所述第二网关标识与所述第一网关标识不同，则所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
结合第一方面，在第六种可能的实现方式中，
所述当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，包括：
所述移动性管理系统还包括第二移动性管理实体，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备将所述第一IP地址或第一网关标识发送至所述第二移动性管理实体，所述第一网关标识用于指示第一网关；
所述第二移动性管理实体确定所述第一IP地址是否为所述第二网关为所述用户设备分配的IP地址，或所述第一网关标识是否与第二网关标识相同，所述第二网关标识用于指示第二网关；
如果所述第一IP地址不是所述第二网关为所述用户设备分配的IP地址，或所述第一网关标识与所述第二网关标识不同，则所述第二移动性管理实体向所述第二网关为所述用户设备申请分配IP地址，并将从所述第二网关接收的所述第二IP地址发送至所述用户设备。
结合第一方面，在第七种可能的实现方式中，
所述当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，包括：
当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备将第二网关标识发送至所述第一基站，所述第二网关标识用于指示第二网关；
如果所述第二网关标识与所述第一网关标识不同，则所述第一基站向所述用户设备发送判断指示消息，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关；
所述用户设备在接收判断指示消息后向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
结合第一方面，在第八种可能的实现方式中，
所述移动性管理系统还包括第二移动性管理实体，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
所述用户设备，还用于当所述用户设备在空闲态从所述第一基站移动到所述第二基站，向所述第二移动性管理实体发送位置更新 请求消息；
所述第二移动性管理实体，用于向所述用户设备发送位置更新确认消息。
结合第一方面，在第九种可能的实现方式中，
所述用户设备，在空闲态从所述第一基站移动到所述第二基站，在连接第二基站完成位置更新之后，进入空闲态；
所述移动性管理系统还包括第一移动性管理实体，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
所述第一网关，还用于在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知；
所述第一移动性管理实体，还用于从所述第一网关接收所述用户设备的下行数据通知，并在接收所述用户设备的下行数据通知后寻呼所述用户设备；
所述用户设备，还用于响应所述第二移动性管理实体的寻呼。
结合第一方面的第九种可能的实现方式，在第十种可能的实现方式中，
所述第一网关，还用于缓存下行数据；
所述第一移动性管理实体，还用于在所述用户设备响应寻呼后向所述第一网关请求所述下行数据，接收所述第一网关发送的所述下行数据，并将从所述第一网关接收的所述下行数据发送至所述用户设备。
结合第一方面的第九种可能的实现方式，在第十一种可能的实现方式中，
所述第一网关，还用于缓存下行数据；
所述第一移动性管理实体，还用于在所述用户设备响应寻呼后建立下行数据转发隧道；
所述第一网关，还用于通过所述下行数据转发隧道向所述用户设备发送所述下行数据。
结合第一方面，在第十二种可能的实现方式中，
所述用户设备，在空闲态从所述第一基站移动到所述第二基站，在连接第二基站完成位置更新之后，进入空闲态；
所述移动性管理系统还包括第一移动性管理实体及第二移动性管理实体，所述第一移动性管理实体用于管理所述第一基站和所述第一网关，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
所述第二移动性管理实体，还用于向所述第一移动性管理实体注册所述用户设备的下行数据通知；
所述第一网关，还用于在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知；
所述第一移动性管理实体，还用于在确认所述第二移动性管理实体的注册后，将所述用户设备的下行数据通知发送至所述第二移动性管理实体；
所述第二移动性管理实体，还用于在接收所述用户设备的下行数据通知后寻呼所述用户设备；
所述用户设备，还用于响应所述第二移动性管理实体的寻呼。
结合第一方面的第十二种可能的实现方式，在第十三种可能的实现方式中，
所述第一网关，还用于缓存下行数据；
所述第二移动性管理实体，还用于在所述用户设备响应寻呼后通过所述第一移动性管理实体请求所述下行数据；
所述第一移动性管理实体，还用于将所述第一网关发送的所述下行数据转发至所述第二移动性管理实体；
所述第二移动性管理实体，还用于将所述下行数据发送至所述用户设备。
结合第一方面的第十二种可能的实现方式，在第十四种可能的实现方式中，
所述第一网关，还用于缓存下行数据；
所述第二移动性管理实体，还用于在所述用户设备响应寻呼后 通过所述第一移动性管理实体建立下行数据转发隧道；
所述第一网关，还用于通过所述下行数据转发隧道向所述用户设备发送所述下行数据。
结合第一方面，在第十五种可能的实现方式中，
所述移动性管理系统还包括：第一移动性管理实体、在线计费系统OCS及策略和计费规则功能PCRF，
所述第一移动性管理实体，用于从所述在线计费系统获取所述用户设备的可用额度，并将所述用户设备的可用额度发送至所述第一网关；
所述第一移动性管理实体，还用于从所述策略和计费规则功能获取所述用户设备的计费规则，并将所述用户设备的计费规则发送至所述第一网关；
所述第一网关，还用于当用户设备通过所述第一子流与所述通信对端进行通信时，根据所述用户设备的计费规则对所述用户设备的可用额度进行扣减，并向在线计费系统发送所述用户设备的可用额度余额。
结合第一方面，在第十六种可能的实现方式中，
所述移动性管理系统还包括：第一移动性管理实体及离线计费系统OFCS。
所述第一网关，还用于向所述第一移动性管理实体发送所述用户设备在所述第一网关的话单；
所述第一移动性管理实体，用于将所述用户设备在所述第一网关的话单发送至离线计费系统。
第二方面，一种用户设备，包括处理器、存储器及总线，所述处理器及所述存储器通过所述总线相互连接；
其中，所述处理器，用于建立与通信对端的第一子流，所述第一子流为所述用户设备使用第一网际互连协议IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
所述处理器，还用于获取第二IP地址，所述第二IP地址为所述第二网关为所述用户设备分配的IP地址；
所述处理器，还用于与所述通信对端建立第二子流，所述第二子流为所述用户设备使用所述第二IP地址与所述通信对端建立的子流；
所述处理器，还用于撤销所述第一子流。
结合第二方面，在第一种可能的实现方式中，
所述处理器，还用于在所述撤销所述第一子流之后，释放所述第一IP地址，并生成指示所述第一网关释放所述第一IP地址的指示消息；
所述用户设备还包括发送器，用于向所述第一网关发送指示所述第一网关释放所述第一IP地址的指示消息。
结合第二方面，在第二种可能的实现方式中，
所述处理器，还用于通过数据转发隧道传输所述第一子流的数据，所述数据转发隧道为所述第一基站及所述第二基站之间的数据转发通道。
结合第二方面的第一种可能的实现方式，在第三可能的实现方式中，
所述数据转发隧道，包括：
下行数据转发隧道或上行数据转发隧道；
或者，下行数据转发隧道和上行数据转发隧道。
结合第二方面的第二种可能的实现方式或第二方面的第三种可能的实现方式，在第四可能的实现方式中，
所述处理器，还用于释放所述第一IP地址；
所述处理器，还用于生成指示所述第一子流已经撤销的指示消息；
所述用户设备还包括发送器，用于向所述第二基站发送指示所述第一子流已经撤销的指示消息，以便于所述第二基站删除所述数据转发隧道。
结合第二方面，在第五种可能的实现方式中，
其特征在于，所述用户设备还包括接收器，
所述接收器，用于接收所述第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关；
所述接收器，还用于接收所述第二基站发送的第二网关标识，所述第二网关标识用于指示第二网关；
所述处理器，还用于判断所述第二网关标识与所述第一网关标识是否相同，如果所述第二网关标识与所述第一网关标识不同，则生成获取IP地址的请求消息；
所述用户设备还包括发送器，用于向所述第二网关发送所述获取IP地址的请求消息；
所述接收器，还用于接收所述第二网关发送的所述第二IP地址。
结合第二方面，在第六种可能的实现方式中，
所述用户设备还包括发送器及接收器，
所述发送器，用于当所述用户设备由所述第一基站向所述第二基站切换时，将所述第一IP地址或第一网关标识发送至第二移动性管理实体，以便于所述第二移动性管理实体根据所述第一IP地址或第一网关标识确定所述第二网关与所述第一网关是否为同一网关，并在所述第二网关与所述第一网关不是同一网关时向所述第二网关为所述用户设备申请分配IP地址，将从所述第二网关接收的所述第二IP地址发送至所述用户设备，所述第一网关标识用于指示第一网关，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
所述接收器，用于接收所述第二移动性管理实体发送的所述第二IP地址。
结合第二方面，在第七种可能的实现方式中，
所述用户设备还包括发送器及接收器，
所述发送器，用于当所述用户设备由所述第一基站向所述第二基站切换时，将第二网关标识发送至所述第一基站，以便于所述第 一基站确定所述第二网关与所述第一网关是否为同一网关，所述第二网关标识用于指示第二网关；
所述接收器，用于接收所述第一基站发送的判断指示消息，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关；
所述处理器，还用于生成获取IP地址的请求消息；
所述发送器，还用于向所述第二网关发送所述获取IP地址的请求消息；
所述接收器，还用于接收所述第二网关发送的所述第二IP地址。
结合第二方面，在第八种可能的实现方式中，
所述处理器还用于当所述用户设备在空闲态从所述第一基站移动到所述第二基站时，生成位置更新请求消息；
所述用户设备还包括接收器和发送器，
所述发送器，用于向第二移动性管理实体发送所述位置更新请求消息，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
所述接收器，用于接收所述第二移动性管理实体发送的位置更新确认消息。
结合第二方面的第八种可能的实现方式，在第九种可能的实现方式中，
所述处理器，还用于控制所述用户设备进入空闲态；
所述接收器，还用于当所述用户设备在空闲态时接收第一移动性管理实体的寻呼，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
所述处理器，还用于生成寻呼响应消息；
所述发送器，用于向所述第一移动性管理实体发送所述寻呼响应消息；
所述接收器，还用于当所述用户设备在空闲态时接收第二移动 性管理实体的寻呼，所述第二移动性管理实体用于管理所述第二基站和所述第二网关。
所述发送器，用于向所述第二移动性管理实体发送所述寻呼响应消息。
结合第二方面的第九种可能的实现方式，在第十种可能的实现方式中，
所述接收器，还用于接收所述下行数据。
第三方面，一种第一基站，包括处理器、存储器、发送器、接收器及总线，所述处理器、所述存储器、所述发送器及所述接收器通过所述总线相互连接；
其中，所述处理器，用于当所述用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，生成数据转发隧道的建立请求消息，所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
所述发送器，用于向所述第二基站发送所述数据转发隧道的建立请求消息；
所述接收器，用于接收所述第二基站发送的所述数据转发隧道的建立确认消息；
所述接收器，还用于接收所述第二基站发送的所述数据转发隧道的删除请求消息；
所述发送器，还用于向所述第二基站发送所述数据转发隧道的删除确认消息；
所述处理器，还用于释放所述数据转发隧道，并生成第一IP释放指示消息；
所述发送器，还用于向所述第一网关发送所述第一IP释放指示消息。
结合第三方面，在第一种可能的实现方式中，
所述接收器，还用于接收所述用户设备发送的第二网关标识，所述第二网关标识用于指示第二网关；
所述处理器，还用于根据所述第二网关标识确定所述第二网关与所述第一网关是否为同一网关，当所述第二网关与所述第一网关不是同一网关时，生成判断指示消息，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关；
所述发送器，还用于向所述用户设备发送所述判断指示消息，以便于所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
第四方面，一种第二基站，包括处理器、存储器、发送器、接收器及总线，所述处理器、所述存储器、所述发送器及所述接收器通过所述总线相互连接；
其中，所述接收器，用于当所述用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，接收所述第一基站发送的数据转发隧道的建立请求消息，所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述 第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
所述处理器，用于生成所述数据转发隧道的建立确认消息；
所述发送器，用于向所述第一基站发送所述数据转发隧道的建立确认消息；
所述处理器，还用于在所述第一子流撤消后生成所述数据转发隧道的删除请求消息；
所述发送器，还用于，向所述第一基站发送所述数据转发隧道的删除请求消息；
所述接收器，还用于接收所述第一基站发送的所述数据转发隧道的删除确认消息；
所述处理器，还用于释放所述数据转发隧道。
第五方面，一种用户设备，其特征在于，包括：多路径控制单元及收发单元，
所述多路径控制单元，用于当所述用户设备与第一基站连接时，建立与通信对端的第一子流，所述第一子流为所述用户设备使用第一网际互连协议IP地址与所述通信对端建立的子流，所述第一网际互联协议IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
所述收发单元，用于获取第二IP地址，所述第二IP地址为所述第二网关为所述用户设备分配的IP地址；
所述多路径控制单元，还用于与所述通信对端建立第二子流，所述第二子流为所述用户设备使用所述第二IP地址与所述通信对端建立的子流；
所述多路径控制单元，还用于在所述第二子流建立完成后，撤销所述第一子流。
结合第五方面，在第一种可能的实现方式中，
多路径控制单元，还用于在所述撤销所述第一子流之后，释放 所述第一IP地址，并生成指示所述第一网关释放所述第一IP地址的指示消息；
所述收发单元，还用于向所述第一网关发送指示所述第一网关释放所述第一IP地址的指示消息。
结合第五方面，在第二种可能的实现方式中，
所述收发单元，还用于通过数据转发隧道传输所述第一子流的数据，所述数据转发隧道为所述第一基站及所述第二基站之间的数据转发通道。
结合第五方面的第二种可能的实现方式，在第三种可能的实现方式中，
下行数据转发隧道或上行数据转发隧道；
或者，下行数据转发隧道和上行数据转发隧道。
结合第五方面的第二种可能的实现方式或第五方面的第三种可能的实现方式，在第四种可能的实现方式中，
所述多路径控制单元，还用于释放所述第一IP地址；
所述多路径控制单元，还用于生成所述第一子流已经撤销的指示消息；
所述收发单元，还用于向所述第二基站发送所述第一子流已经撤销的指示消息，以便于所述第二基站删除所述数据转发隧道。
结合第五方面，在第五种可能的实现方式中，
所述收发单元，还用于当所述用户设备与第一基站连接时，接收所述第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关；
所述收发单元，还用于当所述用户设备由所述第一基站向所述第二基站切换时，接收所述第二基站发送的第二网关标识，所述第二网关标识用于指示第二网关；
所述多路径控制单元，还用于判断所述第二网关标识与所述第一网关标识是否相同，如果所述第二网关标识与所述第一网关标识不同，则生成获取IP地址的请求消息；
所述收发单元，还用于向所述第二网关发送所述获取IP地址的请求消息；
所述收发单元，还用于接收所述第二网关发送的所述第二IP地址。
结合第五方面，在第六种可能的实现方式中，
所述收发单元，还用于当所述用户设备由所述第一基站向所述第二基站切换时，将所述第一IP地址或第一网关标识发送至第二移动性管理实体，以便于所述第二移动性管理实体根据所述第一IP地址或第一网关标识确定所述第二网关与所述第一网关是否为同一网关，并在所述第二网关与所述第一网关不是同一网关时向所述第二网关为所述用户设备申请分配IP地址，将从所述第二网关接收的所述第二IP地址发送至所述用户设备，所述第一网关标识用于指示第一网关，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
所述收发单元，还用于接收所述第二移动性管理实体发送的所述第二IP地址。
结合第五方面，在第七种可能的实现方式中，
所述收发单元，还用于当所述用户设备由所述第一基站向所述第二基站切换时，将第二网关标识发送至所述第一基站，以便于所述第一基站确定所述第二网关与所述第一网关是否为同一网关，所述第二网关标识用于指示第二网关；
所述收发单元，还用于接收所述第一基站发送的判断指示消息，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关；
所述多路径控制单元，还用于生成获取IP地址的请求消息；
所述收发单元，还用于向所述第二网关发送所述获取IP地址的请求消息；
所述收发单元，还用于接收所述第二网关发送的所述第二IP地址。
结合第五方面，在第八种可能的实现方式中，
所述用户设备还包括切换控制单元，
所述切换控制单元，用于当所述用户设备在空闲态从所述第一基站移动到所述第二基站时，生成位置更新请求消息；
所述收发单元，还用于向第二移动性管理实体发送所述位置更新请求消息；
所述收发单元，还用于接收所述第二移动性管理实体发送的位置更新确认消息，所述第二移动性管理实体用于管理所述第二基站和所述第二网关。
结合第五方面，在第九种可能的实现方式中，
所述切换控制单元，还用于控制所述用户设备进入空闲态；
所述收发单元，还用于当所述用户设备在空闲态时接收第一移动性管理实体的寻呼，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
所述切换控制单元，还用于响应所述第一移动性管理实体的寻呼；
所述收发单元，还用于接收所述第一网关缓存并转发的下行数据；
所述收发单元，还用于当所述用户设备在空闲态时接收第二移动性管理实体的寻呼，所述第一移动性管理实体用于管理所述第一基站和所述第一网关。
所述切换控制单元，还用于响应所述第二移动性管理实体的寻呼。
结合第五方面的第九种可能的实现方式，在第十种可能的实现方式中，
所述收发单元，还用于接收所述下行数据。
第六方面，一种第一基站，包括控制单元、发送单元及接收单元；
所述控制单元，用于当所述用户设备由所述第一基站向所述第 二基站切换时，在第二子流建立之前，生成数据转发隧道的建立请求消息，所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
所述发送单元，用于所述第二基站发送所述数据转发隧道的建立请求消息；
所述接收单元，用于接收所述第二基站发送的所述数据转发隧道的建立确认消息；
所述接收单元，还用于接收所述第二基站发送的所述数据转发隧道的删除请求消息；
所述控制单元，还用于生成所述数据转发隧道的删除确认消息；
所述发送单元，还用于向所述第二基站发送所述数据转发隧道的删除确认消息；
所述控制单元，还用于释放所述数据转发隧道，并生成第一IP释放指示消息；
所述发送单元，还用于向所述第一网关发送所述第一IP释放指示消息。
结合第六方面，在第一种可能的实现方式中，
所述接收单元，还用于接收所述用户设备发送的第二网关标识，所述第二网关标识用于指示第二网关；
所述控制单元，还用于根据所述第二网关标识确定所述第二网 关与所述第一网关是否为同一网关，并在所述第二网关与所述第一网关不是同一网关时，生成判断指示消息，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关；
所述发送单元，还用于向所述用户设备发送判断指示消息，以便于所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
第七方面，一种第二基站，包括控制单元、发送单元及接收单元；
所述接收单元，用于当用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，接收所述第一基站发送的数据转发隧道的建立请求消息，所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
所述控制单元，用于生成所述数据转发隧道的建立确认消息；
所述发送单元，用于向所述第一基站发送所述数据转发隧道的建立确认消息；
所述控制单元，还用于在所述第一子流撤消后，生成所述数据转发隧道的删除请求消息；
所述发送单元，还用于向所述第一基站发送所述数据转发隧道的删除请求消息；
所述接收单元，还用于接收所述第一基站发送的所述数据转发 隧道的删除确认消息；
所述控制单元，还用于释放所述数据转发隧道。
第八方面，一种移动性管理方法，其特征在于，
用户设备建立与通信对端的第一子流，所述第一子流为所述用户设备使用第一网际互连协议IP地址与所述通信对端建立的子流，所述第一IP地址是所述第一网关为所述用户设备分配的IP地址；
在所述用户设备由所述第一基站向所述第二基站切换时，当所述第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，所述第二IP地址为所述第二网关为所述用户设备分配的IP地址；
所述用户设备在获取所述第二IP地址后与所述通信对端建立第二子流，所述第二子流为所述用户设备使用所述第二IP地址与所述通信对端建立的子流；
所述通信对端在所述第二子流建立之后，撤销所述第一子流；
所述第一网关在所述第一子流撤销之后释放所述第一IP地址。
结合第八方面，在第一种可能的实现方式中，
所述用户设备，在所述撤销所述第一子流之后，释放所述第一IP地址，并指示所述第一网关释放所述第一IP地址。
结合第八方面，在第二种可能的实现方式中，
所述用户设备由所述第一基站向所述第二基站切换，包括：所述用户设备在与所述通信对端正在进行通信的过程中由所述第一基站向所述第二基站切换；
所述当所述第二网关与所述第一网关不是同一网关时，所述方法还包括：
所述第一基站及所述第二基站，建立数据转发隧道，所述数据转发隧道为所述第一基站及所述第二基站之间的数据转发通道；
所述用户设备及所述通信对端，通过所述数据转发隧道传输所述第一子流的数据。
结合第八方面的第二种可能的实现方式，在第三种可能的实现 方式中，
所述数据转发隧道，包括：
下行数据转发隧道或上行数据转发隧道；
或者，下行数据转发隧道和上行数据转发隧道。
结合第八方面的第二种可能的实现方式或第八方面的第三种可能的实现方式，在第四种可能的实现方式中，
所述撤销所述第一子流之后，所述方法还包括：
所述第二基站，删除所述数据转发隧道。
结合第八方面，在第五种可能的实现方式中，
所述当所述第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，包括：
当所述用户设备与第一基站连接时，接收所述第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关；
当所述用户设备由所述第一基站向所述第二基站切换时，接收所述第二基站发送的第二网关标识，所述第二网关标识用于指示第二网关；
如果所述第二网关标识与所述第一网关标识不同，则所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
结合第八方面，在第六种可能的实现方式中，
所述当所述第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，包括：
所述移动性管理系统还包括第二移动性管理实体；
当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备将所述第一IP地址或第一网关标识发送至所述第二移动性管理实体，所述第一网关标识用于指示第一网关；
所述第二移动性管理实体确定所述第一IP地址是否为所述第二网关为所述用户设备分配的IP地址，或所述第一网关标识是否与第二网关标识相同；
如果所述第一IP地址不是所述第二网关为所述用户设备分配的IP地址，或所述第一网关标识与所述第二网关标识不同，则所述第二移动性管理实体向所述第二网关为所述用户设备申请分配IP地址，并将从所述第二网关接收的所述第二IP地址发送至所述用户设备。
结合第八方面，在第七种可能的实现方式中，
所述当所述第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，包括：
当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备将第二网关标识发送至所述第一基站，所述第二网关标识用于指示第二网关；
如果所述第二网关标识与第一网关标识不同，则所述第一基站向所述用户设备发送判断指示消息，所述第一网关标识用于指示第一网关，所述判断指示消息指示所述第二网关与所述第一网关不是同一网关；
所述用户设备在接收判断指示消息后向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
结合第八方面，在第八种可能的实现方式中，
所述用户设备由所述第一基站向所述第二基站切换，包括：所述用户设备在空闲态从所述第一基站移动到所述第二基站，向第二移动性管理实体发送位置更新请求消息，并接收所述第二移动性管理实体发送的位置更新确认消息，所述第二移动性管理实体用于管理所述第二基站和所述第二网关。
结合第八方面，在第九种可能的实现方式中，所述方法还包括：
当所述用户设备在空闲态从所述第一基站移动到所述第二基站时，进行位置更新，并在接收所述第二基站发送的位置更新确认消息后进入空闲态；
所述第一网关在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知，所述第一移动性管理 实体用于管理所述第一基站和所述第一网关；
所述第一移动性管理实体从所述第一网关接收所述用户设备的下行数据通知，并在接收所述用户设备的下行数据通知后寻呼所述用户设备；
所述用户设备响应所述第一移动性管理实体的寻呼。
结合第八方面的第九种可能的实现方式，在第十种可能的实现方式中，
所述第一网关在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知之前，所述方法还包括：
所述第一网关缓存下行数据；
所述用户设备响应所述第一移动性管理实体的寻呼之后，所述方法还包括：
所述第一移动性管理实体在所述用户设备响应寻呼后向所述第一网关请求所述下行数据，接收所述第一网关发送的所述下行数据，并将从所述第一网关接收的所述下行数据发送至所述用户设备。
结合第八方面的第十种可能的实现方式，在第十一种可能的实现方式中，
所述第一网关在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知之前，所述方法还包括：
所述第一网关缓存下行数据；
所述用户设备响应所述第一移动性管理实体的寻呼之后，所述方法还包括：
所述第一移动性管理实体建立下行数据转发隧道；
所述第一网关通过所述下行数据转发隧道向所述用户设备发送所述下行数据。
结合第八方面，在第十二种可能的实现方式中，
所述用户设备在空闲态从所述第一基站移动到所述第二基站，进行位置更新，并在接收所述第二基站发送的位置更新确认消息后进入空闲态；
第二移动性管理实体在所述用户设备进入空闲态后向第一移动性管理实体注册所述用户设备的下行数据通知，所述第二移动性管理实体用于管理所述第二基站和所述第二网关，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
所述第一移动性管理实体，在确认所述第二移动性管理实体的注册后，将所述用户设备的下行数据通知发送至所述第二移动性管理实体；
所述第二移动性管理实体，在接收所述用户设备的下行数据通知后寻呼所述用户设备；
所述用户设备响应所述第二移动性管理实体的寻呼。
结合第八方面的第十二种可能的实现方式，在第十三种可能的实现方式中，
所述第一网关在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知之前，所述方法还包括：
所述第一网关缓存下行数据；
所述用户设备响应所述第一移动性管理实体的寻呼之后，所述方法还包括：
所述第二移动性管理实体通过所述第一移动性管理实体请求所述下行数据；
所述第一移动性管理实体，将所述第一网关发送的所述下行数据转发至所述第二移动性管理实体；
所述第二移动性管理实体，将所述下行数据发送至所述用户设备。
结合第八方面的第十二种可能的实现方式，在第十四种可能的实现方式中，
所述第一网关在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知之前，所述方法还包括：
所述第一网关缓存下行数据；
所述用户设备响应所述第一移动性管理实体的寻呼之后，所述 方法还包括：
所述第二移动性管理实体，通过所述第一移动性管理实体建立下行数据转发隧道；
所述第一网关，通过所述下行数据转发隧道向所述用户设备发送所述下行数据。
结合第八方面，在第十五种可能的实现方式中，所述方法还包括：
所述第一网关获取所述用户设备的计费规则及所述用户设备的可用额度；
所述第一网关在用户设备通过所述第一子流与所述通信对端进行通信时，根据所述用户设备的计费规则对所述用户设备的可用额度进行扣减；
所述第一网关向在线计费系统发送所述用户设备的可用额度余额。
结合第八方面，在第十六种可能的实现方式中，所述方法还包括：
所述第一网关向所述第一移动性管理实体发送所述用户设备在所述第一网关的话单；
所述第一移动性管理实体将所述用户设备在所述第一网关的话单发送至离线计费系统。
第九方面，一种移动性管理方法，应用于用户设备，
当所述用户设备与第一基站连接时，所述用户设备建立与通信对端的第一子流，所述第一子流为所述用户设备使用第一网际互连协议IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
在所述用户设备由所述第一基站向所述第二基站切换时，当第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，所述第二IP地址为所述第二网关为所述用户设备分配的IP 地址；
所述用户设备与所述通信对端建立第二子流，所述第二子流为所述用户设备使用所述第二IP地址与所述通信对端建立的子流；
所述用户设备在所述第二子流建立完成后，撤销所述第一子流。
结合第九方面，在第一种可能的实现方式中，
所述用户设备在所述撤销所述第一子流之后，释放所述第一IP地址，并指示所述第一网关释放所述第一IP地址。
结合第九方面，在第二种可能的实现方式中，
所述用户设备由所述第一基站向所述第二基站切换，包括：所述用户设备在与所述通信对端正在进行通信的过程中由所述第一基站向所述第二基站切换；
所述当所述第二网关与所述第一网关不是同一网关时，所述方法还包括：
所述用户设备建立与所述通信对端的数据转发隧道，并通过所述数据转发隧道传输所述第一子流的数据，所述数据转发隧道为所述第一基站及所述第二基站之间的数据转发通道。
结合第九方面的第二种可能的实现方式，在第三种可能的实现方式中，所述数据转发隧道，包括：
下行数据转发隧道或上行数据转发隧道；
或者，下行数据转发隧道和上行数据转发隧道。
结合第九方面的第二种可能的实现方式或者第九方面的第三种可能的实现方式，在第四种可能的实现方式中，
所述撤销所述第一子流之后，所述方法还包括：
所述用户设备释放所述第一IP地址，并指示第一网关释放第一IP地址；
所述用户设备向所述第二基站指示所述第一子流已经撤销，以便于所述第二基站删除所述数据转发隧道。
结合第九方面，在第五种可能的实现方式中，
所述当第二网关与所述第一网关不是同一网关时，所述用户设 备获取第二IP地址，包括：
当所述用户设备与第一基站连接时，接收所述第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关；
当所述用户设备由所述第一基站向所述第二基站切换时，接收所述第二基站发送的第二网关标识，所述第二网关标识用于指示第二网关；
如果所述第二网关标识与所述第一网关标识不同，则所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
结合第九方面，在第六种可能的实现方式中，
所述当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，包括：
当所述用户设备由所述第一基站向所述第二基站切换时，将所述第一IP地址或第一网关标识发送至第二移动性管理实体，以便于所述第二移动性管理实体根据所述第一IP地址或第一网关标识确定所述第二网关与所述第一网关是否为同一网关，并在所述第二网关与所述第一网关不是同一网关时向所述第二网关为所述用户设备申请分配IP地址，将从所述第二网关接收的所述第二IP地址发送至所述用户设备，所述第一网关标识用于指示第一网关，所述第二移动性管理实体用于管理所述第二基站和所述第二网关。
结合第九方面，在第七种可能的实现方式中，
所述当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，包括：
当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备将第二网关标识发送至所述第一基站，以便于所述第一基站确定所述第二网关与所述第一网关是否为同一网关，所述第二网关标识用于指示第二网关；
所述用户设备接收所述第一基站发送的判断指示消息，向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的 所述第二IP地址，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关。
结合第九方面，在第八种可能的实现方式中，
所述用户设备由所述第一基站向所述第二基站切换，包括：所述用户设备在空闲态从所述第一基站移动到所述第二基站，向第二移动性管理实体发送位置更新请求消息，并接收所述第二移动性管理实体发送的位置更新确认消息，所述第二移动性管理实体用于管理所述第二基站和所述第二网关。
结合第九方面的第八种可能的实现方式，在第九种可能的实现方式中，
所述接收所述第二移动性管理实体发送的位置更新确认消息之后，所述方法还包括：
所述用户设备进入空闲态；
所述用户设备在空闲态接收第一移动性管理实体的寻呼后，响应所述第一移动性管理实体的寻呼，并接收所述第一网关缓存并转发的下行数据，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
或者，所述用户设备在空闲态接收第二移动性管理实体的寻呼后，响应所述第二移动性管理实体的寻呼，并接收所述第一网关缓存并转发的下行数据，所述第一移动性管理实体用于管理所述第一基站和所述第一网关。
第十方面，一种移动性管理方法，应用于第一基站，当所述用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，所述第一基站向所述第二基站发送数据转发隧道的建立请求消息，并接收所述第二基站发送的所述数据转发隧道的建立确认消息，
所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据 转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
在接收所述第二基站发送的所述数据转发隧道的删除请求消息后，向所述第二基站发送所述数据转发隧道的删除确认消息，并释放所述数据转发隧道；
在释放所述数据转发隧道后，指示所述第一网关释放所述第一IP地址。
结合第十方面，在第一种可能的实现方式中，
所述第一基站向所述第二基站发送数据转发隧道的建立请求消息之前，所述方法还包括：
所述第一基站接收所述用户设备发送的第二网关标识，所述第二网关标识用于指示第二网关；
所述第一基站根据所述第二网关标识确定所述第二网关与所述第一网关是否为同一网关；
当所述第二网关与所述第一网关不是同一网关时，所述第一基站向所述用户设备发送判断指示消息，以便于所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址，其中，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关。
第十一方面，一种移动性管理方法，应用于第二基站，
当所述用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，所述第二基站接收所述第一基站发送的数据转发隧道的建立请求消息，并向所述第一基站发送所述数据转发隧道的建立确认消息，
所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
在所述第一子流撤消后，向所述第一基站发送所述数据转发隧道的删除请求消息，并接收所述第一基站发送的所述数据转发隧道的删除确认消息；
在接收所述第一基站发送的所述数据转发隧道的删除确认消息后，释放所述数据转发隧道。
本发明的实施例提供的移动性管理的方法、装置及系统，通过第一网关及第二网关为用户设备动态分配IP地址。现有技术中通过移动网络架构中的数据汇聚式的锚点设备统一为用户设备分配IP地址，锚点设备压力巨大，一旦锚点设备出现问题，就会影响整个业务网络的正常运行，引起用户设备业务中断。本发明的实施例提供的移动性管理的方法、装置及系统，当用户设备由第一网关向第二网关切换时，用户设备与通信对端，使用第二IP地址建立第二子流，在第二子流建立之前，用户设备与通信对端通过第一子流进行通信，在第二子流建立之后，撤销第一子流。从而在不通过锚点设备的情况下有效保证用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对 实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明的实施例提供的一种移动性管理系统的结构示意图；
图2为本发明的实施例提供的一种用户设备的结构示意图；
图3为本发明的实施例提供的一种第一基站的结构示意图；
图4为本发明的实施例提供的一种第二基站的结构示意图；
图5为本发明的实施例提供的另一种用户设备的结构示意图；
图6为本发明的实施例提供的另一种第一基站的结构示意图；
图7为本发明的另一实施例提供的另一种第二基站的结构示意图；
图8为本发明的实施例提供的一种移动性管理方法的流程示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
本发明的实施例提供一种移动性管理的方法、装置及系统。以LTE(Long Term Evolution，长期演进)蜂窝网络为例进行说明。LTE蜂窝网络包括：第一基站、第二基站、第一网关、第二网关、第一移动性管理实体(Mobility Management Entity，MME)、第二移动性管理实体、用户设备及通信对端，其中第一基站与第一网关连接，第二基站与第二网关连接，第一移动性管理实体用于管理所述第一基站和所述第一网关，第二移动性管理实体用于管理所述第二基站和所述第二网关。需要说明的是，在实际的应用场景中，一个网关可以连接多个基站，本发明实施例的应用场景中，第一基站为与第一网关连接的基站，第二基站为与第二网关的基站，且第一网关与第二网关不是同一个网关。当用户设备与第一基站连接时，第一网关为用户设备分配第一IP地址，用户设备使用第一IP地址与通信对端 建立TCP(Transmission Control Protocol传输控制协议)连接。当用户设备由第一基站向第二基站切换时，由于第二网关与第一网关不是同一网关，第一IP地址不属于第二网关的管理范围，因此第二网关需要为用户设备分配新的IP地址，用户设备使用新的IP地址与通信对端建立通信。本发明的实施例中第二网关为用户设备分配的IP地址为第二IP地址。用户设备获取第二IP地址后，使用第二IP地址与通信对端建立TCP连接。用户设备使用第一IP地址与通信对端建立的TCP连接为第一子流，用户设备使用第二IP地址与通信对端建立的TCP连接为第二子流。本发明的实施例以通过MPTCP技术建立MPTCP子流的应用场景为例，对移动性管理的系统、装置和方法进行说明。
本发明的实施例提供一种移动性管理系统100，参照图1，包括用户设备1001，第一基站1002，第二基站1003，第一网关1004，第二网关1005及通信对端1006，第一基站1002与第一网关1004连接，第二基站1003与第二网关1005连接。可选的，移动性管理系统100还包括第一移动性管理实体1007及第二移动性管理实体1008，第一移动性管理实体1007用于管理第一基站1002和第一网关1004，第二移动性管理实体1008用于管理第二基站1003和第二网关1005。
其中，用户设备1001，用于建立与通信对端1006的第一MPTCP(Multi-Path Transmission Control Protocol，多路径传输控制协议)子流，第一MPTCP子流为用户设备1001使用第一网际互连协议IP地址与通信对端1006建立的MPTCP子流，第一IP地址是第一网关1004为用户设备1001分配的IP地址。可选的，通信对端1006可以是支持MPTCP技术的服务器、用户终端或者MPTCP代理及服务器，第一网关及第二网关可以是分布式的本地网关(Local Gateway)。
当用户设备1001由第一基站1002向第二基站1003切换时，用户设备1001，还用于当第二网关1005与第一网关1004不是同一网关时获取第二IP地址，第二IP地址为第二网关1005为用户设备 1001分配的IP地址。
用户设备1001，还用于在获取第二IP地址后与通信对端1006建立第二MPTCP子流，第二MPTCP子流为用户设备1001使用第二IP地址与通信对端1006建立的MPTCP子流。
通信对端1006，用于在第二MPTCP子流建立之后，撤销第一MPTCP子流。
第一网关1004，还用于在第一MPTCP子流撤销之后释放第一IP地址。第一网关1004释放第一IP地址，即解除用第一IP地址与用户设备1001之间的绑定。第一网关1004释放第一IP地址后，可以将第一IP地址分配给其他用户设备。
现有技术中的移动性管理系统通过移动网络架构中的数据汇聚式的锚点设备统一为用户设备分配IP地址，锚点设备压力巨大，一旦锚点设备出现问题，就会影响整个业务网络的正常运行，引起用户设备业务中断。本发明的实施例提供的移动性管理系统，通过第一网关及第二网关为用户设备动态分配IP地址，当用户设备由第一网关向第二网关切换时，用户设备与通信对端通过MPTCP技术，使用第二IP地址建立第二MPTCP子流，在第二MPTCP子流建立之前，用户设备与通信对端通过第一MPTCP子流进行通信，在第二MPTCP子流建立之后，撤销第一MPTCP子流。从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
可选的，用户设备1001，还用于在撤销第一MPTCP子流之后，释放第一IP地址，并向第一网关1004发送释放第一IP地址的指示消息，以便于第一网关1004在接收用户设备1001发送的释放第一IP地址的指示消息后，释放第一IP地址。具体可选的，用户设备1001可以通过第一基站1002或者第一移动性管理实体1007将释放第一IP地址的指示消息发送至第一网关1004。
用户设备1001释放第一IP地址，即不再占用第一IP地址。
可选的，第一基站1002及第二基站1003，用于建立数据转发隧道，数据转发隧道为第一基站1002及第二基站1003之间的数据 转发通道。
用户设备1001及通信对端1006，还用于通过数据转发隧道传输第一MPTCP子流的数据。
可选的，数据转发隧道包括下行数据转发隧道或上行数据转发隧道，或者，数据转发隧道包括下行数据转发隧道和上行数据转发隧道。
可选的，第二基站1003，还用于在第一MPTCP子流撤销后，删除数据转发隧道。
可选的，当第二网关1005与第一网关1004不是同一网关时获取第二IP地址，包括：
当用户设备1001与第一基站1002连接时，接收第一基站1002发送的第一网关标识，具体的，网关标识可以是本地网络(Local Network)ID，或者，网关标识也可以是本地网关(Local Gateway)ID。
当用户设备1001由第一基站1002向第二基站1003切换时，接收第二基站1003发送的第二网关标识。
如果第二网关标识与第一网关标识不同，则用户设备1001向第二网关1005发送获取IP地址的请求消息，并接收第二网关1005发送的第二IP地址。
可选的，当第二网关1005与第一网关1004不是同一网关时获取第二IP地址，包括：
当用户设备1001由第一基站1002向第二基站1003切换时，用户设备1001将第一IP地址或第一网关标识发送至第二移动性管理实体1008。
第二移动性管理实体1008确定第一IP地址是否为第二网关1005为用户设备1001分配的IP地址，或第一网关标识是否与第二网关标识相同。
如果第一IP地址不是第二网关1005为用户设备1001分配的IP地址，或第一网关标识与第二网关标识不同，则第二移动性管理实体1008向第二网关1005为用户设备1001申请分配IP地址，并将 从第二网关1005接收的第二IP地址发送至用户设备1001。进一步可选的，当第一网关1004与第二网关1005由同一移动性管理实体进行管理时，第一移动性管理实体1007和第二移动性管理实体1008可以是同一移动性管理实体。
可选的，当第二网关1005与第一网关1004不是同一网关时获取第二IP地址，包括：
当用户设备1001由第一基站1002向第二基站1003切换时，用户设备1001将第二网关标识发送至第一基站1002。
如果第二网关标识与第一网关标识不同，则第一基站1002向用户设备1001发送判断指示消息，判断指示消息用于指示第二网关1005与第一网关1004不是同一网关。
用户设备1001在接收判断指示消息后向第二网关1005发送获取IP地址的请求消息，并接收第二网关1005发送的第二IP地址。
可选的，用户设备1001，还用于当用户设备1001在空闲态由第一基站1002向第二基站1003切换时，向第二移动性管理实体1008发送位置更新请求消息。
第二移动性管理实体1008，用于向所述用户设备发送位置更新确认消息。
可选的，用户设备1001，在空闲态从所述第一基站移动到所述第二基站时，在连接第二基站1003完成位置更新之后，进入空闲态。
第一移动性管理实体1006，还用于在用户设备1001进入空闲态后接收第一网关1004发送的用户设备1001的下行数据通知。
第一移动性管理实体1006，还用于从第一网关1004接收用户设备1001的下行数据通知，并在接收用户设备1001的下行数据通知后寻呼用户设备1001。
用户设备1001，还用于响应第一移动性管理实体1006的寻呼。
可选的，第一网关1004，还用于缓存下行数据。
第一移动性管理实体1006，还用于在用户设备1001响应寻呼后向第一网关1004请求下行数据，接收第一网关1004发送的下行数据，并将从第一网关1004接收的下行数据发送至用户设备1001。
可选的，第一移动性管理实体1006，还用于在用户设备1001响应寻呼后建立下行数据转发隧道；
第一网关1004，还用于通过下行数据转发隧道向用户设备1001发送下行数据。
可选的，用户设备1001，在空闲态从所述第一基站移动到所述第二基站时，在连接第二基站1003完成位置更新之后，进入空闲态。
第二移动性管理实体1007，还用于向第一移动性管理实体1006注册用户设备1001的下行数据通知。
第一网关1004，还用于在用户设备1001进入空闲态后向第一移动性管理实体1006发送用户设备1001的下行数据通知。
第一移动性管理实体1006，还用于在确认第一移动性管理实体1006的注册后，将用户设备1001的下行数据通知发送至第二移动性管理实体1007。
第二移动性管理实体1007，还用于在接收用户设备1001的下行数据通知后寻呼用户设备1001。
用户设备1001，还用于响应第二移动性管理实体1007的寻呼。
可选的，第二移动性管理实体1007，还用于在用户设备1001响应寻呼后通过第一移动性管理实体1006请求下行数据。
第一移动性管理实体1006，还用于将第一网关1004发送的下行数据转发至第二移动性管理实体1007。
第二移动性管理实体1007，还用于将下行数据发送至用户设备1001。
可选的，第二移动性管理实体1007，还用于在用户设备1001响应寻呼后通过第一移动性管理实体1006建立下行数据转发隧道。
第一网关1004，还用于通过下行数据转发隧道向用户设备1001发送下行数据。可选的，下行数据转发隧道可以是第一网关1004与第二网关1005之间的数据转发隧道，此时第一网关1004通过下行数据转发隧道将下行数据发送至第二网关1005，第二网关1005通过第二基站1003将下行数据发送至用户设备1001。或者，下行数据转发隧道也可以是第一网关1004与第二基站1003之间的数据转发隧道，此时第一网关1004将下行数据通过数据转发隧道发送至第二基站1003，由第二基站1003将下行数据发送至用户设备1001。
可选的，移动性管理系统100还包括：在线计费系统(OCS，Online Charging System)1009及策略和计费规则功能(PCRF，Policy Control and Charging Rule Function)1010，
第一移动性管理实体1006，还用于从线计费系统1009获取用户设备1001的可用额度，并将用户设备1001的可用额度发送至第一网关1004。
第一移动性管理实体1006，还用于从策略和计费规则功能1010获取用户设备1001的计费规则，并将用户设备1001的计费规则发送至第一网关1004。
第一网关1004，还用于根据用户设备1001的计费规则对用户设备1001的可用额度进行扣减，并向在线计费系统1009发送用户设备1001的可用额度余额。
可选的，移动性管理系统100还包括：离线计费系统(OFCS，Off-line Charging System)1011。
第一网关1004，还用于向第一移动性管理实体1006发送用户设备1001在第一网关1004的话单。
第一移动性管理实体1006，还用于将用户设备1001在第一网关1004的话单发送至离线计费系统1011。
本发明的实施例提供的移动性管理系统，通过第一网关及第二网关为用户设备动态分配IP地址。现有技术中通过移动网络架构中的数据汇聚式的锚点设备统一为用户设备分配IP地址，锚点设备压力巨大， 一旦锚点设备出现问题，就会影响整个业务网络的正常运行，引起用户设备业务中断。本发明的实施例提供的移动性管理系统，当用户设备由第一网关向第二网关切换时，用户设备与通信对端通过MPTCP技术，使用第二IP地址建立第二MPTCP子流，在第二MPTCP子流建立之前，用户设备与通信对端通过第一MPTCP子流进行通信，在第二MPTCP子流建立之后，撤销第一MPTCP子流。从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
本发明的实施例提供一种用户设备20，参照图2所示，包括处理器2001、存储器2002及总线2003，处理器2001及存储器2002通过总线2003相互连接。可选的，该用户设备20还包括接收器2004及发送器2005，该接收器2004及发送器2005通过总线2003与处理器2001和存储器2002相互连接。
该总线2003可以是ISA(Industry Standard Architecture，工业标准体系结构)总线、PCI(Peripheral Component，外部设备互连)总线或EISA(Extended Industry Standard Architecture，扩展工业标准体系结构)总线等。该总线2003可以分为地址总线、数据总线、控制总线等。为便于表示，图2中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。其中：
存储器2002用于执行本发明方案的应用程序代码，执行本发明方案的应用程序代码保存在存储器中，并由处理器2001来控制执行。
该存储器可以是只读存储器ROM或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器EEPROM、只读光盘CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介 质，但不限于此。这些存储器通过总线与处理器相连接。
处理器2001可能是一个中央处理器2001(Central Processing Unit，简称为CPU)，或者是特定集成电路(Application Specific Integrated Circuit，简称为ASIC)，或者是被配置成实施本发明实施例的一个或多个集成电路。
处理器2001，用于调用存储器2002中的程序代码，在一种可能的实施方式中，当上述应用程序被所述处理器2001执行时，实现如下功能。
处理器2001，用于建立与通信对端的第一多路径传输控制协议MPTCP子流，第一MPTCP子流为用户设备20使用第一网际互连协议IP地址与通信对端建立的MPTCP子流，第一IP地址为第一网关为用户设备20分配的网际互联协议IP地址，第一网关与第一基站连接。
处理器2001，还用于获取第二IP地址，第二IP地址为第二网关为用户设备20分配的IP地址。
处理器2001，还用于与通信对端建立第二MPTCP子流，第二MPTCP子流为用户设备20使用第二IP地址与通信对端建立的MPTCP子流。
处理器2001，还用于撤销第一MPTCP子流。
本发明的实施例提供的用户设备，由第一网关向第二网关切换时，获取IP地址，与通信对端通过MPTCP技术，使用第二IP地址建立第二MPTCP子流，在第二MPTCP子流建立之前，用户设备与通信对端通过第一MPTCP子流进行通信，在第二MPTCP子流建立之后，撤销第一MPTCP子流。从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
可选的，处理器2001，还用于在撤销第一MPTCP子流之后，释放第一IP地址，并生成释放第一IP地址的指示消息，其中释放第一IP地址的指示消息用于指示第一网关释放第一IP地址。
发送器2005，用于向第一网关发送释放第一IP地址的指示消 息。具体可选的，发送器2005可以通过第一基站或者第一移动性管理实体将释放第一IP地址的指示消息发送至第一网关。
可选的，处理器2001，还用于通过数据转发隧道传输第一MPTCP子流的数据，数据转发隧道为第一基站及第二基站之间的数据转发通道。
可选的，数据转发隧道包括下行数据转发隧道或上行数据转发隧道，或者数据转发隧道包括下行数据转发隧道和上行数据转发隧道。
可选的，处理器2001，还用于释放第一IP地址。
处理器2001，还用于生成指示第一MPTCP子流已经撤销的指示消息。
发送器2005，还用于向第二基站发送指示所述第一MPTCP子流已经撤销的指示消息，以便于第二基站删除数据转发隧道。
可选的，接收器2004，用于接收第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关。
接收器2004，还用于接收第二基站发送的第二网关标识，第二网关标识用于指示第二网关。
处理器2001，还用于判断第二网关标识与第一网关标识是否相同，如果第二网关标识与第一网关标识不同，则生成获取IP地址的请求消息。
发送器2005，用于向第二网关发送获取IP地址的请求消息。
接收器2004，还用于接收第二网关发送的第二IP地址。
可选的，发送器2005，还用于当用户设备20由第一基站向第二基站切换时，将第一IP地址或第一网关标识发送至第二移动性管理实体，以便于第二移动性管理实体根据第一IP地址或第一网关标识确定第二网关与第一网关是否为同一网关，并在第二网关与第一网关不是同一网关时向第二网关为用户设备20申请分配IP地址，将从第二网关接收的第二IP地址发送至用户设备20，第二移动性管理实体用于管理所述第二基站和所述第二网关。
可选的，接收器2004，还用于接收第二移动性管理实体发送的第二IP地址。
可选的，发送器2005，还用于当用户设备20由第一基站向第二基站切换时，将第二网关标识发送至第一基站，以便于第一基站确定第二网关与第一网关是否为同一网关。
接收器2004，还用于接收第一基站发送的判断指示消息，判断指示消息用于指示第二网关与第一网关不是同一网关。
处理器2001，还用于生成获取IP地址的请求消息。
发送器2005，还用于向第二网关发送获取IP地址的请求消息。
接收器2004，还用于接收第二网关发送的第二IP地址。
可选的，处理器2001还用于当用户设备20在空闲态从所述第一基站移动到所述第二基站时，生成位置更新请求消息。
发送器2005，还用于向第二移动性管理实体发送位置更新请求消息，第二移动性管理实体用于管理所述第二基站和所述第二网关。
接收器2004，还用于接收第二移动性管理实体发送的位置更新确认消息。
可选的，处理器2001，还用于控制用户设备20进入空闲态。
接收器2004，还用于当用户设备20在空闲态时接收第一移动性管理实体的寻呼，第一移动性管理实体用于管理所述第一基站和所述第一网关。
处理器2001，还用于生成寻呼响应消息。
发送器2005，还用于向第一移动性管理实体发送寻呼响应消息。
接收器2004，还用于接收第一网关缓存并转发的下行数据。
接收器2004，还用于当用户设备20在空闲态时接收第二移动性管理实体的寻呼，第一移动性管理实体用于管理所述第一基站和所述第一网关。
发送器2005，还用于向第二移动性管理实体发送寻呼响应消息。
可选的，发送器2005，还用于接收下行数据。
本发明的实施例提供的用户设备，由第一网关向第二网关切换时，获取IP地址，与通信对端通过MPTCP技术，使用第二IP地址建立第二MPTCP子流，在第二MPTCP子流建立之前，用户设备与通信对端通过第一MPTCP子流进行通信，在第二MPTCP子流建立之后，撤销第一MPTCP子流。从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
本发明的实施例提供一种第一基站30，参照图3所示，包括处理器3001、存储器3002及总线3003，处理器3001、存储器3002、接收器3004及发送器3005通过总线3003相互连接。
该总线3003可以是ISA(Industry Standard Architecture，工业标准体系结构)总线、PCI(Peripheral Component，外部设备互连)总线或EISA(Extended Industry Standard Architecture，扩展工业标准体系结构)总线等。该总线3003可以分为地址总线、数据总线、控制总线等。为便于表示，图2中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。其中：
存储器3002用于执行本发明方案的应用程序代码，执行本发明方案的应用程序代码保存在存储器中，并由处理器3001来控制执行。
该存储器可以是只读存储器ROM或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器EEPROM、只读光盘CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。这些存储器通过总线与处理器相连接。
处理器3001可能是一个中央处理器3001(Central Processing Unit，简称为CPU)，或者是特定集成电路(Application Specific Integrated Circuit，简称为ASIC)，或者是被配置成实施本发明实施例的一个或多个集成电路。
处理器3001，用于调用存储器3002中的程序代码，在一种可能的实施方式中，当上述应用程序被所述处理器3001执行时，实现如下功能。
处理器3001，用于当用户设备由第一基站30向第二基站切换时，在第二多路径传输控制协议MPTCP子流建立之前，生成数据转发隧道的建立请求消息，第二MPTCP子流为用户设备使用第二网际互联协议IP地址与通信对端建立的MPTCP子流，第二IP地址为第二网关为用户设备分配的IP地址，第二网关与第二基站连接，数据转发隧道为第一基站30与第二基站之间的数据转发通道，数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者数据转发隧道包括下行数据转发隧道和上行数据转发隧道，数据转发通道用于传输第一MPTCP子流的数据，第一MPTCP子流为用户设备在由第一基站30向第二基站切换之前，使用第一IP地址与通信对端建立的MPTCP子流，第一IP地址为第一网关为用户设备分配的IP地址，第一网关与第一基站30连接。
发送器3005，用于向第二基站发送数据转发隧道的建立请求消息。
接收器3004，用于接收第二基站发送的数据转发隧道的建立确认消息。
接收器3004，还用于接收第二基站发送的数据转发隧道的删除请求消息。
发送器3005，还用于向第二基站发送数据转发隧道的删除确认消息。
处理器3001，还用于释放数据转发隧道，并生成第一IP释放指示消息。
发送器3005，还用于向第一网关发送第一IP释放指示消息。
可选的，接收器3004，还用于接收用户设备发送的第二网关标识。
处理器3001，还用于根据第二网关标识确定第二网关与第一网关是否为同一网关，当第二网关与第一网关不是同一网关时，生成判断指示消息，判断指示消息用于指示第二网关与第一网关不是同一网关。
发送器3005，还用于向用户设备发送判断指示消息，以便于用户设备向第二网关发送获取IP地址的请求消息，并接收第二网关发送的第二IP地址。
本发明的实施例提供的第一基站，当用户设备由第一网关向第二网关切换时，确定第一网关与第二网关不是同一网关，并在第二MPTCP子流建立之前，建立与第二基站的数据转发隧道，用于传输第一MPTCP子流的数据，从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
本发明的实施例提供一种第二基站40，参照图4所示，包括处理器4001、存储器4002及总线4003，处理器4001、存储器4002、接收器4004及发送器4005通过总线4003相互连接。
该总线4003可以是ISA(Industry Standard Architecture，工业标准体系结构)总线、PCI(Peripheral Component，外部设备互连)总线或EISA(Extended Industry Standard Architecture，扩展工业标准体系结构)总线等。该总线4003可以分为地址总线、数据总线、控制总线等。为便于表示，图2中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。其中：
存储器4002用于执行本发明方案的应用程序代码，执行本发明方案的应用程序代码保存在存储器中，并由处理器4001来控制执行。
该存储器可以是只读存储器ROM或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器RAM或者可存储信息 和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器EEPROM、只读光盘CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。这些存储器通过总线与处理器相连接。
处理器4001可能是一个中央处理器4001(Central Processing Unit，简称为CPU)，或者是特定集成电路(Application Specific Integrated Circuit，简称为ASIC)，或者是被配置成实施本发明实施例的一个或多个集成电路。
处理器4001，用于调用存储器4002中的程序代码，在一种可能的实施方式中，当上述应用程序被所述处理器4001执行时，实现如下功能。
接收器4004，用于当用户设备由第一基站向第二基站40切换时，在第二多路径传输控制协议MPTCP子流建立之前，接收第一基站发送的数据转发隧道的建立请求消息，第二MPTCP子流为用户设备使用第二网际互联协议IP地址与通信对端建立的MPTCP子流，第二IP地址为第二网关为用户设备分配的IP地址，第二网关与第二基站40连接，数据转发隧道为第一基站与第二基站40之间的数据转发通道，数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者数据转发隧道包括下行数据转发隧道和上行数据转发隧道，数据转发通道用于传输第一MPTCP子流的数据，第一MPTCP子流为用户设备在由第一基站向第二基站40切换之前，使用第一IP地址与通信对端建立的MPTCP子流，第一IP地址为第一网关为用户设备分配的IP地址，第一网关与第一基站连接。
处理器4001，用于生成数据转发隧道的建立确认消息。
发送器4005，用于向第一基站发送数据转发隧道的建立确认消息。
处理器4001，还用于在第一MPTCP子流撤消后生成数据转发 隧道的删除请求消息。
发送器4005，还用于，向第一基站发送数据转发隧道的删除请求消息。
接收器4004，还用于接收第一基站发送的数据转发隧道的删除确认消息。
处理器4001，还用于释放数据转发隧道。
本发明的实施例提供的第二基站，当用户设备由第一网关向第二网关切换时，在第二MPTCP子流建立之前，建立与第一基站的数据转发隧道，用于传输第一MPTCP子流的数据，从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
本发明的实施例提供另一种用户设备50，参照图5所示，包括多路径控制单元501及收发单元502。
多路径控制单元501，用于当用户设备50与第一基站连接时，建立与通信对端的第一多路径传输控制协议MPTCP子流，第一MPTCP子流为用户设备50使用第一网际互连协议IP地址与通信对端建立的MPTCP子流，第一网际互联协议IP地址为第一网关为用户设备50分配的IP地址，第一网关与第一基站连接。
收发单元502，用于获取第二IP地址，第二IP地址为第二网关为用户设备50分配的IP地址。
多路径控制单元501，还用于与通信对端建立第二MPTCP子流，第二MPTCP子流为用户设备50使用第二IP地址与通信对端建立的MPTCP子流。
多路径控制单元501，还用于在第二MPTCP子流建立完成后，撤销第一MPTCP子流。
可选的，多路径控制单元501，还用于在撤销第一子流之后，释放第一IP地址，并生成释放第一IP地址的指示消息，其中，释放第一IP地址的指示消息用于指示第一网关释放第一IP地址。
收发单元502，还用于向第一网关发送释放第一IP地址的指示 消息。
可选的，收发单元502，还用于通过数据转发隧道传输第一MPTCP子流的数据，数据转发隧道为第一基站及第二基站之间的数据转发通道。
可选的，数据转发隧道包括下行数据转发隧道或上行数据转发隧道，或者，数据转发隧道包括下行数据转发隧道和上行数据转发隧道。
可选的，多路径控制单元501，还用于释放第一IP地址。
多路径控制单元501，还用于生成第一MPTCP子流已经撤销的指示消息。
收发单元502，还用于向第二基站发送第一MPTCP子流已经撤销的指示消息，以便于第二基站删除数据转发隧道。
可选的，收发单元502，还用于当用户设备50与第一基站连接时，接收第一基站发送的第一网关标识。
收发单元502，还用于当当用户设备50由第一基站向第二基站切换时，接收第二基站发送的第二网关标识。
多路径控制单元501，还用于判断第二网关标识与第一网关标识是否相同，如果第二网关标识与第一网关标识不同，则生成获取IP地址的请求消息。
收发单元502，还用于向第二网关发送获取IP地址的请求消息。
收发单元502，还用于接收第二网关发送的第二IP地址。
可选的，收发单元502，还用于当用户设备50由第一基站向第二基站切换时，将第一IP地址或第一网关标识发送至第二移动性管理实体，以便于第二移动性管理实体根据第一IP地址或第一网关标识确定第二网关与第一网关是否为同一网关，并在第二网关与第一网关不是同一网关时向第二网关为用户设备50申请分配IP地址，将从第二网关接收的第二IP地址发送至用户设备50，第二移动性管理实体用于管理所述第二基站和所述第二网关。
收发单元502，还用于接收第二移动性管理实体发送的第二IP地址。
可选的，收发单元502，还用于当用户设备50由第一基站向第二基站切换时，将第二网关标识发送至第一基站，以便于第一基站确定第二网关与第一网关是否为同一网关。
收发单元502，还用于接收第一基站发送的判断指示消息，判断指示消息用于指示第二网关与第一网关不是同一网关。
多路径控制单元501，还用于生成获取IP地址的请求消息。
收发单元502，还用于向第二网关发送获取IP地址的请求消息。
收发单元502，还用于接收第二网关发送的第二IP地址。
可选的，用户设备50还包括切换控制单元503，用于当用户设备50在空闲态从所述第一基站移动到所述第二基站时生成位置更新请求消息。
收发单元502，还用于向第二移动性管理实体发送位置更新请求消息。
收发单元502，还用于接收第二移动性管理实体发送的位置更新确认消息，第二移动性管理实体用于管理所述第二基站和所述第二网关。
可选的，多路径控制单元501，还用于控制用户设备50进入空闲态。
收发单元502，还用于当用户设备50在空闲态时接收第一移动性管理实体的寻呼，第一移动性管理实体用于管理所述第一基站和所述第一网关。
切换控制单元503，还用于响应第一移动性管理实体的寻呼。
收发单元502，还用于接收第一网关缓存并转发的下行数据。
收发单元502，还用于当用户设备50在空闲态时接收第二移动性管理实体的寻呼，第一移动性管理实体用于管理所述第一基站和所述第一网关。
切换控制单元503，还用于响应第二移动性管理实体的寻呼。
可选的，收发单元502，还用于接收下行数据。
本发明的实施例提供的用户设备，由第一网关向第二网关切换时，获取IP地址，与通信对端通过MPTCP技术，使用第二IP地址建立第二MPTCP子流，在第二MPTCP子流建立之前，用户设备与通信对端通过第一MPTCP子流进行通信，在第二MPTCP子流建立之后，撤销第一MPTCP子流。从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
本发明的实施例提供另一种第一基站60，参照图6所示，包括控制单元601、发送单元602及接收单元603。
控制单元601，用于当用户设备由第一基站60向第二基站切换时，在第二多路径传输控制协议MPTCP子流建立之前，生成数据转发隧道的建立请求消息，第二MPTCP子流为用户设备使用第二网际互联协议IP地址与通信对端建立的MPTCP子流，第二IP地址为第二网关为用户设备分配的IP地址，第二网关与第二基站连接，数据转发隧道为第一基站60与第二基站之间的数据转发通道，数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者数据转发隧道包括下行数据转发隧道和上行数据转发隧道，数据转发通道用于传输第一MPTCP子流的数据，第一MPTCP子流为用户设备在由第一基站60向第二基站切换之前，使用第一IP地址与通信对端建立的MPTCP子流，第一IP地址为第一网关为用户设备分配的IP地址，第一网关与第一基站60连接。
发送单元602，用于第二基站发送数据转发隧道的建立请求消息。
接收单元603，用于接收第二基站发送的数据转发隧道的建立确认消息。
接收单元603，还用于接收第二基站发送的数据转发隧道的删除请求消息。
控制单元601，还用于生成数据转发隧道的删除确认消息。
发送单元602，还用于向第二基站发送数据转发隧道的删除确认消息。
控制单元601，还用于释放数据转发隧道，并生成第一IP释放指示消息。
发送单元602，还用于向第一网关发送第一IP释放指示消息。
可选的，接收单元603，还用于接收用户设备发送的第二网关标识。
控制单元601，还用于根据第二网关标识确定第二网关与第一网关是否为同一网关，并在第二网关与第一网关不是同一网关时，生成判断指示消息，判断指示消息用于指示第二网关与第一网关不是同一网关。
发送单元602，还用于向用户设备发送判断指示消息，以便于用户设备向第二网关发送获取IP地址的请求消息，并接收第二网关发送的第二IP地址。
本发明的实施例提供的第一基站，当用户设备由第一网关向第二网关切换时，确定第一网关与第二网关不是同一网关，并在第二MPTCP子流建立之前，建立与第二基站的数据转发隧道，用于传输第一MPTCP子流的数据，从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
本发明的实施例提供另一种第二基站70，包括控制单元701、发送单元702及接收单元703。
接收单元703，用于当用户设备由第一基站向第二基站70切换时，在第二多路径传输控制协议MPTCP子流建立之前，接收第一基站发送的数据转发隧道的建立请求消息，第二MPTCP子流为用户设备使用第二网际互联协议IP地址与通信对端建立的MPTCP子流，第二IP地址为第二网关为用户设备分配的IP地址，第二网关与第二基站70连接，数据转发隧道为第一基站与第二基站70之间的数据转发通道，数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者数据转发隧道包括下行数据转发隧道和上行数据 转发隧道，数据转发通道用于传输第一MPTCP子流的数据，第一MPTCP子流为用户设备在由第一基站向第二基站70切换之前，使用第一IP地址与通信对端建立的MPTCP子流，第一IP地址为第一网关为用户设备分配的IP地址，第一网关与第一基站连接。
控制单元701，用于生成数据转发隧道的建立确认消息。
发送单元702，用于向第一基站发送数据转发隧道的建立确认消息。
控制单元701，还用于在第一MPTCP子流撤消后，生成数据转发隧道的删除请求消息。
发送单元702，还用于向第一基站发送数据转发隧道的删除请求消息。
接收单元703，还用于接收第一基站发送的数据转发隧道的删除确认消息。
控制单元701，还用于释放数据转发隧道。
本发明的实施例提供的第二基站，当用户设备由第一网关向第二网关切换时，在第二MPTCP子流建立之前，建立与第一基站的数据转发隧道，用于传输第一MPTCP子流的数据，从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
基于图1所对应的实施例，本发明的实施例提供一种移动性管理方法，应用于蜂窝网络中的移动性管理系统。移动性管理系统包括用户设备，第一基站，第二基站，第一网关，第二网关及通信对端，第一基站与第一网关连接，第二基站与第二网关连接。当用户设备通过第一网关与通信对端建立TCP(Transmission Control Protocol传输控制协议)连接时，由第一网关为用户设备分配IP地址，第一网关为用户设备分配IP地址为第一IP地址。当用户设备由第一基站向第二基站切换时，由于第二网关并不对第一网关分配的IP地址进行管理，用户设备不能使用第一网关分配的IP地址通过第二网关与通信对端建立TCP连接，因此第二网关为用户设备分配新的IP地址， 以使得用户设备使用新的IP地址与通信对端建立的TCP连接。第二网关为用户设备分配的新的IP地址为第二IP地址。用户设备使用第一IP地址与通信对端建立的TCP连接为第一子流，用户设备使用第二IP地址与通信对端建立的TCP连接为第二子流。本实施例以通过MPTCP(Multi-Path Transmission Control Protocol，多路径传输控制协议)技术建立MPTCP子流的应用场景为例，对移动性管理的方法进行说明。当然，本发明所提供的移动性管理方法同样适用于通过其他技术手段建立子流的应用场景，例如通过MPRTP(Multi-Path Real-time Transport Protocol，实时传输协议)技术建立子流。本发明对建立子流的具体技术手段不做限定。参照图8所示，本发明的实施例提供的移动性管理方法，包括以下步骤：
801、用户设备建立与通信对端的第一子流。
可选的，第一子流可以为第一MPTCP(Multi-Path Transmission Control Protocol，多路径传输控制协议)子流，第一MPTCP子流为用户设备使用第一网际互连协议IP地址与通信对端建立的MPTCP子流。第一IP(Internet Protocol，网络互连协议)地址是第一网关为用户设备分配的IP地址。MPTCP技术中，通过在TCP(Transmission Control Protocol，传输控制协议)/IP(Internet Protocol，网络互连协议)协议栈架构的socket(套接字)和TCP层之间，增加MPTCP层，由MPTCP层负责管理多个子TCP模块。通信双方可以使用不同的IP地址对，建立TCP子流连接，每个TCP子流即为一个MPTCP子流。
可选的，以LTE(Long Term Evolution，长期演进)无线蜂窝网络为例对本发明提供的移动性管理方法进行说明。其中，用户设备及通信对端可以是支持MPTCP技术的用户终端、服务器、或者MPTCP代理及服务器，第一网关及第二网关为分布式的本地网关。用户设备在接入第一基站后，从第一网关获取第一IP地址，并使用第一IP地址，通过MPTCP技术与通信对端建立第一MPTCP子流。
具体可选的，用户设备获取第一IP地址可以有两种方式。第一 种方式，用户设备向第一网关发送DHCP(Dynamic Host Configuration Protocol，动态主机配置协议)消息向第一网关请求IP地址，第一网关通过DHCP消息将第一IP地址发送至用户设备。第二种方式，用户设备向第一移动性管理实体发送NAS(Non Access Stratum，非接入层)消息请求IP地址，第一移动性管理实体通过NAS消息将第一网关为用户设备分配的第一IP地址发送至用户设备。用户设备获取第一IP地址后，通过MPTCP技术与通信对端建立第一MPTCP子流。具体的，用户设备向通信对端发送建立第一MPTCP子流的请求，通信对端在接收到建立第一MPTCP子流的请求后，向用户设备返回确认消息，用户设备在接收确认消息后，向通信终端发送第一MPTCP子流建立的确认消息，由此第一MPTCP子流建立完成。
802、在用户设备由第一基站向第二基站切换时，当第二网关与第一网关不是同一网关时，用户设备获取第二IP地址。
其中，第二IP地址为第二网关为用户设备分配的IP地址。如果第二网关与第一网关不是同一网关，则用户设备由第一基站向第二基站切换的过程中，需要从第二网关获取新的IP地址。在切换完成后，使用第二网关分配的第二IP地址与通信对端进行通信。
在一种具体的应用场景中，用户设备在由第一基站向第二基站切换之前，处于空闲态。可选的，用户设备在空闲态从第一基站移动到第二基站时，可以有两种获取第二IP地址的方式。
第一种获取第二IP地址的方式中，当用户设备与第一基站连接时，接收第一基站发送的第一网关标识，其中第一网关标识用于指示第一网关。当用户设备在空闲态从第一基站移动到第二基站并与第二基站连接时，接收第二基站发送的第二网关标识，其中第二网关标识用于指示第二网关。用户设备对第二网关标识及第一网关标识进行判断，如果第二网关标识与第一网关标识不同，则用户设备向第二网关发送获取IP地址的请求消息，第二网关根据上下文记录判断是否已经为用户设备分配了IP地址，如果已经为用户设备分配 了IP地址，则拒绝用户设备获取新IP地址的请求，并指示用户设备使用第二网关已经为用户设备分配的IP地址，如果第二网关没有为用户设备分配IP地址，则向用户设备发送第二IP地址，用户设备接收第二网关发送的第二IP地址，即完成第二IP地址的获取过程。
可选的，第一基站及第二基站可以将各自的网关标识通过广播发送至用户设备。网关标识可以是本地网络(Local Network)ID，或者，网关标识也可以是本地网关(Local Gateway)ID。获取IP地址的请求消息可以是DHCP请求。
第二种获取第二IP地址的方式中，在空闲态从第一基站移动到第二基站时，向第二移动性管理实体发送位置更新(TAU，Tracking Area Update)请求消息，并将第一IP地址或第一网关标识发送至第二移动性管理实体。第二移动性管理实体确定第一IP地址是否为第二网关为用户设备分配的IP地址，或第一网关标识是否与第二网关标识相同。如果第一IP地址不是第二网关为用户设备分配的IP地址，或第一网关标识与第二网关标识不同，则第二移动性管理实体确定第一网关与第二网关不是同一网关。
第二移动性管理实体确定第一网关与第二网关不是同一网关后，根据上下文记录判断第二网关是否已经为用户设备分配了IP地址，如果第二网关已经为用户设备分配了IP地址，则第二移动性管理实体拒绝用户设备获取新IP地址的请求，并指示用户设备使用第二网关已经为用户设备分配的IP地址，如果第二网关没有为用户设备分配IP地址，则第二移动性管理实体向第二网关为用户设备申请分配IP地址，并将从第二网关接收的第二IP地址发送至用户设备。可选的，第二移动性管理实体可以通过NAS消息向用户设备发送第二IP地址，进一步可选的，第二移动性管理实体将第二IP地址包括在位置更新确认(TAU Accept)消息中向用户设备发送，用户设备接收到第二移动性管理实体发送的第二IP地址，即完成第二IP地址的获取过程。第一网关与第二网关可以由同一移动性管理实体进 行管理，此时第一移动性管理实体和第二移动性管理实体可以是同一移动性管理实体。
可选的，当第二移动性管理实体确定第二网关与第一网关不是同一网关后，也可以指示用户设备向第二网关请求IP地址，完成第二IP地址的获取过程。
可选的，当第一网关与第二网关与同一移动性管理实体连接时，第一移动性管理实体和第二移动性管理实体为同一移动性管理实体。
803、用户设备在获取第二IP地址后与通信对端建立第二子流。
其中，第二MPTCP子流为用户设备使用第二IP地址与通信对端建立的MPTCP子流。MPTCP技术，在TCP(Transmission Control Protocol传输控制协议)/IP协议栈架构的socket(套接字)和TCP层之间增加MPTCP层，由MPTCP层负责管理多个子TCP模块，使得用户设备和通信对端可以使用不同的IP地址对，建立一条或者一条以上的MPTCP子流连接。用户设备在发往通信对端的TCP消息中设置关于MPTCP的选项，发起添加第二MPTCP子流的请求。具体的，用户设备通过设置MP_CAPABLE(Multipath Capable多路径可用)标识，向通信对端查询是否能够建立第二MP TCP子流，当接收到通信对端返回的MP_CAPABLE的ACK(Acknowledgement，确认)消息后，再使用第二IP地址向通信对端发送设置了MP_JOIN(Join Connection，子流接入)标识位的TCP消息，当用户设备接收到通信对端所发送的MP_JOIN的ACK消息，则第二MPTCP子流建立完成。
804、通信对端在第二子流建立之后，撤销第一子流。
第二MPTCP子流建立之后，用户设备和通信对端通过第二MPTCP子流进行通信，因此撤销第一MPTCP子流。
可选的，用户设备可以通过第二MPTCP子流向通信对端发送携带REMOVE_ADDR(Remove Address，移除地址)选项的TCP消息，向通信对端发送撤销第一MPTCP子流的请求，其中 REMOVE_ADDR选项中包括第一IP地址。
或者，用户设备通过第一MPTCP子流，向通信对端发送DSS(Data Sequence Signal，数据序列信息号)标识的F位为1的TCP消息，其中，DSS标识的F位为DATA_FIN位，DATA_FIN位置1代表数据传输完成，请求撤销第一MPTCP子流。
或者，用户设备通过第一MPTCP子流，向通信对端发送携带MP_FASTCLOSE(Multipath Fastclose，多路径快速关闭)选项的TCP消息，请求撤销第一MPTCP子流。
805、第一网关在第一子流撤销之后释放第一IP地址。
第一MPTCP子流撤销之后，用户设备释放第一IP地址，并指示第一网关释放第一IP地址。具体的，用户设备可以通过第一基站或者第一移动性管理实体将释放第一IP地址的指示消息发送至第一网关。
用户设备释放第一IP地址，即不再占用第一IP地址。第一网关释放第一IP地址，即解除用第一IP地址与用户设备之间的绑定。第一网关在释放第一IP地址后，可以将第一IP地址分配给其他用户设备。
可选的，用户设备在第一MPTCP子流撤销之后，同时释放RRC(Radio Resource Control无线资源控制协议)资源及第一IP地址，并进入空闲态。
本发明的实施例提供的移动性管理方法，通过第一网关及第二网关为用户设备动态分配IP地址。现有技术中通过移动网络架构中的数据汇聚式的锚点设备统一为用户设备分配IP地址，锚点设备压力巨大，一旦锚点设备出现问题，就会影响整个业务网络的正常运行，引起用户设备业务中断。本发明的实施例提供的移动性管理方法，当用户设备由第一网关向第二网关切换时，用户设备与通信对端通过MPTCP技术，使用第二IP地址建立第二MPTCP子流，在第二MPTCP子流建立之前，用户设备与通信对端通过第一MPTCP子流进行通信，在第二MPTCP子流建立之后，撤销第一MPTCP子流。从而保证了用户 设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
基于图8所对应的实施例，本发明的实施例提供另一种移动性管理方法，应用于蜂窝网络中的移动性管理系统。图8所对应的实施例中，用户设备在空闲态由第一基站向第二基站切换，在与第二基站连接后即获取第二IP地址。本实施例中用户设备在空闲态由第一基站向第二基站切换，在与第二基站连接后进入空闲态，当用户设备发起业务请求或者需要向用户设备发送下行数据时，用户设备才获取第二IP地址。本实施例中部分步骤与图8所对应的实施例中相应的步骤相同，此处对相同部分不再详述，具体步骤如下：
901、用户设备建立与通信对端的第一子流。
902、在用户设备由第一基站向第二基站切换时，当第二网关与第一网关不是同一网关时，用户设备获取第二IP地址。
在一种具体的应用场景中，用户设备在由第一基站向第二基站切换之前，处于空闲态。结合图8所对应的实施例中步骤802，用户设备在空闲态由第一基站向第二基站切换时，向第二移动性管理实体发送位置更新请求消息，同时将第一IP地址或第一网关标识发送至第二移动性管理实体。第二移动性管理实体根据第一IP地址或第一网关标确定第一网关及第二网关是否为统一网关，并确定是否需要为用户设备分配新的IP地址。
如果需要为用户设备分配新的IP地址，第二移动性管理实体暂不向用户设备申请IP地址，只是向用户设备发送位置更新确认(TAU Accept)消息。用户设备在接收到位置更新确认消息后，进入空闲态。
可选的，用户设备进入空闲态后，可以有三种方式获取第二IP地址。
第一种获取第二IP地址的方式中，用户设备向第二基站发送业务请求(Service Request)，第二基站将业务请求转发至第二移动性管理实体，第二移动性管理实体向第二网关为用户设备申请IP地址， 并将从第二网关接收的第二IP地址向用户设备发送。用户设备接收到第二IP地址，完成第二IP地址的获取过程。
第二种获取第二IP地址的方式中，当第一网关接收到通信对端向用户设备发送的下行数据后，缓存下行数据，并向第一移动性管理实体发送下行数据通知(DDN，Downlink Data Notification)。第一移动性管理实体收到下行数据通知后，寻呼(Page)用户设备。
用户设备响应第一移动性管理实体的寻呼后，第一移动性管理实体向第二网关为用户设备请求新的IP地址，并通过NAS消息将从第二网关接收的第二IP地址发送至用户设备。同时，第一移动性管理实体向第一网关请求第一网关缓存的下行数据，并通过NAS消息将从第一网关接收下行数据发送至用户设备。可选的，第一移动性管理实体可以将第二IP地址及下行数据同时发送给用户设备。
或者，用户设备响应第一移动性管理实体的寻呼后，第一移动性管理实体向第二网关为用户设备请求新的IP地址，并通过NAS消息将从第二网关接收的第二IP地址发送至用户设备。同时，第一移动性管理实体建立下行数据转发隧道，使得第一网关通过下行数据转发隧道向用户设备发送下行数据。可选的，下行数据转发隧道可以是第一网关与第二网关之间的数据转发隧道，此时第一网关通过下行数据转发隧道将下行数据发送至第二网关，第二网关通过第二基站将下行数据发送至用户设备。下行数据转发隧道也可以是第一网关与第二基站之间的数据转发隧道，此时第一网关将下行数据通过数据转发隧道发送至第二基站，由第二基站将下行数据发送至用户设备。
第三种获取第二IP地址的方式中。第二移动性管理实体在向用户设备发送位置更新确认消息后，向第一移动性管理实体注册用户设备的下行数据通知。第一移动性管理实体在确认第二移动性管理实体的注册后，如果接收到第一网关发送的下行数据通知，就将用户设备的下行数据通知发送至第二移动性管理实体。第二移动性管理实体收到下行数据通知后，寻呼用户设备。其中，第二移动性管 理实体用于管理所述第二基站和所述第二网关，第一移动性管理实体用于管理所述第一基站和所述第一网关。
用户设备响应第一移动性管理实体的寻呼后，第二移动性管理实体向第二网关为用户设备请求新的IP地址，并通过NAS消息将从第二网关接收的第二IP地址发送至用户设备。同时，第二移动性管理实体通过第一移动性管理实体向第一网关请求下行数据。第二移动性管理实体接收到第一网关通过第一移动性管理实体发送的下行数据后，通过NAS消息将下行数据发送至用户设备。可选的，第二移动性管理实体可以将第二IP地址及下行数据同时发送给用户设备。
或者，用户设备响应第二移动性管理实体的寻呼后，第二移动性管理实体向第二网关为用户设备请求新的IP地址，并通过NAS消息将从第二网关接收的第二IP地址发送至用户设备。同时，第二移动性管理实体通过第一移动性管理实体建立下行数据转发隧道，使得第一网关通过下行数据转发隧道将缓存的下行数据发送至用户设备，可选的，下行数据转发隧道可以是第一网关与第二网关之间的数据转发隧道，此时第一网关通过下行数据转发隧道将下行数据发送至第二网关，第二网关通过第二基站将下行数据发送至用户设备。下行数据转发隧道也可以是第一网关与第二基站之间的数据转发隧道，此时第一网关将下行数据通过数据转发隧道发送至第二基站，由第二基站将下行数据发送至用户设备。
903、用户设备在获取第二IP地址后与通信对端建立第二子流。
904、通信对端在第二子流建立之后，撤销第一子流。
结合图8所对应实施例中步骤804，第二MPTCP子流建立后，用户设备通过第二MPTCP子流向通信对端发送数据，而不再通过第一MPTCP子流向通信对端发送数据，因此撤销第一MPTCP子流。
905、第一网关在第一子流撤销之后释放第一IP地址。
第一MPTCP子流撤销后，用户设备指示第一移动性管理实体第一MPTCP子流已撤销，第一移动性管理实体向用户设备转发下行数 据之后，如果在预设定时器超时后没有收到新的用户设备的下行数据通知，则指示第一网关释放第一IP地址，下行数据转发隧道，上下文(Context)等资源。
本发明的实施例提供的移动性管理方法，通过第一网关及第二网关为用户设备动态分配IP地址。现有技术中通过移动网络架构中的数据汇聚式的锚点设备统一为用户设备分配IP地址，锚点设备压力巨大，一旦锚点设备出现问题，就会影响整个业务网络的正常运行，引起用户设备业务中断。本发明的实施例提供的移动性管理方法，当用户设备由第一网关向第二网关切换时，用户设备与通信对端通过MPTCP技术，使用第二IP地址建立第二MPTCP子流，在第二MPTCP子流建立之前，用户设备与通信对端通过第一MPTCP子流进行通信，并通过下行数据转发隧道传输用户设备的下行数据，在第二MPTCP子流建立之后，撤销第一MPTCP子流。从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
基于图8所对应的实施例，本发明的实施例提供再一种移动性管理方法，应用于蜂窝网络中的移动性管理系统。图8所对应的实施例中，用户设备在空闲态由第一基站向第二基站切换，在与第二基站连接后即获取第二IP地址。本实施例中，用户设备在由第一基站向第二基站切换前正在通过第一MPTCP子流与通信对端进行通信，当用户设备正在与通信对端进行通信的过程中由第一基站向第二基站切换时，需要保证用户设备的服务连接不中断。本实施例中部分步骤与图8所对应的实施例中相应的步骤相同，此处对相同部分不再详述，具体步骤如下：
1001、用户设备建立于通信对端的第一子流。
1002、在用户设备由第一基站向第二基站切换时，当第二网关与第一网关不是同一网关时，用户设备获取第二IP地址。
在一种具体的应用场景中，用户设备在与通信对端进行通信的过程中由第一基站向第二基站切换，且第二网关与第一网关不是同一网关。此时，建立数据转发隧道，用户设备在获取第二IP地址的同时，通过数据转发隧道继续与通信对端保持通信，即通过数据转发隧道传输第一 MPTCP子流的数据，从而避免了在切换过程中出现业务中断的问题。
数据转发隧道可以包括下行数据转发隧道和上行数据转发隧道两者之一，或者两者都包括。此处，以数据转发隧道包括下行数据转发隧道和上行数据转发隧道的情况为例，对数据转发隧道建立的过程，以及通过数据转发隧道传输第一MPTCP子流的数据的过程进行说明。
可选的，本实施例提供两种建立数据转发隧道的方式。
在第一种建立数据转发隧道的方式中，通过X2接口切换建立数据转发隧道。具体的，第一基站将上行数据转发隧道的IP地址和TEID(Tunnel End ID，隧道终端标识)通过Handover Request(切换请求)消息发送至第二基站。第二基站在接收Handover Request消息后，将下行数据转发隧道的IP地址和TEID通过Handover Request Ack(切换请求确认)消息发送至第一基站，由此建立数据转发隧道。
在第二种建立数据转发隧道的方式中，通过S1接口切换建立数据转发隧道。具体的，第一基站将上行数据转发隧道的IP地址和TEID通过Handover Required(切换查询)消息发送至第一移动性管理实体，经第一移动性管理实体转发至第二移动性管理实体，第二移动性管理实体将上行数据转发隧道的IP地址和TEID通过Handover Request消息发送至第二基站。第二基站在接收到Handover Request消息后向第一基站返回Handover Request Ack消息，由此建立数据转发隧道。
数据转发隧道建立后，用户设备与通信对端通过数据转发隧道传输第一MPTCP子流的数据。第一MPTCP子流的数据包括第一MPTCP子流的下行数据及第一MPTCP子流的上行数据，其中，第一MPTCP子流的下行数据为目标地址是第一IP地址的数据，第一MPTCP子流的上行数据为用户设备向通信对端发送的数据。
对于第一MPTCP子流的下行数据，第一基站在接收到第一MPTCP子流的下行数据后，将第一MPTCP子流的下行数据通过数据转发隧道发送至第二基站，由第二基站发送至用户设备。
对于第一MPTCP子流的上行数据，第二基站在获取第二IP地址后，将源地不是第二IP地址的数据包作为第一MPTCP子流的上行数据包通过数据转发隧道发送至第一基站，由第一基站向通信对端发送。可选的，结合图8所对应的实施例中的步骤802，本实施例提供两种第二基站获取第二IP地址的方式，分别应用于用户设备通过DHCP消息获取第二IP地址的场景，以及第二移动性管理实体请求第二网关为用户设备分配IP地址的场景。
在用户设备通过DHCP消息获取第二IP地址的场景中，用户设备通过接收第一网关标识及第二网关标识确定第一网关与第二网关不是同一网关，通过向第二网关请求新的IP地址获取第二IP地址。或者，用户设备将第二网关标识发送至第一基站，第一基站对第二网关标识和第一网关标识进行判断，如果第二网关标识与第一网关标识不同，则第一基站向用户设备发送判断指示消息，该判断指示消息用于指示第二网关与第一网关不是同一网关。用户设备在接收判断指示消息后，通过向第二网关请求新的IP地址获取第二IP地址。
用户设备获取第二IP地址后，将第二IP地址通过RRC消息发送至第二基站，或者，用户设备将第二IP地址通过NAS消息发送至第二移动性管理实体，由第二移动性管理实体通过S1消息将第二IP地址发送至第二基站。由此，完成用户设备及第二基站获取第二IP地址的过程。第二基站将用户设备发送的源地为第一IP地址的数据包通过数据转发隧道发送至第一基站，由第一基站向通信对端发送。
在第二移动性管理实体请求第二网关为用户设备分配IP地址的场景中，用户设备将第一IP地址或第一网关标识发送至第二移动性管理实体，通过第二移动性管理实体确定第一网关与第二网关不是同一网关，然后由第二移动性管理实体向第二网关为用户设备请求新的IP地址，并将从第二网关接收的第二IP地址通过NAS消息发送至用户设备，同时通过S1消息发送至第二基站，由此，完成用 户设备及第二基站获取第二IP地址的过程。第二基站将用户设备发送的源地为第一IP地址的数据包通过数据转发隧道发送至第一基站，由第一基站向通信对端发送。
或者，在第二移动性管理实体请求第二网关为用户设备分配IP地址的场景中，用户设备将第一IP地址或第一网关标识发送至第二移动性管理实体，通过第二移动性管理实体确定第一网关与第二网关不是同一网关，然后由第二移动性管理实体向第二网关为用户设备请求新的IP地址，第二网关在向第二移动性管理实体发送第二IP地址的同时，通过Bearer Creat Request(承载新建请求)消息请求第二移动性管理实体新建用户设备与第二基站之间的承载。承载新建完成后，第二移动性管理实体将新建的承载与第二IP地址绑定并通过NAS消息一起发送至用户设备。由此，完成用户设备获取第二IP地址的过程。当用户设备发送上行数据时，将源地址为第二IP地址的数据包通过新建的承载发送，将源地址为第一IP地址的数据包通过已有的承载发送。第二基站将用户设备通过已有的承载发送的数据包通过数据转发隧道发送至第一基站，由第一基站向通信对端发送。
1003、用户设备在获取第二IP地址后与通信对端建立第二子流。
1004、通信对端在第二子流建立之后，撤销第一子流。
结合图8所对应实施例中步骤804，第二MPTCP子流建立后，用户设备通过第二MPTCP子流向通信对端发送数据，而不再通过第一MPTCP子流向通信对端发送数据，因此撤销第一MPTCP子流。
1005、第一网关在第一子流撤销之后释放第一IP地址。
第一MPTCP子流撤销后，用户设备通过第一移动性管理实体指示第一网关释放第一IP地址，另外用户设备指示第二基站删除数据转发隧道。
对应建立数据转发隧道的两种方式，删除数据转发隧道的过程也有两种。
具体的，在通过X2接口切换建立数据转发隧道的场景中，用 户设备通过RRC消息指示第二基站第一MPTCP子流已经撤销，或者用户设备通过NAS消息指示第二移动性管理实体第一MPTCP子流已经撤销，由第二移动性管理实体指示第二基站第一MPTCP子流已经撤销。第二基站收到第一MPTCP子流已经撤销的指示后，第一基站发送删除数据转发隧道的请求消息，第一基站在接收删除数据转发隧道的请求消息后，向第二基站返回删除数据转发隧道的确认消息。第一基站与第二基站释放数据转发隧道，第一基站删除用户设备的上下文(Context)和接入网资源。
或者，在通过S1接口切换建立数据转发隧道的场景中，用户设备通过RRC消息指示第二基站第一MPTCP子流已经撤销，或者用户设备通过NAS消息指示第二移动性管理实体第一MPTCP子流已经撤销，由第二移动性管理实体指示第二基站第一MPTCP子流已经撤销。第二基站收到第一MPTCP子流已经撤销的指示后，通过第二移动性管理实体向第一移动性管理实体发送指示消息。第二移动性管理实体指示第二网关释放数据转发隧道，第一移动性管理实体指示第一网关及第一基站释放数据转发隧道，第一基站同时删除用户设备的上下文和接入网资源。
基于本发明的实施例所提供的移动性管理系统，本发明的实施例还提供一种对用户设备进行计费的方法。当用户设备通过第一子流与通信对端通信时，由第一网关对用户设备进行计费，当用户设备通过第二子流与通信对端通信时，由第二网关对用户设备进行计费。本实施例中以第一网关对用户设备进行计费的应用场景为例进行说明。
在使用计费规则功能(PCRF，Policy and Charging Rules Function)以及在线计费系统(OCS，Online Charging System)的应用场景中，第一网关获取用户设备的计费规则及用户设备的可用额度，并根据用户设备的计费规则对用户设备的可用额度进行扣减，然后向在线计费系统发送用户设备的可用额度余额。其中，用户设备的可用额度为该用户设备的账户的可用额度，可用额度可以为该 用户设备的信用(Credit)或配额(Quota)。
具体可选的，当用户设备连接到第一网关时，向第一移动性管理实体请求用户设备的计费规则及用户设备的可用额度。第一移动性管理实体从策略和计费规则功能获得的用户设备的计费规则并发送至第一网关，第一移动性管理实体从在线计费系统获取用户设备的可用余额并发送至第一网关。第一网关根据用户设备的计费规则对用户设备的可用额度进行扣减。如果用户设备的可用额度全部被扣减完，则第一网关重新向第一移动性管理实体请求用户设备的可用额度。第一子流撤销后，第一网关将用户设备的可用额度余额通过移动性管理实体返回给在线计费系统。
在使用计费规则功能以及离线计费系统(OFCS，Off-line Charging System)的应用场景中，第一网关向第一移动性管理实体发送用户设备在第一网关的话单(CDR，Call Detail Record)。第一移动性管理实体将用户设备在第一网关的话单发送至离线计费系统。可选的，第一移动性管理实体可以管理多个网关，第一网关可以为第一移动性管理实体所管理网关中的一个或者多个。
本发明的实施例提供的移动性管理方法，通过第一网关及第二网关为用户设备动态分配IP地址。现有技术中通过移动网络架构中的数据汇聚式的锚点设备统一为用户设备分配IP地址，锚点设备压力巨大，一旦锚点设备出现问题，就会影响整个业务网络的正常运行，引起用户设备业务中断。本发明的实施例提供的移动性管理方法，当用户设备由第一网关向第二网关切换时，用户设备与通信对端通过MPTCP技术，使用第二IP地址建立第二MPTCP子流，在第二MPTCP子流建立之前，用户设备与通信对端通过第一MPTCP子流进行通信，并通过数据转发隧道接收下行数据以及发送上行数据，在第二MPTCP子流建立之后，撤销第一MPTCP子流。从而保证了用户设备与基站之间的正常通信，并保证了用户设备与通信对端之间的业务连续性。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本发明可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用 软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM(Random Access Memory，随机存储器)、ROM(Read Only Memory，只读内存)、EEPROM(Electrically Erasable Programmable Read Only Memory，电可擦可编程只读存储器)、CD-ROM(Compact Disc Read Only Memory，即只读光盘)或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、DSL(Digital Subscriber Line，数字用户专线)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本发明所使用的，盘和碟包括CD(Compact Disc，压缩光碟)、激光碟、光碟、DVD碟(Digital Versatile Disc，数字通用光)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保护范围为准。

Claims (75)

  1. 一种移动性管理系统，其特征在于，包括：用户设备，第一基站，第二基站，第一网关，第二网关及通信对端，所述第一基站与所述第一网关连接，所述第二基站与所述第二网关连接；
    所述用户设备，用于建立与所述通信对端的第一子流，所述第一子流为所述用户设备使用第一网际互连协议IP地址与所述通信对端建立的子流，所述第一IP地址是所述第一网关为所述用户设备分配的IP地址；
    当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备，还用于当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，所述第二IP地址为所述第二网关为所述用户设备分配的IP地址；
    所述用户设备，还用于在获取所述第二IP地址后与所述通信对端建立第二子流，所述第二子流为所述用户设备使用所述第二IP地址与所述通信对端建立的子流；
    所述通信对端，用于在所述第二子流建立之后，撤销所述第一子流；
    所述第一网关，还用于在所述第一子流撤销之后释放所述第一IP地址。
  2. 根据权利要求1所述的系统，其特征在于，
    所述用户设备，还用于在所述撤销所述第一子流之后，释放所述第一IP地址，并向所述第一网关发送释放所述第一IP地址的指示消息；
    所述第一网关，用于在接收所述用户设备发送的所述释放所述第一IP地址的指示消息后，释放所述第一IP地址。
  3. 根据权利要求1所述的系统，其特征在于，
    所述第一基站及所述第二基站，用于建立数据转发隧道，所述数据转发隧道为所述第一基站及所述第二基站之间的数据转发通道；
    所述用户设备及所述通信对端，还用于通过所述数据转发隧道传 输所述第一子流的数据。
  4. 根据权利要求3所述的系统，其特征在于，所述数据转发隧道，包括：
    下行数据转发隧道或上行数据转发隧道；
    或者，下行数据转发隧道和上行数据转发隧道。
  5. 根据权利要求3或4所述的系统，其特征在于，
    所述第二基站，还用于在所述第一子流撤销后，删除所述数据转发隧道。
  6. 根据权利要求1所述的系统，其特征在于，所述当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，包括：
    当所述用户设备与第一基站连接时，接收所述第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关；
    当所述用户设备由所述第一基站向所述第二基站切换时，接收所述第二基站发送的第二网关标识，所述第二网关标识用于指示第二网关；
    如果所述第二网关标识与所述第一网关标识不同，则所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
  7. 根据权利要求1所述的系统，其特征在于，所述当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，包括：
    所述移动性管理系统还包括第二移动性管理实体，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
    当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备将所述第一IP地址或第一网关标识发送至所述第二移动性管理实体，所述第一网关标识用于指示第一网关；
    所述第二移动性管理实体确定所述第一IP地址是否为所述第二网关为所述用户设备分配的IP地址，或所述第一网关标识是否与第二网关标识相同，所述第二网关标识用于指示第二网关；
    如果所述第一IP地址不是所述第二网关为所述用户设备分配的 IP地址，或所述第一网关标识与所述第二网关标识不同，则所述第二移动性管理实体向所述第二网关为所述用户设备申请分配IP地址，并将从所述第二网关接收的所述第二IP地址发送至所述用户设备。
  8. 根据权利要求1所述的系统，其特征在于，所述当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，包括：
    当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备将第二网关标识发送至所述第一基站，所述第二网关标识用于指示第二网关；
    如果所述第二网关标识与所述第一网关标识不同，则所述第一基站向所述用户设备发送判断指示消息，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关；
    所述用户设备在接收判断指示消息后向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
  9. 根据权利要求1所述的系统，其特征在于，
    所述移动性管理系统还包括第二移动性管理实体，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
    所述用户设备，还用于当所述用户设备在空闲态从所述第一基站移动到所述第二基站，向所述第二移动性管理实体发送位置更新请求消息；
    所述第二移动性管理实体，用于向所述用户设备发送位置更新确认消息。
  10. 根据权利要求1所述的系统，其特征在于，
    所述用户设备，在空闲态从所述第一基站移动到所述第二基站，在连接第二基站完成位置更新之后，进入空闲态；
    所述移动性管理系统还包括第一移动性管理实体，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
    所述第一网关，还用于在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知；
    所述第一移动性管理实体，还用于从所述第一网关接收所述用户 设备的下行数据通知，并在接收所述用户设备的下行数据通知后寻呼所述用户设备；
    所述用户设备，还用于响应所述第二移动性管理实体的寻呼。
  11. 根据权利要求10所述的系统，其特征在于，
    所述第一网关，还用于缓存下行数据；
    所述第一移动性管理实体，还用于在所述用户设备响应寻呼后向所述第一网关请求所述下行数据，接收所述第一网关发送的所述下行数据，并将从所述第一网关接收的所述下行数据发送至所述用户设备。
  12. 根据权利要求10所述的系统，其特征在于，
    所述第一网关，还用于缓存下行数据；
    所述第一移动性管理实体，还用于在所述用户设备响应寻呼后建立下行数据转发隧道；
    所述第一网关，还用于通过所述下行数据转发隧道向所述用户设备发送所述下行数据。
  13. 根据权利要求1所述的系统，其特征在于，
    所述用户设备，在空闲态从所述第一基站移动到所述第二基站，在连接第二基站完成位置更新之后，进入空闲态；
    所述移动性管理系统还包括第一移动性管理实体及第二移动性管理实体，所述第一移动性管理实体用于管理所述第一基站和所述第一网关，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
    所述第二移动性管理实体，还用于向所述第一移动性管理实体注册所述用户设备的下行数据通知；
    所述第一网关，还用于在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知；
    所述第一移动性管理实体，还用于在确认所述第二移动性管理实体的注册后，将所述用户设备的下行数据通知发送至所述第二移动性管理实体；
    所述第二移动性管理实体，还用于在接收所述用户设备的下行数据通知后寻呼所述用户设备；
    所述用户设备，还用于响应所述第二移动性管理实体的寻呼。
  14. 根据权利要求13所述的系统，其特征在于，
    所述第一网关，还用于缓存下行数据；
    所述第二移动性管理实体，还用于在所述用户设备响应寻呼后通过所述第一移动性管理实体请求所述下行数据；
    所述第一移动性管理实体，还用于将所述第一网关发送的所述下行数据转发至所述第二移动性管理实体；
    所述第二移动性管理实体，还用于将所述下行数据发送至所述用户设备。
  15. 根据权利要求13所述的系统，其特征在于，
    所述第一网关，还用于缓存下行数据；
    所述第二移动性管理实体，还用于在所述用户设备响应寻呼后通过所述第一移动性管理实体建立下行数据转发隧道；
    所述第一网关，还用于通过所述下行数据转发隧道向所述用户设备发送所述下行数据。
  16. 根据权利要求1所述的系统，其特征在于，
    所述移动性管理系统还包括：第一移动性管理实体、在线计费系统OCS及策略和计费规则功能PCRF，
    所述第一移动性管理实体，用于从所述在线计费系统获取所述用户设备的可用额度，并将所述用户设备的可用额度发送至所述第一网关；
    所述第一移动性管理实体，还用于从所述策略和计费规则功能获取所述用户设备的计费规则，并将所述用户设备的计费规则发送至所述第一网关；
    所述第一网关，还用于当用户设备通过所述第一子流与所述通信对端进行通信时，根据所述用户设备的计费规则对所述用户设备的可用额度进行扣减，并向在线计费系统发送所述用户设备的可用额度余 额。
  17. 根据权利要求1所述的系统，其特征在于，
    所述移动性管理系统还包括：第一移动性管理实体及离线计费系统OFCS；
    所述第一网关，还用于向所述第一移动性管理实体发送所述用户设备在所述第一网关的话单；
    所述第一移动性管理实体，用于将所述用户设备在所述第一网关的话单发送至离线计费系统。
  18. 一种用户设备，其特征在于，包括处理器、存储器及总线，所述处理器及所述存储器通过所述总线相互连接；
    其中，所述处理器，用于建立与通信对端的第一子流，所述第一子流为所述用户设备使用第一网际互连协议IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
    所述处理器，还用于获取第二IP地址，所述第二IP地址为所述第二网关为所述用户设备分配的IP地址；
    所述处理器，还用于与所述通信对端建立第二子流，所述第二子流为所述用户设备使用所述第二IP地址与所述通信对端建立的子流；
    所述处理器，还用于撤销所述第一子流。
  19. 根据权利要求18所述的用户设备，其特征在于，
    所述处理器，还用于在所述撤销所述第一子流之后，释放所述第一IP地址，并生成指示所述第一网关释放所述第一IP地址的指示消息；
    所述用户设备还包括发送器，用于向所述第一网关发送指示所述第一网关释放所述第一IP地址的指示消息。
  20. 根据权利要求18所述的用户设备，其特征在于，
    所述处理器，还用于通过数据转发隧道传输所述第一子流的数据，所述数据转发隧道为所述第一基站及所述第二基站之间的数据转发通道。
  21. 根据权利要求19所述的用户设备，其特征在于，所述数据转发隧道，包括：
    下行数据转发隧道或上行数据转发隧道；
    或者，下行数据转发隧道和上行数据转发隧道。
  22. 根据权利要求20或21所述的用户设备，其特征在于，
    所述处理器，还用于释放所述第一IP地址；
    所述处理器，还用于生成指示所述第一子流已经撤销的指示消息；
    所述用户设备还包括发送器，用于向所述第二基站发送指示所述第一子流已经撤销的指示消息，以便于所述第二基站删除所述数据转发隧道。
  23. 根据权利要求18所述的用户设备，其特征在于，所述用户设备还包括接收器，
    所述接收器，用于接收所述第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关；
    所述接收器，还用于接收所述第二基站发送的第二网关标识，所述第二网关标识用于指示第二网关；
    所述处理器，还用于判断所述第二网关标识与所述第一网关标识是否相同，如果所述第二网关标识与所述第一网关标识不同，则生成获取IP地址的请求消息；
    所述用户设备还包括发送器，用于向所述第二网关发送所述获取IP地址的请求消息；
    所述接收器，还用于接收所述第二网关发送的所述第二IP地址。
  24. 根据权利要求18所述的用户设备，其特征在于，
    所述用户设备还包括发送器及接收器，
    所述发送器，用于当所述用户设备由所述第一基站向所述第二基站切换时，将所述第一IP地址或第一网关标识发送至第二移动性管理实体，以便于所述第二移动性管理实体根据所述第一IP地址或第一网关标识确定所述第二网关与所述第一网关是否为同一网关，并在 所述第二网关与所述第一网关不是同一网关时向所述第二网关为所述用户设备申请分配IP地址，将从所述第二网关接收的所述第二IP地址发送至所述用户设备，所述第一网关标识用于指示第一网关，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
    所述接收器，用于接收所述第二移动性管理实体发送的所述第二IP地址。
  25. 根据权利要求18所述的用户设备，其特征在于，所述用户设备还包括发送器及接收器，
    所述发送器，用于当所述用户设备由所述第一基站向所述第二基站切换时，将第二网关标识发送至所述第一基站，以便于所述第一基站确定所述第二网关与所述第一网关是否为同一网关，所述第二网关标识用于指示第二网关；
    所述接收器，用于接收所述第一基站发送的判断指示消息，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关；
    所述处理器，还用于生成获取IP地址的请求消息；
    所述发送器，还用于向所述第二网关发送所述获取IP地址的请求消息；
    所述接收器，还用于接收所述第二网关发送的所述第二IP地址。
  26. 根据权利要求18所述的用户设备，其特征在于，
    所述处理器还用于当所述用户设备在空闲态从所述第一基站移动到所述第二基站时，生成位置更新请求消息；
    所述用户设备还包括接收器和发送器，
    所述发送器，用于向第二移动性管理实体发送所述位置更新请求消息，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
    所述接收器，用于接收所述第二移动性管理实体发送的位置更新确认消息。
  27. 根据权利要求26所述的用户设备，其特征在于，
    所述处理器，还用于控制所述用户设备进入空闲态；
    所述接收器，还用于当所述用户设备在空闲态时接收第一移动性管理实体的寻呼，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
    所述处理器，还用于生成寻呼响应消息；
    所述发送器，用于向所述第一移动性管理实体发送所述寻呼响应消息；
    所述接收器，还用于当所述用户设备在空闲态时接收第二移动性管理实体的寻呼，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
    所述发送器，用于向所述第二移动性管理实体发送所述寻呼响应消息。
  28. 根据权利要求27所述的用户设备，其特征在于，
    所述接收器，还用于接收所述下行数据。
  29. 一种第一基站，其特征在于，包括处理器、存储器、发送器、接收器及总线，所述处理器、所述存储器、所述发送器及所述接收器通过所述总线相互连接；
    其中，所述处理器，用于当所述用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，生成数据转发隧道的建立请求消息，所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
    所述发送器，用于向所述第二基站发送所述数据转发隧道的建立 请求消息；
    所述接收器，用于接收所述第二基站发送的所述数据转发隧道的建立确认消息；
    所述接收器，还用于接收所述第二基站发送的所述数据转发隧道的删除请求消息；
    所述发送器，还用于向所述第二基站发送所述数据转发隧道的删除确认消息；
    所述处理器，还用于释放所述数据转发隧道，并生成第一IP释放指示消息；
    所述发送器，还用于向所述第一网关发送所述第一IP释放指示消息。
  30. 根据权利要求29所述的第一基站，其特征在于，
    所述接收器，还用于接收所述用户设备发送的第二网关标识，所述第二网关标识用于指示第二网关；
    所述处理器，还用于根据所述第二网关标识确定所述第二网关与所述第一网关是否为同一网关，当所述第二网关与所述第一网关不是同一网关时，生成判断指示消息，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关；
    所述发送器，还用于向所述用户设备发送所述判断指示消息，以便于所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
  31. 一种第二基站，其特征在于，包括处理器、存储器、发送器、接收器及总线，所述处理器、所述存储器、所述发送器及所述接收器通过所述总线相互连接；
    其中，所述接收器，用于当所述用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，接收所述第一基站发送的数据转发隧道的建立请求消息，所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基 站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
    所述处理器，用于生成所述数据转发隧道的建立确认消息；
    所述发送器，用于向所述第一基站发送所述数据转发隧道的建立确认消息；
    所述处理器，还用于在所述第一子流撤消后生成所述数据转发隧道的删除请求消息；
    所述发送器，还用于，向所述第一基站发送所述数据转发隧道的删除请求消息；
    所述接收器，还用于接收所述第一基站发送的所述数据转发隧道的删除确认消息；
    所述处理器，还用于释放所述数据转发隧道。
  32. 一种用户设备，其特征在于，包括：多路径控制单元及收发单元，
    所述多路径控制单元，用于当所述用户设备与第一基站连接时，建立与通信对端的第一子流，所述第一子流为所述用户设备使用第一网际互连协议IP地址与所述通信对端建立的子流，所述第一网际互联协议IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
    所述收发单元，用于获取第二IP地址，所述第二IP地址为所述第二网关为所述用户设备分配的IP地址；
    所述多路径控制单元，还用于与所述通信对端建立第二子流，所述第二子流为所述用户设备使用所述第二IP地址与所述通信对端建 立的子流；
    所述多路径控制单元，还用于在所述第二子流建立完成后，撤销所述第一子流。
  33. 根据权利要求32所述的用户设备，其特征在于，
    多路径控制单元，还用于在所述撤销所述第一子流之后，释放所述第一IP地址，并生成指示所述第一网关释放所述第一IP地址的指示消息；
    所述收发单元，还用于向所述第一网关发送指示所述第一网关释放所述第一IP地址的指示消息。
  34. 根据权利要求32所述的用户设备，其特征在于，
    所述收发单元，还用于通过数据转发隧道传输所述第一子流的数据，所述数据转发隧道为所述第一基站及所述第二基站之间的数据转发通道。
  35. 根据权利要求34所述的用户设备，其特征在于，所述数据转发隧道，包括：
    下行数据转发隧道或上行数据转发隧道；
    或者，下行数据转发隧道和上行数据转发隧道。
  36. 根据权利要求34或35所述的用户设备，其特征在于，
    所述多路径控制单元，还用于释放所述第一IP地址；
    所述多路径控制单元，还用于生成所述第一子流已经撤销的指示消息；
    所述收发单元，还用于向所述第二基站发送所述第一子流已经撤销的指示消息，以便于所述第二基站删除所述数据转发隧道。
  37. 根据权利要求32所述的用户设备，其特征在于，
    所述收发单元，还用于当所述用户设备与第一基站连接时，接收所述第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关；
    所述收发单元，还用于当所述用户设备由所述第一基站向所述第二基站切换时，接收所述第二基站发送的第二网关标识，所述第二网 关标识用于指示第二网关；
    所述多路径控制单元，还用于判断所述第二网关标识与所述第一网关标识是否相同，如果所述第二网关标识与所述第一网关标识不同，则生成获取IP地址的请求消息；
    所述收发单元，还用于向所述第二网关发送所述获取IP地址的请求消息；
    所述收发单元，还用于接收所述第二网关发送的所述第二IP地址。
  38. 根据权利要求32所述的用户设备，其特征在于，
    所述收发单元，还用于当所述用户设备由所述第一基站向所述第二基站切换时，将所述第一IP地址或第一网关标识发送至第二移动性管理实体，以便于所述第二移动性管理实体根据所述第一IP地址或第一网关标识确定所述第二网关与所述第一网关是否为同一网关，并在所述第二网关与所述第一网关不是同一网关时向所述第二网关为所述用户设备申请分配IP地址，将从所述第二网关接收的所述第二IP地址发送至所述用户设备，所述第一网关标识用于指示第一网关，所述第二移动性管理实体用于管理所述第二基站和所述第二网关；
    所述收发单元，还用于接收所述第二移动性管理实体发送的所述第二IP地址。
  39. 根据权利要求32所述的用户设备，其特征在于，
    所述收发单元，还用于当所述用户设备由所述第一基站向所述第二基站切换时，将第二网关标识发送至所述第一基站，以便于所述第一基站确定所述第二网关与所述第一网关是否为同一网关，所述第二网关标识用于指示第二网关；
    所述收发单元，还用于接收所述第一基站发送的判断指示消息，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关；
    所述多路径控制单元，还用于生成获取IP地址的请求消息；
    所述收发单元，还用于向所述第二网关发送所述获取IP地址的请求消息；
    所述收发单元，还用于接收所述第二网关发送的所述第二IP地址。
  40. 根据权利要求32所述的用户设备，其特征在于，所述用户设备还包括切换控制单元，
    所述切换控制单元，用于当所述用户设备在空闲态从所述第一基站移动到所述第二基站时，生成位置更新请求消息；
    所述收发单元，还用于向第二移动性管理实体发送所述位置更新请求消息；
    所述收发单元，还用于接收所述第二移动性管理实体发送的位置更新确认消息，所述第二移动性管理实体用于管理所述第二基站和所述第二网关。
  41. 根据权利要求32所述的用户设备，其特征在于，
    所述切换控制单元，还用于控制所述用户设备进入空闲态；
    所述收发单元，还用于当所述用户设备在空闲态时接收第一移动性管理实体的寻呼，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
    所述切换控制单元，还用于响应所述第一移动性管理实体的寻呼；
    所述收发单元，还用于接收所述第一网关缓存并转发的下行数据；
    所述收发单元，还用于当所述用户设备在空闲态时接收第二移动性管理实体的寻呼，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
    所述切换控制单元，还用于响应所述第二移动性管理实体的寻呼。
  42. 根据权利要求41所述的用户设备，其特征在于，
    所述收发单元，还用于接收所述下行数据。
  43. 一种第一基站，其特征在于，包括控制单元、发送单元及接收单元；
    所述控制单元，用于当所述用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，生成数据转发隧道的建立请求消息，所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
    所述发送单元，用于所述第二基站发送所述数据转发隧道的建立请求消息；
    所述接收单元，用于接收所述第二基站发送的所述数据转发隧道的建立确认消息；
    所述接收单元，还用于接收所述第二基站发送的所述数据转发隧道的删除请求消息；
    所述控制单元，还用于生成所述数据转发隧道的删除确认消息；
    所述发送单元，还用于向所述第二基站发送所述数据转发隧道的删除确认消息；
    所述控制单元，还用于释放所述数据转发隧道，并生成第一IP释放指示消息；
    所述发送单元，还用于向所述第一网关发送所述第一IP释放指示消息。
  44. 根据权利要求43所述的第一基站，其特征在于，
    所述接收单元，还用于接收所述用户设备发送的第二网关标识， 所述第二网关标识用于指示第二网关；
    所述控制单元，还用于根据所述第二网关标识确定所述第二网关与所述第一网关是否为同一网关，并在所述第二网关与所述第一网关不是同一网关时，生成判断指示消息，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关；
    所述发送单元，还用于向所述用户设备发送判断指示消息，以便于所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
  45. 一种第二基站，其特征在于，包括控制单元、发送单元及接收单元；
    所述接收单元，用于当用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，接收所述第一基站发送的数据转发隧道的建立请求消息，所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
    所述控制单元，用于生成所述数据转发隧道的建立确认消息；
    所述发送单元，用于向所述第一基站发送所述数据转发隧道的建立确认消息；
    所述控制单元，还用于在所述第一子流撤消后，生成所述数据转发隧道的删除请求消息；
    所述发送单元，还用于向所述第一基站发送所述数据转发隧道的删除请求消息；
    所述接收单元，还用于接收所述第一基站发送的所述数据转发隧道的删除确认消息；
    所述控制单元，还用于释放所述数据转发隧道。
  46. 一种移动性管理方法，其特征在于，
    用户设备建立与通信对端的第一子流，所述第一子流为所述用户设备使用第一网际互连协议IP地址与所述通信对端建立的子流，所述第一IP地址是所述第一网关为所述用户设备分配的IP地址；
    在所述用户设备由所述第一基站向所述第二基站切换时，当所述第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，所述第二IP地址为所述第二网关为所述用户设备分配的IP地址；
    所述用户设备在获取所述第二IP地址后与所述通信对端建立第二子流，所述第二子流为所述用户设备使用所述第二IP地址与所述通信对端建立的子流；
    所述通信对端在所述第二子流建立之后，撤销所述第一子流；
    所述第一网关在所述第一子流撤销之后释放所述第一IP地址。
  47. 根据权利要求46所述的方法，其特征在于，
    所述用户设备，在所述撤销所述第一子流之后，释放所述第一IP地址，并指示所述第一网关释放所述第一IP地址。
  48. 根据权利要求46所述的方法，其特征在于，所述用户设备由所述第一基站向所述第二基站切换，包括：所述用户设备在与所述通信对端正在进行通信的过程中由所述第一基站向所述第二基站切换；
    所述当所述第二网关与所述第一网关不是同一网关时，所述方法还包括：
    所述第一基站及所述第二基站，建立数据转发隧道，所述数据转发隧道为所述第一基站及所述第二基站之间的数据转发通道；
    所述用户设备及所述通信对端，通过所述数据转发隧道传输所述第一子流的数据。
  49. 根据权利要求48所述的方法，其特征在于，所述数据转发隧道，包括：
    下行数据转发隧道或上行数据转发隧道；
    或者，下行数据转发隧道和上行数据转发隧道。
  50. 根据权利要求48或49所述的方法，其特征在于，所述撤销所述第一子流之后，所述方法还包括：
    所述第二基站，删除所述数据转发隧道。
  51. 根据权利要求46所述的方法，其特征在于，所述当所述第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，包括：
    当所述用户设备与第一基站连接时，接收所述第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关；
    当所述用户设备由所述第一基站向所述第二基站切换时，接收所述第二基站发送的第二网关标识，所述第二网关标识用于指示第二网关；
    如果所述第二网关标识与所述第一网关标识不同，则所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
  52. 根据权利要求46所述的方法，其特征在于，所述当所述第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，包括：
    所述移动性管理系统还包括第二移动性管理实体；
    当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备将所述第一IP地址或第一网关标识发送至所述第二移动性管理实体，所述第一网关标识用于指示第一网关；
    所述第二移动性管理实体确定所述第一IP地址是否为所述第二网关为所述用户设备分配的IP地址，或所述第一网关标识是否与第二网关标识相同；
    如果所述第一IP地址不是所述第二网关为所述用户设备分配的 IP地址，或所述第一网关标识与所述第二网关标识不同，则所述第二移动性管理实体向所述第二网关为所述用户设备申请分配IP地址，并将从所述第二网关接收的所述第二IP地址发送至所述用户设备。
  53. 根据权利要求46所述的方法，其特征在于，所述当所述第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，包括：
    当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备将第二网关标识发送至所述第一基站，所述第二网关标识用于指示第二网关；
    如果所述第二网关标识与第一网关标识不同，则所述第一基站向所述用户设备发送判断指示消息，所述第一网关标识用于指示第一网关，所述判断指示消息指示所述第二网关与所述第一网关不是同一网关；
    所述用户设备在接收判断指示消息后向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址。
  54. 根据权利要求46所述的方法，其特征在于，
    所述用户设备由所述第一基站向所述第二基站切换，包括：所述用户设备在空闲态从所述第一基站移动到所述第二基站，向第二移动性管理实体发送位置更新请求消息，并接收所述第二移动性管理实体发送的位置更新确认消息，所述第二移动性管理实体用于管理所述第二基站和所述第二网关。
  55. 根据权利要求46所述的方法，其特征在于，所述方法还包括：
    当所述用户设备在空闲态从所述第一基站移动到所述第二基站时，进行位置更新，并在接收所述第二基站发送的位置更新确认消息后进入空闲态；
    所述第一网关在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
    所述第一移动性管理实体从所述第一网关接收所述用户设备的下行数据通知，并在接收所述用户设备的下行数据通知后寻呼所述用户设备；
    所述用户设备响应所述第一移动性管理实体的寻呼。
  56. 根据权利要求55所述的方法，其特征在于，
    所述第一网关在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知之前，所述方法还包括：
    所述第一网关缓存下行数据；
    所述用户设备响应所述第一移动性管理实体的寻呼之后，所述方法还包括：
    所述第一移动性管理实体在所述用户设备响应寻呼后向所述第一网关请求所述下行数据，接收所述第一网关发送的所述下行数据，并将从所述第一网关接收的所述下行数据发送至所述用户设备。
  57. 根据权利要求55所述的方法，其特征在于，
    所述第一网关在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知之前，所述方法还包括：
    所述第一网关缓存下行数据；
    所述用户设备响应所述第一移动性管理实体的寻呼之后，所述方法还包括：
    所述第一移动性管理实体建立下行数据转发隧道；
    所述第一网关通过所述下行数据转发隧道向所述用户设备发送所述下行数据。
  58. 根据权利要求46所述的方法，其特征在于，
    所述用户设备在空闲态从所述第一基站移动到所述第二基站，进行位置更新，并在接收所述第二基站发送的位置更新确认消息后进入空闲态；
    第二移动性管理实体在所述用户设备进入空闲态后向第一移动性管理实体注册所述用户设备的下行数据通知，所述第二移动性管理实体用于管理所述第二基站和所述第二网关，所述第一移动性管理实 体用于管理所述第一基站和所述第一网关；
    所述第一移动性管理实体，在确认所述第二移动性管理实体的注册后，将所述用户设备的下行数据通知发送至所述第二移动性管理实体；
    所述第二移动性管理实体，在接收所述用户设备的下行数据通知后寻呼所述用户设备；
    所述用户设备响应所述第二移动性管理实体的寻呼。
  59. 根据权利要求58所述的方法，其特征在于，
    所述第一网关在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知之前，所述方法还包括：
    所述第一网关缓存下行数据；
    所述用户设备响应所述第一移动性管理实体的寻呼之后，所述方法还包括：
    所述第二移动性管理实体通过所述第一移动性管理实体请求所述下行数据；
    所述第一移动性管理实体，将所述第一网关发送的所述下行数据转发至所述第二移动性管理实体；
    所述第二移动性管理实体，将所述下行数据发送至所述用户设备。
  60. 根据权利要求58所述的方法，其特征在于，
    所述第一网关在所述用户设备进入空闲态后向所述第一移动性管理实体发送所述用户设备的下行数据通知之前，所述方法还包括：
    所述第一网关缓存下行数据；
    所述用户设备响应所述第一移动性管理实体的寻呼之后，所述方法还包括：
    所述第二移动性管理实体，通过所述第一移动性管理实体建立下行数据转发隧道；
    所述第一网关，通过所述下行数据转发隧道向所述用户设备发送所述下行数据。
  61. 根据权利要求46所述的方法，其特征在于，所述方法还包括：
    所述第一网关获取所述用户设备的计费规则及所述用户设备的可用额度；
    所述第一网关在用户设备通过所述第一子流与所述通信对端进行通信时，根据所述用户设备的计费规则对所述用户设备的可用额度进行扣减；
    所述第一网关向在线计费系统发送所述用户设备的可用额度余额。
  62. 根据权利要求46所述的方法，其特征在于，所述方法还包括：
    所述第一网关向所述第一移动性管理实体发送所述用户设备在所述第一网关的话单；
    所述第一移动性管理实体将所述用户设备在所述第一网关的话单发送至离线计费系统。
  63. 一种移动性管理方法，应用于用户设备，其特征在于，
    当所述用户设备与第一基站连接时，所述用户设备建立与通信对端的第一子流，所述第一子流为所述用户设备使用第一网际互连协议IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
    在所述用户设备由所述第一基站向所述第二基站切换时，当第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，所述第二IP地址为所述第二网关为所述用户设备分配的IP地址；
    所述用户设备与所述通信对端建立第二子流，所述第二子流为所述用户设备使用所述第二IP地址与所述通信对端建立的子流；
    所述用户设备在所述第二子流建立完成后，撤销所述第一子流。
  64. 根据权利要求63所述的方法，其特征在于，
    所述用户设备在所述撤销所述第一子流之后，释放所述第一IP地址，并指示所述第一网关释放所述第一IP地址。
  65. 根据权利要求63所述的方法，其特征在于，所述用户设备由所述第一基站向所述第二基站切换，包括：所述用户设备在与所述通信对端正在进行通信的过程中由所述第一基站向所述第二基站切换；
    所述当所述第二网关与所述第一网关不是同一网关时，所述方法还包括：
    所述用户设备建立与所述通信对端的数据转发隧道，并通过所述数据转发隧道传输所述第一子流的数据，所述数据转发隧道为所述第一基站及所述第二基站之间的数据转发通道。
  66. 根据权利要求65所述的方法，其特征在于，所述数据转发隧道，包括：
    下行数据转发隧道或上行数据转发隧道；
    或者，下行数据转发隧道和上行数据转发隧道。
  67. 根据权利要求65或66所述的方法，其特征在于，所述撤销所述第一子流之后，所述方法还包括：
    所述用户设备释放所述第一IP地址，并指示第一网关释放第一IP地址；
    所述用户设备向所述第二基站指示所述第一子流已经撤销，以便于所述第二基站删除所述数据转发隧道。
  68. 根据权利要求63所述的方法，其特征在于，所述当第二网关与所述第一网关不是同一网关时，所述用户设备获取第二IP地址，包括：
    当所述用户设备与第一基站连接时，接收所述第一基站发送的第一网关标识，所述第一网关标识用于指示第一网关；
    当所述用户设备由所述第一基站向所述第二基站切换时，接收所述第二基站发送的第二网关标识，所述第二网关标识用于指示第二网关；
    如果所述第二网关标识与所述第一网关标识不同，则所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网 关发送的所述第二IP地址。
  69. 根据权利要求63所述的方法，其特征在于，所述当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，包括：
    当所述用户设备由所述第一基站向所述第二基站切换时，将所述第一IP地址或第一网关标识发送至第二移动性管理实体，以便于所述第二移动性管理实体根据所述第一IP地址或第一网关标识确定所述第二网关与所述第一网关是否为同一网关，并在所述第二网关与所述第一网关不是同一网关时向所述第二网关为所述用户设备申请分配IP地址，将从所述第二网关接收的所述第二IP地址发送至所述用户设备，所述第一网关标识用于指示第一网关，所述第二移动性管理实体用于管理所述第二基站和所述第二网关。
  70. 根据权利要求63所述的方法，其特征在于，所述当所述第二网关与所述第一网关不是同一网关时获取第二IP地址，包括：
    当所述用户设备由所述第一基站向所述第二基站切换时，所述用户设备将第二网关标识发送至所述第一基站，以便于所述第一基站确定所述第二网关与所述第一网关是否为同一网关，所述第二网关标识用于指示第二网关；
    所述用户设备接收所述第一基站发送的判断指示消息，向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关。
  71. 根据权利要求63所述的方法，其特征在于，
    所述用户设备由所述第一基站向所述第二基站切换，包括：所述用户设备在空闲态从所述第一基站移动到所述第二基站，向第二移动性管理实体发送位置更新请求消息，并接收所述第二移动性管理实体发送的位置更新确认消息，所述第二移动性管理实体用于管理所述第二基站和所述第二网关。
  72. 根据权利要求71所述的方法，其特征在于，所述接收所述第二移动性管理实体发送的位置更新确认消息之后，所述方法还包 括：
    所述用户设备进入空闲态；
    所述用户设备在空闲态接收第一移动性管理实体的寻呼后，响应所述第一移动性管理实体的寻呼，并接收所述第一网关缓存并转发的下行数据，所述第一移动性管理实体用于管理所述第一基站和所述第一网关；
    或者，所述用户设备在空闲态接收第二移动性管理实体的寻呼后，响应所述第二移动性管理实体的寻呼，并接收所述第一网关缓存并转发的下行数据，所述第一移动性管理实体用于管理所述第一基站和所述第一网关。
  73. 一种移动性管理方法，应用于第一基站，其特征在于，
    当所述用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，所述第一基站向所述第二基站发送数据转发隧道的建立请求消息，并接收所述第二基站发送的所述数据转发隧道的建立确认消息；
    其中，所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
    在接收所述第二基站发送的所述数据转发隧道的删除请求消息后，向所述第二基站发送所述数据转发隧道的删除确认消息，并释放所述数据转发隧道；
    在释放所述数据转发隧道后，指示所述第一网关释放所述第一 IP地址。
  74. 根据权利要求73所述的方法，其特征在于，所述第一基站向所述第二基站发送数据转发隧道的建立请求消息之前，所述方法还包括：
    所述第一基站接收所述用户设备发送的第二网关标识，所述第二网关标识用于指示第二网关；
    所述第一基站根据所述第二网关标识确定所述第二网关与所述第一网关是否为同一网关；
    当所述第二网关与所述第一网关不是同一网关时，所述第一基站向所述用户设备发送判断指示消息，以便于所述用户设备向所述第二网关发送获取IP地址的请求消息，并接收所述第二网关发送的所述第二IP地址，其中，所述判断指示消息用于指示所述第二网关与所述第一网关不是同一网关。
  75. 一种移动性管理方法，应用于第二基站，其特征在于，
    当所述用户设备由所述第一基站向所述第二基站切换时，在第二子流建立之前，所述第二基站接收所述第一基站发送的数据转发隧道的建立请求消息，并向所述第一基站发送所述数据转发隧道的建立确认消息；
    其中，所述第二子流为所述用户设备使用第二网际互联协议IP地址与通信对端建立的子流，所述第二IP地址为第二网关为所述用户设备分配的IP地址，所述第二网关与所述第二基站连接，所述数据转发隧道为所述第一基站与第二基站之间的数据转发通道，所述数据转发隧道包括下行数据转发隧道或者上行数据转发隧道，或者所述数据转发隧道包括所述下行数据转发隧道和所述上行数据转发隧道，所述数据转发通道用于传输第一子流的数据，所述第一子流为所述用户设备在由所述第一基站向所述第二基站切换之前，使用第一IP地址与所述通信对端建立的子流，所述第一IP地址为第一网关为所述用户设备分配的IP地址，所述第一网关与所述第一基站连接；
    在所述第一子流撤消后，向所述第一基站发送所述数据转发隧道 的删除请求消息，并接收所述第一基站发送的所述数据转发隧道的删除确认消息；
    在接收所述第一基站发送的所述数据转发隧道的删除确认消息后，释放所述数据转发隧道。
PCT/CN2014/090274 2014-11-04 2014-11-04 一种移动性管理的方法、装置及系统 WO2016070333A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2014/090274 WO2016070333A1 (zh) 2014-11-04 2014-11-04 一种移动性管理的方法、装置及系统
EP14905481.9A EP3209043B1 (en) 2014-11-04 2014-11-04 Mobility management method, apparatus, and system
CN201480033896.1A CN105874830B (zh) 2014-11-04 2014-11-04 一种移动性管理的方法、装置及系统
US15/586,151 US20170238215A1 (en) 2014-11-04 2017-05-03 Mobility management method, apparatus, and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/090274 WO2016070333A1 (zh) 2014-11-04 2014-11-04 一种移动性管理的方法、装置及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/586,151 Continuation US20170238215A1 (en) 2014-11-04 2017-05-03 Mobility management method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2016070333A1 true WO2016070333A1 (zh) 2016-05-12

Family

ID=55908355

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/090274 WO2016070333A1 (zh) 2014-11-04 2014-11-04 一种移动性管理的方法、装置及系统

Country Status (4)

Country Link
US (1) US20170238215A1 (zh)
EP (1) EP3209043B1 (zh)
CN (1) CN105874830B (zh)
WO (1) WO2016070333A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017147752A1 (zh) * 2016-02-29 2017-09-08 华为技术有限公司 一种移动性管理的方法、装置及系统
CN108370527A (zh) * 2015-09-07 2018-08-03 源讯公司 通过使用局域计算机网络无线通信协议来建立并保持从移动客户端站对因特网的接入的方法和装置

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10602560B2 (en) * 2015-06-26 2020-03-24 Telefonaktiebolaget Lm Ericsson (Publ) First network node and methods therein, for determining whether a second multi path transmission control protocol connection is to be initiated
CN108353334B (zh) * 2015-12-25 2020-09-04 华为技术有限公司 业务传输方法、装置及设备
CN110419243A (zh) * 2017-04-06 2019-11-05 株式会社Ntt都科摩 通信系统
CN111837371A (zh) * 2018-01-26 2020-10-27 Idac控股公司 基于增强mptcp的应用移动性
US10575234B2 (en) 2018-02-05 2020-02-25 Ofinno, Llc Wireless device handover in a wireless network with bearer capabilities
US10069726B1 (en) * 2018-03-16 2018-09-04 Tempered Networks, Inc. Overlay network identity-based relay
US10116539B1 (en) 2018-05-23 2018-10-30 Tempered Networks, Inc. Multi-link network gateway with monitoring and dynamic failover
US10158545B1 (en) 2018-05-31 2018-12-18 Tempered Networks, Inc. Monitoring overlay networks
CN109451528B (zh) * 2018-12-27 2021-11-23 中国移动通信集团江苏有限公司 异常小流量话单处理方法、装置、设备及计算机存储介质
WO2021042400A1 (zh) * 2019-09-06 2021-03-11 华为技术有限公司 路径切换方法、通信装置和通信系统
US10911418B1 (en) 2020-06-26 2021-02-02 Tempered Networks, Inc. Port level policy isolation in overlay networks
CN112020112B (zh) * 2020-07-27 2021-10-01 北京邮电大学 Sdn架构下基于mptcp的异构网络切换方法和系统
WO2022042606A1 (en) * 2020-08-25 2022-03-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for service management
US11070594B1 (en) 2020-10-16 2021-07-20 Tempered Networks, Inc. Applying overlay network policy based on users
US10999154B1 (en) 2020-10-23 2021-05-04 Tempered Networks, Inc. Relay node management for overlay networks

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101128022A (zh) * 2006-08-18 2008-02-20 华为技术有限公司 终端切换方法及装置、源接入网关地址获取方法及装置
WO2009067494A1 (en) * 2007-11-19 2009-05-28 Cellco Partnership D/B/A Verizon Wireless Low latency handover between wireless communication networks using different radio access technologies
US20120258674A1 (en) * 2011-04-11 2012-10-11 Interdigital Patent Holdings, Inc. Session manager and source internet protocol (ip) address selection
CN103517264A (zh) * 2012-06-29 2014-01-15 华为终端有限公司 用于切换网络的方法和装置

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2532780A1 (en) * 2003-07-17 2005-02-03 Starent Networks Corporation Methods and systems for providing improved handoffs in a wireless communication system
US8483174B2 (en) * 2007-04-20 2013-07-09 Qualcomm Incorporated Method and apparatus for providing gateway relocation
EP2214360B1 (en) * 2007-10-30 2016-06-29 NTT DoCoMo, Inc. Mobile communication method and radio base stations
US8661146B2 (en) * 2011-10-13 2014-02-25 Cisco Technology, Inc. Systems and methods for IP reachability in a communications network
US9883437B2 (en) * 2012-06-19 2018-01-30 Qualcomm Incorporated Systems and methods for enhanced network handoff to wireless local area networks
US8923880B2 (en) * 2012-09-28 2014-12-30 Intel Corporation Selective joinder of user equipment with wireless cell
US9049588B2 (en) * 2013-02-28 2015-06-02 Blackberry Limited Communicating data in a predefined transmission mode
KR20140124116A (ko) * 2013-04-16 2014-10-24 삼성전자주식회사 이동 통신 네트워크에서 데이터-패스를 최적화시키는 장치 및 방법
US9867084B2 (en) * 2013-10-18 2018-01-09 Samsung Electronics Co., Ltd. Method and apparatus for anchoring terminal in wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101128022A (zh) * 2006-08-18 2008-02-20 华为技术有限公司 终端切换方法及装置、源接入网关地址获取方法及装置
WO2009067494A1 (en) * 2007-11-19 2009-05-28 Cellco Partnership D/B/A Verizon Wireless Low latency handover between wireless communication networks using different radio access technologies
US20120258674A1 (en) * 2011-04-11 2012-10-11 Interdigital Patent Holdings, Inc. Session manager and source internet protocol (ip) address selection
CN103517264A (zh) * 2012-06-29 2014-01-15 华为终端有限公司 用于切换网络的方法和装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108370527A (zh) * 2015-09-07 2018-08-03 源讯公司 通过使用局域计算机网络无线通信协议来建立并保持从移动客户端站对因特网的接入的方法和装置
CN108370527B (zh) * 2015-09-07 2020-12-01 源讯公司 建立并保持对因特网的接入的方法、装置和存储介质
WO2017147752A1 (zh) * 2016-02-29 2017-09-08 华为技术有限公司 一种移动性管理的方法、装置及系统
US10945180B2 (en) 2016-02-29 2021-03-09 Huawei Technologies Co., Ltd. Mobility management method, apparatus, and system

Also Published As

Publication number Publication date
CN105874830A (zh) 2016-08-17
EP3209043A4 (en) 2018-02-28
EP3209043A1 (en) 2017-08-23
CN105874830B (zh) 2019-10-25
EP3209043B1 (en) 2020-03-25
US20170238215A1 (en) 2017-08-17

Similar Documents

Publication Publication Date Title
WO2016070333A1 (zh) 一种移动性管理的方法、装置及系统
CN109600802B (zh) 数据传输方法、相关设备及系统
JP6727341B2 (ja) 通信制御方法および関連するネットワーク要素
US10945180B2 (en) Mobility management method, apparatus, and system
US10098042B2 (en) MME, local server, MME-local server interface, and data transmission method for optimized data path in LTE network
JP2021504991A (ja) アプリケーションのためのトラフィックをハンドリングするための方法および機能
WO2011000318A1 (zh) 切换控制的方法和设备
CN109673026B (zh) 数据转发方法、装置和系统
CN110662308B (zh) 一种通信方法及装置
RU2667150C2 (ru) Устройство управления и способ управления передачей обслуживания по однонаправленному каналу
JP6976362B2 (ja) 通信方法および通信装置
WO2009121251A1 (zh) 实现路由优化的方法、系统及装置
CN114651477A (zh) 用于用户面处理的系统和方法
KR102017167B1 (ko) 무선 통신 시스템에서 데이터 트래픽 분산을 위한 방법 및 장치
WO2011143997A1 (zh) 一种实现路由选择的方法和装置
WO2015180141A1 (zh) 一种业务路径变更方法及装置
EP2850912B1 (en) Efficient distribution of signaling messages in a mobility access gateway or local mobility anchor
WO2011023125A1 (zh) 释放连接的方法、装置及系统
WO2016070339A1 (zh) 一种移动性管理的方法、装置及系统
WO2022099484A1 (zh) 标识发送方法和通信装置
WO2017091986A1 (zh) 业务流转发功能部署方法、装置及系统
WO2015089837A1 (zh) 路由优化的方法、路由器及位置管理实体
WO2015100748A1 (zh) 路由方法及路由装置
WO2011097988A1 (zh) 对本地ip数据进行管理的方法及移动通信系统
WO2011103707A1 (zh) 实现锚点切换的全球微波互联接入（wimax）系统及其切换方法

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014905481

Country of ref document: EP