Information processing method, device and equipment of nuclear power instrument control system and medium

Through event triggers and listeners, an ordered custom event flow and an asynchronous event processing model are implemented in the nuclear power instrument control system, which solves the problem of insufficient log collection in the prior art and improves the real-time and reliability of the system.

CN119645700APending Publication Date: 2025-03-18CGN DIGITAL TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411693943.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-25
Publication Date
2025-03-18

AI Technical Summary

Technical Problem

The existing nuclear power instrument control system log collection technology has shortcomings in real-time, efficiency and information integration, which affects system performance and resource utilization, and it is difficult to understand the operating status and fault conditions of the system in a timely and comprehensive manner.

Method used

The events generated by the nuclear power instrument control system are monitored through event triggers, problem events are generated, and stored in the message queue through serialization processing. The event listener listens to the serialization information in the message queue, performs deserialization and event parsing processing, and generates log information.

Benefits of technology

It significantly improves the efficiency, real-time and reliability of server log collection of nuclear power instrument control systems, simplifies the difficulty of system information integration, and improves the scalability and maintainability of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119645700A_ABST
    Figure CN119645700A_ABST
Patent Text Reader

Abstract

The invention provides an information processing method, device and equipment for a nuclear power instrument control system and a medium, and the information processing method comprises the steps: monitoring an event generated by the nuclear power instrument control system in an operation process through an event trigger, and generating a corresponding problem event when the event meets a triggering condition; performing serialization processing on the problem event through the event trigger to generate corresponding serialization information; sequentially storing the serialized information in a message queue according to a time sequence through the event trigger; and processing the serialized information in the message queue through an event monitor, and generating corresponding log information. According to the information processing method and device of the nuclear power instrument control system, the equipment and the medium provided by the invention, the log analysis efficiency can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of nuclear power, and in particular to an information processing method, device, equipment and medium for a nuclear power instrumentation and control system. Background Art

[0002] Among existing log collection technologies for nuclear power instrumentation and control systems, the traditional polling method is a common approach. The polling mechanism periodically obtains log data from various log sources and then sends it to the log processing system.

[0003] Traditional log collection technologies have significant shortcomings in terms of real-time performance, efficiency, and information integration. These deficiencies not only impact system performance and resource utilization, but also make log analysis difficult and inaccurate, making it difficult to obtain a timely and comprehensive understanding of system operating status and fault conditions. Therefore, there is room for improvement. Summary of the Invention

[0004] The object of the present invention is to provide an information processing method, device, equipment and medium for a nuclear power instrumentation and control system, which can improve the efficiency of log analysis.

[0005] To solve the above technical problems, the present invention is achieved through the following technical solutions:

[0006] The present invention provides an information processing method for a nuclear power instrumentation and control system, comprising:

[0007] Monitor events generated by the nuclear power instrumentation and control system during operation through event triggers, and generate corresponding problem events when the events meet the trigger conditions;

[0008] Serialize the problem event through the event trigger to generate corresponding serialization information;

[0009] The serialization information is stored in a message queue in chronological order through the event trigger;

[0010] The serialized information in the message queue is processed by the event listener, and corresponding log information is generated.

[0011] In one embodiment of the present invention, the step of monitoring events generated by the nuclear power instrumentation and control system during operation by using an event trigger and generating a corresponding problem event when the event meets a trigger condition includes:

[0012] Monitor nuclear power instrumentation and control systems through event triggers:

[0013] When the event trigger monitors that the operating status of the equipment in the nuclear power instrumentation and control system meets the preset status trigger condition, a corresponding problem event is generated;

[0014] When the event trigger monitors that the operating time of the nuclear power instrumentation and control system meets the preset time trigger condition, a corresponding problem event is generated;

[0015] When the event trigger monitors that various parameters of the nuclear power instrumentation and control system meet corresponding preset parameter trigger conditions, a corresponding problem event is generated.

[0016] In one embodiment of the present invention, the step of serializing the problem event using the event trigger to generate corresponding serialization information includes:

[0017] Serialize the relevant information of the problem event according to a preset serialization format to generate corresponding coded data; wherein the relevant information includes an event identifier, event type, event description, event level, event source, device information, status information, and timestamp;

[0018] All coded data of the problem event are collected to generate serialized data in a preset serialization format.

