JP2016021663A - Monitoring device and program of the same - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a monitoring device and a program of the device which suppress repeated output of information indicating an identical event.SOLUTION: The monitoring device relating to one embodiment of this invention comprises: a receiver for receiving telegraphic messages with inspection codes from a monitoring target; a determination unit for determining whether the respective inspection codes added to the telegraphic messages received by the receiver are identical or not; and an output unit that, when the determination unit determines that the respective inspection codes are identical, outputs one of the telegraphic messages having the identical inspection code.SELECTED DRAWING: Figure 13

Description

  The present invention relates to an apparatus and a program for monitoring a target event or device state. The present invention also relates to an apparatus and a program for monitoring a target event or device state by notifying an administrator of information indicating a state change such as occurrence of an event or abnormal operation of a monitoring target device.

  In a system configured by connecting a plurality of devices such as servers via a network, it is important to manage the status of each device constituting the system in order to stably operate the system. In particular, in a system that does not allow abnormal operation, such as a financial system, it is necessary to more strictly manage and operate devices constituting the system. In such a system, the state of each device (monitoring target device) constituting the system is monitored by a plurality of monitoring devices. Therefore, when an operation abnormality occurs in a certain device, information indicating the operation abnormality is transmitted from a plurality of monitoring devices, so that redundant operation abnormality information is notified to the administrator.

  As described above, as a technique for receiving redundant information from a monitoring target device or a monitoring device, for example, Patent Document 1 discloses a duplication of a plurality of function modules and a device monitoring control unit that performs centralized monitoring and control. An invention of a configuration connected via a control bus is disclosed. Patent Document 1 discloses an invention in which duplicated response data is received from a lower-level controlled module, and reception of correct data is selected and controlled.

JP-A-5-250344

  According to Patent Document 1, it is ensured that duplicated response data is received, whether or not it is correct data, and correct control is performed based on the response data. However, if any of them is correct, the duplicated data is received as it is by the device monitoring control unit, and the amount of data recorded in the device monitoring control unit increases.

  Further, when the data is displayed on the monitor for monitoring, all the cases are displayed. Therefore, the monitoring operator needs to confirm duplicated data from the data displayed on the monitoring monitor, and there is a problem that the monitoring burden increases. In particular, when duplicate data is displayed separately on the monitoring monitor, there is a problem that the monitoring operator overlooks because of the large amount of information.

  An object of this invention is to provide the apparatus state monitoring apparatus which suppresses that the information which shows the same event is output repeatedly, and its program.

  According to an embodiment of the present invention, a receiving unit that receives a message indicating a monitoring target device status from a monitoring target, to which a check code is added, and each check code that is added to a plurality of messages received by the receiving unit. A determination unit that determines whether or not the same check code is the same, and an output unit that outputs one of the messages having the same check code when the determination unit determines that the check codes are the same. An apparatus state monitoring apparatus is provided.

  According to an embodiment of the present invention, a receiving unit that receives a message indicating a monitored device state from the monitoring target and a message that indicates the same monitored device state among a plurality of messages received by the receiving unit A check code adding unit for adding the check code, a determination unit for determining whether or not each check code added to a plurality of messages received by the receiving unit is the same, and a determination unit for each check code When it determines with it being the same, an apparatus state monitoring apparatus provided with the output part which outputs one message | telegram among the messages | telegrams which have the same test code | symbol is provided.

  Moreover, in said apparatus state monitoring apparatus, a test | inspection code | symbol is produced | generated based on one part or all part of a message | telegram, and has a fixed format irrespective of the format of a message | telegram. In addition, the determination unit may determine a message generated or received within a predetermined time after the reception unit generates or receives the message.

  Moreover, said apparatus state monitoring apparatus may further be provided with the recording part which records a message | telegram. In that form, the determination unit determines whether or not the first check code added to the first message received by the reception unit is the same as the second check code added to the second message recorded in the recording unit. If it is determined that the first check code and the second check code are not the same, the first message is recorded in the recording unit.

  Moreover, said apparatus state monitoring apparatus may be further provided with the monitoring part which monitors a monitoring object for every predetermined time interval. In that form, when the monitoring unit detects a change in the state of the device to be monitored, it generates a message and transmits it to the receiving unit.

  According to an embodiment of the present invention, a message to which a check code is added is received from a monitoring target, and whether or not each check code added to a plurality of received messages is the same is determined. When it is determined that the codes are the same, a program is provided that causes the device state monitoring device to output one of the messages having the same check code.

  According to an embodiment of the present invention, a message indicating a monitoring target device status is received from the monitoring target, and the same check code is added to the messages indicating the same monitoring target device status among the plurality of received messages. It is determined whether or not each check code added to a plurality of received messages is the same, and if it is determined that each check code is the same, one of the messages having the same check code is There is provided a program characterized by causing a device status monitoring device to output a message.

  According to an embodiment of the present invention, a receiving unit that receives event information that is generated based on an event and that includes an identifier that identifies the event, and each identifier that is added to a plurality of event information received by the receiving unit. A determination unit that determines whether the identifiers are the same, and an output unit that outputs one event information of the event information to which the same identifier is added when the determination unit determines that the identifiers are the same, and Are provided.

  According to an embodiment of the present invention, a reception unit that receives event information generated based on an event, and the same identifier is added to event information indicating the same event among a plurality of event information received by the reception unit. An identifier adding unit that performs determination, a determination unit that determines whether or not each identifier added to a plurality of event information received by the receiving unit is the same, and a determination unit that determines that each identifier is the same And an output unit that outputs one piece of event information among the event information to which the same identifier is added.

  According to an embodiment of the present invention, a reception unit that receives event information generated based on an event, and an identifier unique to the event information is generated based on all or part of the event information received by the reception unit. There is provided a monitoring device including an identifier adding unit added to event information.

  According to an embodiment of the present invention, the first event information and the second event are generated by generating the first identifier and the second identifier added to the first event information and the second event information generated based on the event, respectively. An identifier adding unit to be added to the information, a determination unit for comparing the first identifier and the second identifier, and the first event information or the first event information when the determination unit determines that the first identifier and the second identifier are the same And an output unit that outputs any one of the second event information.

  The apparatus state monitoring apparatus according to the present invention has an effect of providing an apparatus state monitoring apparatus and a program thereof that suppress the redundant output of information indicating the same event.

It is the schematic which shows the functional block diagram of the monitoring apparatus which concerns on Embodiment 1 of this invention. It is the schematic which shows the hardware constitutions of the monitoring apparatus which concerns on Embodiment 1 of this invention. It is a figure which shows the operation | movement flow of the monitoring apparatus which concerns on Embodiment 1 of this invention. It is the schematic which shows the functional block diagram of the monitoring apparatus which concerns on Embodiment 2 of this invention. It is a figure which shows the operation | movement flow of the monitoring apparatus which concerns on Embodiment 2 of this invention. It is the schematic which shows the functional block diagram of the monitoring apparatus which concerns on Embodiment 3 of this invention. It is a figure which shows the operation | movement flow of the monitoring apparatus which concerns on Embodiment 3 of this invention. It is the schematic which shows the functional block diagram of the monitoring apparatus which concerns on Embodiment 4 of this invention. It is a figure which shows the operation | movement flow of the monitoring apparatus which concerns on Embodiment 4 of this invention. It is the schematic which shows the functional block diagram of the monitoring apparatus which concerns on Embodiment 5 of this invention. It is a figure which shows the operation | movement flow of the monitoring apparatus which concerns on Embodiment 5 of this invention. It is a figure which shows the concept of the apparatus state monitoring system which concerns on Embodiment 6 of this invention. It is the schematic which shows the functional block diagram of the apparatus state monitoring apparatus which concerns on Embodiment 6 of this invention. It is a figure which shows the operation | movement flow of the apparatus state monitoring system which concerns on Embodiment 6 of this invention. It is a figure which shows the operation | movement flow of the apparatus state monitoring apparatus which concerns on Embodiment 6 of this invention. It is a figure which shows the operation | movement flow of the apparatus state monitoring apparatus which concerns on the modification of Embodiment 6 of this invention. It is the schematic which shows the functional block diagram of the apparatus state monitoring apparatus which concerns on Embodiment 7 of this invention. It is a figure which shows the operation | movement flow of the apparatus state monitoring system which concerns on Embodiment 7 of this invention. It is a figure which shows the operation | movement flow of the apparatus state monitoring apparatus which concerns on Embodiment 7 of this invention. It is a figure which shows an example of the message | telegram and test code | symbol which the test code | symbol addition part of the apparatus state monitoring apparatus which concerns on Embodiment 7 of this invention produces | generates. It is a figure which shows the operation | movement flow of the apparatus state monitoring apparatus which concerns on the modification of Embodiment 7 of this invention. It is the schematic which shows the functional block diagram of the apparatus state monitoring apparatus which concerns on Embodiment 8 of this invention. It is a figure which shows the operation | movement flow of the apparatus state monitoring apparatus which concerns on Embodiment 8 of this invention. It is the schematic which shows the functional block diagram of the apparatus state monitoring apparatus which concerns on Embodiment 9 of this invention. It is a figure which shows the operation | movement flow of the apparatus state monitoring apparatus which concerns on Embodiment 9 of this invention. It is the schematic which shows the functional block diagram of the apparatus state monitoring apparatus which concerns on Embodiment 10 of this invention. It is a figure which shows the operation | movement flow of the apparatus state monitoring apparatus which concerns on Embodiment 10 of this invention. It is a figure which shows the concept of the sensor monitoring system which concerns on Embodiment 11 of this invention. It is the schematic which shows the functional block diagram of the sensor monitoring apparatus which concerns on Embodiment 11 of this invention.

  Hereinafter, a monitoring device and a program thereof according to the present invention will be described with reference to the drawings. However, the monitoring device and the program thereof according to the present invention can be implemented in many different modes, and are not construed as being limited to the description of the embodiments described below. Note that in the drawings referred to in this embodiment, the same portions or portions having similar functions are denoted by the same reference numerals, and repetitive description thereof is omitted.

