SYSTEM AND METHOD FOR RUNNING A MULTI-MODULE TELEPHONY APPLICATION

• US 20110081008A1
• Filed: 10/07/2010
• Published: 04/07/2011
• Est. Priority Date: 10/07/2009
• Status: Active Grant

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Cooke, Evan, Lawson, Jeffrey, Wolthuis, John
• Granted Patent: US 8,582,737 B2
• Time in Patent Office: Days
• US Class Current: 379/114.03
• CPC Class Codes: H04M 15/41 Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/43 Billing software details
• CPC Class Codes: H04M 15/51 for resellers, retailers or service providers
• CPC Class Codes: H04M 15/61 based on the service used
• CPC Class Codes: H04M 15/68 Payment of value-added services

Abstract

A method for running an accountable multi-module telephony application including receiving an application request to a number associated with an account of a telephony platform; directing application control to a first module of an application of the account; passing application control from the first module to a second module of the account through a linking system; and metering use of the first module and the at least second module independently.

Claims

1. A method for running an accountable multi-module telephony application comprising:

receiving an application request for a number associated with an account of a telephony platform;

directing application control to a first module of an application of the account;

passing application control from the first module to a second module of the account through a linking system; and

metering use of the first module and the at least second module independently.

2. The method of claim 1, wherein an application request is an telephony call request.

3. The method of claim 1, wherein an application request is an text message request.

4. The method of claim 1, wherein directing application control to a first module of the account includes directing control to an initial universal resource identifier (URI) of the first module;

and wherein passing application control to the second module through a linking system includes directing application control to an initial URI of the second module.

5. The method of claim 4, wherein passing control to a second module includes receiving from the first module a redirecting URI to specify the initial URI of the second module.

6. The method of claim 4, wherein passing control to a second module includes receiving from the first module a module identity code of the second module, wherein the module identity code is received at a dispatcher engine of the telephony platform;

and further comprising the dispatcher engine converting the module identity code to the initial URI of the second module; and

wherein the dispatcher engine directs application control to the initial URI of the second module.

7. The method of claim 4, further comprising assigning a usage model of the account for the first module and the second module;

and prior to directing application control to the initial URI of the second module, a policy engine of the telephony platform verifying permission for the account to use the second module based on the usage model and metered use of the second module.

8. The method of claim 7, wherein the usage model of the second module is for unlimited use in a time period, and the metering of use includes comparing the time period of unlimited use to the current time.

9. The method of claim 7, wherein passing control to a second module includes receiving from the first module a module identity code of the second module, wherein the module identity code is received at a dispatcher engine of the telephony platform;

and the dispatcher engine converting the module identity code to the initial URI of the second module; and

wherein upon verification of permission for the account to use the second module, the dispatcher engine directs application control to the initial URI of the second module.

10. The method of claim 7, further comprising a billing engine transferring payment from an account based on a usage model for the first module and the second module and the independently metered usage of the first module and the second module;

and wherein verifying permissions includes verifying the account has satisfied a billing requirement associated with the usage model.

11. The method of claim 1, further comprising charging the account for combined usage of the first module and the at least second module as indicated by the metered use of the first module and at least second module;

and distributing payment to an entity of the first module based on usage record of the first module and distributing payment to an entity of the second module based on a usage record of the second module.

12. The method of claim 1, wherein the metering of use for the first module uses a metric different from the metric used for metering the at least second module.

13. The method of claim 1, wherein the metering is triggered through the passing of application control from the first module to a second module through the linkage system.

14. The method of claim 1, wherein the metering of use of the first module and the at least second module includes metering usage during application control and telephony platform use outside of application control.

15. The method of claim 1, further comprising sending a notification to an entity of the module in response to telephony platform activity.

16. The method of claim 1, further comprising sharing configuration state between the first module and at the least second module, wherein the configuration state is set for every application request for operation of the application containing the first module and second module.

17. The method of claim 16, wherein sharing configuration state includes sharing defined keys with parameter values between the first module and the at least second module.

18. The method of claim 17, wherein an instance of application control may additionally have shared configuration state.

19. A method for supplying use of an application protocol interface (API) for an application on a platform comprising:

receiving a request to add a first application for use on a platform;

receiving user account information for the platform;

receiving usage agreement information for the user account; and

metering the first application usage for the account; and

permitting use of a platform resource for the user account according to the metered usage and usage agreement information.

20. The method for claim 19, wherein permitting use of a platform resource for the user account includes a policy engine verifying permission for the account to use the platform resource based on the usage module.

21. The method of claim 19, further comprising charging the user account for metered usage of the platform;

and distributing payment to an entity of the first module based on metered usage of the application.

22. The method of claim 19, wherein permitting use of the platform resource for the user account includes passing application control to a second application through a linking system, wherein the second application is associated with the user account and has a usage agreement information.

23. The method of claim 22, wherein passing control to a second application includes receiving from the first module a module identity code of the second module, wherein the module identity code is received at a dispatcher engine of the telephony platform;

and the dispatcher engine converting the module identity code to the initial URI of the second module; and

wherein upon verification of permission for the account to use the second module, the dispatcher engine directs application control to the initial URI of the second module.

24. The method of claim 19, wherein the platform is a telephony application platform and the application is assigned to a phone number.