A Workflow-Based Multi-Terminal Scene Orchestration and One-Click Linkage Method and System

Abstract

This invention relates to a method and system for multi-terminal scene orchestration and one-click linkage based on workflow. The method includes: an intranet workflow control system models scene elements as nodes such as terminals, approvals, and actions, and constructs a directed acyclic graph (DAG) structure based on business logic, which is then compiled into an executable workflow model; in response to a linkage command issued from an external network control terminal via a unidirectional transmission link, the intranet system triggers an approval node to perform permission verification. After approval, the execution engine schedules the workflow and issues action commands to the corresponding external network terminal via another unidirectional transmission link; the external network terminal executes the linkage playback action and returns a receipt via yet another unidirectional transmission link. This invention achieves visualized orchestration of complex logic through DAG modeling, and combined with multi-link collaboration and approval mechanisms in a physically isolated environment, it achieves efficient one-click linkage and automated scheduling of multiple terminals while ensuring the security of the intranet core control system.

Description

Technical Field

[0001] This invention relates to the fields of information interaction and network security as well as multimedia cluster control technology, and in particular to a workflow-based method and system for multi-terminal scene orchestration and one-click linkage. Background Technology

[0002] In current information technology infrastructure development, emergency command systems are widely used across various industries. When using these systems, two key considerations must be taken: the security of the network hosting the system and the sheer number of signal source terminals being accessed. Existing systems lack the technology to effectively address both of these aspects. Summary of the Invention

[0003] In view of the above-mentioned prior art, the first aspect of the present invention provides a method for multi-terminal scene orchestration and one-click linkage based on workflow, the method comprising the following steps:

[0004] S1. The intranet workflow control system divides the components of a multi-terminal collaborative scenario into multiple nodes, including terminal nodes, approval nodes, and action nodes; and configures the attributes of each node.

[0005] S2. The intranet workflow control system defines the dependencies between the nodes according to the business logic, and constructs one or more directed acyclic graph structures that describe the multi-terminal linkage logic;

[0006] S3. Compile the directed acyclic graph into an executable workflow model;

[0007] S4. In response to the control command issued by the external network control terminal, the internal network workflow control system responds, including triggering the approval node, determining whether the workflow in the control command matches the workflow model, and if so, approving the control command. The internal network workflow control system then continues to execute the corresponding workflow model and its remaining nodes according to the control command, including issuing action node commands to the corresponding terminal on the external network through the first unidirectional transmission link.

[0008] S5. The corresponding terminal on the external network receives the action node instruction and executes the linked playback action according to the action node instruction;

[0009] S6. The corresponding terminal on the external network returns an execution receipt to the status dashboard near the location of the external network control terminal for display. The status dashboard does not form a closed-loop connection with the external network control terminal. The external network control terminal is connected to the internal network workflow control system through a third unidirectional transmission link.

[0010] According to some embodiments of the present invention, the node further includes a content node and a logic node; when the approval node is triggered, the intranet workflow control system pauses and waits for manual or automatic approval instructions, and continues to execute the remaining nodes after approval; when the workflow is transferred to the logic node, serial, parallel, branch judgment or loop operation is performed according to preset conditions; when the workflow is transferred to the action node, action control instructions for a specific terminal are generated; when the workflow is transferred to the terminal node, the linked terminal is determined; when the workflow is transferred to the content node, the linked content is determined.

[0011] According to some embodiments of the present invention, the method further includes: the external network control terminal packaging the control command to include a digital signature and a serial number, and sending the packaged command to the internal network workflow control system through a third unidirectional transmission link; the command issued by the internal network workflow control system to the external network terminal includes the serial number; the execution receipt returned by the external network terminal to the status dashboard includes the serial number and the execution result.

[0012] According to some embodiments of the present invention, the corresponding terminal on the external network pushes the execution receipt to the internal network workflow control system through a second unidirectional transmission link.

