Multi-device cooperative control system

Abstract

The utility model relates to the technical field of equipment coordination, and discloses a multi-equipment coordination control system, which comprises user equipment and a server, and is characterized in that the user equipment comprises main control equipment and at least one coordination equipment, and the main control equipment is connected with the coordination equipment in a wired or wireless manner; the server establishes communication connection with the main control equipment; the main control equipment comprises a first communication interface, a first processor and a first storage module; the cooperative device comprises a second communication interface and an execution module. According to the utility model, through optimizing the communication interface design of the master control device and the cloud instance, the efficient and stable client device cluster physical networking topology is constructed, the hardware module layout is innovated, and the hardware-level security protection structure is strengthened; the problems of unstable equipment connection, poor module collaboration, weak safety protection and the like in the system structure level in the prior art are solved, dynamic permission adjustment, intelligent task allocation and automatic switching after main control equipment fails are realized, and the performance and reliability of multi-equipment cooperative control are improved.

Description

Technical Field

[0001] This utility model relates to the field of equipment collaboration technology, specifically to a multi-device collaborative control system. Background Technology

[0002] In the fields of cloud computing and distributed collaborative control technology, the application scenarios for multi-device collaborative control of cloud mobile phone instances are becoming increasingly diverse, covering areas such as enterprise team collaboration, multi-user sharing in homes, and cross-device task distribution. Operating the same cloud mobile phone instance collaboratively across multiple devices can effectively improve resource utilization efficiency and user convenience. However, current technologies have many shortcomings in system architecture design, severely limiting the performance and reliability of multi-device collaborative control.

[0003] From the perspective of device connectivity, existing systems often employ low-bandwidth, high-latency connection methods in the communication interface design between the main control device and cloud instances. This fails to meet the demands of real-time interaction of large amounts of data, leading to lag in collaborative operations. The physical network topology of client device clusters lacks flexibility. For example, some systems use a chain-like topology, where a failure of an intermediate node interrupts the entire collaborative link, making it difficult to guarantee the stability and security of data transmission. Regarding hardware module layout, the functional divisions of main control devices, auxiliary devices, and restricted devices are unclear, lacking hardware modules adapted to specific tasks. For instance, some devices, while possessing screen display capabilities, lack corresponding high-performance graphics processing modules, resulting in slow processing of complex graphics tasks. Furthermore, the lack of efficient collaboration mechanisms between devices prevents the full utilization of each device's hardware advantages. Security protection structures also have significant shortcomings. Existing systems largely rely on software encryption, lacking hardware-level security measures, making them vulnerable to physical attacks. Additionally, the device casings lack physical protection structures such as anti-tampering circuits, making it easy for sensitive data to be leaked if the device is illegally disassembled, failing to meet the collaborative control needs of complex environments such as enterprise applications and smart home scenarios. Utility Model Content

[0004] This utility model provides a multi-device collaborative control system that solves system structure problems such as unstable device connections, poor module collaboration, and weak security protection in the prior art by optimizing the communication interface design between the master control device and the cloud instance, constructing an efficient and stable physical network topology for the client device cluster, innovating hardware module layout, and strengthening hardware-level security protection structure. It achieves dynamic permission adjustment, intelligent task allocation, and automatic switching after the failure of the master control device, thereby improving the performance and reliability of multi-device collaborative control.

[0005] To achieve the above objectives, the embodiments of this utility model adopt the following technical solutions:

[0006] In a first aspect, this utility model provides a multi-device collaborative control system, the system comprising: user equipment and server, wherein the user equipment includes a main control device and at least one collaborative device, and the main control device and the collaborative device are connected via wired or wireless means;

[0007] The server is used to receive authentication information from the main control device and operating status parameters of the collaborative device, and to establish a communication connection with the main control device.

[0008] The main control device includes a first communication interface, a first processor, and a first storage module. The first communication interface is used to establish a session channel with the server and the collaborative device. The first processor is used to obtain the operating status parameters of the collaborative device based on the session channel and generate a permission allocation matrix and a set of differentiated instructions. The first storage module is used to store the authentication information and the permission allocation matrix.

