WO2010000188A1 - 一种实现移动管理域间切换的方法及装置 - Google Patents

一种实现移动管理域间切换的方法及装置 Download PDF

Info

Publication number
WO2010000188A1
WO2010000188A1 PCT/CN2009/072482 CN2009072482W WO2010000188A1 WO 2010000188 A1 WO2010000188 A1 WO 2010000188A1 CN 2009072482 W CN2009072482 W CN 2009072482W WO 2010000188 A1 WO2010000188 A1 WO 2010000188A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobility management
sma
management domain
mobile node
mobility
Prior art date
Application number
PCT/CN2009/072482
Other languages
English (en)
French (fr)
Inventor
张弓
潘璐伽
何诚
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2010000188A1 publication Critical patent/WO2010000188A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016Hand-off preparation specially adapted for end-to-end data sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface
    • H04W36/142Reselecting a network or an air interface over the same radio air interface technology
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup

Definitions

  • the present invention relates to the field of mobile communication technologies, and in particular, to a method and apparatus for implementing mobility management inter-domain handover.
  • MN mobile node
  • CN peer node
  • the fixed endpoint is the Local Mobile Anchor Point (LMA).
  • LMA Local Mobile Anchor Point
  • the local mobility anchor allows the display to change its attachment location while moving, without the need to advertise to the communication peer, while all mobile node traffic will be routed through the local mobility anchor and forwarded to the MN through the tunnel.
  • the Mobile IP (MIP, Mobi le IP) protocol supports the connectivity of the MN when moving in the IP network, so that the MN after leaving its home network Still able to maintain a connection to the network.
  • the MN always uses the home address (HoA, Home Addres s) assigned by the Home Network to identify it, and does not change due to the change of the visited network; when the MN leaves the home network, it will assign the care-of address (CoA, which is assigned to the visited network). Care Of Addres s ), the current location of the MN is identified by the CoA, and it will send its current location information to the Home Agent (HA, Home Agent).
  • the HA will intercept the packets sent to the MN HoA and forward them through the tunnel to the explicit CoA. The entire process is performed only at the IP layer and transparent to all layers above IP.
  • the present invention provides a method and apparatus for implementing mobility management inter-domain handover, which can provide a more efficient data forwarding path and a shorter communication delay.
  • the method for implementing mobility management inter-domain handover includes: determining, as a session mobility anchor point SMA, a local mobility anchor point LMA1 of a first mobility management domain to which an mobile node MN initially attaches, and establishing a mobile node display a first connection with the LMA1;
  • the explicitly transmitted and received data is transmitted by the SMA and transmitted using the bidirectional tunnel.
  • the embodiment of the invention further provides a network entity, including:
  • a receiving unit configured to receive a proxy binding update request message
  • An update unit configured to perform a proxy binding update according to the proxy binding update request;
  • a tunnel establishing unit configured to establish a bidirectional relationship between the local mobility anchor point in the mobility management domain to which the peer node belongs;
  • a communication unit by using the bidirectional tunnel, forwarding the data sent by the display to the correspondent node to a local mobility anchor in another mobility management domain, and forwarding data from the correspondent node to the MN.
  • the LMA accessing the network in the display guiding process is used as the SMA, which solves the problem that the home network domain becomes a communication bottleneck; between the network domain where the SMA is located and the new LMA administrative domain that enters the display Introduce inter-domain signaling, establish a bidirectional tunnel for data forwarding, ensure communication continuity, and solve the problem of inter-domain handover between PMIPv6.
  • inter-domain signaling establish a bidirectional tunnel for data forwarding, ensure communication continuity, and solve the problem of inter-domain handover between PMIPv6.
  • it provides a more efficient data forwarding path.
  • a network-based mobility management solution is adopted, which is easy to implement without terminal participation.
  • FIG. 1 is a schematic diagram of a network architecture of a mobility management domain according to an embodiment of the present invention
  • Figure lb is a flowchart of a mobile node switching between mobile management domains in the embodiment of the present invention
  • Figure lc is a data format of a proxy binding update PBU in the embodiment of the present invention
  • FIG. 1d is a data format of a proxy binding response PBA according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of switching between mobile nodes in a mobile management domain according to an embodiment of the present invention
  • FIG. 3 is a flowchart of handover of a mobile node in a mobility management domain according to an embodiment of the present invention
  • FIG. 4 is a flowchart of an operation of a mobile node after entering a new mobility management domain according to an embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of an apparatus for implementing mobility management inter-domain handover according to an embodiment of the present invention
  • FIG. 7 is a flowchart of a handover of a mobile management inter-domain handover according to still another embodiment of the present invention
  • FIG. 8 is a structural block diagram of a network device according to an embodiment of the present invention.
  • the present invention proposes a new method for implementing mobile management inter-domain handover, which is used for establishing and maintaining a data forwarding process of a user during handover, to provide localized, user-based network when the user moves between different domains.
  • Mobility support enables users to maintain continuity with peer communication. This solution does not require a home domain to provide data forwarding services for the MN.
  • the embodiment provides a mobile management inter-domain handover system, including: a local mobility anchor point (LMA), configured to provide a home generation to a MN in the domain in a PMIPv6 domain.
  • LMA local mobility anchor point
  • the function of the Home Agent is specifically to assign the home prefix of the MN, manage the reachability state of the MN, and perform mobility management for the users in the bootstraps of the domain. After moving to other domains, you can continue to provide mobility services to users through tunnel forwarding.
  • MAG mobile access gateway
  • the mobile node (MN) as the mobile terminal, does not need to support a special protocol other than the IPv6 protocol, and may Is a laptop, single or multimode mobile phone, PDA, IAD, etc.;
  • the peer communication node (CN), the node that can communicate with the MN, can be a fixed node or a mobile node, and only needs to support the IPv6 protocol; if it is a mobile node, its function will be the same as ⁇ .
  • the MN When the MN initially accesses the PMIP domain I, for example, the MN has just started up in the PMIP domain 1, regardless of whether the original HA of the MN belongs to the current PMIP domain, the MN will send a router request message to the MAG-1 to obtain the current network configuration information; - 1 instead of the MN sending a proxy binding update (PBU, Proxy Binding Update) message to the LMA-1, performing a proxy binding update operation; the LMA-1 determines whether the SMA has previously selected the SMA, and if it is the initial access, ie, the MN SMA was not selected before, and LMA-1 is used as the SMA of MN.
  • the proxy binding update will be performed and a proxy binding response (PBA, Proxy Binding Acknowledgement) message will be sent to MAG-1.
  • PBA Proxy Binding Acknowledgement
  • the network that the MN initially connects will be paired with MN.
  • the mobility service is managed; in addition, inter-domain signaling is introduced between the network guiding the bootstrapping access and the new visited network for session switching and data forwarding.
  • the MN will send a router request message to the MAG-2 to obtain the current network configuration information; the MAG-2 sends the PBU message to the LMA-2 instead of the MN.
  • the agent binding update operation is performed; the LMA-2 determines whether the SMA has previously selected the SMA, because the MN has previously selected LMA-1 as the SMA of the MN, and the LMA-2 forwards the PBU to the SMA (LMA-1) to Registering at SMA, indicating that it is a new LMA for MN; SMA After receiving the PBU, the corresponding policy will be adopted for the MN (same operation as when the MN is local), the proxy binding update will be performed, and a PBA message will be created and sent to the LMA-2; the LMA-2 receives the PBA message and completes the SMA with the SMA. The establishment of the bidirectional tunnel; the LMA-2 forwards the PBA message to the MAG-2.
  • the MAG-2 After receiving the message, the MAG-2 uses the relevant information to complete the configuration of the MN; the MAG-2 sends a router advertisement message to the MN as a request to the router. The response of the message informs the MN that it can continue to use its original address (PMIPv6 process); thereafter, all the communication packets of the MN are received and transmitted through MAG-2, LMA-2, and LMA-2 and SMA (LMA- 1) A two-way tunnel between SMAs.
  • the above LMA-1 and LMA-2 may be entities having the same function and module, and perform a response operation for the attachment of the MN (whether or not the SMA has been selected).
  • the PBU message used in the above interaction includes a sequence number (sequence#), a response identifier bit (A, Acknowledge), a home registration flag (H, Home Registration), and a local connection address.
  • sequence# sequence number
  • A response identifier bit
  • H home registration flag
  • L Link-Local Address
  • the PBU message carries the HoA address of the MN and the address of the MAG. After receiving the message, the LMA saves the correspondence between the MN and the MAG as new proxy information. Then, if the LMA is SMA, the MN is further allocated. A CoA, after which the MN initiates a session using the CoA.
  • the PBA message used in the above interaction includes the status identifier, the Key Management Mobility Capability (K, Key Management Mobility Capability), and the proxy registration identifier (P, Proxy). Registration flag) flag and the like, 1 J bad sequence number (sequence #), reserved field (reserved), survival time (lifetime), and a data field.
  • the MN After the MN switches to the LMA-2, that is, enters the PMIP domain, and the MN needs to initiate a session, the MN first sends a session request to the LMA-2, where the request carries the HoA and the corresponding node (CN) address of the MN, LMA.
  • the proxy information The table includes the proxy information of all MNs responsible for LMA-2 in the domain where LMA-2 is located (PMIP domain ,). If the destination address is in the proxy information table, CN is the node in the local domain (PMIP domain ⁇ ).
  • LMA-2 directly establishes the connection between the MN and the CN without passing through the HoA or LMA-1; when the CN is not a node in the local domain, the LMA-2 forwards the session request to the LMA-1, and then is based on the LMA-1.
  • the address of the CN establishes a connection with the CN, and then performs session communication through the link of the CN-LMA-1 - LMA-2 - MN.
  • the LMA-1 and the LMA-2 are bidirectional tunnels.
  • the MN Before the MN switches to LMA-2, that is, the MN is in its initial access domain (PMIP domain I), when the MN initiates a session, the MN first sends a session request to LMA-1, and LMA-1 checks the local proxy table, if If the end node is an intra-domain node, LMA-1 directly establishes a session between the MN and the CN. If the CN is not a node in the local domain, the LMA-1 establishes a connection with the CN, and then performs a session through the CN-LMA-1 - MN link. Communication. The above session is all called by the MN. If the MN is called, the opposite node CN performs the same operation as the MN caller.
  • the LMA of the access network in the MN boot process is used as its SMA, which solves the problem that the home network domain becomes a communication bottleneck; the inter-domain signaling is introduced between the network domain where the SMA is located and the new LMA management domain that the MN enters.
  • a method for implementing mobility management inter-domain handover according to an embodiment of the present invention, as shown in FIG. 2, includes:
  • Step S201 Determine a local mobility anchor point LMA1 of the first mobility management domain to which the mobile node MN initially attaches as a session mobility anchor SMA, and establish a first connection between the mobile node MN and the LMA1.
  • Step S202 When the MN enters the second mobility management domain, the mobile access gateway MAG in the second mobility management domain receives a route request message sent by the MN, and sends current network configuration information to the MN, establishing a second connection between the mobile node MN and a local mobility anchor LMA2 in the second mobility management domain; and the MN disconnects the first connection with the LMA1; Step S203, establishing a bidirectional tunnel between the LMA2 and the SMA; establishing a transparent bidirectional data channel between the MN and the SMA (LMA1) by the entity LMA2 in the second mobility management domain;
  • Step S204 Update a proxy binding relationship of the session mobility anchor SMA.
  • the SMA receives a proxy binding update acknowledgement sent by an entity in the second mobility management domain (eg, a mobile access gateway MAG or a local mobility anchor LMA device) a message; after updating the proxy binding relationship of the SMA, the SMA sends a proxy binding response message to an entity in the second mobility management domain;
  • a proxy binding update acknowledgement sent by an entity in the second mobility management domain (eg, a mobile access gateway MAG or a local mobility anchor LMA device) a message
  • the SMA sends a proxy binding response message to an entity in the second mobility management domain;
  • Step S205 Forward, by the SMA, and transmit the data sent and received by the MN by using the bidirectional tunnel.
  • the method further includes: locating the SMA:
  • the entity in the second mobility management domain queries a database in which a correspondence between the session mobility anchor SMA and the mobile node is pre-stored, and obtains an address or identifier information of the session mobility anchor SMA, according to the address of the SMA or Identify the information to locate the SMA; or
  • the SMA is located in an indirect manner: the SMA is responsible for managing the IP address and forwarding the session request. Therefore, the message or the data packet transmitted between the SMA and the MN includes the address or identification information of the SMA; the entity in the second mobility management domain may obtain the message or the data packet sent or received from the MN.
  • the address or identifier information of the session mobility anchor SMA is located, and the SMA is located according to the address or the identifier information of the SMA.
  • the message may be a connection request message and a route request message, where the data may be a service data packet and signaling data. .
  • the LMA of the access network in the MN boot process is used as its SMA, which solves the problem that the home network domain becomes a communication bottleneck; the inter-domain signaling is introduced between the network domain where the SMA is located and the new LMA management domain that the MN enters.
  • the network-based MN switching process between local mobility management domains in the embodiment of the present invention includes the following steps S301-S304:
  • the MN When the MN initially attaches to a mobility management domain PMIP Domain 1, establishes a connection between the MN and a local mobility anchor LMA1 in the PMIP Domain 1 domain, and determines the LMA1 as a session mobility anchor SMA.
  • LMA1 becomes the MN's SMA and will be responsible for processing all transmitted and received data packets for the MN so that the MN can communicate with the correspondent node through LMA1.
  • the MN is in the PMIP Domain 1 domain, the operation only uses the normal operation of the PMIP.
  • the MN enters the second mobility management domain, establishes a connection between the mobile node MN and the mobility anchor point LMA2 in the second mobility management domain, and establishes a bidirectional tunnel between the LMA2 and the SMA;
  • the MN moves from the PMIP Domain 1 domain to the second mobility management domain PMIP Domain 2, and the MN establishes a connection with the LMA2 through the MAG2, and establishes a tunnel between the LMA2 in the PMIP Domain 2 domain and the SMA (ie, LMA1).
  • SMA SMA
  • the SMA to act as a mobility anchor for the MN to continue to provide mobility services for the MN; in the PMIP Domain 2 domain, all MN packets are forwarded through a bidirectional tunnel and SMA, and other PMIP operations are equally applicable, so from an SMA perspective,
  • the current LM's LMA can be seen as performing the functions of the MAG.
  • S304 Forward, by the SMA, and transmit the data sent and received by the MN by using the bidirectional tunnel.
  • the MN moves to the mobility management domain PMIP Domain 3
  • the MN establishes a connection with the LMA3 through the MAG3, and establishes a tunnel between the LMA3 in the PMIP Domain 3 domain and the SMA (ie, LMA1) to Allow SMA to continue to provide mobility for MN as MN's mobility anchor Service.
  • the LMA of the domain needs to locate the SMA of the MN and establish a bidirectional tunnel between the LMA and the SMA. This is divided into two situations:
  • the SMA needs to be located before establishing a bidirectional tunnel between the LMA2 and the SMA. There are two ways to locate SMA:
  • the entity in the second mobility management domain queries the database of the correspondence between the pre-stored session mobility anchor SMA and the mobile node, and obtains the address or identification information of the session mobility anchor SMA, and locates according to the identifier information of the SMA. SMA.
  • the SMA is located in the following indirect manner: Because the SMA is responsible for managing the IP address and forwarding A session request, so the message or packet passed between the SMA and the MN contains the address or identification information of the SMA.
  • An entity in the mobility management domain PMIP Domain 2 may obtain an address or identification information of the session mobility anchor SMA from a message or a data packet sent or received by the MN, and locate the SMA according to the address or the identifier information of the SMA. .
  • the message includes a connection request message and a route request message; the data includes a service data packet and signaling data. Referring to Figure 4, after the MN enters the LMA coverage of the new mobility management domain, the operation process is as follows:
  • the attach procedure is first completed; for example, after the MN reboots, the new mobility management domain is entered, and the LMA bootstrap MN in the domain performs mobility management. 5402.
  • the MN sends a router request message to the MAG to obtain current network configuration information.
  • the MAG sends a proxy binding update PBU message to the LMA instead of the MN, and performs a proxy binding update operation;
  • the LMA forwards the proxy binding update PBU message to the SMA, to register with the SMA, indicating that it is a new LMA of the MN;
  • the SMA after receiving the proxy binding update PBU message, the SMA adopts a corresponding policy for the MN (the same operation as the MN is locally), performs proxy binding update, and creates a proxy binding response PBA message, and sends the PBA message to the LMA;
  • the LMA receiving proxy binds the response PBA message, and completes the establishment of the bidirectional tunnel with the SMA;
  • the LMA forwards the PBA message to the MAG. After receiving the message, the MAG uses the related information to complete the configuration of the MN.
  • the MAG sends a router advertisement message to the MN as a response to the router request message, and informs the MN that the original address can be used continuously (the PMIPv6 process);
  • the reception and transmission of all communication data packets of the MN will be forwarded by the SMA through the MAG, the LMA, and the bidirectional tunnel between the LMA and the SMA.
  • the LMA of the access network in the MN boot process is used as its SMA, which solves the problem that the home network domain becomes a communication bottleneck; the inter-domain signaling is introduced between the network domain where the SMA is located and the new LMA management domain that the MN enters.
  • an embodiment of the present invention further provides a network entity 500, including:
  • the receiving unit 510 is configured to receive a proxy binding update request message sent by the MN.
  • the updating unit 520 is configured to perform a proxy binding update according to the proxy binding update request.
  • the tunnel establishing unit 530 is configured to establish a mobility anchor between the mobile management domain and the remote node to which the peer node belongs. Two-way l3 ⁇ 4 way;
  • the communication unit 540 forwards the data sent by the MN to the correspondent node to the local mobility anchor in another mobility management domain by using the bidirectional tunnel, and forwards data from the opposite node to the UI.
  • the management unit 550 is configured to allocate a home prefix to the mobile node MN and manage the reachable routing state of the MN.
  • the LMA accessing the network in the MN guiding process is used as the SMA, which solves the problem that the home network domain becomes a communication bottleneck;
  • Inter-domain signaling is introduced between the network domain and the new mobility management domain that the MN enters, a bidirectional tunnel is established, data is forwarded, communication continuity is ensured, and the problem of switching between PMIPv6 domains is solved.
  • the new domain of the SMA is entered in the network domain and the MN.
  • the LMA manages inter-domain inter-domain signaling, establishes a bidirectional tunnel, performs data forwarding, ensures communication continuity, and solves the problem of inter-domain handover between PMIPv6.
  • the LMA provides More efficient data forwarding path and shorter communication delay; Adopting a network-based mobility management solution, no terminal participation is required at all, and the implementation cost is small.
  • the following examples describe the application of the above solution to the relevant standards of the 3GPP SA2 Working Group.
  • Implementing the above solution under the relevant standards of the 3GPP SA2 Working Group does not require a home domain to provide data forwarding services for the MN.
  • the signaling and data are forwarded to the IP gateway (IP Gateway, GW-L (Serving) service gateway) located in the second mobility management domain.
  • IP gateway IP Gateway, GW-L (Serving) service gateway
  • PDN Packet Data Network
  • a further embodiment of the present invention further provides a method for implementing mobility management inter-domain handover, as shown in FIG. 6 and in conjunction with FIG. 7, the method includes:
  • the local mobility anchor LMA is the 3GPP SAE standard.
  • the mobile access gateway MAG in the second mobility management domain receives the routing request message sent by the mobile node MN, and sends current network configuration information to The mobile node MN establishes a connection between the mobile node MN and a local mobility anchor LMA in the second mobility management domain.
  • the local mobility anchor LMA in the second mobility management domain obtains subscription information and service related information of the mobile node MN.
  • the MN subscription can be obtained through the policy and charging rule function module (hPCRF) of the first mobility management domain.
  • hPCRF policy and charging rule function module
  • the bidirectional tunnel is a PMIP tunnel; at this time, the connection of the mobile node MN to the local mobility anchor of the first mobility management domain is disconnected.
  • the local mobility anchor LMA of the second mobility management domain can be used as the SMA of the mobile node MN, and it can be considered that the MN has two SMAs in this case.
  • the SMA of the MN is the local mobility anchor LMA of the previous mobility management domain (ie, the first mobility management domain) when processing the traffic performed during the mobile process, and the SMA of the MN is the current mobility management domain when processing the service initiated after the mobility. (ie the second mobility management domain) of the local mobility anchor LMA.
  • the SMA receives a proxy binding sent by an entity in the second mobility management domain (eg, a mobile access gateway MAG or a mobility anchor LMA device). a new acknowledgement message; after updating the proxy binding relationship, the SMA sends a proxy binding response message to an entity in the second mobility management domain;
  • an entity in the second mobility management domain eg, a mobile access gateway MAG or a mobility anchor LMA device.
  • the SMA of the mobile node MN in the first mobility management domain forwards data sent and received by the MN through the bidirectional tunnel.
  • the route between the MN and the internetwork passes through the local mobility anchor LMA of the first mobility management domain to the local mobility anchor LMA of the second mobility management domain, and then to the mobile node. MN.
  • the route between the mobile node MN and the Internet is sent to the Internet via the local mobility anchor LMA of the second mobility management domain.
  • the local mobility anchor LMA in the second mobility management domain under the 3GPP SAE standard is the PDN GW, so the data of the mobile node MN is sent to the internetwork through the PDN GW.
  • the mobile access gateway (MAG, Mobile Access Gateway) in the third mobility management domain receives the routing request message sent by the mobile node MN, and The current network configuration information is sent to the mobile node MN to establish a third connection between the mobile node MN and a mobility anchor point in the second mobility management domain (previous mobility management domain).
  • MAG Mobile Access Gateway
  • the local mobility anchor LMA in the third mobility management domain obtains subscription information of the mobile node MN and service related information, for example, an operation and a policy of the first mobility management domain (home network)
  • the home policy Charging Rules Function obtains the subscription information and service related information of the MN.
  • the local mobility anchor LMA in the third mobility management domain of the mobile node MN and its previous mobility management domain (second mobile) interacts to establish a bidirectional tunnel between the two to maintain the continuity of the service.
  • the two-way tunnel between the SMA of the first mobility management domain and the local mobility anchor LMA of the second mobility management domain is Release, when the two-way tunnel is released, the SMA of the mobile node MN is the local mobility anchor LMA of the second mobility management domain, so when the MN moves to the third mobility management domain, the mobile node MN is in the second mobile
  • the local mobility anchor LMA in the management domain acts as the SMA of the mobile node MN.
  • the bidirectional tunnel of the local mobility anchor LMA of the current mobility management domain to which the mobile node MN belongs and the SMA of the mobile node MN are established.
  • the SMA of the MN may be the LMA of the previous mobility management domain to which the MN belongs, and the previous mobility management domain may be a home network or a visited network.
  • the SMA of the mobile node MN in the second mobility management domain is bound to the local mobility anchor LMA of the third mobility management domain.
  • the SMA of the mobile node MN in the second mobility management domain forwards data sent and received by the mobile node MN through the bidirectional tunnel.
  • the route between the mobile node MN and the internetwork passes through the local mobility anchor LMA of the second mobility management domain to the local mobility anchor LMA of the third mobility management domain, and then to the mobile Node MN.
  • the route between the mobile node MN and the Internet is sent to the internetwork through the local mobility anchor LMA of the third mobility management domain.
  • the local mobility anchor LMA in the third mobility management domain under the 3GPP SAE standard is the PDN GW, so the MN data is directly sent to the internetwork through the PDN GW.
  • the switching process is changed correspondingly to the existing process, which will be described in detail below.
  • target Serving Gateway sends a corresponding request message (for example: Create Bearer Request, create bearer request message or Proxy Binding Update, proxy binding update message) to the target packet data gateway (Target PDN GW) of the current mobility management domain.
  • request message for example: Create Bearer Request, create bearer request message or Proxy Binding Update, proxy binding update message
  • the packet data gateway in the new mobility management domain and the PCRF Policy Charging Rules Function perform the relevant policies for obtaining the packet data gateway.
  • the active node MN currently has ongoing services, and the target packet data gateway will initiate a proxy binding update message to the source packet data gateway (Source PDN GW).
  • a request is made to establish a bidirectional tunnel with the Source PDN GW, which is a PMIP tunnel. Determining whether the packet data gateway has changed in operation can be achieved by comparing the destination packet data gateway with the address of the Source PDN GW, or in other ways.
  • the Source PDN GW replies to the target packet data gateway with a request message (for example, a Proxy Binding Ack message); since then, a two-way tunnel has been established between the Source PDN GW and the Target PDN GW.
  • a request message for example, a Proxy Binding Ack message
  • the target packet data gateway sends a reply message to the target service gateway, for example, a Create Bearer Response message or a Proxy Binding Ack.
  • the handover is completed.
  • the data packet reaches the Source PDN GW and is sent to the mobile node MN via the PMIP tunnel of the Source PDN GW and the Target PDN GW.
  • the new service requested by the mobile node MN after switching the data packet is directly sent to the Target PDN.
  • the Source PDN GW considers that the MN is the SMA in the previous mobility management domain, and the Source PDN GW is the LMA of the MN in the previous mobility management domain; the target packet data gateway is The LMA of the current mobility management domain, the target packet data gateway is the PDN GW of the current mobility management domain, and is the SMA of the MN in the current mobility management domain.
  • the above handover procedure can be applied to various scenarios, such as moving a mobile node from a 3GPP network to another 3GPP network under a 3GPP SAE architecture, or moving a mobile node from a 3GPP network to a non-3GPP network, or moving a mobile node from a non-3GPP network to 3GPP network.
  • the mobile node MN When the mobile node moves from the 3GPP network to another 3GPP network, the mobile node MN is located in the 3GPP network VPLMN 1 and accesses from the 3GPP access network, and performs service interaction in the form of Local Breakout. The mobile node MN moves again and roams to another 3GPP network VPLMN 2. There is ongoing business during the roaming process. Or the MN is located in the 3GPP network HPLMN1, roaming to another 3GPP network VPLMN 2, and will perform service interaction in the form of PMIPv6-based Local Breakout, and there is ongoing service in the roaming process; the above process may be adopted in the handover, when the target packet data gateway sends After the message is sent to the target service gateway, the process continues.
  • the MN When the mobile node moves from the 3GPP network to the non-3GPP network, the MN is located in the 3GPP network VPLMN 1 and accesses from the 3GPP access network, and uses the Local Breakout form for service interaction.
  • the mobile node MN moves again and switches to another non-3GPP access network.
  • the Serving GW and the PDN GW (for example, the Inter-PLMN case) need to be reselected at the same time, and there is an ongoing service during the roaming process; the above process may be adopted in the handover, after the target packet data gateway sends a reply message to the target service gateway. Continue to switch processes.
  • the MN When the mobile node moves from the non-3GPP network to the 3GPP network, the MN is located in the non-3GPP access network, and uses the Local Breakout form for service interaction. The MN moves again and switches to a 3GPP access network. At this time, the Serving GW and the PDN GW (for example, the Inter-PLMN case) must be reselected at the same time. There is an ongoing service during the roaming process; the above process can be used in the handover, and the handover process is continued after the target packet data gateway sends a reply message to the target service gateway.
  • the Serving GW and the PDN GW for example, the Inter-PLMN case
  • the device in the previous mobility management domain to which the mobile node belongs is used as an anchor point in the ongoing service in the handover process of the mobile node, and inter-domain signaling is introduced between the mobile management domain to which the mobile node belongs and the previous mobility management domain. , establish a two-way tunnel, forward data, and ensure the connection of the business Continuation, solve the problem of inter-domain switching of PMIPv6.
  • an embodiment of the present invention further provides a network node device 800, where the device includes:
  • connection establishment module 801 configured to establish a connection with the mobile node
  • a tunnel establishment module 802 configured to establish a bidirectional tunnel between a session mobility anchor point of the mobile node
  • the binding update module 803 is configured to update a proxy binding relationship of the session mobility anchor of the mobile node in the previous mobility management domain to which the mobile node belongs.
  • the device may serve as a local mobility anchor of a certain mobility management domain in the network.
  • the device adds the information obtaining module 804 for obtaining the subscription information of the mobile node in the network and the service related information, the device may serve as the mobile node.
  • the session moves the anchor device.
  • the foregoing method can be implemented by using the network node device in this embodiment, and the device in the previous mobility management domain to which the mobile node belongs is used as an anchor point in the ongoing service in the handover process of the mobile node, where the mobile node currently belongs to the mobile management domain and before.
  • Inter-domain signaling is introduced between a mobile management domain to establish a bidirectional tunnel for data forwarding to ensure continuity of services and to resolve inter-domain handover problems of PMIPv6.

Landscapes

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

Description

一种实现移动管理域间切换的方法及装置 技术领域
本发明涉及移动通信技术领域, 具体涉及实现移动管理域间切换的方法 及装置。
背景技术
移动节点 (MN, Mobi le Node )在当前的 Internet 网络中移动时, 需要 维持一个固定的端点, 以提供其与对端节点 (CN, Corresponding Node ) 的 无缝连接与通信。
在基于网络 ( network-based ) 的移动性方案中, 如 PMIP ( Proxy ΜΙΡνό , 代理移动 IP协议 ),固定端点为本地移动锚点( LMA, Loca l Mob i l i ty Anchor )。 该本地移动锚点允许顯在移动时改变其附着位置, 而无需向通信对端进行通 告, 同时所有移动节点的通信流量都将通过本地移动锚点进行路由, 并通过 隧道转发给 MN。
在基于网络的移动性方案中, 当顯在不同移动性管理域间移动时, 移动 IP ( MIP , Mobi le IP )协议支持 MN在 IP网络中移动时的连接性, 使 MN在离 开其归属网络后仍能保持与网络的连接。 MN始终采用归属网络( Home Network ) 分配的归属地址(HoA, Home Addres s )进行标识, 不因拜访网络的改变而改 变; 当 MN 离开归属网络时, 将与拜访网络分配的转交地址(CoA, Care Of Addres s )相关联, MN的当前位置由 CoA来标识, 同时它将向归属代理( HA, Home Agent )发送其当前位置信息。 而 HA将截获发送到 MN HoA的数据包并 通过隧道将其转发给顯的 CoA。 整个处理过程只在 IP层执行, 而对 IP以上 的所有层次透明。
在基于网络的移动性方案中, 需要家乡域的参与, 才能完成域间切换, 因此, 限制了网络的可扩展性, 并且影响了数据转发效率, 这将导致家乡网 络成为通信瓶颈, 将带来更大的数据转发时延和网络资源浪费。 发明内容
本发明提供一种实现移动管理域间切换的方法及装置, 可提供更加有效 的数据转发路径和更短的通信时延。
本发明实施例提供的一种实现移动管理域间切换的方法, 包括: 将移动节点 MN初始附着的第一移动管理域的本地移动锚点 LMA1确定为 会话移动锚点 SMA , 并建立移动节点顯与所述 LMA1之间的第一连接;
建立所述移动节点 MN与第二移动管理域中的本地移动锚点 LMA2之间的 第二连接;
建立所述 LMA2与所述 SMA之间的双向隧道;
更新所述会话移动锚点 SMA的代理绑定关系;
通过所述 SMA转发并采用所述双向隧道传输所述顯发送和接收的数据。 本发明实施例还提供一种网络实体, 包括:
接收单元, 用于接收顯发送的代理绑定更新请求消息;
更新单元, 用于根据所述代理绑定更新请求执行代理绑定更新; 隧道建立单元, 用于建立与对端节点所属移动管理域中本地移动锚点之 间的双向! ¾道;
通信单元, 利用所述双向隧道所述将所述顯发送给对端节点的数据转发 给另一移动管理域中本地移动锚点 ,并将来自对端节点的数据转发给所述 MN。
本发明实施例提供的技术方案中, 采用顯引导过程中接入网络的 LMA作 为其 SMA, 解决了家乡网络域成为通信瓶颈的问题; 在 SMA所在网络域与顯 进入的新的 LMA管理域间引入域间信令, 建立双向隧道进行数据转发, 保证 通信连续性, 解决了 PMIPv6域间切换问题, 与现有的需要家乡网络支持的域 间切换方案相比, 提供了更加有效的数据转发路径和更短的通信时延, 采用 基于网络的移动性管理方案, 完全无需终端参与, 易于实现。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍, 显而易见地, 下面 描述中的附图仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得其他的附图。
图 la为本发明实施例中移动管理域的网络架构示意图;
图 lb为本发明实施例中移动节点在移动管理域间切换流程图; 图 lc为本发明实施例中代理绑定更新 PBU的数据格式;
图 Id为本发明实施例中代理绑定响应 PBA的数据格式;
图 2为本发明实施例中移动节点在移动管理域间切换流程图;
图 3为本发明实施例中移动节点在移动管理域间切换流程图;
图 4为本发明实施例移动节点进入新的移动管理域后的操作流程图; 图 5为本发明实施例实现移动管理域间切换的装置架构示意图; 图 6为本发明又一实施例实现移动管理域间切换的方法流程图; 图 7为本发明又一实施例实现移动管理域间切换的切换流程图; 图 8为本发明实施例中网络设备的结构框图。
具体实施方式
下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行 清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而 不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有作 出创造性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
本发明提出了一种新的实现移动管理域间切换的方法, 用于建立和维护 用户在切换时的数据转发流程, 以在用户进行不同域间移动时, 为用户提供 本地化的, 基于网络的移动性支持, 使用户能保持与对端通信的连续性。 该 方案无需家乡域(home domain ) 为 MN提供数据转发服务。
实施例一
如图 la所示, 本实施例提供了一种移动管理域间切换的系统, 包括: 本地移动锚点 (LMA ) , 用于在 PMIPv6域内向本域内的 MN提供家乡代 理( Home Agent ) 的功能, 具体的为, 分配 MN的家乡前缀( home prefix ) , 管理 MN的可达状态( reachability state ) , 为在本域内引导(bootstraps ) 的用 户进行移动性管理, 当用户移动到其它域后, 可以通过隧道转发的方式, 继 续为用户提供移动性业务;
移动接入网关( MAG ) , 用于为 MN管理移动性相关信令交互, 跟踪 MN 与当前链路的连接状态; 移动节点 (MN ) , 作为移动终端, 无需支持 IPv6协 议外的特殊协议, 可以是笔记本电脑、 单模或多模手机、 PDA、 IAD等;
对端通信节点 (CN ) , 可以与 MN进行通信的节点, 可以是固定节点, 也可以为移动节点, 同样只需支持 IPv6协议; 如果为移动节点, 其功能将与 匪相同。
当 MN初始接入 PMIP域 I时, 例如 MN刚刚在 PMIP域 I中开机, 不 管 MN原来的 HA是否属于现在的 PMIP域, MN将向 MAG-1发送路由器请 求消息, 获取当前网络配置信息; MAG- 1代替 MN向 LMA- 1发送代理绑定 更新 ( PBU, Proxy Binding Update ) 消息, 进行代理绑定更新操作; LMA-1 判断 MN之前是否已经选定了 SMA, 如果是初始接入, 即 MN之前没有选定 SMA, LMA-1作为 MN的 SMA, 进行代理绑定更新并将创建代理绑定响应 ( PBA, Proxy Binding Acknowledgement ) 消息, 向 MAG-1发送。
如图 la及 lb所示, 无论 MN往哪个域(如图 la中的 PMIP域 II及 PMIP 域 III )移动, MN初始连接(例如, 重新开机后导引 bootstraps接入)的网络, 将对 MN的移动性业务进行管理; 此外, 还在导引 bootstrapping接入的网络 和新的拜访网络间引入域间信令, 以进行会话切换和数据转发。 例如, 当 MN 从初始连接网络 PMIP域 I移动到相邻的 PMIP域 II时, MN将向 MAG-2发 送路由器请求消息, 获取当前网络配置信息; MAG-2代替 MN向 LMA-2发 送 PBU消息,进行代理绑定更新操作; LMA-2判断 MN之前是否已经选定了 SMA, 因为 MN之前已经选定 LMA-1作为 MN的 SMA, LMA-2将 PBU向 SMA ( LMA-1 )转发, 以在 SMA进行注册, 表明其为 MN的新 LMA; SMA 收到 PBU后, 将为 MN采取相应的策略(与 MN在本地时操作相同), 进行 代理绑定更新并将创建 PBA消息 , 向 LMA-2发送; LMA-2接收 PBA消息 , 并完成与 SMA间双向隧道的建立; LMA-2将 PBA消息向 MAG-2转发 , MAG-2 收到该消息后, 使用相关信息完成对 MN的配置; MAG-2向 MN发送路由器 通告消息, 作为对路由器请求消息的应答, 告知 MN可以继续使用其原有地 址(PMIPv6 流程); 此后, MN 所有的通信数据包的接收和发送, 都将通过 MAG-2、 LMA-2以及 LMA-2和 SMA ( LMA-1 ) 间的双向隧道, 由 SMA转 发。
其中, 上述 LMA-1、 LMA-2可以是具有相同功能和模块的实体, 针对 MN 的附着情况(是否已选定了 SMA ) , 执行响应的操作。
在上述交互中使用的 PBU消息, 如图 lc所示, 该 PBU消息包括, 序列号 ( sequence# ) , 应答标识位(A, Acknowledge )、 家乡注册标识位 ( H, Home Registration ) 、 本地连接地址兼容 '1 "生标志位(L, Link-Local Address
Compatibility ) 、 密钥管理移动能力标志位 ( K, Key Management Mobility Capability ) 、 代理注册标识位 ( P, Proxy Registration Flag )等标识位, 保留 域(Reserved ) , 生存时间 (Lifetime ) , 以及数据域; 其中 PBU消息中携带 了 MN的 HoA地址和 MAG的地址 , LMA接收到该消息后 , 将其中保存 MN和 MAG的对应关系作为新的代理信息, 之后, 如果该 LMA为 SMA的话则进一步 为 MN分配一个 CoA,之后 MN使用该 CoA发起会话。在上述交互中使用的 PBA 消息, 如图 Id所示, 该 PBA消息包括, 状态标识(status ) , 密钥管理移动能 力标志位 ( K, Key Management Mobility Capability ) 、 代理注册标识位 ( P, Proxy Registration Flag )等标识位,序歹1 J号 ( sequence# ) ,保留域 ( Reserved ) , 生存时间 (Lifetime ) , 以及数据域。
当 MN切换到 LMA-2后, 即进入 PMIP域 Π , MN需要发起会话, 则 MN首 先向 LMA-2发送会话请求, 该请求中携带 MN的 HoA和目的端 ( corresponding node, CN )地址, LMA-2根据会话请求查看自身的代理信息表, 该代理信息 表中包括了 LMA-2所在域(PMIP域 Π ) 中由 LMA-2负责的所有 MN的代理信 息, 如果目的端地址在代理信息表中, 则 CN是本域(PMIP域 Π ) 中的节点, LMA-2直接建立 MN与 CN的连接, 而不需要通过 HoA或者 LMA-1 ; 当 CN不是 本域中的节点时, 则 LMA-2向 LMA-1转发会话请求, 然后由 LMA-1根据 CN的 地址建立与 CN的联系 , 之后通过 CN - LMA-1 - LMA-2 - MN的链路进行会话 通信, 其中, LMA-1与 LMA-2之间是双向隧道。 在 MN切换到 LMA-2之前, 即 MN在其初始接入域( PMIP 域 I ) 中, 当 MN发起会话时, MN首先向 LMA-1 发送会话请求, LMA-1查看本地代理表,如果对端节点是域内节点,则 LMA-1 直接建立 MN与 CN的会话, 如果 CN不是本域内的节点, 则 LMA-1建立与 CN 的连接, 然后通过 CN - LMA-1 - MN的链路进行会话通信。 以上会话都是由 MN主叫 , 如果是 MN被叫 , 则对端节点 CN执行与 MN主叫相同的操作即可。
在该方案中, 采用 MN引导过程中接入网络的 LMA作为其 SMA, 解决了 家乡网络域成为通信瓶颈的问题; 在 SMA所在网络域与 MN进入的新的 LMA 管理域间引入域间信令, 建立双向隧道, 进行数据转发, 保证通信连续性, 解决了 PMIPv6域间切换问题; 采用基于网络的移动性管理方案, 完全无需终 端参与。
实施例二
本发明实施例提供的一种实现移动管理域间切换的方法, 如图 2所示, 包括:
步骤 S201、 将移动节点 MN初始附着的第一移动管理域的本地移动锚点 LMA1确定为会话移动锚点 SMA,并建立移动节点 MN与所述 LMA1之间的 第一连接;
步骤 S202、 在所述 MN进入所述第二移动管理域时, 所述第二移动管理 域中的移动接入网关 MAG接收所述 MN发送的路由请求消息, 将当前网络 配置信息发送给所述 MN, 建立所述移动节点 MN与第二移动管理域中的本 地移动锚点 LMA2之间的第二连接; 并 MN断开与 LMA1的第一连接; 步骤 S203、 建立所述 LMA2与所述 SMA之间的双向隧道; 通过所述第 二移动管理域中的实体 LMA2在 MN与 SMA ( LMA1 )之间建立透明的双向 数据通道;
步骤 S204、 更新所述会话移动锚点 SMA的代理绑定关系;
其中, 所述更新 SMA的代理绑定关系之前, 所述 SMA接收所述第二移 动管理域中的实体(如, 移动接入网关 MAG或本地移动锚点 LMA装置)发 送的代理绑定更新确认消息;更新所述 SMA的代理绑定关系之后,所述 SMA 发送代理绑定响应消息给所述第二移动管理域中的实体;
步骤 S205、 通过所述 SMA转发并采用所述双向隧道传输所述 MN发送 和接收的数据。
在步骤 S203建立所述 LMA2与所述 SMA之间的双向隧道之前 , 还包括 定位所述 SMA的步骤:
所述第二移动管理域中的实体查询预先存储有会话移动锚点 SMA 与移 动节点之间对应关系的数据库,获取所述会话移动锚点 SMA的地址或标识信 息,根据所述 SMA的地址或标识信息定位 SMA; 或者
若所述第一、第二移动管理域中不存在存储有会话移动锚点 SMA与移动 节点之间对应关系的数据库, 则通过间接方式定位所述 SMA: 由于 SMA负 责管理 IP地址并转发会话请求, 因此在 SMA与 MN之间传递的消息或数据 包中包含 SMA的地址或标识信息; 所述第二移动管理域中的实体从所述 MN 发送或接收的消息或数据包中可获取所述会话移动锚点 SMA 的地址或标识 信息, 根据所述 SMA的地址或标识信息定位 SMA; 其中, 所述消息可以是 连接请求消息、 路由请求消息, 所述数据可以是业务数据包以及信令数据。
在该方案中, 采用 MN引导过程中接入网络的 LMA作为其 SMA, 解决 了家乡网络域成为通信瓶颈的问题; 在 SMA所在网络域与 MN进入的新的 LMA管理域间引入域间信令, 建立双向隧道, 进行数据转发, 保证通信连续 性, 解决了 PMIPv6域间切换问题; 采用基于网络的移动性管理方案, 完全无 需终端参与。
实施例三
参照图 lb及图 3 , 本发明实施例中本地移动性管理域间基于网络的 MN切 换流程包括如下步骤 S301 ~ S304:
5301 ,建立移动节点 MN与初次附着的第一移动管理域中的本地移动锚点 LMA1之间的连接, 并将所述 LMA1确定为会话移动锚点 SMA;
MN初始附着到一个移动性管理域 PMIP Domain 1时,建立所述 MN与所述 PMIP Domain 1域中的本地移动锚点 LMA1之间的连接, 并将所述 LMA1确定 为会话移动锚点 SMA, LMA1成为 MN的 SMA, 将负责为 MN处理所有发送和 接收的数据包这样该 MN可提通过 LMA1与对端节点进行通信。 MN在 PMIP Domain 1域本地内时, 操作仅仅采用 PMIP的常规操作。
5302, MN进入第二移动管理域, 建立所述移动节点 MN与第二移动管理 域中的移动锚点 LMA2之间的连接, 并建立所述 LMA2与所述 SMA之间的双向 隧道;
MN从 PMIP Domain 1域移动到第二移动管理域 PMIP Domain 2 , MN通过 MAG2建立与 LMA2之间的连接 , 并建立 PMIP Domain 2域中的 LMA2与所述 SMA (即 LMA1 )之间的隧道, 以允许 SMA作为 MN的移动锚点继续为 MN提 供移动性服务; 在 PMIP Domain 2域中, 所有 MN的数据包都通过双向隧道以 及 SMA转发,其它 PMIP操作同样适用, 因此,从 SMA角度看, 当前 MN的 LMA 可以被看作执行了 MAG的功能。
5303 , 更新所述会话移动锚点 SMA的代理绑定关系。
5304,通过所述 SMA转发并采用所述双向隧道传输所述 MN发送和接收的 数据。
同样地 , 当所述 MN移动到移动管理域 PMIP Domain 3 , MN通过 MAG3建 立与 LMA3之间的连接, 并建立 PMIP Domain 3域中的 LMA3与所述 SMA (即 LMA1 )之间的隧道, 以允许 SMA作为 MN的移动锚点继续为 MN提供移动性 服务。
当 MN附着到一个 PMIP域时, 该域的 LMA需要定位 MN的 SMA, 并建立 该 LMA与 SMA的双向隧道。 这要分为两种情况:
1 )如果该域为 MN初次附着的域, 那么当前的 LMA将成为 SMA并执行常 规 PMIP操作;
2 )如果 MN之前已经附着过一个 PMIP域, SMA存在于之前附着的域, 那 么, LMA将定位 SMA, 并为收发数据建立双向隧道;
在建立所述 LMA2与所述 SMA之间的双向隧道之前 , 需要定位所述 SMA。 定位 SMA的方法可以有如下两种:
一 )直接定位 ( Direct location )
第二移动管理域中的实体查询预先存储的会话移动锚点 SMA与移动节点 之间的对应关系的数据库, 获取所述会话移动锚点 SMA的地址或标识信息, 根据所述 SMA的标识信息定位 SMA。
二) 间接定位 ( Indirect location )
若所述移动管理域 PMIP Domainl、 PMIP Domain2中不存在存储有会话移 动锚点 SMA与移动节点之间对应关系的数据库, 则通过下述间接方式定位所 述 SMA: 由于 SMA负责管理 IP地址并转发会话请求, 因此在 SMA与 MN之间 传递的消息或数据包中包含 SMA的地址或标识信息。 所述移动管理域 PMIP Domain 2中的实体从所述 MN发送或接收的消息或数据包中可获取所述会话 移动锚点 SMA的地址或标识信息, 根据所述 SMA的地址或标识信息定位 SMA。 所述消息包括连接请求消息、 路由请求消息; 所述数据包括业务数据 包以及信令数据。 参照图 4, MN进入新移动管理域的 LMA覆盖范围后, 操作 流程如下:
S401 , 当 MN进入新移动管理域 LMA覆盖网络后, 将首先完成附着流程; 例如, MN重新开机后进入新移动管理域, 本域内 LMA引导(bootstraps ) MN 进行移动性管理。 5402, MN将向 MAG发送路由器请求消息, 获取当前网络配置信息;
5403 , MAG代替 MN向 LMA发送代理绑定更新 PBU消息 , 进行代理绑定 更新操作;
5404, LMA将代理绑定更新 PBU消息向 SMA转发, 以在 SMA进行注册, 表明其为 MN的新 LMA;
5405, SMA收到代理绑定更新 PBU消息后, 将为 MN采取相应的策略(与 MN在本地时操作相同),进行代理绑定更新并将创建代理绑定响应 PBA消息, 向 LMA发送;
5406, LMA接收代理绑定响应 PBA消息, 并完成与 SMA间双向隧道的建 立;
5407, LMA将 PBA消息向 MAG转发, MAG收到该消息后, 使用相关信息 完成对 MN的配置;
5408, MAG向 MN发送路由器通告消息, 作为对路由器请求消息的应答, 告知 MN可以继续使用其原有地址(PMIPv6流程) ;
此后, MN所有的通信数据包的接收和发送, 都将通过 MAG、 LMA以及 LMA和 SMA间的双向隧道 , 由 SMA转发。
在该方案中, 采用 MN引导过程中接入网络的 LMA作为其 SMA, 解决了 家乡网络域成为通信瓶颈的问题; 在 SMA所在网络域与 MN进入的新的 LMA 管理域间引入域间信令, 建立双向隧道, 进行数据转发, 保证通信连续性, 解决了 PMIPv6域间切换问题; 采用基于网络的移动性管理方案, 完全无需终 端参与。
实施例四
参照图 5, 本发明实施例还提供一种网络实体 500, 包括:
接收单元 510, 用于接收 MN发送的代理绑定更新请求消息;
更新单元 520, 用于根据所述代理绑定更新请求执行代理绑定更新; 隧道建立单元 530,用于建立与对端节点所属移动管理域中移动锚点之间 的双向 l¾道;
通信单元 540,利用所述双向隧道所述将所述 MN发送给对端节点的数据 转发给另一移动管理域中本地移动锚点, 并将来自对端节点的数据转发给所 述匪。
管理单元 550, 用于为移动节点 MN分配家乡前缀, 并管理 MN的可达 路由状态。
综上所述, 本发明实施例提供的技术方案中, 在本发明提供的方案中, 采用 MN引导过程中接入网络的 LMA作为其 SMA, 解决了家乡网络域成为通 信瓶颈的问题; 在 SMA所在网络域与 MN进入的新移动管理域间引入域间信 令, 建立双向隧道, 进行数据转发, 保证通信连续性, 解决了 PMIPv6域间切 换问题; 在 SMA所在网络域与 MN进入的新的 LMA管理域间弓 1入域间信令, 建立双向隧道, 进行数据转发, 保证通信连续性, 解决了 PMIPv6域间切换问 题, 与现有的需要家乡网络支持的域间切换方案相比, 提供了更加有效的数 据转发路径和更短的通信时延; 采用基于网络的移动性管理方案, 完全无需 终端参与, 实现代价较小。
以下实施例介绍上述方案在 3GPP SA2工作组相关标准下的应用。在 3GPP SA2工作组相关标准下实现上述的方案不需要家乡网络(home domain )为 MN 提供数据转发服务。 MN从第一移动管理域经过移动到达第二移动管理域后, 信令及数据通过位于所述第二移动管理域的 IP网关 ( IP Gateway , GW-L(Serving)服务网关)转发到所述第二移动管理域的分组数据网 (PDN, Packet Data Network ) 。
本发明实施例再提供的又一实施例实现移动管理域间切换的方法, 如图 6 所示并结合图 7, 该方法包括:
S 601、 将移动节点初始附着的第一移动管理域的本地移动锚点 LMA确定 为会话移动锚点(SMA, Session Mobility Anchor ) , 并建立移动节点 MN与所 述本地移动锚点 LMA之间的连接。 该本地移动锚点 LMA即为 3GPP SAE标准 下的功能实体分组数据网关(PDN GW, Packet Data Network Gateway ) 。
5602、在所述移动节 MN点进入所述第二移动管理域时,建立所述移动节 点 MN与第二移动管理域(当前移动管理域)中的本地移动锚点 LMA之间的连 接。
在所述移动节 MN点进入所述第二移动管理域时,所述第二移动管理域中 的移动接入网关 MAG接收所述移动节点 MN发送的路由请求消息, 将当前网 络配置信息发送给所述移动节点 MN, 建立所述移动节点 MN与第二移动管理 域中的本地移动锚点 LMA之间的连接。
在第二移动管理域中的本地移动锚点 LMA获得移动节点 MN的签约信息 以及业务相关信息, 例如操作中可以通过第一移动管理域的策略和计费规则 功能模块(hPCRF )获得 MN的签约信息以及业务相关信息。
5603、建立所述第二移动管理域的本地移动锚点 LMA与所述 SMA之间的 双向隧道。通过所述第二移动管理域(当前移动管理域)中本地移动锚点 LMA 在移动节点 MN与前一移动管理域(第一移动管理域)中的本地移动锚点 LMA 之间建立双向隧道, 该双向隧道为 PMIP隧道; 此时断开移动节点 MN与第一 移动管理域的本地移动锚点的连接。
在所述双向隧道建立后第二移动管理域的本地移动锚点 LMA可以作为该 移动节点 MN的 SMA, 可以认为在这种情况下 MN有两个 SMA。 在处理移动过 程中进行的业务时该 MN的 SMA为前一移动管理域(即第一移动管理域)的本 地移动锚点 LMA, 在处理移动后发起的业务时 MN的 SMA为当前移动管理域 (即第二移动管理域) 的本地移动锚点 LMA。
5604、 更新该移动节点 MN在前一移动管理域(即第一移动管理域) 的 SMA的代理绑定关系; 将所述移动节点 MN在第一移动管理域的 SMA与当前 移动管理域(即第二移动管理域) 的本地移动锚点 LMA绑定。
其中, 更新所述代理绑定关系之前, 所述 SMA接收所述第二移动管理域 中的实体(如, 移动接入网关 MAG或移动锚点 LMA装置)发送的代理绑定更 新确认消息; 更新所述代理绑定关系之后, 所述 SMA发送代理绑定响应消息 给所述第二移动管理域中的实体;
5605、 该移动节点 MN在第一移动管理域的 SMA通过所述双向隧道转发 所述 MN发送和接收的数据。
当在移动的过程中移动节点 MN有业务进行时, MN与互联网络之间的路 由通过第一移动管理域的本地移动锚点 LMA到第二移动管理域的本地移动锚 点 LMA, 再到移动节点 MN。 当移动节点 MN移动到第二移动管理域后发起的 业务,移动节点 MN到互联网之间的路由为经过第二移动管理域的本地移动锚 点 LMA发送到互联网。在 3GPP SAE标准下第二移动管理域中的本地移动锚点 LMA为 PDN GW, 所以移动节点 MN的数据通过 PDN GW发送到互联网络。
5606、 当所述移动节点 MN再次移动,进入第三移动管理域时该第三移动 管理域中的移动接入网关(MAG, Mobile Access Gateway )接收所述移动节 点 MN发送的路由请求消息, 将当前网络配置信息发送给所述移动节点 MN, 建立所述移动节点 MN与第二移动管理域(前一移动管理域)中的移动锚点之 间的第三连接。
5607、 在第三移动管理域(当前移动管理域) 中的本地移动锚点 LMA获 得移动节点 MN的签约信息以及业务相关信息, 例如操作中可以通过第一移动 管理域(家乡网络)的策略和计费规则功能模块(hPCRF, home Policy Charging Rules Function )获得 MN的签约信息以及业务相关信息。
S608、 建立所述第三移动管理域的本地移动锚点 LMA与前一移动管理域 (第二移动管理域)的本地移动锚点 LMA之间的双向隧道; 移动节点 MN断开 与第二移动管理域的移动锚点的连接。 此实施例中当前移动管理域(第三移 动管理域) 的本地移动锚点 LMA不再与家乡网络的会话移动锚点建立隧道。 (本实施例中家乡网络即为第一移动管理域) 。
移动节点 MN切换过程中, 如果存在正在进行的业务, 此时移动节点 MN 的第三移动管理域中的本地移动锚点 LMA将和其前一移动管理域(第二移动 管理域) 中的本地移动锚点 LMA进行交互, 在两者之间建立一条双向隧道, 用于保持业务的连续性。
在 MN从第一移动管理域到第二移动管理域移动的过程中进行的业务完 成后, 原来第一移动管理域的 SMA与第二移动管理域的本地移动锚点 LMA之 间的双向隧道被释放,当所述的双向隧道被释放以后移动节点 MN的 SMA即为 第二移动管理域的本地移动锚点 LMA, 所以当 MN移动到第三移动管理域时, 该移动节点 MN在第二移动管理域中的本地移动锚点 LMA作为该移动节点 MN的 SMA。 该实施例中移动节点 MN移动后, 建立移动节点 MN所属当前移 动管理域的本地移动锚点 LMA与该移动节点 MN的 SMA (即第二移动管理域 的本地移动锚点) 的双向隧道, 所述 MN的 SMA可以为该 MN所属前一移动管 理域的 LMA, 该前一移动管理域可以为家乡网络或拜访网络。
S609、 更新前一移动管理域 SMA的代理绑定关系, 将该移动节点 MN在 前一移动管理域的 SMA与该移动节点 MN当前所属移动管理域的 LMA绑定。
在本例中将所述移动节点 MN在第二移动管理域的 SMA与第三移动管理 域的本地移动锚点 LMA绑定。
S609、 该移动节点 MN在第二移动管理域的 SMA通过所述双向隧道转发 所述移动节点 MN发送和接收的数据。
当在移动的过程中 MN有业务进行时, 移动节点 MN与互联网络之间的路 由通过第二移动管理域的本地移动锚点 LMA到第三移动管理域的本地移动锚 点 LMA, 再到移动节点 MN。 当移动节点 MN移动到第三移动管理域后发起的 业务,移动节点 MN到互联网之间的路由为经过第三移动管理域的本地移动锚 点 LMA发送到互联网络。在 3GPP SAE标准下第三移动管理域中的本地移动锚 点 LMA为 PDN GW, 所以 MN数据通过 PDN GW直接发送到互联网络。
采用上述的切换方法, 切换流程与现有的流程相比作出了相应的改变, 下面对其进行详细的描述。
当移动节点 MN移动到新的移动管理域后当前移动管理域的目标业务网 关 , target Serving Gateway )将对应的请求消息 (例如: Create Bearer Request, 创建承载请求消息或 Proxy Binding Update, 代理绑定更新消息)发给当前移 动管理域的目标分组数据网关 ( Target PDN GW ) 。
如果消息里面包含切换标志位( Handover Indication ) , 新的移动管理域 中的分组数据网关将和策略和计费规则功能模块( PCRF Policy Charging Rules Function )执行获得分组数据网关的相关策略。 动节点 MN目前有正在进行的业务, 目标分组数据网关将向源分组数据网关 ( Source PDN GW )发起代理绑定更新消息。请求与 Source PDN GW之间建立 双向隧道, 该隧道为 PMIP隧道。 在操作中判断分组数据网关是否发生变化可 以通过对比目标分组数据网关与 Source PDN GW的地址实现, 或者其他的方 式。 通过验证后, Source PDN GW向目标分组数据网关回复请求消息 (例如 Proxy Binding Ack消息); 自此 Source PDN GW与 Target PDN GW之间建立了 一段双向隧道。
目标分组数据网关发送回复消息给目标业务网关, 该回复消息例如创建 载响应消息( Create Bearer Response ) ,或代理绑定应答消息( Proxy Binding Ack ) 。
通过上述的流程当处于漫游状态并采用 Local Breakout方案 (本地接入 / 出)的移动节点 MN再次移动时, 完成切换后。 漫游时正在进行的业务, 数据 包达到 Source PDN GW, 经由 Source PDN GW与 Target PDN GW的 PMIP隧道, 发向移动节点 MN。 而移动节点 MN切换后请求的新业务, 数据包则直接发到 Target PDN匪。
上述过程中 Source PDN GW认为是 MN在所属前一移动管理域中的 SMA, 该 Source PDN GW为 MN在所属前一移动管理域的 LMA; 目标分组数据网关为 当前移动管理域的 LMA ,该目标分组数据网关为当前移动管理域的 PDN GW , 并为 MN在当前移动管理域的 SMA。
上述的切换流程可应用于多种场景, 例如在 3GPP SAE架构下移动节点从 3GPP网络移动到另一 3GPP网络, 或者移动节点从 3GPP网络移动到非 3GPP网 络, 或者移动节点从非 3GPP网络移动到 3GPP网络。
在移动节点从 3GPP网络移动到另一 3GPP网络时,移动节点 MN位于 3GPP 网络 VPLMN 1 ,从 3GPP接入网接入,采用 Local Breakout形式进行业务交互。 移动节点 MN再次移动, 漫游到另一 3GPP网络 VPLMN 2。 漫游过程中有正在 进行的业务。或者 MN位于 3GPP网络 HPLMN1 ,漫游到另一 3GPP网络 VPLMN 2, 将采用基于 PMIPv6的 Local Breakout形式进行业务交互, 漫游过程中有正 在进行的业务; 切换中可采用上述流程, 当目标分组数据网关发送回复消息 给目标业务网关后继续切换流程。
当移动节点从 3GPP网络移动到非 3GPP网络时, MN位于 3GPP网络 VPLMN 1 , 从 3GPP接入网接入, 采用 Local Breakout形式进行业务交互。 移 动节点 MN再次移动, 切换到另一非 3GPP接入网。 此时, 需同时重新选择 Serving GW和 PDN GW (例如 , Inter-PLMN情况) , 漫游过程中有正在进行的业 务; 切换中可以采用上述流程, 当目标分组数据网关发送回复消息给目标业 务网关后继续切换流程。
当移动节点从非 3GPP网络移动到 3GPP网络时, MN位于非 3GPP接入网 , 采用 Local Breakout形式进行业务交互。 MN再次移动,切换到一 3GPP接入网。 此时, 需同时重新选择 Serving GW和 PDN GW (例如, Inter-PLMN情况)。 漫 游过程中有正在进行的业务; 切换中可以采用上述流程, 当目标分组数据网 关发送回复消息给目标业务网关后继续切换流程。
本实施例采用移动节点所属前一移动管理域的设备作为移动节点切换过 程中正在进行的业务中的锚点, 在移动节点当前所属移动管理域与前一移动 管理域之间引入域间信令, 建立双向隧道, 进行数据转发, 保证了业务的连 续性 , 解决 PMIPv6的域间切换问题。
为了便于实施上述实施提供的方法, 参阅图 8, 本发明实施例进一步提供 一种网络节点设备 800, 该设备包括:
连接建立模块 801 , 用于建立与移动节点之间的连接,
隧道建立模块 802,用于建立与所述移动节点的会话移动锚点之间的双向 隧道,
绑定更新模块 803 ,用于更新所述移动节点在其所属前一移动管理域的会 话移动锚点的代理绑定关系。
所述设备在网络中可以作为某一移动管理域的本地移动锚点, 当该设备 增加用于获得移动节点在网络中的签约信息以及业务相关信息的信息获得模 块 804后可以作为该移动节点的会话移动锚点设备。
采用本实施例的网络节点设备可以实现前述的方法, 采用移动节点所属 前一移动管理域的设备作为移动节点切换过程中正在进行的业务中的锚点, 在移动节点当前所属移动管理域与前一移动管理域之间引入域间信令, 建立 双向隧道, 进行数据转发, 保证了业务的连续性, 解决 PMIPv6的域间切换问 题。
显然, 本领域的技术人员应该明白, 上述的本发明的各单元或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 或 者将它们分别制作成各个集成电路模块, 或者将它们中的多个单元或步骤制 作成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软 件结合。
以上所述仅为本发明的较佳实施例而已, 并非用于限定本发明的保护范 围。 凡在本发明的精神和原则之内所作的任何修改、 等同替换、 改进等, 均 包含在本发明的保护范围内。

