Equipment linkage control method and system and computer readable storage medium

Abstract

The invention provides an equipment linkage control method and system and a computer readable storage medium. The method comprises the following steps: if a cloud receives an instruction of deleting a target sub-device, updating a network distribution public key of the target sub-device to obtain an updated public key, issuing the updated public key to a host device, receiving the updated public key sent by the cloud by the host device, encrypting a target data packet in a preset linkage scene by using the updated public key to obtain an encrypted data packet, and sending the encrypted data packet to the cloud; the encrypted data packet is sent to the target sub-device, the target data packet corresponds to the target sub-device, and the target sub-device can only decrypt the data packet obtained by encrypting the distribution network public key. The method solves the problem that according to an existing device linkage control scheme, the sub-device is mistakenly controlled due to the fact that the sub-device deleted at the cloud still executes the corresponding instruction.

Description

Technical Field

[0001] The present application relates to the technical field of Internet of Things, and in particular to a device linkage control method, system and computer-readable storage medium. Background Art

[0002] Smart home scene linkage is to trigger the collaborative work of a series of devices through preset conditions (such as time, sensor status, user instructions, etc.) to achieve specific life scenes or functional requirements. In the smart home system, various devices are connected to each other through wireless communication technologies (such as Wi-Fi, Bluetooth, Zigbee, etc.) to form an intelligent network. When a preset condition is met, the system will automatically perform the corresponding action.

[0003] After the host device configures the network and sets the scene for its sub-device, because the sub-device is deployed under the host device (equivalent to the central control device), if a sub-device is deleted in the cloud, but the host device does not delete the information of this sub-device, the host device will still issue control instructions for the scene related to the sub-device, causing the sub-device deleted in the cloud to still execute the corresponding instructions, thus causing the sub-device to be miscontrolled. Summary of the invention

[0004] The main purpose of the present application is to provide a device linkage control method, system and computer-readable storage medium, so as to at least solve the problem that in the existing device linkage control scheme, the sub-device deleted in the cloud still executes the corresponding instructions, which causes the sub-device to be miscontrolled.

[0005] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a device linkage control method is provided, including: if an instruction to delete a target sub-device is received, the network configuration public key of the target sub-device is updated to obtain an updated public key; the updated public key is sent to a host device, so that the host device uses the updated public key to encrypt a target data packet in a preset linkage scenario to obtain an encrypted data packet, and then sends the encrypted data packet to the target sub-device, wherein the target data packet corresponds to the target sub-device, and the target sub-device can only decrypt the data packet encrypted using the network configuration public key.

[0006] Optionally, if an instruction to delete the target sub-device is received, the network configuration public key of the target sub-device is updated to obtain an updated public key, including: if an instruction to delete the target sub-device is received, the network configuration public key of the target sub-device is updated using kernel programming technology to obtain the updated public key.

[0007] Optionally, if an instruction to delete the target sub-device is received, kernel programming technology is used to update the network configuration public key of the target sub-device to obtain the updated public key, including: in response to the instruction to delete the target sub-device, running a custom program in the system kernel to update the network configuration public key of the target sub-device to obtain the updated public key.

[0008] Optionally, the method further includes: deleting relevant information of the target sub-device stored in the cloud database.

[0009] According to another aspect of the present application, a device linkage control method is provided, including: a host device receives an updated public key sent by a cloud, wherein the updated public key is obtained by the cloud updating a network configuration public key of a target sub-device in response to an instruction to delete the target sub-device; using the updated public key to encrypt a target data packet in a preset linkage scenario to obtain an encrypted data packet, and sending the encrypted data packet to the target sub-device, wherein the target data packet corresponds to the target sub-device, and the target sub-device can only decrypt the data packet encrypted using the network configuration public key.

[0010] Optionally, the host device and multiple sub-devices form a BLE network, the target sub-device is one of the multiple sub-devices, and the encrypted data packet is sent to the target sub-device, including: broadcasting the encrypted data packet in a BLE broadcast manner to send the encrypted data packet to the target sub-device.

[0011] Optionally, the host device and multiple sub-devices form a wifi network, and the method further includes: the host device obtains a heartbeat packet of any of the sub-devices through the wifi network; and determines whether the corresponding sub-device is online based on the heartbeat packet.

[0012] Optionally, the host device receives the updated public key sent by the cloud, including: the host device receives the updated public key sent by the cloud via a mobile data network.

[0013] According to another aspect of the present application, a device linkage control system is provided, comprising: a cloud, a host device and a plurality of sub-devices, wherein the cloud and the host device are used to execute the device linkage control method; and the plurality of sub-devices and the host device form a device network.

[0014] Optionally, the system further includes: a user terminal communicating with the cloud.

[0015] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute any one of the device linkage control methods.

[0016] By applying the technical solution of the present application, if an instruction to delete a target sub-device is received, the network configuration public key of the target sub-device is updated to obtain an updated public key, and the updated public key is sent to the host device. The host device receives the updated public key sent by the cloud, wherein the updated public key is obtained by the cloud in response to the instruction to delete the target sub-device to update the network configuration public key of the target sub-device, and the updated public key is used to encrypt the target data packet in the preset linkage scenario to obtain an encrypted data packet, and the encrypted data packet is sent to the target sub-device, wherein the target data packet corresponds to the target sub-device, and the target sub-device can only decrypt the data packet encrypted using the network configuration public key. This solution solves the problem that the sub-device deleted in the cloud still executes the corresponding instruction in the existing device linkage control solution, i.e., causes the sub-device to be miscontrolled. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings constituting part of the present application are used to provide a further understanding of the present application. The exemplary embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 A schematic diagram of a flow chart of a first device linkage control method provided according to an embodiment of the present application is shown;

[0019] Figure 2 A schematic diagram of a first device linkage control device provided according to an embodiment of the present application is shown;

[0020] Figure 3 A schematic diagram of a flow chart of a second device linkage control method provided according to an embodiment of the present application is shown;

[0021] Figure 4 A schematic diagram of a second device linkage control device provided according to an embodiment of the present application is shown;

[0022] Figure 5 A schematic diagram of a device linkage control system provided according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0023] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0024] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0026] As introduced in the background technology, in the prior art, if a sub-device is deleted in the cloud, but the information of this sub-device is not deleted in the host device, the host device still sends down control instructions for the scene related to the sub-device, causing the sub-device deleted in the cloud to still execute the corresponding instructions, i.e. causing the sub-device to be miscontrolled. In order to solve the problem that in the existing device linkage control scheme, the sub-device deleted in the cloud still executes the corresponding instructions, i.e. causing the sub-device to be miscontrolled, the embodiments of the present application provide a device linkage control method, system and computer-readable storage medium.

[0027] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0028] First aspect embodiment

[0029] In an embodiment of the present application, a first device linkage control method running on the cloud is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0030] Figure 1 is a flow chart of a first device linkage control method according to an embodiment of the present application. Figure 1 As shown, the method comprises the following steps:

