Nuclear power simulation machine data management and application system and method based on six-layer architecture

Abstract

The present disclosure belongs to the technical field of nuclear power and particularly relates to a nuclear power simulator data management and application system and method based on a six-layer architecture. The nuclear power simulator intelligent training and examination system based on the six-layer architecture provided by the present disclosure realizes the full-link standardization, safety and structuring of nuclear power simulator training and examination data collection-storage-management-control-use through the clear layering, fixed connection, bidirectional interaction and safety throughout of the six-layer architecture, any new application can be used by only being connected to the system of the present disclosure, and the development efficiency is greatly improved. Thus, the data islands are broken through, so that the data of all simulators is unified and interconnected, and samples can be centrally analyzed and generated. The bidirectional control effectively guarantees the data safety, not only the data can be safely acquired, but also the instructions can be safely and reliably issued, the whole process is encrypted and audited, and the high safety level requirement of the nuclear power industrial control system is met.

Description

Technical Field

[0001] This invention belongs to the field of nuclear power technology, specifically relating to a nuclear power simulator data management and application system and method based on a six-layer architecture. Background Technology

[0002] Nuclear power full-range simulators serve as core equipment for nuclear power plant operator qualification training, certification examinations, and emergency response drills, completely replicating the nuclear power plant's technological processes, control systems, and main control room interface and layout. However, due to differences in the reference unit reactor type, DCS vendor, and simulator development vendor's simulation platform, DCS simulation methods, and underlying operating systems, different simulators exhibit significant differences in data communication and data structure, posing considerable challenges to standardized simulator training and assessment. Currently, the following technical deficiencies are commonly found in the application development process related to nuclear power simulator training and assessment: 1. Difficulty in data acquisition: The various DCS and simulation platforms involved in each simulator are diverse, with different operating systems and many using proprietary data interfaces, making it difficult to acquire high-frequency and large-volume data. Data quality and real-time performance cannot be guaranteed, and the impact on simulator performance cannot be assessed.

[0003] 2. Low level of data structuring: The mapping relationship between business semantics and underlying variables within each DCS platform is vague, and there are differences in business semantics between different platforms. Upper-layer applications cannot directly interact with the simulator based on business semantics.

[0004] 3. High coupling in the data link: The lack of a unified data bus and coordination mechanism in data acquisition, processing, and service makes it difficult to build a complete end-to-end data link. The modules are tightly coupled, requiring extensive repetitive development when adding new platforms, data types, or applications, and is not compatible with different application development languages, resulting in poor scalability.

[0005] 4. Single data flow direction: Existing solutions focus on data uplink and lack an efficient two-way interaction mechanism, making it difficult to reliably and timely issue control commands to the simulator.

[0006] 5. Weak network security protection: The existing system lacks a unified security control layer, the identity authentication method is simple (mostly passwords), the access control is crude, the data transmission is mostly in plaintext, the operation logs are scattered and not linked to audit, making it difficult to prevent internal unauthorized access, data theft and tampering risks, which does not meet the high security level protection requirements of nuclear power industrial control systems. Summary of the Invention

[0007] To overcome the problems existing in related technologies, a nuclear power simulator data management and application system and method based on a six-layer architecture is provided. According to one aspect of the embodiments of this disclosure, a nuclear power simulator data management and application system based on a six-layer architecture is provided, the system comprising: The edge access layer is deployed on the application side and is used to interact with the underlying heterogeneous system of the application side, collect real-time running data and issue control commands. The data structuring layer is used to convert the real-time running data collected by the terminal access layer into structured data with unified semantics, and to establish a mapping relationship between business information and the scripts of the underlying heterogeneous system. Interface encapsulation layer, used to provide standardized application programming interfaces or software development kits; The data service layer is used to receive data requests or control instructions composed of business semantics initiated by the upper layer application based on the standardized application programming interface of the interface encapsulation layer, and translate the received data requests or control instructions into scripts that can be executed by the underlying heterogeneous system, and execute them through the terminal access layer. The data application layer is used to develop and run training and assessment applications for nuclear power simulators by calling the standardized application programming interface of the interface encapsulation layer. The development includes defining the timing and logical relationships of instruction issuance, data reading and log acquisition. The network security layer is used to perform independent authentication and access control for each data request or control command in cross-layer interactions.

