System and method for enabling real-time eventing

Patent metadata

Field	Value
Publication number	US-11936609-B2
Application number	US-202117302125-A
Country	US
Kind code	B2
Filing date	Apr 23, 2021
Priority date	Jun 25, 2010
Publication date	Mar 19, 2024
Grant date	Mar 19, 2024

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.

First claim

We claim:

1. A system comprising:
one or more computer processors;
one or more computer memories;
a set of instructions stored in the one or more computer memories, the set of instructions configuring the one or more computer processors to perform operations comprising:
receiving, via a first call to an Application Programming Interface (API), a first order in which processing steps are to be performed during a real-time processing of an event, the first order being associated with a first application, the first order determined by a configuration through an API, the configuration specifying a processing attribute for determining the first order, the first order specifying that a processing step occurs before a delegation step;
receiving, via a second call to the API, a second order in which the processing steps are to be performed during the real-time processing of the event, the second order being associated with a second application, the second order determined by an additional configuration through the API, the additional configuration specifying a processing attribute for determining the second order, the second order specifying that a delegation step occurs before a processing step; and
based on a determination that the real-time processing of the event is for the first application, performing the processing steps in the first order or based on a determination that the real-time processing of the event is for the second application, performing the processing steps in the second order.

2. The system of claim 1 , wherein the processing steps correspond to a set of configuration attributes associated with the event.

3. The system of claim 2 , wherein the set of configuration attributes includes one or more of a route attribute, a permissions attribute, a webhook attribute, or a delegate Uniform Resource Identifier (URI) attribute.

4. The system of claim 3 , wherein the performing of the processing events in the first order includes translating an event message before routing the event message and the performing of the processing of the events in the second order includes routing the event message before translating the event message.

5. The system of claim 2 , wherein each of the set of configuration attributes is configurable during the real-time processing of the event.

6. The system of claim 2 , wherein the set of configuration attributes includes a plurality of delegate URIs.

7. The system of claim 6 , wherein the plurality of delegate URIs are processed sequentially or in parallel.

8. A method comprising:
receiving, via a first call to an Application Programming Interface (API), a first order in which processing steps are to be performed during a real-time processing of an event, the first order being associated with a first application, the first order determined by a configuration through an API, the configuration specifying a processing attribute for determining the first order, the first order specifying that a processing step occurs before a delegation step;
receiving, via a second call to the API, a second order in which the processing steps are to be performed during the real-time processing of the event, the second order being associated with a second application, the second order determined by an additional configuration through the API, the additional configuration specifying a processing attribute for determining the second order, the second order specifying that a delegation step occurs before a processing step; and
based on a determination that the real-time processing of the event is for the first application, performing the processing steps in the first order or based on a determination that the real-time processing of the event is for the second application, performing the processing steps in the second order.

9. The method of claim 8 , wherein the processing steps correspond to a set of configuration attributes associated with the event.

10. The method of claim 9 , wherein the set of configuration attributes includes one or more of a route attribute, a permissions attribute, a webhook attribute, or a delegate Uniform Resource Identifier (URI) attribute.

11. The method of claim 10 , wherein the performing of the processing events in the first order includes translating an event message before routing the event message and the performing of the processing of the events in the second order includes routing the event message before translating the event message.

12. The method of claim 9 , wherein each of the set of configuration attributes is configurable during the real-time processing of the event.

13. The method of claim 9 , wherein the set of configuration attributes includes a plurality of delegate URIs.

14. The method of claim 13 , wherein the plurality of delegate URIs are processed sequentially or in parallel.

15. A non-transitory computer-readable storage medium storing a set of instructions that, when executed by one or more computer processors, causes the one or more computer processors to perform operations comprising:
receiving, via a first call to an Application Programming Interface (API), a first order in which processing steps are to be performed during a real-time processing of an event, the first order being associated with a first application, the first order determined by a configuration through an API, the configuration specifying a processing attribute for determining the first order, the first order specifying that a processing step occurs before a delegation step;
receiving, via a second call to the API, a second order in which the processing steps are to be performed during the real-time processing of the event, the second order being associated with a second application, the second order determined by an additional configuration through the API, the additional configuration specifying a processing attribute for determining the second order, the second order specifying that a delegation step occurs before a processing step; and
based on a determination that the real-time processing of the event is for the first application, performing the processing steps in the first order or based on a determination that the real-time processing of the event is for the second application, performing the processing steps in the second order.

16. The non-transitory computer-readable storage medium of claim 15 , wherein the processing steps correspond to a set of configuration attributes associated with the event.

17. The non-transitory computer-readable storage medium of claim 16 , wherein the set of configuration attributes includes one or more of a route attribute, a permissions attribute, a webhook attribute, or a delegate Uniform Resource Indicator (URI) attribute.

18. The non-transitory computer-readable storage medium of claim 17 , wherein the performing of the processing events in the first order includes translating an event message before routing the event message and the performing of the processing of the events in the second order includes routing the event message before translating the event message.

19. The non-transitory computer-readable storage medium of claim 16 , wherein each of the set of configuration attributes is configurable during the real-time processing of the event.

20. The non-transitory computer-readable storage medium of claim 16 , wherein the set of configuration attributes includes a plurality of delegate URIs.

Assignees

• Twilio Inc

Inventors

• Lawson Jeffrey
• Wolthuis John
• Cooke Evan
• Comer Jeffrey

Classifications

• H04L51/52 Primary

  for supporting social networking services · CPC title

• G06F9/542 Primary

  Event management; Broadcasting; Multicasting; Notifications · CPC title

• H04L51/04

  Real-time or near real-time messaging, e.g. instant messaging [IM] · CPC title

• H04L51/212

  using filtering or selective blocking · CPC title

• H04L51/214

  using selective forwarding · CPC title