# US 10,313,512 B2 · Fault routing of an emergency communication > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,313,512 B2 - Document ID: US10313512B2 - Status: Granted - Kind: B2 - Application number: 15/808,650 - Filed: 2017-11-09 - Published: 2018-06-14 - Granted: 2019-06-04 - Earliest claimed: 2011-08-26 - Assignees: Comcast Cable Communications, LLC - Applicants: Comcast Cable Communications, LLC - Inventors: Arvind Kaushal; Jon Boone; Brett Sherman - Web page: https://patentgrep.com/patent/US10313512B2 ## CPC - H04L 65/1069: Session establishment or de-establishment - H04L 65/1066: Session management - H04L 65/1104: Session initiation protocol [SIP] - H04M 3/42187: {Lines and connections with preferential service} - H04W 76/50: for emergency connections - 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} - H04M 3/2218: {Call detail recording} - H04M 2242/04: for emergency applications - H04W 4/90: Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS] - H04W 76/18: Management of setup rejection or failure - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## 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 ### Claim 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. ### Claim 2 (depends on 1) 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. ### Claim 3 (depends on 1) 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. ### Claim 4 (depends on 1) 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. ### Claim 5 (depends on 1) 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. ### Claim 6 (depends on 1) 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. ### Claim 7 (depends on 1) The method of claim 1, wherein the second query message is based on an Emergency Service Routing Number (ESRN). ### Claim 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. ### Claim 9 (depends on 8) 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. ### Claim 10 (depends on 8) 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. ### Claim 11 (depends on 8) 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. ### Claim 12 (depends on 8) 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. ### Claim 13 (depends on 8) The apparatus of claim 8, wherein the second query message is based on an emergency service routing number (ESRN). ### Claim 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. ### Claim 15 (depends on 14) 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. ### Claim 16 (depends on 14) 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. ### Claim 17 (depends on 14) 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. ### Claim 18 (depends on 14) 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. ### Claim 19 (depends on 14) 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. ### Claim 20 (depends on 14) 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).