[0013] According to some embodiments of the present invention, both the first unidirectional transmission link and the third unidirectional transmission link include: an electro-optical conversion unidirectional optical transmitter for receiving electrical signals and converting them into optical signals; a unidirectional optical fiber for transmitting the optical signals unidirectionally; and an opto-optical conversion unidirectional optical receiver for receiving optical signals and converting them into electrical signals before outputting them.

[0014] The present invention also provides a workflow-based multi-terminal scene orchestration and one-click linkage system, characterized in that the system includes: a workflow control system located on the intranet side, a first unidirectional transmission link and a third unidirectional transmission link located in the cross-network transmission domain;

[0015] The workflow control system includes:

[0016] The intranet node manager is used to divide the components of a multi-terminal collaboration scenario into multiple nodes, including terminal nodes, approval nodes, and action nodes; and to configure the attributes of each node.

[0017] The intranet workflow orchestrator is used to define the dependencies between the nodes according to the business logic, construct one or more directed acyclic graph structures describing the multi-terminal linkage logic, compile the directed acyclic graph into an executable workflow model, and deploy it to the intranet execution engine.

[0018] The intranet execution engine is used to respond to control commands issued by the external network control terminal, including triggering approval nodes. The intranet node manager determines whether the workflow in the control command matches the workflow model. If so, the control command is approved, and the intranet workflow control system continues to execute the corresponding workflow model and its remaining nodes according to the control command, including issuing action node commands to the corresponding terminal on the external network through the first unidirectional transmission link.

[0019] The corresponding terminal on the external network receives the action node instruction, executes the linkage playback action according to the action node instruction, and pushes the execution receipt to the status dashboard near the location of the external network control terminal for display. The status dashboard does not form a closed loop connection with the external network control terminal.

[0020] The external network control terminal is connected to the internal network workflow control system via a third unidirectional transmission link.

[0021] According to some embodiments of the present invention, the node further includes a content node and a logic node; at the approval node, the workflow system pauses and waits for manual or automatic approval instructions, and continues to execute the remaining nodes after approval; when the workflow is transferred to the logic node, serial, parallel, branch judgment or loop operation is performed according to preset conditions; when the workflow is transferred to the action node, action control instructions for a specific terminal are generated; when the workflow is transferred to the terminal node, the linked terminal is determined; when the workflow is transferred to the content node, the linked content is determined.

[0022] According to some embodiments of the present invention, the external network control terminal packages the control instructions, including a digital signature and a serial number, and sends the packaged instructions to the internal network workflow control system through a third unidirectional transmission link; the instructions issued by the internal network workflow control system to the external network terminal include the serial number; the execution receipt returned by the external network terminal to the status dashboard includes the serial number and the execution result.

[0023] According to some embodiments of the present invention, the system further includes a corresponding terminal and status dashboard on the external network.

[0024] According to some embodiments of the present invention, both the first unidirectional transmission link and the third unidirectional transmission link include: an electro-optical conversion unidirectional optical transmitter for receiving electrical signals and converting them into optical signals; a unidirectional optical fiber for unidirectional transmission of the optical signals; and an opto-optical conversion unidirectional optical receiver for receiving the optical signals, converting them into electrical signals, and then outputting them.

[0025] The multi-terminal scene orchestration and one-click linkage method and system based on workflow provided in this invention have the following beneficial technical effects:

[0026] This invention transforms abstract control logic into a visualized directed acyclic graph (DAG), making complex parallel, serial, cyclic, and conditional logic clearly visible, thus solving the problems of tedious and error-prone traditional manual configuration. Through automated scheduling by the intranet execution engine, millisecond-level multi-terminal collaborative actions can be achieved, greatly improving response speed in large-scale events or emergency scenarios. Furthermore, the architecture employing intranet orchestration decision-making, unidirectional link distribution, and external network terminal execution, coupled with an approval node mechanism, achieves both flexible control and prevents external network threats from harming the core intranet system through physical unidirectional isolation technology. Attached Figure Description

