Emergency event message

Patent metadata

Field	Value
Publication number	US-9430935-B2
Application number	US-201414334317-A
Country	US
Kind code	B2
Filing date	Jul 17, 2014
Priority date	Dec 13, 2013
Publication date	Aug 30, 2016
Grant date	Aug 30, 2016

Abstract

A gateway can be configured to receive an emergency event message in a predefined format via a network. The emergency event message can characterize a location and a nature of an emergency event. The gateway can also be configured to identify a particular Public Safety Answering Point (PSAP) customer premise equipment (CPE) to service the emergency event. The gateway can further be configured determine a format of messages employable by the particular PSAP. The gateway can still further be configured to provide the particular PSAP CPE with an output message in the format employable by the particular PSAP CPE. The output message can characterize the nature and the location of the emergency event.

First claim

What is claimed is:

1. A gateway comprising one or more computers having machine readable instructions, the gateway being configured to:
receive an emergency event message in a predefined format via a network, wherein the emergency event message characterizes a location and a nature of an emergency event and the location characterizes at least one of geographic coordinates and a civic address;
identify a particular Public Safety Answering Point (PSAP) customer premise equipment (CPE) of a plurality of PSAP CPEs to service the emergency event based on the location or the nature of the emergency event;
determine a format of messages employable by the particular PSAP CPE; and
provide the particular PSAP CPE with an output message in the format employable by the particular PSAP CPE, wherein the output message characterizes the nature and the location of the emergency event.

2. The gateway of claim 1 , wherein the emergency event message comprises an Automated Secure Alarm Protocol (ASAP) message.

3. The gateway of claim 2 , wherein the output message comprises an Internet Protocol (IP) message.

4. The gateway of claim 3 , wherein the output message further comprises a Hypertext Transfer Protocol Secure (HTTPS) message.

5. The gateway of claim 3 , wherein the output message further comprises a Hypertext Transfer Protocol (HTTP) message.

6. The gateway of claim 2 , wherein the output message comprises an Extensible Markup Language (XML) message.

7. The gateway of claim 2 , wherein the output message comprises a Session Initiation Protocol (SIP) message that conforms to the Message Session Relay Protocol (MSRP).

8. The gateway of claim 7 , wherein the output message is provided to the particular PSAP CPE via an Emergency Services Internet Protocol network.

9. The gateway of claim 7 , wherein the emergency event message is a given emergency event message, and the particular PSAP CPE is a given PSAP CPE, the gateway being further configured to:
receive another emergency event message via the network, wherein the emergency event message characterizes a location and a nature of another emergency event; and
identify another PSAP CPE to service the other emergency event; and
provide the other PSAP CPE with another output message in a format employable by the other PSAP CPE, wherein the other output message is provided to the other PSAP CPE via the Internet.

10. The gateway of claim 9 , wherein the other output message comprises a Hypertext Transfer Protocol Secure (HTTPS) message.

11. The gateway of claim 1 , wherein the emergency event message comprises a short message service (SMS) Message.

12. The gateway of claim 1 , wherein the emergency event message comprises a session initiation protocol (SIP) message.

13. The gateway of claim 1 , wherein the emergency event message comprises an Extensible Messaging and Presence Protocol (XMPP) message.

14. The gateway of claim 1 , wherein the emergency event message comprises an alarm panel protocol.

15. The gateway of claim 1 , wherein the emergency event message is received from a central station that receives signals from a plurality of sensors.

16. The gateway of claim 1 , wherein the gateway is further configured to query a given Location-to-Service Translation Protocol (LoST) server to facilitate the identifying of the particular PSAP CPE.

17. The gateway of claim 16 , wherein the gateway is further configured to query another LoST server to facilitate the identifying of the particular PSAP CPE.

18. The gateway of claim 16 , wherein the gateway is further configured to query the given LoST server multiple times to facilitate the identifying of the particular PSAP CPE.

19. The gateway of claim 16 , wherein the LoST server is configured to provide a uniform resource identifier (URI) corresponding to the particular PSAP CPE.

20. The gateway of claim 16 , wherein the LoST server is configured to provide a uniform resource identifier (URI) corresponding to the particular next hop network routing node in the path to the particular PSAP CPE.

21. A system comprising:
a memory configured to store machine readable instructions; and
a processing unit configured to access the memory and execute the machine readable instructions, the machine readable instructions comprising:
a message handler configured to receive a plurality of emergency event messages transmitted over a network, wherein each of the plurality of the emergency event messages comprises a message in a given format that characterizes a location and a nature of a corresponding emergency event of a plurality of emergency events and the location characterizes at least one of geographic coordinates and a civic address; and
a Public Safety Answering Point (PSAP) formatter configured to generate a plurality of output messages for a respective plurality of PSAP CPEs to service the plurality of emergency events, wherein each of the output messages is based on a corresponding emergency event message and each of the output messages is in a format readable by a corresponding PSAP CPE of the plurality of PSAP CPEs,
wherein the corresponding PSAP CPE is selected based on the location or the nature of the corresponding emergency event.

22. The system of claim 21 , wherein at least two of the output messages are in different formats.

23. The system of claim 21 , further comprising a Location-to-Service Translation Protocol (LoST) client configured to query a LoST server to identify each of the plurality of PSAPCPEs.

24. A method comprising:
receiving an emergency event message from a central station or sensor, wherein the emergency event message includes location information that characterizes at least one of geographic coordinates and a civic address for an emergency event;
querying, in response to the emergency event message, a server to identify a particular Public Safety Answering Point (PSAP) customer premise equipment (CPE) of a plurality of PSAP CPEs to service the emergency event corresponding to the emergency event message based on the location or the nature of the emergency event; and
formatting the emergency event message into an output message in a format readable by the particular PSAP CPE.

25. The method of claim 24 , wherein the emergency event message comprises an Automated Secure Alarm Protocol (ASAP) message.

26. The method of claim 25 , wherein the output message comprises one of an Internet Protocol (IP) message and a Session Initiated Protocol (SIP) message.

27. The method of claim 25 , further comprising determining, based on a response to the query, a format of messages employable by the particular PSAP.

28. The method of claim 25 , wherein the server is a Location-to-Service Translation Protocol (LoST) server.

Assignees

• Ginter Thomas
• Mitchell Donald L
• Marshall Roger S
• Poremba Todd
• Harrison Stephen Lee
• Telecomm Systems Inc

Inventors

• Ginter Thomas
• Mitchell Donald L
• Marshall Roger S
• Poremba Todd
• Harrison Stephen Lee

Classifications

• G08B27/005 Primary

  with transmission via computer network · CPC title

• H04L67/18

  Electricity · mapped topic

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L67/12

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

• H04W4/14 Primary

  Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD] · CPC title