Telephony web event system and method

• US 9,407,597 B2
• Filed: 01/07/2015
• Issued: 08/02/2016
• Est. Priority Date: 10/01/2008
• Status: Active Grant

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Lawson, Jeffrey, Wolthuis, John, Cooke, Evan
• Primary Examiner(s): O'Connor, Brian
• Application Number:
  US14/591,279
• Publication Number:
  US 20150127723A1
• Time in Patent Office: 573 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 51/52 for supporting social networking services
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: 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
• CPC Class Codes: H04M 15/44 Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 15/90 using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
• CPC Class Codes: 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
• CPC Class Codes: H04M 2215/016 Billing using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
• CPC Class Codes: H04M 2215/018 On-line real-time billing, able to see billing information while in communication, e.g. via the internet
• CPC Class Codes: H04M 3/2209 for lines also used for data transmission
• CPC Class Codes: H04M 3/2218 Call detail recording
• CPC Class Codes: 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
• CPC Class Codes: 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
• CPC Class Codes: 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
• CPC Class Codes: H04M 7/123 where the packet-switched network is an Internet Protocol Multimedia System-type network
• CPC Class Codes: H04M 7/128 Details of addressing, directories or routing tables

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

1. A system comprising:

a call router constructed to;

manage a plurality of telephony applications provided by a plurality of internet application servers external to the system, wherein each telephony application controls interaction between a telephony device and a respective internet application server,

generate an event from at least one of the plurality of telephony applications during the management of the at least one telephony application, and

publish each generated event to an event router; and

the event router, the event router being constructed to;

responsive to publishing of an event by the call router, identify at least one subscriber to the published event, and send the published event from the event router to the at least one subscriber,

wherein the system is a multi-tenant telephony web event system.

2. The system of claim 1, wherein publishing each generated event to the event router comprises:

publishing each generated event to the event router by using one of an http or https protocol.

3. The system of claim 2, wherein sending the published event from the event router to the at least one subscriber comprises:

sending the published event from the event router to the at least one subscriber through an open http connection.

4. The system of claim 3, wherein the plurality of telephony applications includes different telephony applications.

5. The system of claim 4,

wherein the event router comprises an event proxy system comprising a set of event proxy servers,

wherein each event proxy server of the set of event proxy servers subscribes to the events of the event router and manages subscriptions to events by remote clients by pushing events to subscribed remote clients through an open HTTP connection, and

wherein the event proxy servers comprise event filters that selectively permit pushing of events to a client according to an event attribute.

6. The system of claim 5,

wherein the event router includes a plurality of message brokers that manage the publication of events for the event router, and

wherein the event proxy servers connect to a message broker to subscribe to an event.

7. The system of claim 6, wherein the message brokers are sharded according to an event attribute.

8. The system of claim 1, wherein at least one subscriber generates subscriber events, and the event router additionally manages the publication of subscriber events and manages call router subscriptions to subscriber events.

9. A method comprising:

at a call router of a multi-tenant telephony web event system that includes the call router and an event router;

managing a plurality of telephony applications provided by a plurality of internet application servers external to the multi-tenant web event system, wherein each telephony application controls interaction between a telephony device and a respective internet application server,

generating an event from at least one of the plurality of telephony applications during the management of the at least one telephony application, and

publishing each generated event to the event router;

at the event router;

responsive to publishing of an event by the call router, identifying at least one subscriber to the published event, and sending the published event from the event router to the at least one subscriber.

10. The method of claim 9, wherein publishing each generated event to the event router comprises:

publishing each generated event to the event router by using one of an http or https protocol.

11. The method of claim 10, wherein sending the published event from the event router to the at least one subscriber comprises:

sending the published event from the event router to the at least one subscriber through an open http connection.

12. The method of claim 11, wherein the plurality of telephony applications includes different telephony applications.

13. The method of claim 12, further comprising, at the event router, selectively permitting sending of events to the at least one subscriber according an event attribute.

14. The method of claim 13, wherein sending the published event from the event router to the at least one subscriber comprises:

an event proxy server managing a subscription and subscribing to an event publication of the event router.

15. The method of claim 14, further comprising, at the event router, publishing the event on a message broker.

16. The method of claim 15, wherein the event is published on at least a second message broker of a plurality of message brokers including a first message broker and a second message broker, wherein the message brokers manage publication of events based on different attributes.

17. The method of claim 16, further comprising:

at the event router;

receiving a subscription request from a subscriber for an event;

verifying the subscriber is authorized to subscribe to the event; and

initiating management of the subscription.

18. The method of claim 17, further comprising:

at the event router;

receiving a subscriber generated client event;

identifying a call router subscribed to the client event; and

sending the client event to the call router.

19. A method comprising:

at an event router of a multi-tenant telephony web event system that includes the event router and a call router;

receiving a request to subscribe to an event publication from a subscriber,

verifying the subscriber is authorized to subscribe to the event publication, and

subscribing the subscriber to the event publication, the event publication being published by the event router,

wherein the event router manages subscriptions of a plurality of telephony applications provided by a plurality of internet application servers external to the multi-tenant web event system, each telephony application controlling interaction between a telephony device and a respective internet application server; and

at the call router;

managing the plurality of telephony applications,

generating an event from at least one of the plurality of telephony applications during the management of the at least one telephony application, and

publishing each generated event to the event router, wherein each generated event returned to the subscriber via the event router is returned to the subscriber through an event connection.

20. The method of claim 19, further comprising, at the event router, configuring filters for the subscription and filtering of events prior to returning an event to the subscriber, wherein the filters are specified in a subscription request.

21. The method of claim 20, further comprising, at the event router, aggregating subscriptions to the event publication with a plurality of subscriptions from at least one event proxy server to the event router.

22. The method of claim 21, further comprising, at the event router, queuing events to be returned to a subscriber, and returning the events to the subscriber through an event connection after the subscriber establishes the event connection.

23. The method of claim 21, further comprising, at the event router, receiving a request to subscribe to a second event publication from the subscriber, verifying the subscriber is authorized to subscribe to the second event publication, subscribing the subscriber to the second event publication, and returning a second event through an event connection of a first event.