[0027] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used are briefly described below:

[0028] Figure 1 A flowchart illustrating a workflow-based multi-terminal scene orchestration and one-click linkage method according to some embodiments of the present invention is shown.

[0029] Figure 2 A partial timing diagram of a workflow-based multi-terminal scene orchestration and one-click linkage method according to some embodiments of the present invention is shown.

[0030] Figure 3 Another timing diagram of a workflow-based multi-terminal scene orchestration and one-click linkage method according to some embodiments of the present invention is shown.

[0031] Figure 4 A structural block diagram of a workflow-based multi-terminal scene orchestration and one-click linkage system according to some embodiments of the present invention is shown.

[0032] Correspondence of reference numerals in the attached diagram:

[0033] 101: Node Manager

[0034] 102: Workflow Orchestrator

[0035] 103: Execution Engine

[0036] 201: First unidirectional transmission link (internal network -> external network)

[0037] 203: Third unidirectional transmission link (external network -> internal network)

[0038] 301: Control Terminal

[0039] 302: Corresponding terminal Detailed Implementation

[0040] The present invention will now be described by way of example with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. Furthermore, the described embodiments are only some, not all, of the embodiments of the present invention.

[0041] To address the challenges of multi-terminal collaborative control and low cross-network security in existing technologies, this invention provides a novel control architecture based on a directed acyclic graph (DAG) workflow.

[0042] refer to Figure 1 The document illustrates a flowchart of a workflow-based multi-terminal scene orchestration and one-click linkage method according to some embodiments of the present invention. Figure 1 As shown, the method mainly includes the following steps:

[0043] Step S1: The intranet workflow control system divides the constituent elements of the multi-terminal collaborative scenario into multiple nodes, including terminal nodes, approval nodes, and action nodes, and configures the attributes of each node.

[0044] To enable computers to understand complex human business logic, this invention abstracts all elements in a scenario into standardized nodes. Specifically, these nodes mainly include the following types: Terminal nodes are the target objects of workflow execution (representing specific terminals, such as screens, screen groups, and matrix output ports), and their attribute configurations include the terminal's location, capabilities, resolution, and group relationships; Approval nodes are control points specially designed to meet high security requirements, and their attribute configurations include the approver's role, approval timeout, and default action. Their function is to automatically suspend the system when the workflow reaches this node, waiting for manual confirmation or AI-automated review—a crucial firewall to prevent accidental operations; Action nodes define specific business operations, and their attribute configurations include action types and specific parameters such as play, pause, screen switching, and restart, used to instruct the terminal to perform specific operations; Content nodes define the playback materials, such as videos, images, text, notifications, and dashboards, and their attribute configurations can include file ID, URL link, and content type; Logic nodes are used to control the workflow's direction, including sequential execution nodes, parallel execution nodes, conditional branch nodes that determine the path based on input variables, and loop nodes that repeatedly execute a certain segment of logic. The system can provide a user interface or API through the intranet node manager (or simply node manager) to allow administrators to create these nodes and set their properties.

[0045] Step S2: The intranet workflow control system defines the dependencies between the nodes according to the business logic and constructs one or more directed acyclic graph structures that describe the multi-terminal linkage logic.

[0046] In this step, scattered nodes are combined into a meaningful business process by connecting them. This structure is mathematically described as a Directed Acyclic Graph (DAG). Dependencies mean that a subsequent node will only be triggered after the preceding node has executed successfully. The system automatically checks the graph for infinite loops to ensure that the process can always be completed. For example, in the morning startup mode, the process could start from the start node and proceed to the parallel nodes, branching into two branches: one for all screens to power on and the other for background music to start. After a 5-minute wait, the morning news would then play.

[0047] Step S3: Compile the directed acyclic graph into an executable workflow model.

