Event Processing Method in Stream Processing System and Stream Processing System

• US 20150378797A1
• Filed: 09/09/2015
• Published: 12/31/2015
• Est. Priority Date: 06/30/2014
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Zhang, Songshan, Fang, Fengbin, Li, Yuzhang
• Granted Patent: US 9,483,332 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24568 Data stream processing; Continuous queries
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

An event processing method in a stream processing system includes matching a basic event with basic events stored in engine memories corresponding to each matching mode in a rule engine, to determine an engine memory including the basic event, and when it is determined that the engine memory including the basic event is an engine memory corresponding to a full-loop mode, inputting the basic event into the full-loop mode of the rule engine, adding a full-loop identifier to the basic event. This method implements classification processing on complex events by using different matching modes of the rule engine, improving performance of processing a complex event in an Event Stream Processing (ESP) service processing process.

Claims

1. An event processing method in a stream processing system, wherein the stream processing system comprises an input unit and a rule engine, wherein matching modes of the rule engine comprise at least a full-loop mode, a half-loop mode, and a non-loop mode, wherein each matching mode of the rule engine is corresponding to one engine memory, wherein each engine memory stores at least one basic event, and wherein the method comprises:

acquiring, by using the input unit, the at least one basic event that is used to represent a status of a target object, wherein the basic event comprises at least one of a condition and attribute information of the target object;

matching the basic event with basic events stored in engine memories that are corresponding to each matching mode in the rule engine, to determine an engine memory comprising the basic event;

inputting the basic event into the full-loop mode of the rule engine when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the full-loop mode;

adding a full-loop identifier to the basic event when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the full-loop mode;

using the basic event to which the full-loop identifier is added as a full-loop matching result;

executing the basic event to obtain an execution result when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the full-loop mode;

modifying, according to the execution result, the attribute information of the target object in the engine memory corresponding to the full-loop mode;

matching the execution result with the basic events that are stored in the engine memories in the rule engine;

inputting the basic event into the half-loop mode of the rule engine when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the half-loop mode;

adding a half-loop identifier to the basic event when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the half-loop mode;

using the basic event to which the half-loop identifier is added as a half-loop matching result;

executing the basic event to obtain an execution result when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the half-loop mode;

modifying, according to the execution result, the attribute information of the target object in the engine memory corresponding to the half-loop mode;

outputting the execution result; and

inputting the basic event into the non-loop mode of the rule engine when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the non-loop mode;

adding a non-loop identifier to the basic event when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the non-loop mode;

using the basic event to which the non-loop identifier is added as a non-loop matching result;

executing the basic event to obtain an execution result when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the non-loop mode; and

outputting the execution result.

2. The method according to claim 1, wherein after matching the basic event with basic events stored in the engine memories that are corresponding to each matching mode in the rule engine, to determine the engine memory comprising the basic event, the method further comprises:

performing an aggregation operation on at least two matching results of the full-loop matching result, the half-loop matching result, and the non-loop matching result when the at least two matching results of the full-loop matching result, the half-loop matching result, and the non-loop matching result are obtained; and

determining that an obtained aggregation result is a matching result outputted in a high-level matching mode, wherein a level of the full-loop matching result is higher than a level of the half-loop matching result, and wherein the level of the half-loop matching result is higher than a level of the non-loop matching result.

3. The method according to claim 1, wherein before matching the basic event with the basic events stored in the engine memories that are corresponding to each matching mode in the rule engine, to determine the engine memory comprising the basic event, the method further comprises:

acquiring at least two rule events, wherein the rule events comprise a condition, an action, and the attribute information of the target object, and wherein the rule events are events used to represent the status of the target object and the action of the target object;

determining whether an association relationship exists between an action of a first rule event and a condition of a second rule event, wherein the first rule event and the second rule event are any two rule events in the at least two rule events;

using conditions of the first rule event and conditions of the second rule event as the basic event when an association relationship exists between the action of the first rule event and the condition of the second rule event;

storing the basic event in the engine memory corresponding to the full-loop mode; and

determining whether a condition of the first rule event is the attribute information of the target object when the association relationship does not exist between the action of the first rule event and the condition of the second rule event.

4. The method according to claim 3, wherein after determining whether the condition of the first rule event is the attribute information of the target object, the method further comprises:

determining whether the action of the first rule event triggers the condition of the second rule event when it is determined that the condition of the first rule event is the attribute information of the target object;

determining to use the condition of the first rule event as the basic event when it is determined that the condition of the first rule event is not the attribute information of the target object; and

storing the basic event in the engine memory corresponding to the non-loop mode.

5. The method according to claim 4, wherein after determining whether the action of the first rule event triggers the condition of the second rule event, the method further comprises:

determining to use the condition of the first rule event as the basic event when it is determined that the action of the first rule event triggers the condition of the second rule event;

