Multi-group console linkage control method of stage equipment

Abstract

This invention discloses a method for multi-group console linkage control of stage equipment, comprising the following steps: S1, setting one stage control channel in any console as the master stage control channel, and configuring a unique control permission token for issuing control commands to the stage equipment; S2, based on device fingerprint and dynamic authentication of the stage control channel, adaptively matching and securely binding each group of stage control channels with the target stage equipment; S3, constructing a global state data model, and encapsulating the device control data of all stage control channels through the global state data model; S4, the master console periodically polls the global state data model, drives its own graphics rendering engine to render the device control data of each group of stage control channels, generates a visual interface, and publishes the incremental change data of the global state data model to the slave stage control channels through the DDS protocol.

Description

Technical Field

[0001] This invention relates to the field of stage automation technology, specifically to a method for coordinated control of multiple control consoles for stage equipment. Background Technology

[0002] In large-scale stage performances, theaters, or performing arts venues, complex stage machinery (such as rigging, lifts, turntables, and lighting arrays) typically requires coordinated control and monitoring from multiple control consoles distributed across different areas of the stage or multiple control rooms. Traditional multi-control console systems mainly employ the following architectures: Master-slave architecture: One master stage control channel is designated with control authority, while the others are slave stage control channels. However, master-slave switching in existing technologies is often abrupt, requiring manual reconfiguration of the network and permissions. System control is interrupted during the switch, posing security risks. Furthermore, slave stage control channels typically cannot obtain a real-time, high-fidelity global status view that is completely consistent with the master stage control channel, affecting the effectiveness of monitoring.

[0003] Fully redundant architecture: Multiple consoles are completely peer-to-peer, and any one can take over at any time. While this approach improves availability, it is highly susceptible to command conflicts, where multiple operators simultaneously send different or even contradictory control commands, leading to equipment malfunctions and potentially causing equipment damage or safety incidents. To resolve these conflicts, complex command arbitration mechanisms are typically required, increasing system complexity and latency.

[0004] Distributed shared architecture: Each console shares a portion of the data, but existing data synchronization mostly uses polling or simple heartbeat broadcasting mechanisms, which consumes a lot of network bandwidth and has a large synchronization delay. Especially when the device status changes rapidly, the interfaces of each console are inconsistent, leading to operator misjudgment. Summary of the Invention

[0005] The purpose of this invention is to provide a method for the coordinated control of multiple control consoles for stage equipment to solve the above-mentioned problems.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: A method for coordinated control of multiple control consoles for stage equipment, the method being implemented based on multiple control consoles, each console having several stage control channels, specifically including the following steps: S1. Set one stage control channel on any console as the main stage control channel and configure a unique control permission token to send control commands to the stage equipment. The stage control channel will automatically enter read-only monitoring mode. S2. Based on the dynamic authentication of device fingerprints and stage control channels, each group of stage control channels is adaptively matched and securely bound to the target stage equipment. S3. Construct a global state data model and encapsulate the device control data of all stage control channels through the global state data model; S4. The main control periodically polls the global state data model, drives its own graphics rendering engine to render the device control data for each group of stage control channels, generates a visualization interface, and publishes the incremental change data of the global state data model to the slave stage control channel through the DDS protocol. S5. The incremental change data is received and parsed from the stage control channel, the local model is updated and the visualization interface is re-rendered to maintain consistency with the display of the main stage control channel. S6. In response to the handover command, the main stage control channel generates a handover request containing the target slave stage control channel identifier and a temporary authentication code and broadcasts it. After the slave stage control channel is authenticated, the control is transferred to the target slave stage control channel to become the new main stage control channel. S7. If control needs to be reclaimed, the original initial console sends a priority permission reclamation request to the new main stage control channel.

[0007] Preferably, step S2 specifically includes: S21. Scan the stage equipment network in real time, capture equipment broadcast data packets and extract physical layer features and application layer features to generate equipment fingerprint vectors; S22. Analyze the hardware configuration and software strategy of each stage control channel to construct a channel capability matrix; S23. Input the device fingerprint vector and channel capability matrix into the pre-trained Siamese neural network, calculate the matching score and output the candidate channel list; S24. Based on the candidate channel list, the candidate stage control channel and the target stage equipment perform an adaptive protocol handshake and confirm the security binding. S25. Establish a secure tunnel through PAM to complete parameter configuration and record the binding relationship to the distributed ledger to achieve non-repudiation authentication.

[0008] Preferably, the equipment control data in step S3 includes static information, dynamic information, and alarm information; the static information includes channel name, channel number, equipment name, equipment number, and rated load; the dynamic information includes real-time load value and visual progress bar, equipment target position and value, running speed value and direction vector diagram; the alarm information includes graded alarm status indication and historical alarm log.

