System and method for processing media requests during telephony sessions

• US 9,906,651 B2
• Filed: 01/24/2017
• Issued: 02/27/2018
• 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): HUYNH, KHOA B
• Application Number:
  US15/413,660
• Publication Number:
  US 20170134587A1
• Time in Patent Office: 399 Days
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: H04L 65/1013 Network architectures, gateways, control or user entities
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• 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 69/329 in the application layer [OSI layer 7]
• 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
• CPC Class Codes: H04M 7/0075 Details of addressing, directories or routing tables

Abstract

In a preferred embodiment, the method of caching media used in a telephony application includes: receiving a media request; sending the media request to a media layer using HTTP; the a media layer performing the steps of checking in a cache for the media resource; processing the media request within a media processing server; and storing the processed media in the cache as a telephony compatible resource specified by a persistent address. The system of the preferred embodiment includes a call router and a media layer composed of a cache and media processing server.

Claims

1. A method comprising:

receiving a media processing instruction at a call router system;

converting the media processing instruction into a media processing REST API request that specifies a persistent Universal Resource Identifier (URI) that identifies a media processing server by using the call router system;

providing the REST API request from the call router system to a cache system;

responsive to a determination that the persistent URI is not identified in the cache system, forwarding the REST API request from the cache system to the media processing server identified by the persistent URI;

processing the REST API request by using the media processing server to generate a first telephony compatible media resource;

providing the first telephony compatible media resource from the media processing server to the cache system;

storing the first telephony compatible media resource at the cache system in association with the persistent URI; and

forwarding the first telephony compatible media resource from the cache system to the call router system as a response to the REST API request.

2. The method of claim 1, wherein the cache system uses the persistent URI to determine whether the first telephony compatible media resource is stored at the cache system.

3. The method of claim 1, wherein the media processing instruction is associated with a first telephony session of the call router system, and wherein the REST API request includes state information of the first telephony session.

4. The method of claim 1, wherein the cache system uses the persistent URI to determine whether the first telephony compatible media resource is stored at the cache system.

5. The method of claim 1, wherein the REST API request is a request in accordance with an API of the media processing server.

6. The method of claim 3, wherein the REST API request is a request in accordance with an API of the media processing server.

7. The method of claim 1, further comprising:

receiving a second media processing instruction at the call router system;

converting the second media processing instruction into a second media processing REST API request that specifies a second persistent URI that identifies a different second media processing server by using the call router system;

providing the second media processing REST API request from the call router system to the cache system;

responsive to a determination that the second persistent URI is not identified in the cache system, forwarding the second media processing REST API request from the cache system to the second media processing server;

processing the second media processing REST API request by using the second media processing server to generate a second telephony compatible media resource;

providing the second telephony compatible media resource from the second media processing server to the cache system;

storing the second telephony compatible media resource at the cache system in association with the second persistent URI; and

forwarding the second telephony compatible media resource from the cache system to the call router system as a response to the second media processing REST API request.

8. A method comprising:

receiving a first media processing instruction at a call router system;

converting the first media processing instruction into a first media processing REST API request that specifies a first persistent Universal Resource Identifier (URI) that identifies a first media processing server by using the call router system;

providing the first media processing REST API request from the call router system to a cache system;

responsive to a determination that the first persistent URI is not identified in the cache system, forwarding the first media processing REST API request from the cache system to the first media processing server identified by the first persistent URI;

processing the first media processing REST API request by using the first media processing server to generate a first telephony compatible media resource;

providing the first telephony compatible media resource from the first media processing server to the cache system;

storing the first telephony compatible media resource at the cache system in association with the first persistent URI;

forwarding the first telephony compatible media resource from the cache system to the call router system as a response to the first media processing REST API request;

receiving a second media processing instruction at the call router system;

converting the second media processing instruction into a second media processing REST API request that specifies the first persistent Universal Resource Identifier (URI) that identifies the first media processing server by using the call router system;

providing the second media processing REST API request from the call router system to the cache system;

responsive to the second media processing REST API request, the cache system determining that the first persistent URI is identified in the cache system, and forwarding the associated first telephony compatible media resource from the cache system to the call router system as a response to the second media processing REST API request.

9. A system comprising:

a call router system;

a cache system; and

a media processing server,

wherein the call router system is constructed to;

receive a media processing instruction;

convert the media processing instruction into a media processing REST API request that specifies a persistent Universal Resource Identifier (URI) that identifies the media processing server; and

provide the REST API request to the cache system;

wherein the cache system is constructed to;

responsive to a determination that the persistent URI is not identified in the cache system, forward the REST API request to the media processing server identified by the persistent URI,

wherein the media processing server is constructed to;

process the REST API request to generate a first telephony compatible media resource; and

provide the first telephony compatible media resource to the cache system, and

wherein the cache system is constructed to;

store the first telephony compatible media resource in association with the persistent URI; and

forward the first telephony compatible media resource to the call router system as a response to the REST API request.

10. The system of claim 9, wherein the cache system is constructed to use the persistent URI to determine whether the first telephony compatible media resource is stored at the cache system.

11. The system of claim 9, wherein the media processing instruction is associated with a first telephony session of the call router system, and wherein the REST API request includes state information of the first telephony session.

12. The system of claim 11, wherein the cache system is constructed to use the persistent URI to determine whether the first telephony compatible media resource is stored at the cache system.

13. The system of claim 9, wherein the REST API request is a request in accordance with an API of the media processing server.

14. The system of claim 11, wherein the REST API request is a request in accordance with an API of the media processing server.

15. The system of claim 9,

further comprising a second media processing server,

wherein the call router system is constructed to:

receive a second media processing instruction;

convert the second media processing instruction into a second media processing REST API request that specifies a second persistent URI that identifies the second media processing server; and

provide the second media processing REST API request to the cache system,

wherein responsive to a determination that the second persistent URI is not identified in the cache system, the cache system is constructed to forward the second media processing REST API request to the second media processing server,

wherein the second media processing server is constructed to;

process the second media processing REST API request to generate a second telephony compatible media resource; and

provide the second telephony compatible media resource to the cache system;

wherein the cache system is constructed to;

store the second telephony compatible media resource in association with the second persistent URI; and

forward the second telephony compatible media resource to the call router system as a response to the second media processing REST API request.