WO2009143723A1

WO2009143723A1 - Method, system and node for keeping session continuity at the time of handover between different domains

Info

Publication number: WO2009143723A1
Application number: PCT/CN2009/071116
Authority: WO
Inventors: 严为; 颜小俊; 杨友庆
Original assignee: 华为技术有限公司
Priority date: 2008-05-27
Filing date: 2009-03-31
Publication date: 2009-12-03
Also published as: CN101594609A; CN101594609B

Abstract

A method, a system and a node for keeping session continuity at the time of handover between different domains are disclosed in the present invention which belongs to mobile communication field. The method includes that: a mobile node establishes a session connection with a correspondent node in the first mobile domain; and when the mobile node is handed over from the first mobile domain to the second mobile domain, the mobile node realizes the session with the correspondent node using the address information of an anchor device stored in the first mobile domain before the handover. The system includes a mobile node and an information storage device. The node includes an acquiring module and a session module. In the technical proposal supplied by the present invention, when the mobile node handed over from the first mobile domain to the second mobile domain, it is assured that the mobile node keeps the session with the correspondent node continuing without interruption when the mobile node is handed over between different domains by using the stored address information of an anchor device before the handover by the mobile node.

Description

Method, system and node for maintaining continuous session when switching between different domains This application claims to be submitted to the Chinese Patent Office on May 27, 2008, the application number is 200810097474.7, and the invention name is "the method of maintaining session continuity when switching between different domains" The priority of the Chinese Patent Application, the entire disclosure of which is incorporated herein by reference.

Say

Technical field

The present invention relates to the field of mobile communications, and in particular, to a method, system and node for maintaining a continuous session when switching between different domains.

Background technology

As a technology of network layer mobility management, mobile IP technology has the characteristics of being independent of the lower layer access protocol and physical transmission medium, and transparent to the upper layer protocol application. There are two main protocols for mobile IP: Mobile Internet Protocol version 6, (Mobile Internet Protocol version 6, ΜΙΡνό) and Proxy Mobile Internet Protocol version 6, (Prov. Mobile Internet Protocol version 6, ΡΜΙΡνό).

MIPv6 ensures that when the address of the mobile node (MN) changes, the MN and the Correspondent Node (CN) can still maintain normal communication, that is, the address change does not affect the upper layer communication.

ΜΙΡνό The solution to keep communication going through the network layer movement can be easily summarized into three points:

(1) defines the home address (HoA). The upper layer communication application uses HoA throughout, ensuring transparency to the application's movement;

(2) Defines a Care-of-Address (CoA). Obtaining CoA from the foreign network ensures communication is available in the existing routing mode;

(3) Establishing a mapping relationship between HoA and CoA, so that a relationship is established between the network layer identifier used by the upper layer application and the destination identifier used by the network layer route.

The specific workflow of MN and CN in the MIPv6 domain can be summarized as follows:

When the MN is in the home link, it communicates with the CN according to the traditional routing technology, and does not require the intervention of MIPv6. When the MN moves to the foreign link, the MN's home address remains unchanged, and a temporary IP address, CoA, is obtained. The MN informs the HA (Home Agent) through the Binding Update (BU) message through the mapping relationship between the HoA and the CoA. The communication between the MN and the CN still uses the home address of the MN, and the data packet is still sent to the MN. Home link; HA intercepts the "data packet, and forwards the data packet through the tunnel to the network where the MN's CoA is located according to the obtained mapping relationship.

As another communication method, the MN informs the CN of the mapping relationship between the HoA and the CoA. When the CN knows the CoA of the MN, it can directly forward the data packet to the foreign network segment where the CoA is located, so that the MN and the CN Normal communication can be performed directly. This communication process is also referred to as a route-optimized communication process.

The purpose of ΡΜΙΡνό is to provide a network-based mobility management protocol.无 There is no need to participate in any mobility management signaling in the PMIPv6 domain. The mobile entities in the network track the mobility of the , and initialize the mobile signaling and the routing state required to establish the communication.

The core functional entities in the ΡΜΙΡν6 domain are the Local Mobility Anchor (LMA) and the Mobile Access Gateway (MAG). The LMA is responsible for maintaining the reachability status of the MN and is topologically anchored to the MN's Home Network Prefix (HNP). The MAG is an entity that performs mobility management on behalf of the MN, is responsible for detecting the mobility of the MN on its access link, and sends a PBU message to the LMA of the MN.

