WO2009152669A1 - 网络切换实现方法及系统以及移动节点 - Google Patents

网络切换实现方法及系统以及移动节点 Download PDF

Info

Publication number
WO2009152669A1
WO2009152669A1 PCT/CN2008/073405 CN2008073405W WO2009152669A1 WO 2009152669 A1 WO2009152669 A1 WO 2009152669A1 CN 2008073405 W CN2008073405 W CN 2008073405W WO 2009152669 A1 WO2009152669 A1 WO 2009152669A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
mobile
interface
access gateway
mobile node
Prior art date
Application number
PCT/CN2008/073405
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 EP08874673.0A priority Critical patent/EP2293497B1/en
Priority to US12/999,747 priority patent/US9167482B2/en
Publication of WO2009152669A1 publication Critical patent/WO2009152669A1/zh

Links

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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present invention relates to the field of communications, and in particular, to a network handover implementation method and system, and a mobile node.
  • BACKGROUND OF THE INVENTION Proxy Mobile Internet Protocol version 6 (PMIPv6 for short) is a network layer scheme for providing mobility management on the Internet (Internet), which enables a mobile node (Mobile Node, referred to as For MN), the ongoing communication is not interrupted when the link is switched.
  • ⁇ 's mobility management mechanism is implemented by the network device agent to implement mobility management, so that when any link in a 6 ⁇ 6 management i or (PMIPv6 Domain) moves, it can still pass its IPv6 home network prefix (Home Network Prefix, Referred to as HNP) and / or IPv4 Home Address is accessed, that is, the MN's IPv6 home network prefix and / or IPv4 home address remain unchanged, the MN believes that it has not moved at the IP layer, MN is in progress Business is kept continuous.
  • Figure 1 is a schematic diagram of the PMIPv6 management i or architecture. As shown in Figure 1, the PMIPv6 Domain is mainly composed of a Local Mobility Anchor (LMA) and a Mobile Access Gateway (MAG).
  • LMA Local Mobility Anchor
  • MAG Mobile Access Gateway
  • the MN consists of, where the network consists of LMA and MAG.
  • 2 is an architectural diagram of an Evolved Packet System (EPS).
  • EPS Evolved Packet System
  • 3GPP 3rd Generation Partnership Project
  • EPC Evolved Packet Core
  • the EPC system supports the access of the Evolved Universal Terrestrial Radio Access Network (E-UTRAN); the EPC system supports the access of the Non-3GPP access network, for example, the global microwave interconnection access ( Worldwide Interoperability for Microwave Access, referred to as WiMAX) access network.
  • the user equipment User Equipment, UE for short
  • the UE1 accesses the EPC through the Non-3GPP access network (including the trusted and untrusted Non-3GPP access network).
  • UE2 accesses the EPC through the E-UTRAN.
  • the UE here is the one described in the ⁇ 10 meeting.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • Packet Data Network Gateway Packet Data Network Gateway
  • PDN GW or P-GW Home Subscriber Server
  • HSS Home Subscriber Server
  • 3GPP AAA Server 3GPP Authentication and Authorization Accounting Server
  • e PDG Evolved Packet Data Gateway
  • the MME is responsible for control plane related operations such as mobility management, non-access stratum signaling processing, and user context management
  • the S-GW is an access gateway device connected to the E-UTRAN, and is in the E-UTRAN and the PDN GW.
  • P-GW is the border gateway of the Internet Protocol (IP) service provided by the 3GPP EPS and the Home Public Land Mobile Network (HPLMN), which is responsible for the IP service connection.
  • IP Internet Protocol
  • HPLMN Home Public Land Mobile Network
  • the EPS supports the adoption of PMIPv6 between the S-GW and the P-GW and between the WiMAX access network and the P-GW.
  • the P-GW has the function of LMA
  • the S-GW and WiMAX access network have the MAG. Function, where the UE is the one described in the ⁇ protocol.
  • the non-3GPP radio access network shown in FIG. 2 includes the following two types: Trusted Non 3GPP Access: There is a trust relationship between the 3GPP network and the non-3GPP access network, and the non-3GPP is connected.
  • the incoming network can access the P-GW directly through the S2a interface. Among them, the S2a interface can use PMIPv6.
  • Untrusted Non 3GPP Access There is no trust relationship between the 3GPP network and the non-3GPP access network.
  • the non-3GPP access network must first access the ePDG of the 3GPP network and then pass the S2b interface. Access to the P-GW. At this time, a secure tunnel is established between the UE and the ePDG to ensure secure transmission of data between the UE and the 3GPP network.
  • the S2b interface uses PMIPv6.
  • the LMA is the home agent of the MN in the PMIPv6 management i or, and the LMA is the topology anchor of the MN's home network prefix, which is used to manage the binding state of the MN, where each binding state is Corresponding to the Binding Cache Entry (BCE) managed by the LMA, the content of the BCE includes: a mobile node identifier (MN Identifier), an IPv6 home network prefix currently used by the MN, and/or an IPv4 home address, and current use.
  • Business information ie access point name, Access Point Name, abbreviated as ⁇ ).
  • the LMA can intercept the data packet of the IPv6 home network prefix or the IPv4 home address whose destination address is MN, and forward it to the proxy care-of address (Proxy Care-of Address, referred to as Proxy-CoA) registered by the MN in the BCE.
  • Proxy-CoA is the address of the MAG, where the MAG is an access router, and is used for the mobility of the MN.
  • the MN's mobility includes: the MN accesses or leaves the access link; the MAG is also used for proxy attachment.
  • the MN to the access link manages the mobility related signaling of the MN, including the Proxy Binding Update (PBU) to the LM's LMA and the proxy binding confirmation sent by the LMA.
  • PBU Proxy Binding Update
  • PBA Proxy Binding Acknowledgement
  • the MAG proxy MN establishes the binding state between the MN's IPv6 home network prefix or the IPv4 home address and the Proxy CoA in the LMA, and the LMA saves the binding state as BCE.
  • the MAG After receiving the data packet from the LMA whose destination address is the IPv6 home network prefix or the IPv4 home address of the MN, the MAG forwards the data packet to the MN.
  • the IPv6 home network prefix is a permanent IPv6 address prefix assigned by the network to the MN for use within or within the PMIPv6 management i.
  • the IPv4 home address is a permanent IPv4 address that the network assigns to the MN to use within the PMHV6 management i.
  • the standard IP routing mechanism sends the IP data packet sent to the MN's IPv6 home network prefix or IPv4 home address to its PMIPv6 management i or the LMA is responsible for intercepting the IP data packet, and then looking for the BCE stored therein, according to the BCE.
  • the saved Proxy CoA is forwarded to the corresponding MAG, and the MAG forwards the IP data packet to the corresponding MN according to the destination address or address prefix of the data packet.
  • Binding is the association between the MN's IPv6 home network prefix and/or IPv4 home address and Proxy-CoA.
  • the network needs to determine whether the MN has the ability to reserve addresses between different interfaces. Whether to provide address reservation for the MN.
  • the address reservation refers to: The IP address (including the IPv6 home network prefix and/or the IPv4 home address) to be used before the MN switchover is allocated to the interface for continued use after the MN switches.
  • the MN's IPv6 home network prefix and/or IPv4 home address remain unchanged, the IP service used by the MN before the handover can continue to be used after the handover, and the service continuity is realized. If the network does not provide address reservation, then the MN is The interface 2 will obtain an IPv6 home network prefix and/or an IPv4 home address different from the interface 1. After the switch, the interface 2 will not be able to continuously perform the IP service originally performed on the interface 1, and the IP service will be interrupted, that is, the handover fails.
  • the network side reserves the address for the MN; if the network side does not know whether the MN has the capability, or the network knows that the MN does not have the capability, the network does not provide address reservation. Since the current network side cannot know whether the MN has the ability to reserve addresses between different interfaces, the network does not reserve the pre-switching address for the MN, so that even for the MN having the capability of maintaining the address between different interfaces, Make address reservations for it.
  • the present invention has been made in view of the current problem that an MN having an ability to reserve an address between different interfaces cannot perform address reservation in the case where the network side cannot know its capability, and the present invention aims to provide a An improved network switching implementation solution to solve at least one of the above problems.
  • a network switching implementation method is provided. The network switching implementation method is used in the scenario that the mobile node switches from the first mobile access gateway to the second mobile access gateway to perform local mobility anchor access, where the mobile node passes the first interface and the first mobile access gateway.
  • the method includes the following: After receiving the IP address sent by the MN, the handover target network determines that the access of the MN is a handover access, and the address is allocated to the MN. Further, the IP address is an IP address obtained by the MN at the first mobile access gateway. Further, the handover target network includes a second mobile access gateway and a local mobility anchor.
  • the method provided by the present invention further includes: the local mobility anchor receiving a proxy binding update message from the second mobile access gateway, where the proxy is tied The update message carries the identification information of the mobile node, the IP address of the first interface, and The IP address of the second mobile access gateway; the local mobility anchor searches in its saved binding cache entry for the presence of the identity information of the mobile node and the IP address of the first interface; in the case of the discovery, the local mobility The anchor point continues to determine whether the proxy care-of address in the binding cache entry and the proxy care-of address in the proxy binding update message are the same; if the two are different, the local mobility anchor determines that the connection of the mobile node is a handover connection, and determines the mobile node.
  • the network handover implementation method further includes: the second mobile access gateway receives the proxy binding acknowledgement message, and sends the IP address of the first interface to the mobile node, so that the mobile node is in the The second interface uses the IP address of the first interface.
  • the network handover implementation method further includes: the second mobile access gateway receiving the connection from the mobile node a request, where the connection request carries an IP address of the first interface and identifier information of the mobile node; the second mobile access gateway carries the IP address of the first interface, the identifier information of the mobile node, and the second mobile A proxy binding update message for the IP address of the access gateway is sent to the local mobility anchor.
  • the network handover implementation method includes: after receiving the IP address sent by the MN, the second mobile access gateway determines that the access of the MN is a cross-interface handover access, and sends a proxy binding update message to The local mobility anchor, the message carries the handover indication as a cross-interface handover; the local mobility anchor receives the proxy binding update message, and assigns an IP address to the MN; wherein the IP address is the IP address of the first interface of the MN.
  • a network handover implementation system for a mobile node to switch from a first mobile access gateway to a second mobile access gateway for local mobility anchor A point access scenario, where the mobile node is connected to the first mobile access gateway through the first interface, and is connected to the second mobile access gateway through the second interface.
  • the network switching implementation system includes: a local mobility anchor point and a second mobile access gateway; wherein the local mobility anchor point further includes: a receiving module, configured to receive a proxy binding from the second mobile access gateway And an update message, where the proxy binding update message carries the identifier information of the mobile node, the IP address of the first interface, and the IP address of the second mobile access gateway; the first determining module is configured to use the mobile node The identification information, the binding cache entry corresponding to the mobile node is retrieved, and the IP address of the first interface and the identification information of the mobile node are determined in the binding cache entry.
  • the second determining module is configured to determine the binding cache entry.
  • the sending module is configured to send, to the second mobile access gateway, the IP address of the second mobile access gateway in the proxy forwarding address
  • the proxy binds the acknowledgement message and carries the IP address of the first interface in the proxy binding acknowledgement message.
  • the second mobile access gateway includes: a transceiver module, configured to receive a proxy binding acknowledgement message, and send an IP address of the first interface in the proxy binding acknowledgement message to the mobile node, so that the mobile node is in the second The interface uses the IP address of the first interface.
  • the transceiver module is further configured to receive a connection request from the mobile node, and send the proxy binding update message to the local mobility anchor point, where the connection request carries the IP address of the first interface and the identifier information of the mobile node.
  • another network handover implementation system for a mobile node to switch from a first mobile access gateway to a second mobile access gateway for local mobility anchor access.
  • the mobile node connects to the first mobile access gateway through the first interface, and connects to the second mobile access gateway through the second interface.
  • the network switching implementation system includes: a local mobility anchor point and a second mobile access gateway.
  • the second mobile access gateway specifically includes: a third determining module, configured to receive an IP address sent by the MN, and determine The MN accesses the handover access, and sends a proxy binding update message to the local mobility anchor.
  • the message carries a handover indication.
  • a mobile node is also provided.
  • the mobile node in a case that the mobile node switches from the first mobile access gateway to the second mobile access gateway to access the local mobility anchor point, the mobile node is configured to send a connection request to the second mobile access gateway, where the connection request It carries the IP address of the first interface.
  • FIG. 1 is an architectural diagram of a PMIPv6 management domain according to the related art
  • FIG. 2 is an architectural diagram of an EPS system according to the related art
  • FIG. 3 is a flowchart of a network handover implementation method according to an embodiment of the present invention
  • Figure 5 is a flow chart according to Example 1 of the present invention
  • Figure 5 is a flow chart according to Example 2 of the present invention
  • Figure 6 is a flow chart according to Example 3 of the present invention
  • Figure 7 is a fourth example of the present invention.
  • Figure 8 is a flow chart according to Example 5 of the present invention
  • Figure 9 is a flow chart according to Example 6 of the present invention
  • FIG. 10 is a block diagram of a network switching implementation system according to an embodiment of the present invention.
  • the switching target network receives the IP address sent by the MN
  • the IP address is allocated to the MN.
  • the network side is enabled to reserve the pre-handover address for the user equipment with the address reservation capability. Compared with the prior art, the network side does not know whether the MN has the capability network reserved between the different interfaces, and does not reserve the switch before the MN.
  • the technical solution provided by the embodiment of the present invention enables the switched interface to continuously perform IP services performed on the original interface.
  • FIG. 3 shows a network switching implementation method according to an embodiment of the present invention, which is applied to
  • the scenario in which the MN (or UE) is switched from the first MAG to the LMA from the second MAG, wherein the MN is connected to the first MAG through the first interface, and is connected to the second MAG through the second interface, and the network switching is implemented.
  • the method includes the following processing: Preferably, the second MAG first receives the connection request from the MN, where the connection request carries the IP address of the first interface and the identifier information of the MN; the second MAG carries the IP address of the first interface.
  • the identification information of the MN and the PBU message of the IP address of the second MAG are sent to the LMA.
  • the second MAG receives the PBA message, and sends the IP address of the first interface to the MN, so that the MN uses the IP address of the first interface on the second interface.
  • step S302 to step S308 are shown in FIG. 3.
  • Step S302 The LMA receives the PBU message from the second MAG, where the PBU message carries the identifier information of the MN, the IP address of the first interface, and the IP address of the second MAG, where the proxy care-of address in the PBU message is The IP address of the second MAG.
  • the IP address of the first interface specifically includes: an IPv6 home network prefix and/or an IPv4 home address.
  • S304 The LMA searches, in its saved BCE, whether the identity information of the MN and the IP address of the first interface exist.
  • step S306 If the identifier information of the MN and the IP address of the first interface are found, the LMA continues to determine whether the proxy care-of address in the BCE and the proxy care-of address in the PBU message are the same. S308. If the determination result in step S306 is different, the LMA determines that the connection of the MN is a handover connection, and determines that the mobile node has an address reservation capability, and then sends a PBA message to the second MAG, and carries the first in the PBA message. IP address of the interface. FIG.
  • FIG. 4 illustrates a network handover implementation method according to an embodiment of the present invention, where the method is applied to a scenario in which a MN is switched from a first MAG to an LMA from a second MAG, where the MN passes through the first interface.
  • the first MAG is connected, and is connected to the second MAG through the second interface.
  • the implementation method includes the following processing (steps S402-S406):
  • the MN switches from the first mobile access gateway to the second mobile access gateway, and sends the address obtained by the first mobile access gateway to the second mobile access gateway during the process of accessing the second mobile access gateway.
  • the message may also carry the address sent by the MN;
  • the local mobility anchor After receiving the proxy binding update message, the local mobility anchor performs corresponding processing.
  • the local mobility anchor may include one of the following processing manners: (1) the local mobility anchor performs handover processing according to the handover indication to the second MAG. Sending a PBA message, and carrying the IP address of the first interface in the PBA message; (2) Locally moving the error point to check the address in the PBU (the address is the address sent by the MN) and the address in the locally saved BCE, when two If the addresses are inconsistent, the access is considered to be an erroneous access, and the access of the MN is abrupt; (3) The local mobile error check the address in the PBU and the address in the locally saved BCE.
  • the access is considered to be the initial access
  • the address in the PBU is allocated to the MN
  • the address in the BCE is allocated to the MN, or an address is additionally allocated, which is different from the address in the PBU and the BCE.
  • the embodiments of the present invention are respectively described below according to different connection request modes.
  • Example 1 In the example, the MN switches from MAG1 to MAG2, and the MN connects to the interface of MAG2. Different from the interface connected to MAGI, the MN notifies MAG2 of the IP address used by the interface before switching (including IPv6 HNP and/or IPv4 home address) through DHCP.
  • Figure 5 is a flow chart showing an example 1 of the method of the present invention. As shown in FIG.
  • the network handover implementation method includes the following steps (S502-S512): S502, the MN switches to the MAG2, and the MN uses the address configuration mode according to the adopted address.
  • the MN initiates a Dynamic Host Configuration Protocol (DHCP) request (Solicit) to the MAG2; or, the MN uses the no-dog configuration mode ( Stateless Auto-Configuration ), initiates a DHCP information request (Information-request) to MAG2.
  • DHCP Dynamic Host Configuration Protocol
  • the MN uses the no-dog configuration mode
  • DHCP information request Information-request
  • IPv6 HNP fills in the IPv6 home network prefix option of the PBU according to the IPv6 HNP and/or the IPv4 home address indicated in the received request (ie, the requested source address and/or the DHCP request content) (IPv6 Home Network) Prefix option ) and / or ⁇ ) capture the IPv4 home address to fill in the IPv4 Home Address option of the PBU, the PBU sends it to the LMA, and includes the MN identity in the PBU; or, it can be executed according to S404: MAG2 reception After the address sent by the MN, it is determined that the current MN access is a handover access, and the proxy binding update message is sent to the local mobility anchor, and the handover indication is set to be a cross-interface switch in the message;
  • the LMA After receiving the PBU, the LMA searches for the saved BCE by using the MN identifier in the PBU and the IPv6 home network prefix option and/or the IPv4 home address option, and finds the same user identity and IPv6 home network prefix option and/or IPv4 hometown.
  • the Proxy-CoA (that is, the IP address of MAG1) is different; therefore, the LMA considers that the MN has switched, that is, the PBU is considered to be an update, and the address is reserved for the user during the update process, that is, the MN is
  • the IPv6 home network prefix and/or the IPv4 home address used by the interface before the switchover are allocated to the MN switched interface to continue to use, and the IPv6 home network prefix and/or the IPv4 home address are sent to the MAG2 through the PBA; or, 406 execution;
  • the MAG2 sends a DHCP advertisement (Advertise) to the MN, and sends the IPv6 home network prefix and/or the IPv4 home address received in the PBA to the MN; when using the ⁇ ) dog state automatic configuration The MAG2 sends a DHCP reply (Reply) to the MN, and the IPv6 home network prefix and/or the IPv4 home address received in the PBA are sent to the MN, where the MN is The new interface continues to use the IPv6 home network prefix and/or IPv4 home address, and the handover process is completed;
  • the MN sends a DHCP request (Request) to the MAG2, requesting to use the IPv6 home network prefix and/or the IPv4 home address received in S508; S512, when the MAG2 receives the request sent by the MN in S510. Afterwards, MAG2 sends a DHCP confirm to the MN, confirming that the MN can use the HNP received in S508. After receiving the response message, the MN continues to use the IPv6 home network prefix and/or IPv4 home address on the new interface, and the handover process carry out.
  • Example 2 In this example, the MN switches from MAG 1 to MAG2.
  • the interface connecting the MN to the MAG2 is different from the interface connected to the MAG1.
  • the MN uses the routing request (RS) to use the IP address used by the interface before the handover (including the IPv6 home network prefix and / or IPv4 home address) Notify MAG2.
  • RS routing request
  • 6 is a flowchart of the second embodiment of the method according to the present invention.
  • the network handover implementation method according to the embodiment of the present invention includes the following steps S602-S608: S602, the MN switches to MAG2, and uses the switch.
  • the IPv6 home network prefix and/or the IPv4 home address of the interface are used as the source address of the routing request, and the RS is sent to the MAG2;
  • step S604 the source address of the routing request received by the MAG2, and the source address is filled in the IPv6 home network prefix option and/or the IPv4 home address option of the PBU, ⁇ !
  • the PBU is sent to the LMA, and the user identity is included in the PBU.
  • the step may be performed according to the foregoing step S404.
  • the LMA sends a PBA to the MAG2, where the PBA includes the MN's IPv6 home network prefix and/or IPv4 hometown.
  • the step may be performed according to step S406; in step S608, the MAG2 sends a Router Advertisement to the MN, and the HNP notifies the MN that the MN continues to use the IPv6 home network prefix and/or the IPv4 home address, and the handover process is completed.
  • Example 3 In this example, the MN switches from MAG1 to MAG2. The interface connecting the MN to the MAG2 is different from the interface connected to the MAG1. The MN uses the Layer 2 attach request to change the IP used by the interface before switching. The address (including the IPv6 home network prefix and/or the IPv4 home address) is notified to MAG2.
  • FIG. 7 is a flowchart of the third method of the method according to the present invention. As shown in FIG. 7, the network switching implementation method according to the embodiment of the present invention includes the following steps S702 to S708:
  • S702 The MN switches to the MAG2, and initiates a Layer 2 (link layer) attach request to the MAG2, where the request includes an IPv6 home network prefix and/or an IPv4 home address obtained when the MN attaches to the MAG1.
  • Layer 2 link layer
  • step S704 the IPv6 home network prefix and/or the IPv4 home address in the attach request received by the MAG2, and filling the PBU with the IPv6 home network prefix option and/or the IPv4 home address option, and sending the PBU to the LMA, and returning the PBU to the PBU.
  • the step may also be performed according to step S404;
  • the LMA sends a PBA to the MAG2, where the PBA includes the IPv6 home network prefix and/or the IPv4 home address of the MN; or, the step may also be performed according to step S406; in step S708, the MAG2 sends an attach accept message to the MN, where, the attach The accept message includes the MN's IPv6 home network prefix and/or the IPv4 home address. After receiving the attach accept message, the MN continues to use the IPv6 home network prefix and/or the IPv4 home address on the new interface, and the handover process is completed.
  • Example 4 This embodiment describes that the UE switches from the Non-3GPP access network (including the trusted or untrusted Non-3GPP access network) to the E-UTRAN, and the UE connects to the E-UTRAN interface and connects to the Non-3GPP access.
  • the interface of the network is different.
  • the UE notifies the S-GW of the IP address (including the IPv6 home network prefix and/or the IPv4 home address) used by the interface before the handover through the Layer 2 attach request or the PDN connection request sent to the E-UTRAN.
  • Figure 8 is a flow chart showing an example 4 of the method according to the present invention, wherein the Non-3 GPP access network is a WIMAX access network.
  • the network switching implementation method according to the embodiment of the present invention includes the following steps S802 to S816:
  • the UE switches to the E-UTRAN, and initiates an attach request or a PDN connection request to the MME, where the attach request includes the UE identifier and an IP address used by the interface connected to the WiMAX access network before the handover (including an IPv6 home network prefix and/or IPv4 home address), when the MME initiates a PDN connection request, where the connection request also includes an access point name (Access Point Name, Jane Called APN);
  • the MME, the HSS, and the UE jointly perform access authentication on the UE, and the identity of the user of the insurance card is allowed to access the EPC.
  • the step S804 may not be performed;
  • the MME The HSS initiates a location update, and updates the current location information of the UE in the HSS, and the HSS initiates the process of inserting the subscription data to the MME, and sends the subscription data of the user to the MME, where the MME saves the user subscription information.
  • the MME initiates the PDN connection request in the foregoing step S802. At this time, the step S806 may not be performed;
  • the MME searches for the P-GW that can provide the service corresponding to the APN according to the default APN (the default access point name) indicated in the user subscription information, or when the foregoing steps are performed.
  • the MME may find the P-GW that can provide the service corresponding to the APN according to the APN included in the request, and select an S-GW that can contact the P-GW.
  • the S-GW initiates establishment, and the default load request, wherein, the default 7
  • the option and/or the IPv4 home address is filled in the IPv4 home address option of the PBU, and the PBU is sent to the P-GW, and the user identity and the default APN or APN are also included in the PBU; or, the step may also be performed according to step S404; Step S812: After receiving the PBU, the P-GW searches for the saved BCE by using the user identity in the PBU, the IPv6 home network prefix option, and/or the IPv4 home address option, and the default APN or APN, and finds the same user identity, IPv6 hometown.
  • Step S814 the S-GW uses the establish default bearer response message
  • the received IPv6 home network prefix and/or the IPv4 home address are sent to the ⁇ ; step S816, ⁇ notifying that the wireless network attachment is completed, establishing a wireless load between the wireless network and the UE, and ⁇ capturing the IPv6 home network prefix and/or through the wireless network; Or the IPv4 home address informs the UE that the UE continues to use the IPv6 home network prefix and/or the IPv4 home address to complete the handover from the Non-3GPP access network
  • the WiMAX access network accesses the EPC; the interface connecting the UE to the E-UTRAN is different from the interface connected to the WiMAX access network.
  • the DHCP request sent by the UE to the WiMAX will switch the IP address used by the pre-interface (including the IPv6 home network prefix and / or IPv4 home address) Notify the WiMAX access network.
  • 9 is a flowchart of a fifth method according to the method of the present invention. As shown in FIG.
  • the network handover implementation method includes the following steps S902-S912: Step S902, the UE accesses the WiMAX access network, and the user identity is Sending to the WiMAX access network, the WiMAX access network is in contact with the HSS/AAA, and the user is authenticated and authorized 4; in step S904, after the user authentication and the 4 authorization are passed, the UE initiates a DHCP request, and the DHCP request process and the foregoing
  • the DHCP request process in step S502 is similar, and is not further described herein; in step S906, the WiMAX access network performs the IPv6 HNP and/or IPv4 home address indicated in the DHCP request received in step S904 (ie, the requested source address).
  • IPv6 HNP fills in the IPv6 Home Network Prefix option of the Binding Update Message (PBU) and/or ⁇ 1 IPv4 Home Address is filled in with the Binding Update Message (PBU)
  • PBU Binding Update Message
  • the IPv4 Home Address option is used to send the PBU to the P-GW, and the user identity is also included in the PBU.
  • the step may be performed according to step S404.
  • Step S910 After receiving the PBU, the P-GW searches for the saved BCE (BCE) by using the user identity in the PBU and the IPv6 Home Network Prefix option and/or the IPv4 Home Address option.
  • BCE saved BCE
  • P-GW checks the Proxy-CoA in the PBU The Proxy-CoA in the BCE, because the IP address of the WiMAX access network gateway is different from the IP address of the MAG (ie, the S-GW) that the UE previously accesses in the E-UTRAN, so the Proxy-CoA and the BCE in the PBU The Proxy-CoA is different. Because the jt ⁇ P-GW considers that the UE has been handed over, that is, the PBU is considered to be an update, and the user is reserved in the update process, and the IPv6 hometown used by the E-UTRAN before the UE handover is used.
  • the network prefix and/or the IPv4 home address are allocated to the interface used by the WiMAX access after the UE is switched, and the IPv6 home network prefix and/or the IPv4 home address are sent to the WiMAX access network through the PBA; or, the step is also Can press Step S406 is performed.
  • Step S912 The WiMAX access network sends the IPv6 home network prefix and/or the IPv4 home address received in the PBA to the UE by using the DHCP mode, and the UE continues to use the IPv6 home network prefix and/or the IPv4 home address to complete. Switching from E-UTRAN to WiMAX.
  • Example 6 This embodiment describes that the UE switches from the E-UTRAN to the untrusted Non-3GPP access network, and accesses the EPC through the untrusted Non-3GPP access network; the UE connects to the E-UTRAN interface and connects to the The interfaces of the untrusted Non-3GPP access network are different. Since the Non-3GPP access network is untrusted, the UE needs to initiate a tunnel connection to the ePDG. The UE configures the pre-switch interface with the configuration pay load (CFG_REQUEST) in the IKE AUTH Request message during the IKEv2 (Internet Key Exchange version 2) authentication and the establishment of the ePDG.
  • CFG_REQUEST configuration pay load
  • the IPv6 home network prefix and/or the IPv4 home address are given to the ePDG.
  • 10 is a flowchart of the sixth method according to the method of the present invention.
  • the network handover implementation method according to the embodiment of the present invention includes the following steps S1002 - S1008: Step S 1002, the UE switches from the E-UTRAN To the untrusted Non-3 GPP access network.
  • the UE finds the IP address of an ePDG according to the IP address of the internally configured ePDG or through the DNS (Domain Name Server, i or the name server), and the UE initiates an IKEv2 authentication and tunnel establishment request to the ePDG in the IKEv2 authentication process.
  • DNS Domain Name Server
  • the CFG_REQUEST (configuration request) in the configuration payload of the message carries the IPv6 home network prefix and/or the IPv4 home address of the pre-switch interface to the ePDG.
  • the IKE authentication request also includes the APN used before the UE handover; in step S1004, the ePDG fills in the IPv6 HNP and/or the IPv4 home address indicated in the CFG_REQUEST received in step S1002, ⁇ )
  • the IPv6 Home Network Prefix option and/or ⁇ ) of the IPv6 home address is filled in with the IPv4 Home Address option and the PBU is sent to the IPv4 Home Address option.
  • the P-GW further includes a user identity NAI (Network Access Identifier) and an APN in the PBU; or, the step may also be performed according to step S404; Step S1006, after the P-GW receives the PBU, the P-GW uses The user identity NAI, APN, and IPv6 Home Network Prefix option and/or IPv4 Home Address option in the PBU find their saved BCE (BCE), find the same user identity, BPN entry for APN and IPv6 Home Network Prefix option and/or IPv4 Home Address option; P-GW checks P in PBU The proxy-CoA in the roxy-CoA and the BCE, because the IP address of the ePDG is different from the IP address of the MAG (that is, the S-GW) that the UE previously accesses in the E-UTRAN, so the Proxy-CoA and the BCE in the PBU The Proxy-CoA is different.
  • NAI Network Access Identifier
  • the P-GW considers that the UE has been handed over, that is, the PBU is updated, and the address is reserved for the user during the update process, and the UE is used in the E-UTRAN before the handover.
  • the IPv6 home network prefix and/or the IPv4 home address are allocated to the UE and then used on the new interface, and the IPv6 home network prefix and/or the IPv4 home address are sent to the ePDG through the PBA.
  • the step may be followed by step S406.
  • Step S1008 In the IKEv2 authentication process, the ePDG sends an IKE AUTH Response message to the UE, where the configuration payload in the message includes a CFG REPLY, which is carried in the CFG_REPLY
  • the IPv6 home network prefix and/or IPv4 home address received in the PBA The UE continues to use the IPv6 home network prefix and/or the IPv4 home address on the new interface to complete the handover from the E-UTRAN to the untrusted Non-3GPP access network.
  • the MN initially accesses the MAG.
  • the MN does not carry an IP address during the access process.
  • the network considers the access as the initial access.
  • the connection between the MN and the MAG may be the connection manner in the first, second, third, fourth, fifth and sixth embodiments, and is not mentioned here.
  • 11 is a flowchart of a method VII according to the method of the present invention.
  • the network handover implementation method according to the embodiment of the present invention includes the following steps S1102 - S1108: Step S 1102, when the MN accesses the MAG, During the access process, the IP address is not carried to the MAG, indicating that the attachment is an initial attachment.
  • step S1104 the MAG does not receive the address from the MN according to the MN attachment process, and considers that the access of the MN is initial attachment and sending.
  • the proxy binding update message is sent to the LMA.
  • Step S1106 After receiving the message, the LMA allocates an IP address and/or an address prefix, and sends the assigned IP address and/or the address prefix to the MAG in the proxy binding confirmation message.
  • Step S1108, The MAG sends the IP address assigned by the LMA to the MN.
  • System Embodiments Embodiments of the present invention provide a network switching implementation system. FIG.
  • FIG. 12 is a block diagram of a system for implementing a network handover according to an embodiment of the present invention, where the implementation system is used for a scenario in which an MN switches from a first MAG to an LMA from a second MAG, where the MN passes the first interface and the first An MAG connection is connected to the second MAG through the second interface.
  • the implementation system includes: an LMA 10 and a second MAG 20, where the LMA 10 specifically includes: a receiving module 110, connected to the second MAG 20, for receiving from a PBU message of the second MAG 20, where the PBU message carries the identifier information of the MN, the IP address of the first interface, and the IP address of the second MAG.
  • the first determining module 120 is connected to the receiving module 110, and configured to The identification information of the MN and the APN information (when the APN information is available), and the BCE corresponding to the MN and the APN are retrieved, and it is determined whether the IP address of the first interface exists in the retrieved BCE, and when the judgment result is that
  • the second determining module 130 is configured to determine whether the proxy care-of address in the retrieved BCE is the same as the IP address of the second MAG in the PBU message.
  • the sending module 140 is connected to the second determining module 130.
  • the LMA determines a handover of the MN is connected is connected to the second MAG sends a PBA message, and carries the IP address of the first interface in PB A message.
  • the second MAG 20 specifically includes: a transceiver module 210, connected to the sending module 140, configured to receive the PBA message, and transmit the IP address of the first interface in the PBA message to the MN, so that the MN is in the second The interface uses the IP address of the first interface.
  • the transceiver module 210 is further configured to receive a connection request from the MN, and send the PBU message to the LMA.
  • the connection request carries the IP address of the first interface and the identifier information of the MN.
  • the present invention further provides a network handover implementation system, configured for a scenario in which a mobile node switches from a first mobile access gateway to a local mobility anchor access from a second mobile access gateway, where the mobile node The first interface is connected to the first mobile access gateway, and is connected to the second mobile access gateway through the second interface, where the implementation system includes: a local mobility anchor point and a second mobile access gateway; wherein, the second mobile interface
  • the gateway includes: a third determining module, configured to: after receiving the IP address sent by the MN, determine that the access of the MN is a cross-interface handover access, and send a proxy binding update message to the local mobility anchor, in the message The carryover indication is switched across interfaces.
  • An embodiment of the present invention provides an MN.
  • the MN in a case where the MN is switched from the first MAG to the second MAG, the MN is configured to send a connection request to the second MAG, where the connection request carries the IP of the first interface. address.
  • the MN here may be the MN in the foregoing method embodiment, and details are not described herein again.
  • the address can be reserved for a user equipment having address reservation capability.
  • the invention is not limited to any specific combination of hardware and software.
  • the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalents, and modifications made within the spirit and principles of the present invention. It should be included in the scope of protection of the present invention.

