An ar terminal live working virtual simulation teaching method and system supporting real-time collaboration

Abstract

The application discloses a kind of AR terminal live working virtual simulation teaching method and system supporting real-time cooperation, it is related to electric power operation simulation teaching technical field, the method includes, based on the preset live working teaching process, the task causal dependence graph atlas of node containing role responsibility and operation authority, edge containing causal dependence relationship and conditional expression;In multi-role AR virtual simulation training, real-time monitoring student initiatively initiated or system automatically detected role switching request;When responding to request, make causal integrity judgment in combination with atlas and current task state, and dynamically allocate the original role task responsibility, operation authority and context information to new role by later;Synchronous migration updates information to all AR terminals to keep state consistent, generate causal migration record containing trigger cause, migration role and the like and transmit to teacher end visual display and analysis.The application improves teaching collaboration coherence and safety, provides basis for teaching evaluation.

Description

Technical Field

[0001] This invention relates to the field of power operation simulation teaching technology, specifically to an AR terminal-based virtual simulation teaching method and system for live-line work that supports real-time collaboration. Background Technology

[0002] In the field of virtual simulation teaching for live-line work, AR terminals have become core equipment for multi-role collaborative training due to their immersive experience and real-time interactive features. In existing AR collaborative teaching systems, roles, operation permissions, and task responsibilities are usually fixed and bound during scene initialization, and the task execution process is also fixed according to a preset sequence.

[0003] However, in actual training, unexpected situations such as character offline, temporary support, and operation delays often occur. The existing system lacks the ability to dynamically adjust characters, which leads to the task dependency chain being broken after character switching. The new character cannot obtain the task context and progress information of the original character, and the instructions of other collaborating characters still point to the old character, causing confusion in the teaching logic.

[0004] Meanwhile, live-line work involves high-risk operations, and the existing system has not established a risk priority mechanism for operational safety regulations. During role migration, it is difficult to ensure the integrity of the causal chain of high-risk task nodes, which can easily lead to safety training hazards. Furthermore, the lack of traceable causal records during role switching makes it impossible for teachers to intuitively grasp the impact of the migration, hindering teaching evaluation and review, and seriously affecting the practicality and safety of virtual simulation teaching. Summary of the Invention

[0005] To address this, the present invention provides an AR terminal-based virtual simulation teaching method and system for live-line work that supports real-time collaboration, thereby solving the aforementioned technical problems.

[0006] According to one aspect of this application, an AR terminal-based virtual simulation teaching method for live-line work that supports real-time collaboration is provided, comprising the following steps: Based on the pre-set live-line work teaching process, a task causal dependency graph is constructed, where nodes represent work steps with clear role responsibilities and operating permissions, and edges represent the causal dependency relationships between steps with attached conditional expressions. During multi-role virtual simulation training via AR terminal, real-time monitoring is conducted on role switching requests initiated by trainees or detected automatically. In response to the role switching request, based on the task causal dependency graph and the current task execution status, a causal integrity judgment is performed, and after the judgment is passed, the original role's task responsibilities, operation permissions and task context information are dynamically reassigned to the new role. The updated information after the character migration is synchronized to all participating AR terminals in real time to maintain the consistency of task status and character identification on each terminal interface. Generate a causal migration record describing the role migration process. The record includes at least the triggering cause, the migrating role, the task nodes involved, and the impact on the causal chain. The record is then transmitted to the teacher's end for visualization and teaching analysis.

[0007] Preferably, according to the preset teaching script, the work process is broken down into multiple operation step nodes, and the required roles, prerequisites and postconditions are defined for each node. By analyzing the logical dependencies between operational steps, directional edges are established to connect relevant nodes, forming a directed graph structure that represents the task execution order and constraint relationships.

[0008] Preferably, the conditions for automatically detecting and triggering role switching include: detecting that a role is offline for a long time, the execution of the key task node it is responsible for is delayed, or detecting abnormal conflicts in the collaboration logic between multiple roles.

[0009] Preferably, all task nodes currently bound to the role to be migrated are extracted from the task causal dependency graph; Verify that the new role has the set of permissions required to perform these tasks, and check that all necessary prerequisite task nodes have been correctly completed by the corresponding role.

[0010] Preferably, if a prerequisite task that the original role is responsible for but has not yet been completed is found during the causal integrity judgment, a task handover confirmation instruction for the new role is automatically generated. Only after the instruction receives confirmation feedback on the AR terminal is the final transfer of permissions and responsibilities completed.

[0011] Preferably, the task context information includes the progress data of the current task, the viewpoint positioning information in the AR virtual scene, and the voice communication channel permissions bound to the specific task.

