A BPMN-based three-dimensional digital twin closed-loop control method, system, and storage medium

By adopting a BPMN-based three-dimensional digital twin closed-loop control method, the problems of scattered UE interaction logic and insufficient real-time performance of communication links are solved. The visualization and closed-loop control of the process-driven mechanism are realized, which improves the maintainability and stability of the system.

CN123116572APending Publication Date: 2026-11-17SICHUAN ZHONGRUI INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611253885.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-18
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing technologies in Unreal Engine (UE) interaction and simulation driving suffer from problems such as scattered interaction logic, lack of process visualization, difficulty in associating asynchronous callbacks, insufficient real-time performance of communication links, and disconnection between process and simulation data, resulting in high maintenance costs, delayed response, and difficulty in achieving closed loops.

Method used

A BPMN-based three-dimensional digital twin closed-loop control method is adopted. By establishing a BPMN process engine, a WebSocket communication gateway, and a UE-side driver adapter, the process model configuration, real-time bidirectional communication, simulation data retrieval, and event callback are unified. The responsibilities of External Task, Receive Task, and Service Task are clearly defined, and a mapping relationship between process instances and WebSocket connections is established.

Benefits of technology

It implements a modelable, monitorable, and reusable process-driven mechanism in UE digital twin scenarios, reduces hard-coded logic, improves the maintainability of process models and system stability, and adapts to concurrent control scenarios of multiple UE clients.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123116572A_ABST
    Figure CN123116572A_ABST
Patent Text Reader

Abstract

This invention discloses a BPMN-based closed-loop control method, system, and storage medium for 3D digital twins. The method uses a BPMN process engine as the core of interactive orchestration, establishing a bidirectional long-term connection between the process engine and the Unreal Engine UE-side driver adapter via a WebSocket communication gateway. An External Task handles asynchronous control command issuance and simulation data retrieval, a Receive Task receives UE-side event callbacks and advances the process flow, and a Service Task is only used for internal process processing such as synchronization variable organization and data format conversion. The UE-side driver adapter actively connects to the communication gateway, parses process commands, drives the execution of 3D objects, animations, and simulation interfaces, and then sends the execution results back to the process engine according to the message name and process instance identifier. This invention achieves closed-loop control of process modeling, command transmission, UE execution, event feedback, and resource release, reducing the dependence on hard-coded UE interaction logic and improving process reuse, concurrency control, and operation and maintenance management capabilities in complex digital twin scenarios.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the fields of digital twins, industrial simulation, 3D visualization interaction, process automation and real-time communication technologies, and in particular to a 3D digital twin closed-loop control method, system and storage medium based on BPMN. Background Technology

[0002] Unreal Engine (UE), with its capabilities for real-time rendering, complex scene construction, and 3D interaction, has been widely applied in scenarios such as digital twin factories, smart parks, virtual debugging, equipment training, and industrial simulation. In these scenarios, external business systems often need to send instructions to the UE, such as object transformation, state switching, animation playback, device parameter updates, simulation data retrieval, and execution of various events. The UE also needs to provide feedback to the business systems regarding user operations, simulation completion, state changes, or abnormal information.

[0003] There are two main existing methods for UE interaction and simulation-driven approaches: The first is to hard-code the interaction logic and parameters directly in the UE blueprint or C++ code, fixing control commands, data queries, event feedback, and branch decisions within the UE project, forming an execution and playback flow similar to a sequence animation. The second is to achieve data transmission between external systems and the UE through HTTP interfaces, ordinary message queues, or script calls. While these methods can handle simple command transmission, they struggle to form stable and reusable process-oriented control capabilities in scenarios with multiple steps, multiple objects, concurrent branches, and numerous asynchronous callbacks.

