# US 10,375,556 B2 · Emergency call service backup using device user plane communications > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,375,556 B2 - Document ID: US10375556B2 - Status: Granted - Kind: B2 - Application number: 15/851,094 - Filed: 2017-12-21 - Published: 2019-06-27 - Granted: 2019-08-06 - Earliest claimed: 2017-12-21 - Assignees: International Business Machines Corporation - Applicants: International Business Machines Corporation; LaaSer Critical Communications Corporation - Inventors: Brent Gross; Sushain Pandit; Guenter A. Sauter; Charles D. Wolfson; Michael R. Self; Frederick L. White - Web page: https://patentgrep.com/patent/US10375556B2 ## CPC - H04W 4/90: Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS] - H04W 4/025: {using location based information parameters} - H04W 4/029: Location-based management or tracking services - H04W 24/04: Arrangements for maintaining operational condition - H04W 76/18: Management of setup rejection or failure - H04W 76/50: for emergency connections - H04W 4/02: Services making use of location information - H04W 4/33: for indoor environments, e.g. buildings - H04W 60/005: {Multiple registrations, e.g. multihoming} - H04W 76/16: Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract An initiation of an emergency communication with an emergency service associated with an emergency telephone number is detected by a mobile communications device. A completion of the emergency communication using a first communication path associated with a mobile communications service provider is attempted. The mobile communication device determines that the emergency communication using the first communication path has failed. An identity of a destination of the failed emergency communication is determined using location and telemetry data from the mobile communication device. A connection of the mobile communications device to the identified destination is facilitated using a second communication path. The mobile communications device is identified to the determined destination as an originator of the connection. ## Claims ### Claim 1 A method for emergency communication service backup, the method comprising: detecting, by a mobile communications device, an initiation of an emergency communication with an emergency service associated with an emergency telephone number; attempting completion of the emergency communication using a first communication path associated with a mobile communications service provider; determining, by the mobile communication device, that the emergency communication using the first communication path has failed; determining, using location and telemetry data from the mobile communication device, an identity of a destination of the failed emergency communication; facilitating a connection of the mobile communications device to the identified destination using a second communication path, wherein the mobile communications device is identified to the determined destination as an originator of the connection; storing historical information of the failed emergency communications; determining a failure probability of subsequent emergency communications based upon the historical information; and determining at least one preventative action to mitigate subsequent emergency communication failures based upon the failure probability. ### Claim 2 (depends on 1) The method of claim 1, wherein the second communication path uses a previously unused portion of a network of the mobile communications service provider. ### Claim 3 (depends on 1) The method of claim 1, wherein the second communication path bypasses emergency communication components associated with the mobile communications service provider. ### Claim 4 (depends on 1) The method of claim 1 further comprising: determining enhanced location information based upon the location information and telemetry data; and providing the enhanced location information to the mobile communications service provider. ### Claim 5 (depends on 4) The method of claim 4, wherein the location information includes a latitude and longitude of the mobile device. ### Claim 6 (depends on 4) The method of claim 4, wherein the enhanced location information includes one or more of a pressure, elevation, or floor of a building associated with a location of the mobile device. ### Claim 7 (depends on 4) The method of claim 4, further comprising: receiving updated location information and telemetry data from the mobile device, the updated location information and telemetry data includes a change in location and telemetry of the mobile device since the initiating of the emergency communication. ### Claim 8 (depends on 1) The method of claim 1, further comprising: notifying the mobile communications service provider of the failed emergency communication. ### Claim 9 (depends on 1) The method of claim 1, further comprising: tracking locations of failed emergency communications of at least one of the mobile device and other mobile devices, a frequency of the failed emergency communications, and an identity information of the mobile communications service provider. ### Claim 10 (depends on 1) The method of claim 1, wherein the at least one preventative measure includes selectively changing network routing in a particular geographic area. ### Claim 11 A computer usable program product comprising one or more computer-readable storage devices, and program instructions stored on at least one of the one or more storage devices, the stored program instructions comprising: program instructions to detect, by a mobile communications device, an initiation of an emergency communication with an emergency service associated with an emergency telephone number; program instructions to attempt completion of the emergency communication using a first communication path associated with a mobile communications service provider; program instructions to determine, by the mobile communication device, that the emergency communication using the first communication path has failed; program instructions to determine, using location and telemetry data from the mobile communication device, an identity of a destination of the failed emergency communication; program instructions to facilitate a connection of the mobile communications device to the identified destination using a second communication path, wherein the mobile communications device is identified to the determined destination as an originator of the connection; program instructions to store historical information of the failed emergency communications; program instructions to determine a failure probability of subsequent emergency communications based upon the historical information; and program instructions to determine at least one preventative action to mitigate subsequent emergency communication failures based upon the failure probability. ### Claim 12 (depends on 11) The computer usable program product of claim 11, wherein the second communication path uses a previously unused portion of a network of the mobile communications service provider. ### Claim 13 (depends on 11) The computer usable program product of claim 11, wherein the second communication path bypasses emergency communication components associated with the mobile communications service provider. ### Claim 14 (depends on 11) The computer usable program product of claim 11, further comprising: program instructions to determine enhanced location information based upon the location information and telemetry data; and program instructions to provide the enhanced location information to the mobile communications service provider. ### Claim 15 (depends on 14) The computer usable program product of claim 14, wherein the location information includes a latitude and longitude of the mobile device. ### Claim 16 (depends on 11) The computer usable program product of claim 11, wherein the computer usable code is stored in a computer readable storage device in a data processing system, and wherein the computer usable code is transferred over a network from a remote data processing system. ### Claim 17 (depends on 11) The computer usable program product of claim 11, wherein the computer usable code is stored in a computer readable storage device in a server data processing system, and wherein the computer usable code is downloaded over a network to a remote data processing system for use in a computer readable storage device associated with the remote data processing system. ### Claim 18 A computer system comprising one or more processors, one or more computer-readable memories, and one or more computer-readable storage devices, and program instructions stored on at least one of the one or more storage devices for execution by at least one of the one or more processors via at least one of the one or more memories, the stored program instructions comprising: program instructions to detect, by a mobile communications device, an initiation of an emergency communication with an emergency service associated with an emergency telephone number; program instructions to attempt completion of the emergency communication using a first communication path associated with a mobile communications service provider; program instructions to determine, by the mobile communication device, that the emergency communication using the first communication path has failed; program instructions to determine, using location and telemetry data from the mobile communication device, an identity of a destination of the failed emergency communication; program instructions to facilitate a connection of the mobile communications device to the identified destination using a second communication path, wherein the mobile communications device is identified to the determined destination as an originator of the connection; program instructions to store historical information of the failed emergency communications; program instructions to determine a failure probability of subsequent emergency communications based upon the historical information; and program instructions to determine at least one preventative action to mitigate subsequent emergency communication failures based upon the failure probability.