JP2012059188A - Monitoring network, program, and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide, at low cost, a monitoring network capable of surely monitoring information.SOLUTION: A computer body 41 of a monitoring apparatus 40 determines a state of a monitor result of a monitor target in a monitoring network 10 based on a detection result of a detection device 42, generates a history element each time the state of the monitor result is changed, generates a state history by combining a survival confirmation time, a determination time and the history element with a time in which the detection device 42 sends the detection result as the determination time and with a present time measured by a timepiece device 43 as the survival confirmation time, and transmits the state history through a communication line CL to a monitoring system 20. A computer body 21 of the monitoring system 20 stores in a RAM 33 or an HDD 35 and manages the state history transmitted from the monitoring apparatus 40 in accordance with a PULL type or a PUSH type.

Description

  The present invention relates to a monitoring network, a program, and a recording medium. More specifically, the present invention relates to a monitoring network for monitoring information using a computer network, a program for causing a computer system to function so as to realize the monitoring network, and the program recorded therein. The present invention relates to a computer-readable recording medium.

There are the following two types of monitoring systems that monitor various information using a computer.
(Type 1) Output the acquired information as it is, or process the acquired information so that it can be easily used by another system that uses the monitoring result of the monitoring system (post-process system) or the monitoring system administrator Monitoring system.
(Type 2) A monitoring system that performs some determination based on acquired information, and records and outputs the determination result as a monitoring result.

Type 1 surveillance systems include, for example, a combination of a surveillance camera and a display that displays the video of the surveillance camera, a combination of a temperature sensor that measures the temperature, and a display that outputs the variation in the temperature as a graph. There is.
The type 2 monitoring system includes, for example, a combination of a temperature sensor that measures the temperature inside the electronic device and a determination device that determines an abnormality of the electronic device based on the temperature, and a computer connected to a network. There are things that regularly send a message and check the existence of the computer by checking the response.
The present invention relates to a type 2 monitoring system.

In recent years, with the increase in the number of monitoring targets in the monitoring system, the number of monitoring results has increased significantly.
For example, the TS (Transport Stream) monitoring system for digital broadcasts manufactured and sold by the applicant (Traffic Sim Co., Ltd.) (product names “TSM-1000”, “TSW-1000”, “TSW-3000”, “TSW-500”) "TSG-1000" etc.) another system (post-process system) or monitoring that monitors the monitoring results of 10,000 to 100,000 items in real time with one computer and uses the monitoring results of the monitoring system It has a function to notify the system administrator.

In the conventional monitoring system, the following two methods are used as a method of recording the monitoring result.
(Method 1) A method of recording the monitoring result as a log.
(Method 2) A method of recording a monitoring result as a state.

Method 1 includes a monitoring system using a swatch program having a function of automatically sending an e-mail to an administrator when a target character string is detected in a log file, for example.
Method 2 includes a monitoring system using SNMP (Simple Network Management Protocol) (see, for example, Patent Documents 1 to 3).

JP 2010-066693 A JP 2010-061226 A JP 2009-301306 A

  In the swatch program, the monitoring result is generated in response to a specific character string in the log file. For example, to determine whether a temperature abnormality is currently occurring, refer back to the log from the present to the past. Search for the strings “Temperature Abnormal” and “Temperature Abnormal Recovery”, and if the first character string found is “Temperature Abnormal”, it is determined that a temperature abnormality is currently occurring, and is found first. If the character string is “temperature abnormal recovery”, it is determined that no temperature abnormality is currently occurring, and therefore processing that is heavy on the computer must be performed.

  Therefore, in order to apply Method 2 to a monitoring system that manages the monitoring results of 100,000 items in real time with one computer, such as the TS monitoring system manufactured and sold by the present applicant, an expensive high-performance computer is used. There is a problem that the cost of the monitoring system increases because it is necessary to use or combine a plurality of computers.

In a monitoring system using SNMP, the monitoring device is called an “agent”, the device that manages the monitoring network is called a “manager”, and the agent records the monitoring result.
In the PULL type monitoring system, when the manager requests the agent to transmit the monitoring result, the monitoring result is transmitted from the agent to the manager.
In the PUSH type monitoring system, the monitoring result is transmitted from the agent to the manager every time the monitoring result changes.

In the PULL type monitoring system, since the agent does not transmit the time when the monitoring result has changed to the manager, the manager cannot grasp the time when the monitoring result has changed.
Also, in the PULL type monitoring system, the monitoring result is sent between the manager requesting the agent to send the monitoring result and the next request for sending the monitoring result (between the PULL operation and the PULL operation). If the number of times changes, the manager cannot grasp the changes of the monitoring results for a plurality of times, so it cannot be used for applications in which changes in the monitoring results must not be overlooked even for a moment.

In the PUSH type monitoring system, the time when the manager received the monitoring result is the time when the monitoring result changed, so the monitoring result changed if the manager missed the monitoring result sent from the agent. The manager cannot grasp the time.
In particular, in a PUSH type monitoring system, if an agent sends a large number of monitoring results in a short time, the manager's load becomes excessive, and the probability that the manager cannot receive the monitoring results sent from the agent increases.

Therefore, in the PUSH type monitoring system, the following two methods are used so that the manager can receive the monitoring result transmitted from the agent without missing it.
(Method A) A method in which the agent transmits the same monitoring result a plurality of times so that the manager can reliably receive the monitoring result.
(Method B) A method in which the agent retransmits the monitoring result to the manager when the agent detects that the manager cannot receive the monitoring result using a communication protocol with a retransmission function.

In the method A and the method B, the number of times the agent transmits the monitoring result increases, and the load on the communication line increases. Therefore, it is necessary to use expensive high-performance computers for the agent and the manager.
In the method A and the method B, the monitoring result may be changed while the manager is transmitting the same monitoring result to the agent. In this case, there is a possibility that a new monitoring result cannot be transmitted. .

In a monitoring system that handles a large number of monitoring results, when notifying the monitoring results to another system (post-process system) that uses the monitoring results of the monitoring system or the administrator, the number of monitoring results to be notified If the capacity of the process system or the manager is exceeded, there is a risk that the post-process system or the manager may not be able to take an appropriate action on the monitoring result.
For example, if monitoring results indicating abnormalities occur frequently on a daily basis, when a serious abnormality occurs on rare occasions, it is buried in non-critical monitoring results that occur frequently on a daily basis and appropriate measures are not taken. There was a concern that it would become "Wolf Boy State".

  Therefore, in order to notify only important monitoring results, a function for automatically adding a plurality of monitoring results and generating new monitoring results is required. For example, based on the monitoring results managed by SNMP. In aggregation, monitoring results that change in a short time cannot be managed in chronological order, and the new monitoring results that are generated impair the strictness of time.

In addition, in a monitoring system using SNMP, when a plurality of monitoring results are automatically aggregated to generate a new monitoring result, it is necessary to perform processing according to the description method of the monitoring result of the aggregation source.
That is, in the monitoring system using SNMP, the description method of the monitoring result is not standardized. For example, “represents that there is no abnormality when the value is 0” “represents normality when the value is 1. There are various monitoring method description methods depending on the monitoring system, such as “represents normal when the value is in the range of 50 to 100” and “represents normal when the value is OK”.
For this reason, when generating a new monitoring result by automatically counting a plurality of monitoring results, it is necessary to develop a counting program according to the description method of the monitoring results, which requires a lot of labor for the development. It was.

  Furthermore, in the monitoring system using SNMP, the monitoring result management method in the agent must be set before starting the monitoring system, and the monitoring result management method cannot be changed after starting the monitoring system. It was.

The present invention has been made to solve the above-described problems, and has the following objects.
(1) To provide a monitoring network capable of reliably monitoring information at a low cost.
(2) A program for causing a computer system to function so as to realize the monitoring network of (1) is provided.
(3) Provided is a computer-readable recording medium in which a program for causing a computer system to function so as to realize the monitoring network of (1) is recorded.

<Claim 1>
The invention described in claim 1
A monitoring network comprising one or more monitoring devices, a communication line, and a monitoring system,
The monitoring device
Detection means for detecting the status of the monitoring result of the monitoring target in the monitoring network;
A timekeeping means for measuring the current time;
Based on the detection result of the detection means, the state of the monitoring result is determined, a history element is generated each time the state of the monitoring result changes, and the detection means is based on the current time measured by the time measuring means. A state history generating means for generating a state history by combining a time when the state of the monitoring result is detected as a fixed time, and combining the fixed time and the history element;
Storage means for storing the state history generated by the state history generation means;
A transmission unit that transmits the state history generated by the state history generation unit via the communication line;
The monitoring system includes:
Receiving means for receiving the status history transmitted from the one or more monitoring devices via the communication line;
Storage management means for storing and managing the status history received by the receiving means,
The state history is configured by arranging the confirmed time and one or more history elements into one,
The confirmed time is information on the time when the state history is confirmed,
The history element is composed of a change time and a state of the monitoring result,
The change time is information of a time when the state of the monitoring result has changed,
The state of the monitoring result has two information values, an occurrence state and a return state,
The occurrence state represents that a predefined state is occurring in the monitoring target,
The return state represents a technical feature indicating that the occurrence state has disappeared.