[0008] In one possible implementation, the end-side access layer adopts a master-slave distributed architecture. The master node of the end-side access layer is deployed on the simulation server, and the multiple slave nodes of the end-side access layer are deployed on multiple computing nodes of the distributed control system. The master node is responsible for aggregating the data collected by each slave node, and each slave node is used to obtain the data collected by the corresponding acquisition node of the distributed control system.

[0009] In one possible implementation, the network security layer is deployed between the interface encapsulation layer and the data application layer, serving as a unified security gateway for all cross-layer interactions; the security control also includes: data transmission encryption, operation auditing and tracing, abnormal behavior monitoring, and security policy management.

[0010] In one possible implementation, the data service layer also provides a self-detection execution interface; after a control command is issued, the data service layer obtains and returns the execution result of the control command through the self-detection execution interface.

[0011] In one possible implementation, the data service layer also provides a heap-type synonym query interface; the data application layer, based on the heap-type synonym query interface, realizes scene semantic conversion between different DCS platforms under the same heap type.

[0012] In one possible implementation, the data structuring layer is also used to formulate and execute permissions for data updates, automated synchronization strategies, and self-verification of updated data.

[0013] According to another aspect of the embodiments of this disclosure, a method for data management and application of a nuclear power simulator based on a six-layer architecture is provided. The method applies the aforementioned system and includes: The system interacts with the underlying heterogeneous system of multiple simulators through the terminal access layer to collect the real-time operating data of the simulators and issue control commands. The data structuring layer converts the real-time running data collected by the terminal access layer into structured data with unified semantics, and establishes a mapping relationship between business information and the scripts of the underlying heterogeneous system. The interface encapsulation layer provides standardized application programming interfaces or software development kits to the data application layer to shield the differences between the underlying heterogeneous systems. The data service layer receives data requests or control instructions, which are composed of business semantics, initiated by the data application layer based on the standardized interface, and translates the data requests or control instructions into scripts that the underlying heterogeneous system can execute, and outputs them to the terminal access layer for execution. Each data request or control command initiated by the data application layer is subject to independent security control through a network security layer, which includes identity authentication and access control. The data application layer develops and runs the training and assessment application for the simulator by calling the standardized interface. The development includes defining the timing and logical relationships of instruction issuance, data reading and log acquisition.

[0014] According to another aspect of the present disclosure, a non-volatile computer-readable storage medium is provided, on which computer program instructions are stored, which, when executed by a processor, implement the above-described method.

[0015] The beneficial effects of this disclosure are as follows: The nuclear power simulator data management and application system based on a six-layer architecture provided by this disclosure achieves standardization, security, and structuring of the entire data acquisition, storage, management, control, and application chain for nuclear power simulator training and assessment through clear layering, fixed connections, bidirectional interaction, and secure continuity of the six-layer architecture. Any new application can be used simply by connecting to the system disclosed herein, greatly improving development efficiency. This breaks down data silos, enabling unified and interoperable data from all simulators, allowing for centralized analysis and sample generation. The use of bidirectional control effectively ensures data security, ensuring not only secure data acquisition but also secure and reliable command issuance, with end-to-end encryption and auditing, meeting the high security requirements of nuclear power industrial control systems. Furthermore, the system disclosed herein has stronger robustness; because the six layers are independent of each other, upgrading or replacing any layer will not affect other layers, resulting in extremely high scalability. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of a nuclear power simulator data management and application system based on a six-layer architecture, as shown in an embodiment of this disclosure.

[0017] Figure 2 This is a logical diagram illustrating the system's execution of scene editing and scene transitions in an application example.

