Emergency call back for remote workers

• US 10,225,401 B2
• Filed: 02/25/2016
• Issued: 03/05/2019
• Est. Priority Date: 02/25/2016
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Incorporated
• Inventors: Chatterjee, Manish, Dhal, Purnendu, Mendiratta, Harsh V.
• Primary Examiner(s): El-Zoobi, Maria
• Application Number:
  US15/053,087
• Publication Number:
  US 20170251105A1
• Time in Patent Office: 1,104 Days
• Field of Search: 379 37- 52
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 12/4679 Arrangements for the registration or de-registration of VLAN attribute values, e.g. VLAN identifiers, port VLAN membership
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/80 Responding to QoS
• 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 2203/6054 Biometric subscriber identification
• CPC Class Codes: H04M 3/42195 Arrangements for calling back a calling subscriber when the wanted subscriber ceases to be busy H04M3/48
• CPC Class Codes: H04M 3/5116 for emergency applications
• CPC Class Codes: H04M 3/5231 with call back arrangements
• CPC Class Codes: H04W 4/90 Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]

Abstract

A fingerprint is received from a communication endpoint. The fingerprint is based on a hardware identifier of the communication endpoint. For example the fingerprint may be based on a Media Access Control (MAC) address of the communication endpoint. A request for an emergency call from the communication endpoint is received that also includes the fingerprint. For instance, a user may initiate a 911 call from the communication endpoint. The emergency call is established. After the emergency call is disconnected, a request for an emergency call back is received. For example, if the emergency call prematurely disconnected, the emergency call back is initiated. The request for the emergency call back is routed to the communication endpoint based on the fingerprint to ensure that the emergency call is properly completed.

Claims

1. A system comprising:

a microprocessor; and

a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that cause the microprocessor to execute;

a communication manager that receives a fingerprint in a first Transmission Communication Protocol (TCP) SYN message, wherein the fingerprint is based on a hardware identifier of a first communication endpoint and wherein the hardware identifier of the first communication endpoint is based on at least one of a Media Access Control (MAC) address, a circuit board identifier, a boot up identifier, a hardware serial number, and a Virtual Local Area Network Identifier (VLAN ID);

receives a request for an emergency call from the first communication endpoint, wherein the first communication endpoint is on a first network, and wherein the request for the emergency call comprises the fingerprint;

establishes the emergency call with a second communication endpoint, wherein the second communication endpoint is on a second network;

receives a request for an emergency call back from the second communication endpoint, wherein the request for the emergency call back comprises the fingerprint and wherein the request for the emergency call back is based on a disconnection of the first communication endpoint from the established emergency call; and

routes the request for the emergency call back received from the second communication endpoint on the second network to the first communication endpoint on the first network based on the fingerprint received in the request for the emergency call back.

2. The system of claim 1, wherein a user of the first communication endpoint is not logged in and can still make the request for the emergency call and wherein the user of the first communication endpoint has to be logged in order to make a non-emergency call.

3. The system of claim 1, wherein the disconnection of the first communication endpoint from the established emergency call is based on a reset of a connection-oriented transport layer protocol.

4. The system of claim 1, wherein the request for the emergency call is received in a first Transmission Communication Protocol (TCP) connection, wherein the first TCP SYN message is received in the first TCP connection, and wherein:

the communication manager receives the fingerprint in a second TCP SYN message in a second TCP connection from the first communication endpoint after the disconnection of the first communication endpoint from the established emergency call, and wherein the request for the emergency call back is routed to the first communication endpoint based on the second TCP SYN message in the second TCP connection and based on connection attributes in the second TCP SYN.

5. The system of claim 4, wherein the first communication endpoint uses a first Internet Protocol (IP) address in the first TCP connection and the first communication endpoint uses a second IP address in the second TCP connection.

6. The system of claim 1, wherein the request for the emergency call is a first SIP INVITE, wherein the received fingerprint is the MAC address of the first communication endpoint and wherein:

the communication manager hashes a domain name, a contact address, and the MAC address of the first communication endpoint into a hash value and sends the first SIP INVITE with the hash value as the fingerprint in a SIP Contact header.