When claim 1 is applied to a PULL type monitoring network, when the monitoring system requests the monitoring device to transmit a state history via the communication line, the monitoring device stores the state history stored in the storage means. And the state history is transmitted to the monitoring system via the communication line.
For this reason, the monitoring device has a plurality of histories between the time when the monitoring system requests the monitoring device to transmit the state history and the next time the transmission of the state history is requested (between the PULL operation and the PULL operation). Even if the element is generated, the plurality of history elements are stored in the storage unit of the monitoring device, and therefore the monitoring device can transmit all of the plurality of history elements to the monitoring system.
When claim 1 is applied to a PUSH type monitoring network, the monitoring device generates a history element each time the monitoring result of the monitoring target in the monitoring network changes, and the monitoring device stores the generated history element. The state history read out from the storage means is transmitted to the monitoring system via the communication line.
For this reason, even if the monitoring device generates a large number of history elements in a short time, the generated history elements are temporarily stored in the storage means, so it is necessary to transmit the history information to the monitoring system every time the monitoring device generates a history element. Therefore, the load on the monitoring system does not become excessive, there is no possibility that the monitoring system will miss the history element included in the status history transmitted from the monitoring device, and the overhead related to the transmission of the status history can be reduced.
Therefore, according to claim 1, it is possible to receive all the history elements generated by the monitoring device without the monitoring system missing, and the monitoring system synchronizes all the history elements generated by the monitoring device with time. Can be managed.

According to the first aspect of the present invention, since the history element includes information on the change time, the monitoring system can reliably grasp the time when the state of the history element has changed.
According to claim 1, it is possible to reliably grasp the latest state of the monitoring result of the monitoring target based on the history element having the latest change time and the confirmed time among the plurality of history elements included in the state history.

<Claim 2: Corresponds to the second embodiment (see FIG. 4), the third embodiment (see FIG. 5), another embodiment [a]>
The invention described in claim 2
The monitoring network according to claim 1, wherein
The status of the monitoring result is at least one information value selected from the group consisting of an indefinite state, a reference unnecessary state, a reference unknown state, and a reference destination absent state, in addition to the two information values of the generation state and the return state Have
The indefinite state represents a state in which neither the occurrence state nor the return state can be determined,
The reference unnecessary state represents a state in which it is prohibited to refer to the state of the monitoring result,
The reference unknown state represents a state in which whether or not the reference unnecessary state is unknown,
The state of no reference destination represents a state where the state of the monitoring result to be referred to does not exist.

<Claim 3: Corresponds to the first embodiment (see FIGS. 1 to 3)>
The invention according to claim 3
In the monitoring network according to claim 1 or 2,
The state history generating means uses the current time measured by the time measuring means as a survival confirmation time, generates the state history by combining the survival confirmation time, the determined time, and the history element,
The state history is configured by arranging the survival confirmation time, the confirmed time, and one or more history elements into one,
The survival confirmation time is technically characterized in that it is information of the latest time when the normal operation of the monitoring device is confirmed.

  According to the third aspect, the monitoring system can surely grasp the presence or absence of the failure of the monitoring device or the failure of the communication line based on the survival confirmation time.

<Claim 4: Corresponds to the fourth embodiment (see FIGS. 6 and 7)>
The invention according to claim 4
In the monitoring network according to any one of claims 1 to 3,
The monitoring system has a technical feature in that an identifier and attribute information are assigned to the state history stored in the storage management unit and associated and managed.

  According to the fourth aspect, the administrator of the monitoring network refers to a plurality of state histories collectively for the state histories narrowed down by designating information values included in the attribute information, or is included in the plurality of state histories. Since history elements can be added or deleted collectively, a plurality of state histories can be managed effectively.

<Claim 5: Corresponds to the twelfth embodiment (see FIGS. 15 to 21) and the thirteenth embodiment (see FIGS. 22 to 28)>
The invention described in claim 5
In the monitoring network according to any one of claims 1 to 4,
The monitoring system uses one or a plurality of the state histories as a function argument, generates a new state history obtained by processing the state history, and causes the plurality of state histories to interact with each other. It is technically characterized by comprising a calculation means for generating the obtained new state history.

<Claim 6: Corresponds to the ninth embodiment (see FIGS. 11 and 12) and the tenth embodiment (see FIG. 13)>
The invention described in claim 6
The monitoring network according to claim 5, wherein
A plurality of the monitoring systems are provided, and the plurality of monitoring devices and monitoring systems are managed in a hierarchical structure or a mesh structure.

<Claim 7: Corresponds to the eleventh embodiment (see FIG. 14)>
The invention described in claim 7
In the monitoring network according to any one of claims 1 to 6,
The monitoring system may arrange the history elements included in the plurality of state histories into one with a common confirmation time if the confirmation times are the same for a plurality of the state histories. Thus, a technical feature is that a plurality of the state histories are managed as one state history.

<Claim 8: Corresponds to the fifth embodiment (see FIG. 8)>
The invention according to claim 8 provides:
The monitoring network according to any one of claims 1 to 7,
Whenever the state of the monitoring result included in the history element changes, the monitoring system causes the storage management unit to store a preset log character string in accordance with the change in the state of the monitoring result. Is a technical feature.

  According to the eighth aspect, the monitoring system can reliably manage the change in the state of the monitoring result by storing the log character string in the storage management unit without missing the change in the state of the monitoring result.

<Claim 9: Corresponds to the fifth embodiment and the sixth embodiment>
The invention according to claim 9 is:
The monitoring network according to any one of claims 1 to 8,
The monitoring system includes a visual notification unit, an audio notification unit, and a tactile notification unit according to a change in the state of the monitoring result every time the state of the monitoring result included in the history element changes. A technical feature is that a change in the status of the monitoring result is notified to a monitoring network administrator by the selected at least one notification means.

  According to the ninth aspect, the monitoring system can reliably notify the manager of the monitoring network of a change in the status of the monitoring result.

<Claim 10: Corresponds to the seventh embodiment (see FIG. 9)>
The invention according to claim 10 is:
In the monitoring network of any one of Claims 1-9,
The status of the monitoring result is replaced with the numerical value of the monitoring result,
The history element is composed of a numerical value of the change time and the monitoring result,
It is a technical feature that the numerical value of the monitoring result is information of a numerical value at a time when the value changes beyond a preset threshold value.

<Claim 11: Corresponds to the eighth embodiment (see FIG. 10)>
The invention according to claim 11
In the monitoring network of any one of Claims 1-9,
The status of the monitoring result is replaced with a character string of the monitoring result,
The history element is technically characterized in that it includes the change time and the character string of the monitoring result.

<Claim 12 and Claim 13>
The invention according to claim 12
The program for functioning a computer system as said each means in the monitoring network of any one of Claims 1-11.
The invention according to claim 13
The computer-readable recording medium with which the program for functioning a computer system was recorded as said each means in the monitoring network of any one of Claims 1-11.

According to claim 12, it is possible to provide a program for causing a computer system to function so as to realize the monitoring network according to any one of claims 1 to 11.
According to claim 13, a computer-readable recording medium in which the program of claim 12 is recorded can be provided.

1 is a block diagram showing a schematic configuration of a monitoring network 10 according to a first embodiment embodying the present invention. Explanatory drawing for demonstrating the arrangement structure of the state log | history in 1st Embodiment. Explanatory drawing for demonstrating the relationship of each element (survival confirmation time, fixed time, history element) which comprises a state log | history in 1st Embodiment. Explanatory drawing for demonstrating the relationship of each element which comprises a state log | history in 2nd Embodiment. Explanatory drawing for demonstrating the relationship of each element which comprises a state log | history in 3rd Embodiment. Explanatory drawing for demonstrating the link | linkage management with a state log | history, an identifier, and attribute information in 4th Embodiment. Explanatory drawing for demonstrating the link | linkage management with a state log | history, an identifier, and attribute information in 4th Embodiment. Explanatory drawing for demonstrating the example of the log character string memorize | stored in HDD35, when the state of the monitoring result contained in a log | history element changes in 5th Embodiment. Explanatory drawing for demonstrating the arrangement structure of the state log | history in 7th Embodiment. Explanatory drawing for demonstrating the arrangement | sequence structure of the state log | history in 8th Embodiment. The block diagram which shows schematic structure of the monitoring network 100 of 9th Embodiment. The block diagram which shows schematic structure of the monitoring system 110a, 110b of 9th Embodiment. The block diagram which shows schematic structure of the monitoring network 200 of 10th Embodiment. Explanatory drawing for demonstrating the arrangement structure of the state log | history in 11th Embodiment. Explanatory drawing for demonstrating the 12th-1 example of the production | generation method of the new state history which the monitoring system 20c performs in 12th Embodiment. Explanatory drawing for demonstrating the 12th-2nd example of the production | generation method of the new state history which the monitoring system 20c performs in 12th Embodiment. Explanatory drawing for demonstrating the 12th-3 example of the production | generation method of the new state history which the monitoring system 20c performs in 12th Embodiment. Explanatory drawing for demonstrating the 12th-4th example of the production | generation method of the new state history which the monitoring system 20c performs in 12th Embodiment. Explanatory drawing for demonstrating the 12-5th example of the production | generation method of the new state history which the monitoring system 20c performs in 12th Embodiment. Explanatory drawing for demonstrating the 12-6th example of the production | generation method of the new state history which the monitoring system 20c performs in 12th Embodiment. Explanatory drawing for demonstrating the 12-7th example of the production | generation method of the new state history which the monitoring system 20c performs in 12th Embodiment. Explanatory drawing for demonstrating the 13th-1 example of the production | generation method of the new state history which the monitoring system 20c performs in 13th Embodiment. Explanatory drawing for demonstrating the 13th-2 example of the production | generation method of the new state history which the monitoring system 20c performs in 13th Embodiment. Explanatory drawing for demonstrating the effect | action and effect of 13th Embodiment. FIG. 25 is an explanatory diagram illustrating a relationship between an input state history and an output state history in a conventional PUSH type monitoring network in the case illustrated in FIG. 24. 24 is an explanatory diagram showing the relationship between the input state history and the output state history in the PUSH type monitoring networks 100 and 200 of the thirteenth embodiment in the case shown in FIG. Explanatory drawing for demonstrating the 13th-3rd example of the production | generation method of the new state history which the monitoring system 20c performs in 13th Embodiment. Explanatory drawing for demonstrating the 13th-4 example of the production | generation method of the new state history which the monitoring system 20c performs in 13th Embodiment. Explanatory drawing for demonstrating the monitoring network 300 of 14th Embodiment.

  Hereinafter, embodiments embodying the present invention will be described with reference to the drawings. In each embodiment, the same constituent members and constituent elements are denoted by the same reference numerals, and redundant description of the same content is omitted.