[0009] The collaborative device includes a second communication interface and an execution module. The second communication interface is used to receive the differentiated instruction set, and the execution module is used to perform synchronization control operations according to the differentiated instruction set.

[0010] Furthermore, the first communication interface of the main control device includes a high-speed communication module and a two-way encryption module. The high-speed communication module is used to establish a data connection with the server, and the two-way encryption module is used to generate a session identifier based on the authentication information to establish a session channel between the main control device and the collaborative device.

[0011] Furthermore, the operating status parameters of the collaborative device include hardware performance indicators, network connectivity indicators, and historical task execution indicators;

[0012] The first processor of the main control device includes: a parameter extraction unit, a capability evaluation unit, and a permission allocation unit;

[0013] The parameter extraction unit is used to extract the hardware performance indicators, network connection indicators, and historical task execution indicators from the running status parameters.

[0014] The capability assessment unit has a built-in device capability assessment model, which is used to generate a performance score for the collaborative device based on the indicators.

[0015] The permission allocation unit is used to allocate functional permissions to the collaborative device according to the performance score and generate the permission allocation matrix.

[0016] Furthermore, the first processor of the main control device also includes: a task parsing unit and an instruction generation unit;

[0017] The task parsing unit is used to parse the task requirements of the master control device based on the permission allocation matrix and determine the device permission range;

[0018] The instruction generation unit is used to extract the operation fields in the task requirements according to the device permission scope, and generate a set of differentiated instructions that match the functional permissions of the collaborative device.

[0019] Furthermore, the second communication interface of the collaborative device includes: an instruction receiving module and a progress feedback module;

[0020] The instruction receiving module is used to receive the differentiated instruction set through the session channel;

[0021] The progress feedback module is used to return the instruction execution progress to the main control device.

[0022] Furthermore, the first processor of the main control device also includes an anomaly detection unit, used to determine whether there is an execution anomaly based on the execution progress, and if so, to trigger the first communication interface to perform a reconnection operation to the collaborative device.

[0023] Furthermore, the server also includes a result verification module, used to obtain and verify the operation results of the collaborative device. If the verification results are inconsistent, a conflict resolution mechanism is triggered to generate a correction instruction, which is then sent to the corresponding collaborative device through the main control device.

[0024] Furthermore, the first processor of the main control device also includes: a heartbeat monitoring unit, used to monitor the heartbeat signal of the main control device in the session channel and determine the device status of the main control device;

[0025] Furthermore, the server also includes a master control switching module, used to filter candidate devices with master control function permissions based on the permission allocation matrix when the master control device is in a failed state, and to determine the candidate devices as the master control devices to be switched.

[0026] Furthermore, the main control device and the collaborative device form a star topology, with the main control device serving as the central node and the collaborative device serving as the auxiliary node.

[0027] The multi-device collaborative control system provided in this embodiment of the utility model has the following beneficial effects:

[0028] The system provided in this embodiment of the utility model achieves efficient collaboration and precise control by constructing a layered architecture of user equipment and server. In terms of device connection structure, the wired / wireless connection between the main control device and the collaborative devices, combined with the session channel establishment function of the first communication interface, ensures stable data transmission with low latency. The server's processing of authentication information and operating status parameters provides data support for the main control device to generate a permission allocation matrix and a differentiated instruction set, realizing dynamic permission management and intelligent task allocation. At the hardware module level, the first processor and first storage module integrated in the main control device, and the second communication interface and execution module of the collaborative devices, have clear division of labor and close cooperation. The first processor optimizes task scheduling based on operating status parameters, and the execution module accurately executes instructions, significantly improving task execution efficiency. Simultaneously, the system architecture design allows for rapid transfer of control based on the permission allocation matrix when the main control device fails, ensuring the continuity of collaborative operations and effectively solving structural problems in the prior art such as unstable device connections, permission conflicts, inefficient task allocation, and untimely device switching. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of this utility model or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this utility model. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 A schematic diagram of the structure of the multi-device collaborative control system provided in this embodiment of the utility model;

[0031] Figure 2 A schematic diagram of another multi-device collaborative control system provided in this embodiment of the present invention;

[0032] Figure 3 A schematic diagram of the structure of another multi-device collaborative control system provided in this embodiment of the utility model;

