Emergency 911 data messaging

Abstract

A data request is generated (e.g., text, email, SMS, multimedia messaging system (MMS), etc.) from a source device. The data request is delivered to a PSAP or other emergency monitoring service location in a useable format. Exemplary useable formats include a canned voice message, delivery to a call center that translates data to voice, text to speech, and text to instant messaging (IM). Additional information and location are staged for use by the PSAP or other monitoring service location.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to telecommunications. More particularly, it relates to wireless messaging and wireless emergency services such as E911.

2. Background of the Related Art

9-1-1 is a phone number widely recognized in North America as an emergency phone number that is used to contact emergency dispatch personnel. Enhanced 9-1-1 (E9-1-1) is defined by an emergency call being selectively routed to an appropriate public service access point (PSAP), based on a special identifier (P-ANI, or “Pseudo Automatic Number Identifier”, also referred to as “ESxK”), and includes the transmission of callback number and location information when 9-1-1 is used. E9-1-1 may be implemented for landline, cellular or VolP networks. A Public Service Answering Point (PSAP) is a dispatch office that receives 9-1-1 calls from the public. A PSAP may be a local, fire or police department, an ambulance service or a regional office covering all services. As used herein, the term “PSAP” refers to either a public safety access point (PSAP), or to an Emergency Call Center (ECC), a VoIP term.

Regardless of the network type, a 9-1-1 service becomes E-9-1-1 when automatic number identification and automatic location information related to the call is provided to the 9-1-1 operator at the PSAP. A primary challenge results from the fact that calls may arrive at the PSAP without the caller's actual callback number or location information displayed at the emergency operator's terminal.

The result of an E911 call is a direct circuit connection between the requestor and the responder. 911 is further enhanced with the ability to deliver location information over a data channel in parallel to the emergency call. This data is typically staged in a database that is queried by the PSAP to determine location information.

FIG. 3 depicts an overview of conventional enhanced 9-1-1 (E9-1-1) voice call flow in currently deployed architecture.

In particular, as shown in FIG. 3, an emergency voice call is initiated at a mobile station or handset 102, delivered through a relevant radio tower and base station 104 to a Mobile Switching Center (MSC) 206. The emergency voice call is then held while call setup information is delivered to a location center 222. The location center 222 responds to the MSC 206 with appropriate call routing information, and triggers a request for precise location. The MSC 206 releases the call and routes it to the correct PSAP through a selective router 210 based on information provided from the location center 222. The location center 222 then stages a record in an automatic location information (ALI) database 214. When the precise location information is returned to the location center 222 from a position determining entity 226, this location coordinate information is compared to a coordinate routing database 224, and the matching address and call back information is then staged for retrieval by the ALI database 214.

The current 911 infrastructure was designed to route a voice emergency call to the local PSAP. Unfortunately, this requires that voice circuits be available to carry the emergency call. During times of regional crises, such as a hurricane, the local wireless infrastructure can become overloaded by call volume. This was experienced during the September 11th terrorist attacks during which voice telecommunications along the East Coast was subject to service failures.

SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, an emergency system short messaging system (SMS) location proxy comprises an interface between the SMS location proxy and a short messaging service center (SMSC), and an interface to an emergency services provider. A module provides location information relating to an emergency services data message routed via the SMSC and directed toward the emergency services provider.

In accordance with another embodiment of the present invention, apparatus for providing 911 equivalent data emergency services comprises a short messaging system (SMS) location proxy to provide location information relating to an emergency data message. A module receives a request for location of a data message, and a module provides requested location of a data message to an emergency services provider. In this way, data emergency services are provided using a non-persistent connection with an emergency data initiator.

In accordance with yet another embodiment of the present invention, 911 equivalent data emergency services are provided to an emergency data initiator using a non-persistent connection by associating a request for location relating to a non-persistent emergency data message with a geo-location. The request for location is delivered to an appropriate emergency services provider in a format useable by the emergency services provider. Location information is staged for use by the emergency services provider.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings:

FIG. 1 depicts an exemplary embodiment for generating an E9-1-1 text message with geographic location information for delivery to a PSAP, in accordance with the principles of the present invention.

FIG. 2 shows relevant elements of an SMS location proxy in more detail, in accordance with the principles of the present invention.

FIG. 3 depicts an overview of conventional enhanced 9-1-1 (E9-1-1) voice call flow in currently deployed architecture.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Short message system (SMS) technology is available to generate SMS traffic from a handset and deliver the message to another handset or to an Internet Address. There is also a wireline SMS capability that has been introduced to deliver an SMS message to non-SMS enabled devices. But SMS is not a persistent connection, and there is no conventional location capability associated with SMS. Moreover, conventional technologies do not have the capability to deliver SMS messages to a PSAP.

Public service answering point (PSAP) connectivity to the public switched telephone network (PSTN) is managed through dedicated switches called emergency services gateways (ESGW) that conventionally can not be directly dialed and do not support SMS traffic. Even if the switches were able to support the delivery of SMS to the PSAP, there is no currently available method for the PSAP to process and display or use the information from an SMS.