<First Embodiment>
FIG. 1 is a block diagram illustrating a schematic configuration of a monitoring network 10 according to the first embodiment.
The monitoring network 10 includes one monitoring system 20, one monitoring device 40, and a communication line CL.

The monitoring system 20 includes a computer main body 21, an input device 22, a display device 23, and a notification device 24.
The computer main body 21 includes a CPU (Central Processing Unit) 30, a GPU (Graphics Processing Unit) 31, a ROM (Read Only Memory) 32, a RAM (Random Access Memory) 33, and an input / output device (I / O). 34, a known microcomputer system including an HDD (Hard Disk Drive) 35 and the like.

  The input device 22 includes, for example, a keyboard and a pointing device, converts an instruction command from the administrator of the monitoring network 10 into a data signal, and converts the data signal via the input / output device 34 of the computer main body 21. It transmits to CPU30 and GPU31.

  The display device 23 includes various types of displays such as an LCD (Liquid Crystal Display) and a CRT (Cathode Ray Tube), and the processing of the CPU 30 and the GPU 31 transmitted via the input / output device 34 of the computer main body 21. The result is displayed on the display screen (monitor screen) to notify the administrator.

  The notification device 24 includes a visual notification means (for example, an indicator, a lamp, etc.), an auditory notification means (for example, a buzzer, a sound reproduction device, etc.), and a tactile notification means (for example, a vibrator, etc.). The processing result of the CPU 30 and GPU 31 transmitted via the input / output device 34 of the computer main body 21 is notified to the administrator.

The monitoring device 40 includes a computer main body 41, a detection device 42, and a clock device 43.
The computer main body 41 is constituted by a known microcomputer system including a CPU 30, a ROM 32, a RAM 33, an input / output device 34, and the like.
The computer main body 41 of the monitoring device 40 is different from the computer main body 21 of the monitoring system 20 only in that the GPU 31 and the HDD 35 are omitted.

The detection device 42 detects the state of the monitoring result of the monitoring target in the monitoring network 10 at predetermined time intervals (periodically), converts the detection result into a data signal, and converts the data signal to a computer. The data is transmitted to the CPU 30 via the input / output device 34 of the main body 41.
The clock device 43 measures the current time, converts the current time into a data signal, and transmits the data signal to the CPU 30 via the input / output device 34 of the computer main body 41.

  Each of the monitoring system 20 and the monitoring device 40 loads a computer program of software stored (recorded) in the ROM 32 to the CPU 30 or the GPU 33, and the CPU 30 or the GPU 33 executes various arithmetic processes according to the computer program, which will be described later. Perform the action.

By the way, the computer program is not a ROM 32 built in the computer main bodies 21 and 41, but a backup RAM (not shown) built in the computer main bodies 21 and 41, or an external recording device (not shown) provided with a computer-readable recording medium. The computer program may be recorded (stored) in a storage device, and the computer program may be loaded from the backup RAM or an external recording device to the CPU 30 or the GPU 31 as necessary.
Incidentally, computer-readable recording media include, for example, semiconductor memory, HD (Hard Disk), optical disc (CD-ROM, DVD, etc.), magneto-optical disc (MO, etc.), phase change disc, magnetic disc, magnetic tape. and so on. The names of specific examples of the recording medium include registered trademarks.

The monitoring system 20 and the monitoring device 40 are connected via a communication line CL.
In other words, the computer main body 21 of the monitoring system 20 and the computer main body 41 of the monitoring apparatus 40 are connected to the input / output devices 34 by the communication line CL.
The input / output device 34 functions as a network controller of the monitoring network 10.
A commercially available personal computer may be used for the monitoring system 20 and the monitoring device 40.

The communication line CL is a transmission path for wired communication or wireless communication.
When the communication line CL is embodied by a transmission line for wired communication, for example, an Internet line using a public telephone line including ISDN (Integrated Services Digital Network), ADSL (Asymmetric Digital Subscriber Line), an optical communication line, etc. It consists of dedicated communication lines such as CATV (Community Antenna TeleVision) and LAN (Local Area Network).
Further, when the communication line CL is embodied by a wireless communication transmission path, the communication line CL is configured by, for example, a wireless LAN using radio wave communication or optical wireless communication.

The computer main body 41 of the monitoring device 40 determines the status of the monitoring result of the monitoring target in the monitoring network 10 based on the detection result of the detection device 42, and generates (creates) a history element whenever the status of the monitoring result changes. To do.
The computer main body 41 determines the latest reception time of the detection result based on the current time measured by the clock device 43 every time the detection device 42 transmits the detection result at regular intervals (periodically). Overwrite the old fixed time as the time.
In addition, the computer main body 41 overwrites the old survival confirmation time with the current time measured by the clock device 43 as the latest survival confirmation time (ALIVE time).
Then, the computer main body 41 generates a state history by combining the survival confirmation time, the confirmation time, and the history element, stores (records) the state history in the RAM 33, converts the state history into a data signal, and pulls the PULL. The data signal of the state history is transmitted to the monitoring system 20 via the communication line CL by the type or the PUSH type.

The computer main body 21 of the monitoring system 20 receives a data signal transmitted from the monitoring device 40 via the communication line CL by the PULL type or the PUSH type, converts the data signal into a state history, and converts the state history into the state history. It is stored (recorded) in the RAM 33 or HDD 35 for management.
In addition, the monitoring system 20 uses a PULL type or a PUSH type to record state history data with respect to another system that uses the state history stored and managed in the RAM 33 or the HDD 35 (post-process system: not shown). The signal is transmitted via the communication line CL.

FIG. 2 is an explanatory diagram for explaining an arrangement configuration of state histories in the first embodiment.
The status history is composed of survival confirmation time, confirmed time, and one or more history elements arranged in this order.
The survival confirmation time is information on the latest time (final time) when the normal operation of the monitoring device 40 is confirmed.
The confirmed time is information on the time when the state history is confirmed.

The history element includes a change time and a monitoring result state.
The change time is information on the time when the state of the monitoring result of the monitoring target in the monitoring network 10 changes.
The status of the monitoring result has two information values, a generation status and a return status.
The occurrence state represents that a predetermined state is occurring in the monitoring target.
The return state indicates that the occurrence state has disappeared (represents that the state has disappeared after a predefined state has occurred in the monitoring target).

The generation state and the return state may be appropriately defined according to the monitoring target of the monitoring network 10.
For example, when the monitoring target of the monitoring network 10 is a digital broadcast TS (Transport Stream), a state where an error has occurred in the TS is defined as an occurrence state, and the error occurrence state of the TS is canceled and an error occurs. It is conceivable to define a state that no longer occurs as a return state.
Note that TS errors are described in the applicant's past patent applications (Japanese Unexamined Patent Application Publication Nos. 2010-1119046, 2008-283603, 2007-142536, and 2006-013612). It is detailed.

Further, when the monitoring target of the monitoring network 10 is the temperature of a nuclear reactor in a nuclear power plant, the state where the temperature of the nuclear reactor exceeds the safe temperature and an abnormally high temperature is generated is defined as the occurrence state. A state in which the temperature falls from an abnormally high temperature and falls below the safe temperature may be defined as a return state.
In addition, when the monitoring target of the monitoring network 10 is a river level, the state where the river level is increased beyond the safe level is defined as the occurrence state, and the river level is lowered to be below the safe level. It is conceivable to define a state as a return state.

The history element [0] is a history element when the monitoring network 10 starts to monitor the monitoring target.
The history element [1] is a history element generated by the monitoring device 40 after the first history element [0] (first time).
The history element [n] is a history element generated by the monitoring device 40 for the nth time from the first history element [0].

FIG. 3 is an explanatory diagram for explaining the relationship between each element (survival confirmation time, confirmed time, history element) constituting the state history in the first embodiment.
In the example shown in FIG. 3, the change time of the history element [0] is “10:10:28”, the state is “returned state”, and the change time of the history element [1] is “10:10:30”. The state is “occurrence state”, the change time of the history element [2] is “10:10:33”, the state is “returned state”, and the change time of the history element [3] is “10:10:37” ", The state is" occurrence state ", the confirmation time is" 10:10:40 ", and the survival confirmation time is" 10:10:42 ".

