METHOD FOR OPTIMIZING THE COMMUNICATION BETWEEN MOBILE NODES

Abstract

A method for optimizing communication between mobile nodes (MNs) in a mobile IP network includes the steps for sending: data packets from a MN in a mobile IP network to its foreign agent device, receiving the data packets at the foreign agent device, determining that a destination MN is attached to the foreign agent device, and forwarding the data packets to the destination MN.

Description

FIELD OF THE INVENTION

The present invention relates to network communication, and particularly, to a method for optimizing communication between mobile nodes in a mobile Internet Protocol (IP) based network.

BACKGROUND OF THE INVENTION

Mobile IP technology is a technical solution that provides mobility for users on the Internet. Mobile IP goes beyond geographical restrictions, and exhibits high scalability, reliability and security. It extends mobility and roaming capability, enabling a node to hold up ongoing communication in the progress of a handover.

In a mobile IP network, a mobile node (MN) can be connected to any link by using a permanent IP address. While providing terminals with a large range of mobility, mobile IP also ensures the assignability and reachability of terminal IP addresses. A mobile IP network mainly includes MNs, foreign agents (FAs), home agents (HAs) and communication nodes (CNs).

In a mobile IP network, data packets are transmitted between an MN and a CN in accordance with RFC3344, as shown in FIG. 1. The detailed procedure is as follows:

When the MN moves to a foreign network, data packets sent by the CN to the MN are first routed to the HA of the MN, then to the FA of the MN via a tunnel, and finally to the MN.

Normally, packets sent by the MN to the CN are first routed to the FA of the MN and then directly sent to the CN by the FA. In special scenarios, for instance, during multicast or when a firewall filters packets by source addresses, packets sent by the MN are sent to the HA of the MN via a reverse tunnel assigned to the MN and then routed to the CN. The specific procedure is defined in RFC3024. The routing procedure on a reverse tunnel in the mobile IP network is shown in FIG. 2.

In a mobile IP network, two MNs may be attached to one FA, as shown in FIG. 3. In addition, to optimize the re-registration due to MN handover, hierarchical FA networking may be adopted so that the FAs of several MNs are attached to one gateway FA (GFA). This networking is shown in FIG. 4. In the mobile IP network shown in FIG. 3 or FIG. 4, for communication between two MNs attached to one FA/GFA, if one or both of the MNs have been assigned a reverse tunnel, when the MN requesting the reverse tunnel (an MN1) sends data packets to the other MN (an MN2), the data packets are routed in the following procedure:

The data packets sent by the MN1 to the MN2 are first routed to the FA/GFA and then forwarded to the HA of the MN1 (an HA1) via the reverse tunnel assigned to the MN1. After HA1 resolves the data packets, it routes the packets to the HA of the MN2 (an HA2). The HA2 then routes the data packets to the FA/GFA via a tunnel. The FA/GFA resolves the data packets from the tunnel and forwards the data packets to the MN2.

Because a reverse tunnel exists, for a communication session between two MNs attached to one FA/GFA, packets exchanged between the two MNs need to detour to their home agents for routing. In the process, data packets have to go through two tunnels. This causes a delay in the communication and increases loads of the FA/GFA.

SUMMARY OF THE INVENTION

The present invention provides a method for optimizing the communication between MNs in a mobile IP network, to reduce the delay in inter-MN communication and reduce the load of network devices.

The technical solution is as follows:

A method for optimizing communication between MNs in a mobile IP network includes the steps of:

A: sending, by an MN in the mobile IP network, the data packets destined to another MN to its foreign agent device and

B: by the foreign agent device, receiving the data packets, determining that the destination MN is attached to the foreign agent device, and routing the packets directly to the destination MN.

After an MN registers with its foreign agent device, the foreign agent device can store the attribute information of the MN.

In the above technical solution, data packets exchanged between two MNs attached to one FA/GFA are directly forwarded by the FA/GFA. This optimizes the communication between two MNs under a same FA/GFA, reducing the delay in communication between MNs and relieving the load of network devices like FA/HA.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will become more readily apparent from the Detailed Description of the Invention, which proceeds with reference to the following drawings, in which:

FIG. 1 illustrates a procedure for routing data packets between a MN and a CN in a mobile IP network;

FIG. 2 illustrates a routing procedure on a reverse tunnel in the mobile IP network;

FIG. 3 illustrates a networking diagram where two MNs are attached to one FA;

FIG. 4 illustrates a networking diagram where two MNs are attached to one GFA;

FIG. 5 shows a schematic diagram illustrating a method according to an embodiment of the invention;

FIG. 6 illustrates optimization of routing with a reverse tunnel for MNs under the same FA according to an embodiment of the invention; and

FIG. 7 illustrates optimization of routing with a reverse tunnel for MNs under the same GFA according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

For a better understanding of the purpose, technical solution and benefits of the present invention, the embodiments of the invention are detailed with reference to the accompanying drawings.

An embodiment of the invention provides a method for optimizing the communication between MNs in a mobile IP network. The core idea is: the FA/GFA forwards data packets exchanged between two MNs attached to the FA/GFA without detouring them to the home agents of the MNs.

As shown in FIG. 5, the method includes:

Step 5-1: Register the MNs with the FA/GFA.

According to an embodiment of the invention, the MNs should first register with the FA/GFA. The registration procedure complies with RFC3344/draft-ietf-mip4-reg-tunnel-00. The MNs to register with the FA/GFA fall into two categories: those requiring a reverse tunnel and those requiring normal routing.

After the registration, if an FA hierarchy is not adopted, the FA stores the attribute information of the MNs. The attribute information includes the IP address and an indication as to whether the MN has a reverse channel. If a FA hierarchy is adopted, the attribute information may be stored in both the FA and the GFA, or stored in the GFA only.

The FA/GFA may store the attribute information in an internal visitor list of MNs.

Step 5-2: An MN (an MN1) sends the data packets destined to another MN (an MN2) to the FA/GFA.

When the MN1 and the MN2 are attached to one FA, and the MN1 supports reverse tunneling, the MN1 first sends the data packets destined to the MN2 to the FA.

When the MN1 and the MN2 are attached to one GFA, and the MN1 supports reverse tunneling, the MN1 first sends the data packets destined to the MN2 to the FA of the MN1. The FA encapsulates the received data packets into tunnel data packets and sends the encapsulated data packets to the GFA.

Step 5-3: The FA/GFA forwards the data packets to the destination MN attached to the FA/GFA directly.

If an FA hierarchy is not adopted, upon reception of the data packets sent by MN1, the FA queries an internal visitor list according to the source IP address of the data packets and determines whether the MN1 has been assigned a reverse tunnel. If the MN1 has been assigned a reverse tunnel, the FA queries the internal visitor list according to the destination IP address of the data packets and determines whether the destination MN is locally attached. If the destination MN is locally attached, the FA queries a routing table or its visitor list to obtain the routing information of the destination MN (MN2), and routes the data packets to the MN2. If the MN indicated by the destination IP address is not locally attached, or if the source MN does not have a reverse tunnel, the normal handling procedure is followed. This procedure for routing data packets is shown in FIG. 6.

If an FA hierarchy is adopted, when an MN1 and an MN2 are attached to the same FA, the routing procedure may be the same as that when the FA hierarchy is not adopted. Otherwise, an FA1 encapsulates the data packets received from the MN1 into tunnel data packets and forwards them to the GFA; the GFA decapsulates the tunnel data packets sent by the FA1 via a tunnel to data packets, obtains the source MN (the MN1) attribute information by querying its internal visitor list according to the source IP address of the data packets, and determines whether the MN has been assigned a reverse tunnel. If the MN has been assigned a reverse tunnel, the GFA queries its internal visitor list according to the destination IP address of the data packets and determines whether the MN indicated by the destination IP address is locally attached. If the MN indicated by the destination IP address is locally attached, the GFA obtains the routing information of the MN2 by querying its routing table or visitor list and encapsulates the data packets to tunnel data packets, and sends the tunnel data packets to an FA2. The FA2 decapsulates the received tunnel data packets and forwards the data packets to the MN2. If the MN indicated by the destination IP address is not locally attached or if the source MN attribute indicates that MN1 has not been assigned a reverse tunnel, the data packets are routed in a normal procedure. This procedure for routing data packets is shown in FIG. 7.