<Embodiment 1>
The monitoring apparatus and its program according to Embodiment 1 of the present invention will be described in detail with reference to FIGS. The first embodiment describes an example in which event information to which an identifier that identifies an event (event) that occurs in the monitoring target is added is generated and transmitted to the monitoring device.

[Overview of monitoring system]
FIG. 1 is a schematic diagram showing a functional block diagram of a monitoring apparatus according to Embodiment 1 of the present invention. As shown in FIG. 1, the monitoring system according to the present invention includes a monitoring device 210, a monitoring target 220, and an external device 230. In addition, the monitoring device 210 includes a reception unit 211, a determination unit 212, and an output unit 213. According to FIG. 1, the monitoring target 220 and the reception unit 211 are connected, the reception unit 211 and the determination unit 212 are connected, the determination unit 212 and the output unit 213 are connected, and the output unit 213 and the external device 230 are connected. It is connected.

  The monitoring device 210 may be a device state monitoring device that monitors a device state such as an operation abnormality that occurs in the device to be monitored 220, and a sensor monitoring device that monitors a sensor that detects an abnormality occurring in the facility. It may be.

  The receiving unit 211 receives event information that is generated based on the above-described event that has occurred in the monitoring target 220 and to which an identifier that identifies the event is added. The determination unit 212 determines whether or not the identifiers added to the plurality of event information received by the reception unit 211 are the same. When the determination unit 212 determines that the identifiers are the same, the output unit 213 outputs one event information among a plurality of pieces of event information to which the same identifier is added. Each of these functional units may be provided in one device or server, or may be provided in a distributed manner in a plurality of devices or servers.

[Hardware configuration of monitoring device]
FIG. 2 is a schematic diagram illustrating a hardware configuration of the monitoring apparatus according to the first embodiment of the present invention. According to FIG. 2, the monitoring apparatus 210 includes a control unit 221, a hard disk 222, and a communication unit 223. The control unit 221 includes a central processing unit (CPU), and storage devices such as a register and a memory. The control unit 221 causes the monitoring device 210 to receive event information from the monitoring target 220 by causing the CPU to execute a program stored in the memory, and determines whether or not there is duplicate event information. Output to the external device 230. Further, the storage device of the control unit 221 reads and stores a program necessary for arithmetic processing from the hard disk as necessary. The hard disk 222 is a memory capable of storing a large amount of data. The hard disk 222 stores programs necessary for arithmetic processing and temporarily stores event information and identifiers received from the monitoring target 220. The communication unit 223 connects the monitoring device 210 and the monitoring target 220, and the monitoring device 210 and the external device 230 to control data input / output.

  In FIG. 2, the monitoring device 210 is expressed as one device. However, the monitoring device 210 does not have to be realized as one device, and may be configured by a plurality of devices or servers as described later, for example. When the monitoring device 210 includes a plurality of devices or servers, the hardware illustrated in FIG. 2 may be realized by the plurality of devices or servers, and each of the plurality of devices or servers may include the hardware. You may have.

[Operation flow of monitoring device]
FIG. 3 is a diagram illustrating an operation flow of the monitoring apparatus according to the first embodiment of the present invention. In FIG. 3, the operation flow of the monitoring apparatus 210 will be described in detail using a flowchart.

  As shown in FIG. 3, the monitoring device 210 receives event information with an identifier added from the monitoring target 220 (step S101), and whether or not each identifier added to the received plurality of event information is the same. (Step S102), and when it is determined in step S102 that the identifiers to be determined are the same (“Yes” in step S103), one of the event information having the same identifier Event information is selected (step S104) and output (S105). If it is determined that the identifiers of the received event information are not the same (“No” in step S103), the monitoring apparatus 210 outputs the event information as it is (step S105). The above steps may be executed by a program stored in the memory of the control unit 221 of the monitoring device 210.

  As described above, according to the operation method of the monitoring system and the monitoring apparatus according to the first embodiment of the present invention, the same identifier is added to the event information corresponding to the same event that has occurred in the monitoring target 220. Duplicate output of information indicating the same event can be suppressed. As a result, the burden on the administrator who monitors the monitoring target 220 using the external device 230 can be reduced. Further, the capacity of event information stored in the monitoring device 210 can be reduced.

<Embodiment 2>
With reference to FIGS. 4 and 5, the monitoring apparatus and its program according to Embodiment 2 of the present invention will be described in detail. In the second embodiment, an example will be described in which a monitoring device generates an identifier for event information generated by a monitoring target and adds the identifier to the event information.

[Overview of monitoring system]
FIG. 4 is a schematic diagram showing a functional block diagram of a monitoring apparatus according to Embodiment 2 of the present invention. As shown in FIG. 4, the monitoring system 20 according to the present invention includes a monitoring device 240, a monitoring target 220, and an external device 230. The monitoring device 240 includes a reception unit 211, an identifier addition unit 214, a determination unit 212, and an output unit 213. According to FIG. 4, the monitoring target 220 and the receiving unit 211 are connected, the receiving unit 211 and the identifier adding unit 214 are connected, the identifier adding unit 214 and the determining unit 212 are connected, and the determining unit 212 and the output unit 213. Are connected, and the output unit 213 and the external device 230 are connected.

  The receiving unit 211 receives event information generated based on the event generated in the monitoring target 220. The identifier adding unit 214 generates the same identifier for the same event that has occurred in the monitoring target 220 among the plurality of event information received by the receiving unit 211, and adds the same identifier to the event information. The determination unit 212 determines whether or not the identifiers added to the plurality of event information received by the reception unit 211 are the same. When the determination unit 212 determines that the identifiers are the same, the output unit 213 outputs one event information among a plurality of pieces of event information to which the same identifier is added. Each of these functional units may be provided in one device or server, or may be provided in a distributed manner in a plurality of devices or servers.

  Since the hardware of the monitoring device 240 according to the second embodiment can be the same as that of the monitoring device 10 according to the first embodiment (FIG. 2), description thereof is omitted here.

[Operation flow of monitoring device]
FIG. 5 is a diagram showing an operation flow of the monitoring apparatus according to the second embodiment of the present invention. In FIG. 5, the operation flow of the monitoring device 240 will be described in detail using a flowchart.

  As shown in FIG. 5, the monitoring device 240 receives event information generated based on an event that has occurred in the monitoring target 220 from the monitoring target 220 (step S201), and among the received event information, the monitoring target 240 The same identifier is generated for the same event generated in 220 and added to the event information (step S202), and it is determined whether or not each identifier added to the received plurality of event information is the same. (Step S203) When it is determined that the identifiers to be determined in Step S203 are the same (“Yes” in Step S204), one event information is selected from the event information having the same identifier. (Step S205) and output (S206). When it is determined that the identifiers of the received event information are not the same (“No” in step S204), the monitoring device 240 outputs the event information as it is (step S206). The above steps may be executed by a program stored in the memory of the control unit 221 of the monitoring device 210.

  As described above, according to the operation method of the monitoring system and the monitoring apparatus according to the second embodiment of the present invention, even if the monitoring target 220 does not have a function of adding an identifier to event information, the same event It can suppress that the information which shows is output repeatedly. As a result, the burden on the administrator who monitors the monitoring target 220 using the external device 230 can be reduced. Further, the capacity of event information stored in the monitoring device 210 can be reduced.

<Embodiment 3>
The monitoring apparatus and its program according to Embodiment 3 of the present invention will be described in detail with reference to FIGS. In the third embodiment, the presence or absence of duplicate event information is determined by comparing the identifier of the received event information with the identifier of the event information received and recorded in the past.

