CN119646702A

CN119646702A - Abnormal processing method, system and related media based on nuclear power plant technical specifications

Info

Publication number: CN119646702A
Application number: CN202411684324.1A
Authority: CN
Inventors: 杨宗强; 刘志云; 雷玮剑; 刘洪贞; 马廷伟; 司恒远; 彭锦; 汪鹏; 胡明信; 孙晨; 谢静; 谢志国; 雷智远; 林潇
Original assignee: China Nuclear Power Engineering Co Ltd; Shenzhen China Guangdong Nuclear Engineering Design Co Ltd
Current assignee: China Nuclear Power Engineering Co Ltd; Shenzhen China Guangdong Nuclear Engineering Design Co Ltd
Priority date: 2024-11-22
Filing date: 2024-11-22
Publication date: 2025-03-18
Anticipated expiration: 2044-11-22
Also published as: CN119646702B

Abstract

The embodiment of the present application provides an exception handling method, system and related media based on the technical specification of a nuclear power plant, which belongs to the technical field of nuclear power plant operation management. The method includes: obtaining real-time operation data of a nuclear power plant; wherein the real-time operation data is configured with system identification information that identifies the source of the data; based on the real-time operation data, determining the target operation mode of the nuclear power plant; according to the system identification information and the target operation mode, matching an applicable target rule group from a plurality of preset event rule groups; wherein the event rule group is constructed through the content of the technical specification; based on the target rule group, performing anomaly identification on the real-time operation data, and obtaining the target processing information corresponding to the target event rule according to the triggered target event rule. The embodiment of the present application can realize the efficient use of the technical specification.

Description

Abnormality processing method, system and related medium based on technical specifications of nuclear power plant

Technical Field

The application relates to the technical field of nuclear power plant operation management, in particular to an exception handling method, system and related medium based on a technical specification of a nuclear power plant.

Background

The technical specification is an important operation file of the nuclear power plant, but the text quantity is large, and the content records hundreds of events and corresponding thousands of measures, so that the technical specification is an important reference file in the operation of the nuclear power plant. A number of operating constraints (Limit i ng Cond it ions For Operat ion, LCO) for the normal operation of a nuclear power plant are recorded in the technical specification, which are a set of technical parameters that specify that the plant or system must meet in different modes of operation. These operating constraints are set to ensure safe operation of the nuclear power plant, and they define acceptable operating ranges for the nuclear power plant system under certain conditions.

However, in the prior art, the use of technical specifications is not efficient. In some cases, technical specifications are used in working practice only by means of memory of a unit operator and a paper file inquiring method, so that the efficiency is low, and even if the technical specifications can be electronic, the unit operator is required to make multiple consults. And because a device or system in a nuclear power plant is often associated with multiple operating constraints, and the condition of the nuclear power plant in actual operation is complex, multiple events are often triggered simultaneously, and it is difficult for a plant operator to understand the situation to take specific countermeasures. Therefore, how to efficiently utilize the content in the technical specification to cope with the complex operation condition of the nuclear power plant becomes a technical problem to be solved.

Disclosure of Invention

The embodiment of the application mainly aims to provide an abnormality processing method, an abnormality processing system and a related medium based on a technical specification of a nuclear power plant, and aims to realize efficient utilization of the technical specification.

To achieve the above object, a first aspect of an embodiment of the present application provides an exception handling method based on a technical specification of a nuclear power plant, the method including:

acquiring real-time operation data of a nuclear power plant, wherein system identification information for identifying a data source is configured in the real-time operation data;

Determining a target operating mode of the nuclear power plant based on the real-time operating data;

Matching an applicable target rule group from a plurality of preset event rule groups according to the system identification information and the target operation mode, wherein the event rule groups are constructed through the content of a technical specification;

And based on the target rule group, carrying out anomaly identification on the real-time operation data, and obtaining target processing information corresponding to the target event rule according to the triggered target event rule.

In some embodiments, before the matching of the applicable target rule set from the preset plurality of event rule sets according to the system identification information and the target operation mode, the method further includes constructing the event rule set based on a technical specification, and specifically includes:

Performing character recognition processing on contents recorded in the technical specification to obtain specification text data;

Performing application range analysis according to the specification text data to obtain a plurality of rule application condition information;

carrying out rule event analysis according to the specification text data to obtain event rule data;

and carrying out grouping processing on the event rule data based on the rule application condition information to obtain the corresponding event rule group.

In some embodiments, the performing rule event parsing according to the specification text data to obtain event rule data includes:

analyzing the text content based on the specification text data to obtain operation limiting conditions, measure scheme information, event processing time and abnormal checking frequency, wherein the event processing time represents the time for solving the abnormal problem, and the abnormal checking frequency represents the frequency for actively checking equipment or functions;

Generating an abnormality determination condition according to the operation limiting condition;

generating an exception handling scheme corresponding to the operation limiting condition according to the measure scheme information;

Constructing an abnormal event rule based on the abnormal judgment condition, the abnormal processing scheme, the event processing time and the abnormal inspection frequency;

and integrating all the abnormal event rules to obtain event rule data.

In some embodiments, each triggered target event rule is converted into an abnormal trigger event and stored in an event record database to obtain historical event data, the abnormal identification is performed on the real-time operation data based on the target rule group, and target processing information corresponding to the target event rule is obtained according to the triggered target event rule, including:

Determining an association range in the historical event data based on the target rule set to obtain a potential association event set;

Performing exception identification according to the real-time operation data to obtain the triggered target event rule, and generating a corresponding target trigger event;

Performing association matching in the potential association event group based on the target trigger event to obtain a plurality of target association events;

and obtaining corresponding target processing information based on the target trigger event and the target associated events.

In some embodiments, performing association matching in the potential association event group based on the target trigger event to obtain a plurality of target association events, including:

Determining event trigger factors and event trigger time corresponding to the target trigger event according to the target event rule corresponding to the target trigger event;

an associated plurality of target associated events is determined from the set of potential associated events based on the event trigger and the event trigger time.

In some embodiments, before performing association matching in the potential association event group based on the target trigger event to obtain a plurality of target association events, constructing an event association network, specifically including:

Acquiring event triggering time and event triggering factors corresponding to each abnormal triggering event;

