Fault routing of an emergency communication

• US 10,313,512 B2
• Filed: 11/09/2017
• Issued: 06/04/2019
• Est. Priority Date: 08/26/2011
• Status: Active Grant

• Current Assignee: Comcast Cable Communications LLC (Comcast Corporation)
• Original Assignee: Comcast Cable Communications LLC (Comcast Corporation)
• Inventors: Kaushal, Arvind, Boone, Jon, Sherman, Brett
• Primary Examiner(s): La, Phong
• Application Number:
  US15/808,650
• Publication Number:
  US 20180167503A1
• Time in Patent Office: 572 Days
• Field of Search: 370216
• CPC Class Codes: H04L 65/1066 Session management
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/40 Support for services or applications
• CPC Class Codes: H04M 2242/04 for emergency applications
• CPC Class Codes: H04M 3/12 Marking faulty circuits "busy"; Enabling equipment to disengage itself from faulty circuits ; Using redundant circuits; Response of a circuit, apparatus or system to an error
• CPC Class Codes: H04M 3/2218 Call detail recording
• CPC Class Codes: H04M 3/42187 Lines and connections with preferential service
• 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/18 Management of setup rejection or failure
• CPC Class Codes: H04W 76/50 for emergency connections

Abstract

Aspects of the disclosure relate to routing of an emergency communication under fault conditions. Routing can be implemented in a packet-switching (PS) network that provides voice service. For a network node of the PS network, availability to route the emergency communication through a specific emergency service routing number (ESRN) can be determined and, in response to the network node being unavailable, administrative data associated with the ESRN can be accessed. In addition, an identifier associated with the administrative data can be updated (e.g., created or modified) with data indicative of the device that originated the emergency communication. The administrative data and the resulting identifier can be delivered to a second network node that can route the emergency communication to an emergency service network.

Claims

1. A method, comprising:

receiving, by a routing computing device from a first routing device, a first query message, wherein the first query message is received in response to an emergency communication from a user device;

in response to receiving the first query message, determining a network node that interfaces with an emergency services network;

transmitting, to the first routing device, data indicative of the network node, wherein the data indicative of the network node facilitates communications between the first routing device, via the network node, and a second routing device associated with the emergency services network;

receiving, from the second routing device, a second query message;

determining, based on the second query message, a logical address; and

transmitting, to the second routing device, a response to the second query message, wherein the response comprises data indicative of the logical address, and wherein the second routing device is configured to update an identifier associated with the user device to facilitate the emergency communication.

2. The method of claim 1, wherein the first query message indicates a query to determine an identifier associated with the network node, and wherein the first query message is based on an E.164 Number Mapping (ENUM) Protocol.

3. The method of claim 1, wherein the logical address comprises at least one of an IP address, a Session Initiation Protocol (SIP) address, or a Uniform Resource Identifier (URI) path.

4. The method of claim 1, further comprising receiving, by the first routing device, a Session Initiation Protocol (SIP) message comprising a trunk group number, wherein the SIP message is a SIP INVITE message for initiating the emergency communication.

5. The method of claim 1, wherein the routing computing device comprises a routing database, wherein the first routing device comprises a first Session Initiation Protocol (SIP) routing proxy, and wherein the second routing device comprises a second SIP routing proxy.

6. The method of claim 1, wherein the second routing device is further configured to update the identifier associated with the user device by replacing a randomly generated Emergency Service Query Key (ESQK) with a telephone number associated with the user device.

7. The method of claim 1, wherein the second query message is based on an Emergency Service Routing Number (ESRN).

8. An apparatus, comprising:

one or more processors; and

a memory storing processor executable instructions that, when executed by the one or more processors, cause the apparatus to;

receive, from a first routing device, a first query message, wherein the first query message is received in response to an emergency communication from a user device;

in response to receiving the first query message, determine a network node that interfaces with an emergency services network;

transmit, to the first routing device, data indicative of the network node, wherein the data indicative of the network node facilitates communications between the first routing device, via the network node, and a second routing device associated with the emergency services network;

receive, from the second routing device, a second query message;

determine, based on the second query message, a logical address; and

transmit, to the second routing device, a response to the second query message, wherein the response comprises data indicative of the logical address, and wherein the second routing device is configured to update an identifier associated with the user device to facilitate the emergency communication.

9. The apparatus of claim 8, wherein the first query message indicates a query to determine an identifier associated with the network node, and wherein the first query message is based on an E.164 Number Mapping (ENUM) Protocol.

10. The apparatus of claim 8, wherein the logical address comprises at least one of an IP address, a Session Initiation Protocol (SIP) address, or a Uniform Resource Identifier (URI) path.

11. The apparatus of claim 8, wherein the first routing device comprises a first Session Initiation Protocol (SIP) routing proxy, and wherein the second routing device comprises a second SIP routing proxy.

12. The apparatus of claim 8, wherein the second routing device is further configured to update the identifier associated with the user device by replacing a randomly generated emergency service query key (ESQK) with a telephone number associated with the user device.

13. The apparatus of claim 8, wherein the second query message is based on an emergency service routing number (ESRN).

14. One or more non-transitory computer readable media storing processor executable instructions that, when executed by at least one processor, cause the at least one processor to:

receive, from a first routing device, a first query message, wherein the first query message is received in response to an emergency communication from a user device;

in response to receiving the first query message, determine a network node that interfaces with an emergency services network;

transmit, to the first routing device, data indicative of the network node, wherein the data indicative of the network node facilitates communications between the first routing device, via the network node, and a second routing device associated with the emergency services network;

receive, from the second routing device, a second query message;

determine, based on the second query message, a logical address; and

transmit, to the second routing device, a response to the second query message, wherein the response comprises data indicative of the logical address, and wherein the second routing device is configured to update an identifier associated with the user device to facilitate the emergency communication.

15. The one or more non-transitory computer readable media of claim 14, wherein the first query message indicates a query to determine an identifier associated with the network node, and wherein the first query message is based on an E.164 Number Mapping (ENUM) Protocol.

16. The one or more non-transitory computer readable media of claim 14, wherein the logical address comprises at least one of an IP address, a Session Initiation Protocol (SIP) address, or a Uniform Resource Identifier (URI) path.

17. The one or more non-transitory computer readable media of claim 14, wherein the processor executable instructions, when executed by the at least one processor, further cause the at least one processor to receive, by the first routing device, a Session Initiation Protocol (SIP) message comprising a trunk group number, wherein the SIP message is a SIP INVITE message for initiating the emergency communication.

18. The one or more non-transitory computer readable media of claim 14, wherein the first routing device comprises a first Session Initiation Protocol (SIP) routing proxy, and wherein the second routing device comprises a second SIP routing proxy.

19. The one or more non-transitory computer readable media of claim 14, wherein the second routing device is further configured to update the identifier associated with the user device by replacing a randomly generated Emergency Service Query Key (ESQK) with a telephone number associated with the user device.

20. The one or more non-transitory computer readable media of claim 14, wherein the second query message is based on an Emergency Service Routing Number (ESRN).