7. The system of claim 6, wherein the request for the emergency call back is a second SIP INVITE that has the hash value in a SIP request Universal Resource Identifier (URI) and wherein the hash value in the SIP request URI is used by the communication manager to route the second SIP INVITE to the first communication endpoint.

8. The system of claim 1, wherein the fingerprint is based on at least one of a hash of the hardware identifier and the VLAN ID.

9. The system of claim 1, wherein:

a device identity engine receives the hardware identifier, determines, based on the hardware identifier, a device token from a range of device tokens, wherein the range of device tokens comprises device tokens from a registered Universal Resource Locator (URL) for a vendor of the first communication endpoint and sends the device token to the first communication endpoint.

10. The system of claim 1, wherein the request for the emergency call is a SIP INVITE message.

11. A method comprising:

receiving, by a processor, in a first Transmission Communication Protocol (TCP) SYN message, a fingerprint, wherein the fingerprint is based on a hardware identifier of a first communication endpoint and wherein the hardware identifier of the first communication endpoint is based on at least one of a Media Access Control (MAC) address, a circuit board identifier, a boot up identifier, a hardware serial number, and a Virtual Local Area Network Identifier (VLAN ID);

receiving, by the processor, a request for an emergency call from the first communication endpoint, wherein the first communication endpoint is on a first network and wherein the request for the emergency call comprises the fingerprint;

establishing, by the processor, the emergency call with a second communication endpoint, wherein the second communication endpoint is on a second network;

receiving, by the processor, a request for an emergency call back from the second communication endpoint, wherein the request for the emergency call back comprises the fingerprint and wherein the request for the emergency call back is based on a disconnection of the first communication endpoint from the established emergency call; and

routing, by the processor, the request for the emergency call back received from the second communication endpoint on the second network to the first communication endpoint on the first network based on the fingerprint received in the request for the emergency call back.

12. The method of claim 11, wherein a user of the first communication endpoint is not logged in and can still make the request for the emergency call and wherein the user of the first communication endpoint has to be logged in order to make a non-emergency call.

13. The method of claim 11, wherein the disconnection of the first communication endpoint from the established emergency call is based on a reset of a connection-oriented transport layer protocol.

14. The method of claim 11, wherein the request for the emergency call is received in a first Transmission Communication Protocol (TCP) connection, wherein the first TCP SYN message is received in the first TCP connection, and further comprising:

after the disconnection of the first communication endpoint from the established emergency call, receiving, by the processor, the fingerprint in a second TCP SYN message in a second TCP connection from the first communication endpoint, wherein the request for the emergency call back is routed to the first communication endpoint based on the second TCP SYN message in the second TCP connection.

15. The method of claim 14, wherein the first communication endpoint uses a first Internet Protocol (IP) address in the first TCP connection and the first communication endpoint uses a second IP address in the second TCP connection.

16. The method of claim 11, wherein the request for the emergency call is a first SIP INVITE, wherein the received fingerprint is the MAC address of the first communication endpoint, and further comprising:

hashing a domain name, a contact address, and the MAC address of the first communication endpoint into a hash value; and

sending the first SIP INVITE with the hash value as the fingerprint in a SIP Contact header.

17. The method of claim 16, wherein the request for the emergency call back is a second SIP INVITE that has the hash value in a SIP request Universal Resource Identifier (URI) and wherein the hash value in the SIP request URI is used by the processor to route the second SIP INVITE to the first communication endpoint.

18. The method of claim 11, wherein the fingerprint is based on at least one of a hash of the hardware identifier, and the VLAN ID.

19. The method of claim 11, further comprising:

receiving, by the processor, the MAC address of the first communication endpoint;

determining, by the processor, based on the MAC address, the fingerprint from a range of fingerprints, wherein the range of fingerprints comprises device tokens from a registered Universal Resource Locator (URL) for a vendor of the first communication endpoint; and

sending, by the processor, the fingerprint to the first communication endpoint.

20. The method of claim 11, wherein the fingerprint is based on the VLAN ID.