Industrial equipment three-dimensional simulation control method and system, storage medium and program product

Abstract

The application provides an industrial equipment three-dimensional simulation control method, system, storage medium and program product. The method comprises the following steps: creating a collaboration room at a server end, and loading a unified perspective three-dimensional equipment model; constructing a node dependency graph based on an assembly dependency relationship between components in the perspective three-dimensional equipment model; when any trainee client initiates an operation request on a target node, judging whether the operation precondition of the target node is met according to the node dependency graph; if yes, granting the trainee the operation right on the target node, and determining a node set that needs to be mutually protected based on the node dependency graph; after the operation is completed, broadcasting the operation result and the updated node dependency state to all clients in the collaboration room to synchronize the equipment model state; and if not, rejecting the operation request, and rolling back the state of the perspective three-dimensional equipment model to the nearest legal state under the constraint of the node dependency graph.

Description

Technical Field

[0001] This application relates to the field of industrial equipment operation training, and more specifically, to a three-dimensional simulation control method, system, storage medium, and program product for industrial equipment. Background Technology

[0002] With the deepening of industrial digital and intelligent transformation, hands-on training systems based on 3D simulation have been widely used in fields such as power, rail transportation, petrochemicals, and high-end manufacturing. These systems construct high-fidelity, interactive digital twin models of equipment, enabling trainees to perform operations such as equipment disassembly, assembly, and troubleshooting in a risk-free virtual environment, significantly improving training safety and efficiency.

[0003] Early 3D simulation training systems were primarily designed for single-user scenarios, focusing on model visualization, operation guidance, and result scoring. These systems typically had pre-defined, fixed operating procedures, which trainees followed sequentially. The system verified the correctness of the operations through state machines or scripts. While this approach worked well in a single-user environment, it couldn't support multiple users simultaneously operating the same equipment model collaboratively. It struggled to meet the training needs of real-world industrial scenarios such as dual-person monitoring, joint maintenance, and collaborative switching, and also failed to satisfy the requirements for interactive multi-user training.

[0004] In recent years, some platforms have attempted to introduce multi-user collaboration capabilities, allowing multiple trainees to enter the same virtual room and operate shared 3D equipment models. However, the operation of industrial equipment has strict assembly and safety dependencies. For example, the disconnect switch must be disconnected before operating the grounding switch, and the outer casing must be removed before accessing internal components. Allowing multiple trainees to operate concurrently without constraints can easily lead to illegal operations that violate the dependency sequence, causing the model to fall into logical contradictions or physically infeasible states. This could not only negate the training's purpose but also mislead trainees into developing incorrect operating habits. Summary of the Invention

[0005] In view of this, the purpose of this application is to provide a method, system, storage medium and program product for three-dimensional simulation control of industrial equipment, so as to improve the technical problem that unconstrained operation by multiple people on a shared three-dimensional equipment model can easily lead to the model state falling into a state of logical contradiction or physical infeasibility.

[0006] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows:

[0007] In a first aspect, this application provides a three-dimensional simulation control method for industrial equipment, comprising:

[0008] Create a collaborative room on the server side and load a unified perspectived 3D device model;

[0009] Based on the assembly dependency relationships between the components in the perspectived 3D device model, a node dependency graph is constructed, which is used to constrain the disassembly and assembly sequence of component nodes.

[0010] When any student client initiates an operation request to the target node, the node dependency graph is used to determine whether the operation preconditions of the target node are met.

[0011] If the conditions are met, the student is granted the right to operate on the target node, and a set of nodes that need to be mutually exclusive is determined based on the node dependency graph, preventing other students from operating on any node in the set at the same time.

[0012] After the operation is completed, the operation results and the updated node dependency status are broadcast to all clients in the collaborative room to synchronize the device model status.

[0013] If the aforementioned preconditions are not met, the operation request is rejected, and the state of the perspectived 3D device model is reverted to the most recent valid state under the node dependency graph constraints.

[0014] Optionally, the step of constructing a node dependency graph based on the assembly dependencies between components in the perspectived 3D device model includes:

[0015] The metadata of the perspectived 3D device model is parsed to identify the physical connection relationships between the nodes of each component;

[0016] According to the preset industrial operation specifications, the physical connection relationship is mapped into an operation dependency relationship;

[0017] A node dependency graph is generated based on the operational dependencies.

[0018] Optionally, the step of parsing the metadata of the perspectived 3D device model and identifying the physical connection relationships between the component nodes includes:

[0019] Read the assembly interface attributes of each component node, including interface type, spatial coordinates, normal vector and number of fasteners;

[0020] When two components have matching interface types, a spatial distance less than a distance threshold, and opposite parallel normal vectors, they are determined to have a physical connection.

[0021] Optionally, the step of mapping the physical connection relationship to an operational dependency relationship according to a preset industrial operation specification includes:

[0022] If the first component blocks the disassembly path of the second component, then add a directed edge from the first component to the second component in the node dependency graph;

[0023] If the two components are electrically interlocked, add a bidirectional dependency edge and mark it as a "strong safety constraint" type.

[0024] Optionally, the step of determining whether the preconditions for the operation of the target node are met based on the node dependency graph when any student client initiates an operation request to the target node includes:

[0025] Obtain all the preceding dependent nodes of the target node in the node dependency graph;