Claims

权利 要求 书
1、 一种实现移动管理域间切换的方法, 其特征在于, 包括:
将移动节点 MN初始附着的第一移动管理域的本地移动锚点 LMA1确定为 会话移动错点 SMA, 并建立移动节点 MN与所述 LMA1之间的第一连接; 建立所述移动节点 MN与第二移动管理域中的本地移动锚点 LMA2之间的 第二连接;
建立所述 LMA2与所述 SMA之间的双向隧道;
更新所述会话移动锚点 SMA的代理绑定关系, 通过所述 SMA采用所述双 向隧道转发所述 MN的数据。
2、 如权利要求 1所述的方法, 其特征在于,
所述 MN进入所述第二移动管理域时建立所述移动节点 MN与第二移动管 理域中的本地移动锚点 LMA2之间的第二连接。
3、 如权利要求 1所述的方法, 其特征在于, 建立所述 LMA2与所述 SMA 之间的双向隧道之前, 还包括:
所述第二移动管理域中的实体查询预先存储有会话移动锚点 SMA与移动节 点之间对应关系的数据库, 获取所述会话移动锚点 SMA的地址或标识信息,根 据所述 SMA的地址或标识信息定位 SMA。
4、 如权利要求 1所述的方法, 其特征在于, 建立所述 LMA2与所述 SMA 之间的双向隧道之前, 还包括:
所述第二移动管理域中的实体从所述 MN发送的消息或数据包中获取所述 会话移动锚点 SMA的地址或标识信息, 根据所述 SMA的地址或标识信息定位 SMA。
5、 如权利要求 4所述的方法, 其特征在于, 所述消息包括连接请求消息、 路由请求消息; 所述数据包括业务数据以及信令数据。
6、 如权利要求 1所述的方法, 其特征在于, 还包括:
当所述移动节点 MN进入所述第二移动管理域, 所述第二移动管理域中的 移动接入网关 MAG接收所述 MN发送的路由请求消息, 将当前网络配置信息 发送给所述 MN。
7、 如权利要求 1所述的方法, 其特征在于, 还包括:
所述更新 SMA的代理绑定关系之前, 所述 SMA接收所述第二移动管理域 中的实体发送的代理绑定更新确认消息;
更新所述 SMA的代理绑定关系之后, 所述 SMA发送代理绑定响应消息给 所述第二移动管理域中的实体。
8、 如权利要求 1所述的方法, 其特征在于, 还包括:
通过所述第二移动管理域中的实体在 MN与所述 SMA之间建立透明的双向 隧道。
9、 如权利要求 3、 4、 7或 8所述的方法, 其特征在于, 所述实体为移动接 入网关 MAG或本地移动错点 LMA装置。
10、 一种网络实体, 其特征在于, 包括:
接收单元, 用于接收 MN发送的代理绑定更新请求消息;
更新单元, 用于根据所述代理绑定更新请求执行代理绑定更新;
隧道建立单元, 用于建立与对端节点所属移动管理域中移动锚点之间的双 向! ¾道;
通信单元, 利用所述双向隧道所述将所述 MN发送给对端节点的数据转发 给另一移动管理域中移动锚点, 将来自对端节点的数据转发给所述 MN。
11、 如权利要求 10所述的网络实体, 其特征在于, 还包括:
管理单元, 用于为移动节点 MN分配家乡前缀, 并管理 MN的可达路由状 态。
12、 一种实现移动管理域间切换的方法, 其特征在于, 包括:
移动节点进入移动管理域后建立所述移动节点与当前所属移动管理域的本 地移动错点之间的连接;
建立当前所属移动管理域的移动锚点与该移动节点所属前一移动管理域的 移动锚点之间的双向隧道;
更新该移动节点在其所属前一移动管理域的移动会话锚点的代理绑定关 系;
处理对移动过程中进行的业务时利用所述双向隧道转发移动节点的数据。
13、 如权利要求 12所述的方法, 其特征在于, 处理移动节点进入新的移动 管理域后发起的业务时通过当前所属移动管理域的本地移动锚点转发移动节点 的数据。
14、 如权利要求 12所述的方法, 其特征在于, 所述方法还包括当移动节点 在移动过程中进行的业务完成后译放所述双向隧道。
15、 如权利要求 12所述的方法, 其特征在于, 建立所述移动节点与当前所 属移动管理域的本地移动锚点之间的连接后当前移动管理域中的本地移动锚点 获得移动节点的签约信息以及业务相关信息; 及
在建立当前所属移动管理域的移动锚点与该移动节点所属前一移动管理域 的移动锚点之间的双向隧道之后断开移动节点与所属前一移动管理域的本地移 动锚点的连接。
16、 如权利要求 12所述的方法, 其特征在于, 所述建立当前所属移动管理 域的移动锚点与该移动节点所属前一移动管理域的移动锚点之间的双向隧道的 步骤包括:
目标业务网关将对应的请求消息发给当前移动管理域的目标分组数据网 关;
目标分组数据网关将向源分组数据网关发送代理绑定更新消息;
移动节点及目标分组数据网关通过源分组数据网关的验证后目标业务网关 接收源分组数据网关发送的回复请求消息, 建立双向隧道。
17、 一种网络节点设备, 其特征在于, 该设备包括:
连接建立模块, 用于建立与移动节点之间的连接,
隧道建立模块,用于建立与所述移动节点的会话移动锚点之间的双向隧道, 绑定更新模块, 用于更新所述移动节点在其所属前一移动管理域的会话移 动锚点的代理绑定关系。
18、 如权利要求 6所述的设备, 其特征在于, 该设备还包括一用于获得移动 节点在网络中的签约信息以及业务相关信息的模块。
PCT/CN2009/072482 2008-07-04 2009-06-26 一种实现移动管理域间切换的方法及装置 WO2010000188A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200810133024.9 2008-07-04
CN200810133024 2008-07-04
CN200810166626A CN101621438A (zh) 2008-07-04 2008-10-13 一种实现移动管理域间切换的方法及装置
CN200810166626.4 2008-10-13

