Method, apparatus, and system for providing and using multi-protocol eventing

Patent metadata

Field	Value
Publication number	US-9787749-B2
Application number	US-201313841445-A
Country	US
Kind code	B2
Filing date	Mar 15, 2013
Priority date	Mar 15, 2013
Publication date	Oct 10, 2017
Grant date	Oct 10, 2017

Abstract

Methods and systems for providing an elegant and efficient multi-protocol eventing layer are disclosed. The multi-protocol eventing layer includes a converged container capable of handling multiple types of protocols to manage events while using an open source database. Accordingly, the multi-protocol eventing layer efficiently provides real-time or near real-time eventing to a plurality of devices for scalability and performance enhancement.

First claim

What is claimed is:

1. A method, comprising:
receiving, by a processor, at a multi-protocol eventing layer, a change request from a first communication device, the change request comprising a request to change a database, the multi-protocol eventing layer comprising a front end of the database, wherein the database comprises an open source, NoSQL database and wherein the change request is one of a plurality of change requests, the plurality of change requests comprising both HyperText Transfer Protocol (HTTP) requests and Session Initiation Protocol (SIP) requests;
sending, by the processor, the change request to a converged container of the multi-protocol eventing layer;
processing the change request, by the converged container of the multi-protocol eventing layer, to enable event updates at the system to be provided to the first communication device and a second communication device in accordance with the change request; and
creating an event notification of the multi-protocol eventing layer, the event notification corresponding to the satisfaction of the change request.

2. The method of claim 1 , further comprising:
determining that a change in the system has occurred, the change in the system satisfying the change request; and
providing an event notification to the first communication device and the second communication device to describe the change.

3. The method of claim 2 , wherein the change corresponds to modification of data from a database.

4. The method of claim 3 , wherein the database comprises a Cassandra database.

5. The method of claim 1 , wherein processing the HTTP request results in a query and processing the SIP request results in a subscription.

6. The method of claim 5 , wherein the converged container comprises a converged JSR 289 container and wherein the event notification is created at an application programming interface layer.

7. The method of claim 1 , wherein the first communication device comprises a user device and the second communication device comprises a user device.

8. The method of claim 1 , wherein the change request results in the creation of a database filter that satisfies the change request.

9. A communication system, comprising:
a communication server;
an eventing module in communication with the communication server and providing a front end to a database, a processor executing the eventing module being programmed to receive a change request from a first communication device, the change request comprising a request to change the database, wherein the database comprises an open source, NoSQL database wherein the change request comprises one of a plurality of change requests the plurality of change requests comprising both HyperText Transfer Protocol (HTTP) requests and Session Initiation Protocol (SIP) requests, wherein the processor executing the eventing module is further programmed to distinguish between a change request in HTTP format and SIP format, wherein the processor executing the eventing module is further programmed to process the change request in HTTP and SIP formats, and wherein the eventing module is further programmed to:
send the change request to a converged container;
process the change request, by the converged container, to enable event updates at the system to be provided to the first communication device and a second communication device in accordance with the change request;
determine that a change in the system has occurred, the change in the system satisfying the change request;
create one or more event notifications, the event notifications corresponding to the satisfaction of the change request; and
provide the event notification to the first communication device and the second communication device to describe the change.

10. The system of claim 9 , wherein the change corresponds to a modification of data from a database.

11. The system of claim 9 , wherein the database comprises a Cassandra database.

12. The system of claim 9 , wherein the system processes the HTTP request resulting in a query and the system processes the SIP request resulting in a subscription.

13. The system of claim 9 , wherein the converged container comprises a converged JSR 289 container and wherein the event notification is created at an application programming interface layer.

14. The system of claim 9 , wherein the first communication device comprises a user device and the second communication device comprises a user device.

15. A communication server in communication with a database, the communication server comprising:
memory;
a processor;
a management module;
an eventing module that receives a change request from a first communication device, wherein the change request comprises a request to change the database, wherein the database comprises an open source, NoSQL database wherein the eventing module comprises a front end of the database, wherein the change request is one of a plurality of change requests, the plurality of change requests comprising both HyperText Transfer Protocol (HTTP) requests and Session Initiation Protocol (SIP) requests and wherein the eventing module is further programmed to process the change requests in HTTP and SIP formats;
a container module;
a user input, wherein the user input receives a change request from a first communication device;
a user output; and
a communication interface.

16. The communication server of claim 15 , wherein the wherein the HTTP change request results in a query and the SIP request results in a subscription.

17. The communication server of claim 15 , wherein the database comprises a Cassandra database.

18. The communication server of claim 15 , wherein the converged container comprises a converged JSR 289 container and wherein the event notification is created at an application programming interface layer.

19. The communication server of claim 15 , wherein the change request results in creating a database filter that satisfies the change request.

20. The communication server of claim 15 , wherein the communication server is in communication with a secondary communication server via a message bus, and wherein the message bus transports messages between the communication server and the secondary communication server.

Assignees

• Avaya Inc

Inventors

• Michie Kenneth O
• Brunson Gordon R
• Braudes Robert E
• Haserodt Kurt
• Lee Hyoungjoo

Classifications

• G06F17/30345

  Physics · mapped topic

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L69/40

  for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title

• H04L67/1004

  Server selection for load balancing · CPC title

• G06F16/23

  Updating · CPC title