KR20130033708A - Event processing method using hierarchical structure and event processing engine and system thereof - Google Patents

Abstract

PURPOSE: An event processing method using a hierarchy structure, an event processing engine, and a system are provided to reuse an intermediate operation value, which is generated in an event process, thereby extracting meaningful data from an event determination and transmission result. CONSTITUTION: When data is generated in a data source system, an event sensor unit(110) senses the data as an event. An event processing engine(120) generates an action plan by processing the data as the event corresponding to defined contents. An event action unit(130) transmits an event processing result which is comprised in a content processor(123) and corresponds to an event definition. An event monitor unit(140) performs real time monitoring, event monitoring, sensor monitoring, queue monitoring, and processing situation monitoring of various situations. An event control unit(150) manages information necessary for executing an event processor.

Description

TECHNICAL FIELD [0001] The present invention relates to an event processing method using a hierarchical structure, and an event processing engine using the hierarchical structure,

The present invention relates to an event processing technique, and more particularly, to an event processing method using a hierarchical structure and an event processing engine using the same and a system thereof.

Event processing is being developed variously as a major technical factor that has a major influence on the efficiency and performance of the computer system.

An example of a conventional event processing method is largely performed through the following steps.

(i) define an execution event for the business event, (ii) determine the condition through rule operation if an event occurs in the source data, and (iii) perform a predetermined event processing as a business event if the event corresponds to an execution event. do.

However, this prior art has the following problems. Since the rule operation definition is limited to one at the time of event processing, in order to perform various actions with respect to the rule, it is necessary to newly create an event with another action having the same function. In addition, if the intermediate operation value generated during the operation process is not utilized during the event processing, and the intermediate operation is required, the component called the indicator is defined and stored in the database, so that the system performance degradation due to the database access occurs There is a problem. Due to these problems, data processing occurring in real time in real time is practically difficult, and a large-scale complex event processing can not be performed.

The present application is to provide an event processing technology that can efficiently process a significant complex event for a large amount of transactions (transaction) generated from various systems of the enterprise.

In addition, the present application is to provide an event processing technology that can be reconfigured event definition with the addition of components by standardizing the event definition structure.

In addition, the present application is to provide an event processing technique that can process a plurality of actions with one rule for one event using branch processing.

In addition, the present application is further provided with a stream processing function, to provide an event processing technology that can reuse the object, such as a filter that occurred previously, and its operation result.

In addition, the present application aims to provide an event processing technique capable of reusing the intermediate calculation result generated in event processing through event context transfer.

Among the embodiments, the event processing engine performs event processing on the input data. The event processing engine includes an event definition module and an event process engine. Wherein the event definition module is a sequential structure for at least one event object and content for the event and the at least one event object is a source of data corresponding to the event, And generates an abstract event definition including the content as an end of the sequential structure. Wherein the event processing engine processes the input data according to a sequential structure of the abstract event definition, if the data corresponds to the abstract event definition, If the definition structure is satisfied, process it according to the content of the abstract event.

In one embodiment, the sequential structure may be defined as a cyclic directional graph structure or a cyclic directional graph structure including a termination condition.

In at least one example embodiment, the at least one event object may include a condition object that defines a branch point in the sequential structure such that the abstract event definition includes a plurality of contents.

In one embodiment, the at least one event object stores and references the filtered data as an instance of the filter object in memory, and a filter stream that allows another event object to directly query an instance of the stored filter object You can include view objects.

In one embodiment, the at least one event object performs a predefined specific function on the generated data in the sequential structure to generate a specific result, and whether the generated specific result satisfies a specific condition. It can contain a condition function object to review.

In at least one example embodiment, the at least one event object may include a database reference object for obtaining a search result by referring to an external database in the sequential structure.

In one embodiment, the event processing engine may further include a preprocessing engine for setting the corresponding data to the filter object when data corresponding to the filter stream view object is requested.

Among the embodiments, the event definition structure is a sequential structure for at least one event object and contents, and the at least one event object is a source of data corresponding to the event, as a route of the sequential structure And the content is included as an end of the sequential structure.

