WO2013044694A1

WO2013044694A1 - Communication method and communication system for node roaming between pmip domains

Info

Publication number: WO2013044694A1
Application number: PCT/CN2012/080014
Authority: WO
Inventors: 涂杨巍; 霍玉臻; 沈岷; 江鸿; 王志海
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-09-29
Filing date: 2012-08-13
Publication date: 2013-04-04
Also published as: CN103037350B; CN103037350A

Abstract

A communication method and a communication system for a node roaming between PMIP domains. The method comprises: after a terminal node MN roams from a home PMIP domain that supports routing optimization to a visiting PMIP domain that supports routing optimization, the visiting PMIP domain allocating a roaming identification indicating position information of the MN in the visiting PMIP domain to the MN, binding the roaming identification to a home network prefix of the MN, and further notifying the home PMIP domain of the roaming identification; the home PMIP domain binding the home network prefix of the MN to the roaming identification; when an initial data packet is transmitted from a peer node to the MN, the home PMIP domain searching for the roaming identification according to the home network prefix of the MN, and a PMIP domain where the peer node is located sending, according to the roaming identification, the initial data packet to the visiting PMIP domain with an interworking gateway in the visiting PMIP domain as a destination network element. The scheme provides a solution to communication when a node roams between PMIP domains.

Description

Node communication method and communication system when roaming between PMIP domains

Technical field

The present invention relates to the field of communications, and in particular, to a node communication method and a communication system when roaming between PMIP domains.

Background technique

The Transmission Control Protocol/Internet Protocol (TCP/IP) does not consider the topology change of the terminal in the initial design. That is, the TCP/IP protocol itself does not support mobility. In the traditional TCP/IP network environment, IP provides routing for the Internet. It assigns logical addresses, ie IP addresses, to all nodes (including hosts and routers), and each port of each host is assigned. An IP address. The IP address includes the network prefix and the host part. The IP addresses of all hosts on the same link usually have the same network prefix and different host parts. This allows IP to be routed based on the network prefix portion of the destination node's IP address, allowing the router to maintain a simple network prefix route without having to maintain a separate route for each host. In this case, since the network prefix route is used, when the node switches from one link to another without changing its IP address, the node cannot receive the data packet on the new link. Therefore, it is impossible to communicate with other nodes.

As users' demand for mobility and information rises sharply, more and more people want to access the Internet at high speed during the mobile process, get much-needed information, and do what they want. Therefore, the mobile Internet has become the development direction of the future Internet, but the traditional TCP/IP protocol does not support the defect of mobility, making the mobility management of the terminal node a major problem facing the mobile Internet.

In order to solve the mobility management problem, the industry's more popular mobility management technologies, such as Mobile IP (MIP) and Proxy MIP (PMIP), are introduced by means of a fixed anchor (Anchor). Support terminal mobility. For example, the MIP protocol uses a Home Agent (HA) as an anchor point, and the PMIP protocol uses a Local Mobility Anchor (LMA) as a point of error. Figure 1 shows the logical architecture of the PMIP protocol, including the Mobile Node (MN), the Correspondent Node (CN), the Mobile Access Gateway (MAG), and the Local Mobility Anchor (Local). Mobility Anchor, LMA). The CN can be a fixed node or a mobile node, that is, it has a corresponding MAG and LMA. The MAG is the first hop router of the MN, and its main functions include assigning a Care of Address (CoA) to the MN when accessing it, and performing PMIP Binding (MMIP Binding) with the MN's anchor LMA instead of the MN. . As the anchor of the MN, the LMA's main functions include assigning the Home of Address (HoA) to the MN and processing the above PMIP binding. The main purpose of the PMIP binding performed between the MAG and the LMA is to let both parties know the address of the other party, namely the above CoA and HoA, and save the binding relationship locally. In addition, in the process of performing PMIP binding, a bidirectional tunnel is established between the MAG and the LMA for the MN. It is worth noting that the IP address finally obtained by the MN is the HoA assigned by the LMA. In a typical network deployment, the MAG is generally located at a lower topology, such as at the edge of a metropolitan area network; and the LMA is generally located at a higher topology, such as the core of the provincial backbone. The MAG and the LMA are often connected by a multi-hop router.

In order to optimize the path of the data packet transmission, when the terminal node and the peer node are both in the same PMIP domain, the terminal node or the peer node can obtain the current end of the other end from the other network element by using the local MAG. Serving the MAG, thus establishing a direct link between the two MAGs without rerouting the packets to the LMA, greatly reducing the routing problem. In order to distinguish from the traditional PMIP domain, the above domain is called a PMIP domain that supports route optimization.

The system architecture of the PMIP inter-domain node roaming is shown in Figure 2. The PMIP domain can be divided into a PMIP domain that supports route optimization and a PMIP domain that does not support route optimization, that is, a traditional PMIP domain. For the PMIP domain that supports route optimization, in addition to the traditional network element MAG, it includes a mapping server (MAPS), which mainly performs node location management and address mapping relationship maintenance. It also includes one or more Interworking Gateway (JGW) for interworking with other PMIP domains. Its main functions include signaling interaction with other PMIP domains that support route optimization. It is also the PMIP domain and other PMIPs. For the data export between domains, in the specific implementation, multiple interworking gateways can be set at the boundary of the domain. For the target node in different domains, different interworking gateways are selected according to the route optimization principle. In addition, the interworking gateway can be combined with a border router or a separate device. In order to ensure that the data packets of the outer domain can reach the interworking gateway, interworking The gateway needs to broadcast the HoA/home network prefix to which it belongs.

The current PMIP network architecture is based on the movement of the terminal node under the same local mobility anchor in the same PMIP domain, and the method of the terminal roaming from one PMIP domain to another PMIP domain has not been defined, especially the terminal is supporting A route optimization method for roaming between route-optimized PMIP domains.

Summary of the invention

The technical problem to be solved by the present invention is to provide a node communication method and a communication system when roaming between PMIP domains, and to solve communication problems when nodes roam between PMIP domains.

