JP6344009B2 - Information processing apparatus, program, and information processing method - Google Patents

Description

  The present invention relates to an information processing apparatus, a program, and an information processing method.

  There has been proposed an information processing apparatus that acquires event information (hereinafter referred to as an event as appropriate) having attributes such as time, action history, and position, and executes various processes on the acquired event. Such an information processing apparatus extracts, for example, an event that satisfies a predetermined condition related to the attribute from a plurality of acquired events. Then, the information processing apparatus outputs that the above-described condition is satisfied.

JP 2010-282577 JP 2012-242183 A JP 2012-3494 JP 2012-242859 A International Publication No. 2008/146858

  When such an information processing apparatus acquires a large number of events and executes an event extraction process that satisfies a plurality of conditions from the acquired large number of events, the processing speed decreases. As a result, it becomes difficult for such an information processing apparatus to perform the above-described output quickly.

  An object of one aspect of the present invention is to quickly output that an acquired event is an event that satisfies a predetermined condition.

  In one aspect, event information having a plurality of attributes is acquired, and when the acquired event information satisfies an event condition defined in correspondence with the first attribute, the acquired event information is stored in a memory. An event related to the first attribute, the second attribute time, and at least two event conditions each time the event information is stored. It is an information processing apparatus that determines whether there is storage event information stored in the memory that satisfies an inter-event condition, and outputs a determination result if there is storage event information that satisfies the inter-event condition.

  According to one aspect, it is possible to quickly output that the acquired event is an event that satisfies a predetermined condition.

1 is an example of a block diagram illustrating a hardware configuration of an information processing device 1 according to a first embodiment. FIG. 2 is an example of a block diagram illustrating a software configuration of the information processing apparatus 1 in FIG. It is an example of the figure which shows an event typically. It is a figure explaining the tracking detection which the information processing apparatus 1 of this Embodiment performs. It is a figure explaining the event condition and the condition between events. It is a figure explaining the registration by the registration of an event and the edge of a different event. FIG. 6 is a first flowchart for explaining real-time processing of events described in the first embodiment. FIG. 6 is a second flowchart illustrating real-time processing of an event described in the first embodiment. FIG. 3 is a first diagram illustrating a specific example in the first embodiment. FIG. 6 is a second diagram for explaining a specific example in the first embodiment. FIG. 6 is a third diagram for explaining a specific example in the first embodiment. FIG. 10 is a fourth diagram for explaining a specific example in the first embodiment. FIG. 10 is a fifth diagram for explaining a specific example in the first embodiment. FIG. 10 is a sixth diagram for explaining a specific example in the first embodiment. FIG. 10 is a seventh diagram for explaining a specific example in the first embodiment. FIG. 10 is an eighth diagram for explaining a specific example in the first embodiment. FIG. 10 is a ninth diagram illustrating a specific example in the first embodiment. FIG. 10 is a tenth diagram for explaining a specific example in the first embodiment. FIG. 11 is an eleventh view for explaining a specific example in the first embodiment. FIG. 16 is a twelfth diagram illustrating a specific example in the first embodiment. FIG. 13 is a thirteenth diagram illustrating a specific example in the first embodiment. FIG. 14 is a fourteenth diagram for explaining a specific example in the first embodiment. FIG. 15 is a fifteenth diagram illustrating a specific example in the first embodiment. FIG. 16 is a sixteenth diagram illustrating a specific example in the first embodiment. FIG. 17 is a seventeenth diagram for explaining a specific example in the first embodiment. FIG. 18 is an eighteenth diagram illustrating a specific example in the first embodiment. FIG. 19 is a nineteenth diagram illustrating a specific example in the first embodiment. FIG. 20 is a twentieth diagram illustrating a specific example in the first embodiment. FIG. 21 is a twenty-first diagram illustrating a specific example in the first embodiment. FIG. 22 is a 22nd diagram for explaining a specific example in the first embodiment. FIG. 23 is a 23rd diagram for explaining a specific example in the first embodiment. FIG. 24 is a 24th diagram illustrating a specific example in the first embodiment. FIG. 25 is a 25th diagram for explaining a specific example in the first embodiment. FIG. 26 is a 26th diagram for explaining a specific example in the first embodiment. FIG. 27 is a 27th view for explaining a specific example in the first embodiment. FIG. 28 is a 28th view for explaining a specific example in the first embodiment. FIG. 29 is a 29th diagram for explaining a specific example in the first embodiment. FIG. 30 is a thirtieth diagram illustrating a specific example in the first embodiment. FIG. 32 is a 31st diagram explaining a specific example according to the first embodiment. FIG. 32 is a 32nd diagram for explaining a specific example in the first embodiment. FIG. 33 is a 33rd diagram describing a specific example in the first embodiment. FIG. 34 is a thirty-fourth diagram illustrating a specific example in the first embodiment. FIG. 35 is a 35th view for explaining a specific example in the first embodiment. FIG. 36 is a 36th diagram for explaining a specific example in the first embodiment. FIG. 37 is a 37th diagram for describing a specific example in the first embodiment. FIG. 38 is a 38th diagram for explaining a specific example in the first embodiment. FIG. 39 is a 39th view for explaining a specific example in the first embodiment. FIG. 42 is a fortieth diagram illustrating a specific example in the first embodiment. FIG. 41 is a forty-first diagram illustrating a specific example in the first embodiment. FIG. 42 is a forty-second diagram illustrating a specific example in the first embodiment. FIG. 43 is a 43rd diagram illustrating a specific example in the first embodiment. FIG. 44 is a forty-fourth diagram illustrating a specific example in the first embodiment. FIG. 45 is a forty-fifth diagram illustrating a specific example in the first embodiment. FIG. 46 is a forty-sixth embodiment explaining a specific example in the first embodiment. FIG. 47 is a 47th diagram for explaining a specific example in the first embodiment. FIG. 48 is a forty-eighth diagram illustrating a specific example in the first embodiment. FIG. 49 is a 49th diagram explaining a specific example in the first embodiment. FIG. 50 is a fifty-fifth diagram illustrating a specific example in the first embodiment. 6 is an example of a block diagram illustrating a hardware configuration of an information processing device 2 according to a second embodiment. FIG. FIG. 60 is an example of a block diagram illustrating a software configuration of information processing apparatus 2 in FIG. 59. It is a figure explaining the registration of an event, the connection by the edge of a different event, and the setting of a flag. FIG. 10 is a first flowchart for explaining real-time output of events described in the second embodiment. FIG. 10 is a second flowchart for explaining real-time output of events described in the second embodiment. FIG. 10 is a third flowchart illustrating real-time output of events described in the second embodiment. FIG. 10 is a fourth flowchart illustrating real-time output of events described in the second embodiment. FIG. 10 is a fifth flowchart illustrating real-time output of events described in the second embodiment. FIG. 10 is a first diagram for explaining a specific example in the second embodiment. FIG. 10 is a second diagram for explaining a specific example in the second embodiment. FIG. 11 is a third diagram for explaining a specific example in the second embodiment. FIG. 10 is a fourth diagram for explaining a specific example in the second embodiment. FIG. 10 is a fifth diagram for explaining a specific example in the second embodiment. FIG. 10 is a sixth diagram illustrating a specific example in the second embodiment. FIG. 10 is a seventh diagram for explaining a specific example in the second embodiment. FIG. 10 is an eighth diagram for explaining a specific example in the second embodiment. FIG. 10 is a ninth diagram describing a specific example in the second embodiment. FIG. 10 is a tenth diagram for explaining a specific example in the second embodiment. FIG. 11 is an eleventh view for explaining a specific example in the second embodiment. FIG. 16 is a twelfth diagram illustrating a specific example in the second embodiment. FIG. 16 is a thirteenth diagram illustrating a specific example in the second embodiment. FIG. 14 is a fourteenth diagram for explaining a specific example in the second embodiment. FIG. 15 is a fifteenth diagram illustrating a specific example in the second embodiment. FIG. 16 is a sixteenth diagram for explaining a specific example in the second embodiment. FIG. 17 is a seventeenth diagram illustrating a specific example in the second embodiment. FIG. 18 is an eighteenth diagram illustrating a specific example in the second embodiment. FIG. 19 is a nineteenth diagram illustrating a specific example in the second embodiment. FIG. 20 is a twentieth diagram illustrating a specific example in the second embodiment. FIG. 21 is a 21st diagram for explaining a specific example in the second embodiment. FIG. 22 is a 22nd diagram for explaining a specific example in the second embodiment. FIG. 23 is a 23rd diagram for describing a specific example in the second embodiment. FIG. 24 is a 24th diagram illustrating a specific example in the second embodiment. FIG. 25 is a 25th diagram for explaining a specific example in the second embodiment. FIG. 26 is a 26th diagram for explaining a specific example in the second embodiment. FIG. 27 is a 27th diagram for explaining a specific example in the second embodiment. FIG. 28 is a 28th diagram for explaining a specific example in the second embodiment. FIG. 29 is a 29th diagram for explaining a specific example in the second embodiment. FIG. 30 is a 30th diagram for explaining a specific example in the second embodiment. FIG. 32 is a thirty-first diagram illustrating a specific example in the second embodiment. FIG. 32 is a thirty-second diagram for explaining a specific example in the second embodiment. It is another figure which shows an event typically. It is another figure explaining the event condition and the condition between events.

[First Embodiment]
(Hardware block diagram of information processing device)
FIG. 1 is an example of a block diagram illustrating a hardware configuration of the information processing apparatus 1 according to the first embodiment. In the description of the following drawings, the same reference numerals are assigned to the same blocks and the same configuration, and the description once made is omitted as appropriate.

  The information processing apparatus 1 includes a CPU (processing unit) 101, a RAM (memory) 102, a storage device 103, an external storage medium reading device 104, and a network interface 105 connected to the bus B. CPU is an abbreviation for “Central Processing Unit”. RAM is an abbreviation for “Random Access Memory”. Hereinafter, the CPU (processing unit) 101 is referred to as CPU 101, the RAM (memory) 102 as RAM 102, and the storage device 103 as storage 103, as appropriate.

  The CPU 101 is a central processing unit that controls the entire information processing apparatus 1. The RAM 102 temporarily stores processing executed by the CPU 101, data generated (calculated) at each step executed by the real-time processing software SF1, and the like. Further, the RAM 102 stores events described in FIG. The RAM 102 is a semiconductor memory such as a DRAM (Dynamic Random Access Memory). The contents shown in the RAM 102 will be described later.

  The storage 103 is a mass storage device such as a hard disk drive (HDD) or a solid state drive (SSD). The storage 103 stores an execution file of the real-time processing software SF1. When the information processing apparatus 1 starts up, the CPU 101 reads the execution file of the real-time processing software SF1 from the storage 103, expands it to the RAM 102, and executes in real time whether the event satisfies a predetermined condition (also called real-time processing). ) Note that this execution file may be stored in the external storage medium MD.

  The external storage medium reading device 104 is a device that reads data stored in the external storage medium MD. The external storage medium MD is, for example, a portable storage medium such as a CD-ROM (Compact Disc Read Only Memory) or a DVD (Digital Versatile Disc), or a portable nonvolatile memory such as a USB memory.

  The network interface 105 has, for example, a NIC (Network Interface Card) and provides an interface function for the network N.

(Software block diagram of information processing device)
FIG. 2 is an example of a block diagram illustrating the software configuration of the information processing apparatus 1 in FIG.

  The real-time processing software SF1 includes a condition reading unit 11, a condition conversion unit 12, a data reading unit 13, a condition determination unit 14, a graph management unit 15, a node deletion unit 16, an output management unit 17, and an output unit 18.

  The condition reading unit 11 reads information having an event condition, an inter-event condition, a timeout, and an unconditional timeout preset in the storage 103 by an administrator or the like. This information will be described with reference to FIG. The condition conversion unit 12 converts the event condition, the inter-event condition, the timeout, and the unconditional timeout so that the condition determination unit 14 can read the event condition, the inter-event condition, the timeout, and the unconditional timeout, and stores them in the RAM 102.

  The data reading unit 13 receives (also called acquisition) one event from an external server, and temporarily stores the received event in a buffer memory (not shown). This buffer memory is a memory for temporarily storing events, and may be provided in a partial area (not shown) in the RAM 102. The data reading unit 13 inputs this one event to the condition determining unit 14.

  The condition determination unit 14 determines whether the input event satisfies the above-described condition. When the input event satisfies the event condition (conditions a to d described in FIG. 5), the condition determination unit 14 determines an area (for example, a condition a candidate 102a for the condition a) corresponding to the event condition to be satisfied. , Condition b candidate 102b, condition c candidate 102c, and condition d candidate 102d).

  When the event satisfies the event condition or when the event satisfies the inter-event condition, the graph management unit 15 stores the fact in the RAM 102.

  The node deletion unit 16 deletes the event stored in the RAM 102 by the condition determination unit 14. The output management unit 17 manages overall event output processing. The output unit 18 converts the event data to be output into a predetermined output format (for example, HTML format), and outputs it to an external display device (not shown). The contents necessary before describing a specific example of the present embodiment will be described with reference to FIGS.

