JPH11266248A - Event informing controller - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an event informing controller for receiving event information from plural devices and quickly judging whether or not the event information is to be informed. SOLUTION: When event information whose constituting elements are a block number, a device kind and a state code, etc., are received this event informing controller retrieves a condition record in a condition table 320 by comparing whether or not the block number 311 and device kind 312 of an index match with the contents of the event information in the order of the block number and of the device kind by referring to an index table 310, determines whether or not the event information satisfies all the conditions indicated in the condition record and informs an external device of the event information when satisfying them. The condition record in the condition table 320 are capable of being registered, changed, or eliminated from the external device. At registration or the like, the index table 310 and the comparison order of the block number 311 and the device kind 312 are changed which correspond to the contents of the condition record.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention receives event information sent from a plurality of devices and indicating the status of the device.
The present invention relates to an event notification control device that outputs only event information that satisfies conditions registered in advance.

[0002]

2. Description of the Related Art In recent years, with the progress of information and communication technology, companies and the like are constructing network systems using dedicated lines and exchanges. In general, an exchange is composed of a plurality of devices such as a power management device, a device for controlling communication between exchanges, and a device for controlling communication with telephones and computer terminals. Is notified outside the exchange as event information. The network system is provided with a management device for monitoring the status of the exchange and controlling the network.The management device receives, via a line, various types of event information generated by the devices inside the exchange from the exchange, and Appropriate processing such as communication path selection and troubleshooting is performed according to the content. Some management devices have a function of periodically inquiring the exchange of the status at intervals of several minutes to supplement the event information.

The event information includes various information such as a device number, a device status, a failure type, and an error level so that the management device can grasp the status of each device in the exchange in detail and take appropriate action. It is issued asynchronously from the device. For this reason, when event information is output from each device in the exchange almost simultaneously, the management device receives the event information at one time, and becomes overloaded because the event information is received at one time. May not be.

In order to avoid this problem, the exchange stores all event information generated by each internal device in a storage medium or the like so that the information can be provided in response to a periodic inquiry from a management device. Further, any event information may be used as long as the event information is narrowed down to a minimum necessary for the convenience of management of the management device and is notified to the management device. Here, since the management by the management device includes, for example, a test such as a communication function recovery confirmation after a failure recovery, the event information required for the management of the management device may change with time. is there. Therefore, the management device notifies the exchange of the condition about the event information to be notified, and the exchange determines whether or not the event information generated from each internal device satisfies the condition, and notifies the exchange. If only the event information to be notified is notified to the management device, it is possible to suppress the occurrence of the overload state described above.

[0005] By the way, conditions for event information to be notified are detailed for the sake of convenience of management of the management device, for example, in order to distinguish between those that need to be notified and those that do not need to be notified, depending on the content of the fault and the error level. It is desirable to be able to specify, multiple device numbers, device status, failure type,
It should be possible to specify a plurality of condition sets for each of a plurality of items such as error levels.

However, a condition set is composed of many items,
If the number of condition sets is large, the exchange needs a lot of processing to determine whether or not the event information is to be notified, so that there is a problem that it is not possible to promptly notify the event information to be notified. This problem is caused not only by the above-mentioned exchange, but also by receiving event information indicating the status of the device sent from a plurality of devices and notifying other devices only of event information that satisfies one of a pre-registered condition set. This is also a common problem in such an event notification control device.

As a technique for solving such a problem in a specific case, there is an event report processing circuit disclosed in Japanese Patent Publication No. 8-7723. FIG. 11 is a diagram showing a configuration of a conventional event report processing circuit. In the event report processing circuit, the extraction unit 901 finds out, from a plurality of notification condition expressions (EFDs) stored in the storage unit 904, EFDs in which all the attributes specified in the notification conditions are included in the event (steps S911 to S911). Step S913). One of the washed out EFDs is sequentially taken out (step S
914), determining means 902 for a logical operation relating to the notification condition
If the determination result is true, an event notification is performed by the notification unit 903 (step S915 to step S915).
917). Here, the EFD corresponds to the above-described condition set, and the attribute corresponds to each item such as a failure type and an error level in the above-described condition set. This event report processing circuit aims to speed up the processing by reducing the number of comparison judgment processes by excluding a condition set having attribute information not included in the received event from the comparison judgment targets.

[0008]

However, the above-described event report processing circuit has a problem that when all the attributes are included in the event information, that is, each condition set includes the device number and the device number included in the event information. There is no effect in the case where there is designation information for each of information such as a state, a failure type, and an error level.

The present invention has been made in view of the above-mentioned problems, and has been made in order to receive event information from a plurality of devices and not to notify unnecessary event information.
It is an object of the present invention to provide an event notification control device that promptly determines whether or not the event information is to be notified.

[0010]

According to an aspect of the present invention, there is provided an event notification control apparatus for receiving event information including a plurality of items and outputting only event information satisfying a predetermined condition. A condition storage unit that stores a plurality of condition records indicating the predetermined condition, including a plurality of condition items that are conditions corresponding to the plurality of items of the event information, and a plurality of condition records stored in the condition storage unit. Is used to search for a specific condition record from the condition records of the condition record, and includes at least one condition item among a plurality of condition items in the condition record as a comparison element for search, and includes index information of the condition record. Index storage means for storing an index including the content of the index element; By comparing the content of the condition item as the comparison element with the content of the corresponding item in the event information by comparing the content of the item corresponding to the comparison element in the event information, the condition storage means And a condition determination output unit that outputs the event information only when the content of the event information satisfies all the conditions indicated in the condition record searched by the search unit. Features.

According to the above configuration, a condition record having the same content for a condition item used as a comparison element is indicated by one index. Usually, the number of indexes is smaller than the number of condition records.
According to the search using the index, the number of comparisons can be reduced as compared with a case where individual condition records are brute-force-matched with event information, and as a result, the determination of whether or not to output event information is expedited. Can be achieved.

[0012] Here, the index has a plurality of comparison elements, and the search means determines the content of each comparison element of the index and the content of each item corresponding to each comparison element in the received event information. By searching for a condition record in which the contents of all the condition items that are comparison elements match the contents of the corresponding item in the event information, the comparison in the search means is performed by:
As long as the comparison results match, each comparison element in the index is sequentially compared, and after the comparison result becomes inconsistent, the comparison of other comparison elements may not be performed.