When the MN enters the PMIPv6 domain, the MAG on the access link, after identifying the MN and obtaining its identity, will confirm whether the MN is authorized to the network mobility management service. If the system confirms that a network mobility management service needs to be provided to the MN, the system will ensure that the MN uses any of the address configuration mechanisms allowed by the network to enable the MN to obtain the address configuration on the interface and move anywhere in the PMIPv6 domain. The obtained address configuration includes the address from its HNP, the address of the default router on the link, and other related parameter configurations. From the perspective of the MN, the entire PMIPv6 domain can be regarded as a single link, and the system guarantees that the address configuration obtained by the MN does not change and is always considered to be on the same link.

If the MN is simultaneously connected to the PMIPv6 domain through multiple interfaces, the LMA will assign a unique HNP to each interface, so that the interface configures the home address according to the respective HNP. If the MN switches from one interface to another in the same PMIPv6 domain, the LMA will assign the same HNP to the new interface.

The LMA acts as a topological anchor for the MN and receives any packets sent to the MN. The LMA receives the destination address prefix as

After the HNP packet of the MN, the packet is forwarded to the MAG through the bidirectional tunnel. The MAG receives the encapsulated packet, removes the outer packet header, and forwards it to the MN on the access link.

As a default gateway on the access link, the MAG forwards the packet to the LMA through the bidirectional tunnel after receiving any packet sent to the CN. After receiving the encapsulated packet, the LMA releases the outer packet header and routes the packet to 0.

After the MN obtains the initial address configuration in the PMIPv6 domain, if the MN changes its access link, the MAG on the new access link will send signaling to the LMA for updating the binding and routing status. MN will continue to receive its corresponding HNP Router Advertisement (RA) message, which makes the MN believe that it is still on the same link, and that the MN uses the same address configuration on the new access link.

In practical applications, the following application scenarios are available:

When the MN is in the PMIPv6 domain, after the MN bootstraps, the MAG obtains the LMA address and the HNP of the MN through the corresponding path. The MN uses the HNP to configure the corresponding HoA and communicates with the CN. After the MN switches to the MIPv6 domain, the MN obtains the HA address through the relevant path. If the HA address is different from the previous LMA address, the MN will be assigned HNP1 different from the previous HNP, so that the MN will configure a new ΗοΑ1 according to the new HNP1. The CN that communicates with the MN in the PMIPv6 domain still uses the previous HoA of the MN as the destination address to send the message to the MN. However, the home address of the MN has changed to ΗοΑΙ, so the message sent by the CN will be lost, causing the session to be interrupted. . Conversely, similar problems occur when the MN moves from the MIPv6 domain to the PMIPv6 domain.

In summary, when the MN switches between the PMIPv6 domain and the MIPv6 domain, the session is interrupted due to the difference in the LM A address/H A address. Summary of the invention

In order to keep the session with the communication node uninterrupted when the mobile node switches between different domains, embodiments of the present invention provide a method, system, and node for maintaining a continuous session when switching between different domains. The technical solution is as follows:

A method for maintaining a session continuity when switching between different domains, the method comprising:

The mobile node establishes a session connection with the communication node in the first mobility domain;

When the mobile node switches from the first mobile domain to the second mobile domain, the session with the communication node is implemented by using the anchor device address information stored in the first mobile domain before the handover.

A mobile node, the mobile node comprising:

And an obtaining module, configured to acquire, when the mobile node switches from the first mobile domain to the second mobile domain, the anchor device address information saved in the first mobile domain before the handover;

a session module, configured to implement a session with the communication node in the second mobility domain by using the anchor device address information. A system for maintaining a continuous session, the system comprising:

Mobile node and information storage device;

The information storage device stores anchor device address information before the mobile node switches from the first mobile domain to the second mobile domain;

When the mobile node switches from the first mobile domain to the second mobile domain, the session with the communication node is implemented by using the anchor device address information saved by the information storage device.

The technical solution of the embodiment of the present invention moves when the mobile node performs handover in the first mobile domain and the second mobility domain. The node uses the anchor device address information stored in the first mobile domain before the handover to conduct a session with the communication node, and can ensure that the mobile node maintains the session with the communication node continuously without interruption when switching between different domains. DRAWINGS