(Event)
FIG. 3 is an example of a diagram schematically showing an event. An event is an example of event information (also referred to as an event record) having a plurality of attributes. The event indicates, for example, position information on a certain target earth at a certain time. Here, a certain subject is a human being. An event has an identifier (ID: identifier) that uniquely identifies a target and position information of the target on the earth. This position information is, for example, latitude and longitude.

  The event further has a time when this position information is measured, that is, the certain time described above. This position information is an example of the first attribute. Time is an example of the second attribute. The identifier that uniquely identifies the target is an example of a third attribute.

  The columns in the event table shown in FIG. 3 indicate the event time, event ID, event area, and space in order from the left of the drawing. Area and space indicate position information. For example, the event indicated by E1 in FIG. 3 represents one event. The events E1 to E5 will be described with reference to FIG.

  The area is an area indicated by 1 minute unit of hour in latitude and 1 minute unit of hour in longitude. In FIG. 3, the hour and minute of the latitude of the area and the hour and minute of the longitude are shown in the (Y1 ° Y2 ', X1 ° X2') format. "Y1 ° Y2 '" indicates the hour and minute of latitude, and "X1 ° X2'" indicates the hour and minute of longitude. A specific example of the area will be described with reference to FIG.

  The space is the part indicated by the seconds of latitude and seconds of longitude. In FIG. 3, the latitude second and longitude second of the area are shown in (Y3 ″, X3 ″) format. Y3 "indicates the latitude second, and X3" indicates the longitude second.

  For example, an event having a time T, an identifier ID0, an area (Y1 ° Y2 ', X1 ° X2'), and a space (Y3 ″, X3 ″) is a person identified by the identifier ID0 at time T. , Position (Y1 ° Y2'Y3 ", X1 ° X2'X3").

  As indicated by the arrows in FIG. 3, the data reading unit 13 sequentially acquires events from the external server in order from the top of the drawing.

(Tracking detection)
FIG. 4 is a diagram illustrating tracking detection performed by the information processing apparatus 1 according to the present embodiment. Hereinafter, an area indicated by (35 ° 35 ′, 139 ° 38 ′) to (35 ° 36 ′, 139 ° 39 ′) (see dotted hatching) is referred to as area a or area b.

  Further, an area indicated by (35 ° 34 ′, 139 ° 37 ′) to (35 ° 35 ′, 139 ° 38 ′) (see hatched hatching) is referred to as area c or area d. However, in the following description, it is assumed that (35 ° 35 ′, 139 ° 38 ′) is not included in area c or area d.

  Here, human M1 moves from area a (in other words, area b) to area c (in other words, area d), and similarly, human M2 moves from area a (in other words, area b) to area c. Assume a situation of moving to c (in other words, area d). Then, it is assumed that the human M2 is a human who tracks the movement of the human M1. Human M2 is a so-called stalker.

  Humans M1 and M2 have communication terminals that transmit their position information to an external server at a predetermined timing. This communication terminal has a so-called GPS (Global Positioning System) function, measures the current position, and sends an event including the measured position information, measurement time, and terminal identifier (ID) identifying the terminal itself to an external server. Send to. The measured position information is an area and a space in the example of FIG. 3, the measurement time is time in the example of FIG. 3, and the terminal identifier is ID in the example of FIG. The communication terminal is, for example, a mobile phone or a smartphone.

  The external server receives the event and transmits it to the information processing apparatus 1. Based on the received event, the information processing apparatus 1 extracts an event satisfying a predetermined condition in real time and outputs the extracted event. In the example of FIG. 4, the information processing apparatus 1 detects in real time a person who has moved from an area a (in other words, area b) to an area c (in other words, area d) and a person who tracks this person. To do. Hereinafter, this detection is referred to as tracking detection as appropriate. In the tracking detection, the predetermined condition has, for example, two conditions as a category, that is, an event condition and an inter-event condition.

(Event condition, inter-event condition)
FIG. 5 is a diagram for explaining event conditions and inter-event conditions. This event condition is an example of an event condition defined corresponding to the first attribute (for example, position information) described in FIG. Hereinafter, event conditions are referred to as conditions as appropriate. FIG. 5 (A) is a diagram schematically showing conditions a to d as ellipses. FIG. 5 (B) is a diagram showing the time difference in the inter-event condition.

  The condition a is a condition indicating that the event area satisfies the area a. Condition b is a condition indicating that the area of the event satisfies area b (in other words, area a). The condition c is a condition indicating that the event area satisfies the area c. The condition d is a condition indicating that the event area satisfies the area d.

  As described above, the event condition includes the first condition (for example, condition a) and the second condition (for example, condition b) defined in correspondence with the first attribute (for example, position information). It has a third condition (for example, condition c) and a fourth condition (for example, condition d).

  The inter-event condition is an example of an inter-event condition related to a first attribute (for example, position information), a second attribute, time, and at least two event conditions. In the examples of Figs. 4 and 5, there are four inter-event conditions.

  The first inter-event condition is, for example, an inter-event condition a-b indicating a relationship with the condition a and the condition b. In the inter-event condition a-b, the area (area a or area b) and space included in the first and second events are the same, and the IDs of the first and second events are different. Furthermore, in the inter-event condition a-b, the time difference between the time of the first event and the time of the second event subsequent to the first event is within 40 seconds. This time difference is also called a timeout (in other words, the maximum time of the condition between events). In FIG. 5 (A), the inter-event condition a-b is schematically shown by a solid line arrow. In FIG. 5B, the timeout in the inter-event condition a-b is indicated by “a-b: 40 seconds”.

  The inter-event condition a-b is an example of a first inter-event condition related to the first time (for example, 40 seconds), the third attribute (for example, ID), and the first and second event conditions.

  The second inter-event condition is, for example, an inter-event condition a-c indicating a relationship with the condition a and the condition c. The inter-event condition ac has different areas and spaces in the first and third events, the same IDs in the first and third events, the time of the first event, and the first event The time difference (time-out) from the time of the third event following is within 20 minutes. The area included in the first event is area a. The area included in the third event is area c.

  In FIG. 5 (A), the inter-event condition a-c is schematically shown by a dashed-dotted arrow. In FIG. 5B, the timeout in the inter-event condition a-c is indicated by “a-c: 20 minutes”.

  The inter-event condition ac includes a second time (for example, 20 minutes) longer than the first time (for example, 40 seconds), a third attribute (for example, ID), and the first and third event conditions. It is an example of a related second inter-event condition.

  The third inter-event condition is, for example, an inter-event condition c-d indicating a relationship with the conditions c and d. In the inter-event condition c-d, the area (area c or area d) and space included in the third and fourth events are the same, and the IDs of the third and fourth events are different. Furthermore, the inter-event condition c-d is a condition (condition c, condition d) in the inter-event condition c-d that is not temporally related, and there is no temporal relationship between these conditions. Specifically, the time difference (timeout) between the time of the third event and the time of the fourth event preceding or following the third event is within 40 seconds. Note that the inter-event condition c-d may be a condition that is temporally related, like the inter-event condition a-b. For example, the condition c may be a condition that precedes the condition d in terms of time.

  In FIG. 5 (A), the inter-event condition c-d is schematically shown by a dotted line without an arrow. In FIG. 5B, the timeout in the inter-event condition c-d is indicated by “cd: 40 seconds”.

  The inter-event condition c-d is an example of a third inter-event condition related to the third time (for example, 40 seconds), the third attribute (for example, ID), and the third and fourth event conditions.

  The fourth inter-event condition is, for example, an inter-event condition b-d indicating a relationship with the condition b and the condition d. In the inter-event condition bd, the area and space included in the second and fourth events are different, the IDs included in the second and fourth events are the same, the time of the second event, and the second event The time difference (timeout) from the time of the fourth event that follows is within 20 minutes. Note that the area included in the second event is, for example, area b. The area included in the fourth event is, for example, area d.

  In FIG. 5 (A), the inter-event condition b-d is schematically shown by a dashed arrow. In FIG. 5B, the timeout in the inter-event condition b-d is indicated by “b-d: 20 minutes”.

  The inter-event condition bd includes a fourth time (for example, 20 minutes) longer than the third time (for example, 40 seconds), a third attribute (for example, ID), and the second and fourth event conditions. It is an example of a related fourth inter-event condition.

  Next, conditions for which unconditional timeout is predetermined (set) are condition c and condition d. In FIG. 5 (B), the unconditional timeout for condition c and condition d is indicated by “c: 40 seconds” and “d: 40 seconds”. A specific example of the unconditional timeout will be described in step S3 in the flowchart of FIG.

  The unconditional timeout is determined in accordance with the fifth event condition (for example, condition d) corresponding to the fourth event condition (for example, condition d). This is an example of the sixth time (for example, 40 seconds).

(Event registration, inter-event condition)
FIG. 6 is a diagram for explaining event registration and connection by different event sides. The data reading unit 13 acquires the event and inputs it to the condition determining unit 14. The condition determination unit 14 stores the event in a predetermined area of the RAM 102 when the event satisfies a condition defined in accordance with the first attribute (for example, area). This event storage is synonymous with event registration.

  Specifically, the condition determination unit 14 determines which condition (condition a to condition d) the input event input from the data reading unit 13 satisfies. When the input event satisfies any of the conditions, the condition determination unit 14 newly registers (stores) in the RAM 102 as a candidate for the satisfied condition.

  Then, in event registration, the condition determination unit 14 stores the contents of the event in the RAM 102 together with the registered event. This content includes an individual ID for uniquely identifying a registered event in the RAM 102, a condition satisfied by this event, an inter-event condition satisfied by this event, and other data.

  For example, the event E1 in FIG. 3 is input from the data reading unit 13 to the condition determining unit 14. Since the event E1 includes the areas a and b ((35 ° 35 ′, 139 ° 38 ′) in the example of FIG. 4), the conditions a and b are satisfied among the conditions a to d. The condition determination unit 14 newly registers the input event as a candidate for the satisfied conditions a and b.

  In FIG. 6, the condition determination unit 14 registers (stores) the event E1 in the candidate a of the RAM 102a. Symbol E11 indicates the time of the registered event. Symbol E12 indicates the ID of the registered event. A symbol E13 indicates a space of the registered event. Although the event E1 satisfies the condition b, in order to simplify the illustration, the illustration of the state in which the event E1 is registered in the b candidate 102b of the RAM 102 is omitted.

  Then, the condition determination unit 14 stores the individual ID “0x1” of the event E1 and the event condition “condition a” as shown in the content EI1.

  Further, when the events E2 and E3 including the areas a and b are sequentially input, the condition determination unit 14 newly registers the input events E2 and E3 as candidates for the satisfied conditions a and b. To do. In FIG. 6, the condition determination unit 14 registers events E2 and E3 in the b candidate 102b of the RAM 102. Although the events E2 and E3 satisfy the condition a, the illustration of the state in which the events E2 and E3 are registered in the a candidate 102a of the RAM 102 is omitted to simplify the illustration.

  Then, the condition determination unit 14 stores the individual ID “0x2” of the event E2 and the event condition “condition b” as shown in the content EI2. Further, the condition determination unit 14 stores the individual ID “0x3” of the event E3 and the event condition “condition b” as shown in the content EI3.

  Each time an event is stored in the RAM 102, the condition determination unit 14 determines whether there is a storage event stored in the RAM 102 that satisfies an inter-event condition (for example, an inter-event condition). The condition determination unit 14 makes this determination every time an event is stored in the RAM 102, thereby enabling the above-described determination in real time, that is, at the same time (immediately) as the event is acquired.

  For example, event E1 and events E2 and E3 satisfy the inter-event condition a-b. This is because the areas and spaces of events E1, E2, and E3 are the same, and the time difference between the time of event E1 and the time of events E2 and E3 following event E1 is within 40 seconds. This is because the ID of event E1 is different from the IDs of events E2 and E3.

  The condition determination unit 14 stores in the RAM 102 that the event E1 and the events E2 and E3 satisfy the inter-event condition a-b. FIG. 6 shows that event E1 and events E2 and E3 satisfy the inter-event condition a-b by connecting event E1 and events E2 and E3 by the side indicated by the solid line L1.

  For event E1, the condition determination unit 14 indicates that the event E1 and the events E2 and E3 satisfy the inter-event condition ab as indicated by the event E1 content EI1 and the event destination ID and edge code L1. And stored in the RAM 102. Content In EI1, the inter-event condition is indicated by "0x2 (L1), 0x3 (L1)". In addition, the condition determination unit 14 for the event E2, the event ID and edge code L1 of the connection destination event so that the event E1 and the event E2 satisfy the inter-event condition ab is indicated in the content EI2 of the event E2. And stored in the RAM 102. Content In EI2, the event condition is indicated by "0x1 (L1)". In addition, the condition determination unit 14 determines, for the event E3, the event ID and edge code L1 of the connection destination event so that the event E1 and the event E3 satisfy the inter-event condition ab are indicated in the content E1 of the event E3. And stored in the RAM 102. Content In EI3, the event condition is indicated by "0x1 (L1)".

  Furthermore, when the event E4 including the areas c and d ((35 ° 34 ′, 139 ° 37 ′) in the example of FIG. 4) is input, the condition determination unit 14 receives the input event E4. Are newly registered as candidates for the satisfied conditions c and d. In FIG. 6, the condition determination unit 14 registers the event E4 in the c candidate 102c of the RAM 102. Although the event E4 satisfies the condition d, for simplicity of illustration, the state where the event E4 is registered in the d candidate 102d of the RAM 102 is not shown.

  Then, the condition determination unit 14 stores the event ID “0x4” and the event condition “condition c” as shown in the content EI4.

  Here, the event E1 and the event E4 satisfy the inter-event condition a-c. This is because the areas and spaces included in events E1 and E4 are different, the IDs included in events E1 and E4 are the same, and the time difference between the time of event E1 and the time of event E4 following event E1 is 20 minutes. Because it is within.

  The condition determination unit 14 stores in the RAM 102 that the event E1 and the event E4 satisfy the inter-event condition a-c. In FIG. 6, the fact that the event E1 and the event E4 satisfy the inter-event condition a-c is shown by connecting the event E1 and the event E4 with the side indicated by the alternate long and short dash line L2.

  The condition determination unit 14 uses the individual ID of the connection destination event and the side code L2 to indicate that the event E1 and the event E4 satisfy the inter-event condition ac for the event E1, as shown in the content E1 of the event E1. Store in RAM102. Content In EI1, the event condition is indicated by "0x4 (L2)".

  The condition determination unit 14 uses the individual ID of the connection destination event and the side code L2 to indicate that the event E4 and the event E1 satisfy the inter-event condition ac for the event E4, as shown in the content EI4 of the event E4. Store in RAM102. Content In EI4, the event condition is indicated by "0x1 (L2)".

  Furthermore, when the event E5 including the areas c and d is input, the condition determination unit 14 newly registers the input event E5 as a candidate for the satisfied conditions c and d. In FIG. 6, the condition determination unit 14 registers the event E5 in the d candidate 102d of the RAM 102. Although the event E5 satisfies the condition c, for the sake of simplicity of illustration, the state where the event E5 is registered in the c candidate 102c of the RAM 102 is not shown.

  Then, the condition determination unit 14 stores the individual ID “0x5” of the event E5 and the event condition “condition d” as shown in the content EI5.

  Here, the event E3 and the event E5 satisfy the inter-event condition b-d. This is because the areas and spaces included in events E3 and E5 are different, the IDs included in events E3 and E5 are the same, and the time difference between the time of event E1 and the time of event E5 following event E1 is 20 minutes. Because it is within.

  The condition determination unit 14 stores in the RAM 102 that the event E3 and the event E5 satisfy the inter-event condition b-d. In FIG. 6, the fact that the event E3 and the event E5 satisfy the inter-event condition b-d is indicated by connecting the event E3 and the event E5 with the side indicated by the broken line L3.

  The condition determination unit 14 uses the individual ID of the connection destination event and the side code L3 to indicate that the event E3 and the event E5 satisfy the inter-event condition bd in the event EI3 content EI3. Store in RAM102. Content In EI3, the event condition is indicated by "0x5 (L3)".

  The condition determination unit 14 further determines, for the event E5, the event ID of the connection destination event and the side code L3 so that the event E3 and the event E5 satisfy the inter-event condition bd are indicated in the content EI5 of the event E5. And stored in the RAM 102. Content In EI5, the event condition is indicated by "0x3 (L3)".

  Here, the event E4 and the event E5 satisfy the inter-event condition c-d. This is because the areas and spaces of the events E4 and E5 are the same, and the time difference between the time of the event E4 and the time of the event E5 following the event E4 is within 40 seconds. This is because the ID of event E4 and the ID of event E5 are different.

  The condition determination unit 14 stores in the RAM 102 that the event E4 and the event E5 satisfy the inter-event condition c-d. In FIG. 6, the fact that the event E4 and the event E5 satisfy the inter-event condition c-d is indicated by connecting the event E4 and the event E5 with the side indicated by the dotted line L4.

  The condition determination unit 14 uses the individual ID of the connection destination event and the side code L4 to indicate that the event E4 and the event E5 satisfy the inter-event condition cd for the event E4, as shown in the content EI4 of the event E4. Store in RAM102. Content In EI4, the event condition is indicated by "0x5 (L4)".

  In addition, the condition determination unit 14 determines, for the event E5, the event ID and edge code L4 of the connection destination event so that the event E4 and the event E5 satisfy the inter-event condition cd are indicated in the content EI5 of the event E5. And stored in the RAM 102. Content In EI5, the event condition is indicated by "0x4 (L4)".

(Event real-time processing)
Each time an event is stored in the RAM 102, the condition determination unit 14 determines in real time whether there is an event stored in the RAM 102 (hereinafter referred to as a storage event as appropriate) that satisfies the event-event condition. The output unit 18 outputs a determination result when there is a storage event that satisfies the inter-event condition.

  As described in FIG. 6, the condition determination unit 14 performs the following determination. The condition determination unit 14 determines whether the first storage event (for example, event E1 in FIG. 6) satisfies the condition a and the inter-event conditions ab and ac (first determination). The condition determination unit 14 determines whether the second storage event (for example, event E3 in FIG. 6) satisfies the condition b and the inter-event conditions ab and bd (second determination).

  The condition determination unit 14 determines whether the third storage event (for example, event E4 in FIG. 6) satisfies the condition c and the inter-event conditions a-c and c-d (third determination). The condition determination unit 14 determines whether the fourth storage event (for example, event E5 in FIG. 6) satisfies the condition d and the inter-event conditions b-d and c-d (fourth determination).

  If the output management unit 17 determines that all the inter-event conditions are satisfied in the first to fourth determinations (fifth determination), the output management unit 17 outputs a determination result indicating that the conditions are satisfied. An example of the determination result is a storage event that satisfies the above-described inter-event condition.

  The condition determination unit 14 performs the fifth determination at the timing when an event that satisfies the condition c and the inter-event conditions ac and cd, or an event that satisfies the condition d and the inter-event conditions bd and cd is stored in the RAM 102. I do.

  Note that the node deletion unit 16 may delete the first to fourth storage events after the output unit 18 outputs the determination result. As a result, the useless storage area of the RAM 102 can be reduced.

  As described above, the condition determination unit 14 determines in real time whether the acquired event satisfies a predetermined event condition or an inter-event condition every time an event is acquired. Then, the output management unit 17 outputs the determination result in real time when the stored event satisfies the inter-event condition.

  That is, according to the information processing apparatus of the present embodiment, events satisfying all predetermined conditions can be extracted from a plurality of events in real time, and information indicating that the predetermined conditions are satisfied can be quickly output.

  In the examples of FIGS. 3 to 6, the determination result is the target (the stalker actor and the stalker victim) in the tracking detection. Thus, according to the information processing apparatus of the present embodiment, the administrator can acquire the detection result quickly and in real time.

  Here, in addition to executing the above-described determination processing in real time, the condition determination unit 14 determines whether there is a storage event satisfying the inter-event condition in the storage event stored in the RAM 102 at every predetermined timing. You may judge. The manager can acquire the detection result as appropriate by the process of determining at each predetermined timing.

(Delete event)
Here, it is assumed that there are a large number of events or a large number of conditions are set. Under this assumption, when the information processing apparatus determines whether an event satisfies a number of conditions, the used capacity of the RAM 102 required for the determination process increases, and the processing load increases. As a result, it is difficult to perform the determination process quickly. Therefore, the information processing apparatus reduces the used capacity of the RAM 102.

  Specifically, the node deletion unit 16 specifies an event that does not satisfy the inter-event condition based on the storage event time stored in the RAM 102 and the reference time corresponding to the current time, and the specified storage event is stored in the RAM 102. Delete from. Here, the current time is, for example, the time included in the latest event or the time when the latest event is acquired. The reference time corresponding to the current time is, for example, the same time as the current time or a time delayed by several seconds.

  If the event that satisfies the inter-event condition is not stored in the RAM 102 even if the sum of the time of the storage event that satisfies the first event condition and the time of the inter-event condition exceeds the reference time, the node deletion unit 16 A memory event satisfying the event condition 1 is deleted from the RAM 102.

  Here, the event condition is, for example, the condition a, the inter-event condition is the inter-event condition a-b, and the time of the inter-event condition is, for example, 40 seconds. In the example of FIG. 6, after the event E1 is stored in the RAM 102, the addition time obtained by adding the time of the event E1 "17:54:00" and the time of the inter-event condition ab "40 seconds" is the current time. If the event that satisfies the inter-event condition ab (the event that is a candidate for the condition b) is not stored in the RAM 102 even if it exceeds, the event E1 is deleted.

  On the other hand, the event condition is, for example, condition a, the inter-event condition is an inter-event condition a-c, and the time of the inter-event condition a-c is, for example, 20 minutes. In the example of FIG. 6, after the event E1 is stored in the RAM 102, the current time is obtained by adding the time of the event E1 "17:54:00" and the time "20 minutes" of the inter-event condition ac. If the event that satisfies the condition between the events (candidate for the condition c) is not stored in the RAM 102 even if it exceeds, the event E1 is deleted.

  The node deletion unit 16 also sets the first storage event when the first storage event satisfies the first event condition and the second storage event satisfies the third event condition and the second inter-event condition. When the first storage event is deleted, the second storage event is deleted from the RAM 102.

  In the example of FIG. 6, the first storage event is event E1. The first event condition is condition a, the third event condition is condition c, and the second inter-event condition is inter-event condition a-c.

  In the example of FIG. 6, after the event E1 is stored in the RAM 102, the event having the time “17:54:40”, the ID “1”, the area c, and the spaces “36”, 39 ”” ( Assume that the second storage event) is registered as a candidate for condition c.

  Here, in FIG. 6, it is assumed that no event is stored in the candidate for condition b. In other words, the event E1 does not satisfy the inter-event condition a-b.

  In this example, when the node deletion unit 16 deletes the first stored event (event E1) registered as a candidate for the condition a, other events satisfying the inter-event condition ac are found for the second stored event. Since it is not stored, the second stored event is deleted.

  The node deletion unit 16 also adds the third storage event time to the third time when the time obtained by adding the fifth time determined in accordance with the third event condition exceeds the reference time. The memory event is deleted from the RAM 102. In the example of FIG. 6, the third storage event is event E4, the third event condition is condition c, and the fifth time is an unconditional timeout time “40 seconds”.

  Similarly, when the time obtained by adding the time of the fourth storage event and the fifth time determined corresponding to the fourth event condition exceeds the reference time, the node deletion unit 16 performs the fourth storage event. Delete event from RAM102. In the example of FIG. 6, the fourth stored event is event E5, the fourth event condition is condition d, and the sixth time is an unconditional timeout time “40 seconds”.

  As described above, the storage capacity of the RAM 102 can be effectively used by deleting events that do not satisfy the inter-event condition. In other words, an event that does not satisfy the inter-event condition even after a lapse of time can be deleted, and a useless storage area of the RAM 102 can be reduced.

(Flow diagram)
FIGS. 7 and 8 are first and second flowcharts for explaining the real-time processing of events described in the first embodiment. In the following description, Sn (n is an integer of 1 or more) means step Sn, and the letter “step” is omitted as appropriate.

  S1: The condition reading unit 11 reads, for example, information having the event condition, the inter-event condition, the timeout, and the unconditional timeout described in FIG.

  This information is stored in the storage 103 in a text format, for example. The condition conversion unit 12 performs the conversion described with reference to FIG. Next, the process proceeds to S2.

  S2: The data reading unit 13 waits for an event to be received, and inputs the event to the condition determination unit 14 when an event is received. Next, the process proceeds to S3.

  S3: The condition determination unit 14 determines whether the current time and the event registered in the condition candidate for which the unconditional timeout is set among the events registered in the condition candidate for which the unconditional timeout is set. Determine if there is an event whose time difference exceeds the unconditional timeout. The condition for setting the unconditional timeout is condition c or condition d. The unconditional timeout is 40 seconds, for example. If YES at S3, move to S7. If S3 is NO, go to S4.

  S4: The condition determination unit 14 determines whether there is any unprocessed event that does not satisfy all the inter-event conditions related to the event among the events registered in each candidate. In other words, the condition determination unit 14 determines whether there is any unprocessed event that is not connected by two different types of events among the events registered in each candidate. If YES at S4, move to S5. If S4 is NO, go to S8.

  An inter-event condition related to an event is a condition having some relationship with a condition satisfied by the event. For example, when this event satisfies condition a, the inter-event conditions related to this event are condition a-b and condition a-c. When this event satisfies condition b, the inter-event conditions related to this event are condition ab and condition bd. When this event satisfies condition c, the inter-event conditions related to this event are condition a-c and condition c-d. When this event satisfies condition d, the inter-event conditions related to this event are condition b-d and condition c-d.

  An unprocessed event is an event that has not been processed among events registered as candidates for condition a to candidate for condition d, in other words, an event that has not been processed. An event newly registered in the candidate for condition a to the candidate for condition d is an unprocessed event.

  S5: The condition determination unit 14 determines whether there is an event to be deleted (hereinafter referred to as a deletion event as appropriate) among the registered events. If YES at S5, move to S7. If NO in S5, go to S6. The condition determination unit 14 executes the process of S5 for each registered event. S5 will be specifically described with reference to FIGS. 24, 57, 58, and the like.

  The event to be deleted is any one of the first to third deletion events. The first delete event is related to this unprocessed event, which is the difference between the current time and the time of this unprocessed event that does not satisfy any inter-event condition related to the unprocessed event. The event exceeds the timeout period of the inter-event condition to be performed. It may be longer than the timeout time. This unprocessed event that does not satisfy any inter-event condition regarding an unprocessed event is an unprocessed event that has no edge.

  Here, when there are a plurality of timeout times for the above-described inter-event condition, the first deletion event is as follows. That is, the first deletion event is the shortest event in which the difference between the current time and the time of an unprocessed event that does not satisfy any inter-event condition related to the unprocessed event is related to the above-mentioned unprocessed event. The event exceeds the timeout time of the interval condition.

  The second delete event is an unprocessed event that does not satisfy the inter-event condition in which the time difference between the current time and this unprocessed event satisfies the condition that this unprocessed event satisfies as its own condition The event exceeds the timeout time of the interval condition. It may be longer than the timeout time. In the inter-event condition related to the event, the self-condition is a condition that this event satisfies.

  The third deletion event is an unprocessed event that is not connected to an event that satisfies a condition related to a time before a condition that is satisfied by an unprocessed event (hereinafter referred to as condition X).

  When the condition X is the condition a, there is no condition related to the time before the condition a. When the condition X is the condition b, the condition related to the time before the condition b is the condition a. When the condition X is the condition c, the condition related to the time before the condition c is, for example, the condition a. When the condition X is the condition d, the condition related to the time before the condition d is, for example, the condition b.

  As is clear from the above description of the delete event, an event having two different types of sides is not a delete event.

  Hereinafter, in S5, when a plurality of registered events include a deletion event and an event other than the deletion event, the processing of S7 is first executed for the deletion event, and then the deletion event The process of S6 is executed for other events.

  S6: The condition determination unit 14 determines that an unprocessed event determined as YES in S5 (an event not to be deleted) has been processed. Specifically, the condition determination unit 14 sets a processed flag in the RAM 102 corresponding to an event that is not a deletion target. And it returns to S3. Note that the condition determination unit 14 may set the processed flag in a portion indicated by “other data:” in the contents of each event in FIG.

  S7: The node deletion unit 16 unprocesses the event connected to the event to be deleted (in other words, deletes the processed flag), and further deletes the event to be deleted and the event to be deleted. Delete the edges. And it returns to S3.

  In S3, when it is determined as S3 / NO and the process proceeds from S3 to S7, the event to be deleted in S7 is an event that has exceeded the unconditional timeout.

  S8: The condition determination unit 14 unprocesses the processed event (in other words, deletes the processed flag). And it moves to S9.

  S9: The condition determining unit 14 determines whether the input event satisfies any condition (condition a to condition d). If YES at S9, move to S10. If NO at S9, return to S2.

  S10: The condition determination unit 14 newly registers the input event as a candidate for the satisfied condition. Then, the condition determining unit 14 executes the processing from S11 onward for each newly registered event.

  S11: The condition determining unit 14 determines whether the partner condition of each inter-event condition related to the newly registered event includes a preceding condition whose time precedes its own condition. If YES at S11, then move to S12. If NO in S11, the process moves to S21 in FIG.

  As described in S4, the inter-event condition related to the event is a condition having some relationship with the condition satisfied by the event.

  As described above, in the inter-event condition related to the event, the self-condition is a condition that this event satisfies. The opponent condition is a condition different from the self condition in the inter-event condition. For example, inter-event conditions related to events registered as candidates for condition a are condition a-b and condition a-c. Here, in the case of the inter-event conditions a-b and a-c, the self-condition is the condition a. The partner condition in the inter-event condition a-b is the condition b. The partner condition in the inter-event condition a-c is the condition c.

  The preceding condition whose time precedes its own condition is a condition related to the time before the own condition. For example, if the self condition is condition b, the preceding condition is condition a. If the self-condition is condition c, the preceding conditions are conditions a and b. If the self-condition is condition d, the preceding conditions are conditions a and b. If the self-condition is condition a, there is no preceding condition.

  S12: The condition determination unit 14 includes events satisfying the preceding condition (see S11) (events registered as candidates for the preceding condition) that satisfy the inter-event condition including the preceding condition related to the newly registered event. Determine if there is. If YES in S12, the process moves to S14. If NO in S12, the process moves to S13.

  S13: The node deletion unit 16 deletes the newly registered event. Next, the process returns to S2.

  S14: The graph management unit 15 connects the event determined to satisfy the inter-event condition in S12 and the newly registered event with edges. Next, the process proceeds to S21 in FIG.

  S21 in FIG. 8: The condition determination unit 14 determines whether the self-condition and the partner condition of any inter-event condition related to the newly registered event are irrelevant conditions. If YES at S21, then move to S22. If NO at S21, proceed to S24.

  In the inter-event condition related to the event, the unrelated condition is that there is no time-related condition between the own condition and the partner condition. For example, the condition c and the condition d are conditions that have no time-related condition and no context between the two conditions.

  S22: The condition determination unit 14 determines whether there is an event that satisfies any of the inter-event conditions related to the newly registered event among the events registered as candidate conditions having no context. If YES in S22, the process moves to S23. If NO at S22, proceed to S24.

  S23: The graph management unit 15 connects the event satisfying the above-described condition in S22 and the newly registered event with an edge. Next, the process proceeds to S24.

  S24: The condition determination unit 14 determines whether the partner condition of each inter-event condition related to the newly registered event includes a subsequent condition whose time follows the own condition.

  In an inter-event condition related to an event, a subsequent condition in which time follows the own condition is a condition related to a time later than the own condition. For example, if the self condition is condition a, the subsequent conditions are conditions b, c, and d. If the self condition is condition b, the subsequent conditions are conditions c and d. If the self-condition is conditions c and d, there are no following conditions because conditions c and d are unrelated conditions.

  If YES at S24, return to S2. If S24 is NO, move to S25.

  S25: The condition determination unit 14 determines whether the newly registered event satisfies the conditions between all events related to the newly registered event. For example, the condition determination unit 14 determines whether the newly registered event has two different types of sides. If YES in S25, the process moves to S26. If S25 is NO, move to S2.

  S26: The output management unit 17 additionally registers the newly registered event in the RAM 102 as a candidate set 102f, assuming that the condition that the newly registered event that satisfies the inter-event condition in S25 satisfies is satisfied. Specifically, the output management unit 17 treats a condition that a newly registered event having two different types of edges has been processed, and additionally registers the newly registered event as a candidate set 102f in the RAM 102. Next, the process proceeds to S27.

  S27: The output management unit 17 determines whether there is an unprocessed condition. If YES in S27, the process moves to S28. If S27 is NO, then move to S29.

  S28: The output management unit 17 sets one of the unprocessed conditions and the condition that satisfies the processed condition and the inter-event condition as the current event condition. Next, the process proceeds to S30.

  S29: The output unit 18 outputs an event registered in the candidate set 102f, and unprocesses all condition candidates. Next, the process returns to S2.

  S30: The output management unit 17 determines whether the candidate set 102f of the RAM 102 is empty (no event is registered). If YES in S30, the process moves to S31. If S30 is NO, move to S32.

  S31: The output management unit 17 sets the entry of the new candidate set 102g in the RAM 102 as the candidate set 102f of the RAM 102, and further processes the current event condition. Then, the process returns to S27.

  S32: The output management unit 17 additionally registers one entry extracted from the candidate set 102f of the RAM 102 in the RAM 102 as the current candidate 102e. Then, the process proceeds to S33.

  S33: The output management unit 17 adds the related event and the event registered as the current candidate 102e to the new candidate set 102g. A related event has two different types of events registered in the current event condition, and is connected to the event registered in the current candidate by at least one of these two sides. Event.

  Here, when the number of events obtained by subtracting 1 from the number of all event conditions is registered as the current candidate 102e, the related events are the events registered in the current candidate by two sides of different types. It is a connected event. For example, assuming that all event conditions (condition a to condition d) are four, the related events are of different types when 3 (4-1) events are registered as the current candidate 102e. It is an event connected to the event registered in the current candidate by two sides.

  After S33 ends, return to S30. Here, when there is no related event, the above-described addition in S33 is not executed, and the process returns to S30. When the input of the event stops for a predetermined time (for example, 10 minutes), the information processing apparatus 1 ends the processing described with reference to FIGS.

(Specific example of the first embodiment)
9 to 58 are first to fifty diagrams illustrating specific examples of the first embodiment. Here, before describing a specific example of the first embodiment, the condition reading unit 11 reads information having the event condition, the inter-event condition, the timeout, and the unconditional timeout described in FIG. 5 from the storage 103 ( S1). Then, the condition conversion unit 12 performs the conversion described in FIG. 2 on the read information and stores the conversion result in the RAM 102.

  In the following specific example, the time included in the input event is the current time. Then, the processing after S3 is executed at the timing when the event is input.

(Event input of ID1)
The data reading unit 102 waits until an event is input (S2). The data reading unit 13 reads the event of ID1 shown in the event table of FIG. 9 (S2). In FIG. 9, no event is registered in the candidate for condition c and the candidate for condition d. Therefore, there is no event where the difference between the current time "17:54:00" and the time of the event registered in the condition c candidate or the condition d candidate exceeds the unconditional timeout "40 seconds" ( S3 / NO). It should be noted that the event table shown in the following figure is described for explanation and is not stored in the RAM 102.

  In FIG. 9, no event is registered in the candidates for condition a to candidate for condition d. Therefore, in FIG. 9, there is no unprocessed event that is not connected by an edge among the events registered in each candidate (S4 / NO).

  Accordingly, the condition determination unit 14 determines NO in S3 and NO in S4, and sets the processed event as unprocessed (S8). The condition determining unit 14 does not execute the process of S8 when there is no processed event.

  Since the input event of ID1 includes areas a and b, conditions a and b are satisfied in conditions a to d (S9 / YES). Accordingly, the condition determination unit 14 determines YES in S9, and newly registers the event with ID1 as a candidate for conditions a and b (S10).

  Then, the condition determining unit 14 executes the process of S11 for each event newly registered as a candidate for the conditions a and b.

  In the partner condition (condition b, c) of the inter-event condition (condition ab, condition ac) related to the event of ID1 newly registered as a candidate for condition a (event satisfying condition a), in the own condition (condition a) The preceding condition (no condition) preceded by time is not included (S11 / NO). Therefore, the condition determination unit 14 determines NO in S11.

  Hereinafter, an event with ID1 newly registered as a candidate for condition a is referred to as event ID1a. The self-condition (condition a) and partner condition (condition b or condition c) of any inter-event condition (condition ab or condition ac) related to event ID 1a are not unrelated conditions (condition c and condition d) (S21 / NO).

  The partner condition (condition b, c) of each inter-event condition (condition ab, condition ac) related to event ID 1a includes a subsequent condition (condition b or condition c) that is timed after itself (condition a). (S24 / YES).

  Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

  Next, the process of S11 is executed for the event with ID1 newly registered as a candidate for condition b. In the partner condition (condition a, d) of each inter-event condition (condition a or condition bd) related to the event with ID1 newly registered as a candidate for condition b (event satisfying condition b), in the own condition (condition b) The preceding condition (condition a) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID1 newly registered as a candidate for condition b is referred to as event ID1b. Among the events that satisfy the preceding condition (condition a) (events registered as candidates for condition a), there is no event that satisfies the inter-event condition including the preceding condition (for example, condition ab) related to event ID1b (S12 / NO). An event that satisfies this inter-event condition a-b is an event that satisfies the inter-event condition a-b (an event having a time within 40 seconds from "17:54:00", a different ID, and the same area and space).

  Accordingly, the condition determination unit 14 determines NO in S12, and the node deletion unit 16 deletes the event ID 1b as shown in FIG. 10 (S13). This deletion is indicated by “x” in FIG. And it returns to S2.

(Event input of ID3)
The data reading unit 13 waits until an event is input (S2). The data reading unit 13 reads the ID3 event shown in the event table of FIG. 11 (S2). In FIG. 11, no event is registered in the candidate for condition c and the candidate for condition d. Therefore, there is no event where the difference between the current time "17:54:00" and the time of the event registered in the condition c candidate or the condition d candidate exceeds the unconditional timeout "40 seconds" ( S3 / NO).

  In FIG. 11, among the events registered in each candidate, the event ID 1a is an unprocessed event and is not connected on two different sides. Therefore, there is an unprocessed event (event ID 1a) in S4 and an event (event ID 1a) that is not connected by two sides of different types (S4 / YES). Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 11, there is no deletion event described in S5 of FIG. The reason is as follows. The timeout period of the inter-event conditions a-b and a-c including the condition a satisfied by the unprocessed event ID 1a as its own condition is 40 seconds and 20 minutes.

  The difference between the current time "17:54:00" and the time "17:54:00" of event ID1a registered in the condition a candidate does not exceed this timeout time (40 seconds, 20 minutes) ( S5 / NO). Further, there is no related condition before the condition a satisfied by the event ID 1a (S5 / NO). Therefore, the condition determination unit 14 determines NO in S5, and proceeds to S6.

  The condition determination unit 14 sets the unprocessed event ID 1a to the processed (S6) and returns to S3. In S3, no event is registered in the candidate for condition c and the candidate for condition d (S3 / NO). Since the event ID 1a has been processed and there is no unprocessed event (S4 / NO), the condition determination unit 14 unprocesses the processed event (event ID 1a) (S8).

  Since the input event of ID3 does not include the areas a to d, the conditions a to d are not satisfied (S9 / NO). Therefore, the condition determination unit 14 does nothing for the event of ID3.

(Event input of ID7)
The data reading unit 13 reads the event of ID7 shown in the event table of FIG. 12 (S2). In FIG. 12, no event is registered in the candidate for condition c and the candidate for condition d. Therefore, there is no event where the difference between the current time "17:54:00" and the time of the event registered in the condition c candidate or the condition d candidate exceeds the unconditional timeout "40 seconds" ( S3 / NO).

  In FIG. 12, the condition determination unit 14 determines that the event ID 1a is NO in S3, YES in S4, NO in S5, as described in FIG. 11, and proceeds to S6.

  The condition determination unit 14 sets the unprocessed event ID 1a to the processed (S6) and returns to S3. In S3, no event is registered in the candidate for condition c and the candidate for condition d (S3 / NO). Since the event ID 1a has been processed and there is no unprocessed event (S4 / NO), the condition determination unit 14 unprocesses the processed event (event ID 1a) (S8).

  Since the input event of ID7 includes areas a and b, conditions a and b are satisfied in conditions a to d (S9 / YES). Accordingly, the condition determination unit 14 determines YES in S9, and newly registers the event ID7 as a candidate for conditions a and b (S10).

  Then, the condition determining unit 14 executes the process of S11 for each event newly registered as a candidate for the conditions a and b.

  In the partner condition (condition b, c) of each inter-event condition (condition ab, condition ac) related to the event of ID7 newly registered as a candidate for condition a (event satisfying condition a), in the own condition (condition a) The preceding condition (no condition) preceded by time is not included (S11 / NO). Therefore, the condition determination unit 14 determines NO in S11.

  Hereinafter, an event with ID7 newly registered as a candidate for condition a is referred to as event ID7a. The own condition (condition a) and partner condition (condition b or condition c) of any inter-event condition (condition ab or condition ac) related to event ID 7a are not unrelated conditions (condition c and condition d) (S21 / NO).

  The partner condition (condition b, c) of each inter-event condition (condition ab, condition ac) related to event ID 7a includes a subsequent condition (condition b or condition c) that is followed by its own condition (condition a). (S24 / YES).

  Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

  Next, the process of S11 is executed for the event with ID7 newly registered as a candidate for condition b. In the partner condition (condition a, d) of each inter-event condition (condition a or condition bd) related to the event of ID7 newly registered as a candidate for condition b (event satisfying condition b), in the own condition (condition b) The preceding condition (condition a) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID7 newly registered as a candidate for condition b is referred to as event ID7b. Among the events that satisfy the preceding condition (condition a) (events registered as candidates for condition a), there is no event that satisfies the inter-event condition including the preceding condition (for example, condition ab) related to event ID 7b (S12 / NO). An event that satisfies this inter-event condition a-b is an event that satisfies the inter-event condition a-b (an event having a time within 40 seconds from "17:54:00", a different ID, and the same area and space).

  Therefore, the node deletion unit 16 determines NO in S12, and deletes the event ID 7b as shown in FIG. 13 (S13). This deletion is indicated by “x” in FIG. And it returns to S2.

(Event input of ID4)
The data reading unit 13 reads the event of ID4 shown in the event table of FIG. 14 (S2). In FIG. 14, no event is registered in the candidate for condition c and the candidate for condition d. Therefore, there is no event where the difference between the event time registered in the condition c candidate or the condition d candidate and the current time "17:54:10" exceeds the unconditional timeout "40 seconds" ( S3 / NO).

  In FIG. 14, among the events registered in each candidate, event IDs 1a and ID7a are unprocessed events and events that are not connected by two different types of sides. Therefore, there is an unprocessed event (event ID1a, ID7a) of S4 and an event (event ID1a, ID7a) that is not connected between two different types (S4 / YES). Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 14, there is no deletion event described in S5 of FIG. The reason is as follows. The timeout period of the inter-event conditions a-b, a-c including the condition a that the unprocessed event ID 1a, ID 7a satisfies as its own condition is 40 seconds, 20 minutes. In addition, the timeout period of the inter-event conditions ab and bd including the condition b satisfied by the unprocessed event ID 4b as its own condition is 40 seconds and 20 minutes.

  The current time is "17:54:00", and the time of the event registered in the condition a and condition b candidates is "17:54:00" and "17:54:10", so the condition a candidate There is no event that exceeds the timeout period (40 seconds or 20 minutes) among the events registered in (S5 / NO).

  In addition, among the events registered as candidates for condition a, there is no related condition before condition a satisfied by this event (S5 / NO). Therefore, the condition determination unit 14 determines NO in S5, and proceeds to S6.

  The condition determination unit 14 sets the unprocessed event IDs 1a and ID7a to be processed (S6), and returns to S3. In S3, no event is registered in the candidate for condition c and the candidate for condition d (S3 / NO). Since event ID1a and ID7a have been processed and there is no unprocessed event (S4 / NO), the condition determination unit 14 sets the processed event (event ID1a and ID7a) to be unprocessed (S8).

  Since the input event of ID4 includes areas a and b, conditions a and b are satisfied in conditions a to d (S9 / YES). Accordingly, the condition determination unit 14 determines YES in S9, and newly registers the event ID4 as a candidate for conditions a and b (S10).

  In the partner condition (condition b, c) of the inter-event condition (condition ab, condition ac) related to the event of ID4 newly registered as a candidate for condition a (event satisfying condition a), in the own condition (condition a) The preceding condition (no condition) preceded by time is not included (S11 / NO). Therefore, the condition determination unit 14 determines NO in S11.

  Hereinafter, an event with ID4 newly registered as a candidate for condition a is referred to as event ID4a. The own condition (condition a) and partner condition (condition b or condition c) of any inter-event condition (condition ab or condition ac) related to event ID 4a are not unrelated conditions (condition c and condition d) (S21 / NO).

  The partner condition (condition b, c) of each inter-event condition (condition ab, condition ac) related to event ID 4a includes a subsequent condition (condition b or condition c) whose time follows the own condition (condition a). (S24 / YES).

  Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

  Next, the process of S11 is executed for the event with ID4 newly registered as a candidate for condition b.

  In the other condition (condition a, d) of each inter-event condition (condition ab or condition bd) related to the event with ID4 newly registered as a candidate for condition b (event satisfying condition b), in the own condition (condition b) The preceding condition (condition a) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID4 newly registered as a candidate for condition b is referred to as event ID4b. Among events that satisfy the preceding condition (condition a) (events registered as candidates for condition a), events that satisfy the inter-event condition including the preceding condition (for example, condition ab) related to event ID 4b (event ID1a) Yes (S12 / YES). An event that satisfies this inter-event condition ab satisfies the inter-event condition ab (an event having a time within 40 seconds from "17:54:10", a different ID, and the same area and space (2 ", 23")) Event ID 1a.

  Therefore, the condition determination unit 14 determines YES in S12. Then, as shown in FIG. 15, the graph management unit 15 connects the event ID 1a satisfying the inter-event condition and the newly registered event ID 4b with a side (see a solid line) (S14).

  The own condition (condition b) and partner condition (condition a or condition d) of any inter-event condition (condition ab or condition bd) related to event ID 4b are not unrelated conditions (condition c and condition d) (S21 / NO).

  The partner condition (condition a, d) of each inter-event condition (condition ab or condition bd) related to the event ID 4b includes a subsequent condition (condition d) whose time follows the own condition (condition b) (S24 / YES).

  Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

(Event input of ID1)
The data reading unit 13 reads the event of ID1 shown in the event table of FIG. 16 (S2). In FIG. 16, no event is registered in the candidate for condition c and the candidate for condition d. Therefore, there is no event in which the difference between the event time registered in the condition c candidate or the condition d candidate and the current time "17:54:20" exceeds the unconditional timeout "40 seconds" ( S3 / NO).

  In FIG. 16, among the events registered in each candidate, event ID 1a, ID 7a, ID 4a, ID 4b are unprocessed events. Event ID1a and ID4b are events connected on one side.

  Therefore, there are unprocessed events in S4 (event ID1a, ID7a, ID4a, ID4b) that are not connected on two different sides (event ID1a, ID7a, ID4a, ID4b) (S4 / YES). Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 16, there is no deletion event described in S5 of FIG. The reason is as follows. The timeout period of the inter-event conditions a-b, a-c including the condition a satisfying the unprocessed event ID 1a, ID 4a, ID 7a as its own condition is 40 seconds, 20 minutes. In addition, the timeout period of the inter-event conditions ab and bd including the condition b satisfied by the unprocessed event ID 4b as its own condition is 40 seconds and 20 minutes.

  The current time is "17:54:20", and the event times registered as candidates for condition a and condition b are "17:54:00" and "17:54:10", so condition a and condition Among the events registered as candidates for b, there is no event that exceeds the timeout time (40 seconds or 20 minutes) (S5 / NO).

  In addition, among the events registered as candidates for condition a, there is no related condition before condition a satisfied by this event (S5 / NO). Furthermore, among events registered as candidates for condition b, they are connected by edges to an event (event ID 1a) that satisfies condition a related to a time prior to condition b that this event (event ID 4b) satisfies ( S5 / NO). Therefore, the condition determination unit 14 determines NO in S5, and proceeds to S6.

  The condition determination unit 14 processes the unprocessed events ID1a, ID7a, ID4a, and ID4b (S6), and returns to S3. In S3, no event is registered in the candidate for condition c and the candidate for condition d (S3 / NO). Since event ID1a, ID7a, ID4a, and ID4b have been processed and there is no unprocessed event (S4 / NO), the condition determination unit 14 sets the processed event to be unprocessed (S8).

  Since the input event of ID1 includes areas a and b, conditions a and b are satisfied in conditions a to d (S9 / YES). Accordingly, the condition determination unit 14 determines YES in S9, and newly registers the event with ID1 as a candidate for conditions a and b (S10).

  In the partner condition (condition b, c) of the inter-event condition (condition ab, condition ac) related to the event of ID1 newly registered as a candidate for condition a (event satisfying condition a), in the own condition (condition a) The preceding condition (no condition) preceded by time is not included (S11 / NO). Therefore, the condition determination unit 14 determines NO in S11.

  Hereinafter, the event of ID1 newly registered as a candidate for condition a is described as event ID1a “17:54:20”. The self-condition (condition a) and partner condition (condition b or condition c) of any inter-event condition (condition ab or condition ac) related to event ID1a "17:54:20" are unrelated conditions (conditions Not c and condition d) (S21 / NO).

  Subordinate condition (condition b, c) of each inter-event condition (condition ab, condition ac) related to event ID 1a "17:54:20", and subsequent condition (condition b) that follows the own condition (condition a) Or condition c) is included (S24 / YES).

  Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

  Next, the process of S11 is executed for the event with ID1 newly registered as a candidate for condition b. In the partner condition (condition a, d) of each inter-event condition (condition a or condition bd) related to the event with ID1 newly registered as a candidate for condition b (event satisfying condition b), in the own condition (condition b) The preceding condition (condition a) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID1 newly registered as a candidate for condition b is referred to as event ID1b. Among the events that satisfy the preceding condition (condition a) (events registered as candidates for condition a), there is no event that satisfies the inter-event condition including the preceding condition (for example, condition ab) related to event ID1b (S12 / NO). An event that satisfies this inter-event condition a-b is an event that satisfies the inter-event condition a-b (an event having a time within 40 seconds from "17:54:20", a different ID, and the same area and space).

  Therefore, the node deletion unit 16 determines NO in S12, and deletes the event ID 1b as shown in FIG. 17 (S13). This deletion is indicated by “x” in FIG. And it returns to S2.