In order to solve the above technical problem, the present invention provides a node communication method when roaming between PMIP domains, wherein the visited PMIP is accessed after the terminal node roams from a home PMIP domain supporting route optimization to a visited PMIP domain supporting route optimization. The domain assigns, to the terminal node, a roaming identifier indicating location information of the terminal node in the visited PMIP domain, and binds the roaming identifier to a home network prefix of the terminal node, and notifies the roaming identifier to the terminal The home PMIP domain is bound to the home network prefix of the terminal node and the roaming identifier; in the first data packet transmission process of the peer node to the terminal node, the home PMIP domain Querying the roaming identifier according to the home network prefix of the terminal node, the PMIP domain to which the peer node belongs sends the first data packet according to the roaming identifier in the visited PMIP domain interworking gateway as a destination network element. Go to the visited PMIP domain.

Preferably, the foregoing method may further have the following features: after the terminal node roams from the home PMIP domain that supports route optimization to the visited PMIP domain that supports route optimization, the mobile access gateway to which the terminal node belongs sends a proxy binding update to the mapping server. And the mapping server sends the roaming identifier to the interworking gateway to which the terminal node belongs, directly or via the mobile access gateway, and the interworking gateway notifies the roaming identifier to the home PMIP domain.

Preferably, the foregoing method may further have the following feature: the mapping server of the visited PMIP domain binds the home network prefix of the terminal node and the roaming identifier;

When the peer node is located in the visited PMIP domain, the peer node sends the first data packet to the terminal node, and the mobile access gateway to which the opposite node belongs uses the home of the terminal node. The home network prefix queries the mapping server for the information of the mobile access gateway to which the terminal node belongs, and the mapping server that visits the PMIP domain queries the roaming identifier according to the home network prefix, and implements the opposite to the opposite end in the visited PMIP domain. The data of the node is sent.

Preferably, the foregoing method may further have the following feature: when the peer node is located in the visited PMIP domain, the terminal node sends the first data packet to the peer node, and the terminal node sends the visited PMIP domain to the visited PMIP domain. The mobile access gateway sends a first data packet, and the mobile access gateway queries the mapping server of the visited PMIP domain to query the location information of the opposite node, and sends the first data packet to the mobile access gateway to which the opposite node belongs. To the opposite node.

Preferably, the above method may also have the following features:

When the peer node is located in the PMIP domain outside the visited PMIP domain, the terminal node sends the first packet to the mobile access gateway of the visited PMIP domain during the process of sending the first data packet to the peer node. a data packet, the mobile access gateway queries the mapping server of the visited PMIP domain to query the location information of the opposite node, and after receiving the inter-domain communication indication sent by the mapping server, sending the first data packet to the peer end The PMIP domain to which the node belongs.

Preferably, the foregoing method may further have the following feature: the peer node is located in the attribution

In the PMIP domain, after receiving the first data packet sent by the opposite node to the terminal node, the mobile access gateway of the home PMIP domain uses the home network prefix of the terminal node to map to the home PMIP domain. When the server queries the location information of the terminal node, the roaming identifier is obtained, and the network element that sends the interworking gateway in the visited PMIP domain according to the roaming identifier sends the first data packet via the interworking gateway of the home PMIP domain. Accessing the interworking gateway in the PMIP domain, the interworking gateway in the visited PMIP domain queries the location information of the terminal node from the visited PMIP domain mapping server according to the home network prefix and/or the roaming identifier. Sending the first data packet to the terminal node via a mobile access gateway to which the terminal node belongs.

Preferably, the above method may also have the following features:

When the peer node is located in the PMIP domain that supports the route optimization other than the home PMIP domain and the visited PMIP domain, the interworking gateway of the home PMIP domain receives the interworking gateway of the PMIP domain to which the peer node belongs. After the first node sends the first data packet to the terminal node, the home network prefix of the terminal node is used to query the mapping server of the home PMIP domain to query the location information of the terminal node, and the roaming identifier is obtained. According to the roaming identifier, the visited PMIP The interworking gateway in the domain sends the first data packet to the interworking gateway in the visited PMIP domain via the interworking gateway of the home PMIP domain, and the interworking gateway in the visited PMIP domain is based on the home network prefix and/or After the roaming identifier queries the location information of the terminal node from the visited PMIP domain mapping server, the first data packet is sent to the terminal node via a mobile access gateway to which the terminal node belongs.

Preferably, the foregoing method may further have the following feature: when the peer node is located in the PMIP domain that supports the route optimization except the home PMIP domain and the visited PMIP domain, the PMIP domain to which the peer node belongs After receiving the first data packet sent by the opposite end node to the terminal node, the gateway uses the home network prefix of the terminal node to query the mapping server of the home PMIP domain via the interworking gateway of the home PMIP domain. The location information of the terminal node is used to learn the roaming identifier, and the interworking gateway of the PMIP domain to which the peer node belongs sends the first data packet to the interworking gateway in the visited PMIP domain according to the roaming identifier, the visited PMIP After the interworking gateway in the domain queries the location information of the terminal node from the visited PMIP domain mapping server according to the home network prefix and/or the roaming identifier, the mobile access gateway to which the terminal node belongs The first data packet is sent to the terminal node.

Preferably, the foregoing method may further have the following feature: after the interworking gateway of the home PMIP domain queries the mapping server of the home PMIP domain to query the location information of the terminal node, after obtaining the roaming identifier, notifying the roaming identifier And the interworking gateway to which the peer node belongs in the PMIP domain to which the peer node belongs; the interworking gateway to which the peer node belongs receives the subsequent data packet sent by the peer node to the terminal node, and directly sends the Go to the visited PMIP domain.

