CLUSTERED SESSION MANAGEMENT

• US 20140115176A1
• Filed: 10/18/2013
• Published: 04/24/2014
• Est. Priority Date: 10/22/2012
• Status: Abandoned Application

• Current Assignee: Vesta Solutions, Inc. (Motorola Solutions, Inc.)
• Original Assignee: Cassidian Communications Incorporated (European Aeronautic Defence and Space Company EADS NV)
• Inventors: Kamboh, Ameel, Wellonen, Jason, Stelzig, James
• Application Number:
  US14/058,049
• Publication Number:
  US 20140115176A1
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• 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: H04M 2242/04 for emergency applications
• CPC Class Codes: H04M 3/5116 for emergency applications

Abstract

Systems and methods for emergency call-center session routing in an all-active cluster formation are provided. Each node in a cluster receives sessions through load balanced distribution. Nodes in the cluster may be configured to use a common database. The database is synchronized across the cluster ensuring that data is accessible by any node in the cluster. Session state is maintained in the database, such that any session can be managed by any node in the cluster.

Claims

1. A system comprising:

a first node and a second node, the first node and the second node configured to receive and maintain communication session information, the first node and the second node executing on at least one session management server;

a distributed database, wherein the first node and the second node include an instance of the distributed database, the distributed database configured to store at least one characteristic of the first node and at least one characteristic of the second node;

a session load balancing server configured to;

receive a communication session;

identify one of the first node or the second node to receive the communication session based at least in part on a policy and the at least one characteristic for the first node and the at least one characteristic of the second node; and

produce an indicator indicative of the communication session and the identified node, wherein the identified node is configured to obtain the communication session from the distributed database.

2. The system of claim 1, wherein the communication session information includes a session state, a session identifier, and a current node.

3. The system of claim 1, wherein the characteristic of the first node and the second node includes one or more of a number of answering points coupled to the node, a number of communication sessions handled over a unit of time, a node load, or a node session volume.

4. The system of claim 1, further comprising a cluster management server configured to monitor the first node and the second node, and

wherein upon failure of one of the first node or the second node, the cluster management server is configured to update one or more communication session information entries in the distributed database associated with the failed node, the entries to be associated with an active node, the active node configured to reconstruct the communication session based at least in part on the communication session information.

5. The system of claim 4, wherein the update is based on at least in part on the policy and the at least one characteristic of the active node.

6. The system of claim 4, wherein the cluster management server is configured to:

generate a re-invite message based on the communication session information; and

transmit the re-invite message to the active node.

7. The system of claim 4, wherein the cluster management server is configured to:

receive a registration request from a third node, the registration request including a node configuration and a node state; and

store the registration request in the distributed database, wherein the session load balancer is configured to identify one of the first node, the second node, or the third node to receive the communication session.

8. The system of claim 1, wherein the communication session is a session initiation protocol communication session.

9. The system of claim 1, wherein the first node is associated with a first answering point and the second node is associated with a second answering point.

10. The system of claim 1, wherein the policy includes a threshold value for a node characteristic, and wherein a node is identified based on a comparison of a value for the characteristic of the node with the threshold value.

11. A method of managing communication sessions, the method comprising:

registering a first node and a second node;

obtaining at least one characteristic of the first node and at least one characteristic of the second node;

receiving a communication session;

identifying one of the first node or the second node to receive the communication session based at least in part on a policy and the at least one characteristic of the first node and the at least one characteristic of the second node; and

providing communication session information to the identified node.

12. The method of claim 11, wherein the communication session information includes a session state, a session identifier, and a current node.

13. The method of claim 11, wherein the characteristic of the first node and the second node includes one or more of a number of answering points coupled to the node, a number of communication sessions handled over a unit of time, a node load, or a node session volume.

14. The method of claim 11, further comprising:

upon failure of one of the first node or the second node, updating one or more communication session information entries in the distributed database associated with the failed node, the entries to be associated with an active node, the active node configured to reconstruct the communication session based at least in part on the communication session information.

15. The method of claim 14, wherein said updating is based on at least in part on the policy and the at least one characteristic of the active node.

16. The method of claim 14, further comprising:

generating a re-invite message based on the communication session information; and

transmitting the re-invite message to the active node.

17. The method of claim 14, further comprising:

receiving a registration request from a third node, the registration request including a node configuration and a node state; and

storing the registration request in the distributed database, wherein said identifying includes identifying one of the first node, the second node, or the third node to receive the communication session.

18. The method of claim 11, wherein the communication session is a session initiation protocol communication session.

19. The method of claim 11, wherein the first node is associated with a first answering point and the second node is associated with a second answering point.

20. A computer readable storage medium comprising instructions, said instructions, upon execution by a processor of a device, causing the device to:

register a first node and a second node;

obtain at least one characteristic of the first node and at least one characteristic of the second node;

receive a communication session;

identify one of the first node or the second node to receive the communication session based at least in part on a policy and the at least one characteristic for the first node and the at least one characteristic of the second node; and

provide communication session information to the identified node.

21. A system comprising:

means for receiving and maintaining communication session information;

means for distributed storage of at least one characteristic of the means for receiving and maintaining communication session information;

means for session load balancing configured to;

receive a communication session;

identify said means for receiving and maintaining communication session information to receive the communication session based at least in part on a policy and the at least one characteristic; and

produce an indicator indicative of the communication session and the identified means for receiving and maintaining communication session information, wherein the identified means for receiving and maintaining communication session information is configured to obtain the communication session from said means for distributed storage.