If an FA hierarchy is adopted, when an MN1 and an MN2 are attached to the same FA, the routing procedure may also differ from that when an FA hierarchy is not adopted. In this case, the FA only encapsulates, decapsulates, and forwards the received data packets. The GFA determines whether the source MN has been assigned a reverse tunnel and whether the destination MN is locally attached, and forwards to the locally attached destination MN the data packets sent by the source MN that has been assigned a reverse tunnel.

The mobile IP network is an IPv4 or IPv6 network.

Although the invention has been described through some exemplary embodiments, the invention is not limited to such embodiments. It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. The invention is intended to cover all modifications and variations provided that they fall in the scope of protection defined by the following claims or their foreseeable equivalents.

Claims

1. A method for optimizing communication between MNs in a mobile IP network, comprising the steps of: A: sending, by a MN in the mobile IP network, data packets destined to another MN to its foreign agent device; andB: by the foreign agent device, receiving the data packets, determining that the destination MN is attached to the foreign agent device, and routing the packets directly to the destination MN.

2. The method of claim 1, wherein the MN registers with an foreign agent device and the foreign agent device stores the attribute information of the MN.

3. The method of claim 2, wherein the MN attribute information is stored in the internal visitor list of the FA.

4. The method of claim 2, wherein the MN attribute information comprises whether the MN has been assigned a reverse tunnel or further comprises the IP address of the MN.

5. The method of claim 4, wherein, in step B, the foreign agent device receives the data packets, determines that the sending MN has been assigned a reverse tunnel according to the MN attribute information stored in the foreign agent device, and goes on to determine that the destination MN is attached to the foreign agent device.

6. The method of claim 1, wherein the foreign agent device queries its routing table or visitor list to determine that the destination MN is attached to the foreign agent device.

7. The method of claim 1, wherein the foreign agent device is a FA or a GFA.

8. The method of claim 1, wherein the foreign agent device in step A is a FA and step B comprises the steps of: B1: by the FA, querying the MN attribute information it stores, determining that the source MN has a reverse tunnel according to the source IP address of the received data packets, determining whether the destination MN is locally attached and if the destination MN is locally attached, proceeding with step B2; if the destination MN is not locally attached, proceeding with step B3;B2: routing, by the FA, the data packets to the destination MN attached to the FA; andB3: routing, by the FA, the data packets to a GFA, and by the GFA, sending the data packets to the destination MN attached to the GFA after determining that the destination MN is locally attached.

9. The method of claim 8, wherein step B3 comprises the steps of: B31: by the FA, encapsulating the received packets into tunnel data packets and sending the tunnel data packets to the GFA, and by the GFA, decapsulating the tunnel data packets to data packets;B32: by the GFA, querying the MN attribute information the GFA stores, determining that the source MN has a reverse tunnel according to the source IP address of the decapsulated data packets, determining that the destination MN is locally attached, and proceeding with step B33; andB33: by the GFA, querying its routing table, encapsulating the extracted data packets into tunnel data packets, and sending the tunnel data packets to the FA of the destination MN attached to the GFA; by the FA of the destination MN, decapsulating the received tunnel data packets to data packets and sending the data packets to the destination MN.

10. The method of claim 1, wherein the mobile IP network is an IPv4 or IPv6 network.

11. The method of claim 2, wherein the foreign agent device is a FA or a GFA.

12. The method of claim 3, wherein the foreign agent device is a FA or a GFA.

13. The method of claim 4, wherein the foreign agent device is a FA or a GFA.

14. The method of claim 5, wherein the foreign agent device is a FA or a GFA.

15. The method of claim 6, wherein the foreign agent device is a FA or a GFA.