storing the basic event in the engine memory corresponding to the full-loop mode;

determining to use the condition of the rule event as the basic event when it is determined that the action of the first rule event does not trigger the condition of the second rule event; and

placing the basic event in the engine memory corresponding to the half-loop mode.

6. The method according to claim 1, wherein the rule engine is defined by using a domain-specific language (DSL).

7. A stream processing system, comprising:

an input unit, wherein the input unit is configured to acquire at least one basic event that is used to represent a status of a target object, wherein the basic event comprises at least one of a condition and attribute information of the target object; and

a rule engine, wherein the rule engine comprises;

a matching unit, wherein the matching unit is configured to match the basic event with basic events stored in engine memories that are corresponding to each matching mode in the rule engine, to determine an engine memory comprising the basic event; and

an execution unit, wherein matching modes of the rule engine comprise at least;

a full-loop mode;

a half-loop mode; and

a non-loop mode, wherein each matching mode of the rule engine is corresponding to one engine memory, and each engine memory stores at least one basic event, and

wherein the execution unit is configured to;

input the basic event into the full-loop mode of the rule engine when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the full-loop mode;

add a full-loop identifier to the basic event when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the full-loop mode;

use the basic event to which the full-loop identifier is added as a full-loop matching result;

execute the basic event to obtain an execution result when it is determined that the engine memory comprising the basic event is the engine memory corresponding to the full-loop mode;

modify, according to the execution result, the attribute information of the target object in the engine memory corresponding to the full-loop mode;

match the execution result with the basic events that are stored in engine memories in the rule engine;

input the basic event into the half-loop mode of the rule engine when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the half-loop mode;

add a half-loop identifier to the basic event when it is determined that the engine memory comprising the basic event is the engine memory corresponding to the half-loop mode;

use the basic event to which the half-loop identifier is added as a half-loop matching result;

execute the basic event to obtain an execution result when it is determined that the engine memory comprising the basic event is the engine memory corresponding to the half-loop mode;

modify, according to the execution result, the attribute information of the target object in the engine memory corresponding to the half-loop mode;

output the execution result;

input the basic event into the non-loop mode of the rule engine when it is determined that the engine memory comprising the basic event is an engine memory corresponding to the non-loop mode;

add a non-loop identifier to the basic event when it is determined that the engine memory comprising the basic event is the engine memory corresponding to the non-loop mode;

use the basic event to which the non-loop identifier is added as a non-loop matching result;

execute the basic event to obtain an execution result when it is determined that the engine memory comprising the basic event is the engine memory corresponding to the non-loop mode; and

output the execution result.

8. The system according to claim 7, wherein the execution unit is further configured to:

perform an aggregation operation on at least two matching results of the full-loop matching result, the half-loop matching result, and the non-loop matching result when the at least two matching results of the full-loop matching result, the half-loop matching result, and the non-loop matching result are obtained; and

determine that an obtained aggregation result is a matching result outputted in a high-level matching mode, wherein a level of the full-loop matching result is higher than a level of the half-loop matching result, and the level of the half-loop matching result is higher than a level of the non-loop matching result.

9. The system according to claim 7, further comprising:

an acquiring unit, wherein the acquiring unit is configured to acquire at least two rule events, wherein the rule events comprise;

a condition;

an action; and

the attribute information of the target object, wherein the rule events are events used to represent the status of the target object and an action of the target object; and

a determining unit, wherein the determining unit is configured to;

determine whether an association relationship exists between an action of a first rule event and a condition of a second rule event, wherein the first rule event and the second rule event are any two rule events in the at least two rule events;

use conditions of the first rule event and conditions of the second rule event as the basic event when the association relationship exists between the action of the first rule event and the condition of the second rule event;

store the basic event in the engine memory corresponding to the full-loop mode; and

determine whether the condition of the first rule event is the attribute information of the target object when the association relationship does not exist between the action of the first rule event and the condition of the second rule event.

10. The system according to claim 9, wherein the determining unit is further configured to:

determine whether the action of the first rule event triggers the condition of the second rule event when it is determined that the condition of the first rule event is the attribute information of the target object; and

determine to use the condition of the first rule event as the basic event when it is determined that the condition of the first rule event is not the attribute information of the target object; and

store the basic event in the engine memory corresponding to the non-loop mode.

11. The system according to claim 10, wherein the determining unit is further configured to:

determine to use the condition of the first rule event as the basic event when it is determined that the action of the first rule event triggers the condition of the second rule event;

store the basic event in the engine memory corresponding to the full-loop mode;

determine to use the condition of the rule event as the basic event when it is determined that the action of the first rule event does not trigger the condition of the second rule event; and

place the basic event in the engine memory corresponding to the half-loop mode.

12. The system according to claim 7, wherein the rule engine is defined by using a domain-specific language (DSL).