A smart home linkage control method and device, and a storage medium

Abstract

The application belongs to the field of smart home control, and discloses a smart home linkage control method, equipment and storage medium, which comprises the following steps: abstracting controlled devices, device states and home scenes in a home environment into device nodes, state nodes and scene nodes respectively, establishing a directed association edge among the three types of nodes, recording the real-time state of each device node, and outputting a corresponding scene state atlas; identifying the front dependency relationship and mutual exclusion dependency relationship among the device nodes based on the scene state atlas, and constructing a linkage dependency link diagram; performing topological sorting according to the device node in-degree, and generating a linkage topological execution sequence; generating a control instruction and a scene dynamic weight of the corresponding device node according to the scene state atlas, performing consistency checking on the control instruction according to the linkage topological execution sequence, and outputting the control instruction that passes the consistency checking; and effectively improving the stability and execution reliability of linkage control under a complex home scene.

Description

Technical Field

[0001] The present invention relates to the field of smart home control, and more specifically, the present invention relates to a smart home linkage control method, apparatus and storage medium. Background

[0002] With the continuous increase in the types of smart home devices, linkage control between different devices has become an important way to improve the level of home automation. Existing smart home linkage control methods usually complete device control based on preset scenario scripts or fixed execution sequences, and lack unified description and dynamic parsing of the pre-dependency relationships between devices. When sequential execution constraints exist for multiple devices, subsequent devices are prone to execute in advance before the control of the pre-device is completed, resulting in linkage failure, inconsistent device states or abnormal scenario switching; at the same time, when the number of linked devices increases or the linkage relationship between devices changes, the fixed execution sequence is difficult to adapt to the new dependency relationship, which affects the flexibility and reliability of linkage control.

[0003] On the other hand, in the scenario where multiple users and multiple terminals control the same device at the same time, existing methods usually adopt methods such as fixed priority, latest control first or simple time sequence to handle control conflicts, and fail to conduct comprehensive arbitration in combination with the actual role of control instructions in the current home scenario. When multiple control instructions have different scenario requirements, the control instruction that better conforms to the current scenario is likely to be overwritten; when multiple control instructions have the same priority, there is a lack of a unified and deterministic secondary arbitration mechanism, which easily leads to unstable control results, and further affects the continuity and consistency of the entire linkage execution process.

[0004] In view of this, the present invention proposes a smart home linkage control method, apparatus and storage medium to solve the above problems. Contents of the Invention

[0005] In order to overcome the above-mentioned defects of the prior art, the present invention provides the following technical solutions to achieve the above objectives: A smart home linkage control method, comprising: S1. Abstracting the controlled devices, device states and home scenarios in the home environment into device nodes, state nodes and scenario nodes respectively, establishing directed association edges between the three types of nodes, recording the real-time state of each device node, and outputting a corresponding scenario state graph. S2. Identifying the pre-dependency relationships and mutual-exclusion dependency relationships between device nodes based on the scenario state graph, and constructing a linkage dependency link diagram; performing topological sorting according to the in-degree of the device nodes to generate a linkage topological execution sequence. S3. Generating scenario dynamic weights for the control instructions and corresponding device nodes according to the scenario state graph, performing consistency check on the control instructions according to the linkage topological execution sequence, and outputting the control instructions that pass the consistency check. S4. Establish an arbitration request group for control commands that have passed the consistency check, compare the scene dynamic weights of the device nodes, and determine the arbitration priority order; when the scene dynamic weights are the same, determine the arbitration priority order according to the arrival time of the control commands, and generate a linkage execution plan according to the arbitration priority order. S5. Monitor the linkage execution plan in real time, perform corresponding corrections based on the scope of impact of execution anomalies, and update the real-time status of each device node to the scene status map.

[0006] Preferably, the method for outputting the corresponding scene state map includes: Establish a corresponding device node for each controlled device in the home environment, establish a corresponding status node for the operating status of each controlled device, and establish a corresponding scene node for each home scene. Based on the triggering relationship between home scenes and controlled devices, scene association edges are established between scene nodes and device nodes. Based on the mapping relationship between controlled devices and operating states, state association edges are established between device nodes and state nodes. Based on the preset linkage relationship between devices, device association edges are established between device nodes. The device nodes, status nodes, scene nodes, and their corresponding directed edges are organized to form a scene state graph, and the current operating status of each controlled device is recorded in the scene state graph as the real-time status of the corresponding device node.

[0007] Preferably, the method for constructing the linkage dependency graph includes: Based on the activated scene nodes in the scene state graph, traverse the scene association edges corresponding to the scene nodes, obtain the device nodes associated with the scene nodes, and form a set of linked devices. Based on the preset linkage rules between devices, the relationships between device nodes in the linkage device set are resolved. When the control action corresponding to one device node requires another device node to complete the control before it can be executed, a prerequisite dependency relationship is established between the corresponding device nodes. When the control actions corresponding to two device nodes cannot be executed simultaneously or the corresponding operating states cannot be established simultaneously, a mutual exclusion dependency relationship is established between the corresponding device nodes; a linkage dependency link diagram is constructed based on the set of linked devices, the preceding dependencies, and the mutual exclusion dependencies.

[0008] Preferably, the method for generating the linked topology execution sequence includes: Based on the linkage dependency link graph, the in-degree of each device node is counted. The in-degree of a device node represents the number of preceding dependencies pointing to that device node. Device nodes with an in-degree of zero are added to the execution queue and output to the linkage topology execution sequence in sequence. After each device node completes its output, the preceding dependencies of that device node are released, and the in-degree of subsequent device nodes is updated; when the in-degree of a subsequent device node is updated to zero, the subsequent device node is added to the execution queue. The process involves repeatedly executing device node output, releasing prerequisite dependencies, updating device node in-degree, and updating the pending queue until all device nodes in the linkage dependency link graph have completed their output, thus generating a linkage topology execution sequence.