[0018] Figure 3 This is a schematic diagram illustrating the data configuration, synchronization, and operation and maintenance process of a system in an application example. Detailed Implementation

[0019] The present disclosure will now be described in further detail with reference to the accompanying drawings and specific embodiments.

[0020] Unless otherwise defined, the technical and scientific terms used in this disclosure have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains; the terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of this disclosure; the term "comprising" and any variations thereof in this disclosure are intended to cover non-exclusive inclusion. Clearly, the embodiments described in this disclosure are only a part of the embodiments of this disclosure, and not all of them. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0021] In this disclosure, the reference to "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this disclosure. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0022] Figure 1 This is a schematic diagram of a nuclear power simulator data management and application system based on a six-layer architecture, as shown in an embodiment of this disclosure. Figure 1 As shown, the system includes: The edge access layer is deployed on the simulation server of at least one simulator and the computing node of the distributed control system (DCS). It is used to interact with the underlying heterogeneous system, collect real-time operating data, and issue control commands.

[0023] As an example of this embodiment, the edge access layer is deployed on multiple heterogeneous simulators, simulation servers, and DCS computing nodes. The edge access layer interacts directly with various heterogeneous DCS systems and simulation platforms at the underlying level through API calls, OPC communication, shared memory, and other means to achieve real-time data acquisition, control command issuance, and log scanning.

[0024] In one possible implementation, the end-side access layer can adopt a master-slave architecture. The master node of the end-side access layer is set on the simulation server, and there are multiple slave nodes in the end-side access layer. The master node is responsible for communicating with each slave node to aggregate the data collected by each slave node. Each slave node then communicates with its corresponding DCS acquisition node to obtain the data collected by the acquisition node of the corresponding distributed control system. This distributes the pressure of a large amount of high-frequency data acquisition to multiple servers (e.g., 20) within the simulator, and aggregates the data through the simulation server. To address the problem that traditional centralized data acquisition has a large impact on simulator performance and the impact cannot be assessed, the "master-slave" distributed acquisition architecture is introduced, which effectively reduces the impact on simulator performance.

[0025] The data structuring layer is used to convert the real-time running data collected by the terminal access layer into structured data with unified semantics, and to establish a mapping relationship between business information and the scripts of the underlying heterogeneous system.

[0026] As an example of this embodiment, the data structuring layer transforms various controls, configurations, and database data of the DCS, realizes the mapping between business information and the underlying scripts of the simulator, and unifies the semantics of different DCS of the same stack type, realizing the storage and sample creation of unit and simulator operation data and operation logs.

[0027] In one possible implementation, the data structuring layer is also used to formulate and execute data update permissions and automated synchronization strategies for continuous data maintenance. Addressing the lack of effective collaborative maintenance mechanisms for traditional static configuration data and operational data, access control, automatic synchronization, and verification functions are integrated into the data structuring layer. Through independent configuration, synchronization, and verification processes, the consistency, accuracy, and timeliness of static configuration data and dynamic operational data across layers are ensured, providing a reliable data foundation for data-driven applications.

[0028] An interface encapsulation layer is used to provide standardized application programming interfaces or software development kits to shield the differences between the underlying heterogeneous systems.

[0029] As an example of this embodiment, the interface encapsulation layer acts as a bridge between the access layer on the connecting end and the data structuring layer. It can shield the heterogeneity of the underlying platform and provide standardized interfaces for upper layers to call. The interface encapsulation layer can encapsulate rich API function libraries and SDKs, support multiple high-level languages ​​such as C, C++, and JAVA, and perform containerized encapsulation.

[0030] The data service layer is used to receive data requests or control instructions composed of business semantics initiated by upper-layer applications based on the standardized application programming interface of the interface encapsulation layer, and translate the received data requests or control instructions into scripts that can be executed by the underlying heterogeneous system, and execute them through the terminal access layer.