With the above arrangement, the comparison order of the comparison elements is
If a predetermined standard such as the order in which the comparison judgment can be performed at a high speed is set, the possibility of speeding up the comparison judgment is increased as a whole. Further, the event information is sent from any of a plurality of managed devices, and includes information specifying a source managed device and information indicating a state of the managed device as items, respectively, and the condition record includes: The index includes a condition item for limiting the managed device, a condition item indicating a condition related to a state of the managed device, and suppression control instruction information that is information indicating a transmission source to be suppressed. Is used as a comparison element for a search, and the event notification control device further includes, when the content of the event information satisfies all the conditions indicated in the condition record searched by the search means, the condition The condition record including the transmission source indicated by the suppression control instruction information included in the record as a condition item for limiting the managed device is described. Is so as not to be searched using the index may be to include an index reconstructing means for reconstructing the indexes.

According to the above configuration, an index indicating a specific condition record is not dynamically generated based on the event information without instructing registration, change or deletion of the condition record indicating the output condition of the event information from an external device. In this way, it is possible to immediately suppress the output of other event information that has occurred in conjunction with the occurrence of certain event information, thus preventing unnecessary output of event information. it can. Further, as a result of the suppression control, the index indicating the specific condition record disappears, so that the search for other condition records can be performed more quickly, and the speed of determining whether to output the event information can be increased.

[0015]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the event notification control device according to the present invention will be described below in detail with reference to the drawings. <Embodiment 1> Hereinafter, the ATM (A
Synchronous Transmission
(Mode: Asynchronous Exchange Mode) The event notification control unit of the exchange will be described with reference to FIGS.

<Configuration> FIG. 1 is a configuration diagram of a network system including an ATM switch according to Embodiment 1 of the present invention. As shown in FIG. 1, in the network system 1, the ATM switch 100 is connected to another ATM switch via a dedicated line, connected to a personal computer (hereinafter, referred to as a personal computer) via a router, and also connected to a telephone. , And also connected to the management device 10.

Here, the management device 10 is an ATM switch 1
00 is a personal computer that manages the status of 00, and stores event information of various contents indicating the status of each device inside the ATM exchange.
The information is received from the ATM exchange 100 via a line, and appropriate processing such as communication path selection and troubleshooting is performed according to the contents. In order to receive only necessary information among the event information, the management device 10 stores a condition record indicating the condition of the event information to be transmitted to its own device.
0, or a condition record that has already been registered can be changed or deleted.

FIG. 2 is a configuration diagram of the ATM switch 100 according to the first embodiment. FIG. 1 shows the hardware configuration of the ATM switch 100, and further shows the internal functional configuration of the event notification control unit 110.
The ATM switch 100 is composed of ten blocks each having 16 slots and an event notification control unit 110, and each slot stores a device such as a power management device and a device for controlling communication between switches. Has been
Event information indicating the device status is sent from each device to the event notification control unit 110, and the event notification control unit 110
Only necessary event information of the sent event information is transmitted to the management device 10.

More specifically, each device in the ATM switch 100 is mounted in each of the slots 121 to 125 in the block 120, the slots 131 to 135 in the block 130, each slot in the block 140, and the like. Is
It can be specified by block numbers 1 to 10 and slot numbers 1 to 16. Here, block 12
The block number of 0 is 1, and the slot 121 stores a device (hereinafter, referred to as a SWCON package) that enables data exchange between the device stored in each slot in the block 120 and the event notification control unit 110. And
In the slot 122, a device for controlling communication with a telephone or a personal computer (hereinafter, referred to as a VIFI package) is stored, and in the slot 124, a device for controlling communication between exchanges (hereinafter, referred to as an S6.3 package). Is stored in a slot 125, and a device (hereinafter, referred to as an A156 package) for controlling communication between exchanges with a protocol different from that of the S6.3 package is stored in a slot 123. A VIFI package and S6 are stored in a slot 123. It is assumed that a device (hereinafter, referred to as an SW package) for exchanging data with the .3 package or the A156 package is stored.

The block number of the block 130 is 3
The slot 131 has a SWCON package, the slot 132 has a VIFI package, the slot 133 has a SW package, the slot 134 has an S6.3 package, and the slot 135 has an A156.
It is assumed that the package is stored. It is not necessary to store devices of the same type in slots of the same number in each block.

The event notification control unit 110 is composed of a computer including a CPU, a memory, a hard disk, and the like in terms of hardware, and is executed by the hardware or by executing a program stored in the memory by the CPU. , The function of selectively outputting only necessary event information is realized. Functionally,
Event information acquisition unit 111, condition determination unit 112, event information output unit 113, search unit 114, comparison order storage unit 115, condition storage unit 116, condition update unit 11
And 7.

Here, the event information acquisition unit 111 receives event information sent from each device via the SWCON package. The condition determining unit 112 determines whether or not the event information acquired by the event information acquiring unit 111 satisfies a condition registered in advance.
Judgment is made by referring to the condition record searched by the search unit 114 and comparing with the event information. If the condition is satisfied, the event information is output to the event information output unit 113.
To tell.

The event information output unit 113 transmits the event information transmitted from the condition determination unit 112 to the management device 10 via a line. The condition storage unit 116
A hard disk or a memory stores a condition table that is a set of condition records indicating conditions for event information to be transmitted to the management device, and an index table that is a set of indexes for searching the condition table. The comparison order storage unit 115 stores, in one area of the memory, comparison order information indicating whether to compare the block number or the device type first when the search unit 114 searches using the index table. It is something to memorize. Here, the condition record includes a block number and a device type as items, and the index uses the block number and the device type as comparison elements. The condition table and the index table will be described later in detail.

The search unit 114 refers to the comparison order storage unit 115 and the condition storage unit 116 to search for event information, a condition record that matches with the block number and the device type. The condition updating unit 117 stores the management device 10
Updates the condition table and the index table stored in the condition storage unit 116 in response to a request for registration, change, and deletion of a condition record from the server, and stores the comparison order stored in the comparison order storage unit 115 as necessary. Updates information. When the condition record is registered, the condition update unit 117 returns the record number to the management device 10.

<Data Structure> First, the event information sent from each device to the event notification control unit 110 will be described. FIG. 3 is a diagram showing a data structure and an example of contents of event information. The event information 200 includes the device number 21
0, the device type 220, the status code 230, and the error level 240. The device number 210 includes a block number 211 and a slot number 212.

Here, the block number 211 is 4-bit data indicating which block the source of the event information belongs to, and is a number from 1 to 10. The slot number 212 is 4-bit data indicating in which slot the source of the event information is the device stored in the block.
To any number from 16 to 16.

The device type 220 is 1-byte data indicating what type of device the source device of the event information is, and indicates whether the device is a SWCON package, a VIFI package, or the like. There are ten types of devices. The status code 230 is two-byte data indicating the status of the device such as the occurrence of a communication failure or the occurrence of a device failure. Can be identified.

The error level 240 is one-byte data that complements the status code 230, and means one of a major level, a minor level, and a warning level in descending order of severity according to the degree of a failure or the like. Take a value. The event information illustrated in the figure is an example of event information issued from the device stored in the slot 125 in the block 120 in FIG. Type is A156
This means that the communication has been issued from a device which is a package and that a communication failure of a major level having a high degree of seriousness has occurred. In the example of FIG. 3, the contents of the device type, the status code, and the error level are represented by character strings, but each of them is actually a bit string whose meaning can be identified.

Next, the condition table and the index table stored in the condition storage unit 116 will be described. FIG. 4 is a diagram illustrating a data structure of the condition table and the index table stored in the condition storage unit 116 and an example of the contents thereof. The condition table 320 is a set of condition records registered by the management device 10, and each condition record indicates a condition to be satisfied by event information to be notified to the management device 10, and has a record number 321.
, A block number 322, a device type 323, and a status code / error level condition 324.

The record number 321 is a number assigned to identify each condition record.
Reference numeral 7 is attached at the time of condition record registration, and can be used for specifying a target of change or deletion when the condition record is changed or deleted later. The block number 322 and the device type 323 are conditions for limiting the device of the generation source of the event information to be notified to the management device 10, and the condition is the block number 21 in the event information shown in FIG.
1 and the device type 220.

The status code / error level condition 324 is:
This is a condition for limiting the content of the event information to be notified to the management device 10, corresponds to the status code 230 and the error level 240 in the event information shown in FIG. 3, and determines whether or not these conditions are satisfied. For this reason, it is described in a certain format. For example, the logical product of conditions (an
Formats such as d) and a description such as a logical sum (or), a description for checking each bit of a status code, and a description for checking whether or not a status code falls within a certain numerical range are predetermined.

The index table 310 is a set of indexes in which each condition record of the condition table 320 is indicated by a block number and a device number type as an index.
11, a device type 312, a pointer 313, and a next pointer 314. That is, the index table 3
Reference numeral 10 indicates that condition records having the same block number 322 and device type 323 are combined into one, and one index is associated with the condition records. According to this, each condition record can be searched quickly. Therefore, pointer 3
13 may have pointers to a plurality of condition records, as seen in FIG.

The index table 310 is sorted by the contents of either the block number 311 or the device type 312, and the next pointer 314 is a pointer indicating the next different index for the sorted contents. If there is no different index next, the next pointer 314 is set to NULL. Hereinafter, the example contents of FIG.

The index table is sorted by the block number in the example shown in the figure. The next pointer of the index 331 having the block number 1 is different from the block number 1 and points to the index 332 having the block number 3. Since no index larger than 3 exists, the next pointer of the index 332 is NULL.
It has become.

The index 331 has a block number of 1
The condition record conditioned on the condition that the device type is the A156 package is pointed by a pointer. The condition record pointed by the pointer has a record number of 1 and a status code error level condition indicates that a communication failure has occurred. And that the error level is equal to or higher than the minor level.

The index 333 indicates, by a pointer, a condition record on condition that the block number is 3 and the device type is the SW package. There are two condition records pointed by the pointer, and one is a record. A condition record having a number of 4 and a status code indicating that a device failure has occurred, and another condition record having a record number of 5 and a status code of indicating that device recovery has been completed. This is a condition record.

<Operation> The operation of the event notification control unit 110 having the above configuration will be described below. First, the operation of the condition update unit 117 when a condition record is registered from the management device 10 will be described.

FIG. 5 is a flowchart showing the operation of the condition updating unit 117 for registering condition records. Management device 10
Transmits one condition record together with the registration request to the ATM switch 100, the condition updating unit 117
Checks the grammar of the received condition record (step S401). Here, the grammar check includes checking that the received condition record is composed of a block number, a device type, a status code and an error level condition, checking whether each value range is appropriate, and checking the status code and error level. Checking whether the description format of the condition is appropriate or not.

If the result of the grammar check of the condition record is normal (step S402), the condition updating unit 117
The condition record is added to the condition table with the record number included (step S403), and an index table is constructed accordingly (step S404). Here, the construction of the index table refers to creating, by referring to the condition table, those having the same block number and device type, and creating an index including a block number, a device type, and a pointer to a condition record.

After the construction of the index table, the condition updating unit 117 refers to the index table, and if the block number or the device type is to be compared first, whether the event information should be notified to the management device 10 or not. The comparison order is determined from the viewpoint of whether the possibility of reducing the number of comparison judgments for (1) increases (step S40).
5).

