A nuclear power site operation structured execution system and method based on mobile interaction and offline synchronization

The structured execution system for nuclear power plant on-site operations, based on mobile interaction and offline synchronization, solves the problems of inefficient information flow, safety blind spots, and network dependence in nuclear power plant on-site operations, achieving full coverage and efficient management.

CN122390419APending Publication Date: 2026-07-14CPI NUCLEAR POWER CO LTD +4
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
CPI NUCLEAR POWER CO LTD
Filing Date
2026-03-25
Publication Date
2026-07-14

AI Technical Summary

Technical Problem

In existing nuclear power plant field operations, information flow is inefficient and prone to errors, process control has safety blind spots, data silos are serious, and mobile applications rely on network environments and cannot be applied across the entire area.

Method used

A structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization is adopted, including a background service subsystem and a mobile operation terminal. The system generates offline data packets through structured operation templates, executes processes in a network-free environment using the offline operation module, and achieves real-time data upload or local storage by combining on-site data acquisition devices and intelligent synchronization queue modules.

Benefits of technology

It has achieved rigid technical control over the operation process, improved the reliability and safety of the operation, covered all areas of the nuclear power plant, generated structured high-value data, and improved management efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122390419A_ABST
    Figure CN122390419A_ABST
Patent Text Reader

Abstract

The application provides a nuclear power field operation structured execution system and method based on mobile interaction and offline synchronization. The system comprises a background service subsystem and a mobile operation terminal. The background service subsystem comprises a work package structured engine for generating a structured template containing work steps, risks, acceptance and other elements; an offline package management module for dynamically assembling an encrypted offline package according to tasks, with a version identifier and a signature; a data synchronization and archiving service for checking, decrypting and returning results to the business system. The mobile operation terminal comprises: an offline operation module for guiding execution according to the structured process in a network-free environment; a field data collector for calling a camera, a code scanner and an RFID, and binding work steps and device data collection; an intelligent synchronization queue module for automatically resuming transmission after network recovery. The system realizes operation error prevention, full-area coverage, structured data sedimentation and efficient work order closed loop.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application belongs to the field of digital maintenance and safety management technology for nuclear power plants, specifically relating to a structured execution system and method for on-site nuclear power operations based on mobile interaction and offline synchronization. Background Technology

[0002] In the production and operation of nuclear power plants, preventive maintenance, corrective maintenance, and equipment inspections are core aspects of ensuring the safe and stable operation of the units. Currently, these operations generally employ a combination of work orders generated through enterprise asset management systems (such as SAP and EAM) and paper-based "standard work packages." This model has the following main drawbacks: 1. Inefficient and error-prone information flow: Work packages (including procedures, drawings, risk analysis forms, etc.) need to be manually retrieved, printed and combined from multiple independent systems (such as document management system ECM, drawing system), which can easily lead to version confusion. On-site records rely on handwriting, and data entry afterward is time-consuming and prone to secondary errors.

[0003] 2. There are safety blind spots in process control: Paper-based processes cannot technically enforce the execution sequence of key steps and the confirmation of checkpoints. The verification of safety measures such as isolation boundaries and radiation protection relies on the self-awareness of personnel and paper checks, which poses a high risk of human error.

[0004] 3. Data gap between field and back-end: First-hand data generated during operations (such as instrument readings and equipment status images) cannot be structurally linked with work orders and equipment, forming "data silos" that make it difficult to support effective experience feedback and refined analysis.

[0005] 4. High dependence on network environment: Some existing mobile solutions require uninterrupted wireless network access throughout the entire operation process. However, the control areas of nuclear power plants, such as reactor buildings and fuel buildings, have strict network restrictions or signal shielding, making mobile applications unsuitable for the entire area.

[0006] Therefore, there is an urgent need for a technical solution that can overcome the above-mentioned defects, ensure that the work process is rigidly controlled, the data is real-time and reliable, and that the field operation is not dependent on a continuous network connection in complex industrial environments. Summary of the Invention

[0007] The purpose of this application is to overcome the defects.