[0012] Preferably, when the result of the causal integrity judgment is that the migration will disrupt the task logic, the advancement of the affected task node is automatically paused, the role is locked, and an alarm message is sent to the teacher.

[0013] Preferably, the visualization display specifically involves rendering the causal path affected by this role migration event in the visualization graph of the task causal dependency graph using highlighting, animation, or color differentiation on the teacher's end interface, marking the role change points and maintaining a complete causal chain.

[0014] Preferably, the node attributes in the task causal dependency graph include risk level identifiers related to live-line work safety regulations. When making judgments in the causal reasoning and transfer steps, priority is given to ensuring the integrity of the causal chain of high-risk task nodes.

[0015] In another aspect, this application also provides an AR terminal-based live-line operation virtual simulation teaching system that supports real-time collaboration, comprising: The task causal dependency graph construction module is used to construct a task causal dependency graph based on a preset live-line operation teaching process. In this graph, nodes represent operation steps with clear roles, responsibilities, and operating permissions, and edges represent causal dependencies between steps with conditional expressions attached. The role switching request monitoring module is used to monitor role switching requests initiated by trainees or detected automatically in real time during multi-role virtual simulation training conducted through AR terminals. The causal integrity judgment and role migration module is used to respond to the role switching request, perform causal integrity judgment based on the task causal dependency graph and the current task execution status, and dynamically reassign the original role's task responsibilities, operation permissions and task context information to the new role after the judgment is passed. The update information synchronization module is used to synchronize the updated information after the role migration to all participating AR terminals in real time, so as to maintain the consistency of task status and role identification in the interface of each terminal. The migration record and analysis module is used to generate a causal migration record describing the role migration process. The record includes at least the triggering reason, the migrating role, the task nodes involved, and the impact on the causal chain, and is transmitted to the teacher's end for visualization and teaching analysis.

[0016] This invention constructs a task causal dependency graph containing role responsibilities and risk levels, and combines real-time role switching request monitoring and causal integrity judgment to achieve dynamic migration of the original role's task responsibilities, permissions, and context information to the new role. This ensures the priority integrity of the causal chain of high-risk nodes, avoiding task dependency chain breaks and confusion in teaching logic. At the same time, role migration update information is synchronized to all AR terminals in real time, ensuring that the interface status is consistent with the role identification, and generating traceable causal migration records that are visualized on the teacher's end. This not only improves the safety, collaborative continuity, and emergency adaptability of live-line operation virtual simulation teaching, but also provides a clear basis for teaching evaluation and review, effectively optimizing teaching effectiveness and system practicality. Attached Figure Description

[0017] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the accompanying drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, the elements or parts are not necessarily drawn to scale.

[0018] Figure 1A flowchart of a virtual simulation teaching method for live-line work using an AR terminal that supports real-time collaboration, provided as an embodiment of the present invention; Figure 2 This is a schematic diagram of the causal integrity determination process provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the role migration implementation process provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the task context information migration process provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of an AR terminal-based live-line operation virtual simulation teaching system that supports real-time collaboration, provided as an embodiment of the present invention. Detailed Implementation

[0019] 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, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] like Figure 1 As shown in the figure, this invention discloses a virtual simulation teaching method 100 for live-line work using an AR terminal that supports real-time collaboration, comprising the following steps: S1. Based on the preset live-line work teaching process, a task causal dependency graph is constructed, where nodes represent work steps with clear role responsibilities and operation permissions, and edges represent the causal dependency relationship between steps with attached conditional expressions. S2, during multi-role virtual simulation training via AR terminal, monitors in real time role switching requests initiated by trainees or detected automatically; S3, in response to the role switching request, based on the task causal dependency graph and the current task execution status, perform a causal integrity judgment, and after the judgment is passed, dynamically reassign the original role's task responsibilities, operation permissions and task context information to the new role. S4 synchronizes the updated information after the character migration to all participating AR terminals in real time to maintain the consistency of task status and character identification in the interface of each terminal. S5. Generate a causal migration record describing the role migration process. The record includes at least the triggering cause, the migrating role, the task nodes involved, and the impact on the causal chain. The record is then transmitted to the teacher's end for visualization and teaching analysis.

[0021] In some embodiments, for step S1, the complete live-line operation teaching process is discretized based on a preset live-line operation teaching script to ensure that each decomposed operation step node corresponds to a single and clear operation action, avoiding step overlap or functional ambiguity.