[0033] Figure 4 This is a schematic diagram of the structure of another multi-device collaborative control system provided in an embodiment of the present utility model. Detailed Implementation

[0034] The technical solutions of the present utility model will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of the present utility model, and not all embodiments. Based on the embodiments of the present utility model, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of the present utility model.

[0035] Figure 1 This is a schematic diagram of the structure of a multi-device collaborative control system provided in an embodiment of the present invention. The system includes: user equipment 100 and server 200, wherein the user equipment 100 includes a main control device 110 and at least one collaborative device 120, and the main control device 110 and the collaborative device 120 are connected via wired or wireless means;

[0036] Server 200 is used to receive authentication information from main control device 110 and operating status parameters from collaborative device 120, and to establish a communication connection with main control device 110.

[0037] The main control device 110 includes a first communication interface 111, a first processor 112, and a first storage module 113. The first communication interface 111 is used to establish a session channel with the server 200 and the collaborative device 120. The first processor 112 is used to obtain the operating status parameters of the collaborative device 120 based on the session channel and generate a permission allocation matrix and a set of differentiated instructions. The first storage module 113 is used to store authentication information and the permission allocation matrix.

[0038] The collaborative device 120 includes a second communication interface 121 and an execution module 122. The second communication interface 121 is used to receive a differentiated instruction set, and the execution module 122 is used to perform synchronous control operations according to the differentiated instruction set.

[0039] It should be noted that the structural diagram of the main control device 110 is as follows: Figure 2 As shown, the main control device 110 includes: a first communication interface 111, a first processor 112, and a first storage module 113. The first communication interface 111 is communicatively connected to the first processor 112. The first processor 112 is communicatively connected to both the first communication interface 111 and the first storage module 113. The first storage module 113 is communicatively connected to the first processor 112. A schematic diagram of the collaborative device 120 is shown below. Figure 3 As shown, the collaborative device 120 includes a second communication interface 121 and an execution module 122, with the second communication interface 121 and the execution module 122 being communicatively connected.

[0040] Specifically, the multi-device collaborative control system of this utility model adopts a distributed architecture, consisting of user equipment 100 (main control device 110 + collaborative device 120) and server 200: the main control device 110 connects to the collaborative device 120 via wired / wireless means (USB / Ethernet / Wi-Fi / Bluetooth) to form a star topology; the server 200 receives the authentication information of the main control device 110 and the status parameters (hardware performance / network status) of the collaborative device 120, and establishes a communication link; the first communication interface 111 of the main control device 110 uses 5G / Wi-Fi 6 to connect to the server 200 at high speed, and at the same time establishes a secure session channel with the collaborative device 120 through a two-way encryption module; the first processor 112 obtains the device status parameters based on the session channel, generates a dynamic permission allocation matrix and a set of differentiated instructions (stored in the first storage module 113); the second communication interface 121 of the collaborative device 120 receives the differentiated instructions, and the execution module 122 calls local resources to perform operations. This architecture solves the problems of permission conflicts and rigid task allocation in traditional systems through hardware-level secure communication, dynamic permission management, and intelligent task scheduling, thereby achieving efficient, secure, and flexible multi-device collaborative control.

[0041] As an example, the workflow of a multi-device collaborative control system, such as Figure 4 As shown, the process includes: In the multi-device collaborative control system, after the server receives the authentication information from the master control device 110 and the operating status parameters of the collaborative device 120, it establishes a communication connection with the master control device 110. The master control device 110 establishes a session channel with the server 200 and the collaborative device 120 through the first communication interface 111. Its first processor 112 extracts hardware performance indicators, network connection indicators, historical task execution indicators, etc. from the operating status parameters of the collaborative device 120. Based on the built-in device capability evaluation model, a performance score for the collaborative device 120 is generated. Accordingly, the permission allocation unit assigns functional permissions to the collaborative device 120, generating a permission allocation matrix. At the same time, the task parsing unit parses the task requirements of the master control device 110 based on the permission allocation matrix, determines the device permission range, and the instruction generation unit extracts the operation fields in the task requirements according to the range, generates a differentiated instruction set that matches the functional permissions of the collaborative device 120, and sends it to the collaborative device 120 through the first communication interface 111. The second communication interface 121 of the collaborative device 120 receives a set of instructions, and the execution module 122 performs synchronous control operations accordingly, returning the execution progress to the master control device 110 through the progress feedback module. The first processor 112 of the master control device 110 can determine whether there is an execution abnormality based on the progress. If so, it triggers the first communication interface 111 to perform a reconnection operation to the collaborative device 120. The server 200 obtains the operation results of the collaborative device 120 and verifies them. If there is an inconsistency, it triggers a conflict resolution mechanism to generate a correction instruction, which is sent to the collaborative device 120 via the master control device 110.

