SYSTEM AND METHOD TO PRESERVE DIALOGS IN CLUSTERED ENVIRONMENTS IN CASE OF NODE FAILURE

• US 20120259986A1
• Filed: 04/05/2012
• Published: 10/11/2012
• Est. Priority Date: 04/05/2011
• Status: Abandoned Application

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Research In Motion Limited (Blackberry Limited)
• Inventors: Rozinov, Boris, John Chuan, Mee Tchin Jane, Kramarenko, Valentina Iqorevna, Pang, Swee Tuan
• Application Number:
  US13/440,109
• Publication Number:
  US 20120259986A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 2101/30 Types of network names
• CPC Class Codes: H04L 2101/385 Uniform resource identifier for session initiation protocol [SIP URI]
• CPC Class Codes: H04L 61/2575 using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
• CPC Class Codes: H04L 61/4535 using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/108 when the policy decisions are valid for a limited amount of time
• CPC Class Codes: H04L 63/1458 Denial of Service
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/143 Termination or inactivation of sessions, e.g. event-controlled end of session
• CPC Class Codes: H04L 67/147 Signalling methods or messages providing extensions to protocols defined by standardisation

Abstract

The present disclosure provides a system and method to preserve dialogs in clustered environments in case of node failure. In accordance with one embodiment, there is provided a method for performing a transaction call between an originating device and a terminating device, comprising: receiving, by a originating proxy server in a first cluster, a SIP message from the originating device over a first connection; and sending, by the originating proxy server, the SIP message to a routing proxy server in a second server cluster.

Claims

1. A method for performing a transaction call between an originating device and a terminating device, comprising:

receiving, by an originating proxy server in a first server cluster, a SIP message from the originating device over a first connection; and

sending, by the originating proxy server, the SIP message to a routing proxy server in a second server cluster.

2. The method of claim 1, further comprising:

sending, by the routing proxy server, the SIP message to a terminating proxy server in the second server cluster; and

sending, by the terminating proxy server, the SIP message to the terminating device.

3. The method of claim 1, wherein the first server cluster maintains a binding for the originating device, and wherein the second server cluster maintains a binding for the terminating device.

4. The method of claim 1, wherein the second server cluster is determined using an address-of-record (AOR) of the terminating device.

5. The method of claim 1, further comprising:

modifying, by the originating proxy server, the SIP message to include a first Record-Route header with a cluster address of the originating proxy server which maintains a binding for the originating device, a second Record-Route header with an address-of-record (AOR) associated with the originating device, and a Route header with an address of the routing proxy server.

6. The method of claim 5, wherein the originating proxy server retrieves the AOR associated with the first persistent connection of the originating device from internal storage.

7. The method of claim 5, wherein the cluster address is determined using the AOR of the terminating device.

8. The method of claim 5, further comprising:

sending, by the originating proxy server, the modified SIP message to each routing proxy server having a binding associated with the AOR of the terminating device.

9. The method of claim 5, further comprising:

removing, by the routing proxy server, the Route header;

modifying, by the routing proxy server, the SIP message to include a first Route header with an address of a terminating proxy server and a second Route header with the AOR of the terminating device;

retrieving, by the routing proxy server, binding information for the AOR of the terminating device; and

sending the modified SIP message to the terminating proxy server.

10. The method of claim 9, further comprising:

removing, by the terminating proxy server, the first Route header and second Route header; and

sending the modified SIP message to the terminating device.

11. The method of claim 10, further comprising:

modifying, by the terminating proxy server, the SIP message to include a third new Record-Route header with an address of a SIP network in which the first cluster and second cluster reside.

12. The method of claim 10, further comprising:

sending, by the terminating device, a 200OK message to the terminating proxy server when the SIP message is successfully processed by the terminating device, the 200OK message including a Contact header, the first Record-Route header, second Record-Route header and third Record-Route header;

removing, by the terminating proxy server, the first Record-Route header, second Record-Route header and third Record-Route header;

modifying, by the terminating proxy server, the 200OK message to include a first Record-Route header with the AOR of the terminating device and a second Record-Route header with an address of a routing proxy server; and

sending, by the terminating proxy server, the modified 200OK message to the routing proxy server.

13. The method of claim 12, further comprising:

sending, by the routing proxy server, the modified 200OK message to the originating proxy server;

further modifying, by the originating proxy server, the modified 200OK message to include a Record-Route header with a cluster address of the terminating proxy server which maintains a binding for the terminating device; and

sending, by the originating proxy server, the modified 200OK message to the originating device.

14. The method of claim 1, wherein the SIP message is an SIP INVITE request.

15. A network component, comprising:

a processor configured to;

receive, by a originating proxy server in a first server cluster, a SIP message from an originating device over a first connection; and

send, by the originating proxy server, the SIP message to a routing proxy server in a second server cluster.

16. The network component of claim 15, wherein the processor is configured to:

send, by the routing proxy server, the SIP message to a terminating proxy server in the second server cluster; and

send, by the terminating proxy server, the SIP message to a terminating device.

17. The network component of claim 15, wherein the first server cluster maintains a binding for the originating device, and wherein the second server cluster maintains a binding for a terminating device.

18. The network component of claim 15, wherein the second server cluster is determined using an address-of-record (AOR) of a terminating device.

19. The network component of claim 15, wherein the processor is configured to:

modify, by the originating proxy server, the SIP message to include a first Record-Route header with a cluster address of the originating proxy server which maintains a binding for the originating device, a second Record-Route header with an AOR associated with the originating device, and a Route header with an address of the routing proxy server.

20. The network component of claim 19, wherein the processor is configured to:

remove, by the routing proxy server, the Route header;

modify, by the routing proxy server, the SIP message to include a first Route header with an address of a terminating proxy server and a second Route header with the AOR of a terminating device;

retrieve, by the routing proxy server, binding information for the AOR of the terminating device;

send the modified SIP message to the terminating proxy server.