[0022] Specifically, the steps can be broken down according to industry standards and teaching objectives for live-line work. For example, the industry standard is the Low-Voltage Electrical Safety Work Procedure. Based on this standard, the low-voltage live-line maintenance process can be broken down into eight core operation steps: "Power Off Operation," "Voltage Verification Confirmation," "Electrical Grounding Wire Installation," "Equipment Fault Detection," "Equipment Repair," "Electrical Grounding Wire Removal," "Power Restoration," and "Work Site Cleanup." Each step contains only one core operation action. For example, the "Voltage Verification Confirmation" step only corresponds to the action of "using a voltage detector to check whether the equipment is powered off," and does not include the subsequent action of "recording the voltage verification result." The latter is included in the post-condition verification step of this step. Each decomposed operation step node is assigned a unique ID code, such as "DY-ZY-001" representing the "power-off operation" node in live-line work; at the same time, a node information table is established in the cloud database to store basic information such as node ID, operation name, and to which the operation module belongs, which facilitates subsequent map construction and node calling. For example, the operation module includes "safety preparation module", "maintenance execution module" and "completion module".

[0023] According to some embodiments of the present invention, multi-dimensional attribute definitions are performed for each split operation step node to ensure that the role, responsibility, and execution conditions of each node are clear and unambiguous. The specific implementation is as follows: Define the required roles. For example, based on the role division of live-line work, assign one or more required execution roles to each node. For instance, for the nodes of "power outage operation", "equipment fault detection", "equipment repair" and "power restoration", designate "operator" as the only required role, clearly defining that this role is responsible for performing specific operational actions; The "Electricity Verification Confirmation", "Grounding Wire Installation Confirmation", and "Grounding Wire Removal Confirmation" nodes designate "Supervisor" as the only required role, clearly defining this role as responsible for safety confirmation and supervision; For the "work site cleanup" node, "operator + supervisor" can be designated as the required roles, and it is clear that the two must work together to complete the on-site tool inventory and safety hazard investigation.

[0024] Additionally, in the attribute configuration interface, a "role priority" option can be set. If a node requires collaboration among multiple roles, the primary responsible role can be marked to provide a basis for subsequent responsibility allocation. For example, the primary responsible role for "work site cleanup" is "operator".

[0025] Define preconditions and postconditions. For preconditions, based on operational logic and safety regulations, clearly define the conditions that must be met before a node can be executed, and each condition must be associated with a specific verification subject and verification method. For example, the precondition for the "Power Verification Confirmation" node is "The operator has completed the 'power-off operation' and uploaded a power-off operation record via the AR terminal, specifically including the power-off time and a photo of the operated location; the AR system detects that the voltage value at the power-off location is lower than the safety threshold (≤36V)." Here, "Operator uploaded record" is submitted for verification by the operator through the AR interface, and "voltage value detection" is automatically collected and verified by the system. The prerequisite for the "grounding wire connection" node is that "the supervisor confirms the 'voltage verification' result is valid on the AR interface, and the AR system generates a voltage verification qualified report". The verification subjects are the supervisor and the system, and the verification method is interface confirmation and report generation.

[0026] Specifically, the definition of postconditions specifies the results to be achieved after a node is executed, and these results must be verifiable through the AR system or user interaction. For example, the postcondition for the "grounding wire connection" node is: "The AR system detects that the grounding wire is securely connected to the grounding electrode, and it can simulate the detection through virtual force feedback; the monitor records the grounding wire connection location and quantity on the AR interface." The postconditions for the "Equipment Maintenance" node are: "The operator submits a maintenance record, including the cause of the fault, the parts to be repaired, and the test data; the AR system simulates the equipment operation test and displays the result of 'operating normally'."

[0027] Define risk levels and safety constraints. For example, referencing live-line work safety regulations, label each node with a risk level and configure corresponding safety constraint rules to provide a basis for prioritizing subsequent causal reasoning. For instance, the nodes "connecting grounding wires," "removing grounding wires," and "restoring power supply" are labeled "high risk," and the safety constraint rule is "must be supervised by a monitor throughout the process, and the AR system must monitor the operation procedures in real time. If a violation is detected, an audible and visual alarm will be triggered immediately." The operation procedures include, for example, the order of grounding wire connection and line inspection before restoring power supply. The "Electricity Verification Confirmation" and "Equipment Fault Detection" nodes are marked as "Medium Risk". The safety constraint rule is that "operators must check the electricity verification points in sequence according to the prompts on the AR interface. If any point is missed, the results cannot be submitted." The "Work Site Cleanup" node is marked as "Low Risk" and the safety constraint rule is that "tools must be inventoried and the inventory results must match the initial tool list; otherwise, the node cannot be marked as completed."

