Socket extensions for redundancy

• US 6,938,179 B2
• Filed: 11/01/2002
• Issued: 08/30/2005
• Est. Priority Date: 11/01/2002
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Iyer, Sreeram P., Mahamuni, Atul
• Primary Examiner(s): Beausoliel, Robert
• Assistant Examiner(s): PUENTE, EMERSON C
• Application Number:
  US10/286,350
• Publication Number:
  US 20040088418A1
• Time in Patent Office: 1,033 Days
• Field of Search: 714/4, 709/227, 709237-238
• US Class Current: 714/4.4
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/586 of virtual routers
• 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/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• 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 80/06 Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless transmission control protocol/Internet protocol [TCP/IP] or user datagram protocol [UDP] H04L69/16

Abstract

A standard socket interface is provided to implement socket redundancy. The interface includes socket options to create redundant sockets, obtain the status of redundant sockets, as well as providing error information relating to redundant sockets. A redundant socket may be created on a standby side that becomes active should the active side fail. The standby socket is associated with the active side socket. When an active side fails that has a redundant socket created, the standby side socket seamlessly takes over the sockets operations.

Claims

1. A method for socket redundancy, comprising:

opening a primary socket;

requesting a redundant socket to be opened through a socket layer associated with the primary socket and a socket layer associated with the redundant socket;

associating the primary socket with the redundant socket and sending a message to the redundant socket that includes a unique identifier that is associated with the primary socket and the redundant socket;

determining when the primary socket fails; and

when, making the redundant socket the primary socket.

2. The method of claim 1, further comprising sending an acknowledgement message in response to the request to open the redundant socket.

3. A method for socket redundancy, comprising:

opening a primary socket;

requesting a redundant socket to be opened through a socket layer associated with the primary socket and a socket layer associated with the redundancy socket;

associating the primary socket with the redundant socket and sending an application associated with the redundant socket a cookie;

determining when the primary socket fails; and

when, making the redundant socket the primary socket.

4. The method of claim 3, further comprising associating the cookie with the redundant socket.

5. The method of claim 4, further comprising providing a standard socket interface for an application.

6. The method of claim 5, wherein the standard socket interface further comprises providing a redundant socket state and an option to make the socket redundant.

7. A system for socket redundancy that provides a standard socket interface, comprising:

an active node configured to open a primary socket, request that a redundant socket is opened, and associate the primary socket with the redundant socket; and

a standby node configured to open the redundant socket and associate the redundant socket with the primary socket, wherein the redundant socket is configured to seamlessly act as the primary socket when the primary socket fails;

the active node and the standby node comprising an application, a socket library, and a socket layer, wherein the socket layer for the active node is configured to request that the redundant socket be opened on the standby node and the socket layer for the active node and the socket layer for the standby node are configured to send a message relating to the creation of the redundant socket;

wherein the message further comprises a cookie that uniquely identifies the socket.

8. The system of claim 7, wherein the redundant socket and the primary socket are associated with the cookie.

9. The system of claim 8, wherein the standby node is further configured to send an acknowledgement message to the active node in response to the request to open a redundant socket.

10. The system of claim 9, wherein the acknowledgement message is sent by the redundant socket layer to the primary socket layer.