[0009] Preferably, the method for outputting control instructions that pass consistency verification includes: Based on the activated scene nodes in the scene state graph, traverse the scene association edges and state association edges to obtain the target running state corresponding to each device node, and generate control instructions for the corresponding device node based on the target running state; generate corresponding scene dynamic weights for each device node based on the control role of the device node in the current scene. The control commands corresponding to each device node are read sequentially according to the linkage topology execution sequence. Pre-dependency and mutual exclusion dependency checks are performed on each control command. When there is an incomplete pre-dependency between the device node corresponding to the control command, the execution of the control command is paused and the check is re-executed after the corresponding pre-dependency is satisfied. When there is a mutual exclusion dependency between the device node corresponding to the control instruction and the device node to be executed, the control instruction is prevented from entering the execution phase; control instructions that pass both the pre-dependency check and the mutual exclusion dependency check are determined to be control instructions that pass the consistency check.

[0010] Preferably, the method for determining arbitration priority includes: Based on the control commands that pass the consistency check of the target device node, control commands that are the same on the target device node are divided into the same arbitration request group, and different target device nodes establish corresponding arbitration request groups respectively. Read the scene dynamic weights of the device nodes corresponding to each control command within the same arbitration request group, compare the scene dynamic weights, and generate the arbitration priority order corresponding to the control commands according to the scene dynamic weights from largest to smallest; The control instruction with the highest dynamic weight in the scenario is determined as the first priority control instruction of the current arbitration request group, and the remaining control instructions are arranged in order according to the comparison results of the dynamic weight in the scenario to form the arbitration priority order of the corresponding arbitration request group.

[0011] Preferably, the method for generating a coordinated execution plan based on arbitration priority includes: Determine whether there are control instructions with the same scene dynamic weight within the same arbitration request group; when there are control instructions with the same scene dynamic weight, divide the control instructions with the same scene dynamic weight into a time arbitration subset; Obtain the arrival time of each control instruction in the time arbitration subset, sort the control instructions according to the arrival time, and update the arbitration priority order of the corresponding arbitration request group; Based on the updated arbitration priority, the control instruction corresponding to the first priority in each arbitration request group is selected as the final execution instruction for the corresponding device node, and a linkage execution plan is generated based on the final execution instructions of each device node and the linkage topology execution sequence.

[0012] Preferably, the method for updating the real-time status of each device node to the scene status map includes: According to the linkage topology execution sequence, the execution status of the corresponding control command of each device node is monitored in turn, and the execution status is compared with the target running status of the corresponding device node; when the execution status is consistent with the target running status, the monitoring of the next device node in the linkage topology execution sequence continues. When the execution state is inconsistent with the target running state, the device node where the execution exception occurs is taken as the starting node, and the device nodes affected by the execution exception are determined according to the linkage dependency link diagram to form a set of nodes affected by the exception. Perform corresponding correction processing based on the abnormal impact range corresponding to the abnormal impact node set; after completing the correction processing, obtain the current operating status of each device node, and update the current operating status of each device node to the real-time status of the corresponding device node in the scene status map.

[0013] A device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements a smart home linkage control method.

[0014] A storage medium storing a computer program, which, when executed, implements a smart home linkage control method.

[0015] This invention provides a smart home linkage control method, device, and storage medium, which have the following beneficial effects: By constructing a linkage dependency link graph, the number of unmet prerequisites for a device is represented by the in-degree of the device node. A topology sorting method based on in-degree dynamic release of prerequisites is used to generate a linkage topology execution sequence. This ensures that devices only enter the execution queue after all prerequisites are satisfied, guaranteeing that the device execution order corresponds to the actual dependency relationship. After a device node completes execution, the corresponding prerequisites are dynamically released, and the in-degree of subsequent nodes is updated in real time. This allows the linkage execution sequence to advance gradually as dependencies are resolved, eliminating the need to pre-fix the entire execution process and improving the adaptive capability of device scheduling in complex linkage scenarios. By abstracting device linkage as a topology scheduling process, when adding or adjusting device dependencies, only the linkage dependency link graph needs to be updated to regenerate the execution sequence, without reconfiguring the entire process. This improves the scalability, stability, and linkage reliability of the smart home linkage control system in complex scenarios.

[0016] Arbitration request groups are established based on target device nodes, allowing control commands from the same device to be compared in a unified arbitration space, avoiding interference between different control commands. The scenario dynamic weight of each control command's corresponding device node is then used as the primary arbitration criterion for prioritizing commands that meet the current scenario requirements. This ensures the arbitration result reflects the actual control value of the device, rather than relying solely on fixed priorities or control entity decisions. When multiple control commands have the same scenario dynamic weight, a second arbitration mechanism based on command arrival time is introduced to adjust the arbitration priority of commands with the same weight, ensuring a unique arbitration result and preventing the inability to resolve control conflicts due to identical weights. Based on the updated arbitration order, the final execution command for each device node is determined from each arbitration request group. Combined with the linkage topology execution sequence, a linkage execution plan is generated, subjecting device control priorities and execution order to unified constraints. This achieves integrated processing of multi-entity control conflict resolution and linkage execution scheduling, improving the stability, consistency, and overall execution reliability of linkage control in complex smart home scenarios. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of a smart home linkage control method according to the present invention; Figure 2 This is a schematic diagram of the structure of a smart home linkage control system according to the present invention; Figure 3 This is a schematic diagram of the device of the present invention; Figure 4 This is a schematic diagram of the storage medium of the present invention. Detailed Implementation

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

[0019] Please see Figure 1 In this embodiment, a smart home linkage control method is provided, which specifically includes the following steps: S1. Abstract the controlled devices, device status, and home scene in the home environment into device nodes, status nodes, and scene nodes, respectively. Establish directed association edges between the three types of nodes, record the real-time status of each device node, and output the corresponding scene status graph. S2. Identify the pre-dependencies and mutual dependencies between device nodes based on the scene state graph, and construct a linkage dependency link graph; perform topology sorting according to the in-degree of device nodes to generate a linkage topology execution sequence; S3. Generate control commands and corresponding dynamic weights of device nodes based on the scene state map, perform consistency verification on the control commands according to the linkage topology execution sequence, and output control commands that pass the consistency verification. S4. Establish an arbitration request group for control commands that have passed the consistency check, compare the scene dynamic weights of the device nodes, and determine the arbitration priority order; when the scene dynamic weights are the same, determine the arbitration priority order according to the arrival time of the control commands, and generate a linkage execution plan according to the arbitration priority order. S5. Monitor the linkage execution plan in real time, perform corresponding corrections based on the scope of impact of execution anomalies, and update the real-time status of each device node to the scene status map.