[0008] To achieve the above objectives, this application proposes a structured execution system for nuclear power plant field operations based on mobile interaction and offline synchronization. The system includes a backend service subsystem and a mobile operation terminal; wherein... The backend service subsystem includes: The work package structuring engine is used to generate structured work templates based on the work tasks of the business system, including sequential work steps, work content, risk warnings, acceptance criteria, related materials, and safety permission prerequisites. The offline package management module, in response to requests from the mobile work terminal, dynamically assembles and encrypts offline data packages based on the work tasks, personnel qualifications, and equipment information in the structured work template. These data packages contain complete work instructions and required resources, and are accompanied by a globally unique version identifier and digital signature. The data synchronization and archiving service is used to receive the data packets of job results uploaded by the mobile job terminal, perform integrity verification and decryption, and output the result data to the relevant business system; The mobile operation terminal includes: The offline job module is used to download, store and manage offline data packets from the background service subsystem, and drive the job process using the structured process guidance engine in the absence of a network environment. The on-site data acquisition device integrates and calls upon terminal cameras, barcode scanners, and RFID readers. Guided by a structured process guidance engine, it performs location confirmation, status verification, and parameter entry operations, and binds the collected data to the current process step and equipment ID; and The intelligent synchronization queue module is used to automatically attempt network connection after the job is completed. If the connection is established, the data packet is uploaded in real time; if the connection is not established, the data packet is encrypted and stored in the local synchronization queue, and the interrupted transmission is automatically started after the network is restored.

[0009] As an improvement to the above system, the process of the structured process guidance engine driving the job flow includes: Step A1: Load the offline data package and perform integrity verification; Step A2: Create a sandbox based on offline data packets, parse the offline data packets, initialize the state machine, and start a local database transaction; Step A3: The state machine drives the user interface flow according to the predefined logic in the offline data packet, guiding the user to perform tasks.

[0010] As an improvement to the above system, the integrity verification in step A1 includes: Perform hash value comparison and digital signature verification on offline data packets; Parse the header information of the offline data packet to confirm its validity period, and verify whether the mobile operation terminal has the hardware resources required to execute the operation according to the job requirements.

[0011] As an improvement to the above system, step A2 includes: Step A2-1: Create an independent offline runtime sandbox for the job; this sandbox has an independent database tablespace or file directory to isolate and store all process data generated by this job; Step A2-2: Parse the work step sequence, branch logic, and condition rules in the structured job template, and initialize the finite state machine; this state machine records the currently completed steps, the next step to be executed, and the completion conditions for each step; Step A2-3: Start a local database transaction to ensure that all subsequent operations comply with ACID properties.

[0012] As an improvement to the above system, step A3 includes: Step A3-1: Read the step index of the current job step from the sandbox; Step A3-2: Extract the content of the current step index from the structured job template, display the job step content on the terminal interface, receive and verify the user's processing data, determine the next index based on the verification result, and repeat this step until the job is completed.

[0013] As an improvement to the above system, step A3-2 includes: Step A3-2-1: Extract the content of the current work step from the structured work template, including: work step title, detailed description, safety warnings, and required action type; Step A3-2-2: Display the work steps on the terminal interface; Step A3-2-3: Receive and verify the user's processing data according to the work step type until the job is completed. When the step type is "normal", the user confirms the operation, records the operation time, notifies the state machine that the current step has been completed, and the state machine advances the index to the next step. When the step type is "key - scan", the terminal's scanning function is activated, the scanning result is received, and the scanning result is compared and verified locally with the "device-QR code comparison table" preset in the offline data packet. If the verification is successful, the scan value, time and geographical location are recorded. After the user confirms, the state machine advances the index to the next step. If the verification fails, the state machine is prevented from advancing until the scan is successful. When the process type is "data acquisition - taking a picture", the camera is invoked to receive the picture, the picture is named according to the set rules and stored in the multimedia evidence library of the sandbox, and the picture path is recorded in the data field of the current process. The state machine then advances the index to the next step.

[0014] As an improvement to the above system, step A3-2-3 further includes: If branching conditions are defined in the structured job template, the next index will be determined based on the user input data after the current step is completed.