In an exemplary embodiment, the event definition structure may further include a condition object for determining a specific condition, and the condition object may form a branch point of the sequential structure according to the condition determination.

In one embodiment, the event definition structure may include contents different from each other for each branching according to the branch point.

Among the embodiments, the event processing system performs event processing on the source data using the defined event definition structure. Wherein the event definition structure is a sequential structure for at least one event object and content, the at least one event object includes a filter object for determining whether the source data corresponds to the event, as the root of the sequential structure, Content is included at the end of the sequential structure. The event processing system includes an event sensor unit and an event processing engine. The event sensor unit maps the source data to data corresponding to the event definition structure. Wherein the event processing engine processes the input data provided by the event sensor unit to determine whether the data corresponds to the abstract event definition and if so, sequentially processes the input data according to the sequential structure of the abstract event definition, As a result, if the abstract event definition structure is satisfied, it is processed according to the content of the abstract event.

In one embodiment, the sequential structure may be defined as a cyclic directional graph structure or a cyclic directional graph structure including a termination condition.

In one embodiment, the event processing system may further include an event action unit for delivering the event processing result configured in the event processing engine according to the event definition structure.

In one embodiment, the event processing engine may include an event definition module for generating an abstract event definition according to the event definition structure, and data corresponding to the event definition structure for the input data, And an event process engine that processes the events sequentially according to the event definition structure, and processes the events according to contents of the abstract events when the sequential processes are satisfied.

Among the embodiments, an event processing method includes the steps of: (a) mapping received source data and a predefined event structure; (b) constructing a processing sequence for the elements of the event definition structure to generate a processing process (C) filtering the received source data to start event processing; (d) assigning a job to a corresponding event object processor according to the generated process; and (e) And configuring the delivery contents according to the contents included in the event definition structure if it is successfully performed.

In one embodiment, the event processing method may further include a preprocessing step of, when data corresponding to the filter stream view for the filter instance is requested for the source data, setting the corresponding data.

In an embodiment, the step (c) may include generating an event context including input / output data information used in an event object included in an event as a data set of an event instance.

In one embodiment, the step (e) may comprise the step of configuring the delivery content including the intermediate operation results generated during the event processing.

According to the disclosed technology of the present application, independence of an event object for event definition can be guaranteed, and a hierarchical and sequential definition structure can be used, so that a plurality of processes can be processed for one event.

In addition, according to the disclosed technology of the present application, since the intermediate operation value generated in the event processing process can be utilized again, there is an effect that can extract meaningful data in the event determination and delivery results.

In addition, according to the disclosed technology of the present application, there is an effect that can improve the performance by changing to store and retrieve the data that was previously stored in the DB in the memory.

In addition, according to the disclosed technology of the present application, providing an API for event definition and processing has the effect of making it lightweight based on API and increasing portability with other systems.

1 is a reference diagram for explaining an embodiment of a complex event processing system according to the disclosed technology.
2 is a reference diagram for explaining an embodiment of an event configuration according to the disclosed technology.
3 is a reference diagram for explaining an embodiment of an event definition according to the disclosed technology.
4 is a flow diagram illustrating one embodiment of an event processing process in accordance with the disclosed technology.
5 is a reference diagram for explaining an embodiment of event processing performed in a complex event processing system according to the disclosed technology.
FIG. 6 is a reference diagram for explaining an embodiment of processing the event of FIG. 5 according to the related art.
7 is a reference diagram for explaining another embodiment of event processing performed in a complex event processing system according to the disclosed technology.
8 is a reference diagram for explaining another embodiment of event processing performed in a complex event processing system according to the disclosed technology.
9 is a reference diagram for explaining an embodiment of processing the event of FIG. 8 according to the related art.
10 is a reference diagram for explaining another embodiment of event processing performed in a complex event processing system according to the disclosed technology.
FIG. 11 is a reference diagram for explaining an embodiment of processing the event of FIG. 10 according to the related art.