Preferably, the foregoing method may further have the following feature: when the correspondent node is located in the legacy PMIP domain and the traditional PMIP domain outside the visited PMIP domain, the interworking gateway of the home PMIP domain is from the peer node After receiving the first data packet sent by the opposite node to the terminal node, the local mobility anchor of the PMIP domain queries the mapping server of the home PMIP domain to query the terminal node by using the home network prefix of the terminal node. Obtaining the roaming identifier when the location information is obtained, and the first data packet is sent to the visited PMIP domain by using the interworking gateway of the home PMIP domain as the destination gateway in the visited PMIP domain according to the roaming identifier. a medium interworking gateway, wherein the interworking gateway in the visited PMIP domain queries the location information of the terminal node from the visited PMIP domain mapping server according to the home network prefix and/or the roaming identifier, The mobile access gateway to which the end node belongs sends the first data packet to the terminal node.

Preferably, the above method may also have the following features:

After receiving the subsequent data packet sent by the opposite end node to the terminal node, the local mobility anchor point of the PMIP domain to which the peer node belongs is forwarded to the visited PMIP domain via the home PMIP domain.

Preferably, the foregoing method may further have the following feature: the terminal node switches from the source mobile access gateway of the visited PMIP domain to the target mobile access gateway, and the mapping server of the visited PMIP domain or the target mobile access The gateway or the source mobile access gateway notifies the address of the target mobile access gateway to the interworking gateway of the visited PMIP domain.

In order to solve the above technical problem, the present invention further provides a node communication system for roaming between PMIP domains, which includes a terminal node, a peer node, a home PMIP domain to which the terminal node belongs, and a terminal node to which the terminal node belongs. Supporting the route optimization of the PMIP domain and the PMIP domain to which the peer node belongs;

The visited PMIP domain is configured to: after the terminal node roams from the home PMIP domain supporting route optimization to the visited PMIP domain that supports route optimization, assigning, to the terminal node, location information indicating that the terminal node is in the visited PMIP domain Binding the roaming identifier to the home network prefix of the terminal node, and notifying the roaming identifier to the home PMIP domain;

The home PMIP domain is configured to: bind the home network prefix of the terminal node to the roaming identifier; and further, during the first data packet transmission process from the peer node to the terminal node, The home network prefix of the terminal node queries the roaming identifier;

The PMIP domain to which the peer node belongs is further set as: according to the roaming identifier, the visit

The interworking gateway in the PMIP domain sends the first data packet to the visited PMIP domain for the destination network element.

Preferably, the above system may also have the following characteristics:

The visited PMIP domain includes a mapping server; the home PMIP domain includes a mapping server; and the mapping server of the visited PMIP domain is configured to: allocate, to the terminal node, location information indicating that the terminal node is in the visited PMIP domain. Roaming the identifier and binding the roaming identifier to a home network prefix of the terminal node;

The mapping server of the home PMIP domain is configured to: after obtaining the roaming identifier of the terminal node from the visited PMIP domain, and attach the roaming identifier to the home network prefix of the terminal node Set.

Preferably, the above system may also have the following characteristics:

The home PMIP domain includes a mobile access gateway; the visited PMIP domain includes an interworking gateway; and the mobile access gateway of the home PMIP domain is configured to: receive the first data packet sent by the peer node to the terminal node After the home network prefix of the terminal node is used to query the mapping server of the home PMIP domain to query the location information of the terminal node, the roaming identifier is obtained, and the first data packet is exchanged through the home PMIP domain. The gateway sends to the interworking gateway of the visited PMIP domain.

Preferably, the above system may also have the following characteristics:

The home PMIP domain includes an interworking gateway;

The interworking gateway of the home PMIP domain is configured to: after receiving the first data packet sent by the opposite end node to the terminal node, query the mapping server of the home PMIP domain by using the home network prefix of the terminal node The roaming identifier is obtained when the location information of the terminal node is described, and the first data packet is sent to the interworking gateway of the visited PMIP domain.

Preferably, the above system may also have the following characteristics:

The interworking gateway of the home PMIP domain is further configured to notify the roaming identifier to the visited PMIP domain after the roaming identifier is obtained from the mapping server of the home PMIP domain.

Preferably, the above system may also have the following characteristics:

The PMIP domain to which the peer node belongs includes an interworking gateway;

The interworking gateway of the PMIP domain to which the peer node belongs is configured to: after receiving the first data packet sent by the peer node to the terminal node, query the home PMIP domain by using the home network prefix of the terminal node After the roaming identifier is known, the first data packet is sent to the visited domain according to the roaming identifier.

In order to solve the above technical problem, the present invention further provides a mapping server, where the mapping server includes a roaming identifier processing module;

The roaming identifier processing module is configured to: when the mapping server belongs to the mapping server in the PMIP domain that belongs to the terminal node after roaming, assign the terminal node to the terminal The node is in the visited roaming identifier of the location information in the PMIP domain and binds the roaming identifier to the home network prefix of the terminal node, and also notifies the roaming identifier to the home PMIP domain.

The roaming identity processing module is configured to: affinate the mapping server as a terminal node

When the mapping server in the PMIP domain receives a request to query the mapping server for the location of the terminal node by using the home network prefix of the terminal node, the roaming identifier is provided to the requesting party.

This solution provides a solution for communication problems when nodes roam between PMIP domains. BRIEF abstract

Figure 1 is a schematic diagram of the architecture of the PMIP system;

2 is a system architecture diagram of node roaming between PMIP domains;

3 is a schematic diagram of a node communication method when roaming between PMIP domains;

FIG. 4 is a schematic diagram of Embodiment 1 of a method for registering and updating a terminal between a PMIP domain that supports route optimization;

FIG. 5 is a schematic diagram of Embodiment 2 of a method for registering and updating a terminal in a PMIP domain supporting route optimization;

6 is a schematic diagram of a route optimization method for inter-node communication when the peer end is located in the visited PMIP domain of the terminal;

7 is a schematic diagram of a route optimization method for inter-node communication when the peer end is located in the home PMIP domain of the terminal;

FIG. 8 is a schematic diagram of a route optimization method for inter-node communication when the peer end is located in another PMIP domain that supports route optimization;

FIG. 9 is a schematic diagram of a route optimization method for inter-node communication when the peer end is located in another PMIP domain that supports route optimization;