[0015] As an improvement to the above system, step A3-2 further includes: While recording the status changes, user confirmations, and collected data at each step, the data is written to the sandbox's local encrypted database in real time via transactional commits to ensure instant data persistence. Continuously record operation logs in the background, including any anomalies and interface switching, to form a complete audit trail; A checkpoint is created after each critical step is completed or after a set number of ordinary steps are accumulated. The checkpoint records a complete snapshot of the current state machine, including completed steps and collected data. The system monitors the remaining space in the storage area where the sandbox is located in real time. When the remaining space is lower than a set threshold, it issues a warning to the user and prevents new multimedia acquisition until the space is released.

[0016] As an improvement to the above system, step A3 further includes: When the job is saved and exited normally in the middle, the current state machine snapshot and all collected data are submitted to the local database and the sandbox is closed; when it is opened again, it can load the process from the current state machine snapshot and restore the steps before the interruption. When restarting after an abnormal interruption, the offline task library is scanned. If any tasks in the "running" state with incomplete checkpoints are found, a recovery prompt will automatically pop up, and data will be loaded from the most recent checkpoint.

[0017] This application also provides a structured execution method for nuclear power plant field operations based on mobile interaction and offline synchronization, implemented based on the above system, the method comprising: Step B1: The background service subsystem generates a structured job template based on the work task. Step B2: The mobile task terminal retrieves and updates its authorized task list and corresponding offline data packets from the background service subsystem; Step B3: The mobile work terminal starts the offline work mode, displays the detailed work content, safety warnings and required tools of the current work step in a preset order, receives work data and confirms and stores it; Step B4: When the mobile terminal returns to the network coverage area after the job is completed or partially completed, it automatically detects the network and triggers background synchronization, uploading the job process data packets to the background service subsystem to complete the data loop.

[0018] Compared with existing technologies, the advantages of this application are: 1. Rigid technical control of work processes has been achieved: Through structured guidance and error prevention confirmation mechanisms, human errors such as skipping steps and missing checks are eliminated at the system level, which greatly improves the reliability of nuclear safety-related operations.

[0019] 2. Enables mobile operation capability covering all working conditions: The "offline package" mechanism eliminates the need for a continuous and stable network for operations, enabling coverage of all areas of the nuclear power plant and solving the last obstacle to mobile applications.

[0020] 3. Generates high-value structured field data: Transforms originally discrete and unstructured field information into structured and analyzable data assets that are strongly associated with equipment, work orders, and work steps, providing a data foundation for equipment reliability analysis and preventive maintenance strategy optimization.

[0021] 4. Improved overall management efficiency: It has achieved full-process digital integration of work order preparation, on-site execution and data archiving, which has greatly reduced the circulation of paper documents and manual data entry, and improved the work order closed-loop efficiency by more than 50%. Attached Figure Description

[0022] Figure 1 The diagram shows the overall architecture of a structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization. Figure 2 The diagram shows the core software modules of the mobile operating terminal. Figure 3 The diagram shows the overall flowchart of the structured execution method for nuclear power plant field operations based on mobile interaction and offline synchronization (offline synchronization, on-site execution, data feedback). Figure 4 The image shows a schematic diagram of the mobile operation terminal interface, illustrating the scenario of structured process step guidance and data acquisition. Detailed Implementation

[0023] The technical solution of this application will be described in detail below with reference to the accompanying drawings.

[0024] The purpose of this invention is to provide a mobile and structured execution system and method suitable for on-site operations in nuclear power plants, in order to solve problems such as weak operation process control, offline unavailability of data acquisition, and difficulty in information traceability in the prior art, thereby improving operation safety, reliability and management efficiency.

[0025] Example 1 like Figure 1 As shown, this application provides a structured execution system for nuclear power plant field operations based on mobile interaction and offline synchronization, including a background service subsystem and a mobile operation terminal.

[0026] The back-end service subsystem is deployed on the power plant's internal information network and is integrated with business systems such as the production management system, document control system, and isolation management system. It includes a work package structured engine, an offline package management module, and data synchronization and archiving services.

[0027] Work Package Structure Engine: Used to intelligently parse and associate unstructured documents (work tasks) such as work orders and drawings from ECM, and generate structured work templates that include sequential work steps, work content, risk warnings, acceptance criteria, related materials and safety permission prerequisites.