[0042] As an optional solution of this utility model, the first communication interface 111 of the main control device 110 includes: a high-speed communication module and a two-way encryption module. The high-speed communication module is used to establish a data connection with the server 200, and the two-way encryption module is used to generate a session identifier based on authentication information and establish a session channel between the main control device 110 and the cooperating device 120.

[0043] Specifically, the main control device 110 achieves efficient and secure data interaction through the dual-module architecture of the first communication interface 111: the high-speed communication module uses 5G / Wi-Fi 6 technology to establish a low-latency, high-bandwidth connection with the server 200, and quickly transmits authentication information and device status parameters; the two-way encryption module generates a unique session identifier based on the authentication information, and after verifying the identity of the cooperating device 120 through the handshake protocol, establishes a secure session channel using symmetric / asymmetric encryption technology, realizing real-time encryption / decryption of data transmission, ensuring the efficiency and security of system communication from the hardware level, and solving the problems of easy data leakage and high transmission latency in traditional systems.

[0044] As an optional solution of this utility model, the operating status parameters of the collaborative device 120 include hardware performance indicators, network connection indicators, and historical task execution indicators; the first processor 112 of the main control device 110 includes: a parameter extraction unit, a capability evaluation unit, and a permission allocation unit; the parameter extraction unit is used to extract hardware performance indicators, network connection indicators, and historical task execution indicators from the operating status parameters; the capability evaluation unit has a built-in device capability evaluation model and is used to generate a performance score for the collaborative device 120 based on the indicators; the permission allocation unit is used to allocate functional permissions to the collaborative device 120 based on the performance score and generate a permission allocation matrix.

[0045] Specifically, the main control device 110 achieves dynamic management of the collaborative device 120 through a three-level processing architecture of the first processor 112: the parameter extraction unit filters key data from the hardware performance, network connection, and historical task execution indicators uploaded in real time by the collaborative device 120; the capability assessment unit quantifies and scores the extracted indicators (0-100 points) using a preset machine learning model or weighted scoring algorithm; and the permission allocation unit dynamically generates a permission allocation matrix (stored in the first storage module 113) containing device identifiers, permission levels, and executable operations based on the scoring results and preset strategies (such as granting full-function permissions to high-scoring devices). This architecture solves the resource mismatch problem caused by static permission management in traditional systems through closed-loop processing from data acquisition and capability assessment to dynamic permission allocation, and realizes intelligent task scheduling and security control based on the real-time status of devices.

[0046] As an optional solution of this utility model, the first processor 112 of the main control device 110 further includes: a task parsing unit and an instruction generation unit; the task parsing unit is used to parse the task requirements of the main control device 110 based on the permission allocation matrix and determine the device permission range; the instruction generation unit is used to extract the operation fields in the task requirements according to the device permission range and generate a differentiated instruction set that matches the functional permissions of the cooperating device 120.

[0047] Specifically, the main control device 110 achieves precise task allocation through a two-level processing mechanism of a task parsing unit and an instruction generation unit: the task parsing unit retrieves the permission allocation matrix from the first storage module 113, compares the user's task requirements with the permission range of each collaborative device 120 (e.g., filtering devices with data write permissions), and determines the list of executable tasks and operation boundaries; based on the parsing results, the instruction generation unit deeply decomposes the task requirements, extracts specific operation fields (e.g., calling the camera), and generates differentiated instruction sets according to the device's functional characteristics (e.g., high-performance devices handle complex calculations, while lightweight devices are responsible for data display), while embedding permission verification tags to ensure that instructions are executed only within the permission range. This architecture solves the problems of rigid task allocation and weak permission control in traditional systems by coordinating permission-driven task allocation with function-adaptive instruction generation, achieving efficient collaboration and security management among multiple devices.

