Emergency 911 data messaging
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.
1. 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) of 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; and
transmitting said route destination address to a location proxy server;
wherein said physical MPC server further receives an identity of a carrier network providing communication service to said physical emergency text-initiating mobile device, and said MSISDN, together with said emergency text message.
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 location proxy server is a short messaging system (SMS) location proxy 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 emergency text message and said current geographic location are routed to said route destination address by said 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 rough position is a tower/sector.
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 request for routing said emergency text message includes an indicator of emergency services content.
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 emergency text message is a short messaging system (SMS) text message.
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 MSISDN has a form of [email protected].
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) 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; and
transmitting said route destination address to a location proxy server;
wherein said physical MPC server further receives an identity of a carrier network providing communication service to said physical emergency text-initiating mobile device, and said MSISDN, together with said emergency text message.
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 location proxy server is a short messaging system (SMS) location proxy 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 emergency text message and said current geographic location are routed to said route destination address by said 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 request for routing said emergency text message includes an indicator of emergency services content.
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 emergency text message is a short messaging system (SMS) text message.
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 MSISDN has a form of [email protected].
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).