CA2477155C - Method and apparatus for robust local mobility management in a mobile network - Google Patents
Method and apparatus for robust local mobility management in a mobile network Download PDFInfo
- Publication number
- CA2477155C CA2477155C CA2477155A CA2477155A CA2477155C CA 2477155 C CA2477155 C CA 2477155C CA 2477155 A CA2477155 A CA 2477155A CA 2477155 A CA2477155 A CA 2477155A CA 2477155 C CA2477155 C CA 2477155C
- Authority
- CA
- Canada
- Prior art keywords
- mobile node
- map
- anchor point
- network
- mobility anchor
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/20—Selecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/085—Mobility data transfer involving hierarchical organized mobility servers, e.g. hierarchical mobile IP [HMIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
Abstract
A method and apparatus for robust mobility management in a network having a mobile node (MN), a mobility anchor point (MAP), a correspondent node (CN1, CN2), a home agent (HA) and an access router (AR1) and operating under a hierarchical protocol. The mobile node (MN) sends the address (102, 104) of the mobility anchor point (MAP) to the correspondent node (CN1, CN2) and sends the address (106, 108) of the mobile node (MN) on the network of the access router (AR) to the home agent (HA) and to the mobility anchor point (MAP).
When failure of the mobility anchor point occurs, the mobile node recovers from the failure by selecting a new mobility anchor point or operating under a non-hierarchical protocol. Failure is detected by an intermediate router or by a correspondent node when messages fail to reach the mobility anchor point.
When failure of the mobility anchor point occurs, the mobile node recovers from the failure by selecting a new mobility anchor point or operating under a non-hierarchical protocol. Failure is detected by an intermediate router or by a correspondent node when messages fail to reach the mobility anchor point.
Description
METHOD AND APPARATUS FOR ROBUST LOCAL MOBILITY
MANAGEMENT IN A MOBILE NETWORK
TECHNICAL FIELD
This invention relates to local mobility management techniques for mobile networks and, in particular, to a method and apparatus for recovering from failure of local mobility management.
BACKGROUND OF THE INVENTION
As the number of wireless devices for voice or data increases, mobile data communication will likely emerge as the technology supporting most communication including voice and video. Mobile data communication will be pervasive in cellular systems such as 3G and in wireless LAN such as 802.11, and will extend into satellite communication.
In IP (Internet Protocol) networks, routing is based on stationary IP
addresses, similar to how a postal letter is delivered to the fixed address on the envelope. A
device on a network is reachable through normal IP routing by the IP address it is assigned on the network.
When a device roams away from its home network it is no longer reachable using normal IP routing. This results in the active sessions of the device being terminated. Mobile protocols (such as the Hierarchical Mobile Internet protocol (HMIP v4 and v6) or the Mobile IP defined by the Internet Engineering Task Force (IETF) RFC 2002) were created to enable users to keep the same IP address while traveling to a different network (which may even be on a different wireless system), thus ensuring that a roaming individual could continue communication without sessions or connections being dropped. When the mobility functions of mobile protocols are performed at the network layer rather than the physical layer, the mobile device can span different types of wireless and wire-line networks while maintaining connections and ongoing applications. In some applications, such as remote login, remote printing, and file transfers, it is undesirable to interrupt communications while an individual roams across network boundaries. Also, certain network services, such as software licenses and access privileges, are based on IP addresses.
Changing these IP addresses could compromise the network services.
The concept of local mobility management is well known in the cellular and IP domains. For instance, in a mobile IP network, the concept of a mobility anchor point (MAP) is defined to support fast mobility. A MAP is a node that enhances handoff performance by acting as a care-of-address (CoA) of the mobile node.
Specifically, the mobile node registers the address in the network of the MAP
with its home agent and its correspondent nodes and registers its "real CoA" with the MAP.
As long as the'MAP is not changed, a mobile node need not update its home agent and correspondent nodes. However, if the MAP fails or gets disconnected, the correspondent nodes cannot send packets to the mobile node and packets in transit will be lost. Additionally, it takes a significant amount of time to identify the problem and recover. Meanwhile, all packets sent will be lost.
SUMMARY OF THE INVENTION
According to one aspect of the invention, a method for robust mobility management in a network having a mobile node, a mobility anchor point, a correspondent node, a home agent and an access router and operating under a hierarchical protocol, is presented. The method comprises providing binding updates during agent discovery stage or whenever the mobile node is moving to a new access router, the updates including the mobile node sending an address belonging to the mobility anchor point to the correspondent node, the mobile node sending an address of the mobile node on a network of the access router to the home agent, the mobile node sending the address of the mobile node on the network of the access router to the mobility anchor point, and detecting failure of the mobility anchor point comprising the correspondent node attempting to transmit an information packet to the mobility anchor point, the correspondent node continuously monitoring packets for determining if an information packet is successfully transmitted to the mobility anchor point, and if the information packet is not successfully transmitted to the mobility anchor point deleting binding updates, passing the information packet to the home agent, and the home agent encapsulating the information packet for transmission to the mobile node.
BRIEF DESCRIPTION OF THE DRAWINGS
The features of the invention believed to be novel are set forth with particularity in the appended claims. The invention itself however, both as to organization and method of operation, together with objects and advantages thereof, may be best understood by reference to the following detailed description of the invention, which describes certain exemplary embodiments of the invention, taken in conjunction with the accompanying drawings in which:
FIG. 1 is a diagrammatic representation of binding updates according to the invention, in an exemplary network.
FIG. 2 is a diagrammatic representation of information flow in a network in accordance with the present invention in normal operation.
FIG. 3 is a diagrammatic representation of information flow in a network in accordance with the present invention when the MAP fails.
FIG. 4 is a flow chart of an embodiment of the method of the present invention.
FIG. 5 is a further flow chart of an embodiment of the method of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
While this invention is susceptible of embodiment in many different forms;
there is shown in the drawings and will herein be described in detail specific embodiments, with the understanding that the present disclosure is to be considered as an example of the principles of the invention and not intended to limit the invention to the specific embodiments shown and described. In the description below, like reference numerals are used to describe the same, similar or corresponding parts in the several views of the drawings.
When a network device is capable of roaming away from its home network it is called a Mobile Node (MN). A Mobile Node is a device such as a cell phone, personal digital assistant, automobile computer or portable computer whose software enables network roaming capabilities.
A Correspondent Node (CN) is a device on the network with which the Mobile Node is in communication.
A Home Agent (HA) is a device on the home network, i.e. the network of the Mobile node when it is not roaming. The HA may serve as the default anchor point for communication with the Mobile Node, tunneling packets from a Correspondent Node to the roaming Mobile Node.
An Access Router (AR) or Foreign Agent (FA) is a router that may function as the point of attachment for the Mobile Node when it roams to a foreign network. It delivers information packets to the Mobile Node. Information packets from the CN
may be forwarded via the Home Agent or via the Mobility Anchor Point.
The care-of address (CoA) is the address that can be used to reach a Mobile Node when it is on a foreign network. The Home Agent maintains an association between the home IP address of the Mobile Node and its care-of address, which is the current location of the Mobile Node on the foreign or visited network.
Encapsulation is a protocol which allows information packets of a network A, including routing information, to be transmitted across an arbitrary network B
by encapsulating the packets of A within packets of B. Encapsulation may also be used to transport packets from one point in a network to another. This process is called Tunneling.
A routing header is an option in the IP header that enables a source to specify, in order, multiple addresses through which a packet must be routed before it reaches its final destination.
In standard Mobile IP, when a MN moves to a new location on the network, all of the Correspondent Nodes and the Home Agent are informed of the new CoA.
This generates an excess of communication and increases delay. An alternative approach is a Hierarchical Mobile Internet protocol (HMIP), in which information packets are routed to the MN via a Mobility Anchor Point (MAP). The HA and CNs are each provided with the address of the MAP or an address in the MAPs network which uniquely identifies the mobile node (henceforth denoted by MAP_Addr). In the latter case the MAP can intercept the packet on behalf of the Mobile Node.
In either case, the MAP receives the information packets and then forwards the information packets to the MN. When a MN moves to a new location on the network, only the MAP needs to be informed of the move. That is, only devices in the neighborhood of the MN need to be informed of the move. This provides a more efficient network. However, if the MAP fails then communication to all of the CNs is lost.
The method of the invention allows a mobile node to continue receiving packets even when the MAP fails. It also enables the mobile node to discover the problem quickly.
According to the method of the invention, the operation of the Mobile Node is 5 changed as shown in FIG. 1. FIG. 1 shows an exemplary network including a Mobile Node (MN), two Correspondent Nodes (CN1 and CN2), three Access Routers (AR1, AR2 and AR3), a Home Agent router (HA) and a Mobility Anchor Point (MAP). Also shown are two intermediate routers (R1 and R2) indicating that there may be several layers between the MAP and the ARs. Following the Agent Discovery stage, during which AR1 is identified as the current Access Router and MAP as the current Mobility Anchor Point, the Mobile Node registers its current location with the MAP and Home Agent. The mobile node sends a binding update (BU), with MAP Addr) as its CoA, only to the correspondent nodes (CN1 and CN2), shown as links 102 and 104 in FIG. 1. However, it gives its "real CoA" (i.e.
its actual address on the network of ARl, denoted by CMN-Addr) to the home agent via link 106. This is in contrast to prior schemes in which the MAP Addr was sent to the Home Agent. The CMN Addr is also sent to the MAP via link 108.
As the mobile node moves to a new access router and gets a new CMN Addr, it sends a BU to both the MAP and its Home Agent, with the CMN Addr as the CoA.
This is in contrast to prior schemes, where the Home Agent was aware only of the MAP Addr, and no update was needed when the mobile nodes moved to a new access router. Note that when the mobile node performs a handoff, it needs to receive packets seamlessly from the correspondent nodes. There is often very little real-time communication between the home agent and the mobile node - assuming that all correspondents support the binding update (BU) option. So, the roundtrip latency associated with sending a BU to the HA will not affect the performance of the current sessions between the mobile node and its correspondents.
The operation of the network is also changed according to the method of the invention. In normal operation, as shown in FIG. 2, information flows between the mobile node (MN) and the correspondent nodes (CN1 and CN2) via the Mobility Anchor Point (MAP). The information passes through the access router (ARl) and other routers (R1 and AR2).
When a router tries to send packets with a routing header to another node and finds that the node is unreachable, instead of dropping the packet, the router will process the packet's routing header. In other words, the router will send the packet to the next destination given in the routing header.
When the MAP fails or gets disconnected from the network, packets from the correspondent node CN2 will reach the last router (Rl) on the path to the MAP
that is still functional. That router then determines that the packet cannot be sent to the MAP
using the standard mechanisms (like routing table/neighbor discovery/ARP). It then processes the routing header and sends the packet to the next entry in the routing header. This entry is the home address of the mobile node. The router then sends the packet to the home network where the home agent HA intercepts the packet. This situation is shown in FIG. 3. The HA, which has the "real CoA" encapsulates the packet to the mobile node. Thus the MN receives the packet even if MAP fails.
Also, based on the fact that HA has encapsulated a packet with a routing header containing MAP's address, the MN realizes that the MAP has failed. Note that even if a mobile node uses multiple MAPs, this scheme provides a way for identifying the MAP
that has failed. It can then recover by either using a different MAP, if present, or by reverting to base mobile IP.
FIG. 4 is a flow chart of an embodiment of the operation of a Mobile Node in accordance with the present invention. Following start block 402, the Mobile Node performs Agent Discovery at block 404, during which the Home Agent, Access Routers (Foreign Agents) and Mobility Anchor Points are discovered. The Mobile Node then registers its current network location with the Foreign Agent if there is one and Access Router at block 406. At block 408, the Mobile Node sends the MAP Addr to any correspondent nodes as its CoA. At block 410, the Mobile Node sends its current network location address (CMN Addr) to the Home Agent. The CMN Addr is also sent to the Mobility Anchor Point at block 412. At this, point in the process, normal network operation can proceed, with information flowing between the Mobile Node and the Correspondent Nodes via the Mobility Anchor Point. As the Mobile node roams, it may become necessary to perform a hand-off to a new Access Router. At block 414 a check is made to determine if hand-off to a new router is required. If a hand-off is required, as depicted by the positive branch from decision block 414, flow returns to block 410, and the new CMN Addr is sent to the Home Agent and to the Mobility Anchor Point. If a hand-off is not required, as depicted by the negative branch from decision block 414, flow continues to decision block 416, where a check is made to determine if the Mobility Anchor Point has failed.
The failure can be detected rapidly, as described above, since information packets will be received via the Home Agent rather than via the MAP. If the MAP has failed, as indicated by the positive branch from decision block 416, a recovery process is performed at block 418, where a new MAP is selected or the process reverts to a standard Mobile IP. If the MAP has not failed, as indicated by the negative branch from decision block 416, flow continues to decision block 420. If the session is not terminated, normal operation continues and, as indicated by the negative branch from decision block 420, flow returns to block 414. Otherwise, the session ends at termination block 422.
FIG. 5 is a flow chart of an embodiment of the operation of a network in accordance with the present invention. Following start block 502, an information packet in the network from a correspondent node passes through a number of routers until it reaches the router before the Mobility Anchor Point (MAP). At block 504, this router receives the information packet. At block 506, the router tries to send the packet to MAP, as specified in the packet header. (Each correspondent node has the MAP Addr as the CoA for the Mobile node.) At decision block 508, a check is made to determine if the packet has been received successfully by the MAP. If it has been received, as depicted by the positive branch from decision block 508, the MAP
sends the packet to the Access Router (possibly via additional routers). (The MAP
has the CMN Addr as the CoA for the Mobile node). Finally, the packet is received by the Access Router and intercepted by the Mobile node at block 512. However, if the router is unsuccessful in sending the packet to the MAP, as depicted by the negative branch from decision block 508, the router instead sends the packet to the next address in the header at block 516. The next address is the address of the home network. At block 518, the home agent intercepts the packet on the home network.
At block 520 the Home Agent encapsulates the packet and, at block 522, sends the packet to the Mobile Node using the CMN Addr. The process is completed at block 524.
An advantage of the present invention is that it does not require any non-standard enhancement in the CN or the HA. Additionally, it achieves a balance between a pure end-to-end approach and a pure network-based approach. Note that for a pure end-to-end approach, only the changes described with reference to FIG. 4 above need to be implemented. In that case, the CNs will get a 'destination unreachable' ICMP message and will delete the binding as per the standard protocol.
They will then send packets to the home address directly. The home agent, which has the "real CoA", can then tunnel the packet to the mobile node. This enables the connection to be maintained. The mobile node can still recognize the failure of the MAP as follows: when the mobile node gets a packet tunneled by the home agent and originally sent by a correspondent in its binding update list, the mobile can verify if the MAP is functional.
Those of ordinary skill in the art will recognize that although the present invention has been described in terms of exemplary embodiments based upon a modification to a Hierarchical Mobile IP network, the method can be applied to a variety of IP based wireless infrastructures, including 3G cellular systems and CGISS
wideband networks.
While the invention has been described in conjunction with specific embodiments, it is evident that many alternatives, modifications, permutations and variations will become apparent to those of ordinary skill in the art in light of the foregoing description. Accordingly, it is intended that the present invention embrace all such alternatives, modifications and variations as fall within the scope of the appended claims.
MANAGEMENT IN A MOBILE NETWORK
TECHNICAL FIELD
This invention relates to local mobility management techniques for mobile networks and, in particular, to a method and apparatus for recovering from failure of local mobility management.
BACKGROUND OF THE INVENTION
As the number of wireless devices for voice or data increases, mobile data communication will likely emerge as the technology supporting most communication including voice and video. Mobile data communication will be pervasive in cellular systems such as 3G and in wireless LAN such as 802.11, and will extend into satellite communication.
In IP (Internet Protocol) networks, routing is based on stationary IP
addresses, similar to how a postal letter is delivered to the fixed address on the envelope. A
device on a network is reachable through normal IP routing by the IP address it is assigned on the network.
When a device roams away from its home network it is no longer reachable using normal IP routing. This results in the active sessions of the device being terminated. Mobile protocols (such as the Hierarchical Mobile Internet protocol (HMIP v4 and v6) or the Mobile IP defined by the Internet Engineering Task Force (IETF) RFC 2002) were created to enable users to keep the same IP address while traveling to a different network (which may even be on a different wireless system), thus ensuring that a roaming individual could continue communication without sessions or connections being dropped. When the mobility functions of mobile protocols are performed at the network layer rather than the physical layer, the mobile device can span different types of wireless and wire-line networks while maintaining connections and ongoing applications. In some applications, such as remote login, remote printing, and file transfers, it is undesirable to interrupt communications while an individual roams across network boundaries. Also, certain network services, such as software licenses and access privileges, are based on IP addresses.
Changing these IP addresses could compromise the network services.
The concept of local mobility management is well known in the cellular and IP domains. For instance, in a mobile IP network, the concept of a mobility anchor point (MAP) is defined to support fast mobility. A MAP is a node that enhances handoff performance by acting as a care-of-address (CoA) of the mobile node.
Specifically, the mobile node registers the address in the network of the MAP
with its home agent and its correspondent nodes and registers its "real CoA" with the MAP.
As long as the'MAP is not changed, a mobile node need not update its home agent and correspondent nodes. However, if the MAP fails or gets disconnected, the correspondent nodes cannot send packets to the mobile node and packets in transit will be lost. Additionally, it takes a significant amount of time to identify the problem and recover. Meanwhile, all packets sent will be lost.
SUMMARY OF THE INVENTION
According to one aspect of the invention, a method for robust mobility management in a network having a mobile node, a mobility anchor point, a correspondent node, a home agent and an access router and operating under a hierarchical protocol, is presented. The method comprises providing binding updates during agent discovery stage or whenever the mobile node is moving to a new access router, the updates including the mobile node sending an address belonging to the mobility anchor point to the correspondent node, the mobile node sending an address of the mobile node on a network of the access router to the home agent, the mobile node sending the address of the mobile node on the network of the access router to the mobility anchor point, and detecting failure of the mobility anchor point comprising the correspondent node attempting to transmit an information packet to the mobility anchor point, the correspondent node continuously monitoring packets for determining if an information packet is successfully transmitted to the mobility anchor point, and if the information packet is not successfully transmitted to the mobility anchor point deleting binding updates, passing the information packet to the home agent, and the home agent encapsulating the information packet for transmission to the mobile node.
BRIEF DESCRIPTION OF THE DRAWINGS
The features of the invention believed to be novel are set forth with particularity in the appended claims. The invention itself however, both as to organization and method of operation, together with objects and advantages thereof, may be best understood by reference to the following detailed description of the invention, which describes certain exemplary embodiments of the invention, taken in conjunction with the accompanying drawings in which:
FIG. 1 is a diagrammatic representation of binding updates according to the invention, in an exemplary network.
FIG. 2 is a diagrammatic representation of information flow in a network in accordance with the present invention in normal operation.
FIG. 3 is a diagrammatic representation of information flow in a network in accordance with the present invention when the MAP fails.
FIG. 4 is a flow chart of an embodiment of the method of the present invention.
FIG. 5 is a further flow chart of an embodiment of the method of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
While this invention is susceptible of embodiment in many different forms;
there is shown in the drawings and will herein be described in detail specific embodiments, with the understanding that the present disclosure is to be considered as an example of the principles of the invention and not intended to limit the invention to the specific embodiments shown and described. In the description below, like reference numerals are used to describe the same, similar or corresponding parts in the several views of the drawings.
When a network device is capable of roaming away from its home network it is called a Mobile Node (MN). A Mobile Node is a device such as a cell phone, personal digital assistant, automobile computer or portable computer whose software enables network roaming capabilities.
A Correspondent Node (CN) is a device on the network with which the Mobile Node is in communication.
A Home Agent (HA) is a device on the home network, i.e. the network of the Mobile node when it is not roaming. The HA may serve as the default anchor point for communication with the Mobile Node, tunneling packets from a Correspondent Node to the roaming Mobile Node.
An Access Router (AR) or Foreign Agent (FA) is a router that may function as the point of attachment for the Mobile Node when it roams to a foreign network. It delivers information packets to the Mobile Node. Information packets from the CN
may be forwarded via the Home Agent or via the Mobility Anchor Point.
The care-of address (CoA) is the address that can be used to reach a Mobile Node when it is on a foreign network. The Home Agent maintains an association between the home IP address of the Mobile Node and its care-of address, which is the current location of the Mobile Node on the foreign or visited network.
Encapsulation is a protocol which allows information packets of a network A, including routing information, to be transmitted across an arbitrary network B
by encapsulating the packets of A within packets of B. Encapsulation may also be used to transport packets from one point in a network to another. This process is called Tunneling.
A routing header is an option in the IP header that enables a source to specify, in order, multiple addresses through which a packet must be routed before it reaches its final destination.
In standard Mobile IP, when a MN moves to a new location on the network, all of the Correspondent Nodes and the Home Agent are informed of the new CoA.
This generates an excess of communication and increases delay. An alternative approach is a Hierarchical Mobile Internet protocol (HMIP), in which information packets are routed to the MN via a Mobility Anchor Point (MAP). The HA and CNs are each provided with the address of the MAP or an address in the MAPs network which uniquely identifies the mobile node (henceforth denoted by MAP_Addr). In the latter case the MAP can intercept the packet on behalf of the Mobile Node.
In either case, the MAP receives the information packets and then forwards the information packets to the MN. When a MN moves to a new location on the network, only the MAP needs to be informed of the move. That is, only devices in the neighborhood of the MN need to be informed of the move. This provides a more efficient network. However, if the MAP fails then communication to all of the CNs is lost.
The method of the invention allows a mobile node to continue receiving packets even when the MAP fails. It also enables the mobile node to discover the problem quickly.
According to the method of the invention, the operation of the Mobile Node is 5 changed as shown in FIG. 1. FIG. 1 shows an exemplary network including a Mobile Node (MN), two Correspondent Nodes (CN1 and CN2), three Access Routers (AR1, AR2 and AR3), a Home Agent router (HA) and a Mobility Anchor Point (MAP). Also shown are two intermediate routers (R1 and R2) indicating that there may be several layers between the MAP and the ARs. Following the Agent Discovery stage, during which AR1 is identified as the current Access Router and MAP as the current Mobility Anchor Point, the Mobile Node registers its current location with the MAP and Home Agent. The mobile node sends a binding update (BU), with MAP Addr) as its CoA, only to the correspondent nodes (CN1 and CN2), shown as links 102 and 104 in FIG. 1. However, it gives its "real CoA" (i.e.
its actual address on the network of ARl, denoted by CMN-Addr) to the home agent via link 106. This is in contrast to prior schemes in which the MAP Addr was sent to the Home Agent. The CMN Addr is also sent to the MAP via link 108.
As the mobile node moves to a new access router and gets a new CMN Addr, it sends a BU to both the MAP and its Home Agent, with the CMN Addr as the CoA.
This is in contrast to prior schemes, where the Home Agent was aware only of the MAP Addr, and no update was needed when the mobile nodes moved to a new access router. Note that when the mobile node performs a handoff, it needs to receive packets seamlessly from the correspondent nodes. There is often very little real-time communication between the home agent and the mobile node - assuming that all correspondents support the binding update (BU) option. So, the roundtrip latency associated with sending a BU to the HA will not affect the performance of the current sessions between the mobile node and its correspondents.
The operation of the network is also changed according to the method of the invention. In normal operation, as shown in FIG. 2, information flows between the mobile node (MN) and the correspondent nodes (CN1 and CN2) via the Mobility Anchor Point (MAP). The information passes through the access router (ARl) and other routers (R1 and AR2).
When a router tries to send packets with a routing header to another node and finds that the node is unreachable, instead of dropping the packet, the router will process the packet's routing header. In other words, the router will send the packet to the next destination given in the routing header.
When the MAP fails or gets disconnected from the network, packets from the correspondent node CN2 will reach the last router (Rl) on the path to the MAP
that is still functional. That router then determines that the packet cannot be sent to the MAP
using the standard mechanisms (like routing table/neighbor discovery/ARP). It then processes the routing header and sends the packet to the next entry in the routing header. This entry is the home address of the mobile node. The router then sends the packet to the home network where the home agent HA intercepts the packet. This situation is shown in FIG. 3. The HA, which has the "real CoA" encapsulates the packet to the mobile node. Thus the MN receives the packet even if MAP fails.
Also, based on the fact that HA has encapsulated a packet with a routing header containing MAP's address, the MN realizes that the MAP has failed. Note that even if a mobile node uses multiple MAPs, this scheme provides a way for identifying the MAP
that has failed. It can then recover by either using a different MAP, if present, or by reverting to base mobile IP.
FIG. 4 is a flow chart of an embodiment of the operation of a Mobile Node in accordance with the present invention. Following start block 402, the Mobile Node performs Agent Discovery at block 404, during which the Home Agent, Access Routers (Foreign Agents) and Mobility Anchor Points are discovered. The Mobile Node then registers its current network location with the Foreign Agent if there is one and Access Router at block 406. At block 408, the Mobile Node sends the MAP Addr to any correspondent nodes as its CoA. At block 410, the Mobile Node sends its current network location address (CMN Addr) to the Home Agent. The CMN Addr is also sent to the Mobility Anchor Point at block 412. At this, point in the process, normal network operation can proceed, with information flowing between the Mobile Node and the Correspondent Nodes via the Mobility Anchor Point. As the Mobile node roams, it may become necessary to perform a hand-off to a new Access Router. At block 414 a check is made to determine if hand-off to a new router is required. If a hand-off is required, as depicted by the positive branch from decision block 414, flow returns to block 410, and the new CMN Addr is sent to the Home Agent and to the Mobility Anchor Point. If a hand-off is not required, as depicted by the negative branch from decision block 414, flow continues to decision block 416, where a check is made to determine if the Mobility Anchor Point has failed.
The failure can be detected rapidly, as described above, since information packets will be received via the Home Agent rather than via the MAP. If the MAP has failed, as indicated by the positive branch from decision block 416, a recovery process is performed at block 418, where a new MAP is selected or the process reverts to a standard Mobile IP. If the MAP has not failed, as indicated by the negative branch from decision block 416, flow continues to decision block 420. If the session is not terminated, normal operation continues and, as indicated by the negative branch from decision block 420, flow returns to block 414. Otherwise, the session ends at termination block 422.
FIG. 5 is a flow chart of an embodiment of the operation of a network in accordance with the present invention. Following start block 502, an information packet in the network from a correspondent node passes through a number of routers until it reaches the router before the Mobility Anchor Point (MAP). At block 504, this router receives the information packet. At block 506, the router tries to send the packet to MAP, as specified in the packet header. (Each correspondent node has the MAP Addr as the CoA for the Mobile node.) At decision block 508, a check is made to determine if the packet has been received successfully by the MAP. If it has been received, as depicted by the positive branch from decision block 508, the MAP
sends the packet to the Access Router (possibly via additional routers). (The MAP
has the CMN Addr as the CoA for the Mobile node). Finally, the packet is received by the Access Router and intercepted by the Mobile node at block 512. However, if the router is unsuccessful in sending the packet to the MAP, as depicted by the negative branch from decision block 508, the router instead sends the packet to the next address in the header at block 516. The next address is the address of the home network. At block 518, the home agent intercepts the packet on the home network.
At block 520 the Home Agent encapsulates the packet and, at block 522, sends the packet to the Mobile Node using the CMN Addr. The process is completed at block 524.
An advantage of the present invention is that it does not require any non-standard enhancement in the CN or the HA. Additionally, it achieves a balance between a pure end-to-end approach and a pure network-based approach. Note that for a pure end-to-end approach, only the changes described with reference to FIG. 4 above need to be implemented. In that case, the CNs will get a 'destination unreachable' ICMP message and will delete the binding as per the standard protocol.
They will then send packets to the home address directly. The home agent, which has the "real CoA", can then tunnel the packet to the mobile node. This enables the connection to be maintained. The mobile node can still recognize the failure of the MAP as follows: when the mobile node gets a packet tunneled by the home agent and originally sent by a correspondent in its binding update list, the mobile can verify if the MAP is functional.
Those of ordinary skill in the art will recognize that although the present invention has been described in terms of exemplary embodiments based upon a modification to a Hierarchical Mobile IP network, the method can be applied to a variety of IP based wireless infrastructures, including 3G cellular systems and CGISS
wideband networks.
While the invention has been described in conjunction with specific embodiments, it is evident that many alternatives, modifications, permutations and variations will become apparent to those of ordinary skill in the art in light of the foregoing description. Accordingly, it is intended that the present invention embrace all such alternatives, modifications and variations as fall within the scope of the appended claims.
Claims (4)
1. A method for robust mobility management in a network having a mobile node, an access router, a mobility anchor point, a correspondent node, and a home, operating under a hierarchical protocol, said method comprising:
receiving at an intermediate router an information packet, wherein the information packet is intended for transmission between the correspondent node and the mobile node via the mobility anchor point;
the intermediate router determining if the information packet is successfully transmitted to the mobility anchor point; and if the information packet is not successfully transmitted to the mobility anchor point, transmitting the information packet to a next address in a routing header in the information packet.
receiving at an intermediate router an information packet, wherein the information packet is intended for transmission between the correspondent node and the mobile node via the mobility anchor point;
the intermediate router determining if the information packet is successfully transmitted to the mobility anchor point; and if the information packet is not successfully transmitted to the mobility anchor point, transmitting the information packet to a next address in a routing header in the information packet.
2. A method in accordance with claim 1, wherein the next address is a home address of the mobile node.
3. A method in accordance with claim 2 further comprising the home agent intercepting and encapsulating the information packet and transmitting it to the mobile node.
4. A method in accordance with claim 3 further comprising the mobile node receiving a packet from the home agent and recovering from failure of the mobility anchor point.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US10/107,861 US8068494B2 (en) | 2002-03-27 | 2002-03-27 | Method and apparatus for robust local mobility management in a mobile network |
| US10/107,861 | 2002-03-27 | ||
| PCT/US2003/004491 WO2003084148A1 (en) | 2002-03-27 | 2003-02-14 | Method and apparatus for robust local mobility management in a mobile network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2477155A1 CA2477155A1 (en) | 2003-10-09 |
| CA2477155C true CA2477155C (en) | 2011-11-15 |
Family
ID=28452725
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2477155A Expired - Fee Related CA2477155C (en) | 2002-03-27 | 2003-02-14 | Method and apparatus for robust local mobility management in a mobile network |
Country Status (8)
| Country | Link |
|---|---|
| US (1) | US8068494B2 (en) |
| KR (1) | KR100780260B1 (en) |
| AU (1) | AU2003223176B2 (en) |
| CA (1) | CA2477155C (en) |
| GB (1) | GB2401758B (en) |
| HK (1) | HK1071649A1 (en) |
| NZ (1) | NZ535335A (en) |
| WO (1) | WO2003084148A1 (en) |
Families Citing this family (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7623497B2 (en) * | 2002-04-15 | 2009-11-24 | Qualcomm, Incorporated | Methods and apparatus for extending mobile IP |
| US7460547B2 (en) * | 2002-10-03 | 2008-12-02 | Cisco Technology, Inc. | Mobile director |
| JP3965382B2 (en) * | 2003-11-28 | 2007-08-29 | 松下電器産業株式会社 | Communication system and communication method |
| WO2006040619A1 (en) * | 2004-10-14 | 2006-04-20 | Telefonaktiebolaget L M Ericsson (Publ) | Updating quality of service reservation |
| US7529207B2 (en) | 2004-12-21 | 2009-05-05 | International Business Machines Corporation | Method of reestablishing communication by a mobile node upon recovery from an abrupt shut down |
| US7843871B2 (en) * | 2004-12-21 | 2010-11-30 | International Business Machines Corporation | Method of reestablishing communication by a mobile node upon recovery from an abrupt shut down |
| WO2006129863A1 (en) * | 2005-05-31 | 2006-12-07 | Matsushita Electric Industrial Co., Ltd. | Method and apparatus for controlling packet forwarding, and communication node |
| CN101204064A (en) * | 2005-05-31 | 2008-06-18 | 松下电器产业株式会社 | Method and apparatus for controlling packet forwarding |
| US7899456B2 (en) * | 2005-12-16 | 2011-03-01 | International Business Machines Corporation | Method for faster mobility handoff of a mobile node |
| KR100838095B1 (en) * | 2006-07-27 | 2008-06-13 | 경희대학교 산학협력단 | Mobile router for supporting network mobility of sensor network based on 6LoWPAN and zigbee network communicating with IPv6 node |
| KR100781678B1 (en) * | 2006-07-27 | 2007-12-03 | 경희대학교 산학협력단 | Mobile router for supporting the network mobility of sensor network based on 6lowpan |
| US20120087345A1 (en) * | 2006-10-25 | 2012-04-12 | Yan Wenjun | Method and system for handover between different types of access systems |
| CN101170808B (en) * | 2006-10-25 | 2011-03-30 | 华为技术有限公司 | Switching method and system for heterogenous access systems |
| US20080240116A1 (en) * | 2007-03-26 | 2008-10-02 | Motorola, Inc. | Method and Apparatus for Determining the Locating of Nodes in a Wireless Network |
| FR2917937B1 (en) * | 2007-06-25 | 2009-10-16 | Alcatel Lucent Sas | COMMUNICATION METHOD WITH INTERCEPTION OF CONTROL MESSAGES |
| US8675630B2 (en) * | 2008-05-22 | 2014-03-18 | Qualcomm Incorporated | Systems and methods for multiplexing multiple connections in mobile IP network |
| WO2011053330A1 (en) * | 2009-11-02 | 2011-05-05 | Hewlett-Packard Development Company, L.P. | Multiprocessing computing with distributed embedded switching |
| CN102447750A (en) * | 2010-10-13 | 2012-05-09 | 北京邮电大学 | Method for reducing location management signaling overhead in HMIPv6 (hierarchical mobile internet protocol version 6) network based on pointer chains |
| US8817707B2 (en) * | 2012-07-20 | 2014-08-26 | Intel Corporation | Mechanisms for roaming between 3GPP operators and WLAN service providers |
| US9949185B2 (en) * | 2015-10-08 | 2018-04-17 | At&T Intellectual Property I, L.P. | Facilitating mobile service anchor management |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3641128B2 (en) * | 1998-02-20 | 2005-04-20 | 株式会社東芝 | MOBILE COMPUTER DEVICE, MOBILE COMPUTER MANAGEMENT DEVICE, MOBILE COMPUTER MANAGEMENT METHOD, AND COMMUNICATION CONTROL METHOD |
| JP3581251B2 (en) * | 1998-06-16 | 2004-10-27 | 株式会社東芝 | Communication system, data packet transfer method, router device, and packet relay device |
| US6195705B1 (en) * | 1998-06-30 | 2001-02-27 | Cisco Technology, Inc. | Mobile IP mobility agent standby protocol |
| FI108832B (en) * | 1999-03-09 | 2002-03-28 | Nokia Corp | IP routing optimization in an access network |
| US6947401B2 (en) * | 2000-03-08 | 2005-09-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Hierarchical mobility management for wireless networks |
| DE50114963D1 (en) * | 2001-07-10 | 2009-08-13 | Nokia Siemens Networks Gmbh | METHOD FOR CARRYING OUT A QOS-ORIENTED HANDLE BETWEEN A FIRST AND A SECOND IP-BASED, ESPECIALLY MOBILE IPV6-BASED COMMUNICATION PATH BETWEEN A MOBILE NODE (MN) AND A CORRESPONDENT NODE (CN) |
| US7512120B2 (en) * | 2002-07-09 | 2009-03-31 | Ntt Docomo, Inc. | Node, correspondent node, mobility anchor point, and home agent in packet communication system, packet communication system, and path MTU discovery method |
| US7292565B2 (en) * | 2002-08-07 | 2007-11-06 | Fujitsu Limited | Communication method |
| KR100605984B1 (en) * | 2003-10-18 | 2006-07-28 | 삼성전자주식회사 | System and Method for discovering mobile anchor point and managing mobility of a mobile node in a network system |
-
2002
- 2002-03-27 US US10/107,861 patent/US8068494B2/en active Active
-
2003
- 2003-02-14 CA CA2477155A patent/CA2477155C/en not_active Expired - Fee Related
- 2003-02-14 KR KR1020047015363A patent/KR100780260B1/en active IP Right Grant
- 2003-02-14 AU AU2003223176A patent/AU2003223176B2/en not_active Ceased
- 2003-02-14 GB GB0419429A patent/GB2401758B/en not_active Expired - Fee Related
- 2003-02-14 WO PCT/US2003/004491 patent/WO2003084148A1/en active IP Right Grant
- 2003-02-14 NZ NZ535335A patent/NZ535335A/en not_active IP Right Cessation
-
2005
- 2005-05-14 HK HK05104079A patent/HK1071649A1/en not_active IP Right Cessation
Also Published As
| Publication number | Publication date |
|---|---|
| HK1071649A1 (en) | 2005-07-22 |
| US8068494B2 (en) | 2011-11-29 |
| AU2003223176B2 (en) | 2007-05-24 |
| GB2401758A (en) | 2004-11-17 |
| KR100780260B1 (en) | 2007-11-28 |
| GB2401758B (en) | 2006-04-12 |
| US20030185196A1 (en) | 2003-10-02 |
| AU2003223176A1 (en) | 2003-10-13 |
| NZ535335A (en) | 2007-04-27 |
| CA2477155A1 (en) | 2003-10-09 |
| KR20040094445A (en) | 2004-11-09 |
| GB0419429D0 (en) | 2004-10-06 |
| WO2003084148A1 (en) | 2003-10-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2477155C (en) | Method and apparatus for robust local mobility management in a mobile network | |
| US7633898B2 (en) | Mobile IP addressing | |
| FI108983B (en) | Lapsed by a mobility agent in an access network | |
| EP1329124B1 (en) | Seamless handoff in mobile ip | |
| US7751379B2 (en) | IP mobility mechanism for a packet radio network | |
| US9516495B2 (en) | Apparatus and methods of PMIPv6 route optimization protocol | |
| US7277708B2 (en) | Router and mobile communication terminal for mobile communication network | |
| US20120063428A1 (en) | Interface Switching System, Mobile Node, Proxy Node, and Mobile Management Node | |
| US20030193952A1 (en) | Mobile node handoff methods and apparatus | |
| US20090239531A1 (en) | Policy for a Roaming Terminal Based on a Home Internet Protocol (IP) Address | |
| US20100290621A1 (en) | Tunneling support for mobile ip using a key for flow identification | |
| US8873507B2 (en) | Distributed local mobility anchors for achieving optimized mobility routing | |
| JP2004015143A (en) | Hand-over method in mobile communication system and router used for the mobile communication system | |
| US20100268804A1 (en) | Address allocation method, address allocation system, mobile node, and proxy node | |
| US20100296443A1 (en) | System, method and apparatus for route-optimized communication for a mobile node nested in a mobile network | |
| KR20050101693A (en) | Method for recovery routing path with damage in a mobile network | |
| US8649352B2 (en) | Packet forwarding methods for use in handoffs | |
| US8824353B2 (en) | Mobility route optimization in a network having distributed local mobility anchors | |
| JP2008541516A (en) | Communication method between IPv6 communicating node and mobile IPv6 node, and communicating node proxy gateway | |
| JP4934200B2 (en) | Mobility route optimization by network control for IP wireless base station architecture | |
| Sun et al. | Mobile IP applicability: When do we really need it? | |
| Lee et al. | A mobility scheme for personal and terminal mobility | |
| JP2010541302A (en) | System, method and apparatus for mobile node nested in mobile network to perform optimal route communication | |
| Ma et al. | Role of mobile IPv6 for mobile networks and its remaining issues | |
| Stoica | A Review on Mobile IP Connectivity and its QoS |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |
Effective date: 20210831 |
|
| MKLA | Lapsed |
Effective date: 20200214 |