[Operations and effects of the first embodiment]
In the monitoring network 10 of the first embodiment, the monitoring result of the monitoring target by the monitoring device 40 changes with time, but since the history of the monitoring result is managed by the monitoring system 20 in the state history format, The following actions and effects can be obtained.

  [1] In the PULL type monitoring network 10, when the monitoring system 20 requests the monitoring device 40 to transmit the state history via the communication line CL, the monitoring device 40 reads the state history stored in the RAM 33. The status history is transmitted to the monitoring system 20 via the communication line CL.

For this reason, there are a plurality of monitoring devices 40 between the time when the monitoring system 20 requests the monitoring device 40 to transmit the state history and the next time the transmission of the state history is requested (between the PULL operation and the PULL operation). Even if a plurality of history elements are generated, the plurality of history elements are stored in the RAM 33 of the monitoring device 40, so that the monitoring device 40 can transmit all of the plurality of history elements to the monitoring system 20.
Therefore, in the PULL type monitoring network 10, it is possible to receive all the history elements generated by the monitoring device 40 without the monitoring system 20 missing, and all the history elements generated by the monitoring device 40 are received by the monitoring system 20. Can be managed in sync with time.

  And according to 1st Embodiment, with respect to the real-time property which promises that the process which should be completed in a short time is completed within the predetermined time without being forced to perform the poll which performs the PULL operation in a short cycle. There is an advantage that it is not necessary to write a strict program.

In other words, recent computers have improved their processing speed year by year, but multiple software can perform multitasking operations, multiple interrupt processing can operate in parallel, memory cache structure and virtual memory processing, etc. Therefore, it is operated in a best effort manner in which it is difficult to commit to finish processing that should be completed in a short time within a predetermined time. For example, a process that should be completed within 0.1 seconds with a probability of 99.999% may sometimes take several seconds.
According to the first embodiment, the best effort type can be applied to the polling cycle, which is highly practical.

  [2] In the PUSH type monitoring network 10, the monitoring device 40 generates a history element each time the state of the monitoring result of the monitoring target in the monitoring network 10 changes, and the monitoring device 40 stores the generated history element in the RAM 33. The state history read from the RAM 33 is transmitted to the monitoring system 20 via the communication line CL.

Therefore, even when the monitoring device 40 generates a large number of history elements in a short time, the generated history elements are temporarily stored in the RAM 33, so that each time the monitoring device 40 generates a history element, it is transmitted to the monitoring system 20. Since there is no need, the load on the monitoring system 20 does not become excessive, there is no possibility that the monitoring system 20 misses the history element included in the state history transmitted from the monitoring device 40, and the overhead associated with the transmission of the state history is eliminated. Can be reduced.
Therefore, also in the PUSH type monitoring network 10, the same operation and effect as the PULL type can be obtained, and the monitoring system 20 can manage all the history elements generated by the monitoring device 40 in synchronization with time.

  [3] Since the history element includes information on the change time, the monitoring system 20 can reliably grasp the time when the state of the history element changes.

[4] When the monitoring device 40 transmits the state history data signal to the monitoring system 20, when the transmission is completed, the last history element of the history elements stored in the RAM 33 is stored as the last history element. The removed history element may be deleted.
The monitoring device 40 may delete the state history stored in the RAM 33 when a predetermined time has elapsed after transmitting the state history data signal to the monitoring system 20. .
In this way, the storage capacity of the RAM 33 of the monitoring device 40 can be reduced to reduce the cost, and the history elements can be efficiently stored and saved with the RAM 33 having a small recording capacity.

[5] For the calculation for the monitoring system 20 to generate the state history, the state history can be generated at high speed by using a matrix operation executed by the GPU 31.
The GPU 31 is an arithmetic device intended to perform a large amount of simple operations such as matrix operations at high speed, and is therefore suitable for generating a state history. However, the GPU 31 may be omitted, and the state history may be generated by the CPU 30 capable of high-speed operation or the dedicated hardware configured with a logic circuit.

[6] The confirmed time included in the state history is the time when the computer main body 41 of the monitoring device 40 receives the latest detection result of the detection device 42, and the transmission / reception of data signals between the computer main body 41 and the detection device 42 is performed. It takes a very short time. Therefore, the fixed time that is the time when the detection result is received is substantially the same as the time when the detection device 42 detects the state of the monitoring result of the monitoring target in the monitoring network 10.
The confirmed time is the time when the state history is confirmed.
Therefore, the monitoring system 20 can surely grasp the latest state of the monitoring result of the monitoring target based on the history element having the latest change time and the confirmed time among the plurality of history elements included in the state history.

[7] The survival confirmation time included in the state history is the current time measured by the clock device 43 of the monitoring device 40, and is the latest time when the state history is generated.
The survival confirmation time is the latest time (final time) when the normal operation of the monitoring device 40 is confirmed.
Therefore, the monitoring system 20 can reliably grasp the presence or absence of the failure of the monitoring device 40 or the failure of the communication line CL based on the survival confirmation time.

Second Embodiment
The configuration of the monitoring network 10 of the second embodiment is the same as that of the first embodiment shown in FIG.
The second embodiment is different from the first embodiment only in that the state of the monitoring result included in the history element has an indefinite state information value in addition to the generation state and the return state.
In other words, in the second embodiment, the status of the monitoring result included in the history element has three information values: the occurrence status, the return status, and the indefinite status.

An indeterminate state represents a state in which neither an occurrence state nor a return state can be determined.
In other words, when the data signal of the detection result of the detection device 42 received by the computer main body 41 of the monitoring device 40 contains an error, it is unknown whether the state of the monitoring result included in the history element is the occurrence state or the return state. The computer main body 41 of the monitoring device 40 determines that the monitoring result is indefinite.

FIG. 4 is an explanatory diagram for explaining the relationship between each element (survival confirmation time, confirmed time, history element) constituting the state history in the second embodiment.
The example shown in FIG. 4 is different from the example of the first embodiment shown in FIG. 3 only in that the state of the history element [1] is “indefinite state”.
That is, for the time between “10:10:30” and “10:10:33”, it is unknown whether the state of the monitoring result included in the history element is the occurrence state or the return state.

  According to the second embodiment, another system (post-process system) that uses the state history stored and managed by the monitoring system 20 in the RAM 33 or the HDD 35 or the administrator of the monitoring system 20 An indefinite state can be handled appropriately.

For example, if the monitoring target of the monitoring network 10 is the temperature of a nuclear reactor at a nuclear power plant and the temperature of the nuclear reactor exceeds the safe temperature and an abnormally high temperature is generated, In the post-process system, it is necessary to handle the indefinite state as the generated state because the post-process system must appropriately cope with the generated state.
Further, in the case where the post-process system must deal with only when the state of the monitoring result is surely generated, the post-process system may treat the undefined state as the return state.

<Third Embodiment>
The configuration of the monitoring network 10 of the third embodiment is the same as that of the first embodiment shown in FIG.
The third embodiment is different from the first embodiment only in that the state of the monitoring result included in the history element has an information value of a reference unnecessary state in addition to the generation state and the return state.
That is, in the third embodiment, the state of the monitoring result included in the history element has three information values, that is, the occurrence state, the return state, and the reference unnecessary state.

The reference unnecessary state is that another system (post-process system) that uses the state history stored and managed by the monitoring system 20 in the RAM 33 or the HDD 35 is prohibited from referring to the state of the monitoring result. Represents a state.
That is, the computer main body 41 of the monitoring device 40 sets a time zone in which the state of the monitoring result is not desired to be used in the post-process system as a reference unnecessary state.
It should be noted that the administrator of the monitoring network 10 sets in advance the time zone in which the reference is unnecessary.

For example, when the monitoring target of the monitoring network 10 is an image of a television broadcast and the state in which the image is disturbed is defined as the occurrence state, it is not necessary to monitor the image disturbance during the midnight broadcast suspension. .
Therefore, the monitoring device 40 includes the monitoring result included in the history element for the time zone during which the broadcast is suspended at midnight, regardless of the state of the monitoring result included in the history element generated based on the detection result of the detection device 42. The state history may be generated with the state of FIG.

FIG. 5 is an explanatory diagram for explaining the relationship between each element (survival confirmation time, confirmed time, history element) constituting the state history in the third embodiment.
The example shown in FIG. 5 is different from the example of the first embodiment shown in FIG. 3 only in that the state of the history element [1] is “reference unnecessary state”.
That is, for the time between “10:10:30” and “10:10:33”, the monitoring device 40 determines that the reference is unnecessary regardless of the state of the monitoring result included in the history element. It will be.

<Fourth embodiment>
The configuration of the monitoring network 10 of the fourth embodiment is the same as that of the first embodiment shown in FIG.
The fourth embodiment is different from the first embodiment only in that the monitoring system 20 assigns identifiers and attribute information to the state history stored in the RAM 33 or the HDD 35 and manages them in association with each other. .
Note that specific association management is set by the administrator of the monitoring network 10 using the input device 22 of the monitoring system 20.

6 and 7 are explanatory diagrams for explaining the association management between the state history, the identifier, and the attribute information.
In the example shown in FIG. 6, the history element included in the state history is the birth rate, a state in which the birth rate is increasing is defined as an occurrence state, and a state in which the birth rate is unchanged or decreased is defined as a return state. ing.
An identifier (ID: IDentifier) IDr and attribute information are associated and managed with respect to the state history.
The attribute information includes three information values: country name, population, and GDP (Gross Domestic Product).

  The monitoring system 20 can narrow down the status history, identifier, and attribute information managed in association as shown in FIG. 6 by designating information values included in the attribute information. As shown in FIG. Thus, it is possible to manage the association by assigning an identifier ListID indicating a narrowing result to the list of identifier IDr of the narrowed state history.