And constructing a knowledge graph of each corresponding abnormal trigger event based on the event trigger time and the event trigger factors to obtain an event correlation network.

In some embodiments, after obtaining the corresponding target processing information based on the target trigger event and the plurality of target association events, the method further includes:

generating the target trigger event configured with an event priority label, event trigger time and event processing time according to the triggered target event rule;

The critical degree rating is carried out based on the event priority label, the event triggering time and the event processing time, so that the event critical rating of the target triggering event is obtained;

performing critical degree rating based on the event critical rating and a plurality of target associated events to obtain comprehensive critical rating;

and sending event early warning information according to the comprehensive critical grade.

In some embodiments, the performing anomaly identification on the real-time operation data based on the target rule set, and after obtaining target processing information corresponding to the target event rule according to the triggered target event rule, further includes evaluating the target processing information, including:

Performing exception repair processing on a target trigger event triggering the target event rule based on the target processing information to obtain an exception repair result;

Performing abnormal repair evaluation based on the abnormal repair result to obtain rule feedback information;

And iterating the target event rule based on the rule feedback information to obtain a target modification rule.

In some embodiments, the iterating the target event rule based on the rule feedback information to obtain a target modification rule includes:

Performing simulation environment test according to the target modification rule to obtain rule test information;

And adding the target modification rule to the target rule group according to the rule test information.

In some embodiments, the method further comprises, based on the real-time operation data, determining a target operation mode of the nuclear power plant, and in a case where the nuclear power plant needs to switch the operation mode:

receiving an operation mode switching request to obtain an operation mode to be switched, which is ready to be switched;

based on the operation mode to be switched, matching an applicable preparation rule group from a plurality of preset event rule groups;

performing abnormal association evaluation based on the preparation rule group and the triggered target event rule to obtain a mode switching suggestion;

And executing the operation mode switching request according to the mode switching suggestion.

In some embodiments, the performing abnormal association evaluation based on the preparation rule set and the triggered target event rule to obtain a mode switching suggestion includes:

generating the mode switching suggestion which does not recommend to switch the operation mode under the condition that the abnormal event rule contained in the preparation rule group is associated with the triggered target event rule;

and generating the mode switching proposal for recommending the switching operation mode under the condition that the abnormal event rule contained in the preparation rule group is not associated with the triggered target event rule.

In order to achieve the above objective, a second aspect of the embodiments of the present application provides an exception handling system based on a technical specification of a nuclear power plant, where the system includes a data acquisition module, a rule application range determination module, an operation mode identification module, and an exception identification processing module;

The data acquisition module is used for acquiring real-time operation data of the nuclear power plant, wherein system identification information for identifying a data source is configured in the real-time operation data;

The operation mode identification module is used for determining a target operation mode of the nuclear power plant based on the real-time operation data;

The rule application range determining module is used for matching an applicable target rule group from a plurality of preset event rule groups according to the system identification information and the target operation mode, wherein the event rule groups are constructed through the content of a technical specification;

the anomaly identification processing module is used for carrying out anomaly identification on the real-time operation data based on the target rule set, and obtaining target processing information corresponding to the target event rule according to the triggered target event rule.

In some embodiments, the system further comprises a rules database and an event record database;

the rule database is used for storing abnormal event rules in the event rule group;

the event record database is used for storing abnormal trigger events converted according to the triggered target event rules and recording event priority labels, event trigger time and event processing time corresponding to the target event rules.

To achieve the above object, a third aspect of the embodiments of the present application provides an electronic device, where the electronic device includes a memory and a processor, where the memory stores a computer program, and the processor implements the abnormality processing method based on the technical specification of a nuclear power plant according to the first aspect when executing the computer program.

To achieve the above object, a fourth aspect of the embodiments of the present application proposes a computer-readable storage medium storing a computer program that, when executed by a processor, implements the abnormality processing method based on the technical specification of a nuclear power plant described in the first aspect.

The application provides an exception handling method, system and related medium based on a technical specification of a nuclear power plant, which are used for acquiring real-time operation data of the nuclear power plant and identifying system identification information of a real-time operation data source. The current target operation mode of the nuclear power plant is determined through the real-time operation data, and then the applicable target rule set is matched from a plurality of event rule sets constructed through the content of the technical specification through the system identification information and the target operation mode. And carrying out anomaly identification on the real-time operation data through the target rule group, triggering a corresponding target event rule when the anomaly is found, and obtaining corresponding target processing information according to the target event rule. Therefore, the application constructs a plurality of event rule sets through the content of the technical specification, determines the applicable target rule sets based on the system identification information and the current target operation mode of the nuclear power plant, and then carries out anomaly identification on the fact operation data of the nuclear power plant. When the target event rule is triggered, corresponding target processing information is given. Thereby realizing the efficient utilization of technical specifications.

Drawings

FIG. 1 is a flowchart of an exception handling method based on a technical specification of a nuclear power plant according to an embodiment of the present application;

Fig. 2 is a flowchart before step S103 in fig. 1;

Fig. 3 is a flowchart of step S203 in fig. 2;

fig. 4 is a flowchart of step S104 in fig. 1;

fig. 5 is a flowchart of step S403 in fig. 4;

fig. 6 is a flowchart before step S403 in fig. 4;

fig. 7 is a flowchart after step S404 in fig. 4;

fig. 8 is a flowchart after step S104 in fig. 1;

Fig. 9 is a flowchart of step S803 in fig. 8;

FIG. 10 is another flowchart of an exception handling method based on a technical specification of a nuclear power plant according to an embodiment of the present application;

fig. 11 is a flowchart of step S1003 in fig. 10;

FIG. 12 is a schematic diagram of an exception handling system based on a technical specification of a nuclear power plant according to an embodiment of the present application;

Fig. 13 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

It should be noted that although functional block diagrams are depicted as block diagrams, and logical sequences are shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the block diagrams in the system. The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.

The embodiment of the application provides an abnormality processing method, an abnormality processing system and a related medium based on a technical specification of a nuclear power plant, aiming at realizing efficient utilization of the technical specification.

The method, the system and the related medium for processing the abnormality based on the technical specification of the nuclear power plant provided by the embodiment of the application are specifically described through the following embodiment, and the method for processing the abnormality based on the technical specification of the nuclear power plant in the embodiment of the application is described first.