Here, the quotient obtained by dividing the number of different block numbers existing in all indexes by the number of all block numbers that can be included in the event information is:
Compare the quotient obtained by dividing the number of different device types existing in all indexes by the number of all device types that can be included in the event information, and if the smaller one is the quotient related to the block number, Indicates that the comparison order information stored in the comparison order storage unit 115 is that the block number is first, and if the reverse is true, the comparison order information is that the device type is first.

After determining the comparison order, the condition updating unit 117
For example, after sorting all indices of the block number and the device type to be compared first in ascending order, for example, concatenate indices having different values in the comparison target first with a pointer chain. The index table is made available (step S406). At this time, the states of the condition table and the index table are as shown in FIG. 4, for example. In FIG. 4, there are only two types of block number values in the index table, 1 or 3, and dividing this by 10 which is the number of all block numbers results in 0.2, and the value of the device type is A
156, SWCON, S6.3, SW, and VIFI, which are divided by 10 which is the number of all device types, to obtain 0.5. It is to be compared first.

After making the index table available, the condition updating unit 117 returns the record number assigned in step S403 to the management device 10 (step S407), and ends the condition record registration process.
If the grammar check result of the condition record is not normal (step S402), the condition updating unit 117 returns a code indicating a grammar error to the management device 10 (step S408), and ends the condition record registration process. I do.

In the case of changing the condition record, a record number for specifying the condition record to be changed is received from the management device 10, and thereafter, the above-described step S is performed.
403 is replaced with the change of the designated condition record, and the same processing as the registration of the condition record is performed except for step S407. In the case of deleting the condition record, the condition record for specifying the condition record to be deleted is specified. The record number is received from the management device 10, and thereafter, the above-described step S
403 is replaced by the deletion of the designated condition record, and the same processing as the registration of the condition record is performed except for steps S401, S402, S407, and S408.

Next, the event notification control unit 110 sets the ATM
An operation when event information is received from any device in the exchange 100 will be described. FIG. 6 is a flowchart illustrating a notification control process of event information by the event notification control unit 110. However, the procedure shown in the figure is a processing procedure of the event information in the case where the comparison order information stored in the comparison order storage unit 115 indicates that the block numbers are compared first, and is repeatedly executed. Things.

When the comparison order information indicates that the device type is to be compared first, the processing procedure of the event information is shown in steps S502 and S5 in FIG.
05 are exchanged, the judgment contents of step S503 and step S506 are exchanged, and the judgment contents of step S504 and step S507 are exchanged.
That is, the comparison order information is realized as a pointer indicating a storage position in one of the memories among the programs for realizing the two types of algorithms.