1 is a schematic diagram of a method for maintaining a continuous session when a mobile node switches between different domains when the MN switches from the PMIPv6 domain to the MIPv6 domain according to Embodiment 1 of the present invention;

2 is a schematic diagram of a method for maintaining a continuous session when a mobile node switches between different domains when the MN switches from the MIPv6 domain to the PMIPv6 domain according to Embodiment 1 of the present invention;

FIG. 3 is a schematic diagram of another method for maintaining a continuous session when a mobile node switches between different domains when the MN switches from a PMIPv6 domain to a MIPv6 domain according to Embodiment 2 of the present invention; FIG.

4 is a schematic diagram of another method for maintaining a continuous session when a mobile node switches between different domains when the MN switches from the MIPv6 domain to the PMIPv6 domain according to Embodiment 2 of the present invention;

5 is a schematic diagram of another method for maintaining a continuous session of a mobile node when switching between different domains when the MN switches from the PMIPv6 domain to the MIPv6 domain according to Embodiment 3 of the present invention;

6 is a schematic structural diagram of a mobile node according to Embodiment 4 of the present invention;

FIG. 7 is a schematic structural diagram of a system for maintaining a continuous session according to Embodiment 4 of the present invention.

detailed description

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

Example 1

An embodiment of the present invention provides a method for maintaining a continuous session when a mobile node switches between different domains. The method saves an anchor device address information by using an Authentication, Authorization, and Accounting (AAA) server. When switching between the PMIPv6 domain and the MIPv6 domain, the MN performs a session with the communication node by using the anchor device address information saved by the AAA server before the handover, so that the normal session between the MN and the CN can be continuously interrupted. The anchor device refers to the LMA in the PMIPv6 domain and the HA in the MIPv6 domain. The AAA server can be called an information storage device. The following describes the application scenarios in which the MN switches from the PMIPv6 domain to the MIPv6 domain and the MN switches from the MIPv6 domain to the PMIPv6 domain.

As shown in FIG. 1 , the application scenario of the MN moving from the PMIPv6 domain to the MIPv6 domain is as follows: 101: The MN is connected to an access link of the PMIPv6 domain, and the MAG on the access link obtains the identifier of the MN, and sends a PBU message to the LMA, where the PBU message includes the MN related to the MAG address, the identifier of the MN, and the like. information.

102: The LMA receives the PBU message, allocates a unique HNP to the MN, and sends an access request message to the AAA server, requesting to verify whether the MAG is legally authorized, and the access request message includes the MAG address, the LMA address, and the HNP of the MN. , MN identification and other MN related information.

It should be noted that the bearer mode of the foregoing information depends on the specific form of the access request message, for example, by defining an AVP (Attribute Value Pair) attribute in the AAA message.

103: The AAA server receives the access request message, and verifies whether the MAG is legally authorized. If the MAG is legally authorized, the device returns an access reply message to the LMA, and saves the MAG address, the LMA address, and the MN in the access request message. MN related information such as HNP and MN identity.

The access response message includes information for verifying the legal authorization of the MAG.

104: The LMA receives the access response message, and sends a Proxy Banding Acknowledgement (PBA) message to the MAG according to the information in the access response message that is verified by the MAG legal authorization.

105: When the MN switches from the PMIPv6 domain to the MIPv6 domain, the access router of the MIPv6 domain (Access Router,

AR) The access authentication of the MN is completed through interaction with the AAA server. In the access authentication process of the MN, the AR obtains the LMA address information of the MN in the PMIPv6 domain and other MN related information from the AAA server.

Specifically, the AR sends an AAA request message to the AAA server, requesting to obtain the MN related information.

The AAA server receives the AAA request message, and sends the MN related information such as the LMA address information of the MN in the PMIPv6 domain to the AR in the AAA response message.

The AR obtains the MN related information, such as the LMA address information of the MN in the PMIPv6 domain, from the received AAA response message, and sends an RA message to the MN, where the RA message includes the foreign link prefix information.

106: The MN configures the CoA according to the foreign link prefix information in the RA message, and sends a Dynamic Host Configuration Protocol (DHCP) Request message to the AR, requesting to obtain related information of the MN, including obtaining the LMA address. HNP and other information.