The embodiment of the application provides an exception handling method based on a technical specification of a nuclear power plant, and relates to the technical field of operation management of the nuclear power plant. The exception handling method based on the technical specification of the nuclear power plant provided by the embodiment of the application can be applied to a terminal, a server side and software running in the terminal or the server side. In some embodiments, the terminal may be a smart phone, a tablet computer, a notebook computer, a desktop computer, etc., the server may be configured as an independent physical server, may be configured as a server cluster or a distributed system formed by a plurality of physical servers, and may be configured as a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, and basic cloud computing services such as big data and artificial intelligence platforms, and the software may be an application for implementing an exception handling method based on a technical specification of a nuclear power plant, but is not limited to the above form.

The application is operational with numerous general purpose or special purpose computer system environments or configurations. Such as a personal computer, a server computer, a hand-held or portable device, a tablet device, a multiprocessor system, a microprocessor-based system, a set top box, a programmable consumer electronics, a network PC, a minicomputer, a mainframe computer, a distributed computing environment that includes any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

Fig. 1 is an optional flowchart of an abnormality processing method based on a technical specification of a nuclear power plant according to an embodiment of the present application, and the method in fig. 1 may include, but is not limited to, steps S101 to S104.

Step S101, acquiring real-time operation data of a nuclear power plant, wherein system identification information for identifying a data source is configured in the real-time operation data;

Step S102, determining a target operation mode of the nuclear power plant based on real-time operation data;

step S103, matching an applicable target rule group from a plurality of preset event rule groups according to the system identification information and the target operation mode, wherein the event rule groups are constructed through the content of the technical specification;

Step S104, based on the target rule group, carrying out anomaly identification on the real-time operation data, and obtaining target processing information corresponding to the target event rule according to the triggered target event rule.

In the steps S101 to S104 shown in the embodiment of the present application, the real-time operation data of the nuclear power plant is obtained, and the system identification information of the real-time operation data source is identified. The current target operation mode of the nuclear power plant is determined through the real-time operation data, and then the applicable target rule set is matched from a plurality of event rule sets constructed through the content of the technical specification through the system identification information and the target operation mode. And carrying out anomaly identification on the real-time operation data through the target rule group, triggering a corresponding target event rule when the anomaly is found, and obtaining corresponding target processing information according to the target event rule. Therefore, the application constructs a plurality of event rule sets through the content of the technical specification, determines the applicable target rule sets based on the system identification information and the current target operation mode of the nuclear power plant, and then carries out anomaly identification on the fact operation data of the nuclear power plant. When the target event rule is triggered, corresponding target processing information is given. Thereby realizing the efficient utilization of technical specifications.

In step S101 of some embodiments, real-time operational data of a nuclear power plant is acquired. Real-time operational data typically includes various parameters and indicators, such as temperature, pressure, flow, vibration, etc., which are critical information in assessing the current status of a nuclear power plant. To ensure accuracy and reliability of the data, the real-time running data will contain system identification information, which is the source for the identification data.

The configuration of the system identification information enables the data to trace back to a specific system or equipment, and is beneficial to follow-up processing measures. For example, if a sensor detects an abnormal reading, system identification information may help an operator quickly locate a particular sensor location, determine if the reading is accurate, or if there is a device failure. In addition, the system identification information also helps to distinguish between multiple similar systems or devices, especially in large nuclear power plants, where multiple sensors or systems of the same type may be operating simultaneously.

Through the step, the running state of the nuclear power plant can be monitored in real time, and necessary data support is provided for matching and abnormality identification of subsequent abnormal event rules. The acquisition of the real-time data is the key for realizing the operation management of the automatic and intelligent nuclear power plant, so that the content of the technical specification can be dynamically applied to the actual operation, and the operation efficiency and the safety of the nuclear power plant are improved.

In step S102 of some embodiments, during the operation of the nuclear power plant, there are a plurality of different modes of operation, each mode having its specific operating parameters and requirements. These modes may include various conditions of startup, power operation, maintenance, shutdown, etc., each of which has a different impact on the equipment and systems of the nuclear power plant.

In order to ensure safe and efficient operation of a nuclear power plant, the current operation mode of the nuclear power plant must be monitored and accurately determined in real time. The real-time operation data contains the current state information of each system and equipment of the nuclear power plant, such as temperature, pressure, flow and other key parameters. Through deep analysis of the data, the current state of the nuclear power plant can be identified and matched with a preset operation mode, so that the target operation mode of the current nuclear power plant is determined.

In step S103 of some embodiments, the system analyzes the system identification information in the real-time operation data and the target operation mode of the nuclear power plant, and then matches a target rule set most suitable for the real-time operation data from the plurality of event rule sets according to the system identification information and the target operation mode. By means of techniques such as exact matching or pattern matching, the system can quickly find and apply the adapted target rule set. The event rule group is constructed in advance according to the content of the technical specification, and comprises a plurality of abnormal event rules which represent rules and conditions to be observed when the nuclear power plant operates.

The technical specifications detail the operational constraints that the nuclear power plant should meet in various modes of operation, including equipment performance parameters, safety thresholds, operating procedures, and the like. By translating these operational constraints into abnormal event rules, a framework for analysis and evaluation of real-time data can be provided.

The implementation of the matching mechanism enables the monitoring system of the nuclear power plant to be more flexible and efficient. The system is allowed to dynamically select the most suitable abnormal event rule for analysis according to the characteristics of the real-time data, so that the monitoring accuracy and response speed are improved. At the same time, this also reduces the operator workload, as they can rely on the system to automatically match and apply the abnormal event rules without having to manually find and apply the complex information in the technical specifications.

In step S104 of some embodiments, after the target rule set is determined, abnormality identification is performed on real-time operation data of the nuclear power plant. In a complex operating environment of a nuclear power plant, the real-time monitoring system must be able to accurately identify any deviations from normal operating parameters in order to take timely measures to ensure safe and stable operation of the plant.

The target rule set contains various operation constraints and countermeasures specified in the technical specifications, which are the basis for evaluating whether real-time operation data meet the safety standards. By comparing the real-time operation data with the abnormal event rules in the target rule set, the system can identify any abnormal condition, such as that a certain parameter exceeds a set safety threshold or the operation state of the equipment does not accord with an expected mode.