[0020] Methods for outputting the corresponding scene state graph include: Establish a corresponding device node for each controlled device in the home environment, establish a corresponding status node for the operating status of each controlled device, and establish a corresponding scene node for each home scene. In this embodiment, it should be noted that a corresponding device node is established for each controlled device in the home environment. The device node is used to uniquely represent a device that can receive control instructions and execute linkage control, each device node corresponds to one controlled device, and stores basic attribute information such as device number, device type, installation position and communication address. The device type is used to distinguish different categories such as lighting equipment, air conditioning equipment, curtain equipment, door lock equipment and security equipment, and the installation position is used to indicate the spatial area where the device is located, so as to quickly locate the devices participating in the linkage according to different home scenarios subsequently. For example, a device node D1 is established for the living room chandelier, a device node D2 is established for the living room air conditioner, a device node D3 is established for the electric curtain, and a device node D4 is established for the smart door lock, and each device node corresponds to a unique controlled device respectively.

[0021] After the establishment of the device nodes is completed, a corresponding state node is established for the operating state of each controlled device. The state node is used to describe the operating state of the device at a certain moment, each state node corresponds to one device state, the same device node can be associated with multiple state nodes, and different state nodes are independent of each other. For example, the lighting equipment can correspond to an on state, an off state and a dimming state; the air conditioning equipment can correspond to a cooling state, a heating state, a standby state and an off state; the curtain equipment can correspond to a fully open state, a half-open state and an off state. The state node is used to represent the target operating state that the device can reach, and provides a state mapping basis for the subsequent device control result. For example, the device node D1 is associated with state node S11 (on), state node S12 (off) and state node S13 (fifty percent brightness) respectively; the device node D2 is associated with state node S21 (cooling at twenty-six degrees Celsius), state node S22 (standby) and state node S23 (off) respectively.

[0022] Subsequently, a corresponding scenario node is established for each home scenario supported by the system. The scenario node is used to represent a preset or user-defined linkage control scenario, and each scenario node corresponds to a set of devices that need to participate in control together and target states. For example, a scenario node C1 is established corresponding to the "home mode", a scenario node C2 corresponding to the "away mode", a scenario node C3 corresponding to the "cinema mode", and a scenario node C4 corresponding to the "sleep mode".

[0023] According to the trigger relationship between the home scenario and the controlled device, a scenario association edge is established between the scenario node and the device node; according to the mapping relationship between the controlled device and the operating state, a state association edge is established between the device node and the state node; and a device association edge is established between the device nodes according to the preset linkage relationship between the devices; After the nodes are established, directed association edges are created between the three types of nodes. Among them, scenario association edges are created between scenario nodes and device nodes. The scenario association edge is used to indicate the devices that need to participate in linkage control when the corresponding home scenario is triggered. The direction of the association edge points from the scenario node to the device node, indicating that the control relationship is transmitted from the scenario to the devices. For example, when the scenario node C1 represents the home mode, three scenario association edges C1→D1, C1→D2 and C1→D3 are respectively created, indicating that after the home mode is triggered, the ceiling lamp in the living room, the air conditioner in the living room and the electric curtain need to be controlled to participate in the linkage together.

[0024] Subsequently, state association edges are created between device nodes and state nodes. The state association edge is used to indicate the target state that a device needs to reach after executing control. The direction of the association edge points from the device node to the state node, which is used to establish a one-to-one mapping relationship between the device and the target operating state. For example, creating D1→S11 indicates that the target state of the ceiling lamp in the living room after control is on; creating D2→S21 indicates that the target state of the air conditioner in the living room after control is cooling at 26 degrees Celsius; creating D3→S31 indicates that the target state of the electric curtain after control is fully open.

[0025] According to the preset linkage relationship between devices, device association edges are created between device nodes. The device association edge is used to describe the control dependency relationship between different devices. When the control execution of one device needs to rely on another device to complete the execution first, a directed association edge is created pointing from the pre-device node to the post-device node; when there is no execution sequence relationship between two devices, the corresponding association edge is not created. The device association edge is only used to describe the control association between devices, and provides data for subsequent analysis of the pre-dependency relationship and mutual exclusion dependency relationship between device nodes. For example, in the cinema mode, it is necessary to close the electric curtain first, then turn off the indoor lighting, and finally turn on the projection device, then two device association edges D3→D1 and D1→D5 are respectively created, where D5 represents the projection device, indicating that only after the electric curtain is completely closed can the lighting device perform the turn-off control, and after the lighting device is completely turned off can the projection device perform the turn-on control.

[0026] The device nodes, state nodes, scenario nodes and the corresponding directed association edges are organized to form a scenario state graph, and the current operating state of each controlled device is recorded in the scenario state graph as the real-time state of the corresponding device node.

[0027] After establishing all nodes and directed edges, the device node set, state node set, scene node set, and various directed edges are organized according to a unified graph structure to form a corresponding scene state graph. Real-time state information is maintained for each device node in the scene state graph. This real-time state information records the current actual operating state of the device. When the device completes its execution, the real-time state information of the corresponding device node is updated synchronously based on the device's feedback, ensuring that the scene state graph always remains consistent with the current operating state of the home environment. For example, when the living room chandelier is currently on, the real-time state of device node D1 is recorded as "on"; when the user turns off the living room chandelier, the system receives feedback information from the device and updates the real-time state of device node D1 to "off".

[0028] Methods for constructing a dependency chain graph include: Based on the activated scene nodes in the scene state graph, traverse the scene association edges corresponding to the scene nodes, obtain the device nodes associated with the scene nodes, and form a set of linked devices. It should be noted that, based on the activated scene node in the scene state graph, all scene association edges corresponding to that scene node are traversed to obtain all device nodes associated with that scene node, forming the set of linked devices for the current scene. Since scene association edges between scene nodes and device nodes have already been established in the scene state graph, when a home scene is triggered, it is not necessary to traverse all home devices; only the scene association edges emanating from the corresponding scene node are needed to obtain the device nodes participating in this linkage control. This reduces the number of subsequent dependency analysis objects and improves linkage parsing efficiency.

[0029] For example, when a user triggers "Away Mode", the corresponding scene node is C1. Scene node C1 is connected to smart door lock device node D1, living room lighting device node D2, air conditioner device node D3, and electric curtain device node D4 through scene association edges. Then, device nodes D1, D2, D3, and D4 are obtained sequentially along the scene association edges and form a set of linked devices corresponding to Away Mode. Other devices, such as kitchen lighting and television devices, that have not established association edges with scene node C1 are not included in this linkage parsing process.