107: After receiving the DHCP Request message, the AR adds a relay option to the DHCP Request message if the AR is a DHCP relay. The relay option carries the LMA address information obtained from the AAA server and carries the LMA. The DHCP Request message of the address information is sent to the DHCP server, and then the 108-110 is executed; if the AR is a DHCP proxy, the DHCP reply message is directly returned to the MN, and the DHCP reply message carries the MN obtained from the AAA server in the PMIPv6 domain. The LMA address information, the MN uses the LMA address information obtained from the DHCP reply message to conduct a session with the CN. 108: After receiving the DHCP Request message, the DHCP server returns a DHCP reply message to the AR, where the DHCP reply message carries the LMA address information of the MN in the PMIPv6 domain obtained from the AR.

109: The AR relays a DHCP Reply message to the MN.

The MN receives the DHCP Reply message, obtains the LMA address information in the PMIPv6 domain, and establishes a tunnel with the LMA by using the obtained LMA address information, and implements a session with the CN through the tunnel.

It should be noted that, in the MIPv6 domain, after the MN obtains the address information of the LMA, the MN considers the address as the address of the home agent, and uses the address to establish a tunnel with the LMA.

As shown in FIG. 2, the application scenario of the MN moving from the MIPv6 domain to the PMIPv6 domain is as follows:

201: The MN completes the access authentication in the MIPv6 domain, and obtains the HA address in the bootstrap process through related channels.

The MN obtains the HA address in the bootstrap process is a prior art and will not be described again.

202: The MN sends a BU message to the HA, where the BU message includes information such as the MN's CoA, Ho A, and MN identity.

203: The HA receives the BU message, allocates a unique HNP to the MN, and sends an access request message to the AAA server, where the access request message includes the MN related information such as the HA address and the identifier of the MN.

204: The AAA server receives the access request message, returns an access response message to the HA, and saves the HA address in the access request message and related information of other MNs.

205: The HA receives the access response message, and sends a Binding Acknowledgement (BA) message to the MN.

206: When the MN is switched from the MIPv6 domain to the PMIPv6 domain, the MAG obtains the identity of the MN in the MN access authentication process, and sends an AAA request message to the AAA server to obtain the HA address information of the MN in the MIPv6 domain.

207: The AAA server receives the AAA request message, and sends the HA address information of the MN in the MIPv6 domain to the MAG in the AAA response message.

208: The MAG receives the AAA response message, obtains the HA address information of the MN in the MIPv6 domain, and establishes a tunnel between the obtained HA address information and the HA.

It should be noted that, in the PMIPv6 domain, after the MAG obtains the address information of the HA, the MAG considers the address as the address of the local mobility anchor, and uses the address to establish a tunnel with the LMA.

209: The MN uses the tunnel established between the MAG and the HA to conduct a session with the CN.

In the embodiment of the present invention, the anchor device address information is saved by the AAA server. When the MN switches between the PMIPv6 domain and the MIPv6 domain, the MN performs a session with the CN by using the anchor device address information saved on the AAA server before the handover. Thereby, it is possible to ensure that the session between the MN and the CN is continuously uninterrupted. Example 2

Different from the embodiment 1, in this embodiment, the anchor device address information is saved by using another information storage device. When the MN switches between the PMIPv6 domain and the MIPv6 domain, the MN uses the anchor device address information saved by the information storage device. CN conducts a conversation. In this embodiment, other information storage devices use a domain name server (DNS) as an example, but the actual application is not limited to DNS. The anchor device refers to the LMA in the PMIPv6 domain and the HA in the MIPv6 domain. The following describes the application scenarios in which the MN switches from the PMIPv6 domain to the MIPv6 domain and the MN switches from the MIPv6 domain to the ΡΜΙΡνό domain.

As shown in FIG. 3, the application scenario of the method for moving from the PMIPv6 domain to the MIPv6 domain is as follows:

301: The MN completes access authentication in the PMIPv6 domain.

302: The MAG sends a PBU message to the LMA, requesting registration for the MN.

303: The LMA receives the PBU message, and if the MN is successfully registered, sends a DNS update request message to the DNS, where the DNS update request message carries the MN related information such as the LMA address of the MN, the home network prefix, the MN identity, and the multi-interface information.

The specific update request message depends on the selection of the specific information storage network element. Since the DNS is used as the information storage device in this embodiment, the format of the update request message conforms to the standard of the DNS message format.