Once an anomaly is identified, the system will give countermeasures corresponding to the operational constraints in the technical specification, i.e. target process information, according to the triggered target event rules. The automated response mechanism not only improves the efficiency of handling abnormal situations, but also reduces the possibility of human error.

In some embodiments, the present application builds a set of event rules using the techniques of a rules engine. A rule engine is a software component designed to handle complex business logic and decision making. The main purpose of the rules engine is to separate event rules from application code for ease of administration and maintenance. The operating parameters and safety regulations of a nuclear power plant may need to be updated according to up-to-date technical and regulatory requirements, the flexibility of the rules engine making such updates easier to implement. The technical specifications of the nuclear power plant record a large number of operation limiting conditions and corresponding measures, the rule engine can be used for flexibly adding, deleting or modifying the abnormal event rules, and the rule engine is designed to take the increase of the number of rules into consideration, so hundreds of rules can be easily processed, the advanced rule engine usually comprises a performance optimization mechanism such as a cache, an index and reasoning mechanism and the like, which is critical for processing a large number of rules, and therefore, the rule engine can very well process a large number of abnormal event rules obtained through technical specification conversion. On the other hand, complex operation modes and functional interaction exist between systems and equipment in the nuclear power plant, and the rule engine supports functions such as conflict detection, rule reasoning, simulation execution and the like, so that the problems in the aspect can be well solved, and an application scene containing a large amount of condition judgment and complex logic can be processed. In some embodiments, a rule engine may also be used in combination with a logic diagram that is used to visualize the rules flow in the rule engine to help the user understand better the behavior of the rule engine, with the rule engine being responsible for handling complex business logic, particularly those exception rules that need frequent updating and maintenance. Logic diagrams may be used to represent decision flows within a rules engine. For example, a decision tree logic diagram may be created that shows which actions should be taken under different conditions. In this way, the rules engine can ensure the accuracy and efficiency of the logic process, while the logic diagram provides an intuitive view to help non-technicians better understand the rules engine's working principles, thereby enhancing the transparency and usability of the system.

Referring to fig. 2, in some embodiments, step S103 further includes constructing an event rule set based on the technical specification, which may include, but is not limited to, steps S201 to S204:

step S201, performing character recognition processing on contents recorded in technical specifications to obtain specification text data;

Step S202, carrying out application range analysis according to the specification text data to obtain a plurality of rule application condition information;

step S203, rule event analysis is carried out according to the specification text data to obtain event rule data;

Step S204, grouping processing is carried out on the event rule data based on the condition information of each rule application, and a corresponding event rule group is obtained.

In step S201 of some embodiments, character recognition processing is performed on the original content of the technical specification, which generally refers to converting a specification in a format such as a paper document or PDF into editable and analyzable text data. May be implemented by optical character recognition techniques, or by techniques of other language models.

In step S202 of some embodiments, a plurality of rule application condition information is extracted by parsing the obtained specification text data. In the technical specification, rule applicable condition information defines specific conditions to which operation restriction conditions or countermeasures are applicable, such as a specific operation mode, a device state, or an environmental parameter. By this step it is possible to ascertain which rules should be triggered in which case.

In step S203 of some embodiments, the specification literal data is further analyzed to identify and build specific abnormal event rules. The abnormal event rules are constraint rules transformed by operating constraint conditions, which define actions that the nuclear power plant must take when certain conditions are detected. The text description in the specification is converted into structured abnormal event rule data, and clear guidance is provided for subsequent real-time monitoring.

In step S204 of some embodiments, the abnormal event rules in the event rule data are grouped based on the rule application condition information extracted previously to form a plurality of event rule groups. Each event rule set contains a series of abnormal event rules that should be considered and applied under certain conditions. The packet processing enables the system to quickly match and apply the correct abnormal event rules in the real-time monitoring process, thereby improving the efficiency of abnormal recognition and response.

Through the steps S201 to S204, the complex text information in the technical specification can be converted into abnormal event rules which can be used for real-time monitoring, and powerful support is provided for the safe operation of the nuclear power plant. The method not only improves the accuracy of the application of the abnormal event rules, but also greatly improves the automation and intelligence level of the management of the nuclear power plant based on the technical specification.

Referring to fig. 3, in some embodiments, step S203 may include, but is not limited to, steps S301 to S305:

step S301, analyzing text content based on the text data of the specification to obtain operation limiting conditions, measure scheme information, event processing time and abnormal inspection frequency, wherein the event processing time represents the time for solving the abnormal problem, and the abnormal inspection frequency represents the frequency for actively inspecting equipment or functions;

step S302, generating an abnormality judgment condition according to the operation limiting condition;

step S303, generating an exception handling scheme corresponding to the operation limiting condition according to the measure scheme information;

step S304, constructing an abnormal event rule based on the abnormal judgment condition, the abnormal processing scheme, the event processing time and the abnormal inspection frequency;

step S305, integrating all abnormal event rules to obtain event rule data.

In step S301 of some embodiments, important operation parameters including operation limitation conditions, measure scheme information, event processing time, and anomaly detection frequency are extracted by parsing text contents of the specification. The operating constraints are technical parameters which must be followed by the safe operation of the nuclear power plant, and the measure scheme information indicates countermeasures to be taken in the case of a specific abnormality. The event processing time is the time window allowed to resolve the anomaly issue, and the anomaly detection frequency determines the period of active detection of the device or system.

In step S302 of some embodiments, an abnormality determination condition for use in real-time monitoring is generated in accordance with the extracted operation restriction condition. These conditions define what parameters or states the system should consider to be abnormal and trigger an alarm.

In step S303 of some embodiments, a corresponding exception handling scheme is generated for each operation constraint based on the previously obtained measure scheme information. I.e., an exception handling scheme corresponding to each exception decision condition. These schemes include specific operational steps that should be performed when an anomaly is detected to ensure that the nuclear power plant can respond in time and take corrective action.

In step S304 of some embodiments, an abnormal event rule is constructed in combination with an abnormal decision condition, an abnormal processing scheme, an event processing time, and an abnormal inspection frequency. This step integrates the previously separated information into complete exception rules, each including not only the conditions that determine the exception, but also a detailed scheme of how the exception should be responded to once it occurs.