[0031] Step S101: if an instruction to delete a target sub-device is received, the network configuration public key of the target sub-device is updated to obtain an updated public key.

[0032] Specifically, when the cloud receives an instruction to delete the target sub-device, it is necessary to execute the step of updating the network configuration public key of the target sub-device to ensure that the target sub-device will have difficulty responding to control instructions even if it receives subsequent control instructions. The cloud generates an updated public key, which is different from the original network configuration public key of the target sub-device and is usually designed to be invalid or mismatched with the original public key. Through this step, even if the network connection of the target sub-device is poor, it can be ensured that the device will no longer participate in scene linkage after being deleted, thereby avoiding miscontrol.

[0033] Step S102, the updated public key is sent to the host device, so that the host device uses the updated public key to encrypt the target data packet in the preset linkage scenario to obtain an encrypted data packet, and then sends the encrypted data packet to the target sub-device, wherein the target data packet corresponds to the target sub-device, and the target sub-device can only decrypt the data packet encrypted by using the distribution network public key.

[0034] Specifically, for example, in a smart home system, when the cloud receives a user's instruction to delete a sub-device (such as a smart light), the system needs to ensure that the device will not mistakenly perform any actions in the linkage scene in the future. If necessary, the system also removes the device's information from the database.

[0035] The specific process is as follows:

[0036] Generation and issuance of update public key: The cloud generates an update public key and then sends it to the host device. After receiving the update public key, the host device broadcasts it to all connected sub-devices via wireless communication methods such as Bluetooth.

[0037] Generation and sending of encrypted data packets: When the host device receives instructions in a preset linkage scenario, it will check whether the scenario contains a target sub-device that has been marked as to be deleted. If it does, the host device will use the updated public key (i.e., the updated public key mentioned above) to encrypt the data packet corresponding to the target sub-device and generate an encrypted data packet. The data packet may contain instructions, device status information, etc., which will be encrypted with the updated public key before being sent to ensure security.

[0038] Device decryption response: When the target sub-device receives an encrypted data packet, it will attempt to decrypt it using its own private key. For devices that have been deleted, since the updated public key does not match the original network public key, the target sub-device cannot correctly decrypt these data packets and will not execute the instructions in the data packet, effectively preventing the deleted device from continuing to participate in scene linkage.

[0039] During the specific implementation process, if an instruction to delete the target sub-device is received, the network configuration public key of the above target sub-device is updated to obtain the updated public key, including: if the above instruction to delete the target sub-device is received, the network configuration public key of the above target sub-device is updated to obtain the above updated public key using kernel programming technology.

[0040] Specifically, kernel programming technology is used to update the public key. This is because the device's network configuration public key and related encryption / decryption operations may be located in the operating system kernel, especially for those devices that involve direct hardware control or secure key storage. Through kernel programming, these low-level data can be securely accessed and modified, including updating the public key. Kernel programming technology to update keys usually involves low-level programming of the operating system and direct control of hardware or software.

[0041] Here are some specific implementation methods:

[0042] 1. Direct Memory Access (DMA):

[0043] By writing a kernel driver, you can directly access the key storage location in memory and update the key value. This method requires a deep understanding of hardware architecture and memory management.

[0044] 2. Hardware Security Module (HSM):

[0045] If the keys are stored in an HSM, you can update the keys by writing a kernel module that communicates with the HSM. This usually involves following the HSM's API and security protocols.

[0046] 3. Encryption device driver:

[0047] For hardware devices with integrated cryptographic capabilities, the device driver can be written or modified to update the key. This may involve programming the device firmware.

[0048] 4. Kernel encryption framework:

