Telephony Web Event System and Method

• US 20100150139A1
• Filed: 10/01/2009
• Published: 06/17/2010
• Est. Priority Date: 10/01/2008
• Status: Active Grant

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Cooke, Evan, Lawson, Jeffrey, Wolthuis, John
• Granted Patent: US 8,964,726 B2
• Time in Patent Office: Days
• US Class Current: 370/352
• 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 for publishing events of a telephony application to a client, wherein the telephony application interfaces with a telephony device and an application server, the system comprising:

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.

2. The system of claim 1, wherein the event router includes a plurality of event proxy servers that manage the subscriptions for the clients of the event router and that subscribe to the events of the event router.

3. The system of claim 2, wherein the client is an API server.

4. The system of claim 2, wherein the event router further includes a load balancer that manages event proxy loads and scales the event proxy system.

5. The system of claim 2, wherein the event proxy servers include event filters that selectively pass events to a client according to an event attribute.

6. The system of claim 5, wherein the event filters selectively pass events from a single call to a client.

7. The system of claim 5, wherein the event filter filters selectively pass events associated with a set phone number.

8. The system of claim 5, wherein at least one of the event filters is implemented by an event publisher to prevent a client from receiving an event type.

9. The system of claim 5, wherein the event proxy servers additionally include a security policy engine that authorizes clients to subscribe to an event.

10. 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.

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

12. The system of claim 1, wherein the call router simultaneously manages a plurality of telephony applications and the event router publishes a plurality of events and manages a plurality of subscriptions.

13. The system of claim 1, wherein the client generates client events, and the event router additionally manages the publication of client events and manages call router subscriptions to client events.

14. A method for publishing events of a telephony application comprising:

generating an event from the telephony application;

publishing an event to an event router;

identifying a subscriber to an event; and

sending the event from the event router to the subscriber.

15. The method of claim 14, wherein the step of identifying a subscriber includes an event proxy server managing a subscription and subscribing to an event publication of the event router.

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

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

18. The method of claim 16, further comprising allocating additional event proxy servers to increase subscription capacity and allocating additional message brokers to increase event publication capacity.

19. The method of claim 16, further comprising the steps of:

receiving a subscription request from a subscriber for an event;

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

initiating management of the subscription.

20. The method of claim 19, wherein the step of sending the event from the event router to a subscriber includes detecting if the client is not connected and establishing a connection to the subscriber if a connection is not detected.

21. The method of claim 19, further comprising receiving a subscriber generated client event;

publishing the client event to the event router;

identifying a call router subscribed to the client event; and

sending the client event to the call router.

22. The method of claim 14, further comprising sending the event from the event router to a plurality of subscribers.

23. A method for forming a subscription to an event of a telephony application comprising:

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

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

subscribing to the event publication published by a event router, wherein the event router manages subscriptions of a telephony application; and

returning events of the event publication to the subscriber through an event connection.

24. The method of claim 23, further comprising aggregating subscriptions to the event publication with a plurality of subscriptions from an event proxy server to the event router.

25. The method of claim 23, further comprising configuring filters for the subscription and filtering events prior to returning to the subscriber, wherein the filters are specified in the subscription request.

26. The method of claim 25, further comprising 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.

27. The method of claim 23, further comprising receiving a request to subscribe to a second request from the subscriber;

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

subscribing to the second event published by a event router; and

returning the second event through the event connection of the first event.