Emergency services routing proxy cluster management

• US 10,212,282 B2
• Filed: 09/25/2017
• Issued: 02/19/2019
• Est. Priority Date: 02/07/2014
• Status: Active Grant

• Current Assignee: Motorola Solutions Connectivity Incorporated (Motorola Solutions, Inc.)
• Original Assignee: Vesta Solutions, Inc. (Motorola Solutions, Inc.)
• Inventors: Kamboh, Ameel, Wellonen, Jason
• Primary Examiner(s): El-Zoobi, Maria
• Application Number:
  US15/714,678
• Publication Number:
  US 20180027115A1
• Time in Patent Office: 512 Days
• Field of Search: 379 37- 52
• CPC Class Codes: H04L 12/1895 for short real-time information, e.g. alarms, notifications, alerts, updates
• CPC Class Codes: H04L 2101/385 Uniform resource identifier for session initiation protocol [SIP URI]
• CPC Class Codes: H04L 41/0661 by reconfiguring faulty entities
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 45/3065 for real time traffic
• CPC Class Codes: H04L 45/46 Cluster building
• CPC Class Codes: H04L 47/2416 Real-time traffic
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• 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/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04M 11/04 with alarm systems, e.g. fire, police or burglar alarm systems
• CPC Class Codes: H04M 3/5116 : for emergency applications
• CPC Class Codes: H04M 7/0075 : Details of addressing, directories or routing tables
• CPC Class Codes: H04W 4/90 : Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 76/50 : for emergency connections

Abstract

Systems and methods for clustering emergency services routing proxies are provided. The described features allow a group of ESRPs running as individual servers or a group of virtual servers, to be referenced using a single URI. In one implementation, an emergency services routing proxy device includes an emergency services routing proxy node configured to route a call to a downstream entity, the call received from an upstream entity. The device further includes a cluster manager configured to receive registration information from the emergency services routing proxy node, the registration information including a routing service identifier. The cluster manager may be further configured to identify the emergency services routing proxy node for call routing based on a comparison of an identifier included in the call with the routing service identifier.

Claims

1. A cluster management system comprising:

a computer-readable memory storing executable instructions; and

one or more computer processors in communication with the computer-readable memory, wherein the one or more computer processors are configured to execute the executable instructions to at least;

receive first registration information from a first emergency services routing proxy node, the first registration information including a routing service identifier for an emergency service provider;

receive second registration information from a second emergency services routing proxy node for an emergency service provider, the second registration information including the routing service identifier, wherein the first emergency services routing proxy node and the second emergency services routing proxy node are included in a clustered emergency services routing proxy managed by a cluster manager, and wherein the clustered emergency services routing proxy is configured to route a call received from an upstream entity to a downstream entity via one of the first emergency services routing proxy node or the second emergency services routing proxy node;

receive node status information from nodes included in the clustered emergency services routing proxy associated with the routing service identifier, the nodes including the first emergency services routing proxy node and the second emergency services routing proxy node;

generate a service status message for the clustered emergency services routing proxy based on;

(i) the received node status information for the nodes included in the clustered emergency services routing proxy associated with the routing service identifier, and (ii) a status policy; and

transmit the service status message to the upstream entity.

2. The system of claim 1, wherein the downstream entity includes at least one of another emergency services routing proxy or a public safety answering point.

3. The system of claim 1, wherein the routing service identifier and the identifier included in the call include a uniform resource identifier (URI).

4. The system of claim 1, wherein the upstream entity includes at least one of a call originating device or another emergency services routing proxy.

5. The system of claim 1 wherein the one or more computer processors are configured to execute the executable instructions to at least identify a node to receive a call based on a load balancing policy.

6. The system of claim 1, further comprising:

a first database server associated with the first emergency services routing proxy node, the first database server including routing policy data; and

a second database server associated with the second emergency services routing proxy node, the second database server including the routing policy data,

wherein the first database server and the second database server are configured to replicate routing policy data such that the routing policy data included in database servers is identical.

7. The system of claim 1, wherein the one or more computer processors are configured to execute the executable instructions to at least:

identify the first emergency services routing proxy node and the second emergency services proxy node to provide the routing service for a call based at least in part on a correspondence between a service identifier included in the call and the routing service identifier; and

select one of the first emergency services routing proxy node and the second emergency services proxy node based on a comparison between the first registration information and the second registration information.

8. The system of claim 7, wherein the call is a session initiation protocol call.

9. The system of claim 7, wherein the call comprises mixed media data.

10. The system of claim 1, wherein the node status information includes at least one of node load, a number of active calls for the node, node memory usage, node network bandwidth, and node routing time.

11. The system of claim 10, wherein the status policy associates a service status with aggregated node status information values, and wherein the service status message includes the service status.

12. A method of managing a cluster of emergency services routing proxy nodes, the method comprising:

receiving, at an electronic device including a cluster management processor, first registration information from a first emergency services routing proxy node, the first registration information including a routing service identifier for an emergency service provider;

receiving second registration information from a second emergency service routing proxy node for an emergency service provider, the second registration information including the routing service identifier, wherein the first emergency services routing proxy node and the second emergency services routing proxy node are included in a clustered emergency services routing proxy managed by a cluster manager, and wherein the clustered emergency services routing proxy is configured to route a call received from an upstream entity to a downstream entity via one of the first emergency services routing proxy node or the second emergency services routing proxy node;

receiving node status information from nodes included in the clustered emergency services routing proxy associated with the routing service identifier, the nodes including the first emergency services routing proxy node and the second emergency services routing proxy node;

generating the service status message for the clustered emergency services routing proxy based on;

(i) the received node status information for the nodes included in the clustered emergency services routing proxy associated with the routing service identifier, and (ii) a status policy; and

transmitting the service status message to an upstream entity.

13. The method of claim 12, further comprising providing the call to the identified one of the first emergency services routing proxy node or the second emergency services proxy node.

14. The method of claim 12, wherein the node status information includes at least one of node load, a number of active calls for the node, node memory usage, node network bandwidth, and node routing time.

15. The method of claim 12, wherein the status policy associates a service status with aggregated node status information values, and wherein the service status message includes the service status.

16. The method of claim 12, wherein the routing service identifier comprises a uniform resource identifier (URI).

17. The method of claim 12, wherein identifying the first emergency services routing proxy node or the second emergency services proxy node to provide the routing service for the call comprises:

receiving a load balancing policy;

receiving node information from one or more of the first emergency services routing proxy node and the second emergency services proxy node; and

identifying the first emergency services routing proxy node or the second emergency services proxy node further based on the load balancing policy and the received node information.

18. The method of claim 12, wherein a first routing service identifier is received from the first emergency services routing proxy node, the first routing service identifier associated with a first tenant of the first emergency services routing proxy node, and

wherein a second routing service identifier is received from the first emergency services routing proxy node, the second routing service identifier associated with a second tenant of the first emergency services routing proxy node.

19. The method of claim 12 further comprising:

identifying the first emergency services routing proxy node and the second emergency services proxy node to provide the routing service for a call based at least in part on a correspondence between a service identifier included in the call and the routing service identifier; and

selecting one of the first emergency services routing proxy node and the second emergency services proxy node based on a comparison between the first registration information and the second registration information.

20. A cluster management system comprising:

means for receiving registration information from a plurality of means for routing calls to a downstream entity, the calls received from an upstream entity, wherein registration information for a first means for routing calls includes a routing service identifier and registration information for a second means for routing calls includes the routing service identifier, and wherein the first means for routing calls and the second means for routing calls are included in a clustered emergency services routing proxy maintained by a cluster manager, and wherein the clustered emergency services routing proxy is configured to route a call from the upstream entity via one of the first means for routing calls or the second means for routing calls;

means for receiving node status information from nodes included in the clustered emergency services routing proxy associated with the routing service identifier, the nodes including the first emergency services routing proxy node and the second emergency services routing proxy node;

means for generating the service status message for the clustered emergency services routing proxy based on;

(i) the received node status information for the nodes included in the clustered emergency services routing proxy associated with the routing service identifier, and (ii) a status policy; and

means for transmitting the service status message to an upstream entity.