[Overview of monitoring system]
FIG. 6 is a schematic diagram showing a functional block diagram of a monitoring apparatus according to Embodiment 3 of the present invention. As shown in FIG. 6, the monitoring system 30 according to the present invention includes a monitoring device 250, a monitoring target 220, and an external device 230. The monitoring device 250 includes a reception unit 211, a determination unit 212, an output unit 213, and a recording unit 215. According to FIG. 6, the monitoring target 220 and the receiving unit 211 are connected, the receiving unit 211 and the determining unit 212 are connected, the determining unit 212, the output unit 213, and the recording unit 215 are connected, and the output unit 213 and the external unit A device 230 is connected. The functional block diagram of the monitoring device 250 shown in FIG. 6 is similar to the functional block diagram of the monitoring device 210 shown in FIG. 1, but the monitoring device 250 further includes a recording unit 215 that records event information received in the past. This is different from the monitoring device 210 in that respect.

  Since the hardware of the monitoring device 250 according to the third embodiment can be the same as that of the monitoring device 10 according to the first embodiment (FIG. 2), description thereof is omitted here.

[Operation flow of monitoring device]
FIG. 7 is a diagram illustrating an operation flow of the monitoring apparatus according to the third embodiment of the present invention. In FIG. 7, the operation flow of the monitoring device 250 will be described in detail using a flowchart.

  As illustrated in FIG. 7, the monitoring device 250 receives the first event information to which the first identifier is added from the monitoring target 220 (Step S301), and the first identifier added to the received first event information; It is determined whether or not the second identifier added to the second event information recorded in the recording unit 215 is the same (step S302). When it is determined that the first identifier and the second identifier are not the same (“none” in step S303), the monitoring device 250 records the first event information and the first identifier (step S304), and the first event information The first identifier is output (step S305). When it is determined that the first identifier and the second identifier are the same (“Yes” in step S303), the monitoring device 250 discards or invalidates the first event information and the first identifier (step S306). ). The above steps may be executed by a program stored in the memory of the control unit 221 of the device state monitoring apparatus 250.

  As described above, according to the operation method of the monitoring system and the monitoring apparatus according to the third embodiment of the present invention, whether or not event information to which the same identifier as the identifier of the received event information is added exists in the recording unit 215. Thus, it is possible not only to determine whether or not there is duplication of event information, but also to automatically record or discard event information according to the necessity for determining whether or not there is duplication of event information. Therefore, it is possible to determine the duplication of event information with a smaller amount of data.

<Embodiment 4>
The monitoring apparatus and its program according to Embodiment 4 of the present invention will be described in detail with reference to FIGS. Embodiment 4 is a method for determining whether or not there is duplicate event information by comparing an identifier of received event information with an identifier of event information received and recorded in the past. Set the validity period.

[Overview of monitoring system]
FIG. 8 is a schematic diagram showing a functional block diagram of a monitoring apparatus according to Embodiment 4 of the present invention. As shown in FIG. 8, the monitoring system 40 according to the present invention includes a monitoring device 260, a monitoring target 220, and an external device 230. In addition, the monitoring device 260 includes a reception unit 211, a determination unit 212, an output unit 213, a recording unit 215, and an effective period management unit 216. According to FIG. 8, the monitoring target 220 and the receiving unit 211 are connected, the receiving unit 211 and the determining unit 212 are connected, and the determining unit 212, the output unit 213, the recording unit 215, and the effective period management unit 216 are connected. The output unit 213 and the external device 230 are connected.

  The functional block diagram of the monitoring device 260 shown in FIG. 8 is similar to the functional block diagram of the monitoring device 250 shown in FIG. 6, but is different from the monitoring device 250 in that it further includes an effective period management unit 216. Here, the determination unit 212 sets the second event information generated or received within a predetermined period from the generation or reception of the first event information as a determination target, but the effective period management unit 216 is set in advance. The predetermined period is managed.

  Since the hardware of the monitoring device 260 of the fourth embodiment can be the same as that of the monitoring device 10 of the first embodiment (FIG. 2), description thereof is omitted here.

[Operation flow of monitoring device]
FIG. 9 is a diagram illustrating an operation flow of the monitoring apparatus according to the fourth embodiment of the present invention. In FIG. 9, the operation flow of the monitoring device 260 will be described in detail using a flowchart. The operation flow illustrated in FIG. 9 is similar to the operation flow illustrated in FIG. 7, but the operation flow illustrated in FIG. 9 includes the first event information when it is determined that the first identifier and the second identifier are the same. 7 is an operation flow shown in FIG. 7 in that it has an operation for determining whether the time when the second event information is generated or received is within a predetermined period set in advance. Is different. Here, in FIG. 9, steps in which the same operation as in FIG. 7 is performed are denoted by the same reference numerals as in FIG. Description of steps already described in FIG. 7 is omitted here, and differences from FIG. 7 are mainly described.

  In the operation flow of FIG. 7, when it is determined that the first identifier and the second identifier are the same (“Yes” in step S303), the monitoring device 250 discards or invalidates the first event information and the first identifier. (Step S306). However, in the operation flow of FIG. 9, when it is determined that the first identifier and the second identifier are the same (“Yes” in step S303), the monitoring device 260 has generated or received the first event information. It is determined whether the time and the time when the second event information is generated or received are within a predetermined period (step S401).

  When the validity period management unit 216 determines that the time when the first event information is generated or received and the time when the second event information is generated or received are within a predetermined period (“Yes” in step S401) The monitoring device 260 discards or invalidates the first event information and the first identifier (step S306). On the other hand, when it is determined that the above two times are not within the predetermined period (“No” in step S401), it is determined that the first event information and the second event information are not targets for determining overlap. That is, similarly to the case where it is determined that the first identifier and the second identifier are not the same (“none” in step S303), the monitoring device 260 records the first event information and the first identifier (step S304), and One event information and a first identifier are output (step S305).

  As described above, according to the operation method of the monitoring system and the monitoring apparatus according to the fourth embodiment of the present invention, only the event information generated or received within a predetermined period is set as a duplication determination target. Accidental matches can be further reduced, and the detection efficiency of duplicate event information is improved.

<Embodiment 5>
The monitoring apparatus and its program according to the fifth embodiment of the present invention will be described in detail with reference to FIGS. In the fifth embodiment, the monitoring device periodically monitors the monitoring target, and when an event occurs in the monitoring target, the monitoring device generates event information.

[Overview of monitoring system]
FIG. 10 is a schematic diagram showing a functional block diagram of a monitoring apparatus according to Embodiment 5 of the present invention. As shown in FIG. 10, the monitoring system 50 according to the present invention includes a monitoring device 270, a monitoring target 220, and an external device 230. The monitoring device 270 includes a monitoring unit 217, a receiving unit 211, a determination unit 212, an output unit 213, and a recording unit 215. 10, the monitoring target 220 and the monitoring unit 217 are connected, the monitoring unit 217 and the receiving unit 211 are connected, the receiving unit 211 and the determining unit 212 are connected, and the determining unit 212, the output unit 213, and the recording Unit 215 is connected, and the output unit 213 and the external device 230 are connected.

  The functional block diagram of the monitoring device 270 illustrated in FIG. 10 is similar to the functional block diagram of the monitoring device 250 illustrated in FIG. 6, but further includes a monitoring unit 217 that monitors the monitoring target 220 at predetermined time intervals. In FIG. When the monitoring unit 217 detects that an event has occurred in the monitoring target 220, the monitoring unit 217 generates event information and transmits the event information to the receiving unit 211.

  Since the hardware of the monitoring device 270 of the fifth embodiment can be the same as that of the monitoring device 10 of the first embodiment (FIG. 2), description thereof is omitted here.

[Operation flow of monitoring device]
FIG. 11 is a diagram illustrating an operation flow of the monitoring apparatus according to the fifth embodiment of the present invention. The operation flow shown in FIG. 11 is similar to the operation flow shown in FIG. 7, but in the operation flow shown in FIG. 11, the monitoring unit 217 monitors the monitoring target 220 and detects that an event has occurred in the monitoring target 220. Then, it differs from the operation flow shown in FIG. 7 in that event information is generated and transmitted to the receiving unit 211. Here, in FIG. 11, steps in which the same operation as in FIG. 7 is performed are denoted with the same reference numerals as in FIG. 7. Description of steps already described in FIG. 7 is omitted here, and differences from FIG. 7 are mainly described.

  In the operation flow of FIG. 7, when an event occurs in the monitoring target 220, the monitoring target 220 spontaneously generates event information and transmits it to the monitoring device 250. However, in the operation flow of FIG. 11, the monitoring device 270 monitors the monitoring target 220 every predetermined time interval (step S501), and detects that an event has occurred in the monitoring target 220 (step S502). Instead of 220, event information is generated and transmitted to the receiving unit 211 (step S503). In step S502, if no event occurrence is confirmed in the monitoring target 220, the process returns to step S501. Then, the monitoring device 270 again monitors the monitoring target 220 after a predetermined time interval (step S501). The event information generated and transmitted in step S503 is received by the reception unit 211 (step S301), and the process proceeds to subsequent steps.

  As described above, according to the operation method of the monitoring system and the monitoring apparatus according to the fifth embodiment of the present invention, when the monitoring target 220 does not have a function of generating event information, or the monitoring target 220 generates event information. Even when an abnormality that cannot be performed occurs, an event occurring in the monitoring target 220 can be detected, and duplication of the generated event information can be suppressed.