(Event input of ID2)
The data reading unit 13 reads the event of ID2 shown in the event table of FIG. 18 (S2). In FIG. 18, no event is registered in the candidate for condition c and the candidate for condition d. Therefore, there is no event in which the difference between the event time registered in the condition c candidate or the condition d candidate and the current time "17:54:20" exceeds the unconditional timeout "40 seconds" ( S3 / NO).

  In FIG. 18, among the events registered for each candidate, event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a, ID4b are unprocessed events, And it is an event that is not connected by two different types of sides. Therefore, it is an unprocessed event of S4 and is not connected by two sides of different types (event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a ID4b) (S4 / YES). Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 18, there is no deletion event described in S5 of FIG. The reason is as follows. Unprocessed event ID1a "17:54:00", ID1a "17:54:20", inter-event condition ab and ac that include condition a satisfying ID4a and ID7a as its own condition, and the timeout time of ac is 40 seconds and 20 minutes is there. In addition, the timeout period of the inter-event conditions ab and bd including the condition b satisfied by the unprocessed event ID 4b as its own condition is 40 seconds and 20 minutes.

  The current time is "17:54:20", and the event times registered as candidates for condition a and condition b are "17:54:00", "17:54:10", "17:54:20" Therefore, there is no event that exceeds the timeout time (40 seconds or 20 minutes) among the events registered as candidates for condition a and condition b (S5 / NO).

  In addition, among the events registered as candidates for condition a, there is no related condition before condition a satisfied by this event (S5 / NO). Furthermore, among events registered as candidates for condition b, they are connected by edges to an event (event ID 1a) that satisfies condition a related to a time prior to condition b that this event (event ID 4b) satisfies ( S5 / NO). Therefore, the condition determination unit 14 determines NO in S5, and proceeds to S6.

  The condition determination unit 14 sets the unprocessed event ID 1a ("17:54:00", "17:54:20"), event IDs 7a, ID4a, and ID4b to be processed (S6), and returns to S3. In S3, no event is registered in the candidate for condition c and the candidate for condition d (S3 / NO). Since event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a, and ID4b have been processed and there are no unprocessed events (S4 / NO), condition determination unit 14 Makes the processed event unprocessed (S8).

  Since the input event of ID2 includes areas a and b, conditions a and b are satisfied in conditions a to d (S9 / YES). Accordingly, the condition determination unit 14 determines YES in S9, and newly registers the event of ID2 as a candidate for conditions a and b (S10).

  In the event condition (condition b, c) of each inter-event condition (condition ab, condition ac) related to the event of ID2 newly registered as a candidate for condition a (event satisfying condition a), in the own condition (condition a) The preceding condition (no condition) preceded by time is not included (S11 / NO). Therefore, the condition determination unit 14 determines NO in S11.

  Hereinafter, an event with ID2 newly registered as a candidate for condition a is referred to as event ID2a. The own condition (condition a) and partner condition (condition b or condition c) of any inter-event condition (condition ab or condition ac) related to event ID2a are not unrelated conditions (condition c and condition d) (S21 / NO).

  The partner condition (condition b, c) of each inter-event condition (condition ab, condition ac) related to the event ID 2a includes a subsequent condition (condition b or condition c) whose time follows the own condition a (S24 / YES). Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

  Next, the process of S11 is executed for the event of ID2 newly registered as a candidate for condition b. Condition b of the inter-event condition (condition a or d) related to the event of ID2 newly registered as a candidate for condition b (event satisfying condition b) is preceded by its own condition b. The preceding condition (condition a) to be included is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID2 newly registered as a candidate for condition b is referred to as event ID2b. Among events that satisfy the preceding condition (condition a) (events registered as candidates for condition a), events that satisfy the inter-event condition including the preceding condition (for example, condition ab) related to event ID2b (event ID4a) Yes (S12 / YES). An event that satisfies this inter-event condition ab satisfies the inter-event condition ab (an event having a time within 40 seconds from "17:54:20", a different ID, and the same area and space (2 ", 23")) Event ID 1a “17:54:00”, ID 4a.

  Therefore, the condition determination unit 14 determines YES in S12. Then, as shown in FIG. 19, the graph management unit 15 connects the event ID 1a “17:54:00”, ID 4a, and the newly registered event ID 2b that satisfy the inter-event condition by edges (see solid lines) (S14). ).

  The own condition (condition b) and partner condition (condition a or condition d) of any inter-event condition (condition ab or condition bd) related to event ID 2b are not unrelated conditions (condition c and condition d) (S21 / NO).

  The partner condition (condition a, d) of each inter-event condition (condition ab or condition bd) related to the event ID 4b includes a subsequent condition (condition d) whose time follows the own condition (condition b) (S24 / YES).

  Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