[0030] Based on the preset linkage rules between devices, the relationships between device nodes in the linkage device set are resolved. When the control action corresponding to one device node requires another device node to complete the control before it can be executed, a prerequisite dependency relationship is established between the corresponding device nodes. After obtaining the set of interconnected devices, the relationships between the device nodes in the set are resolved according to the preset interconnection rules. These preset interconnection rules are device control rules established in advance during the system configuration phase, used to describe the execution sequence, execution constraints, and state constraints between different devices. These preset interconnection rules can be pre-defined by device manufacturers based on device operating characteristics, or customized by users during scene configuration based on their home usage habits. When a new device is added to the smart home system, corresponding interconnection rules can be added simultaneously to ensure that the interconnection relationships can be dynamically expanded.

[0031] Specifically, each linkage rule includes a front-end device, a back-end device, and a trigger condition. When the trigger condition is met, the back-end device is only allowed to execute the corresponding control action after the front-end device has completed the specified control action. The system reads all linkage rules corresponding to the set of linked devices and determines whether there is an execution sequence relationship between the devices one by one. For example, in "Cinema Mode," the following linkage rules are pre-set: the projector is turned on after the electric curtains are closed, and the projector is turned on after the lighting is turned off. Therefore, the rules are represented as "Curtains → Projection" and "Lighting → Projection," respectively. After reading the above rules, the system recognizes that the projector needs to wait for the curtains to close and the lighting to turn off. Therefore, it determines that there is a front dependency relationship between device node D2 and device node D5, and there is also a front dependency relationship between device node D1 and device node D5.

[0032] When it is determined that the control action corresponding to a device node must wait for another device node to complete its control before execution, a prerequisite dependency relationship is established between the corresponding device nodes. This is achieved by creating a directed dependency edge with the preceding device node as the starting node and the following device node as the ending node, representing the order in which the devices execute. This directed dependency edge is then used as the basis for calculating the in-degree of the device nodes during subsequent topology sorting. For example, if the projector device node D5 can only open after the motorized curtain device node D2 has closed, then a prerequisite dependency edge D2→D5 is established; similarly, if the projector device node D5 can only open after the lighting device node D1 has closed, then a prerequisite dependency edge D1→D5 is established. Therefore, the projector device node D5 has two prerequisite dependencies.

[0033] When the control actions corresponding to two device nodes cannot be executed simultaneously or the corresponding operating states cannot be established simultaneously, a mutual exclusion dependency relationship is established between the corresponding device nodes; a linkage dependency link diagram is constructed based on the set of linked devices, the preceding dependencies, and the mutual exclusion dependencies.

[0034] Based on the preset linkage rules, the system further analyzes whether there are mutual exclusion dependencies between the device nodes in the linkage device set. A mutual exclusion dependency means that the control actions corresponding to two device nodes cannot be executed simultaneously, or the target operating states of two devices cannot be simultaneously established. The system reads the mutual exclusion constraint information in the linkage rules. When the rules stipulate that two control actions have resource conflicts, security conflicts, or functional conflicts, it determines that there is a mutual exclusion dependency between the two device nodes and establishes a mutual exclusion relationship identifier between the corresponding device nodes.

[0035] Among these, the inability to execute control actions simultaneously includes multiple devices sharing the same control resources, communication resources, or power supply resources; and the inability for target operating states to be simultaneously established includes situations where establishing a target state for one device would cause the target state for another device to fail, or where the two target states have logical conflicts. For example, in energy-saving mode, a preset linkage rule stipulates that "when the air conditioner enters cooling mode, the fresh air equipment cannot enter maximum ventilation mode," otherwise it will lead to a decrease in cooling efficiency. Therefore, a mutual exclusion dependency is established between the air conditioner node D3 and the fresh air equipment node D6. As another example, during the automatic locking control of a smart door lock, simultaneous automatic unlocking control is not allowed. Therefore, a mutual exclusion dependency is established between the locking control action and the unlocking control action corresponding to the door lock.

[0036] After establishing prerequisite and mutual exclusion dependencies, a linkage dependency link graph is constructed based on the set of linked devices, prerequisite dependencies, and mutual exclusion dependencies. Specifically, the set of linked devices serves as the node set in the linkage dependency link graph. Prerequisite dependencies form directed dependency edges between device nodes, and mutual exclusion dependencies form mutual exclusion constraints between device nodes, together forming the linkage dependency link graph. Directed dependency edges represent the device control execution order, serving as the basis for subsequent calculation of device node in-degree and generation of the linkage topology execution sequence; mutual exclusion constraints represent device control conflict relationships, serving as the constraint basis for subsequent control command consistency verification and multi-party arbitration decisions.

[0037] For example, in cinema mode, the set of linked devices includes device nodes D1 (lighting equipment), D2 (electric curtains), D5 (projection equipment), and D7 (audio equipment). The preceding dependency edges D2→D5 and D1→D5 are established, indicating that the projection equipment must wait for the curtains and lighting equipment to complete their control before it can execute. At the same time, there is no execution conflict between the audio equipment D7 and the projection equipment D5, so no mutual exclusion relationship is established. They can be executed synchronously after the preceding dependency relationship is satisfied, thus ultimately forming a complete linkage dependency link graph.

[0038] Methods for generating linked topology execution sequences include: Based on the linkage dependency link graph, the in-degree of each device node is counted. The in-degree of a device node represents the number of preceding dependencies pointing to that device node. Device nodes with an in-degree of zero are added to the execution queue and output to the linkage topology execution sequence in sequence. Let the linkage dependency graph have a total of There are n device nodes, and the adjacency matrix of the device nodes is represented as follows: ;in, This represents the adjacency matrix corresponding to the linkage dependency link graph; This represents the matrix elements in the adjacency matrix, when the device node... There exists a pointer to the device node. When there is a prerequisite dependency, the value is 1; otherwise, the value is 0. This represents the total number of device nodes in the dependency chain diagram; For example, in cinema mode, if the projection device can only be turned on after the electric curtains have been closed, then a prerequisite dependency relationship is established between device node D2 and device node D5, corresponding to the adjacent matrix elements. If the projection device can only be turned on after the lighting equipment has been turned off, then the corresponding matrix element... .