The notification control processing of event information shown in FIG. 6 includes step S501 for acquiring event information, steps S502 to S504 for comparing the event information and the index with respect to the block number, and the event information and the index for the device type. In comparison, steps S505 to S507 for specifying a condition record indicating a condition to notify the event information and steps S508 to S51 to determine whether the event information satisfies the condition to notify.
0 and step S511 of notifying the management apparatus of event information when the condition is satisfied.

Hereinafter, the operation will be described in detail. The event information acquisition unit 111 acquires event information (step S5).
01), and transmits the event information to the retrieval unit 114. Search unit 11
4 focuses on the block number of the first index with reference to the index table (step S50).
2) Compare with the block number in the event information (step S503), and if they do not match, refer to the next pointer of the index (step S504). If NULL, notify the event information without performing notification. The process ends. If the next pointer is not NULL and points to an index having the next block number (step S504), the process returns to step S502 and focuses on the block number and compares it with the block number in the event information (step S504). S503).

If the block number in the index matches the block number in the event information (step S503), the search unit 114 focuses on the device type in the index (step S505), and checks the device type in the event information. (Step S506), and if they do not match,
If the next index does not exist (step S50)
7) The notification control process is terminated without notifying the event information. If the next index exists, that is, if there is an index including the next device type (step S507), the process returns to step S505, and focuses on that device type and compares it with the device type in the event information (step S506). .

If the device type in the index matches the device type in the event information (step S50)
6), the search unit 114 gives all the pointers included in the index of interest to the condition determination unit 112, and the condition determination unit 112 pays attention to the status code / error level condition of the condition record indicated by one pointer. (Step S508), by referring to the status code and the error level in the event information, it is determined whether the event information satisfies the condition (Step S509). If the condition is not satisfied, the condition determining unit If the pointer that points to the condition record that has not been focused on yet has not been obtained (step S510), the notification control processing ends without notifying the event information, and also points to the condition record that has not been focused on yet. If the pointer has been obtained, the process returns to step S508, and the status code / error Focusing on Le condition, event are decision condition is satisfied (step S509).

If the condition is satisfied in the judgment in step S509, the event information is transmitted to the management device 10 via the event information output unit 113 (step S511), and the notification control process ends. Although the condition determining unit 112 and the search unit 114 have different functions, they are expressed as different functional blocks.
In the notification control processing of event information of
The search unit 114 and the search unit 114 operate as a single unit, and in fact, it does not take much time to exchange data between them.

Hereinafter, the above-described notification control operation of event information will be briefly described based on a specific example. It is assumed that the condition table and the index table have the contents illustrated in FIG. As a first example, a case where the event information shown in FIG. 3 is issued from the A156 package stored in the slot 125 of the block 120 of the ATM switch 100 will be described.

The event information acquisition section 111 acquires the event information shown in FIG. 3 (step S 501), and in response to this, the search section 114 sets the event information and the block number 1 of the first index 331 of the index table 310. The block number in the middle is compared with 1 (steps S502 and S503), and since they match, the device type is compared next (steps S505 and S506). Since the device type is A156 and matches, the search unit 114 notifies the condition determination unit 112 of the pointer of the condition record with the record number of 1, and the condition determination unit 112 checks the status code / error level condition of the condition record. This is referred to as “communication failure occurrence and minor level or higher”, the status code in the event information is “communication failure occurrence”, and the error level is “major level”, so it is determined that the condition is satisfied (step S509). The event information is transmitted to the management device 10 via the event information output unit 113 (step S511).

As a second example, a case will be described in which event information is issued from the A156 package stored in a certain slot of the block 140 having the block number 10 of the ATM exchange 100. Event information acquisition unit 11
1 acquires the event information (step S501), and upon receiving the event information, the search unit 114 sets the block number 1 of the index 331 at the head of the index table 310 and the block number 1 in the event information.
0 (steps S502 and S503), and since they do not match, the next pointer of the index 331 is referred to.
Since it is not NULL (step S504), the block number 3 of the index 332 indicated by the next pointer is compared with the block number 10 in the event information (steps S502 and S503).
The next pointer of the index 332 is referred to, and this
Since it is LL (step S504), the operation for the event information ends without notifying the management device 10 of the event information.

As described above, the event notification control unit 110
Focuses on some items in the condition record, such as the condition block number and device type, when adding, changing, and deleting condition records that indicate conditions for reporting event information as needed. Event information was sent by creating an index and determining the order of comparison so that each item to be an index is compared in a certain order in order to increase the possibility that the number of comparisons will be reduced In this case, it is possible to promptly determine whether or not to notify. <Embodiment 2> An event notification control section of an ATM exchange according to Embodiment 2 will be described below with reference to FIGS.

<Structure> FIG. 7 shows an AT according to the second embodiment.
3 is a configuration diagram of an M exchange 1100. FIG. This figure shows the hardware configuration of the ATM switch 1100.
The internal configuration of the event notification control unit 1110 is shown. The ATM exchange 1100 is a modification of the ATM exchange 100 according to the first embodiment, and among the constituent elements of the ATM exchange 1100, those equivalent to the ATM exchange 100 are denoted by the same reference numerals in FIG.
The ATM exchange 1100 is positioned in place of the ATM exchange 100 in the network system shown in FIG.

The ATM exchange 1100 has the same configuration as that of the ATM exchange 100 according to the first embodiment except that the ATM exchange 1100 has an event notification control unit 1110 which is a modification of the event notification control unit 110.
It is the same as the TM exchange 100. Event notification control unit 1
The hardware 110 includes a computer including a CPU, a memory, a hard disk, and the like. The hardware 110 or a computer executes a program stored in the memory to execute only necessary event information. The function of selectively outputting is realized, and functionally, an event information acquisition unit 111, a condition determination unit 1112, an event information output unit 113, a search unit 114, a comparison order storage unit 115, Condition storage unit 11
16, the condition update unit 1117, and the suppression device information storage unit 1
118. Hereinafter, the event notification control unit 1110
In the following, each part will be described, but the parts denoted by the same reference numerals as those in the first embodiment have already been described in the first embodiment, and thus description thereof will be omitted.

The condition judging unit 1112 determines whether the event information acquired by the event information acquiring unit 111 satisfies the conditions registered in advance by referring to the condition record searched by the search unit 114. The event information is transmitted to the event information output unit 113 when the condition is satisfied.
When an index restructuring instruction is described in a condition record related to a condition satisfied by the event information,
According to this instruction, an index restructuring instruction corresponding process is performed. Here, the event information is the ATM exchange 1100
Are emitted from the respective devices in FIG. 3 and are the same as those shown in the first embodiment (see FIG. 3). The index restructuring instruction and the processing corresponding to the index restructuring instruction will be described later.