In step S305 of some embodiments, all the constructed abnormal event rules are integrated to form event rule data. These event rule data are further subjected to packet processing based on rule application condition information. Therefore, a comprehensive rule base is provided for the real-time monitoring system, so that the system can quickly and accurately identify the abnormality and take the predefined measures under different target operation modes and conditions.

In some embodiments, the operator may also customize the exception decision conditions, exception handling schemes, event handling times, and exception checking frequency by the system configuring the input fields for creating the exception event rules. This means that the operator can set specific parameters or thresholds according to specific requirements and operation experience of the nuclear power plant on the basis of the abnormal event rules given by the technical specifications, and flexibly adjust and optimize the monitoring and processing flow of the abnormal event, thereby improving the overall operation efficiency and safety performance. It is also possible to create new rules for anomalies that are better suited to detect anomalies and to determine anomalies based on anomalies that have a fairly high partial relevance in the technical specification.

In some embodiments, the operator may also configure a control area for testing the exception rules through the system to test whether the triggering and operation of the exception rules are normal, e.g., whether the status reasons of the exception triggering event are described correctly, whether the event handling time is reasonable.

In some embodiments, the operator is also provided with the authority to eliminate or reset the abnormal trigger event that has occurred to eliminate or reset the abnormal trigger event that was false triggered or tested.

In some embodiments, because the abnormal event rules may be grouped based on system identification information, the relevant staff may query the abnormal event rules that are in effect based on information of the device or manage the abnormal event rules.

Referring to fig. 4, in some embodiments, each triggered target event rule is converted into an abnormal trigger event and stored in an event record database to obtain historical event data, and step S104 may include, but is not limited to, steps S401 to S404:

step S401, determining an association range in historical event data based on a target rule set to obtain a potential association event set;

step S402, carrying out anomaly identification according to real-time operation data to obtain a triggered target event rule and generating a corresponding target trigger event;

step S403, performing association matching in a potential association event group based on the target trigger event to obtain a plurality of target association events;

step S404, obtaining corresponding target processing information based on the target trigger event and the plurality of target association events.

In step S401 of some embodiments, a potential association range is first determined in the historical event data based on the target rule set to identify other events that may be related to the current anomaly. This step finds events that are similar or causally related to the current abnormal condition by analyzing the historical data, thereby obtaining a set of potentially related events. This helps the system understand the general view of anomalies, rather than just seeing a single event in isolation.

In some embodiments, in step S402, the anomaly identification is performed using real-time operation data, and in this process, the system obtains the triggered target event rule according to the anomaly event rule in the target rule set. When the target event rule is triggered, the system generates a corresponding target trigger event, and the event records the specific abnormal situation and trigger condition in detail. The target trigger event is essentially the same as the exception trigger event, except that the exception trigger event is historical data stored in the event log database.

In step S403 of some embodiments, the system will make a deep association match in the previously determined set of potential association events based on the target trigger event. This step is to discover other events related to the current anomaly, whether they are direct causes or indirect effects. In this way, the system can identify a plurality of target-related events, providing more information for a comprehensive understanding and handling of anomalies.

In step S404 of some embodiments, the system will integrate the target trigger event with the identified plurality of target association events to determine the optimal processing scheme. This step involves an in-depth analysis of the event and an evaluation of possible treatment measures to obtain corresponding target treatment information. Such information will instruct the operator to take appropriate action to resolve the anomaly and resume normal operation of the system.

Through steps S401 to S404, a comprehensive and deep exception handling flow is constituted. The process not only can respond to the abnormality in real time, but also can provide a more comprehensive view angle and a more effective processing scheme by analyzing the historical data and identifying the related event. The method not only improves the safety and reliability of the operation of the nuclear power plant, but also optimizes the efficiency and effect of event processing.

Referring to fig. 5, in some embodiments, step S403 may include, but is not limited to, steps S501 to S502:

Step S501, determining event trigger factors and event trigger time corresponding to target trigger events according to target event rules corresponding to the target trigger events;

step S502, determining a plurality of associated target associated events from the potential associated event group based on the event trigger factors and the event trigger time.

In step S501 of some embodiments, an event trigger factor and a trigger time of a trigger event are determined according to a target event rule corresponding to a target trigger event. An event trigger is a specific condition or parameter that causes a rule to be triggered, such as a certain sensor reading exceeding a preset safety threshold. The event trigger time is the specific moment when the target event rule is triggered, which is very important for understanding the timing and dynamic change of the target trigger event.

In step S502 of some embodiments, a target correlation event is selected from a set of potential correlation events that is related to a current target trigger event depth based on the event trigger factor and the event trigger time. This screening process may involve comparison of time stamps, matching of event types, and analysis of anomaly sources. In this way, the system is able to identify those target-related events that are closely related in time and logically to the current target trigger event.

The significance of this step is that it not only helps the operator locate the root cause of the anomaly quickly, but also predicts possible chain reactions and secondary effects. For example, if a failure of a certain device triggers a series of protection actions, then these protection actions may also be considered as events associated with the initial failure event. By identifying these correlated events, the operator can more fully evaluate the impact of the anomaly and take appropriate action to avoid potential risk.

Referring to fig. 6, in some embodiments, step S403 may be preceded by, but not limited to, steps S601 to S602:

step S601, acquiring event trigger time and event trigger factors corresponding to each abnormal trigger event;

step S602, based on the event triggering time and the event triggering factors, carrying out knowledge graph construction on each corresponding abnormal triggering event to obtain an event correlation network.

In steps S601 to S602 of some embodiments, the system constructs an event correlation network based on the historical event data, and correlates the abnormal trigger events with the correlation factors in time sequence. And the event trigger factors and the event trigger time of each abnormal trigger event can be associated in a mode of constructing a knowledge graph, so that an event association network is constructed. Thus, the method can better help operators trace back abnormal trigger events occurring in the past, and also can help to determine associated target associated events from potential associated event groups.

In some embodiments, the associated target association event is determined from the potential association event group according to the system identification information configured by the real-time operation data of the trigger target trigger event or the functional module related to the target trigger event, so that the abnormal source and development process of the abnormal trigger event are more comprehensively evaluated.

