Telephony web event system and method

Patent metadata

Field	Value
Publication number	US-11665285-B2
Application number	US-202117301335-A
Country	US
Kind code	B2
Filing date	Mar 31, 2021
Priority date	Oct 1, 2008
Publication date	May 30, 2023
Grant date	May 30, 2023

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.

First claim

We claim:

1. A method comprising:
detecting, at a first system and via a network, an event generated on a second system, the event having an event type;
based on the event type, selecting a message broker of a plurality of message brokers;
providing the event to the selected message broker;
receiving, at the first system and via the network, a connection from a client device; and
in response to receiving the connection from the client device and based on the event type, providing the event from the message broker to the client device.

2. The method of claim 1 , further comprising:
after detecting the event and before receiving the connection from the client device, storing the event in a cache up to an expiration time.

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

4. The method of claim 1 , further comprising:
receiving, before detecting the event, a subscription request from the client device, the subscription request comprising an identification of an account;
wherein:
the event is associated with the account; and
the providing of the event from the message broker to the client device is further based on the account being identified in the subscription request and the event being associated with the account.

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

6. The method of claim 4 , wherein:
the subscription request comprises a parameter filter comprising an identification of a characteristic of the event.

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

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

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

10. A system comprising:
a memory that stores instructions; and
one or more processors configured by the instructions to perform operations comprising:
detecting, via a network, an event generated on another system, the event having an event type;
based on the event type, selecting a message broker of a plurality of message brokers;
providing the event to the selected message broker;
receiving, via the network, a connection from a client device; and
in response to the connection from the client device and based on the event type, providing the event from the message broker to the client device.

11. The system of claim 10 , wherein the operations further comprise:
after detecting the event and before receiving the connection from the client device, storing the event in a cache up to an expiration time.

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

13. The system of claim 10 , wherein:
the operations further comprise receiving, before the detecting of the event, a subscription request from the client device, the subscription request comprising 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.

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

15. The system of claim 13 , wherein:
the subscription request comprises a parameter filter comprising an identification of a characteristic of the event.

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

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:
detecting, via a network, an event generated on another system, the event having an event type;
based on the event type, selecting a message broker of a plurality of message brokers;
providing the event to the selected message broker;
receiving, via the network, a connection from a client device; and
in response to the connection from the client device and based on the event type, providing the event from the message broker to the client device.

18. The machine-readable medium of claim 17 , wherein the operations further comprise:
after detecting the event and before receiving the connection from the client device, storing the event in a cache up to an expiration time.

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

20. The machine-readable medium of claim 17 , wherein:
the operations further comprise receiving, before the detecting of the event, a subscription request from the client device, the subscription request comprising 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.

Assignees

• Twilio Inc

Inventors

• Lawson Jeffrey
• Wolthuis John
• Cooke Evan

Classifications

• H04L51/52

  for supporting social networking services · CPC title

• H04M7/128

  Details of addressing, directories or routing tables · CPC title

• H04M15/44

  Augmented, consolidated or itemized billing statement or bill presentation · CPC title

• H04M3/2209

  for lines also used for data transmission · CPC title

• H04M2215/016

  Billing using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN] · CPC title