[0048] The constructed graphical structure needs to be converted into computer-executable code or instruction sequences. The system uses a topological sorting algorithm to parse the DAG, determine the execution order of the nodes, and serialize the graphical data into a definition file, i.e., a workflow model. Subsequently, the compiled model is loaded into the memory of the intranet execution engine, ready to respond to trigger signals at any time.

[0049] S4. In response to the control command issued by the external network control terminal, the internal network workflow control system responds, including triggering the approval node. The internal network node manager determines whether the workflow in the control command matches the workflow model. If so, the control command is approved, and the internal network workflow control system continues to execute the corresponding workflow model and its remaining nodes according to the control command, including issuing action node commands to the corresponding terminal on the external network through the first unidirectional transmission link.

[0050] In many scenarios, operators may be in an external network environment and need to remotely trigger a complex scenario preset on the internal network. In this case, the external network control terminal will generate a command. The complex scenario may include, for example, multiple terminals simultaneously looping through content 1, multiple terminals simultaneously looping through content 2, or multiple terminals playing content 3 according to certain conditions.

[0051] The instruction can be transmitted to the intranet via a third unidirectional transmission link. Upon receiving the instruction, the intranet system first activates the approval node in the workflow. It checks whether the workflow (or ID) requested by the instruction is in the deployed list of valid models. If valid and approved by manual or automated rules, the approval node status changes to "approved." Once approved, the system continues the subsequent process, performing branch judgments or loop counting when encountering logical nodes, and encapsulating the action instruction when encountering action nodes. Since the terminal is located on the external network, the intranet engine cannot directly establish a TCP connection; therefore, the encapsulated action instruction is sent to the external network environment via the first unidirectional transmission link.

[0052] In step S5, the corresponding terminal on the external network receives the action node instruction and executes the linked playback action according to the action node instruction.

[0053] The external network terminal listens to the exit of the first unidirectional link. Once a data packet is received, it unpacks and verifies it, and then executes specific operations, such as calling the local player to play video, switching the HDMI signal source, and adjusting the volume. Because it is based on workflow orchestration, multiple terminals may receive their respective instructions within the same millisecond, thus achieving a visually synchronized effect. Furthermore, the terminals in this application can also include multiple terminals or screen groups connected together via a splicing controller; in this case, the instructions will be sent to the splicing controller.

[0054] S6. The corresponding terminal on the external network returns an execution receipt to the status dashboard near the location of the external network control terminal for display. The status dashboard does not form a closed-loop connection with the external network control terminal. The external network control terminal is connected to the internal network workflow control system through a third unidirectional transmission link.

[0055] After the external terminal completes the action, it generates a receipt containing a sequence number, execution status, error code, and execution time. The receipt can be sent back to the internal network system via a second unidirectional transmission link.

[0056] Figure 2 A partial timing diagram of a workflow-based multi-terminal scene orchestration and one-click linkage method according to some embodiments of the present invention is shown. Figure 3 Another timing diagram of a workflow-based multi-terminal scene orchestration and one-click linkage method according to some embodiments of the present invention is shown.

[0057] Part One ( Figure 2 Modeling and Approval Process

[0058] The diagram illustrates how the intranet, through the collaboration of various components, completes the entire process from defining business logic to model deployment and permission verification. First, the intranet node manager, serving as the primary entry point for user operations, abstracts and divides the components of a multi-terminal collaborative scenario into standardized nodes. These nodes include terminal nodes defining devices, content nodes defining playback materials, logic nodes controlling the flow of information, and approval nodes for security control. Administrators configure the specific attributes of each node at this stage. Next, the intranet workflow orchestrator reads these definitions, determines the dependencies between nodes based on the business logic, and constructs a directed acyclic graph (DAG) structure describing the multi-terminal linkage logic. Before generating the model, the orchestrator compiles the DAG into a computer-executable workflow model and deploys it to the intranet execution engine. When a scenario needs to be executed, the intranet execution engine responds to the instruction and triggers the approval node. At this point, the system process pauses and waits for manual or automatic approval for verification. Only after approval is granted will the intranet workflow control system unlock and continue executing the subsequent workflow model.

[0059] Part Two Figure 3 ): Execution and linkage process