Publications (1)

Publication Number Publication Date
WO2010000188A1 true WO2010000188A1 (zh) 2010-01-07

Family

ID=41465497

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/072482 WO2010000188A1 (zh) 2008-07-04 2009-06-26 一种实现移动管理域间切换的方法及装置

Country Status (2)

Country Link
CN (1) CN101621438A (zh)
WO (1) WO2010000188A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113923593A (zh) * 2021-10-12 2022-01-11 南京信息工程大学 一种按需分布式边缘节点移动管理方法

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102958039B (zh) * 2011-08-24 2018-03-06 中兴通讯股份有限公司 一种代理移动ip域间节点通信系统及方法
WO2015109583A1 (zh) * 2014-01-26 2015-07-30 华为技术有限公司 一种数据包发送方法及移动路由器

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060692A (zh) * 2006-04-18 2007-10-24 华为技术有限公司 一种无线演进网络中的切换方法及系统
CN101175316A (zh) * 2006-10-30 2008-05-07 华为技术有限公司 跨本地移动管理域切换的方法及通信系统
WO2008071276A1 (en) * 2006-12-15 2008-06-19 Panasonic Corporation Local mobility anchor relocation and route optimization during handover of a mobile node to another network area

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101060692A (zh) * 2006-04-18 2007-10-24 华为技术有限公司 一种无线演进网络中的切换方法及系统
CN101175316A (zh) * 2006-10-30 2008-05-07 华为技术有限公司 跨本地移动管理域切换的方法及通信系统
WO2008071276A1 (en) * 2006-12-15 2008-06-19 Panasonic Corporation Local mobility anchor relocation and route optimization during handover of a mobile node to another network area

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113923593A (zh) * 2021-10-12 2022-01-11 南京信息工程大学 一种按需分布式边缘节点移动管理方法
CN113923593B (zh) * 2021-10-12 2023-10-27 南京信息工程大学 一种按需分布式边缘节点移动管理方法

