Method and system for complex event processing

• US 20080109824A1
• Filed: 12/20/2006
• Published: 05/08/2008
• Est. Priority Date: 11/08/2006
• Status: Active Grant

• Current Assignee: Institute For Information Industry
• Original Assignee: Institute For Information Industry
• Inventors: Huang, Joseph, Chen, Pin-Chan, Hsu, Chih-Hao
• Granted Patent: US 7,457,728 B2
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A method for complex event processing is disclosed. An event correlation engine detects various event correlation rules to analyze events to be detected and then retrieves event processing languages from an event definition storage module to implement and receive other relative events using a process engine.

Claims

1. A method for complex event processing, comprising:

receiving and storing at least one event in an input queue;

determining whether the event corresponds to predefined correlation rules;

if the event does not correspond to the predefined correlation rules, storing the event in an output queue for output;

if the event corresponds to the predefined correlation rules, determining whether a lacking event is detected;

if required events have been received, generating a complex event based on the received event;

storing the complex event in the output queue for output; and

if a lacking event is detected, retrieving event processing language corresponding to the event using a coordination engine to enable a process engine to perform a process corresponding to the event and receive required events.

2. The method for complex event processing as claimed in claim 1, further comprising:

if another lacking event is detected, notifying the coordination engine to enable a guideline engine to determine whether guidelines corresponding to the correlation rules are manually or automatically performed; and

the coordination engine retrieving compositions and data fields of the lacking event using an event definition storage module.

3. The method for complex event processing as claimed in claim 2, wherein if the guidelines corresponding to the correlation rules are manually performed, the guideline engine requests an administrator to determine whether the guidelines are performed.

4. The method for complex event processing as claimed in claim 1, further comprising:

determining the character of a component sending the event;

if the component acts as an event emitter of an event source, subscribing the event and sending the event using the event emitter;

if the component acts as an application interface (API), receiving the event using the application interface (API) provided by an event provider; and

if the component is not the event emitter or the application interface (API), receiving the event using event processing logic defined by a process engine and implementing data access, re-loadable operations, and data transformation to the event.

5. The method for complex event processing as claimed in claim 4, wherein the event emitter is installed on the event source of a client to detect, send, and receive events and subscribe to events.

6. The method for complex event processing as claimed in claim 5, wherein a server publishes events and subscribes and unsubscribes the client to events of the event source.

7. The method for complex event processing as claimed in claim 4, wherein the application interface (API) is installed on a client of the event source and retrieves a query request from a server and responds with the query request to the server.

8. The method for complex event processing as claimed in claim 4, wherein the component acts as a graphical user interface (GUI) and is installed on a client and a user of the client implements an event processing on a server via the graphical user interface (GUI).

9. The method for complex event processing as claimed in claim 4, wherein the event source is installed on a client and directly implements an event processing on a server without any interfaces.

10. The method for complex event processing as claimed in claim 1, further comprising:

providing a timestamp in the event;

when a server publics or subscribes an event to a server, transmitting the timestamp to an event source of the client;

the event source checking the timestamp to determine whether the event is a delay message;

determining whether a historical record comprises previous events corresponding to the timestamp; and

when the timestamp is confirmed, the event source activating event notifying or subscribing.

11. The method for complex event processing as claimed in claim 1, wherein the correlation rules at least comprise a match rule, a repeat rule, an order rule, a reset rule, an upper limit rule for a number, and a time rule.

12. The method for complex event processing as claimed in claim 11, wherein the time rule defines whether an event generated with a time segment or a time interval or at a predetermined time corresponds to the correlation rules.

13. A system for complex event processing, comprising:

a client, comprising an event source for generating an event; and

a server, further comprising;

an input queue, receiving the event;

an output queue;

a process engine;

a correlation engine, comprising multiple predefined correlation rules;

an event definition storage module, comprising event processing languages corresponding to multiple events;

a correlation engine, determining whether the event corresponds to at least one correlation rule, if the event does not correspond, storing the event in the output queue, if the event does correspond, determining whether a lacking event is detected, if not detected, generating a complex event based on the received event, and storing the complex event for output; and

a coordination engine, if a lacking event is not detected, retrieving event processing language corresponding to the event using a coordination engine to enable a process engine to perform a process corresponding to the event and receive required events.

14. The system for complex event processing as claimed in claim 13, further comprising a guideline engine providing multiple predefined guidelines, wherein:

if another lacking event is detected, the guideline engine notifies the coordination engine to determine whether guidelines corresponding to the correlation rules are manually or automatically performed; and

the coordination engine receives compositions and data fields of the lacking event using an event definition storage module.

15. The system for complex event processing as claimed in claim 14, wherein if the guidelines corresponding to the correlation rules are manually performed, the guideline engine requests an administrator to determine whether the guidelines are performed.

16. The system for complex event processing as claimed in claim 13, further comprising:

the coordination engine determines the character of a component sending the event;