[0049] Many operating systems provide kernel-level encryption frameworks (such as Linux's CryptoAPI), and keys can be updated through the interfaces provided by these frameworks.

[0050] 5. File system operations:

[0051] If the key is stored in the file system, the key file can be updated through kernel-level file system operations. This may involve programming the VFS (Virtual File System) layer of the file system.

[0052] 6. Interrupt handling:

[0053] In some cases, updating keys may need to be done in a specific hardware interrupt context, which requires writing an interrupt handler.

[0054] 7. System calls:

[0055] New system calls can be created to update the keys in the kernel from user space. This approach requires implementing the system call interface in the kernel and ensuring security.

[0056] 8. Key Management Framework:

[0057] Use or develop a key management framework that can securely store, manage, and update keys in the kernel.

[0058] 9. Secure Boot:

[0059] During system startup, the integrity of the key can be updated or verified through the secure boot mechanism.

[0060] 10. Virtualization Technology:

[0061] In a virtualized environment, virtual machine keys can be managed in the kernel of the host machine.

[0062] Each method has its own specific application scenarios and security requirements. When implementing these methods, it is necessary to consider the security of the operating system, the lifecycle management of the key, the performance impact, and the compatibility with the existing system.

[0063] This embodiment adopts the eBPF (Extended Berkeley Packet Filter) kernel programming technology. eBPF is an extension of the traditional BPF (Berkeley Packet Filter) technology. eBPF allows users to run custom programs in the kernel of the Linux operating system. These programs can process, modify and monitor network packets, as well as other kernel events. The main advantages of eBPF include: eBPF programs run in the kernel, so they have higher performance, close to the hardware processing speed; eBPF programs are subject to strict security restrictions of the kernel and can only access limited kernel resources, reducing potential security risks; eBPF allows users to write custom programs to meet specific needs, such as network monitoring, performance analysis, security auditing, etc.; eBPF programs can run on different Linux systems and have good compatibility. The application scenarios of eBPF include but are not limited to:

[0064] Network monitoring: Monitor network traffic through eBPF programs, analyze network performance, and detect abnormal behavior.

[0065] Performance analysis: Use eBPF programs to monitor system performance, diagnose performance bottlenecks, and optimize system performance.

[0066] Security Audit: Use eBPF programs to perform security audits, detect potential security threats, and improve system security.

[0067] Network Function Virtualization: Network function virtualization is implemented through eBPF, such as load balancing, firewall, VPN, etc.

[0068] In short, eBPF is a powerful kernel programming technology that can provide users with efficient, flexible and secure network packet processing and kernel event monitoring capabilities.

[0069] During the specific implementation process, if the above-mentioned instruction to delete the target sub-device is received, the kernel programming technology is used to update the network configuration public key of the above-mentioned target sub-device to obtain the above-mentioned updated public key, including: in response to the above-mentioned instruction to delete the target sub-device, running a custom program in the system kernel to update the network configuration public key of the above-mentioned target sub-device to obtain the above-mentioned updated public key.

[0070] Specifically, in order to respond to the deletion instruction, and considering security and efficiency, the system needs to execute a custom program at the kernel level. The kernel is the core of the operating system, directly controlling computer hardware resources and providing underlying services, so operating at this level can more directly access and modify key data such as device keys. Custom programs can run in the kernel using eBPF (Extended Berkeley Packet Filter) or other similar technologies. The core function of the custom program is to update the network configuration public key of the target sub-device to a new, invalid update public key, which is different from the original public key of the device, meaning that any data packet encrypted with this public key will not be correctly decrypted by the device. This process ensures that no new control instructions will be executed even if the device is in a poor or disconnected network.

[0071] By executing a custom program at the kernel level to update the sub-device's network configuration public key, this mechanism can effectively prevent the deleted device from mistakenly executing actions in future scene linkages, protecting the user's security and privacy, and avoiding the waste of system resources. This method is particularly suitable for smart home network environments with a large number of devices and frequent scene linkages.

[0072] The embodiment of the present application also includes: deleting the relevant information of the above-mentioned target sub-device stored in the cloud database.

[0073] Specifically, for example, in a smart home system, when a user decides not to use a sub-device (such as a smart light, smart socket, etc.) and initiates a command to delete the device through an application, in addition to updating the network configuration public key of the device on the host device to prevent the device from receiving the command by mistake, the relevant information of the device stored in the cloud database needs to be deleted. The cloud database stores the status information of all registered devices, user settings, scene linkage rules, and network configuration information between devices. The system first locates the information related to the sub-device in the cloud database, which may include device ID, network configuration public key, private key, status information, user settings, etc. After determining the target device, the system performs a deletion operation to remove all information related to the device. This includes not only the basic information of the device, but also all scene linkage settings, historical records, etc. related to it. The deletion operation ensures the consistency of the system state and prevents future scene linkage attempts to communicate with the deleted device. By deleting the relevant information of the target sub-device stored in the cloud database, the system can not only technically achieve the complete removal of the device, but also maintain user privacy and data security.

[0074] In an embodiment of the present application, if an instruction to delete a target sub-device is received, the network configuration public key of the target sub-device is updated to obtain an updated public key; the updated public key is sent to the host device, so that the host device uses the updated public key to encrypt the target data packet in the preset linkage scenario to obtain an encrypted data packet, and then the encrypted data packet is sent to the target sub-device, wherein the target data packet corresponds to the target sub-device, and the target sub-device can only decrypt the data packet encrypted using the network configuration public key. By updating the network configuration public key and using the updated public key to encrypt the instruction data packet, the system achieves effective isolation of the deleted device, enhances security, ensures the accurate execution of instructions, and at the same time optimizes resource management and improves user experience.

[0075] To illustrate the embodiment of the present application, for example, in a smart home system, there is a host device and multiple sub-devices, such as smart bulbs, smart sockets, etc. These devices communicate with the host device through Wi-Fi and BLE (Bluetooth Low Energy), and the host device is connected to the cloud server to achieve remote control and scene linkage. A "away mode" scene is set in the home, which automatically turns off all lights and non-essential appliances when the user leaves home, and turns on the security camera at the same time. Smart bulb A and smart socket B are part of the scene. They have been networked through the host device and registered in the cloud database. Assume that the user decides to replace smart socket B, so an instruction is sent through the application of the user terminal (such as a smart phone) to request the cloud to delete the information of smart socket B. After receiving the deletion request, the cloud performs the following steps: the network public key of smart socket B is updated to generate an updated public key. The updated public key may be a randomly generated invalid key to ensure that smart socket B cannot correctly decrypt subsequent control instructions; the cloud sends the updated public key to the host device. After receiving the updated public key, the host device will associate the public key with the device ID of smart socket B for subsequent encryption operations.

[0076] The user triggers the "Away Mode" scene through the user terminal, and the cloud sends a scene execution instruction to the host device, which includes the control instructions of each sub-device. After receiving the instruction, the host device processes the target data packet in the preset linkage scene: the host device checks each sub-device in the "Away Mode" scene, and for smart socket B, uses the updated public key (invalid public key) to encrypt the control instructions (target data packet) of smart socket B to generate an encrypted data packet.

[0077] The host device broadcasts the encrypted scene execution instructions to all sub-devices in the home through the BLE protocol. After receiving the encrypted data packet, smart socket B attempts to decrypt it using its own private key, but the decryption fails because an invalid public key is used for encryption, thus avoiding miscontrol of the deleted smart socket B.

[0078] For devices that have not been deleted, such as smart bulb A, the host device will use its network configuration public key for encryption, and the generated encrypted data packet smart bulb A can correctly decrypt and perform corresponding actions (such as turning off the light).

[0079] By updating the public key of the target sub-device and using the updated public key to encrypt the control instructions in the preset scene, it can be ensured that the deleted sub-device in the home cannot decrypt and execute subsequent control instructions, thereby avoiding miscontrol during the scene execution process. This mechanism is particularly important when there are a large number of devices and a complex network environment. It enhances the security and accuracy of the smart home system and ensures the precise execution of user intentions.

[0080] In the above-mentioned embodiment, if the cloud receives an instruction to delete the target sub-device, the network configuration public key of the target sub-device is updated to obtain an updated public key, and the updated public key is sent to the host device. The host device receives the updated public key sent by the cloud, and uses the updated public key to encrypt the target data packet in the preset linkage scenario to obtain an encrypted data packet, and sends the encrypted data packet to the target sub-device, wherein the target data packet corresponds to the target sub-device, and the target sub-device can only decrypt the data packet encrypted using the network configuration public key, thereby solving the problem that the sub-device deleted in the cloud in the existing device linkage control scheme still executes the corresponding instruction, i.e., causes the sub-device to be miscontrolled.

[0081] Second aspect embodiment

[0082] In the embodiment of the present application, a first device linkage control device is provided. It should be noted that the device linkage control device of the embodiment of the present application can be used to execute the device linkage control method provided by the embodiment of the present application. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0083] The following introduces the first device linkage control device provided in the embodiment of the present application.

[0084] Figure 2 Schematic diagram of the first device linkage control device according to an embodiment of the present application. Figure 2 As shown, the device comprises:

[0085] The updating unit 21 is configured to update the network configuration public key of the target sub-device to obtain an updated public key upon receiving an instruction to delete the target sub-device.

[0086] Specifically, when the cloud receives an instruction to delete the target sub-device, it is necessary to execute the step of updating the network configuration public key of the target sub-device to ensure that the target sub-device will have difficulty responding to control instructions even if it receives subsequent control instructions. The cloud generates an updated public key, which is different from the original network configuration public key of the target sub-device and is usually designed to be invalid or mismatched with the original public key. Through this step, even if the network connection of the target sub-device is poor, it can be ensured that the device will no longer participate in scene linkage after being deleted, thereby avoiding miscontrol.

[0087] The sending unit 22 is used to send the above-mentioned updated public key to the host device, so that the above-mentioned host device uses the above-mentioned updated public key to encrypt the target data packet in the preset linkage scenario to obtain an encrypted data packet, and then sends the above-mentioned encrypted data packet to the above-mentioned target sub-device, wherein the above-mentioned target data packet corresponds to the above-mentioned target sub-device, and the above-mentioned target sub-device can only decrypt the data packet encrypted using the above-mentioned distribution network public key.

[0088] Specifically, for example, in a smart home system, when the cloud receives a user's instruction to delete a sub-device (such as a smart light), the system needs to ensure that the device will not mistakenly perform any actions in the linkage scene in the future. If necessary, the system also removes the device's information from the database.