[0009] Preferably, the control permission token is generated and managed by the HSM hardware security module, and its lifecycle state changes are recorded in the blockchain node. The underlying driver of the stage equipment is configured to execute only control commands from the main stage control channel holding the control permission token.

[0010] Preferably, step S6 specifically includes: S61. In response to the handover command, the main stage control channel actively initiates the handover and, after successful authentication from the stage control channel, executes the transfer of control. S61. The main stage control channel generates a handover request broadcast, the request containing the target stage control channel identifier and a temporary authentication code; S62. The target receives a request from the stage control channel, verifies the operator's identity, and then returns a confirmation signal. S63. After successful verification, the main stage control channel will encrypt and transmit the current control context and permission token to the target secondary stage control channel, clear its own instruction queue, and switch to read-only monitoring mode. S64. After obtaining the token and context from the stage control channel, the target becomes the new master stage control channel and takes over control of the stage equipment.

[0011] Preferably, in the read-only monitoring mode, the main stage control channel or the stage control channel receives and displays all device control data information and views alarm logs in real time, but all input controls in its interface are disabled by software, and the output signal of its physical controller is cut off by hardware relays, making it impossible to modify any device parameters or confirm global alarms.

[0012] Preferably, during the handover of control, the system enters a command silence period, during which all main stage control channels and secondary stage control channels are unable to issue new control commands to the stage equipment. All stage equipment maintains its motion state at the last moment before the handover or performs preset safety hold actions. After the handover is completed, the new main stage control channel takes over control and unlocks the system.

[0013] Preferably, the control context includes the real-time target positions of all stage equipment, the queue of unexecuted motion commands, the currently effective equipment operation rules, and the grouping synchronization relationships.

[0014] Preferably, step S7 specifically includes: S71. If control needs to be reclaimed, the system administrator or the original initial console shall send a priority permission reclamation request to the new main stage control channel. S72. The current main stage control channel stops outputting control commands immediately or after a delay based on the request priority, and returns the latest context and control permission token to the initial main stage control channel, and automatically switches to read-only monitoring mode.

[0015] Preferably, the priority of the permission revocation request includes advanced emergency revocation and normal safe revocation. Advanced emergency revocation is to immediately interrupt all current control commands and forcibly revoke the permission. Normal safe revocation is to wait for the current motion command to be executed to a safe position or for a control cycle to end before revoking the permission.

[0016] By adopting the above technical solution, the present invention has the following advantages compared with the prior art: 1. This invention provides a method for multi-control console linkage control of stage equipment. By using a unique control permission token mechanism and configuring the driver at the hardware level to only respond to the main stage control channel holding the control permission token, it ensures that only one control source can output valid commands at any given time, completely avoiding command conflicts that may be caused by multiple console operations, and greatly improving the security and reliability of the system.

[0017] 2. This invention provides a method for multi-group console linkage control of stage equipment. By constructing a unified global state data model and adopting an incremental data publish-subscribe mechanism based on the DDS data distribution service protocol, the main stage control channel only synchronizes incremental change data of the state model, rather than the full data. This greatly reduces network bandwidth usage and synchronization latency, enabling all slave stage control channels to update their local interfaces in near real-time and maintain a high degree of display consistency with the main stage control channel, providing operators with an accurate and reliable global monitoring view.

[0018] 3. This invention provides a method for multi-control console linkage control of stage equipment, where the transfer of control is no longer a simple and crude permission switch. By generating an encrypted transfer request containing a temporary authentication code, verifying the operator's identity, and encrypting the transmission of control context and permission token, the security and legality of the transfer operation are ensured. After the transfer, the new main stage control channel can immediately and seamlessly take over all unfinished instructions and equipment status, ensuring the continuity of the performance or operation.

[0019] 4. This invention provides a method for multi-group console linkage control of stage equipment. It sets a command silence period. During the brief process of handing over control, all equipment maintains its original state or performs safety actions to prevent equipment malfunctions caused by command interruption or conflict. At the same time, the permission revocation mechanism is designed with priority, which can not only deal with emergency intervention in sudden situations, but also smoothly transition under normal circumstances, reflecting a flexible safety strategy. Attached Figure Description

[0020] Figure 1 This is a flowchart of the method of the present invention. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention. Example