FIG. 10 is a schematic diagram of a route optimization method for inter-node communication when a peer end is located in a traditional PMIP domain; FIG. 11 is a schematic diagram of a method for updating address information after a terminal cross-MAG handover in a visited domain. Preferred embodiment of the invention

As shown in FIG. 3, the node communication method when roaming between PMIP domains includes:

After the terminal node roams from the home PMIP domain that supports route optimization to the visited PMIP domain that supports route optimization, the visited PMIP domain allocates a roaming identifier indicating the location information of the terminal node in the visited PMIP domain to the terminal node. Binding the roaming identifier to the home network prefix of the terminal node, and notifying the roaming identifier to the home PMIP domain, where the home PMIP domain binds the home network prefix of the terminal node and the roaming identifier Set

During the first data packet transmission process from the peer node to the terminal node, the home PMIP domain queries the roaming identifier according to the home network prefix of the terminal node, and the PMIP domain to which the peer node belongs is The roaming identifier sends the first data packet to the visited PMIP domain by the network element in the visited PMIP domain.

After the terminal node roams from the home PMIP domain that supports route optimization to the visited PMIP domain that supports route optimization, the mobile access gateway to which the terminal node belongs sends a proxy binding update to the mapping server, and the mapping server directly or via the mobile The access gateway sends the roaming identifier to the interworking gateway to which the terminal node belongs, and the interworking gateway notifies the roaming identifier to the home PMIP domain. The details will be described below with reference to Figs. 4 and 5.

Referring to FIG. 4, the first embodiment of the method for registering and updating the location of the PMIP inter-domain roaming supporting the route optimization is as follows:

Step 401: The terminal node performs access authentication in the visited domain.

The terminal initiates the access authentication process through MAG2 (in this process, the MAPS can be used for authentication, or the AAA is responsible for authentication, or other network elements are responsible for authentication), and the visited domain's MAPS2 may need to pass through the interworking gateway IGW1 and The IGW2 interacts with the home MAPS1 of the terminal node to authenticate the user, so the MAPS2 will acquire the HNP of the terminal node.

Step 402: The MAG2 initiates a proxy binding update to the MAPS2, and the MAPS2 allocates a roaming identifier to the terminal node, and may also bind the terminal roaming identifier to the terminal HNP.

The roaming identifier is an identifier assigned to MAPS2, and may be in the form of an IP address. Packets with the IP address as the destination address outside the PMIP domain will be routed to the PMIP domain. The IGW network element, and the IGW can determine, according to the roaming identifier, that the data packet is sent to the terminal roaming to the local area.

MAPS2 can assign different unique roaming identities to different roaming users. The advantages of using unique roaming identities are: For IGW, different roaming users can be identified only according to roaming identities; for MAPS2, bear roaming is received. When the query request is identified, a specific roaming user can be identified based only on the roaming identifier.

Step 403: The MAPS2 returns the proxy binding response to the MAG2, where the message carries the terminal HNP and the roaming identifier. At this time, the IP address of the MAPS1 needs to be carried, so that the subsequent MAG initiates a terminal location update to the MAPS1.

Steps 404 ~ 406, MAG2 initiates a terminal location update to MAPS1. This message may pass through the interworking gateways IGW1 and IGW2, and the terminal roaming identifier is also carried to MAPS1. MAPS1 will bind the terminal roaming identity with the terminal HNP.

Steps 407 ~ 409, MAPS1 sends a terminal location update response to MAG2, and the message may pass through the interworking gateways IGW1 and IGW2.

Step 410: The MAG2 sends a router advertisement message to the terminal, and carries the HNP of the roaming terminal. This step may be issued after completing step 403 without waiting for the terminal location update response to return.

Referring to FIG. 5, the second embodiment of the method for registering and updating the location of the PMIP inter-domain roaming supporting the route optimization is as follows:

Step 501: The terminal node performs access authentication in the visited domain.

The terminal will initiate the access authentication to the MAPS2 through the MAG2, and the MAPS2 of the visited domain may need to interact with the home MAPS1 of the terminal node through the interworking gateways IGW1 and IGW2 to authenticate the user. Therefore, the MAPS2 will obtain the HNP of the terminal node.

Step 502: The MAG2 initiates a proxy binding update to the MAPS2. At this time, the MAPS2 allocates a roaming identifier to the terminal node, and binds the terminal roaming identifier to the terminal HNP.

Steps 503 ~ 505, MAPS2 initiates a terminal location update to MAPS1. This message may pass through the interworking gateways IGW1 and IGW2, and the terminal roaming identifier is also carried to MAPS1. MAPS1 will bind the terminal roaming identifier to the terminal HNP.

Steps 506 ~ 508, MAPS1 sends a terminal location update response to MAPS2, this message may be Will pass through the interworking gateways IGW1 and IGW2.

In step 509, MAPS2 returns the proxy binding response to MAG2. This message can be executed after step 402

Step 510: The MAG2 sends a router advertisement message to the terminal, and carries the HNP of the roaming terminal. After the terminal completes the registration and location update of the PMIP inter-domain roaming, the mappings constructed in each NE in the system are as follows:

MAPS1: MN identity, HNP, roaming identity

IGW1: MN identity, roaming identity, HNP

MAPS2: MN identity, HNP, roaming identity, CoA

MAG2: MN identity, HNP, CoA, roaming identity (only in Figure 4)

IGW2: MN identity, roaming identity, CoA

MAG3: roaming identity, HNP

IGW3: roaming identity, HNP

In the following description of the method, the first data packet refers to a data packet sent during the routing path determination process between the terminal node and the opposite node, and the subsequent data packet refers to the data packet after the routing path is determined.

The CN is located in the MN's visit to the PMIP domain.

During the process of the first node transmitting the first data packet to the terminal node, the mobile access gateway to which the peer node belongs uses the home network prefix of the terminal node to query the mapping server for the information of the mobile access gateway to which the terminal node belongs. The mapping server that visits the PMIP domain queries the roaming identifier according to the home network prefix, and implements data transmission to the peer node in the visited PMIP domain.