In the example shown in FIG. 7, in the example shown in FIG. 6, as a result of specifying and narrowing down a country with a population of 1 billion or more, two countries of China and India are narrowed down, and identifiers IDr [2], The IDr [4] list is assigned and managed by assigning an identifier ListID [0] indicating a narrowing result.
In addition, as a result of narrowing down by specifying countries with a population of 200 million or more and less than 1 billion, the United States (USA) and Indonesia were narrowed down, and the identifiers IDr [0] and IDr [5] of the two countries were narrowed down. The list is assigned and managed by assigning an identifier ListID [1] indicating a narrowing result.

  According to the fourth embodiment, the administrator of the monitoring network 10 refers to a plurality of state histories collectively or designates a plurality of state histories for the state histories narrowed down by designating information values included in the attribute information. Since the included history elements can be added or deleted collectively, a plurality of state histories can be managed effectively.

For example, in the example illustrated in FIG. 7, two state histories included in the identifier ListID [0] can be referred to collectively, and history elements included in the two state histories can be added or deleted collectively.
In the example illustrated in FIG. 7, among the information values included in the attribute information, narrowing is performed based on the population, but narrowing may be performed based on GDP.

<Fifth Embodiment>
The configuration of the monitoring network 10 of the fifth embodiment is the same as that of the first embodiment shown in FIG.
In the fifth embodiment, the status of the monitoring result included in the history element is a combination of the second embodiment and the third embodiment, and the four information values of the occurrence state, the return state, the undefined state, and the reference unnecessary state are displayed. Have.
In the fifth embodiment, each time the status of the monitoring result included in the history element changes, the monitoring system 20 changes the log character string set in advance according to the change in the status of the monitoring result to the HDD 35. Remember me.

FIG. 8 is an explanatory diagram for explaining an example of a log character string stored in the HDD 35 when the state of the monitoring result included in the history element changes.
According to the fifth embodiment, by storing the log character string in the HDD 35 without omission in response to a change in the monitoring result state, the monitoring system 20 can reliably manage the change in the monitoring result state.

Of the log character strings No. 1 to No. 12 shown in FIG. 8, only the log character string preset by the administrator using the input device 22 of the monitoring system 20 is displayed on the display device 23. For example, it is conceivable to display the log character string only when the state of the monitoring result changes to the occurrence state (No. 1, No. 8, No. 11).
Further, if the log character string is displayed on the display device 23 of the monitoring system 20 in addition to storing the log character string in the HDD 35, the administrator of the monitoring network 10 is surely notified of a change in the status of the monitoring result. it can.

<Sixth Embodiment>
The configuration of the monitoring network 10 of the sixth embodiment is the same as that of the first embodiment shown in FIG.
The sixth embodiment is different from the fifth embodiment only in that the monitoring system 20 causes the notification device 24 to execute notifications corresponding to the cases of No. 1 to No. 12 shown in FIG.
Therefore, according to the sixth embodiment, the same operation and effect as the fifth embodiment can be obtained.

For example, when the status of the monitoring result changes to the occurrence status (in the case of No. 1, No. 8, and No. 11 shown in FIG. 8), the monitoring system 20 has a red lamp ( (Not shown) is turned on and a warning sound is emitted from a buzzer (not shown) provided in the notification device 24 to vibrate a vibrator (not shown) provided in the notification device 24.
In addition, the monitoring system 20 detects a yellow lamp (not shown) provided in the notification device 24 when the monitoring result changes to an indefinite state (in the case of No. 21, No. 5, and No. 12 shown in FIG. 8). ) Is lit.
In addition, the monitoring system 20 synthesizes and reproduces the log character strings of No. 1 to No. 12 shown in FIG. 8 by using a voice reproducing device provided in the notification device 24.

<Seventh embodiment>
The configuration of the monitoring network 10 of the seventh embodiment is the same as that of the first embodiment shown in FIG.
The seventh embodiment is different from the first embodiment only in that the status of the monitoring result constituting the history element is replaced with the numerical value of the monitoring result.

FIG. 9 is an explanatory diagram for explaining an arrangement configuration of state histories in the seventh embodiment.
The history element includes a change time and a numerical value of the monitoring result.
The change time is information on the time when the numerical value of the monitoring result of the monitoring target in the monitoring network 10 changes exceeding a preset threshold.

The numerical value of the monitoring result is information on the numerical value at the time when the value changes beyond a preset threshold, and may be appropriately defined according to the monitoring target of the monitoring network 10.
For example, when the monitoring target of the monitoring network 10 is digital broadcasting, it is conceivable to define the bit rate of various data transmitted from the broadcasting station as the numerical value of the monitoring result.
Further, when the monitoring target of the monitoring network 10 is a nuclear power plant reactor, it is conceivable to define the temperature of the reactor as a numerical value of the monitoring result.
Further, when the monitoring target of the monitoring network 10 is a nuclear power plant reactor, it is conceivable to define the temperature of the reactor as a numerical value of the monitoring result.
Further, when the monitoring target of the monitoring network 10 is river safety management, it is conceivable to define the water level of the river as a numerical value of the monitoring result.

<Eighth Embodiment>
The configuration of the monitoring network 10 of the eighth embodiment is the same as that of the first embodiment shown in FIG.
The eighth embodiment is different from the first embodiment only in that the state of the monitoring result constituting the history element is replaced with a character string of the monitoring result.

FIG. 10 is an explanatory diagram for explaining an arrangement configuration of state histories in the eighth embodiment.
The history element is composed of a character string of the change time and the monitoring result.
The change time is information on the time when the character string of the monitoring result of the monitoring target in the monitoring network 10 has changed to another character string.

The character string of the monitoring result may be appropriately defined according to the monitoring target of the monitoring network 10.
For example, when the monitoring target of the monitoring network 10 is digital broadcasting, a character string (“documentary”, “news”, “drama”, “music”) that represents the genre of the program in the electronic program guide used in terrestrial digital broadcasting. Etc.) may be defined as the character string of the monitoring result.

In the eighth embodiment, another system (post-process system) that uses the state history stored and managed by the monitoring system 20 in the RAM 33 or the HDD 35 converts the monitoring result character string into the second or third embodiment. The operation can be handled as each state (occurrence state, return state, undefined state, reference unnecessary state) of the embodiment.
For example, if a character string representing the genre of a program in the electronic program guide is used as the character string of the monitoring result, “documentary” is generated, “news” is returned, “drama” is undefined, “music” "Can be considered as a reference unnecessary state.

<Ninth Embodiment>
FIG. 11 is a block diagram illustrating a schematic configuration of the monitoring network 100 according to the ninth embodiment.
The monitoring network 100 includes monitoring systems 20a to 20c having the same configuration as the monitoring system 20 of the first embodiment shown in FIG. 1, monitoring devices 40a to 40e having the same configuration as the monitoring device 40 of the first embodiment, and the first embodiment. The detectors 42a and 42b and the monitoring systems 110a and 110b have the same configuration as that of the detector 42.
The monitoring systems 20a to 20c, 110a and 110b, the monitoring devices 40a to 40e and the detection devices 42a and 42b are connected via the communication line CL as in the first embodiment, but in FIG. Illustration of CL is omitted.

FIG. 12 is a block diagram illustrating a schematic configuration of the monitoring systems 110a and 110b.
Each of the monitoring systems 110a and 110b having the same configuration includes a computer main body 21, an input device 22, a display device 23, a notification device 24, a detection device 42, and a clock device 43.

The computer main body 21 of the monitoring systems 110a and 110b determines the status of the monitoring result of the monitoring target in the monitoring network 10 based on the detection result of the detection device 42, and generates a history element whenever the status of the monitoring result changes. .
The computer main body 21 of each of the monitoring systems 110a and 110b determines the time at which the detection result is received based on the current time measured by the clock device 43 each time the detection device 42 transmits the detection result at regular intervals. Overwrite the old fixed time as the latest fixed time.
The computer main body 21 of the monitoring systems 110a and 110b overwrites the old survival confirmation time with the current time measured by the clock device 43 as the latest survival confirmation time.
The computer main body 21 of the monitoring systems 110a and 110b generates a state history by combining the survival confirmation time, the confirmed time, and the history element, and stores the state history in the RAM 33 or the HDD 35.

Each of the detection devices 42a and 42b detects the state of the monitoring result of the monitoring target in the monitoring network 100 at predetermined time intervals (periodically), converts the detection result into a data signal, and the data The signal is transmitted to the monitoring systems 110a and 110b via the communication line CL.
The computer main bodies 21 of the monitoring systems 110a and 110b receive the detection results of the detection devices 42a and 42b, respectively, generate the history element based on the detection results of the detection devices 42a and 42b, as in the case of the detection device 42, A state history is generated based on the history element, and the state history is stored in the RAM 33 or the HDD 35.
The computer main body 21 of the monitoring system 110a converts the generated state history into a data signal, and transmits the state history data signal via the communication line CL by the PULL type or the PUSH type.

  In FIG. 11, the transmission direction of the state history is illustrated by a white arrow, and the transmission direction of the state of the monitoring result of the monitoring target is illustrated by a solid arrow.