(Event input of ID6)
The data reading unit 13 reads the event of ID6 shown in the event table of FIG. 20 (S2). In FIG. 20, no event is registered in the candidate for condition c and the candidate for condition d. Therefore, there is no event in which the difference between the event time registered in the condition c candidate or the condition d candidate and the current time "17:54:20" exceeds the unconditional timeout "40 seconds" ( S3 / NO).

  In Fig. 20, among the events registered for each candidate, event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a, ID4b, ID2a, ID2b are unprocessed An event that is not connected by two sides of different types. Therefore, it is an unprocessed event of S4 and is not connected by two sides of different types (event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a , ID4b, ID2a, ID2b) (S4 / YES). Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 20, there is no deletion event described in S5 of FIG. The reason is as follows.

  Unprocessed event ID1a "17:54:00", ID1a "17:54:20", inter-event condition ab and ac that include condition a that satisfies ID4a, ID7a, and ID2a as their own conditions The timeout time of ac is 40 seconds, 20 Minutes. In addition, the timeout period of the inter-event conditions ab and bd including the condition b satisfying the unprocessed event ID 4b and ID2 condition b as its own condition is 40 seconds and 20 minutes.

  The current time is "17:54:20", and the event times registered as candidates for condition a and condition b are "17:54:00", "17:54:10", "17:54:20" Therefore, there is no event that exceeds the timeout time (40 seconds or 20 minutes) among the events registered as candidates for condition a and condition b (S5 / NO).

  In addition, among the events registered as candidates for condition a, there is no related condition before condition a satisfied by this event (S5 / NO). In addition, among the events registered as candidates for condition b, the event (event ID1a, ID4a) that meets condition a related to the time before condition b that this event (event ID4b, ID2b) satisfies is connected on the side (S5 / NO). Therefore, the condition determination unit 14 determines NO in S5, and proceeds to S6.

  The condition determination unit 14 processes unprocessed event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a, ID4b, ID2a, ID2b (S6) Return. In S3, no event is registered in the candidate for condition c and the candidate for condition d (S3 / NO). And since event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a, ID4b, ID2a, ID2b have been processed and there are no unprocessed events (S4 / NO), The condition determination unit 14 unprocesses the processed event (S8).

  Since the input event of ID6 includes areas a and b, conditions a and b are satisfied in conditions a to d (S9 / YES). Therefore, the condition determination unit 14 determines YES in S9, and newly registers the event of ID6 as a candidate for conditions a and b (S10).

  In the partner condition (condition b, c) of the inter-event condition (condition ab, condition ac) related to the event of ID6 newly registered as a candidate for condition a (event satisfying condition a), in the own condition (condition a) The preceding condition (no condition) preceded by time is not included (S11 / NO). Therefore, the condition determination unit 14 determines NO in S11.

  Hereinafter, an event with ID6 newly registered as a candidate for condition a is referred to as event ID6a. The own condition (condition a) and partner condition (condition b or condition c) of any inter-event condition (condition ab or condition ac) related to event ID 6a are not unrelated conditions (condition c and condition d) (S21 / NO).

  The partner condition (condition b, c) of each inter-event condition (condition ab, condition ac) related to the event ID 6a includes a subsequent condition (condition b or condition c) whose time follows the own condition a (S24 / YES).

  Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

  Next, the process of S11 is executed for the event with ID6 newly registered as a candidate for condition b. Condition b of the inter-event condition (condition a or d) related to the event of ID6 newly registered as a candidate of condition b (event satisfying condition b) is preceded by its own condition b. The preceding condition (condition a) to be included is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID6 newly registered as a candidate for condition b is referred to as event ID6b. Among events that satisfy the preceding condition (condition a) (events registered as candidates for condition a), events that satisfy the inter-event condition including the preceding condition (for example, condition ab) related to event ID 6b (event ID 7a) Yes (S12 / YES). An event that satisfies this inter-event condition ab satisfies the inter-event condition ab (an event having a time within 40 seconds from "17:54:20", a different ID, and the same area and space (3 ", 23")) Event ID 7a.

  Therefore, the condition determination unit 14 determines YES in S12. Then, as shown in FIG. 21, the graph management unit 15 connects the event ID 7a that satisfies the inter-event condition and the newly registered event ID 6b with a side (see a solid line) (S14).

  The own condition (condition b) and partner condition (condition a or condition d) of any inter-event condition (condition ab or condition bd) related to event ID 6b are not unrelated conditions (condition c and condition d) (S21 / NO).

  The partner condition (condition a, d) of each inter-event condition (condition ab or condition bd) related to the event ID 6b includes a subsequent condition (condition d) in which the time follows the own condition (condition b) (S24 / YES).

  Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

(Event input of ID5)
The data reading unit 13 reads the event of ID5 shown in the event table of FIG. 22 (S2). In FIG. 22, no event is registered in the candidate for condition c and the candidate for condition d. Therefore, there is no event in which the difference between the event time registered in the condition c candidate or the condition d candidate and the current time "17:54:20" exceeds the unconditional timeout "40 seconds" ( S3 / NO).

  In Fig. 22, among the events registered for each candidate, event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a, ID4b, ID6a, ID6b, ID2a, ID2b are , An unprocessed event and an event that is not connected by two sides of different types. Therefore, it is an unprocessed event of S4 and is not connected by two sides of different types (event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a , ID4b, ID6a, ID6b, ID2a, ID2b) (S4 / YES). Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 22, there is no deletion event described in S5 of FIG. The reason is as follows.

  Unprocessed event ID1a "17:54:00", ID1a "17:54:20", inter-event conditions ab and ac that include condition a satisfying ID4a, ID7a, ID2a, and ID6a as their own conditions The timeout time of ac is 40 seconds , 20 minutes. Further, the timeout period of the inter-event conditions ab and bd including the condition b satisfying the unprocessed event IDs 4b, ID2b, and ID6b as their own conditions is 40 seconds and 20 minutes.

  The current time is "17:54:20", and the event times registered as candidates for condition a and condition b are "17:54:00", "17:54:10", "17:54:20" Therefore, there is no event that exceeds the timeout time (40 seconds or 20 minutes) among the events registered as candidates for condition a and condition b (S5 / NO).

  In addition, among the events registered as candidates for condition a, there is no related condition before condition a satisfied by this event (S5 / NO). Furthermore, among the events registered as candidates for condition b, events (event ID1a, ID4a, ID7a) satisfying condition a related to the time prior to condition b satisfied by this event (event ID4b, ID2b, ID6b) And connected at the side (S5 / NO). Therefore, the condition determination unit 14 determines NO in S5, and proceeds to S6.

  The condition judgment unit 14 processes unprocessed event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a, ID4b, ID6a, ID6b, ID2a, ID2b (S6). Return to S3. In S3, no event is registered in the candidate for condition c and the candidate for condition d (S3 / NO). Event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a, ID4b, ID6a, ID6b, ID2a, and ID2b have been processed and there are no unprocessed events (S4 / NO), the condition determination unit 14 unprocesses the processed event (S8).

  Since the input event of ID5 includes areas a and b, conditions a and b are satisfied in conditions a to d (S9 / YES). Accordingly, the condition determination unit 14 determines YES in S9, and newly registers the event ID5 as a candidate for conditions a and b (S10).

  In the partner condition (condition b, c) of the inter-event condition (condition ab, condition ac) related to the event of ID5 newly registered as a candidate for condition a (event satisfying condition a), in the own condition (condition a) The preceding condition (no condition) preceded by time is not included (S11 / NO). Therefore, the condition determination unit 14 determines NO in S11.

  Hereinafter, an event with ID5 newly registered as a candidate for condition a is referred to as event ID5a. The own condition (condition a) and partner condition (condition b or condition c) of any inter-event condition (condition ab or condition ac) related to event ID 5a are not unrelated conditions (condition c and condition d) (S21 / NO).

  The partner condition (condition b, c) of each inter-event condition (condition ab, condition ac) related to the event ID 5a includes a subsequent condition (condition b or condition c) whose time follows the own condition a (S24 / YES).

  Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

  Next, the process of S11 is executed for the event with ID5 newly registered as a candidate for condition b. Condition b of the inter-event condition (condition a or d) related to the event of ID5 newly registered as a candidate for condition b (event satisfying condition b) is preceded by its own condition b. The preceding condition (condition a) to be included is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID5 newly registered as a candidate for condition b is referred to as event ID5b. Among events that satisfy the preceding condition (condition a) (events registered as candidates for condition a), events that satisfy the inter-event condition including the preceding condition (for example, condition ab) related to event ID 5b (event ID1a " 17:54:00 ", event ID 4a) is present (S12 / YES). An event that satisfies this inter-event condition ab satisfies the inter-event condition ab (an event having a time within 40 seconds from "17:54:20", a different ID, and the same area and space (2 ", 23")) Event ID 1a “17:54:00”, event ID 4a.

  Therefore, the condition determination unit 14 determines YES in S12. Then, as shown in FIG. 23, the graph management unit 15 connects the event ID 1a “17:54:00”, the event ID 4a, and the newly registered event ID 5b that satisfy the inter-event condition by edges (see solid lines) ( S14).

  The own condition (condition b) and partner condition (condition a or condition d) of any inter-event condition (condition ab or condition bd) related to event ID5b are not unrelated conditions (condition c and condition d) (S21 / NO).

  The partner condition (condition a, d) of each inter-event condition (condition ab or condition bd) related to the event ID 5b includes a subsequent condition (condition d) whose time follows the own condition (condition b) (S24 / YES).

  Accordingly, the condition determination unit 14 determines NO in S21, YES in S24, and proceeds to S2.

(Event input of ID8)
The data reading unit 13 reads the event of ID8 shown in the event table of FIG. 24 (S2). In FIG. 24, no event is registered in the candidate for condition c and the candidate for condition d. Therefore, there is no difference between the time of the event registered in the condition c candidate or the condition d candidate and the current time “17:55:00” (may be “17:55:01” seconds). There is no event that exceeds the condition timeout "40 seconds" (S3 / NO).

  In FIG. 24, among the events registered for each candidate, event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a, ID4b, ID6a, ID6b, ID5a, ID5b, ID2a and ID2b are unprocessed events that are not connected by two sides of different types. Therefore, it is an unprocessed event of S4 and is not connected by two sides of different types (event ID1a ("17:54:00", "17:54:20"), event ID7a, ID4a , ID4b, ID6a, ID6b, ID5a, ID5b, ID2a, ID2b (S4 / YES) Therefore, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 24, the deletion events described in S5 of FIG. 7 are event ID1a “17:54:20”, ID6a, ID5a, and ID2a. The reason is as follows.

  For these events, the difference between the current time "17:55:01" and the unprocessed event time "17:54:20" that has no edge is related to the above-mentioned unprocessed event. , The event that exceeds the timeout time (40 seconds) of the shortest event condition ab.

  That is, event ID1a “17:54:20”, ID6a, ID5a, and ID2a are unprocessed events that do not have one side, and the current time “17:55:01” and event ID1a “17:54: The time difference between 20 ", ID6a, ID5a, and ID2a exceeds the timeout time" 40 seconds "of the inter-event condition ab. Accordingly, the node deletion unit 16 determines YES in S5 for these event ID1a “17:54:20”, ID2a, ID6a, and ID5a, and deletes these events (S7).

  The unprocessed event ID 1a “17:54:00”, ID 4a, and ID 7a are connected to the event registered as a candidate for the condition b by a side (solid line). Therefore, the timeout period of the inter-event condition a-b including the unprocessed event ID 1a “17:54:00”, the condition a satisfying the ID 4a and ID 7a as its own condition is 20 minutes.

  Further, the unprocessed events ID4b, ID2b, ID6b, and ID5b are connected to the events registered as candidates for the condition a by sides (solid lines). Accordingly, the timeout period of the inter-event condition b-d including the condition b satisfying the unprocessed event ID 4b, ID 2b, ID 6b, ID 5b as its own condition is 20 minutes.

  The current time is "17:55:00", and the time of events registered as candidates for condition a and condition b is "17:54:00", "17:54:10" or "17:54:20" Therefore, there is no unprocessed event ID1a “17:54:00”, ID4a, ID7a, ID4b, ID2b, ID6b, ID5b that has exceeded the timeout time (20 minutes) (S5 / NO ).

  All events registered as candidates for condition b are connected to the events registered as candidates for condition a by edges. Furthermore, no event registered as a candidate for condition b exceeds the timeout period (20 minutes) of the inter-event condition b-d related to this event (S5 / NO).

  Of the events registered as candidates for condition a, there is no related condition prior to condition a satisfied by this event (S5 / NO). In addition, among the events registered as candidates for condition b, events (event ID1a, ID4a, ID4a, ID4a, ID4a, It is connected to ID7a) at the side (S5 / NO). Therefore, the condition determination unit 14 determines NO in S5 for these events, and proceeds to S6. The condition determination unit 14 sets unprocessed event ID1a “17:54:00”, ID4a, ID7a, ID4b, ID2b, ID6b, and ID5b to be processed. After S6 and S7, return to S3.

  In S3, no event is registered in the candidate for condition c and the candidate for condition d (S3 / NO). Event ID1a “17:54:00”, ID7a, ID4a, ID4b, ID6b, ID5b, and ID2b have been processed and there are no unprocessed events (S4 / NO). Unprocessed events (S8).

  Since the input event of ID8 does not include the areas a to d, the conditions a to d are not satisfied (S9 / NO). Therefore, the condition determination unit 14 does nothing for the event with ID8.

(Event input of ID1)
The data reading unit 13 reads the event of ID1 shown in the event table of FIG. 25 (S2). In FIG. 25, no event is registered in the candidate for condition c and the candidate for condition d. Therefore, there is no event where the difference between the event time registered in the condition c candidate or the condition d candidate and the current time “18:06:00” exceeds the unconditional timeout “40 seconds” ( S3 / NO).

  In FIG. 25, among the events registered for each candidate, event ID1a, ID7a, ID4a, ID2b, ID4b, ID5b, and ID6b are unprocessed events and are not connected by two sides of different types. It is an event. Therefore, there is an unprocessed event in S4 and an event (event ID1a, ID7a, ID4a, ID2b, ID4b, ID5b, ID6b) that is not connected on two different sides (S4 / YES). Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 25, as described in FIG. 24, unprocessed events ID1a, ID4a, ID7a, ID4b, ID2b, ID6b, and ID5b are not deletion events. Therefore, the condition determination unit 14 determines NO in S5 for these events, and proceeds to S6.

  The condition determination unit 14 processes the unprocessed events ID1a, ID7a, ID4a, ID2b, ID4b, ID5b, and ID6b (S6), and returns to S3. In S3, no event is registered in the candidate for condition c and the candidate for condition d (S3 / NO). Since event ID1a, ID7a, ID4a, ID2b, ID4b, ID5b, and ID6b have been processed and there are no unprocessed events (S4 / NO), the condition determination unit 14 unprocesses the processed event. (S8).

  Since the input event of ID1 includes areas c and d, conditions c and d are satisfied among conditions a to d (S9 / YES). Therefore, the condition determination unit 14 determines YES in S9, and newly registers the event with ID1 as a candidate for conditions c and d (S10).

  In the partner condition (condition a, d) of each inter-event condition (condition ac, condition cd) related to the event of ID1 newly registered as a candidate for condition c (event satisfying condition c), in the own condition (condition c) The preceding condition (condition a) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID1 newly registered as a candidate for condition c is referred to as event ID1c. Among events that satisfy the preceding condition (condition a) (events registered as candidates for condition a), events that relate to event ID1c and that satisfy the inter-event condition (for example, condition ac) that includes the preceding condition (event ID1a) Yes (S12 / YES). Here, the event that satisfies the inter-event condition a-c is the event ID 1a that satisfies the inter-event condition a-c (an event having the same ID as a time within 20 minutes from “18:06:00”).

  Therefore, the condition determination unit 14 determines YES in S12. Then, as shown in FIG. 26, the graph management unit 15 connects the event ID 1a that satisfies the inter-event condition and the newly registered event ID 1c with edges (see the alternate long and short dash line) (S14).

  The own condition (condition c) and partner condition (condition a or condition d) of any inter-event condition (condition ac or condition cd) related to event ID 1c are unrelated conditions (condition c and condition d) (S21 / YES).

  Among any of the unrelated conditions (condition c and condition d), the condition other than the condition related to the event ID 1c is the condition d. Then, no event registered as a candidate for condition d satisfies any inter-event condition (condition c-d or condition a-c) related to event ID 1c (S22 / NO). This is because the event registered as a candidate for condition d is the same as the event registered as a candidate for condition c.

  The partner condition (conditions a and d) of each inter-event condition (condition ac or condition cd) related to the event ID 1c does not include a subsequent condition (no condition) whose time follows the own condition (condition c) (S24). / NO).

  Accordingly, the condition determining unit 14 determines YES in S21, NO in S22, NO in S24, and proceeds to S25.

  Event ID 1c does not have two sides of different types (S25 / NO). Therefore, the condition determination unit 14 determines NO in S25, and proceeds to S2.

  Next, the process of S11 is executed for the event with ID1 newly registered as a candidate for condition d. In the partner condition (condition b, c) of each inter-event condition (condition bd or condition cd) related to the event with ID1 newly registered as a candidate for condition d (event satisfying condition d), in the own condition (condition c) The preceding condition (condition b) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID1 newly registered as a candidate for condition d is referred to as event ID1d. There is no event that satisfies the preceding condition (condition b) (the event registered as a candidate for condition b) that satisfies the inter-event condition including the preceding condition (for example, condition bd) related to event ID1d (S12 / NO). An event that satisfies the inter-event condition b-d is an event that satisfies the inter-event condition b-d (an event having the same ID and a time within 20 minutes from “18:06:00”).

  Therefore, the node deletion unit 16 determines NO in S12, and deletes the event ID 1d as shown in FIG. 27 (S13). This deletion is indicated by “x” in FIG. And it returns to S2.