During the process of the first node transmitting the first data packet to the peer node, the terminal node sends a first data packet to the mobile access gateway of the visited PMIP domain, and the mobile access gateway queries the mapping server of the visited PMIP domain to query the pair. The end node location information is sent to the correspondent node by the mobile access gateway to which the correspondent node belongs.

The details will be described below with reference to Fig. 6.

Referring to FIG. 6 , route optimization of inter-node communication when the peer end is located in the visited PMIP domain of the terminal The specific implementation steps are as follows:

Step 601: When the terminal needs to send the first data packet to the opposite node, the terminal first sends the first data packet to the MAG2.

Step 602: The MAG2 queries the MAPS2 for the location information of the peer node.

Step 603: The MAPS2 finds that the peer node is also in the PMIP domain, and the MAPS2 returns the location information of the peer node (for example, the CoA or the current service MAG address) to the MAG2.

Step 604: The MAG2 forwards the first data packet to the MAG3 of the opposite node.

Step 605: The MAG3 forwards the first data to the opposite node.

The transmission path of the subsequent data packet sent by the MN to the CN is sent by the MN to the MAG2, the MAG2 is sent to the MAG3, and the MAG3 is sent to the CN.

Step 606: When the peer node needs to send the first data packet to the terminal node, the peer node sends the first data packet to the MAG3.

Step 607: The MAG3 uses the HNP of the terminal to query the MAPS2 for the address information of the current MAG. The MAPS2 queries the terminal according to the HNP of the terminal, and finds that the terminal roams to the local domain, and finally queries the location information of the terminal.

Step 608: The MAPS2 returns the location information of the terminal to the MAG3.

Step 609: The MAG3 forwards the first data packet to the MAG2.

Step 610: The MAG2 forwards the first data packet to the terminal node.

The transmission path of the subsequent first data packet sent by the CN to the MN is sent by the CN to the MAG3, the MAG3 is sent to the MAG2, and the MAG2 is sent to the CN.

The CN is located in the case of the MN's home PMIP domain.

When the MN sends the first data packet to the opposite node, the terminal node sends a first data packet to the mobile access gateway of the visited PMIP domain, and the mobile access gateway sends the first data packet to the visited PMIP domain. After the mapping server queries the peer node location information and receives the inter-domain communication indication sent by the mapping server, the first data packet is sent to the PMIP domain to which the peer node belongs.

When the peer end is located in the home PMIP domain of the terminal, the CN is in the direction of the MN, and the home PMIP domain is located. After receiving the first data packet sent by the opposite node to the terminal node, the mobile access gateway uses the home network prefix of the terminal node to query the mapping server of the home PMIP domain for the location information of the terminal node. Obtaining the roaming identifier, and transmitting, according to the roaming identifier, the first data packet to the interworking gateway in the visited PMIP domain by using the interworking gateway of the home PMIP domain as the destination gateway in the visiting PMIP domain. After the intercommunication gateway in the visited PMIP domain queries the location information of the terminal node from the visited PMIP domain mapping server according to the home network prefix and/or the roaming identifier, the mobile terminal to which the terminal node belongs The ingress gateway sends the first data packet to the terminal node.

Referring to FIG. 7 , the method for communication between nodes when the peer end is located in the home PMIP domain of the terminal, and the specific implementation steps are as follows:

Step 701: When the terminal needs to send the first data packet to the opposite node, the terminal first sends the data packet to the MAG2.

In step 702, the MAG2 queries the MAPS2 for the location information of the peer node.

Step 703: The MAPS2 finds that it is not in the PMIP domain according to the address information of the peer node, and the MAPS2 returns an inter-domain communication indication to the MAG2.

Step 704: The MAG2 forwards the first data packet to the interworking gateway IGW2.

Step 705: IGW2 forwards the first data packet to IGW1.

Step 706: The IGW1 queries the MAPS1 for location information of the peer node.

Step 707: The MAPS1 returns the location information of the opposite node to the IGW1.

Steps 708 ~ 709, IGW1 forwards the first data packet to MAG3, and finally forwards it to the peer node.

The transmission path of the subsequent data packet from MN to CN direction is MN-MAG2-IGW2-IGW1 -MAG3-CN„

Step 710: When the peer node needs to send the first data packet to the terminal node, the peer node sends the first data packet to the MAG3.

Step 711: The MAG3 queries the MAPS 1 for its location information by using the HNP of the terminal, and the MAPS 1 queries the roaming identifier of the terminal according to the terminal HNP. In step 712, the MAPS1 returns the terminal roaming identifier to the MAG3.

Steps 713 ~ 714, the MAG3 forwards the first data packet to the IGW2 through the IGW1 according to the roaming identifier of the terminal.

Step 715: The IGW2 queries the MAPS2 for the location information of the terminal according to the HNP and/or the roaming identifier of the terminal.

Step 716, MAPS2 returns the current location information of the terminal to IGW2.

Steps 717 ~ 718, IGW2 forwards the first data packet to the terminal node through MAG2.

The transmission path of the subsequent data packets in the CN to MN direction is CN-IGW1-IGW2-MAG2-MN.

An implementation in the case where the CN is located in a PMIP domain that supports route optimization except for the home domain of the MN and the visited domain of the MN.

In the direction of the CN to the MN, the interworking gateway that belongs to the PMIP domain receives the first data packet sent by the opposite end node to the terminal node from the interworking gateway of the PMIP domain to which the opposite end node belongs, and uses the home network of the terminal node. When the prefix is queried by the mapping server of the home PMIP domain to the location information of the terminal node, the roaming identifier is obtained, and the network element of the visited PMIP domain is connected to the destination PMIP domain according to the roaming identifier. The interworking gateway sends the first data packet to the interworking gateway in the visited PMIP domain, and the interworking gateway in the visited PMIP domain queries the mapping server from the visited PMIP domain according to the home network prefix and/or the roaming identifier. After the location information of the terminal node, the first data packet is sent to the terminal node via a mobile access gateway to which the terminal node belongs.