The inventors of the present invention have empirically recognized that during times of voice circuit overload, the signaling system No. 7 (SS7) signaling network had excess capacity available to carry short message traffic. The present invention enables a Short Message Service (SMS) capability for generating an emergency 911 “equivalent” call. This capability enables SMS savvy consumers to generate requests for assistance to the local Public Safety Answering Point (PSAP) that can be understood and translated to provide first responders with the information they need to offer timely assistance.

This invention offers a solution architecture and method for delivery of 911 equivalent requests for emergency assistance using non-voice centric, and importantly non-persistent connectivity sources such as SMS, email, and autonomous data/message generation devices.

According to the principles of the present invention, a data request is generated (e.g., text, email, SMS, multimedia messaging system (MMS), etc.) from a source device. The data request is delivered to a PSAP or other emergency monitoring service location in a useable format. Exemplary useable formats include a canned voice message, delivery to a call center that translates data to voice, text to speech, and text to instant messaging (IM). Additional information and location are staged for use by the PSAP or other monitoring service location.

An overview of the invention for data 911 is now described. While some similarities to conventional voice based persistent circuit technologies exist, the inventive data 911 call flow is broken down into more detail in subsequent sections to specifically delineate significant differences and uniqueness of the invention.

FIG. 1 depicts an exemplary embodiment for generating an E9-1-1 text message with geographic location information for delivery to a PSAP, in accordance with the principles of the present invention.

In particular, as shown in FIG. 1, an example of the invention based on use of Short Message technology is presented. In this example, the source of the emergency data message is a handset type of device 102 also capable of making a voice call. However, while the handset device 102 sends a text message addressed by the user/caller simply as 911 instead of dialing a phone number.

In call flow, the 911 emergency text message from the mobile station/user equipment (MS/UE), or handset, 102 traverses the radio network and the base station controller 104, and then is delivered to the mobile switching center (MSC) 106. The MSC 106 routes the 911 emergency text message to an SMS platform (SMSC) 108.

In step 1 of FIG. 1, a user on a handset 102 sends an emergency data message (e.g., text) via their servicing Short-Message-Service (SMS) network addressed simply to “911” or other designated Emergency Services Identity. In the given example, the source of the emergency data message has a preferable form of MSISDN@carrierdomain.com, though any appropriate unique address scheme unique to the handset 102 or specific user is possible.

In step 2, the exemplary emergency SMS data message (e.g., “Help me!”) is routed from the MSC 106 to the relevant SMSC 108.

In step 3, the SMSC 108 routes the exemplary emergency SMS data message to the SMS location proxy 100.

In step 4, the SMS location proxy 100 initiates a request for routing to the MPC 114. The emergency SMS data message originating MSISDN and the identity of the carrier is sent to a mobile positioning center (MPC) 114 with the request for routing.

In step 5, the MPC 114 receives the request for routing, and then requests information from the network using the current method to derive the remaining information necessary to request location from the network.

In step 6, the MPC 114 then requests information about the precise latitude/longitude (lat/lon) and/or rough position (tower/sector) of the emergency texter. The request for routing preferably includes an indicator of “Emergency Services” or similar designation.

In step 7, the network calculates the position of the emergency texter and returns this information to the MPC 114.

In step 8, the MPC 114 uses the “rough” location information (or optionally: the precise) to determine the routing necessary for the emergency SMS data message, and returns a route destination to the SMS location proxy 100.