The condition storage unit 1116 stores, in the hard disk or the memory, a condition table which is a set of condition records indicating conditions for event information to be transmitted to the management device, and an index which is a set of indexes for searching the condition table. The table is stored.
The condition records forming the condition table are the same as those in the first embodiment.
Is added to the condition record (see FIG. 4) shown in FIG. 4 as an index restructuring instruction, which will be described later in detail.

The suppression device information storage unit 1118 stores the event information generated from a certain device in the memory.
In order to prevent the notification from being made to the notification device, a suppression device information table which is a set of suppression device information for specifying the device of the generation source whose notification should be suppressed is stored. Condition update unit 111
7 is a condition record registration, change,
In response to a request for deletion, the condition table stored in the condition storage unit 1116 is updated, the index table is updated, and the comparison order information stored in the comparison order storage unit 115 is updated as necessary. is there. The update of the index table by the condition updating unit 1117 is performed with reference to the inhibition device information table stored in the inhibition device information storage unit 1118.

<Data Structure> First, the condition storage unit 1116
The condition table and the index table stored in the. FIG. 8 is a diagram illustrating a data structure of the condition table and the index table stored in the condition storage unit 1116 and an example of the contents thereof.

The condition table 1320 is a set of condition records registered by the management device 10. Each condition record includes a record number 321 indicating a condition to be satisfied by event information to be notified to the management device 10, and a block number 322. In addition to the device type 323 and the status code / error level condition 324, after notifying the event information that satisfies the condition, the notification of the event information in which the specific device is the generation source is suppressed, or It includes an index restructuring instruction 1325 indicating an instruction as to whether to release the suppression. The record number 321, the block number 322, the device type 323, and the status code / error level condition 324 are the same as those described in the first embodiment.

The index rebuilding instruction 1325 specifically includes a suppression instruction or a cancellation instruction and a device type to be inhibited or released. A plurality of device types to be inhibited or released can be specified. is there. Hereinafter, the condition records will be described based on the example contents of FIG. The condition record 1331 indicates that, when receiving event information indicating that a device failure has occurred from a SW package having a block number of 3 as a source, the management device 10 is notified of the event.
A156 package, S6.3 package, and V located in the block having the same block number as the SW package.
It is a condition record indicating an instruction to set an IFI package as a suppression target. Since the SW package is a device for exchanging data between the A156 package or the S6.3 package and the VIFI package, when a device failure occurs in the SW package, the A156 package, The S6.3 package and the VIFI package generate communication failure event information, and the index restructuring instruction in the condition record 1331 is for suppressing this secondary occurrence of event information.

The condition record 1332 indicates that, when receiving event information indicating that the device recovery is completed with the SW package having the block number 3 as the generation source, the event is notified to the management device 10 and then the SW package 7 is a condition record indicating an instruction to remove the A156 package, the S6.3 package, and the VIFI package located in the block having the same block number as the suppression target.

The data structure of the index table stored in condition storage unit 1116 is the same as that in the first embodiment. Next, the inhibition device information table stored in the inhibition device information storage unit 1118 will be described. FIG. 9 is a diagram illustrating a data structure of a suppression device information table and an example of the content thereof.

The inhibit device information table 1600 is a set of inhibit device information. Each inhibit device information includes a block number 1601 and a device type 1602. Each of the suppression device information is added or deleted by the condition determination unit 1112, and the condition determination unit 1112 specifies a device to be suppressed according to the above-described index rebuilding instruction 1325 (see FIG. 8). The device information is added or the suppressed device information is deleted to release the suppression.

The example of contents shown in FIG. 9 indicates that the A156 package, the S6.3 package, and the VIFI package located in the block with the block number 3 are to be suppressed. <Operation> The operation of the event notification control unit 1110 having the above configuration will be described below.

First, the event notification control unit 1110 sets the AT
An operation when event information is received from any device in the M exchange 1100 will be described. The notification control process of the event information by the event notification control unit 1110 is performed as a procedure after the step S511 of outputting the event information in the notification control process of the event information (see FIG. 6) by the event notification control unit 110 in the first embodiment. An index restructuring instruction corresponding process is added.

FIG. 10 is a flowchart showing an index restructuring instruction corresponding process by the event notification controller 1110. After outputting the event information (step S511 in FIG. 6), the condition determining unit 1112 refers to the index restructuring instruction in the condition record satisfied by the event information, and determines whether the instruction is a suppression instruction or a release instruction (step S1601). ). Note that the index restructuring instruction corresponding process is not executed for a record in which the index restructuring instruction is not described.

If the instruction is a suppression instruction, referring to the block number in the condition record and the device type for specifying the suppression target included in the index restructuring instruction, create the suppression device information, and The information is added to the suppression device information table stored in the information storage unit 1118 (step S1602). In the case of a release instruction, the information of the device specified by these is suppressed by referring to the block number in the condition record and the device type that specifies the release target included in the index rebuilding instruction. It is deleted from the suppression device information table stored in the device information storage unit 1118 (step S1603).

After updating the inhibiting device information table, the condition judging unit 1112 constructs an index table so as not to include an index for a condition record including the block number and device type registered in the inhibiting device information table. (Step S1604). After constructing the index table, the condition determining unit 1112
If the index table is referred to, and the block number or the device type is set as the comparison target first, a viewpoint of increasing the possibility of reducing the number of comparison determinations as to whether the event information should be notified to the management device 10 or not. Then, the comparison order is determined (step S1605), and after sorting all indices of the block number and the device type to be compared first in ascending order, for example,
First, indices having different values to be compared are linked by a pointer chain to make the index table usable (step S1606), and the index restructuring instruction corresponding process ends. This step S160
5 and S1606 are the same as the processing contents in steps S405 and S406 shown in the first embodiment.

The operation corresponding to the above-described index restructuring instruction will be briefly described below based on a specific example. It is assumed that the condition table has the contents illustrated in FIG. 8 and the index table has the contents illustrated in FIG.
A case where event information indicating that a device failure has occurred from the SW package stored in the slot 133 of the block 130 of the exchange 1100 will be described.

Since the event information satisfies the condition of the condition record 1331, the condition judgment unit 1112 transmits the event information to the management apparatus 10 via the event information output unit 113.
Since the index restructuring instruction of the condition record 1331 is the inhibition instruction (step S1601), the inhibition device information indicating the A156 package, the S6.3 package, and the VIFI package of the block having the third block number is stored in the inhibition device information storage unit 1118. (Step S1602). Here, assuming that nothing is registered in the inhibition device information table at first, the inhibition device information table has the contents shown in FIG. 9 as the execution result of step S1602.

