# US 2025/0071183 A1 · System and method for providing a micro-services communication platform

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0071183 A1
- Document ID: US20250071183A1
- Status: Published application
- Kind: A1
- Application number: 18/946,271
- Filed: 2024-11-13
- Published: 2025-02-27
- Earliest claimed: 2014-10-21
- Assignees: Twilio Inc.
- Applicants: Twilio Inc.
- Inventors: Jeffrey Lawson; John Wolthius
- Web page: https://patentgrep.com/patent/US20250071183A1

## CPC

- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04L 12/1403: {Architecture for metering, charging or billing}
- 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)
- H04L 65/80: Responding to QoS
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/104: Peer-to-peer [P2P] networks
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- 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)
- H04M 15/41: {Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]}
- H04M 15/44: {Augmented, consolidated or itemized billing statement or bill presentation}
- H04M 15/47: {Fraud detection or prevention means}
- H04M 15/52: {for operator independent billing system}
- H04M 15/62: {based on trigger specification}
- H04L 61/2514: between local and global IP addresses
- H04L 61/2564: {for a higher-layer protocol, e.g. for session initiation protocol [SIP]}
- H04L 61/2575: using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
- H04L 61/2589: over a relay server, e.g. traversal using relay for network address translation [TURN]
- H04L 2101/38: Telephone uniform resource identifier [URI]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## 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

### Claim 1

A communication platform 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 communication platform to perform operations comprising:
detecting, based on accounting for use of a micro-service by a first account and a second account and shared profile information between the first account and the second account, an illicit usage pattern; and
in response to the detecting of the illicit usage pattern, preventing future interactions between the first account and the communication platform.

### Claim 2 (depends on 1)

The communication platform of claim 1, wherein the detecting of the illicit usage pattern is further based on detecting that a communication stream that is registered for transmission of data of a first data type is used to transmit data of a second data type.

### Claim 3 (depends on 1)

The communication platform of claim 1, wherein the operations further comprise:
in response to the detecting of the illicit usage pattern, preventing future interactions between subaccounts of the first account and the communication platform.

### Claim 4 (depends on 1)

The communication platform of claim 1, wherein the operations further comprise:
calculating a fraud score from usage data for the first account; and
determining whether the fraud score satisfies a fraud threshold.

### Claim 5 (depends on 1)

The communication platform of claim 1, wherein the operations further comprise:
providing the micro-service in relation to a communication session between a first communication endpoint and a second communication endpoint.

### Claim 6 (depends on 1)

The communication platform of claim 1, wherein the operations further comprise:
establishing, for the first account, a micro-service configuration that describes triggering conditions for initiating use of the micro-service in relation to the first account.

### Claim 7

A method comprising:
detecting, at a communication platform, based on accounting for use of a micro-service by a first account and a second account and shared profile information between the first account and the second account, an illicit usage pattern; and
in response to the detecting of the illicit usage pattern, preventing future interactions between the first account and the communication platform.

### Claim 8 (depends on 7)

The method of claim 7, wherein the detecting of the illicit usage pattern is further based on detecting that a communication stream that is registered for transmission of data of a first data type is used to transmit data of a second data type.

### Claim 9 (depends on 7)

The method of claim 7, further comprising:
in response to the detecting of the illicit usage pattern, preventing future interactions between subaccounts of the first account and the communication platform.

### Claim 10 (depends on 7)

The method of claim 7, further comprising:
calculating a fraud score from usage data for the first account; and
determining whether the fraud score satisfies a fraud threshold.

### Claim 11 (depends on 7)

The method of claim 7, further comprising:
providing the micro-service in relation to a communication session between a first communication endpoint and a second communication endpoint.

### Claim 12 (depends on 7)

The method of claim 7, further comprising:
establishing, for the first account, a micro-service configuration that describes triggering conditions for initiating use of the micro-service in relation to the first account.

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
detecting, based on event data of the first account, that a triggering event associated with the first account has been triggered; and
processing detection of the triggering event according to the triggering conditions for use of the micro-service described by the micro-service configuration.

### Claim 14 (depends on 12)

The method of claim 12, further comprising:
establishing, for the second account, a second micro-service configuration that describes triggering conditions for initiating use of the micro-service in relation to the second account, the triggering conditions for use of the micro-service by the second account being different than the triggering conditions for use of the micro-service by the first account.

### Claim 15 (depends on 14)

The method of claim 14, 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.

### Claim 16 (depends on 8)

The method of claim 8, 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 the second account defines the pricing of usage at a second tier of usage.

### Claim 17 (depends on 16)

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

### Claim 18

A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of a communication platform, cause the communication platform to perform operations comprising:
detecting, based on accounting for use of a micro-service by a first account and a second account and shared profile information between the first account and the second account, an illicit usage pattern; and
in response to the detecting of the illicit usage pattern, preventing future interactions between the first account and the communication platform.

### Claim 19 (depends on 18)

The non-transitory computer-readable medium of claim 18, wherein the detecting of the illicit usage pattern is further based on detecting that a communication stream that is registered for transmission of data of a first data type is used to transmit data of a second data type.

### Claim 20 (depends on 18)

The non-transitory computer-readable medium of claim 18, wherein the operations further comprise:
in response to the detecting of the illicit usage pattern, preventing future interactions between subaccounts of the first account and the communication platform.