[0004] Specifically, hard-coding results in the interaction logic being scattered throughout the UE project, requiring recompilation or repackaging for process modifications, leading to high maintenance costs; ordinary interface methods typically lack process modeling, gateway branching, failure retry, status monitoring, and process backtracking capabilities, making it impossible to intuitively describe complex interaction processes; HTTP short connections or non-real-time message links are prone to response delays, uncontrollable connection states, or difficulties in command replay in high-frequency interaction and multi-client concurrent scenarios; at the same time, the lack of a unified mapping between UE simulation data and process variables makes it difficult to achieve a closed loop of "process-driven simulation and simulation feedback process".

[0005] Therefore, there is a need for a technical solution that can unify visual process orchestration, real-time two-way communication, UE command execution, simulation data retrieval, and event callback, so that those skilled in the art can configure complex UE interaction logic through process models and reliably complete command issuance, callback association, process advancement, and resource release during process execution. Summary of the Invention

[0006] The purpose of this invention is to provide a three-dimensional digital twin closed-loop control method, system and storage medium based on BPMN, which solves the problems of existing UE interaction logic relying on hard coding, process not being visualized, difficulty in associating asynchronous callbacks, insufficient real-time performance of communication links and disconnection between process and simulation data, and realizes a process-driven mechanism that can be modeled, monitored, reused and closed-loop in UE digital twin scenarios.

[0007] To achieve the above objectives, the technical solution adopted by this invention is: a three-dimensional digital twin closed-loop control method based on BPMN, comprising:

[0008] Establish a BPMN process engine, and configure an External Task for asynchronous command issuance or simulation data call, a Receive Task for receiving callback messages from the UE side, and a Service Task for internal process synchronization in the BPMN process engine.

[0009] Start the WebSocket communication gateway;

[0010] The UE-side driver adapter acts as a WebSocket client to actively connect to the Netty communication gateway and complete the client identifier registration; the service side carries the UE client identifier or binding identifier to start a process instance, so that the process instance establishes a mapping relationship with the corresponding WebSocket connection;

[0011] When the process reaches the External Task, the External Task Worker generates control commands or simulation data call requests and sends them to the UE-side driver adapter via the Netty communication gateway. The UE-side driver adapter parses the commands and drives the execution of 3D objects, animations, or simulation interfaces in the UE. The UE-side driver adapter encapsulates the execution result into a callback message and sends it to the Netty communication gateway. The BPMN process engine then triggers the corresponding Receive Task based on the message name and process instance identifier, thus continuing the process execution.

[0012] As a further improvement of the present invention, the Service Task is used for process variable organization, data format conversion, synchronization status verification or rule calculation, and does not undertake the issuance of WebSocket control commands and asynchronous simulation data calls on the UE side.

[0013] As a further improvement of the present invention, the External Task Worker pulls tasks according to the topic configured in the External Task and generates instruction payloads including commandType, targetObjectId, param, processInstanceId and callbackMessageName according to process variables.

[0014] As a further improvement of the present invention, the Netty communication gateway maintains at least the mapping relationship between the UE's client IdueClientId, bindId, processInstanceId and WebSocket Channel, and maintains connection reliability through heartbeat detection, disconnection reconnection and message retransmission mechanisms.

[0015] As a further improvement of the present invention, after receiving the control command, the UE-side driving adapter distributes it to object space transformation, state switching, animation playback or simulation interface call and other event processing logic according to the commandType, and converts the processing result into a unified event feedback format.

[0016] As a further improvement of the present invention, the callback message includes at least the fields messageName, processInstanceId, taskId, status, and resultData. The BPMN process engine completes the association of the Receive Task message based on messageName and processInstanceId.

[0017] As a further improvement of the present invention, it also includes: when the process ends, the BPMN process engine global event listener listens for the process end event and notifies the Netty communication gateway to release the connection mapping and cache resources corresponding to the process instance; the end node judgment based on the process node identifier and the process instance identifier serves as an auxiliary verification mechanism for connection release.

[0018] This invention also provides a BPMN-based three-dimensional digital twin closed-loop control system for implementing the BPMN-based three-dimensional digital twin closed-loop control method described above. The system includes: a BPMN process modeling and execution module, a WebSocket communication gateway module, a UE-side driver adapter module, and a process-simulation data mapping module; wherein:

[0019] The BPMN process modeling and execution module is used to configure and execute External Task, Receive Task, Service Task, and gateway nodes;

[0020] The WebSocket communication gateway module is used to establish and maintain the mapping relationship between process instances and UE-side WebSocket connections, as well as the bidirectional transmission of commands, events, and data.

[0021] The UE-side driver adapter module is used to receive communication messages from various network communication methods (HTTP / WebSocket / MQTT, etc.), parse commands, drive UE objects or simulation interfaces, and collect callback events;

[0022] The process-simulation data mapping module is used to realize the bidirectional mapping between process variables and UE attributes, simulation parameters and execution results.

[0023] As a further improvement of the present invention, the process-simulation data mapping module maps process variables to UE three-dimensional object attributes, simulation parameters or visualization status, and writes the event data or simulation results collected on the UE side back into the process variables.

[0024] The present invention also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the BPMN-based three-dimensional digital twin closed-loop control method as described above.

[0025] This invention uses a BPMN process engine as the process orchestration center, a WebSocket communication gateway as the real-time communication bridge, and a UE-side driver adapter as the execution end, abstracting UE interaction behavior, simulation data retrieval, and event callbacks into BPMN process nodes. In the process model, External Tasks handle asynchronous command issuance and simulation data retrieval; ReceiveTasks wait for UE-side callbacks and resume process execution; Service Tasks are only used for internal synchronous processing, such as variable organization, data format conversion, or rule calculation. This division of responsibilities avoids confusion between Service Tasks and External Tasks in command issuance and data retrieval.

[0026] After the UE-side driver adapter starts, it actively connects to the WebSocket communication gateway and registers its client identifier. When the service side starts a process instance, it carries the UE client identifier or binding identifier, and the communication gateway establishes a mapping relationship between the process instance and the WebSocket connection. After the process execution reaches the External Task, the External Task Worker generates standardized instructions or simulation data requests based on process variables and sends them to the UE-side driver adapter via the communication gateway. After the UE side completes execution, it sends a feedback message containing messageName and processInstanceId back to the communication gateway. The process engine then associates this with the corresponding Receive Task and advances subsequent nodes, thus forming a complete closed loop.

[0027] The beneficial effects of this invention are:

[0028] 1. Introduce the BPMN process model into the UE digital twin driven scenario, so that complex interaction processes can be designed, deployed, monitored and traced in a visual way, reducing hard-coded logic in UE engineering.

[0029] 2. Clearly define the responsibilities of External Task, Receive Task, and Service Task to prevent confusion between asynchronous instruction issuance, simulation data retrieval, event callbacks, and synchronous variable processing, thereby improving the maintainability of the process model.

[0030] 3. Establish a real-time bidirectional communication link through the WebSocket communication gateway, and maintain the mapping relationship between process instances and UE connections to adapt to scenarios with multiple UE clients, multiple objects, and multiple commands for concurrent control.

[0031] 4. The process-simulation data mapping module enables bidirectional synchronization between process variables and UE attributes, simulation parameters, and event results, thus forming a closed loop between process advancement and UE execution.

[0032] 5. By centrally releasing connection mappings and temporary resources through process end event listeners, the risk of invalid long connections being occupied is reduced, and the stability of system operation is improved. Attached Figure Description

[0033] Figure 1 This is a communication timing diagram of an embodiment of the present invention, showing the interaction sequence of process initiation, External Task instruction issuance, UE execution, Receive Task callback triggering, and process end and resource release;

[0034] Figure 2 This is a schematic diagram of the BPMN process nodes in an embodiment of the present invention, showing the division of responsibilities of External Task, Receive Task, Service Task and gateway node in the process;

[0035] Figure 3 This is a flowchart of the UE-side driver adapter in an embodiment of the present invention, showing the process of adapter actively connecting, command parsing, UE execution, event acquisition, and callback sending;

