IP Library › Granted Patent US 12,177,304
Granted Patent B2
US 12,177,304 · App. 17/301,340 · Granted Dec 24, 2024

System and method for providing a micro-services communication platform

Inventors: Jeffrey Lawson (San Francisco, CA); John Wolthius (San Francisco, CA)
Assignee: Twilio Inc.
H04L67/51H04L12/14H04L12/1403H04L65/403H04L65/75H04L65/80H04L67/02H04L67/104H04L67/141H04L67/535H04L67/565H04L67/60H04M15/41H04M15/44H04M15/47H04M15/52H04M15/62H04L61/2514H04L61/2564H04L61/2575H04L61/2589H04L2101/38
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 12,177,304
App. No.
17/301,340
Granted
Dec 24, 2024
Kind
B2
Abstract

A multi-tenant media communication platform system and methods. The platform system includes media communication micro-services and micro-service configuration for a plurality of entities configured for use of the platform system. Enrolling an entity in the platform system includes setting entity configuration for use of the platform system by the entity. A micro-service request is processed according to the entity configuration. The micro-service request is a request for use of at least one micro-service of the platform system on behalf of the entity. Use of each micro-service is accounted for on behalf of the entity. Billing information for the entity is generated based on the accounting for the use of each micro-service on behalf of the entity. Entity configuration includes micro-service configuration, and micro-service configuration specifies at least one of: an endpoint mapping to at least one application logic URI, an event callback URI, and an event application logic URI.

Claims (55)

1. A method comprising:

detecting, based on event data of a first account, that a first triggering event associated with the first account has been triggered;

accessing a callback uniform resource identifier (URI) associated with the first triggering event, the callback URI corresponding to a micro-service;

transmitting, to a computing system and via the callback URI, a communication;

receiving application logic from the computing system in response to the communication; and

executing the received application logic to provide the micro-service in relation to the first account.

2. The method of claim 1 , wherein providing the micro-service in relation to the first account comprises:

providing the micro-service in relation to a communication session between a first communication endpoint and a second communication endpoint.

3. The method of claim 1 , further comprising:

establishing, for the first account, a micro-service configuration describing triggering conditions for initiating use of micro-services in relation to the first account, wherein detection of the first triggering event is processed according to the triggering conditions for use of the micro-service described by the micro-service configuration.

4. The method of claim 3 , further comprising:

detecting, based on the event data of the first account, that a second triggering event associated with the first account has been triggered; and

processing detection of the second triggering event according to the triggering conditions for use of micro-services described by the micro-service configuration.

5. The method of claim 3 , further comprising:

establishing, for a second account, a second micro-service configuration describing triggering conditions for initiating use of micro-services in relation to the second account establishing, the triggering conditions for use of the micro-services by the second account being different than the triggering conditions for use of the micro-services by the first account.

6. The method of claim 5 , further comprising:

accounting for usage of the micro-services in association with the second account based on the second micro-service configuration established for the second account.

7. The method of claim 1 , wherein a first billing profile for the first account defines a pricing of usage at a first tier of usage and a second billing profile for a second account defines the pricing of usage at a second tier of usage.

8. The method of claim 7 , wherein the pricing of usage at the second tier of usage is higher than the pricing of usage at the first tier of usage.

9. The method of claim 7 , wherein the first tier of usage includes a usage limit.

10. A system comprising:

one or more computer processors; and

one or more computer-readable mediums storing instructions that, when executed by the one or more computer processors, cause the system to perform operations comprising:

detecting, based on event data of a first account, that a first triggering event associated with the first account has been triggered;

accessing a callback uniform resource identifier (URI) associated with the first triggering event, the callback URI corresponding to a micro-service;

transmitting, to a computing system and via the callback URI, a communication;

receiving application logic from the computing system in response to the communication; and

executing the received application logic to provide the micro-service in relation to the first account.

11. The system of claim 10 , wherein providing the micro-service in relation to the first account comprises:

providing the micro-service in relation to a communication session between a first communication endpoint and a second communication endpoint.

12. The system of claim 10 , the operations further comprising:

establishing, for the first account, a micro-service configuration describing triggering conditions for initiating use of micro-services in relation to the first account, wherein detection of the first triggering event is processed according to the triggering conditions for use of the micro-service described by the micro-service configuration.

13. The system of claim 12 , the operations further comprising:

detecting, based on the event data of the first account, that a second triggering event associated with the first account has been triggered; and

processing detection of the second triggering event according to the triggering conditions for use of micro-services described by the micro-service configuration.

14. The system of claim 12 , the operations further comprising:

establishing, for a second account, a second micro-service configuration describing triggering conditions for initiating use of micro-services in relation to the second account establishing, the triggering conditions for use of the micro-services by the second account being different than the triggering conditions for use of the micro-services by the first account.

15. The system of claim 14 , the operations further comprising:

accounting for usage of the micro-services in association with the second account based on the second micro-service configuration established for the second account.

16. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of one or more computing devices, cause the one or more computing devices to perform operations comprising:

detecting, based on event data of a first account, that a first triggering event associated with the first account has been triggered;

accessing a callback uniform resource identifier (URI) associated with the first triggering event, the callback URI corresponding to a micro-service;

transmitting, to a computing system and via the callback URI, a communication;

receiving application logic from the computing system in response to the communication; and

executing the received application logic to provide the micro-service in relation to the first account.

17. The non-transitory computer-readable medium of claim 16 , wherein providing the micro-service in relation to the first account comprises:

providing the micro-service in relation to a communication session between a first communication endpoint and a second communication endpoint.

18. The non-transitory computer-readable medium of claim 16 , the operations further comprising:

establishing, for the first account, a micro-service configuration describing triggering conditions for initiating use of micro-services in relation to the first account, wherein detection of the first triggering event is processed according to the triggering conditions for use of the micro-service described by the micro-service configuration.

19. The non-transitory computer-readable medium of claim 18 , the operations further comprising:

detecting, based on the event data of the first account, that a second triggering event associated with the first account has been triggered; and

processing detection of the second triggering event according to the triggering conditions for use of micro-services described by the micro-service configuration.

20. The non-transitory computer-readable medium of claim 18 , the operations further comprising:

establishing, for a second account, a second micro-service configuration describing triggering conditions for initiating use of micro-services in relation to the second account establishing, the triggering conditions for use of the micro-services by the second account being different than the triggering conditions for use of the micro-services by the first account; and

accounting for usage of the micro-services in association with the second account based on the second micro-service configuration established for the second account.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 31, 2021
From: LAWSON, JEFFREY; WOLTHIUS, JOHN
To: TWILIO INC.
Reel/Frame 055786/0926 →
Continuity (11)
Continuation 16823223 · Mar 18, 2020
Continuation 15842731 · Dec 14, 2017
Continuation 15297857 · Oct 19, 2016
Continuation 15141624 · Apr 28, 2016
Continuation 14919650 · Oct 21, 2015
Provisional Application 62066766 · Oct 21, 2014
Provisional Application 62066776 · Oct 21, 2014
Provisional Application 62066763 · Oct 21, 2014
Provisional Application 62066768 · Oct 21, 2014
Provisional Application 62066774 · Oct 21, 2014
Related Publication 20210218819A1 · Jul 15, 2021