Method and Apparatus for Mobility Agent Recovery

• US 20110202671A1
• Filed: 04/21/2011
• Published: 08/18/2011
• Est. Priority Date: 03/26/2008
• Status: Active Grant

• Current Assignee: Chandramouli Balasubramanian, Janaradan Ramesh, Vamsidhar Valluri, Venkatesan Pradeep
• Original Assignee: Chandramouli Balasubramanian, Janaradan Ramesh, Vamsidhar Valluri, Venkatesan Pradeep
• Inventors: Pradeep, Venkatesan, Valluri, Vamsidhar, Balasubramanian, Chandramouli, Ramesh, Janaradan
• Granted Patent: US 8,239,555 B2
• Time in Patent Office: Days
• US Class Current: 709/229
• CPC Class Codes: H04W 8/12 between location registers or mobility servers
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]

Abstract

Techniques for recovering Mobile Internet Protocol (IP) session(s) of a mobility agent in a Mobile IP network are described herein. In one embodiment of the invention, for each mobility session associated with a mobility agent, the mobility agent distributively backs up mobility agent specific information to the mobility agent peer associated with that mobility session. The mobility agent specific information is not used by the mobility agent peer. Upon the mobility agent inadvertently losing at least one mobility session, the mobility agent recovers the stored mobility agent specific information associated with those sessions from the mobility agent peers respectively associated with those sessions. Other methods and apparatuses are also described.

Claims

1. A mobility agent in a Mobile IP network that provides Mobile IP services to one or more mobile nodes, comprising:

a packet processing module to process Mobile IP packets received at the mobility agent and transmitted by the mobility agent;

a security module coupled with the packet processing module to perform authentication, authorization, and accounting services;

one or more mobility agent to mobility agent capabilities modules coupled with the packet processing module, wherein each capability module is a particular set of one or more operations that is to provide functionality of an application feature between one mobility agent with another mobility agent;

a Mobile IP data structure coupled with the packet processing module and at least some of the mobility agent to mobility agent capabilities modules, the Mobile IP data structure including,

a local mobility agent Mobile IP structure to store a record with Mobile IP information for each mobile node the mobility agent is providing Mobile IP service to, the Mobile IP information is specific to the mobility agent, and

a remote mobility agent Mobile IP structure to store remote mobility agent specific information, wherein the remote mobility agent specific information is unrelated to the mobility agent providing Mobile IP services to the one or more mobile nodes;

a static peer structure to store indication of one or more static mobility agent peers of the mobility agent; and

a remote mobility agent configuration structure including,

a supported remote mobility agents capabilities structure to indicate capabilities of remote mobility agents, and

a remote mobility agents type structure to indicate a type of each remote mobility agent.

2. The mobility agent of claim 1, further comprising,

a mobility agent to mobility agent capabilities module coupled with the packet processing module and the remote mobility agent configuration structure, the mobility agent to mobility agent capabilities module to negotiate a set of one or more capabilities with one or more remote mobility agents, and to cause an indication of the negotiated capabilities to be stored in the remote mobility agent configuration structure.

3. The mobility agent of claim 2, wherein at least one of the mobility agent to mobility agent capabilities modules is to provide functionality of a Mobile IP session recover application, wherein the mobility agent is to transfer mobility agent specific information stored in the local mobility agent Mobile IP structure to one or more mobility agent peers that also support the Mobile IP session recover application as indicated by the supported remote mobility agent capabilities structure.

4. The mobility agent of claim 3, wherein if the information in the local mobility agent Mobile IP structure inadvertently is lost, the Mobile IP session recover application to request, from at least some of the one or more static mobility agent peers indicated in the static peer structure, mobility agent specific information to reconstruct the local mobility agent Mobile IP structure.

5. The mobility agent of claim 4, wherein prior to the request, the mobility agent to mobility agent capabilities negotiation module to renegotiate a set of one or more capabilities with at least the one or more static mobility agent peers indicated in the static peer structure, wherein one of the one or more capabilities negotiated includes the Mobile IP session recover application, and wherein the request is made to at least ones of the one or more static mobility agent peers that support the Mobile IP session recover application.

6. The mobility agent of claim 3, wherein at least one of the mobility agent to mobility agent capabilities modules is to provide functionality of a hello protocol application, wherein the mobility agent is to periodically transmit and receive hello messages from remote mobility agent peers that also support the hello protocol application, wherein if the mobility agent restarts and the information in the local mobility agent Mobile IP structure is lost, the mobility agent is to receive a hello message from a remote mobility agent peer that is not indicated in the static peer structure and request from that remote mobility agent peer mobility agent specific information to reconstruct the local mobility agent Mobile IP structure.