[0022] Please refer to Figure 1 As shown, this invention discloses a method for multi-control console linkage control of stage equipment. This method is based on multiple control consoles, and each control console is equipped with several stage control channels. Specifically, it includes the following steps: S1. Set one stage control channel on any console as the main stage control channel and configure a unique control permission token to send control commands to the stage equipment. The stage control channel will automatically enter read-only monitoring mode. S2. Based on the dynamic authentication of device fingerprints and stage control channels, each group of stage control channels is adaptively matched and securely bound to the target stage equipment. S3. Construct a global state data model and encapsulate the device control data of all stage control channels through the global state data model; S4. The main control periodically polls the global state data model, drives its own graphics rendering engine to render the device control data for each group of stage control channels, generates a visualization interface, and publishes the incremental change data of the global state data model to the slave stage control channel through the DDS protocol. S5. The incremental change data is received and parsed from the stage control channel, the local model is updated and the visualization interface is re-rendered to maintain consistency with the display of the main stage control channel. S6. In response to the handover command, the main stage control channel generates a handover request containing the target slave stage control channel identifier and a temporary authentication code and broadcasts it. After the slave stage control channel is authenticated, the control is transferred to the target slave stage control channel to become the new main stage control channel. S7. If control needs to be reclaimed, the original initial console sends a priority permission reclamation request to the new main stage control channel.

[0023] Step S2 is as follows: S21. Scan the stage equipment network in real time, capture equipment broadcast data packets and extract physical layer features and application layer features to generate equipment fingerprint vectors; S22. Analyze the hardware configuration and software strategy of each stage control channel to construct a channel capability matrix; S23. Input the device fingerprint vector and channel capability matrix into the pre-trained Siamese neural network, calculate the matching score and output the candidate channel list; S24. Based on the candidate channel list, the candidate stage control channel and the target stage equipment perform an adaptive protocol handshake and confirm the security binding. S25. Establish a secure tunnel through PAM to complete parameter configuration and record the binding relationship to the distributed ledger to achieve non-repudiation authentication.

[0024] In step S3, the equipment control data includes static information, dynamic information, and alarm information; static information includes channel name, channel number, equipment name, equipment number, and rated load; dynamic information includes real-time load value and visual progress bar, equipment target position and value, running speed value and direction vector diagram; alarm information includes graded alarm status indication and historical alarm log.

[0025] The control permission token is generated and managed by the HSM hardware security module, and its lifecycle state changes are recorded in the blockchain node. The underlying driver of the stage equipment is configured to execute only control commands from the main stage control channel that holds the control permission token.

[0026] Step S6 is as follows: S61. In response to the handover instruction, the main stage control channel initiates the handover and, after successful authentication from the stage control channel, executes the transfer of control. S61. The main stage control channel generates a handover request broadcast, which includes the target stage control channel identifier and a temporary authentication code. S62. The target receives a request from the stage control channel, verifies the operator's identity, and then returns a confirmation signal. S63. After successful verification, the main stage control channel will encrypt and transmit the current control context and permission token to the target secondary stage control channel, clear its own instruction queue, and switch to read-only monitoring mode. S64. After obtaining the token and context from the stage control channel, the target becomes the new master stage control channel and takes over control of the stage equipment.

[0027] In read-only monitoring mode, the main stage control channel or the stage control channel can receive and display all equipment control data and view alarm logs in real time. However, all input controls in the interface are disabled by the software, and the output signal of the physical controller is cut off by the hardware relay, making it impossible to modify any equipment parameters or confirm global alarms.

[0028] During the handover of control, the system enters a command silence period. All main stage control channels and secondary stage control channels are unable to issue new control commands to the stage equipment. All stage equipment maintains its motion state at the last moment before the handover or performs preset safety hold actions. After the handover is completed, the new main stage control channel takes over control and unlocks the system.

[0029] The control context includes the real-time target positions of all stage equipment, the queue of unexecuted motion commands, the currently effective equipment operation rules, and group synchronization relationships.

[0030] Step S7 is as follows: S71. If control needs to be reclaimed, the system administrator or the original initial console shall send a priority permission reclamation request to the new main stage control channel. S72. The current main stage control channel stops outputting control commands immediately or after a delay based on the request priority, and returns the latest context and control permission token to the initial main stage control channel, and automatically switches to read-only monitoring mode.

[0031] The priority of permission revoke requests includes advanced emergency revoke and normal safe revoke. Advanced emergency revoke immediately interrupts all current control commands and forcibly revokes permissions, while normal safe revoke waits for the current motion command to be executed to a safe position or for a control cycle to end before revoking permissions.