[0028] Offline package management module: In response to terminal requests, it dynamically assembles and encrypts offline data packages based on the job tasks, personnel qualifications, and equipment information in the structured job template. The data package contains complete job instructions and required resources, and has a globally unique version identifier and digital signature.

[0029] Data synchronization and archiving service: Used to receive data packets of work results uploaded by terminals, perform integrity verification and decryption, and automatically distribute and write back structured data to EAM (update work order status, actual working hours and material consumption), document control system and related systems.

[0030] like Figure 2 As shown, the mobile operation terminal is an industrial explosion-proof mobile device (such as a PAD) equipped with a dedicated operation client, including an offline operation module, a field data acquisition device, and an intelligent synchronization queue module.

[0031] Offline job module: Used to download, store and manage offline data packets from the background, and drive the job process using a structured process guidance engine in the absence of network.

[0032] The structured process guidance engine is used to parse and execute structured job templates sequentially. It forces operators to perform the work step by step through a graphical interface, and the next step cannot be performed until the previous step is confirmed to be completed.

[0033] The implementation steps for driving the job process are as follows: Step 1: Local loading and integrity self-verification of offline data packets.

[0034] Step 1-1: Data packet location: When the operator enters a network-free area and starts the mobile work terminal on the terminal, the offline work module first scans the preset "offline task library" directory in the terminal's local storage.

[0035] Step 1-2: Integrity Verification: For each downloaded but not yet executed offline data packet, the module performs the following verifications: a. Hash Value Comparison: Using the SHA-256 hash value attached to the data packet, the integrity of all files within the packet (including structured job template JSON files, PDF procedure attachments, drawing thumbnails, QR code comparison tables, etc.) is calculated to ensure that the files have not been tampered with or damaged. b. Digital Signature Verification: The digital signature of the data packet is verified by calling the terminal's built-in certificate to confirm that the data packet originates from a legitimate backend service subsystem, preventing unauthorized data injection.

[0036] Steps 1-3: Validity Check: Read the "Planned Execution Date Range" from the data packet header to determine if the current job time is within the validity period. If the validity period has expired, the module will lock the task and prompt "Job has expired, please resynchronize".

[0037] Steps 1-4: Dependency Check: Verify whether the terminal has the hardware resources required to execute the task, such as whether a camera (for taking pictures), Bluetooth (for connecting to instruments), NFC (for reading employee cards), etc., are needed. If critical hardware is missing, a warning will be issued.

[0038] Step 2: Create an offline runtime sandbox environment Step 2-1: Isolate the runtime environment: After successful verification, the module creates an independent offline runtime sandbox for the job. This sandbox has an independent database tablespace or file directory to isolate and store all process data generated by this job.

[0039] Step 2-2: Initialize the State Machine: The module parses the work step sequence, branch logic, and condition rules in the structured job template and initializes a finite state machine in memory. The state machine records the currently completed steps, the next step to be executed, and the completion conditions for each step.

[0040] Steps 2-3: Start a local transaction: The module starts a local database transaction to ensure that all subsequent operations comply with ACID (Atomicity, Consistency, Isolation, Durability) properties and prevent data corruption due to abnormal power outages or program crashes.

[0041] Step 3: Sequential execution of bootstrapping and mandatory logic control This is the core of offline operations; the state machine drives the user interface flow based on predefined logic. Step 3-1: Obtain the current state: The state machine reads the current step index (e.g., StepIndex=3) from the sandbox.

[0042] Step 3-2: Render the current step: Step 3-2-1: The module extracts the content of the current operation step from the structured operation template, including: step title (e.g., "Confirm Isolation Boundary"), detailed description (e.g., "Check that upstream valve V-101 has been marked with a red tag and locked"), safety warning (e.g., "If not isolated, operation is strictly prohibited!"), and required action type (e.g., "Scan code to confirm").

[0043] Step 3-2-2: Render this step on the terminal interface and highlight the "Confirm" button, but the button's initial state is "Disabled".

