Mobile networking system and method

• US 20060123079A1
• Filed: 10/19/2005
• Published: 06/08/2006
• Est. Priority Date: 09/12/2001
• Status: Active Grant

• Current Assignee: Netmotion Wireless Holdings, Inc. (NetMotion Software, Inc.)
• Original Assignee: Netmotion Wireless Incorporated
• Inventors: Olson, Erik, Sturniolo, Emil A., Patashnik, Eli, Savarese, Joseph T.
• Granted Patent: US 7,644,171 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/167 Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 translation of Internet protocol [IP] addresses H04L61/2503
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04W 36/08 Reselecting an access point
• CPC Class Codes: H04W 8/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
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]
• CPC Class Codes: H04W 80/045 involving different protocol versions, e.g. MIPv4 and MIPv6
• CPC Class Codes: H04W 80/10 adapted for application session management, e.g. SIP [Session Initiation Protocol] connection management H04W76/00; arrangements for session management H04L67/14
• CPC Class Codes: H04W 88/182 Network node acting on behalf of an other network entity, e.g. proxy

Abstract

A seamless solution transparently addresses the characteristics of nomadic systems, and enables existing network applications to run reliably in mobile environments. A Mobility Management Server coupled to the mobile network maintains the state of each of any number of Mobile End Systems and handles the complex session management required to maintain persistent connections to the network and to other peer processes. If a Mobile End System becomes unreachable, suspends, or changes network address (e.g., due to roaming from one network interconnect to another), the Mobility Management Server maintains the connection to the associated peer task—allowing the Mobile End System to maintain a continuous connection even though it may temporarily lose contact with its network medium. An interface-based listener uses network point of attachment information supplied by a network interface to determine roaming conditions and to efficiently reestablish connection upon roaming. The Mobility Management Server can distribute lists to Mobile End Systems specifying how to contact it over disjoint networks. Architectures are provided for bridging between IPv4 and IPv6 Internet Protocols.

Claims

1. A method of communicating Internet Protocol data between first and second devices, comprising:

(a) communicating Internet Protocol data of a predetermined version IPvX between said first device and a further device;

(b) communicating Internet Protocol data of a predetermined version IPvY between said second device and said further device, where X does not equal Y; and

(c) using functionality provided at least in part at said further device to bridge said first device communications with said second device communications.

2. The method of claim 1 wherein X=4 and Y=5.

3. The method of claim 1 wherein said step (c) comprises proxying said first device communications.

4. The method of claim 1 wherein said first device has an IPvX stack but not an IPvY stack.

5. The method of claim 1 wherein said first device has an IPvY stack but not an IPvX stack.

6. The method of claim 1 wherein said first device has both an IPvX stack and an IPvY stack.

7. The method of claim 1 wherein said first device includes an application level proxy.

8. The method of claim 1 wherein said first device includes an IPvX sockets interface and an IPvY sockets interface.

10. A system for communicating Internet Protocol data comprising:

a first device that communicates Internet Protocol data of a predetermined version IPvX with a bridging device;

a second device that communicates Internet Protocol data of a predetermined version IPvY between said second device and said bridging device, where X does not equal Y; and

a facility within the bridging device that bridges said first device communications with said second device communications.

wherein said first device does not have an IPvY protocol stack and said second device does not have an IPvX protocol stack.