<Embodiment 6>
With reference to FIGS. 12 to 15, a device status monitoring apparatus and a program thereof according to Embodiment 6 of the present invention will be described in detail. In the sixth embodiment, the monitoring target device 200 is monitored by a plurality of monitoring servers (the first monitoring server 110 and the second monitoring server 120), and a message is sent as event information when an operation abnormality occurs in the monitoring target device 200. A case where information is transmitted using a check code as an identifier will be described.

[Outline of device status monitoring system]
FIG. 12 is a diagram showing a concept of a device state monitoring system according to Embodiment 6 of the present invention. As illustrated in FIG. 12, the device state monitoring system 60 includes a device state monitoring device 100, a monitoring target device 200, and a monitor 300. The device state monitoring apparatus 100 includes a first monitoring server 110, a second monitoring server 120, and a hub (HUB) server 130.

  The device state monitoring apparatus 100 and the monitoring target apparatus 200 are connected via a network 400. More specifically, the monitoring target device 200 is connected to the first monitoring server 110 and the second monitoring server 120 included in the device state monitoring device 100 via the network 400. The first monitoring server 110 and the second monitoring server 120 are connected to the HUB server 130 via a dedicated line 410. The HUB server 130 is connected to the monitor 300 by wire or wireless.

  Next, the operation flow of the device state monitoring system 60 will be briefly described. First, when an abnormality occurs in the monitoring target device 200, the monitoring target device 200 generates a message indicating the device status. A message is a set of data transmitted and received between computers described according to a certain format, and is also called a message, packet, request, or response. Further, in the monitoring target device 200, a check code that identifies an abnormality that has occurred in the monitoring target device 200 is generated, and the generated check code is added to the above-described message. Note that the same inspection code is generated for the same abnormality of the same monitoring target device 200.

  Here, the check code is one of error detection methods and may be referred to as a checksum. The check code is data in a fixed format generated based on the contents of the message or mapped with the contents of the message, and functions as an identifier for identifying each message. The check code may be data obtained by dividing a message into blocks of a certain number of bits and adding the data of each block as a numerical value. The inspection code may be generated together with a message by the monitoring target device 200, or may be generated by the device state monitoring device 100 for a message received from the monitoring target device 200. In the sixth embodiment, a case where a message is generated by the monitoring target device 200 will be described.

  The message to which the check code is added is transmitted to the first monitoring server 110 and the second monitoring server 120 via the network 400. Next, each message received by the two servers is transferred to the HUB server 130 via the dedicated line 410. Then, the HUB server 130 determines the presence or absence of a duplicate message based on the check code added to the received message, and if there is a duplicate message, selects one of those messages and outputs it to the monitor 300. . The monitoring operator can know the details of the abnormality that has occurred in the monitoring target device 200 by checking the contents of the message displayed on the monitor 300.

  FIG. 12 illustrates a system configuration in which each server included in the device state monitoring apparatus 100 is connected via the dedicated line 410. However, the present invention is not limited to this configuration. For example, the HUB server 130 includes the first monitoring server 110 and the first monitoring server 110. Similarly to the two monitoring servers 120, they may be connected via the network 400. Further, the first monitoring server 110, the second monitoring server 120, and the HUB server 130 may be directly connected by wire or wireless without using the dedicated line 410. In FIG. 12, the device state monitoring apparatus 100 is configured by a plurality of different servers. However, the present invention is not limited to this configuration, and the device state monitoring apparatus 100 may be configured by one server. In the configuration, the one server includes a first monitoring unit, a second monitoring unit, and a HUB unit having functions equivalent to those of the first monitoring server 110, the second monitoring server 120, and the HUB server 130, respectively. It only has to be.

[Functional configuration of device status monitoring apparatus 100]
FIG. 13 is a schematic diagram showing a functional block diagram of a device state monitoring apparatus according to Embodiment 6 of the present invention. As illustrated in FIG. 13, the device state monitoring apparatus 100 receives a message indicating a device state of a monitoring target (monitoring target device 200) to which a check code is added from the monitoring target, and the receiving unit 140 receives the message. The determination unit 142 that determines whether or not the check codes added to the plurality of electronic messages are the same, and the determination unit 142 determines that the check codes are the same, and has the same check code An output unit 144 that outputs one of the messages to the monitor 300; According to FIG. 13, the reception unit 140 and the monitoring target device 200 are connected, the reception unit 140 and the determination unit 142 are connected, the determination unit 142 and the output unit 144 are connected, and the output unit 144 and the monitor 300 are connected. It is connected.

  Each functional unit described above may be provided in one device or server, or may be provided in a distributed manner in a plurality of devices or servers. An example of a configuration in which each functional unit is provided in a plurality of apparatuses or servers will be described with reference to FIGS. 12 and 13. The first monitoring server 110 and the second monitoring server 120 have the function of the receiving unit 140. Further, the HUB server 130 has functions of a determination unit 142 and an output unit 144.

  The receiving unit 140 is connected to the network 400 and receives data from other devices via the network 400, more specifically, a message to which a check code is added from the monitoring target device 200. Here, the receiving unit 140 stores the message in the storage device in order to prevent the received message from being lost (lost). In order to store the message, the receiving unit 140 may be connected to a database, or the receiving unit 140 itself may have a memory. As the memory, a hard disk, a nonvolatile memory, a RAM (Random Access Memory), or the like can be used. Further, the receiving unit 140 may have a function of adding the time at which the electronic message is received to the electronic message. The receiving unit 140 may have a function of confirming whether or not a check code is added to the received electronic message and adding information on the presence or absence of the check code to the electronic message.

  The determination unit 142 has a function of temporarily storing a message and a check code in order to compare each check code added to a plurality of messages and determine whether or not there is a message to which the same check code is added. You may do it. In order to store the electronic message and the check code, the determination unit 142 may be connected to a database, or the determination unit 142 itself may have a memory. As the memory, a hard disk, a nonvolatile memory, a RAM (Random Access Memory), or the like can be used.

  The determination unit 142 may have a function of detecting whether or not a check code is added to the message received by the reception unit 140, and automatically performs the next operation according to the presence or absence of the check code. It may have a function to select. For example, if a check code is added to the message, the message duplication determination may be performed, and if not added, the output unit 144 may output the determination without performing the determination.

  Further, when determining whether or not the plurality of check codes are the same, the determination unit 142 may determine that the check codes are the same by matching all of the check codes or some values specified in advance. Further, the determination unit 142 may have a function of determining that they are not the same not based on the value of the check code but based on a format such as the number of bits of the check code and the check code format.

  The output unit 144 may be connected to a database in order to store a plurality of messages corresponding to an abnormality that has occurred in the monitoring target device 200, and the output unit 144 itself may have a memory. As the memory, a hard disk, a nonvolatile memory, a RAM (Random Access Memory), or the like can be used. In addition, the output unit 144 may select the earliest message generated when selecting one message among the messages to which the same check code is added. Further, it may have a function of erasing other messages having the same check code when the above-mentioned one message is selected.

  As described above, according to the device status monitoring apparatus according to the sixth embodiment of the present invention, among the plurality of messages received by the device status monitoring device 100, messages corresponding to the same abnormality that has occurred in the same monitored device 200. Can be determined based on the added check code. Further, by outputting one message out of the messages to which the same check code is added, duplicate information is not displayed on the monitor 300, and the device status monitoring apparatus 100 has duplicate information indicating the same event. Output can be suppressed. As a result, the monitoring burden on the monitoring operator can be reduced. In addition, the capacity of the telegram stored in the device state monitoring apparatus 100 can be reduced.