304: The DNS receives the DNS update request message, and saves the MN related information such as the LMA address, the home network prefix, the MN identity, and the multi-interface information in the DNS update request message, and returns an update response message to the LMA.

305: After receiving the update response message, the LMA sends a PBA message to the MAG.

306: When the MN switches from the PMIPv6 domain to the MIPv6 domain, send a DNS request message to the DNS to request information about the MN.

307: The DNS receives the DNS request message, and sends the LMA address information of the MN stored in the PMIPv6 domain to the MN.

308: The MN receives the DNS response message, obtains the LMA address information of the MN in the PMIPv6 domain, and establishes a tunnel with the LMA by using the obtained LMA address information, and implements a session with the CN through the tunnel.

It should be noted that, in the MIPv6 domain, after the MN obtains the address information of the LMA, the MN considers the address as the address of the home agent, and uses the address to establish a tunnel with the LMA. As shown in FIG. 4, the application scenario of the MN moving from the MIPv6 domain to the PMHV6 is as follows:

401: The MN completes the access authentication in the MIPv6 domain. 402: The MN sends a BU message to the HA requesting registration.

403: After receiving the BU message, the HA sends a BA message to the MN if the MN is successfully registered, and sends a DNS update request message to the DNS, where the DNS update request message carries the HA address of the MN, the home network prefix, and the MN. MN related information such as identification and multi-interface information.

The specific content is similar to the above 303, and will not be described again.

404: The DNS receives the DNS update request message, saves the MN related information such as the HA address, the home network prefix, the MN identifier, and the multi-interface information of the MN in the DNS update request message, and returns a DNS update response message to the HA, indicating that the update is successful. .

405: The HA receives the DNS update response message and sends a BA message to the MN.

406: When the MN switches from the MIPv6 domain to the PMIPv6 domain, initiate an access authentication request to the MAG, where the access authentication request includes the MN related information such as the identifier of the MN.

407: After obtaining the identifier of the MN, the MAG sends a DNS request message to the DNS, requesting to obtain information about the MN.

408: The DNS receives the DNS request message, and sends the HA address information of the MN in the MIPv6 domain to the MAG in the DNS response message.

409: The MAG receives the DNS response message, obtains the HA address information of the MN in the MIPv6 domain, and uses the obtained

A tunnel is established between the HA address information and the HA.

410: The MN uses the tunnel established between the MAG and the HA to talk to the CN.

In the embodiment of the present invention, the anchor device address information is saved by the domain name server DNS. When the MN switches between the PMIPv6 domain and the MIPv6 domain, the MN uses the pre-switch domain name server DNS to save the anchor device address information to perform a session with the CN. Thus, it can be ensured that the session between the MN and the CN is continuously uninterrupted.

Example 3

Different from the first embodiment, in this embodiment, the MMA stores the LMA address information of the MN in the PMIPv6 domain by using the MAG. When the MN moves from the PMIPv6 domain to the MIPv6 domain, the AR obtains and saves the LMA address information of the MN in the PMIPv6 domain from the MAG. And providing the MMA address information of the MN in the PMIPv6 domain to the MAG, the MAG uses the LMA address information to establish a tunnel with the HA, and the MN uses the tunnel between the MAG and the HA to conduct a session with the CN, thereby ensuring that the session between the MN and the CN is continuous. Interrupt, where the MAG can be referred to as other information storage devices. As shown in FIG. 5, the details of this embodiment are as follows: 501: When the MN is in the PMIPv6 domain, the MAG obtains and saves the LMA address through the related path.

The process of obtaining the LMA address by the MAG through related channels is not described in the prior art.

502: When the MN switches from the PMIPv6 domain to the MIPv6 domain, the context between the AR and the MAG in the PMIPv6 domain is requested. The seek/response message acquires and saves the LMA address and other MN related information.

Specifically, the methods for the AR to obtain the LMA address and other MN related information are as follows:

First, the AR sends a context request message to the MAG, requesting to acquire the LMA address information and other MN related information. After receiving the context request message, the MAG sends the LMA address and other MN related information carrying the context response message to the AR. The AR receives the context response. The message, and save the LMA address information and other MN related information in the context response message.

Second, the MAG directly informs the AR by transmitting the LMA address information and other MN related information by carrying the message in the context; the AR acquires and saves the LMA address and other MN related information.