if the component acts as an event emitter of an event source, the process engine subscribes to the event and sends the event using the event emitter;

if the component acts as an application interface (API), the process engine receives the event using the application interface (API) provided by an event provider; and

if the component is not the event emitter or the application interface (API), the process engine receives the event using event processing logic defined by a process engine and implements data access, re-loadable operations, and data transformation to the event.

17. The system for complex event processing as claimed in claim 16, wherein the event emitter is installed on the event source of a client to detect, send, and receive events and subscribe to events.

18. The system for complex event processing as claimed in claim 17, wherein the server publishes events and subscribes and unsubscribes the client to events of the event source.

19. The system for complex event processing as claimed in claim 18, wherein the application interface (API) is installed on a client of the event source and retrieves a query request from a server and responds with the query request to the server.

20. The system for complex event processing as claimed in claim 16, wherein the component acts as a graphical user interface (GUI) and is installed on a client and a user of the client implements an event processing on a server via the graphical user interface (GUI).

21. The system for complex event processing as claimed in claim 16, wherein the event source directly implements an event processing on a server without any interfaces.

22. The system for complex event processing as claimed in claim 13, wherein:

the server provides a timestamp in the event and, when issuing or subscribing an event to the server, transmits the timestamp to an event source of the client; and

the event source checks the timestamp to determine whether the event is a delay message, determines whether a historical record comprises previous events corresponding to the timestamp, and, when the timestamp is confirmed, activates event notification or subscription.

23. The system for complex event processing as claimed in claim 13, wherein the correlation rules at least comprise a match rule, a repeat rule, an order rule, a reset rule, an upper limit rule for a number, and a time rule.

24. The system for complex event processing as claimed in claim 23, wherein the time rule defines whether an event generated with a time segment or a time interval or at a predetermined time corresponds to the correlation rules.

25. A computer-readable storage medium storing a computer program providing a method for complex event processing, comprising using a computer to perform the steps of:

receiving and storing at least one event in an input queue;

determining whether the event corresponds to predefined correlation rules;

if the event does not correspond to the predefined correlation rules, storing the event in an output queue for output;

if the event corresponds to the predefined correlation rules, determining whether a lacking event is detected;

if required events have been received, generating a complex event based on the received event;

storing the complex event for output; and

if a lacking event is detected, retrieving event processing language corresponding to the event using a coordination engine to enable a process engine to perform a process corresponding to the event and receive required events.

26. The computer-readable storage medium as claimed in claim 25, further comprising:

if another lacking event is detected, notifying the coordination engine to enable a guideline engine to determine whether guidelines corresponding to the correlation rules are manually or automatically performed; and

the coordination engine receiving compositions and data fields of the lacking event using an event definition storage module.

27. The computer-readable storage medium as claimed in claim 26, wherein if the guidelines corresponding to the correlation rules are manually performed, the guideline engine requests an administrator to determine whether the guidelines are performed.

28. The computer-readable storage medium as claimed in claim 25, further comprising:

determining the character of a component sending the event;

if the component acts as an event emitter of an event source, subscribing the event and sending the event using the event emitter;

if the component acts as an application interface (API), receiving the event using the application interface (API) provided by an event provider; and

if the component is not the event emitter or the application interface (API), receiving the event using event processing logic defined by a process engine and implementing data access, re-loadable operations, and data transformation to the event.

29. The computer-readable storage medium as claimed in claim 28, wherein the event emitter is installed on the event source of a client to detect, send, and receive events and subscribe to events.

30. The computer-readable storage medium as claimed in claim 29, wherein a server publishes events a client subscribes to and unsubscribes from events and event sources.

31. The computer-readable storage medium as claimed in claim 28, wherein the application interface (API) is installed on a client of the event source and retrieves a query request from a server and responds with the query request to the server.

32. The computer-readable storage medium as claimed in claim 28, wherein the component acts as a graphical user interface (GUI) and is installed on a client and a user of the client implements an event processing on a server via the graphical user interface (GUI).

33. The computer-readable storage medium as claimed in claim 28, wherein the event source is installed on a client and directly implements an event processing on a server without any interfaces.

34. The computer-readable storage medium as claimed in claim 25, further comprising:

providing a timestamp in the event;

when a server publics or subscribes an event to a server, transmitting the timestamp to an event source of the client;

the event source checking the timestamp to determine whether the event is a delay message;

determining whether a historical record comprises previous events corresponding to the timestamp; and

when the timestamp is confirmed, the event source activating event notifying or subscribing.

35. The computer-readable storage medium as claimed in claim 25, wherein the correlation rules at least comprise a match rule, a repeat rule, an order rule, a reset rule, an upper limit rule for a number, and a time rule.

36. The computer-readable storage medium as claimed in claim 35, wherein the time rule defines whether an event generated with a time segment or a time interval or at a predetermined time corresponds to the correlation rules.