[0060] This section primarily demonstrates how the intranet execution engine schedules logic after approval and securely links with external terminals via a physical unidirectional link. The intranet execution engine continues running according to the model logic. When the flow reaches a logic node, the engine executes branch judgments (If / Else) or loop operations (Loop) based on preset conditions. After determining the specific operation, the engine generates an action instruction packet and sends it unidirectionally to the external network via the first unidirectional transmission link located in the cross-network transmission domain. This link utilizes electro-optical conversion technology to ensure that data can only flow from the intranet to the external network. The corresponding terminal on the external network listens to this link, parses the received instruction, and executes specific actions such as linked playback or screen switching. After the action is completed, the terminal generates a receipt containing a sequence number and execution result, which is securely sent back to the intranet execution engine via the second unidirectional transmission link. Upon receiving the receipt, the intranet execution engine extracts the sequence number and updates the node state machine of the DAG graph in memory, ultimately summarizing the execution status of the entire workflow and completing closed-loop management.

[0061] refer to Figure 4 The diagram shows the overall architecture of a workflow-based multi-terminal scene orchestration and one-click linkage system according to some embodiments of the present invention.

[0062] The system is physically divided into an intranet side and an extranet side, connected by a cross-network transmission domain. In the workflow control system on the intranet side, the intranet node manager (101) is the main entry point for user operations. It is responsible for providing a visual interface for administrators to drag and drop components to define various types of nodes and for configuring attributes, such as setting the approver permissions of approval nodes or the specific parameters of action nodes. The main function of the intranet workflow orchestrator (102) is logic construction. It reads the data defined by the node manager, establishes the dependencies between nodes according to the business logic, and constructs a directed acyclic graph (DAG) structure. Its compiler converts the visual DAG graph into a model file that the execution engine can read and deploys it into the execution engine, while performing legality verification. The intranet execution engine (103) is used to interpret and run the workflow model in real time. When it receives a trigger command from the extranet, it drives the flow of the process and generates instructions to send through a one-way link when it encounters an action node. According to some embodiments of the present invention, in response to a control command issued by an external network control terminal, the internal network execution engine (103) responds by triggering an approval node. The internal network node manager determines whether the workflow in the control command matches the workflow model. If so (for example, the command requires three terminals to work together, and the existing workflow model also includes the workflow of the three terminals working together), the control command is approved. The internal network workflow control system continues to execute the corresponding workflow model and its remaining nodes according to the control command, including issuing action node commands to the corresponding terminals on the external network through the first unidirectional transmission link.

[0063] To ensure intranet security, the cross-network transmission domain does not use conventional bidirectional TCP / IP connections, but instead uses physical unidirectional links. The first unidirectional transmission link (201) is from the intranet to the extranet, used to send control commands, action parameters, and content metadata. The second unidirectional transmission link (202) is from the extranet to the intranet, used to send execution receipts and terminal status reports back to the intranet or its execution engine. The third unidirectional transmission link (203) is from the extranet control terminal to the intranet, specifically used by the extranet control terminal to initiate scene-related commands to the intranet. All of the above links can adopt the structure of an electro-optical conversion unidirectional optical transmitter, a unidirectional optical fiber, and an opto-optical conversion unidirectional optical receiver, fundamentally eliminating the possibility of reverse attacks using the TCP handshake protocol.