[0031] As an example of this embodiment, the data service layer can respond to various data requests and control commands from upper-layer applications, and provide interactive interfaces based on business semantics so that the application layer only needs to focus on specific business semantics.

[0032] In one possible implementation, the data service layer also provides a self-detection execution interface for instruction execution. After a control instruction is issued, the data service layer obtains and returns the execution result of the control instruction through the self-detection execution interface. Addressing the lack of efficient two-way interaction and poor reliability of control instruction feedback in related technologies, this disclosure confirms the execution status of the instruction through a self-detection mechanism, ensuring closed-loop feedback in the control instruction issuance process, and improving the reliability of instruction execution and the determinism of application-side business logic such as simulators.

[0033] In one possible implementation, the data service layer also provides a registration group interface. The data application layer sends target parameters (the target parameters are the parameters of the device to be monitored) to the data service layer. The data service layer calls the registration group interface, determines the related parameters associated with the target parameters and the calculation relationship between the target parameters and the related parameters according to a preset query configuration form. Then, the data service layer sends the target parameters to the application end to trigger the application end to start monitoring whether the value of the target parameters has changed. When the application end detects a change in the value of the target parameters, it pushes a change event to the data service layer. The data service layer determines the related parameters based on the current value of the changed target parameters and the associated calculation relationship, and sends the target parameters and related parameters to the data application layer, so that the data application layer updates the corresponding target parameters and related parameters.

[0034] The registration group mechanism enables the edge acquisition layer and data service layer to push data only when the variable changes, and can automatically call the corresponding calculation relationship script to ensure that the changed target parameter and a series of parameters related to the target parameter are updated, without having to repeatedly transmit the current value of the target parameter, which significantly reduces the communication load between layers.

[0035] In one possible implementation, the data service layer also provides a heap-based synonym query interface, which allows applications to switch between different DCS scenarios. It provides data synchronization and query interfaces to ensure data consistency across all levels. Through synonym queries and semantic conversion, it enables rapid reuse of the same training and assessment scenario across different DCS platforms, significantly reducing the workload of developing repetitive scenarios for different DCS platforms.

[0036] The data application layer is used to develop and run training and assessment applications for nuclear power simulators by calling the standardized application programming interface of the interface encapsulation layer. The development includes defining the timing and logical relationships of instruction issuance, data reading and log acquisition.

[0037] As an example of this embodiment, the data application layer includes various intelligent training and assessment applications (behavioral analysis, automatic scoring, scenario verification, training management, etc.). The data application layer supports scenario editing functions, used to define the timing and logical relationships of various command issuances, real-time value readings, and log acquisitions, upon which various applications call data. The data application layer scenario conversion module supports semantic conversion between various DCS systems.

[0038] The network security layer is used to perform independent authentication and access control for each data request or control command in cross-layer interactions.

[0039] For example, the network security layer can be deployed between the data encapsulation layer and the data application layer, serving as a security gateway for all cross-layer interactions. The network security layer can independently implement functions such as unified identity authentication, fine-grained access control, auditing and tracing of encrypted data transmission operations, abnormal behavior monitoring, and security policy management.

[0040] To address the security shortcomings of existing systems, such as single-source authentication, plaintext transmission, and fragmented logs without associated auditing, this disclosure establishes an independent network security layer and endows it with more comprehensive security functions. Through a separately deployed security gateway, unified management of authentication, access control, encrypted transmission, operation auditing, and anomaly monitoring is achieved, meeting the compliance requirements of nuclear power plant control systems for "defense in depth and security zoning" in high-security protection, and effectively preventing internal unauthorized access and data tampering risks.

[0041] This disclosure addresses the problems of high system coupling, lack of standardized interaction layers, weak security protection, and unidirectional data flow in existing technologies. It constructs a six-layer decoupled architecture consisting of "end-side access layer - data structuring layer - data service layer - interface encapsulation layer - data application layer - network security layer" and clearly defines the bidirectional interaction logic and security penetration mechanism between layers.