The description of the disclosed technique is merely an example for structural or functional explanation and the scope of the disclosed technology should not be construed as being limited by the embodiments described in the text. That is, the embodiments may be variously modified and may have various forms, and thus the scope of the disclosed technology should be understood to include equivalents capable of realizing the technical idea.

Meanwhile, the meaning of the terms described in the present application should be understood as follows.

The terms "first "," second ", and the like are intended to distinguish one element from another, and the scope of the right should not be limited by these terms. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

It is to be understood that when an element is referred to as being "connected" to another element, it may be directly connected to the other element, but there may be other elements in between. On the other hand, when an element is referred to as being "directly connected" to another element, it should be understood that there are no other elements in between. On the other hand, other expressions describing the relationship between the components, such as "between" and "immediately between" or "neighboring to" and "directly neighboring to", should be interpreted as well.

It should be understood that the singular " include "or" have "are to be construed as including a stated feature, number, step, operation, component, It is to be understood that the combination is intended to specify that it does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

In each step, the identification code (e.g., a, b, c, etc.) is used for convenience of explanation, the identification code does not describe the order of each step, Unless otherwise stated, it may occur differently from the stated order. That is, each step may occur in the same order as described, may be performed substantially concurrently, or may be performed in reverse order.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. Commonly used predefined terms should be interpreted to be consistent with the meanings in the context of the related art and can not be interpreted as having ideal or overly formal meaning unless explicitly defined in the present application.

Table 1 is a reference diagram illustrating composite events in accordance with the disclosed technology.

Event Event that has business meaning AbstractEventElement Object for component definition of Event EventObject Filter Define source data as the starting point for event processing FilterStreamView Object that stores and queries Filter instances in memory DBReference Define a DB Data Reference for Event Processing Condition Rule operation definition for condition determination (define occurrence of branching according to condition) ConditionFunction Formula / Logic / User-Defined Function Arithmetic component ConditionFunctionStreamView An object that stores and queries the ConditionFunction instance in memory. Contents Define what to deliver and what Cachemanager Used to store and share data needed for event processing in memory Mapper Mapping between Data Sources and Filters EventContext Data set object of the event instance for event processing

In the disclosed technology, EVENT refers to an event that has a business meaning, and means a final unit that defines an event for processing.

An abstract event element (AbstractEventElement) is an object for conceptual definition of an event component and has a one-to-one relationship with an event. An abstract event element (AbstractEventElement) can be composed of a number of event objects (EventObject) and contents (Contents).

An event object (EventObject) can be a component of an event. EventObjects can be defined and componentized individually. The event objects generated in this way can be used in addition to the components of the event.

The types of event objects are as follows.

A filter is an object representing the starting point of event processing in which an event is triggered. A filter may define external source data received from a data source system.