[0064] The external network control terminal (301) (or simply control terminal) on the external network side is the device in the operator's hands. It does not directly control the screens of the corresponding terminals on each external network, but instead sends instructions to the internal network. When sending instructions, they are packaged and accompanied by digital signatures and serial numbers to ensure that the requests are tamper-proof and traceable. The corresponding terminals (302) on the external network listen for and execute playback or screen switching actions, and generate receipts. In addition to sending back execution receipts and terminal status reports to the internal network or its execution engine via the second unidirectional transmission link (202), the corresponding terminals can also send the receipts back to a status dashboard for the operator to see. This status dashboard can be set up relatively independently from the external network control terminal, and the operator can only confirm the system status by visually observing the content on the dashboard. According to some embodiments of the present invention, the content on the dashboard can also be photographed and identified by the internal network's camera and recognition device and then transmitted to the control terminal.

[0065] Regarding security mechanisms and end-to-end tracing, to ensure that instructions are not lost or tampered with in complex cross-network environments, this invention introduces a sequence number and signature mechanism. When the external network control terminal generates a trigger instruction, it generates a globally unique sequence number and digitally signs the instruction digest using a private key. Upon receiving the instruction, the internal network verifies the signature's validity. If valid, this sequence number will persist throughout the entire workflow lifecycle. This sequence number is also included in the action instructions sent from the internal network to the external network terminal. After the external network terminal completes execution, the returned receipt must carry the same sequence number. Upon receiving the receipt, the internal network execution engine extracts the sequence number, finds the corresponding node instance in the DAG graph in memory, and updates its state machine. States include waiting, running, success, failure, timeout, and skipped. If a timeout or failure occurs, the execution engine can automatically handle it according to a preset strategy.

[0066] This invention transforms abstract control logic into a visualized directed acyclic graph (DAG), making complex parallel, serial, cyclic, and conditional logic clearly visible, thus solving the problems of tedious and error-prone traditional manual configuration. Through automated scheduling by the intranet execution engine, millisecond-level multi-terminal collaborative actions can be achieved, greatly improving response speed in large-scale events or emergency scenarios. Furthermore, the architecture employing intranet orchestration decision-making, unidirectional link distribution, and external network terminal execution, coupled with an approval node mechanism, achieves both flexible control and prevents external network threats from harming the core intranet system through physical unidirectional isolation technology.

[0067] It should be noted that, for ease of understanding, this application has broken down each step in the method and each module in the system in detail. However, those skilled in the art will understand that, depending on the actual implementation needs, each step and module can be further broken down or reorganized, and these are all within the scope of the present invention.

Claims

1. A method for multi-terminal scenario orchestration and one-click linkage based on workflow, the method comprising the following steps: S1. The intranet workflow control system divides the components of a multi-terminal collaborative scenario into multiple nodes, including terminal nodes, approval nodes, and action nodes; and configures the attributes of each node. S2. The intranet workflow control system defines the dependencies between the nodes according to the business logic, and constructs one or more directed acyclic graph structures that describe the multi-terminal linkage logic; S3. Compile the directed acyclic graph into an executable workflow model; S4. In response to the control command issued by the external network control terminal, the internal network workflow control system responds, including triggering the approval node, determining whether the workflow in the control command matches the workflow model, and if so, approving the control command. The internal network workflow control system then continues to execute the corresponding workflow model and its remaining nodes according to the control command, including issuing action node commands to the corresponding terminal on the external network through the first unidirectional transmission link. S5. The corresponding terminal on the external network receives the action node instruction and executes the linked playback action according to the action node instruction; the corresponding terminal on the external network pushes the execution receipt to the internal network workflow control system through the second unidirectional transmission link; as well as S6. The corresponding terminal on the external network returns an execution receipt to the status dashboard near the location of the external network control terminal for display. The status dashboard does not form a closed-loop connection with the external network control terminal. The external network control terminal is connected to the internal network workflow control system through a third unidirectional transmission link.