[0039] The in-degree of each device node is calculated based on the adjacency matrix. The in-degree of a device node represents the number of unmet prerequisite dependencies of the current device node, and its calculation method is as follows: ;in, Represents device node in-degree; This represents the index for traversing all device nodes in the dependency chain graph; Represents device node Does a pointer to a device node exist? Pre-dependencies.

[0040] For example, if projection device node D5 depends on motorized curtain device node D2 and lighting device node D1, then the in-degree of device node D5 is 2; while motorized curtain device node D2 and lighting device node D1 have no prior dependencies, and their corresponding in-degrees are both 0.

[0041] After each device node completes its output, the preceding dependencies of that device node are released, and the in-degree of subsequent device nodes is updated; when the in-degree of a subsequent device node is updated to zero, the subsequent device node is added to the execution queue. The process involves repeatedly executing device node output, releasing prerequisite dependencies, updating device node in-degree, and updating the pending queue until all device nodes in the linkage dependency link graph have completed their output, thus generating a linkage topology execution sequence.

[0042] Let the linkage dependency link graph be as follows: The execution sequence of the linked topology is then represented as: ;in, This represents the generated execution sequence of the linked topology; This represents a topology sorting process that gradually releases prerequisite dependencies based on the in-degree of device nodes. During initialization, it prioritizes nodes that satisfy the prerequisite dependencies. Device nodes are added to the execution queue; for example, in cinema mode, the electric curtain device node D2 and the lighting device node D1 both have an in-degree of 0, so they are added to the execution queue first, while the projection device node D5 does not enter the execution queue for the time being because it still has two preceding dependencies.

[0043] Subsequently, after each device node completes scheduling, all its preceding dependencies are released, and the in-degree of its successor device nodes is updated. This is done when the adjacency matrix satisfies... At that time, for the device node Perform the following updates: ;in, This indicates the index of the device node that has completed scheduling. This indicates the index of the successor device node corresponding to the currently scheduled device node; This indicates an assignment update operation, which reassigns the updated calculation result to the device node. The degree of ingress.

[0044] When a device node completes execution, one of its preceding dependencies is removed. Therefore, the in-degree of all subsequent device nodes that directly depend on this device node is decreased by 1. When the in-degree of a subsequent device node is updated to 0, it indicates that all preceding dependencies for that device node have been satisfied, and it is immediately added to the execution queue to continue participating in scheduling. For example, after the electric curtain device node D2 completes execution, the in-degree of the projection device node D5 is updated from 2 to 1. Subsequently, after the lighting device node D1 completes execution, the in-degree of the projection device node D5 continues to be updated from 1 to 0. At this point, the projection device node D5 is immediately added to the execution queue and awaits scheduling.

[0045] Methods for outputting control commands that pass the consistency check include: Based on the activated scene nodes in the scene state graph, traverse the scene association edges and state association edges to obtain the target running state corresponding to each device node, and generate control instructions for the corresponding device node based on the target running state; generate corresponding scene dynamic weights for each device node based on the control role of the device node in the current scene. In this embodiment, it should be noted that the system first reads the target operating status corresponding to each device node and then queries the device protocol mapping table. The device protocol mapping table is used to record the control command format and control parameter mapping relationship corresponding to different types of controlled devices. For example, lighting equipment corresponds to the switch control protocol, air conditioning equipment corresponds to the operating mode, set temperature and fan speed control protocol, electric curtains correspond to the opening ratio control protocol, and smart door locks correspond to the unlocking or locking control protocol, etc.

[0046] The system retrieves the corresponding control command template from the device protocol mapping table based on the device type of the device node, then converts the target operating state into control parameters that the corresponding device can recognize, and fills them into the control command template, thereby forming the control instruction for the corresponding device node. The control instruction includes at least the device identifier, control action, and control parameters to ensure that devices of different brands and communication protocols can be scheduled and executed according to a unified format.

[0047] For example, when the target operating state corresponding to the cinema scene is "curtains closed, lights off, projection on", the system reads the target operating states corresponding to the motorized curtain device node, lighting device node, and projection device node respectively, and generates a curtain-closing control command, a lighting-closing control command, and a projection-on control command according to the device protocol mapping table. The curtain-closing control command includes the curtain device identifier and the closing percentage parameter; the lighting-closing control command includes the lighting device identifier and brightness setting parameter; and the projection-on control command includes the projection device identifier and power-on control parameter.

[0048] After generating control commands, the system generates corresponding dynamic scene weights for each device node based on its control role in the current scene. The system first reads the scene node corresponding to the currently active scene and then traverses the scene association edges between scene nodes and device nodes in the scene state graph. Based on the device node's role in the current scene, the system determines its corresponding control role. Control roles include core control devices, collaborative control devices, and auxiliary control devices. Core control devices are the key devices that determine whether the current scene can be established normally; collaborative control devices are devices that cooperate with core control devices to complete scene linkage; and auxiliary control devices are devices that only optimize the scene experience but do not affect scene establishment.

[0049] Subsequently, the system establishes a correspondence between control roles and scene dynamic weights, mapping different control roles to different levels of scene dynamic weights. Specifically, core control devices correspond to the first scene dynamic weight, collaborative control devices to the second scene dynamic weight, and auxiliary control devices to the third scene dynamic weight; the first scene dynamic weight is greater than the second scene dynamic weight, and the second scene dynamic weight is greater than the third scene dynamic weight. The system associates and stores the mapped scene dynamic weights with the corresponding device nodes, serving as the priority basis for subsequent control command arbitration.

[0050] For example, in a cinema scene, the projection equipment and motorized curtains directly determine whether the cinema scene can be established, so they are identified as core control equipment and assigned dynamic weights for the first scene; the lighting equipment is used to help create the viewing environment, so it is identified as a coordinating control equipment and assigned dynamic weights for the second scene; the aromatherapy equipment is only used to improve the user experience and does not affect the establishment of the cinema scene, so it is identified as an auxiliary control equipment and assigned dynamic weights for the third scene.