A filter stream view (FilterStreamView) is an object that stores and queries the actual data instance (Filter instance) of the filter in memory. In one embodiment, the filter stream view (FilterStreamView) has a value of (PREVIOUS_VALUE, previous value), (AVERAGE, average value), (SUM, sum), (COUNT, The calculation result can be inquired for at least one.

A database reference object (DB Reference) is an object for defining necessary data by referring to an external DB. A database reference object (DB Reference) can be accessed by executing a query by accessing the DB under a DB connection name.

Condition defines rule operations for condition determination. In addition, the condition may determine True / False on the operation result. For example, if it is True, you can proceed to the next process and if it is False, you can end it.

The disclosed technique can define a branch according to a condition by adding a condition to an event object (EventObject) when a branch is required under a plurality of conditions for the event.

Condition Function Object (ConditionFunction) is an operation component that provides expression, logic, and user-defined function functions that can be used throughout event processing.

The condition function stream view (ConditionFunctionStreamView) is an object storing and inquiring a data instance generated by a condition function object (ConditionFunction) in a memory. In one embodiment, the ConditionFunctionStreamView has a value of (PREVIOUS_VALUE, previous value), (AVERAGE, average value), (SUM, SUM), (COUNT, The result of the operation on at least one of them can be inquired.

Contents define contents and targets to be delivered when corresponding to a specific event. For example, if True after determining the final event, Contents may define a result action corresponding to the corresponding event, for example, delivering specific content or determining a specific target.

The cache manager may temporarily store data to store and share data necessary for event processing in memory.

The mapper may map data received from the data source with a filter.

An event context is an event set for event handling. An event context is generated 1: 1 in an event processing request and may include input / output data information used in an event object in an event.

1 is a reference diagram for explaining an embodiment of a complex event processing system according to the disclosed technology.

Referring to FIG. 1, the complex event processing system 100 includes an event sensor 110, a complex event processing engine 120, and an event action unit 130. . In an embodiment, the complex event processing system 100 may further include an event monitor 140 or an event controller 150.

When data is generated in the data source system, the event sensor unit 110 may sense the detected event as an event. The event sensor unit 110 may provide the sensed source data to the event processing engine 120.

In one embodiment, the event sensor unit 110 may include a sensing API 111 and a mapping unit 112. The sensing API 111 may provide an API for event definition and processing thereof required to determine the source data as an event. The outside may access (call) the sensing API 111 to define an event or process the defined event. The sensing API 111 may provide the received data to the mapping unit 112. The mapping unit 112 may map the received data with a predefined event and then provide it to the event processing engine 120.

In an embodiment, the event sensor unit 110 may perform at least one function of event validity check, event format conversion, error processing, and communication with the event source on the received source data. Event Validation is to perform certain tasks to validate the data collected from the event source. Event formatter is to perform definition to define correlation between simple events in case of complex event. Error Processing checks for errors in the source data to be stored in the event queue and logs them to a specific folder. Status Monitoring checks the communication status between the event source and the event queue. Means monitoring.

In one embodiment, the event sensor unit 110 may use a real-time or periodic extraction method for the collection of source data. For example, the event sensor 110 may be a real-time extraction method by agent monitoring, a periodic extraction method by folder monitoring, an event queue transmission method or JMS (Open API) using Open API (Application Programming Interface). At least one of real-time server transmission method using Java Message Service) or a combination thereof may be used.

The event processing engine (CEP) 120 may process an event and generate an action plan based on the data collected by the event sensor unit 110 according to a defined content. The event processing engine (CEP) 120 is a core engine unit of the event processing system and can be configured as a processor for event processing.

The event processing engine (CEP) 120 may include a pre processor engine 121, an event object engine 122, and a content processor 123. In one embodiment, event processing engine (CEP) 120 may further include an event definition module (not shown) or a cache manager 124.

The preprocessor engine 121 may perform preprocessing for event processing according to the event definition.

The event processor engine 122 may start and process each process according to the event processing process configured in the preprocessing engine 121.

In one embodiment, in performing the event processing process, the event processor engine 122 may include a processor configured for each event object to perform event processing. For example, the event processor engine 122 may perform a predetermined filtering on the preprocessed data. However, as shown in the illustrated example, an event processor engine 122 may include a filter processor to dedicate a filter operation. Can be.

In one such embodiment, the EventObject Processor Engine 122 may identify the event object and assign a task to the processor corresponding to the particular event object. To this end, the EventObject Processor Engine 122 includes a FilterStreamView Processor, a DBReference Processor, a ConditionFunction Processor, a ConditionFunctionView Processor, And a processor (Condition Processor).

The contents processor 123 may include content for post-event processing as a final step of event processing.

The event definition module may define components of an event according to an abstract event element. As described above, the abstract event element (AbstractEventElement) is composed of at least one event object (EventObject) and its contents (Contents) and may be configured in a sequential structure. The event definition module may define a business event that can be applied in a corresponding system based on user input or request information. The event definition module may generate event definition meta information about the defined event.

The cache manager 124 may be linked with the event object processor engine 122 to provide a cache memory for event processing.

The event action unit 130 may deliver the event processing result configured in the contents processor 123 according to the event definition. For example, depending on the delivery method defined for each event, the contents can be delivered by SMS, E-mail, DB Insert, etc.

The event monitor unit 140 may perform functions such as real time monitoring, event monitoring, sensor monitoring, queue monitoring, and processing status monitoring of various situations occurring in the complex event processing system.

The event controller 150 is responsible for managing information necessary to execute the event processor. You can manage users or roles, run or stop the event engine, and manage system environment variables.

2 is a reference diagram for explaining an embodiment of an event configuration according to the disclosed technology, and FIG. 3 is a reference diagram for explaining an embodiment of an event definition according to the disclosed technology.

With reference to Figs. 2 and 3, the event configuration and definition will be described. In the disclosed technology, an event refers to an event that has a business meaning, and an event definition may design content to be detected as an event as an event component and define a combination of components. Event processing may be performed while performing operations based on necessary data in the order of predefined event elements.

As illustrated in FIG. 2, an event may include an abstract event element (AEE). As illustrated in FIG. 3, an event may include a plurality of event elements to which a composite pattern is applied. It may be defined as a hierarchy including a. The disclosed hierarchy may constitute an order of event components. In one embodiment, the event may be defined as a circular directional graph structure that includes an acyclic directional graph structure or an end condition.

For example, an event may be defined as a hierarchy starting with a filter (F) and ending with content (CT). At least one event object (EO) or condition (CD) may be added between the filter and the content. The event object EO may include the above-described FilterStreamView, DB Reference, ConditionFunction, ConditionFunctionStreamView. Condition (CD) can also be added as one of the Event Object (EO), and Condition (CD) changes the processing flow according to the True / False judgment result of the condition (i.e. branching, etc.). Can be performed).