(Event input of ID5)
The data reading unit 13 reads the event of ID5 shown in the event table of FIG. 28 (S2). In FIG. 28, event ID 1c is registered as a candidate for condition c. However, the difference between the current time “18:06:20” and the event ID 1c time “18:06:00” does not exceed the unconditional timeout “40 seconds” (S3 / NO).

  In FIG. 28, among the events registered for each candidate, event ID7a, ID4a, ID2b, ID4b, ID5b, ID6b, and ID1c are unprocessed events and are not connected by two sides of different types. It is an event. Therefore, there is an unprocessed event of S4 and an event (event ID7a, ID4a, ID2b, ID4b, ID5b, ID6b, ID1c) that is not connected on two different sides (S4 / YES). Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 28, as described in FIG. 24, unprocessed events ID1a, ID4a, ID7a, ID4b, ID2b, ID6b, and ID5b are not deletion events.

  The timeout period of the inter-event condition c-d including the condition c satisfied by the unprocessed event ID 1c as its own condition is 40 seconds. Since the current time is "18:06:20" and the time of the event registered in the condition c candidate is "18:06:00", the time-out described above among the events registered in the condition c candidate There is no event exceeding the time (40 seconds) (S5 / NO).

  Therefore, the condition determination unit 14 determines NO in S5 for these events, and proceeds to S6.

  The condition determination unit 14 processes the unprocessed events ID1a, ID7a, ID4a, ID2b, ID4b, ID5b, ID6b, and ID1c (S6), and returns to S3. In S3, the difference between the current time “18:06:20” and the time “18:06:00” of the event ID 1c does not exceed the unconditional timeout “40 seconds” (S3 / NO).

  Event ID1a, ID7a, ID4a, ID2b, ID4b, ID5b, ID6b, and ID1c are processed and there are no unprocessed events (S4 / NO), so the condition determination unit 14 does not process the processed event. (S8).

  Since the input event of ID5 includes areas c and d, conditions c and d are satisfied among conditions a to d (S9 / YES). Therefore, the condition determination unit 14 determines YES in S9, and newly registers the event ID5 as a candidate for conditions c and d (S10).

  In the partner condition (condition a, d) of each inter-event condition (condition ac or condition cd) related to the event of ID5 newly registered as a candidate for condition c (event satisfying condition c), in the own condition (condition c) The preceding condition (condition a) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID5 newly registered as a candidate for condition c is referred to as event ID5c. There is no event that satisfies the preceding condition (condition a) (the event registered as a candidate for condition a) that satisfies the inter-event condition including the preceding condition (for example, condition ac) related to event ID 5c (S12). / NO). An event that satisfies the inter-event condition a-c is an event that satisfies the inter-event condition a-c (an event having the same ID and a time within 20 minutes from “18:06:20”).

  Therefore, the node deletion unit 16 determines NO in S12, and deletes the event ID 5c as shown in FIG. 29 (S13). This deletion is indicated by “x” in FIG. And it returns to S2.

  Next, the process of S11 is executed for the event of ID5 newly registered as a candidate for condition d. In the partner condition (condition b, c) of each inter-event condition (condition bd, condition cd) related to the event of ID5 newly registered as a candidate for condition d (event satisfying condition d), in the own condition (condition d) The preceding condition (condition b) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID5 newly registered as a candidate for condition d is referred to as event ID5d. Among events that satisfy the preceding condition (condition b) (events registered as candidates for condition b), events that satisfy the inter-event condition including the preceding condition (for example, condition bd) related to event ID 5d (event ID 5b) Yes (S12 / YES). Here, the event that satisfies the inter-event condition b-d is the event ID 5b that satisfies the inter-event condition b-d (an event having the same ID and a time within 20 minutes from “18:06:20”).

  Therefore, the condition determination unit 14 determines YES in S12. Then, as shown in FIG. 30, the graph management unit 15 connects the event ID 5b that satisfies the inter-event condition and the newly registered event ID 5d with edges (see broken lines) (S14).

  The own condition (condition d) and partner condition (condition b or condition c) of any inter-event condition (condition bd or condition cd) related to event ID 5d are unrelated conditions (condition c and condition d) (S21 / YES).

  Among any of the unrelated conditions (condition c and condition d), the condition other than the condition related to the event ID 5d is the condition c. Among the events registered as candidates for the condition c, there is an event that satisfies any of the inter-event conditions (condition c-d or condition b-d) related to the event ID 1d (S22 / YES).

  An event that satisfies the inter-event condition c-d is an event having a time “18:06:20” within 40 seconds from the current time “18:06:20” and the same space “36”, 39 ”.

  Therefore, the condition determination unit 14 determines YES in S22. Then, as shown in FIG. 30, the graph management unit 15 connects the event ID 1c satisfying the inter-event condition and the newly registered event ID 5d with sides (see dotted lines) (S23).

  The partner condition (condition b, c) of each inter-event condition (condition bd or condition cd) related to the event ID 5d does not include the subsequent condition (no condition) in which the time follows the own condition (condition d) (S24). / NO).

  Therefore, the condition determination unit 14 determines NO in S24, and proceeds to S25. The event ID 5d has two sides of different types (see dotted line and broken line) (S25 / YES). Therefore, the condition determining unit 14 determines YES in S25, and proceeds to S26.

  As shown in FIG. 31, the output management unit 17 determines that the condition d satisfied by the newly registered event ID 5d has been processed (S26). In FIG. 31, “processed” is described below “d candidate”. Then, as shown in FIG. 31, the output management unit 17 registers the newly registered event ID5d as a candidate set (S26). In the following description, the illustrated character string “candidate set” corresponds to the candidate set 102f in the RAM 102 of FIG.

(Event output)
The event output will be described below. Here, unprocessed conditions are condition a, condition b, and condition c, that is, candidate conditions that are not “processed” are candidates for conditions a, b, and c. Therefore, the output management unit 17 determines that there is an unprocessed condition (S27 / YES), and as shown in FIG. 32, among the unprocessed conditions a, b, and c, the processed condition d and the event are processed. One of the conditions b and c satisfying the interval condition is set as the current event condition (for example, the condition c is the current event condition) (S28). In FIG. 32, “current event condition” is described above “c candidate”.

  In FIG. 31, the event of ID5 is registered as a candidate set, and the candidate set is not empty. Therefore, the output management unit 17 determines NO in S30, extracts one entry (event) from the candidate set, and registers the extracted entry (ID5 event) as the current candidate as shown in FIG. (S32). In the following description, the illustrated character string “current candidate” corresponds to the current candidate 102e in the RAM 102 of FIG.

  The output management unit 17 adds the related event related to the event registered in the current candidate and the event registered in the current candidate among the events registered in the current event condition to the new candidate set (S33). In the following description, the illustrated character string “new candidate set” corresponds to the new candidate set 102g in the RAM 102 of FIG.

  In the example of Fig. 33, among the events registered in the current event condition, event ID1c has two different types of sides (one-dot chain line, dotted line), and one side (dotted line) makes it the current candidate. This is an event connected to the registered event (event ID 5d) (S33). Therefore, the related event is event ID 1c.

  As shown in FIG. 33, the output management unit 17 adds the pair of the related event ID 1c and the event of the current candidate ID 5 to the new candidate set (S33), and returns to S30.

  In FIG. 33, since the candidate set is empty (S30 / YES), the output management unit 17 determines YES in S30. As shown in FIG. 34, the output management unit 17 moves the entry (ID1, ID5 event) of the new candidate set shown in FIG. 33 to the candidate set, processes the current event condition (S31), and proceeds to S27. Return. In FIG. 34, “processed” is indicated under “c candidates”.

  Here, unprocessed conditions are conditions a and b, that is, candidates for conditions that are not “processed” are candidates for conditions a and b. Therefore, the output management unit 17 determines that there is an unprocessed condition (S27 / YES). Then, as shown in FIG. 35, the output management unit 17 changes the processed condition (for example, condition d) and the condition b that satisfies the condition between events among the unprocessed conditions a and b to the current event condition (for example, Condition b) is set (S28).

  In FIG. 34, events of ID5 and ID1 are registered as candidate sets, and the candidate set is not empty. Accordingly, the output management unit 17 determines NO in S30, extracts one entry (ID1, ID5 event) from the candidate set, and registers the extracted entry as the current candidate as shown in FIG. S32).

  The output management unit 17 adds the related event and the event registered in the current candidate to the new candidate set (S33).

  In the example of FIG. 35, among the events registered in the current event condition, the event ID 5b has two different types (one-dot chain line and solid line). The event is connected to the event (event ID 5d) registered in the current candidate by one side (dashed line). Therefore, the related event is event ID 5b.

  As shown in FIG. 36, the output management unit 17 adds the pair of the related event ID 5b and the current candidate ID1 and ID5 event to the new candidate set (S33), and returns to S30.

  In FIG. 36, since the candidate set is empty (S30 / YES), the output management unit 17 determines YES in S30. As shown in FIG. 37, the output management unit 17 moves the entry (ID1, ID5, ID5 event) of the new candidate set shown in FIG. 36 to the candidate set, sets the current event condition as processed (S31), Return to S27. In FIG. 37, “processed” is indicated under “b candidate”.

  Here, an unprocessed condition is a condition a, that is, a candidate for a condition that is not “processed” is a candidate for condition a. Therefore, the output management unit 17 determines that there is an unprocessed condition (S27 / YES). Then, the output management unit 17 sets the unprocessed condition a as the current event condition (S28). In FIG. 38, “current event condition” is described above “a candidate”.

  In FIG. 37, events of ID5, ID1, and ID5 are registered as candidate sets, and the candidate set is not empty. Therefore, the output management unit 17 determines NO in S30, extracts one entry (ID1, ID5, ID5 event) from the candidate set, and registers the extracted one entry as the current candidate as shown in FIG. (S32).

  The output management unit 17 adds the related event and the event registered in the current candidate to the new candidate set (S33).

  In the example of FIG. 38, the number of events (three events) obtained by subtracting 1 from the number of all event conditions (conditions a to d) is registered as the current candidate 102e.

  In the example of FIG. 38, among the events registered in the current event condition, the event ID 1a has two different types of sides (one-dot chain line and a solid line). The event is connected to the event registered in the current candidate (event ID 1c) by one side (dashed line). Furthermore, the event is connected to the event registered in the current candidate (event ID 5b) by one side (solid line). That is, the event ID 1a is connected to the event registered in the current candidate on two different types of sides. Therefore, the related event is event ID 1a.

  As shown in FIG. 39, the output management unit 17 adds the pair of the related event ID 1a and the current candidate ID 1, ID 5, and ID 5 events to the new candidate set (S33), and returns to S30.

  In FIG. 39, since the candidate set is empty (S30 / YES), the output management unit 17 determines YES in S30. As shown in FIG. 40, the output management unit 17 moves the entry (ID1, ID1, ID5, ID5 event) of the new candidate set shown in FIG. 39 to the candidate set and sets the current event condition as processed (S31 ), Return to S27. In FIG. 40, “processed” is indicated under “candidate a”.

  Here, there is no unprocessed condition ("processed" is added to all condition candidates). Therefore, the output management unit 17 determines that there is no unprocessed condition (S27 / NO). Then, the output unit 18 outputs the candidate set entries (two ID1 events, two ID5 events), as shown in “Output” in FIG. 41 (S29). Finally, the output unit 18 unprocesses all condition candidates (S29). In FIG. 40, this unprocessed state is shown by deleting “processed” and “current event condition” in FIG.

(Event input of ID7)
The data reading unit 13 reads the event of ID7 shown in the event table of FIG. 42 (S2). In FIG. 42, event ID 1c is registered as a candidate for condition c. However, the difference between the current time "18:06:40" (or "18:06:39") and the event ID1c time "18:06:00" exceeds the unconditional timeout "40 seconds" (S3 / NO).

  In FIG. 42, event ID 5d is registered as a candidate for condition d. However, the difference between the event ID 5d time “18:06:20” and the current time “18:06:40” does not exceed the unconditional timeout “40 seconds” (S3 / NO).

  In FIG. 42, among the events registered in each candidate, event IDs 7a, ID4a, ID2b, ID4b, and ID6b are unprocessed events that are not connected by two different types of sides. Therefore, there is an unprocessed event in S4 and an event that is not connected between two different types of sides (S4 / YES). Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 42, as described in FIG. 24, unprocessed events ID1a, ID4a, ID7a, ID4b, ID2b, ID6b, and ID5b are not deletion events.

  There is no inter-event condition that does not satisfy the inter-event conditions a-c and c-d including the condition c satisfied by the unprocessed event ID 1c as its own condition (the unprocessed event ID 1c has two different types of sides). Furthermore, there is no inter-event condition that does not satisfy the inter-event conditions b-d and c-d including the condition d that the unprocessed event ID 5d satisfies as its own condition (the unprocessed event ID 5d has two different types of sides).

  Therefore, the condition determination unit 14 determines NO in S5 for these events, and proceeds to S6.

  The condition determination unit 14 processes the unprocessed events ID1a, ID7a, ID4a, ID2b, ID4b, ID5b, ID6b, ID1c, and ID5d (S6), and returns to S3. In S3, the difference between the current time “18:06:40” and the event ID 1c time “18:06:00” does not exceed the unconditional timeout “40 seconds” (S3 / NO).

  Since event ID1a, ID7a, ID4a, ID2b, ID4b, ID5b, ID6b, ID1c, and ID5d have been processed and there are no unprocessed events (S4 / NO), the condition determination unit 14 displays the processed event. Unprocessed (S8).

  Since the input event of ID7 includes areas c and d, conditions c and d are satisfied among conditions a to d (S9 / YES). Accordingly, the condition determining unit 14 determines YES in S9, and newly registers the event ID7 as a candidate for conditions c and d (S10).

  In the partner condition (condition b, c) of each inter-event condition (condition bd or condition cd) related to the event of ID7 newly registered as a candidate for condition d (event satisfying condition d), in the own condition (condition c) The preceding condition (condition b) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID7 newly registered as a candidate for condition d is referred to as event ID7d. Among the events that satisfy the preceding condition (condition b) (events registered as candidates for condition b), there is no event that satisfies the inter-event condition including the preceding condition (for example, condition bd) related to event ID 7d (S12 / NO). An event that satisfies the inter-event condition b-d is an event that satisfies the inter-event condition b-d (an event having the same ID and a time within 20 minutes from “18:06:40”).

  Therefore, the node deletion unit 16 determines NO in S12, and deletes the event ID 7d as shown in FIG. 43 (S13). This deletion is indicated by “x” in FIG. And it returns to S2.

  Next, the process of S11 is executed for the event with ID7 newly registered as a candidate for condition c. In the partner condition (condition a, d) of each inter-event condition (condition ac, condition cd) related to the event of ID7 newly registered as a candidate for condition c (event satisfying condition c), in its own condition (condition c) The preceding condition (condition a) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11. Hereinafter, an event with ID7 newly registered as a candidate for condition c is referred to as event ID7c.

  Among the events that satisfy the preceding condition (condition a) (events registered as candidates for condition a), the event that satisfies the inter-event condition including the preceding condition (for example, condition ac) related to event ID 7c (event ID 7a) Yes (S12 / YES). Here, the event that satisfies the inter-event condition a-c is the event ID 7a that satisfies the inter-event condition a-c (an event having the same ID and a time within 20 minutes from “18:06:40”).

  Therefore, the condition determination unit 14 determines YES in S12. Then, as shown in FIG. 43, the graph management unit 15 connects the event ID 7a that satisfies the inter-event condition and the newly registered event ID 7c with edges (see the alternate long and short dash line) (S14).

  The own condition (condition c) and partner condition (condition a or condition d) of any inter-event condition (condition ac or condition cd) related to event ID 7c are unrelated conditions (condition c and condition d) (S21 / YES).

  Among any of the unrelated conditions (condition c and condition d), the condition other than the condition related to the event ID 7c is the condition d. There is no event that satisfies any of the inter-event conditions (condition c-d or condition a-c) related to the event ID 7c among the events registered as candidates for the condition d (S22 / NO). This is because the space of the event registered as a candidate for condition d is different from the space of event ID 7c.

  The partner condition (conditions a and d) of each inter-event condition (condition ac or condition cd) related to event ID 7c does not include the subsequent condition (no condition) whose time follows the own condition (condition c) (S24). / NO). Accordingly, the condition determining unit 14 determines YES in S21, NO in S22, NO in S24, and proceeds to S25.

  Event ID 7c does not have two sides of different types (S25 / NO). Therefore, the condition determination unit 14 determines NO in S25, and proceeds to S2.