[0048] As an optional solution of this utility model, the second communication interface 121 of the collaborative device 120 includes: an instruction receiving module and a progress feedback module; the instruction receiving module is used to receive a set of differentiated instructions through a session channel; the progress feedback module is used to return the instruction execution progress to the main control device 110.

[0049] Specifically, the second communication interface 121 of the collaborative device 120 consists of an instruction receiving module and a progress feedback module. The instruction receiving module receives a set of differentiated instructions issued by the main control device 110 through a session channel established with the main control device 110, and transmits the instructions to the execution module 122. The progress feedback module monitors the instruction execution status in real time and transmits the execution progress back to the main control device 110 in real time. This dual-module structure realizes bidirectional interaction between instruction transmission and execution status feedback, ensuring that the main control device can promptly grasp the working status of the collaborative device, providing data support for dynamic task scheduling and optimization.

[0050] As an optional solution of this utility model, the first processor 112 of the main control device 110 further includes: an anomaly detection unit, used to determine whether there is an execution anomaly based on the execution progress, and if so, to trigger the first communication interface 111 to perform a reconnection operation to the cooperating device 120.

[0051] Specifically, the first processor 112 of the main control device 110 integrates an anomaly detection unit. This unit determines in real time whether there are execution anomalies, such as instruction execution timeouts or progress stalls, based on the instruction execution progress returned by the collaborative device 120 through the progress feedback module. Once an anomaly is detected, the anomaly detection unit immediately triggers the first communication interface 111 to perform a reconnection operation on the collaborating device with the anomaly, attempting to restore communication and task execution. This structural design effectively improves the system's self-healing capability against device failures and task anomalies, ensuring the continuity and stability of multi-device collaborative operations.

[0052] As an optional solution of this utility model, the server 200 further includes: a result verification module, which is used to obtain the operation result of the collaborative device 120 and verify it. If the verification result is inconsistent, a conflict resolution mechanism is triggered to generate a correction instruction, which is sent to the corresponding collaborative device 120 through the master control device 110.

[0053] Specifically, server 200 is configured with a result verification module to collect the operation results of each collaborative device 120 after completing its task and verify the results according to preset rules. When the verification finds inconsistencies in the results (such as data conflicts or contradictory calculation results), the result verification module automatically triggers a conflict resolution mechanism and generates correction instructions. These correction instructions are forwarded to the corresponding collaborative device 120 through the master control device 110 to correct execution deviations. This structure ensures the consistency and accuracy of the results of multi-device collaborative operations and avoids task failures due to data conflicts.

[0054] As an optional solution of this utility model, the first processor 112 of the main control device 110 further includes: a heartbeat monitoring unit, used to monitor the heartbeat signal of the main control device 110 in the session channel and determine the device status of the main control device 110;

[0055] Specifically, the first processor 112 of the main control device 110 is equipped with a heartbeat monitoring unit. This unit continuously monitors the heartbeat signal of the main control device in the session channel and judges the operating status of the main control device itself by the stability of the heartbeat signal, such as normal operation, abnormal lag, or failure. This real-time monitoring mechanism provides data basis for the status management of the main control device and lays the foundation for system fault early warning and emergency handling.

[0056] As an optional solution of this utility model, the server 200 further includes: a master control switching module, which is used to filter candidate devices with master control function permissions based on the permission allocation matrix when the master control device 110 is in a failed state, and determine the candidate devices as the target master control devices to be switched.

[0057] Specifically, server 200 is equipped with a master control switching module. When the heartbeat monitoring unit determines that the master control device 110 is in a failed state, the master control switching module is immediately activated. Based on a pre-stored permission allocation matrix on the server, this module filters candidate devices with master control permissions from the collaborative devices and determines the target master control device to be switched to according to preset rules (such as device performance priority and historical task completion rate), thus completing the transfer of master control. This structural design enables automated and seamless switching of the system when the master control device fails, ensuring uninterrupted collaborative control of multiple devices.