[0044] Step 3-2-3: Waiting for and processing user actions: a. Case A - Normal Confirmation Step: If the step type is "Normal," the operator clicks "Confirm" after reading. The module will unlock the button, record the operation time, and notify the state machine that the current step is complete. The state machine will then advance the index to the next step (e.g., StepIndex=4). b. Case B - QR Code Verification Step: If the step type is "Critical - QR Code Scan," the module automatically activates the terminal's QR code scanning function and displays a pop-up message: "Please scan the device / lock QR code." After the operator scans the code, the module will locally compare the scan result with the "Device-QR Code Comparison Table" pre-set in the offline data package.

[0045] If the verification is successful: the QR code value matches and belongs to the correct device / lock, the module records the scan value, time, and geographical location (if GPS is available), unlocks the "Confirm" button, and after the operator clicks it, the state machine progresses.

[0046] If verification fails: QR code mismatch or error, the terminal vibrates and pops up a red warning "Verification failed, please confirm the target!", and the state machine is prohibited from proceeding until the scan is successful.

[0047] c. Scenario C - Data Acquisition Step: If the step type is "Data Acquisition - Photo Capture", the module automatically calls the camera and creates a non-editable filename template, such as "E_FD_001A_Step3_20231027103025.jpg" (Device ID + Step + Timestamp). After taking the photo, the image is automatically named according to this rule and stored in the "Multimedia Evidence Library" in the sandbox. At the same time, the image path is recorded in the data field of the current step, and the state machine automatically advances.

[0048] Step 3-2-4: Inter-step logic transition control: The state machine strictly follows preset logic. If the work template defines branch conditions (e.g., "if pressure > 10MPa, jump to step 5A, otherwise jump to step 5B"), the module will automatically determine the next index based on the user-input data (such as pressure reading) after the current step is completed, realizing dynamic path guidance without a network.

[0049] During the implementation of the work process, the offline work module also has offline data preservation and anti-loss mechanisms: 1. Real-time disk storage: The status changes, user confirmations, and collected data of each step are recorded and written to the local encrypted database of the sandbox in real time through transactional commit, ensuring that the data is persisted immediately.

[0050] 2. Log recording: The module continuously records detailed operation logs in the background, including any anomalies (such as failed QR code scanning, low battery warnings), interface switching, etc., forming a complete audit trail.

[0051] 3. Checkpoint Mechanism: A checkpoint is created after each critical step is completed or after accumulating multiple (e.g., 5) ordinary steps. The checkpoint records a complete snapshot of the current state machine, including completed steps and collected data. If the program unexpectedly restarts, the module can resume from the most recent checkpoint instead of starting from the beginning.

[0052] 4. Storage Space Monitoring: The module monitors the remaining space of the storage partition where the sandbox is located in real time. When the remaining space is lower than a threshold (e.g., 50MB), a warning is issued to the user, and new multimedia capture (e.g., taking photos) is blocked until the space is released to prevent data loss due to full storage.

[0053] During the implementation of the work process, the offline work module also has an execution interruption and recovery process: 1. Normal Interruption: If operators need to pause work for any reason (such as lunch break or shift change), they can click "Save and Exit". The module will submit the current state machine snapshot and all collected data to the local database and close the sandbox. The next time the module is opened, it will prompt "Incomplete task detected, continue?". Selecting "Yes" will load the snapshot and restore the steps before the interruption.

[0054] 2. Abnormal Interruption: If an abnormality such as terminal crash or battery depletion occurs, restart the terminal and open the client. When the offline job module starts, it will automatically scan the "offline task library". If it finds any tasks in the "running" state with incomplete checkpoints, it will automatically pop up a recovery prompt and load data from the most recent checkpoint to minimize on-site duplication of work.

[0055] On-site data acquisition device: Integrates and calls hardware such as terminal camera, barcode scanner, and RFID reader to perform location confirmation (barcode / RFID), status verification (photo / video recording), and parameter input (manual input or instrument Bluetooth reading) under the guidance of specific work steps, and automatically binds the collected data with the current work step and equipment ID.

[0056] Intelligent synchronization queue module: After the job is completed, it automatically attempts to connect to the network. If the connection is established, the data packet is uploaded in real time. If the connection is not established, the data packet is encrypted and stored in the local "synchronization queue". Once the network is restored, the interrupted transmission will be resumed automatically.