[0028] According to some embodiments of the present invention, directed edge construction is achieved by sorting out the logical dependencies between nodes of each operation step, constructing directed edges to connect related nodes, and forming a directed graph structure of task execution order and constraint relationships. The specific implementation is as follows: First, the dependencies are analyzed. Specifically, the forward process traversal follows the natural execution order of the operations, such as "power off → power test → grounding → maintenance → grounding removal → power restoration", to initially determine the sequential relationship between nodes. The reverse constraint verification is based on safety regulations and operational logic to supplement implicit dependencies. For example, the forward traversal determines that "power test confirmation" is after "power off operation", and the reverse verification supplements that "power test confirmation" must be before "grounding wire connection", to avoid the violation of skipping power test and directly connecting the grounding wire. The forward traversal determines that "equipment maintenance" is performed after "grounding wire installation," while the reverse verification confirms that "equipment maintenance" must be performed before "grounding wire removal" to avoid the risk of electric shock caused by accidentally removing the grounding wire during maintenance.

[0029] Next, directed edges are generated for the analyzed and confirmed dependencies. For example, directed edges suitable for linear process dependencies, such as "power off → power test → grounding", are automatically constructed, and then directed edges are automatically generated between adjacent nodes according to the process order when the nodes are split. Meanwhile, each directed edge is assigned a unique ID, such as “DY-B-001”, which represents the edge from “power off operation” to “power verification confirmation” in live-line work. The edge attributes are marked with dependency types, specifically “mandatory dependency” and “optional dependency”. “Mandatory dependency” means that the target node can only be executed after the source node is completed, such as “power verification confirmation” depending on “power off operation”. “Optional dependency” means that the target node can be executed after any of the multiple source nodes is completed, such as “work site cleanup” can be executed after “power restoration” or “equipment maintenance record submission”.

[0030] According to some embodiments of the present invention, a conditional expression is appended to each directed edge to describe the context conditions under which the target node can be executed, ensuring that the target node can only switch from the "pending execution" state to the "executable" state when the conditions are met. The specific implementation is as follows: First, define the expression syntax, specifically using the syntax format of "logical operator + condition factor," where the condition factor originates from the node's precondition verification result, role operation status, system detection data, etc. For example, the condition factor can be represented as "[node ID].precondition.verification result (success / failure)", "[role ID].operation status (complete / incomplete)", or "[system detection item].value".

[0031] Next, conditional expressions are written. Specifically, based on the dependencies and safety specifications corresponding to the directed edges, conditional expressions are written. For example, the conditional expression for the directed edge from "Power Off Operation" to "Voltage Verification Confirmation" is "(DY-ZY-001.Precondition.Verification Result = Success) AND (Operator.Operation Status = Completed) AND (System Detection.Voltage Value of Power Off Location ≤ 36V)", where the node ID of "Power Off Operation" is DY-ZY-001, the node ID of "Voltage Verification Confirmation" is DY-ZY-002, and the ID of the directed edge is DY-B-001.

[0032] In some embodiments, for step S2, a "role switching request" function module is set in the interactive interface of the AR terminal, and the student initiates a role switching request through voice command or gesture operation. For example, the voice command can be "request to switch to guardian", and the gesture operation can be "double-click the character icon on the AR interface".

[0033] The AR terminal will encrypt the request information, including the initiating student ID, current role, and target role, and upload it to the cloud system in real time. The cloud system will verify the format of the request information and mark it as "pending active switching request" after confirming that the information is complete.

[0034] According to some embodiments of the present invention, the system automatically triggers the conditions for monitoring role switching. For example, a timed heartbeat packet communication mechanism is established between the cloud system and each AR terminal. The AR terminal sends a heartbeat packet to the cloud system every 10 seconds. If the cloud system fails to receive a heartbeat packet from an AR terminal for three consecutive times and confirms through backup network detection that the terminal has no network connection, it determines that the role corresponding to the terminal is "offline for a long time" and triggers the automatic switching process. The heartbeat communication cycle can be configured according to the training scenario, with a minimum of 5 seconds and a maximum of 30 seconds; the number of times the heartbeat packet was not received in the offline confirmation condition can be configured, with a default of 3 times; the means of detection through the backup network include trying to ping the terminal IP address.

[0035] For example, based on the timing requirements of nodes in the task causal dependency graph, the estimated execution time of each critical task node is set, such as "power verification confirmation" with an estimated execution time of 5 minutes. If it is detected that the actual execution time of a node under the responsibility of a certain role exceeds the estimated time by 150%, and no reason for the delay is received from that role, such as "device detection abnormality", then it is determined to be "critical task node execution lag", triggering automatic switching; For example, real-time analysis of interaction data between multiple roles can detect command conflicts between roles, such as an operator initiating a "restore power" request while the supervisor has not completed the "confirmation of grounding wire removal"; or a role failing to respond to collaboration commands three times in a row, such as the supervisor not confirming the operator's "maintenance completed" feedback, which is determined to be an "abnormal conflict in collaboration logic" and triggers automatic switching.