503: The MN completes access authentication in the MIPv6 domain.

504: The MN obtains the CoA of the MIPv6 domain on the access link, and sends a DHCP Request message to the AR, requesting to obtain the MN related information, including the LMA address, HNP, and the like.

505: After receiving the DHCP Request message, the AR adds a relay option to the DHCP Request message if the AR is a DHCP relay. The relay option carries the obtained LMA address information and carries the LMA address information. The DHCP Request message is sent to the DHCP server, and 506-508 is performed; if the AR is a DHCP proxy, the DHCP reply message is directly sent to the MN, where the DHCP reply message carries the LMA address information, and the MN obtains the PMIPv6 domain. LMA address information, and use the acquired LMA address information to talk with the CN.

506: After receiving the DHCP Request message, the DHCP server returns a DHCP reply message to the AR, where the DHCP reply carries the LMA address information obtained from the AR.

507: The AR relays a DHCP Reply message to the MN.

508: The MN receives the DHCP Reply message, obtains the LMA address information of the PMIPv6 domain, and establishes a tunnel with the LMA by using the obtained LMA address information, and performs a normal session with the CN through the tunnel.

In the embodiment of the present invention, the MAG of the PMIPv6 domain saves the LMA address information of the MN in the PMIPv6 domain, when

When the MN switches from the PMIPv6 domain to the MIPv6 domain, the AR of the MIPv6 domain obtains and saves the LMA address information of the MN in the PMIPv6 domain from the MAG, and provides the LM address information of the MN in the PMIPv6 domain to the MN, and the MN uses the LMA address information and the HA. (LMA of the SPPMIPv6 domain) Establishes a tunnel, and the MN uses the tunnel to conduct a session with the CN, thereby ensuring continuous uninterrupted sessions between the MN and the CN.

Example 4

The embodiment of the invention provides a mobile node, and the specific function description of the mobile node is as follows: A mobile domain establishes a session connection with a communication node.

When the mobile node switches from the first mobile domain to the second mobile domain, the session with the communication node is implemented using the anchor device address information saved in the first mobile domain before the handover.

Wherein, the situation of implementing the session with the communication node by using the anchor device address information saved in the first mobile domain before the handover can be divided into two types:

First, the mobile node establishes a tunnel with the anchor device by using the anchor device address information, and uses the tunnel to implement a session with the communication node in the second mobile domain.

Second, the mobile node implements a session with the communication node in the second mobile domain by using a tunnel established between the mobile access gateway MAG and the anchor device, and the tunnel uses the anchor point saved from the first mobile domain by the mobile access gateway MAG. Device address information is established between anchor devices.

It should be noted that the first mobility domain is a PMIPv6 domain, and the second mobility domain is a MIPv6 domain; or the first mobility domain is a MIPv6 domain, and the second mobility domain is a PMIPv6 domain.

As shown in Figure 6, a typical mobile node includes:

The obtaining module 601 is configured to: when the mobile node switches from the first mobile domain to the second mobile domain, obtain the anchor device address information saved in the first mobile domain before the handover; where, how to obtain the first mobile domain before saving For the anchor device address information, refer to the corresponding description of the method embodiment, and details are not described herein again.

The session module 602 is configured to establish a tunnel with the anchor device by using the obtained anchor device address information, and implement a session with the communication node in the second mobility domain by using the established tunnel.

For the process of establishing a tunnel between the obtained anchor device address information and the anchor device, and implementing the session with the communication node in the second mobile domain by using the established tunnel, refer to the corresponding description of the method embodiment, and no longer Narration.

The session module 602 includes:

a tunnel establishment sub-module 6021, configured to establish a tunnel with the anchor device by using the anchor device address information;

The session sub-module 6022 is configured to implement a session with the communication node in the second mobility domain by using the established tunnel.

In the embodiment of the present invention, when the mobile node switches from the first mobile domain to the second mobile domain, the mobile node performs a session with the communication node by using the anchor device address information saved before the handover, and can ensure that the mobile node switches between different domains. The session with the communication node is kept uninterrupted. An embodiment of the present invention provides a system for maintaining a continuous session. As shown in FIG. 7, the system includes:

Mobile node 701 and information storage device 702;