[0057] Example 2 like Figure 3 As shown, this application also provides a structured execution method for nuclear power plant field operations based on mobile interaction and offline synchronization, implemented based on the above system, including the following steps: Step 1: Task preparation: The background service subsystem generates a structured job template based on the work task.

[0058] Step 2: Task Synchronization Phase: Operators log in to their terminals in the network availability zone. The terminals retrieve and update their authorized task list and corresponding offline data packets from the background service subsystem.

[0059] Step 3: Offline Execution Phase: The operator enters the work site (where there may be no network), and the terminal starts the offline work mode: Step 3-1: Process guidance: The terminal displays the detailed work content, safety warnings and required tools for the current step in a preset order.

[0060] Step 3-2: Operation Confirmation and Error Prevention: After completing the current step, the operator must perform electronic confirmation; for critical safety steps (such as "verify isolation has been performed"), the system requires scanning the QR code of the isolation lock or entering an independent verification code for secondary confirmation.

[0061] Step 3-3: Data Acquisition: When needed, the system will automatically redirect to the data acquisition interface and guide you to complete the specified action (such as "taking a picture of the pressure gauge reading"). The data will be automatically tagged and stored.

[0062] Step 4: Data Synchronization Phase: After the operation is completed or partially completed, the operator returns to the network coverage area. The terminal automatically detects the network and triggers background synchronization, uploading the complete and structured operation process data packet to the background service subsystem to complete the data loop.

[0063] Example 3 Taking the "main pump lubricating oil sampling" operation in a nuclear power plant as an example, this paper illustrates the structured execution method of nuclear power field operations based on mobile interaction and offline synchronization. Step 1: Task Preparation: The engineer creates a "Main Pump A Lubricating Oil Sampling" work order in SAP. The background service subsystem automatically links the "Oil Sampling Procedure", the equipment drawings of Main Pump A, historical oil sample data, and checks the "Radiation Work Permit" status to generate a structured operation template.

[0064] Step 2: Offline Synchronization: Laboratory worker A logs in using an explosion-proof PAD in the office, and the system automatically pushes the task. A clicks "Download," and the terminal downloads an offline data package containing the job template, associated document QR codes, and other information to its local machine.

[0065] Step 3: On-site execution: Personnel A enters the nuclear island site.

[0066] Step 3-1: The terminal displays "1. Confirm sampling point location and identification". When A arrives near main pump A, the terminal prompts "Please scan the equipment QR code". A scans the QR code on the pump body, the terminal verifies the scan, and displays a schematic diagram of the pump's sampling point.

