WO2010107107A1

WO2010107107A1 - Event processing system, event processing method, rule distributor, and program storage medium

Info

Publication number: WO2010107107A1
Application number: PCT/JP2010/054759
Authority: WO
Inventors: 磯山和彦
Original assignee: 日本電気株式会社
Priority date: 2009-03-17
Filing date: 2010-03-15
Publication date: 2010-09-23
Also published as: JPWO2010107107A1; JP5327315B2

Abstract

Provided is an event processing system which is capable of suppressing increase in the dispatch rule set in a dispatcher incident to increase in the processing rule of event. An event processing system comprises a plurality of external dispatchers (140) each transferring an event (201) to a local system (100), and a plurality of local systems (100) each transmitting the results (205) of event processing to an application server (160). Upon receiving a processing rule (202) including the event conditions indicating the conditions of an event (201) to be processed from the application server (160), the local system (100) generates an external dispatch rule (204) where the aggregate event conditions aggregating a plurality of event conditions are the external event conditions, and sets the external dispatch rule (204) in the external dispatcher (140). The external dispatcher (140) transfers the event (201) to the local system (100) with reference to the external dispatch rule (204).

Description

Event processing system, event processing method, rule distribution device, and program storage medium

The present invention relates to an event processing system, an event processing method, a rule distribution apparatus, and a program storage medium, and in particular, an event processing system that processes a large amount of events from devices such as RFID (Radio Frequency Identification) and sensors, The present invention relates to an event processing method, a rule distribution device, and a program storage medium.

An example of a system that processes a large number of events generated from a device or the like is described in Japanese Patent No. 4161998. FIG. 17 shows a load distribution distribution system disclosed in Japanese Patent No. 41611998. Referring to FIG. 17, the load distribution distribution system includes an event processing distribution unit 501, a context-independent distribution unit 502, a plurality of context-dependent distribution units (dispatchers) 503a and 503b (hereinafter abbreviated as 503), and a plurality of event processes. The

servers

504a and 504b (hereinafter abbreviated as 504) are configured. The

applications

506a and 506b (hereinafter abbreviated as 506) that request event processing transmit event processing rules to the event processing distributor 501 (arrow 511). The event processing distributor 501 that has received the processing rule sets the processing rule in the event processing server 504 so that the load on the event processing server 504 is equalized, and event processing related to the same event is performed by the same server. (Arrow 512).
For example, in the RFID system, when the application 506 wants to detect all the RFID tags of all the members necessary for manufacturing a certain product, the application 506 reads “If all the RFID tags of all the members of a certain product are detected, the application Process rule "is sent to the event processing distributor 501. The event processing distributor 501 sets this processing rule, for example, in the event processing server 504a.
The event processing distributor 501 sets an event distribution rule (dispatch rule) in all the context-dependent distribution units 503 so that the event to be processed is transferred to the processing server for which the processing rule related to the event is set (arrow) 513a, 513b).
In the case of the example shown above, the event processing distributor 501 sets the event distribution rule that “the detection event of the RFID tag of the member related to the product is transferred to the event processing server 504a” to the context-dependent distributor 503 (dispatcher). Set.
As a result, an event generated from an

event generation source

505a, 505b (hereinafter abbreviated as 505) such as a device is sent to the event processing server 504 in which a processing rule regarding the event is set by the context-dependent event distributor 503 (dispatcher). (Arrows 514a, 514b, 515a, 515b, 516a, 516b, 516c, 516d). The event processing server 504 processes the event based on the processing rule, and notifies the processing result to the application 506 (

arrows

517a and 517b).

In a system in which a plurality of dispatchers are distributed like the load distribution distribution system of Japanese Patent No. 4161998, it is impossible to predict which dispatcher can receive an event that matches the event distribution rule. Therefore, the event processing distributor sets the generated dispatch rule to all dispatchers so that the event can be transferred to the event processing server for which the processing rule related to the event is set regardless of which dispatcher receives the event. To do.
Therefore, as the number of applications increases and the event processing rules increase, the processing rules are distributed and distributed to multiple processing servers, but the dispatch rules set in the dispatcher increase, and the processing load associated with dispatch rule search There was a problem of increasing.
An object of the present invention is to solve the above-described problems, an event processing system and an event processing method capable of suppressing an increase in dispatch rules set in a dispatcher even when the number of applications increases and an event processing rule increases. It is to provide a rule distribution device and a program storage medium.

