System and method for triggering on platform usage

Patent metadata

Field	Value
Publication number	US-9319857-B2
Application number	US-201414569036-A
Country	US
Kind code	B2
Filing date	Dec 12, 2014
Priority date	Oct 15, 2012
Publication date	Apr 19, 2016
Grant date	Apr 19, 2016

Abstract

A system and method for triggering on platform usage can include at a platform, receiving and storing a trigger configuration of an account; operating a platform comprising internally executing a process on behalf of an account and publishing at least one event when executing the process; at the platform, incrementing a counter in response to the at least one event and if the stored trigger configuration species a usage key associated with a category of counted events of the at least one event; monitoring counters in a context of an associated trigger; and processing the trigger upon the counter satisfying condition of an associated trigger.

First claim

What is claimed is:

1. A method comprising:
at a multitenant communication platform, receiving a trigger configuration creation request from an account and storing a trigger configuration of the account, wherein the received trigger configuration includes a callback uniform resource identifier and a trigger condition;
operating the multitenant communication platform comprising internally facilitating a communication on behalf of an account and publishing at least one event when facilitating the communication;
at the platform, incrementing a counter in response to the at least one event if the stored trigger configuration of the account specifies a usage key associated with a category of counted events of the at least one event;
monitoring counters in a context of an associated trigger; and
processing the trigger, wherein processing the trigger comprises transmitting a request to the callback uniform resource identifier of an application server outside of the multitenant platform, upon the counter satisfying the trigger condition of an associated trigger.

2. The method of claim 1 , wherein the trigger condition is conditional on at least one category of usage within the account.

3. The method of claim 1 , wherein the trigger condition is associated with an application programming interface (API) usage key that identifies a type of API call made in association with the communication platform.

4. The method of claim 1 , wherein the trigger condition is associated with an outbound call usage key that identifies communications as outbound calls.

5. The method of claim 1 , wherein the trigger condition is associated with an inbound call usage key that identifies communications as inbound calls.

6. The method of claim 1 , wherein the trigger condition is associated with a mobile usage key that identifies communications as involving a mobile client.

7. The method of claim 1 , wherein the trigger condition is associated with a call usage key that identifies communications as call sessions.

8. The method of claim 1 , wherein the trigger condition is associated with a message usage key that identifies communications as message communications.

9. The method of claim 1 , wherein the trigger condition is associated with a regional usage key that identifies regional associations of a communication based on involved endpoints.

10. The method of claim 1 , wherein the trigger condition is associated with an endpoint type usage key wherein one endpoint type usage key identifies communications with short code endpoints.

11. The method of claim 1 , wherein the trigger condition is associated with an endpoint type usage key wherein one endpoint type usage key identifies communications with long code endpoints.

12. The method of claim 1 , wherein the trigger condition is associated with an endpoint type usage key wherein one endpoint type usage key identifies communications with toll-free endpoints.

13. The method of claim 1 , wherein the trigger condition is associated with communications identified by at least one categorization selected from a set of categories that comprise a communication type identifier, an endpoint type identifier, an inbound identifier, and an outbound identifier.

14. The method of claim 1 , wherein incrementing a counter in response to the at least one event comprises incrementing the counter by the cost of the communication.

15. The method of claim 1 , wherein incrementing a counter in response to the at least one event comprises incrementing the counter by the resource usage of the communication.

16. The method of claim 1 , wherein the trigger condition is a condition of usage within a sub-account of the account; and wherein facilitating a communication on behalf of an account is facilitated on behalf of the sub-account of the account.

17. The method of claim 16 , wherein the trigger configuration is defined by the account managing the subaccount.

18. The method of claim 16 , wherein the trigger configuration is explicitly associated with the subaccount.

19. The method of claim 16 , wherein incrementing a counter in response to the at least one event comprises incrementing the counter by the cost of the communication.

20. The method of claim 16 , wherein the trigger condition is associated with a call usage key that identifies communications as call sessions.

21. The method of claim 16 , wherein the trigger condition is associated with a message usage key that identifies communications as message communications.

22. The method of claim 16 , wherein the trigger condition is associated with communications identified by at least one categorization selected from a set of categories that comprise a communication type identifier, an endpoint type identifier, an inbound identifier, and an outbound identifier.

Assignees

• Twilio Inc

Inventors

• Cooke Evan
• Milliron Timothy
• Ballai Adam
• Nowack Matthew D
• Hagemann Iii Robert C

Classifications

• H04W4/16 Primary

  Communication-related supplementary services, e.g. call-transfer or call-hold · CPC title

• G06F9/542

  Event management; Broadcasting; Multicasting; Notifications · CPC title

• H04L43/08

  Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters · CPC title

• H04W24/08

  Testing, {supervising or monitoring} using real traffic · CPC title

• G06F9/546

  Message passing systems or structures, e.g. queues · CPC title