[0026] Check whether the current state of each preceding dependent node matches the preset completion state;

[0027] The prerequisite condition is considered satisfied only if all preceding dependent nodes are in the completed state.

[0028] Optionally, the step of determining the set of nodes that need to be mutually exclusive based on the node dependency graph includes:

[0029] Identify all descendant nodes of the target node in the node dependency graph, forming a first mutually exclusive subset;

[0030] If the target node has a preset security sensitivity attribute, then according to the domain security rule base, determine the associated device nodes that are in the same security isolation area as the target node and have no dependency relationship with the target node in the node dependency graph, and form a second mutually exclusive subset.

[0031] The union of the first mutually exclusive subset and the second mutually exclusive subset is taken as the final set of mutually exclusive protected nodes.

[0032] Optionally, it also includes:

[0033] Record the user ID, target node, operation time, dependency verification result, operation success status, and status change details for each operation request to form a structured operation log;

[0034] Align the structured operation log with the audio and video streams recorded in the room by timestamp;

[0035] Based on the operation logs, an operation compliance score is automatically calculated. The compliance score is generated by weighting the number of dependency violations, operation path redundancy, and task completion time.

[0036] Secondly, embodiments of this application provide a three-dimensional simulation control system for industrial equipment, comprising:

[0037] The room management module is used to create collaborative rooms on the server side and load a unified perspective 3D device model.

[0038] The dependency graph construction module is used to construct a node dependency graph based on the assembly dependency relationships between the components in the perspectived 3D device model. The node dependency graph is used to constrain the disassembly and assembly order of the component nodes.

[0039] The operation verification module is used to determine whether the operation preconditions of the target node are met based on the node dependency graph when any student client initiates an operation request to the target node.

[0040] The mutual exclusion control module is used to grant the student the right to operate on the target node when the operation verification module determines that the preconditions are met, and to determine the set of nodes that need to be mutually excluded based on the node dependency graph, so as to prevent other students from operating any node in the set at the same time.

[0041] The state synchronization module is used to broadcast the operation results and the updated node dependency state to all clients in the collaborative room after the operation is completed, so as to synchronize the device model state.

[0042] The state rollback module is used to reject the operation request when the operation verification module determines that the preconditions are not met, and to roll back the state of the perspectived 3D device model to the nearest valid state under the node dependency graph constraints.

[0043] Thirdly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the industrial equipment three-dimensional simulation control method as described in the first aspect.

[0044] Fourthly, embodiments of this application provide a computer program product, including computer program instructions, which, when executed by a processor, cause the processor to perform the industrial equipment three-dimensional simulation control method as described in the first aspect.

[0045] In the method described in the first aspect above, the following can be understood:

[0046] This application provides a 3D simulation control method for industrial equipment. By constructing a node dependency graph based on the assembly dependencies of equipment components on the server side, and using this graph as the core basis for collaborative operation control, it effectively solves the technical problems of frequent illegal operations and chaotic model states caused by the lack of operation sequence constraints in existing multi-user 3D simulation systems. Specifically, when any student initiates an operation request, the system dynamically verifies whether its preconditions are met based on the node dependency graph, granting operation rights only when they are legal. Based on this dependency graph, the system automatically determines the set of nodes requiring mutual exclusion protection (including all descendant nodes of the target node and associated devices extended by domain security rules), thereby ensuring operational compliance while preventing state conflicts caused by concurrent operation by multiple users. If an operation request violates dependency constraints, it is immediately rejected, and the equipment model state is automatically rolled back to the most recent legal state allowed by the node dependency graph, ensuring that the simulation process is always in a logically consistent and reliable state. Simultaneously, after each legal operation is completed, the system broadcasts the operation result and the updated dependency state to all clients in real time, achieving strong consistency synchronization of model states across multiple clients. Therefore, this application not only eliminates high-risk violations such as "live disassembly" and "unisolated operation", which helps to improve the safety and standardization of industrial simulation training, but also achieves a highly reliable and consistent multi-person collaborative operation experience through a dependency-driven dynamic mutual exclusion and automatic rollback mechanism.

[0047] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, embodiments of this application are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0048] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0049] Figure 1 A schematic diagram of the network architecture of a three-dimensional simulation control system for industrial equipment provided in this application embodiment;

[0050] Figure 2 This is a schematic diagram of the structure of the industrial equipment three-dimensional simulation control system provided in the embodiments of this application;

[0051] Figure 3 This is a flowchart illustrating a three-dimensional simulation control method for industrial equipment provided in an embodiment of this application. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0053] Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0054] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0055] It should be noted that, where there is no conflict, the features in the embodiments of this application can be combined with each other.

[0056] This application provides a technical solution including: a three-dimensional simulation control method, system, storage medium, and program product for industrial equipment. The technical solution provided by this application will be described below with reference to the accompanying drawings.

[0057] Please see Figure 3 This application provides a three-dimensional simulation control method for industrial equipment. This three-dimensional simulation supports multi-person collaborative perspective disassembly, enabling training to meet the needs of real-world industrial scenarios such as dual-person monitoring, joint maintenance, and collaborative switching, as well as multi-person interaction. The industrial equipment three-dimensional simulation control method includes:

