SYSTEM AND METHOD FOR PROVIDING A MICRO-SERVICES COMMUNICATION PLATFORM

• US 20160248861A1
• Filed: 04/28/2016
• Published: 08/25/2016
• Est. Priority Date: 10/21/2014
• Status: Active Grant

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Lawson, Jeffrey, Wolthius, John
• Granted Patent: US 9,509,782 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 2101/38 Telephone uniform resource identifier [URI]
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04L 61/2564 for a higher-layer protocol, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 61/2575 using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
• CPC Class Codes: H04L 61/2589 over a relay server, e.g. traversal using relay for network address translation [TURN]
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 65/75 Media network packet handling
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04M 15/41 Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/44 Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 15/47 Fraud detection or prevention means
• CPC Class Codes: H04M 15/52 : for operator independent billing system
• CPC Class Codes: H04M 15/62 : based on trigger specification

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

1. A method comprising:

at a multi-tenant media communication platform system that includes;

a plurality of micro-services constructed to be independently configured and metered for a first platform entity of the platform system, and independently configured and metered for a second platform entity,

first micro-service configuration for use of a communication micro-service of the platform system by the first platform entity,

a first micro-service application programming interface (API) resource of the communication micro-service for the first platform entity,

second micro-service configuration for use of the communication micro-service by the second platform entity, and

a second micro-service API resource of the communication micro-service for the second platform entity;

enrolling the first platform entity in the platform system by setting first entity configuration for use of the platform system by the first platform entity,

wherein the first platform entity is an entity managed by an account system of the platform system,

wherein the platform system receives the first entity configuration from a first external system of the first platform entity via an account management interface of the platform system,

wherein the first entity configuration includes the first micro-service configuration,

wherein the communication micro-service is constructed to provided peer-to-peer communication between at least a first media communication endpoint and a second media communication endpoint,

wherein the first API resource is accessible by the first external system via a public API of the platform system,

processing a first micro-service request for a first peer-to-peer communication session between at least the first media communication endpoint and the second media communication endpoint according to the first micro-service configuration, the first communication micro-service request being a request for use of the communication micro-service for the first peer-to-peer communication session on behalf of the first platform entity;

accounting for the use of the communication micro-service for the first peer-to-peer communication session on behalf of the first platform entity;

processing a second micro-service request for a second peer-to-peer communication session between at least a third media communication endpoint and a fourth media communication endpoint according to the second micro-service configuration, the second communication micro-service request being a request for use of the communication micro-service for the second peer-to-peer communication session on behalf of the second platform entity; and

accounting for the use of the communication micro-service for the second peer-to-peer communication session on behalf of the second platform entity.

2. The method of claim 1,

wherein the platform system includes:

third micro-service configuration for use of a second micro-service of the platform system by the first platform entity, and

a third micro-service API resource of the second micro-service for the first platform entity,

the method further comprising, at the platform system;

processing a third micro-service request for the first peer-to-peer communication session according to the third micro-service configuration, the third micro-service request being a request for use of the second micro-service for the first peer-to-peer communication session on behalf of the first platform entity; and

accounting for the use of the second micro-service for the first peer-to-peer communication session on behalf of the first platform entity.

3. The method of claim 2, wherein use of the second micro-service comprises operating on media of the first peer-to-peer communication session.

4. The method of claim 3,

wherein the first peer-to-peer communication and the second peer-to-pear communication session each includes at least one of:

asynchronous media communication that includes messaging, and

synchronous media communication that includes at least one of voice and video communication.

5. The method of claim 4,

wherein the first micro-service API resource provides at least one of:

access to micro-service configuration of the communication micro-service for the first platform entity;

access to micro-service information of the communication micro-service for the first platform entity;

access to micro-service data of the communication micro-service for the first platform entity;

access to micro-service media of the communication micro-service for the first platform entity; and

use of the micro-service of the communication micro-service for the first platform entity,

wherein the second micro-service API resource provides at least one of;

access to micro-service configuration of the communication micro-service for the second platform entity;

access to micro-service information of the communication micro-service for the second platform entity;

access to micro-service data of the communication micro-service for the second platform entity;

access to micro-service media of the communication micro-service for the second platform entity; and

use of the micro-service of the communication micro-service for the second platform entity, and

wherein the third micro-service API resource provides at least one of;

access to micro-service configuration of the second micro-service for the first platform entity;

access to micro-service information of the second micro-service for the first platform entity;

access to micro-service data of the second micro-service for the first platform entity;

access to micro-service media of the second micro-service for the first platform entity; and

use of the micro-service of the second micro-service for the first platform entity.

6. The method of claim 5, wherein the platform system includes an API system that provides a public API, and the platform system receives requests to access the first micro-service API resource and requests to access the third micro-service API resource from the first external system via the API system.

7. The method of claim 6,

wherein accounting for the use of the communication micro-service for the first peer-to-peer communication session on behalf of the first platform entity comprises:

metering access of the first micro-service API resource by the first external system, wherein accounting for the use of the communication micro-service for the second peer-to-peer communication session on behalf of the second platform entity comprises;

metering access of the second micro-service API resource by a second external system of the second platform entity, and

wherein accounting for the use of the second micro-service for the first peer-to-peer communication session on behalf of the first platform entity comprises;

metering access of the third micro-service API resource by the first external system.

8. The method of claim 7, further comprising performing fraud detection for the first platform entity based on the accounting for the use of the communication micro-service and the accounting for the use of the second micro-service for the first platform entity.

9. The method of claim 8, wherein operating on media of the first-peer-to-peer communication session comprises:

mutably operating on the media by modifying the media.

10. The method of claim 9, wherein the second micro-service is a synchronous media micro-service.

11. The method of claim 10, wherein the second micro-service is a transcoding media micro-service.

12. The method of claim 9, wherein the second micro-service is an asynchronous media micro-service.

13. The method of claim 8, wherein operating on media of the first-peer-to-peer communication session comprises:

immutably operating on the media by preserving the media.

14. The method of claim 13, wherein the second micro-service is a synchronous media micro-service.

15. The method of claim 14, wherein the second micro-service is a real-time speech detection media micro-service.

16. The method of claim 13, wherein the second micro-service is an asynchronous media micro-service.

17. The method of claim 16, wherein the second micro-service is at least one of a speech to text micro-service and an emotion detection micro-service.