[0042] Through a clear six-layer architecture and collaborative interaction, the decoupling of data acquisition, processing, service, application and security control is achieved. While shielding the differences of the underlying heterogeneous systems, it provides standardized business development interfaces and ensures that all cross-layer interactions are subject to unified security control, thereby building a highly scalable, highly secure, and bidirectional interactive intelligent training and assessment platform for nuclear power simulators.

[0043] In one application example, see Figure 2 The scene editing and scene transition of the system disclosed herein include the following steps: Step 1: The data application layer detects whether there is any human operation throughout the process and acquires the operating data of 100 sensors until the scene ends (acquiring human operation records). In Step 1, it is defined to acquire all operation logs and registration group information, with a start time of 00:00:00 and an end time of the end of Step 4.

[0044] Step 2: The preset scenario is to insert an SGTR breach fault of 0.1 one minute after the start (inserting the teaching control fault according to the time sequence), that is, define the inserted fault as rcs_mal11c, the fault size as 0.1, and the insertion time as 00:01:00. Step 3: After the data application layer detects that the average pressure of pressure sensors XXX001MP and XXX002MP exceeds the threshold of 5MPa, it opens valve XXX001VP (continuously monitoring and calculating registered group variables, and logically triggering DCS operation commands). The action trigger logic is defined in Step 3 as: (XX001MP + XXX002MP) / 2 > 5, with the command format: XXX001VP OPEN. Step 4: 30 seconds after the valve opens, read the real-time values ​​of pressure sensors XXX001MP and XXX002MP (read values ​​in real-time sequence). Define the trigger logic for reading the real-time values ​​in Step 4: STEP03+30S. The real-time value transmission format is: XXX001MP real-time value, XXX002MP real-time value. Save the scene after editing.

[0045] If the reuse of the same type in different scenarios is involved, the scenario conversion module calls the synonym query interface, such as converting the "XXX001VP OPEN" instruction in platform A into the "XXX001VP Open" instruction in platform B, forming a new scenario suitable for platform B and saving it.

[0046] Once the scenario begins, the edge access layer starts working. Each node in the DCS and the simulation server perform a full polling read of values ​​based on the configuration point table. Simultaneously, they scan for changes in operation and alarm-related variables to generate operation logs and alarm logs. All read values ​​and scan results are aggregated and cached on the simulation server.

[0047] The data application layer continuously retrieves all operation logs through the log query interface. Through the registration group interface, it queries the corresponding variables based on the device number and continuously monitors them, obtaining real-time values ​​from 100 sensors to plot operational curves.

[0048] When the data application layer has a runtime timer of 1 minute, it sends a command to insert SGTR vulnerability 0.1. This command first enters the network security layer, where authentication, permission verification, replay protection, and parameter validity checks are performed, and an audit log is recorded. (Every data interaction between the application and the data service layer must pass through the network security layer; subsequent steps will not be repeated.) After successful verification, the command is forwarded to the interface encapsulation layer, which ensures compatibility across different programming languages. (Every data interaction between the data application layer and the data service layer must pass through the interface encapsulation layer.) Next, the teaching control command interface of the data service layer is called to issue commands. The commands are transmitted to the simulation server, which calls the underlying teaching control execution API command to insert faults and returns a success result. The execution result is returned to the upper application layer, and the data application layer continues with subsequent scenarios.

[0049] The data application layer transmits the pressure sensor device number to the structured interaction interface of the data service layer. The structured interaction interface queries relevant variables based on the device number, continuously retrieving real-time values ​​of these variables and returning them to the data application layer. If the average value calculated by the data application layer exceeds the 5 MPa threshold, it calls the structured interaction interface, sending the XXX001VP OPEN command. The structured interaction interface queries the configuration form, converts it into an executable script, and sends the script to the endpoint node for execution, retrieving the execution result through a self-test execution interface. The structured interaction interface collects the execution result and returns it to the application. Upon receiving a successful valve opening command, the data application layer starts a timer, sending the read parameters to the structured interaction interface after 30 seconds and retrieving the real-time value.