[0036] In some embodiments, for step S3, such as Figure 2 As shown, the determination of causal integrity includes the following steps: S201, filter the task nodes to be migrated based on the task causal dependency graph and the current task execution status; specifically, using the current role identifier of the role to be migrated as an index, traverse the task causal dependency graph to locate all task nodes that the role is already bound to, which may include, Current execution node: The node that the AR terminal reports in real time and that the role to be migrated is currently operating, such as the "electricity verification confirmation" node that the supervisor is currently executing; it can be quickly identified through the node status field, such as pending execution, in execution, or completed; Subsequent nodes to be executed: Nodes in the causal graph that have a direct downstream dependency relationship with the current node to be executed, such as the "grounding wire" node after "power verification confirmation"; and related nodes of downstream nodes, such as the "equipment maintenance" node after "grounding wire"; these can be obtained by traversing the target nodes of directed edges. High-risk associated nodes: Regardless of whether they are already bound, any high-risk nodes that have a causal dependency on the node to be migrated, such as "Restore Power Supply" and "Remove Grounding Wire" nodes, will be forcibly included in the extraction scope and filtered by "Risk Level = High" in the node attributes.

[0037] The extracted nodes are sorted by priority: currently executing, high-risk follow-up, and normal follow-up, generating a list of task nodes to be migrated. The list includes node ID, node name, required permissions, prerequisite dependent nodes, and risk level, providing a basis for subsequent verification.

[0038] S202, Verify the new role's permissions and prerequisites. The verification of new role permissions includes retrieving the new role's preset permission set and comparing it with the required permissions of each node in the list of task nodes to be migrated. The role's permission set is stored in the role management database and includes operation permissions, data viewing permissions, communication permissions, etc. Specifically, if the new role's permission set completely covers the permissions required by all nodes, such as the "grounding wire" node requiring "security confirmation permission" and "virtual device operation permission", and the new role has both, then the permission verification is deemed successful; if there are missing permissions, such as the new role not having the "operation confirmation permission" for the high-risk node "restoring power", then the permission verification is deemed unsuccessful, triggering an exception handling process, such as prompting the teacher to temporarily grant permissions; The precondition verification process includes extracting all preconditions of the node to be migrated based on the task causal dependency graph. Specifically, this can be obtained through the "preconditions" field in the node attributes. Then, the execution status of each precondition is checked. Specifically, if the status of the preceding node is "completed" and the completing role is consistent with the preset role in the diagram, such as the "voltage verification confirmation" of the preceding node for "grounding wire connection" being completed by the supervisor, which is consistent with the preset role, then the preceding node is deemed to have passed the verification. If the status of the preceding node is "in execution" or "pending execution", or the completion role is inconsistent with the preset, such as "power verification confirmation" being completed by the operator, while the preset requires the supervisor to complete it, then the preceding condition verification is deemed to have failed. Preferably, in some embodiments, during the verification process, the preconditions for high-risk nodes are processed first. If the preconditions for a high-risk node are not met, the causal integrity judgment is directly determined to have failed. For example, the high-risk node is "restoring power supply," and its precondition is "removing the grounding wire."

[0039] S203, Handover confirmation processing for incomplete prerequisite tasks, includes the generation, sending, and feedback reception of handover confirmation instructions. Specifically, if the verification reveals that the original role was responsible for but has not yet completed a prerequisite task, such as the original operator not completing the final record of the "power outage operation," a task handover confirmation instruction is automatically generated. For example, the instruction content includes details of the incomplete prerequisite task and confirmation requirements; the prerequisite task details include the task name, incomplete items, and operation guidelines; the confirmation requirements may require the new role to click "Confirm Understanding" on the AR interface.

[0040] After the new character completes the "Confirm Understanding" operation on the AR interface, the terminal will upload feedback information including the confirmation time and the new character's ID to the cloud. If the new character does not respond within 10 minutes, the system will automatically push the instruction repeatedly. If there is still no response, the teacher will be triggered to intervene. The maximum number of times the instruction can be pushed repeatedly is 3. After receiving confirmation feedback, the cloud system updates the status of the preceding task node to "awaiting new role follow-up", determines that the causal integrity judgment has passed, and triggers the subsequent role migration process.