[0058] S1. Create a collaborative room on the server side and load a unified perspective 3D device model.

[0059] In this step, the system dynamically creates an independent collaborative room on the server side for a collaborative training task. This room serves as a logical unit for multi-user interaction, hosting the status, messages, and data of all users within the room. The server can be a communication server. The creation of collaborative rooms can be implemented using Docker containers, with each room running in an independent Docker container, ensuring resource isolation and security compared to other rooms, and supporting on-demand rapid start / stop to optimize server resources. After creation, the system loads a unified perspective-based 3D device model matching the current training task from the database server, which is based on MySQL and Redis caching. For example, the perspective-based 3D device model can be a 220V DC system for a switch station, including charging screens 1 and 2, a power supply screen, and batteries. This device model is optimized using lightweight meshes, texture merging, and atlas techniques to ensure efficient loading and smooth rendering on the client side.

[0060] S2. Based on the assembly dependency relationships between components in the perspectived 3D equipment model, construct a node dependency graph. The node dependency graph is used to constrain the disassembly and assembly sequence of component nodes.

[0061] In detail, the system transforms the physical and logical operational rules of the equipment into computable structured data. It analyzes the assembly relationships between components in the equipment model (such as circuit breakers, disconnectors, and housings), such as the electrical and mechanical dependencies implied in "connecting a battery bank to charging panel #1," and constructs a node dependency graph based on this—where each component is a node, and dependencies (such as "A must be disconnected before B can be operated") are represented by directed edges. This dependency graph not only reflects the static assembly structure but also incorporates industrial operating standards (such as electrical safety regulations), such as dynamic constraints like "obstructing disassembly paths" or "electrical interlocks." The construction of the dependency graph combines the concepts of "model resource optimization" and "standardized modeling" to ensure a reasonable data structure, minimal redundancy, and efficient updates. Through this graph, the system makes the originally implicit operational sequences explicit and verifiable, providing authoritative evidence for judging the legality of subsequent operations. This fundamentally prevents trainees from performing incorrect operations due to a lack of understanding of the process flow, thus improving the professionalism and safety of the training.

[0062] S3. When any student client initiates an operation request to the target node, determine whether the preconditions for the operation of the target node are met based on the node dependency graph.

[0063] During the collaborative process, when any student initiates an operation on a device component via the client, the request is first sent to the collaborative room processing module on the server. The system then traverses the node dependency graph, obtains all the preceding dependent nodes of the target node (such as the corresponding circuit breaker status, grounding switch position, etc.), and checks whether its current state meets the preset completion conditions (such as "circuit breaker has been tripped" or "grounding switch is in the grounded position"). This verification process is centrally executed on the server side. If a Spring Boot application server is used to handle the business logic, it ensures authoritative judgment and tamper-proof protection, transforming teaching rules into a real-time verification mechanism. By judging the node dependency graph, violations can be intercepted before the operation is executed, preventing the model from entering an illegal state. At the same time, real-time feedback (such as highlighting incomplete prerequisites) helps students understand the operation logic and strengthens the learning effect. Real-time feedback can be achieved by highlighting incomplete prerequisites.

[0064] S4. If satisfied, grant the student the right to operate on the target node, and determine the set of nodes that need to be mutually exclusive based on the node dependency graph, preventing other students from operating on any node in the set at the same time.

[0065] Specifically, once an operation request is verified, the system immediately grants the student exclusive operation rights to the target node and initiates a mutual exclusion control mechanism. The mutual exclusion scope is not limited to the target node itself, but dynamically extends to all its descendant nodes (i.e., sub-components affected by the operation) based on the node dependency graph. For example, when disassembling the main busbar, all connected feeder switches are automatically locked. Furthermore, a domain security rule base can be used to include devices that, while having no dependencies, belong to the same security isolation zone into the mutual exclusion set. This mechanism is efficiently handled by the communication server, utilizing message queues and state synchronization technology to ensure low-latency distribution of mutual exclusion commands. This step effectively resolves operation conflicts under concurrent operation by multiple users, ensures consistency of model state logic, and avoids dangerous scenarios such as "two people disassembling the same device simultaneously" or "one person disassembling the busbar while another closes the switch," effectively improving the reliability and realism of collaborative simulation.

[0066] S5. After the operation is completed, broadcast the operation results and the updated node dependency status to all clients in the collaboration room to synchronize the device model status.