Through steps S501 to S502, an effective event correlation analysis flow is constituted. The process provides powerful support for the abnormality treatment of the nuclear power plant by deeply analyzing the triggering factors and time of the abnormality and performing accurate matching in the potential associated events. This not only improves the accuracy and efficiency of exception handling, but also enhances the security and reliability of the overall system.

Referring to fig. 7, in some embodiments, step S404 may include, but is not limited to, steps S701 to S704:

step S701, generating a target trigger event configured with an event priority label, event trigger time and event processing time according to a triggered target event rule;

Step S702, carrying out critical degree rating based on event priority labels, event triggering time and event processing time to obtain event critical rating of a target triggering event;

Step S703, carrying out critical degree rating based on the event critical rating and a plurality of target associated events to obtain comprehensive critical rating;

and step S704, sending event early warning information according to the comprehensive critical grade.

In step S701 of some embodiments, a target trigger event configured with an event priority tag, an event trigger time, and an event processing time is generated according to a triggered target event rule. Event priority labels are a key parameter that classifies events according to their severity and urgency. The event trigger time records the specific moment when the rule is triggered, and the event processing time is the time window allowed for solving the exception problem.

In step S702 of some embodiments, a criticality rating is performed based on the event priority label, event trigger time, and event processing time to determine the urgency and possible impact of the event, resulting in an event criticality rating of the target trigger event. For example, in some embodiments, an adverse effect may occur due to insufficient event processing, and its criticality rating will be high, meaning immediate action is required to respond.

In step S703 of some embodiments, this rating process is further extended to multiple target-associated events, resulting in a comprehensive critical rating. In this step, the system will integrate all relevant events, including interactions and potential chain reactions between them, to arrive at an integrated critical grade. This rating takes into account not only the criticality of the individual events, but also their potential impact on the operational safety of the nuclear power plant as a whole.

In step S704 of some embodiments, the system issues event alert information based on the integrated critical rating. This pre-warning information will provide details of the event, including its criticality, possible impact and suggested response measures. The early warning information can be issued through various channels, including an alarm system of a control room, an email, a short message or an automatic voice call, etc., so that all related personnel can be ensured to be informed in time and take necessary actions.

Through steps S701 to S704, the safety monitoring system of the nuclear power plant can rapidly and accurately respond to the abnormal event, and ensure that all related personnel can timely know the condition and countermeasures of the event. The safety and the reliability of the nuclear power plant are improved, and the efficiency and the effect of handling emergency events are also improved.

Referring to fig. 8, in some embodiments, step S104 further includes evaluating the target processing information, which may include, but is not limited to, steps S801 to S803:

Step S801, performing exception repair processing on a target trigger event triggering a target event rule based on target processing information to obtain an exception repair result;

step S802, performing abnormal repair evaluation based on an abnormal repair result to obtain rule feedback information;

Step S803, iterating the target event rule based on the rule feedback information to obtain a target modification rule.

In step S801 of some embodiments, an exception repair process is performed on a target trigger event that triggers a target event rule based on target processing information. In this step, the operator or automated system will perform countermeasures given by the target process information to resolve or mitigate the abnormal event. These countermeasures may include adjusting device parameters, restarting the system, performing certain maintenance procedures, and the like. After the countermeasures are performed, the system will record the exception repair results, including whether the treatment was successful or not, the effect of the treatment, and any observed side effects.

In step S802 of some embodiments, the system will perform an anomaly repair assessment based on the anomaly repair result. This evaluation process involves analyzing the effect of the exception repair process, determining whether the problem was successfully solved, and whether the intended objective was reached. The evaluation results will generate rule feedback information that is critical to understanding the validity and efficiency of the current target event rules.

In step S803 of some embodiments, the system will iterate the target event rule based on the rule feedback information. This iterative process may include adjusting exception decision conditions, modifying the processing scheme, updating event processing time, or adjusting the exception checking frequency. In this way, the nuclear power plant can constantly learn and improve, making the event rules more accurate and efficient.

Through steps S801 to S803, a continuous improvement loop based on empirical feedback is commonly achieved. By evaluating the abnormal repair results and updating the event rules accordingly, the nuclear power plant can improve the capability of responding to abnormal triggering events, reduce the occurrence probability of future similar events, and improve the overall operation safety and reliability. This self-optimizing and learning capability is a key feature of modern nuclear power plant management that helps ensure that the nuclear power plant maintains the highest safety standards under constantly changing operating conditions.

Referring to fig. 9, in some embodiments, step S803 may include, but is not limited to, steps S901 to S902:

step S901, performing simulation environment test according to a target modification rule to obtain rule test information;

Step S902, adding a target modification rule to a target rule group according to the rule test information.

In step S901 of some embodiments, sufficient testing and verification is required before the target modification rule is applied to the actual operation. The target modification rules are first tested in a simulation environment. The simulation environment is a low risk test platform that simulates the actual operating conditions of the nuclear power plant, allowing operators or engineers to evaluate the modification effects of the target modification rules without disturbing the real system. In simulation testing, various hypothetical situations can be created, including equipment failures, parameter anomalies, etc., to verify that the target modification rule can properly trigger and guide appropriate treatment measures. By the method, the accuracy, reliability and efficiency of the target modification rule can be verified, and the target modification rule can be ensured to effectively identify and respond to abnormal events in practical application.

In step S902 of some embodiments, after the simulated environment test is completed, a target modification rule is added to the target rule group according to the rule test information. This step is to integrate the validated rules into the formal monitoring system of the nuclear power plant. After the target modification rules are added to the target rule set, they will begin to function in the actual monitoring process, directing the operator or automated system to respond to the abnormal event.

Through the steps S901 to S902, the nuclear power plant can ensure that all target modification rules pass through strict tests and verification, thereby ensuring the continuity and safety of the operation of the nuclear power plant. The strict test and examination procedure is helpful for reducing potential risks caused by target modification rule errors, enhancing the response capability of the nuclear power plant to abnormal events, and improving the overall operation efficiency and safety.

Referring to fig. 10, in some embodiments, in the case that the nuclear power plant needs to switch the operation mode, the method may further include, but is not limited to, steps S1001 to S1004:

Step S1001, receiving an operation mode switching request to obtain a to-be-switched operation mode to be switched;