Refer to Figure 8 for the route optimization method for inter-node communication when the peer end is located in another PMIP domain that supports route optimization. The specific implementation steps are as follows:

Step 801: When the terminal needs to send the first data packet to the opposite node, the terminal first sends the first data packet to the MAG2. In step 802, the MAG2 queries the MAPS2 for the location information of the peer node.

Step 803: The MAPS2 finds that it is not in the PMIP domain according to the address information of the peer node, and the MAPS2 returns an inter-domain communication indication to the MAG2.

Step 804: The MAG2 forwards the first data packet to the interworking gateway IGW2.

Step 805: IGW2 forwards the first data packet to MAG3 through IGW3, and finally forwards it to the opposite node.

The transmission path of the MN to the CN side of the subsequent data packet is MN-MAG2-IGW2-IGW3-MAG3-CN„

Step 806: When the peer node needs to send the first data packet to the terminal node, the peer node sends the data packet to the MAG3, and the MAG3 forwards the first data packet to the home interworking gateway IGW1 of the terminal through the IGW3.

Step 807: The IGW1 uses the HNP of the terminal to query the MAPS 1 for its current location information, and the MAPS 1 queries the terminal's roaming identifier according to the terminal HNP.

Step 808: The MAPS 1 returns the terminal roaming identifier to the IGW1.

Step 809, the IGW1 returns the terminal roaming identifier to the IGW3. (This roaming identity may only be returned to the IGW of the domain where MAG3 is located, and is optimized by the IGW)

In step 810, the IGW1 forwards the first data packet to the IGW2.

Step 811: The IGW2 queries the MAPS2 for terminal location information according to the HNP and/or the roaming identifier of the terminal.

Step 812: The MAPS2 returns the location information of the terminal to the IGW2.

Steps 813 ~ 814, IGW2 sends the first data packet to the terminal node through MAG2.

The transmission path of the subsequent data packets from the CN to the MN direction is CN-MAG3-IGW3-IGW2-MAG2-MN. The subsequent packet forwarding path directly reaches IGW2 and MAG2, and is no longer forwarded to the home network of the terminal. The process in which IGW2 queries the MAPS2 according to the HNP and/or roaming identity of the terminal.

The CN is located in another implementation in the case of a PMIP domain that supports route optimization except for the home domain of the MN and the MN visited domain. When the MN sends the first data packet to the opposite node, the terminal node sends a first data packet to the mobile access gateway of the visited PMIP domain, and the mobile access gateway sends the first data packet to the visited PMIP domain. After the mapping server queries the peer node location information and receives the inter-domain communication indication sent by the mapping server, the first data packet is sent to the PMIP domain to which the peer node belongs.

When the CN is in the MN direction, the peer node is located in the PMIP domain that supports the route optimization except the home PMIP domain and the visited PMIP domain, and the interworking gateway of the PMIP domain to which the peer node belongs receives the pair. After the end node sends the first data packet to the terminal node, the interworking gateway of the home PMIP domain queries the mapping server of the home PMIP domain for the location information of the terminal node by using the home network prefix of the terminal node and Obtaining the roaming identifier, the interworking gateway of the PMIP domain to which the peer node belongs sends the first data packet to the interworking gateway in the visited PMIP domain according to the roaming identifier, and the interworking gateway in the visited PMIP domain according to the After the home network prefix and/or the roaming identifier queries the location information of the terminal node from the visited PMIP domain mapping server, the first data packet is sent to the mobile access gateway to which the terminal node belongs to The terminal node.

Refer to Figure 9 for the route optimization method for inter-node communication when the peer end is located in another PMIP domain that supports route optimization. The specific implementation steps are as follows:

Step 901: When the terminal needs to send the first data packet to the opposite node, the terminal first sends the first data packet to the MAG2.

Step 902: The MAG2 queries the MAPS2 for current location information of the peer node.

Step 903: The MAPS2 finds that it is not in the PMIP domain according to the address information of the peer node, and the MAPS2 returns an inter-domain communication indication to the MAG2.

Step 904: The MAG2 forwards the first data packet to the interworking gateway IGW2.

In step 905, the IGW2 forwards the first data packet to the MAG3 through the IGW3, and finally forwards it to the opposite node.

Step 906, when the peer node needs to send the first data packet to the terminal node, the peer node will The first data packet is sent to the MAG3, and the MAG3 forwards the first data to the IGW3, and the IGW3 performs a terminal location query to the home network of the terminal node, and the message arrives at the home interworking gateway IGWl of the terminal.

Step 907: The IGW1 uses the HNP of the terminal to query the MAPS 1 for its current location information, and the MAPS 1 queries the terminal's roaming identifier according to the terminal HNP.

Step 908: The MAPS 1 returns the terminal roaming identifier to the IGW1.

Step 909: The IGW1 returns the terminal roaming identifier to the IGW3.

In step 910, the IGW3 forwards the first data packet to the IGW2.

Step 911, IGW2 queries the MAPS2 for terminal location information.

Step 912: The MAPS2 returns the location information of the terminal to the IGW2.

Steps 913 ~ 914, IGW2 sends the first data packet to the terminal node through MAG2.

Subsequent packet forwarding paths directly reach IGW2 and MAG2, and are no longer forwarded to the home network of the terminal.

The CN is located in the case of a legacy PMIP domain of the MN other than the home domain and the visited domain.

When the CN is in the MN direction, when the peer node is located in the legacy PMIP domain and the traditional PMIP domain outside the visited PMIP domain, the interworking gateway of the home PMIP domain is from the local mobility anchor of the PMIP domain to which the peer node belongs. After receiving the first data packet sent by the peer node to the terminal node, using the home network prefix of the terminal node to query the mapping server of the home PMIP domain to query the location information of the terminal node, the roaming is obtained. And identifying, by the network element in the visited PMIP domain, the first data packet is sent to the interworking gateway in the visited PMIP domain by using the interworking gateway of the home PMIP domain according to the roaming identifier, the visited PMIP After the interworking gateway in the domain queries the location information of the terminal node from the visited PMIP domain mapping server according to the home network prefix and/or the roaming identifier, the mobile access gateway to which the terminal node belongs First The data packet is sent to the terminal node.