[0067] In detail, after a participant completes an operation (such as successfully opening an isolation switch), the system packages the operation result (including new node states, spatial transformations, and visibility changes) along with the updated state of the node dependency graph (such as the removal of a dependency edge due to the operation's completion). This package is then broadcast efficiently and systematically to all clients in the room via a communication server. The broadcast employs an incremental update strategy, transmitting only the changed portions to reduce network bandwidth consumption and improve response speed. Upon receiving the message, each client synchronously updates its local model and dependency graph, ensuring that all participants see a completely consistent device state and operable range.

[0068] S6. If the preconditions are not met, the operation request is rejected, and the state of the perspectived 3D device model is rolled back to the nearest valid state under the node dependency graph constraints.

[0069] Specifically, if the operation verification fails (e.g., a trainee attempts to disassemble the device while it is still powered on), the system immediately rejects the request and returns a structured error message to the client (e.g., "Please disconnect the output of charging screen 1 first"), while simultaneously triggering the state rollback mechanism. The system maintains a state snapshot stack, automatically restoring the device model to its most recent valid state, ensuring the simulation environment is always in a trustworthy state conforming to industry standards. Maintaining the state snapshot stack refers to saving a composite snapshot of the model and dependency graph before each valid operation. By setting up the rollback mechanism, even if a trainee makes a mistake, the system can self-correct, preventing training interruptions or model crashes. Simultaneously, the rollback process itself serves as teaching feedback, helping trainees understand "why they cannot operate," strengthening safety awareness and process understanding, and truly achieving "fault-tolerant learning."

[0070] The technical solution provided in this application effectively solves the technical problems of frequent illegal operations and chaotic model states caused by the lack of operation sequence constraints in existing multi-user 3D simulation systems by constructing a node dependency graph based on the assembly dependencies of equipment components on the server side and using this as the core basis for collaborative operation control. Specifically, when any student initiates an operation request, the system dynamically verifies whether its preconditions are met based on the node dependency graph, granting operation rights only when they are legal. Based on this dependency graph, the system automatically determines the set of nodes that need mutual exclusion protection (including all descendant nodes of the target node and associated devices extended by domain security rules), thereby ensuring operational compliance while preventing state conflicts caused by concurrent operation by multiple users. If an operation request violates dependency constraints, it is immediately rejected, and the equipment model state is automatically rolled back to the most recent legal state allowed by the node dependency graph, ensuring that the simulation process is always in a logically consistent and reliable state. Simultaneously, after each legal operation is completed, the system broadcasts the operation result and the updated dependency state to all clients in real time, achieving strong consistency synchronization of model states across multiple clients. Therefore, this application not only eliminates high-risk violations such as "live disassembly" and "unisolated operation", which helps to improve the safety and standardization of industrial simulation training, but also achieves a highly reliable and consistent multi-person collaborative operation experience through a dependency-driven dynamic mutual exclusion and automatic rollback mechanism.

[0071] In some embodiments, step S2, which constructs a node dependency graph based on the assembly dependencies between components in a perspectived 3D device model, may further include:

[0072] S21. Analyze the metadata of the perspectived 3D device model and identify the physical connection relationships between the nodes of each component.

[0073] The system first loads the pre-built perspective-based 3D device model and reads its embedded metadata. This metadata is structured and stored during the model creation stage, using formats that support semantic tags, such as glTF and FBX. It includes the assembly interface attributes of each component node, such as interface type, spatial coordinates, normal vector direction, and the number of fasteners. Interface types include bolt holes, clips, and electrical plugs. The system uses both geometric and semantic judgments: when two components have matching interface types, a spatial distance less than a preset threshold, and opposite parallel normal vectors, they are considered to have a physical connection. The preset threshold for spatial distance can be set to less than 5mm, and opposite parallel normal vectors indicate surface-to-surface fit. This process can be completed using a GPU-accelerated spatial query algorithm.

[0074] S22. Based on the preset industrial operation specifications, map the physical connection relationship into the operation dependency relationship.

[0075] After identifying the physical connections, the system calls a pre-defined industrial operation specification knowledge base, which can be stored in a MySQL database and accessed more quickly via Redis caching. This transforms the physical connections into dependencies with operational semantics. For example, if component A completely blocks the disassembly path of component B, the system automatically adds a directed edge from A to B in the dependency graph according to electrical safety regulations or mechanical maintenance procedures, indicating that "A must be disassembled before B can be operated." If the two components are electrically interlocked, such as a disconnector and a grounding switch interlocked, a bidirectional dependency edge is added and marked as a "strong safety constraint" type, ensuring that operation of one component requires the other to be in a safe state.

[0076] S23. Generate a node dependency graph based on operation dependencies.

[0077] After mapping the operational dependencies, the system constructs a Directed Acyclic Graph (DAG), or node dependency graph, using each component node as a vertex and operational dependencies as directed edges. This graph is stored in memory using an adjacency list or edge list structure and supports dynamic updates. An example of a dynamic update is removing satisfied dependency edges after an operation is completed. The generated dependency graph is not only used for real-time operation verification but also serves as a basis for task guidance, automatically highlighting currently operable nodes.

[0078] In some embodiments, step S21, which involves parsing the metadata of the perspective-enhanced 3D device model and identifying the physical connection relationships between the component nodes, may further include:

[0079] S211. Read the assembly interface attributes of each component node. The assembly interface attributes include interface type, spatial coordinates, normal vector and number of fasteners.

[0080] S212. When the interface types of two components match, the spatial distance is less than the distance threshold, and the normal vectors are opposite and parallel, it is determined that there is a physical connection between the two.

[0081] Specifically, each equipment component is assigned structured assembly interface attributes during the modeling phase, including interface type, spatial coordinates, normal vector, and number of fasteners. For example, the interface type can be flange, thread, snap-fit, or electrical plug; the spatial coordinates can be based on the equipment's global coordinate system; the normal vector represents the interface orientation; and the number of fasteners can include the number of bolt holes. For example, after the system loads the model, it iterates through all component nodes and performs geometric matching checks on any two components: first, it verifies whether their interface types are compatible (e.g., flanges only match flanges); second, it calculates the Euclidean distance between the center points of their interfaces. If it is less than a preset distance threshold, such as 3mm, it can be dynamically configured according to the equipment's precision; third, it further determines whether the normal vectors of the two interfaces are approximately opposite and parallel (e.g., the included angle can be preset to less than 5° to confirm that the components are in the correct docking posture). Only when all three conditions are met simultaneously does the system determine that the two components have a valid physical connection.

[0082] In some embodiments, step S22, which maps physical connections to operational dependencies according to preset industrial operating specifications, includes:

[0083] S221. If the first component blocks the disassembly path of the second component, then add a directed edge from the first component to the second component in the node dependency graph.

[0084] S222. If there is an electrical interlock between the two components, add a bidirectional dependency edge and mark it as a "strong safety constraint" type.

[0085] Specifically, after obtaining the physical connections between components, the system further maps these physical connections into dependencies with operational semantics based on preset industrial operation specifications, thereby constructing a node dependency graph that conforms to the logic of real-world operations. More specifically, the system has a built-in configurable operation rule base, which defines various dependency generation strategies according to industry standards (such as electrical safety work procedures and mechanical assembly manuals). For example, when the system detects that the first component completely blocks the disassembly path of the second component in space, it automatically adds a directed edge from the first component to the second component in the node dependency graph, indicating that "the first component must be removed or moved before the second component can be operated." Furthermore, when there is an electrical interlocking mechanism between two components, such as the mechanical or electrical interlock between a disconnector and a grounding switch, the system adds a bidirectional dependency edge between them and marks the edge as a "strong safety constraint" type, meaning that the operation of either component requires the other to be in a specific safety state, such as "disconnector open" and "grounding switch closed."

[0086] In some embodiments, step S3, which determines whether the preconditions for the operation of the target node are met based on the node dependency graph when any student client initiates an operation request to the target node, includes:

[0087] S31. Obtain all the preceding dependent nodes of the target node in the node dependency graph;

[0088] S32. Check whether the current state of each preceding dependent node conforms to the preset completion state;

[0089] S33. The prerequisite condition is satisfied only if all the preceding dependent nodes are in the completed state.

[0090] When a student initiates an operation request for a device component through the client, the server does not immediately execute the operation. Instead, it first performs precondition verification based on the constructed node dependency graph. Specifically, the system first traverses all incoming edges of the target node in the dependency graph to obtain all its precondition dependent nodes. These nodes represent related components that must complete the operation first. For example, in a power system simulation, the preconditions for operating a grounding switch may include the corresponding circuit breaker, which must be in the open state, and the upstream disconnecting switch, which must be disconnected. Subsequently, the system checks the current operating status of each precondition dependent node one by one to determine whether it meets the preset "completion status": for power supply nodes (such as circuit breakers and switches), the completion status is usually "power off" or "open"; for mechanical fastening nodes (such as bolts and clips), the completion status is "loosened" or "removed"; for isolation nodes (such as grounding switches), the completion status is "reliably grounded". The system only determines that the current operation request meets the preconditions and allows execution to continue when all prerequisite nodes are in their corresponding completed states; otherwise, it is considered an illegal operation and is blocked. In other words, the method in this embodiment transforms teaching rules into real-time, automatic logical verification. The system can accurately identify violations before operation execution, effectively avoiding serious misoperations such as "connecting a grounding wire while the circuit is live." This not only ensures the safety and logical consistency of the simulation process but also provides trainees with immediate and clear operational feedback, strengthening their understanding and memorization of the correct process flow.

[0091] In some embodiments, step S4 of determining the set of nodes requiring mutual exclusion protection based on the node dependency graph includes:

[0092] S41. Identify all descendant nodes of the target node in the node dependency graph and form the first mutually exclusive subset;

[0093] S42. Query the preset domain security rule base. If the target node has preset security sensitive attributes, then according to the domain security rule base, determine the associated device nodes that are in the same security isolation area as the target node and have no dependency relationship with the target node in the node dependency graph, and form the second mutually exclusive subset.

[0094] S43. Take the union of the first mutually exclusive subset and the second mutually exclusive subset as the final set of mutually exclusive protected nodes.

[0095] When a user gains access to a target node, the system doesn't simply lock the node itself. Instead, it dynamically determines a complete set of mutually exclusive protected nodes based on the node dependency graph to prevent state conflicts caused by concurrent operations from multiple users. This process has two levels: First, starting with the target node, the system performs a breadth-first traversal in the node dependency graph to identify all its direct and indirect descendant nodes—nodes that are logically affected by the target node's operations. For example, disassembling the main busbar will render all connected feeder switches inoperable, thus forming the first mutually exclusive subset. Second, the system further queries a pre-defined domain safety rule base (which can be configured for industries such as power, chemical, and rail transportation). If the target node is marked as having "safety-sensitive attributes" (such as high-voltage energization, flammable media, high-speed rotation, etc.), then, according to the safety isolation strategy defined in the rule base, it identifies other equipment nodes that are in the same safety isolation area but have no dependency path in the node dependency graph. These include other switchgear in the same busbar segment, adjacent equipment in the same explosion-proof zone, etc., and these nodes are included in the second mutually exclusive subset. Ultimately, the system takes the union of the first and second mutually exclusive subsets as the complete mutual exclusion protection range for this operation, and sends mutual exclusion commands to all clients in the room via the communication server, prohibiting other trainees from initiating operations on any node within the set. Understandably, even if the devices operated by two trainees are not directly related in assembly, because they belong to the same electrical isolation zone, the system can still automatically implement linked locking according to safety rules.

[0096] In some embodiments, step S5 includes:

[0097] S51. Generate an incremental state package, which contains only a list of node IDs that have changed, the new state value of each node, and a list of dependent edges that have been added, deleted, or modified in the node dependency graph.

[0098] S52. Use a reliable and ordered transmission protocol to send incremental state packets to all clients, ensuring that each client applies state changes in the same order.

[0099] Specifically, to ensure consistency of client states during multi-user collaborative operations, the system does not broadcast the entire device model data after each legitimate operation. Instead, it generates a lightweight incremental state packet for synchronization. This incremental state packet contains only three types of information: first, a list of changed node IDs, identifying which component states have been updated; second, the new state values ​​for each node, including attributes such as visibility, spatial pose, and connection status; and third, the topology changes in the node dependency graph caused by the operation, specifically manifested as a list of added, deleted, or modified dependency edges. For example, when a student completes the operation of "opening the No. 1 isolating switch," the system only marks the state of that switch node as "open," removes the "prohibited operation" dependency edge between it and the downstream grounding switch, and packages these changes to avoid transmitting data from hundreds of other unaffected components. Subsequently, this incremental state packet is sent to all clients in the collaborative room via a reliable ordered transmission protocol through the communication server. The transmission protocol can use a custom ordered message channel based on TCP or a reliable UDP transmission mechanism with sequence numbers. After receiving the message, each client applies the state change in strict order according to the sequence number. This ensures that even in the event of network jitter or message out-of-order delivery, the final device state and dependencies of all terminals are completely consistent. This effectively avoids the bandwidth waste and latency issues caused by using full synchronization, and helps improve system response speed and smoothness of collaboration.

[0100] In some embodiments, step S6, which involves reverting the state of the perspectived 3D device model to the nearest valid state under the node dependency graph constraints, further includes:

[0101] Before each legitimate operation is executed, a composite snapshot containing the global state of the device model and the version number of the node dependency graph is generated, and the composite snapshot is bound to the operation transaction ID and stored.

[0102] When an illegal operation occurs, the current transaction is terminated, and a composite snapshot corresponding to the ID of the most recent legal transaction is loaded to restore the model state and dependency graph topology in one go.

[0103] In detail, to ensure a rapid and complete restoration of the device model to a valid state in the event of an illegal operation, the system automatically generates a composite snapshot containing the global state of the device model and the topology of the node dependency graph before each valid operation is executed. This composite snapshot records not only the current attributes of each component node (such as spatial coordinates, visibility, connection status, operation flags, etc.), but also the complete set of edges in the node dependency graph and their version numbers, used to identify the current evolution stage of the dependency relationship. After the snapshot is generated, it is immediately bound to a uniquely assigned operation transaction ID and stored in the memory state stack of the collaboration room. For example, when an operation request initiated by a student is determined to be illegal, the system immediately terminates the current operation transaction and retrieves the composite snapshot corresponding to the most recent valid transaction ID from the state stack. Subsequently, the system restores the model state and dependency graph topology recorded in the snapshot all at once, ensuring that not only the appearance and component states of the device are reverted, but also its internal operational logic constraints are synchronously restored to a consistent state. By setting up the above technical solution, it is possible to effectively prevent the system from only rolling back the model state while ignoring the synchronization of the dependency graph. This prevents the hidden error of "the model seems normal, but the subsequent operation logic is chaotic", thus avoiding incorrect teaching for students in the future.

[0104] In some embodiments, the three-dimensional simulation control method for industrial equipment may further include:

[0105] S7. Record the user ID, target node, operation time, dependency verification result, operation success status, and status change details for each operation request to form a structured operation log;

[0106] S8. Align the structured operation log with the audio and video streams recorded in the room by timestamp;

[0107] S9. Based on operation logs, automatically calculate operation compliance scores. The compliance scores are generated by weighting the number of dependency violations, operation path redundancy, and task completion time.

[0108] In detail, the system synchronously records structured operation logs during collaborative operations for subsequent review and automated evaluation. Whenever a student initiates an operation request, regardless of success or failure, the server generates a log record. This log includes the user's unique identifier, target node ID, operation timestamp, dependency verification result (pass or fail), whether the operation was actually executed, and details of key state changes in the device model before and after the operation (such as node state, changes in dependent edges, etc.). This log is stored in a structured format (such as JSON or database records) and time-aligned with the synchronously recorded audio and video streams within the collaborative room. Specifically, a unified system clock source is used to accurately timestamp log events and video frames, ensuring precise location of specific actions during playback, such as "a student clicked on the grounding switch at 2 minutes and 15 seconds of the video, but was rejected because the preconditions were not met." Based on this, the system further automatically calculates the student's operation compliance score based on the operation logs.

[0109] In this embodiment, the scoring model comprehensively considers three core indicators: the number of times dependency order is violated (e.g., the number of times forced operations are rejected), the redundancy of the operation path (e.g., multiple steps can be combined into one), and the task completion time (time deviation relative to the standard process). These are weighted according to preset weights to generate the final score. In this embodiment, by transforming the operation process into quantifiable, traceable, and backtrackable data assets, not only is the burden of manual review for instructors significantly reduced, but objective and accurate feedback is also provided to students. Of course, it is understandable that the scoring model's score can only be used as reference data. That is, when students perform operations, teachers can subjectively score based on the students' actions. This allows for both systematic objective scoring and subjective scoring by the teacher. Finally, the final score is obtained by combining subjective and objective scores based on the actual situation. This avoids the weak authority of the score due to incomplete coverage of preset system scoring items, and also avoids unfair scoring behavior by teachers who are overly subjective.

[0110] Please see Figure 1 and Figure 2 In some embodiments, this application also provides a three-dimensional simulation control system for industrial equipment, including:

[0111] Room management module 100 is used to create collaborative rooms on the server side and load a unified perspective 3D device model;

[0112] The dependency graph construction module 200 is used to construct a node dependency graph based on the assembly dependency relationship between various components in the perspective 3D device model. The node dependency graph is used to constrain the disassembly and assembly order of component nodes.

[0113] The operation verification module 300 is used to determine whether the operation preconditions of the target node are met based on the node dependency graph when any student client initiates an operation request to the target node.

[0114] The mutual exclusion control module 400 is used to grant the student the right to operate on the target node when the operation verification module determines that the preconditions are met, and to determine the set of nodes that need to be mutually protected based on the node dependency graph, so as to prevent other students from operating any node in the set at the same time.

[0115] The state synchronization module 500 is used to broadcast the operation results and the updated node dependency status to all clients in the collaboration room after the operation is completed, so as to synchronize the device model status.

[0116] The state rollback module 600 is used to reject the operation request when the operation verification module determines that the preconditions are not met, and roll back the state of the perspectived 3D device model to the nearest legal state under the node dependency graph constraints.

[0117] In detail, the industrial equipment 3D simulation control system is deployed on the server side and adopts a modular architecture. The various functional modules work together to achieve safe operation control under multi-person collaboration. Among them, the room management module is responsible for responding to training task requests, creating independent collaborative rooms on the communication server, which can be implemented based on Docker containers, and loading a unified perspective 3D equipment model from the model resource library during room initialization to ensure that all participants operate on the same data source.

[0118] The dependency graph construction module, after the model is loaded, parses the assembly relationships between its components and, combined with preset industrial operation specifications, automatically generates a node dependency graph to constrain the operation sequence, maintaining it within the room's operational context. When any student client initiates an operation request, the operation verification module immediately intervenes, determining whether the operation meets all preconditions based on the current node dependency graph. If verification passes, the mutual exclusion control module grants the operation right and, based on the dependency graph, determines the set of nodes requiring mutual exclusion protection, issuing locking commands to other clients. If verification fails, the state rollback module is triggered, restoring the model to its most recent valid state. After the operation is completed, the state synchronization module is responsible for broadcasting the changes incrementally to all clients, ensuring consistency across multiple terminals. All of the above modules run on a high-concurrency communication server and collaborate efficiently through memory sharing and message queues.

[0119] In summary, the control system provided in this embodiment effectively solves the technical problems of frequent illegal operations and chaotic model states caused by the lack of operation sequence constraints in existing multi-user 3D simulation systems. This is achieved by constructing a node dependency graph based on the assembly dependencies of equipment components on the server side, using this graph as the core basis for collaborative operation control. Specifically, when any student initiates an operation request, the system dynamically verifies whether the preconditions are met based on the node dependency graph, granting operation rights only when they are legal. The system also automatically determines the set of nodes requiring mutual exclusion protection based on this dependency graph, thereby ensuring operational compliance while preventing state conflicts caused by concurrent operation by multiple users. If an operation request violates dependency constraints, it is immediately rejected, and the equipment model state is automatically rolled back to the most recent legal state allowed by the node dependency graph, ensuring that the simulation process is always in a logically consistent and reliable state. Simultaneously, after each legal operation is completed, the system broadcasts the operation result and the updated dependency state to all clients in real time, achieving strong consistency and synchronization of model states across multiple clients. Therefore, this application not only eliminates high-risk violations such as "live disassembly" and "unisolated operation", which helps to improve the safety and standardization of industrial simulation training, but also achieves a highly reliable and consistent multi-person collaborative operation experience through a dependency-driven dynamic mutual exclusion and automatic rollback mechanism.

[0120] Based on the above method embodiments, this application also provides a storage medium, which is a computer-readable storage medium. The storage medium stores a computer program, which, when run by a processor, executes the above method embodiments. Specifically, the storage medium can be a general-purpose storage medium, such as a removable disk or hard disk, and the computer program on the storage medium, when run, can execute the methods described in the above embodiments.

[0121] Based on the above method embodiments, this application also provides a computer program product, including computer instructions, which, when run on an industrial equipment three-dimensional simulation control system, enable the system to execute the above-described industrial equipment three-dimensional simulation control method embodiments.

[0122] Please see Figure 1Regarding all the technical solutions described above, it can be understood that each student will have a client application for practice, while backend personnel, teachers, or other administrators can manage the data from multiple clients and other system settings in real time through the management backend webpage. The database server and communication server in the system are interconnected, and both can be configured with backup servers for unforeseen circumstances. For example, a backup database server and a backup communication server can be configured. The database server can connect to the management backend webpage and client applications via a local area network (LAN), and similarly, the communication server can also connect to the management backend webpage and client applications via a LAN. Communication between LANs can also be achieved by configuring hardware devices such as switches and routers.

[0123] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A three-dimensional simulation control method for industrial equipment, characterized in that, include: Create a collaborative room on the server side and load a unified perspectived 3D device model; Based on the assembly dependency relationships between the components in the perspectived 3D device model, a node dependency graph is constructed, which is used to constrain the disassembly and assembly sequence of component nodes. When any student client initiates an operation request to the target node, the node dependency graph is used to determine whether the operation preconditions of the target node are met. If the conditions are met, the student is granted the right to operate on the target node, and a set of nodes that need to be mutually exclusive is determined based on the node dependency graph, preventing other students from operating on any node in the set at the same time. After the operation is completed, the operation results and the updated node dependency status are broadcast to all clients in the collaborative room to synchronize the device model status. If the aforementioned preconditions are not met, the operation request is rejected, and the state of the perspectived 3D device model is reverted to the most recent valid state under the node dependency graph constraints.

2. The industrial equipment three-dimensional simulation control method according to claim 1, characterized in that, The step of constructing a node dependency graph based on the assembly dependency relationships between components in the perspectived 3D device model includes: The metadata of the perspectived 3D device model is parsed to identify the physical connection relationships between the nodes of each component; According to the preset industrial operation specifications, the physical connection relationship is mapped into an operation dependency relationship; A node dependency graph is generated based on the operational dependencies.

3. The industrial equipment three-dimensional simulation control method according to claim 2, characterized in that, The step of parsing the metadata of the perspectived 3D device model and identifying the physical connection relationships between the component nodes includes: Read the assembly interface attributes of each component node, including interface type, spatial coordinates, normal vector and number of fasteners; When two components have matching interface types, a spatial distance less than a distance threshold, and opposite parallel normal vectors, they are determined to have a physical connection.

4. The industrial equipment three-dimensional simulation control method according to claim 2, characterized in that, The step of mapping the physical connection relationship to an operational dependency relationship according to the preset industrial operation specifications includes: If the first component blocks the disassembly path of the second component, then add a directed edge from the first component to the second component in the node dependency graph; If the two components are electrically interlocked, add a bidirectional dependency edge and mark it as a "strong safety constraint" type.

5. The three-dimensional simulation control method for industrial equipment according to claim 1, characterized in that, The step of determining whether the preconditions for the operation of the target node are met based on the node dependency graph when any student client initiates an operation request to the target node includes: Obtain all the preceding dependent nodes of the target node in the node dependency graph; Check whether the current state of each preceding dependent node matches the preset completion state; The prerequisite condition is considered satisfied only if all preceding dependent nodes are in the completed state.

6. The industrial equipment three-dimensional simulation control method according to claim 1, characterized in that, The step of determining the set of nodes that need mutual exclusion protection based on the node dependency graph includes: Identify all descendant nodes of the target node in the node dependency graph, forming a first mutually exclusive subset; If the target node has a preset security sensitivity attribute, then according to the domain security rule base, determine the associated device nodes that are in the same security isolation area as the target node and have no dependency relationship with the target node in the node dependency graph, and form a second mutually exclusive subset. The union of the first mutually exclusive subset and the second mutually exclusive subset is taken as the final set of mutually exclusive protected nodes.

7. The industrial equipment three-dimensional simulation control method according to claim 1, characterized in that, Also includes: Record the user ID, target node, operation time, dependency verification result, operation success status, and status change details for each operation request to form a structured operation log; Align the structured operation log with the audio and video streams recorded in the room by timestamp; Based on the operation logs, an operation compliance score is automatically calculated. The compliance score is generated by weighting the number of dependency violations, operation path redundancy, and task completion time.

8. A three-dimensional simulation control system for industrial equipment, characterized in that, include: The room management module is used to create collaborative rooms on the server side and load a unified perspective 3D device model. The dependency graph construction module is used to construct a node dependency graph based on the assembly dependency relationships between the components in the perspectived 3D device model. The node dependency graph is used to constrain the disassembly and assembly order of the component nodes. The operation verification module is used to determine whether the operation preconditions of the target node are met based on the node dependency graph when any student client initiates an operation request to the target node. The mutual exclusion control module is used to grant the student the right to operate on the target node when the operation verification module determines that the preconditions are met, and to determine the set of nodes that need to be mutually excluded based on the node dependency graph, so as to prevent other students from operating any node in the set at the same time. The state synchronization module is used to broadcast the operation results and the updated node dependency state to all clients in the collaborative room after the operation is completed, so as to synchronize the device model state. The state rollback module is used to reject the operation request and roll back the state of the perspectived 3D device model to the nearest valid state under the node dependency graph constraints when the operation verification module determines that the preconditions are not met.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the industrial equipment three-dimensional simulation control method as described in any one of claims 1 to 7.

10. A computer program product, characterized in that, It includes computer program instructions, which, when executed by a processor, cause the processor to perform the industrial equipment three-dimensional simulation control method as described in any one of claims 1 to 7.

Images