System and method for connecting a communication to a client

• US 10,122,763 B2
• Filed: 06/16/2016
• Issued: 11/06/2018
• Est. Priority Date: 05/23/2011
• Status: Active Grant

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Lawson, Jeffrey Gordon, Wolthuis, John Robert, Cooke, Evan Mansfield, Boerjesson, Jonas Mikael
• Primary Examiner(s): Scott, Randy A
• Application Number:
  US15/184,621
• Publication Number:
  US 20160323320A1
• Time in Patent Office: 873 Days
• Field of Search: 713167, 713172, 713185, 713190, 726 1, 726 4, 726 6, 726 8, 726 10
• CPC Class Codes: H04L 2101/30 Types of network names
• CPC Class Codes: H04L 2101/33 containing protocol addresses or telephone numbers
• 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/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 9/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• 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: H04W 76/10 Connection setup

Abstract

A method and system for connecting a communication to a client including at a system bridge, establishing a client subscription connection with a client device; receiving an incoming communication request at the system bridge; publishing an incoming communication notification from the system bridge to the client device; receiving a client communication at the system bridge; and merging the incoming communication request into the client communication at the system bridge.

Claims

1. A method comprising:

a policy engine receiving a connection request from a client device, the connection request including a client identifier;

the policy engine sending the received client identifier to an authentication server;

the policy engine receiving an authentication token for the client identifier from the authentication server;

the policy engine authenticating the client device by verifying the authentication token;

responsive to verification of the authentication token by the policy engine, a system bridge establishing a persistent client subscription connection with the client device via a pub-sub system, the persistent client subscription connection being a connection of the pub-sub system;

the system bridge receiving an incoming communication;

the system bridge encrypting a communication token with a key unique to the system bridge and pushing the encrypted communication token to the client device via the persistent client subscription connection of the pub-sub system;

the system bridge receiving the encrypted communication token and a client communication from the client device; and

the system bridge merging the received incoming communication with the client communication received from the client device by using the encrypted communication token received from the client device.

2. The method of claim 1, wherein the encrypted communication token identifies the system bridge within a distributed computing cluster comprising at least two system bridges.

3. The method of claim 1, wherein the encrypted communication token comprises a communication identifier and a host identifier.

4. The method of claim 1, wherein the client device is a mobile device.

5. The method of claim 4, wherein a native application running on the mobile device controls the mobile device to send the connection request to the policy engine.

6. The method of claim 5, wherein the encrypted communication token comprises a communication identifier and a host identifier.

7. The method of claim 5, wherein the encrypted communication token identifies the system bridge within a distributed computing cluster comprising at least two system bridges.

8. The method of claim 1, wherein the system bridge receives the encrypted communication token from the client device via the persistent client subscription connection of the pub-sub system.

9. The method of claim 2, wherein the system bridge receives the client communication from the client device via the persistent client subscription connection of the pub-sub system.

10. The method of claim 7, wherein the system bridge receives the encrypted communication token from the client device via the persistent client subscription connection of the pub-sub system.

11. The method of claim 10, wherein the system bridge receives the client communication from the client device via the persistent client subscription connection of the pub-sub system.

12. The method of claim 9, wherein the client communication is communication of a voice communication session.

13. The method of claim 9, wherein the client communication is communication of a video communication session.

14. The method of claim 9, wherein the client communication is communication of a screen sharing session.

15. The method of claim 9, wherein the client communication is communication of an IP messaging session.