[Operation flow of device status monitoring system]
FIG. 14 is a diagram illustrating an operation flow of the device state monitoring system according to the sixth embodiment of the present invention. In FIG. 14, when an abnormality occurs in the monitoring target device 200, a message and a check code are generated in the monitoring target device 200, and a message with the check code added is transmitted to the first monitoring server 110 and the second monitoring server 120. The operation flow will be described in detail using a flowchart.

  When an event such as an abnormality occurs in the monitoring target device 200 (step S601), a message A including information such as the device unique ID or host name of the monitoring target device 200 in which the abnormality has occurred, the type of abnormality that has occurred, and the time of occurrence of the abnormality is generated. It is generated (step S602). Next, a check code is generated based on part or all of the generated message A and added to the message A (step S603). Here, the check code has a fixed format regardless of the format of the message A. Then, the message A to which the check code is added is transmitted to both the first monitoring server 110 and the second monitoring server 120 (step S604). Here, the message A transmitted to the two monitoring servers is the same, but for convenience of explanation, the message A transmitted to the first monitoring server 110 is the message A and the message transmitted to the second monitoring server 120 is the message. It is assumed that the message A ′. Here, the message A and the message A ′ have the same check code.

  Subsequently, the message A transmitted from the monitoring target device 200 is received by the first monitoring server 110 (step S611). That is, in this case, the first monitoring server 110 has a function as the receiving unit 140. Next, the message A received in step S611 is stored in a database connected to the first monitoring server 110 for data backup (step S612). The message A is stored in step S612 and then transmitted to the HUB server 130 (step S613).

  Similarly to steps S611 to S613, the message A transmitted from the monitoring target device 200 is received as the message A 'by the second monitoring server 120 (step S621). In other words, in this case, the second monitoring server 120 also has a function as the receiving unit 140 as with the first monitoring server 110. Next, the message A ′ received in step S621 is stored in a database connected to the second monitoring server 120 for data backup (step S622). Then, the message A ′ is stored in step S622 and then transmitted to the HUB server 130 (step S623).

  Subsequently, the message A transmitted from the first monitoring server 110 and the message A ′ transmitted from the second monitoring server 120 are received by the HUB server 130 (steps S631 and S632). Next, it is determined whether or not the electronic mail A and the electronic mail A ′ have the same check code added to the electronic mail by the HUB server 130 (step S633). In FIG. 14, since the same check code is added to the message A and the message A ′, only the message A is selected and output to a device such as the monitor 300 (step S634). That is, in this case, the HUB server 130 functions as the determination unit 142 and the output unit 144.

  Here, each of the message A received in step S611 and A ′ received in step S621 is determined by the first monitoring server 110 and the second monitoring server 120 as to whether or not a check code is added. Good. In addition, the first monitoring server 110 and the second monitoring server 120 may further add information regarding the presence or absence of the check code to each message, and transmit the information to the HUB server 130 together with the message A and the message A ′.

  In addition, the message A and the message A ′ received in steps S631 and S632 may be detected whether or not a check code is added to each message before the check code determination in step S633. Here, when a check code is not added to the message, the message may be automatically output in step S634 after step S633 is automatically invalidated. Further, when the check code is determined in step S633, the determination may be performed by comparing all the check codes or a part of the values specified in advance, and a pre-comparison is performed before the comparison. It may be broken. The pre-comparison may be performed based not on the value of the check code but on the format such as the number of bits of the check code and the check code format. When it is determined that the check codes are not the same in the preliminary comparison stage, the subsequent determination may not be performed and may be output in step S634.

[Operation flow of device status monitoring device]
FIG. 15 is a diagram illustrating an operation flow of the device state monitoring apparatus according to the sixth embodiment of the present invention. In FIG. 15, the operation flow of the device state monitoring apparatus 100 will be described in detail using a flowchart.

  As illustrated in FIG. 15, the device state monitoring apparatus 100 receives a message to which a check code is added from the monitoring target device 200 (step S701), and each check code added to the received plurality of messages is the same. It is determined whether or not there is (step S702), and when it is determined that each check code is the same (“Yes” in step S703), one message is selected from the messages having the same check code ( Step S704) and output (S705). When it is determined that the check codes of the received electronic messages are not the same (“No” in step S703), the electronic message is output as it is (step S705). Here, step S701 is executed by the first monitoring server 110 and the second monitoring server 120, and steps S702 to S705 are executed by the HUB server 130. Further, the above steps may be executed by a program stored in the memory of the control unit 111 of the device state monitoring apparatus 100.

  As described above, according to the operation method of the device state monitoring system and the device state monitoring device according to the sixth embodiment of the present invention, the same check code is used for messages corresponding to the same abnormality occurring in the same monitored device 200. Is added, it is possible to suppress redundant output of information indicating the same event. As a result, the monitoring burden on the monitoring operator can be reduced. In addition, the capacity of the telegram stored in the device state monitoring apparatus 100 can be reduced.

<Modification of Embodiment 6>
A device status monitoring apparatus according to a modification of the sixth embodiment of the present invention will be described with reference to FIG. FIG. 16 illustrates an operation flow in which synchronization processing is performed between the first monitoring server 110 and the second monitoring server 120 which are two receiving units.

  FIG. 16 is a diagram illustrating an operation flow of the device state monitoring apparatus according to the modification of the sixth embodiment of the present invention. Since the operation flow shown in FIG. 16 is similar to the operation flow shown in FIG. 14, steps in which the same operations as those in FIG. 14 are performed are denoted by the same reference numerals as those in FIG. Description of the steps already described in FIG. 14 will be omitted here, and differences from FIG. 14 will be mainly described.

  In the operation flow of FIG. 14, the message A is transmitted to the first monitoring server 110 and the second monitoring server 120 at the same time or close to each other. On the other hand, in the operation flow of FIG. 16, first, when the message A1 is transmitted to the first monitoring server 110 and a transmission error occurs or when it cannot be confirmed that the message has been transmitted normally, the message A1 ′ is transmitted to the second monitoring server 120. Sent to. In the operation flow shown in FIG. 16, the message A1 is transmitted to the first monitoring server 110 by the monitoring target device 200, but the monitoring target device 200 confirms that the message A1 is normally received by the first monitoring server 110. This shows the case where the electronic message A1 ′ is transmitted to the second monitoring server 120 because it was not possible. Here, although the message A1 transmitted to the two monitoring servers is the same, for convenience of explanation, the message transmitted to the first monitoring server 110 is the message A1 and the message transmitted to the second monitoring server 120 is the message. The message is A1 ′. The message A1 and the message A1 'have the same check code.

  In the above case, the first monitoring server 110 and the second monitoring server 120 receive the telegram A1 and the telegram A1 'as in FIG. 14, but the timing at which each server receives is different. In FIG. 16, synchronization processing is performed between the first monitoring server 110 and the second monitoring server 120 in order to prevent the message from being lost (step S <b> 841). Here, as described above, since the message A1 and the message A1 'are received at different timings, it may be determined that the message A1 and the message A1' are different messages. In such a case, the first monitoring server 110 generates a message A2 based on the message A1 '(step S811), and the second monitoring server 120 generates a message A2' based on the message A1 (step S821). Here, in step S811, a check code identical to the check code of the message A1 'is generated together with the message A2. In step S821, a check code identical to the check code of the message A1 is generated together with the message A2 '. Then, the message A1 and the message A2 are transmitted from the first monitoring server 110 to the HUB server (step S812). Also, the message A1 'and the message A2' are transmitted from the second monitoring server 120 to the HUB server (step S822).

  Subsequently, the electronic message A1 and electronic message A2 transmitted from the first monitoring server 110 and the electronic message A1 'and electronic message A2' transmitted from the second monitoring server 120 are received by the HUB server 130 (steps S831 and S832). Next, it is determined whether or not the check codes added to the electronic message A1, the electronic message A2, the electronic message A1 ', and the electronic message A2' are the same by the HUB server 130 (step S833). In FIG. 16, since the same check code is added to the message A1, the message A2, the message A1 ′, and the message A2 ′, only the message A is selected and output to a device such as the monitor 300, for example (step). S834).

  As described above, even in a device state monitoring system in which the number of duplicated messages is very large due to the influence of synchronization processing etc., the same check code is added to messages corresponding to the same abnormality, Duplicate output of information indicating the same event can be suppressed. As a result, the monitoring burden on the monitoring operator can be reduced. In addition, the capacity of the telegram stored in the device state monitoring apparatus 100 can be reduced.

<Embodiment 7>
With reference to FIGS. 17 to 20, a device status monitoring apparatus and a program thereof according to Embodiment 7 of the present invention will be described in detail. Since the outline of the device status monitoring system and the hardware configuration of the device status monitoring device are the same as those in the sixth embodiment, description thereof is omitted here. In the seventh embodiment, the monitoring target device 201 does not generate a check code, and the device state monitoring device 101 generates a check code.

[Functional configuration of device status monitoring apparatus 101]
FIG. 17 is a schematic diagram showing a functional block diagram of a device state monitoring apparatus according to Embodiment 7 of the present invention. As illustrated in FIG. 17, the device state monitoring apparatus 101 includes a receiving unit 140 that receives a message indicating the device state of the monitoring target (monitoring target device 201) from the monitoring target, and a plurality of messages received by the receiving unit 140. Whether the check code adding unit 146 for adding the same check code to the messages indicating the same monitored device status and the check codes added to the plurality of messages received by the receiving unit 140 are the same. And an output unit 144 that outputs one message out of messages having the same check code to the monitor 300 when the determination unit 142 determines that each check code is the same. . According to FIG. 17, the receiving unit 140 and the monitoring target device 201 are connected, the receiving unit 140 and the check code adding unit 146 are connected, the check code adding unit 146 and the determining unit 142 are connected, and the determining unit 142 The output unit 144 is connected, and the output unit 144 and the monitor 300 are connected.

  Each functional unit described above may be provided in one device or server, or may be provided in a distributed manner in a plurality of devices or servers. An example of a configuration in which each functional unit is provided in a plurality of apparatuses or servers will be described with reference to FIGS. 12 and 17. The first monitoring server 110 and the second monitoring server 120 include a receiving unit 140 and a check code adding unit 146. It has the function of. Further, the HUB server 130 has functions of a determination unit 142 and an output unit 144.

  The check code adding unit 146 may generate a check code based on a part or all of the message generated by the monitoring target device 201. Specifically, the check code adding unit 146 generates a device ID or host name of the monitoring target device 201, a message, and an occurrence time of each event added to the message (for example, the monitoring target device 200 generates or transmits a message). And the time at which each monitoring server receives the message, etc.). Also, the check code adding unit 146 may generate a check code in a certain format regardless of the above-described message format.

  As described above, according to the device state monitoring apparatus according to the seventh embodiment of the present invention, even when the monitoring target device 201 does not have a function of adding a check code, the message generated by the monitoring target device 201 is generated. Since the device state monitoring apparatus 101 adds the inspection code based on the information, the device state monitoring apparatus 101 can suppress the information indicating the same event from being output repeatedly as in the sixth embodiment. As a result, the monitoring burden on the monitoring operator can be reduced. In addition, the capacity of the message stored in the device state monitoring apparatus 101 can be reduced.