Landscapes

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

Description

网络切换实现方法及系统以及移动节点 技术领域 本发明涉及通信领域， 具体地， 涉及一种网络切换实现方法及系统以及 移动节点。 背景技术 代理移动 IP十办议第六版 ( Proxy Mobile Internet Protocol version 6 , 简称 为 PMIPv6 ) 是在因特网 （Internet ) 上提供移动性管理的网络层方案， 该协 议能够使移动节点 （ Mobile Node, 简称为 MN )在进行链路切换时不中断正 在进行的通信。 ΡΜΙΡνό的移动性管理机制是由网络设备代理 ΜΝ实施移动性管理， 使 得 ΜΝ在一个 ΡΜΙΡν6管理 i或（PMIPv6 Domain ) 内的任何链路移动时， 仍 然可以通过其 IPv6家乡网络前缀 ( Home Network Prefix, 简称为 HNP ) 和 / 或 IPv4家乡地址 （ Home Address ) 被访问， 即 , MN的 IPv6家乡网络前缀 和 /或 IPv4家乡地址保持不变， MN在 IP层认为自身并没有发生移动， MN 正在进行的业务得以保持连续。 图 1是 PMIPv6管理 i或的架构图， 如图 1所示， PMIPv6 Domain主要由 本地移动 4苗点（ Local Mobility Anchor, 简称为 LMA )、移动接入网关（ Mobile Access Gateway, 简称为 MAG ) 和 MN组成， 其中， 网络由 LMA和 MAG 组成。 图 2是演进的分组系统 （ Evolved Packet System, 简称为 EPS ) 的架构 图。 为了保持第三代移动通信系统在移动通信领域的竟争力， 必须提高其网 络性能以及降低网络建设和运营成本。 因此， 第三代合作伙伴计划 （3rd Generation Partnership Project, 简称为 3GPP ) 的标准化工作组目前正致力研 究核心网系统下一代演进 演进的分组核心网（ Evolved Packet Core, 简称 为 EPC ), 目的是为用户提供更高的传输速率、 更短的传输时延。 EPC 系统 支持演进的通用陆地无线接入网 （ Evolved Universal Terrestrial Radio Access Network, 简称为 E-UTRAN ) 的接入； EPC系统支持 Non-3GPP接入网的接 入， 例如， 全球微波互联接入 ( Worldwide Interoperability for Microwave Access , 简称为 WiMAX )接入网。 如图 2所示， 用户设备 ( User Equipment, 简称为 UE ) 处于非漫游情 况下， UE1通过 Non-3GPP接入网 （包括信任的和不信任的 Non-3GPP接入 网）接入 EPC, 而 UE2通过 E-UTRAN接入 EPC。 这里的 UE是 ΡΜΙΡνό十办 议中描述的 ΜΝ。 图 2 中示出的网元还包括： 移动管理实体 ( Mobility Management Entity, 简称为 MME )、 月 务网关 （Serving Gateway, 简称为 S-GW )、分组数据网络网关（ Packet Data Network Gateway, 简称为 PDN GW 或 P-GW )、 归属用户月 务器 （ Home Subscriber Server, 简称为 HSS )、 3GPP 认证授权计费服务器 （ 3GPP AAA服务器）， 演进的分组数据网关 （ Evolved Packet Data Gateway , 简称为 e PDG )。 其中， MME负责移动性管理、 非接入层信令的处理、 用户的上下文管 理等控制面相关工作； S-GW 是与 E-UTRAN 相连的接入网关设备， 在 E-UTRAN和 PDN GW之间转发数据； P-GW是 3GPP EPS与公共陆地移动 网络 ( Home Public Land Mobile Network, 简称为 HPLMN )提供的网络十办议 ( Internet Protocol, 简称为 IP ) 业务的边界网关， 负责 IP业务的接入、 在 EPS与 IP业务网间转发数据。
EPS支持在 S-GW和 P-GW之间以及 WiMAX接入网与 P-GW之间采 用 PMIPv6十办议， 其中， P-GW具有 LMA的功能， S-GW和 WiMAX接入网 具有 MAG的功能， 这里的 UE是 ΡΜΙΡνό协议中描述的 ΜΝ。 如图 2所示的非 3GPP无线接入网包括以下两种类型： 信任的非 3GPP接入网 （ Trusted Non 3GPP Access ): 3GPP网络和该非 3GPP接入网络之间存在信任关系 ,非 3GPP接入网络可以直接通过 S2a接口 接入 P-GW。 其中， S2a接口可以使用 PMIPv6。 不信任的非 3GPP接入网 （ Untrusted Non 3GPP Access ): 3GPP网络和 该非 3GPP接入网络之间不存在信任关系 , 非 3GPP接入网络必须首先接入 3GPP网络的 ePDG, 然后再通过 S2b接口接入 P-GW。 这时 UE与 ePDG之 间建立安全隧道， 保证 UE 与 3GPP 网络之间数据的安全传输。 其中， S2b 接口使用 PMIPv6。
LMA是 MN在 PMIPv6管理 i或内的家乡代理 , 并且 , LMA是 MN的家 乡网络前缀的拓朴锚点， 用于管理 MN的绑定状态， 其中， 每个绑定状态都 对应于 LMA管理的绑定緩存条目 （ Binding Cache Entry , 简称为 BCE ) , 该 BCE的内容包括： 移动节点标识 （MN Identifier )、 MN当前使用的 IPv6家 乡网络前缀和 /或 IPv4 家乡地址、 当前使用的业务信息 （即接入点名称， Access Point Name , 简称为 ΑΡΝ )。 LMA能够截取其管理 i或内目的地址为 MN的 IPv6家乡网络前缀或 IPv4 家乡地址的数据包，并转发到 BCE中 MN注册的代理转交地址（ Proxy Care-of Address , 简称为 Proxy-CoA )。 该 Proxy-CoA为 MAG的地址， 其中， MAG 是一个接入路由器， 用于 3艮踪 MN的移动， 这里的 MN的移动包括： MN接 入或离开接入链路； MAG 还用于代理附着到其接入链路上的 MN, 管理与 MN 的移动性相关的信令， 包括向 MN 的 LMA发起代理绑定更新 ( Proxy Binding Update, 简称为 PBU ) 以及接收 LMA发来的代理绑定确认 ( Proxy Binding Acknowledgement, 简称为 PBA )。 通过 PBU和 PBA, MAG代理 MN在 LMA中建立 MN的 IPv6家乡网络前缀或 IPv4家乡地址与 Proxy CoA 之间的绑定状态， LMA保存该绑定状态为 BCE。 MAG在接收到来自 LMA 的目的地址为 MN的 IPv6家乡网络前缀或 IPv4家乡地址的数据包后， 转发 该数据包给 MN。
IPv6 家乡网络前缀是网络分配给 MN在 PMIPv6管理 i或内使用的永久 的 IPv6地址前缀。 IPv4家乡地址是网络分配给 MN在 PMHV6管理 i或内使 用的永久的 IPv4地址。标准的 IP路由机制会 发送给 MN的 IPv6家乡网络 前缀或 IPv4家乡地址的 IP数据包发送到其 PMIPv6管理 i或， LMA负责截取 该 IP数据包， 之后查找其中保存的 BCE , 才艮据 BCE中保存的 Proxy CoA转 发给相应的 MAG, MAG再才艮据数据包的目的地址或地址前缀将 IP数据包 转发给相应的 MN。 绑定 （Binding ) 是 MN 的 IPv6 家乡网络前缀和 /或 IPv4 家乡地址与 Proxy-CoA之间的关联关系。 如图 1所示， 在 PMIPv6 Domain中， 当 MN由通过接口 1接入 MAG1、 切换为通过接口 2接入 MAG2时 ,网络需要才艮据 MN是否具有在不同接口之 间保留地址的能力， 判断是否需要为 MN提供地址保留。 该地址保留是指： 将在 MN切换前接口使用的 IP地址 （包括 IPv6家乡网络前缀和 /或 IPv4家 乡地址） 在 MN在切换后分配给接口继续使用。 当 MN的 IPv6家乡网络前 缀和 /或 IPv4家乡地址保持不变时， MN在切换前使用的 IP业务可以在切换 后继续使用 , 业务连续性得以实现。 如果网络不提供地址保留， 那么 MN在 接口 2将获得不同于接口 1的 IPv6家乡网络前缀和 /或 IPv4家乡地址， 切换 后接口 2将不能连续进行原来在接口 1进行的 IP业务， 该 IP业务将发生中 断， 即， 切换失败。 目前， 如果网络侧知道 MN有该能力 , 则网络为 MN保留该地址； 如 果网络侧不知道 MN是否有该能力， 或者网络知道 MN没有该能力， 那么网 络不提供地址保留。 由于目前网络侧在无法获知 MN 是否具有在不同接口之间地址保留的 能力的情况下， 网络不为 MN保留切换前地址， 使得即使对于具有在不同接 口之间地址保留的能力的 MN , 也无法为其进行地址保留。 发明内容 针对目前对于具有在不同接口之间地址保留的能力的 MN,在网络侧无 法获知其能力的情况下无法为其进行地址保留的问题而提出本发明 , 为此， 本发明旨在提供一种改进的网络切换实现方案， 以解决上述问题至少之一。 为了实现上述目的 , 才艮据本发明的一个方面， 提供了一种网络切换实现 方法。 上述网络切换实现方法，用于移动节点从第一移动接入网关切换到第二 移动接入网关进行本地移动锚点接入的场景， 其中， 移动节点通过第一接口 与第一移动接入网关连接， 并通过第二接口与第二移动接入网关连接， 该方 法包括如下处理： 切换目标网络接收到 MN发送的 IP地址后 , 判断 MN的接入为切换接 入， 夺 地址分配给 MN。 进一步地， IP地址为 MN在第一移动接入网关获得的 IP地址。 进一步地， 切换目标网络包括第二移动接入网关和本地移动锚点。 进一步地， 若本地移动锚点判断 MN 的接入为切换接入， 则本发明提 供的方法还包括： 本地移动锚点接收来自第二移动接入网关的代理绑定更新消息， 其中， 代理绑定更新消息中携带有移动节点的标识信息、 第一接口的 IP地址、 以及 所述第二移动接入网关的 ip地址; 本地移动锚点在其保存的绑定緩存条目中查找是否存在移动节点的标 识信息以及第一接口的 IP地址； 在查找到的情况下，本地移动锚点继续判断绑定緩存条目中的代理转交 地址和代理绑定更新消息中的代理转交地址是否相同； 如果二者不同， 则本地移动锚点判断移动节点的连接为切换连接， 并且 判断移动节点具有地址保留能力， 向第二移动接入网关发送代理绑定确认消 息， 并在代理绑定确认消息中携带第一接口的 IP地址。 进一步地，代理绑定更新消息中的代理转交地址为第二移动接入网关的 IP地址。 进一步地， 才艮据本发明的网络切换实现方法还包括： 第二移动接入网关接收代理绑定确认消息， 并将其中的第一接口的 IP 地址发送到移动节点 , 以使移动节点在第二接口使用第一接口的 IP地址。 进一步地，在本地移动 4苗点接收来自第二移动接入网关的代理绑定更新 消息之前， 才艮据本发明的网络切换实现方法还包括： 第二移动接入网关接收来自移动节点的连接请求， 其中， 连接请求中携 带有第一接口的 ip地址以及移动节点的标识信息； 第二移动接入网关将携带有所述第一接口的 IP地址、 移动节点的标识 信息、以及第二移动接入网关的 IP地址的代理绑定更新消息发送到本地移动 锚点。 进一步地， 才艮据本发明的网络切换实现方法包括： 第二移动接入网关收到 MN发来的 IP地址后， 判断 MN的接入为跨接 口切换接入， 发送代理绑定更新消息给本地移动锚点， 该消息中携带切换指 示为跨接口切换； 本地移动锚点收到代理绑定更新消息， 将 IP地址分配给 MN; 其中上述 IP地址为 MN的第一接口的 IP地址。 为了实现上述目的 , 才艮据本发明的另一方面， 还提供了一种网络切换实 现系统， 该系统用于移动节点从第一移动接入网关切换到第二移动接入网关 进行本地移动锚点接入的场景， 其中， 移动节点通过第一接口与第一移动接 入网关连接， 并通过第二接口与第二移动接入网关连接。 根据本发明的网络切换实现系统包括：本地移动锚点以及第二移动接入 网关； 其中， 上述的本地移动锚点又具体包括： 接收模块，用于接收来自第二移动接入网关的代理绑定更新消息，其中， 代理绑定更新消息中携带有移动节点的标识信息、 第一接口的 IP地址、以及 第二移动接入网关的 IP地址； 第一判断模块， 用于才艮据移动节点的标识信息， 检索与移动节点对应的 绑定緩存条目 ,判断绑定緩存条目中是否存在第一接口的 IP地址以及移动节 点的标识信息； 第二判断模块，用于判断绑定緩存条目中的代理转交地址和代理绑定更 新消息中的第二移动接入网关的 IP地址是否相同； 发送模块， 用于在第二判断模块的判断结果为不同的情况下， 向第二移 动接入网关发送代理绑定确认消息， 并在代理绑定确认消息中携带第一接口 的 IP地址。 进一步地， 第二移动接入网关包括： 收发模块， 用于接收代理绑定确认消息 , 并将代理绑定确认消息中的第 一接口的 IP地址发送到移动节点 ,以使移动节点在第二接口使用第一接口的 IP地址。 进一步地， 收发模块还用于接收来自移动节点的连接请求， 并将代理绑 定更新消息发送到本地移动锚点； 其中， 连接请求中携带有第一接口的 IP地 址以及移动节点的标识信息。 为了实现上述目的 , 根据本发明的再一方面， 还提供了另一种网络切换 实现系统， 用于移动节点从第一移动接入网关切换到第二移动接入网关进行 本地移动锚点接入的场景， 其中， 移动节点通过第一接口与第一移动接入网 关连接， 并通过第二接口与第二移动接入网关连接。 根据本发明的网络切换实现系统包括：本地移动锚点以及第二移动接入 网关； 其中， 第二移动接入网关又具体包括： 第三判断模块 , 用于接收 MN发来的 IP地址 , 判断 MN的接入为切换 接入，发送代理绑定更新消息给本地移动锚点， 上述消息中携带有切换指示。 为了实现上述目的， 根据本发明的又一方面， 还提供了一种移动节点。 其中，在移动节点从第一移动接入网关切换到第二移动接入网关接入本 地移动锚点的情况下， 该移动节点用于向第二移动接入网关发送连接请求， 其中， 连接请求中携带有第一接口的 IP地址。 借助于上述技术方案至少之一， 通过在切换目标网络接收到 MN发送 的 IP地址后， 在判断 MN的接入为切换接入时， 夺该 IP地址分配给 MN, 使得网络侧能够为具有地址保留能力的用户设备保留切换前地址。 附图说明 此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中： 图 1是根据相关技术的 PMIPv6管理域的架构图； 图 2是根据相关技术 EPS系统的架构图； 图 3是根据本发明实施例的网络切换实现方法的流程图； 图 4是才艮据本发明实例一的流程图； 图 5是才艮据本发明实例二的流程图； 图 6是才艮据本发明实例三的流程图； 图 7是才艮据本发明实例四的流程图； 图 8是才艮据本发明实例五的流程图； 图 9是才艮据本发明实例六的流程图； 图 10是才艮据本发明实施例的网络切换实现系统的框图。 具体实施方式 功能相克述 在本发明实施例提供的技术方案中， 在切换目标网络接收到 MN发送 的 IP地址后， 在判断 MN的接入为切换接入时， 夺该 IP地址分配给 MN, 使得网络侧能够为具有地址保留能力的用户设备保留切换前地址 , 相比于现 有技术中网络侧在无法获知 MN是否具有在不同接口之间地址保留的能力网 络时、 不为 MN保留切换前地址的情况， 本发明实施例提供的技术方案可以 使得切换后的接口能够连续进行在原接口进行的 IP业务。 以下结合附图对本发明的优选实施例进行说明， 应当理解， 此处所描述 的优选实施例仅用于说明和解释本发明， 并不用于限定本发明， 如果不冲突， 本申请中的实施例以及实施例中的特征可以相互组合。 方法实施例 本发明实施例提供了一种网络切换实现方法。 图 3示出了才艮据本发明实施例的一种网络切换实现方法，该方法应用于
MN (或 UE ) 从第一 MAG切换到从第二 MAG进行 LMA接入的场景， 其 中， MN通过第一接口与第一 MAG连接， 并通过第二接口与第二 MAG连 接， 该网络切换实现方法包括以下处理： 优选地， 第二 MAG首先接收来自 MN的连接请求， 其中， 连接请求中 携带有第一接口的 IP地址以及 MN的标识信息；第二 MAG将携带有第一接 口的 IP地址、 MN的标识信息、 以及第二 MAG的 IP地址的 PBU消息发送 到 LMA。 优选地 , 上述第二 MAG接收 PBA消息， 并将其中的第一接口的 IP地址发送到 MN, 以使 MN在第二接口使用第一接口的 IP地址。 具体如 图 3所示的步骤 S302—步骤 S308。 步骤 S302 , LMA接收来自第二 MAG的 PBU消息， 其中， PBU消息 中携带有 MN的标识信息、 第一接口的 IP地址、 以及第二 MAG的 IP地址， 这里的 PBU消息中的代理转交地址为第二 MAG的 IP地址。 优选地， 第一 接口的 IP地址具体包括： IPv6家乡网络前缀和 /或 IPv4家乡地址。 S304, LMA在其保存的 BCE中查找是否存在 MN的标识信息以及第 一接口的 IP地址。
S306 ,在查找到 MN的标识信息以及第一接口的 IP地址的情况下， LMA 继续判断 BCE中的代理转交地址和 PBU消息中的代理转交地址是否相同。 S308 , 在步骤 S306中的判断结果为不同的情况下， LMA判断 MN的 连接为切换连接， 并且判断移动节点具有地址保留能力， 于是向第二 MAG 发送 PBA消息， 并在 PBA消息中携带第一接口的 IP地址。 图 4示出了才艮据本发明实施例的一种网络切换实现方法，该方法应用于 MN从第一 MAG切换到从第二 MAG进行 LMA接入的场景， 其中， MN通 过第一接口与第一 MAG连接， 并通过第二接口与第二 MAG连接， 该实现 方法包括以下处理 (步骤 S402—S406 ):
S402 , MN从第一移动接入网关切换到第二移动接入网关 , 在接入第二 移动接入网关过程中， 将在第一移动接入网关获得的地址发送给第二移动接 入网关； S404, 第二移动接入网关收到 MN发来的地址后， 判断当前 MN的接 入为切换接入， 发送代理绑定更新消息给本地移动锚点 , 消息中设置切换指 示为跨接口切换， 该消息中还可以携带 MN发来的地址；
S406, 本地移动锚点接收到代理绑定更新消息后， 进行相应处理； 具体 地， 可以包括以下的处理方式之一： （ 1 ) 本地移动锚点根据切换指示， 执行 切换处理 , 向第二 MAG发送 PBA消息 , 并在 PBA消息中携带第一接口的 IP地址； （ 2 )本地移动错点检查 PBU中的地址（该地址是 MN发来的地址） 与本地保存的 BCE中的地址，当两个地址不一致时，认为该接入为错误接入 , 并 巨绝该 MN的接入； （3 ) 本地移动错点检查 PBU中的地址与本地保存的 BCE 中的地址， 当两个地址不一致时， 认为该接入为初始接入， 将 PBU中 的地址分配给 MN使用， 或者， 夺 BCE中的地址分配给 MN使用， 或者， 另外分配一个地址 , 该地址不同于 PBU和 BCE中的地址。 下面根据不同的连接请求方式分别描述本发明实施例。 实例一 在实例中， MN从 MAG1切换到 MAG2 , 且 MN连接 MAG2的接口 与连接 MAGI 的接口不同， MN通过 DHCP的方式将切换前接口使用的 IP 地址（包括 IPv6 HNP和 /或 IPv4家乡地址）通知 MAG2。 图 5是才艮据本发明 方法实例一的流程图。 如图 5所示， 根据本发明实施例的网络切换实现方法 包括以下步骤 ( S502— S512 ): S502, MN切换到 MAG2, MN才艮据采用的地址配置模式， 当使用有^！犬 态自动配置模式 ( Stateful Auto-Configuration ) 时， MN向 MAG2发起动态 主机配置十办议 ( Dynamic Host Configuration Protocol, 简称为 DHCP )要求 ( Solicit ); 或者 , MN使用无^)犬态配置模式 ( Stateless Auto-Configuration ), 向 MAG2发起 DHCP信息请求（ Information-request )。 在上述 DHCP请求与 DHCP信息请求中， 使用切换前接口的 IP地址作为源地址和 /或^ 1切换前接 口的 IP地址作为请求内容；
S504, MAG2才艮据接收到的请求中表明的 IPv6 HNP和 /或 IPv4家乡地 址（即请求的源地址和 /或 DHCP请求内容）， IPv6 HNP填入 PBU的 IPv6 家乡网络前缀选项 （ IPv6 Home Network Prefix option ) 和 /或 ^)夺 IPv4家乡地 址填入 PBU的 IPv4家乡地址选项 （ IPv4 Home Address option ), PBU发 送给 LMA,并在 PBU中包含 MN标识；或者，也可以按照 S404执行： MAG2 接收到 MN发来的地址后 , 判断当前 MN的接入为切换接入， 发送代理绑定 更新消息给本地移动锚点 , 在该消息中设置切换指示为跨接口切换；
S506, LMA接收到 PBU之后， 使用 PBU中的 MN标识以及 IPv6家乡 网络前缀选项和 /或 IPv4家乡地址选项查找其保存的 BCE, 找到有相同的用 户身份和 IPv6家乡网络前缀选项和 /或 IPv4家乡地址选项的 BCE条目； LMA 检查 PBU中的 Proxy-CoA与 BCE中的 Proxy-CoA, 由于 MAG2的 IP地址 与 MAG1的 IP地址不同， 所以 PBU中的 Proxy-CoA (即 MAG2的 IP地址） 与 BCE中的 Proxy-CoA (即 MAG1的 IP地址） 是不同的； 因此， LMA认 为该 MN发生了切换， 即， 认为该 PBU是一个更新， 并在更新过程中为该 用户保留地址，即，将 MN切换前的接口使用的 IPv6家乡网络前缀和 /或 IPv4 家乡地址分配给 MN切换后的接口继续使用， 并通过 PBA将该 IPv6家乡网 络前缀和 /或 IPv4家乡地址发给 MAG2; 或者， 也可以按照 406执行；
S508 , 当使用有状态自动配置时， MAG2 向 MN 发送 DHCP 公告 ( Advertise ), 将 PBA中接收到的 IPv6家乡网络前缀和 /或 IPv4家乡地址发 给 MN; 当使用无^)犬态自动配置时， MAG2向 MN发送 DHCP应答 ( Reply ), PBA中接收到的 IPv6家乡网络前缀和 /或 IPv4家乡地址发给 MN, MN在 新的接口继续使用该 IPv6家乡网络前缀和 /或 IPv4家乡地址 ,切换过程完成；
S510 , 当使用有状态自动配置时， MN 向 MAG2 发送 DHCP 请求 ( Request ),请求使用 S508中接收到的 IPv6家乡网络前缀和 /或 IPv4家乡地 址； S512, 当 MAG2接收到 S510中 MN发送的请求后， MAG2向 MN发 送 DHCP confirm (应答）， 确认 MN可以使用 S508中接收到的 HNP, MN 接收到该应答消息后， 在新接口继续使用该 IPv6家乡网络前缀和 /或 IPv4家 乡地址， 切换过程完成。 实例二 在该实例中， MN从 MAG 1切换到 MAG2 , MN连接 MAG2的接口与 连接 MAG1 的接口不同， MN通过路由请求 （RS ) 将切换前的接口使用的 IP地址 （包括 IPv6家乡网络前缀和 /或 IPv4家乡地址） 通知 MAG2。 图 6是才艮据本发明方法实例二的流程图， 如图 6所示， 才艮据本发明实施 例的网络切换实现方法包括以下步骤 S602— S608: S602 , MN切换到 MAG2 , 使用切换前的接口的 IPv6家乡网络前缀和 / 或 IPv4家乡地址作为路由请求的源地址， 将 RS发给 MAG2；
S604 , MAG2接收到的路由请求的源地址， 将源地址填入 PBU的 IPv6 家乡网络前缀选项和 /或 IPv4家乡地址选项， ^！夺 PBU发给 LMA, 并在 PBU 中包含用户身份； 或者， 该步骤也可以按照上述步骤 S404执行； 步骤 S606, LMA向 MAG2发送 PBA, 其中， PBA包含 MN的 IPv6 家乡网络前缀和 /或 IPv4家乡地址；或者，该步骤也可以按照步骤 S406执行； 步骤 S608 , MAG2向 MN发送路由公告 ( Router Advertisement ), HNP通知 MN, MN继续使用该 IPv6家乡网络前缀和 /或 IPv4家乡地址， 切 换过程完成。 实例三 在该实例中， MN从 MAG1切换到 MAG2 , MN连接 MAG2的接口与 连接 MAG 1 的接口不同， MN通过二层附着请求， 将切换前接口使用的 IP 地址 （包括 IPv6家乡网络前缀和 /或 IPv4家乡地址） 通知 MAG2。 图 7是才艮据本发明方法实例三的流程图， 如图 7所示， 才艮据本发明实施 例的网络切换实现方法包括以下步骤 S702—步骤 S708:
S702, MN切换到 MAG2 , 向 MAG2发起二层 （链路层） 附着请求， 该请求中包含 MN附着在 MAG1 时获得的 IPv6家乡网络前缀和 /或 IPv4家 乡地址。
S704, MAG2接收到的附着请求中的 IPv6家乡网络前缀和 /或 IPv4家 乡地址， 将其填入 PBU的 IPv6家乡网络前缀选项和 /或 IPv4家乡地址选项， 将 PBU发给 LMA , 在 PBU中还包含用户身份； 或者， 该步骤也可以按照步 骤 S404执行；
S706, LMA向 MAG2发送 PBA, 其中， PBA包含 MN的 IPv6家乡网 络前缀和 /或 IPv4家乡地址； 或者 , 该步骤也可以按照步骤 S406执行； 步骤 S708 , MAG2向 MN发送附着接受消息， 其中， 附着接受消息包 含 MN的 IPv6家乡网络前缀和 /或 IPv4家乡地址， MN接收到该附着接受消 息后， MN在新接口继续使用该 IPv6家乡网络前缀和 /或 IPv4家乡地址， 切 换过程完成。 实例四 本实施例描述的是 UE从 Non-3GPP接入网 （包括信任或者不信任的 Non-3GPP接入网） 切换到 E-UTRAN, UE 连接 E-UTRAN 的接口与连接 Non-3GPP接入网的接口是不同的， UE通过向 E-UTRAN发送的二层附着请 求或者 PDN连接请求将切换前接口使用的 IP地址（包括 IPv6家乡网络前缀 和 /或 IPv4家乡地址） 通知 S-GW。 图 8 是才艮据本发明方法实例四的流程图， 其中， Non-3 GPP 接入网为 WIMAX接入网络。 如图 8所示， 才艮据本发明实施例的网络切换实现方法包 括以下步骤 S802—步骤 S816:
S802, UE切换到 E-UTRAN,向 MME发起附着请求或 PDN连接请求， 该附着请求中包含有 UE标识和切换前连接 WiMAX接入网的接口使用的 IP 地址 （包括 IPv6家乡网络前缀和 /或 IPv4家乡地址）， 当 MME发起 PDN连 接请求时， 其中， 连接请求中还包含有接入点名称 （ Access Point Name , 简 称为 APN );
S804, MME、 HSS和 UE共同对 UE进行接入认证， 险证用户身份及 允许该 UE接入 EPC; 当上述步骤 S802中 MME发起 PDN连接请求时 , 该 步骤 S804可以不执行； S806, MME向 HSS发起位置更新， 更新 HSS中 UE当前的位置信息， 同时 HSS向该 MME发起插入签约数据过程，将用户的签约数据发给 MME, MME保存用户签约信息； 当上述步骤 S802中 MME发起 PDN连接请求时 , 该步骤 S806可以不执行；
S808 , 当上述步骤 S802 中 MME发起附着请求时， MME才艮据用户签 约信息中表明的 default APN (默认接入点名称） 查找到可以提供该 APN对 应的业务的 P-GW, 或者当上述步骤 S802中 MME发起 PDN连接请求时， MME可以才艮据该请求中包含的 APN查找到可以提供该 APN对应的业务的 P-GW; 同时选择一个可以和该 P-GW联系的 S-GW, 向该 S-GW发起建立 ,默认 载请求 , 其中， ，默认 7|c载请求包含用户身份和切换前连接 WiMAX接 入网的接口使用的 IP地址 （包括 IPv6家乡网络前缀和 /或 IPv4家乡地址）， 以及 default APN或 APN; 步骤 S810, S-GW根据步骤 S808中收到的建立默认承载请求中的 IPv6 家乡网络前缀和 /或 IPv4家乡地址， 将 IPv6家乡网络前缀填入 PBU的 IPv6 家乡网络前缀选项和 /或将 IPv4家乡地址填入 PBU的 IPv4家乡地址选项， PBU发给 P-GW ,在 PBU中还包含用户身份以及 default APN或 APN; 或 者， 该步骤也可以按照步骤 S404执行； 步骤 S812, P-GW接收到 PBU之后， 使用 PBU中的用户身份、 IPv6 家乡网络前缀选项和 /或 IPv4家乡地址选项以及 default APN或 APN查找其 保存的 BCE, 找到有相同的用户身份、 IPv6家乡网络前缀选项 （IPv6 Home Network Prefix option )和 /或 IPv4家乡地址选项 ( IPv4 Home Address option ) 以及 default APN或 APN的 BCE条目； P-GW检查 PBU中的 Proxy-CoA与 BCE中的 Proxy-CoA, 由于 S-GW的 IP地址与 UE先前在 Non-3GPP中接入 的 MAG的 IP地址不同， 所以 PBU中的 Proxy-CoA与 BCE中的 Proxy-CoA 是不同的， 因此 P-GW认为该 UE发生了切换 , 即 ,认为该 PBU是更新过的 , 在更新过程中为该用户保留地址，将 UE切换前用于 WiMAX接入使用的 IPv6 家乡网络前缀和 /或 IPv4家乡地址分配给 UE在切换到 E-UTRAN后的接口继 续使用 ,并通过 ΡΒΑ将该 IPv6家乡网络前缀和 /或 IPv4家乡地址发给 S-GW; 或者， 该步骤也可以按照步骤 S406执行； 步骤 S814, S-GW使用建立默认承载响应消息将 ΡΒΑ中接收到的 IPv6 家乡网络前缀和 /或 IPv4家乡地址发送给 ΜΜΕ; 步骤 S816, ΜΜΕ通知无线网络附着完成， 无线网络与 UE之间建立无 线 载， ΜΜΕ通过无线网络 ^)夺 IPv6家乡网络前缀和 /或 IPv4家乡地址通知 UE, UE继续使用该 IPv6家乡网络前缀和 /或 IPv4家乡地址，完成从 Non-3GPP 接入网到 E-UTRAN的切换。 实例五 本实施例描述的是 UE从 E-UTRAN切换到 WiMAX接入网， 通过该
WiMAX接入网接入 EPC; UE连接 E-UTRAN的接口与连接 WiMAX接入网 的接口是不同的， UE通过向 WiMAX发送的 DHCP请求将切换前接口使用 的 IP地址 （包括 IPv6家乡网络前缀和 /或 IPv4家乡地址） 通知 WiMAX接 入网。 图 9是根据本发明方法实例五的流程图， 如图 9所示， 根据本发明实施 例的网络切换实现方法包括以下步骤 S902— S912: 步骤 S902 , UE接入 WiMAX接入网 ,将用户身份发给 WiMAX接入网 , WiMAX接入网与 HSS/AAA联系， 对该用户进行认证与 4受权； 步骤 S904, 在用户认证与 4受权通过后， UE发起 DHCP请求， 该 DHCP 请求的过程与上述步骤 S502中的 DHCP请求过程类似， 这里不再赞述； 步骤 S906, WiMAX接入网才艮据步骤 S904中接收到的 DHCP请求中表 明的 IPv6 HNP和 /或 IPv4家乡地址（即请求的源地址和 /或 DHCP请求内容）， IPv6 HNP填入绑定更新消息（ PBU )的 IPv6家乡网络前缀选项（ IPv6 Home Network Prefix option ) 和 /或^ 1 IPv4家乡地址填入绑定更新消息 （ PBU ) 的 IPv4家乡地址选项（ IPv4 Home Address option ), PBU发给 P-GW,在 PBU 中还包含用户身份； 或者， 该步骤也可以按照步骤 S404执行； 步骤 S908 , P-GW接收到该 PBU之后向 HSS/AAA发起更新 P-GW身 份， 将自身的 P-GW身份信息通知 HSS/AAA, HSS/AAA保存该信息； 步骤 S910, P-GW接收到 PBU之后， 使用 PBU中的用户身份和 IPv6 家乡网络前缀选项 （ IPv6 Home Network Prefix option ) 和 /或 IPv4家乡地址 选项 （IPv4 Home Address option ) 查找其保存的 BCE ( BCE ), 找到有 目同 的用户身份和 IPv6家乡网络前缀选项（ IPv6 Home Network Prefix option )和 /或 IPv4家乡地址选项 （ IPv4 Home Address option ) 的 BCE条目； P-GW检 查 PBU中的 Proxy-CoA与 BCE中的 Proxy-CoA,由于 WiMAX接入网网关的 IP地址与 UE先前在 E-UTRAN中接入的 MAG (即 S-GW )的 IP地址不同， 所以 PBU中的 Proxy-CoA与 BCE中的 Proxy-CoA是不同的； 因 jt匕 P-GW认 为该 UE发生了切换， 即认为该 PBU是一个更新， 在更新过程中为该用户保 留地址， 将 UE切换前在 E-UTRAN使用的 IPv6家乡网络前缀和 /或 IPv4家 乡地址分配给 UE切换后在 WiMAX接入使用的接口继续使用， 并通过 PBA 将该 IPv6家乡网络前缀和 /或 IPv4家乡地址发给 WiMAX接入网； 或者， 该 步骤也可以按照步骤 S406执行； 步骤 S912, WiMAX接入网通过 DHCP方式将 PBA中收到的 IPv6家 乡网络前缀和 /或 IPv4家乡地址发给 UE, UE继续使用该 IPv6家乡网络前缀 和 /或 IPv4家乡地址， 完成从 E-UTRAN到 WiMAX的切换。 实例六 本实施例描述的是 UE从 E-UTRAN切换到不信任的 Non-3GPP接入网， 通过该不信任的 Non-3GPP接入网接入 EPC; UE连接 E-UTRAN的接口与 连接该不信任的 Non-3GPP接入网的接口是不同的。 由于该 Non-3GPP接入 网是不信任的， UE需要发起建立到 ePDG的隧道连接。 UE在与 ePDG的 IKEv2 ( Internet Key Exchange version 2, 因特网密胡交换十办议版本 2 ) 认证 及随道建立的过程中 , 在 IKE AUTH Request消息中的 configuration pay load (CFG_REQUEST)携带切换前接口的 IPv6家乡网络前缀和 /或 IPv4家乡地址 给 ePDG。 图 10是才艮据本发明方法实例六的流程图， 如图 10所示， 才艮据本发明实 施例的网络切换实现方法包括以下步骤 S1002— S1008: 步骤 S 1002 , UE从 E-UTRAN切换到不信任的 Non-3 GPP接入网。 UE 才艮据内部配置的 ePDG的 IP地址或者通过 DNS ( Domain Name Server,i或名 月 务器） 查找到一个 ePDG的 IP地址， UE向 ePDG发起 IKEv2认证及隧道 建立请求，在 IKEv2认证过程中， UE在 IKE— AUTH Request ( IKE认证请求） 消息中的 configuration payload (配置载荷 ) 中的 CFG_REQUEST (配置请 求）中携带切换前接口的 IPv6家乡网络前缀和 /或 IPv4家乡地址给 ePDG。 在 IKE认证请求中还包含 UE切换前使用的 APN; 步骤 S1004, ePDG才艮据步骤 S1002中接收到的 CFG— REQUEST中表明 的 IPv6 HNP和 /或 IPv4家乡地址， ^)夺 IPv6 HNP填入绑定更新消息 （ PBU ) 的 IPv6家乡网络前缀选项 （ IPv6 Home Network Prefix option ) 和 /或 ^)夺 IPv4 家乡地址填入绑定更新消息的 IPv4 家乡地址选项 （IPv4 Home Address option ),将 PBU发给 P-GW,在 PBU中还包含用户身份 NAI( Network Access Identifier,网络接入点标识） 以及 APN; 或者， 该步骤也可以按照步骤 S404 执行； 步骤 S 1006 , P-GW接收到 PBU之后 , 使用 PBU中的用户身份 NAI、 APN和 IPv6家乡网络前缀选项（ IPv6 Home Network Prefix option )和/或 IPv4 家乡地址选项 （IPv4 Home Address option ) 查找其保存的 BCE ( BCE ), 找 到有相同的用户身份、 APN和 IPv6家乡网络前缀选项 （ IPv6 Home Network Prefix option ) 和 /或 IPv4家乡地址选项 （ IPv4 Home Address option ) 的 BCE 条目； P-GW检查 PBU中的 Proxy-CoA与 BCE中的 Proxy-CoA,由于 ePDG 的 IP地址与 UE先前在 E-UTRAN中接入的 MAG (即 S-GW ) 的 IP地址不 同，所以 PBU中的 Proxy-CoA与 BCE中的 Proxy-CoA是不同的，因 jt匕， P-GW 认为该 UE发生了切换， 即， 该 PBU是更新过的， 在更新过程中为该用户保 留地址， 将 UE切换前在 E-UTRAN使用的 IPv6家乡网络前缀和 /或 IPv4家 乡地址分配给 UE切换后在新的接口继续使用， 并通过 PBA将该 IPv6家乡 网络前缀和 /或 IPv4家乡地址发给 ePDG;或者，该步骤也可以按照步骤 S406 执行； 步骤 S1008 , 在 IKEv2认证过程中， ePDG发送 IKE AUTH Response ( IKE认证响应 ) 消息给 UE, 其中， 该消息中的 configuration payload (配 置载荷 ) 中包含 CFG REPLY (配置回复）， 该 CFG_REPLY中携带 PBA中 接收到的 IPv6家乡网络前缀和 /或 IPv4家乡地址。 UE继续在新接口使用该 IPv6 家乡网络前缀和 /或 IPv4 家乡地址， 完成从 E-UTRAN 到不信任的 Non-3GPP接入网的切换。 实例七
MN初始接入 MAG, MN在接入过程中不携带 IP地址， 网络认为该接 入为初始接入。 MN与 MAG之间的连接可以是实施例一、 二、 三、 四、 五 和六中的连接方式， 这里不再赞述。 图 11根据本发明方法实例七的流程图， 如图 11所示， 根据本发明实施 例的网络切换实现方法包括以下步骤 S1102—步骤 S1108: 步骤 S 1102 , MN在接入 MAG的时 4美 , 在接入过程中不携带 IP地址给 MAG, 表示该附着为初始附着； 步骤 S1104, MAG才艮据 MN的附着过程中没有接收到来自 MN的地址， 认为该 MN的接入为初始附着 , 发送代理绑定更新消息给 LMA; 步骤 S1106, LMA接收到消息后， 分配 IP地址和 /或地址前缀， 在代理 绑定确认消息中将分配的 IP地址和 /或地址前缀发送给 MAG; 步骤 S1108 , MAG将 LMA分配的 IP地址发送给 MN。 系统实施例 本发明实施例提供了一种网络切换实现系统。 图 12是才艮据本发明实施例的网络切换实现系统的框图 , 该实现系统用 于 MN从第一 MAG切换到从第二 MAG进行 LMA接入的场景， 其中， MN 通过第一接口与第一 MAG连接， 并通过第二接口与第二 MAG连接， 该实 现系统包括： LMA 10以及第二 MAG 20, 其中， LMA 10具体包括： 接收模 块 110 , 连接至第二 MAG 20 , 用于接收来自第二 MAG 20的 PBU消息 , 其 中， PBU消息中携带有 MN的标识信息、第一接口的 IP地址、以及第二 MAG 的 IP地址； 第一判断模块 120, 连接至接收模块 110, 用于根据 MN的标识 信息以及 APN信息（当有该 APN信息的时 4美 ), 检索与 MN以及 APN对应 的 BCE , 判断检索到的 BCE中是否存在第一接口的 IP地址， 当判断结果为 存在时 ,执行第二判断模块 130; 第二判断模块 130 , 用于判断检索到的 BCE 中的代理转交地址和 PBU消息中的第二 MAG的 IP地址是否相同； 发送模 块 140, 连接至第二判断模块 130 , 用于在第二判断模块 130的判断结果为 不同的情况下 , LMA判断 MN的连接为切换连接 , 向第二 MAG发送 PBA 消息， 并在 PB A消息中携带第一接口的 IP地址。 优选地， 第二 MAG 20具体包括： 收发模块 210, 连接至发送模块 140, 用于接收 PBA消息， 并 ^)夺 PBA消息中的第一接口的 IP地址发送到 MN, 以 使 MN在第二接口使用第一接口的 IP地址。 优选地， 该收发模块 210还用于接收来自 MN的连接请求， 并将 PBU 消息发送到 LMA; 其中， 连接请求中携带有第一接口的 IP地址以及 MN的 标识信息。 另夕卜， 本发明还提供了一种网络切换实现系统， 用于移动节点从第一移 动接入网关切换到从第二移动接入网关进行本地移动锚点接入的场景，其中， 移动节点通过第一接口与第一移动接入网关连接， 并通过第二接口与第二移 动接入网关连接， 上述实现系统包括： 本地移动锚点以及第二移动接入网关； 其中， 第二移动接入网关具体包括： 第三判断模块， 用于接收 MN发来的 IP 地址后 , 判断所述 MN的接入为跨接口的切换接入， 发送代理绑定更新消息 给本地移动锚点 , 消息中携带切换指示为跨接口切换。 装置实施例 本发明实施例提供了一种 MN。才艮据本发明实施例，在 MN从第一 MAG 切换到从第二 MAG接入 LMA的情况下， MN用于向第二 MAG发送连接请 求， 其中， 连接请求中携带有第一接口的 IP地址。 优选地， 这里的 MN可 以是上述方法实施例中的 MN, 这里不再赘述。 综上所述， 采用本发明的上述实施例， 能够为具有地址保留能力的用户 设备保留该地址。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 或 者将它们分别制作成各个集成电路模块 , 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 ？丈进等， 均应包含在本发明的保护 范围之内。