Step S1002, based on the operation mode to be switched, matching the applicable preparation rule set from the preset event rule sets;

step S1003, carrying out abnormal association evaluation based on the preparation rule group and the triggered target event rule to obtain a mode switching suggestion;

step S1004, executing an operation mode switching request according to the mode switching suggestion.

In some embodiments, in step S1001, the control system of the nuclear power plant receives an operation mode switching request in case the nuclear power plant needs to switch operation modes. This request may come from an operator or may be due to a decision by the automated system. The request indicates the operation mode to be switched to currently, and the operation mode to be switched refers to the operation mode to be switched to.

In step S1002 of some embodiments, the system will match the applicable set of preliminary rules from the preset plurality of sets of event rules based on the operational mode to be switched. The set of preliminary rules contains exception rules and parameters corresponding to the operational mode to be switched, which define how the system should respond to different exception events in the new operational mode.

In step S1003 of some embodiments, the system will evaluate for abnormal associations based on the set of preliminary rules and the target event rules that have been triggered. The step is to inquire whether some abnormal trigger events influence the switched operation mode in the triggered target event rule, pre-judge the possible abnormal situation after the operation mode is switched, and generate a mode switching suggestion, and suggest whether to respond to the operation mode switching request to switch the operation mode.

In step S1004 of some embodiments, the control system will execute the operation mode switching request according to the mode switching suggestion. This step includes updating system parameters, adjusting device settings, notifying relevant personnel, etc. to ensure the smoothness and safety of the handoff process.

Referring to fig. 11, in some embodiments, step S1003 may include, but is not limited to including, steps S1101 to S1102:

step S1101, generating a mode switching proposal not recommending a switching operation mode under the condition that the abnormal event rule contained in the preparation rule group is associated with the triggered target event rule;

in step S1102, if the abnormal event rule included in the preparation rule set is not associated with the triggered target event rule, a mode switching suggestion recommending the switching operation mode is generated.

In some embodiments, in step S1101, if the abnormal event rule included in the preliminary rule set is associated with the triggered target event rule, the system generates a mode switching suggestion that does not recommend switching operation modes. Such association may mean that the current abnormal event has not been properly handled, and switching to the operational mode to be switched may exacerbate the existing problem. For example, if an abnormal event associated with the cooling system is occurring and a new mode of operation requires greater cooling efficiency, switching may exacerbate the pressure on the cooling system. In this case, it is recommended that no handover is performed until the current abnormal event is resolved.

In step S1102 of some embodiments, if there is no association of an abnormal event rule in the preliminary rule set with the triggered target event rule, this indicates that switching to the new operational mode is unlikely to be affected by the current abnormal event. In this case, the system generates a mode switching suggestion recommending a switching mode of operation. This may be because the current exception event has been isolated or resolved, or the new mode of operation has enough buffering to handle the potential problem.

Through steps S1101 to S1102, the nuclear power plant can carefully analyze the association between the preliminary rule set and the triggered target event rule to determine whether to switch the operation mode, taking into account the existing triggered target event rule. Thereby helping to ensure the stability and safety of the switching of the operation modes of the nuclear power plant, and preventing possible risks and problems.

The embodiment of the application obtains the real-time operation data of the nuclear power plant and identifies the system identification information of the source of the real-time operation data. The current target operation mode of the nuclear power plant is determined through the real-time operation data, and then the applicable target rule set is matched from a plurality of event rule sets constructed through the content of the technical specification through the system identification information and the target operation mode. And carrying out anomaly identification on the real-time operation data through the target rule group, triggering a corresponding target event rule when the anomaly is found, and obtaining corresponding target processing information according to the target event rule. Therefore, the application constructs a plurality of event rule sets through the content of the technical specification, determines the applicable target rule sets based on the system identification information and the current target operation mode of the nuclear power plant, and then carries out anomaly identification on the fact operation data of the nuclear power plant. When the target event rule is triggered, corresponding target processing information is given. Thereby realizing the efficient utilization of technical specifications.

Referring to fig. 12, the embodiment of the application further provides an abnormality processing system based on a technical specification of a nuclear power plant, which can implement the abnormality processing method based on the technical specification of the nuclear power plant, and the system comprises a data acquisition module, a rule application range determination module, an operation mode identification module and an abnormality identification processing module:

the data acquisition module is used for acquiring real-time operation data of the nuclear power plant; wherein, the real-time operation data is configured with system identification information for identifying the source of the data;

The rule application range determining module is used for matching an applicable target rule group from a plurality of preset event rule groups according to the system identification information and the target operation mode, wherein the event rule groups are constructed through the content of the technical specification;

The specific implementation manner of the exception handling system based on the technical specification of the nuclear power plant is basically the same as the specific embodiment of the exception handling method based on the technical specification of the nuclear power plant, and will not be described herein.

Referring to fig. 12, in some embodiments, the system further includes a rules database for storing abnormal event rules in the set of event rules and an event record database. The event record database is used for storing abnormal trigger events converted according to the triggered target event rules and recording event priority labels, event trigger time and event processing time of the corresponding target event rules.

An operator can export the abnormal triggering events stored in the event record database through a history query module configured by the system, or sort or query the abnormal triggering events according to a certain standard, and display the abnormal triggering events. An abnormal trigger event is an event generated based on a trigger target event rule.

In some embodiments, the operator can display the object trigger event and the corresponding object processing information which have occurred in a certain terminal, so that the relevant operator can conveniently react and view the situation in time.

The embodiment of the application also provides electronic equipment, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor realizes the abnormality processing method based on the technical specification of the nuclear power plant when executing the computer program. The electronic equipment can be any intelligent terminal including a tablet personal computer, a vehicle-mounted computer and the like.

Referring to fig. 13, fig. 13 illustrates a hardware structure of an electronic device according to another embodiment, the electronic device includes:

The processor 1301 may be implemented by a general-purpose CPU (Centra l Process I ng Un it ), a microprocessor, an application-specific integrated circuit (APP L I CAT I on SPEC I F I C I NTEGRATED CI rcu it, AS ic), or one or more integrated circuits, etc. for executing related programs, so AS to implement the technical solution provided by the embodiments of the present application;