[Operation flow of device status monitoring system]
FIG. 18 is a diagram illustrating an operation flow of the device state monitoring system according to the seventh embodiment of the present invention. In FIG. 18, when an abnormality occurs in the monitoring target device 201, a message is generated and transmitted by the monitoring target device 201, and the first monitoring server 110 and the second monitoring server 120 that have received the message receive the message. The operation flow in which the check code is generated / added will be described in detail using a flowchart.

  When an abnormality occurs in the monitoring target device 201 (step S901), a message A including information such as the device unique ID or host name of the monitoring target device 201 in which the abnormality has occurred, the type of abnormality that has occurred, and the time of occurrence of the abnormality is generated. (Step S902). Next, the message A is transmitted to both the first monitoring server 110 and the second monitoring server 120 (step S903). Here, the message A transmitted to the two monitoring servers is the same, but for convenience of explanation, the message A transmitted to the first monitoring server 110 is the message A and the message transmitted to the second monitoring server 120 is the message. It is assumed that the message A ′.

  Subsequently, the message A transmitted from the monitoring target device 201 is received by the first monitoring server 110 (step S911). Next, the first monitoring server 110 generates a check code based on part or all of the message A received in step S911 and adds it to the message A (step S912). Here, the check code has a fixed format regardless of the format of the message A. Next, the message A to which the check code is added is stored in a database connected to the first monitoring server 110 for data backup (step S913). The message A is stored in step S913 and then transmitted to the HUB server 130 (step S914).

  Similarly to steps S911 to S914, the message A transmitted from the monitoring target device 201 is received as the message A ′ by the second monitoring server 120 (step S921). Next, the second monitoring server 120 generates a check code based on part or all of the message A ′ received in step S921 and adds it to the message A ′ (step S922). Here, the check code has a fixed format regardless of the format of the message A. Next, the message A ′ to which the check code is added is stored in a database connected to the second monitoring server 120 for data backup (step S923). The message A ′ is stored in step S923 and then transmitted to the HUB server 130 (step S924).

  Subsequently, the message A transmitted from the first monitoring server 110 and the message A ′ transmitted from the second monitoring server 120 are received by the HUB server 130 (steps S931 and S932). Next, it is determined whether or not the electronic mail A and the electronic mail A ′ have the same check code added to the electronic mail by the HUB server 130 (step S933). In FIG. 18, since the same check code is added to the message A and the message A ′, only the message A is selected and output to a device such as the monitor 300 (step S934).

[Operation flow of device status monitoring device]
FIG. 19 is a diagram illustrating an operation flow of the device state monitoring apparatus according to the seventh embodiment of the present invention. 19, the operation flow of the device state monitoring apparatus 101 will be described in detail using a flowchart.

  As illustrated in FIG. 19, the device status monitoring apparatus 101 receives a message indicating the device status to be monitored from the monitoring target device 201 (step S1001), and among the received plurality of messages, the device status monitoring apparatus 101 The same check code is added to the message indicating the device status (step S1002), and it is determined whether or not the check codes added to the plurality of received messages are the same (step S1003). Are determined to be the same ("Yes" in step S1004), one of the messages having the same check code is selected (step S1005) and output (step S1006). When it is determined that the check codes of the received messages are not the same (“No” in step S1004), the message is output as it is (step S1006). Here, steps S1001 and S1002 are executed by the first monitoring server 110 and the second monitoring server 120, and steps S1003 to S1006 are executed by the HUB server 130. In addition, the above steps may be executed by a program stored in the memory of the control unit 111 of the device state monitoring apparatus 101.

[Example of message and check code]
Here, an example is shown in FIG. 20 about the message | telegram produced | generated by the monitoring object apparatus 201, and the test | inspection code | symbol produced | generated by the test | inspection code addition part 146 of the apparatus state monitoring apparatus 101. FIG. FIG. 20 is a diagram illustrating an example of a message and a check code generated by the check code adding unit of the device state monitoring apparatus according to the seventh embodiment of the present invention.

  In FIG. 20, a message 610 and a check code 620 are displayed for each item, but the actual message and check code are described in text format or HTML format. As shown in FIG. 20, the message 610 includes a “HUB server MSG number” that identifies a message received by the HUB server 130, a “workflow ID” that identifies each workpiece, and an importance level in the system of the monitoring target device 201. "Importance", "host name" identifying the monitored device 201, "event occurrence time" indicating the time when an event such as an abnormality occurred, "message generation time" indicating the time when the message was generated, “MSG (message)” indicating details is included. Here, the MSG includes detailed information such as the type of event that occurred, the host name and IP address of the device where the event occurred, the time when the event occurred, and the result of the event.

  The check code 620 is generated based on part or all of the electronic message 610. For example, the check code may be generated based on the host name, event occurrence time, and MSG. Here, the check code may be calculated using a hash function for the above three items. The hash function is a mathematical processing method used for digital authentication and integrity check, and is a function that disturbs long data and compresses it into a hash value of a certain length (for example, 128 bits). An example of the hash function is MD5 (Message Digest Algorithm 5) defined by RFC1321. In this algorithm, 128-bit data can be generated by calculation using a one-way hash function regardless of the length of the original data.

  Here, a case where the check code 620 is generated based on a part of the electronic message 610 will be described. As shown in FIG. 20, the message 610 is a serial number for identifying each message such as a numerical value “000001” of the lower 6 digits of the “HUB server MSG number” or a value “232643” of the “workflow ID”. A serial number for identifying each workpiece may be included. Since these numerical values are always different values for each message, they do not serve as identifiers for specifying each message. As described above, when a check code is generated by excluding information that cannot be an identifier from information included in a message in advance, the check code is generated based on a part of the message.

  As described above, according to the operation method of the device state monitoring system and the device state monitoring device according to the seventh embodiment of the present invention, even if the monitoring target device 201 does not have the function of adding the inspection code, As in the sixth embodiment, the device state monitoring apparatus 101 can suppress the redundant output of information indicating the same event. As a result, the monitoring burden on the monitoring operator can be reduced. In addition, the capacity of the message stored in the device state monitoring apparatus 101 can be reduced.

<Modification of Embodiment 7>
A device state monitoring apparatus according to a modification of the seventh embodiment of the present invention will be described with reference to FIG. FIG. 21 illustrates an operation flow in which a check code is generated / added by the HUB server 130.

  FIG. 21 is a diagram illustrating an operation flow of the device state monitoring apparatus according to the modification of the seventh embodiment of the present invention. Since the operation flow shown in FIG. 21 is similar to the operation flow shown in FIG. 18, in FIG. 21, steps in which the same operation as that in FIG. 18 is performed are denoted by the same reference numerals as in FIG. Description of steps already described in FIG. 18 is omitted here, and points different from FIG. 18 will be mainly described.

  In the operation flow of FIG. 18, the check code of the message A is generated after the first monitoring server 110 receives the message A (after step S911), and the check code of the message A ′ is generated by the second monitoring server 120. It is generated after A ′ is received (after step S921). On the other hand, in the operation flow of FIG. 21, the check codes of the message A and the message A ′ are generated based on part or all of each message after each message is received by the HUB server 130. Added (steps S1131 and S1132).

  As described above, by generating a check code based on part or all of a message, a check code can be generated and added in any process from message generation to check code determination. Therefore, it is not necessary to provide the check code adding unit 146 in each monitoring server, and the present invention can be realized by providing the check code adding unit 146 only in the HUB server 130 that manages the electronic message.

<Embodiment 8>
With reference to FIGS. 22 and 23, a device state monitoring apparatus and its program according to Embodiment 8 of the present invention will be described in detail. Since the outline of the device status monitoring system and the hardware configuration of the device status monitoring device are the same as those in the sixth embodiment, description thereof is omitted here. In the eighth embodiment, the presence / absence of a duplicate message is determined by comparing the check code of the received message with the check code of the message received in the past.

[Functional Configuration of Device Status Monitoring Device 102]
FIG. 22 is a schematic diagram showing a functional block diagram of a device state monitoring apparatus according to Embodiment 8 of the present invention. The functional block diagram of the device status monitoring apparatus 102 shown in FIG. 22 is similar to the functional block diagram of the device status monitoring apparatus 100 shown in FIG. 13, but the device status monitoring device 102 records a message that has been received in the past. The device state monitoring apparatus 100 is different from the device state monitoring apparatus 100 in that the unit 148 is further provided. 22, the receiving unit 140 and the monitoring target device 200 are connected, the receiving unit 140 and the determining unit 142 are connected, the determining unit 142, the output unit 144, and the recording unit 148 are connected, and the output unit 144 A monitor 300 is connected.

  Each functional unit described above may be provided in one device or server, or may be provided in a distributed manner in a plurality of devices or servers. An example of a configuration in which each functional unit is provided in a plurality of apparatuses or servers will be described with reference to FIGS. 12 and 22. The first monitoring server 110 and the second monitoring server 120 have the function of the receiving unit 140. The HUB server 130 has functions of a determination unit 142, an output unit 144, and a recording unit 148.