Also Published As

Publication number Publication date
CN101621438A (zh) 2010-01-06

Similar Documents

Publication Publication Date Title
US8102815B2 (en) Proxy mobility optimization
US8503416B2 (en) Method and system for efficient homeless MPLS micro-mobility
WO2009152669A1 (zh) 网络切换实现方法及系统以及移动节点
JP2010512702A (ja) モバイル・ノードの他ネットワーク領域へのハンドオーバ時のローカル・モビリティ・アンカーのリロケーションおよびルート最適化
BRPI0617009A2 (pt) método executado por um agente doméstico, método para permitir o uso simultáneo de uma pluralidade de interfaces por um nó móvel multidoméstico, agente doméstico que serve um nó móvel multidoméstico, nó móvel multidoméstico para permitir o uso simultáneo de uma pluralidade de interfaces por um nó móvel multidoméstico, substituto de um nó móvel multidoméstico e mìdia que pode ser lida por computador
WO2010000174A1 (zh) 移动节点的注册、通信、切换方法及装置
US20110080872A1 (en) Distributed Local Mobility Anchors for Achieving Optimized Mobility Routing
KR20150074220A (ko) 고속 핸드오프 전이 동안 이동성 액세스 게이트웨이 간의 터널링을 위한 시스템 및 프로토콜들
KR101065958B1 (ko) 통신 시스템 및 통신 시스템의 통신 방법
KR20070002100A (ko) 인터넷 프로토콜 버전 6 서비스를 제공하기 위한 방법 및시스템
KR20110071772A (ko) 네트워크 기반 서비스 플로우 바인딩 방법
WO2009143723A1 (zh) 在不同域间切换时保持会话连续的方法、系统及节点
WO2010000188A1 (zh) 一种实现移动管理域间切换的方法及装置
US10986551B2 (en) Method for managing a low latency handover for mobile host seamless mobility
WO2013007133A1 (zh) 报文转发路径管理方法、系统及网元
CN105764041A (zh) 一种基于命名数据网络覆盖层的IPv6移动通信方法
KR100490130B1 (ko) 무선 이동통신 네트워크에서 에스아이피 프로토콜 및에스아이피 모빌리티 에이전트 수단을 이용한 이동성 관리방법 및 시스템
WO2013044688A1 (zh) 一种在pmip域间漫游时的节点通信方法及通信系统
WO2013064053A1 (zh) 一种流移动中的策略管理方法和系统
US20100135244A1 (en) REDUCTION OF HANDOVER DELAYS IN NESTED PROXY MOBILE IPv6/MOBILE IPv6 NETWORKS
KR101527611B1 (ko) 이종망 접속 방법
Kim et al. Network based global mobility management scheme in NGN
WO2014000175A1 (zh) 会话路由方法、设备及系统
Sugimoto et al. Network-Controlled Route Optimization for Heterogeneous Mobile IP Networks
WO2013044693A1 (zh) 一种在pmip域间漫游时的节点通信方法及通信系统

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09771958

Country of ref document: EP

Kind code of ref document: A1