[0051] For example, in a sleep scenario, air conditioning and lighting equipment are used to ensure a good sleep environment, thus corresponding to core control devices and assigned a first-scene dynamic weight; electric curtains are used to assist in blocking light, thus corresponding to collaborative control devices and assigned a second-scene dynamic weight; background music equipment is only used to improve the sleep experience, thus corresponding to auxiliary control devices and assigned a third-scene dynamic weight. It is evident that the same device node can correspond to different control roles in different home scenarios, and its scene dynamic weight is adjusted synchronously with the currently active scenario.

[0052] The control commands corresponding to each device node are read sequentially according to the linkage topology execution sequence. Pre-dependency and mutual exclusion dependency checks are performed on each control command. When there is an incomplete pre-dependency between the device node corresponding to the control command, the execution of the control command is paused and the check is re-executed after the corresponding pre-dependency is satisfied. When there is a mutual exclusion dependency between the device node corresponding to the control instruction and the device node to be executed, the control instruction is prevented from entering the execution phase; control instructions that pass both the pre-dependency check and the mutual exclusion dependency check are determined to be control instructions that pass the consistency check.

[0053] Methods for determining arbitration priority include: Based on the control commands that pass the consistency check of the target device node, control commands that are the same on the target device node are divided into the same arbitration request group, and different target device nodes establish corresponding arbitration request groups respectively. Assume the system forms The arbitration request group, then the first The arbitration request group is represented as follows: ;in, Indicates the first One arbitration request group; An index representing a group of arbitration requests; Indicates the first [node name] targeting the same device node. One control command; Indicates the index of the control command; This indicates the number of control instructions within the current arbitration request group.

[0054] For example, if user A issues a command to turn on the air conditioner via a mobile terminal, and user B issues a command to turn off the air conditioner via a voice terminal, since both commands correspond to the air conditioner device node, they are assigned to the same arbitration request group. However, the control command corresponding to the lighting device is assigned to a separate arbitration request group and is not involved in the arbitration of the air conditioner device.

[0055] Read the scene dynamic weights of the device nodes corresponding to each control command within the same arbitration request group, compare the scene dynamic weights, and generate the arbitration priority order corresponding to the control commands according to the scene dynamic weights from largest to smallest; After establishing the arbitration request group, the scene dynamic weights of all control commands corresponding to the device nodes within the same arbitration request group are compared. Since each control command corresponds to the same target device node, the system directly reads the scene dynamic weight associated with each control command and determines the priority control command with the largest scene dynamic weight in the current arbitration request group. ;in, This indicates the control command with the highest dynamic weight in the current arbitration request group; Indicates control commands Dynamic weights for the corresponding device nodes in the scene; This indicates a control instruction that selects the scenario with the highest dynamic weight from the current arbitration request group.

[0056] The control instruction with the highest dynamic weight in the scenario is determined as the first priority control instruction of the current arbitration request group, and the remaining control instructions are arranged in order according to the comparison results of the dynamic weight in the scenario to form the arbitration priority order of the corresponding arbitration request group.

[0057] For example, when controlling living room lighting in both the "away from home" and "entertainment" scenarios simultaneously, the dynamic scene weight for the lighting in the "away from home" scenario is higher than that in the "entertainment" scenario. Therefore, the digital comparator prioritizes outputting the control command corresponding to the "away from home" scenario and designates it as the first priority control command in the current arbitration request group, while the control command corresponding to the "entertainment" scenario follows. When the dynamic scene weights corresponding to all control commands within the arbitration request group are different, the arbitration priority can be determined directly, and the subsequent linkage execution plan generation process can begin.

[0058] Methods for generating joint execution plans based on arbitration priority include: Determine whether there are control instructions with the same scene dynamic weight within the same arbitration request group; when there are control instructions with the same scene dynamic weight, divide the control instructions with the same scene dynamic weight into a time arbitration subset; Obtain the arrival time of each control instruction in the time arbitration subset, sort the control instructions according to the arrival time, and update the arbitration priority order of the corresponding arbitration request group; Update the arbitration priority order for the corresponding arbitration request group: ;in, Indicates the updated arbitration priority; Indicates control commands Arbitration has higher priority than control orders. ; Indicates control commands Arbitration has higher priority than control orders. ; Indicates control commands Arrival time; Indicates control commands Arrival time; Based on the updated arbitration priority, the control instruction corresponding to the first priority in each arbitration request group is selected as the final execution instruction for the corresponding device node, and a linkage execution plan is generated based on the final execution instructions of each device node and the linkage topology execution sequence.

[0059] For example, in a homecoming scenario, family member A issues a control command to turn on the living room air conditioner via a mobile terminal, while family member B issues a control command to turn off the living room air conditioner via a smart panel. Both control commands correspond to the living room air conditioner device node, and if their dynamic weights are the same, they enter the time arbitration subset. Let the arrival time of control command A be 09:00:01, and the arrival time of control command B be 09:00:03. Then, the control commands in the time arbitration subset are sorted according to their arrival times, and the arbitration priority of the corresponding arbitration request group is updated so that the arbitration priority of control command A is higher than that of control command B. Subsequently, the system selects the control command with the highest arbitration priority from this arbitration request group as the final execution command for the living room air conditioner device node. Based on this, if the linkage topology execution sequence is "curtains → lighting → air conditioner," the system maps and integrates the final execution commands corresponding to the curtain device node, lighting device node, and living room air conditioner device node to generate a linkage execution plan of "open curtains → turn on lighting → turn on living room air conditioner," and executes it sequentially according to the linkage topology execution sequence.

[0060] Methods for updating the real-time status of each device node to the scene status graph include: According to the linkage topology execution sequence, the execution status of the corresponding control command of each device node is monitored in turn, and the execution status is compared with the target running status of the corresponding device node; when the execution status is consistent with the target running status, the monitoring of the next device node in the linkage topology execution sequence continues. When the execution state is inconsistent with the target running state, the device node where the execution exception occurs is taken as the starting node, and the device nodes affected by the execution exception are determined according to the linkage dependency link diagram to form a set of nodes affected by the exception. In this embodiment, it should be noted that the node identifier corresponding to the device node that experienced the execution exception is obtained and used as the starting point for exception propagation. Then, based on the preset device association edges and preceding dependencies between device nodes in the linkage dependency chain graph, a graph traversal operation is performed on the exception initiating node, tracing its subsequent dependent nodes and constrained nodes level by level along the direction of the device association edges until the traversal is completed or no subsequent dependent nodes are reached. During the traversal process, all device nodes that meet the dependency propagation conditions are added to the set of nodes affected by the exception. The dependency propagation conditions include: the current device node has a direct or indirect dependency path relationship with the exception initiating node in the linkage dependency chain graph, and the dependency path satisfies the execution order constraint or state constraint propagation conditions, thereby indicating that the running state of the device node may be affected by the execution failure of the exception initiating node.