(Event input of ID6)
The data reading unit 13 reads the event of ID6 shown in the event table of FIG. 44 (S2). In FIG. 44, event ID1c and ID7c are registered as candidates for condition c. However, the difference between event ID1c time "18:06:00", event ID7c time "18:06:00", and current time "18:06:40" is the unconditional timeout "40 seconds" Is not exceeded (S3 / NO).

  In FIG. 44, among the events registered for each candidate, event ID1a, ID4a, ID2b, ID4b, ID6b, and ID7c are unprocessed events that are not connected on two different sides. is there. Therefore, there is an unprocessed event of S4 and an event (event ID1a, ID4a, ID2b, ID4b, ID6b, ID7c) that is not connected on two different sides (S4 / YES). Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 44, as described in FIGS. 24 and 42, unprocessed events ID1a, ID4a, ID7a, ID4b, ID2b, ID6b, ID5b, ID1c, and ID5d are not deletion events.

  The unprocessed event ID 1c has two different types of sides. Furthermore, the unprocessed event ID 5d has two different types of sides. Therefore, the unprocessed event ID 1c and the unprocessed event ID 5d are not deletion events.

  In addition, the unprocessed event ID 7c is connected to the event ID 1a by a side (dashed line). The timeout period of the inter-event condition c-d including the condition c satisfied by the unprocessed event ID 7c as its own condition is 40 seconds. The difference between the current time “18:06:40” and the unprocessed event ID 7c time “18:06:40” does not exceed the timeout time “40 seconds”.

  Therefore, the condition determination unit 14 determines NO in S5 for these events, and proceeds to S6.

  The condition determination unit 14 processes the unprocessed events ID1a, ID7a, ID4a, ID2b, ID4b, ID5b, ID6b, ID1c, ID7c, and ID5d (S6), and returns to S3. In S3, the difference between the current time “18:06:40” and the event ID 1c time “18:06:00” does not exceed the unconditional timeout “40 seconds” (S3 / NO).

  Since event ID1a, ID7a, ID4a, ID2b, ID4b, ID5b, ID6b, ID1c, ID7c, and ID5d have been processed and there are no unprocessed events (S4 / NO), the condition determination unit 14 has processed The event is unprocessed (S8).

  Since the input event of ID6 includes areas c and d, conditions c and d are satisfied among conditions a to d (S9 / YES). Accordingly, the condition determination unit 14 determines YES in S9, and newly registers the event of ID6 as a candidate for conditions c and d (S10).

  In the partner condition (condition a, d) of each inter-event condition (condition ac or condition cd) related to the event of ID6 newly registered as a candidate for condition c (event satisfying condition c), in the own condition (condition c) The preceding condition (condition a) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID6 newly registered as a candidate for condition c is referred to as event ID6c. Among the events that satisfy the preceding condition (condition a) (events registered as candidates for the condition a), there is no event related to the event ID 6c that satisfies the inter-event condition including the preceding condition (for example, the condition ac) (S12 / NO). An event that satisfies this inter-event condition a-c is an event that satisfies the inter-event condition a-c (an event having the same ID and a time within 20 minutes from “18:06:40”).

  Therefore, the node deletion unit 16 determines NO in S12, and deletes the event ID 6c as shown in FIG. 45 (S13). This deletion is indicated by “x” in FIG. And it returns to S2.

  Next, the process of S11 is executed for the event with ID6 newly registered as a candidate for condition d. In the partner condition (condition b, c) of each inter-event condition (condition bd, condition cd) related to the event of ID6 newly registered as a candidate for condition d (event satisfying condition d), in the own condition (condition d) The preceding condition (condition b) preceded by time is included (S11 / YES). Therefore, the condition determination unit 14 determines YES in S11.

  Hereinafter, an event with ID6 newly registered as a candidate for condition d is referred to as event ID6d. Among the events that satisfy the preceding condition (condition b) (events registered as candidates for condition b), the event that satisfies the inter-event condition including the preceding condition (for example, condition bd) related to event ID 6d (event ID 6b) Yes (S12 / YES). Here, the event that satisfies the inter-event condition b-d is the event ID 6b that satisfies the inter-event condition b-d (an event having the same ID and a time within 20 minutes from “18:06:40”).

  Therefore, the condition determination unit 14 determines YES in S12. Then, as shown in FIG. 45, the graph management unit 15 connects the event ID 6b satisfying the inter-event condition and the newly registered event ID 6d with sides (see broken lines) (S14).

  The own condition (condition d) and partner condition (condition b or condition c) of any inter-event condition (condition bd or condition cd) related to event ID 6d are unrelated conditions (condition c and condition d) (S21 / YES).

  Among any of the unrelated conditions (condition c and condition d), the condition other than the condition related to the event ID 6d is the condition c. Then, among the events registered as candidates for the condition c, there is an event that satisfies any event condition (condition c-d or condition b-d) related to the event ID 6d (S22 / YES).

  The event ID 1c satisfying the inter-event condition c-d is an event having a time “18:06:00” within 40 seconds from the current time “18:06:40” and the same space “36”, 39 ”.

  Therefore, the condition determination unit 14 determines YES in S22. Then, as shown in FIG. 45, the graph management unit 15 connects the event ID 1c that satisfies the inter-event condition and the newly registered event ID 6d with edges (see dotted lines) (S23).

  The partner condition (condition b, c) of each inter-event condition (condition bd or condition cd) related to the event ID 6d does not include a subsequent condition (no condition) whose time follows the own condition (condition d) (S24). / NO).

  Therefore, the condition determination unit 14 determines NO in S24, and proceeds to S25. The event ID 6d has two types of different types (see dotted line and broken line) (S25 / YES). Therefore, the condition determining unit 14 determines YES in S25, and proceeds to S26.

  As shown in FIG. 46, the output management unit 17 determines that the condition d satisfied by the newly registered event ID 6d has been processed (S26). In FIG. 46, “processed” is described under “d candidate”. Then, as shown in FIG. 46, the output management unit 17 registers the newly registered event ID6d as a candidate set (S26).

(Event output)
The event output will be described below. Here, unprocessed conditions are condition a, condition b, and condition c, that is, candidate conditions that are not “processed” are candidates for conditions a, b, and c. Therefore, the output management unit 17 determines that there is an unprocessed condition (S27 / YES), and as shown in FIG. 47, among the unprocessed conditions a, b, and c, the processed condition d and the event are processed. One of the conditions b and c satisfying the interval condition is set as the current event condition (for example, the condition c is the current event condition) (S28). In FIG. 47, “current event condition” is described above “c candidate”.

  In FIG. 46, an event with ID6 is registered as a candidate set, and the candidate set is not empty. Therefore, the output management unit 17 determines NO in S30, extracts one entry (event) from the candidate set, and registers the extracted one entry (ID6 event) as the current candidate as shown in FIG. (S32).

  The output management unit 17 adds the related event related to the event registered in the current candidate and the event registered in the current candidate among the events registered in the current event condition to the new candidate set (S33).

  In the example shown in Fig. 48, among the events registered in the current event condition, event ID 1c has two sides of different types (one-dot chain line, dotted line), and one side (dotted line) makes it the current candidate. This is an event connected to the registered event (event ID 6d) (S33). Therefore, the related event is event ID 1c.

  As shown in FIG. 48, the output management unit 17 adds the set of the related event ID 1c and the event of the current candidate ID 6 to the new candidate set (S33), and returns to S30.

  In FIG. 48, since the candidate set is empty (S30 / YES), the output management unit 17 determines YES in S30. As shown in FIG. 49, the output management unit 17 moves the entry (ID1, ID6 event) of the new candidate set shown in FIG. 48 to the candidate set, processes the current event condition (S31), and moves to S27. Return. In FIG. 49, “processed” is indicated under “c candidates”.

  Here, unprocessed conditions are conditions a and b, that is, candidates for conditions that are not “processed” are candidates for conditions a and b. Therefore, the output management unit 17 determines that there is an unprocessed condition (S27 / YES). Then, as shown in FIG. 50, the output management unit 17 changes the processed condition (for example, condition d) and the condition b that satisfies the inter-event condition among the unprocessed conditions a and b to the current event condition (for example, Condition b) is set (S28).

  In FIG. 49, ID6 and ID1 events are registered as candidate sets, and the candidate set is not empty. Therefore, the output management unit 17 determines NO in S30, extracts one entry (event of ID1, ID6) from the candidate set, and registers the extracted entry as the current candidate as shown in FIG. S32).

  The output management unit 17 adds the related event and the event registered in the current candidate to the new candidate set (S33).

  In the example of FIG. 50, among the events registered in the current event condition, the event ID 6b has two different types of sides (broken line and solid line). The event is connected to the event registered in the current candidate (event ID 6d) by one side (broken line). Therefore, the related event is event ID 6b.

  As shown in FIG. 51, the output management unit 17 adds the set of the related event ID 6b and the events of the current candidate ID1 and ID6 to the new candidate set (S33), and returns to S30.

  In FIG. 51, since the candidate set is empty (S30 / YES), the output management unit 17 determines YES in S30. As shown in FIG. 52, the output management unit 17 moves the entry (ID1, ID6, ID6 event) of the new candidate set shown in FIG. 51 to the candidate set, sets the current event condition as processed (S31), Return to S27. In FIG. 52, “processed” is indicated under “b candidate”.

  Here, an unprocessed condition is a condition a, that is, a candidate for a condition that is not “processed” is a candidate for condition a. Therefore, the output management unit 17 determines that there is an unprocessed condition (S27 / YES). Then, the output management unit 17 sets the unprocessed condition a as the current event condition (S28). In FIG. 53, “current event condition” is described above “a candidate”.

  In FIG. 52, events of ID6, ID1, and ID6 are registered as candidate sets and are not empty. Therefore, the output management unit 17 determines NO in S30, extracts one entry (ID1, ID6, ID6 event) from the candidate set, and registers the extracted one entry as the current candidate as shown in FIG. (S32).

  The output management unit 17 adds the related event and the event registered in the current candidate to the new candidate set (S33).

  In the example of FIG. 53, there is no related event among the events registered in the current event condition. The reason will be described below. In the example of FIG. 53, the number of events (three events) obtained by subtracting 1 from the number of all event conditions (condition a to condition d) are registered as current candidates. Of the events registered in the current event condition, there are no events connected to the event registered in the current candidate on two sides of different types. Therefore, there are no related events. Therefore, as shown in FIG. 53, the output management unit 17 does not execute the process of adding to the new candidate set (non-execution of S33) and returns to S30.

  In FIG. 54, since the candidate set is empty (S30 / YES), the output management unit 17 determines YES in S30. The output management unit 17 moves the entry of the new candidate set shown in FIG. 54 (empty in FIG. 54) to the candidate set, processes the current event condition (S31), and returns to S27. In FIG. 54, “processed” is described below “a candidate”.

  Here, there is no unprocessed condition. That is, there is no candidate for a condition that is not “processed” (“processed” is assigned to all candidate conditions). Therefore, the output management unit 17 determines that there is no unprocessed condition (S27 / NO). Then, the output unit 18 outputs the entries of the candidate set as shown in “Output” in FIG. 55 (S30). In the example of FIG. 55, the candidate set is empty, so nothing is output. Finally, the output unit 18 unprocesses all candidate conditions (S30). In FIG. 55, this unprocessed state is shown by deleting “processed” and “current event condition” in FIG.

(Event input of ID8)
The data reading unit 13 reads the event of ID8 shown in the event table of FIG. 56 (S2).

  In FIG. 56, event ID1c and ID7c are registered as candidates for condition c. The difference between the current time "18:14:10", event ID1c time "18:06:00", and event ID7c time "18:06:00" exceeds the unconditional timeout "40 seconds" Yes (S3 / YES).

  Further, in FIG. 56, event IDs 5d and ID6d are registered as candidates for the condition d. The difference between event ID 5d time "18:06:20", event ID 6d time "18:06:40", and current time "18:14:10" exceeds the unconditional timeout "40 seconds" (S3 / NO). Events ID1c, ID7c, ID5d, and ID6d including the time exceeding the unconditional timeout “40 seconds” are events to be deleted.

  Therefore, the condition determination unit 14 determines YES in S3. Then, as shown in FIG. 56, the node deletion unit 16 deletes the event IDs 1c, ID7c, ID5d, and ID6d to be deleted and the edge connected to the event to be deleted (S7). In FIG. 56, this deletion is indicated by a cross mark. Further, the node deletion unit 16 unprocesses the event IDs 1a, ID7a, ID5b, and ID6b connected to the event to be deleted on the side (S7). And it returns to S3.

  There is no event registered as a candidate condition for which an unconditional timeout is set (S3 / NO). Furthermore, there is an event (for example, event ID 1a) that is not connected between two different types of sides. Accordingly, the condition determination unit 14 determines NO in S3, YES in S4, and proceeds to S5.

  In FIG. 57, the timeout time of the inter-event condition a-c that does not satisfy the inter-event conditions a-b and a-c including the condition a that the unprocessed event ID 1a, ID 4a, ID 7a satisfies as its own condition is 20 minutes. Further, the timeout period of the inter-event condition b-d that does not satisfy the inter-event conditions a-b and b-d including the condition b satisfying the unprocessed event ID 4b, ID 2b, ID 6b, and ID 5b as its own condition is 20 minutes.

  The current time is "18:14:10", the unprocessed event ID1a and ID7a registered in the condition a candidate is "17:54:00", the unprocessed event ID1a, ID4a, ID7a, ID4b, The times of ID2b, ID6b, and ID5b are “17:54:10” or “17:54:20”. Therefore, among these unprocessed events, the events exceeding the timeout time (20 minutes) are unprocessed events ID1a and ID7a. In other words, the difference between the current time “18:14:10” and the time “17:54:00” of the unprocessed events ID1a and ID7a exceeds the timeout time (20 minutes). Therefore, these unprocessed event IDs 1a and ID7a are deletion events (S5 / YES).

  On the other hand, unprocessed events other than the deletion event are event ID4a, ID4b, ID2b, ID6b, and ID5b (S5 / NO). The condition determination unit 14 determines that the unprocessed events ID4a, ID4b, ID2b, ID6b, and ID5b other than the deletion event have been processed (S6). Next, as shown in FIG. 57, the node deletion unit 16 deletes the event IDs 1a and ID7a to be deleted and the edge connected to the event to be deleted (S7). Further, the node deletion unit 16 unprocesses the event IDs 2b, ID4b, ID5b, and ID6b connected to the event to be deleted on the side (S7). And it returns to S3.

  FIG. 58 will be described. There is no event registered as a candidate condition for which an unconditional timeout is set (S3 / NO). Furthermore, there is an event (for example, event ID 4b, ID 6b) that is not connected between two different types (S4 / YES).

  The node deletion unit 16 sets the event IDs 4b and ID6b as unprocessed events having no edges by deleting the edges. The difference between the current time "18:14:10" and the event ID4b and ID6b times "17:54:10" and "17:54:20" exceeds the timeout time "40 seconds" of the inter-event condition ab ing. Therefore, the node deletion unit 16 deletes the event IDs 4b and ID6b as shown in FIG. 58 (S7).

  As described above, according to the present embodiment, it is possible to determine in real time whether an event stored in the RMA 101 satisfies the condition.

[Second Embodiment]
Next, an information processing apparatus that outputs a determination result indicating that a predetermined condition is satisfied earlier than in the first embodiment will be described.

(Hardware block diagram of information processing device)
FIG. 59 is an example of a block diagram illustrating a hardware configuration of the information processing apparatus 2 according to the second embodiment. The information processing apparatus 2 in FIG. 59 has the same configuration as the information processing apparatus 1 in FIG. The output candidate 102h of the RAM 102 will be described later.

  The storage 103 stores an execution file of the real-time processing software SF2. When the information processing apparatus 2 is activated, the CPU 101 reads the execution file of the real-time processing software SF2 from the storage 103, expands it in the RAM 102, and executes in real time whether or not the event satisfies a predetermined condition. Note that this execution file may be stored in the external storage medium MD.

(Software block diagram of information processing device)
FIG. 60 is an example of a block diagram illustrating the software configuration of the information processing apparatus 2 in FIG.

  The real-time processing software SF2 includes an output condition setting unit 21 and a combined flag update unit 22 in addition to the units described in the real-time processing software SF1 in FIG. The output condition setting unit 21 reads out the output time set in advance by the administrator or the like in the storage 103 and inputs it to the output management unit 17. The output time will be described with reference to FIG. When the registered event satisfies the inter-event condition related to this event, the combined flag update unit 22 sets a combined flag for this event (hereinafter referred to as “set” as appropriate), and notifies the RAM 102. To remember.

  Also in the second embodiment, the data reading unit 13 sequentially receives the events described in the first embodiment. Then, the information processing apparatus 2 performs tracking detection described in the first embodiment.

(Event registration, connection by different event sides, and flag setting)
FIG. 61 is a diagram for explaining event registration, connection by different event sides, and flag setting. As described with reference to FIG. 6, the condition determination unit 14 of the information processing device 2 stores the contents of the event in the RAM 102 together with the registered event when registering the event. Furthermore, when the two events satisfy the inter-event condition set in advance corresponding to these events, the condition determination unit 14 stores that fact in the RAM 102.

  Further, when the registered event satisfies the inter-event condition related to this event, the combined flag update unit 22 sets a combined flag for this event, and stores this in the RAM 102.

  For example, when the combination flag update unit 22 sets the combination flag FLG1 in the event E5 registered as a candidate for the condition d, the combination flag update unit 22 stores the fact in the RAM 102. In FIG. 61, the combination flag FLG1 is indicated by a circle in the upper left corner of the event E5. As shown in the content EI5 of the event E5, the combination flag update unit 22 stores in the RAM 102 that the combination flag FLG1 is set in the event E5 as “combination flag: 1”. When the combination flag is not set in the event, the fact is stored in the RAM 102 as “combination flag: 0”.

  When outputting an event, the output unit 18 sets an identifier indicating that the event has been output (hereinafter referred to as an “output flag” as appropriate), and stores the fact in the RAM 102. For example, when the output unit 18 outputs an event E5 registered as a candidate for the condition d, the output unit 18 stores the fact in the RAM 102.

  In FIG. 61, “completed” is shown at the lower left of the event, and the output flag FLG2 is shown. As shown in the content EI5 of the event E5, the output unit 18 stores the fact that the output flag FLG2 is set in the event E5 as “output flag: 1” in the RAM 102. When the output flag is not set in the event, the fact is stored in the RAM 102 as “output flag: 0”.

  Thereafter, the output unit 18 does not execute the output of the event for which the output completion flag is set. This non-execution of the output prevents duplicate events from being output, so that the administrator can easily see the output events displayed on the screen.

  Next, deletion of the combination flag will be described. Hereinafter, the combination flag update unit 22 sets three combination flags. Note that these set of combination flags are not shown in FIG. 6 from the viewpoint of the space of the drawing.

  First, the combination flag update unit 22 combines the first storage event when the first storage event (for example, event E1) satisfies the condition a and the first and second inter-event conditions ab and ac. Set the flag.

  Second, the combination flag update unit 22 combines the second storage event when the second storage event (for example, event E3) satisfies the condition b and the first and fourth inter-event conditions ab and bd. Set the flag.

  Third, the combination flag update unit 22 combines the third storage event when the third storage event (for example, event E5) satisfies the condition d and the third and fourth inter-event conditions bd and cd. Set the flag.

  Then, the combination flag update unit 22 adds the time of the event satisfying the condition c and the third and fourth inter-event conditions bd and cd to the time of the event and the third inter-event condition cd. If it is not stored in the RAM 102 even after the reference time has elapsed, the following processing is performed. That is, the combination flag update unit 22 deletes the combination flags set in the first, second, and third storage events in a chain manner.

  By deleting this flag, an event that does not have the possibility of satisfying all the predetermined conditions described in the first embodiment is not executed. This reduces the output processing load and reduces the CPU load factor.

  Here, the output management unit 17 determines that the difference between the reference time corresponding to the current time and the time of the stored event that satisfies the event condition (for example, condition a) and the event condition (for example, event condition ab), It is determined whether or not the output time (for example, 10 minutes) determined in accordance with the event condition satisfied by the stored event is exceeded, and if the output time is exceeded, the determination result is output.

  This determination result is, for example, the storage event. According to this output process, before performing the determination of the fifth determination described in the first embodiment, it is possible to quickly output an event that satisfies at least two inter-event conditions.

  The output event does not completely specify the detection target in tracking detection (the probability of being a detection target in tracking detection is high). However, the information processing apparatus 2 can output an event having a high probability of being a detection target in tracking detection at high speed.

  Here, the aforementioned output time is a time determined corresponding to the event condition. The output time has, for example, the following three output times. The first output time is a time “10 minutes” determined corresponding to the conditions a and b. The second output time is a time “30 seconds” determined in accordance with the condition c. The third output time is a time “0 second” determined in accordance with the condition d.