The memory 1302 may be implemented in the form of read-only memory (Read On l y Memory, ROM), static storage, dynamic storage, or random access memory (Random Access Memory, RAM). The memory 1302 may store an operating system and other application programs, and when the technical solutions provided in the embodiments of the present disclosure are implemented by software or firmware, relevant program codes are stored in the memory 1302, and the processor 1301 invokes an exception handling method based on the technical specifications of the nuclear power plant to execute the embodiments of the present disclosure;

An input/output interface 1303 for implementing information input and output;

the communication interface 1304 is configured to implement communication interaction between the device and other devices, and may implement communication in a wired manner (e.g. USB, network cable, etc.), or may implement communication in a wireless manner (e.g. mobile network, WI F I, bluetooth, etc.);

a bus 1305 to transfer information between the various components of the device (e.g., the processor 1301, memory 1302, input/output interfaces 1303, and communication interfaces 1304);

wherein the processor 1301, the memory 1302, the input/output interface 1303 and the communication interface 1304 enable a communication connection between each other inside the device via a bus 1305.

The embodiment of the application also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program which is executed by a processor to realize the abnormality processing method based on the technical specification of the nuclear power plant.

The memory, as a non-transitory computer readable storage medium, may be used to store non-transitory software programs as well as non-transitory computer executable programs. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes memory remotely located relative to the processor, the remote memory being connectable to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The embodiment of the application provides an abnormality processing method, an abnormality processing system and a related medium based on a technical specification of a nuclear power plant. The current target operation mode of the nuclear power plant is determined through the real-time operation data, and then the applicable target rule set is matched from a plurality of event rule sets constructed through the content of the technical specification through the system identification information and the target operation mode. And carrying out anomaly identification on the real-time operation data through the target rule group, triggering a corresponding target event rule when the anomaly is found, and obtaining corresponding target processing information according to the target event rule. Therefore, the application constructs a plurality of event rule sets through the content of the technical specification, determines the applicable target rule sets based on the system identification information and the current target operation mode of the nuclear power plant, and then carries out anomaly identification on the fact operation data of the nuclear power plant. When the target event rule is triggered, corresponding target processing information is given. Thereby realizing the efficient utilization of technical specifications.

The embodiments described in the embodiments of the present application are for more clearly describing the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application, and those skilled in the art can know that, with the evolution of technology and the appearance of new application scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

It will be appreciated by persons skilled in the art that the embodiments of the application are not limited by the illustrations, and that more or fewer steps than those shown may be included, or certain steps may be combined, or different steps may be included.

The system embodiments described above are merely illustrative, in that the units illustrated as separate components may or may not be physically separate, i.e., may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

Those of ordinary skill in the art will appreciate that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof.

The terms "first," "second," "third," "fourth," and the like in the description of the application and in the above figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be understood that in the present application, "at least one (item)" means one or more, and "a plurality" means two or more. "and/or" is used to describe an association relationship of an associated object, and indicates that three relationships may exist, for example, "a and/or B" may indicate that only a exists, only B exists, and three cases of a and B exist simultaneously, where a and B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one of a, b or c may represent a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

In the several embodiments provided by the present application, it should be understood that the disclosed systems and methods may be implemented in other ways. For example, the system embodiments described above are merely illustrative, e.g., the division of the above elements is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed. The coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, indirect coupling or communication connection of systems or units, electrical, mechanical, or other form.

The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including multiple instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method of the various embodiments of the present application. The storage medium includes various media capable of storing programs, such as a USB flash disk, a removable hard disk, a Read-only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk.

The preferred embodiments of the present application have been described above with reference to the accompanying drawings, and are not thereby limiting the scope of the claims of the embodiments of the present application. Any modifications, equivalent substitutions and improvements made by those skilled in the art without departing from the scope and spirit of the embodiments of the present application shall fall within the scope of the claims of the embodiments of the present application.

Claims

1. An exception handling method based on a technical specification of a nuclear power plant, the method comprising:

2. The method according to claim 1, wherein before matching the applicable target rule set from the preset plurality of event rule sets according to the system identification information and the target operation mode, the method further comprises constructing the event rule set based on a technical specification, and specifically comprises:

3. The method according to claim 2, wherein said performing rule event parsing based on said specification text data to obtain event rule data comprises:

and integrating all the abnormal event rules to obtain event rule data.

4. The method of claim 1, wherein each triggered target event rule is converted into an abnormal trigger event and stored in an event record database to obtain historical event data, wherein the step of performing abnormal recognition on the real-time operation data based on the target rule set and obtaining target processing information corresponding to the target event rule according to the triggered target event rule comprises the steps of:

5. The method of claim 4, wherein performing association matching in the set of potential association events based on the target trigger event to obtain a plurality of target association events, comprising:

6. The method according to claim 4, wherein before performing association matching in the potential association event group based on the target trigger event to obtain a plurality of target association events, further comprising constructing an event association network, specifically comprising:

7. The method of claim 4, further comprising, after deriving corresponding target processing information based on the target trigger event and the plurality of target association events:

8. The method according to claim 1, wherein the performing anomaly identification on the real-time operation data based on the target rule set, and obtaining target processing information corresponding to the target event rule according to the triggered target event rule, further comprises evaluating the target processing information, specifically includes:

9. The method of claim 8, wherein iterating the target event rule based on the rule feedback information to obtain a target modification rule comprises:

10. The method of claim 1, wherein the determining a target operating mode of the nuclear power plant based on the real-time operating data, the method further comprises, in the event that the nuclear power plant needs to switch operating modes:

11. The method of claim 10, wherein the performing an abnormal association evaluation based on the set of preliminary rules and the triggered target event rule to obtain a mode switch suggestion comprises:

12. An exception handling system based on a technical specification of a nuclear power plant is characterized by comprising a data acquisition module, a rule application range determination module, an operation mode identification module and an exception identification handling module;

13. The system of claim 12, further comprising a rules database and an event record database;

14. An electronic device comprising a memory storing a computer program and a processor implementing the nuclear power plant technical specification-based exception handling method of any one of claims 1 to 11 when the computer program is executed.

15. A computer-readable storage medium storing a computer program, characterized in that the computer program, when executed by a processor, implements the abnormality processing method based on the nuclear power plant specifications according to any one of claims 1 to 11.