[0019] In one embodiment of the present invention, the step of processing the serialized information in the message queue through the event listener and generating corresponding log information includes:

[0020] Monitor the serialized information in the message queue through an event listener;

[0021] The event listener performs deserialization and event parsing processing on the monitored serialized information to generate log information in a preset format.

[0022] In one embodiment of the present invention, the step of monitoring the serialization information in the message queue through the event listener includes:

[0023] Register an event listener in the message queue to monitor the corresponding serialized information in the message queue.

[0024] In one embodiment of the present invention, the step of performing deserialization and event parsing processing on the monitored serialized information by the event listener to generate log information in a preset format includes:

[0025] Determine whether the event listener has listened to the serialization information associated with it:

[0026] When corresponding serialization information is monitored, the event listener extracts the corresponding serialization information;

[0027] Otherwise, the event listener continues to listen;

[0028] The extracted serialized information is deserialized and event parsed by the event listener to generate log information in a preset format.

[0029] In one embodiment of the present invention, after the step of processing the serialized information in the message queue through the event listener and generating corresponding log information, the method further includes: storing the log information.

[0030] The present invention also provides an information processing device for a nuclear power instrumentation and control system, comprising:

[0031] An event triggering module is used to monitor events generated by the nuclear power instrumentation and control system during operation, and generate corresponding problem events when the events meet the triggering conditions; the event triggering module is also used to serialize the problem events to generate corresponding serialization information; the event triggering module is also used to store the serialization information in a message queue in chronological order; and

[0032] The event monitoring module is used to process the serialized information in the message queue and generate corresponding log information.

[0033] The present invention also provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the information processing method of the nuclear power instrumentation and control system are implemented.

[0034] The present invention also provides a computer-readable storage medium, which stores a computer program, and is characterized in that when the computer program is executed by a processor, the steps of the information processing method of the nuclear power instrumentation and control system are implemented.

[0035] As described above, the present invention provides an information processing method, device, equipment and medium for a nuclear power instrumentation and control system. Through an ordered custom event stream, an asynchronous event processing model and a flexible event monitoring mechanism, the present invention significantly improves the efficiency, real-timeness and reliability of log collection of the nuclear power instrumentation and control system server, while simplifying the difficulty of information integration of the system and improving the scalability and maintainability of the system.

[0036] Of course, any product implementing the present invention does not necessarily need to achieve all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0038] Figure 1 This is a flow chart of an information processing method for a nuclear power instrumentation and control system according to an embodiment of the present invention;

[0039] Figure 2 Schematic diagram of an information processing device for a nuclear power instrumentation and control system according to an embodiment of the present invention;

[0040] Figure 3 FIG. 1 is a schematic diagram of an electronic device according to an embodiment of the present invention.

[0041] In the figure: 100, event triggering module; 200, event monitoring module; 1, electronic device; 12, memory; 13, processor. DETAILED DESCRIPTION

[0042] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present invention.

[0043] See also Figure 1 The present invention provides an information processing method for a nuclear power instrumentation and control system, which can be used to collect and process various events and log information generated during the operation of the nuclear power instrumentation and control system. The information processing method may include the following steps:

[0044] Step S10: Monitor events generated by the nuclear power instrumentation and control system during operation through event triggers, and generate corresponding problem events when the events meet the trigger conditions;

[0045] Step S20: Serialize the problem event through the event trigger to generate corresponding serialization information;

[0046] Step S30: storing the serialized information in a message queue in chronological order through an event trigger;

[0047] Step S40: Process the serialized information in the message queue through the event listener and generate corresponding log information.

[0048] Step S50: Store the log information.

[0049] In one embodiment, when step S10 is executed, specifically, step S10 may include the following steps:

[0050] Step S11: Monitor the nuclear power instrumentation and control system through event triggers:

[0051] Step S12: When the event trigger monitors that the operating status of the equipment in the nuclear power instrumentation and control system meets the preset status trigger condition, a corresponding problem event is generated;

[0052] Step S13: When the event trigger monitors that the operating time of the nuclear power instrumentation and control system meets the preset time trigger condition, a corresponding problem event is generated;

[0053] Step S14: When the event trigger monitors that various parameters of the nuclear power instrumentation and control system meet corresponding preset parameter trigger conditions, a corresponding problem event is generated.