4 is a flow diagram illustrating one embodiment of an event processing process in accordance with the disclosed technology. As shown in FIG. 4, event processing according to the disclosed technique may be performed by visiting a hierarchical event definition structure in a Visitor pattern in order.

When data occurs in the source system, the event sensor unit 110 may perform event processing on the source data and provide it to the event processing engine (CEP) 120. The event processing engine (CEP) 120 may request the event action unit 130 to perform a defined action if it is determined to be TRUE when it is determined as an event by performing a series of procedures.

In more detail, the mapping unit 112 may map the received source data and data defined in the filter (Mapper Processing). As a result of mapping, since it corresponds to the defined data, it may correspond to an event and may provide it to the event processing engine (CEP) 120 (S410).

If a filter stream view instance exists for a filter instance corresponding to the provided source data, the pre-processor engine 121 may perform a data setting operation according to the filter stream view instance (S420) .

The event processor engine 122 may generate an event context for the input data in operation S430. Here, an event context is an event set of an event instance for event processing and is generated 1: 1 with each event. An event context may include input / output data information used in an event object included in an event.

The event processor engine 122 may generate a process to be processed for the corresponding event (S440). That is, the event processor engine 122 may generate a processing process by configuring the processing order for the event definition elements in the event definition meta information.

The event processor engine 122 performs a process of mapping the received input data according to the filter definition information and starting an event (S450).

The event processor engine 122 allocates and processes a task to each event object processor according to the process generated in step S440 (S460). As described above with reference to FIG. 1, an event object processor may include a FilterStreamView Processor, a DBReference Processor, a ConditionFunction Processor, a ConditionFunctionView Processor, and a Condition Processor, each of which processes an Event Object. You can do it.

The contents processor 123 may configure delivery contents according to the event definition (S470). The content may include input data as well as intermediate calculation results generated during event processing.

The event action unit 130 performs a process of delivering the content configured in step S470 according to the delivery method defined when defining the event (S480). Here, the delivery method may be performed by various methods such as SMS, E-mail, DB Insert.

5 is a reference diagram for explaining an embodiment of event processing performed in a complex event processing system according to the disclosed technology, and FIG. 6 is a reference for explaining an embodiment of processing the event of FIG. 5 according to the related art. It is also.

5 and 6 illustrate an example of sensing as an event when the internal temperature of the measuring device is 100 degrees or more.

Referring to FIG. 5, the complex event processing system 100 according to the disclosed technology may combine an event object, including a Filter and a ConditionFucntion, and configure an event as a hierarchical structure including contents thereof. have.