After the registration in the inhibiting device information table, the condition judging unit 1112 refers to the inhibiting device information registered in the inhibiting device information table, and determines the number of the block whose block number is the third device to be inhibited. A156 package, S
The index table is constructed so that the condition record having the 6.3 package or the VIFI package as a source condition is not included in the index (step S160).
4), a comparison order is determined (step S1605), and index sorting and pointer chaining are performed (step S1606). As a result, the index table has the contents shown in FIG.

Since the condition record that is not registered in the index table is not searched by the search unit 114, event information indicating that the device recovery is completed is issued from the SW package having the third block number. Accordingly, until the suppression is released based on the instruction described in the condition record 1332, the A156 package of the block having the block number 3 and the S6.3
Event information originating from the package and the VIFI package is not notified to the management apparatus 10.

Next, the operation of the condition update unit 1117 when a condition record is registered from the management device 10 will be described. The operation of condition updating section 1117 is similar to that of the first embodiment.
Is basically the same as the operation of the condition updating unit 117 described in (1), except that the processing content of the construction of the index table (step S404 in FIG. 5) is changed to the step S16 in the index restructuring instruction corresponding processing of the condition determining unit 1112.
04.

That is, the condition updating unit 1117 refers to the inhibiting device information table stored in the inhibiting device information storage unit 1118, and stores a condition record including the block number and the device type registered in the inhibiting device information table. The operation is the same as that of the condition updating unit 117 in the first embodiment except that the index table is constructed so as not to include the index for.

As described above, the event notification control unit 1110
The condition record indicating the condition for notifying the event information may be added / changed / deleted at any time.In the case where the condition is satisfied, instruction information related to suppression of other event information is included, and based on this instruction information, By performing the control, the validity / invalidity control of the condition record triggered by the occurrence of a certain state is enabled.

Although the event notification control device according to the present invention has been described based on the embodiments, it is needless to say that the present invention is not limited to these embodiments. (1) In both embodiments, the event information sent from each device in the ATM exchange to the event notification control unit is output to the management device 10 only when the event information satisfies certain conditions. The notification control unit may store all the event information sent from each device in a hard disk or other storage medium in the ATM exchange in order to manage the occurrence history of the event information. In order to manage the notification history, the event information output from the event notification control unit to the management device 10 may be stored in a storage medium in the ATM exchange. (2) In both embodiments, the condition to be satisfied by the event information to be notified to the management device is the condition record. However, the condition for the event information to be suppressed from being notified may be the condition record. In this case, in order to respond to the index restructuring instruction described in the second embodiment, if the index restructuring instruction is a suppression instruction, a condition record for suppression is created by executing a condition record to execute the instruction. If the index restructuring instruction is a release instruction, the condition record added in response to the suppression instruction may be deleted in order to execute this. (3) In the first embodiment, the management device 10 is the ATM switch 1
In the second embodiment, the management apparatus 10 manages the ATM exchange 1100. However, the management apparatus 10 may manage other ATM exchanges. , Managed AT
The M switch is the management device 1 via the ATM switch 100 or the like.
0 may be notified of event information. In this case, the event information may include identification information about the ATM exchange. (4) The event information described in both embodiments may include various other information, and the size of each item that is a component of the event information is different from the size described in the embodiment. There may be. Further, in the embodiment, the number of types of the devices is ten, but the present invention is not limited thereto, and the number of types of the devices may be ten or more or less. (5) Regarding the grammar check at the time of registration of the condition record described in the first embodiment (step S401), no condition record having the same content must exist or a condition record having an overlapping condition must not exist. May be provided to check if the condition record satisfies this rule. (6) The calculation method for determining the comparison order between the block number and the device type described in the first embodiment is not limited to this. For example, a method of predicting the event occurrence rate and performing the calculation is used. Alternatively, the comparison order may be determined. If the comparison speed of the block number differs from the comparison speed of the device type due to a difference in the number of bits of information or the like, the comparison order may be determined in consideration of the comparison speed. (7) In the second embodiment, a device to be suppressed or released by an index restructuring instruction of a certain condition record is:
Although it is assumed that the device is located in the block of the block number of the condition record, the present invention is not limited to this. The device may be of another block. In this case, the block number is included in the index restructuring instruction. May also be described.

Further, in the second embodiment, the device is specified based on the suppression device information, and all the event information generated from the device can be suppressed. In addition, event information including a specific state code may be suppressed. For this purpose, the index restructuring instruction should include a description specifying the status code, and when rebuilding the index in accordance with this, a pointer to a condition record that includes the status code in the status code / error level condition should be set. You do not have to include it in the index. (8) In both embodiments, one of the block number and the device type shown as an item in the condition record may be unspecified. In this case, no designation means that there is no limitation on the conditions. In the creation of the index, the unspecified data may be regarded as one block number or one device type, and the condition record including the unspecified data may be always indexed regardless of the suppression device information. . In determining the comparison order, for example, the calculation may be performed excluding the unspecified one.

Further, only one of the block number and the device type may be used as the item element of the index. Even in this case, the suppression control of the event information based on the index restructuring instruction is possible. Even if it is not a method of sequentially comparing each index item, the index information may be sorted based on a predetermined rule and the event information may be compared with the index using a binary search method or another method. Good.

Further, other items such as a status code and an error level in the event information, or only the upper several bits of a certain item may be used as an item element of the index of the condition record. May be determined so as to increase the possibility of reducing the number of comparison determinations by a certain calculation. When it is necessary to support many types of devices, for example, when there are many types of devices in an ATM exchange, the device types are hierarchized into a main type and a sub-type, and each is set as an item element of an index. Is also good. However, the items that can be used as indices are not conditional expressions that require complicated calculations, but are limited to items that can be simply compared to determine whether they are the same, such as a fixed-length bit string. (9) The event information notification control process (see FIG. 6) described in the first embodiment compares the block number before the device type, but compares the set of the block number and the device type at once. You may do it. In this case, components related to the comparison order in the comparison order storage unit and the like are not required. (10) The condition records described in both embodiments may further include destination information for notification, and the event notification control unit may notify event information to the destination indicated in the destination information. Good. In this case, if the destinations are different, condition records having overlapping conditions may exist, and the process of step S510 may be performed after the process of step S511. (11) In both embodiments, only the case where the event notification control device according to the present invention is implemented as an event notification control unit in an ATM exchange has been described, but the event notification control device according to the present invention What is necessary is just to selectively output a part of the input event information to the outside, and may be used by being included in equipment other than the ATM exchange. (12) A machine language program for realizing the function related to the event notification control (the procedure shown in the flowcharts of FIGS. 5, 6, and 10) of the event notification control device according to the present invention as described in the embodiment is recorded. Recorded on media and distributed
It may be a target for sale. Such a recording medium includes I
C card, optical disk, flexible disk, ROM
The machine language programs recorded in these are
It is provided for use by being installed on a general-purpose computer. That is, the general-purpose computer sequentially executes the installed machine language program to realize the event notification control function of the event notification control device according to the present invention.