[0058] As an optional solution of this utility model, the main control device 110 and the cooperating device 120 form a star topology, with the main control device 110 as the central node and the cooperating device 120 as the auxiliary node.

[0059] Specifically, the main control device 110 and the collaborative devices 120 are networked in a star topology, with the main control device 110 acting as the central node and the collaborative devices 120 acting as auxiliary nodes connected to the main control device. In this structure, the main control device can centrally manage and schedule all collaborative devices, achieving unified data distribution and collection; the auxiliary nodes communicate only with the central node, reducing the complexity of inter-device communication. The star topology offers good stability and scalability; the failure of a single auxiliary node does not affect the operation of other devices, and it facilitates the addition or removal of collaborative devices, adapting to multi-device collaborative application scenarios of varying scales.

Claims

1. A multi-device collaborative control system, characterized in that, The system includes: user equipment and server, wherein the user equipment includes a main control device and at least one collaborative device, and the main control device and the collaborative device are connected via wired or wireless means; The server is used to receive authentication information from the main control device and operating status parameters of the collaborative device, and to establish a communication connection with the main control device. The main control device includes a first communication interface, a first processor, and a first storage module. The first communication interface is used to establish a session channel with the server and the collaborative device. The first processor is used to obtain the operating status parameters of the collaborative device based on the session channel and generate a permission allocation matrix and a set of differentiated instructions. The first storage module is used to store the authentication information and the permission allocation matrix. The collaborative device includes a second communication interface and an execution module. The second communication interface is used to receive the differentiated instruction set, and the execution module is used to perform synchronization control operations according to the differentiated instruction set.

2. The system according to claim 1, characterized in that, The first communication interface of the main control device includes a high-speed communication module and a two-way encryption module. The high-speed communication module is used to establish a data connection with the server, and the two-way encryption module is used to generate a session identifier based on the authentication information to establish a session channel between the main control device and the collaborative device.

3. The system according to claim 1, characterized in that, The operating status parameters of the collaborative device include hardware performance indicators, network connectivity indicators, and historical task execution indicators. The first processor of the main control device includes: a parameter extraction unit, a capability evaluation unit, and a permission allocation unit; The parameter extraction unit is used to extract the hardware performance indicators, network connection indicators, and historical task execution indicators from the running status parameters. The capability assessment unit has a built-in device capability assessment model, which is used to generate a performance score for the collaborative device based on the indicators. The permission allocation unit is used to allocate functional permissions to the collaborative device according to the performance score and generate the permission allocation matrix.

4. The system according to claim 3, characterized in that, The first processor of the main control device further includes: a task parsing unit and an instruction generation unit; The task parsing unit is used to parse the task requirements of the master control device based on the permission allocation matrix and determine the device permission range; The instruction generation unit is used to extract the operation fields in the task requirements according to the device permission scope, and generate a set of differentiated instructions that match the functional permissions of the collaborative device.

5. The system according to claim 1, characterized in that, The second communication interface of the collaborative device includes: an instruction receiving module and a progress feedback module; The instruction receiving module is used to receive the differentiated instruction set through the session channel; The progress feedback module is used to return the instruction execution progress to the main control device.

6. The system according to claim 5, characterized in that, The first processor of the main control device further includes an anomaly detection unit, used to determine whether there is an execution anomaly based on the execution progress. If there is, the first communication interface is triggered to perform a reconnection operation on the collaborative device.

7. The system according to claim 5, characterized in that, The server further includes a result verification module, which is used to obtain and verify the operation results of the collaborative device. If the verification results are inconsistent, a conflict resolution mechanism is triggered to generate a correction instruction, which is then sent to the corresponding collaborative device through the main control device.

8. The system according to claim 1, characterized in that, The first processor of the main control device further includes a heartbeat monitoring unit, used to monitor the heartbeat signal of the main control device in the session channel and determine the device status of the main control device.

9. The system according to claim 8, characterized in that, The server further includes a master control switching module, which is used to filter candidate devices with master control function permissions based on the permission allocation matrix when the master control device is in a failed state, and determine the candidate devices as the master control devices to be switched.

10. The system according to claim 1, characterized in that, The main control device and the collaborative device form a star topology, with the main control device serving as the central node and the collaborative device serving as the auxiliary node.

Images