[0041] According to some embodiments of the present invention, such as Figure 3 As shown, the implementation of role migration specifically includes task responsibility migration, operation permission migration, and task context information migration. Specifically, for task responsibility migration: S301, update the binding relationship between nodes and roles in the task causal dependency graph: remove the original role ID from the "currently responsible role" field of the node, replace it with the new role ID, and mark the "migration time"; The task assignment interface of the AR terminal is updated synchronously. The new role terminal displays a list of task nodes to be migrated, marked with "New Responsible Tasks"; other collaborating role terminals display "Role Change Notification", such as "The guardian has been changed to student B, and he will be responsible for subsequent safety confirmation".

[0042] Specifically, regarding the migration of operational permissions: S302, revoke the original role's temporary operational permissions in the node to be migrated, such as the permissions for "grounding wire connection confirmation" and "voltage testing data entry"; at the same time, grant the corresponding permissions to the new role, with the permission taking effect at the same time as the responsibility migration. Preferably, when a new user operates a high-risk node for the first time, they need to enter a verification code on the AR interface. Only after successful verification can the operation be performed. This verification code is generated in real time by the teacher.

[0043] S303 involves the migration of task context information, including the progress data of the current task, the viewpoint positioning information in the AR virtual scene, and the voice communication channel permissions bound to a specific task.

[0044] Specifically, such as Figure 4 As shown in S3031, for the migration of current task progress data, real-time progress data of the nodes to be migrated is collected from the original character's AR terminal and stored according to node ID; the progress data is pushed to the new character's AR terminal, and the terminal displays the progress synchronously on the task interface, ensuring that the new character does not need to start the operation again. For example, the real-time progress data shows that "electricity verification" has been completed for 2 out of 3 testing points, and "grounding wire has been installed" for 1 grounding wire.

[0045] For example, the progress can be displayed as a progress bar or a completed checkpoint marker.

[0046] S3032, for the migration of AR virtual scene view positioning information, the original character's AR terminal records the current virtual scene view parameters, including view position, viewing angle, and zoom ratio, such as "1 meter in front of the power distribution cabinet, eye level, zoom 100%"; and then converts it into general coordinates through a spatial coordinate transformation algorithm. After the new character's AR terminal receives the coordinate parameters, it automatically adjusts the virtual scene perspective to match the original character's perspective, thus avoiding operational errors caused by perspective deviation, such as not being able to find the virtual grounding wire mounting point.

[0047] S3033, For the migration of voice communication channel permissions, revoke the original role's permissions in the exclusive voice channel of the node to be migrated, and add the new role to the channel; For example, this dedicated voice channel is the "operator-monitor safety confirmation channel".

[0048] This allows for the simultaneous retention of historical voice recordings from the original channel, such as the most recent 30 minutes. New users can click "Historical Voice Replay" on the AR interface to review previous collaboration information. For example, this historical voice recording includes the safety confirmation dialogue between the original supervisor and the operator.

[0049] Preferably, in some embodiments, high-risk nodes, such as "grounding" and "restoring power supply," are always considered as core protection targets during causal reasoning and migration. Specifically, when extracting nodes, high-risk nodes are prioritized for inclusion in the migration list; during permission and precondition verification, migration is terminated directly if a high-risk node fails. During migration, the responsibilities, permissions, and context information of high-risk nodes are migrated first. For example, the permission migration of the "Restore Power" node takes ≤1 second.

[0050] Preferably, in some embodiments, after the high-risk node migration is completed, the upstream and downstream dependencies of the node are retraced, such as the upstream "removal of grounding wire" and the downstream "confirmation of work completion" for "restoring power". Then it is confirmed that the causal connection between the node and its upstream and downstream is not interrupted, such as "restoring power" still depends on "removal of grounding wire" to be completed. If the verification detects a broken causal chain, a rollback will be automatically triggered, and an alarm message will be sent to the teacher's end. If the verification finds that the dependency relationship between "restoring power" and "removing the grounding wire" is lost, the original role binding will be automatically restored, and an alarm message will be sent to the teacher's end.

[0051] In some embodiments, for step S4, after completing the role migration, the cloud system generates a role migration update data package, which includes the updated role-node binding relationship, the permission status of each node, and task progress data. The data package is then broadcast to all participating AR terminals via edge computing nodes, specifically including the terminal that initiated the switch, the new role terminal, and other collaborating role terminals. Upon receiving the data package, each AR terminal automatically updates its local interface display, which may include... Character identifier update: For example, the "Online" icon next to the original character name will be changed to "Switched", and the new character name will be marked with "Currently in charge"; Task status update: such as synchronizing the progress of the new role's responsible node in the task progress bar and marking it as "Pending execution by new role"; Permission interface update: In the operator AR interface, only the "Safety Confirmation" button for the new guardian will be displayed, while the relevant interaction entry points for the original guardian will be hidden. If a terminal fails to receive data during the synchronization process, the cloud system will re-push the data packet until all terminals report "Synchronization Complete".