(Flow diagram)
62 to 66 are first to fifth flowcharts for explaining real-time output of events described in the second embodiment.

  Each step of S2 to S14 in the flowchart of FIG. 62 is the same as S2 to S14 described in the flowchart of FIG. In FIG. 62, the condition reading unit 11 executes the processing described in FIG. 7 (S1 ′). Further, the output condition setting unit 21 reads out the output time previously set by the administrator or the like in the storage 103 and inputs it to the output management unit 17 (S1 '). Note that the output time is stored in the storage 103 in, for example, a text format. Next, after S1 'ends, the process proceeds to S2, and when the event reception (S2) ends, the process proceeds to S41 in FIG.

  S41 of FIG. 64 (A): The output management unit 17 determines that the difference between the current time and the time of the event registered in the output candidate 102h (the event of the output candidate) satisfies the condition that the event of the output candidate 102h satisfies. It is determined whether the output time is longer than the corresponding time.

  When the event of the output candidate 102h is registered as a candidate of the condition a and the condition b, the output time of the event of the output candidate 102h is “10 minutes” defined for the condition a and the condition b. . When the event of the output candidate 102h is registered as the candidate of the condition c, the output time of the event of the output candidate 102h is the time “30 seconds” determined corresponding to the condition c. When the event of the output candidate 102h is registered as a candidate of the condition d, the output time of the event of the output candidate is a time “0 second” determined in accordance with the condition d.

  If YES in S41, the process moves to S42. If NO in S41, the process moves to S3 in FIG.

  S42: The output unit 18 outputs an event of the output candidate 102h having a time longer than the output time, and deletes the output event from the output candidate 102h. After S42, the process proceeds to S3 in FIG. The process of S3 in FIG. 62 is executed to reach S7. After the completion of S7, the process proceeds to S51 in FIG. 64 (B).

  S51 in FIG. 64 (B): The join flag update unit 22 sets a join flag for an unprocessed event for which the join flag is set and a connection event connected by the same type of edge as the deleted edge. Judge whether it is.

  When there is no connection event (S51 / YES), or when the connection flag is not set in the connection event (S51 / YES), the process proceeds to S52. When there is no unprocessed event for which the join flag is set (S51 / NO), or when there is a connection event and the join flag is set for the connection event (S51 / NO), S3 in FIG. Move on.

  S52: The combination flag update unit 22 deletes the combination flag from an unprocessed event (hereinafter referred to as a flag deletion event) for which the combination flag is set. Then, the combination flag update unit 22 performs the process of S53 on the event that is connected to the flag deletion event and the side (hereinafter referred to as the reference side) and the combination flag is set.

  S53: The combination flag update unit 22 determines whether a combination flag is set for an event for which the combination flag is set and a connection event connected by the same type of side as the reference side.

  When there is no connection event (S53 / YES), or when the connection flag is not set in the connection event (S53 / YES), the process returns to S52. When returning to S52, the event for which the combination flag is set in S52 becomes the flag deletion event. If there is a connection event and the join flag is set in the connection event (S51 / NO), do nothing.

  Thereafter, the combination flag update unit 22 moves to S3 in FIG. 62 after completing the processing from S51 on all unprocessed events for which the combination flag is set.

  In FIG. 62, if NO is determined in S11, or after the end of S14, the process proceeds to S21 in FIG. Then, the process of S21 is executed to reach S25, and if YES is determined in S25, the process proceeds to S61 in FIG.

  S61 in FIG. 65: The combined flag update unit 22 sets the combined flag in the newly registered event, and executes the processing from S62 on all the events that are connected to the newly registered event at the side and have no combined flag. .

  S62: The combined flag update unit 22 determines whether an event without a combined flag in S61 or S63 described later (referred to as a target event as appropriate in S62 and S63) satisfies an inter-event condition related to the target event.

  Specifically, the combination flag update unit 22 determines whether the target event has two different types of sides. If YES in S62, the process moves to S63. If NO in S62, the process moves to S64.

  S63: The combination flag update unit 22 sets a combination flag for the target event, and executes the process of S62 for all events that are connected to the event for which the combination flag is set and which has no combination flag. In execution of the processing of S62 (returning to S62), an event for which the combination flag is not set is a target event.

  S64: The combination flag update unit 22 shifts to a wait state until all the combination flag setting processes are completed. The combination flag update unit 22 proceeds to S65 when all the set processes are completed.

  S65: The combined flag update unit 22 explained in S62 and S64, the event for which the combined flag was not finally set, or the event in which the combined flag was deleted as described in S67 (hereinafter referred to as a reference event) The process of S66 is executed for an event that is connected at the edges and for which the combination flag is set (hereinafter referred to as a flag deletion event).

  Here, the combination flag updating unit 22 proceeds to S71 when the processing of S65 and subsequent steps is completed for all the reference events. If there is no flag deletion event, the combined flag update unit 22 does not execute the process from S66 onward, and executes the process from S65 on for other reference events.

  S66: The combined flag update unit 22 determines whether there is an event that is connected to the flag deleted event on the same type of side as the side to which the flag deleted event and the reference event are connected, and the combined flag is set. If there is no such event (S66 / YES), the process proceeds to S65.

  S67: The combination flag update unit 22 deletes the combination flag set in the flag deletion event. Then, the process returns to S65.

  When returning to S65, in S65, the flag deletion event in which the combined flag is deleted in S67 becomes the reference event. When the process returns to S66, in S66, an event that is connected to the reference event at the side and in which the combination flag is set becomes a flag deletion event. If NO in S66, the process proceeds to S71 in FIG.

  S71 in FIG. 63: The output management unit 17 determines whether or not the combination flag is set in the newly registered event. If NO in S71, the process moves to S2 in FIG. If YES in S71, the process moves to S26. The process of S26 is executed to reach S28, and after the end of S28, the process proceeds to S72.

  S72: The output management unit 17 determines whether all events registered as the candidate set 102f have been processed. If YES in S72, the process moves to S76. If NO in S72, the process moves to S73.

  S73: The output management unit 17 registers the unprocessed event of the candidate set 102f as the current candidate 102e in the RAM 102, and sets this unprocessed event as processed.

  S74: The output management unit 17 executes the output processing flow (see FIG. 66) for the event registered as the current candidate 102e. The event in S74 is an output target event described in the output processing flow.

  S75: The output management unit 17 sets, as new candidates, events that are connected to the events registered in the candidate set 102f and whose edges are connected among the events registered in the current event condition. It is additionally registered in the set 102g.

  S76: The output management unit 17 sets the entry of the new candidate set 102g as the candidate set 102f and further processes the current event condition. Then, the process returns to S27. If NO in S27, the process moves to S77.

  S77: The output management unit 17 executes an output process flow (see FIG. 66) for an unprocessed event registered in the candidate set 102f. The event in S77 is an output target event described in the output processing flow.

  S78: The output management unit 17 unprocesses all condition candidates and deletes (also called clear) the event registered in the candidate set 102f. Then, the process returns to S2 of FIG.

  Next, the output processing flow described in S74 and S77 will be described with reference to FIG.

  S81 in FIG. 66: The output management unit 17 determines whether the event to be output has already been output. If YES in S81, the output processing flow ends. If NO in S81, the process moves to S82.

  S82: The output management unit 17 determines that the difference between the current time and the time of the event to be output corresponds to a condition related to the event to be output (in other words, a condition that the event to be output satisfies). It is determined whether the output time is longer than specified. Here, the output time determined corresponding to the conditions a and b satisfied by the event to be output is 10 minutes. The output time determined corresponding to the condition c satisfied by the event to be output is 30 seconds. The output time determined corresponding to the condition d satisfied by the event to be output is 0 seconds.

  If YES in S82, the process moves to S83. If NO in S82, the process moves to S84.

  S83: The output unit 18 outputs an event to be output and assumes that the output event has already been output.

  S84: The output management unit 17 additionally registers the event to be output as an output candidate 102h in the RAM 102.

(Specific example of the second embodiment)
67 to 98 are first to thirty-second diagrams for explaining specific examples in the second embodiment. As described with reference to FIGS. 9 to 30 in the first embodiment, events are sequentially input to the information processing apparatus 2, and the steps of the flowcharts of FIGS. 62 to 64 are executed.

  When the processing described with reference to FIGS. 9 to 23 is executed, as described with reference to FIG. 24, the node deletion unit 16 performs event ID1a “17:54:20”, ID2a, ID6a, and ID5a in FIG. S5 determines YES and deletes these events (S7). Next, the process proceeds to S51. Here, since there is no unprocessed event for which the combination flag is set (S51 / NO), the combination flag update unit 22 proceeds to S3 in FIG. Thereafter, the processes described in FIG. 24 are executed. Then, as described with reference to FIGS. 25 to 30, events are sequentially input, and each step of the flowcharts of FIGS. 62 to 64 is executed.

  9 to 30, since no event is registered in the output candidates, after receiving the event (S2), the output management unit 17 determines NO in S41, and proceeds to S3.

(Event input of ID5)
As described with reference to FIG. 28 in the first embodiment, the data reading unit 13 reads the event of ID5 (S2). The information processing apparatus 2 executes each step described in FIG. 29 and FIG. 30, and the graph management unit 15 connects the newly registered event ID 5d and the event ID 5b with edges (see broken lines) as shown in FIG. (S14).

  Next, the information processing apparatus 2 executes each step described in FIG. 29 and FIG. Then, as shown in FIG. 67, the graph management unit 15 connects the newly registered event ID 5d and the event ID 1c with edges (see dotted lines) (S23). The partner condition (condition b, c) of each inter-event condition (condition bd or condition cd) related to the event ID 5d does not include the subsequent condition (no condition) in which the time follows the own condition (condition d) (S24). / NO). Therefore, the condition determination unit 14 determines NO in S24, and proceeds to S25. The newly registered event ID 5d has two types of different types (see dotted line and alternate long and short dash line) (S25 / YES). Therefore, the condition determining unit 14 determines YES in S25, and proceeds to S61. As shown in FIG. 67, the combination flag update unit 22 sets a combination flag in the new registration event ID 5d (S61). In the following description, the combination flag is schematically indicated by a circle.

  The combined flag update unit 22 executes the processes of S62 and S63 for two event IDs 1c and ID5b (target events) that are connected to the newly registered event ID 5d on the side and have no combined flag.

  The target event ID 1c has two different types of sides (a dotted line side and a one-dot chain line side). The target event ID 5b has two different types of sides (solid line side, broken line side). Accordingly, the combination flag update unit 22 determines YES in S62, sets the combination flag in the target events ID1c and ID5b as shown in FIG. 68 (S63), and returns to S62.

  The combined flag update unit 22 executes the processing of S62 and S63 for two event IDs 1a and ID4a (target events) that are connected by an edge to the event ID 5b for which the combined flag is set and that have no combined flag. The target event ID 1a has two different types of sides (solid line side and one-dot chain line side). Therefore, the combined flag update unit 22 determines YES in S62 for the target event ID 1a, sets the combined flag in the target event ID 1a as shown in FIG. 69 (S63), and returns to S62. On the other hand, the target event ID 4a does not have two different types of sides. Therefore, the combination flag update unit 22 determines NO in S62 for the target event ID 4a, and proceeds to S64.

  In addition, there is no event that is connected to the target event ID 1c at the side and does not have a join flag. Therefore, the combination flag update unit 22 determines NO in S62 for the target event ID 1c, and proceeds to S64. Since all the combination flag setting processes have been completed, the process proceeds from the wait state (S64) to S65. In the above description, events (reference events) for which the combination flag is not finally set are event IDs 4a and ID4b.

  The combination flag update unit 22 executes the process of S66 on the event ID 5b (flag deletion event ID 5b) that is connected to the reference event ID 4a by a side (solid line) and for which the combination flag is set.

  There is an event ID 1a that is connected to the flag deletion event 5b on the side of the same type (solid line) as the side to which the flag deletion event ID 5b and the reference event ID 4a are connected, and in which the combined flag is set. Therefore, the combination flag update unit 22 determines NO in S66.

  The combination flag update unit 22 executes the process of S66 on the event ID 1a (flag deletion event ID 1a) that is connected to the reference event ID 4b by a side (solid line) and for which the combination flag is set.

  There is an event ID 5b that is connected to the flag deletion event ID 1a on the side of the same type (solid line) as the side to which the flag deletion event ID 1a and the reference event ID 4b are connected, and the combined flag is set. Therefore, the combination flag update unit 22 determines NO in S66. Since the combination flag update unit 22 has finished the processes of S65 to S67 for all the reference events, the process proceeds to S71.

  The newly registered event ID 5d has a combined flag as shown in FIG. Accordingly, the output management unit 17 determines YES in S71, and sets the condition d satisfied by the newly registered event ID 5d as shown in FIG. 70 (S26). Then, as illustrated in FIG. 70, the output management unit 17 registers the newly registered event ID 5d as a candidate set (S26).

  Unprocessed conditions are condition a, condition b, and condition c, that is, candidates for conditions that are not “processed” are candidates for conditions a, b, and c. Therefore, the output management unit 17 determines that there is an unprocessed condition (S27 / YES). Then, as shown in FIG. 71, the output management unit 17 sets one of the unprocessed conditions a, b, and c as the current event condition that satisfies the processed condition d and the condition between events. (For example, condition c is the current event condition) (S28).

  All events registered as a candidate set have not been processed (S72 / NO). Accordingly, the output management unit 17 determines NO in S72, registers the unprocessed event ID 5d of the candidate set as the current candidate, and sets the unprocessed event ID 5d to be processed as shown in FIG. 71 (S73 ). This processing is indicated by attaching “done” to the event in the candidate set.

  Here, the event ID 5d registered as the current candidate is the event to be output. The output management unit 17 executes the output processing flow for the event ID 5d registered as the current candidate. The event ID 5d to be output has not been output. Therefore, the output management unit 17 determines NO in S81, and proceeds to S82.

  The difference between the current time “18:06:20” and the time “18:06:20” of the event ID 5d to be output is the output time determined according to the condition d that the event ID 5d to be output satisfies. 0 seconds "or more (S82 / YES). Therefore, the output management unit 17 determines YES in S82, and outputs the output target event ID 5d as shown in FIG. 72 and assumes that it has been output (S83). This output has been indicated by adding "Done" to event ID 5d.

  As shown in FIG. 73, the event registered in the current event condition (condition c) is event ID 1c. The event ID 1c has a combined flag set, and is connected to the event ID 5d registered in the candidate set by an edge (see dotted line). Therefore, the output management unit 17 registers the event ID 1c in the new candidate set as shown in FIG. 73 (S75). Then, the process returns to S72.

  All event IDs 5d registered as a candidate set have been processed (S72 / YES). Therefore, as shown in FIG. 74, the output management unit 17 moves the entry (ID1 event) of the new candidate set shown in FIG. 73 to the candidate set and sets the current event condition (condition c) to the processed state (S76 ), Return to S27.

  Unprocessed conditions are condition a and condition b, that is, candidate conditions that are not “processed” are candidate conditions a and b. Therefore, the output management unit 17 determines that there is an unprocessed condition (S27 / YES). Then, as shown in FIG. 75, the output management unit 17 sets the processed event condition (for example, condition d) and the condition condition that satisfies the inter-event condition among the unprocessed conditions a and b, for example, the current event condition (for example, Condition b) is set (S28).

  All events registered as a candidate set are event IDs 1c and ID5d. Event ID 5d has been processed, and event ID 1c has not been processed.

  Accordingly, the output management unit 17 determines NO in S72, registers the unprocessed event ID 1c of the candidate set as the current candidate, and sets the unprocessed event ID 1c as processed (S73), as shown in FIG. ).

  Here, the event ID 1c registered as the current candidate is the event to be output. The output management unit 17 executes the output processing flow for the event ID 1c registered as the current candidate (S74). The event ID 1c to be output has not been output. Therefore, the output management unit 17 determines NO in S81, and proceeds to S82.

  The difference between the current time "18:06:20" and the time "18:06:00" of the event ID 1c to be output is the output time determined according to the condition c that the event ID 1c to be output satisfies. It is not more than 30 seconds "(S82 / NO). Therefore, the output management unit 17 determines NO in S82, and registers the event ID 1c to be output as an output candidate as shown in FIG. 76 (S84).

  As shown in FIG. 77, the events registered in the current event condition (condition b) are event ID2b, ID4b, ID5b, and ID6b. The event ID 5b has a combination flag set, and is connected to the event ID 5d registered in the candidate set by an edge (see a broken line). Accordingly, the output management unit 17 registers the event ID 5b in the new candidate set as shown in FIG. 77 (S75). Then, the process returns to S72.

  All event IDs 5d and ID1c registered as a candidate set have been processed (S72 / YES). Therefore, as shown in FIG. 78, the output management unit 17 moves the entry (ID5 event) of the new candidate set shown in FIG. 77 to the candidate set and sets the current event condition (condition b) to the processed state (S76 ), Return to S27.

  An unprocessed condition is a condition a, that is, a candidate for a condition that is not “processed” is a candidate for condition a. Therefore, the output management unit 17 determines that there is an unprocessed condition (S27 / YES). Then, as shown in FIG. 79, the output management unit 17 sets the processed condition (for example, condition b) and the condition a that satisfies the inter-event condition as the current event condition (S28).

  All events registered as a candidate set are event ID1c, ID5d, and ID5b. Event IDs 5d and ID1c have been processed, and event ID 5b has not been processed.

  Accordingly, the output management unit 17 determines NO in S72, registers the unprocessed event ID 5b of the candidate set as the current candidate, and sets the unprocessed event ID 5b as processed as shown in FIG. 79 (S73 ).

  Here, the event ID 5b registered as the current candidate is the event to be output. The output management unit 17 executes the output processing flow for the event ID 5b registered as the current candidate (S74). The event ID 5b to be output has not been output. Therefore, the output management unit 17 determines NO in S81, and proceeds to S82.

  The difference between the current time "18:06:20" and the time "17:54:20" of the event ID 5b to be output is the output time determined according to the condition b that is satisfied by the event ID 5b to be output " 10 minutes "or more (S82 / YES). Therefore, the output management unit 17 determines YES in S82, and outputs the output target event ID 5b as shown in FIG. 80 (S83). This output has been indicated by attaching "Done" to event ID 5b.

  As shown in FIG. 81, the events registered in the current event condition (condition a) are event ID1a, ID4a, and ID7a. The event ID 1a has a combined flag set, and is connected to the event ID 5b registered in the candidate set by an edge (see solid line). Accordingly, the output management unit 17 registers the event ID 1a in the new candidate set as shown in FIG. 81 (S75). Then, the process returns to S72.

  All event IDs 5b, ID5d, and ID1c registered as a candidate set have been processed (S72 / YES). Therefore, as shown in FIG. 82, the output management unit 17 moves the entry (ID1 event) of the new candidate set shown in FIG. 81 to the candidate set and sets the current event condition (condition a) as processed (S76). ), Return to S27.

  Here, there is no unprocessed condition. That is, there is no candidate for a condition that is not “processed” (“processed” is assigned to all candidate conditions). Therefore, the output management unit 17 determines that there is no unprocessed condition (S27 / NO).

  Event ID1a registered as a candidate set is an unprocessed event. That is, event ID 1a is an event to be output. The output management unit 17 executes an output processing flow for the event ID 1a registered as a candidate set (S77). The event ID 1a to be output has not been output. Therefore, the output management unit 17 determines NO in S81, and proceeds to S82.

  The difference between the current time “18:06:20” and the time “17:54:00” of the event ID 1a to be output is the output time that is determined according to the condition a that the event ID 1a to be output satisfies. 10 minutes "or more (S82 / YES). Therefore, the output management unit 17 determines YES in S82, outputs the event ID 1a to be output as shown in FIG. 83, and assumes that it has been output (S83). This output has been indicated by attaching "Done" to event ID1a. Then, the output management unit 17 clears the event registered in the candidate set (S83).

(Event input of ID7)
The data reading unit 13 reads the event of ID7 shown in the event table of FIG. 84 (S2). In FIG. 83, the output time of the output candidate event (event ID 1c) is 30 seconds. Specifically, the time (output time) determined corresponding to the condition c satisfied by the output candidate event is 30 seconds. And the current time is "18:06:40".

  Therefore, the output management unit 17 determines that the difference between the current time and the time of the output candidate event is equal to or greater than the output time (S41 / YES). Then, the output unit 18 outputs an output candidate event (event ID 1c), and deletes the output event from the output candidates (S42).

  Next, the information processing apparatus 2 executes the steps described in FIG. 42 and newly registers the event of ID7 as a candidate for conditions c and d as shown in FIG. 85 (S10).

  The newly registered event ID 7d will be described. The node deletion unit 16 determines NO in S12 as described in FIG. 43, and deletes the event ID 7d as shown in FIG. 86 (S13). This deletion is indicated by “x” in FIG. And it returns to S2.

  For the newly registered event ID 7c, the condition determination unit 14 determines YES in S12, as described in FIG. Then, as shown in FIG. 43, as shown in FIG. 86, the graph management unit 15 connects the event ID 7a that satisfies the inter-event condition and the newly registered event ID 7c with edges (see the dashed line) (S14). ).

  Next, as described with reference to FIG. 42, the condition determination unit 14 determines YES in S21, NO in S22, YES in S24, NO in S25, and proceeds to S2.