[0054] In one embodiment, when executing step S11, event triggers may be designed and configured based on specific monitoring requirements. These event triggers are triggered when specific trigger conditions are met, thereby monitoring the operating status of the nuclear power instrumentation and control system. When certain trigger conditions are met, the corresponding event trigger triggers corresponding actions or notifications.

[0055] In one embodiment, for example, in a nuclear power instrumentation and control system, monitoring requirements may include equipment status monitoring, system performance monitoring, fault detection, and operational behavior monitoring. Equipment status monitoring refers to monitoring the operating status of equipment, such as temperature, pressure, and vibration. System performance monitoring refers to monitoring system performance indicators, such as CPU utilization and memory usage. Fault detection refers to detecting faults or anomalies in the system, such as sensor failure and communication interruption. Operational behavior monitoring refers to monitoring operator behavior to ensure compliance with specifications.

[0056] In one embodiment, when executing step S12, the change in the internal state of the nuclear power instrumentation and control system specifically refers to a change in the state of a component or device in the nuclear power instrumentation and control system. For example, the device may change from a normal operating state to a faulty state. Another example is the value of a key parameter (such as temperature, pressure, current, etc.) exceeding a preset safety range.

[0057] In one embodiment, a status monitoring point can be pre-set within the nuclear power instrumentation and control system to regularly check the equipment status or parameter values. When a status change is detected, it indicates that a trigger condition has been met and a corresponding problem event is generated.

[0058] In one embodiment, when executing step S13, a scheduled task is specifically a task that is automatically executed at a specific time or at a predetermined interval. For example, a comprehensive inspection of a nuclear power plant's instrumentation and control system may be performed every morning, or performance data from the nuclear power plant's instrumentation and control system may be collected hourly to ensure that all equipment and parameters are within normal ranges. In this case, when the event trigger reaches the preset time, the trigger condition is met and a corresponding problem event is generated.

[0059] In one embodiment, when executing step S14, sensor data monitoring specifically refers to real-time or on-demand monitoring of data collected by sensors deployed in the nuclear power instrumentation and control system. When the data from a particular sensor changes and reaches a preset threshold, a corresponding problem event is triggered. For example, real-time monitoring of temperature sensor data can trigger an alarm if the temperature exceeds a preset value.

[0060] In one embodiment, real-time data is acquired from sensors using a hardware interface or network protocol (e.g., MODBUS, TCP / IP, etc.). The collected data is then processed and analyzed, and a determination is made based on a preset threshold whether the data meets a trigger condition. If the trigger condition is met, an event trigger can generate a corresponding problem event.

[0061] In one embodiment, trigger conditions can be flexibly configured based on actual needs, and multiple conditions can be combined to implement more complex monitoring logic. Through these mechanisms, abnormal conditions in nuclear power instrumentation and control systems can be discovered and handled in a timely manner, ensuring the safe and stable operation of nuclear power instrumentation and control systems.

[0062] In one embodiment, when executing step S20, specifically, step S20 may include the following steps:

[0063] Step S21: Serialize the relevant information of the problem event according to a preset serialization format to generate corresponding coded data; wherein the relevant information includes an event identifier, event type, event description, event level, event source, device information, status information, and timestamp;

[0064] Step S22: All coded data of the problem event are collected to generate serialized data in a preset serialization format.

[0065] In one embodiment, when executing step S21, the relevant information of the problem event may include, specifically, an event identifier, event type, event description, event level, event source, device information, status information, timestamp, etc. The event identifier (ID) refers to a string or number that uniquely identifies an event and is used to distinguish different events. The event type describes the specific type of event, such as "device failure," "parameter out of range," or "system restart." The event description provides a detailed description of the event, facilitating subsequent analysis and processing. The event level indicates the importance of the event and may include "normal information," "warning," or "error." The event source refers to the source of the event, i.e., the component or module where the event occurred, such as "main control system," "sensor module," etc. Device information refers to the specific device information involved, such as the device ID, name, and location. Status information refers to changes in the device or system status, such as a change from "normal" to "faulty." The timestamp refers to the time when the event occurred and is typically a date and time string accurate to seconds or milliseconds.