The event processing system of the present invention includes a plurality of external dispatchers that receive events from an event generation source and a plurality of local systems that transmit event processing results to an application server, and each of the plurality of local systems includes the application When a processing rule including an event condition indicating an event condition to be processed is received from a server, an aggregate event condition is generated by aggregating a plurality of the event conditions, the aggregate event condition is set as an external event condition, and the local system is When an external dispatch rule that is a transfer destination of the event that matches an external event condition is generated, the external dispatch rule is set in the external dispatcher, and the event is received from the external dispatcher, the processing rule is Processing the event, the processing result of the event, and notifies the application server of the transmission source of the processing rule,
When each of the plurality of external dispatchers receives the event from the event generation source, each of the plurality of external dispatchers refers to the external dispatch rule, and sends the event to the local system of the transfer destination corresponding to the external event condition that matches the event. It is characterized by transferring.
The rule distribution device of the present invention is provided in a local system having at least one processing server and at least one local dispatcher, and sets processing rules received from an application server to any one of the processing servers of the local system. And a local dispatch rule that uses the processing server as a transfer destination of an event that matches the event condition included in the processing rule, and sets the local dispatch rule in the local dispatcher of the local system. Generating an aggregated event condition that aggregates a plurality of the event conditions, setting the aggregated event condition as an external event condition, and using the local system as a transfer destination of the event that matches the external event condition Generates Le, characterized in that a dispatch rule setting unit which sets the external dispatch rule to external dispatcher.
In the event processing method of the present invention, when the local system receives a processing rule including an event condition indicating an event condition to be processed from the application server, the local system sets an aggregate event condition obtained by aggregating a plurality of the event conditions. Generate the aggregate event condition as an external event condition, generate an external dispatch rule with the local system as a transfer destination of the event that matches the external event condition, set the external dispatch rule in the external dispatcher, and When the external dispatcher receives the event from the event generation source, the external dispatcher refers to the external dispatch rule and transfers the event to the local system of the transfer destination corresponding to the external event condition that matches the event. When the local system receives the event from the external dispatcher, the local system processes the event according to the processing rule and sends the processing result of the event to the application server that is the transmission source of the processing rule. It is characterized by notifying.
The program recording medium of the present invention sets a processing rule received from an application server to any one of the processing servers of a local system having at least one processing server and at least one local dispatcher. A local dispatch rule is generated as a transfer destination of an event that matches an event condition included in the processing rule, the local dispatch rule is set in the local dispatcher of the local system, and a plurality of event conditions are aggregated Generate an event condition, set the aggregated event condition as an external event condition, generate an external dispatch rule with the local system as the transfer destination of the event that matches the external event condition, and generate the external dispatch To execute a process of setting Lumpur external dispatcher.

An effect of the present invention is that an increase in dispatch rules accompanying an increase in processing rules can be suppressed in an event processing system.

It is a figure which shows the structure of the whole event processing system in 1st embodiment of this invention. It is a figure which shows the structure of the local system 100 in 1st embodiment of this invention. It is a sequence diagram which shows the setting operation | movement of the dispatch rule in 1st embodiment of this invention. It is a sequence diagram which shows the operation | movement of the event process in 1st embodiment of this invention. It is a figure which shows the example of the process rule 202 in 1st embodiment of this invention. It is a figure which shows the example of the process rule setting information 211 in 1st embodiment of this invention. It is a figure which shows the example of the local dispatch rule 203 in 1st embodiment of this invention. It is a figure which shows the example of the external dispatch rule 204 produced | generated by the local system 100 in 1st embodiment of this invention. It is a figure which shows the example of the external dispatch rule 204 set to the external dispatcher in 1st embodiment of this invention. It is a figure which shows the example of the event 201 in 1st embodiment of this invention. It is a figure which shows the characteristic structure of 1st embodiment of this invention. It is a figure which shows the structure of the whole event processing system in 2nd embodiment of this invention. It is a figure which shows the structure of the local system 100 in 2nd embodiment of this invention. It is a sequence diagram which shows the operation | movement of the event process in 2nd embodiment of this invention. It is a figure which shows the example of the external dispatch rule 204 produced | generated by the local system 100 in 2nd embodiment of this invention. It is a figure which shows the example of the external dispatch rule 204 set to the external dispatcher in 2nd embodiment of this invention. It is a figure which shows the structure of the load distribution distribution system of the patent 4161998 gazette.

DESCRIPTION OF SYMBOLS 100 Local system 110 Rule distribution part 111 Processing rule setting part 112 Processing rule distribution algorithm memory | storage part 113 Processing rule setting information storage part 114 Dispatch rule setting part 115 Event discard counter 120 Processing server 130 Local dispatcher 140 External dispatcher 150 Event generation source 160 Application Server 201 Event 202 Processing rule 203 Local dispatch rule 204 External dispatch rule 205 Event processing result 211 Processing rule setting information