[0036] Figure 4 This is a system architecture diagram of an embodiment of the present invention, showing the connection relationship between the BPMN process modeling and execution module, the WebSocket communication gateway module, the UE-side driver adapter module, and the process-simulation data mapping module. Detailed Implementation

[0037] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0038] Example 1

[0039] A three-dimensional digital twin closed-loop control method based on BPMN includes:

[0040] S1. Process Modeling and Deployment. Configure process nodes using the BPMN (Business Process Model and Notation) process designer. The External Task configures the task topic and retry strategy, the Receive Task configures the callback message name, the Service Task configures the synchronization variable processing logic, and the processEndListener is configured to end the process event.

[0041] S2. Connection Initialization. After starting the WebSocket communication gateway, the UE-side driver adapter actively initiates a WebSocket long connection request to the communication gateway and submits registration information such as ueClientId or bindId; the communication gateway saves the mapping relationship between the client identifier and the Channel.

[0042] S3. Process Initiation and Connection Binding. The web client or backend business service starts the BPMN process instance with ueClientId or bindId. The process engine generates processInstanceId, and the communication gateway or business service establishes a mapping relationship between processInstanceId and the corresponding WebSocket Channel.

[0043] S4. Asynchronous command issuance and simulation data retrieval. When the process reaches the External Task, the ExternalTask ​​Worker pulls the task according to the topic, reads the process variables and generates control commands or simulation data retrieval requests, encapsulates them into a unified payload and sends them to the UE-side driver adapter through the communication gateway.

[0044] S5. UE Execution and Event Acquisition. The UE-side driver adapter parses the commandType, targetObjectId, and parameters in the payload, drives the execution of UE 3D objects, animations, states, or simulation interfaces, and acquires execution results, interaction events, or simulation data.

[0045] S6. Callback Association and Process Progression. The UE-side driver adapter encapsulates the feedback data into a callback message containing messageName, processInstanceId, taskId, status, and resultData, and sends it to the process engine via the communication gateway. The process engine triggers the corresponding Receive Task based on messageName and processInstanceId, and writes resultData into the process variable.

[0046] S7. Process End and Resource Release. After a process instance reaches its end event, the processEndListener, as the primary solution, notifies the communication gateway to release the connection mapping, cached messages, and temporary variables corresponding to the process instance. Determining whether the next node is the end node based on nodeId and processInstanceId serves only as an auxiliary verification or fallback mechanism for exceptions.

[0047] Example 2

[0048] like Figure 1 As shown, a three-dimensional digital twin closed-loop control method based on BPMN includes:

[0049] (a) Implementation environment:

[0050] In one embodiment, the process engine uses Camunda 7.18.0, the communication framework uses Netty 4.1.x, the UE environment uses UE 5.3, the process engine and communication gateway are implemented in Java, the UE-side driver adapter is implemented in C++ or Blueprints, and the runtime environment can be a Windows or Linux server and a PC-based UE client. This embodiment is only for illustrating possible implementations of the present invention and does not constitute a limitation on software versions and deployment methods.

[0051] (II) System Deployment and Connection Establishment:

[0052] During deployment, the backend service first starts the Camunda process engine and the WebSocket communication gateway. After the UE-side driver adapter starts with the UE application, it proactively initiates a WebSocket connection request to the communication gateway, carrying the ueClientId, sceneId, and bindId. After completing the handshake, the communication gateway establishes a first-layer mapping between ueClientId, bindId, and the Channel, and periodically sends heartbeat packets to check connection availability.

[0053] When a web-based user selects a specific UE scenario and initiates a business process, the backend service calls the Camunda process initiation interface, carrying the bindId, business parameters, and initial process variables. After the process instance is created, the backend service or communication gateway establishes a second-level mapping between the processInstanceId and the registered Channel. Subsequently, the External Task Worker only needs to locate the specific UE connection based on the processInstanceId, avoiding the unclear link of the server "requesting the UE service interface to establish a connection."

[0054] (III) BPMN Process Modeling and Node Configuration:

[0055] like Figure 2 As shown, the BPMN process model can include a start event, a parallel gateway, an exclusive gateway, an external task, a receive task, a service task, and an end event. External tasks are used to execute time-consuming or asynchronous external actions, such as issuing movement commands to the UE, calling simulation data interfaces, or triggering animation playback. Receive tasks are used to wait for UE callback messages, such as MSG_MOVE_DONE, MSG_SIM_DONE, or MSG_FINAL_CONFIRM. Service tasks are used for internal synchronous processing, such as converting UE return results into process variables, calculating branch conditions, or verifying parameter integrity.

[0056] Taking the movement command as an example, the external task's id can be configured as external_task_movecommand, the topic as UE_COMMAND_MOVE, the number of retries as 3, and the input parameters as commandType=MOVE, targetObjectId=Robot01, and the three-dimensional coordinate parameters; the receive task can be configured to wait for the message MSG_MOVE_DONE; and the process end event can be configured as processEndListener to trigger resource release.

[0057] (iv) Implementation of External Task Worker and Communication Gateway:

[0058] External Task Workers subscribe to topics such as UE_COMMAND_MOVE and UE_SIM_CALL through the Camunda external task client. Once a Worker acquires a task, it reads process variables and constructs a unified instruction payload. The communication gateway receives this payload, looks up the WebSocket Channel based on the processInstanceId, serializes the payload into a JSON or Protobuf message, and sends it to the UE-side driver adapter. It also records the taskId, messageId, and sending status for easy retrying and log tracking.

[0059] client.subscribe("UE_COMMAND_MOVE").handler((externalTask, service) -> {

[0060] String processInstanceId = externalTask.getProcessInstanceId();

[0061] CommandPayload payload = CommandPayload.fromTask(externalTask);

[0062] WebSocketChannel channel = channelManager.getByProcessInstanceId(processInstanceId);

[0063] gateway.send(channel, payload);

[0064] service.complete(externalTask);

[0065] });

[0066] In the example above, the External Task Worker is responsible for generating instructions from process variables and sending them via the communication gateway, without using the Service Task to handle instruction delivery. For simulation data retrieval, the Worker can first call the process-simulation data mapping module or an external simulation interface to obtain the data, then write the data into the process variables and send it to the UE side along with the control instructions.

[0067] (v) UE-side driver adapter implementation:

[0068] like Figure 3As shown, the UE-side driver adapter includes a connection management unit, a network message receiving and processing unit, a command parsing unit, a UE behavior control unit, a simulation interface adaptation unit, and an event feedback unit. The connection management unit is responsible for actively connecting to the communication gateway and maintaining a heartbeat; the command parsing unit parses commandType, targetObjectId, and param; the UE behavior control unit calls the UE object control interface according to the command; the simulation interface adaptation unit is responsible for reading or calculating simulation data; and the event feedback unit encapsulates the results into a standard callback message.

[0069] void FUEProcessAdapter::OnMessage(const FString& JsonText)

[0070] {

[0071] FCommandPayload Payload = ParseCommand(JsonText);

[0072] FExecutionResult Result = DispatchToUE(Payload.CommandType,Payload.TargetObjectId, Payload.Param);

[0073] FCallbackMessage Callback;

[0074] Callback.MessageName = Payload.CallbackMessageName;

[0075] Callback.ProcessInstanceId = Payload.ProcessInstanceId;

[0076] Callback.TaskId = Payload.TaskId;

[0077] Callback.Status = Result.bSuccess ? "success" : "failed";

[0078] Callback.ResultData = Result.Data;

[0079] WebSocketClient->Send(Callback.ToJson());

[0080] }

[0081] (vi) Callback association and process advancement

[0082] After receiving the callback message from the UE, the communication gateway first verifies the integrity of the messageName, processInstanceId, and taskId. Then, it calls the Camunda message association interface to associate the callback message with the corresponding Receive Task. The process engine writes the callback data into process variables and proceeds to the next node based on the gateway conditions in the BPMN process. For example, when the MSG_MOVE_DONE message arrives, the process advances to the parallel convergence gateway; once all parallel branches are completed, the process continues to execute subsequent External Tasks or Service Tasks.

