Method and system for complex event processing
First Claim
Patent Images
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;
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;
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.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
33 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; 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; 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. 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; 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; 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. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
-
-
23. 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 in the output queue for output; 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; 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. - View Dependent Claims (24, 25, 26, 27, 28, 29, 30, 31, 32, 33)
-
Specification