Claims

权 利 要 求 书
1. 一种网络切换实现方法， 应用于移动节点 MN从第一移动接入网关切换 到第二移动接入网关进行本地移动锚点接入的场景 , 其中， 所述移动节 点通过第一接口与所述第一移动接入网关连接， 并通过第二接口与所述 第二移动接入网关连接 , 其特征在于， 切换目标网络接收到 MN发送的 IP地址后， 判断 MN的接入为切 换接入 , 将所述 IP地址分配给所述 MN„
2. 根据权利要求 1所述的方法 , 其特征在于 , 所述 IP地址为 MN在第一移 动接入网关获得的 IP地址。
3. 根据权利要求 1所述的方法， 其特征在于， 所述切换目标网络包括所述 第二移动接入网关和所述本地移动 4苗点。
4. 根据权利要求 3所述的方法， 若所述本地移动锚点判断 MN的接入为切 换接入， 其特征在于， 所述方法还包括：
所述本地移动苗点接收来自所述第二移动接入网关的代理绑定更 新消息， 其中， 所述代理绑定更新消息中携带有所述移动节点的标识信 息、 所述第一接口的 IP地址、 以及所述第二移动接入网关的 IP地址； 所述本地移动锚点在其保存的绑定緩存条目中查找是否存在所述 移动节点的标识信息以及所述第一接口的 IP地址；
在查找到所述移动节点的标识信息以及所述第一接口的 IP地址的 情况下， 所述本地移动锚点继续判断所述绑定緩存条目中的代理转交地 址和所述代理绑定更新消息中的代理转交地址是否相同；
如果判断结果为不同，则所述本地移动锚点判断所述移动节点的连 接为切换连接， 并且如果判断所述移动节点具有地址保留能力， 则向所 述第二移动接入网关发送代理绑定确认消息， 并在所述代理绑定确认消 息中携带所述第一接口的 IP地址。
5. 根据权利要求 4所述的实现方法， 其特征在于， 所述代理绑定更新消息 中的代理转交地址为所述第二移动接入网关的 IP地址。
6. 根据权利要求 4所述的实现方法， 其特征在于， 所述方法还包括： 所述第二移动接入网关接收所述代理绑定确认消息，并将其中的所 述第一接口的 IP地址发送到所述移动节点， 以使所述移动节点在所述第 二接口使用所述第一接口的 IP地址。
7. 根据权利要求 4所述的实现方法， 其特征在于， 在所述本地移动锚点接 收来自所述第二移动接入网关的代理绑定更新消息之前， 所述方法还包 括：
所述第二移动接入网关接收来自所述移动节点的连接请求， 其中， 所述连接请求中携带有所述第一接口的 IP 地址以及所述移动节点的标 识信息；
所述第二移动接入网关将携带有所述第一接口的 IP地址、 所述移 动节点的标识信息、以及所述第二移动接入网关的 IP地址的代理绑定更 新消息发送到所述本地移动锚点。
8. 根据权利要求 3所述的方法， 若所述第二移动接入网关判断 MN的接入 为切换接入， 其特征在于， 所述方法包括：
所述第二移动接入网关接收到来自 MN的 IP地址后 ,判断所述 MN 的接入为跨接口切换接入，发送代理绑定更新消息给所述本地移动锚点， 所述消息中携带有切换指示为跨接口切换；
所述本地移动锚点接收到所述代理绑定更新消息 , 将所述 IP地址 分配给所述 MN„
9. 一种网络切换实现系统， 用于移动节点从第一移动接入网关切换到从第 二移动接入网关进行本地移动锚点接入的场景 , 其中， 所述移动节点通 过第一接口与所述第一移动接入网关连接， 并通过第二接口与所述第二 移动接入网关连接， 其特征在于， 所述实现系统包括： 本地移动锚点以 及第二移动接入网关， 其中， 所述本地移动锚点具体包括： 接收模块，用于接收来自所述第二移动接入网关的代理绑定更新消 息， 其中， 所述代理绑定更新消息中携带有所述移动节点的标识信息、 所述第一接口的 IP地址、 以及所述第二移动接入网关的 IP地址； 第一判断模块 , 用于才艮据所述移动节点的标识信息， 检索与所述移 动节点对应的绑定緩存条目 , 判断所述绑定緩存条目中是否存在所述第 一接口的 IP地址以及所述移动节点的标识信息；
第二判断模块，用于判断所述绑定緩存条目中的代理转交地址和所 述代理绑定更新消息中的所述第二移动接入网关的 IP地址是否相同； 发送模块 , 用于在所述第二判断模块的判断结果为不同的情况下 , 所述本地移动锚点判断所述移动节点的连接为切换连接， 向所述第二移 动接入网关发送代理绑定确认消息， 并在所述代理绑定确认消息中携带 所述第一接口的 IP地址。
10. 根据权利要求 9所述的实现系统 , 其特征在于 , 所述第二移动接入网关 包括：
收发模块， 用于接收所述代理绑定确认消息， 并将所述代理绑定确 认消息中的所述第一接口的 IP地址发送到所述移动节点 , 以使所述移动 节点在所述第二接口使用所述第一接口的 IP地址。
11. 根据权利要求 9所述的实现系统 , 其特征在于 , 所述收发模块还用于接 收来自所述移动节点的连接请求 , 并将所述代理绑定更新消息发送到所 述本地移动锚点； 其中， 所述连接请求中携带有所述第一接口的 IP地址 以及所述移动节点的标识信息。
12. 一种网络切换实现系统， 用于移动节点从第一移动接入网关切换到从第 二移动接入网关进行本地移动锚点接入的场景 , 其中， 所述移动节点通 过第一接口与所述第一移动接入网关连接， 并通过第二接口与所述第二 移动接入网关连接， 其特征在于， 所述实现系统包括： 本地移动锚点以 及第二移动接入网关， 其中， 所述第二移动接入网关具体包括：
第三判断模块， 用于接收 MN发来的 IP地址后， 判断所述 MN的 接入为跨接口切换接入， 发送代理绑定更新消息给本地移动锚点， 所述 消息中携带切换指示为跨接口切换。
13. 一种移动节点， 其特征在于， 在所述移动节点从第一移动接入网关切换 到从第二移动接入网关接入本地移动锚点的情况下， 所述移动节点用于 向所述第二移动接入网关发送连接请求， 其中， 所述连接请求中携带有 所述第一接口的 IP地址。
PCT/CN2008/073405 2008-06-20 2008-12-09 网络切换实现方法及系统以及移动节点 WO2009152669A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP08874673.0A EP2293497B1 (en) 2008-06-20 2008-12-09 Method for realizing network switching and system and mobile node
US12/999,747 US9167482B2 (en) 2008-06-20 2008-12-09 Method and system for realizing network switching

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810124969 2008-06-20
CN200810124969.4 2008-06-20