[0066] In one embodiment, serialization refers to converting information related to a problem event into a standard, storable format, such as XML or JSON. XML is a structured, tokenized data format widely used for data exchange and storage. JSON is a lightweight, easy-to-read and parse data format widely used for data exchange in web applications and APIs.

[0067] In one embodiment, when serializing relevant information about a problem event, relevant information about the problem event can be collected first, for example, by obtaining relevant information about the problem event from the system, such as the event ID, event type, and event description. A timestamp and source information can then be added to record the timestamp and source information of the problem event. The problem event can then be serialized to convert the collected event information into a preset serialization format. Finally, corresponding encoded data can be generated, and the serialized data can be converted into standard encoded data for storage and transmission.

[0068] In one embodiment, through the above steps, the relevant information of the problem event can be serialized and the corresponding encoded data can be generated. The choice of serialization format (such as JSON or XML) can be determined based on specific needs and system compatibility. The serialized data can be easily stored, transmitted, and parsed, ensuring that the event information can be effectively managed and utilized.

[0069] In one embodiment, when step S22 is executed, specifically, each problem event can generate corresponding coded data after serialization processing. Since the relevant information of the problem event includes a variety of contents, different coded data can be generated for different relevant information. At this time, all coded data of the same problem event can be summarized into a data structure, such as a list, array, etc. This ensures that the information of the same problem event is concentrated together, which is convenient for subsequent processing. Finally, according to the requirements and specifications of the system, a specific serialization format (such as JSON, XML, etc.) can be selected to represent the event information in the collection.

[0070] In one embodiment, when executing step S30, specifically, the message queue is a middleware used to transmit messages between different components, which can ensure the reliability and sequence of messages. In this embodiment, the event listener can publish the generated serialized data to the message queue through the event publishing mechanism for storage. The message queue is used to store and transmit serialized event information, and stores it in chronological order.

[0071] In one embodiment, when step S40 is executed, specifically, step S40 may include the following steps:

[0072] Step S41: Monitor serialization information in the message queue through the event listener;

[0073] Step S42: Deserialize and parse the monitored serialized information through the event listener to generate log information in a preset format.

[0074] In one embodiment, when step S41 is executed, specifically, an event listener is registered with a message queue to monitor the corresponding serialized information in the message queue. An event listener can be a component in a nuclear power instrumentation and control system that is specifically used to monitor and process specific types of events. Based on monitoring requirements, the nuclear power instrumentation and control system can create multiple event listeners, each responsible for monitoring different types of problem events. For example, an equipment failure listener can be used to monitor equipment failure events. A parameter out-of-range listener can be used to monitor events in which parameters exceed a preset range. A security event listener can be used to monitor security-related events, such as illegal logins and data leaks.

[0075] In one embodiment, the registration and subscription process of the event listener can be adjusted at any time without restarting or redeploying the nuclear power instrumentation and control system. The nuclear power instrumentation and control system administrator can manage the listener through configuration files, management interfaces, API interfaces, etc. For example. Managing event listeners through configuration files means storing the configuration information of the event listener in the configuration file, and the nuclear power instrumentation and control system administrator can add, remove or adjust the event listener by editing the configuration file. For another example, managing event listeners through the management interface means providing a graphical management interface, and the nuclear power instrumentation and control system administrator can manage and configure the event listener through interface operations. For another example, managing event listeners through the API interface means providing a REST API or command line tool, and the nuclear power instrumentation and control system administrator can manage and configure the event listener through the API interface.

[0076] In one embodiment, different types of event listeners can be configured with different processing logic to ensure that specific types of events are properly handled. Processing logic refers to the series of operations or steps that an event listener performs after receiving serialized information from a message queue. This design allows nuclear power I&C systems to handle various types of events more flexibly, efficiently, and reliably, ensuring timely response and resolution of issues, and improving the overall performance and stability of the nuclear power I&C system.

[0077] In one embodiment, an event channel is a specific channel or queue within a message queue that stores and transmits serialized event information. Event triggers in a nuclear power instrumentation and control system can publish serialized information through the event channel, ensuring that this information is delivered to registered event listeners in a timely manner.

