System and method for connecting a communication to a client

• US 9,398,622 B2
• Filed: 05/23/2012
• Issued: 07/19/2016
• Est. Priority Date: 05/23/2011
• Status: Active Grant

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Lawson, Jeffrey G., Wolthuis, John, Cooke, Evan Mansfield, Boerjesson, Jonas
• Primary Examiner(s): Scott, Randy
• Application Number:
  US13/478,495
• Publication Number:
  US 20120304245A1
• Time in Patent Office: 1,518 Days
• Field of Search: 726/1, 726/5, 726/9, 726/12, 709/225, 709/226, 709/227
• US Class Current: 1/1
• 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:

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,

wherein publishing the incoming communication notification comprises pushing a communication token from the system bridge to the client device,

wherein the communication token comprises a communication identifier and a host identifier,

wherein the host identifier identifies the system bridge within a distributed computing cluster comprising at least two system bridges, and

wherein the method further comprises;

encrypting the communication token with a key unique to the system bridge.

2. The method of claim 1, wherein establishing a client subscription connection further comprises registering a client identifier at the system bridge.

3. The method of claim 2, wherein the client identifier comprises a name space and one or more subdirectories.

4. The method of claim 2, further comprising encrypting the client identifier.

5. The method of claim 1, wherein receiving an incoming communication request comprises receiving an incoming communication request from a cloud-based communication router.

6. The method of claim 5, wherein receiving an incoming communication request comprises receiving an incoming communication request from a cloud-based communication router that is integrated into the system bridge.

7. The method of claim 5, wherein the incoming communication request comprises the client identifier.

8. The method of claim 7, wherein the incoming communication request comprises the name space and at least one subdirectory.

9. The method of claim 1, further comprising receiving the encrypted communication token at the system bridge from the client and decrypting the encrypted communication token at the system bridge.

10. The method of claim 1, wherein the client communication comprises a transport layer message to the system bridge.

11. The method of claim 10, wherein the client communication comprises an application identifier comprising a name-spaced endpoint.

12. The method of claim 11, wherein the name-spaced endpoint is selected from the group consisting of:

an associated phone number, an application URI, a status callback URI, an allowed user designation, a pricing model designation, and an account application setting.

13. The method of claim 1, further comprising authenticating the client communication at a policy engine.

14. The method of claim 13, further comprising merging the incoming communication request into the client communication at the system bridge in response to client authentication at the policy engine.