[0067] Step 3-2: The terminal displays "2. Perform pre-sampling radiation dose monitoring" (e.g., Figure 4 (As shown). This step is critical and mandatory by the system. After taking the measurement using the Bluetooth dosimeter, User A manually enters the reading into the terminal and takes a photo to upload to the dosimeter screen. The system compares the reading to see if it is within the allowable range.

[0068] Step 3-3: The terminal displays "3. Take samples using a dedicated container". After sample collection, the terminal prompts "Take a photo of the labeled sample bottle". The photo automatically records the sample identification and sampling time.

[0069] After each step is completed, A must click "Confirm Completion" to proceed to the next step.

[0070] Step 4: Data Closure: Personnel A returns to the office, and the PAD automatically connects to Wi-Fi, packaging and encrypting the complete record of this operation (including confirmation time for each step, personnel, scanning device ID, input dose readings, and sample photos) and uploading it. The background service subsystem automatically writes the "actual working hours" back to the SAP work order, includes the sampling record and photos in the main pump A's equipment file, and notifies the laboratory that the sample has been delivered.

[0071] The structured execution system and method for nuclear power plant field operations based on mobile interaction and offline synchronization provided in this application have the following characteristics: 1. "Offline Packet" Dynamic Generation and Intelligent Synchronization Mechanism: For nuclear power plants without network access, a data packet format and synchronization strategy containing the complete operation context were designed to achieve full-area coverage of mobile operations.

[0072] 2. Error-proof process guidance engine based on structured templates: Transforms unstructured procedures into executable "state machines" and implements mandatory verification of key operations through a combination of software and hardware (scanning codes, taking photos).

[0073] 3. Automated acquisition and semantic binding technology of heterogeneous data in the field: Through preset rules, data collected by terminal peripherals is automatically called and given business semantics (such as "Device ID: P-001A, Step: Radiation monitoring, Reading: 5.2μSv / h") to form a high-quality data chain.

[0074] This application may also provide a computer device, including: at least one processor, memory, at least one network interface, and a user interface. The various components in this device are coupled together via a bus system. It is understood that the bus system is used to implement communication between these components. In addition to a data bus, the bus system also includes a power bus, a control bus, and a status signal bus.

[0075] The user interface can include a display, keyboard, or clicking device. Examples include a mouse, trackball, touchpad, or touchscreen.

[0076] It is understood that the memory in the embodiments disclosed in this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memories described herein are intended to include, but are not limited to, these and any other suitable types of memory.

[0077] In some implementations, the memory stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof: operating systems and applications.

[0078] The operating system includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application programs include various applications, such as media players and browsers, used to implement various application functions. Programs implementing the methods of the embodiments of this disclosure can be included in the application programs.

[0079] In the above embodiments, the processor can also invoke programs or instructions stored in memory, specifically programs or instructions stored in an application program, for the following purposes: Follow the steps described above.

[0080] The above methods can be applied to or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the processor's hardware or by software instructions. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic diagrams disclosed above. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the disclosed methods can be directly implemented by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0081] It is understood that the embodiments described in this application can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this application, or combinations thereof.

[0082] For software implementation, the technology of this application can be implemented by executing the functional modules (e.g., procedures, functions, etc.) of this application. The software code can be stored in memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0083] This application may also provide a non-volatile storage medium for storing a computer program. When the computer program is executed by a processor, it can implement the steps in the above method embodiments.

[0084] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit it. Although this application has been described in detail with reference to the embodiments, those skilled in the art should understand that modifications or equivalent substitutions to the technical solutions of this application do not depart from the spirit and scope of the technical solutions of this application, and should all be covered within the scope of the claims of this application.

Claims

1. A structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization, characterized in that, The system includes a backend service subsystem and a mobile operation terminal; wherein... The backend service subsystem includes: The work package structuring engine is used to generate structured work templates based on the work tasks of the business system, including sequential work steps, work content, risk warnings, acceptance criteria, related materials, and safety permission prerequisites. The offline package management module, in response to requests from the mobile work terminal, dynamically assembles and encrypts offline data packages based on the work tasks, personnel qualifications, and equipment information in the structured work template. These data packages contain complete work instructions and required resources, and are accompanied by a globally unique version identifier and digital signature. The data synchronization and archiving service is used to receive the data packets of job results uploaded by the mobile job terminal, perform integrity verification and decryption, and output the result data to the relevant business system; The mobile operation terminal includes: The offline job module is used to download, store and manage offline data packets from the background service subsystem, and drive the job process using the structured process guidance engine in the absence of a network environment. The on-site data acquisition device integrates and calls upon terminal cameras, barcode scanners, and RFID readers. Guided by a structured process guidance engine, it performs location confirmation, status verification, and parameter entry operations, and binds the collected data to the current process step and equipment ID; and The intelligent synchronization queue module is used to automatically attempt network connection after the job is completed. If the connection is established, the data packet is uploaded in real time; if the connection is not established, the data packet is encrypted and stored in the local synchronization queue, and the interrupted transmission is automatically started after the network is restored.

2. The structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization according to claim 1, characterized in that, The process by which the structured process guidance engine drives the job flow includes: Step A1: Load the offline data package and perform integrity verification; Step A2: Create a sandbox based on offline data packets, parse the offline data packets, initialize the state machine, and start a local database transaction; Step A3: The state machine drives the user interface flow according to the predefined logic in the offline data packet, guiding the user to perform tasks.

3. The structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization according to claim 2, characterized in that, The integrity verification in step A1 includes: Perform hash value comparison and digital signature verification on offline data packets; Parse the header information of the offline data packet to confirm its validity period, and verify whether the mobile operation terminal has the hardware resources required to execute the operation according to the job requirements.