[0078] In one embodiment, the registration process of an event listener refers to adding the event listener to the subscription list of a message queue so that it can receive serialized information associated with it. The registration steps may include adding monitoring information, subscribing to an event channel, etc. Adding monitoring information refers to adding the monitoring type and processing logic configuration information of the event listener to the subscription list of the message queue. Subscribing to an event channel refers to the event listener subscribing to the event channel and waiting to receive event information of a specific type. After registering with the message queue, the event listener will continuously monitor the event channel for new serialized information.

[0079] In one embodiment, since multiple events may occur in a nuclear power I&C system, each event generates a serialized message and publishes it to an event channel. Message queues typically ensure message order, so event listeners process serialized messages sequentially in the order in which the events are published. A nuclear power I&C system can be configured with multiple event listeners, each independently listening for and processing its associated serialized messages. This improves the processing capacity and concurrency of the nuclear power I&C system.

[0080] In one embodiment, when step S42 is executed, specifically, step S42 may include the following steps:

[0081] Step S421: Determine whether the event listener has listened to the serialization information associated with it:

[0082] Step S422: When the corresponding serialization information is monitored, the event listener extracts the corresponding serialization information;

[0083] Step S423: Otherwise, the event listener continues to listen;

[0084] Step S424: Deserialize and parse the extracted serialized information through the event listener to generate log information in a preset format.

[0085] In one embodiment, when executing steps S421, S422, and S423, specifically, after registering with the message queue, the event listener continuously checks whether there is new serialization information in the event channel. The event listener continuously monitors the event channel until it receives serialization information associated with it.

[0086] In one embodiment, the associated serialization information refers to the serialization information that matches the event type pre-configured by the event listener. The event listener needs to determine whether the information received from the event channel is the type it needs to process. First, when the event listener takes out a new serialization information from the event channel, it first checks the event type of the information. Then, it can be determined whether it matches. If the event type matches the event type configured by the event listener, it means that the event listener has listened to the serialization information associated with it. If the event type does not match, the event listener will ignore the information, continue to listen to the event channel, and wait for the next new serialization information. This process continues until the event listener receives matching serialization information.

[0087] In one embodiment, when executing step S424, specifically, deserialization refers to converting serialized information (such as a string, JSON, XML, etc.) back into an object that the program can understand and process. Serialized information is usually transmitted or stored over a network, and in order to be able to process it, it needs to be restored to its original structured data.

[0088] In one embodiment, event parsing refers to parsing the deserialized event data to extract key information for subsequent processing logic. The parsing process may include extracting event ID, event type, timestamp, device information, etc.

[0089] In one embodiment, generating log information in a preset format means converting the parsed event data into log information according to a predefined format (such as log4j, log4net, etc.) and outputting or storing the log information. Log information is generally used to record the details of the event to facilitate subsequent analysis and auditing.

[0090] In one embodiment, after the event listener receives a new serialized information from the event channel of the message queue, it can select a suitable deserialization method to convert it back to the original event data object based on the format of the serialized information (such as JSON, XML, etc.). For example, if the serialized information is in JSON format, the listener will use the JSON deserialization method to convert it into an object. The deserialized event data object contains various field information, such as event ID, event type, event description, timestamp, device information, etc. The event listener parses these fields and extracts key information for subsequent processing. The event listener can convert the extracted key information into log information based on a predefined log format (such as log4j, log4net, etc.). For example, the generated log information may include fields such as event ID, event type, event description, timestamp, device information, etc., and be arranged and output according to a specific format.

[0091] In one embodiment, when executing step S50, specifically, the database is a system for storing and managing data. To ensure persistent storage and traceability of event information, the event listener can connect to the database. The connection process may include steps such as database configuration, connection establishment, and log information generation. Database configuration refers to pre-configuring database connection information, such as the database address, port, username, password, etc. Establishing a connection refers to the event listener establishing a connection with the database when it starts or processes an event. Generating log information refers to generating log information from the parsed event information according to a standardized log format. After the event is converted into traceable and queryable log information, it can be stored in the database. Traceable and queryable means that the log information can be easily searched and traced back in the database. Traceable means that the log information contains detailed timestamps and event descriptions, making it easy to trace back to the event situation at a specific point in time. Queryable means that specific types of log information can be quickly queried using a database query language (such as SQL), for example, to find all device failure events or events within a specific time range.