[0061] Perform corresponding correction processing based on the abnormal impact range corresponding to the abnormal impact node set; after completing the correction processing, obtain the current operating status of each device node, and update the current operating status of each device node to the real-time status of the corresponding device node in the scene status map.

[0062] After forming the set of nodes affected by an anomaly, the system performs hierarchical correction processing on the linkage execution plan based on the scope of the anomaly's impact. Specifically: when the set of nodes affected by an anomaly only contains the node that started the anomaly, it is determined to be a local anomaly, and only the control command corresponding to that device node is resent or its status is reset; when the set of nodes affected by an anomaly contains multiple device nodes but does not cover all nodes in the linkage execution plan, it is determined to be a local link anomaly. In this case, the subsequent execution of the device nodes corresponding to the set of nodes affected by the anomaly is suspended, and the execution path of the affected subgraph is readjusted based on the linkage dependency link graph to generate a locally corrected execution sequence. When an anomaly affects a set of nodes that cover all device nodes in the coordinated execution plan, it is determined to be a global anomaly. At this point, the current coordinated execution plan is terminated, and a re-planning and generation mechanism based on the current scene state graph is triggered. After the correction process is completed, the system re-collects and synchronizes the operating status of each device node. Specifically, this includes: obtaining the current actual operating feedback status of each device node, mapping and updating it with the corresponding status node in the scene state graph, and synchronously correcting the weights of the state association edges between device nodes and status nodes. This ensures that the state information in the scene state graph is consistent with the actual operating status of the home environment, thereby providing an updated state basis for subsequent coordinated control and scene reconstruction.

[0063] For example, in a "homecoming linkage scenario," the system executes a linkage plan: "Curtains closed → Air conditioner turned on → Lights turned on." If an execution anomaly occurs when executing "Air conditioner turned on," the system identifies the air conditioner node as the originating node of the anomaly. Tracing back along the linkage dependency graph, the system finds that the execution of the lighting device depends on changes in the air conditioner's state (e.g., adjusting the lighting mode after the air conditioner stabilizes). Therefore, the lighting device node is included in the set of nodes affected by the anomaly. The curtain device, having already completed its operation and not constrained by the air conditioner, is not affected. Based on this, the system determines it to be a partial link anomaly, suspends subsequent execution of the lighting device, and regenerates a corrected execution sequence for the local sub-link formed by the air conditioner and lights, for example, adjusting it to "Restart the air conditioner → Turn on the lights after the air conditioner stabilizes." Finally, the system reads the latest operational feedback status of the curtains, air conditioner, and lights and updates the scene state graph to ensure that the real-time status of the device nodes is consistent with the actual home environment.

[0064] It should be noted that all formulas in this manual are calculated by removing dimensions and taking their numerical values. The formulas are derived from software simulations based on a large amount of collected data to obtain the most recent real-world results. The preset parameters and thresholds in the formulas are set by those skilled in the art according to the actual situation. Example

[0065] Please see Figure 2 As shown, parts not described in detail in this embodiment are described in Embodiment 1. A smart home linkage control system is provided, including: The graph construction module is used to abstract controlled devices, device status, and home scenes in the home environment into device nodes, status nodes, and scene nodes, respectively. It establishes directed association edges between the three types of nodes, records the real-time status of each device node, and outputs the corresponding scene status graph. The linkage parsing module is used to identify the pre-dependencies and mutual exclusions between device nodes based on the scene state graph, and to construct a linkage dependency link graph; it also performs topology sorting based on the in-degree of device nodes to generate a linkage topology execution sequence. The instruction verification module is used to generate control instructions and corresponding dynamic weights of device nodes based on the scene state map, perform consistency verification on the control instructions according to the linkage topology execution sequence, and output control instructions that pass the consistency verification. The arbitration decision module is used to establish arbitration request groups for control commands that have passed consistency verification, compare the scene dynamic weights of device nodes, and determine the arbitration priority order; when the scene dynamic weights are the same, the arbitration priority order is determined according to the arrival time of the control commands, and a linkage execution plan is generated according to the arbitration priority order. The feedback correction module is used to monitor the linkage execution plan in real time, perform corresponding correction processing according to the scope of the impact of execution anomalies, and update the real-time status of each device node to the scene status map.

[0066] The modules are connected via wired and / or wireless means to enable data transmission between them. Example

[0067] Please see Figure 3 As shown, this application also provides a device 500. The device 500 may include one or more processors and one or more memories. The memories store computer-readable code, which, when executed by the one or more processors, can perform a smart home linkage control method as described above.

[0068] like Figure 3 As shown, device 500 may include a bus 501, one or more CPUs 502, ROM 503, RAM 504, a communication port 505 connected to a network, input / output 506, hard disk 507, etc. The storage device in device 500, such as ROM 503 or hard disk 507, may store a smart home linkage control method provided in this application. Furthermore, device 500 may also include a user interface 508. Of course, Figure 2 The architecture shown is merely exemplary and can be omitted as needed when implementing different devices. Figure 2 One or more components in the illustrated electronic device. Example

[0069] Please see Figure 4The diagram shows a storage medium 250 according to one embodiment of this application. The storage medium 250 stores computer-readable instructions. When the computer-readable instructions are executed by a processor, a smart home linkage control method according to an embodiment of this application, as described with reference to the above figures, can be performed. The storage medium 250 includes, but is not limited to, volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc.

[0070] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this invention can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0071] In the several embodiments provided by this invention, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only one method, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0072] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