[0032] The above are merely preferred embodiments of the present invention, but the scope of protection of the present invention 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 the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for coordinated control of multiple control consoles for stage equipment, characterized in that: This method is implemented using multiple consoles, each with several stage control channels, and includes the following steps: S1. Set one stage control channel on any console as the main stage control channel and configure a unique control permission token to send control commands to the stage equipment. The stage control channel will automatically enter read-only monitoring mode. S2. Based on the dynamic authentication of device fingerprints and stage control channels, each group of stage control channels is adaptively matched and securely bound to the target stage equipment. S3. Construct a global state data model and encapsulate the device control data of all stage control channels through the global state data model; S4. The main control periodically polls the global state data model, drives its own graphics rendering engine to render the device control data for each group of stage control channels, generates a visualization interface, and publishes the incremental change data of the global state data model to the slave stage control channel through the DDS protocol. S5. The incremental change data is received and parsed from the stage control channel, the local model is updated and the visualization interface is re-rendered to maintain consistency with the display of the main stage control channel. S6. In response to the handover command, the main stage control channel generates a handover request containing the target slave stage control channel identifier and a temporary authentication code and broadcasts it. After the slave stage control channel is authenticated, the control is transferred to the target slave stage control channel to become the new main stage control channel. S7. If control needs to be reclaimed, the original initial console sends a priority permission reclamation request to the new main stage control channel.

2. The method for multi-group control console linkage of stage equipment as described in claim 1, characterized in that: Step S2 is as follows: S21. Scan the stage equipment network in real time, capture equipment broadcast data packets and extract physical layer features and application layer features to generate equipment fingerprint vectors; S22. Analyze the hardware configuration and software strategy of each stage control channel to construct a channel capability matrix; S23. Input the device fingerprint vector and channel capability matrix into the pre-trained Siamese neural network, calculate the matching score and output the candidate channel list; S24. Based on the candidate channel list, the candidate stage control channel and the target stage equipment perform an adaptive protocol handshake and confirm the security binding. S25. Establish a secure tunnel through PAM to complete parameter configuration and record the binding relationship to the distributed ledger to achieve non-repudiation authentication.

3. The method for multi-group control console linkage of stage equipment as described in claim 1, characterized in that: The equipment control data in step S3 includes static information, dynamic information, and alarm information; the static information includes channel name, channel number, equipment name, equipment number, and rated load; the dynamic information includes real-time load value and visual progress bar, equipment target position and value, running speed value and direction vector diagram; the alarm information includes graded alarm status indication and historical alarm log.

4. The method for multi-group control console linkage of stage equipment as described in claim 1, characterized in that: The control permission token is generated and managed by the HSM hardware security module, and its lifecycle state changes are recorded in the blockchain node. The underlying driver of the stage equipment is configured to execute only control commands from the main stage control channel that holds the control permission token.

5. The method for multi-group control console linkage of stage equipment as described in claim 1, characterized in that: Step S6 is as follows: S61. In response to the handover command, the main stage control channel actively initiates the handover and, after successful authentication from the stage control channel, executes the transfer of control. S61. The main stage control channel generates a handover request broadcast, the request containing the target stage control channel identifier and a temporary authentication code; S62. The target receives a request from the stage control channel, verifies the operator's identity, and then returns a confirmation signal. S63. After successful verification, the main stage control channel will encrypt and transmit the current control context and permission token to the target secondary stage control channel, clear its own instruction queue, and switch to read-only monitoring mode. S64. After obtaining the token and context from the stage control channel, the target becomes the new master stage control channel and takes over control of the stage equipment.

6. The method for multi-group control console linkage of stage equipment as described in claim 5, characterized in that: In the read-only monitoring mode, the main stage control channel or the stage control channel receives and displays all device control data information and views alarm logs in real time, but all input controls in its interface are disabled by the software, and the output signal of its physical controller is cut off by the hardware relay, making it impossible to modify any device parameters or confirm global alarms.

7. The method for multi-group control console linkage of stage equipment as described in claim 5, characterized in that: During the handover of control, the system enters a command silence period. All main stage control channels and secondary stage control channels are unable to issue new control commands to the stage equipment. All stage equipment maintains its motion state at the last moment before the handover or performs preset safety hold actions. After the handover is completed, the new main stage control channel takes over control and unlocks the system.

8. The method for multi-group control console linkage of stage equipment as described in claim 5, characterized in that: The control context includes the real-time target positions of all stage equipment, the queue of unexecuted motion commands, the currently effective equipment operation rules, and grouping synchronization relationships.

9. The method for multi-group control console linkage of stage equipment as described in claim 1, characterized in that: Step S7 is as follows: S71. If control needs to be reclaimed, the system administrator or the original initial console shall send a priority permission reclamation request to the new main stage control channel. S72. The current main stage control channel stops outputting control commands immediately or after a delay based on the request priority, and returns the latest context and control permission token to the initial main stage control channel, and automatically switches to read-only monitoring mode.

10. The method for multi-group control console linkage of stage equipment as described in claim 1, characterized in that: The priority of the permission revoke request includes advanced emergency revoke and normal safe revoke. Advanced emergency revoke immediately interrupts all current control commands and forcibly revokes permissions. Normal safe revoke waits for the current motion command to be executed to a safe position or for a control cycle to end before revoking permissions.

Images