[0052] In some embodiments, for step S5, the cloud system automatically generates a structured causal migration record after the role migration is completed. For example, the record content includes at least: Triggering reason: Mark "Active request" or "Automatic trigger". For automatic triggers, please provide a specific reason, such as "Character is offline". Migrating Roles: Record the original role ID / name and the new role ID / name, such as "Original Guardian: Student A, New Guardian: Student B"; Task nodes involved: List all relevant nodes extracted and their risk levels, such as "Electricity verification confirmation (medium risk), Grounding wire connection (high risk)"; Causal chain impact: Describes the impact of migration on the causal chain, such as "After migration, the causal chain of 'voltage verification → grounding wire connection' remains intact without any interruption at any node"; Migration time: The start and end times of the migration are accurate to the second.

[0053] Once the record is generated, it is stored in the system log database and simultaneously pushed to the teacher's system.

[0054] According to some embodiments of the present invention, preferably, after receiving the causal migration record, the teacher implements visualization rendering in the teaching monitoring interface, specifically including: Graph Highlighting: In the visualization of the task causal dependency graph, the task nodes involved in the migration are highlighted in red, and the role binding relationship before and after the migration is marked with yellow arrows, such as "original guardian → power verification confirmation" being changed to "new guardian → power verification confirmation"; the visualization image can be in the form of a flowchart. Animation demonstration: The animation effect simulates the character migration process. For example, a flashing icon indicates that the original character has left the node, and the new character icon moves to the corresponding node and stays there. At the same time, a "migration successful" message is displayed. Color coding: Green indicates "maintaining a complete causal chain," such as "power off operation → power verification → grounding wire connection"; gray indicates "causal chains not involved," helping teachers quickly identify the scope of the migration impact. Teachers can click on nodes in the visualization to view the migration details of that node, such as permission change records and handover confirmation information.

[0055] According to some embodiments of the present invention, preferably, when the causal integrity judgment result is that migration will disrupt the task logic, such as when the new role does not have the operation permission to "connect to the ground wire" of high-risk nodes, and there is no other role that can temporarily replace it, the following operations are performed: Send a "task lock command" to all AR terminals to pause the affected task nodes. The AR interface displays a message that "task is locked, waiting for teacher intervention" and prohibits students from operating the locked nodes. The system sends alerts via pop-ups and voice prompts on the teacher's end, such as "Role migration risk detected, manual intervention required"; and pushes risk details, such as "The new role does not have 'grounding wire' permission, migration will cause high-risk node interruption"; After viewing the risk details through the teacher-side system, teachers can choose to "assign another role", "temporarily grant new role permissions", and "cancel role switching". After the operation instructions are sent to the cloud system, the cloud system unlocks the task, executes the subsequent process according to the teacher's instructions, and adds the intervention record to the causal migration record.

[0056] Figure 5 An AR terminal-based virtual simulation teaching system 500 supporting real-time collaboration for live-line work is illustrated. This device embodiment is similar to... Figure 1 Corresponding to the illustrated method embodiments, the specific methods include: The task causal dependency graph construction module 501 is used to construct a task causal dependency graph based on a preset live-line operation teaching process. In this graph, nodes represent operation steps with clear role responsibilities and operation permissions, and edges represent causal dependencies between steps with attached conditional expressions. The role switching request monitoring module 502 is used to monitor role switching requests initiated by the trainee or detected automatically in real time during multi-role virtual simulation training conducted through an AR terminal. The causal integrity judgment and role migration module 503 is used to respond to the role switching request, perform causal integrity judgment based on the task causal dependency graph and the current task execution status, and dynamically reassign the original role's task responsibilities, operation permissions and task context information to the new role after the judgment is passed. The update information synchronization module 504 is used to synchronize the updated information after the role migration to all participating AR terminals in real time, so as to maintain the consistency of task status and role identification in the interface of each terminal. The migration record and analysis module 505 is used to generate a causal migration record describing the current role migration process. The record includes at least the triggering reason, the migrating role, the task nodes involved, and the impact on the causal chain, and is transmitted to the teacher's end for visualization and teaching analysis.