[0089] The above-mentioned updating unit includes: an updating module, which is used to update the network configuration public key of the above-mentioned target sub-device by adopting kernel programming technology to obtain the above-mentioned updated public key if the above-mentioned instruction to delete the target sub-device is received.

[0090] The above-mentioned updating module includes: a response submodule, which is used to respond to the above-mentioned instruction to delete the target sub-device, and run a custom program in the system kernel to update the network configuration public key of the above-mentioned target sub-device to obtain the above-mentioned updated public key.

[0091] Specifically, in order to respond to the deletion instruction, and considering security and efficiency, the system needs to execute a custom program at the kernel level. The kernel is the core of the operating system, directly controlling computer hardware resources and providing underlying services, so operating at this level can more directly access and modify key data such as device keys. Custom programs can run in the kernel using eBPF (Extended Berkeley Packet Filter) or other similar technologies. The core function of the custom program is to update the network configuration public key of the target sub-device to a new, invalid update public key, which is different from the original public key of the device, meaning that any data packet encrypted with this public key will not be correctly decrypted by the device. This process ensures that no new control instructions will be executed even if the device is in a poor or disconnected network.

[0092] By executing a custom program at the kernel level to update the sub-device's network configuration public key, this mechanism can effectively prevent the deleted device from mistakenly executing actions in future scene linkages, protecting the user's security and privacy, and avoiding the waste of system resources. This method is particularly suitable for smart home network environments with a large number of devices and frequent scene linkages.

[0093] The first type of device linkage control apparatus further includes: a deleting unit, configured to delete relevant information of the target sub-device stored in the cloud database.

[0094] Specifically, for example, in a smart home system, when a user decides not to use a sub-device (such as a smart light, smart socket, etc.) and initiates a command to delete the device through an application, in addition to updating the network configuration public key of the device on the host device to prevent the device from receiving the command by mistake, the relevant information of the device stored in the cloud database needs to be deleted. The cloud database stores the status information of all registered devices, user settings, scene linkage rules, and network configuration information between devices. The system first locates the information related to the sub-device in the cloud database, which may include device ID, network configuration public key, private key, status information, user settings, etc. After determining the target device, the system performs a deletion operation to remove all information related to the device. This includes not only the basic information of the device, but also all scene linkage settings, historical records, etc. related to it. The deletion operation ensures the consistency of the system state and prevents future scene linkage attempts to communicate with the deleted device. By deleting the relevant information of the target sub-device stored in the cloud database, the system can not only technically achieve the complete removal of the device, but also maintain user privacy and data security.

[0095] The first type of device linkage control device includes a processor and a memory, and the updating unit, the sending unit, etc. are stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions. The modules are all located in the same processor; or, the modules are located in different processors in any combination.

[0096] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0097] Third aspect embodiment

[0098] In an embodiment of the present application, a device linkage control method running on a host device is provided, and the host device communicates with the cloud. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0099] Figure 3 is a flow chart of a second device linkage control method according to an embodiment of the present application. Figure 3 As shown, the method comprises the following steps:

[0100] In step S301, the host device receives an updated public key sent by the cloud, wherein the updated public key is obtained by the cloud updating the network configuration public key of the target sub-device in response to an instruction to delete the target sub-device.

[0101] Specifically, the host device receives an update public key from the cloud, which is generated after the cloud receives an instruction to delete the target sub-device. After deleting the target sub-device, the cloud generates a new network configuration public key as the update public key, and then sends this update public key to the host device. After receiving the update public key, the host device can use this new network configuration public key to re-pair and connect with the target sub-device to ensure communication security and effectiveness.

[0102] Step S302, use the above-mentioned updated public key to encrypt the target data packet in the preset linkage scenario to obtain an encrypted data packet, and send the above-mentioned encrypted data packet to the above-mentioned target sub-device, wherein the above-mentioned target data packet corresponds to the above-mentioned target sub-device, and the above-mentioned target sub-device can only decrypt the data packet encrypted using the above-mentioned distribution network public key.

[0103] Specifically, after the host device receives the updated public key sent from the cloud, it will use this updated public key to encrypt all data packets associated with the target sub-device in the preset linkage scene. These data packets contain control instructions to trigger or adjust the device actions in the scene. After the encryption is completed, the host device sends these encrypted data packets to the target sub-device through the wireless communication protocol. Even if the device is still online in the network environment, it will not be able to decrypt these data packets because the updated public key and the device's private key no longer match. The target sub-device has its own private key, which is synchronized with the cloud server and the home host when the device is networked. Under normal circumstances, the sub-device can use this private key to decrypt the data packet encrypted with the network configuration public key (i.e., the original public key of the device) and execute the instruction. However, when the network configuration public key is updated, the target sub-device can only decrypt the data packet encrypted with the original network configuration public key, but cannot decrypt the data packet encrypted with the updated public key. By encrypting the data packet with the updated public key, even if a device is still connected to the system at the technical level, it cannot decrypt and execute the actions in the linkage scene, effectively avoiding the situation of miscontrol of the deleted device and protecting the accuracy and security of the scene linkage.

[0104] During the specific implementation process, the host device and multiple sub-devices form a BLE network, the target sub-device is one of the multiple sub-devices, and the encrypted data packet is sent to the target sub-device, including: broadcasting the encrypted data packet in a BLE broadcasting manner to send the encrypted data packet to the target sub-device.

[0105] Specifically, in a smart home environment, the host device, as the central node of the network, establishes a wireless communication network with multiple sub-devices (such as smart lights, smart sockets, etc.) through the BLE protocol. The low power consumption characteristics of the BLE network make communication between devices both efficient and energy-saving, which is suitable for the wide deployment and continuous operation of devices in smart homes. The target sub-device is one of the multiple sub-devices in the BLE network and has been deleted by the user. In order to ensure that the device no longer responds to the control instructions of the system, a specific strategy is required to send encrypted data packets. The host device sends encrypted data packets through the broadcast feature of BLE. The broadcast function of BLE allows devices to send data packets without establishing a connection, which is very useful when information needs to be sent to all devices or specific devices in the network. The host device uses the updated public key to encrypt the control instructions related to the target sub-device and generate an encrypted data packet. This encryption process ensures that only the target sub-device holding the correct private key can decrypt and understand the content of the instruction. By sending encrypted data packets through BLE broadcast, the host device can send information to all sub-devices (or specific device groups) in the network at one time without establishing a connection with each device separately. This not only improves communication efficiency and reduces network latency, but also ensures the security of instructions through encryption mechanisms. Even if the data packet is received by other devices, it cannot be decrypted and executed.

[0106] Specifically, BLE, the full name of Bluetooth Low Energy, is a Bluetooth technology standard that aims to address the power consumption and distance limitations of traditional Bluetooth. It is particularly suitable for small devices that need to run for a long time and rely on battery power. The main features of BLE include:

[0107] Low power consumption: BLE is designed to significantly reduce power consumption, allowing devices to run for years on a single coin cell battery. This is achieved by reducing the radio's active time and optimizing the data transmission protocol.

[0108] Fast connection: Compared to traditional Bluetooth, BLE provides faster connection establishment time, generally within 3 milliseconds, which greatly reduces the time required for device search and pairing.

[0109] Broadcast mode: BLE supports broadcast mode, which allows devices to send data without establishing a formal connection. This means that a device can continuously broadcast its status information, and other devices (such as smartphones or home hosts) can receive this information without establishing a full Bluetooth connection with it.

[0110] Data packet size limit: In order to improve efficiency and reduce power consumption, the data packet size of BLE is limited, and each data packet can contain up to 20 bytes of variable data. Although this limits the amount of data transmitted in a single time, it improves the efficiency and speed of data transmission.

[0111] Scalability: BLE can support star networks between multiple devices, and a central device can communicate with multiple peripheral devices. At the same time, BLE also supports one-to-one and many-to-many network topologies, which can flexibly adapt to different application scenarios.

[0112] Compatibility: BLE is compatible with traditional Bluetooth devices at the physical layer, but the application layer and data transmission protocols are different. BLE devices can be paired with devices that support traditional Bluetooth, but a dual-mode Bluetooth device that can support both standards is required as a bridge.

[0113] Security: BLE provides multiple security mechanisms, including AES-based encryption and device authentication, to protect data transmission and prevent unauthorized devices from accessing the network.

[0114] In the specific implementation process, the host device and multiple sub-devices form a wifi network, and the method further includes: the host device obtains a heartbeat packet of any of the sub-devices through the wifi network; and determines whether the corresponding sub-device is online based on the heartbeat packet.

[0115] Specifically, the host device is connected to multiple sub-devices through a Wi-Fi network. The Wi-Fi network provides a high-speed, long-distance wireless communication method, which is suitable for application scenarios with large amounts of data and requiring real-time transmission, such as video streaming transmission, large amounts of data upload, etc. In order to continuously monitor the online status of the sub-device, the host device periodically sends a heartbeat request to the sub-device. After receiving the heartbeat request, the sub-device will return a heartbeat packet accordingly. The heartbeat packet is a lightweight, periodically sent communication signal, which is mainly used to verify whether the device is operating normally and online, and generally contains basic status information of the device. The host device receives these heartbeat packets through the Wi-Fi network instead of the BLE network. The Wi-Fi network has a wider coverage range and a higher data transmission rate, and is more suitable for transmitting information such as heartbeat packets that require frequent and real-time communication. The host device determines whether the sub-device is online based on the received heartbeat packet. If the heartbeat response of a specific sub-device is not received within a certain period of time, the host device will believe that the sub-device may have been disconnected or failed, and thus mark it as offline. This information is very important for the system because it affects whether the host device can send control instructions to the sub-device and the execution of certain linkage scenes. The determination of online status is the basis of linkage control. When the host device knows that a sub-device is online, it can send control instructions to the device through the Wi-Fi or BLE network to execute the preset linkage scene. On the contrary, if the device is marked as offline, the host device will not try to send instructions to it, avoiding invalid communication and waste of resources. The use of heartbeat packets helps to enhance the security of the system because it can help the host device to detect abnormal conditions in the network in a timely manner, such as illegal disconnection of the device or network attacks. By continuously monitoring the status of sub-devices, the stable operation of the smart home system and the protection of user privacy can be further guaranteed. By obtaining and analyzing heartbeat packets through the Wi-Fi network, the host device can effectively manage the sub-devices under its network, ensuring that only online devices can participate in scene linkage, improving the overall efficiency, security and user experience of the smart home system.

[0116] In a specific implementation process, the host device receives the updated public key sent by the cloud, including: the host device receives the updated public key sent by the cloud via a mobile data network.

[0117] Specifically, a mobile data network generally refers to a network that transmits data through a cellular network or mobile Internet, such as a 3G, 4G LTE, or 5G network. In a smart home system, the host device usually has dual connection capabilities for Wi-Fi and mobile data networks, so that it can maintain communication with the cloud when the Wi-Fi network at home is unavailable or unstable. By receiving updated public keys through the mobile data network and applying them instantly, the host device can ensure that the system can execute user instructions securely and accurately under various network conditions, especially when the user deletes a sub-device, it can respond quickly to avoid security risks. At the same time, when the Wi-Fi network is unavailable, it can also maintain normal communication with the cloud to ensure the stable operation of the smart home system. This mechanism is an important part of the network architecture and device management of the smart home system, and plays a key role in maintaining the overall security of the system and user experience.

[0118] Fourth aspect embodiment

[0119] A second device linkage control device is provided in the embodiment of the present application. It should be noted that the device linkage control device of the embodiment of the present application can be used to execute the device linkage control method provided in the embodiment of the present application. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0120] The following introduces the second device linkage control device provided in the embodiment of the present application.

[0121] Figure 4 is a schematic diagram of a second device linkage control device according to an embodiment of the present application. Figure 4 As shown, the device comprises:

[0122] The receiving unit 41 is used for the host device to receive the updated public key sent by the cloud, wherein the updated public key is obtained by the cloud updating the network configuration public key of the target sub-device in response to the instruction to delete the target sub-device.

[0123] Specifically, the host device receives an update public key from the cloud, which is generated after the cloud receives an instruction to delete the target sub-device. After deleting the target sub-device, the cloud generates a new network configuration public key as the update public key, and then sends this update public key to the host device. After receiving the update public key, the host device can use this new network configuration public key to re-pair and connect with the target sub-device to ensure communication security and effectiveness.

[0124] The encryption unit 42 is used to use the above-mentioned updated public key to encrypt the target data packet in the preset linkage scenario to obtain an encrypted data packet, and send the above-mentioned encrypted data packet to the above-mentioned target sub-device, wherein the above-mentioned target data packet corresponds to the above-mentioned target sub-device, and the above-mentioned target sub-device can only decrypt the data packet encrypted using the above-mentioned distribution network public key.

[0125] Specifically, after the host device receives the updated public key sent from the cloud, it will use this updated public key to encrypt all data packets associated with the target sub-device in the preset linkage scene. These data packets contain control instructions to trigger or adjust the device actions in the scene. After the encryption is completed, the host device sends these encrypted data packets to the target sub-device through the wireless communication protocol. Even if the device is still online in the network environment, it will not be able to decrypt these data packets because the updated public key and the device's private key no longer match. The target sub-device has its own private key, which is synchronized with the cloud server and the home host when the device is networked. Under normal circumstances, the sub-device can use this private key to decrypt the data packet encrypted with the network configuration public key (i.e., the original public key of the device) and execute the instruction. However, when the network configuration public key is updated, the target sub-device can only decrypt the data packet encrypted with the original network configuration public key, but cannot decrypt the data packet encrypted with the updated public key. By encrypting the data packet with the updated public key, even if a device is still connected to the system at the technical level, it cannot decrypt and execute the actions in the linkage scene, effectively avoiding the situation of miscontrol of the deleted device and protecting the accuracy and security of the scene linkage.