A computer program for causing a general-purpose computer to execute a processing procedure for realizing the above-described event notification control function can also be distributed and distributed via a recording medium such as a hard disk and various communication paths. .

[0084]

As apparent from the above description, the event notification control device according to the present invention is an event notification control device that receives event information including a plurality of items and outputs only event information satisfying a predetermined condition. A condition storage unit that stores a plurality of condition records indicating the predetermined condition, the condition storage unit including a plurality of condition items that are conditions corresponding to the plurality of items of the event information, and a plurality of the condition records stored in the condition storage unit. An index that is used to search for a specific condition record from a condition record, includes at least one condition item among a plurality of condition items in the condition record as a comparison element for search, and includes index information of the condition record. Index storage means for storing the content of the comparison element of the index,
By comparing the content of the item corresponding to the comparison element in the received event information with the content of the condition item that is the comparison element, the condition record in which the content of the corresponding item in the event information matches the content of the condition item is compared with the condition record. A search unit that searches from the storage unit; and a condition determination output unit that outputs the event information only when the content of the event information satisfies all the conditions indicated in the condition record searched by the search unit. It is characterized by the following.

As a result, a condition record having the same content as a condition item used as a comparison element is indicated by one index. Usually, the number of indexes is smaller than the number of condition records. According to the search using, the number of comparisons can be reduced as compared with the case where individual condition records are brute-force matched with event information, and the comparison judgment can be speeded up.
In addition, if a condition item whose contents can be compared at high speed is selected as a comparison element of the index, the speed of comparison judgment can be increased.

[0086] Further, the index has a plurality of comparison elements, and the search means determines the content of each comparison element of the index and the content of each item corresponding to each comparison element in the received event information. By searching for a condition record in which the contents of all the condition items that are the comparison elements match the contents of the corresponding items in the event information, and the comparison in the search means performs the comparison as long as the comparison result matches. Each comparison element in the index may be sequentially compared, and after the comparison result becomes inconsistent, the comparison of other comparison elements may not be performed.

As a result, if the comparison order of the comparison elements is determined based on a certain standard, the possibility of speeding up the comparison judgment as a whole is increased. For example, when the comparison speed for a certain comparison element is faster than the comparison speed for another comparison element, the comparison speed is compared with the item corresponding to the comparison element in the event information in order from the comparison element with the fastest comparison speed,
If the comparison results do not match, if no comparison is made for the other comparison elements, the processing is speeded up comprehensively when a large number of event information are processed.

The event information is sent from any one of the plurality of managed devices, and information indicating the type of the source managed device, information indicating the arrangement of the managed device, and the state of the managed device. The condition record includes a condition item that limits the type of the managed device, a condition item that limits the arrangement of the managed device, and a condition related to the state of the managed device. A condition item, and the index may be information that limits the type of the device to be managed and information that limits the arrangement of the device to be managed as comparison elements for a search. it can.

Thus, when the event information includes contents indicating various states of each device and the condition record includes detailed conditions for limiting the states,
Even if a large number of condition records exist, the event notification control device according to the present invention uses the information for identifying the device of the source of the event information as an index, so that the condition notification can be performed at high speed by focusing on the source. Condition comparison can be performed quickly to narrow down records. Generally, in the management of internal devices such as exchanges, the number of devices to be managed is smaller than the number of possible states of the devices. If the condition records are narrowed down by performing the comparison, it is relatively easy to make a comparison judgment due to the small data size of the information for identifying the source device of the event information. The determination as to whether or not the condition indicated in the condition record is satisfied can be speeded up.

The event notification control device further receives an instruction for additional registration, change or deletion of the condition record stored in the condition storage means, and in response thereto, additionally registers the condition record, changes the content, Or, a condition updating means for performing deletion, and after the additional registration, content change or deletion has been performed by the condition updating means, the index storage means is adapted to match the condition record stored in the condition storage means. Index comparison means for rebuilding the stored index, and comparison order determination means for determining a comparison order for each comparison element of the index, wherein the comparison in the search means is performed by the comparison order determination means May be performed according to the comparison order determined by

Thus, when a specific device to be managed is replaced for maintenance or the like, the replacement is performed after registering a condition record so that event information is not output even if a failure related to the device to be managed occurs. It is also easy to perform the work and delete the condition record after the replacement work is completed. Therefore, it is possible to dynamically perform external control such as preventing unnecessary output of event information and outputting necessary event information. Even if a condition record indicating a condition for outputting event information is externally registered, changed, or deleted, the index is reconstructed accordingly and the comparison order of each comparison element is determined. A comparison can be made, and as a result, the speed of the judgment as to whether or not to output the event information can be increased.

The comparison order determining means may determine the comparison order according to a predetermined criterion based on the number of types of values taken by the content of each comparison element of the index. Further, the predetermined criterion is to calculate, for each comparison element, a ratio of the number of types of values taken by the content of the comparison element to the number of possible values of an item corresponding to the comparison element in the event information. The order may be determined in ascending order of the obtained ratio.

Thus, the comparison order for each comparison element of the index is determined in relation to the number of different values of the contents of each comparison element. Therefore, the event information is stored in the optimum comparison order according to the contents of the condition record. Item and index comparison element can be compared. Here, the optimal comparison order refers to a comparison order that can reduce the number of comparisons for each comparison element of the index when viewed as a whole. The comparison order is such that the comparison element increases the probability that a subsequent comparison will not be necessary. Therefore,
As a result, the number of comparisons can be reduced, and as a result, the speed of determining whether to output event information can be increased.

The event information is sent from any one of the plurality of managed devices, and includes information specifying the source managed device and information indicating the status of the managed device as items. Includes a condition item for limiting the managed device, a condition item indicating a condition related to a state of the managed device, and suppression control instruction information that is information indicating a transmission source of a suppression target, and the index includes the The information that limits the management target device is used as a comparison element for search, and the event notification control device further includes a case where the content of the event information satisfies all the conditions indicated in the condition record searched by the search unit. A condition source including a transmission source indicated by the suppression control instruction information included in the condition record as a condition item for limiting the managed device. For over de so as not to be searched using the index may be to include an index reconstructing means for reconstructing the indexes.