Refer to Figure 10 for the route optimization method for inter-node communication when the peer end is in the traditional PMIP domain. The specific implementation steps are as follows:

Step 1001: When the terminal needs to send the first data packet to the opposite node, the terminal first sends the first data packet to the MAG2.

Step 1002: MAG2 queries MAPS2 for current location information of the peer node.

Step 1003: The MAPS2 finds that it is not in the PMIP domain according to the address information of the peer node, and the MAPS2 returns an inter-domain communication indication to the MAG2.

Step 1004: The MAG2 forwards the first data packet to the interworking gateway IGW2.

In step 1005, the IGW2 forwards the first data packet to the LMA3 of the opposite node, and the LMA3 sends the first data packet to the MAG3 through the tunnel, and finally forwards it to the opposite node.

Step 1006: When the peer node needs to send the first data packet to the terminal node, the peer node sends the first data packet to the MAG3, and the MAG3 uses the tunnel to forward the first data packet to the LMA3, and then the LMA3 sends the terminal to the terminal. The domain was intercepted by IGW1.

Step 1007: The IGW1 uses the HNP of the terminal to query the MAPS1 for its current location information, and the MAPS 1 queries the terminal's roaming identifier according to the terminal HNP.

Step 1008: MAPS 1 returns the terminal roaming identity to IGW1.

Step 1009: IGW1 may return the terminal roaming identity to LMA3, but LMA3 ignores the message because it cannot resolve the message.

In step 1010, the MAG3 forwards the first data packet to the IGW2.

Step 1011: The IGW2 queries the MAPS2 for terminal location information.

In step 1012, the MAPS2 returns the location information of the terminal to the IGW2.

Steps 1013 to 1014, IGW2 sends the first data packet to the terminal node through MAG2.

Subsequent packet forwarding paths still need to be forwarded through the interworking gateway IGW1 of the terminal home network, and then reach IGW2 and MAG2. Local mobile anchor point of the PMIP domain to which the peer node belongs After the subsequent data packet sent by the opposite end node to the terminal node is forwarded to the visited PMIP domain via the home PMIP domain.

When the MN performs the MAG handover, the terminal node switches from the source mobile access gateway of the visited PMIP domain to the target mobile access gateway, the mapping server of the visited PMIP domain or the target mobile access gateway or the source. The mobile access gateway notifies the address of the target mobile access gateway to the interworking gateway of the visited PMIP domain.

Referring to FIG. 11 , when the terminal roaming identifier is an address that can be routed to the visited network, the terminal updates the address information after the MAG switchover in the visited domain. The specific implementation steps are as follows:

Step 1101: The terminal is switched from MAG2 to MAG3 in the visited domain.

Step 1102, in order to ensure smooth communication with the peer node, MAPS2 may update the terminal location information (for example: the address of the new CoA or MAG3) to IGW2.

Step 1103: The MAG3 may obtain the inter-domain communication identifier when switching, and update the terminal location information (for example, the address of the new CoA or MAG3) to the IGW2.

Step 1104, MAG2 may update the terminal location information to IGW2 after the handover is completed. According to the actual network deployment, the above steps 1102, 1103 and 1104 can be sent at least once.

a node communication system that roams between PMIP domains corresponding to the foregoing method, including a terminal node, a peer node, a home PMIP domain to which the terminal node belongs, and a visited PMIP domain to which the terminal node belongs to support route optimization, The PMIP domain to which the peer node belongs. The functions and execution manners of the respective constituent units are the same as those described in the above methods, and are not described herein again.

The mapping server provided in the solution includes a roaming identity processing module.

The roaming identifier processing module is configured to allocate, to the terminal node, location information indicating that the terminal node is in the visited PMIP domain, when the mapping server is a mapping server in a visiting PMIP domain that belongs to the terminal node after roaming as a terminal node The roaming identifier is bound to the home network prefix of the terminal node, and the roaming identifier is also notified to the home PMIP domain.

The roaming identifier processing module is configured to: when the mapping server is used as a mapping server in a home PMIP domain of the terminal node, receive a home network prefix to the mapping service using the terminal node After querying the request for the location of the terminal node, the server provides the roaming identifier to the requesting party.

It should be noted that the features in the embodiments and the embodiments of the present application may be arbitrarily combined with each other without conflict. It is a matter of course that the invention may be embodied in various other forms and modifications without departing from the spirit and scope of the invention. One of ordinary skill in the art will appreciate that all or a portion of the above steps may be accomplished by a program instructing the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

Industrial applicability

This solution provides a solution for communication problems when nodes roam between PMIP domains.

Claims

Claim

1. A node communication method when roaming between PMIP domains, wherein

2. The method of claim 1 wherein

After the terminal node roams from the home PMIP domain that supports route optimization to the visited PMIP domain that supports route optimization, the mobile access gateway to which the terminal node belongs sends a proxy binding update to the mapping server, and the mapping server directly or via the mobile The access gateway sends the roaming identifier to the interworking gateway to which the terminal node belongs, and the interworking gateway notifies the roaming identifier to the home PMIP domain.

3. The method of claim 1, wherein

The mapping server of the visited PMIP domain binds the home network prefix of the terminal node to the roaming identifier;

When the peer node is located in the visited PMIP domain, the peer node sends a first data packet to the terminal node, and the mobile access gateway to which the peer node belongs uses the home network prefix mapping of the terminal node. The server queries the information about the mobile access gateway to which the terminal node belongs, and the mapping server that visits the PMIP domain queries the roaming identifier according to the home network prefix, and implements data transmission to the opposite node in the visited PMIP domain.

4. The method of claim 1, wherein