[0050] See Figure 3 Furthermore, the system disclosed herein can also perform data configuration, synchronization, and maintenance.

[0051] Data configuration synchronization and operation and maintenance involve two types of data. One type is static configuration data, including DCS configuration forms and teaching control configuration forms. These forms are the foundation for data interaction at all levels and need to be updated, synchronized, and verified regularly. The other type is data generated by reference units and simulators during long-term operation, including operational data and operation logs. This type of data is time-series data and needs to be sampled according to application requirements, selecting measurement points and time ranges before being distributed to various applications.

[0052] For example, the production, use, and maintenance process of static configuration data may include: Develop various DCS configuration translation tools to convert inputs such as unit configuration files, control files, and database files into configuration forms, and establish a mapping between the executable device operations and acquired display information and scripts of all second-level screens in the simulator DCS system.

[0053] Develop a teaching control configuration synchronization tool that can quickly synchronize fault forms, local operations, IC lists, etc. from various simulation platform databases to the data warehouse.

[0054] Configure maintenance permissions for fields in various forms, and allow each user to update all or some fields according to their permissions.

[0055] Develop a synchronization strategy and regularly use synchronization tools to back up and synchronize data.

[0056] Form validation checks whether updated data meets consistency requirements.

[0057] Data warehouse update form.

[0058] Data warehouse forms are automatically synchronized to the client and various applications.

[0059] Each application automatically performs scene verification and assesses the impact of data updates on the scene.

[0060] For example, the production, use, and maintenance processes of unit and simulator operating data may include: The simulator log scanning module generates operation logs, which are persistently stored in the data warehouse.

[0061] The simulator registration module works by continuously collecting simulator operation data and persistently storing it in the data warehouse.

[0062] Unit operation data and operation logs are imported into the data warehouse.

[0063] Sample creation can include creating unit samples, simulator samples, and comparison samples between units and simulators.

[0064] Distribute samples to applications as needed.

[0065] In one possible implementation, a data management and application method for a nuclear power simulator based on a six-layer architecture is provided. This method is applied to the aforementioned system and includes: The system interacts with the underlying heterogeneous system of multiple simulators through the terminal access layer to collect the real-time operating data of the simulators and issue control commands. The data structuring layer converts the real-time running data collected by the terminal access layer into structured data with unified semantics, and establishes a mapping relationship between business information and the scripts of the underlying heterogeneous system. The interface encapsulation layer provides standardized application programming interfaces or software development kits to the data application layer to shield the differences between the underlying heterogeneous systems. The data service layer receives data requests or control instructions initiated by the data application layer based on the standardized interface, which are composed of business semantics, and translates the data requests or control instructions into scripts that the underlying heterogeneous system can execute, and outputs them to the terminal access layer for execution. Each data request or control command initiated by the data application layer is subject to independent security control through a network security layer, which includes identity authentication and access control. The data application layer develops and runs the training and assessment application for the simulator by calling the standardized interface. The development includes defining the timing and logical relationships of instruction issuance, data reading and log acquisition.

[0066] The methods described above have already been explained in detail in the description of the system, and will not be repeated here.

[0067] This disclosure can be a system, method, and / or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for causing a processor to implement various aspects of this disclosure.

[0068] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination of the foregoing. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0069] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0070] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to implement various aspects of this disclosure.

