SYSTEM AND METHOD FOR REAL TIME COMMUNICATING WITH A CLIENT APPLICATION

• US 20140044123A1
• Filed: 10/15/2013
• Published: 02/13/2014
• Est. Priority Date: 05/23/2011
• Status: Abandoned Application

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Lawson, Jeffrey, Wolthuis, John, Cooke, Evan, Borjesson, Jonas, Simutis, Rob, Tarricone, Brian, Kim, Edward, Lokare, Ameya
• Application Number:
  US14/054,254
• Publication Number:
  US 20140044123A1
• Time in Patent Office: Days
• US Class Current: 370/352
• 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 65/1023 Media gateways
• CPC Class Codes: H04L 65/1046 Call controllers; Call servers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04W 76/10 Connection setup

Abstract

A system and method for communicating with a client application that can include establishing a client signaling communication channel with a first client application; receiving a communication request from the first client application through the client signaling communication channel, wherein the communication request contains at least an authentication token and a specified communication destination; verifying the authentication token; if the authentication token is verified, at the system bridge, establishing a signaling communication channel with the communication destination and a second media communication channel with the specified communication destination; at the system bridge, establishing a first media communication channel with the client application; and merging the first media communication channel with the second media communication channel.

Claims

1. A method for making outgoing communications comprising:

at a system bridge, establishing a client signaling communication channel with a first client application;

receiving a communication request from the first client application through the client signaling communication channel, wherein the communication request contains at least an authentication token and a specified communication destination;

verifying the authentication token;

if the authentication token is verified, at the system bridge, establishing a signaling communication channel with the communication destination and a second media communication channel with the specified communication destination;

at the system bridge, establishing a first media communication channel with the client application; and

merging the first media communication channel with the second media communication channel.

2. The method of claim 1, wherein the first media communication channel is of a first type supported by a browser and the second media communication channel is of a second type, wherein the first type is not the same as the second type.

3. The method of claim 2, wherein merging the first media communication channel with the second media communication channel further comprises transcoding media of the first media communication channel to a format compatible with the second media communication channel and transmitting the transcoded media of the first media communication channel in the second media communication channel, and transcoding media of the second media communication channel to a compatible format of the first media communication channel and transmitting the transcoded media of the second media communication channel in the first media communication channel.

4. The method of claim 3, wherein the first media communication channel is a WebRTC communication channel, and the second media communication channel is a real time messaging protocol (RTMP) channel.

5. The method of claim 4, wherein the client signaling communication channel is a serialized data signaling channel;

and wherein the second signaling communication channel is a session initiation protocol (SIP) channel.

6. The method of claim 2, wherein establishing the client signaling communication connection with the first client application is established over a websocket.

7. The method of claim 2, wherein merging the first media communication channel with the second media communication channel further comprises transcoding between media formats according to a selected real time protocol of the client application.

8. The method of claim 2, further comprising at the client application, selecting real time protocol capabilities of the client application and implementing a selected real time protocol in the first media communication channel.

9. The method of claim 2, when the communication request contains an authorization token;

and further comprising authorizing actions of a communication according to the authorization token.

10. The method of claim 2, wherein the communication destination is a public switched telephone network (PSTN) device.

11. The method of claim 2, wherein the communication destination is a session initiation protocol (SIP) device.

12. The method of claim 2, wherein the communication destination is a communication control application.

13. The method of claim 2, wherein the first media communication channel and the second media communication channel are video media communication channels.

14. A method for inbound communications comprising:

receiving a connection request from a first client application, wherein the connection request contains at least an authentication token;

verifying at least the authentication token;

at a system bridge, establishing a client signaling communication channel with the first client application if the authentication token is successfully verified;

at the system bridge, receiving an incoming communication request from a calling entity, the communication request signaled over a second signaling communication channel, and wherein the communication request includes a client identifier;

identifying the established client signaling communication channel from the client identifier;

establishing a first media communication channel with the first client application through the identified client signaling communication channel;

at the system bridge, establishing a second media communication channel with the calling entity; and

merging the first media communication channel with the second media communication channel.

15. The method of claim 14, wherein the first media communication channel is of a first type supported by a browser and the second media communication channel is of a second type, wherein the first type is not the same as the second type.

16. The method of claim 15, further comprising after establishing a client signaling communication channel, registering a client identifier associated with the client signaling communication channel, wherein identifying an established client signaling communication channel from the client identifier comprises querying registered client identifiers for an established client signaling communication channel associated with the client identifier.

17. The method of claim 15, wherein namespace of a client identifier is scoped to within an account.

18. The method of claim 15, wherein merging the first media communication channel with the second media communication channel further comprises transcoding between media formats according to a selected real time protocol of the client application.

19. The method of claim 18, wherein the client signaling communication channel is a serialized data signaling channel;

wherein the second signaling communication channel is a session initiation protocol (SIP) channel;

wherein the first media communication channel is a WebRTC communication channel; and

wherein the second media communication channel is a real time messaging protocol (RTMP) channel.

20. The method of claim 15, wherein the first media communication channel and the second media communication channel are video media communication channels.