The information storage device 702 is configured to save anchor device address information before the mobile node 701 switches from the first mobile domain to the second mobile domain; The mobile node 701 is configured to implement, in the second mobile domain, the anchor device address information saved on the information information storage device 702 of the first mobile domain before the handover, when the mobile node is switched from the first mobile domain to the second mobile domain. The session of the node.

The information storage device 702 is an AAA server or a mobile access gateway MAG, and the AAA server or the mobile access gateway MAG saves the anchor before the mobile node 701 switches from the PMIPv6 domain as the first mobile domain to the MIPv6 domain in the second mobility domain. Point device address information; correspondingly, the mobile node 701 is specifically configured to switch from the ΡΜΙΡνό domain as the first mobile domain to the ΜΙΡν6 domain as the second mobility domain, and obtain the PMIPv6 domain before the handover by using the access router AR of the MIPv6 domain. The anchor device address information stored on the AAA server or the mobile access gateway MAG establishes a tunnel with the anchor device by using the anchor device address information, and uses the tunnel to implement a session with the communication node in the MIPv6 domain.

The information storage device 702 is a domain name server DNS, and the domain name server DNS saves the anchor device address information before the mobile node 701 switches from the PMIPv6 domain as the first mobile domain to the MIPv6 domain in the second mobility domain; correspondingly, the mobile node 701. Specifically, when switching from a PMIPv6 domain that is the first mobile domain to a MIPv6 domain that is the second mobility domain, obtain, from the domain name server DNS, the anchor device address information saved in the PMIPv6 domain before the handover, and use the anchor device address. The information establishes a tunnel with the anchor device, and uses the tunnel to implement a session with the communication node in the MIPv6 domain.

When the information storage device 702 is an AAA server or a domain name server DNS, the AAA server or the domain name server DNS saves the anchor device address before the mobile node 701 switches from the MIPv6 domain as the first mobile domain to the PMIPv6 domain in the second mobility domain. Correspondingly, the mobile node 701 is specifically configured to implement a session with the communication node in the PMIPv6 domain by using a tunnel between the mobile access gateway MAG and the anchor device, and the tunnel is utilized by the mobile access gateway MAG from the AAA server or the domain name server. The anchor device address information obtained on the DNS is established between the anchor devices.

In the embodiment of the present invention, when the mobile node switches from the first mobile domain to the second mobile domain, the mobile node performs a session with the communication node by using the anchor device address information saved before the handover, and can ensure that the mobile node switches between different domains. The session with the communication node is kept uninterrupted.

The technical solution provided by the above embodiments can be implemented by hardware and software, and the software is stored on a readable storage medium, such as a floppy disk, a hard disk or an optical disk of a computer.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., which are within the spirit and scope of the present invention, should be included in the protection of the present invention. Within the scope.

Claims

Claim

A method for maintaining a continuation of a session when switching between different domains, the method comprising: the mobile node establishing a session connection with the communication node in the first mobility domain;

When the mobile node switches from the first mobility domain to the second mobility domain, the session with the communication node is implemented by using the anchor device address information stored in the first mobility domain before the handover.

2. The method of maintaining a continuation of a session when switching between different domains according to claim 1, wherein the first mobile domain is a PMIPv6 domain, and the second mobility domain is an MIPv6 domain; or

The first mobile domain is a MIPv6 domain, and the second mobility domain is a PMIPv6 domain.

3. The method of maintaining a continuation of a session when switching between different domains according to claim 2, wherein when the mobile node switches from the first mobile domain to the second mobile domain, The implementation of the session device address information of the first mobile domain to implement the session with the communication node specifically includes:

The mobile node switches from a PMIPv6 domain as the first mobility domain to a second mobility domain

ΜΙΡνό domain, obtaining anchor device address information saved in the PMIPv6 domain before switching;

The mobile node establishes a tunnel with the anchor device by using the anchor device address information, and implements a session with the communication node in the MIPv6 domain by using the tunnel.

4. The method of maintaining a continuation of a session when switching between different domains according to claim 3, wherein the mobile node switches from a PMIPv6 domain that is the first mobility domain to a second mobility domain. In the ΜΙΡνό domain, obtaining the anchor device address information stored in the PMIPv6 domain before the handover specifically includes:

And the mobile node obtains, by using the access router AR of the MIPv6 domain, the anchor device address information saved in the PMIPv6 domain before the handover from the AAA server; or