[0071] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0072] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0073] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0074] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0075] The various embodiments of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A nuclear power simulator data management and application system based on a six-layer architecture, characterized in that, The system includes: The edge access layer, deployed on the application end, is used to interact with the underlying heterogeneous system of the application end, collect the real-time operation data of the underlying heterogeneous system, and issue control commands; the application end includes simulation servers of various types of simulators or computing nodes of distributed control systems; The data structuring layer is used to convert the real-time running data collected by the terminal access layer into structured data with unified semantics, and to establish a mapping relationship between business information and the scripts of the underlying heterogeneous system. Interface encapsulation layer, used to provide standardized application programming interfaces or software development kits; The data service layer is used to receive data requests or control instructions composed of business semantics initiated by the upper layer application based on the standardized application programming interface of the interface encapsulation layer, and translate the received data requests or control instructions into scripts that can be executed by the underlying heterogeneous system, and execute them through the terminal access layer. The data application layer is used to develop and run training and assessment applications for nuclear power simulators by calling the standardized application programming interface of the interface encapsulation layer. The development includes defining the timing and logical relationships of instruction issuance, data reading and log acquisition. The network security layer is used to perform independent authentication and access control for each data request or control command in cross-layer interactions.

2. The system according to claim 1, characterized in that, The edge access layer includes a master node and multiple slave nodes. The master node is deployed on the simulation server, and the multiple slave nodes are deployed on multiple computing nodes of the distributed control system. The master node is used to aggregate the data collected by each slave node, and each slave node is used to obtain the data collected by the corresponding acquisition node of the distributed control system.

3. The method according to claim 1, characterized in that, The network security layer is deployed between the interface encapsulation layer and the data application layer, serving as a unified security gateway for all cross-layer interactions; The security controls also include: data transmission encryption, operation auditing and tracing, abnormal behavior monitoring, and security policy management.

4. The method according to claim 1, characterized in that, The data service layer also provides a self-detection execution interface; after a control command is issued, the data service layer obtains and returns the execution result of the control command through the self-detection execution interface.

5. The method according to claim 1, characterized in that, The data service layer also provides a heap-type synonym query interface; the data application layer, based on the heap-type synonym query interface, realizes scene semantic conversion between different DCS platforms under the same heap type.

6. The method according to claim 1, characterized in that, The data service layer also provides a registration group interface, and the data application layer sends target parameters to the data service layer. The target parameters are the parameters of the device to be monitored. The data service layer calls the registration group interface, determines the related parameters associated with the target parameter and the calculation relationship between the target parameter and the related parameters based on the preset query configuration form. Then, the data service layer sends the target parameter to the application to trigger the application to start monitoring whether the value of the target parameter has changed. When the application detects a change in the value of the target parameter, it pushes a change event to the data service layer. The change event includes the current value of the changed target parameter. Based on the received current value and the associated calculation relationship, the data service layer determines the updated value of the related parameters and sends the current value and the updated value to the data application layer, so that the data application layer updates the corresponding target parameter and related parameters.

7. The method according to claim 1, characterized in that, The data structuring layer is also used to formulate and execute permissions for data updates, automated synchronization strategies, and self-verification of updated data.

8. A method for data management and application of a nuclear power simulator based on a six-layer architecture, characterized in that, The method is applied to the system as described in any one of claims 1 to 7, and the method includes: The system interacts with the underlying heterogeneous system of multiple simulators through the terminal access layer to collect the real-time operating data of the simulators and issue control commands. The data structuring layer converts the real-time running data collected by the terminal access layer into structured data with unified semantics, and establishes a mapping relationship between business information and the scripts of the underlying heterogeneous system. The interface encapsulation layer provides standardized application programming interfaces or software development kits to the data application layer to shield the differences between the underlying heterogeneous systems. The data service layer receives data requests or control instructions initiated by the data application layer based on the standardized interface, which are composed of business semantics, and translates the data requests or control instructions into scripts that the underlying heterogeneous system can execute, and outputs them to the terminal access layer for execution. Each data request or control command initiated by the data application layer is subject to independent security control through a network security layer, which includes identity authentication and access control. The data application layer develops and runs the training and assessment application for the simulator by calling the standardized interface. The development includes defining the timing and logical relationships of instruction issuance, data reading and log acquisition.

9. A non-volatile computer-readable storage medium storing computer program instructions thereon, characterized in that, When the computer program instructions are executed by the processor, they implement the method of claim 8.

Images