JP2005018341A - Event-driven program execution device, security system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable a description of more complicated processing while maintaining conventional easiness of event table description in an event-driven program. <P>SOLUTION: An event-driven program execution device comprises means for monitoring generation of events related to given state changes, means for sequentially accumulating generated events as an event series, means for determining by comparison whether the accumulated event series matches any event pattern or not according to an event table associating event patterns of one or more events and processing to be executed upon event series matching the event patterns, and means for, if an event series matches any event pattern, executing the processing corresponding to the event pattern. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a technique for executing an event-driven program. More particularly, the present invention relates to a technique for executing an event-driven program that executes one or more event sequences as a trigger and executes a program associated with the event sequence.
[0002]
[Prior art]
Conventionally, an event-driven program execution method includes the following method. First, there is a method in which an event that is a trigger in the event table and a process that is executed when the event occurs are described in the event table, and the program is executed according to the description of the event table. An example of the event table here is shown in FIG. In FIG. 7, for example, it is described that the process P1 is executed when the event E1 occurs. Second, describe in the state transition table the combination of the event that triggers for each system state, the process to be executed when that event occurs, and the state that transitions after the process is completed, and execute the program according to the description in the state transition table There is a way. An example of the state transition table here is shown in FIG. In FIG. 8, for example, when the event E1 occurs in the state 1, the process P1 is executed to make a transition to the state 2.
[0003]
In the conventional program execution method as described above, a simple description using a single event as a trigger is written in the event table or state transition table, and the program is executed using the described single event as a trigger. I was running.
[0004]
In addition, there are techniques disclosed in Patent Document 1 and Patent Document 2 as techniques related to event processing.
[0005]
[Patent Document 1]
JP-A-8-272727
[Patent Document 2]
JP-A-8-115107
[0006]
[Problems to be solved by the invention]
However, the conventional program execution method as described above has a problem that it is difficult to describe a complicated process because only a single event can be described as a trigger. For this reason, in an event-driven program, it has been difficult to execute complicated processing across a plurality of events.
[0007]
The present invention solves the above problems and provides a technique for enabling description of more complicated processing while maintaining the simplicity of description of a conventional event table in an event-driven program. For the purpose.
[0008]
[Means for Solving the Problems]
In order to solve the above problems, the present invention has the following configuration. That is, the present invention is an event-driven program execution device, comprising means for monitoring the occurrence of an event relating to a predetermined state change, means for sequentially accumulating generated events as an event series, and one or more events Whether or not the accumulated event series matches any of the above event patterns based on an event table that associates an event pattern with processing to be executed when an event series that matches the event pattern occurs. Means for comparing, and means for executing processing corresponding to the event pattern when there is an event series that matches the event pattern.
[0009]
Preferably, the event-driven program execution device includes means for recording the occurrence time of the event in association with the event, an elapsed time based on an occurrence time of an event sequence that matches the event pattern, and a time limit for the event pattern And means for excluding the processing corresponding to the event pattern from the execution target when the elapsed time due to the event sequence exceeds the time limit.
[0010]
Preferably, the event-driven program execution device includes means for recording the occurrence time of the event in association with the event, and means for deleting an event that has passed a predetermined time from the occurrence from the accumulated event series. It may be configured.
[0011]
Preferably, the event pattern is a combination of a plurality of events, a permutation in which a plurality of events are sequentially consecutive, a discontinuous permutation in which another unspecified event is inserted in a permutation of the plurality of events, or information indicating that a specific event has not occurred. At least one may be included.
[0012]
According to the present invention, the occurrence of an event related to a predetermined state change is monitored, the generated events are sequentially accumulated as an event series, and an event pattern composed of one or more events and an event series that matches the event pattern are generated. Based on the event table that associates the process to be executed sometimes, it is compared whether or not the accumulated event sequence matches any of the above event patterns, and there is an event sequence that matches the event pattern. In this case, processing corresponding to the event pattern is executed. Therefore, according to the present invention, an appropriate process can be executed according to a combination of a plurality of events.
[0013]
According to another aspect of the present invention, there is provided a security system including the event-driven program execution device described above, which monitors human actions as events. As a result, it is possible to execute a process related to the security system using an event pattern based on a human action as a trigger. Therefore, for example, when the present invention is applied to a home security system, it is possible to execute processing such as releasing alert using an event pattern based on an operation that only a resident knows as a trigger.
[0014]
As described above, according to the present invention, more complicated processing can be described while maintaining the simplicity of description of the event table. Therefore, in an event-driven program, it is possible to execute a complicated process triggered by an event pattern with a plurality of operations.
[0015]
Further, the present invention may be a method in which a computer, other devices, machines, etc. execute any one of the processes described above. Further, the present invention may be a program that causes a computer, other devices, machines, or the like to realize any of the functions described above. Further, the present invention may be a program in which such a program is recorded on a computer-readable recording medium.
[0016]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. The description of the present embodiment is an exemplification, and the configuration of the present invention is not limited to the following description.
[0017]
<Embodiment>
In this embodiment, it is assumed that an event-driven program is applied to a home security system.
[0018]
<Hardware configuration>
FIG. 1 is a diagram showing a hardware configuration in the system of the present embodiment. The controller 1 includes a CPU 2, a memory 3, a secondary storage 4, a communication unit 5, and an I / O (Input / Output) 6.
[0019]
The CPU 2 is connected to the memory 3, the secondary storage 4, the communication unit 5, and the I / O 6, and executes the program stored in the memory 3 to control the entire apparatus. The memory 3 stores programs and temporary data. The memory 3 is composed of, for example, a ROM or a RAM. The secondary storage 4 stores files used by the program. The secondary storage 4 is composed of, for example, a hard disk, a flash ROM, or the like. The communication unit 5 is connected to the Internet, and transmits and receives mails and the like via the Internet. The I / O 6 performs input / output with various sensors and switches connected to the controller 1.
[0020]
Various sensors and switches connected to the I / O 6 are, for example, a magnet sensor 7, an infrared sensor 8, an illuminance sensor 9, an electric lock 10, an interphone 11, a remote control receiving unit 12, a warning release button 13, and the like. The magnet sensor 7 is a sensor that detects opening and closing of windows and doors. This magnet sensor 7 detects whether or not a current flows through the opening / closing operation of the window or door by installing a magnet in the opening / closing portion of the window or door. The infrared sensor 8 is a sensor that detects the presence / absence of a person. The illuminance sensor 9 is a sensor that detects on / off of the lighting device. The illuminance sensor 9 is installed in a room equipped with lighting equipment, and detects the brightness or darkness of the room. The electric lock 10 is a lock that can be electrically unlocked / locked and that can be detected. The intercom 11 is a device that informs residents of visitors. The remote control receiver 12 is a receiver for an infrared remote controller. The alert release button 13 is a button for canceling alert for home security.
[0021]
<Software configuration>
FIG. 2 is a diagram showing a software configuration in the present embodiment. The software in the present embodiment functions by an event generation unit 20, an event queue 21, an event deletion unit 22, an event manager 23, an event handler 24, and an event table 25. Among these, the event generation unit 20 is a control program that monitors an input signal from a sensor or the like, for example.
[0022]
The event generation unit 20 monitors an event such as a sensor input, generates information related to the event, and records (registers) it in the event queue 21. That is, the event generation unit 20 inputs various sensors input to the I / O 6 shown in FIG. 1, for example, opening / closing of a window by the magnet sensor 7, detection of a person by the infrared sensor 8, notification from the illuminance sensor 9, and electric The information on the corresponding event is recorded by receiving the opening / closing of the lock 10, the operation of the intercom 11, the remote control input, and the like. Each event is identified by event ID. Hereinafter, information related to an event is also simply referred to as an event.
[0023]
The event queue 21 stores information related to events generated by the event generation unit 20. For example, the event queue 21 stores an event ID, an event occurrence time, and event detailed information for each event. Among these, the event detailed information is information related to the event, and is, for example, an event occurrence location or unique information (for example, illuminance).
[0024]
The event deletion unit 22 deletes events from the event queue 21 that have been accumulated for a certain period of time (event survival time) after being accumulated in the event queue 21.
[0025]
The event manager 23 compares the sequence of events stored in the event queue 21 with the event pattern registered in the event table 25, and if they match, the event handler 24 registered in the entry of the event table 25 is matched. Execute.
[0026]
The event handler 24 is a program that performs processing corresponding to the event with the occurrence of the event as a trigger.
[0027]
In FIG. 2, first, the event generation unit 20 registers the generated event in the event queue 21 (1). Then, the event manager 23 compares the event sequence in the event queue 21 with the event pattern in the event table 25 (2). If the compared pattern matches, the event manager 23 executes the event handler registered in the entry of the event table 25 (3).
[0028]
<Event table>
FIG. 3 is a diagram illustrating a data structure of the event table 25. The event table 25 describes a plurality of event patterns monitored by the event manager 23 and processing (event handler 24) executed using the event patterns as triggers. Hereinafter, each item of the event table 25 shown in FIG. 3 will be described in detail.
[0029]
In the event pattern, an event pattern monitored by the event manager 23 is described. Here, the event pattern to be monitored by the event manager 23 is described according to the following rules. First, in order to monitor the occurrence of a single event, the event ID of the event is described. Second, in order to monitor the occurrence of any one of a plurality of events, event IDs are described in “[]” separated by “|”. Third, in order to monitor the occurrence order of a plurality of consecutive events, event IDs are described separated by “-”. Fourth, in order to monitor the order of occurrence of a plurality of non-consecutive events, event IDs are described separated by “-”. Fifth, in order to monitor the occurrence (in no particular order) of a plurality of consecutive events, event IDs are described separated by “&”. Sixth, in order to monitor the occurrence (in no particular order) of a plurality of non-consecutive events, event IDs are described separated by “&&”. Seventh, in order to monitor the occurrence of an event, “!” Is described before the event ID.
[0030]
The scope describes a time limit from when the first event of the event pattern occurs until the end event occurs. In the present embodiment, the event handler 24 is executed when it matches the event pattern and the actual elapsed time from the start event to the end event is less than or equal to the time specified in the scope of the event table 25.
[0031]
In the process, an event handler 24 that is executed when an event that satisfies the conditions described in the event pattern field and the scope field occurs is described. In this system, a plurality of event handlers 24 may be described in one processing column. That is, a plurality of event handlers 24 can be activated corresponding to one event pattern.
[0032]
In the comparison start position, a numerical value indicating from what number of events stored in the event queue 21 the event manager 23 compares with the event pattern is described. In the event queue 21, it is indicated that the event before the comparison start position has been inspected.
[0033]
As described above, the event handler 24 (process) is executed according to the description of the event table 25 shown in FIG. For example, if events occur continuously in the order of E1 → E2 within T1 seconds, the process P1 is executed (* 1 in FIG. 3). Further, when the event E6 occurs after any of the events E3, E4, E5 within T2 seconds, the processes P2, P3, etc. are executed (* 2 in FIG. 3). If events occur in the order of E7, E8, E9 within T3 seconds (it is possible even if they are not continuous), processing P4, P5, P6, etc. are executed (* 3 in FIG. 3). . If events E10 and E11 occur continuously (in no particular order) within T4 seconds, processes P7 and P8 are executed (* 4 in FIG. 3). Further, when events E12 and E13 occur within T5 seconds (it is possible even if they are not continuous, in any order), processes P9 and P10 are executed (* 5 in FIG. 3). If event E15 does not occur within T6 seconds after event E14 occurs, processes P11 and P12 are executed (* 6 in FIG. 3).
[0034]
As described above, according to the present embodiment, it is possible to make a complicated description in the event table such that an event pattern composed of a plurality of events and a process is executed with a time restriction on the occurrence of the event pattern.
[0035]
<Specific example of event table>
Next, an example of a data structure when the event table 25 shown in FIG. 3 is applied to the home security controller will be described. FIG. 4 shows an example of the data structure of the event table 25 in the home security controller. Among these, the event pattern shown in the 1st to 4th lines in FIG. 4 is a description for releasing / starting home security alerts triggered by a natural operation performed when the resident returns home. On the other hand, the event pattern shown in the 5th to 7th lines in FIG. 4 is a description for sending an alarm mail to a resident or a security company, triggered by an unnatural operation that is not performed by a resident.
[0036]
In the example shown in FIG. 4, for example, when an event pattern occurs in which the entrance is unlocked and the TV or air conditioner is turned on, it is determined that the resident has come home and the process of releasing the alert is performed. It is executed (first line in FIG. 4). Also, if an event pattern occurs where the entrance is unlocked and the bathroom is turned on and then enters the living room, it is determined that the resident has come home, washed his hands, moved to the living room, A process of releasing the alert is executed (second line in FIG. 4). In addition, when an event pattern occurs in which the entrance is unlocked, the kitchen lighting is turned on, and the refrigerator door is opened afterwards, it is determined that the resident has returned from shopping and the warning is released. It is executed (third line in FIG. 4). Further, when an event pattern occurs in which the TV and air conditioner are turned off and the living room is unattended, it is determined that the resident has gone out and a process of starting alert is executed (4 in FIG. 4). Line). Also, if an event pattern occurs in which the door is unlocked after the intercom is sounded, it is determined that the thief has entered after confirming absence from the intercom, and processing to send an alarm mail is executed (5th line of FIG. 4). In addition, when an event pattern in which an infrared sensor is turned on (a person is detected) occurs in the living room after the window is opened, a process of transmitting an alarm mail based on a thief intrusion is executed (FIG. 4). 6th line). Also, if an event pattern occurs where there is a person in the living room but the room is dark (no lighting on event occurs), a process is performed in which it is determined that the thief is in color and an alarm email is sent. (7th line in FIG. 4).
[0037]
As described above, according to the present embodiment, it is possible to easily describe in the event table the process executed using an event pattern composed of a plurality of events as a trigger. Therefore, when such an event table is applied to the home security controller, for example, processing based on a complicated description such as releasing alerts triggered by an event pattern with a plurality of operations that only the person knows is a trigger. Can be executed.
[0038]
<Processing flow>
<Event generation processing>
Next, processing at the time of event generation will be described. FIG. 5 is a flowchart showing the event generation process. This process is executed by the event manager 23 when the event generation unit 20 generates information related to an event based on monitoring of sensor input.
[0039]
First, the event generation unit 20 adds the generated event to the end of the event queue 21 (S1). Here, it is determined whether or not the event table 25 is empty (S2). If the event table 25 is empty, the process is terminated as it is. That is, if nothing is set in the event table 25, no processing is performed. On the other hand, if the event table 25 is not empty, the inspection target entry is set to the top entry of the event table 25 (S3).
[0040]
Subsequently, the event manager 23 compares the event pattern of the inspection target entry set in the event table 25 with the event string stored in the event queue 21 (S4). Here, the comparison is performed from the comparison start position set in the event table 25.
[0041]
Subsequently, the event manager 23 determines whether a pattern that matches the event pattern exists in the event queue 21 (S5). That is, it is determined whether or not the event pattern of the entry to be inspected set in the event table 25 exists in the event queue 21. Here, if there is a matching event pattern, the event manager 23 determines the elapsed time from the occurrence of the first event to the occurrence of the end event and the time registered in the scope (hereinafter referred to as the scope time). (Noted) is compared (S6).
[0042]
Subsequently, the event manager 23 determines whether or not the elapsed time from the occurrence of the first event to the occurrence of the end event in the portion where the patterns match is equal to or less than the scope time (S7). If the elapsed time is equal to or less than the scope time, the event manager 23 executes the event handler 24 (S8). That is, the event handler 24 is executed when the elapsed time has not reached the scope time set in the event table 25.
[0043]
After executing the event handler 24, the event manager 23 updates the comparison start position to the head of the unexamined portion of the event queue 21 (S9). In this way, the comparison between the event pattern and the event queue 21 is repeated until there is no unexamined portion in the event queue 21.
[0044]
If it is determined in S7 that the elapsed time from the start event occurrence to the end event occurrence of the portion with the matching pattern is greater than the scope time, S9 is executed as it is. That is, assuming that the conditions in the scope column described in the event table 25 are not satisfied, the event handler 24 is not executed and the inspection target is moved to the uninspected portion of the event queue 21.
[0045]
If it is determined in S5 that no matching event pattern exists, the event manager 23 determines whether there is an unchecked entry in the event table 25 (S10). If there is an uninspected entry, the event manager 23 sets the inspection target entry as the next entry in the event table 25 (S11). On the other hand, when there is no uninspected entry, the event manager 23 ends the process as it is.
[0046]
As described above, when the condition (event pattern and scope time) registered in the event table 25 is satisfied, the event handler 24 is executed, and the event is repeated until there are no unexamined entries in the event table 25. Comparison with the queue 21 is performed.
[0047]
According to this embodiment, an event pattern and a process executed using the event pattern as a trigger are described in the event table 25 as a pair, and the event sequence stored in the event queue 21 and the event table 25 are described. It is possible to execute the necessary processing when the pattern matches with the event pattern. For this reason, when this system is applied to a home security system, for example, it is possible to execute a process of canceling the alert using an event pattern with a plurality of operations that only the person knows as a trigger.
[0048]
<Event deletion processing>
Next, processing for deleting an event from the event queue 21 will be described. FIG. 6 is a flowchart showing processing for deleting an event from the event queue 21. This process is periodically executed by the event deletion unit 22 and deletes from the event queue 21 an event for which a time equal to or longer than the event lifetime defined from the event occurrence to the present has elapsed. Here, it is assumed that the event deletion unit 22 executes the process every second and defines the event survival time as 10 minutes.
[0049]
First, the event deletion unit 22 determines whether or not the event queue 21 is empty (S21). That is, the event deletion unit 22 determines whether the generated event is accumulated in the event queue 21. Here, if the event queue 21 is empty, the processing is terminated as it is. On the other hand, if the event queue 21 is not empty, the inspection target event is set as the first event in the event queue 21 (S22).
[0050]
Subsequently, the event deletion unit 22 determines whether or not the elapsed time after the occurrence of the inspection target event is equal to or longer than the event survival time (S23). If the elapsed time is not the same as or longer than the event survival time, the event deletion unit 22 ends the process as it is. On the other hand, when the elapsed time after the occurrence of the inspection target event is equal to or longer than the event survival time, the event deletion unit 22 deletes the inspection target event from the event queue 21 (S24). After the event deletion, the event deletion unit 22 subtracts 1 from the value in the comparison start position column of the event table 25 (S25).
[0051]
Subsequently, the event deletion unit 22 determines whether or not there is an uninspected event in the event queue 21 (S26). If it is determined that there is an uninspected event in the event queue 21, the event deletion unit 22 sets the inspection target event as the next event in the event queue 21 (S27). Similarly thereafter, the elapsed time after the occurrence of the inspection target event is compared with the event survival time, and the process of deleting the event in the event queue 21 is executed. On the other hand, if it is determined that there is no uninspected event in the event queue 21, the processing is terminated as it is.
[0052]
In this way, according to the present embodiment, the events accumulated in the event queue 21 can be periodically inspected to determine and delete events that have become obsolete based on a predetermined event survival time.
[0053]
As described above, according to the present system, it is possible to easily describe in the event table a process executed using an event pattern composed of a plurality of events as a trigger. For this reason, appropriate processing can be executed in accordance with a combination of a plurality of events.
[0054]
In addition, for example, when this system is applied to a home security system, according to the conventional event-driven program execution method, only a simple description such as “when the warning release button is pressed, the warning release processing is performed” can be performed. However, if the door lock is unlocked and the TV or air conditioner is turned on, the alarm will be released or if the intercom is turned on and the door lock is unlocked, It is possible to easily describe a complicated operation such as “send alarm mail”. In this way, by applying this system to a home security system, a simple and inexpensive sensor is combined to detect daily natural actions of the resident (which differs from resident to resident) and release the alert. Or, conversely, it is possible to easily perform a process of detecting an unnatural operation (which varies depending on the resident and depending on the transition of the criminal technique) as an abnormality and issuing a warning to the user, which is not performed by a resident. Furthermore, the warning cancellation by an operation that only the resident knows has the effect that it can not be easily released by an intruder because it works as a password. As described above, by applying this system to a home security system, the above-described specific effects can be exhibited.
[0055]
【The invention's effect】
According to the present invention, it is possible to easily describe in the event table a process executed using an event pattern composed of a plurality of events as a trigger. Therefore, by using the event table of the present invention, it is possible to execute complicated processing across a plurality of events.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating a hardware configuration in a system according to an embodiment.
FIG. 2 is a diagram showing a software configuration in the present embodiment.
3 is a diagram showing a data structure of an event table 25. FIG.
FIG. 4 shows an example of the data structure of an event table 25 in the home security controller.
FIG. 5 is a flowchart showing an event generation process.
FIG. 6 is a flowchart showing processing for deleting an event from the event queue 21;
FIG. 7 shows an example of a conventional event table.
FIG. 8 shows an example of a conventional state transition table.
[Explanation of symbols]
1 Controller
2 CPU
3 memory
4 Secondary memory
5 Communication Department
6 I / O
7 Magnet sensor
8 Infrared sensor
9 Illuminance sensor
10 Electric lock
11 Intercom
12 Remote control receiver
13 Alert release button
20 Event generator
21 Event queue
22 Event deletion part
23 Event Manager
24 Event Handler
25 Event table