[0083] runtimeService.createMessageCorrelation(callback.getMessageName())

[0084] .processInstanceId(callback.getProcessInstanceId())

[0085] .setVariable("ueCallbackStatus", callback.getStatus())

[0086] .setVariable("ueResultData", callback.getResultData())

[0087] .correlate();

[0088] (vii) Process completion and resource release

[0089] When a process instance reaches its end event, the `processEndListener` listens for the process end event and triggers resource release as the primary solution. The listener reads the `processInstanceId`, notifies the communication gateway to delete the mapping between `processInstanceId` and the `Channel`, and cleans up unacknowledged messages, temporary caches, and process-side bound data. If the process terminates abnormally or the listener notification fails, `nodeId` and `processInstanceId` can be used to determine if the next node is the end node as an auxiliary verification, and a scheduled task will reclaim timeout mappings. This design clearly defines the trade-off between the primary solution and the fallback solution.

[0090] (viii) Multi-object concurrency and branch control:

[0091] For scenarios involving multiple objects or concurrent commands, the BPMN process can use a parallel gateway to split into multiple ExternalTask ​​branches, each carrying a different targetObjectId or commandType. The UE-side driver adapter can distribute commands to different 3D objects according to the targetObjectId, and the communication gateway tracks the callbacks of each branch according to the processInstanceId and taskId. The parallel convergence gateway waits for multiple Receive Tasks to complete before proceeding to the next step, thus applying BPMN gateway capabilities to the specific scenario of concurrent control of UE digital twin objects.

[0092] Through the above implementation method, the UE interaction logic is extracted from the hard-coded UE engineering into a BPMN process model. Process adjustments are mainly completed through model configuration and External Task Worker extensions. The communication link is uniformly managed by the WebSocket communication gateway, which can support long connections of multiple UE clients and callback message association. A bidirectional mapping is formed between process variables, UE attributes, and simulation parameters, enabling process-driven simulation and simulation feedback processes. Compared with simple HTTP interfaces or hard-coded methods within the UE, this solution has stronger maintainability and scalability in terms of process visualization, asynchronous callbacks, concurrent branch control, and resource release.

[0093] Example 3

[0094] like Figure 4 As shown, a BPMN-based three-dimensional digital twin closed-loop control system includes:

[0095] 1. BPMN Process Modeling and Execution Module. This module is based on BPMN process engines such as Camunda and is used to define process nodes such as start events, external tasks, receive tasks, service tasks, parallel gateways, exclusive gateways, and end events, and to manage process variables, process instance states, task retries, event listeners, and process logs.

[0096] 2. WebSocket Communication Gateway Module. This module implements WebSocket server capabilities based on the Netty framework, and is responsible for UE client registration, long connection maintenance, heartbeat detection, disconnection reconnection, message serialization and deserialization, process instance and connection mapping, and routing of instructions and callback messages.

[0097] 3. UE-side driver adapter module. This module is deployed on the UE side and acts as a WebSocket client to actively connect to the communication gateway. It is responsible for parsing control commands, calling the UE object control interface or simulation interface, collecting interactive events and execution results, and sending them back in a unified message format.

[0098] 4. Process-Simulation Data Mapping Module. This module is responsible for maintaining the mapping relationship between process variables and UE object attributes, simulation parameters, and event results, enabling the process engine to read, update, and determine the UE-side status in the form of variables.

[0099] The embodiments described above are merely illustrative of specific implementations of the present invention, and while the descriptions are detailed, they should not be construed as limiting the scope of the present invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these modifications and improvements all fall within the scope of protection of the present invention.

Claims

