Systems and methods for robust and persistent emergency communications

• US 9,998,507 B2
• Filed: 12/21/2016
• Issued: 06/12/2018
• Est. Priority Date: 12/22/2015
• Status: Active Grant

• Current Assignee: Rapidsos, Inc.
• Original Assignee: Rapidsos, Inc.
• Inventors: Mehta, Anil, Martin, Michael John, Horelik, Nicholas Edward
• Primary Examiner(s): STRANGE, AARON N
• Application Number:
  US15/387,363
• Publication Number:
  US 20170180486A1
• Time in Patent Office: 538 Days
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 43/0823 Errors, e.g. transmission errors
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 49/552 by ensuring the integrity of packets received through redundant connections
• CPC Class Codes: H04L 51/222 using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area
• CPC Class Codes: H04L 65/401 wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04M 11/04 with alarm systems, e.g. fire, police or burglar alarm systems
• CPC Class Codes: H04M 3/5116 for emergency applications
• CPC Class Codes: H04M 7/0057 : Services where the data services network provides a telephone service in addition or as an alternative, e.g. for backup purposes, to the telephone service provided by the telephone services network
• CPC Class Codes: H04M 7/006 : Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/90 : Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 40/12 : based on transmission quality or channel quality
• CPC Class Codes: H04W 40/34 : Modification of an existing route
• CPC Class Codes: H04W 64/00 : Locating users or terminals or network equipment for network management purposes, e.g. mobility management
• CPC Class Codes: H04W 76/50 : for emergency connections

Abstract

Described herein are systems, devices, methods, and media for managing emergency communications by using multiple transport layer sessions to ensure robust communications during periods of poor communication quality and/or by providing persistent communication sessions that continue despite poor communication quality or disconnections.

Claims

1. An emergency management system (EMS) comprising at least one processor, a memory, a network element, and a computer program including instructions executable by the at least one processor to create a server software application for managing emergency communication sessions comprising:

a) a communication module managing an emergency communication session at an application layer with a communication device, the communication session comprising a plurality of communication channels comprising a voice channel between the communication device and an emergency dispatch center (EDC), at least one data channel between the EMS and the communication device, and at least one data channel between the EMS and the EDC, wherein the EMS provides data transfer between the communication device and the EDC during the emergency communication session;

b) a flow evaluation module evaluating data flow transmitted over the plurality of communication channels during the emergency communication session against one or more performance benchmarks;

c) a flow transfer module dynamically transferring data from a communication channel failing the one or more performance benchmarks to a different communication channel without terminating or suspending the emergency communication session; and

d) a session-stay-alive (SSA) module maintaining the emergency communication session with at least one of the communication device and the EDC when data flow is degraded sufficiently to result in disconnection of at least one of the plurality of communication channels, wherein the maintaining comprises using the data channels to provide user data from the communication device to the EDC when the voice channel is disconnected or degraded in order to facilitate an emergency response without requiring voice communications, wherein the user data comprises at least one of location information, emergency indication, and user health information.

2. The system of claim 1, wherein maintaining the communication session comprises modifying one or more session parameters for one or more of the plurality of communication channels to maintain connection with the communication device when data flow is degraded sufficiently to result in disconnection under one or more performance benchmarks.

3. The system of claim 1, wherein the plurality of communication channels comprises a primary communication channel and one or more secondary communication channels.

4. The system of claim 3, wherein the flow transfer module directs data flow through the primary communication channel and the one or more secondary communication channels simultaneously to provide data redundancy.

5. The system of claim 4, wherein the flow transfer module provides data redundancy when the primary communication channel is losing data packets beyond a defined threshold.

6. The system of claim 1, wherein the communication module assigns a unique session identification number (USIN) to the emergency communication session, wherein a new communication device obtains authentication to join the emergency communication session by providing the USIN.

7. The system of claim 1, further comprising a session management module saving a session state of the emergency communication session and transmitting the saved session state to the new communication device to enable the emergency communication session to continue with the new communication device using the saved session state.

8. A method for managing emergency communications comprising:

a) managing, by an emergency management system (EMS), an emergency communication session at an application layer with a communication device, the emergency communication session comprising a plurality of communication channels comprising a voice channel between the communication device and an emergency dispatch center (EDC), at least one data channel between the EMS and the communication device, and at least one data channel between the EMS and the EDC, wherein the EMS provides data transfer between the communication device and the EDC during the emergency communication session;

b) evaluating, by the EMS, data flow transmitted over the plurality of communication channels during the emergency communication session against one or more performance benchmarks;

c) dynamically transferring, by the EMS, data from a communication channel failing the one or more performance benchmarks to a different communication channel without terminating or suspending the emergency communication session; and

d) maintaining, by the EMS, the emergency communication session with at least one of the communication device and the EDC when data flow is degraded sufficiently to result in disconnection of at least one of the plurality of communication channels, wherein the maintaining comprises using the data channels to provide user data from the communication device to the EDC when the voice channel is disconnected or degraded in order to facilitate an emergency response without requiring voice communications, wherein the user data comprises at least one of location information, emergency indication, and user health information.

9. The method of claim 8, further comprising modifying, by the EMS, one or more session parameters for one or more of the plurality of communication channels to maintain connection with the communication device when data flow is degraded sufficiently to result in disconnection under one or more performance benchmarks.