[0092] It can be seen that in the above scheme, through the orderly custom event flow, asynchronous event processing model and flexible event monitoring mechanism, the efficiency, real-time and reliability of nuclear power instrumentation and control system server log collection are significantly improved, while the difficulty of information integration of the system is simplified and the scalability and maintainability of the system are improved.

[0093] Specifically, traditional log collection methods require significant resource consumption through periodic scanning and polling, even when only a small number of events occur in the system. The present invention utilizes an asynchronous message queue mechanism to avoid periodic scanning of the entire system, significantly reducing resource waste. In this invention, through an asynchronous event processing model, event publishers can immediately continue executing other operations after publishing an event, without having to wait for the event to be processed, thereby improving resource utilization efficiency. This system is better able to handle large-scale, highly concurrent data scenarios, ensuring efficient operation.

[0094] Furthermore, the periodic scanning and polling of traditional log collection methods can result in delayed collection of events and log information, making them unsuitable for applications requiring high real-time performance. This present invention, through message queue technology, implements asynchronous event publishing and subscription, ensuring the orderly delivery of event streams and significantly improving the system's real-time performance. The system can rapidly respond to and capture immediate changes in system status, ensuring that critical events are recorded and processed immediately, thus improving the system's responsiveness and troubleshooting capabilities.

[0095] Furthermore, by utilizing message queues and other technical means as event channels, the present invention ensures the orderliness of events in the event stream, improving the efficient collection and processing capabilities of multi-source, heterogeneous events. This enables the system to more reliably handle complex event environments. The system includes a database that converts event information collected from the event stream into formatted logs and saves them to the database. Persistent storage ensures the long-term retention and traceability of log information in the system, providing reliable data support.

[0096] Furthermore, in traditional log collection methods, direct scanning and polling can lead to tight coupling between various parts of the system, affecting the system's flexibility and maintainability. The present invention introduces message queues to decouple event publishers and subscribers, enabling efficient communication between various system modules through message queues, reducing inter-module dependencies. Through an orderly event stream and a flexible event monitoring mechanism, the present invention simplifies the difficulty of information integration and improves the system's scalability and maintainability. Users can customize monitoring and response logic according to specific needs, further enhancing the system's flexibility.

[0097] It should be understood that the order of execution of the steps in the above embodiments does not necessarily mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0098] See also Figure 2 The present invention also provides an information processing device for a nuclear power instrumentation and control system, which can be applied to the above-mentioned information processing method. The information processing device can include an event triggering module 100 and an event monitoring module 200.

[0099] In one embodiment, the event trigger module 100 may be used to monitor events generated during the operation of the nuclear power instrumentation and control system, and generate corresponding problem events when an event meets a trigger condition.

[0100] In one embodiment, the event triggering module 100 may also be used to perform serialization processing on the problem event and generate corresponding serialization information.

[0101] In one embodiment, the event triggering module 100 is further configured to store the serialization information in the message queue in chronological order.

[0102] In one embodiment, the event monitoring module 200 may be used to process serialized information in the message queue and generate corresponding log information.

[0103] In one embodiment, the event monitoring module 200 may also be used to store log information.

[0104] See also Figure 3 In one embodiment, the electronic device 1 may include a memory 12, a processor 13 and a bus, and may also include a computer program stored in the memory 12 and executable on the processor 13, such as an information processing program.

