# US 2018/0027115 A1 · Emergency services routing proxy cluster management

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0027115 A1
- Document ID: US20180027115A1
- Status: Published application
- Kind: A1
- Application number: 15/714,678
- Filed: 2017-09-25
- Published: 2018-01-25
- Earliest claimed: 2014-02-07
- Assignees: Airbus DS Communications, Inc.
- Applicants: Airbus DS Communications, Inc.
- Inventors: Ameel Kamboh; Jason Wellonen
- Web page: https://patentgrep.com/patent/US20180027115A1

## CPC

- H04M 3/5116: {for emergency applications}
- H04L 41/0668: by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
- H04L 41/0894: Policy-based network configuration management
- H04L 43/0817: by checking functioning
- H04L 45/3065: {for real time traffic}
- H04L 45/46: {Cluster building}
- H04L 47/2416: Real-time traffic
- H04L 61/4511: using domain name system [DNS]
- H04L 65/1073: Registration or de-registration
- H04L 65/1104: Session initiation protocol [SIP]
- H04M 7/0075: {Details of addressing, directories or routing tables}
- H04M 11/04: with alarm systems, e.g. fire, police or burglar alarm systems
- H04W 4/90: Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
- H04W 76/50: for emergency connections
- H04L 12/1895: {for short real-time information, e.g. alarms, notifications, alerts, updates}
- H04L 41/0661: {by reconfiguring faulty entities}
- H04L 41/069: using logs of notifications; Post-processing of notifications
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/0853: by actively collecting configuration information or by backing up configuration information
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 43/16: Threshold monitoring
- H04L 67/288: Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
- H04L 2101/385: Uniform resource identifier for session initiation protocol [SIP URI]
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## 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

### Claim 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;
receive second registration information from a second emergency services routing proxy node, 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 route calls received from an upstream entity to a downstream entity;
receive node status information from nodes 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 the service status message based on the received node status information and a status policy; and
transmit the service status message to the upstream entity.

### Claim 2 (depends on 1)

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.

### Claim 3 (depends on 1)

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

### Claim 4 (depends on 1)

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

### Claim 5 (depends on 1)

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.

### Claim 6 (depends on 1)

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.

### Claim 7 (depends on 1)

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.

### Claim 8 (depends on 7)

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

### Claim 9 (depends on 7)

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

### Claim 10 (depends on 1)

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.

### Claim 11 (depends on 10)

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.

### Claim 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;
receiving second registration information from a second emergency service routing proxy node, 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 route calls received from an upstream entity to a downstream entity;
receiving node status information from nodes 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 based on the received node status information and a status policy; and
transmitting the service status message to an upstream entity.

### Claim 13 (depends on 12)

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.

### Claim 14 (depends on 12)

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.

### Claim 15 (depends on 12)

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.

### Claim 16 (depends on 12)

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

### Claim 17 (depends on 12)

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.

### Claim 18 (depends on 12)

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.

### Claim 19 (depends on 12)

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.

### Claim 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;
means for receiving node status information from nodes 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 based on the received node status information and a status policy; and
means for transmitting the service status message to an upstream entity.