10. The method of claim 8, wherein the plurality of communication channels comprises a primary communication channel and one or more secondary communication channels.

11. The method of claim 10, further comprising directing, by the EMS, data through the primary communication channel and the one or more secondary communication channels simultaneously to provide data redundancy.

12. The method of claim 11, wherein data redundancy is provided when the primary communication channel is losing data packets beyond a defined threshold.

13. The method of claim 8, further comprising assigning, by the EMS, a unique session identification number (USIN) to the emergency communication session, wherein a new communication device obtains authentication to join the emergency communication session by providing the USIN.

14. The method of claim 8, wherein maintaining the emergency communication session comprises saving a session state of the emergency communication session and transmitting the saved session state to the new communication device to enable the emergency communication session to continue with the new communication device using the saved session state.

15. A communication device comprising at least one processor, a memory, a network element, and a computer program including instructions executable by the at least one processor to create a software application for managing emergency communications comprising:

a) a communication module managing an emergency communication session comprising a plurality of communication channels comprising a voice channel between the communication device and an emergency dispatch center (EDC), at least one data channel between the communication device and an emergency management system (EMS), and at least one data channel between the EMS and the EDC, wherein the EMS provides data transfer between the communication device and the EDC during the emergency communication session;

b) a flow evaluation module evaluating data flow transmitted over the plurality of communication channels during the emergency communication session against one or more performance benchmarks;

c) a flow transfer module dynamically transferring data from a communication channel failing the one or more performance benchmarks to a different communication channel without terminating or suspending the emergency communication session; and

d) a session-stay-alive (SSA) module maintaining the emergency communication session with at least one of the EMS and the EDC when data flow is degraded sufficiently to result in disconnection of at least one of the plurality of communication channels, wherein the maintaining comprises using the data channels to provide user data from the communication device to the EMS when the voice channel is disconnected or degraded in order to facilitate an emergency response without requiring voice communications, wherein the user data comprises at least one of location information, emergency indication, and user health information.

16. The device of claim 15, wherein the plurality of communication channels comprises a primary communication channel and one or more secondary communication channels.

17. The device of claim 16, wherein the flow transfer module directs data flow through the primary communication channel and the one or more secondary communication channels simultaneously to provide data redundancy.

18. The device of claim 17, wherein the flow transfer module provides data redundancy when the primary communication channel is losing data packets beyond a defined threshold.

19. The device of claim 17, wherein the communication module harmonizes data received over the primary communication channel and the one or more secondary communication channels.

20. The device of claim 15, wherein the plurality of communication channels comprises a plurality of TCP data sessions, wherein each of the plurality of TCP data sessions uses a different routing path from the communication device and the EMS or EDC.

21. The device of claim 15, wherein the emergency communication session is assigned a unique session identification number (USIN) by the emergency management system or emergency dispatch center.

22. The device of claim 21, wherein the emergency communication session is transferred to a new emergency management system or a new emergency dispatch center, wherein the communication device obtains authentication to join the emergency communication session from the new emergency management system or new emergency dispatch center by providing the USIN assigned to the emergency communication session.

23. A method for managing emergency communications comprising:

a) managing, by a communication device, an emergency communication session comprising a plurality of communication channels comprising a voice channel between the communication device and an emergency dispatch center (EDC), at least one data channel between the communication device and an emergency management system (EMS), and at least one data channel between the EMS and the EDC, wherein the EMS provides data transfer between the communication device and the EDC during the emergency communication session;

b) evaluating, by the communication device, data flow transmitted over the plurality of communication channels during the emergency communication session against one or more performance benchmarks;

c) dynamically transferring, by the communication device, data from a communication channel failing the one or more performance benchmarks to a different communication channel without terminating or suspending the emergency communication session; and

d) maintaining, by the communication device, the emergency communication session with at least one of the EMS and the EDC when data flow is degraded sufficiently to result in disconnection of at least one of the plurality of communication channels, wherein the maintaining comprises using the data channels to provide user data from the communication device to the EMS when the voice channel is disconnected or degraded in order to facilitate an emergency response without requiring voice communications, wherein the user data comprises at least one of location information, emergency indication, and user health information.

24. The method of claim 23, wherein the plurality of communication channels comprises a primary communication channel and one or more secondary communication channels.

25. The method of claim 24, further comprising directing, by the communication device, data through the primary communication channel and the one or more secondary communication channels simultaneously to provide data redundancy.

26. The method of claim 25, wherein data redundancy is provided when the primary communication channel is losing data packets beyond a defined threshold.

27. The method of claim 25, further comprising harmonizing, by the communication device, data received over the primary communication channel and the one or more secondary communication channels.

28. The method of claim 23, wherein the plurality of communication channels comprises a plurality of TCP data sessions, wherein each of the plurality of TCP data sessions uses a different routing path from the communication device and the EMS or EDC.

29. The method of claim 23, wherein the emergency communication session is assigned a unique session identification number (USIN) by the emergency management system or emergency dispatch center.

30. The method of claim 29, further comprising transferring, by the communication device, to a new emergency management system or new emergency dispatch center, wherein the transferring comprises obtaining authentication to join the emergency communication session from the new emergency management system or new emergency dispatch center by providing the USIN assigned to the emergency communication session.