Fault early warning method and system
By setting up a gateway server and gateway client in the instrument control system of the nuclear power plant, collecting fault data and performing automatic alarm processing, the problem of slaves being unable to take over after the host failure is solved, and the operational safety of the nuclear power unit is improved.
Patent Information
- Application Number
- CN202411171745.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-23
- Publication Date
- 2024-12-03
AI Technical Summary
In the instrument control system of a nuclear power plant, the slave cannot take over normally after the host failure, resulting in the instrument control system being unable to operate normally, which poses safety hazards. It is necessary to collect fault data in a timely manner and automatically analyze potential risks to ensure the stability of the system.
Set up a gateway server and gateway client in the instrument control system, collect fault data through the interface gateway and determine risk warning information based on the preset risk warning logic. The gateway server performs system alarm processing to realize fault data acquisition and automatic fault data of the device node Alarm.
It effectively improves the operational safety of the nuclear power unit, timely identify and handles faults, avoids safety hazards caused by the slave's inability to take over after the host failure, and ensures the stable operation of the system.
Smart Images

Figure CN119071137A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to but is not limited to nuclear power network technology, and particularly to a method and system for fault early warning. Background Art
[0002] With the rapid development of my country's nuclear power industry, the instrumentation and control system has been widely used in the operation of nuclear power units. It not only has the function of online real-time monitoring of field signals and control of field equipment, but also has the function of alarm and historical data analysis. Therefore, the safe and stable operation of field control stations, communication stations, servers, operator stations and other equipment in the instrumentation and control system is very important. Once the equipment of the instrumentation and control system fails and is not identified and repaired in time by the on-site personnel, the nuclear power plant will lose the monitoring of the unit operation data, and the operator will be unable to issue control instructions, which may bring great safety hazards to the nuclear power plant.
[0003] At present, important equipment in the instrumentation and control system adopts the master-slave redundant working mode, which is specifically manifested as: one master and one standby, the master is in working state, and the slave is in hot standby state as a hot device; when the master device fails, the slave device takes over and enters the working state; although the instrumentation and control system was designed with a safe redundant operation mode in mind, in most cases, when the master fails, the slave can be promoted to the master and continue to operate. However, there are some special cases that cause the instrumentation and control system to fail to operate normally after the master fails. Now let's explain one of the special scenarios: devices A, B, and C transmit field signals, and devices A, B, and C are all NETA and NETB dual-network configurations, and devices A and B are redundant machines. Device A is the master, device B is the hot standby, and device C transmits field signals to the host device A. If the A network of device B fails and the B network of device C fails; at this time, device C communicates with device A through the A network, and device A sends data redundancy to device B through the B network, and the instrumentation and control system can operate normally; however, when device A fails, device B is promoted to the host; due to the failure of the A network of device B and the failure of the B network of device C, device C cannot communicate with device B, the field signal cannot be uploaded to the operator station, and the control command cannot be sent to the field device. In the case of cross-faults and multiple faults between multiple devices, the host fails and the slave cannot take over normally.
[0004] In summary, timely collection of fault data from various equipment in the instrumentation and control system and automatic analysis of potential risks are crucial for the safe operation of nuclear power units. Summary of the invention
[0005] The following is a summary of the subject matter described in detail in this application. This summary is not intended to limit the scope of the claims.
[0006] The disclosed embodiments provide a method and system for fault early warning, which can timely collect fault data of various devices in an instrumentation and control system and automatically analyze potential risks.
[0007] The embodiment of the present disclosure provides a method for fault early warning, which is applied to the instrumentation and control system of a nuclear power plant. A gateway server is set on the instrumentation and control system, a gateway client is deployed on each second-layer device node of the instrumentation and control system, and an interface gateway is deployed on each unit of the instrumentation and control system. The interface gateway establishes a communication connection with the gateway client deployed in the unit to which it belongs, and the gateway server is connected with all the interface gateways, including:
[0008] The gateway client collects fault data of the first-layer device nodes and the second-layer device nodes in the instrumentation and control system;
[0009] The interface gateway obtains the fault data of the gateway client that has established a communication connection with it;
[0010] The interface gateway determines the risk warning information based on the pre-set risk warning logic for the fault data;
[0011] The gateway server performs system alarm processing based on fault data and risk warning information;
[0012] The first-layer device nodes include: one or more master-slave redundant field control stations and one or more master-slave redundant field communication stations; the second-layer device nodes include: one or more redundant servers and one or more sites.
[0013] On the other hand, the embodiment of the present disclosure also provides a fault warning system, which is applied to the instrumentation and control system of a nuclear power plant, including: a gateway server set on the instrumentation and control system, a gateway client deployed on each second-layer device node of the instrumentation and control system, and an interface gateway deployed on each unit of the instrumentation and control system. The interface gateway establishes a communication connection with the gateway client deployed in the unit to which it belongs, and the gateway server is connected to all interface gateways; wherein,
[0014] The gateway client is set to collect fault data of the first-layer device nodes and the second-layer device nodes in the instrumentation and control system;
[0015] The interface gateway is configured to: obtain fault data of the gateway client that establishes a communication connection with it; determine risk warning information for the fault data according to a pre-set risk warning logic;
[0016] The gateway server is configured to: perform system alarm processing based on the fault data and defect risk warning information obtained by the interface gateway machine;
[0017] The first-layer device nodes include: one or more master-slave redundant field control stations and one or more master-slave redundant field communication stations; the second-layer device nodes include: one or more redundant servers and one or more sites.
[0018] The disclosed embodiments achieve the acquisition of fault data of device nodes, automatic system alarms, and automatic analysis of potential risks, thereby improving the safety of nuclear power unit operation.
[0019] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or be understood by implementing the present application. Other advantages of the present application can be realized and obtained by the schemes described in the description and the drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] The accompanying drawings are used to provide an understanding of the technical solution of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present application and do not constitute a limitation on the technical solution of the present application.
[0021] Figure 1 A structural block diagram of a system for early warning of faults according to an embodiment of the present disclosure;
[0022] Figure 2 A flowchart of a method for fault warning according to an embodiment of the present disclosure;
[0023] Figure 3 A schematic diagram of a process flow executed by a gateway client according to an embodiment of the present disclosure;
[0024] Figure 4 This is a schematic diagram of local network connection of an instrumentation and control system according to an embodiment of the present disclosure;
[0025] Figure 5 This is a flow chart of implementing path failure judgment processing in the first embodiment of the present disclosure;
[0026] Figure 6 This is a schematic diagram of local network connection of another instrumentation and control system according to an embodiment of the present disclosure;
[0027] Figure 7 This is another flowchart for implementing path failure judgment processing according to an embodiment of the present disclosure;
[0028] Figure 8 The present invention is a flowchart of a process performed by a gateway server according to an embodiment of the present invention. DETAILED DESCRIPTION
[0029] The present application describes multiple embodiments, but the description is exemplary rather than restrictive, and it is obvious to those skilled in the art that there may be more embodiments and implementations within the scope of the embodiments described in the present application. Although many possible feature combinations are shown in the drawings and discussed in the specific embodiments, many other combinations of the disclosed features are also possible. Unless specifically limited, any feature or element of any embodiment may be used in combination with any other feature or element in any other embodiment, or may replace any other feature or element in any other embodiment.
[0030] The present application includes and contemplates combinations of features and elements known to those of ordinary skill in the art. The embodiments, features and elements disclosed in the present application may also be combined with any conventional features or elements to form a unique invention scheme defined by the claims. Any features or elements of any embodiment may also be combined with features or elements from other invention schemes to form another unique invention scheme defined by the claims. Therefore, it should be understood that any feature shown and / or discussed in the present application may be implemented individually or in any appropriate combination. Therefore, except for the limitations made according to the attached claims and their equivalents, the embodiments are not subject to other restrictions. In addition, various modifications and changes may be made within the scope of protection of the attached claims.
[0031] In addition, when describing representative embodiments, the specification may have presented the method and / or process as a specific sequence of steps. However, to the extent that the method or process does not rely on the specific order of the steps described herein, the method or process should not be limited to the steps of the specific order described. As will be understood by those of ordinary skill in the art, other sequences of steps are also possible. Therefore, the specific sequence of the steps set forth in the specification should not be interpreted as a limitation to the claims. In addition, the claims for the method and / or process should not be limited to the steps of performing them in the order written, and those skilled in the art can easily understand that these sequences can be changed and still remain within the spirit and scope of the embodiments of the present application.
[0032] The present disclosure provides a method for early warning of a fault, which is applied to an instrumentation and control system of a nuclear power plant, such as Figure 1 As shown, a gateway server is set up on the instrumentation and control system, a gateway client is deployed on each second-layer device node of the instrumentation and control system, and an interface gateway is deployed on each unit of the instrumentation and control system. The interface gateway establishes a communication connection with the gateway client deployed in the unit to which it belongs, and the gateway server is connected to all interface gateways; Figure 2 Flow chart of the method for fault warning according to the embodiment of the present disclosure. Figure 2 As shown, including:
[0033] Step 201, the gateway client collects fault data of the first layer device nodes and the second layer device nodes in the instrumentation and control system;
[0034] Step 202: The interface gateway obtains fault data of the gateway client that has established a communication connection with it;
[0035] Step 203: The interface gateway determines risk warning information based on the pre-set risk warning logic for the fault data;
[0036] Step 204: The gateway server performs system alarm processing according to the fault data and risk warning information;
[0037] The first-layer device nodes include: one or more master-slave redundant field control stations and one or more master-slave redundant field communication stations; the second-layer device nodes include: one or more redundant servers and one or more sites.
[0038] The disclosed embodiments achieve the acquisition of fault data of device nodes, automatic system alarms, and automatic analysis of potential risks, thereby improving the safety of nuclear power unit operation.
[0039] In an exemplary embodiment, the instrumentation and control system of the embodiment of the present disclosure also includes field device nodes of layer 0.
[0040] In an exemplary instance, one or more sets of master-slave redundant servers in the embodiment of the present disclosure include: one or more sets of master-slave redundant real-time servers and one or more sets of redundant input and output IO servers (including dual master redundant settings); one or more sites include: an engineer station and an operator station.
[0041] Before the gateway client, the interface gateway, and the gateway server execute the fault warning, the gateway client sends a connection request to the interface gateway after startup to establish a communication connection with the interface gateway; the gateway client determines whether the communication connection with the interface gateway is successful; if the communication connection with the interface gateway is unsuccessful, continue to try to establish a communication connection with the interface gateway according to the preset connection cycle until the communication connection with the interface gateway is established. The gateway client executes the following Figure 3 The processing shown includes:
[0042] Step 301: for each second-layer device node, the gateway client determines whether the current device node where it is located is an engineer station; when the current device node is a device node other than the engineer station, the process of obtaining the fault data of the current device node is executed from step 3021; when the current device node is an engineer station, the process of obtaining the fault data of the first-layer device node connected to the engineer station is executed from step 3031;
[0043] Step 3021, determine the first node information of the current device node, the first node information includes: station number, the IP address of the master network and the slave network of the management network;
[0044] Step 3022: Obtain the running program information file of the current device node according to the first node information, and obtain the software list of the instrumentation and control system running on the current device node from the running program information file;
[0045] Obtain the software list and execute the processing from step 3023 to step 3025 according to the first preset period:
[0046] Step 3023, determine the first fault information of the hardware of the current device node according to the hardware of the current device node; the embodiment of the present disclosure may include: obtaining information about the hardware of the current device node, including one or any combination of the following: CPU load, memory load, network load, network connection fault status, CPU temperature, hard disk temperature, etc.; determining the first fault information according to the obtained hardware information; the first fault information may include a network connection failure directly determined according to the network connection failure status; it may also include referring to relevant technologies and judging according to a pre-set hardware alarm threshold, one or any combination of the following hardware failures: CPU overload status, memory overload status, network overload status, CPU temperature exceeding standard status, and hard disk temperature exceeding standard status.
[0047] Step 3024: determining the second fault information of the software running on the current device node obtained by a preset monitoring tool, where the second fault information includes one or any combination of the following: the software is not started, the number of software fault startups exceeds the startup number threshold, and the software is unresponsive, etc.; the monitoring tool in the embodiment of the present disclosure can be implemented with reference to the relevant technology, as long as the recording of the above second fault information can be implemented;
[0048] Step 3025: Obtain the first software running log of each software in the software list, and parse to obtain the third fault information of the software running on the current device node;
[0049] In an exemplary embodiment, the embodiment of the present disclosure parses and obtains the third fault information of the software running on the current device node, including: parsing the first software operation log through a preset first parsing file to obtain the third fault information; wherein the first parsing file is a file that has the following functions for the first software operation log: filtering non-fault operation logs, and formatting the fault logs into the third fault information. The first parsing file in the embodiment of the present disclosure may be a file including a parsing table.
[0050] The software operation log in the embodiment of the present disclosure records important information of the software operation, such as: software startup time, initialization completion information, execution records of key processes, abnormal events during operation, etc.; some of this information is normal information and some is abnormal information, so it is necessary to identify the abnormal information from the software operation information and format a unified new log; the first parsing file in the embodiment of the present disclosure may include the original format information of the abnormal information and the corresponding formatted third fault information; for example, the original format information of the abnormal information is: ZSW Svrdiag:80#node faultfor timeout! t1=3, and the corresponding translated new format information is: Error—Node 80 diagnostic timeout fault, the number of timeouts is 3.
[0051] In the disclosed embodiment, the determined first fault data, second fault data and third fault data are sent as fault data of the current device node to the interface gateway machine of the unit machine group where the current device node is located.
[0052] Step 3031, determine the second node information of the first-layer device node connected to the engineer station, the second node information includes: station number, IP addresses of the host management network master network and slave network, IP addresses of the host system network master network and slave network, IP addresses of the slave management network master network and slave network, and IP addresses of the slave system network master network and slave network;
[0053] The disclosed embodiment can read the station number of the first-layer device node from the node information file of the first-layer device node, and calculate the IP addresses of the management network master network and slave network of the host in the first-layer device node, the IP addresses of the host system network master network and slave network, the IP addresses of the slave management network master network and slave network, and the IP addresses of the slave system network master network and slave network in the first-layer device node with reference to relevant technologies.
[0054] According to the second preset cycle, the processing of step 3032 to step 3033 is performed according to the second node information:
[0055] Step 3032, determine the hardware of the first-layer device node connected to the engineer station, and determine the fourth fault information of the hardware; the first-layer device node connected to the engineer station in the embodiment of the present disclosure includes the control station and / or communication station connected to the engineer station; determining the fourth fault information of the hardware of the first-layer device node connected to the engineer station may include: according to the acquired second node information, sequentially acquire the hardware information of the control station and / or communication station connected to the engineer station, the hardware information includes the following one or any combination: CPU load, memory load, network load, connection status of the management network / connection status of the system network, module fault status, channel fault status. The fourth fault information may include a network fault directly determined according to the module fault status and the channel fault status; it may also include the following one or any combination of hardware faults determined according to the pre-set hardware alarm threshold with reference to the relevant technology: CPU overload status, memory overload status, network overload status, network overload status.
[0056] Step 3033, obtain the second software running log of the first-layer device node connected to the engineer station, and parse to obtain the fifth fault information of the software running on the first-layer device node; wherein the fourth fault information and the fifth fault information are the fault data of the first-layer device node.
[0057] In an exemplary embodiment, the embodiment of the present disclosure parses and obtains the fifth fault information of the software running on the first-layer device node, including: parsing the second software operation log through a preset second parsing file to obtain the fifth fault information; wherein the second parsing file is a file having the following functions for the second software log file: filtering out non-fault operation logs, and formatting the fault logs into the fifth fault information. The second parsing file of the embodiment of the present disclosure may be a file including a parsing table.
[0058] In the disclosed embodiment, the gateway client sends the fourth fault data and the fifth fault data of all first-layer device nodes connected to the engineer station as the fault data of the first-layer device nodes to the interface gateway of the unit group to which the engineer station belongs.
[0059] In an exemplary embodiment, before the interface gateway determines the risk warning information for the fault data according to a preset risk warning logic, the method of the embodiment of the present disclosure further includes:
[0060] For each gateway client, the interface gateway machine determines whether the period during which the gateway machine client fails to send fault data continuously is greater than or equal to a preset period threshold;
[0061] If the period during which the gateway client fails to send fault data continuously is greater than or equal to a preset period threshold, all first-layer device nodes connected to the second-layer device node where the gateway client is located are determined to be faulty, and the data indicating that the first-layer device nodes are faulty are added to the fault data.
[0062] Figure 4 This is a schematic diagram of a local network connection of an instrumentation and control system according to an embodiment of the present disclosure. Figure 4 As shown in the figure, the real-time server host and the real-time server slave are connected by a master-slave redundant logic unit. It means that the real-time server host is connected to the operator station through the management network master network and the management network slave network, and the real-time server slave is connected to the operator station through the management network master network and the management network slave network, and the above network connection (the real-time server host, the real-time server slave and the operator station are connected in a triangular redundant structure) is composed; Figure 5 Flow chart of implementing path failure judgment processing in the first embodiment of the present disclosure, as shown in FIG. Figure 5 As shown, including:
[0063] Step 501, the interface gateway determines that the real-time server host and the management network master network of the operator station are connected normally, and determines the network status of the management network slave network of the operator station and the management network master network of the real-time server slave;
[0064] Step 502: The interface gateway determines that both the management network slave network of the operator station and the management network master network of the real-time server slave network are faulty, sets the path between the real-time server and the operator station as faulty, and generates corresponding risk warning information;
[0065] Step 503: If the path between the real-time server and the operator station fails and the interface gateway determines that the connection between the real-time server host and the management network slave of the operator station is normal, the network status of the management network master of the operator station and the management network slave of the real-time server slave is determined;
[0066] Step 504: The management network master network of the operator station and the management network slave network of the real-time server slave are both faulty, the path between the real-time server and the operator station is set as faulty, and corresponding risk warning information is generated.
[0067] In an exemplary embodiment, the embodiment of the present disclosure may determine a real-time server master and a real-time server slave according to system information of a redundant configuration.
[0068] In the embodiment of the disclosure, when the data communication between the real-time server host and the operator station is normal, if there is a network cross-fault between the real-time server slave and the operator station, once the real-time server host fails or is manually deregistered, the real-time server slave will be promoted to the real-time server host. However, the network between the real-time server promoted to the real-time server host and the operator station cannot communicate, which will cause the operator station to be unable to monitor the operation of the on-site equipment and unable to issue control commands; by identifying the network cross-fault between the real-time server and the operator station, the on-site staff can solve the fault in time, avoiding the operator station from losing monitoring and control.
[0069] Figure 6 FIG. 1 is a schematic diagram of a local network connection of another instrumentation and control system according to an embodiment of the present disclosure. Figure 6 As shown in the figure, the real-time server host and the real-time server slave are connected by a master-slave redundant logic unit; the IO server host and the IO server slave are connected by a dual-master redundant logic unit. Indicates that both servers work as the master at the same time. The real-time server master and the real-time server slave are connected to the IO server master and the IO server slave through two redundant networks, the management network master network and the management network slave network. Only the real-time server as the master communicates with the IO server master and the IO server slave. The above network connection (real-time server master, real-time server slave, IO server master and IO server slave are connected in a four-corner redundant structure) is composed; Figure 7 FIG. 1 is another flowchart for implementing path failure judgment processing according to an embodiment of the present disclosure. Figure 7 As shown, including:
[0070] Step 701: When the interface gateway determines that the management network master network of the real-time server host is connected normally and the management network master network of at least one of the IO server host and the IO server slave is connected normally, the network status of the management network slave network of the IO server host, the management network slave network of the IO server slave, and the management network master network of the real-time server slave is determined;
[0071] Step 702: The network status of the management network slave network of the IO server host, the management network slave network of the IO server slave, and the management network master network of the real-time server slave are all faulty, and the path between the real-time server and the IO server is set to faulty, and corresponding risk warning information is generated;
[0072] Step 703: When the interface gateway determines that the management network master network of the real-time server host is connected normally and the management network master network of at least one of the IO server host and the IO server slave is connected normally, the network status of the management network master network of the IO server host, the management network master network of the IO server slave, and the management network slave network of the real-time server slave is determined;
[0073] Step 704: The management network master network of the IO server host, the management network master network of the IO server slave, and the management network slave network of the real-time server slave are all faulty, the path between the real-time server and the IO server is set as faulty, and corresponding risk warning information is generated.
[0074] In the embodiment of the present disclosure, when the data communication between the real-time server host and the IO server host and the IO server slave is normal, if there is a network cross-fault between the real-time server slave and the two IO servers, when the real-time server switches from master to slave, the network between the real-time server that has been promoted to the master and the two IO servers cannot communicate, the field signal data cannot be uploaded to the real-time server host, and important process alarm events cannot be generated, and the operator cannot monitor the real-time operating status of the field; through the above-mentioned risk warning information, the embodiment of the present disclosure promptly notifies the field staff to solve the instrumentation and control equipment failure and avoid the occurrence of safety accidents. The gateway server execution of the embodiment of the present disclosure Figure 8 The processing includes:
[0075] Step 801: Obtain the fault data and risk warning information of each unit from all interface gateways;
[0076] Step 802, displaying the fault data of each unit respectively according to the unit;
[0077] Step 803: Display risk warning information by unit and perform relevant alarm processing; the alarm processing includes but is not limited to issuing an alarm sound.
[0078] The disclosed embodiment also provides a fault warning system, which is applied to the instrumentation and control system of a nuclear power plant, including: a gateway server set on the instrumentation and control system, a gateway client deployed on each second-layer device node of the instrumentation and control system, and an interface gateway deployed on each unit of the instrumentation and control system. The interface gateway establishes a communication connection with the gateway client deployed in the unit to which it belongs, and the gateway server is connected to all the interface gateways; wherein,
[0079] The gateway client is set to collect fault data of the first-layer device nodes and the second-layer device nodes in the instrumentation and control system;
[0080] The interface gateway is configured to: obtain fault data of the gateway client that establishes a communication connection with it; determine risk warning information for the fault data according to a pre-set risk warning logic;
[0081] The gateway server is configured to: perform system alarm processing based on the fault data and defect risk warning information obtained by the interface gateway machine;
[0082] The first-layer device nodes include: one or more master-slave redundant field control stations and one or more master-slave redundant field communication stations; the second-layer device nodes include: one or more redundant servers and one or more sites.
[0083] In an exemplary embodiment, one or more redundant servers of the disclosed embodiment include: one or more master-slave redundant real-time servers and one or more redundant input and output servers; one or more sites include: an engineer station and an operator station.
[0084] In an exemplary embodiment, the gateway client of the embodiment of the present disclosure is configured as follows:
[0085] For each second-layer device node, the gateway client determines whether the current device node where it is located is an engineer station;
[0086] The current device node is a device node other than the engineer station, and the fault data of the current device node is obtained;
[0087] The current device node is an engineer station, and the fault data of the first-layer device node connected to the engineer station is obtained.
[0088] In an exemplary embodiment, the gateway client of the embodiment of the present disclosure is configured to obtain fault data of the current device node, including:
[0089] Determine the first node information of the current device node, the first node information includes: station number, the IP address of the master network and the slave network of the management network;
[0090] Acquire the running program information file of the current device node according to the first node information, and acquire the software list of the instrumentation and control system running on the current device node from the running program information file;
[0091] The following processing is performed according to the first preset cycle:
[0092] Determine first fault information of the hardware of the current device node according to the hardware of the current device node;
[0093] Determine second fault information of software running on the current device node obtained by a preset monitoring tool, the second fault information including one or any combination of the following: software not started, software fault startup times exceeding a startup times threshold, and software no response;
[0094] Obtaining a first software running log of each software in the software list, and parsing to obtain third fault information of the software running on the current device node;
[0095] The first fault information, the second fault information and the third fault information are fault data of the current device node.
[0096] In an exemplary embodiment, the gateway client of the embodiment of the present disclosure is configured to parse and obtain the third fault information of the software running on the current device node, including:
[0097] Parsing the first software running log by using a preset first parsing file to obtain third fault information;
[0098] The first parsing file is a file that has the following functions for the first software operation log: filtering non-fault operation logs and formatting fault logs into third fault information.
[0099] In an exemplary embodiment, the gateway client of the embodiment of the present disclosure is configured to obtain fault data of the first-layer device node connected to the engineer station, including:
[0100] Determine the second node information of the first-layer device node connected to the engineer station, the second node information includes: station number, IP addresses of the host management network master and slave network, IP addresses of the host system network master and slave network, IP addresses of the slave management network master and slave network, and IP addresses of the slave system network master and slave network;
[0101] According to the second preset period, the following processing is performed according to the second node information:
[0102] Determine the hardware of the first-layer device node connected to the engineer station, and determine the fourth fault information of the hardware;
[0103] Acquire the second software running log of the first-layer device node connected to the engineer station, and parse to obtain the fifth fault information of the software running on the first-layer device node;
[0104] The fourth fault information and the fifth fault information are fault data of the first layer device node.
[0105] In an exemplary embodiment, the gateway client of the embodiment of the present disclosure is configured to parse and obtain the fifth fault information of the software running on the first-layer device node, including:
[0106] parsing the second software operation log by using a preset second parsing file to obtain fifth fault information;
[0107] The second parsing file is a file that has the following functions for the second software log file: filtering out non-fault operation logs, and formatting the fault logs into fifth fault information.
[0108] In an exemplary embodiment, the interface gateway machine of the embodiment of the present disclosure is further configured as follows:
[0109] For each gateway client, determine whether the period during which the gateway client fails to send fault data continuously is greater than or equal to a preset period threshold;
[0110] If the period during which the gateway client fails to send fault data continuously is greater than or equal to a preset period threshold, all first-layer device nodes connected to the second-layer device node where the gateway client is located are determined to be faulty, and the data indicating that the first-layer device nodes are faulty are added to the fault data.
[0111] In an exemplary embodiment, the gateway server of the embodiment of the present disclosure is configured as:
[0112] Obtain the fault data and risk warning information of each unit group from all interface gateways; display the fault data of each unit group separately by unit group; display the risk warning information by unit group, and perform relevant alarm processing; the alarm processing includes but is not limited to, issuing an alarm sound.
[0113] In an exemplary embodiment, a group of master-slave redundant real-time servers includes a real-time server host and a real-time server slave connected by a master-slave redundant logical unit, the real-time server host is connected to an operator station via a management network master network and a management network slave network, and the real-time server slave is connected to the operator station via a management network master network and a management network slave network. The interface gateway of the embodiment of the present disclosure is also configured as follows:
[0114] Make sure that the real-time server host and the operator station's management network master network are connected normally, and determine the network status of the operator station's management network slave network and the real-time server slave's management network master network;
[0115] It is determined that both the management network slave network of the operator station and the management network master network of the real-time server slave are faulty, a group of paths between the real-time server and the operator station are set as faulty, and corresponding risk warning information is generated;
[0116] When a path between a group of real-time servers and an operator station fails, the interface gateway determines that the connection between the real-time server host and the management network slave of the operator station is normal, and then determines the network status of the management network master of the operator station and the management network slave of the server slave;
[0117] The management network master network of the operator station and the management network slave network of the real-time server slave are both faulty, and the paths between a group of real-time servers and the operator station are set as faulty, and corresponding risk warning information is generated.
[0118] In an exemplary embodiment, a group of master-slave redundant real-time servers includes a real-time server host and a real-time server slave connected by a master-slave redundant logical unit, a group of redundant IO servers includes an IO server host and an IO server slave connected by a dual master redundant logical unit, the real-time server host and the real-time server slave are connected to the IO server host and the IO server slave through two redundant networks, the management network master network and the management network slave network, and the interface gateway of the embodiment of the present disclosure is also configured as follows:
[0119] When it is determined that the management network master network connection of the real-time server host is normal, and the management network master network connection of at least one of the IO server host and the IO server slave is normal, determine the network status of the management network slave network of the IO server host, the management network slave network of the IO server slave, and the management network master network of the real-time server slave;
[0120] The network status of the management network slave network of the IO server host, the management network slave network of the IO server slave, and the management network master network of the real-time server slave are all faulty, and the path between a group of real-time servers and IO servers is set as faulty, and corresponding risk warning information is generated;
[0121] When it is determined that the management network master network connection of the real-time server host is normal, and the management network master network connection of at least one of the IO server host and the IO server slave is normal, determine the network status of the management network master network of the IO server host, the management network master network of the IO server slave, and the management network slave network of the real-time server slave;
[0122] The main management network of the IO server host, the main management network of the IO server slave, and the secondary management network of the real-time server slave are all faulty, setting the path between a group of real-time servers and the IO server as faulty, and generating corresponding risk warning information.
[0123] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all components may be implemented as software executed by a processor, such as a digital signal processor or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those of ordinary skill in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.
Claims
1. A fault early warning method, applied to the instrumentation and control system of a nuclear power plant, characterized in that: A gateway server is set up on the instrumentation and control system, a gateway client is deployed on each second-layer device node of the instrumentation and control system, and an interface gateway is deployed on each unit of the instrumentation and control system. The interface gateway establishes a communication connection with the gateway client deployed in the unit to which it belongs. The gateway server is connected to all interface gateways, including: The gateway client collects fault data of the first-layer device nodes and the second-layer device nodes in the instrumentation and control system; The interface gateway obtains the fault data of the gateway client that has established a communication connection with it; The interface gateway determines the risk warning information based on the pre-set risk warning logic for the fault data; The gateway server performs system alarm processing based on fault data and risk warning information; The first-layer device nodes include: one or more master-slave redundant field control stations and one or more master-slave redundant field communication stations; the second-layer device nodes include: one or more redundant servers and one or more sites.
2. The method according to claim 1, characterized in that The group of master-slave redundant servers includes: one or more master-slave redundant real-time servers and one or more redundant input and output IO servers; the one or more sites include: an engineer station and an operator station.
3. The method according to claim 2, characterized in that The gateway client collects fault data of the first layer device nodes and the second layer device nodes in the instrumentation and control system, including: For each of the second-layer device nodes, the gateway client determines whether the current device node where the gateway client is located is an engineer station; The current device node is a device node other than the engineer station, and the fault data of the current device node is obtained; The current device node is an engineer station, and the fault data of the first-layer device node connected to the engineer station is acquired.
4. The method according to claim 3, characterized in that The obtaining of the fault data of the current device node includes: Determine the first node information of the current device node, the first node information including: station number, IP address of the master network and slave network of the management network; Acquire a running program information file of the current device node according to the first node information, and acquire a software list of the instrumentation and control system running on the current device node from the running program information file; The following processing is performed according to the first preset cycle: Determine first fault information of the hardware of the current device node according to the hardware of the current device node; Determine second fault information of the software running on the current device node obtained by a preset monitoring tool, the second fault information including one or any combination of the following: software not started, software fault startup times exceeding a startup times threshold, and software no response; Obtaining a first software running log of each software in the software list, and parsing to obtain third fault information of the software running on the current device node; The first fault information, the second fault information and the third fault information are fault data of the current device node.
5. The method according to claim 4, characterized in that The parsing obtains the third fault information of the software running on the current device node, including: Parsing the first software running log by using a preset first parsing file to obtain the third fault information; The first parsing file is a file that has the following functions for the first software operation log: filtering non-fault operation logs and formatting fault logs into third fault information.
6. The method according to claim 3, characterized in that The acquiring of the fault data of the first-layer device node connected to the engineer station includes: Determine the second node information of the first layer device node connected to the engineer station, the second node information including: station number, IP address of the host management network master network and slave network, IP address of the host system network master network and slave network, IP address of the slave management network master network and slave network, IP address of the slave system network master network and slave network; According to the second preset period, the following processing is performed according to the second node information: Determine the hardware of the first-layer device node connected to the engineer station, and determine the fourth fault information of the hardware; Obtaining a second software running log of the first-layer device node connected to the engineer station, and parsing to obtain fifth fault information of the software running on the first-layer device node; The fourth fault information and the fifth fault information are fault data of the first-layer device node.
7. The method according to claim 6, characterized in that The parsing obtains fifth fault information of the software running on the first-layer device node, including: Parsing the second software operation log by using a preset second parsing file to obtain the fifth fault information; The second parsing file is a file that has the following functions for the second software log file: filtering out non-fault operation logs and formatting fault logs into fifth fault information.
8. The method according to claim 1, characterized in that Before the interface gateway determines the risk warning information for the fault data according to a preset risk warning logic, the method further includes: For each of the gateway clients, the interface gateway machine determines whether the period during which the gateway client machine fails to send fault data continuously is greater than or equal to a preset period threshold; When the period during which the gateway client fails to send fault data continuously is greater than or equal to a preset period threshold, all first-layer device nodes connected to the second-layer device node where the gateway client is located are determined to be faulty, and the data indicating that the first-layer device nodes are faulty are added to the fault data.
9. The method according to claim 2, characterized in that: A group of real-time servers with master-slave redundancy includes a real-time server host and a real-time server slave connected by a master-slave redundancy logic unit, the real-time server host is connected to an operator station via a management network master network and a management network slave network, and the real-time server slave is connected to the operator station via a management network master network and a management network slave network, and the method further includes: The interface gateway determines that the real-time server host and the management network master network of the operator station are connected normally, and determines the network status of the management network slave network of the operator station and the management network master network of the real-time server slave; The interface gateway determines that both the management network slave network of the operator station and the management network master network of the real-time server slave are faulty, sets the path between the group of real-time servers and the operator station as faulty, and generates corresponding risk warning information; When the path between the real-time server and the operator station fails and the interface gateway determines that the real-time server host and the management network slave of the operator station are connected normally, the interface gateway determines the network status of the management network master of the operator station and the management network slave of the server slave; The management network master network of the operator station and the management network slave network of the real-time server slave are both faulty, the path between the group of real-time servers and the operator station is set as faulty, and corresponding risk warning information is generated.
10. The method according to claim 2, characterized in that A group of real-time servers with master-slave redundancy includes a real-time server host and a real-time server slave connected by a master-slave redundancy logic unit, a group of IO servers with redundant settings includes an IO server host and an IO server slave connected by a dual-master redundancy logic unit, the real-time server host and the real-time server slave are connected to the IO server host and the IO server slave through two redundant networks, a management network master network and a management network slave network, and the method further includes: When the interface gateway determines that the management network master network of the real-time server host is connected normally and the management network master network of at least one of the IO server host and the IO server slave is connected normally, the network status of the management network slave network of the IO server host, the management network slave network of the IO server slave and the management network master network of the real-time server slave is determined; The network status of the management network slave network of the IO server host, the management network slave network of the IO server slave and the management network master network of the real-time server slave are all faulty, the path between the group of real-time servers and the IO server is set as faulty, and corresponding risk warning information is generated; When the interface gateway determines that the management network master network of the real-time server host is connected normally, and the management network master network of at least one of the IO server host and the IO server slave is connected normally, the network status of the management network master network of the IO server host, the management network master network of the IO server slave, and the management network slave network of the real-time server slave is determined; The management network main network of the IO server host, the management network main network of the IO server slave and the management network slave network of the real-time server slave are all faulty, the path between the group of real-time servers and the IO server is set as a fault, and corresponding risk warning information is generated.
11. The method according to any one of claims 1 to 10, characterized in that: The gateway server performs system alarm processing according to the fault data and risk warning information, including: The gateway server displays the fault data of the instrumentation and control system by unit, displays the risk warning information of each unit by unit, and executes relevant alarm processing.
12. A fault warning system, applied to the instrumentation and control system of a nuclear power plant, characterized in that: include: A gateway server is set up on the instrumentation and control system, a gateway client is deployed on each second-layer device node of the instrumentation and control system, and an interface gateway is deployed on each unit of the instrumentation and control system. The interface gateway establishes a communication connection with the gateway client deployed in the unit to which it belongs, and the gateway server is connected to all interface gateways; wherein the gateway client is set to: collect fault data of the first-layer device nodes and the second-layer device nodes in the instrumentation and control system; The interface gateway is configured to: obtain fault data of the gateway client that establishes a communication connection with it; determine risk warning information for the fault data according to a pre-set risk warning logic; The gateway server is configured to: perform system alarm processing based on the fault data and defect risk warning information obtained by the interface gateway machine; The first-layer device nodes include: one or more master-slave redundant field control stations and one or more master-slave redundant field communication stations; the second-layer device nodes include: one or more redundant servers and one or more sites.
