Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Ensuring Infallible Connectivity in Private Networks

IP.com Disclosure Number: IPCOM000167981D
Original Publication Date: 2008-Feb-26
Included in the Prior Art Database: 2008-Feb-26
Document File: 2 page(s) / 43K

Publishing Venue



Disclosed is a method to ensure infallible connectivity in private networks. Most companies today have created their own Virtual Private Networks (VPN's) in order to accommodate remote offices and remotely working employees. The remote computer uses VPN software, such as the AT&T* client to establish a secure connection with the private office network. The user expects connectivity round the clock even when mobile. The proposed method will make it possible to dynamically failover the network connectivity in such a manner that the end user does not get disconnected when moving between mobile networks.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

Ensuring Infallible Connectivity in Private Networks

Disclosed is a method to ensure infallible connectivity in private networks.

In this scenario, the IP addresses are usually dynamic with the DHCP server distributing IP addresses. The system's IP generally changes each time the client re-connects or when he moves from one wireless region to another. If the VPN uses TCP (VPN over SSL), the VPN software uses TCP/IP to maintain the connection and data transfer between the VPN client and the host. Therefore if the client is connected to his VPN on wireless and shifts his location, his system's IP also changes, resulting in the termination of the already established VPN connection using the old IP. This results in:

Loss of all connections that were established over the VPN client to the private network.

Additional overhead of having to reconnect to the VPN after having got the new IP.

Proposed Solution

The idea described in this solution provides the following method:
Instead of TCP over IP, the VPN software can internally use SCTP (Stream Control Transmission Protocol) over IP which is capable of associating multiple IP's with a connection and handle the IP address changes gracefully.

SCTP can handle Multi-homed endpoints. An SCTP endpoint is considered multi-homed if there are more than one transport addresses(IP Address) can be used to reach that endpoint.

Therefore when the IP changes when the client moves from Area1 to Area2, S...