The monitoring system 20a receives the state history data signals transmitted from the monitoring devices 40a to 40c, newly generates another state history based on the state history, and monitors the other state history data signal. Send to system 20c.
The monitoring system 20b receives state history data signals transmitted from the monitoring devices 40d and 40e, newly generates another state history based on the state history, and monitors the other state history data signal. Transmit to the system 20c, 110a.
The monitoring system 20c receives the state history data signal transmitted from the monitoring systems 20a and 20b, generates another state history based on the state history, and monitors the other state history data signal. Send to system 110b.

The monitoring system 110a receives the data signal of the state history transmitted from the monitoring system 20b, and also receives the data signal of the detection result (the state of the monitoring result to be monitored) transmitted from the detection device 42a. Another state history is newly generated based on the state history and the detection result and the state history generated by the monitoring system 110a itself, and a data signal of the other state history is transmitted to the monitoring system 110b.
The monitoring system 110b receives the state history data signal transmitted from the monitoring system 110a, and also receives the detection result data signal transmitted from the detection device 42b, and the state history and detection result and the monitoring system 110a. Another state history is newly generated based on the state history generated by itself, and the other state history is managed.

In the monitoring network 100 of the ninth embodiment, the state history is transmitted and received between the monitoring systems 20a to 20c, 110a and 110b and the monitoring devices 40a to 40e, and the monitoring systems 110a and 110b receive the detection results of the detection devices 42a and 42b. To do.
The monitoring systems 20a to 20c, 110a, and 110b manage the received state history alone, or generate and manage another state history from the received state history or the state history generated by itself.

Therefore, according to the monitoring network 100 of the ninth embodiment, the monitoring systems 20a to 20c, 110a, and 110b and the monitoring devices 40a to 40e can be managed in a hierarchical structure.
That is, the monitoring system 110b is the top layer (layer) of the hierarchical structure, the monitoring systems 20c and 110a are the second layer, the monitoring systems 20a and 20b are the third layer, and the monitoring devices 40a to 40e are the top layers. It becomes a lower hierarchy.

<Tenth Embodiment>
FIG. 13 is a block diagram illustrating a schematic configuration of the monitoring network 200 according to the tenth embodiment.
The monitoring network 200 differs from the monitoring network 100 of the ninth embodiment shown in FIG. 11 in that the monitoring system 110b transmits a status history data signal to the monitoring system 20b as indicated by the white arrow P. Just a point.

The monitoring system 20b receives the state history data signals transmitted from the monitoring devices 40d and 40e and the monitoring system 110b, and newly generates another state history based on the state history.
Therefore, according to the monitoring network 200 of the tenth embodiment, the monitoring systems 20a to 20c, 110a and 110b and the monitoring devices 40a to 40e can be managed with a mesh structure such as a neural network.

<Eleventh embodiment>
The configuration of the monitoring networks 100 and 200 of the eleventh embodiment is the same as that of the ninth or tenth embodiment shown in FIG. 11 or FIG.