1. A three-dimensional digital twin closed-loop control method based on BPMN, characterized in that, include: Establish a BPMN process engine, and configure an External Task for asynchronous command issuance or simulation data call, a Receive Task for receiving callback messages from the UE side, and a Service Task for internal process synchronization in the BPMN process engine. Start the WebSocket communication gateway; The UE-side driver adapter acts as a WebSocket client to actively connect to the Netty communication gateway and complete the client identifier registration; the service side carries the UE client identifier or binding identifier to start a process instance, so that the process instance establishes a mapping relationship with the corresponding WebSocket connection; When the process reaches the External Task, the External Task Worker generates control commands or simulation data call requests and sends them to the UE-side driver adapter via the Netty communication gateway. The UE-side driver adapter parses the instructions and drives the execution of 3D objects, animations, or simulation interfaces in the UE. The UE-side driver adapter encapsulates the execution result into a callback message and sends it to the Netty communication gateway. The BPMN process engine then triggers the corresponding Receive Task based on the message name and process instance identifier, thus propelling the process to continue execution.

2. The BPMN-based three-dimensional digital twin closed-loop control method according to claim 1, characterized in that, The Service Task is used for process variable organization, data format conversion, synchronization status verification, or rule calculation, and does not undertake the issuance of WebSocket control commands or asynchronous simulation data calls on the UE side.

3. The BPMN-based three-dimensional digital twin closed-loop control method according to claim 1, characterized in that, The External Task Worker pulls tasks according to the topic configured in the External Task and generates instruction payloads including commandType, targetObjectId, param, processInstanceId, and callbackMessageName based on process variables.

4. The BPMN-based three-dimensional digital twin closed-loop control method according to claim 1, characterized in that, The Netty communication gateway maintains at least the mapping relationship between the UE's client ID (ueClientId), bindId, processInstanceId, and WebSocket Channel, and maintains connection reliability through heartbeat detection, disconnection reconnection, and message retransmission mechanisms.

5. The BPMN-based three-dimensional digital twin closed-loop control method according to claim 1, characterized in that, After receiving the control command, the UE-side driver adapter distributes it to object space transformation, state switching, animation playback or simulation interface call and other event processing logic according to the commandType, and converts the processing result into a unified event feedback format.

6. The BPMN-based three-dimensional digital twin closed-loop control method according to claim 1, characterized in that, The callback message includes at least the fields messageName, processInstanceId, taskId, status, and resultData. The BPMN process engine uses messageName and processInstanceId to associate the Receive Task message.

7. The BPMN-based three-dimensional digital twin closed-loop control method according to claim 1, characterized in that, Also includes: When the process ends, the BPMN process engine global event listener listens for the process end event and notifies the Netty communication gateway to release the connection mapping and cache resources corresponding to the process instance. The end node determination based on process node identifier and process instance identifier serves as an auxiliary verification mechanism for connection release.

8. A three-dimensional digital twin closed-loop control system based on BPMN, characterized in that, The system for implementing the BPMN-based three-dimensional digital twin closed-loop control method as described in any one of claims 1-7 includes: a BPMN process modeling and execution module, a WebSocket communication gateway module, a UE-side driver adapter module, and a process-simulation data mapping module; wherein: The BPMN process modeling and execution module is used to configure and execute External Task, Receive Task, ServiceTask, and gateway nodes; The WebSocket communication gateway module is used to establish and maintain the mapping relationship between process instances and UE-side WebSocket connections, as well as the bidirectional transmission of commands, events, and data. The UE-side driver adapter module is used to receive communication messages from various network communication methods, parse instructions, drive UE objects or simulation interfaces, and collect callback events. The process-simulation data mapping module is used to realize the bidirectional mapping between process variables and UE attributes, simulation parameters and execution results.

9. The BPMN-based three-dimensional digital twin closed-loop control system according to claim 8, characterized in that, The process-simulation data mapping module maps process variables to UE 3D object attributes, simulation parameters, or visualization status, and writes the event data or simulation results collected on the UE side back into the process variables.

10. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the BPMN-based three-dimensional digital twin closed-loop control method as described in any one of claims 1 to 7.