[Operation flow of device status monitoring device]
FIG. 23 is a diagram illustrating an operation flow of the device state monitoring apparatus according to the eighth embodiment of the present invention. As illustrated in FIG. 23, in the device state monitoring apparatus 102, the reception unit 140 receives the first message to which the first check code is added from the monitoring target apparatus 200 (step S1301), and the determination unit 142 receives the first received message. It is determined whether or not the first check code added to the electronic message is the same as the second check code added to the second electronic message recorded in the recording unit 148 (step S1302). When it is determined that the first check code and the second check code are not the same (“none” in step S1303), the recording unit 148 records the first message and the first check code (step S1304), and the output unit 144. Outputs the first telegram and the first check code (step S1305). If it is determined that the first check code and the second check code are the same (“Yes” in step S1303), the determination unit 142 discards or invalidates the first message and the first check code (step S1303). S1306). The above steps may be executed by a program stored in the memory of the control unit 111 of the device state monitoring apparatus 102.

  Here, the method of determining whether or not the first check code and the second check code are the same is performed by the determination unit 142 searching the recording unit 148 for the first check code. If the second check code identical to the first check code exists in the recording unit 148 as a result of the search, the determination unit 142 determines that the first check code and the second check code are the same, and the first electronic message Discard or invalidate. On the other hand, if the same check code as the first check code does not exist in the recording unit 148, the determination unit 142 determines that the first check code and the second check code are not the same, and the first electronic message is stored in the recording unit 148. Record and output.

  As described above, according to the operation method of the device status monitoring system and the device status monitoring apparatus according to the eighth embodiment of the present invention, a message to which the same check code as the received check code is added exists in the recording unit 148. Whether or not there is duplication of messages is determined depending on whether or not to do so, and recording or discarding of messages can be automatically executed according to the necessity for determination of whether or not there is duplication of messages. Therefore, it is possible to determine the duplication of messages with a smaller amount of data.

<Embodiment 9>
With reference to FIGS. 24 and 25, a device status monitoring apparatus and a program thereof according to Embodiment 9 of the present invention will be described in detail. Since the outline of the device status monitoring system and the hardware configuration of the device status monitoring device are the same as those in the sixth embodiment, description thereof is omitted here. In the ninth embodiment, in a method for determining the presence / absence of a duplicate message by comparing the check code of the received message with the check code of the message received in the past, an effective period as to whether or not to perform the determination is set. .

[Functional Configuration of Device Status Monitoring Device 103]
FIG. 24 is a schematic diagram showing a functional block diagram of a device state monitoring apparatus according to Embodiment 9 of the present invention. The functional block diagram of the device status monitoring device 103 shown in FIG. 24 is similar to the functional block diagram of the device status monitoring device 102 shown in FIG. 22, but the device status monitoring device 102 is further provided with a validity period management unit 150. Is different. Here, the determination unit 142 sets a message generated or received within a predetermined period after the message is generated or received as a target of determination, but the validity period management unit 150 uses the predetermined period set in advance. to manage. 24, the receiving unit 140 and the monitoring target device 200 are connected, the receiving unit 140 and the determining unit 142 are connected, and the determining unit 142, the output unit 144, the recording unit 148, and the validity period managing unit 150 are connected. The output unit 144 and the monitor 300 are connected.

  Each functional unit described above may be provided in one device or server, or may be provided in a distributed manner in a plurality of devices or servers. An example of a configuration in which each functional unit is provided in a plurality of apparatuses or servers will be described with reference to FIGS. 12 and 24. The first monitoring server 110 and the second monitoring server 120 have the function of the receiving unit 140. The HUB server 130 has functions of a determination unit 142, an output unit 144, a recording unit 148, and a validity period management unit 150.

[Operation flow of device status monitoring device]
FIG. 25 is a diagram illustrating an operation flow of the device state monitoring apparatus according to the ninth embodiment of the present invention. The operation flow shown in FIG. 25 is similar to the operation flow shown in FIG. 23, but the operation flow shown in FIG. 25 is the first when the first check code and the second check code are determined to be the same. What is the operation flow shown in FIG. 23 in that it has an operation of determining whether the time when the electronic message is generated or received and the time when the second electronic message is generated or received are within a predetermined period set in advance. Is different. Here, in FIG. 25, steps in which the same operation as in FIG. 23 is performed are denoted with the same reference numerals as in FIG. Description of the steps already described in FIG. 23 is omitted here, and differences from FIG. 23 are mainly described.

  In the operation flow of FIG. 23, when it is determined that the first check code and the second check code are the same ("Yes" in step S1303), the determination unit 142 discards the first message and the first check code or It is invalidated (step S1306). However, in the operation flow of FIG. 25, when it is determined that the first check code and the second check code are the same (“Yes” in step S1303), the validity period management unit 150 generates or generates the first message. It is determined whether the received time and the time when the second telegram is generated or received are within a predetermined period (step S1501).

  When the validity period management unit 150 determines that the time when the first message is generated or received and the time when the second message is generated or received are within the predetermined period (“Yes” in step S1501), the determination The unit 142 discards or invalidates the first message and the first check code (step S1306). On the other hand, when it is determined that the above two times are not within the predetermined period (“No” in step S1501), it is determined that the first message and the second message are not targets for determining overlapping of messages. That is, as in the case where it is determined that the first check code and the second check code are not the same, the recording unit 148 records the first telegram and the first check code (step S1304), and the output unit 144 is the first telegram. The first check code is output (step S1305).

  As described above, according to the operation method of the device state monitoring system and the device state monitoring device according to the ninth embodiment of the present invention, only the messages generated or received within a predetermined period are set as the duplication determination targets. The coincidence of check codes can be further reduced, and the detection efficiency of duplicate messages is improved.

<Embodiment 10>
The apparatus state monitoring apparatus and its program according to Embodiment 10 of the present invention will be described in detail with reference to FIGS. Since the outline of the device status monitoring system and the hardware configuration of the device status monitoring device are the same as those in the sixth embodiment, description thereof is omitted here. In the tenth embodiment, the device status monitoring device periodically monitors the monitoring target device, and generates a message when an abnormality occurs in the monitoring target device.

[Functional Configuration of Device Status Monitoring Device 104]
FIG. 26 is a schematic diagram showing a functional block diagram of a device state monitoring apparatus according to Embodiment 10 of the present invention. The functional block diagram of the device status monitoring device 104 shown in FIG. 26 is similar to the functional block diagram of the device status monitoring device 102 shown in FIG. 22, but monitors the monitoring target device 200 at predetermined time intervals. It differs from the device state monitoring apparatus 102 in that it further includes 152. When the monitoring unit 152 detects a change in the device state of the monitoring target device 200, the monitoring unit 152 generates a message and transmits the message to the receiving unit 140. 26, the monitoring unit 152 and the monitoring target device 200 are connected, the receiving unit 140 and the monitoring unit 152 are connected, the receiving unit 140 and the determining unit 142 are connected, and the determining unit 142 and the output unit 144 are connected. The recording unit 148 is connected, and the output unit 144 and the monitor 300 are connected.

  Each functional unit described above may be provided in one device or server, or may be provided in a distributed manner in a plurality of devices or servers. An example of a configuration in which each functional unit is provided in a plurality of apparatuses or servers will be described with reference to FIGS. 12 and 26. The first monitoring server 110 and the second monitoring server 120 are functions of the receiving unit 140 and the monitoring unit 152. Have The HUB server 130 has functions of a determination unit 142, an output unit 144, and a recording unit 148.

[Operation flow of device status monitoring device]
FIG. 27 is a diagram illustrating an operation flow of the device state monitoring apparatus according to the tenth embodiment of the present invention. The operation flow shown in FIG. 27 is similar to the operation flow shown in FIG. 23, but the operation flow shown in FIG. 27 is that the monitoring unit 152 monitors the monitoring target device 200 and an abnormality has occurred in the monitoring target device 200. When a message is detected, a message is generated, which is different from the operation flow shown in FIG. Here, in FIG. 27, steps in which the same operation as in FIG. 23 is performed are denoted by the same reference numerals as in FIG. Description of the steps already described in FIG. 23 is omitted here, and differences from FIG. 23 are mainly described.

  In the operation flow of FIG. 23, when an abnormality occurs in the monitoring target device 200, the monitoring target device 200 spontaneously generates a message and transmits it to the device state monitoring device 102. However, in the operation flow of FIG. 27, the monitoring unit 152 monitors the monitoring target device 200 at predetermined time intervals (step S1701) and detects that an abnormality has occurred in the monitoring target device 200 (“Yes” in step S1702). The monitoring unit 152 generates a message on behalf of the monitoring target device 200 and transmits it to the receiving unit 140 (step S1703). If no abnormality is confirmed in the monitoring target device 200 in step S1702, the process returns to step S1701 (“No” in step S1702). Then, the monitoring unit 152 again monitors the monitoring target device 200 after a predetermined time interval (step S1701). The message generated and transmitted in step S1703 is received by the receiving unit 140 (step S1301), and the process proceeds to the subsequent steps.

  As described above, according to the operation method of the device state monitoring system and the device state monitoring device according to the tenth embodiment of the present invention, when the monitoring target device 200 does not have a function of generating a message, or the monitoring target device 200. Even when an abnormality that cannot generate a message has occurred, an abnormality that has occurred in the monitoring target device 200 can be detected, and duplication of the generated messages can be suppressed.