Publications (1)

Publication Number Publication Date
WO2009152669A1 true WO2009152669A1 (zh) 2009-12-23

Family

ID=40743581

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073405 WO2009152669A1 (zh) 2008-06-20 2008-12-09 网络切换实现方法及系统以及移动节点

Country Status (4)

Country Link
US (1) US9167482B2 (zh)
EP (1) EP2293497B1 (zh)
CN (1) CN101448252B (zh)
WO (1) WO2009152669A1 (zh)

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127766B (zh) * 2007-09-24 2010-06-09 中兴通讯股份有限公司 基于sip协议的消息处理方法、装置及ip通信系统
HUE025946T2 (en) * 2007-10-09 2016-05-30 ERICSSON TELEFON AB L M (publ) Technique to provide support for a multitude of mobility protocols
US8611306B2 (en) * 2009-01-12 2013-12-17 Qualcomm Incorporated Context fetching after inter-system handover
CN101848454B (zh) * 2009-03-26 2014-01-01 华为技术有限公司 一种分配前缀的方法、网络系统和本地移动锚点
KR101080852B1 (ko) * 2009-08-05 2011-11-07 숭실대학교산학협력단 프록시 모바일 아이피 네트워크에서의 네트워크 이동성 관리장치 및 방법
CN101998566B (zh) * 2009-08-13 2013-03-13 华为技术有限公司 一种代理移动ip中移动接入网关的切换方法及装置
CN102036217B (zh) * 2009-09-29 2013-10-09 华为技术有限公司 代理移动ip系统中建立多个移动会话的方法及系统
CN101702800B (zh) * 2009-11-19 2012-08-22 中国科学院计算技术研究所 代理移动通信系统与方法
US20110134883A1 (en) * 2009-12-09 2011-06-09 Electronics And Telecommunications Research Institute Network based mobility system and handover method thereof
CN102111744B (zh) * 2009-12-29 2014-12-10 中国移动通信集团公司 本地移动锚点的重定向方法、设备及系统
CN102149072A (zh) * 2011-03-17 2011-08-10 中山大学 一种基于链路层分组的代理移动IPv6组切换解决方法
US9986425B2 (en) * 2011-05-13 2018-05-29 Nokia Solutions And Networks Oy Apparatus and method for routing in a network
CN102882788A (zh) * 2011-07-14 2013-01-16 中兴通讯股份有限公司 报文转发处理方法、网元及系统
CN103037350B (zh) * 2011-09-29 2017-03-22 中兴通讯股份有限公司 一种在pmip域间漫游时的节点通信方法及通信系统
CN103052125B (zh) * 2011-10-13 2018-03-23 广州市瑞雅通信技术有限公司 流迁移方法及装置
KR20160075864A (ko) * 2011-11-29 2016-06-29 인터디지탈 패튼 홀딩스, 인크 Ip 이동성 관리 방법
EP2611228A1 (en) * 2011-12-27 2013-07-03 Alcatel Lucent Allowing access to services delivered by a service delivery platform in a 3GPP HPLM, to an user equipment connected over a trusted non-3GPP access network
CN103634853A (zh) * 2012-08-24 2014-03-12 中兴通讯股份有限公司 一种请求获取支持移动性的ip的方法、终端和网络侧
CN107682900B (zh) * 2012-09-29 2020-11-17 华为终端有限公司 数据流控制方法及相关设备和通信系统
CN103260145B (zh) * 2013-04-18 2016-07-20 中国科学院计算技术研究所 基于PMIPv6域内业务流切换的移动管理方法及系统
US9392494B2 (en) 2013-07-15 2016-07-12 Qualcomm Incorporated Systems and methods for reduced latency during initial link setup
CN105874829B (zh) * 2014-01-10 2019-11-01 华为技术有限公司 用于对移动网络和移动主机的分布式的和集成的移动性支持的系统和方法
RU2669582C2 (ru) * 2014-05-30 2018-10-12 Хуавэй Текнолоджиз Ко., Лтд. Способ и устройство смены пути услуги
CN105636195A (zh) * 2014-11-04 2016-06-01 中兴通讯股份有限公司 一种终端位置信息获取方法、装置及系统
CN105848249A (zh) * 2015-01-15 2016-08-10 中兴通讯股份有限公司 接入点名称apn的处理方法、装置及系统
WO2016155011A1 (zh) * 2015-04-03 2016-10-06 华为技术有限公司 一种分组数据网关的选择方法、相关装置及系统
US10965655B2 (en) * 2015-05-28 2021-03-30 Telefonaktiebolaget Lm Ericsson (Publ) Multiple PDN connections over untrusted WLAN access
CN107950056B (zh) * 2015-10-06 2021-02-23 苹果公司 使用3gpp无线电接入技术的接入系统之间的双无线电操作
US10517012B2 (en) 2018-01-16 2019-12-24 Cisco Technology, Inc. Methods and apparatus for use in adaptively rerouting user plane traffic for mobility using segment routing for IPv6
CN111163493B (zh) * 2018-11-08 2022-08-19 中国电信股份有限公司 通信配置方法、系统和相关设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008046655A1 (en) * 2006-10-20 2008-04-24 Panasonic Corporation Methods in mixed network- and host-based mobility management
CN101175316A (zh) * 2006-10-30 2008-05-07 华为技术有限公司 跨本地移动管理域切换的方法及通信系统