[0105] In one embodiment, the memory 12 includes at least one type of readable storage medium, and the readable storage medium includes a flash memory, a mobile hard disk, a multimedia card, a card-type memory (for example, an SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 12 can be an internal storage unit of the electronic device 1, such as a mobile hard disk of the electronic device 1. In other embodiments, the memory 12 can also be an external storage device of the electronic device 1, such as a plug-in mobile hard disk, a smart memory card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 1. Furthermore, the memory 12 can also include both an internal storage unit of the electronic device 1 and an external storage device. The memory 12 can not only be used to store application software and various types of data installed in the electronic device 1, such as information processing codes, etc., but can also be used to temporarily store data that has been output or is to be output.

[0106] In one embodiment, the processor 13 may be comprised of an integrated circuit, such as a single packaged integrated circuit or multiple packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and combinations of various control chips. The processor 13 is the control core (Control Unit) of the electronic device 1, connecting the various components of the entire electronic device 1 using various interfaces and circuits. It executes or runs programs or modules stored in the memory 12 and accesses data stored in the memory 12 to perform various functions of the electronic device 1 and process data.

[0107] In one embodiment, the processor 13 executes the operating system and various installed application programs of the electronic device 1. The processor 13 executes the application programs to implement the steps in the above-mentioned information processing method.

[0108] In one embodiment, the computer program may be divided into one or more modules, one or more of which are stored in the memory 12 and executed by the processor 13 to complete the present application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device 1.

[0109] The embodiments of the present invention disclosed above are intended only to illustrate the present invention. They do not describe all details in detail, nor do they limit the present invention to the specific embodiments described. Obviously, many modifications and variations are possible based on the content of this specification. These embodiments are selected and described in detail in this specification to better explain the principles and practical applications of the present invention, thereby enabling those skilled in the art to better understand and utilize the present invention. The present invention is limited only by the claims and their full scope and equivalents.

Claims

1. An information processing method for a nuclear power instrumentation and control system, characterized in that: include: Monitoring the events generated by the nuclear power instrumentation and control system during operation through event triggers, and generating corresponding problem events when the events meet the triggering conditions; Performing serialization processing on the problem event through the event trigger to generate corresponding serialization information; The serialization information is stored in a message queue in chronological order through the event trigger; The serialized information in the message queue is processed through the event listener, and corresponding log information is generated.

2. The information processing method of the nuclear power instrumentation and control system according to claim 1, characterized in that: The step of monitoring the events generated by the nuclear power instrumentation and control system during operation by means of event triggers, and generating corresponding problem events when the events meet the triggering conditions, comprises: Monitor the nuclear power instrumentation and control system through event triggers: When the event trigger monitors that the operating status of the equipment in the nuclear power instrumentation and control system meets the preset status trigger condition, a corresponding problem event is generated; When the event trigger monitors that the operation time of the nuclear power instrumentation and control system meets the preset time trigger condition, a corresponding problem event is generated; When the event trigger monitors that various parameters of the nuclear power instrumentation and control system meet corresponding preset parameter trigger conditions, a corresponding problem event is generated.

3. The information processing method of a nuclear power instrumentation and control system according to claim 1, characterized in that: The step of serializing the problem event through the event trigger to generate corresponding serialization information includes: Serialize the relevant information of the problem event according to a preset serialization format to generate corresponding coded data; wherein the relevant information includes an event identifier, event type, event description, event level, event source, device information, status information, and timestamp; All the coded data of the problem event are collected to generate serialized data in a preset serialization format.

4. The information processing method of a nuclear power instrumentation and control system according to claim 1, characterized in that: The step of processing the serialized information in the message queue through the event listener and generating corresponding log information includes: Monitor the serialization information in the message queue through an event listener; The event listener performs deserialization and event parsing processing on the monitored serialized information to generate log information in a preset format.

5. The information processing method of the nuclear power instrumentation and control system according to claim 4, characterized in that: The step of monitoring the serialization information in the message queue through the event listener comprises: Register an event listener in a message queue to monitor the corresponding serialized information in the message queue.

6. The information processing method of a nuclear power instrumentation and control system according to claim 4, characterized in that: The step of deserializing and parsing the monitored serialized information through the event listener to generate log information in a preset format includes: Determine whether the event listener has listened to the serialization information associated with it: When the corresponding serialization information is monitored, the event listener extracts the corresponding serialization information; Otherwise, the event listener continues to listen; The extracted serialized information is deserialized and event parsed by the event listener to generate log information in a preset format.

7. The information processing method of a nuclear power instrumentation and control system according to claim 1, characterized in that: After the step of processing the serialized information in the message queue through the event listener and generating corresponding log information, the method further includes: storing the log information.

8. An information processing device for a nuclear power instrumentation and control system, characterized in that: include: An event trigger module is used to monitor the events generated by the nuclear power instrumentation and control system during operation, and generate corresponding problem events when the events meet the triggering conditions; the event trigger module is also used to serialize the problem events and generate corresponding serialization information; the event trigger module is also used to store the serialization information in a message queue in chronological order; as well as The event monitoring module is used to process the serialized information in the message queue and generate corresponding log information.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the information processing method of the nuclear power instrumentation and control system as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the information processing method of a nuclear power instrumentation and control system as described in any one of claims 1 to 7 are implemented.