(Event input of ID6)
The data reading unit 13 reads the event of ID6 shown in the event table of FIG. 87 (S2). In FIG. 87, since no event is registered in the output candidate, after receiving the event (S2), the output management unit 17 determines NO in S41, and proceeds to S3.

  Next, the information processing apparatus 2 executes each step described with reference to FIG. 44, and newly registers an event with ID6 as a candidate for conditions c and d as shown in FIG. 87 (S10).

  The newly registered event ID 6c will be described. The node deletion unit 16 determines NO in S12 as described in FIG. 45, and deletes the event ID 6c as shown in FIG. 88 (S13). This deletion is indicated by “x” in FIG. And it returns to S2.

  For the newly registered event ID 7d, the condition determination unit 14 determines YES in S12, as described in FIG. Then, as shown in FIG. 88, the graph management unit 15 connects the event ID 6b that satisfies the inter-event condition and the newly registered event ID 6d with sides (see broken lines) (S14).

  The information processing apparatus 2 executes each step described with reference to FIG. 45, and the graph management unit 15 uses the side (see the dotted line) for the event ID 1c that satisfies the inter-event condition and the newly registered event ID 6d as shown in FIG. ) To connect (S23). The partner condition (condition b, c) of each inter-event condition (condition bd or condition cd) related to the event ID 6d does not include a subsequent condition (no condition) whose time follows the own condition (condition d) (S24). / NO). Therefore, the condition determination unit 14 determines NO in S24, and proceeds to S25. The newly registered event ID 5d has two types of different types (see dotted line and alternate long and short dash line) (S25 / YES). Therefore, the condition determining unit 14 determines YES in S25, and proceeds to S61. As shown in FIG. 89, the combination flag update unit 22 sets a combination flag in the new registration event ID 6d (S61).

  The combination flag update unit 22 executes the processing of S62 and S63 for the event ID 16b (target event) that is connected to the newly registered event ID 6d at the side and has no combination flag.

  The target event ID 6b has two different types of sides (solid line side, broken line side). Accordingly, the combination flag update unit 22 determines YES in S62, sets the combination flag in the target event ID 6b as shown in FIG. 90 (S63), and returns to S62.

  The combination flag update unit 22 executes the processing of S62 and S63 for the event ID 7a that is connected by an edge to the event ID 6b for which the combination flag is set, and has no combination flag. The target event ID 7a has two different types of sides (solid line side, one-dot chain line side). Therefore, the combination flag updating unit 22 determines YES in S62 for the target event ID 7a, sets the combination flag in the target event ID 7a as shown in FIG. 91 (S63), and returns to S62.

  The combination flag update unit 22 executes the processing of S62 and S63 for the event ID 7c that is connected to the event ID 7a for which the combination flag is set and has no combination flag.

  Event ID 7c (target event) without a combination flag does not have two different types of edges. Therefore, the combination flag update unit 22 determines NO in S62 for the target event ID 7c, and proceeds to S64. Since all the combination flag setting processes have been completed, the process proceeds from the wait state (S64) to S65.

  The combined flag update unit 22 finally responds to the event ID 7a (flag deletion event ID 7a) for which the combined flag connected with the target event ID 7c (reference event ID 7c) for which the combined flag has not been set is set. , S66 is executed (S65).

  In FIG. 92, there is no event connected to the flag deletion event ID 7a on the same type of side as the side (one-dot chain line) to which the flag deletion event ID 7a and the reference event ID 7c are connected (S66 / YES). Therefore, the combination flag update unit 22 determines YES in S66, and deletes the combination flag set in the flag deletion event ID 7a as shown in FIG. 92 (S67). Deletion of the join flag is indicated by a cross. After S67 ends, return to S65.

  As shown in Fig. 93, the processing of S66 is performed for event ID 7a (reference event ID 7a) from which the combination flag has been deleted and event ID 6b (flag deletion event ID 6b) in which the combination flag connected by the side is set. Execute (S65).

  In FIG. 93, there is no event connected to the flag deletion event ID 6b on the same type of side (solid line) to which the flag deletion event ID 6b and the reference event ID 7a are connected (S66 / YES). Therefore, the combination flag update unit 22 determines YES in S66, and deletes the combination flag set in the flag deletion event ID 6b as shown in FIG. 93 (S67). After S67 ends, return to S65.

  As shown in Fig. 94, the processing of S66 is performed for event ID 6b (flag deletion event ID 6d) for which event ID 6b (reference event ID 6b) for which the combination flag has been deleted and event flag 6d connected for the edge is set. Execute (S65).

  In FIG. 94, there is no event connected to the flag deletion event ID 6d on the same type of side (dashed line) to which the flag deletion event ID 6d and the reference event ID 6b are connected (S66 / YES). Therefore, the combination flag update unit 22 determines YES in S66, and deletes the combination flag set in the flag deletion event ID 6d as shown in FIG. 94 (S67). After S67 ends, return to S65.

  As shown in Fig. 95, the processing of S66 is performed for event ID1d (flag deletion event ID1c) for which event ID6d (reference event ID6d) for which the combination flag has been deleted and the combination flag connected by the side is set. Execute (S65).

  In FIG. 95, there is an event connected to the flag deletion event ID 1c on the same type of side (dotted line) to which the flag deletion event ID 1c and the reference event ID 6d are connected. This event is event ID 5d. Therefore, the combined flag update unit 22 determines NO in S66 and does nothing for the flag deletion event ID 1c. Then, the process proceeds to S71.

  As shown in FIG. 95, the new registration event ID 6d does not have a combination flag. Accordingly, the output management unit 17 determines NO in S71 and returns to S2.

(Event input of ID8)
The data reading unit 13 reads the event of ID8 shown in the event table of FIG. 96 (S2).

  The condition determination unit 14 determines YES in S3 as described in FIG. Then, as shown in FIG. 96, the node deletion unit 16 deletes the event IDs 1c, ID7c, ID5d, and ID6d to be deleted and the edge connected to the event to be deleted (S8). In FIG. 56, this deletion is indicated by a cross mark. Further, the node deletion unit 16 unprocesses the event IDs 1a, ID7a, ID5b, and ID6b connected to the event to be deleted at the side (S8). Then, the process proceeds to S51.

  As shown in FIG. 97, an unprocessed event (for example, event ID 1a) for which the join flag is set and an edge of the same type as the deleted edge (for example, the one-dot chain line shown in FIG. 96) (the one-dot chain line) There is no connection event connected at (side).

  Accordingly, the combined flag update unit 22 determines YES in S51, and deletes the combined flag from the unprocessed event (flag deletion event ID1a) for which the combined flag is set, as shown in FIG. 97 (S52).

  Then, the combination flag update unit 22 performs S53 on the event ID 5b in which the combination flag is set in the event connected to the flag deletion event ID 1a by the side (reference side, for example, the side of the solid line in FIG. 97). Execute the process.

  The combination flag is not set for the event ID 5b for which the combination flag is set and the connection event ID 4a connected by the same type of side as the reference side (solid line side) (S53 / YES). Therefore, the combination flag update unit 22 determines YES in S53, and returns to S52.

  As shown in FIG. 98, the combination flag update unit 22 deletes the combination flag from the event ID 5b (flag deletion event ID 5b) for which the combination flag is set (S52). Here, there is no event for which the combination flag is set (S51 / NO). Therefore, the combination flag update unit 22 determines NO in S51, and proceeds to S3.

  Thereafter, as described with reference to FIG. 57, the node deletion unit 16 deletes the event IDs 1a and ID7a to be deleted and the edge connected to the event to be deleted (S7). Further, the node deletion unit 16 unprocesses the event IDs 2b, ID4b, ID5b, and ID6b connected to the event to be deleted at the side (S8). And it returns to S3.

  Next, as described in FIG. 58, the node deletion unit 16 deletes the event IDs 4b and ID6b to be deleted (S7).

  According to the present embodiment, it is possible to output a determination result indicating that an event satisfies a condition between two events. As a result, the administrator can quickly obtain the detection result.

[Other embodiments]
(Event)
The information processing apparatuses 1 and 2 can extract an event satisfying a condition from various events other than the events described in the first and second embodiments.

  FIG. 99 is another diagram schematically showing an event. The event acquired by the data reading unit 13 from the external server indicates, for example, the load of a certain server belonging to a certain network at a certain time. The event indicates a server identifier (server ID) for uniquely identifying a server, a network identifier (network ID) for uniquely identifying a network to which the server belongs, and a load of the server at a certain time. The load is, for example, the load factor (%) of the server CPU.

  The columns in the event table shown in FIG. 99 indicate the event time, server ID, network ID, and load in order from the left of the drawing. Note that the arrows in FIG. 99 schematically show the passage of time.

(Event condition, inter-event condition)
FIG. 100 is another diagram for explaining the event condition and the inter-event condition. In FIG. 100, conditions a to f are schematically shown as ellipses. In condition a, condition b, and condition c, the load included in the event is 80% or more. The conditions a, b, and c may include a load included in the event of 80% or more and less than 90%. In condition d, condition e, and condition f, the load included in the event is 90% or more.

  In the example of FIG. 100, there are seven inter-event conditions. The first inter-event condition is an inter-event condition a-b indicating a relationship with the conditions a and b. The inter-event condition a-b is to satisfy the following two relationships. That is, the first relationship is identified by the network ID of the first event (satisfying condition a) and the network ID of the second event (satisfying condition b) following the first event. The network to be connected is adjacent. The second relationship is that the time difference (timeout) between the time of the first event and the time of the second event is within 60 seconds.

  The second inter-event condition is an inter-event condition b-c indicating a relationship with the conditions b and c. The inter-event condition b-c is to satisfy the following two relationships. In other words, the first relationship is that the network identified by the network ID of the second event is adjacent to the network identified by the network ID of the third event (satisfying condition c) following the second event. Is. The second relationship is that the time difference between the time of the second event and the time of the third event is within 60 seconds.

  The third inter-event condition is an inter-event condition a-d indicating a relationship with the conditions a and d. The inter-event condition a-d is to satisfy the following two relationships. The server IDs included in the first and fourth events are the same, and the time difference between the time of the first event and the time of the fourth event (satisfying condition d) following the first event is 15 seconds. Is within.

  The fourth inter-event condition is an inter-event condition b-e indicating a relationship with the condition b and the condition e. The inter-event condition b-e is to satisfy the following two relationships. The server IDs included in the second and fifth events are the same, and the time difference between the time of the second event and the time of the fifth event (satisfying condition e) following the second event is 15 seconds. Is within.

  The fifth inter-event condition is an inter-event condition c-f indicating the relationship between the condition c and the condition f. The inter-event condition c-f is to satisfy the following two relationships. The server ID included in the third and sixth events is the same, and the time difference between the time of the third event and the time of the sixth event (satisfying condition f) following the third event is 15 seconds. Is within.

  The sixth inter-event condition is an inter-event condition d-e indicating a relationship with the condition d and the condition e. The inter-event condition d-e is to satisfy the following two relationships. In other words, the first relationship is that the network identified by the network ID of the fourth event is adjacent to the network identified by the network ID of the fifth event following the fourth event. . The second relationship is that the time difference between the time of the fourth event and the time of the fifth event is within 60 seconds.

  The seventh inter-event condition is an inter-event condition e-f indicating a relationship with the condition e and the condition f. The inter-event condition e-f satisfies the following two relationships. In other words, the first relationship is that the network identified by the network ID of the fifth event is adjacent to the network identified by the network ID of the sixth event following the fifth event. . The second relationship is that the time difference between the time of the fifth event and the time of the sixth event is within 60 seconds.

  The condition reading unit 11 reads, for example, information having the event condition, the inter-event condition, and the timeout described in FIG. 100 from the storage 103 (S1). Then, the data reading unit 13 of the information processing apparatuses 1 and 2 receives the event indicated by one line in FIG. Then, the information processing apparatuses 1 and 2 execute the processes after S2 described with reference to FIGS.

  The above embodiment is summarized as follows.

(Appendix 1)
A processing unit that acquires event information having a plurality of attributes, and stores the acquired event information in a memory when the acquired event information satisfies an event condition defined in correspondence with the first attribute; Have
Each time the processing unit stores the event information, the processing unit satisfies the inter-event condition related to the first attribute, the second attribute time, and at least two event conditions. An information processing apparatus that determines whether there is stored storage event information, and outputs a determination result if there is storage event information that satisfies the inter-event condition.

(Appendix 2)
In Appendix 1,
The processing unit specifies the storage event information that does not satisfy the inter-event condition based on the time of the storage event information and a reference time corresponding to the current time, and deletes the specified storage event information An information processing apparatus characterized by that.

(Appendix 3)
In Appendix 2,
The event conditions are the first event condition and the second event condition defined corresponding to the first attribute,
The inter-event condition is an inter-event condition related to time, the third attribute, and the first and second event conditions,
In the deletion of the storage event information, the processing unit adds the time of the storage event information satisfying the first event condition and the time of the inter-event condition exceeding the reference time, An information processing apparatus, wherein event information that satisfies a second event condition and a condition between second events is not stored in the memory, and the stored event information that satisfies the first event condition is deleted.

(Appendix 4)
In Appendix 2,
The event conditions are the first event condition, the second event condition, and the third event condition, which are defined corresponding to the first attribute,
The inter-event condition includes a first inter-event condition associated with a first time, a third attribute, and the first and second event conditions, and a second longer than the first time. A second inter-event condition related to time, the third attribute, and the first and third event conditions,
In the deletion of the storage event information, the processing unit may add the time of the first storage event information that satisfies the first event condition and the second time to exceed the reference time. The event information that satisfies the condition between the second events is not stored in the memory, and the first stored event information is deleted.

(Appendix 5)
In Appendix 2,
The event conditions are the first event condition, the second event condition, and the third event condition, which are defined corresponding to the first attribute,
The inter-event condition includes a first inter-event condition associated with a first time, a third attribute, and the first and second event conditions, and a second longer than the first time. A second inter-event condition related to time, the third attribute, and the first and third event conditions,
In the deletion of the storage event, the processing unit has the first storage event information satisfying the first event condition but not satisfying the first inter-event condition, and the second storage event information is: When the first storage event information is deleted when the third event condition and the second inter-event condition are satisfied, the second storage event information is deleted. Information processing device.

(Appendix 6)
In Appendix 1,
The event condition is defined by the first attribute, the first event condition, the second event condition, the third event condition, and the fourth event condition. Because
The inter-event condition includes a first inter-event condition associated with a first time, a third attribute, and the first and second event conditions, and a second longer than the first time. A second inter-event condition related to time, the third attribute, and the first and third event conditions; a third time, the third attribute, and the third and fourth event conditions; A fourth inter-event condition related to the third inter-event condition related to the fourth time longer than the third time, the third attribute, and the second and fourth event conditions. There,
In the output of the determination, the processing unit includes the first storage event information satisfying the first event condition and the first and second inter-event conditions, and the second storage event information is: The second event condition and the first and fourth inter-event conditions are satisfied, and the third memory event information satisfies the third event condition and the second and third inter-event conditions , Determining whether the fourth stored event information satisfies the fourth event condition and the third and fourth inter-event conditions, and outputting the determination result if satisfied. Processing equipment.

(Appendix 7)
In Appendix 1,
The information processing apparatus according to claim 1, wherein the processing unit determines whether there is the stored event information that satisfies the inter-event condition at every predetermined timing.

(Appendix 8)
In Appendix 6,
The processing unit includes the event information satisfying the third event condition and the second and third inter-event conditions, or the fourth event condition and the third and fourth inter-event conditions. An information processing apparatus characterized in that the determination is performed at a timing when satisfied event information is stored in the memory.

(Appendix 9)
In Appendix 6,
The information processing apparatus, wherein the processing unit deletes the first to fourth storage event information after outputting the determination result.

(Appendix 10)
In Appendix 6,
When the time obtained by adding the time of the third storage event information and the fifth time determined corresponding to the third event condition exceeds the reference time, the processing unit An information processing apparatus characterized by deleting the stored event information.

(Appendix 11)
In Appendix 6,
When the time obtained by adding the time of the fourth storage event information and the sixth time determined corresponding to the fourth event condition exceeds the reference time, the processing unit An information processing apparatus characterized by deleting the stored event information.

(Appendix 12)
In Appendix 1,
In the determination, the processing unit determines that the difference between the reference time corresponding to the current time and the time of the storage event information that satisfies the event condition and the inter-event condition is before the storage event information is satisfied. An information processing apparatus that determines whether the output time is longer than a predetermined time corresponding to the event condition, and outputs the determination result if the output time is longer than the output time.

(Appendix 13)
In Appendix 12,
The processing unit sets an identifier indicating that it has been output in correspondence with the output storage event information, and does not execute the output of the storage event information in which the identifier is set. apparatus.

(Appendix 14)
In Appendix 12,
The processing unit specifies all the storage event information that does not satisfy the inter-event condition based on the time of the storage event information and the reference time, deletes the specified storage event information, and stores the storage event information. An information processing apparatus for performing the determination after deleting event information.

(Appendix 15)
In Appendix 12,
The processing unit sets an identifier indicating that the inter-event condition is satisfied in the storage event information satisfying the inter-event condition, and outputs the stored event information in which the identifier is set. Information processing apparatus.

(Appendix 16)
In Appendix 15,
The event condition is defined by the first attribute, the first event condition, the second event condition, the third event condition, and the fourth event condition. Because
The inter-event condition is the first inter-event condition related to the first time, the third attribute, the first and second event conditions, and the first inter-event condition, A second inter-event condition related to a second time longer than time, the third attribute, and the first and third event conditions, a third time, the third attribute, and the third , A third inter-event condition related to the fourth event condition, a fourth time longer than the third time, the third attribute, and the second and fourth event conditions The fourth inter-event condition,
The processing unit sets the identifier in the first storage event information when the first storage event information satisfies the first event condition and the first and second inter-event conditions, When the second storage event information satisfies the second event condition and the first and fourth inter-event conditions, the identifier is set in the second storage event information, and the third storage event information However, when the fourth event condition and the third and fourth inter-event conditions are satisfied, the identifier is set in the fourth stored event information, and further, the third event condition and the second and third events are set. Even if the event information that satisfies the above-mentioned inter-event condition and that has not been output exceeds the reference time after the sum of the time of the event information and the time of the third inter-event condition has elapsed in the memory If not stored, the identifier set in the first, second, and third stored event information is deleted. Processing apparatus.

(Appendix 17)
In Appendix 1,
The information processing apparatus, wherein the determination result is stored event information that satisfies the inter-event condition.

(Appendix 18)
Computer
Get event information with multiple attributes,
If the acquired event information satisfies an event condition defined corresponding to the first attribute, the acquired event information is stored in a memory;
Each time the event information is stored, the stored event stored in the memory satisfying an inter-event condition related to the first attribute, the second attribute time, and at least two event conditions Determine if there is information,
A program for executing a process of outputting a determination result when there is stored event information satisfying the inter-event condition.

(Appendix 19)
Get event information with multiple attributes,
If the acquired event information satisfies an event condition defined corresponding to the first attribute, the acquired event information is stored in a memory;
Each time the event information is stored, the stored event stored in the memory satisfying an inter-event condition related to the first attribute, the second attribute time, and at least two event conditions Determine if there is information,
A determination result is output when there is stored event information that satisfies the inter-event condition.

  1, 2 ... Information processing device, 101 ... CPU (processing unit), 102 ... RAM (memory), 103 ... Storage device, 104 ... External storage medium reader, 105 ... Network interface, SF1, SF2 ... Real-time processing software, 11 ... Condition reading part, 12 ... Condition conversion part, 13 ... Data reading part, 14 ... Condition judgment part, 15 ... Graph management part, 16 ... Node deletion part, 17 ... Output management part, 18 ... Output part, 21 ... Output condition Setting unit, 22... Combined flag update unit.

Claims (6)

A processing unit that acquires event information having a plurality of attributes, and stores the acquired event information in a memory when the acquired event information satisfies an event condition defined in correspondence with the first attribute; Have
Wherein the processing unit each time to store the event information, the first attribute and satisfying between related events in at least two of said event conditions for a period of time a second of said attribute, said memory An information processing apparatus that determines whether there is stored storage event information, and outputs a determination result if there is storage event information that satisfies the inter-event condition. In claim 1,
The processing unit specifies the storage event information that does not satisfy the inter-event condition based on the time of the storage event information and a reference time corresponding to the current time, and deletes the specified storage event information An information processing apparatus characterized by that. In claim 1,
In the determination, the processing unit determines that the difference between the reference time corresponding to the current time and the time of the storage event information that satisfies the event condition and the inter-event condition is before the storage event information is satisfied. An information processing apparatus that determines whether the output time is longer than a predetermined time corresponding to the event condition, and outputs the determination result if the output time is longer than the output time. In claim 3,
The processing unit sets an identifier indicating that the inter-event condition is satisfied in the storage event information satisfying the inter-event condition, and outputs the stored event information in which the identifier is set. Information processing apparatus. Computer
Get event information with multiple attributes,
If the acquired event information satisfies an event condition defined corresponding to the first attribute, the acquired event information is stored in a memory;
Each time storing said event information, wherein the first attribute and events between satisfies associated with time and at least two said event condition is a second of said attributes, storing events stored in the memory Determine if there is information,
A program for executing a process of outputting a determination result when there is stored event information satisfying the inter-event condition. The computer acquires event information with multiple attributes,
The computer stores the acquired event information in a memory if the acquired event information satisfies an event condition defined in correspondence with the first attribute;
Said computer, said each time for storing event information, the first attribute and satisfying between related events in time and at least two said event condition is a second of said attributes, stored in the memory Whether there is stored memory event information,
An information processing method characterized in that the computer outputs a determination result when there is stored event information that satisfies the inter-event condition.

Images