FIG. 14 is an explanatory diagram for explaining an arrangement configuration of state histories in the eleventh embodiment.
For example, in the monitoring system 20c shown in FIG. 11 or 13, if the survival confirmation time and the confirmation time are the same for the two status histories respectively transmitted from the monitoring systems 20a and 20b, the survival confirmation time and State history history element 20b [sent from monitoring system 20b at the end of the array of state history history elements 20a [0] to 20a [n] sent from monitoring system 20a with the same fixed time. [0] to 20b [n] are added and arranged into one to manage as one state history.

Therefore, according to the eleventh embodiment, two state histories respectively generated by the two monitoring systems 20a and 20b can be efficiently managed as one state history by the one monitoring system 20c.
Note that three or more status histories respectively generated by three or more monitoring systems or monitoring devices may be managed as one status history by one monitoring system.

<Twelfth embodiment>
The configuration of the monitoring networks 100 and 200 of the twelfth embodiment is the same as that of the ninth or tenth embodiment shown in FIG. 11 or FIG.
In the twelfth embodiment, the monitoring system 20c receives the data signal of the state history transmitted from the monitoring system 20a, and newly updates another state history (output state history) based on the state history (input state history). To generate.
FIGS. 15-21 is explanatory drawing for demonstrating the 12th-1st example-the 12th-7th example of the production | generation method of the new state log | history which the monitoring system 20c performs in 12th Embodiment, respectively.

[Example 12-1]
As illustrated in FIG. 15, in the 12th example, the monitoring system 20 c generates an output state history by performing a NOT process on the input state history.
That is, the occurrence state of the input state history is converted into the return state in the output state history, and the return state of the input state history is converted into the occurrence state in the output state history.
Then, the survival confirmation time and the confirmation time of the output state history are the same as the input state history.

[Example 12-2]
As shown in FIG. 16, in the twelfth example, the monitoring system 20c generates an output state history by performing a process of removing a short-time occurrence state in the input state history.
That is, the occurrence state that is less than the set time t1 in the input state history is converted into a return state in the output state history.
Therefore, since the occurrence state of time t2 in the input state history is equal to or longer than the set time t1, it remains in the output state history, and the occurrence state of time t3 in the input state history is less than the set time t1, so that the output state history Then, it is converted to the return state.
The survival confirmation time of the output state history is the same as that of the input state history.

When the continuous occurrence state at the input state history confirmation time is equal to or longer than the set time t1, or when the state at the input state history confirmation time is the return state, the input state history confirmation time is the output state history confirmation time. Become.
When the state at the input time history confirmation time is the occurrence state and the continuous occurrence state is less than the set time t1, the change time from the last return state to the occurrence state in the input state history is the time of the output state history. It becomes the fixed time.

[Example 12-3]
As shown in FIG. 17, the 12-3 example differs from the 12-2 example shown in FIG. 16 in that the occurrence state starts from the time Ta, and the occurrence state continues for the time t4 until the confirmed time. It is only a point that t4 is less than the set time t1.
Therefore, since the occurrence state of time t2 in the input state history is equal to or greater than time t1, it remains in the occurrence state in the output state history, and since the occurrence states of times t3 and t4 in the input state history are less than time t1, the output state history Then, it is converted to the return state.
The survival confirmation time of the output state history is the same as that of the input state history.
However, the confirmation time of the output state history is shifted to time Ta, which is an old time by the time t4 of the short occurrence state removed from the input state history.

[Example 12-4]
As shown in FIG. 18, the example 12-4 is different from the example 12-2 shown in FIG. 16 in that the occurrence state starts from time Tb, and the occurrence state continues for the time t5 until the confirmed time. The only point is that t5 is equal to or longer than the set time t1.
Therefore, the occurrence state of the times t2 and t5 in the input state history is equal to or greater than the time t1, and therefore remains in the output state history, and the occurrence state of the time t3 in the input state history is less than the time t1, and thus the output state history. Then, it is converted to the return state.
Then, the survival confirmation time and the confirmation time of the output state history are the same as the input state history.

[Example 12-5]
As shown in FIG. 19, in the 12th-5th example, the monitoring system 20c sets the output state history to the occurrence state when the total occurrence time within the unit time of the occurrence state in the input state history is a predetermined time or more.
In the 12th-5th example, the unit time is set to 18 seconds and the total occurrence time is set to 10 seconds, and the output state history is generated when the occurrence state in the input state history continues for more than 10 seconds within the past 18 seconds. It becomes a state.
Then, the survival confirmation time and the confirmation time of the output state history are the same as the input state history.

[Example 12-6]
As illustrated in FIG. 20, in the twelfth to sixth examples, the monitoring system 20 c generates an output state history by performing processing for removing a short-time return state from the input state history.
That is, the return state that is less than the set time t1 in the input state history is converted into the occurrence state in the output state history.
Therefore, since the return state at time t2 in the input state history is equal to or longer than the set time t1, the output state history also remains in the return state, and the return state at time t3 in the input state history is less than the set time t1. Then, it is converted into an occurrence state.
The survival confirmation time of the output state history is the same as that of the input state history.

When the continuous return state at the input state history confirmation time is longer than the set time t1, or when the state at the input state history confirmation time is the occurrence state, the input state history confirmation time is the output state history confirmation time. Become.
In addition, when the state at the fixed time of the input state history is the return state and the continuous return state is less than the set time t1, the change time from the last occurrence state to the return state in the input state history is the time of the output state history. It becomes the fixed time.

[Example 12-7]
As shown in FIG. 21, in the 12th-7th example, the monitoring system 20c recovers within the unit time from the point when the change from the return state to the occurrence state within the unit time in the input state history exceeds the predetermined number of times. The output state history is set to the generation state for a period from when the change from the state to the generation state becomes zero.
In the 12th-7th example, the unit time is set to 8 seconds and the predetermined number of times is set to 3 times, and from the time when the change from the return state to the generated state becomes 3 times or more in the past 8 seconds in the input state history. In the past 8 seconds, the output state history is in the generated state for the period from the time when the change from the return state to the generated state becomes zero.
Then, the survival confirmation time and the confirmation time of the output state history are the same as the input state history.

  As shown in Examples 12-1 to 12-7, the monitoring system 20c of the twelfth embodiment is obtained by processing a state history using one state history (input state history) as a function argument. A history calculation function for generating a new state history (output state history) is provided.

<13th Embodiment>
The configuration of the monitoring networks 100 and 200 of the thirteenth embodiment is the same as that of the ninth or tenth embodiment shown in FIG. 11 or FIG.
In the thirteenth embodiment, the monitoring system 20c receives two state history data signals respectively transmitted from the monitoring systems 20a and 20b, and performs different processing based on the two state histories (input state history). A new state history (output state history) is generated.
FIGS. 22 and 23 are explanatory diagrams for explaining examples 13-1 and 13-2 of a new state history generation method executed by the monitoring system 20c in the thirteenth embodiment, respectively.

[Example 13-1]
As shown in FIG. 22, in the thirteenth example, the monitoring system 20c generates an output state history by performing AND processing on the two input state histories transmitted from the monitoring systems 20a and 20b. Only when both of the input state histories are in the generated state, the output state history is converted into the generated state, and when one of the two input state histories is in the recovered state, the output state history is converted into the recovered state.

In the thirteenth example, the input state history of the monitoring system 20a is generated at the fixed time, the input state history of the monitoring system 20b is in the return state at the fixed time, and the monitoring system is started from the fixed time of the monitoring system 20a. The determined time of 20b is older than time t5.
That is, at time t5, it is unknown whether the input state history of the monitoring system 20b is in a generation state or a return state.
At time t5, if the input state history of the monitoring system 20b is in the occurrence state, the output state history is converted to the occurrence state, and if the input state history of the monitoring system 20b is in the return state, the output state history is converted to the return state. However, since the input state history of the monitoring system 20b is unknown, the output state history is also unknown.
Therefore, the confirmation time of the output state history is the confirmation time of the monitoring system 20b, and is the oldest time among the confirmation times in the two input state histories.
The survival confirmation time of the output state history is the same as that of the input state history.

[Example 13-2]
As shown in FIG. 23, in the thirteenth example, the monitoring system 20c generates an output state history by performing AND processing on the two input state histories transmitted from the monitoring systems 20a and 20b. When both of the input state histories are in the generated state, the output state history is converted into the generated state, and when the two input state histories are in the generated state and the indefinite state, the output state history is converted into the indefinite state. When either one of the input state histories is in the return state, the output state history is converted into the return state.

In the thirteenth example, the input state history of the monitoring system 20a is in a return state at a fixed time, the input state history of the monitoring system 20b is in an indefinite state at a fixed time, and the monitoring system starts from the fixed time of the monitoring system 20a. The determined time of 20b is older by time t6.
That is, at time t6, it is unknown whether the input state history of the monitoring system 20b is the occurrence state, the return state, or the indefinite state.
However, since the input state history of the monitoring system 20a is in the return state regardless of whether the input state history of the monitoring system 20b is in the generated state, return state, or indefinite state at time t6, the output state history is in the return state. Become.
Therefore, the confirmation time of the output state history becomes the confirmation time of the monitoring system 20a, and becomes a new time of the confirmation times in the two input state histories.
The survival confirmation time of the output state history is the same as that of the input state history.

  As described above, in the AND processing, the return state has the highest priority, and the indeterminate state has the second highest priority for the four information values (occurrence state, return state, undefined state, and reference unnecessary state) of the monitoring result state. The state is given the third priority, and the priority of the reference unnecessary state is the lowest (priority: return state> undefined state> occurrence state> reference unnecessary state).

24-26 is explanatory drawing for demonstrating the effect | action and effect of 13th Embodiment.
The monitoring system 20c generates an output state history by performing an AND process on the two state histories (input state histories) respectively transmitted from the monitoring systems 20a and 20b.

FIG. 25 is an explanatory diagram showing the relationship between the input state history and the output state history in the conventional PUSH type monitoring network in the case shown in FIG.
FIG. 26 is an explanatory diagram showing the relationship between the input state history and the output state history in the PUSH type monitoring networks 100 and 200 of the thirteenth embodiment in the case shown in FIG.

As shown in FIG. 24, since the monitoring system 20c operates in a best effort manner, the time when the status history data transmitted from the monitoring systems 20a and 20b was actually received and the monitoring systems 20a and 20b transmitted The change time of the history element in the state history may vary depending on the history element.
In the conventional PUSH type monitoring network, the time when the monitoring system 20c actually receives the state history data is the change time of the history element included in the state history.

Therefore, the input state history and output state history of the conventional PUSH type monitoring network shown in FIG. 25 are the same as the correct input state history and output state history of the PUSH type monitoring networks 100 and 200 of the thirteenth embodiment shown in FIG. Would be a completely different mistake.
According to the thirteenth embodiment, such problems of the prior art can be solved.

  FIG. 27 and FIG. 28 are explanatory diagrams for explaining a 13th-3rd example and a 13th-4th example of a new state history generation method executed by the monitoring system 20c in the thirteenth embodiment, respectively.

[Example 13-3]
As shown in FIG. 27, in Example 13-3, the monitoring system 20c generates an output state history by performing OR processing on the two input state histories transmitted from the monitoring systems 20a and 20b. When either one of the input state histories is in the generated state, the output state history is converted into the generated state, and only when both of the two input state histories are in the return state, the output state history is converted into the return state.

In the thirteenth example, the input state history of the monitoring system 20a is in the return state at the fixed time, the input state history of the monitoring system 20b is in the return state at the fixed time, and the monitoring system is started from the fixed time of the monitoring system 20a. The determined time of 20b is older by time t7.
That is, at time t7, it is unknown whether the input state history of the monitoring system 20b is in a generated state or a return state.
At time t7, if the input state history of the monitoring system 20b is in the occurrence state, the output state history is converted to the occurrence state, and if the input state history of the monitoring system 20b is in the return state, the output state history is converted to the return state. However, since the input state history of the monitoring system 20b is unknown, the output state history is also unknown.
Therefore, the confirmation time of the output state history is the confirmation time of the monitoring system 20b, and is the oldest time among the confirmation times in the two input state histories.
The survival confirmation time of the output state history is the same as that of the input state history.

[Example 13-4]
As shown in FIG. 28, in Example 13-4, the monitoring system 20c generates an output state history by performing OR processing on the two input state histories transmitted from the monitoring systems 20a and 20b. If both input state histories are in the return state, the output state history is converted to the return state. If the two input state histories are in the return state and indefinite state, the output state history is converted to the indefinite state. When either one of the input state histories is in the generated state, the output state history is converted into the generated state.

In the thirteenth example, the input state history of the monitoring system 20a is generated at the fixed time, the input state history of the monitoring system 20b is indefinite at the fixed time, and the monitoring system is started from the fixed time of the monitoring system 20a. The determined time of 20b is older than time t8.
That is, at time t8, it is unknown whether the input state history of the monitoring system 20b is the occurrence state, the return state, or the indefinite state.
However, since the input state history of the monitoring system 20a is in the generated state regardless of whether the input state history of the monitoring system 20b is in the generated state, return state, or indefinite state at time t8, the output state history is in the generated state. Become.
Therefore, the confirmation time of the output state history becomes the confirmation time of the monitoring system 20a, and becomes a new time of the confirmation times in the two input state histories.
The survival confirmation time of the output state history is the same as that of the input state history.

  As described above, in the OR process, with respect to the four information values of the monitoring result state (occurrence state, return state, indeterminate state, and reference unnecessary state), the occurrence state has the highest priority, the indeterminate state has the second priority, and the return. The state is given the third priority, and the priority order of the reference unnecessary state is the lowest (priority order: occurrence state> undefined state> return state> reference unnecessary state).

As described above, the monitoring system 20c of the thirteenth embodiment uses two state histories (input state histories) as function arguments, and a new state histories obtained by interacting the two state histories ( A history calculation function for generating an output state history) is provided.
It is also possible to generate a new state history obtained by interacting a plurality of state histories with three or more state histories as function arguments.

<Fourteenth embodiment>
FIG. 29 is an explanatory diagram for explaining a monitoring network 300 according to the fourteenth embodiment.
The monitoring system 20 provided in the monitoring network 300 receives data signals of three state histories respectively transmitted from another monitoring system or a monitoring device (not shown), and the three state histories (input states) History) Another state history (output state history) is newly generated based on α to γ.

Here, the monitoring system 20 performs weighting for each of the input state histories α to γ, and when the addition result of the input state histories α to γ exceeds a predetermined value, the output state history is set to the generation state.
For example, for the status of the monitoring result, the monitoring system 20 defines the occurrence state as a numerical value “1”, defines the return state as a numerical value “0”, multiplies the input state history α by a numerical value “2”, The input state history β is multiplied by the numerical value “1”, the input state history γ is multiplied by the numerical value “5”, and output when the addition result of the multiplied values of the input state history α to γ is equal to or larger than a predetermined value. The state history is set as the occurrence state.

  A neural network can be realized by combining the fourteenth embodiment and the tenth embodiment shown in FIG.

For the weighting for each of the input state histories α to γ, the total occurrence time may be used for the state of the monitoring result.
For example, for the input state histories α to γ, the numerical values “2”, “1”, and “5” are respectively multiplied by the time of the occurrence state in the latest x seconds, and the addition result of the multiplied values of the input state histories α to γ is predetermined. The output state history may be set as the generation state when the value exceeds the value.
Further, in the 12-5 example shown in FIG. 19 or the 12-6 example shown in FIG. 20, it is conceivable to perform weighting by multiplying the total occurrence time by a predetermined numerical value.

<Another embodiment>
The present invention is not limited to the above-described embodiments, and may be embodied as follows. Even in this case, operations and effects equivalent to or higher than those of the above-described embodiments can be obtained.

[A] Combining the second embodiment and the third embodiment, the status of the monitoring result included in the history element is set so as to have four information values of the occurrence status, the return status, the undefined status, and the reference unnecessary status. Also good.
Further, a new state may be added to the monitoring result according to the monitoring target of the monitoring network, and it is conceivable to add a reference unknown state and a reference destination absent state.

