Distributed Emergency Text Message Architecture

• US 20140287714A1
• Filed: 03/20/2014
• Published: 09/25/2014
• Est. Priority Date: 03/20/2013
• Status: Abandoned Application

• Current Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Original Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Inventors: Marshall, Roger S., Mitchell, Donald L., Ginter, Thomas, Erkkila, Robin, Sonenthal, Seth
• Application Number:
  US14/220,940
• Publication Number:
  US 20140287714A1
• Time in Patent Office: Days
• US Class Current: 455/404.2
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 40/20 based on geographic position or location
• CPC Class Codes: H04W 76/50 for emergency connections

Abstract

An internet-protocol (IP) based distributed emergency text message architecture for providing reliable text to 911 services. The distributed emergency text message architecture distributes call routing and media transportation functionalities implemented in a conventional text to 911 solution over the following network entities: an emedia aggregation gateway, an emedia message broker, and an emedia distribution server. An emedia aggregation gateway, emedia message broker, and emedia distribution server each interconnect over an IP network to deliver emergency text messages directly to legacy public safety answering points (PSAPs). Uncoupling emergency services call routing and media transportation functionalities into multiple distributed elements absolves scaling issues associated with the conventional text to 911 solution. An emedia local gateway is preferably positioned on a PSAP in the distributed emergency text message architecture to eliminate the need for a selective router element when routing a teletype (TTY) message to a teletype (TTY) terminal on a legacy PSAP.

Claims

1. A distributed emergency text message architecture, comprising:

an emedia aggregation gateway to receive an emergency text message initiated on an originating communications device; and

an emedia distribution server to convert said emergency text message, received from said emedia aggregation gateway, from an Internet protocol (IP) to a suitable message delivery protocol for delivery to a responsible recipient public safety answering point (PSAP) appropriate for a location of an emergency text messaging device initiating said emergency text message.

2. The distributed emergency text message architecture according to claim 1, further comprising:

an emedia message broker, in communication with said emedia aggregation gateway, to route said emergency text message to said emedia distribution server.

3. The distributed emergency text message architecture according to claim 1, further comprising:

an emedia local gateway to route said emergency text message to a teletype (TTY) terminal at said responsible public safety answering point (PSAP).

4. The distributed emergency text message architecture according to claim 1, wherein:

said emedia aggregation gateway, and said emedia distribution server modularly integrate over an internet protocol (IP) network to deliver said emergency text message to said responsible public safety answering point (PSAP).

5. The distributed emergency text message architecture according to claim 3, wherein:

said emedia local gateway is integrated with, and located at, said responsible public safety answering point (PSAP).

6. The distributed emergency text message architecture according to claim 1, wherein:

said emedia distribution server is located at said responsible public safety answering point (PSAP).

7. The distributed emergency text message architecture according to claim 1, wherein:

said emedia aggregation gateway is integrated within a servicing carrier network.

8. The distributed emergency text message architecture according to claim 1, wherein:

said suitable message delivery protocol is a teletype (TTY) protocol.

9. The distributed emergency text message architecture according to claim 1, wherein:

said suitable message delivery protocol is a hypertext transport protocol with secure sessions layer (HTTPS).

10. The distributed emergency text message architecture according to claim 1, wherein:

said suitable message delivery protocol is an internet protocol (IP).

11. The distributed emergency text message architecture according to claim 1, wherein:

said message recipient entity is a teletype (TTY) terminal.

12. The distributed emergency text message architecture according to claim 1, wherein:

said responsible PSAP receives said emergency text message at a web browser client.

13. The distributed emergency text message architecture according to claim 1, wherein:

said responsible PSAP receives said emergency text message via an emergency services Internet protocol (IP) network.

14. The distributed emergency text message architecture according to claim 1, wherein:

said emedia distribution server routes said emergency text message to said emedia local gateway to route to a teletype terminal (TTY) at said responsible public safety answering point (PSAP).

15. The distributed emergency text message architecture according to claim 1, wherein:

said emedia distribution server routes said emergency text message to said emedia local gateway to route to a web browser client at said responsible public safety answering point (PSAP).

19. The method for providing reliable text to 911 services according to claim 6, wherein:

said text to 911 message is routed to an emergency services IP network at said public safety answering point (PSAP).

16. A method for providing reliable text to 911 services, comprising:

receiving an emergency text to 911 message on an emedia aggregation gateway;

routing said emergency text to 911 message from said emedia aggregation gateway, via Internet protocol (IP), to an emedia distribution server;

converting said emergency text to 911 message from Internet protocol (IP) to teletype protocol (TTY); and

routing said emergency text to 911 message to a message recipient entity at said public safety answering point (PSAP).

17. The method for providing reliable text to 911 services according to claim 16, wherein said routing said emergency text to 911 message from said emedia aggregation gateway comprises:

routing said emergency text to 911 message via internet protocol (IP) from said emedia aggregation gateway to an emedia message broker; and

routing said emergency text to 911 message from said emedia message broker to said emedia distribution server.

18. The method for providing reliable text to 911 services according to claim 16, wherein:

said emergency text to 911 message is routed to an emedia local gateway at said public safety answering point (PSAP).

20. The method for providing reliable text to 911 services according to claim 17, wherein:

wherein said routing from said emedia message broker is location-based.