System and method for enabling real-time eventing

• US 9,967,224 B2
• Filed: 08/05/2014
• Issued: 05/08/2018
• Est. Priority Date: 06/25/2010
• Status: Active Grant

• Current Assignee: Twilio, Inc.
• Original Assignee: Twilio, Inc.
• Inventors: Lawson, Jeffrey, Wolthuis, John, Cooke, Evan, Comer, Jeffrey
• Primary Examiner(s): RECEK, JASON D
• Application Number:
  US14/452,277
• Publication Number:
  US 20140344388A1
• Time in Patent Office: 1,372 Days
• Field of Search: 709206
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/52 for supporting social networking services

Abstract

A method and system for real-time eventing including interacting with at least one configuration attribute according to instructions specified through an application programming interface (API); adding subscribers for an event channel; generating an event from operation of an application; publishing the event message to the event channel on an event router; processing the event message according to the at least one configuration attribute; identifying a subscriber to the event channel; and sending the event from the event router to the subscriber.

Claims

1. A method for real-time eventing comprising:

an event router system receiving a first event subscription request from a first subscriber for a first event channel of a plurality of event channels of the event router system;

the event router system receiving from the first subscriber a first event processing attribute for the first event channel that specifies processing for event messages received at the first event channel;

the event router system receiving a second event subscription request from a second subscriber for a second event channel of the plurality of event channels;

the event router system receiving from the second subscriber a second event processing attribute for the second event channel that specifies processing for event messages received at the second event channel;

the event router system authenticating a publisher system;

responsive to receiving a first event message from the authenticated publisher system, the event router system providing the first event message to the first event channel;

responsive to the first event channel receiving the first event message, the event router system;

routing the first event message from the first event channel to the second event channel in accordance with a routing attribute of the first event channel that specifies routing of messages from the first event channel to the second event channel;

identifying the first subscriber as a subscriber to the first event channel;

processing the first event message, received at the first event channel, in accordance with the first event processing attribute for the first event channel; and

sending the processed event message of the first event channel from the first event channel to a system of the first subscriber;

identifying the second subscriber as a subscriber to the second event channel;

processing the first event message, received at the second event channel from the first event channel, in accordance with the second event processing attribute for the second event channel; and

sending the processed event message of the second event channel from the second event channel to a system of the second subscriber.

2. The method of claim 1 , further comprising, at the event router, interacting with the at least one event attribute for the first event channel via an application programming interface (API), wherein interacting includes setting a delegate universal resource identifier (URI) attribute, a webhook attribute, and a routing attribute for the first event channel.

3. The method of claim 1, wherein the first event message is for an event occurring during operation of a telephony application for a voice session.

4. The method of claim 1, wherein the first event message is for an event occurring during operation of a telephony application sending short message service (SMS) messages.

5. The method of claim 1, wherein the system of the first subscriber is external to the event router system.

6. The method of claim 1, wherein each event channel is an event name to which a publisher publishes and to which a subscriber subscribes.

7. The method of claim 1, wherein the publisher system generates the first event message responsive to occurrence of an event during operation of an application.

8. The method of claim 1, wherein the publisher system is external to the event router system.

9. The method of claim 8, wherein the event router system receives the routing attribute of the first event channel from the publisher system via an application programming interface (API) of the event router system.

10. The method of claim 1, wherein the event router system receives the routing attribute of the first event channel from a system of a developer via an application programming interface (API) of the event router system.

11. The method of claim 10, wherein the system of the developer is different from a system of the first subscriber, and wherein the system of the developer and the system of the first subscriber are external to the event router system.

12. The method of claim 10, wherein the system of the developer is different from a system of the second subscriber, and wherein the system of the developer and the system of the second subscriber are external to the event router system.

13. The method of claim 10, wherein the system of the developer is different from a system of the first subscriber, wherein the system of the developer is different from a system of the second subscriber, and wherein the system of the developer, the system of the first subscriber, and the system of the second subscriber are external to the event router system.

14. The method of claim 1, wherein the event router system receives the routing attribute of the first event channel from the system of the first subscriber via an application programming interface (API) of the event router system.

15. The method of claim 1, wherein the event router system receives the routing attribute of the first event channel from the system of the second subscriber via an application programming interface (API) of the event router system.

16. The method of claim 1,

wherein the event router system uses the first event channel to process the first event message, received at the first event channel, in accordance with the first event processing attribute for the first event channel to generate the processed event message of the first event channel, and

wherein the event router system uses the second event channel to process the first event message, received at the second event channel, in accordance with the second event processing attribute for the first event channel to generate the processed event message of the second event channel.