Thus, for example, when event information indicating a device state such as a failure is sent from a plurality of managed devices, the event is triggered by a primary failure that has occurred in one managed device, and the other managed device has a second fault. When the next failure occurs, the event information indicating the secondary failure can be prevented from being output to the management device that manages the managed device. That is, even if the external device does not instruct registration, change, or deletion of the condition record indicating the output condition of the event information, the index is dynamically re-created based on the event information so as not to generate the index indicating the specific condition record. Since the suppression control to be constructed is performed, the output of other event information generated in conjunction with the generation of certain event information can be immediately suppressed, and unnecessary output of event information can be prevented. Further, as a result of the suppression control, the index indicating the specific condition record disappears, so that the search for other condition records can be performed more quickly, and the speed of determining whether to output the event information can be increased.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a network system including an ATM exchange according to a first embodiment of the present invention.

FIG. 2 is a configuration diagram of the ATM switch 100 according to the first embodiment.

FIG. 3 is a diagram showing a data structure and an example of contents of event information.

FIG. 4 is a diagram illustrating a data structure of a condition table and an index table stored in a condition storage unit and an example of contents thereof.

FIG. 5 is a flowchart showing an operation of condition record registration of a condition update unit 117.

FIG. 6 is a flowchart showing notification control processing of event information by an event notification control unit 110;

FIG. 7 is a configuration diagram of an ATM exchange 1100 according to a second embodiment.

FIG. 8 is a diagram showing a data structure of a condition table and an index table stored in a condition storage unit 1116 and an example of the contents thereof.

FIG. 9 is a diagram illustrating a data structure of a suppression device information table and an example of the content thereof.

FIG. 10 is a flowchart illustrating an index restructuring instruction corresponding process performed by an event notification control unit 1110.

FIG. 11 is a diagram showing a configuration of a conventional event report processing circuit.

[Explanation of symbols]

 Reference Signs List 10 management device 100, 1100 ATM exchange 110, 1110 event notification control unit 111 event information acquisition unit 112, 1112 condition determination unit 113 event information output unit 114 search unit 115 comparison order storage unit 116, 1116 condition storage unit 117, 1117 condition update Unit 1118 Suppression device information storage unit 200 Event information 210 Device number 211 Block number 212 Slot number 220 Device type 230 Status code 240 Error level 310 Index table 311 Block number 312 Device type 313 Pointer 314 Next pointer 320, 1320 Condition table 321 Record number 322 Block number 323 Device type 324 Status code / error level condition 1325 Index rebuilding instruction 1600 Suppressed device information Bull

Claims (8)

[Claims] 1. An event notification control device that receives event information including a plurality of items and outputs only event information satisfying a predetermined condition, wherein the plurality of conditions are conditions corresponding to the plurality of items of the event information. A condition storage unit that stores a plurality of condition records that include an item and indicates the predetermined condition; and a condition storage unit that is used to search for a specific condition record from the plurality of condition records stored in the condition storage unit. An index storage unit that stores at least one condition item among the plurality of condition items as a comparison element for search and stores an index including index information of the condition record; a content of the comparison element of the index; By comparing with the content of the item corresponding to the comparison element in the event information A search unit that searches the condition storage unit for a condition record in which the content of the condition item that is the comparison element matches the content of the corresponding item in the event information; and a condition record that is indicated by the condition record searched by the search unit. An event notification control device that outputs condition information only when the contents of the event information satisfy all of the conditions. 2. The method according to claim 1, wherein the comparing means includes a plurality of comparison elements in the index, and wherein the search unit determines a content of each comparison element of the index and a content of each item corresponding to each of the comparison elements in the received event information. By searching for a condition record in which the contents of all the condition items that are the comparison elements match the contents of the corresponding item in the event information, the comparison in the search means is performed as long as the comparison result matches. 2. The event notification control device according to claim 1, wherein each comparison element in the index is sequentially compared, and after the comparison result becomes inconsistent, the comparison of the other comparison elements is not performed. 3. The event information is sent from any of a plurality of managed devices, and information indicating a type of a managed device as a transmission source, information indicating an arrangement of the managed device, and a state of the managed device are stored in the event information. The condition record includes a condition item that limits the type of the managed device, a condition item that limits the arrangement of the managed device, and a condition related to the state of the managed device. And a condition item, wherein the index is information that limits the type of the device to be managed and information that limits the arrangement of the device to be managed as comparison elements for a search. The event notification control device according to claim 2. 4. The event notification control device further receives an instruction for additional registration, change or deletion of a condition record stored in the condition storage means, and additionally registers a condition record, changes a content, Or a condition updating means for performing deletion, and after the additional registration, content change or deletion is performed by the condition updating means, the index storage means is adapted to match the condition record stored in the condition storage means. Index comparison means for reconstructing the stored index; and comparison order determination means for determining a comparison order for each comparison element of the index, wherein the comparison in the search means is performed by the comparison order determination means. The event according to claim 2 or 3, wherein the event is performed in accordance with the comparison order determined by (1). Intellectual control device. 5. The comparison order determining unit according to claim 4, wherein the comparison order determination unit determines the comparison order according to a predetermined criterion based on the number of types of values taken by the content of each comparison element of the index. Event notification control device. 6. The predetermined criterion is a ratio of the number of types of values taken by the content of the comparison element to the number of possible values of an item corresponding to the comparison element in the event information. 6. The standard for calculating the order and determining the order in ascending order of the obtained ratio.
The event notification control device according to the above. 7. The event information is sent from any one of a plurality of managed devices, and includes, as items, information specifying a source managed device and information indicating a status of the managed device. Includes a condition item for limiting the managed device, a condition item indicating a condition related to a state of the managed device, and suppression control instruction information that is information indicating a transmission source of a suppression target. The information that limits the management target device is used as a comparison element for search, and the event notification control device further includes a case where the content of the event information satisfies all conditions indicated in the condition record searched by the search unit. A condition record including a transmission source indicated by the suppression control instruction information included in the condition record as a condition item for limiting the managed device. 2. The event notification control device according to claim 1, further comprising: an index reconstructing unit that reconstructs the index so that the index cannot be searched using the index. 8. An event notification control process of receiving event information including a plurality of items and outputting only event information satisfying a predetermined condition includes a plurality of condition items which are conditions corresponding to the plurality of items of the event information. A plurality of condition records indicating the predetermined condition are stored, and a plurality of comparison elements for searching for a plurality of condition items in the condition record are used for searching for a specific condition record from the plurality of condition records. A computer-readable storage medium storing a control program for causing a computer including a memory to store an index to be executed, wherein the event notification control process includes: a content of each comparison element of the index; By comparing the content of each item corresponding to each of the comparison elements, all of the comparison elements are compared. A search step of searching for a condition record in which the content of the condition item matches the content of the corresponding item in the event information; and And a condition determination output step of outputting the event information only when the condition is satisfied.The comparison in the search step sequentially compares each comparison element in the index as long as the comparison result matches. A recording medium that does not perform a comparison for another comparison element after the recording medium has been changed.