In more detail, the complex event processing system 100 performs filtering (i.e., filters only the internal temperature of the corresponding measuring device received from the measuring device) to confirm that the event corresponds to the present event (Filter), and measures the measured internal temperature value. The rule can be applied to meet the defined condition (100 degrees) (CF). If it exceeds 100 degrees, since it corresponds to True, the processing result can be delivered according to the contents of the corresponding event.

Referring to Figure 6, it can be seen that this embodiment operates similarly in the prior art. That is, the internal temperature measurement information is configured as an initial event based on the event source, and the execution type is configured based on this. Subsequently, a rule (condition) may be applied to perform a subsequent action plan.

This embodiment is an event requiring simple processing without branching, and it can be seen that the event processing procedures according to the prior art and the disclosed technology correspond to each other.

7 is a reference diagram for explaining another embodiment of event processing performed in a complex event processing system according to the disclosed technology.

7 shows an example of measuring the internal temperature of a measuring instrument and detecting an event as a difference if the difference between the current value and the previous value is 30 or more.

Referring to FIG. 7, the complex event processing system 100 combines an event object, including a Filter, a FilterStreamView (FSV), and a ConditionFucntion (CF), and includes an event for the event as a hierarchical structure including contents thereof. Can be configured.

In more detail, the complex event processing system 100 may perform information filtering or filtering on the internal temperature sent by the measuring device, and may query the stream for the internal temperature value that was last measured before the current measurement (FSV). The complex event processing system 100 may check whether the difference between the current measured value and the previous measured value is greater than a defined condition (CF), and if so, deliver the processing result according to the contents of the corresponding event. .

In the embodiment illustrated in FIG. 7, an embodiment in which a previously processed intermediate processing value (middle value) may be utilized, and since the intermediate value cannot be used in the prior art, such an embodiment cannot be processed.

FIG. 8 is a diagram illustrating another embodiment of event processing performed in a complex event processing system according to the disclosed technology, and FIG. 9 is a diagram for describing an embodiment of processing the event of FIG. 8 according to the related art. See also.

8 and 9 illustrate an example in which the internal temperature of the measuring device is measured and sensed as an event when the current temperature is greater than 100 and occurred more than once in the last hour.

Referring to FIG. 8, the complex event processing system 100 combines an event object, including a Filter, two ConditionFucntion (CF), and a ConditionFunctionStreamView (CFSV), and includes a hierarchy including contents thereof. You can configure events as

In more detail, the complex event processing system 100 performs filtering to determine whether the internal temperature sent by the measuring device is information (Filter), and determines whether the current internal temperature value corresponds to the condition (100 degrees) (CF1). The complex event processing system 100 inquires in the stream the number of times that the condition 1 (CF1) has been satisfied in the last hour (CFSV), and determines whether the inquired value exceeds the reference number (two times) (CF2). Eventually, the event processing result can be delivered (Contents).

In the prior art illustrated in FIG. 9, it can be seen that two events should be defined using a connection event. That is, in the prior art, it is not possible to use a hierarchical event structure, and thus, in order to determine two conditions, two different events must be configured and then interconnected and operated. This prior art has a problem that the steps are complicated and difficult.

FIG. 10 is a diagram illustrating another embodiment of event processing performed in a complex event processing system according to the disclosed technology. FIG. 11 is a diagram for describing an embodiment of processing the event of FIG. 10 according to the related art. See also.

10 and 11, the internal temperature of the measuring device is measured to measure a range of levels of a section (section level High (80 <= temperature <100) and section level: Normal (60 <= temperature <80)). When included, the event delivers the interval level.

Referring to FIG. 10, the complex event processing system 100 may configure an event as a branched hierarchical structure including a filter, two conditions, and contents for each condition.

In more detail, the complex event processing system 100 may filter whether information on the internal temperature sent by the measuring device is filtered, and may provide it to Condition 1 and Condition 2, respectively. . Each condition may determine whether the received internal temperature value satisfies a condition in the corresponding section, and may transmit the event processing result accordingly (Contents 1 and 2).