<Embodiment 11>
28 and 29, the sensor monitoring apparatus and its program according to Embodiment 11 of the present invention will be described in detail. In the eleventh embodiment, in a sensor monitoring system in which a plurality of sensors for detecting an abnormality occurring in a managed facility is installed, one monitoring computer monitors the plurality of sensors, and the abnormality occurring in the facility is detected by the plurality of sensors. A case will be described.

[Outline of device status monitoring system]
FIG. 28 is a diagram showing the concept of a sensor monitoring system according to Embodiment 11 of the present invention. As shown in FIG. 28, the sensor monitoring system 29 includes a sensor monitoring device 700, a monitoring target facility 800, a sensor A 810, a sensor B 820, a sensor C 830, and a speaker 840. Each device constituting the sensor monitoring system 29 is connected by wire or wirelessly. Here, the sensors A to C are sensors that sense the same phenomenon. The speaker 840 is a sound wave generator that issues an alarm in the monitoring target device in response to an instruction from the sensor monitoring device 700 when each sensor senses an abnormality.

[Functional Configuration of Sensor Monitoring Device 700]
FIG. 29 is a schematic diagram showing a functional block diagram of a sensor monitoring apparatus according to Embodiment 11 of the present invention. The functional block diagram of the sensor monitoring device 700 shown in FIG. 29 is similar to the functional block diagram of the monitoring device 270 shown in FIG. 10, but the monitoring unit 717 is connected to a plurality of sensors A810 to C830. It differs from the monitoring device 270 in that an identifier adding unit 714 is provided between the receiving unit 711 and the determining unit 712 and an output unit 713 is connected to the speaker 840.

  In the sensor monitoring apparatus 700, when the sensors A810 to C830 sense an abnormality for a certain phenomenon, each sensor generates a sensing signal (hereinafter referred to as an abnormal signal) indicating that the abnormality has occurred. The monitoring unit 717 of the sensor monitoring device 700 periodically monitors each sensor, and when an abnormal signal is detected, the type of sensor that generated the abnormal signal, the time when the abnormal signal was detected, the location where the sensor was installed, etc. Event information is generated based on the information.

  The generated event information is received by the receiving unit 711. The event information generated / received as described above is transmitted to the identifier adding unit 714. The identifier adding unit 714 generates the same identifier for event information for the same phenomenon among the event information, and the identifier is used as the event information. Added to the information. The event information to which the identifier is added is determined by the determination unit 712 whether or not the event information to which the same identifier is added is recorded in the recording unit 715. If event information to which the same identifier is added is not recorded in the recording unit 715, the event information is output to the speaker 840 by the output unit 713. On the other hand, when event information to which the same identifier is added is recorded in the recording unit 715, the event information is discarded or invalidated.

  As a more specific example of the event information and identifier, a case will be described in which the monitored facility 800 is a factory and the sensors A to C are fire sensors. In the factory, when a fire occurs and a plurality of sensors A to C detect a fire, the identifier adding unit 714 of the sensor monitoring device 700 generates event information indicating the occurrence of the fire based on those abnormal signals. The event information includes information such as an abnormal signal type (in this case, “fire”), an abnormal signal generation time, an abnormal signal generation area, and the like. Next, the identifier adding unit 714 generates an identifier based on the event information. For example, if the phenomenon to be sensed is a fire, there is a possibility that the timing at which each sensor detects a fire may be slightly different, but a sensor installed in the same room is likely to detect a fire. Therefore, for example, the same identifier is generated and added to the event information for a fire abnormality signal whose abnormality occurrence time is within 5 minutes and the abnormality occurrence area is the same room.

  As described above, according to the sensor monitoring system according to the eleventh embodiment of the present invention, it is possible to determine whether or not there is duplication of event information even in a system such as a sensor that detects the same phenomenon by a plurality of means. it can.

10, 210, 240, 260, 270: monitoring device, 20, 30, 40, 50: monitoring system, 29: sensor monitoring system, 60: device status monitoring system, 100, 101, 102, 103, 104, 250: device State monitoring device 110: first monitoring server 111, 221: control unit 120: second monitoring server 130: HUB server 140, 211, 711: receiving unit 142, 212, 712: determining unit 144 213, 713: output unit, 146, 714: check code adding unit, 148, 215, 715: recording unit, 150, 216: effective period management unit, 152, 217, 717: monitoring unit, 200, 201: monitoring target device 214: identifier adding unit 220: monitoring target 222: hard disk , 223: communication unit, 230: external device, 300: monitor, 400: network, 410: dedicated line, 610: telegram, 620: inspection code, 700: sensor monitoring device, 800: facility to be monitored, 840: speaker, 810 : Sensor A, 820: Sensor B, 830: Sensor C

Claims (13)

A receiving unit that receives a message indicating a monitoring target device status, to which a check code is added, from the monitoring target;
A determination unit for determining whether or not each of the check codes added to the plurality of messages received by the reception unit is the same;
When the determination unit determines that each of the check codes is the same, an output unit that outputs one of the messages having the same check code;
A monitoring device comprising: A receiving unit that receives a message indicating a device status of a monitoring target from the monitoring target;
Among the plurality of messages received by the receiving unit, a check code adding unit that adds the same check code to the messages indicating the same device status to be monitored;
A determination unit for determining whether or not each of the check codes added to the plurality of messages received by the reception unit is the same;
When the determination unit determines that each of the check codes is the same, an output unit that outputs one of the messages having the same check code;
A monitoring device comprising:   The monitoring apparatus according to claim 1, wherein the check code is generated based on a part or all of the electronic message.   The monitoring apparatus according to claim 1, wherein the check code has a fixed format regardless of the format of the message. A recording unit for recording the electronic message;
The determination unit determines whether the first check code added to the first message received by the reception unit is the same as the second check code added to the second message recorded in the recording unit. And
5. The method according to claim 1, wherein when it is determined that the first check code and the second check code are not the same, the first telegram and the first check code are recorded in the recording unit. A monitoring device according to claim 1.   The monitoring device according to claim 1, wherein the determination unit uses a message generated or received within a predetermined time after the message is generated or received as a determination target. A monitoring unit for monitoring the monitoring target at predetermined time intervals;
The monitoring device according to any one of claims 1 to 6, wherein when the monitoring unit detects a change in a device state to be monitored, the monitoring unit generates the message and transmits the message to the receiving unit. A reception unit that receives event information that is generated based on an event and to which an identifier that identifies the event is added;
A determination unit that determines whether or not the identifiers added to the plurality of event information received by the reception unit are the same;
When the determination unit determines that the identifiers are the same, an output unit that outputs the event information of one of the event information to which the same identifier is added;
A monitoring device comprising: A receiving unit for receiving event information generated based on the event;
An identifier adding unit for adding the same identifier to the event information indicating the same event among the plurality of event information received by the receiving unit;
A determination unit that determines whether or not the identifiers added to the plurality of event information received by the reception unit are the same;
When the determination unit determines that the identifiers are the same, an output unit that outputs the event information of one of the event information to which the same identifier is added;
A monitoring device comprising: A receiving unit for receiving event information generated based on the event;
An identifier adding unit that generates a unique identifier for the event information based on all or part of the event information received by the receiving unit and adds the identifier to the event information;
A monitoring device comprising: Identifier addition for generating a first identifier and a second identifier added to the first event information and the second event information generated based on the event, respectively, and adding the first identifier and the second event information to the first event information and the second event information, respectively. And
A determination unit that compares the first identifier and the second identifier;
An output unit that outputs any one of the first event information or the second event information when the determination unit determines that the first identifier and the second identifier are the same;
A monitoring device comprising: Receive a message with a check code from the monitoring target,
It is determined whether or not each of the check codes added to the plurality of received messages is the same,
When it is determined that the check codes are the same, a program for causing the monitoring device to execute one of the messages having the same check code is output. A message indicating the device status of the monitoring target is received from the monitoring target,
Among the plurality of received messages, the same check code is added to the messages indicating the same monitored device status,
It is determined whether or not each of the check codes added to the plurality of received messages is the same,
When it is determined that the check codes are the same, a program for causing the monitoring device to execute one of the messages having the same check code is output.

Images