System and method for processing telephony sessions

• US 10,893,078 B2
• Filed: 07/23/2019
• Issued: 01/12/2021
• Est. Priority Date: 04/02/2008
• Status: Active Grant

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Lawson, Jeff, Wolthuis, John, Cooke, Evan
• Primary Examiner(s): Thompson, Jr., Otis L
• Application Number:
  US16/520,190
• Publication Number:
  US 20190349409A1
• Time in Patent Office: 539 Days
• Field of Search: None
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• 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 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 9/0643 Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
• CPC Class Codes: H04L 9/3247 involving digital signatures
• CPC Class Codes: H04M 1/2473 Telephone terminals interfacing a personal computer, e.g. using an API (Application Programming Interface) details of API H04M7/0021
• CPC Class Codes: H04M 7/0021 Details of Application Programming Interfaces
• CPC Class Codes: H04M 7/003 Click to dial services

Abstract

In one embodiment, the method of processing telephony sessions includes: communicating with an application server using an application layer protocol; processing telephony instructions with a call router; and creating call router resources accessible through a call router Application Programming Interface (API). In another embodiment, the system for processing telephony sessions includes: a call router, a URI for an application server, a telephony instruction executed by the call router, and a call router API resource.

Claims

1. A method comprising:

sending a first communication to an application server using an application layer protocol;

creating a call router resource accessible through an Application Programming Interface (API) of a call router, the call router resource being accessible at an addressable Uniform Resource Identifier (URI);

mapping a telephony session to the URI, the URI being associated with the application server;

sending, to the application server, a second communication comprising state information of the telephony session;

receiving, from the application server, a third communication comprising telephony instructions for sequential processing; and

interacting with media of the call router according to the API of the call router.

2. The method of claim 1, further comprising:

sequentially processing the telephony instructions.

3. The method of claim 1, further comprising:

modifying the call router resource to alter a state of the call router.

4. The method of claim 1, further comprising:

embedding state information of the telephony session into the URI.

5. The method of claim 1, wherein:

the telephony session comprises a telephony voice session; and

the method further comprises;

initiating the telephony voice session to a telephony device.

6. The method of claim 1, further comprising:

converting the telephony instructions into executable operations to process the telephony session.

7. The method of claim 1, wherein the telephony instructions are encoded in Extensible Markup Language (XML).

8. The method of claim 1, further comprising sending a digital signature with the first communication.

9. The method of claim 8, wherein the digital signature is a cryptographic hash generated by a key, the key is shared by the call router, and the cryptographic hash is included in the URI.

10. The method of claim 1, wherein the telephony session includes a sent Short Message Service (SMS) message.

11. A system comprising:

a memory that stores instructions; and

one or more processors configured by the instructions to perform operations comprising;

sending a first communication to an application server using an application layer protocol;

creating a call router resource accessible through an Application Programming Interface (API) of a call router, the call router resource being accessible at an addressable Uniform Resource Identifier (URI);

mapping a telephony session to the URI, the URI being associated with the application server;

sending, to the application server, a second communication comprising state information of the telephony session;

receiving, from the application server, a third communication comprising telephony instructions for sequential processing; and

interacting with media of the call router according to the API of the call router.

12. The system of claim 11, wherein the operations further comprise:

sequentially processing the telephony instructions.

13. The system of claim 11, wherein the operations further comprise:

modifying the call router resource to alter a state of the call router.

14. The system of claim 11, wherein the operations further comprise:

embedding state information of the telephony session into the URI.

15. The system of claim 11, wherein:

the telephony session comprises a telephony voice session; and

the operations further comprise;

initiating the telephony voice session to a telephony device.

16. The system of claim 11, wherein the operations further comprise:

converting the telephony instructions into executable operations to process the telephony session.

17. The system of claim 11, wherein the telephony instructions are encoded in Extensible Markup Language (XML).

18. A non-transitory machine-readable medium that stores instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

sending a first communication to an application server using an application layer protocol;

creating a call router resource accessible through an Application Programming Interface (API) of a call router, the call router resource being accessible at an addressable Uniform Resource Identifier (URI);

mapping a telephony session to the URI, the URI being associated with the application server;

sending, to the application server, a second communication comprising state information of the telephony session;

receiving, from the application server, a third communication comprising telephony instructions for sequential processing; and

interacting with media of the call router according to the API of the call router.

19. The non-transitory machine-readable medium of claim 18, wherein the operations further comprise:

sequentially processing the telephony instructions.

20. The non-transitory machine-readable medium of claim 18, wherein the operations further comprise:

modifying the call router resource to alter a state of the call router.