In step 9, the SMS location proxy 100 routes the emergency SMS data message (+appended Location Information—Rough and Precise (when available) to the appropriate PSAP or call center 116.

In step 10, the emergency texting user or emergency text message initiator is messaged that their emergency SMS data message has been received. An instant messaging (IM)-like non-persistent connection is made between the PSAP or call center 116 and the emergency texting user or emergency text message initiator through the SMS location proxy 100.

FIG. 2 shows relevant elements of an SMS location proxy in more detail, in accordance with the principles of the present invention.

In particular, as shown in FIG. 2, the exemplary SMS location proxy 100 includes an application module loaded into an appropriate gateway element to receive requests for location of a data message. The exemplary SMS location proxy 100 also includes an application module that stages the relevant location information relating to the location of emergency data messages (e.g., emergency 911 text messages) and transmits that location information (e.g., lat/long information and/or street address information) to an appropriate emergency services provider such as a PSAP or call center 116 (FIG. 1).

While initially envisioned as a method for supporting SMS initiated emergency 911 text messages, the present invention can also be used for delivery of other types of non-voice initiated sources using non-persistent communications, such as in-vehicle monitoring systems, autonomous monitoring devices for dams/levies, health monitoring equipment, electronic mail, etc. However, in the given example the emergency texting device must be CDMA capable.

This invention enables PSAPs to receive, process, and act upon a wide variety of non-voice messaging information such as a simple text message to complex image messaging (e.g., MMS).

The present invention can be extended for use to enable automated systems to provide text message warnings or notifications to operator monitored services that have a specific geographic regional coverage.

The invention has particular applicability to the wireless E9-1-1 market, including to any US CDMA carrier, and to virtually any company which markets devices with CDMA connectivity.

The present invention permits a method for routing an emergency SMS data message based upon the general or precise location of an emergency texting sender's data messaging device.

While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.

Claims

1. A mobile positioning center (MPC) server method for non-pearsistent data 911 communication with an emergency data initiator, comprising: receiving, at a physical mobile positioning center (MPC) server, a request for routing an emergency text message addressed to “911” initiated by a physical emergency text-initiating mobile device;receiving, at said physical MPC server, routing of a mobile station international subscriber directory number (MSISDN) in a form of MSISDN@carrierdomain.com identifying a carrier network providing communication service to the emergency text-initiating mobile device;requesting, from said physical MPC server, a rough position of said emergency text-initiating mobile device;receiving, in response to said request, a current geographic location of said emergency text-initiating device;determining a route destination address for said emergency text message based on said received current geographic location; andtransmitting said route destination address to a location proxy server.

2. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 1, wherein: said MSISDN is received together with said emergency text message by said physical MPC server.

3. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 1, wherein: said location proxy server is a short messaging system (SMS) location proxy server.

4. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 1, wherein: said emergency text message and said current geographic location are routed to said route destination address by said location proxy server.

5. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 1, wherein: said rough position is a tower/sector.

6. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 1, wherein: said request for routing said emergency text message includes an indicator of emergency services content.

7. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 1, wherein: said emergency text message is a short messaging system (SMS) text message.

8. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 1, wherein: said emergency text message is routed to said physical MPC server from a mobile switching center (MSC).

9. A mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator, comprising: receiving, at a physical mobile positioning center (MPC) server, a request for routing an emergency text message addressed to “911” initiated by a physical emergency text-initiating mobile device;receiving, at said physical MPC server, routing of a mobile station international subscriber directory number (MSISDN) in a form of MSISDN@carrierdomain.com identifying a carrier network providing communication service to of the emergency text-initiating mobile device;requesting, from said physical MPC server, a precise latitude/longitude (lat/lon) of said emergency text-initiating mobile device;receiving, in response to said request, a current geographic location of said emergency text-initiating device;determining a route destination address for said emergency text message based on said received current geographic location; andtransmitting said route destination address to a location proxy server.

10. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 9, wherein: said MSISDN is received together with said emergency text message by said physical MPC server.

11. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 9, wherein: said location proxy server is a short messaging system (SMS) location proxy server.

12. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 9, wherein: said emergency text message and said current geographic location are routed to said route destination address by said location proxy server.

13. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 9, wherein: said request for routing said emergency text message includes an indicator of emergency services content.

14. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 9, wherein: said emergency text message is a short messaging system (SMS) text message.

15. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 9, wherein: said emergency text message is routed to said physical MPC server from a mobile switching center (MSC).

16. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 9, wherein: said emergency email is routed to said physical MPC server from a mobile switching center (MSC).

17. A mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator, comprising: receiving, at a physical mobile positioning center (MPC) server, a request for routing an email addressed to “911” initiated by a physical emergency email-initiating mobile device;receiving, at said physical MPC server, routing of a mobile station international subscriber directory number (MSISDN) in a form of MSISDN@carrierdomain.com identifying a carrier network providing communication service to the emergency email-initiating mobile device;requesting, from said physical MPC server, a current geographic location of said emergency email-initiating mobile device;receiving, in response to said request, said requested current geographic location of said emergency email-initiating device;determining a route destination address for said emergency email based on said received current geographic location; andtransmitting said route destination address to a location proxy server.

18. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 17, wherein: said MSISDN is received together with said emergency email by said physical MPC server.

19. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 17, wherein: said emergency email and said current geographic location are routed to said route destination address by said location proxy server.

20. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 17, wherein: said request for routing said emergency email includes an indicator of emergency services content.

21. A mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator, comprising: receiving, at a physical mobile positioning center (MPC) server, a request for routing an emergency multimedia message addressed to “911” initiated by a physical emergency text-initiating mobile device;receiving, at said physical MPC server, routing of a mobile station international subscriber directory number (MSISDN) in a form of MSISDN@carrierdomain.com identifying a carrier network providing communication service to of the emergency multimedia message-initiating mobile device;requesting, from said physical MPC server, a current geographic location of said emergency multimedia message-initiating mobile device;receiving, in response to said request, said current geographic location of said emergency multimedia message-initiating device;determining a route destination address for said emergency multimedia message based on said received current geographic location; andtransmitting said route destination address to a location proxy server.

22. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 21, wherein: said MSISDN is received together with said emergency multimedia message by said physical MPC server.

23. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 21, wherein: said emergency multimedia message and said current geographic location are routed to said route destination address by said location proxy server.

24. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 21, wherein: said request for routing said emergency multimedia message includes an indicator of emergency services content.

25. The mobile positioning center (MPC) server method for non-persistent data 911 communication with an emergency data initiator according to claim 21, wherein: said emergency multimedia message is routed to said physical MPC server from a mobile switching center (MSC).