The mobile node obtains, by using the access router AR of the MIPv6 domain, the anchor device address information in the PMIPv6 domain before the handover from the mobile access gateway MAG of the PMIPv6 domain.

5. The method for maintaining session continuity when switching between different domains according to claim 2, wherein the mobile node switches from a PMIPv6 domain that is the first mobility domain to a second mobility domain. In the ΜΙΡνό domain, obtaining the anchor device address information stored in the PMIPv6 domain before the handover specifically includes:

The mobile node obtains anchor device address information in the PMIPv6 domain before the handover from the domain name server DNS.

6. The method of maintaining a continuation of a session when switching between different domains according to claim 2, wherein the mobile node switches from a MIPv6 domain that is the first mobility domain to a second mobility domain. When the ΡΜΙΡνό domain is used, the implementation of the session with the communication node by using the anchor device address information stored in the first mobile domain before the handover specifically includes:

The mobile node implements a session with the communication node by using a tunnel between the mobile access gateway MAG of the PMIPv6 domain and the anchor device, and the tunnel is utilized by the mobile access gateway MAG of the PMIPv6 domain. The anchor device address information is established between the anchor devices.

7. A mobile node, wherein the mobile node comprises:

An obtaining module (601), configured to: when the mobile node switches from the first mobile domain to the second mobile domain, acquire anchor point device address information saved in the first mobile domain before switching;

The session module (602) is configured to implement a session with the communication node in the second mobility domain by using the anchor device address information.

The mobile node according to claim 7, wherein the session module comprises:

a tunnel establishment sub-module (6021), configured to establish a tunnel with the anchor device by using the anchor device address information, and a session sub-module (6022), configured to implement, by using the tunnel, the communication in the second mobility domain The session of the node.

9. A system for maintaining a continuous session, wherein the system comprises:

a mobile node (701) and an information storage device (702);

The information storage device (702) is configured to store anchor device address information before the mobile node switches from the first mobile domain to the second mobile domain;

The mobile node (701) is configured to implement a session with the communication node by using the anchor device address information saved by the information storage device (702) when switching from the first mobile domain to the second mobility domain.

The system for maintaining session continuity according to claim 9, wherein the information storage device (702) is an AAA server or a mobile access gateway MAG, and the AAA server or the mobile access gateway MAG saves the The mobile node (701) from the PMIPv6 domain as the first mobility domain to the anchor device address information before the handover as the MIPv6 domain of the second mobility domain;

Correspondingly, the mobile node (701) is specifically configured to switch from the PMIPv6 domain as the first mobile domain to When the MIPv6 domain is the MIPv6 domain of the second mobility domain, obtain the anchor point saved on the AAA server or the mobile access gateway MAG in the ΡΜΙΡνό domain before the handover by using the access router AR of the MIPv6 domain. Device address information, establishing a tunnel with the anchor device by using the anchor device address information, and implementing a session with the communication node in the MIPv6 domain by using the tunnel.

11. The system for maintaining session continuity according to claim 9, wherein said information storage device (702) is a domain name server DNS, and said domain name server DNS holds said mobile node (701) from said An anchor device address information of a mobile domain's PMIPv6 domain before being switched to the MIPv6 domain as the second mobility domain;

Correspondingly, the mobile node (701) is specifically configured to: before switching from a PMIPv6 domain that is the first mobility domain to a MIPv6 domain that is the second mobility domain, obtain a pre-switching location from the domain name server DNS. The anchor device address information saved in the PMIPv6 domain is used to establish a tunnel with the anchor device by using the anchor device address information, and the session with the communication node is implemented in the MIPv6 domain by using the tunnel.

12. The system for maintaining a continuous session during inter-domain handover according to claim 9, wherein the information storage device (702) is an AAA server or a domain name server DNS, and the AAA server or domain name server DNS saves the The mobile node (701) transmits anchor point device address information from the MIPv6 domain as the first mobile domain to the PMIPv6 domain as the second mobility domain;

Correspondingly, the mobile node (701) is specifically configured to implement a session with the communication node in the PMIPv6 domain by using a tunnel between the mobile access gateway MAG and an anchor device, where the tunnel is The mobile access gateway MAG establishes between the anchor devices using the anchor device address information obtained from the AAA server or the domain name server DNS.