[0126] The host device and multiple sub-devices form a BLE network, the target sub-device is one of the multiple sub-devices, and the encrypted data packet is sent to the target sub-device, including: broadcasting the encrypted data packet in a BLE broadcasting manner to send the encrypted data packet to the target sub-device.

[0127] Specifically, in a smart home environment, the host device, as the central node of the network, establishes a wireless communication network with multiple sub-devices (such as smart lights, smart sockets, etc.) through the BLE protocol. The low power consumption characteristics of the BLE network make communication between devices both efficient and energy-saving, which is suitable for the wide deployment and continuous operation of devices in smart homes. The target sub-device is one of the multiple sub-devices in the BLE network and has been deleted by the user. In order to ensure that the device no longer responds to the control instructions of the system, a specific strategy is required to send encrypted data packets. The host device sends encrypted data packets through the broadcast feature of BLE. The broadcast function of BLE allows devices to send data packets without establishing a connection, which is very useful when information needs to be sent to all devices or specific devices in the network. The host device uses the updated public key to encrypt the control instructions related to the target sub-device and generate an encrypted data packet. This encryption process ensures that only the target sub-device holding the correct private key can decrypt and understand the content of the instruction. By sending encrypted data packets through BLE broadcast, the host device can send information to all sub-devices (or specific device groups) in the network at one time without establishing a connection with each device separately. This not only improves communication efficiency and reduces network latency, but also ensures the security of instructions through encryption mechanisms. Even if the data packet is received by other devices, it cannot be decrypted and executed.

[0128] The host device and multiple sub-devices form a wifi network, and the second device linkage control device further includes:

[0129] An acquisition unit, used for the host device to acquire a heartbeat packet of any of the sub-devices through the WiFi network;

[0130] The determination unit is used to determine whether the corresponding sub-device is online according to the heartbeat packet.

[0131] Specifically, the host device is connected to multiple sub-devices through a Wi-Fi network. The Wi-Fi network provides a high-speed, long-distance wireless communication method, which is suitable for application scenarios with large amounts of data and requiring real-time transmission, such as video streaming transmission, large amounts of data upload, etc. In order to continuously monitor the online status of the sub-device, the host device periodically sends a heartbeat request to the sub-device. After receiving the heartbeat request, the sub-device will return a heartbeat packet accordingly. The heartbeat packet is a lightweight, periodically sent communication signal, which is mainly used to verify whether the device is operating normally and online, and generally contains basic status information of the device. The host device receives these heartbeat packets through the Wi-Fi network instead of the BLE network. The Wi-Fi network has a wider coverage range and a higher data transmission rate, and is more suitable for transmitting information such as heartbeat packets that require frequent and real-time communication. The host device determines whether the sub-device is online based on the received heartbeat packet. If the heartbeat response of a specific sub-device is not received within a certain period of time, the host device will believe that the sub-device may have been disconnected or failed, and thus mark it as offline. This information is very important for the system because it affects whether the host device can send control instructions to the sub-device and the execution of certain linkage scenes. The determination of online status is the basis of linkage control. When the host device knows that a sub-device is online, it can send control instructions to the device through the Wi-Fi or BLE network to execute the preset linkage scene. On the contrary, if the device is marked as offline, the host device will not try to send instructions to it, avoiding invalid communication and waste of resources. The use of heartbeat packets helps to enhance the security of the system because it can help the host device to detect abnormal conditions in the network in a timely manner, such as illegal disconnection of the device or network attacks. By continuously monitoring the status of sub-devices, the stable operation of the smart home system and the protection of user privacy can be further guaranteed. By obtaining and analyzing heartbeat packets through the Wi-Fi network, the host device can effectively manage the sub-devices under its network, ensuring that only online devices can participate in scene linkage, improving the overall efficiency, security and user experience of the smart home system.

[0132] The host device receives the updated public key sent by the cloud, including: the host device receives the updated public key sent by the cloud through a mobile data network.

[0133] Specifically, a mobile data network generally refers to a network that transmits data through a cellular network or mobile Internet, such as a 3G, 4G LTE, or 5G network. In a smart home system, the host device usually has dual connection capabilities for Wi-Fi and mobile data networks, so that it can maintain communication with the cloud when the Wi-Fi network at home is unavailable or unstable. By receiving updated public keys through the mobile data network and applying them instantly, the host device can ensure that the system can execute user instructions securely and accurately under various network conditions, especially when the user deletes a sub-device, it can respond quickly to avoid security risks. At the same time, when the Wi-Fi network is unavailable, it can also maintain normal communication with the cloud to ensure the stable operation of the smart home system. This mechanism is an important part of the network architecture and device management of the smart home system, and plays a key role in maintaining the overall security of the system and user experience.

[0134] The second type of device linkage control device includes a processor and a memory. The receiving unit, encryption unit, etc. are stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions. The modules are all located in the same processor; or, the modules are located in different processors in any combination.

[0135] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0136] Fifth aspect embodiment

[0137] In an embodiment of the present application, a device linkage control method is provided, which specifically includes:

[0138] Step S1: If the cloud receives an instruction from the terminal device to delete the target sub-device, the network configuration public key of the target sub-device is updated to obtain an updated public key.

[0139] Step S2: The cloud sends the updated public key to the host device.

[0140] Step S3: the host device receives the updated public key sent by the cloud, wherein the updated public key is obtained by the cloud updating the network configuration public key of the target sub-device in response to the instruction to delete the target sub-device.

[0141] Step S4: The host device uses the updated public key to encrypt the target data packet in the preset linkage scenario to obtain an encrypted data packet, and sends the encrypted data packet to the target sub-device, wherein the target data packet corresponds to the target sub-device, and the target sub-device can only decrypt the data packet encrypted using the configuration network public key.

[0142] To illustrate this embodiment, for example, a smart security system includes a smart door lock, a smart camera, and a home alarm system, which are also connected to the cloud through a host device. The user plans to renovate his home and needs to temporarily allow the renovation workers to enter the home, but only during a specific time period, such as from 9 am to 5 pm. The user sets a temporary linkage rule through the application of his smart terminal (such as a smart phone), allowing the smart camera to automatically start recording when the smart door lock is unlocked within the specified time, and the home alarm system remains silent to avoid false alarms.

[0143] The cloud receives the deletion command. After the decoration is completed, the user no longer needs this temporary linkage rule, so the user terminal sends a command to the cloud to request the deletion of the temporary smart door lock access rights related to the decoration workers.

[0144] The cloud will update the network public key of the smart door lock and generate an updated public key. This updated public key is created for temporary access rights for renovation workers and should now be marked as invalid to ensure that the smart door lock cannot decrypt subsequent control instructions for renovation workers.

[0145] The updated public key is sent to the host device via the Internet. After receiving the updated public key, the host device associates it with the device ID of the smart door lock and stores it for subsequent encryption operations.