In the case of the prior art shown in FIG. 11, it can be seen that two events are separately defined and processed. That is, in the prior art, it is understood that two events different only in the section level condition with respect to the same contents are defined and judged respectively. This conventional technique has a problem in that the number of events must be increased, and therefore, the number of definition steps increases and the performance deteriorates.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the following claims It can be understood that

Claims (18)

An event processing engine for performing event processing on input data,
The event is a sequential structure for at least one event object and content, and the at least one event object includes a filter object for determining whether the source data corresponding to the event is the root of the sequential structure, and the content is An event definition module for generating an abstract event definition included at the end of the sequential structure; And
And if the input data is data corresponding to the abstract event definition, processing the input data sequentially according to the sequential structure of the abstract event definition, if the input data satisfies the abstract event definition structure as a result of the processing And an event processing engine for processing the contents of the abstract event according to the content of the abstract event.
The method of claim 1, wherein the sequential structure
A circular directional graph structure or a circular directional graph structure including an end condition.
The method of claim 2, wherein the at least one event object
And a condition object for defining a branch point in the sequential structure so that the abstract event definition includes a plurality of contents.
The method of claim 2, wherein the at least one event object
An event processing engine comprising: a filter stream view object for storing and querying the filtered data in memory as an instance of the filter object, and allowing other event objects to directly query the instance of the stored filter object; .
The method of claim 2, wherein the at least one event object
And a condition function object for performing a predetermined function defined on the generated data in the sequential structure to generate a specific result and examining whether or not the generated specific result satisfies a specific condition Event processing engine.
The method of claim 2, wherein the at least one event object
And a database reference object for referring to an external database in the sequential structure to obtain a search result.
5. The method of claim 4, wherein the event processing engine
Further comprising a preprocessing engine for setting the corresponding data to the filter object when data corresponding to the filter stream view object is requested.
A sequential structure for at least one event object and content, wherein the at least one event object includes a filter object that determines whether source data corresponding to the event is the root of the sequential structure, and the content is the sequential structure Event definition structure included at the end of.
9. The method of claim 8, wherein the event definition structure
And a condition object for determining a specific condition, wherein the condition object forms a branch point of the sequential structure according to the condition determination.
10. The method of claim 9, wherein the event definition structure
And different contents for each branched according to the branch point.
In the event processing system that performs event processing on the source data using the defined event definition structure,
The event definition structure is a sequential structure for at least one event object and content, and the at least one event object includes a filter object for determining whether source data corresponding to the corresponding event is a root of the sequential structure. Content is included at the end of the sequential structure,
An event sensor for mapping the source data to data corresponding to the event definition structure; And
And an event processing engine that sequentially processes the input data according to the event definition structure when the input data provided by the event sensor unit corresponds to the event definition structure.
12. The method of claim 11, wherein the sequential structure
And a circular directional graph structure including an acyclic directional graph structure or an end condition.
The system of claim 11, wherein the event processing system is
And an event action unit configured to deliver an event processing result configured in the event processing engine according to the event definition structure.
The method of claim 11, wherein the event processing engine
An event definition module for generating an abstract event definition according to the event definition structure; And
The input data is processed according to the event definition structure, and if it is determined that the input data corresponds to the event definition structure, the input data is sequentially processed according to the event definition structure. If all the sequential processes are satisfied, The event processing system comprising:
(a) mapping the received source data with a predefined event structure;
(b) creating a processing process by constructing a processing order for the components of the event definition structure;
(c) filtering the received source data to start event processing;
(d) assigning a job to the corresponding event object processor according to the generated process; and
(e) if the assigned task is successful, constructing delivery content according to content included in the event definition structure.
The method of claim 15, wherein the event processing method is
And when data corresponding to the filter stream view for the filter instance is requested for the source data, setting the corresponding data.
The method of claim 15, wherein step (c)
A data set of an event instance, comprising: generating an event context including input / output data information used in an event object included in the event.
The method of claim 15, wherein step (e)
And configuring the delivery contents including an intermediate operation result generated during the event processing process.

Images