Claims (10)

Means for monitoring the occurrence of an event relating to a predetermined state change;
Means for sequentially accumulating generated events as an event sequence;
Based on an event table in which an event pattern composed of one or more events and a process to be executed when an event sequence that matches the event pattern is generated, the accumulated event sequence becomes one of the event patterns. Means for comparing whether or not they match,
Means for executing processing corresponding to the event pattern when there is an event series that matches the event pattern;
An event-driven program execution device comprising: Means for recording the event occurrence time in association with the event;
Means for comparing an elapsed time based on an occurrence time of an event sequence that matches the event pattern and a time limit for the event pattern;
Means for excluding the processing corresponding to the event pattern from the execution target when the elapsed time by the event series exceeds the time limit;
An event-driven program execution device according to claim 1. Means for recording the event occurrence time in association with the event;
Means for deleting an event that has passed a predetermined time from occurrence from the accumulated event series;
An event-driven program execution device according to claim 1. The event pattern is at least one of a combination of a plurality of events, a permutation in which a plurality of events are successively arranged, a non-consecutive permutation in which another unspecified event is inserted in the permutation of the plurality of events, or information indicating that a specific event has not occurred. The event-driven program execution device according to claim 1, comprising: A security system comprising the event-driven program execution device according to any one of claims 1 to 4, wherein a human operation is monitored as an event. On the computer,
Monitoring the occurrence of an event relating to a predetermined state change;
Sequentially accumulating the events that occurred as an event sequence;
Based on an event table in which an event pattern composed of one or more events and a process to be executed when an event sequence that matches the event pattern is generated, the accumulated event sequence becomes one of the event patterns. Comparing whether or not they match,
If there is an event series that matches the event pattern, executing a process corresponding to the event pattern;
An event-driven program that can be executed by a computer. On the computer,
Recording the event occurrence time in association with the event;
Comparing an elapsed time based on an occurrence time of an event sequence that matches the event pattern and a time limit for the event pattern;
When the elapsed time due to the event series exceeds the time limit, removing the process corresponding to the event pattern from the execution target;
7. The computer-executable event-driven program according to claim 6, wherein the program is executed. On the computer,
Recording the event occurrence time in association with the event;
Deleting an event that has passed a predetermined time from occurrence from the accumulated event series;
7. The computer-executable event-driven program according to claim 6, wherein the program is executed. The computer includes at least one of a combination of a plurality of events, a permutation in which the plurality of events are sequentially consecutive, a non-continuous permutation in which other unspecified events are inserted in the permutation of the plurality of events, or information indicating that a specific event has not occurred. The computer-executable event-driven program according to any one of claims 6 to 8, wherein a process related to an event pattern is executed. A program for a security system, which causes a computer to execute the event-driven program according to any one of claims 6 to 9 and monitors a human operation as an event.

Images