[0073] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A smart home linkage control method, characterized in that, include: S1. Abstract the controlled devices, device status, and home scene in the home environment into device nodes, status nodes, and scene nodes, respectively. Establish directed association edges between the three types of nodes, record the real-time status of each device node, and output the corresponding scene status graph. S2. Identify the pre-dependencies and mutual dependencies between device nodes based on the scene state graph, and construct a linkage dependency link graph; perform topology sorting according to the in-degree of device nodes to generate a linkage topology execution sequence; S3. Generate control commands and corresponding dynamic weights of device nodes based on the scene state map, perform consistency verification on the control commands according to the linkage topology execution sequence, and output control commands that pass the consistency verification. S4. Establish an arbitration request group for control commands that have passed the consistency check, compare the scene dynamic weights of the device nodes, and determine the arbitration priority order; when the scene dynamic weights are the same, determine the arbitration priority order according to the arrival time of the control commands, and generate a linkage execution plan according to the arbitration priority order. S5. Monitor the linkage execution plan in real time, perform corresponding corrections based on the scope of impact of execution anomalies, and update the real-time status of each device node to the scene status map.

2. The smart home linkage control method according to claim 1, characterized in that, The method for outputting the corresponding scene state map includes: Establish a corresponding device node for each controlled device in the home environment, establish a corresponding status node for the operating status of each controlled device, and establish a corresponding scene node for each home scene. Based on the triggering relationship between home scenes and controlled devices, scene association edges are established between scene nodes and device nodes. Based on the mapping relationship between controlled devices and operating states, state association edges are established between device nodes and state nodes. Based on the preset linkage relationship between devices, device association edges are established between device nodes. The device nodes, status nodes, scene nodes, and their corresponding directed edges are organized to form a scene state graph, and the current operating status of each controlled device is recorded in the scene state graph as the real-time status of the corresponding device node.

3. The smart home linkage control method according to claim 2, characterized in that, The method for constructing the linkage dependency graph includes: Based on the activated scene nodes in the scene state graph, traverse the scene association edges corresponding to the scene nodes, obtain the device nodes associated with the scene nodes, and form a set of linked devices. Based on the preset linkage rules between devices, the relationships between device nodes in the linkage device set are resolved. When the control action corresponding to one device node requires another device node to complete the control before it can be executed, a prerequisite dependency relationship is established between the corresponding device nodes. When the control actions corresponding to two device nodes cannot be executed simultaneously or the corresponding operating states cannot be established simultaneously, a mutual exclusion dependency relationship is established between the corresponding device nodes; a linkage dependency link diagram is constructed based on the set of linked devices, the preceding dependencies, and the mutual exclusion dependencies.

4. The smart home linkage control method according to claim 3, characterized in that, The method for generating the linked topology execution sequence includes: Based on the linkage dependency link graph, the in-degree of each device node is counted. The in-degree of a device node represents the number of preceding dependencies pointing to that device node. Device nodes with an in-degree of zero are added to the execution queue and output to the linkage topology execution sequence in sequence. After each device node completes its output, the preceding dependencies of that device node are released, and the in-degree of subsequent device nodes is updated; when the in-degree of a subsequent device node is updated to zero, the subsequent device node is added to the execution queue. The process involves repeatedly executing device node output, releasing prerequisite dependencies, updating device node in-degree, and updating the pending queue until all device nodes in the linkage dependency link graph have completed their output, thus generating a linkage topology execution sequence.

5. The smart home linkage control method according to claim 4, characterized in that, The method for outputting control instructions that pass consistency verification includes: Based on the activated scene nodes in the scene state graph, traverse the scene association edges and state association edges to obtain the target running state corresponding to each device node, and generate control instructions for the corresponding device node based on the target running state; generate corresponding scene dynamic weights for each device node based on the control role of the device node in the current scene. The control commands corresponding to each device node are read sequentially according to the linkage topology execution sequence. Pre-dependency and mutual exclusion dependency checks are performed on each control command. When there is an incomplete pre-dependency between the device node corresponding to the control command, the execution of the control command is paused and the check is re-executed after the corresponding pre-dependency is satisfied. When there is a mutual exclusion dependency between the device node corresponding to the control instruction and the device node to be executed, the control instruction is prevented from entering the execution phase; control instructions that pass both the pre-dependency check and the mutual exclusion dependency check are determined to be control instructions that pass the consistency check.

6. The smart home linkage control method according to claim 5, characterized in that, The method for determining arbitration priority includes: Based on the control commands that pass the consistency check of the target device node, control commands that are the same on the target device node are divided into the same arbitration request group, and different target device nodes establish corresponding arbitration request groups respectively. Read the scene dynamic weights of the device nodes corresponding to each control command within the same arbitration request group, compare the scene dynamic weights, and generate the arbitration priority order corresponding to the control commands according to the scene dynamic weights from largest to smallest; The control instruction with the highest dynamic weight in the scenario is determined as the first priority control instruction of the current arbitration request group, and the remaining control instructions are arranged in order according to the comparison results of the dynamic weight in the scenario to form the arbitration priority order of the corresponding arbitration request group.

7. A smart home linkage control method according to claim 6, characterized in that, The method for generating a coordinated execution plan based on arbitration priority includes: Determine whether there are control instructions with the same scene dynamic weight within the same arbitration request group; when there are control instructions with the same scene dynamic weight, divide the control instructions with the same scene dynamic weight into a time arbitration subset; Obtain the arrival time of each control instruction in the time arbitration subset, sort the control instructions according to the arrival time, and update the arbitration priority order of the corresponding arbitration request group; Based on the updated arbitration priority, the control instruction corresponding to the first priority in each arbitration request group is selected as the final execution instruction for the corresponding device node, and a linkage execution plan is generated based on the final execution instructions of each device node and the linkage topology execution sequence.

8. The smart home linkage control method according to claim 7, characterized in that, The method for updating the real-time status of each device node to the scene status map includes: According to the linkage topology execution sequence, the execution status of the corresponding control command of each device node is monitored in turn, and the execution status is compared with the target running status of the corresponding device node; when the execution status is consistent with the target running status, the monitoring of the next device node in the linkage topology execution sequence continues. When the execution state is inconsistent with the target running state, the device node where the execution exception occurs is taken as the starting node, and the device nodes affected by the execution exception are determined according to the linkage dependency link diagram to form a set of nodes affected by the exception. Perform corresponding correction processing based on the abnormal impact range corresponding to the abnormal impact node set; after completing the correction processing, obtain the current operating status of each device node, and update the current operating status of each device node to the real-time status of the corresponding device node in the scene status map.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the electronic device executes the computer program, it implements the smart home linkage control method according to any one of claims 1-8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed, implements a smart home linkage control method according to any one of claims 1-8.

Images