IP Library › Granted Patent US 9,319,857
Granted Patent B2
US 9,319,857 · App. 14/569,036 · Granted Apr 19, 2016

System and method for triggering on platform usage

Inventors: Evan Cooke (San Francisco, CA); Timothy Milliron (San Francisco, CA); Adam Ballai (San Francisco, CA); Matthew D Nowack (San Francisco, CA); Robert C Hagemann, III (San Francisco, CA)
Assignee: Twilio, Inc.
H04W4/16G06F9/542G06F9/546H04L43/08H04W24/08H04Q2213/13098
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,319,857
App. No.
14/569,036
Granted
Apr 19, 2016
Kind
B2
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.

Claims (27)

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.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 12, 2014
From: COOKE, EVAN; MILLIRON, TIMOTHY; BALLAI, ADAM; NOWACK, MATTHEW D.; HAGEMANN, ROBERT C, III
To: TWILIO, INC.
Reel/Frame 034497/0240 →
Continuity (4)
Continuation 14054464 · Oct 15, 2013
Provisional Application 61714113 · Oct 15, 2012
Provisional Application 61879035 · Sep 17, 2013
Related Publication 20150100689A1 · Apr 9, 2015