Systems and methods for robust and persistent emergency communications

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.

What is claimed is: 
     
         1 . An emergency management system 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 establishing an emergency communication session at an application layer with a first communication device upon receiving an user emergency request from the first device, the communication session comprising a plurality of transport layer sessions simultaneously connected to the first device;   b) a flow evaluation module evaluating data flow transmitted over each of the plurality of transport layer sessions against one or more performance benchmarks; and   c) a flow transfer module dynamically transferring data flow from any transport layer session failing the one or more performance benchmarks to another transport layer session of the plurality of transport layer sessions during the communication session;   d) a device management module associating a new communication device with the communication session when provided with authentication to join the communication session and detecting when the first communication device is dropped from the communication session; and   e) a session management module maintaining the emergency communication session when the first communication device is dropped by relocating data flow to the new communication device, wherein the communication session at the application layer continues with the new communication device replacing the dropped first communication device.   
     
     
         2 . The system of  claim 1 , further comprising a session-stay-alive (SSA) module modifying one or more session parameters for one or more of the plurality of transport layer sessions to maintain connection with the first or new communication device when data flow is degraded sufficiently to result in disconnection under one or more performance benchmarks corresponding to industry standard acceptable limits. 
     
     
         3 . The system of  claim 1 , wherein the plurality of transport layer sessions comprise a primary transport layer session and one or more secondary transport layer sessions. 
     
     
         4 . The system of  claim 3 , wherein the flow transfer module directs data flow through the primary transport layer session and the one or more secondary transport layer sessions simultaneously when the flow evaluation module determines data redundancy is needed. 
     
     
         5 . The system of  claim 4 , wherein the flow evaluation module determines data redundancy is needed when data flow over the primary transport layer session 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 communication session, wherein the new communication device obtains authentication by providing the USIN assigned to the communication session. 
     
     
         7 . The system of  claim 1 , wherein the session management module saves a session state of the communication session and transmits the saved session state to the new communication device to enable the communication session to continue with the new communication device using the same session state. 
     
     
         8 . A method for managing emergency communications comprising:
 a) establishing, by a server application, an emergency communication session at an application layer with a first communication device upon receiving an user emergency request from the first device, the communication session comprising a plurality of transport layer sessions simultaneously connected to the first device;   b) evaluating, by the server application, data flow transmitted over each of the plurality of transport layer sessions against one or more performance benchmarks;   c) dynamically transferring, by the server application, data flow from any transport layer session failing the one or more performance benchmarks to another transport layer session of the plurality of transport layer sessions during the communication session;   d) associating, by the server application, a new communication device with the communication session when provided with authentication to join the communication session and detecting when the first communication device is dropped from the communication session; and   e) maintaining, by the server application, the emergency communication session when the first communication device is dropped by relocating data flow to the new communication device, wherein the communication session at the application layer continues with the new communication device replacing the dropped first communication device.   
     
     
         9 . The method of  claim 8 , further comprising modifying, by the server application, one or more session parameters for one or more of the plurality of transport layer sessions to maintain connection with the first or new communication device when data flow is degraded sufficiently to result in disconnection under one or more performance benchmarks corresponding to industry standard acceptable limits. 
     
     
         10 . The method of  claim 8 , wherein the plurality of transport layer sessions comprise a primary transport layer session and one or more secondary transport layer sessions. 
     
     
         11 . The method of  claim 10 , wherein the transferring data flow comprises directing data flow through the primary transport layer session and the one or more secondary transport layer sessions simultaneously when data redundancy is needed. 
     
     
         12 . The method of  claim 11 , wherein data redundancy is needed when data flow over the primary transport layer session is losing data packets beyond a defined threshold. 
     
     
         13 . The method of  claim 8 , further comprising assigning, by the server application, a unique session identification number (USIN) to the communication session, wherein the new communication device obtains authentication by providing the USIN assigned to the communication session. 
     
     
         14 . The method of  claim 8 , wherein maintaining the emergency communication session comprises saving a session state of the communication session and transmitting the saved session state to the new communication device to enable the communication session to continue with the new communication device using the same 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 establishing a communication session with an emergency management system (EMS) or emergency dispatch center (EDC), the communication session comprising a plurality of transport layer sessions simultaneously connected to the EMS or EDC;   b) a flow evaluation module evaluating data flow transmitted over each of the plurality of transport layer sessions against one or more performance benchmarks;   c) a flow transfer module dynamically transferring data flow from any transport layer session failing the one or more performance benchmarks to another transport layer session of the plurality of transport layer sessions during the communication session; and   d) a session-stay-alive (SSA) module modifying one or more session parameters for one or more of the plurality of transport layer sessions to maintain connection with the emergency management system or emergency dispatch center when data flow is degraded sufficiently to result in disconnection under one or more performance benchmarks corresponding to industry standard acceptable limits.   
     
     
         16 . The device of  claim 15 , wherein the plurality of transport layer sessions comprise a primary transport layer session and one or more secondary transport layer sessions. 
     
     
         17 . The device of  claim 16 , wherein the flow transfer module directs data flow through the primary transport layer session and the one or more secondary transport layer sessions simultaneously when the flow evaluation module determines data redundancy is needed. 
     
     
         18 . The device of  claim 17 , wherein the flow evaluation module determines data redundancy is needed when data flow over the primary transport layer session is losing data packets beyond a defined threshold. 
     
     
         19 . The device of  claim 17 , wherein the communication module harmonizes data flow received over the primary transport layer session and the one or more secondary transport layer sessions. 
     
     
         20 . The device of  claim 15 , wherein the plurality of transport layer sessions comprises a plurality of TCP transport layer sessions, wherein each of the plurality of TCP transport layer sessions uses a different routing path from the communication device and the EMS or EDC. 
     
     
         21 . The device of  claim 15 , wherein the 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 communication session is transferred to a new emergency management system or emergency dispatch center, wherein the device obtains authentication to join the communication session from the new emergency management system or emergency dispatch center by providing the USIN assigned to the communication session. 
     
     
         23 . A method for managing emergency communications comprising:
 a) establishing, by a communication device, a communication session with an emergency management system (EMS) or emergency dispatch center (EDC), the communication session comprising a plurality of transport layer sessions simultaneously connected to the EMS or EDC;   b) evaluating, by the communication device, data flow transmitted over each of the plurality of transport layer sessions against one or more performance benchmarks;   c) dynamically transferring, by the communication device, data flow from any transport layer session failing the one or more performance benchmarks to another transport layer session of the plurality of transport layer sessions during the communication session; and   d) modifying, by the communication device, one or more session parameters for one or more of the plurality of transport layer sessions to maintain connection with the emergency management system or emergency dispatch center when data flow is degraded sufficiently to result in disconnection under one or more performance benchmarks corresponding to industry standard acceptable limits.   
     
     
         24 . The method of  claim 23 , wherein the plurality of transport layer sessions comprise a primary transport layer session and one or more secondary transport layer sessions. 
     
     
         25 . The method of  claim 24 , wherein the transferring data flow comprises directing data flow through the primary transport layer session and the one or more secondary transport layer sessions simultaneously when data redundancy is needed. 
     
     
         26 . The method of  claim 25 , wherein data redundancy is needed when data flow over the primary transport layer session is losing data packets beyond a defined threshold. 
     
     
         27 . The method of  claim 25 , further comprising harmonizing, by the communication device, data flow received over the primary transport layer session and the one or more secondary transport layer sessions. 
     
     
         28 . The method of  claim 23 , wherein the plurality of transport layer sessions comprises a plurality of TCP transport layer sessions, wherein each of the plurality of TCP transport layer sessions uses a different routing path from the communication device and the EMS or EDC. 
     
     
         29 . The method of  claim 23 , wherein the 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 emergency dispatch center, wherein the transferring comprises obtaining authentication to join the communication session from the new emergency management system or emergency dispatch center by providing the USIN assigned to the communication session.