[0057] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A virtual simulation teaching method for live-line work using an AR terminal that supports real-time collaboration, characterized in that, Includes the following steps: Based on the pre-set live-line work teaching process, a task causal dependency graph is constructed, where nodes represent work steps with clear role responsibilities and operating permissions, and edges represent the causal dependency relationships between steps with attached conditional expressions. During multi-role virtual simulation training via AR terminal, real-time monitoring is conducted on role switching requests initiated by trainees or detected automatically. In response to the role switching request, based on the task causal dependency graph and the current task execution status, a causal integrity judgment is performed, and after the judgment is passed, the original role's task responsibilities, operation permissions and task context information are dynamically reassigned to the new role. The updated information after the character migration is synchronized to all participating AR terminals in real time to maintain the consistency of task status and character identification on each terminal interface. Generate a causal migration record describing the role migration process. The record includes at least the triggering cause, the migrating role, the task nodes involved, and the impact on the causal chain. The record is then transmitted to the teacher's end for visualization and teaching analysis.

2. The AR terminal-based live-line operation virtual simulation teaching method supporting real-time collaboration according to claim 1, characterized in that, The construction of the causal dependency graph for the task specifically includes: Based on the pre-set teaching script, the work process is broken down into multiple operation steps and nodes, and the required roles, prerequisites and postconditions are defined for each node. By analyzing the logical dependencies between operational steps, directional edges are established to connect relevant nodes, forming a directed graph structure that represents the task execution order and constraint relationships.

3. The AR terminal-based virtual simulation teaching method for live-line work supporting real-time collaboration as described in claim 1, characterized in that, Automatically detect the conditions that trigger character switching, including: The system detects that a certain role is offline for an extended period of time, that the critical task nodes it is responsible for are lagging behind, or that abnormal conflicts occur in the collaboration logic between multiple roles.

4. The AR terminal-based virtual simulation teaching method for live-line work supporting real-time collaboration as described in claim 1, characterized in that, The determination of causal integrity includes: Extract all task nodes currently bound to the role to be migrated from the task causal dependency graph; Verify that the new role has the set of permissions required to perform these tasks, and check that all necessary prerequisite task nodes have been correctly completed by the corresponding role.

5. The AR terminal-based virtual simulation teaching method for live-line work supporting real-time collaboration as described in claim 4, characterized in that, If, during the causal integrity assessment, a prerequisite task that was originally the responsibility of the original role but has not yet been completed is found, a task handover confirmation instruction for the new role will be automatically generated. Only after the instruction receives confirmation feedback on the AR terminal will the final transfer of permissions and responsibilities be completed.

6. The AR terminal-based virtual simulation teaching method for live-line work supporting real-time collaboration according to claim 1, characterized in that, The task context information includes: The current task's progress data, the viewpoint positioning information in the AR virtual scene, and the voice communication channel permissions bound to the specific task.

7. The AR terminal-based virtual simulation teaching method for live-line work supporting real-time collaboration according to claim 1, characterized in that, It also includes exception handling, including: When the result of the causal integrity judgment is that the migration will disrupt the task logic, the progress of the affected task node is automatically paused, the role is locked, and an alarm message is sent to the teacher.

8. The AR terminal-based virtual simulation teaching method for live-line work supporting real-time collaboration according to claim 1, characterized in that, Specifically, the visualization involves rendering the causal path affected by this role migration event in the visualization of the task causal dependency graph on the teacher's interface using highlighting, animation, or color differentiation, marking the role change points and maintaining a complete causal chain.

9. The AR terminal-based virtual simulation teaching method for live-line work supporting real-time collaboration according to claim 1, characterized in that, The node attributes in the task causal dependency graph include risk level identifiers related to live-line work safety regulations. When making judgments in the causal reasoning and transfer steps, priority is given to ensuring the integrity of the causal chain of high-risk task nodes.

10. An AR terminal-based virtual simulation teaching system for live-line work that supports real-time collaboration, characterized in that, include: The task causal dependency graph construction module is used to construct a task causal dependency graph based on a preset live-line operation teaching process. In this graph, nodes represent operation steps with clear roles, responsibilities, and operating permissions, and edges represent causal dependencies between steps with conditional expressions attached. The role switching request monitoring module is used to monitor role switching requests initiated by trainees or detected automatically in real time during multi-role virtual simulation training conducted through AR terminals. The causal integrity judgment and role migration module is used to respond to the role switching request, perform causal integrity judgment based on the task causal dependency graph and the current task execution status, and dynamically reassign the original role's task responsibilities, operation permissions and task context information to the new role after the judgment is passed. The update information synchronization module is used to synchronize the updated information after the role migration to all participating AR terminals in real time, so as to maintain the consistency of task status and role identification in the interface of each terminal. The migration record and analysis module is used to generate a causal migration record describing the role migration process. The record includes at least the triggering reason, the migrating role, the task nodes involved, and the impact on the causal chain, and is transmitted to the teacher's end for visualization and teaching analysis.

Images