4. The structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization according to claim 2, characterized in that, Step A2 includes: Step A2-1: Create an independent offline runtime sandbox for the job; this sandbox has an independent database tablespace or file directory to isolate and store all process data generated by this job; Step A2-2: Parse the work step sequence, branch logic, and condition rules in the structured job template, and initialize the finite state machine; this state machine records the currently completed steps, the next step to be executed, and the completion conditions for each step; Step A2-3: Start a local database transaction to ensure that all subsequent operations comply with ACID properties.

5. The structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization according to claim 2, characterized in that, Step A3 includes: Step A3-1: Read the step index of the current job step from the sandbox; Step A3-2: Extract the content of the current step index from the structured job template, display the job step content on the terminal interface, receive and verify the user's processing data, determine the next index based on the verification result, and repeat this step until the job is completed.

6. The structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization according to claim 5, characterized in that, Step A3-2 includes: Step A3-2-1: Extract the content of the current work step from the structured work template, including: work step title, detailed description, safety warnings, and required action type; Step A3-2-2: Display the work steps on the terminal interface; Step A3-2-3: Receive and verify the user's processing data according to the work step type until the job is completed. When the step type is "normal", the user confirms the operation, records the operation time, notifies the state machine that the current step has been completed, and the state machine advances the index to the next step. When the step type is "key - scan", the terminal's scanning function is activated, the scanning result is received, and the scanning result is compared and verified locally with the "device-QR code comparison table" preset in the offline data packet. If the verification is successful, the scan value, time and geographical location are recorded. After the user confirms, the state machine advances the index to the next step. If the verification fails, the state machine is prevented from advancing until the scan is successful. When the process type is "data acquisition - taking a picture", the camera is invoked to receive the picture, the picture is named according to the set rules and stored in the multimedia evidence library of the sandbox, and the picture path is recorded in the data field of the current process. The state machine then advances the index to the next step.

7. The structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization according to claim 6, characterized in that, Step A3-2-3 further includes: If branching conditions are defined in the structured job template, the next index will be determined based on the user input data after the current step is completed.

8. The structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization according to claim 6, characterized in that, Step A3-2 further includes: While recording the status changes, user confirmations, and collected data at each step, the data is written to the sandbox's local encrypted database in real time via transactional commits to ensure instant data persistence. Continuously record operation logs in the background, including any anomalies and interface switching, to form a complete audit trail; A checkpoint is created after each critical step is completed or after a set number of ordinary steps are accumulated. The checkpoint records a complete snapshot of the current state machine, including completed steps and collected data. The system monitors the remaining space in the storage area where the sandbox is located in real time. When the remaining space is lower than a set threshold, it issues a warning to the user and prevents new multimedia acquisition until the space is released.

9. The structured execution system for nuclear power plant on-site operations based on mobile interaction and offline synchronization according to claim 2, characterized in that, Step A3 further includes: When the job is saved and exited normally in the middle, the current state machine snapshot and all collected data are submitted to the local database and the sandbox is closed; when it is opened again, it can load the process from the current state machine snapshot and restore the steps before the interruption. When restarting after an abnormal interruption, the offline task library is scanned. If any tasks in the "running" state with incomplete checkpoints are found, a recovery prompt will automatically pop up, and data will be loaded from the most recent checkpoint.

10. A structured execution method for nuclear power plant field operations based on mobile interaction and offline synchronization, implemented based on the system described in any one of claims 1-9, the method comprising: Step B1: The background service subsystem generates a structured job template based on the work task. Step B2: The mobile task terminal retrieves and updates its authorized task list and corresponding offline data packets from the background service subsystem; Step B3: The mobile work terminal starts the offline work mode, displays the detailed work content, safety warnings and required tools of the current work step in a preset order, receives work data and confirms and stores it; Step B4: When the mobile terminal returns to the network coverage area after the job is completed or partially completed, it automatically detects the network and triggers background synchronization, uploading the job process data packets to the background service subsystem to complete the data loop.