The present invention relates to the field of fault diagnosis and intelligent warning, and in particular, to a fault diagnosis and intelligent warning method for monitoring a system device.
Fault diagnosis and intelligent warning are important functions of monitoring systems. In a current monitoring system, device alarm logic and recovery logic are not clearly differentiated, and fault analysis methods are not unified. Consequently, system fault analysis procedures are chaotically executed, and a probability of occurrence of false alarms is increased. In addition, a traditional system has a single fault analysis function, and simply sets a fault generation and recovery condition, thereby resulting in a large increase in a quantity of repeated alarms in the system, increasing storage space overheads and system CPU consumption, and increasing workloads of maintenance personnel. In addition, the traditional system does not consider a relationship between faulty devices during fault analysis. Consequently, a system fault analysis result has low referability, and system function availability is reduced.
To overcome the disadvantages in the prior art, an objective of the present invention is to provide a fault diagnosis and intelligent warning method for monitoring a system device, to reduce a probability of occurrence of false alarms, reduce a quantity of invalid alarms, reduce storage space overheads, reduce system CPU consumption, reduce workloads of maintenance personnel, and improve system availability.
The objective of the present invention may be achieved by using the following technical solutions:
A fault diagnosis and intelligent warning method for monitoring a system device is provided, including the following steps:
step 1. establishing independent alarm analysis logic and independent recovery analysis logic based on a fault model of each alarm: based on a device operating characteristic, establishing an alarm fault model, and defining device alarm logic and device alarm recovery logic;
step 2. controlling the alarm logic and the recovery logic to be mutually exclusively executed: based on a current fault analysis result, automatically choosing to execute the alarm logic or the recovery logic;
step 3. performing delay processing on an alarm event and a recovery event: buffering a logically generated alarm event and a logically generated recovery event, and controlling, based on an established delay rule, whether to discard a logically generated event; and
step 4. establishing a cascading relationship between alarm events generated after the delay processing: establishing an alarm cascading group based on a relationship between different alarm events, automatically determining, by using generation of an alarm event as a triggering condition, whether alarms in a same cascading group simultaneously exist within a time, and generating association information between alarm events.
Preferably, the rule of automatically choosing to execute the alarm logic or the recovery logic in step 2 is as follows:
Preferably, the delay rule in step 3 includes an event delay time, and the alarm event and the recovery event are mutually excluded within the delay time.
Preferably, step 3 specifically includes the following rules:
Preferably, the relationship between alarm events in step 4 includes a hardware connection relationship between alarm event entities, functions that the entities have in the system, and a time interval between the alarm events.
Preferably, step 4 specifically includes the following steps:
step 4.1. according to a connection relationship between system devices and functional mutual impact between devices, according to a response time of the impact between the devices, establishing a relationship configuration of an alarm event between the devices by groups;
step 4.2. when an independent alarm event is generated, determining, by the system, whether another alarm in a cascading group where the alarm is located occurs within a specified time; and
step 4.3. if the another alarm occurs, further sending, by the system, information of a relationship between the alarm and an alarm that has occurred at the same time as the alarm is sent; if the another alarm does not occur, only the alarm is sent.
Preferably, the device operating characteristic in step 1 includes a device mechanical state and an electrical characteristic value.
Preferably, the alarm includes, but is not limited to, a switching value alarm, a multi-state quantity alarm, an analog quantity alarm, and a curve alarm in a monitoring system.
Preferably, a rule of defining the alarm logic and the recovery logic is as follows:
Compared with the prior art, the present invention has the following advantages:
The following clearly and completely describes the technical solutions in the embodiments of the present invention. Apparently, the described embodiments is some rather than all of the embodiments of the present invention. Based on the embodiments of the present invention, all the other embodiments obtained by those of ordinary skill in the art without inventive effort shall fall within the protection scope of the present invention.
As shown in
Step 1. Establish independent alarm analysis logic and independent recovery analysis logic based on a fault model of each alarm: based on a device operating characteristic, establish an alarm fault model, and define device alarm logic and device alarm recovery logic.
Step 2. Control the alarm logic and the recovery logic to be mutually exclusively executed: based on a current fault analysis result, automatically choose to execute the alarm logic or the recovery logic.
Step 3. Perform delay processing on an alarm event and a recovery event: buffer a logically generated alarm event and a logically generated recovery event, and control, based on an established delay rule, whether to discard a logically generated event.
Step 4. Establish a cascading relationship between alarm events generated after the delay processing: establish an alarm cascading group based on a relationship between different alarm events, automatically determine, by using generation of an alarm event as a triggering condition, whether alarms in a same cascading group simultaneously exist within a time, and generate association information between alarm events.
The rule of automatically choosing to execute the alarm logic or the recovery logic in step 2 is as follows:
The delay rule in step 3 includes an event delay time, and the alarm event and the recovery event are mutually exclusively executed within the delay time.
As shown in
The relationship between alarm events in step 4 includes a hardware connection relationship between alarm event entities, functions that the entities have in the system, and a time interval between the alarm events.
As shown in
Step 4.1. According to a connection relationship between system devices and functional mutual impact between devices, according to a response time of the impact between the devices, establish a relationship configuration of an alarm event between the devices by groups.
Step 4.2. When an independent alarm event is generated, the system determines whether another alarm in a cascading group where the alarm is located occurs within a specified time.
Step 4.3. If the another alarm occurs, the system further sends information of a relationship information between the alarm and an alarm that has occurred at the same time as the alarm is sent; if the another alarm does not occur, only the alarm is sent.
The device operating characteristic in step 1 includes a device mechanical state and an electrical characteristic value.
The alarm is not limited to a switching value alarm, a multi-state quantity alarm, an analog quantity alarm, and a curve alarm in a monitoring system.
A rule of defining the alarm logic and the recovery logic is as follows:
What is mentioned above is only the specific implementation of the present invention, but does not limit the protection scope of the present invention, and anyone skilled in the art can easily think of mortifications and alternations within the technical scope disclosed by the present invention, all of which shall fall within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.
Number | Date | Country | Kind |
---|---|---|---|
201810671962.8 | Jun 2018 | CN | national |
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/CN2019/078248 | 3/15/2019 | WO |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2020/001077 | 1/2/2020 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5513312 | Loebig | Apr 1996 | A |
7890794 | Gasser | Feb 2011 | B1 |
8504214 | Genc | Aug 2013 | B2 |
10049509 | Liu | Aug 2018 | B1 |
10332212 | Jhoney | Jun 2019 | B2 |
10832564 | Subramanian | Nov 2020 | B2 |
20050256601 | Lee | Nov 2005 | A1 |
20050268147 | Yamamoto | Dec 2005 | A1 |
20070078976 | Taylor | Apr 2007 | A1 |
20100102982 | Hoveida | Apr 2010 | A1 |
20110185229 | Lapiotis | Jul 2011 | A1 |
20210041862 | Qian | Feb 2021 | A1 |
Number | Date | Country |
---|---|---|
103700031 | Apr 2014 | CN |
103713976 | Apr 2014 | CN |
104125095 | Oct 2014 | CN |
104808645 | Jul 2015 | CN |
108170581 | Jun 2018 | CN |
109002031 | Dec 2018 | CN |
0482522 | Apr 1992 | EP |
Entry |
---|
International Search Report (in English and in Chinese) and Written Opinion issued in PCT/CN2019/078248, dated Jun. 20, 2019, total 12 pages provided. |
Number | Date | Country | |
---|---|---|---|
20210055984 A1 | Feb 2021 | US |