[0146] The user triggers the regular "Away Mode" scenario of the home security system through the user terminal, which activates all security measures when the user is away from home, including 24 / 7 recording of smart cameras and activation of the home alarm system. The cloud sends instructions to the host device to execute the "Away Mode" scenario, which includes control instructions for all security devices. When the host device processes these instructions, it encrypts the control instructions of the smart door lock with the updated public key (invalid public key) to generate an encrypted data packet. When the smart door lock receives the encrypted data packet, it will try to decrypt it using its own private key, but because the invalid public key was used for encryption, the decryption will fail, which means that the smart door lock will not perform any actions related to the deleted temporary permissions. For smart cameras and home alarm systems, the home host uses their correct network configuration public keys for encryption, and the generated encrypted data packets can be correctly decrypted by these devices and perform the corresponding security startup operations to ensure the normal operation of home security measures.

[0147] The above linkage control method can ensure the security and accuracy of the home automation system even in the case of frequent device updates or temporary access rights management. When the cloud receives an instruction to delete a specific permission (such as temporary smart door lock access rights), by updating the public key and synchronizing it to the home host, it can prevent the device with deleted permissions from decrypting and executing subsequent control instructions, while ensuring that all other authorized devices can still respond and execute commands in the linkage scenario normally.

[0148] Sixth aspect embodiment

[0149] The embodiment of the present application also provides a device linkage control system. It should be noted that the device linkage control system of the embodiment of the present application can be used to execute the device linkage control method provided by the embodiment of the present application. The system is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0150] The following is an introduction to the device linkage control system provided in the embodiments of the present application.

[0151] Figure 5 Schematic diagram of a device linkage control system according to an embodiment of the present application. Figure 5 As shown, the system includes:

[0152] A cloud, used to execute any one of the first device linkage control methods mentioned above;

[0153] A host device, used for communicating with the cloud, and for executing any one of the second device linkage control methods;

[0154] Multiple sub-devices are used to form a device network with the above host device.

[0155] Specifically, the cloud is the command processing and distribution center. The cloud is the receiving point for users to send device control commands through channels such as mobile applications, web interfaces or voice assistants. Whether creating a new linkage scene, modifying an existing scene, or directly controlling a single device, all user commands will first be received by the cloud; the cloud maintains the latest status information and device public keys of all networked devices. When the device status changes (such as online status, device information update, etc.), the host device will synchronize this information to the cloud, keep the cloud database updated, and ensure that the cloud can make decisions based on the latest device status; the cloud is responsible for processing the linkage logic between devices, including the creation, execution and maintenance of scenes. For example, the user may preset an "away mode". In this mode, when the user leaves home and locks the door, the cloud will automatically send commands to the host device. , allowing the host device to control all connected devices to reduce energy consumption, such as turning off lights, adjusting thermostats, etc.; when the cloud receives an instruction from the user terminal to delete the target sub-device, the cloud is responsible for updating the public key of the device to make it invalid, thereby isolating the device on a technical level. The cloud sends the updated public key to the host device to ensure that the host device does not send instructions to the deleted device in subsequent scene executions; the cloud is also responsible for collecting and analyzing device usage data, and through machine learning and artificial intelligence technology, continuously optimizing device linkage strategies to make smart home systems more intelligent, able to learn user living habits and preferences, and automatically adjust scene settings; the cloud stores key data such as device network configuration information and scene settings. Even if the host device or user device fails, data can be restored from the cloud to quickly rebuild the smart home environment.

[0156] In this embodiment, the cloud receives an instruction to delete the target sub-device sent by the user terminal, updates the network configuration public key of the target sub-device to obtain an updated public key, and then sends the updated public key to the host device. The host device receives the updated public key sent by the cloud, uses the updated public key to encrypt the target data packet in the preset linkage scene to obtain an encrypted data packet, and sends the encrypted data packet to the above-mentioned target sub-device. The target sub-device can only decrypt the data packet encrypted using the above-mentioned network configuration public key. The cloud will generate response data, which may include device status updates, scene execution results, system feedback, etc. These response data will be encrypted (to protect data security) and returned to the user terminal via the Internet. The user terminal receives the response data packet from the cloud, and the application on the user terminal will decrypt these data and display them to the user, such as displaying the current status of the home device, confirming the scene execution results, displaying system feedback information, etc.

[0157] The cloud not only provides powerful computing and storage resources, but also makes device linkage control more flexible and efficient through its high accessibility and scalability. Users can access the cloud through mobile Internet anytime and anywhere to create or adjust linkage scenes without directly interacting with the host device. The cloud's real-time status monitoring and command processing capabilities ensure that even when the network is unstable or the host device is offline, the linkage between devices can be dynamically adjusted through the cloud's decision logic, improving the stability and security of the entire smart home system.

[0158] Specifically, in the device linkage control system of smart home, the host device (which can be a smart air conditioner, smart screen, etc.) plays the role of a link between the cloud and multiple sub-devices in the home (such as smart bulbs, smart sockets, security cameras, etc.), and is the core entity for executing the second device linkage control method. The host device maintains continuous communication with the cloud server through the Internet. This communication can be bidirectional, receiving instructions and information from the cloud and sending device status and data to the cloud. The communication protocol may include Wi-Fi, mobile data network (such as 4G, 5G) or other Internet protocols. The host device is responsible for executing the device linkage control method assigned by the cloud. The linkage control method may include but is not limited to automatic control of the device, execution of the scene, monitoring of the device status, and coordination between devices. For example, if the user sets a "home mode" in the cloud through a mobile application, the mode may involve turning on specific lights, adjusting the temperature, starting the TV, etc. After the host device receives the "home mode" instruction from the cloud, it will send control commands to the corresponding sub-device according to the preset rules and device status. After receiving the scene execution instructions from the cloud, the host device is responsible for converting these instructions into control signals suitable for the sub-devices, and sending the instructions directly to the sub-devices through Wi-Fi, BLE (Bluetooth Low Energy) or other wireless communication protocols. This instruction forwarding mechanism ensures that even if the sub-device cannot communicate directly with the cloud, it can still be effectively controlled by the host device. The host device will also monitor the status of all sub-devices in the home regularly or on demand, such as online status, power, working mode, etc. This information will be periodically sent back to the cloud through heartbeat packets, etc., so that the cloud can understand the health of the home network and the availability of devices in real time, so as to make more accurate decisions. The host device uses public key encryption technology to encrypt the instructions sent to the sub-device to ensure the security of the communication process. When the cloud requires the public key of a sub-device to be updated, the host device will receive and apply the update to avoid miscontrol of the deleted device and enhance the security of the system. The host device manages the home network and optimizes communication between devices to ensure efficient device control and data transmission even when the network environment changes or the number of devices is large. The host device also has user interaction functions, such as receiving user input through the local user interface or voice commands, processing and sending to the cloud or directly controlling the device. At the same time, it is also responsible for processing the data uploaded by the sub-devices, performing preliminary analysis and filtering, and then sending the processed data to the cloud for further analysis or storage. The host device is a key control point in the smart home system, ensuring the accurate, safe and efficient execution of user commands from the cloud to each sub-device in the home network.