Family Cites Families (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7539164B2 (en) * 2002-06-14 2009-05-26 Nokia Corporation Method and system for local mobility management
US7218618B2 (en) * 2002-07-19 2007-05-15 Nokia Corporation Method of providing mobile IP functionality for a non mobile IP capable mobile node and switching device for acting as a mobile IP proxy
JP4088540B2 (ja) * 2003-03-03 2008-05-21 株式会社日立製作所 パケット通信システム、通信ネットワーク、およびモバイルノードにおけるｉｐアドレス選択方法
GB0308980D0 (en) * 2003-04-17 2003-05-28 Orange Personal Comm Serv Ltd Telecommunications
US7917152B2 (en) * 2003-06-27 2011-03-29 Nokia Corporation Enhanced fast handover procedures
WO2007012054A2 (en) * 2005-07-20 2007-01-25 Nortel Networks Limited Fmipv6 integration with wimax
EP1764970A1 (en) * 2005-09-19 2007-03-21 Matsushita Electric Industrial Co., Ltd. Multiple interface mobile node with simultaneous home- and foreign network connection
KR100739811B1 (ko) * 2005-10-26 2007-07-13 삼성전자주식회사 인터넷 프로토콜 버전 4만 제공하는 네트워크에서 듀얼모바일 노드의 경로 최적화 방법
WO2007082007A2 (en) * 2006-01-11 2007-07-19 Starent Networks Corporation Systems and methods for mobility management on wireless networks
US8625609B2 (en) * 2006-05-19 2014-01-07 Futurewei Technologies Inc. Using DHCPv6 and AAA for mobile station prefix delegation and enhanced neighbor discovery
US8189544B2 (en) * 2006-06-26 2012-05-29 Alcatel Lucent Method of creating security associations in mobile IP networks
CN101150838B (zh) * 2006-09-18 2010-06-23 大唐移动通信设备有限公司 一种在系统间切换的方法及系统
CN101170808B (zh) * 2006-10-25 2011-03-30 华为技术有限公司 异种接入系统间的切换方法及切换系统
US8144593B2 (en) * 2006-11-17 2012-03-27 Qualcomm Incorporated Method and apparatus for efficient routing in communication networks
US20080130571A1 (en) * 2006-12-05 2008-06-05 Motorola, Inc. Handover in a mobile network domain
US8199717B2 (en) * 2007-02-09 2012-06-12 Telefonaktiebolaget L M Ericsson (Publ) Method for permitting vertical handoff of a mobile node in a communication system
US7953044B2 (en) * 2007-02-16 2011-05-31 Futurewei Technologies, Inc. Method, component and system for network-based handover
US8446875B2 (en) * 2007-02-23 2013-05-21 Toshiba America Research, Inc. Media independent pre-authentication supporting fast-handoff in proxy MIPv6 environment
US9516495B2 (en) * 2007-03-01 2016-12-06 Futurewei Technologies, Inc. Apparatus and methods of PMIPv6 route optimization protocol
JP2010521888A (ja) * 2007-03-12 2010-06-24 ノーテル・ネットワークス・リミテッド フロー識別用の鍵を使用した、モバイルｉｐのトンネリング・サポート
US20100103876A1 (en) * 2007-03-16 2010-04-29 Panasonic Corporation Mobile terminal and communication management device
JP4794520B2 (ja) * 2007-05-16 2011-10-19 Ｋｄｄｉ株式会社 ネットワーク主導型移動管理プロトコルにおける通信経路を最適化するシステム、アクセスゲートウェイ、ホームエージェント、およびプログラム
US8533455B2 (en) * 2007-05-30 2013-09-10 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for combining internet protocol authentication and mobility signaling
US9602332B2 (en) * 2007-06-15 2017-03-21 Qualcomm Incorporated Method and apparatus for DNS update triggered IPv6 neighbor advertisement
US9049629B2 (en) * 2007-06-18 2015-06-02 Qualcomm Incorporated Method and apparatus for fast inter-system handover
US8289862B2 (en) * 2007-06-27 2012-10-16 Futurewei Technologies, Inc. Method and apparatus for dynamic LMA assignment in proxy mobile IPv6 protocol
US8102815B2 (en) * 2007-07-12 2012-01-24 Telefonaktiebolaget L M Ericsson (Publ) Proxy mobility optimization
US8228935B2 (en) * 2007-07-13 2012-07-24 Qualcomm Incorporated MIP/PMIP concatenation when overlapping address space are used
US8077686B2 (en) * 2007-07-20 2011-12-13 Marvell World Trade Ltd. Multiple packet data network support over trusted access
US8634344B2 (en) * 2007-08-06 2014-01-21 Marvell World Trade Ltd. Dynamic internet protocol addressing solutions with network-based mobility
US8085793B2 (en) * 2007-09-24 2011-12-27 Telefonaktiebolaget Lm Ericsson (Publ) Traffic localization with proxy mobility
EP2206401B1 (en) * 2007-10-10 2017-05-31 BlackBerry Limited Support for multi-homing protocols
US8228843B2 (en) * 2007-11-12 2012-07-24 Futurewei Technologies, Inc. Internet protocol version 4 support for proxy mobile internet protocol version 6 route optimization protocol
US8325680B2 (en) * 2007-11-21 2012-12-04 Apple Inc. Support for continuity of tunnel communications for mobile nodes having multiple care of addressing
US8462728B2 (en) * 2007-12-24 2013-06-11 Apple Inc. Method and wireless system for achieving local anchoring of a mobile node
US20090207812A1 (en) * 2008-01-07 2009-08-20 Vivek Gupta Dual radio handovers beween wimax and 3gpp
US8447349B2 (en) * 2008-02-15 2013-05-21 Motorola Solutions, Inc. Method and apparatus for inter-technology handoff of a multi-mode mobile station
US8477729B2 (en) * 2008-03-19 2013-07-02 Research In Motion Limited Support for multi-homing protocols using transient registration and expanded binding revocation messages
US8675551B2 (en) * 2008-03-31 2014-03-18 Futurewei Technologies, Inc. Multi-protocol label switching support for proxy mobile internet protocol version 6
US8675630B2 (en) * 2008-05-22 2014-03-18 Qualcomm Incorporated Systems and methods for multiplexing multiple connections in mobile IP network
WO2009147468A2 (en) * 2008-05-27 2009-12-10 Telefonaktiebolaget L M Ericsson (Publ) System and method for backwards compatible multi-access with proxy mobile internet protocol
US8040845B2 (en) * 2008-09-12 2011-10-18 Telefonaktiebolaget L M Ericsson (Publ) Efficient routing between a mobile node and a correspondent node in a proxy mobile IP network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008046655A1 (en) * 2006-10-20 2008-04-24 Panasonic Corporation Methods in mixed network- and host-based mobility management
CN101175316A (zh) * 2006-10-30 2008-05-07 华为技术有限公司 跨本地移动管理域切换的方法及通信系统

Also Published As

Publication number Publication date
EP2293497A1 (en) 2011-03-09
US9167482B2 (en) 2015-10-20
EP2293497A4 (en) 2013-06-26
CN101448252A (zh) 2009-06-03
CN101448252B (zh) 2011-03-16
US20110103340A1 (en) 2011-05-05
EP2293497B1 (en) 2016-11-02

Similar Documents

Publication Publication Date Title
WO2009152669A1 (zh) 网络切换实现方法及系统以及移动节点
US11477634B2 (en) Home agent discovery upon changing the mobility management scheme
US8792453B2 (en) Secure tunnel establishment upon attachment or handover to an access network
US8379599B2 (en) Local mobility anchor relocation and route optimization during handover of a mobile node to another network area
KR101019927B1 (ko) 프록시 모바일 ｉｐ을 위한 패킷－전달 방법
US8224330B2 (en) Method and system for interworking between two different networks
KR101227455B1 (ko) 핸드오버 동작에서 자원 관리를 위한 방법 및 장치
US8279807B2 (en) Communication control method, network node, and mobile terminal
US20100215019A1 (en) Detection of mobility functions implemented in a mobile node
WO2010041440A1 (ja) インタフェース切換システム、モバイルノード、代理ノード及び移動管理ノード
US20070014262A1 (en) Method for handling over a call involving a mobile node in a macromobility situation in an IP communication network using hierarchical routing
KR102536020B1 (ko) 다중 액세스에 걸쳐 트래픽을 분할하기 위한 방법 및 컴퓨팅 디바이스
KR20140000335A (ko) 네트워크-기반 ip 이동성을 지원하는 다중-액세스 모바일 통신 시스템 내의 트래픽 오프로드
EP2299748B1 (en) Method and system for supporting mobility security in the next generation network
WO2010146815A1 (ja) 移動管理プロトコル選択方法、移動管理プロトコル選択システム、モバイルノード、ホームエージェント及び代理ノード
WO2010010693A1 (ja) 垂直ハンドオフ方法、垂直ハンドオフシステム、ホームエージェント及びモバイルノード
KR101527611B1 (ko) 이종망 접속 방법
WO2011050662A1 (zh) 多接入的处理方法、家乡代理及用户设备
Abdelatif et al. Next-generation mobility for advanced scenario roaming

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 12999747

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2008874673

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2008874673

Country of ref document: EP