2. The method according to claim 1, wherein, The nodes also include content nodes and logic nodes; when an approval node is triggered, the intranet workflow control system pauses and waits for manual or automatic approval instructions, and continues to execute the remaining nodes after the approval is passed. When the flow reaches a logic node, it performs serial, parallel, branch judgment, or loop operations according to preset conditions; when the flow reaches an action node, it generates action control instructions for a specific terminal; when the flow reaches a terminal node, it determines the linked terminal; when the flow reaches a content node, it determines the linked content.

3. The method according to claim 1 or 2, wherein, The method further includes: the external network control terminal packages the control command to include a digital signature and a serial number, and sends the packaged command to the internal network workflow control system through a third unidirectional transmission link; the command issued by the internal network workflow control system to the external network terminal includes the serial number; the execution receipt returned by the external network terminal to the status dashboard includes the serial number and the execution result.

4. The method according to claim 1 or 2, wherein, Both the first unidirectional transmission link and the third unidirectional transmission link include: an electro-optical conversion unidirectional optical transmitter for receiving electrical signals and converting them into optical signals; a unidirectional optical fiber for transmitting optical signals unidirectionally; and an opto-optical conversion unidirectional optical receiver for receiving optical signals, converting them into electrical signals, and then outputting them.

5. A workflow-based multi-terminal scenario orchestration and one-click linkage system, characterized in that, The system includes: a workflow control system located on the intranet side, a first unidirectional transmission link and a third unidirectional transmission link located in the cross-network transmission domain; The workflow control system includes: The intranet node manager is used to divide the components of a multi-terminal collaboration scenario into multiple nodes, including terminal nodes, approval nodes, and action nodes; and to configure the attributes of each node. The intranet workflow orchestrator is used to define the dependencies between the nodes according to the business logic, construct one or more directed acyclic graph structures describing the multi-terminal linkage logic, compile the directed acyclic graph into an executable workflow model, and deploy it to the intranet execution engine. The intranet execution engine is used to respond to control commands issued by the external network control terminal, including triggering approval nodes. The intranet node manager determines whether the workflow in the control command matches the workflow model. If so, the control command is approved, and the intranet workflow control system continues to execute the corresponding workflow model and its remaining nodes according to the control command, including issuing action node commands to the corresponding terminal on the external network through the first unidirectional transmission link. The corresponding terminal on the external network receives the action node instruction, executes the linkage playback action according to the action node instruction, and pushes the execution receipt to the internal network workflow control system and the execution receipt to the status dashboard near the location of the external network control terminal through the second unidirectional transmission link for display. The status dashboard does not form a closed loop connection with the external network control terminal. The external network control terminal is connected to the internal network workflow control system via a third unidirectional transmission link.

6. The system according to claim 5, wherein, The nodes also include content nodes and logic nodes; at the approval node, the workflow system pauses and waits for manual or automatic approval instructions, and continues to execute the remaining nodes after approval; when the workflow reaches the logic node, it performs serial, parallel, branch judgment or loop operation according to preset conditions; when the workflow reaches the action node, it generates action control instructions for a specific terminal; when the workflow reaches the terminal node, it determines the linked terminal; when the workflow reaches the content node, it determines the linked content.

7. The system according to claim 5, wherein, The external network control terminal packages the control commands, including a digital signature and a serial number, and sends the packaged commands to the internal network workflow control system via a third unidirectional transmission link. The commands issued by the internal network workflow control system to the external network terminal contain the serial number. The execution receipt returned by the external network terminal to the status dashboard contains the serial number and the execution result.

8. The system according to claim 5 or 6, wherein, The system also includes the corresponding terminal on the external network and the status dashboard.

9. The system according to claim 5 or 6, wherein, Both the first unidirectional transmission link and the third unidirectional transmission link include: an electro-optical conversion unidirectional optical transmitter for receiving electrical signals and converting them into optical signals; a unidirectional optical fiber for transmitting optical signals unidirectionally; and an opto-optical conversion unidirectional optical receiver for receiving optical signals, converting them into electrical signals, and then outputting them.

Images