When the peer node is located in the visited PMIP domain, in the process of sending the first data packet to the peer node, the terminal node sends the first to the mobile access gateway of the visited PMIP domain. a data packet, the mobile access gateway queries the mapping server of the visited PMIP domain to the location information of the peer node, and sends the first data packet to the peer node by using the mobile access gateway to which the opposite node belongs. .

5. The method of claim 1, wherein

6. The method of claim 1, wherein

When the correspondent node is located in the home PMIP domain, the mobile access gateway of the home PMIP domain receives the first data packet sent by the correspondent node to the terminal node, and uses the home network of the terminal node. When the prefix is queried by the mapping server of the home PMIP domain to the location information of the terminal node, the roaming identifier is obtained, and the network element of the visited PMIP domain is connected to the destination PMIP domain according to the roaming identifier. The interworking gateway sends the first data packet to the interworking gateway in the visited PMIP domain, and the interworking gateway in the visited PMIP domain queries the mapping server from the visited PMIP domain according to the home network prefix and/or the roaming identifier. After the location information of the terminal node, the first data packet is sent to the terminal node via a mobile access gateway to which the terminal node belongs.

7. The method of claim 1, wherein

When the peer node is located in the PMIP domain that supports the route optimization other than the home PMIP domain and the visited PMIP domain, the interworking gateway of the home PMIP domain receives the interworking gateway of the PMIP domain to which the peer node belongs. After the first node sends the first data packet to the terminal node, the home network prefix of the terminal node is used to query the mapping server of the home PMIP domain to query the location information of the terminal node, and the roaming identifier is obtained. According to the roaming identifier, the network element in the visited PMIP domain uses the interworking gateway of the home PMIP domain to send the first data packet to the interworking gateway in the visited PMIP domain, and the visit is made. After the interworking gateway in the PMIP domain queries the location information of the terminal node from the visited PMIP domain mapping server according to the home network prefix and/or the roaming identifier, the mobile access gateway to which the terminal node belongs The first The data packet is sent to the terminal node.

8. The method of claim 1, wherein

When the peer node is located in the PMIP domain that supports the route optimization except the home PMIP domain and the visited PMIP domain, the interworking gateway of the PMIP domain to which the peer node belongs receives the destination node to send to the peer node. After the first data packet of the terminal node is used, the interworking gateway of the home PMIP domain uses the home network prefix of the terminal node to query the mapping server of the home PMIP domain for location information of the terminal node and learns the roaming identifier. And the interworking gateway of the PMIP domain to which the peer node belongs sends the first data packet to the interworking gateway in the visited PMIP domain according to the roaming identifier, where the interworking gateway in the visited PMIP domain is based on the home network prefix and And after the roaming identifier queries the location information of the terminal node from the visited PMIP domain mapping server, the first data packet is sent to the terminal node via a mobile access gateway to which the terminal node belongs.

9. The method according to claim 7 or 8, wherein

After the interworking gateway of the home PMIP domain queries the mapping server of the home PMIP domain to query the location information of the terminal node, after the roaming identifier is known, the roaming identifier is notified to the PMIP domain to which the peer node belongs. An interworking gateway to which the peer node belongs; the interworking gateway to which the peer node belongs receives the subsequent data packet sent by the peer node to the terminal node, and then directly sent to the visited PMIP domain.

10. The method of claim 1, wherein

When the peer node is located in the traditional PMIP domain and the traditional PMIP domain outside the visited PMIP domain, the interworking gateway of the home PMIP domain receives the local mobility anchor from the PMIP domain to which the peer node belongs. After the first node sends the first data packet to the terminal node, the home network prefix of the terminal node is used to query the mapping server of the home PMIP domain to query the location information of the terminal node, and the roaming identifier is obtained according to the The roaming identifier sends the first data packet to the interworking gateway in the visited PMIP domain via the interworking gateway of the home PMIP domain by using the interworking gateway of the visited PMIP domain as the destination gateway, and the visited PMIP domain communicates with each other. After the gateway queries the location information of the terminal node from the visited PMIP domain mapping server according to the home network prefix and/or the roaming identifier, the gateway sends the first data by using a mobile access gateway to which the terminal node belongs. The packet is sent to the terminal node.

11. The method of claim 10, wherein

12. The method of claim 1, wherein

The terminal node switches from the source mobile access gateway of the visited PMIP domain to the target mobile access gateway, and the mapping server of the visited PMIP domain or the target mobile access gateway or the source mobile access gateway The address of the target mobile access gateway is notified to the interworking gateway of the visited PMIP domain.

13. A node communication system for roaming between PMIP domains, wherein: a terminal node, a peer node, a home PMIP domain to which the terminal node belongs, and a visited PMIP domain to which the terminal node belongs to support route optimization Describe the PMIP domain to which the peer node belongs;

The PMIP domain to which the peer node belongs is further configured to: send the first data packet to the visited PMIP domain by using the visited gateway in the visited PMIP domain as the destination network element according to the roaming identifier.

14. The system of claim 13 wherein

The mapping server of the home PMIP domain is configured to: after learning the roaming identifier of the terminal node from the visited PMIP domain, and binding the roaming identifier to the home network prefix of the terminal node.

15. The system of claim 14 wherein

16. The system of claim 14 wherein

The home PMIP domain includes an interworking gateway;

17. The system of claim 16 wherein

18. The system of claim 14 wherein

19. A mapping server, wherein

The mapping server includes a roaming identifier processing module;

The roaming identifier processing module is configured to: when the mapping server is a mapping server in the visiting PMIP domain that belongs to the terminal node after the roaming of the terminal node, assigning, to the terminal node, location information indicating that the terminal node is in the visited PMIP domain Roaming identity and the roaming identity with the end The home network prefix of the end node is bound, and the roaming identifier is also notified to the home PMIP domain.

20, a mapping server, wherein

The mapping server includes a roaming identifier processing module;

The roaming identifier processing module is configured to: when the mapping server is used as a mapping server in the home PMIP domain of the terminal node, after receiving the request for querying the location of the terminal node by using the home network prefix of the terminal node to the mapping server Providing the roaming identifier to the requesting party.