(First embodiment)
Next, a first embodiment of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a configuration diagram of the entire event processing system according to the first embodiment of the present invention. Referring to FIG. 1, the first embodiment of the event processing system of the present invention includes a plurality of local systems 100 installed on a network (not shown), a plurality of external dispatchers 140, an event source 150, and An application server 160 is provided.
Here, the local system 100 has two local systems with identifiers LS1 and LS2, respectively. The plurality of external dispatchers 140 have four dispatchers with identifiers GD1 to GD4, respectively. The event generation source 150 has eight event generation sources with identifiers G1 to G8, respectively. The application server 160 has six application servers with identifiers AS11, AS12, AS13, AS21, AS22, and AS23, respectively.
In each drawing and the following description, the symbol in parentheses following the reference number indicates an identifier. For example, the local system 100 (LS1) indicates the local system with the identifier LS1, and the application server 160 (AS11) indicates the application server with the identifier AS11. This is the same for the processing rules.
The event generation source 150 transmits the detected information to the local system 100 as an event 201. The event generation source 150 may be anything as long as it can detect information and transmit it to the local system 100.
Examples of the event generation source 150 include a non-contact or contact-type information reading device such as an RFID reader and a magnetic card reader, and various sensors for detecting temperature, atmospheric pressure, acceleration, and the like.
In addition to “information detected by the event generation source 150 at a certain time (for example, an identifier of an RFID tag detected at a certain time, temperature, atmospheric pressure, acceleration, etc.)” in the event 201 transmitted by the event generation source 150, Attributes such as “type of information detected by the event source (event source type)”, “identifier of the event source (event source identifier)”, “related information such as detection time of detected information”, etc. It is included as information (event attribute information).
When receiving the event 201 from the event generation source 150, the external dispatcher 140 refers to the external dispatch rule 204 and transfers the event 201 to the local system 100.
The application server 160 is a server on which an application that performs various types of information processing on the event 201 detected in the event generation source 150 operates. The application server 160 performs various types of information processing on the results of processing performed in the local system 100 for the event 201 detected by the event generation source 150. In addition, the application server 160 localizes an event condition specifying the condition of the event 201 to be processed by the local system 100 and a processing rule 202 including the processing content performed by the local system 100 for the event 201 that matches the event condition. To system 100.
The local system 100 generates an external dispatch rule 204 based on the processing rule 202 received from the application server 160 and sets the external dispatch rule 204 in the external dispatcher 140. When the local system 100 receives the event 201 from the external dispatcher 140, the local system 100 processes the event 201 according to the processing rule 202, and transmits the processing result (event processing result 205) of the event 201 to the application server 160.
The local system 100 further includes a rule distribution unit 110, at least one processing server 120, and at least one local dispatcher 130. FIG. 1 shows a case where the local system 100 includes a plurality of processing servers 120 and one local dispatcher 130. Here, the processing server 102 has six processing servers with identifiers PS11, PS12, PS13, PS21, PS22, and PS23, respectively. The processing server 202 (PS11, PS12, PS13) is arranged in the local system 100 (LS1), and the processing server 202 (PS21, PS22, PS23) is arranged in the local system 100 (LS2).
The rule distribution unit 110 of the local system 100 performs setting of the processing rule 202 to the processing server 120, generation of the local dispatch rule 203, and generation of the external dispatch rule 204. The processing server 120 processes the event 201 according to the processing rule 202. When the local dispatcher 130 receives the event 201 from the external dispatcher 140, the local dispatcher 130 refers to the local dispatch rule 203 and transfers the event 201 to the processing server 120 of the local system 100.
FIG. 2 shows the configuration of the local system 100 in the first embodiment of the present invention. The rule distribution unit 110 of the local system 100 further includes a processing rule setting unit 111, a processing rule distribution algorithm storage unit 112, a processing rule setting information storage unit 113, and a dispatch rule setting unit 114.
When the processing rule setting unit 111 receives the processing rule 202 from the application server 160, the processing rule setting unit 111 determines the processing server 120 that processes the processing rule 202 and sets the processing rule 202. The processing rule distribution algorithm storage unit 112 stores and manages a processing rule distribution algorithm (not shown) for determining the processing server 120 that processes the processing rule 202. The processing rule setting information storage unit 113 stores and manages the setting result of the processing rule 202 as processing rule setting information 211. The dispatch rule setting unit 114 generates a local dispatch rule 203 and sets it in the local dispatcher 130. In addition, the dispatch rule setting unit 114 generates an external dispatch rule 204 and sets it in the external dispatcher 140.
Note that the rule distribution unit 110, the processing server 120, the local dispatcher 130, the external dispatcher 140, the event generation source 150, and the application server 160 may be information processing devices that operate under program control. Some of these may be configured as one device.
Next, the operation of the first embodiment of the present invention will be described with reference to the drawings.
First, the dispatch rule setting operation in the first embodiment of the present invention will be described. FIG. 3 is a sequence diagram showing a dispatch rule setting operation in the first embodiment of the present invention.
First, it is assumed that the local system 100 from which each application server 160 requests the processing of the event 201 is determined in advance and set in each application server 160. Similarly, it is assumed that the external dispatcher 140 from which each event generation source 150 transmits the event 201 is also determined in advance and set to each event generation source 150. The above-described setting for the local system 100 in the application server 160 may be set by an administrator directly specifying the local system 100, or each application server 160 may be set to a nearby local system based on the distance on the network. 100 may be detected and set. Similarly, the above setting regarding the external dispatcher 140 at the event source 150 may be set by the administrator directly specifying the external dispatcher 140, or each event source 150 may be set based on the distance on the network. Alternatively, a nearby external dispatcher 140 may be detected and set.
The application server 160 that requests processing of the event 201 transmits the processing rule 202 to the local system 100 (step S101).
Here, as shown in FIG. 5, the processing rule 202 includes processing rule identifiers R11, R12, R21, and R22, event conditions that specify the conditions of the event 201 that the local system 100 processes, associated with each rule identifier, And processing performed by the local system 100 for the event 201 that matches the event condition.
FIG. 5 shows an example in which the local system 100 (LS1) receives the processing rule 202 (R11, R12) and the local system 100 (LS2) receives the processing rule 202 (R21, R22). In the example of FIG. 5, the event generation source type (RFID here) and detection information (RFID tag Tag ID = 1 to 3) are specified as event conditions in the processing rule 202 (PR11) of the local system 100 (LS1). ing. Further, “notify to application server AS11” is designated as the processing contents of the processing server 120 for this event condition.
When the local system 100 receives the processing rule 202, the processing rule setting unit 111 of the rule distribution unit 110 stores the processing rule distribution algorithm stored in the processing rule distribution algorithm storage unit 112 and the processing rule setting information storage unit 113. With reference to the processing rule setting information 211, the processing server 120 that processes the processing rule 202 is determined (step S102). The local system 100 sets the processing rule 202 in the determined processing server 120 (step S103). The processing rule setting unit 111 updates the processing rule setting information 211, and stores the updated processing rule setting information 211 in the processing rule setting information storage unit 113 (step S104).
Here, as the processing rule distribution algorithm, for example, a method of distributing the processing rules 202 so that the load of the processing server 120 is equalized according to the processing content, or an event as described in Japanese Patent No. 4161998 is disclosed. There is a method of distributing processing rules 202 having the same conditions to the same processing server 120.
Further, as shown in FIG. 6, the processing rule setting information 211 includes a processing server identifier and an identifier of the set processing rule 202.
FIG. 6 shows an example of the processing rules 202 set in the processing servers (PS11, PS12) of the local system 100 (LS1) and the processing servers (PS21, PS22) of the local system 100 (LS2). In the example of FIG. 6, the processing rule 202 (PR11) is set in the processing server 120 (PS11) of the local system 100 (LS1). With this setting, the processing server 120 (PS11) processes the processing rule 202 (R11).
The dispatch rule setting unit 114 generates a local dispatch rule 203 with the processing server 120 set with the processing rule 202 as a transfer destination of the event 201 that matches the event condition of the processing rule 202 (step S105).
As shown in FIG. 7, the local dispatch rule 203 includes local dispatch rule identifiers DRL11, DRL12, DRL21, and DRL22, an event condition associated with each rule identifier, and an identifier of the processing server 120 that is a transfer destination.
FIG. 7 shows an example of the local dispatch rule 203 (DRL11, DRL12) generated by the local system 100 (LS1) and the local dispatch rule 203 (DRL21, DRL22) generated by the local system 100 (LS2). In the example of FIG. 7, as the local dispatch rule 203 (DRL11) of the local system 100 (LS1), the event condition (event generation source type: RFID, detection information: TagID = 1-3) ), The identifier (PS11) of the processing server 120 that processes the processing rule 202 (PR11) is set as the transfer destination.
The dispatch rule setting unit 114 sets the generated local dispatch rule 203 in the local dispatcher 130 (step S106).
The dispatch rule setting unit 114 generates an aggregate event condition obtained by aggregating the event conditions of the plurality of processing rules 202, sets the external event condition as the aggregate event condition, and sets the local local system 100 for the event 201 that matches the external event condition. An external dispatch rule 204 (with aggregation) as a transfer destination is generated (step S107).
Here, as an event condition aggregation method, for example, when an event condition is specified by a value of detection information, a range of values including a plurality of event conditions may be set as the aggregation event condition.
For example, when the processing rule 202 (PR11, PR12) as shown in FIG. 5 is set in the local system 100 (LS1), the PR11 event condition (RFID, TagID = 1 to 3), the PR12 event condition (RFID , TagID = 5 to 7) can be aggregated to generate an aggregate event condition (RFID, TagID = 1 to 7).
In addition, when the event condition is specified by a hierarchical value such as 1.1, 1.3, 2.1, 2.5, the value of the hierarchy common to a plurality of event conditions is used as the aggregate event condition Also good. In this case, for the event conditions 1.1, 1.3, 2.1, 2.5, the aggregated event conditions 1 *, 2. * (* Is an arbitrary number) can be generated.
As shown in FIG. 8, the external dispatch rule 204 includes the external dispatch rule identifiers DRG11, DRG12, DRG21, and DRG22, the external event condition associated with each rule identifier, and the identifier of the local system 100 that is the transfer destination of the event 201. Including.
FIG. 8 shows an example of the external dispatch rule 204 (DRG11, DRG12) generated by the local system 100 (LS1) and the dispatch rule 204 (DRG21, DRG22) generated by the local system 100 (LS2). In the example of FIG. 8, the external event condition of the external dispatch rule 204 (DRG11) generated by the local system 100 (LS1) is an aggregated event condition that aggregates the event conditions of the processing rule 202 (PR11, PR12) of FIG. RFID, TagID = 1 to 7) is set, and the identifier of the local system 100 (LS1) is set as the transfer destination. Further, the external event condition of the external dispatch rule 204 (DRG 21) generated by the local system 100 (LS2) includes an aggregate event condition (RFID, TagID =) that aggregates the event conditions of the processing rule 202 (PR21, PR22) of FIG. 5 to 11) are set, and the identifier of the local system 100 (LS2) is set as the transfer destination.
The dispatch rule setting unit 114 sets the generated external dispatch rule 204 (with aggregation) in the external dispatcher 140 (step S108).
For example, when the local system 100 (LS1, LS2) sets the external dispatch rule 204 (DRG11, DRG21) in the external dispatcher 140, the external dispatch rule 204 as shown in FIG. 9 is set in each external dispatcher 140. The
Next, the event processing operation in the first embodiment of the present invention will be described. FIG. 4 is a sequence diagram showing an event processing operation in the first embodiment of the present invention.
When the event generation source 150 detects information to be detected, the event generation source 150 transmits the detected information to the external dispatcher 140 as an event 201 (step S201).
As shown in FIG. 10, the event 201 can include event attribute information such as an event identifier 131, an event generation source type, an event generation source identifier, a detection time, and detection information. In the example of FIG. 10, event generation source type: RFID, event generation source identifier: G3, and detection information: TagID = 6 are set as event attribute information of event 201 (I31).
When receiving the event 201, the external dispatcher 140 searches whether or not the event attribute information included in the event 201 matches any of the external event conditions of the external dispatch rule 204 (step S202). If there is a matching external event condition, the external dispatcher 140 refers to the external dispatch rule 204 and transfers the event 201 to the local system 100 corresponding to the external event condition (steps S203 and S204).
For example, when the external dispatcher 140 (GD2) receives the event 201 (I31), the event attribute information (event source type: RFID, detection information: TagID = 6) of the event 201 (I31) is stored in the external dispatch rule 204 ( The external dispatcher 140 (GD2) transfers the event 201 (I31) to the local system 100 (LS1) and the local system 100 (LS2) in order to meet the external event conditions of the DRG11 and DRG21).
When the external dispatcher 140 (GD2) receives the event 201 (I41), the event attribute information (event source type: RFID, detection information: TagID = 4) of the event 201 (I41) is stored in the external dispatch rule 204 ( In order to meet the external event condition of the DRG 11), the external dispatcher 140 (GD2) transfers the event 201 (I41) to the local system 100 (LS1).
When the local system 100 receives the event 201, the local dispatcher 130 searches whether the event attribute information included in the event 201 matches any of the event conditions of the local dispatch rule 203 (steps S211 and S221). If there is a matching event condition, the local dispatcher 130 refers to the local dispatch rule 203 and transfers the event 201 to the processing server 120 corresponding to the event condition (steps S212 and S222). If there is no matching event condition, the event 201 is discarded.
For example, when the local system 100 (LS1) receives the event 201 (I31), the event attribute information (event source type: RFID, detection information: TagID = 6) of the event 201 (I31) is the local dispatch rule 203 ( In order to meet the event condition of the DRL 12), the local dispatcher 130 of the local system 100 (LS1) transfers the event 201 (I31) to the processing server 120 (PS12). Similarly, when the local system 100 (LS2) receives the event 201 (I31), the event attribute information (event source type: RFID, detection information: TagID = 6) of the event 201 (I31) is the local dispatch rule 203. Since the event condition of (DRL21) is met, the local dispatcher 130 of the local system 100 (LS2) transfers the event 201 (I31) to the processing server 120 (PS21).
When the local system 100 (LS1) receives the event 201 (I41), the event attribute information (event source type: RFID, detection information: TagID = 4) of the event 201 (I41) Since the event condition is not met, the local dispatcher 130 of the local system 100 (LS1) discards the event 201 (I41).
When the processing server 120 of the local system 100 receives the event 201, the processing server 120 processes the event 201 according to the processing rule 202 (steps S213 and S223), and transmits the event processing result 205 to the application server 160 (step S214, S224).
For example, the processing server 120 (PS12) of the local system 100 (LS1) transmits the event 201 (I31) to the application server 160 (AS12) as the event processing result 205. Further, the processing server 120 (PS21) of the local system 100 (LS2) transmits the event 201 (I31) to the application server 160 (AS21) as the event processing result 205.
As described above, the event 201 (I31) (TagID = 6) transmitted from the event generation source 150 under the local system 100 is transferred to the local system 100 (LS1, LS2) as shown in FIG. 205 is transmitted to the application server 160 (AS12, 21).
Thus, the operation of the first embodiment of the present invention is completed.
Next, FIG. 11 shows a characteristic configuration of the first embodiment.
The event processing system includes a plurality of external dispatchers 140 that receive the event 201 from the event generation source 150 and a plurality of local systems 100 that transmit the event processing result 205 to the application server 160.
Here, the local system 100 receives the processing rule 202 including the event condition indicating the condition of the event 201 to be processed from the application server 160, and generates an aggregate event condition in which a plurality of event conditions are aggregated. The local system 100 uses the aggregate event condition as an external event condition, generates an external dispatch rule 204 with the local system as a transfer destination of the event 201 that matches the external event condition, and uses the external dispatch rule 204 as the external dispatcher 140. Set to. When the local system 100 receives the event 201 from the external dispatcher 140, the local system 100 processes the event 201 according to the processing rule 202, and notifies the event processing result 205 to the application server 160 that is the transmission source of the processing rule 202.
When the external dispatcher 140 receives the event 201 from the event generation source 150, the external dispatcher 140 refers to the external dispatch rule 204 and sends the event 201 to the local system 100 that is a transfer destination corresponding to the external event condition that matches the event 201. Forward.
According to the first embodiment of this invention, in the event processing system, it is possible to suppress an increase in dispatch rules accompanying an increase in processing rules. The reason for this is that the local system 100 sets an external event rule that is a consolidated event condition obtained by aggregating a plurality of event conditions as an external event condition, and sets an external dispatch rule 204 as a transfer destination of an event 201 that matches the external event condition. This is because it is set to 140.
(Second embodiment)
Next, a second embodiment of the present invention will be described in detail with reference to the drawings.
In the second embodiment of the present invention, when the number of events 201 discarded in the local dispatcher 130 is large, the aggregation of event conditions is stopped, and the event 201 discarded by the external dispatcher 140 in the local system 100 is Transfer to the local system 100 is suppressed.
In the second embodiment of the present invention, the local dispatcher 130 of the local system 100 counts the number of events to be discarded, and when the number of events to be discarded exceeds a predetermined value, the external dispatch rule 204 is restarted. In the point to set, it differs from 1st embodiment of this invention.
In the second embodiment of the present invention, components having the same reference numerals as those in the first embodiment are the same as those in the first embodiment unless otherwise specified.
FIG. 12 shows the configuration of the entire event processing system according to the second embodiment of the present invention, and FIG. 13 shows the configuration of the local system 100 according to the second embodiment of the present invention. Referring to FIG. 13, the local dispatcher 130 of the local system 100 further includes an event discard counter 115 that counts the number of events 201 discarded.
The local dispatcher 130 counts the number of events 201 that do not match the local dispatch rule 203 and are discarded by the event discard counter 115. Further, the contents of the event discard counter 115 are periodically transmitted to the dispatch rule setting unit 114 as dispatch statistical information 206.
The dispatch rule setting unit 114 refers to the value of the event discard counter 115 received from the local dispatcher 130. When the discard number of the event 201 exceeds a predetermined threshold, the event rule aggregation is stopped, and the external dispatch rule 204 To reset.
Next, the operation of the second embodiment of the present invention will be described.
The dispatch rule setting operation in the second embodiment of the present invention is the same as that in the first embodiment (FIG. 3) of the present invention. Here, as in the first embodiment of the present invention, it is assumed that the external dispatch rule 204 as shown in FIG. 9 is set in each external dispatcher 140 based on the processing rule 202 of FIG. .
Next, the event processing operation in the second embodiment of the present invention will be described. FIG. 14 is a sequence diagram showing an event processing operation according to the second embodiment of the present invention.
Processing from when the event generation source 150 transmits the event 201 to when the local dispatcher 130 searches for the event condition of the local dispatch rule 203 (steps S301 to S311) is the first embodiment (steps S201 to S211). It will be the same.
In step S <b> 311, if there is no event condition that matches the event attribute information of the event 201 in the event condition of the local dispatch rule 203, the local dispatcher 130 discards the event 201. In this case, the local dispatcher 130 adds 1 to the event discard counter 115 (step S312).
For example, when the local system 100 (LS1) receives the event 201 (I41), the event attribute information (event source type: RFID, detection information: TagID = 4) of the event 201 (I41) Since the event condition is not met, the local dispatcher 130 discards the event 201 (I 41) and adds 1 to the event discard counter 115.
Note that the value of the event discard counter 115 is reset to 0 at a predetermined cycle.
The local dispatcher 130 transmits the value of the event discard counter 115 as dispatch statistical information 206 to the dispatch rule setting unit 114 of the rule distribution unit 110 at a predetermined cycle (step S313).
The dispatch rule setting unit 114 refers to the value of the event discard counter 115 received from the local dispatcher 130, and compares it with a predetermined discard number threshold value (step S314).
Here, when the value of the event discard counter 115 exceeds the discard number threshold value, the dispatch rule setting unit 114 sets the event condition (non-aggregated event condition) of each processing rule 202 as an external event condition, and the own local system An external dispatch rule 204 (no aggregation) having 100 as the transfer destination of the event 201 that matches the external event condition is generated (step S315).
For example, the local system 100 (LS1) sets the event condition of the processing rule 202 (PR11, PR12) in FIG. 5 as an external event condition, and sets the identifier of the local system 100 (LS1) as the transfer destination in FIG. The external dispatch rule 204 (DRG12, DRG13) is regenerated.
The dispatch rule setting unit 114 sets the generated external dispatch rule 204 (no aggregation) in the external dispatcher 140 (step S316). As a result, the event 201 having the same event attribute information as the event 201 discarded by the local dispatcher 130 does not match the external event condition of the external dispatch rule 204, and is therefore discarded by the external dispatcher 140 (Step S317, S318).
For example, when the local system 100 (LS1) sets the external dispatch rule 204 (DRG12, DRG13) to the external dispatcher 140, the external dispatch rule 204 as shown in FIG. Thereby, for example, when the external dispatcher 140 (GD2) receives the event 201 of the same event attribute information (event generation type: RFID, detection information: TagID = 4) as the event 201 (I41), the event of the event 201 The attribute information does not match the external event condition of the external dispatch rule 204, and the external dispatcher 140 (GD2) discards the event 201.
The dispatch rule setting unit 114 counts the elapsed time after setting the external dispatch rule 204 (no aggregation) (step S319), and aggregates event conditions of a plurality of processing rules 202 again when a predetermined time elapses. An event condition is generated, and an external dispatch rule 204 (with aggregation) using the aggregate event condition as an external event condition is generated (step S320). The dispatch rule setting unit 114 sets the generated external dispatch rule 204 (with aggregation) in the external dispatcher 140 (step S321).
Thus, the operation of the second embodiment of the present invention is completed.
According to the second embodiment of the present invention, in an event processing system in which an external dispatcher transfers events to a local system based on an external dispatch rule in which event conditions are aggregated, useless event transfer by the external dispatcher can be reduced. . The reason for this is that when the number of events 201 that do not match any of the event conditions exceeds a predetermined threshold, the local system 100 stops the aggregation of the event conditions, and external dispatch using each event condition as an external event condition. This is because the rule 204 is reset in the external dispatcher 140.
According to the second embodiment of the present invention, in the event processing system in which an external dispatcher transfers events to a local system based on an external dispatch rule in which event conditions are aggregated, unnecessary event transfer by the external dispatcher occurs frequently. Except for the period, the number of dispatch rules can be adjusted to reduce the number of dispatch rules. The reason is that when the local system 100 resets the external dispatch rule 204 that does not aggregate event conditions in the external dispatcher 140 and then a predetermined time has elapsed, the external dispatch rule 204 with the aggregate event condition as the external event condition is set. This is for resetting to the external dispatcher 140.
The effect of the present invention is that an increase in dispatch rules accompanying an increase in processing rules can be suppressed in an event processing system.
While the present invention has been described with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.
This application claims the priority on the basis of Japanese application Japanese Patent Application No. 2009-063720 for which it applied on March 17, 2009, and takes in those the indications of all here.