[0159] Specifically, sub-devices refer to various smart devices in the smart home system that directly participate in the home automation process, including but not limited to smart bulbs, smart sockets, smoke alarms, security cameras, thermostats, smart locks, curtain controllers, etc. These devices usually have the ability to connect to wireless networks (such as Wi-Fi, Zigbee, Z-Wave, BLE, etc.) and can receive and execute control instructions from the host device or the cloud. Multiple sub-devices form a network connection with the host device through wireless communication technology.

[0160] The construction of the device network allows efficient communication between sub-devices and between sub-devices and host devices, making it possible to execute home automation scenarios. The device network enables sub-devices to work together to execute preset smart scenarios. For example, "away mode" may include turning off all lights, disconnecting the power of non-essential appliances, and starting the security monitoring system. After receiving user instructions or detecting specific trigger conditions (such as time, sensor status, external events), the host device will send control instructions to the relevant sub-devices through the device network to execute these scenarios. The device network is not static and can be dynamically adjusted as new devices are added or old devices are removed. The construction and management of the device network also includes security mechanisms, such as using encrypted communication protocols to protect data transmission between devices and ensure that user instructions and device status information are not accessed by unauthorized persons. The host device is usually equipped with a variety of wireless communication technologies to ensure wide coverage of the device network and good compatibility between devices. For example, Wi-Fi is used for high-speed data transmission and remote control, BLE is used for communication of low-power devices, and Zigbee or Z-Wave is used to build a long-distance, low-power IoT device network. Through a device network consisting of a host device and multiple sub-devices, the smart home system realizes intelligent management of the home environment.

[0161] During the specific implementation process, the above system also includes a user terminal for communicating with the above cloud.

[0162] Specifically, in the device linkage control system, the user terminal serves as the interface for the user to interact with the smart home system, allowing the user to manage various smart devices in the home through intuitive operations. The user terminal usually refers to a smart phone, tablet computer, personal computer or a dedicated control panel, which provides users with a graphical user interface (GUI) or a voice user interface (VUI). Through these interfaces, users can easily create, edit or delete device linkage scenes, view device status, and directly control individual devices. The user terminal communicates with the cloud server through the Internet. Any operation performed by the user on the terminal, such as device configuration, scene setting or status query, will be converted into a data packet and sent to the cloud. Similarly, the cloud will also send the processed response (such as scene execution results, real-time device status, etc.) back to the user terminal via the Internet. When the user terminal communicates with the cloud, user authentication will be performed to ensure that only authorized users can control the smart home system. The cloud server is responsible for verifying the user's identity, and the user terminal provides the user with corresponding control permissions, such as device management, scene editing, etc. When a user creates or edits a scene through a user terminal, the terminal generates corresponding control instructions based on the user input, encrypts these instructions and sends them to the cloud. After the cloud decrypts the instructions, it processes and forwards them to the host device, which then performs specific device control. The user terminal is not only used to send instructions, but also to receive and display device status feedback. When the device performs an action, its status will be transmitted to the cloud through the host device, and then sent to the user terminal through the Internet. The user can check in real time whether the device has been operated as expected. In addition, the user terminal can also receive real-time notifications from the cloud, such as device failures and security alarms. The communication between the user terminal and the cloud also includes the synchronization of device and scene information. The settings on the user terminal will be uploaded to the cloud database for backup. Even if the user terminal is lost or replaced, the data can be restored from the cloud through the new terminal and the smart home system can continue to be used. The existence of the user terminal makes remote control possible. No matter where the user is, as long as he can access the Internet, he can connect to the cloud through the user terminal to control and manage the smart devices in the home, realizing a true "remote smart home".

[0163] As a bridge between the smart home system and the user, the user terminal greatly facilitates the user's management and control of home intelligent devices and provides a safe and convenient interactive platform. Through close communication with the cloud, the user terminal can not only monitor the home status in real time, but also respond to user needs immediately, and realize remote triggering and adjustment of home automation scenes.

[0164] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the device linkage control method.

[0165] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0166] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0167] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0168] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0169] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0170] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0171] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0172] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0173] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0174] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A device linkage control method, characterized in that: include: If an instruction to delete a target sub-device is received, the network configuration public key of the target sub-device is updated to obtain an updated public key; The updated public key is sent to the host device, so that the host device uses the updated public key to encrypt the target data packet in the preset linkage scenario to obtain an encrypted data packet, and then sends the encrypted data packet to the target sub-device, wherein the target data packet corresponds to the target sub-device, and the target sub-device can only decrypt the data packet encrypted using the distribution network public key.

2. The method according to claim 1, characterized in that If an instruction to delete a target sub-device is received, updating the network configuration public key of the target sub-device to obtain an updated public key includes: If the instruction to delete the target sub-device is received, the network configuration public key of the target sub-device is updated by using kernel programming technology to obtain the updated public key.

3. The method according to claim 2, characterized in that If the instruction to delete the target sub-device is received, the network configuration public key of the target sub-device is updated by using kernel programming technology to obtain the updated public key, including: In response to the instruction to delete the target sub-device, a custom program is run in the system kernel to update the network configuration public key of the target sub-device to obtain the updated public key.

4. The method according to any one of claims 1 to 3, characterized in that The method further includes: deleting relevant information of the target sub-device stored in the cloud database.

5. A device linkage control method, characterized in that: include: The host device receives an updated public key sent by the cloud, wherein the updated public key is obtained by the cloud updating the network configuration public key of the target sub-device in response to an instruction to delete the target sub-device; The updated public key is used to encrypt the target data packet in the preset linkage scenario to obtain an encrypted data packet, and the encrypted data packet is sent to the target sub-device, wherein the target data packet corresponds to the target sub-device, and the target sub-device can only decrypt the data packet encrypted using the distribution network public key.

6. The method according to claim 5, characterized in that The host device and a plurality of sub-devices form a BLE network, the target sub-device is one of the plurality of sub-devices, and the encrypted data packet is sent to the target sub-device, comprising: The encrypted data packet is broadcasted by BLE broadcasting to send the encrypted data packet to the target sub-device.

7. The method according to claim 5, characterized in that The host device and a plurality of sub-devices form a wifi network, and the method further comprises: The host device obtains a heartbeat packet of any of the sub-devices through the WiFi network; Determine whether the corresponding sub-device is online according to the heartbeat packet.

8. The method according to claim 5, characterized in that The host device receives the updated public key sent by the cloud, including: The host device receives the updated public key sent by the cloud via a mobile data network.

9. A device linkage control system, characterized in that: include: A cloud, used to execute the device linkage control method according to any one of claims 1 to 4; A host device, communicating with the cloud, and configured to execute the device linkage control method according to any one of claims 5 to 8; A plurality of sub-devices and the host device form a device network.

10. The equipment linkage control system according to claim 9, characterized in that: The system further comprises: A user terminal communicates with the cloud.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the device linkage control method described in any one of claims 1 to 4 or any one of claims 5 to 8.

Images