# US 2021/0218847 A1 · Telephony web event system and method

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

- Number: US 2021/0218847 A1
- Document ID: US20210218847A1
- Status: Published application
- Kind: A1
- Application number: 17/301,330
- Filed: 2021-03-31
- Published: 2021-07-15
- Earliest claimed: 2008-10-01
- Assignees: Twilio Inc.
- Applicants: Twilio Inc.
- Inventors: Jeffrey Lawson; John Wolthuis; Evan Cooke
- Web page: https://patentgrep.com/patent/US20210218847A1

## CPC

- H04M 7/0012: {Details of application programming interfaces [API] for telephone networks; Arrangements which combine a telephonic communication equipment and a computer, i.e. computer telephony integration [CPI] arrangements}
- H04L 12/66: Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
- H04L 51/52: for supporting social networking services
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04M 3/2209: {for lines also used for data transmission}
- H04M 3/2218: {Call detail recording}
- H04M 7/006: {Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer (H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42)}
- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- H04M 15/44: {Augmented, consolidated or itemized billing statement or bill presentation}
- H04M 15/90: {using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]}
- H04M 3/42229: {Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location (diverting calls from one subscriber to another subscriber, i.e. two different subscriptions H04M3/54; selecting arrangements in intelligent networks H04Q3/005)}
- H04M 7/123: {where the packet-switched network is an Internet Protocol Multimedia System-type network}
- H04M 7/128: {Details of addressing, directories or routing tables}
- H04M 2215/0104: Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
- H04M 2215/016: Billing using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
- H04M 2215/018: On-line real-time billing, able to see billing information while in communication, e.g. via the internet
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An embodiment of the system for publishing events of a telephony application to a client includes a call router that generates events from the telephony application and an event router that manages the publication of events generated by the call router and that manages the subscription to events by clients. The system can be used with a telephony application that interfaces with a telephony device and an application server

## Claims

### Claim 1

A method comprising:
receiving, at a first system, from a client device, and via a network, a subscription request, wherein the subscription request comprises an identification of an event type of a plurality of event types;
detecting, at the first system and via the network, an event generated by an application executing on a second system, the event having the event type;
based on the event type, providing the event to a message broker of a plurality of message brokers; and
based on the subscription request and the event type, providing the event from the message broker to the client device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the event is a communication event.

### Claim 3 (depends on 1)

The method of claim 1, wherein:
the subscription request comprises an identification of an account;
the event is associated with the account; and
the providing of the event to the client device is further based on the account being identified in the subscription request and event being associated with the account.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
establishing, in response to receiving the subscription request, a subscription for events associated with the event type.

### Claim 5 (depends on 1)

The method of claim 1, wherein:
the client device has permission to receive information for the event type.

### Claim 6 (depends on 1)

The method of claim 1, wherein:
the subscription request includes a parameter filter that comprises an identification of a characteristic of the event.

### Claim 7 (depends on 1)

The method of claim 1, wherein:
the subscription request is received using an application programming interface (API).

### Claim 8 (depends on 1)

The method of claim 1, wherein the plurality of message brokers are sharded according to one or more event types.

### Claim 9

A system comprising:
a memory that stores instructions; and
one or more processors configured by the instructions to perform operations comprising:
receiving, from a client device, and via a network, a subscription request that comprises an identification of an event type of a plurality of event types;
detecting, via the network, an event generated by an application executing on another system, the event having the event type;
based on the event type, providing the event to a message broker of a plurality of message brokers; and
based on the subscription request and the event type, providing the event from the message broker to the client device.

### Claim 10 (depends on 9)

The system of claim 9, wherein the event is a communication event.

### Claim 11 (depends on 9)

The system of claim 9, wherein:
the subscription request comprises an identification of an account;
the event is associated with the account; and
the providing of the event to the client device is further based on the account being identified in the subscription request and the event being associated with the account.

### Claim 12 (depends on 9)

The system of claim 9, wherein the operations further comprise:
establishing, in response to the subscription request, a subscription for events associated with the event type.

### Claim 13 (depends on 9)

The system of claim 9, wherein:
the client device has permission to receive information for the event type.

### Claim 14 (depends on 9)

The system of claim 9, wherein:
the subscription request includes a parameter filter that comprises an identification of a characteristic of the event.

### Claim 15 (depends on 9)

The system of claim 9, wherein:
the subscription request is received using an application programming interface (API).

### Claim 16 (depends on 9)

The system of claim 9, wherein the plurality of message brokers are sharded according to one or more event types.

### Claim 17

A non-transitory machine-readable medium that stores instructions that, when executed by one or more processors of a system, cause the system to perform operations comprising:
receiving, from a client device, and via a network, a subscription request that comprises an identification of an event type of a plurality of event types;
detecting, via the network, an event generated by an application executing on a second system, the event having the event type;
based on the event type, providing the event to a message broker of a plurality of message brokers; and
based on the subscription request and the event type, providing the event from the message broker to the client device.

### Claim 18 (depends on 17)

The machine-readable medium of claim 17, wherein the event is a communication event.

### Claim 19 (depends on 17)

The machine-readable medium of claim 17, wherein:
the subscription request comprises an identification of an account;
the event is associated with the account; and
the providing of the event to the client device is further based on the account being identified in the subscription request and the event being associated with the account.

### Claim 20 (depends on 17)

The machine-readable medium of claim 17, wherein the operations further comprise:
establishing, in response to the subscription request, a subscription for events associated with the event type.