The reference unknown state represents a state in which it is unknown whether the reference is unnecessary.
For example, if the monitoring target of the monitoring network 10 shown in FIG. 1 is an image of a television broadcast and the state in which the image is disturbed is defined as the occurrence state, is it a time zone during which midnight broadcasting is suspended? When it is not possible to determine whether or not the video is disturbed, it is not certain whether or not the state is regarded as the generated state, so the monitoring system 20 treats it as an unreferenced state.
Although this unknown state seems to be similar to the undefined state, it refers to the case where the state itself is unknown as a result of referring to the state, even though the undefined state is the state to be referenced, whereas the reference is unnecessary A state refers to a case where it is unclear whether or not to refer to the state itself.

The state of no reference destination refers to a state in which there is no state to be referred to when referring to the state of the monitoring result of the monitoring target.
For example, when the monitoring target of the monitoring network 100 shown in FIG. 11 is the presence / absence of sound of all channels that can be received by television broadcasting, and the state in which the sound is present is defined as the occurrence state, In spite of the state to be monitored, since the state cannot be acquired, the monitoring system 20a treats it as an indefinite state.
However, when the monitoring device 40b has not failed, if the monitoring system 20a inquires the monitoring device 40b about the presence or absence of the sound of a television station that does not exist by mistake, the monitoring device 40b does not monitor the sound of the television station in the first place. Since there is no monitoring result state, the monitoring system 20a treats the state as a reference destination absent state.
Thereby, it is possible to clearly distinguish and manage the failure of the monitoring target and the failure of the monitoring system.

[A] The detection devices 42, 42a, and 42b of the respective embodiments detect the state of the monitoring result of the monitoring target at predetermined time intervals (periodically) and each time the detection result is detected. It is transmitted to the computer main bodies 41 and 21.
However, the detection devices 42, 42a, and 42b may detect the state of the monitoring result to be monitored in real time and transmit the detection result to the computer main bodies 41 and 21 in real time.
Further, the detection devices 42, 42a, 42b may detect the state of the monitoring result to be monitored and transmit the detection result to the computer main bodies 41, 21 only when the state changes.

[C] In each of the above embodiments, each of the monitoring devices 40, 40a to 40e includes one detection device 42, but each of the monitoring devices 40, 40a to 40e includes a plurality of detection devices 42. May be.
In the tenth to thirteenth embodiments, the monitoring systems 110a and 110b include one detection device 42, but the monitoring systems 110a and 110b may include a plurality of detection devices 42.

[D] In each of the above-described embodiments, the operations of the monitoring system and the monitoring apparatus are realized by software processing by the computer main bodies 21 and 41 configured by a microcomputer system.
However, the computer main bodies 21 and 41 may be replaced with dedicated circuits by providing a dedicated circuit having a function of realizing the operation of the monitoring system and the monitoring apparatus as hardware.

  [E] In each of the above embodiments, the RAM 33 or the HDD 35 is used as a recording medium. However, if the monitoring system and the monitoring apparatus can reliably perform the operation, the RAM 33 and the HDD 35 are replaced with any recording medium. May be.

  [F] In each of the above embodiments, the status history, the identifier of the status history, the right to generate attribute information, the reference right, the write right, the usage right, and the sales right of the reference right are assigned to each monitoring network user and user group. Management function and the function to manage the usage rights and sales rights of the history calculation function for each user and user group, and each user is charged and monitored for obtaining and exercising each right. The network administrator, the creator of the status history, the creator of the history calculation function, and the sales right holder may be charged.

  [G] The embodiments described above may be combined as appropriate, in which case the actions and effects of the combined embodiments can be combined or a synergistic effect can be obtained.

<Explanation of terms>
Correspondence between the constituent elements described in [Claims] and [Means for Solving the Problems] and the constituent members described in [Mode for Carrying Out the Invention] is as follows.

The “detection means” corresponds to the detection devices 42, 42a, and 42b.
The “time measuring means” corresponds to the clock device 43.
The “state history generating unit” corresponds to the computer main body 41 of the monitoring device 40 and the computer main body 21 of the monitoring systems 110a and 110b.
The “storage unit” corresponds to the RAM 33 of the monitoring device 40.
The “transmission means” corresponds to the input / output device 34 of the monitoring device 40.
The “reception unit” corresponds to the input / output device 34 of the monitoring system 20, 110a, 110b.
The “storage management unit” corresponds to the RAM 33 or the HDD 35 of the monitoring systems 20, 110a, 110b.
The “calculation means” corresponds to the CPU 30 or the GPU 31 of the monitoring system 20, 110a, 110b.
The “notification unit” corresponds to the display device 23 or the notification device 24 of the monitoring system 20, 110a, 110b.

10, 100, 200, 300 ... monitoring network 20, 20a to 20c, 110a, 110b ... monitoring system 21 ... computer body 22 of monitoring system ... input device 23 ... display device 24 ... notification device 30 ... CPU
31 ... GPU
32 ... ROM
33 ... RAM
34 ... I / O device (I / O)
35 ... HDD
40, 40a to 40e ... monitoring device 41 ... computer main body 42, 42a, 42b of the monitoring device ... detection device 43 ... clock device

Claims (13)

A monitoring network comprising one or more monitoring devices, a communication line, and a monitoring system,
The monitoring device
Detection means for detecting the status of the monitoring result of the monitoring target in the monitoring network;
A timekeeping means for measuring the current time;
Based on the detection result of the detection means, the state of the monitoring result is determined, a history element is generated each time the state of the monitoring result changes, and the detection means is based on the current time measured by the time measuring means. A state history generating means for generating a state history by combining a time when the state of the monitoring result is detected as a fixed time, and combining the fixed time and the history element;
Storage means for storing the state history generated by the state history generation means;
A transmission unit that transmits the state history generated by the state history generation unit via the communication line;
The monitoring system includes:
Receiving means for receiving the status history transmitted from the one or more monitoring devices via the communication line;
Storage management means for storing and managing the status history received by the receiving means,
The state history is configured by arranging the confirmed time and one or more history elements into one,
The confirmed time is information on the time when the state history is confirmed,
The history element is composed of a change time and a state of the monitoring result,
The change time is information of a time when the state of the monitoring result has changed,
The state of the monitoring result has two information values, an occurrence state and a return state,
The occurrence state represents that a predefined state is occurring in the monitoring target,
The monitoring network, wherein the return state represents that the occurrence state has disappeared. The monitoring network according to claim 1, wherein
The status of the monitoring result is at least one information value selected from the group consisting of an indefinite state, a reference unnecessary state, a reference unknown state, and a reference destination absent state, in addition to the two information values of the generation state and the return state Have
The indefinite state represents a state in which neither the occurrence state nor the return state can be determined,
The reference unnecessary state represents a state in which it is prohibited to refer to the state of the monitoring result,
The reference unknown state represents a state in which whether or not the reference unnecessary state is unknown,
The no-reference-destination state represents a state in which there is no state of the monitoring result to be referred to. In the monitoring network according to claim 1 or 2,
The state history generating means uses the current time measured by the time measuring means as a survival confirmation time, generates the state history by combining the survival confirmation time, the determined time, and the history element,
The state history is configured by arranging the survival confirmation time, the confirmed time, and one or more history elements into one,
The survival confirmation time is information on the latest time when normal operation of the monitoring device is confirmed. In the monitoring network according to any one of claims 1 to 3,
The monitoring network is characterized in that an identifier and attribute information are assigned to the state history stored in the storage management means and managed in association with each other. In the monitoring network according to any one of claims 1 to 4,
The monitoring system uses one or a plurality of the state histories as a function argument, generates a new state history obtained by processing the state history, and causes the plurality of state histories to interact with each other. A monitoring network comprising a calculation means for generating an obtained new state history. The monitoring network according to claim 5, wherein
A monitoring network comprising a plurality of the monitoring systems, wherein the plurality of monitoring devices and monitoring systems are managed in a hierarchical structure or a mesh structure. In the monitoring network according to any one of claims 1 to 6,
The monitoring system may arrange the history elements included in the plurality of state histories into one with a common confirmation time if the confirmation times are the same for a plurality of the state histories. A monitoring network characterized in that a plurality of the state histories are managed as one state history. The monitoring network according to any one of claims 1 to 7,
Whenever the state of the monitoring result included in the history element changes, the monitoring system causes the storage management unit to store a preset log character string in accordance with the change in the state of the monitoring result. A surveillance network characterized by The monitoring network according to any one of claims 1 to 8,
The monitoring system includes a visual notification unit, an audio notification unit, and a tactile notification unit according to a change in the state of the monitoring result every time the state of the monitoring result included in the history element changes. A monitoring network characterized by notifying an administrator of the monitoring network of a change in the status of the monitoring result by the selected at least one notification means. In the monitoring network of any one of Claims 1-9,
The status of the monitoring result is replaced with the numerical value of the monitoring result,
The history element is composed of a numerical value of the change time and the monitoring result,
The monitoring network is characterized in that the numerical value of the monitoring result is information of a numerical value at a time when the value changes beyond a preset threshold. In the monitoring network of any one of Claims 1-9,
The status of the monitoring result is replaced with a character string of the monitoring result,
The history network includes the change time and the monitoring result character string.   The program for functioning a computer system as said each means in the monitoring network of any one of Claims 1-11.   The computer-readable recording medium with which the program for functioning a computer system was recorded as said each means in the monitoring network of any one of Claims 1-11.

Images