The present invention can be applied to an event processing system that processes events that occur in large quantities from devices such as RFIDs and sensors. For example, the present invention can be applied to a physical distribution traceability system using an event from an RFID or a sensor, an SCEM (Supply Chain Event Management) system, and an environmental management system such as weather or disaster.

Claims

A plurality of external dispatchers for receiving events from an event source and a plurality of local systems for transmitting event processing results to an application server;
Each of the plurality of local systems is
When a processing rule including an event condition indicating an event condition to be processed is received from the application server, an aggregate event condition obtained by aggregating a plurality of the event conditions is generated, and the aggregate event condition is set as an external event condition. Generate an external dispatch rule with the event transfer destination that matches the external event condition, and set the external dispatch rule in the external dispatcher,
When the event is received from the external dispatcher, the event is processed according to the processing rule, the processing result of the event is notified to the application server that is the transmission source of the processing rule,
Each of the plurality of external dispatchers is
Event processing characterized in that, when the event is received from the event generation source, the event is transferred to a local system of a transfer destination corresponding to the external event condition that matches the event with reference to the external dispatch rule. system.
Each of the local systems, when the number of events that do not match any of the event conditions exceeds a predetermined threshold, sets each of the event conditions as the external event condition, and sets the local system as the external event condition. The event processing system according to claim 1, wherein the external dispatch rule that is a transfer destination of the matching event is generated, and the external dispatch rule is set in the external dispatcher.
Each of the local systems has the aggregate event condition as the external event condition when a predetermined time has elapsed after setting the external dispatch rule with the external event condition as the external event condition in the external dispatcher. The event processing system according to claim 2, wherein an external dispatch rule is generated and the external dispatch rule is set in the external dispatcher.
The said local system produces | generates the range of the numerical value containing the said several event conditions as said aggregate event conditions, when the said event conditions are designated by the numerical value, The Claim 1 thru | or 3 characterized by the above-mentioned. Event processing system.
Each of the plurality of local systems is
A processing rule setting unit that sets the processing rule received from the application server in any one processing server of the local system;
Generate a local dispatch rule having the processing server as a transfer destination of the event that matches the event condition included in the processing rule, set the local dispatch rule in a local dispatcher of the local system, and set the external dispatch rule to A rule distribution unit having a dispatch rule setting unit for generating and setting the external dispatch rule in the external dispatcher;
When the event is received from the external dispatcher, at least one local dispatcher that refers to the local dispatch rule and transfers the event to a transfer destination processing server corresponding to the event condition that matches the event, and the processing The event processing system according to claim 1, further comprising: at least one processing server that processes the event that matches the event condition included in the processing rule according to a rule.
Provided in a local system having at least one processing server and at least one local dispatcher;
A processing rule setting unit that sets a processing rule received from an application server in any one of the processing servers of the local system;
A local dispatch rule having the processing server as a transfer destination of an event that matches an event condition included in the processing rule is generated, the local dispatch rule is set in the local dispatcher of the local system, and a plurality of the event conditions are set. An aggregated event condition is generated, the aggregated event condition is set as an external event condition, an external dispatch rule is generated with the local system as a transfer destination of the event that matches the external event condition, and the external dispatch rule is externally generated. A rule distribution device comprising: a dispatch rule setting unit set in a dispatcher.
When the local system receives a processing rule including an event condition indicating an event condition to be processed from the application server, the local system generates an aggregate event condition in which a plurality of the event conditions are aggregated, and the aggregated event condition is As an external event condition, generate an external dispatch rule with the local system as the transfer destination of the event that matches the external event condition, and set the external dispatch rule in the external dispatcher.
When the external dispatcher receives the event from the event generation source, the external dispatcher refers to the external dispatch rule and sends the event to the local system of the transfer destination corresponding to the external event condition that matches the event. Forward,
When the local system receives the event from the external dispatcher, the local system processes the event according to the processing rule, and notifies the processing result of the event to the application server that is the transmission source of the processing rule. An event processing method characterized by:
The local system further sets each of the event conditions as the external event condition when the number of events that do not match any of the event conditions exceeds a predetermined threshold, and sets the local system as the external event condition. 8. The event processing method according to claim 7, wherein the external dispatch rule as a transfer destination of the matching event is generated, and the external dispatch rule is set in the external dispatcher.
The local system further sets the external event rule as the external event condition when a predetermined time has elapsed after setting the external dispatch rule in the external dispatcher with each of the event conditions as the external event condition. 9. The event processing method according to claim 8, wherein an external dispatch rule is generated and the external dispatch rule is set in the external dispatcher.
The said local system produces | generates the range of the numerical value containing several said event conditions as said aggregate event conditions, when the said event conditions are designated by the numerical value. Event processing method.
In setting the external dispatch rule,
The rule distribution unit of the local system sets the processing rule received from the application server to any one processing server of the local system, and the processing server matches the event condition included in the processing rule. Generate a local dispatch rule as an event transfer destination, set the local dispatch rule in the local dispatcher of the local system, generate the external dispatch rule, set the external dispatch rule in the external dispatcher,
In the event processing,
The local dispatcher refers to the local dispatch rule, transfers the event to a processing server of a transfer destination corresponding to the event condition that matches the event,
The event processing method according to claim 7, wherein the processing server processes the event that matches the event condition included in the processing rule according to the processing rule.
On the computer,
Setting the processing rules received from the application server in any one of the local systems having at least one processing server and at least one local dispatcher;
A local dispatch rule having the processing server as a transfer destination of an event that matches an event condition included in the processing rule is generated, the local dispatch rule is set in the local dispatcher of the local system, and a plurality of the event conditions are set. An aggregated event condition is generated, the aggregated event condition is set as an external event condition, an external dispatch rule is generated with the local system as a transfer destination of the event that matches the external event condition, and the external dispatch rule is externally generated. A program recording medium in which a rule distribution program for executing processing to be set in a dispatcher is recorded.