Cross-system linkage method for smart home entry-level devices

Abstract

The present invention discloses a cross-system linkage method for smart home entry-level devices, which relates to the field of smart home technology. The key points of its technical solution include the following steps: collecting device status data information of each system and scene instructions of the smart home; wherein, the device status data information includes a device status data set, a trigger condition data set and a linkage execution parameter set; parsing the scene instructions of the smart home to obtain the target device type and cross-system linkage rules; performing priority classification analysis on the cross-system linkage rules to hierarchically decompose the linkage tasks to obtain a linkage task result set; performing communication adaptation processing on the tasks at each level in the linkage task result set according to the communication protocol of the target device type and the cross-system linkage rules to obtain a linkage task set to be executed; the effect is to continuously adapt to user habits and needs to help smart homes move from simple device connections to a deeply collaborative, intelligent and reliable full-scene smart life ecosystem.

Description

Technical Field

[0001] The present invention relates to the field of smart home technology, and more specifically, to a cross-system linkage method for smart home entry-level devices. Background Art

[0002] The rapid adoption of smart homes, coupled with the increasing complexity of device types and system architectures, has created a pressing need for cross-system collaboration, yet it faces multiple challenges. First, the diverse smart home device ecosystem, with smart lighting, security, and environmental control systems utilizing different communication protocols such as Wi-Fi, Bluetooth, and Zigbee, is crucial. For example, smart door locks often use Bluetooth, while smart curtains often rely on Zigbee. This heterogeneous nature of protocols creates a "language barrier" between devices, hindering direct collaboration. For example, if the door locks, lighting, and air conditioning systems can't communicate across protocols when a user issues a "home mode" command, the linkage scenario won't execute smoothly. Second, existing linkage solutions often focus on a single system or a simple combination of devices, lacking sophisticated handling for complex scenarios. For example, traditional timing control relies solely on fixed time or simple status triggers, failing to account for data exchange latency and clock synchronization errors across multiple systems. This can lead to situations where, when executing "cinema mode," the projector might start but the lights don't dim immediately, disrupting the immersive experience. Furthermore, fault tolerance for abnormal conditions is insufficient, making linkage easily interrupted by network fluctuations or temporary device failures, impacting user experience and home safety. Summary of the Invention

[0003] In view of the shortcomings of the existing technology, the purpose of the present invention is to provide a cross-system linkage method for smart home entry-level devices.

[0004] To achieve the above object, the present invention provides the following technical solutions:

[0005] A cross-system linkage method for smart home entry-level devices, the method comprising the following steps:

[0006] Collecting device status data information of each system and scene instructions of smart home; wherein, the device status data information includes a device status data set, a trigger condition data set and a linkage execution parameter set;

[0007] Parse smart home scene commands to obtain target device types and cross-system linkage rules;

[0008] Perform priority classification analysis on cross-system linkage rules to decompose linkage tasks into hierarchical levels to obtain linkage task result sets;

[0009] According to the communication protocol of the target device type and the cross-system linkage rules, communication adaptation processing is performed on the tasks at each level in the linkage task result set to obtain the linkage task set to be executed;

[0010] Extract key trigger nodes from the linkage task result set;

[0011] Set the system linkage trigger conditions according to the key trigger nodes, and process the system linkage trigger conditions, trigger condition data set, linkage execution parameter set, device status data set and data between each system to obtain the time series evaluation set to be processed;

[0012] A device linkage behavior trajectory set is obtained based on the linkage execution records of the key trigger nodes, the actions of each system device in the device linkage behavior trajectory set are analyzed to obtain a third interaction performance dataset, and the execution of the cross-system linkage task is evaluated based on the third interaction performance dataset and the trigger condition dataset to obtain a reliability evaluation result set to be executed;

[0013] After comprehensive linkage strategy optimization of the linkage task set to be executed, the timing evaluation set to be processed and the reliability evaluation result set to be executed, a cross-system linkage execution plan is obtained.

[0014] Preferably, communication adaptation processing is performed on tasks at each level in the linkage task result set according to the communication protocol of the target device type and the cross-system linkage rule to obtain a linkage task set to be executed, which specifically includes the following steps:

[0015] Identifying the communication protocol of the target device type to obtain a protocol identification result;

[0016] According to the protocol identification results and the cross-system linkage rules, communication adaptation processing is performed on the tasks at each level in the linkage task result set to obtain the linkage task set to be executed.

[0017] Preferably, the system linkage trigger conditions, trigger condition data set, linkage execution parameter set, device status data set and data between each system are processed to obtain a time series evaluation set to be processed, specifically:

[0018] The first interactive performance data set is obtained based on the matching degree of the system linkage trigger conditions and the device status data set, as well as the data interaction delay results between the systems; the second interactive performance data set is obtained based on the matching degree of the linkage trigger conditions and the device status data set, as well as the data synchronization deviation results between the systems. The execution timing of the cross-system linkage task is evaluated based on the first interactive performance data set, the second interactive performance data set, the device status data set and the linkage execution parameter set to obtain the timing evaluation set to be processed.

[0019] Preferably, identifying the communication protocol of the target device type to obtain a protocol identification result specifically includes the following steps:

[0020] Collect physical interface information and network connection parameters of the target device type;

[0021] The communication protocol of the device is identified based on the physical interface information and network connection parameters to obtain a protocol identification result.

[0022] Preferably, communication adaptation processing is performed on tasks at each level in the linkage task result set according to the protocol identification result and the cross-system linkage rule to obtain a linkage task set to be executed, which specifically includes the following steps:

[0023] Adjusting the communication parameters of the linkage task according to the protocol identification result and the priority level of the cross-system linkage rule to obtain a parameter adjustment result;

[0024] Obtain the execution node positions of tasks at each level in the linkage task result set, convert the communication protocols and process the data formats of tasks at each level in the linkage task result set according to the parameter adjustment results and the execution node positions, and then obtain a standardized task data set;

[0025] Verify the preconditions and postconditions of each task in the standardized task dataset to obtain a verification result set;

[0026] Obtain the execution dependency dataset of each level of tasks in the linkage task result set, pre-process and sort the tasks of each level in the linkage task result set according to the dependency dataset and the verification result set to obtain the linkage task set to be executed.

[0027] Preferably, extracting key trigger nodes from the linkage task result set specifically includes the following steps:

[0028] Extract the trigger event data information of the priority task from the verification result set;

[0029] The key trigger nodes are extracted from the linkage task result set based on the trigger event data information and the execution node positions of tasks at each level.

[0030] Preferably, it also includes:

[0031] Based on the time trigger condition of the key trigger node, the scheduled task cycle and execution time window of each system device are marked as a first trigger condition set, and the real-time time synchronization status of the device and the task execution history data are collected to obtain a first device status data set;

[0032] Based on the state trigger conditions of the key trigger nodes, the operating state thresholds and state change rules of each system device are marked as a second trigger condition set, and the current operating parameters and state feedback signals of the devices are collected to obtain a second device state data set;

[0033] Based on the combined trigger conditions of key trigger nodes, the multi-system device status combination logic and linkage response rules are marked as a third trigger condition set, and cross-system data interaction logs and linkage execution records are collected to obtain a third device status data set;

[0034] The first trigger condition set, the second trigger condition set and the third trigger condition set are combined into a trigger condition data set; the first device status data set, the second device status data set and the third device status data set are combined into a device status data set.

[0035] Preferably, a first interactive performance data set is obtained based on the matching degree between the system linkage trigger condition and the device status data set and the data interaction delay result between each system; a second interactive performance data set is obtained based on the matching degree between the linkage trigger condition and the device status data set and the data synchronization deviation result between each system, and the execution timing of the cross-system linkage task is evaluated based on the first interactive performance data set, the second interactive performance data set, the device status data set and the linkage execution parameter set to obtain a timing evaluation set to be processed, which specifically includes the following steps:

[0036] Counting the matching degree between the system linkage triggering condition and each device status in the device status data set to obtain a third matching degree data set;

[0037] Predicting the delay time of the data interaction path based on the third matching degree dataset and the multi-system network topology to obtain a first interaction performance dataset;

[0038] The second interactive performance dataset is obtained by predicting the deviation range of multi-system data synchronization based on the matching degree dataset and the cross-system clock synchronization error;

[0039] Evaluate the trigger response time and execution order of the linkage tasks according to the first interactive performance data set and the device status data set to obtain a first to-be-processed timing evaluation result set;

[0040] Evaluating the timing consistency and fault tolerance of the multi-system linkage according to the second interactive performance data set and the linkage execution parameter set to obtain a second to-be-processed timing evaluation result set;

[0041] The first to-be-processed timing evaluation result set and the second to-be-processed timing evaluation result set are combined into a to-be-processed timing evaluation set.

[0042] Preferably, a device linkage behavior trajectory set is obtained based on the linkage execution records of the key trigger nodes, the actions of each system device in the device linkage behavior trajectory set are analyzed to obtain a third interaction performance data set, and the execution of the cross-system linkage task is evaluated based on the third interaction performance data set and the trigger condition data set to obtain a reliability evaluation result set to be executed, which specifically includes the following steps:

[0043] According to the linkage execution records of key trigger nodes, the linkage execution timestamps and action sequence data of each system device are collected to generate a device linkage behavior trajectory set;

[0044] Obtaining the device action record corresponding to the first trigger condition set during the linkage execution process to obtain a first behavior trajectory subset;

[0045] Acquire the device action record corresponding to the second trigger condition set during the linkage execution process to obtain a second behavior trajectory subset;

[0046] Calculate the action timing deviation of the first behavior trajectory subset and the second behavior trajectory subset to output a deviation data set;

[0047] The consistency and synchronization of the actions of the devices in each system are judged based on the deviation dataset and the third matching dataset to obtain a third interactive performance dataset;

[0048] Based on the third interactive performance data set and the trigger condition data set, the execution reliability of the cross-system linkage task under abnormal conditions is evaluated to obtain a reliability evaluation result set to be executed.

[0049] Preferably, a cross-system linkage execution plan is obtained after a comprehensive linkage strategy optimization is performed on the linkage task set to be executed, the time sequence evaluation set to be processed, and the reliability evaluation result set to be executed, which specifically includes the following steps:

[0050] Performing timing conflict detection on the linkage task set to be executed and the first timing evaluation result set to be processed to obtain a first optimization difference result set;

[0051] Performing timing redundancy judgment on the linkage task set to be executed and the second timing evaluation result set to be processed to obtain a second optimization difference result set;

[0052] Perform reliability verification on the linkage task set to be executed and the reliability evaluation result set to be executed to obtain a third optimized difference result set;

[0053] Performing weight distribution processing on the first optimization difference result set, the second optimization difference result set, and the third optimization difference result set to obtain an optimization weight result set;

[0054] Based on the optimization weight result set, the execution order and resource allocation of the linkage task set to be executed are optimized to obtain the linkage strategy optimization result set;

[0055] After performing integrated execution plan generation processing on the cross-system linkage tasks in the linkage strategy optimization result set, a cross-system linkage execution plan is obtained.

[0056] Compared with the prior art, the present invention has the following beneficial effects:

[0057] The present invention brings significant gains in multiple dimensions by constructing a complete system from data collection and analysis to strategy optimization. At the device collaboration level, by accurately identifying the target device communication protocol, the protocol barriers between different system devices are broken, allowing multiple types of devices such as smart door locks, lighting, and environmental control to interact smoothly. For example, after the smart door lock is unlocked, the lighting system can be seamlessly linked to turn on the lights and the air conditioning system can be adjusted to adjust the temperature, realizing "talking and moving together" across system devices, greatly improving the consistency and fluency of the smart home scenario experience. In terms of task execution timing, relying on the matching analysis of the system linkage trigger conditions and device status, combined with network topology, clock synchronization error and other factors to predict data interaction delays and synchronization deviations, the linkage task trigger response, execution order and multi-system timing consistency are accurately evaluated to effectively avoid task conflicts and delays. For example, in the "home mode", each device can be started in a reasonable sequence, with the lights on first and the air conditioner adjusted to a suitable temperature later, making scene switching natural and smooth, and optimizing user experience. This solution continuously collects data such as device status and linkage execution to provide a basis for the iteration of the smart home system. It can optimize device communication parameters and linkage logic by analyzing task timing deviations and reliability shortcomings, making the system smarter with use, and constantly adapting to user habits and needs to help smart homes move from simple device connections to a deeply collaborative, intelligent and reliable full-scene smart life ecosystem, creating a more convenient, efficient and secure living experience for users. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 This is a schematic diagram of the steps of the cross-system linkage method for smart home entry-level devices proposed by the present invention;

[0059] Figure 2 This is a schematic diagram of obtaining a set of linkage tasks to be executed in the cross-system linkage method for smart home entry-level devices proposed by the present invention;

[0060] Figure 3 This is a schematic diagram of obtaining a set of reliability assessment results to be executed in the cross-system linkage method for smart home entry-level devices proposed in the present invention. DETAILED DESCRIPTION

[0061] Reference Figures 1 to 3 .

[0062] The embodiment further illustrates the cross-system linkage method of smart home entry-level devices proposed in the present invention.

[0063] A cross-system linkage method for smart home entry-level devices, the method comprising the following steps:

[0064] Collect device status data information of each system and scene instructions of smart home; wherein, the device status data information includes device status data set, trigger condition data set and linkage execution parameter set;

[0065] Parse smart home scene commands to obtain target device types and cross-system linkage rules;

[0066] Perform priority classification analysis on cross-system linkage rules to decompose linkage tasks into hierarchical levels to obtain linkage task result sets;

[0067] According to the communication protocol of the target device type and the cross-system linkage rules, communication adaptation processing is performed on the tasks at each level in the linkage task result set to obtain the linkage task set to be executed;

[0068] Extract key trigger nodes from the linkage task result set;

[0069] Set the system linkage trigger conditions according to the key trigger nodes, and process the system linkage trigger conditions, trigger condition data set, linkage execution parameter set, device status data set and data between each system to obtain the time series evaluation set to be processed;

[0070] A device linkage behavior trajectory set is obtained based on the linkage execution records of the key trigger nodes, and the actions of each system device in the device linkage behavior trajectory set are analyzed to obtain a third interaction performance dataset. The execution of the cross-system linkage task is evaluated based on the third interaction performance dataset and the trigger condition dataset to obtain a reliability evaluation result set to be executed;

[0071] After comprehensive linkage strategy optimization of the linkage task set to be executed, the timing evaluation set to be processed and the reliability evaluation result set to be executed, a cross-system linkage execution plan is obtained.

[0072] The cross-system linkage of smart home entry-level devices in this application starts with the collection and instruction analysis of multi-dimensional data. The system actively collects device status data information of each smart home subsystem, covering device status data sets (such as the switch and brightness status of smart lights, and the lock / unlock status of smart door locks), trigger condition data sets (such as trigger rules such as smart temperature and humidity sensors reaching preset thresholds and smart human sensors detecting human activities), linkage execution parameter sets (including parameters such as the execution duration and power limit of device linkage), and at the same time captures smart home scene commands issued by users through entry devices (such as "away mode" and "cinema mode"). After obtaining this information, the scene commands are deeply analyzed to accurately identify the target device type (clearly whether it is to control the lighting system, air conditioning system, or security system equipment) and cross-system linkage rules (determine the logical order of linkage between different system devices, such as "when turning on the cinema mode, turn off the living room lights first, then start the audio and video equipment, and finally adjust the air conditioner to a suitable temperature"), laying a solid foundation for subsequent linkage operations.

[0073] Priority grading analysis is performed based on the cross-system linkage rules obtained through analysis. Considering factors such as the urgency of linkage tasks (e.g., fire alarm linkage is a high priority, while daily scenarios are switched to regular priority), user demand weight (the "sleep mode" frequently used by users is prioritized to ensure smooth execution), and other factors, linkage tasks are broken down into layers to form a clear linkage task result set, clarifying the execution order and correlation of tasks at each level. Subsequently, based on the communication protocol corresponding to the target device type (different devices may use Wi-Fi, Bluetooth, Zigbee, and other protocols), combined with cross-system linkage rules, communication adaptation processing is performed on tasks at each level in the linkage task result set. The communication parameters are debugged in a unified data interaction format, and tasks are converted into instructions that can be recognized and executed by devices of different systems, generating a set of linkage tasks to be executed, and breaking the linkage barriers caused by differences in protocols between devices.

[0074] Key trigger nodes are extracted from the linkage task result set. These nodes serve as the core "switches" of the linkage process. For example, "successful unlocking of the smart door lock" can serve as the key trigger point for the "home mode" linkage. System linkage trigger conditions are set based on these key trigger nodes. These conditions are combined with the trigger condition dataset, linkage execution parameter set, device status dataset, and inter-system data interaction characteristics (e.g., data transmission latency and synchronization). These conditions are then processed and calculated to construct a pending timing evaluation set. This is used to assess the rationality of the linkage task execution's timing logic, such as whether the various device actions flow smoothly along the timeline and whether there are any delay conflicts. Simultaneously, using linkage execution records of key trigger nodes, the device linkage behavior trajectories are analyzed to assess the coherence and synchronization of device actions across the various systems, generating a third interaction performance dataset. Combined with the trigger condition dataset, the reliability of the cross-system linkage task execution under different environments and device states is evaluated (e.g., whether the linkage is fault-tolerant in the event of a device failure and whether the backup plan is effective), generating a pending reliability evaluation result set.

[0075] Integrate the set of pending linkage tasks, the set of pending timing assessments, and the set of pending reliability assessment results to conduct comprehensive linkage strategy optimization. Adjust the order of task execution from the timing dimension to avoid time conflicts and optimize resource allocation (e.g., rationally allocate network bandwidth to linkage devices during peak hours); from the reliability dimension, strengthen fault redundancy design and supplement backup linkage paths. Through the collaborative optimization of multi-dimensional assessment results, a cross-system linkage execution plan is generated to guide smart home entry-level devices in accurately scheduling various system devices, achieving stable, efficient, and user-friendly cross-system linkage, allowing users to enjoy a smooth and intelligent home scene experience.

[0076] According to the communication protocol of the target device type and the cross-system linkage rules, communication adaptation processing is performed on the tasks at each level in the linkage task result set to obtain the linkage task set to be executed, which specifically includes the following steps:

[0077] Identifying the communication protocol of the target device type to obtain a protocol identification result;

[0078] According to the protocol identification results and the cross-system linkage rules, communication adaptation processing is performed on the tasks at each level in the linkage task result set to obtain the linkage task set to be executed.

[0079] In the cross-system linkage process for smart home entry-level devices, the process of "adapting the communication protocols of each level of the linkage task result set to generate a set of pending linkage tasks based on the target device type's communication protocol and cross-system linkage rules" begins with accurate identification of the communication protocol corresponding to the target device type. Different smart home devices (e.g., smart lighting may use the Zigbee protocol, while smart door locks often use the Bluetooth protocol) utilize different communication protocols. Protocol identification is performed by collecting information such as the device's communication characteristics and protocol identifiers, and the resulting results are generated. Based on this protocol identification and combined with cross-system linkage rules (such as the sequencing logic and data exchange specifications for linkage between devices in different systems), the tasks at each level of the linkage task result set are adapted at the communication level. By adjusting the task's communication parameters and converting the data format, tasks that might otherwise be incompatible due to protocol differences can now be smoothly transmitted and correctly executed across devices in different systems, ultimately forming a set of pending linkage tasks. This builds a solid foundation for communication adaptation and ensures that linkage commands can be effectively transmitted and executed across devices across different protocols, transcending protocol barriers.

[0080] The system linkage trigger conditions, trigger condition data set, linkage execution parameter set, device status data set and data between each system are processed to obtain the time series evaluation set to be processed, specifically:

[0081] The first interactive performance data set is obtained based on the matching degree of the system linkage trigger conditions and the device status data set, as well as the data interaction delay results between the systems; the second interactive performance data set is obtained based on the matching degree of the linkage trigger conditions and the device status data set, as well as the data synchronization deviation results between the systems. The execution timing of the cross-system linkage task is evaluated based on the first interactive performance data set, the second interactive performance data set, the device status data set and the linkage execution parameter set to obtain the timing evaluation set to be processed.

[0082] This application has a detailed and critical working logic for the link of "processing the system linkage trigger conditions, trigger condition data sets, linkage execution parameter sets, device status data sets and data conditions between systems to obtain a time series evaluation set to be processed" in the cross-system linkage process of smart home entry-level devices. First, the system must obtain multiple types of core data, including linkage trigger conditions pre-set by the system (such as "start the air conditioner and close the windows when the ambient temperature reaches 30°C"), trigger condition data sets covering various trigger rules of the equipment (such as detailed rules for triggering linkage under what status and parameters of different devices), linkage execution parameter sets that clearly define how the linkage is executed (such as the duration of the linkage execution, power limit, etc.), device status data sets that reflect the current operating status of the device (for example, the smart light is on and the brightness is 50%, the smart door lock is in a locked state, etc.), and data such as interaction delays and synchronization deviations during data transmission between systems.

[0083] Based on this data, a two-step critical analysis was conducted. The first step calculated the degree of match between the system linkage trigger conditions and the device status dataset, specifically to determine whether the current device status met the linkage trigger requirements. This was combined with the data interaction delay results between the systems (e.g., the number of milliseconds of data transmission delay between the air conditioning system and the door and window system). These two data sets were then integrated to construct the first interaction performance dataset, which primarily reflects the impact of data interaction delays on linkage execution performance. The second step also involved calculating the degree of match between the linkage trigger conditions and the device status dataset. This was then combined with the data synchronization deviation results between the systems (e.g., data deviations caused by clock synchronization errors between devices in different systems) to form the second interaction performance dataset, which focused on reflecting the interference of data synchronization issues on linkage.

[0084] Finally, the first and second interactive performance data sets are combined with the device status data set (to understand the actual state of the devices that can support linkage) and the linkage execution parameter set (to clarify the basic rules and restrictions for linkage execution) to conduct a comprehensive evaluation from the perspective of the execution timing of cross-system linkage tasks. This analysis examines the rationality of the sequence of device actions in the time dimension of linkage tasks, the smooth temporal connection between task executions across different systems, and whether delays and synchronization deviations disrupt the linkage rhythm. This multi-dimensional data fusion ultimately generates a pre-processed timing evaluation set, providing a basis for subsequent optimization of the timing logic of cross-system linkage and ensuring efficient and orderly linkage execution.

[0085] Identifying the communication protocol of the target device type to obtain a protocol identification result specifically includes the following steps:

[0086] Collect physical interface information and network connection parameters of the target device type;

[0087] The communication protocol of the device is identified based on the physical interface information and network connection parameters to obtain a protocol identification result.

[0088] The system must actively collect two types of core information about the target device type. The first is physical interface information. The physical interfaces of different smart home devices vary greatly. For example, a smart camera may have a USB interface, and a smart door lock may have a dedicated wireless communication interface. The shape, pin definition and other details of these physical interfaces contain the basic clues of device communication. The second is network connection parameters, which cover the device's IP address, port number, the protocol used in the network transport layer (such as TCP or UDP), the network frequency band (2.4G or 5G Wi-Fi, etc.), etc. They are the "digital coordinates" for devices to realize data interaction in a network environment.

[0089] After acquiring the physical interface information and network connection parameters, the system conducts identification based on a pre-set protocol recognition rule base. This rule base contains pre-stored physical interface characteristics and network connection parameter templates for various common communication protocols, such as Wi-Fi, Bluetooth, Zigbee, and Matter. The system then compares the collected target device information against the templates in the rule base. For example, if the physical interface is a short-range wireless interface that complies with the Bluetooth protocol specification, and the network connection parameters exhibit typical Bluetooth characteristics such as channel and frequency hopping, the system can determine that the device uses the Bluetooth communication protocol. If the physical interface is a small, low-power interface commonly used by Zigbee devices, and the network connection parameters align with the protocol's self-organizing network and low-speed data transmission characteristics, the system identifies the device as using the Zigbee protocol. This precise collection of key information and deep matching of protocol feature templates ultimately yields accurate protocol identification results, laying a solid foundation for subsequent inter-device communication adaptation and command exchange in cross-system linkage.

[0090] According to the protocol identification results and the cross-system linkage rules, communication adaptation processing is performed on the tasks at each level in the linkage task result set to obtain the linkage task set to be executed, which specifically includes the following steps:

[0091] Adjusting the communication parameters of the linkage task according to the protocol identification result and the priority level of the cross-system linkage rule to obtain a parameter adjustment result;

[0092] Obtain the execution node positions of tasks at each level in the linkage task result set, convert the communication protocols and process the data formats of tasks at each level in the linkage task result set according to the parameter adjustment results and the execution node positions, and then obtain a standardized task data set;

[0093] Verify the preconditions and postconditions of each task in the standardized task dataset to obtain a verification result set;

[0094] Obtain the execution dependency dataset of each level of tasks in the linkage task result set, pre-process and sort the tasks of each level in the linkage task result set according to the dependency dataset and the verification result set to obtain the linkage task set to be executed.

[0095] This application uses protocol identification results (identifying device communication protocol types, such as Bluetooth and Wi-Fi) and the priority levels of cross-system linkage rules (emergency tasks like fire alarm linkage have a higher priority, while daily scene switching has a relatively lower priority) to adjust the communication parameters of linkage tasks. For example, high-priority tasks are assigned more stable frequency bands and higher transmission rates to ensure rapid command transmission. The parameter adjustment results are used to determine the basic parameters for subsequent communication adaptation.

[0096] Obtain the execution node position of each task at each level in the linkage task result set (i.e., the order and stage of the tasks in the entire linkage process). Combined with the newly obtained parameter adjustment results, perform communication protocol conversion and data format processing on each level of tasks. Different system devices have different protocols, so task instructions must be converted into a protocol format that the corresponding device can recognize. At the same time, data encoding and message structure must be unified to form a standardized task data set.

[0097] Verify the preconditions (e.g., the state the device must meet before executing the task, such as "To execute the air conditioner power-on task, the precondition is that the air conditioner is in the power-on standby state") and postconditions (the state that should be achieved after the task is executed, such as "After turning on the air conditioner, the temperature must drop to the set value within 5 minutes") of each task in the standardized task dataset. Check whether the preconditions are met and the postconditions are reasonable to generate a verification result set, and filter out tasks that can be executed normally.

[0098] Obtain a dataset of execution dependencies for tasks at each level from the linkage task result set (clarifying which tasks precede and depend on each other, for example, the "Start Smart Curtain Closing Task" depends on the "Indoor Light Sensor Detects Excessive Light" task to execute first). Combined with the verification result set, pre-process and sort the tasks at each level. Prioritize tasks that meet dependency conditions and pass verification, adjust the execution order, and ultimately generate a set of pending linkage tasks. This ensures that cross-system linkage tasks can be accurately executed across different devices according to a reasonable and orderly logic.

[0099] Extracting key trigger nodes from the linkage task result set includes the following steps:

[0100] Extract the trigger event data information of the priority task from the verification result set;

[0101] The key trigger nodes are extracted from the linkage task result set based on the trigger event data information and the execution node positions of tasks at each level.

[0102] In this application, the "Extracting Key Trigger Nodes from the Linkage Task Result Set" step within the cross-system linkage process for entry-level smart home devices begins by focusing on the verification result set, which records the status of each task after verification. The application then filters out the trigger event data for priority tasks (such as the fire alarm linkage task related to safety and the core "Away Mode" task, which are frequently used by users and play a key role in driving the linkage process). This identifies the triggering conditions for these high-priority tasks (for example, a fire alarm task is triggered by the smoke sensor detecting excessive smoke concentration, and an "Away Mode" task is triggered by the door lock detecting a locking action). Next, the application combines the execution node positions of tasks at each level (that is, the order and stage of each task in the entire linkage task sequence, determining which tasks execute first and which ones execute later, and their interconnectedness). Using the trigger event data as a clue, the application locates the key trigger nodes within the linkage task result set. The application then identifies the key stages within the execution node positions of the tasks corresponding to the trigger events, which can trigger the subsequent linkage tasks, thereby accurately extracting the key trigger nodes. These key trigger nodes are like the "engine" of the linkage process, which determines when and in what order the cross-system linkage tasks are started, ensuring that the smart home triggers the linkage of various system devices in an orderly manner according to user needs or environmental changes in appropriate scenarios, making the entire cross-system linkage logic clearer and more efficient.

[0103] Also includes:

[0104] Based on the time trigger condition of the key trigger node, the scheduled task cycle and execution time window of each system device are marked as a first trigger condition set, and the real-time time synchronization status of the device and the task execution history data are collected to obtain a first device status data set;

[0105] Based on the state trigger conditions of the key trigger nodes, the operating state thresholds and state change rules of each system device are marked as a second trigger condition set, and the current operating parameters and state feedback signals of the devices are collected to obtain a second device state data set;

[0106] Based on the combined trigger conditions of key trigger nodes, the multi-system device status combination logic and linkage response rules are marked as a third trigger condition set, and cross-system data interaction logs and linkage execution records are collected to obtain a third device status data set;

[0107] The first trigger condition set, the second trigger condition set and the third trigger condition set are combined into a trigger condition data set; the first device status data set, the second device status data set and the third device status data set are combined into a device status data set.

[0108] Many smart home linkages are executed on a set schedule, such as "automatically opening the curtains and starting the coffee machine at 7 a.m." To determine the time trigger conditions for key trigger nodes, the system first identifies the key node for time-driven linkages (for example, the trigger point for a "7 a.m. wake-up scenario" is "7:00"). It then marks the scheduled task cycles (daily, weekdays, or the first day of each month) and execution window (7:00-7:05 a.m. to avoid conflicts with other tasks) for each system device as the first trigger condition set.

[0109] The system collects two types of data: the device's real-time time synchronization status (for example, whether the smart curtain's clock is synchronized with the home's central control server or the NTP network time); and historical task execution data (the curtain's 7:00 execution success rate, delay duration, and any failures due to network issues over the past seven days). This data is integrated to generate the first device status dataset.

[0110] Another type of linkage is "executed only when the device state changes," for example, "when the temperature and humidity sensor detects humidity > 80%, start the dehumidifier and close the windows." In this case, the state triggering condition of the key trigger node is the "sensor" of this "state linkage":

[0111] The system first identifies the key nodes for state-driven linkage (for example, the trigger for "dehumidification when humidity exceeds the standard" is "humidity > 80%)). It then identifies the operating status thresholds of each system device (80% humidity is the threshold, 30°C temperature is the air conditioning activation threshold) and state change rules (whether a humidity increase from 75% to 80% triggers the system, and the rule for a 5°C temperature drop) as the second trigger condition set. This step is equivalent to setting the "trigger threshold" for state linkage—the conditions and changes in the device status that trigger the linkage.

[0112] The system collects two types of data: the current operating parameters of the device (real-time humidity values ​​measured by the temperature and humidity sensors, the dehumidifier's current power and dehumidification capacity); and status feedback signals (whether the window motor has responded "off" and whether the dehumidifier has reported any errors). These data are integrated to generate a second device status dataset.

[0113] Execution requires "multiple device states to be met simultaneously", for example, "when the door lock is unlocked and the light sensor detects that it is dark, the living room lights will be automatically turned on and the security arm will be turned off". In this case, the combined trigger conditions of the key trigger node are:

[0114] The system first finds the key nodes of the "combination-driven linkage" (for example, the trigger point of the "return home scene" is "door lock unlocked and dark"), and then marks the multi-system device status combination logic (must the door lock be unlocked and the light be dim at the same time; or can only one of them be met) and the linkage response rules (turn on the light first or disarm first, and are there any requirements for the execution order) as the third trigger condition set.

[0115] The system collects two types of data: first, cross-system data interaction logs (e.g., whether packets are lost when the door lock sends the "unlocked" command to the central control system, and whether data from the light sensor reaches the central control system); and second, linkage execution records (e.g., how long it took to execute the "return home scenario," whether the device response sequence was correct, and whether the "lights on but security not disarmed" bug occurred). These data are integrated to generate a third device status dataset.

[0116] Finally, the first trigger condition set, the second trigger condition set, and the third trigger condition set are integrated together to form a trigger condition data set - this is like building a "condition engine" for the cross-system linkage of the smart home. Whether it is timed linkage, status linkage, or complex combination linkage, you have to find the "execution rules" here; the first device status data set, the second device status data set, and the third device status data set are integrated together to form a device status data set - this is like building a "status dashboard" for the linkage, reflecting in real time whether the device can execute the linkage and whether it is stable when executing the linkage.

[0117] When a cross-system scenario (such as "Go Home Mode") is triggered, the system first searches the trigger condition dataset for rules: whether it's a time trigger (is it time to leave work?), a state trigger (is the door unlocked?), or a combination trigger (is the door unlocked + the phone located at home?). It then checks the device status dataset for status information: Is the device clock synchronized? Do the current parameters meet the conditions? Is cross-system communication functioning properly? Finally, based on the results of "rule matching + state verification," it precisely drives multi-system device linkage—a complete closed loop from "defining conditions" to "executing linkage."

[0118] A first interactive performance dataset is obtained based on the matching degree between the system linkage trigger condition and the device status dataset and the data interaction delay results between the systems; a second interactive performance dataset is obtained based on the matching degree between the linkage trigger condition and the device status dataset and the data synchronization deviation results between the systems; and an execution timing of the cross-system linkage task is evaluated based on the first interactive performance dataset, the second interactive performance dataset, the device status dataset, and the linkage execution parameter set to obtain a timing evaluation set to be processed, specifically including the following steps:

[0119] Counting the matching degree between the system linkage triggering condition and each device status in the device status data set to obtain a third matching degree data set;

[0120] Predicting the delay time of the data interaction path based on the third matching degree dataset and the multi-system network topology to obtain a first interaction performance dataset;

[0121] The second interactive performance dataset is obtained by predicting the deviation range of multi-system data synchronization based on the matching degree dataset and the cross-system clock synchronization error;

[0122] Evaluate the trigger response time and execution order of the linkage tasks according to the first interactive performance data set and the device status data set to obtain a first to-be-processed timing evaluation result set;

[0123] Evaluating the timing consistency and fault tolerance of the multi-system linkage according to the second interactive performance data set and the linkage execution parameter set to obtain a second to-be-processed timing evaluation result set;

[0124] The first to-be-processed timing evaluation result set and the second to-be-processed timing evaluation result set are combined into a to-be-processed timing evaluation set.

[0125] This application calculates the matching degree between the system linkage trigger conditions and the device status in the device status dataset to generate a third matching degree dataset. This step is like a "preliminary physical examination" of the linkage task, to determine the consistency between the trigger conditions and the actual device status. For example, to execute the "sleep mode" linkage, we must first check whether the trigger conditions such as "lights off condition" and "curtains closed state" match the actual status of the smart lights and smart curtains. The matching degree data can reflect the rationality of the linkage basic conditions.

[0126] Based on the third matching data set and the multi-system network topology, the delay time of the data interaction path is predicted to obtain the first interactive performance data set. The network topology is like a "connection map" of smart home devices, marking how devices communicate and which paths they take. Combined with the matching data, it can be inferred how much delay will be generated when data is transmitted between devices due to factors such as network paths and device loads. For example, the wireless network path that a smart door lock takes to send an unlock signal to the smart hub will have different delay times under different device status matching degrees. The first interactive performance data set records these delays to evaluate the speed of linkage command transmission.

[0127] The second interactive performance dataset is formed by predicting the deviation range of multi-system data synchronization based on the matching dataset and cross-system clock synchronization error. The clocks of different system devices in a smart home may vary slightly, such as in smart speakers and smart air conditioners. If the clocks are not precisely synchronized, data synchronization will deviate when executing coordinated tasks. The approximate range of this deviation can be calculated by combining the device status matching. The second interactive performance dataset quantifies this deviation to assist in determining the accuracy of data coordination when multi-systems are linked.

[0128] The first interactive performance dataset and device status dataset are used to evaluate the trigger response time and execution order of the linkage task, resulting in the first pending timing evaluation result set. Knowing the data interaction delay, combined with the actual device status (such as whether the device is online or busy), allows us to determine how long it takes for the device to respond after the linkage task is triggered and whether the execution order of each device's actions is reasonable. For example, in "home mode," after unlocking the smart door lock, is the response time of smart lights, air conditioners, and other devices within an acceptable range? Is turning on the lights or air conditioner first a more appropriate execution order? The first pending timing evaluation result set provides these evaluation conclusions, optimizing the linkage time flow.

[0129] The second set of pending timing evaluation results is generated by evaluating the timing consistency and fault tolerance of multi-system linkage based on the second interactive performance data set and linkage execution parameter set. The linkage execution parameter set specifies the execution criteria for linkage tasks, such as execution duration and number of retries. Combined with data synchronization deviations, this allows us to determine whether the timing of device actions during multi-system linkage is consistent (timing consistency) and whether the linkage can automatically adjust to data deviations or temporary device failures (fault tolerance). For example, whether the linkage between the smart lighting system and the smart curtain system can still coordinate smoothly despite clock synchronization deviations, and whether the linkage will fail due to network fluctuations. The second set of pending timing evaluation results provides a score and assessment of these capabilities.

[0130] The first and second pending timing evaluation result sets are combined to form the pending timing evaluation set. This evaluation set comprehensively covers the performance of cross-system linkage tasks in terms of trigger response, execution sequence, timing consistency, fault tolerance, and other temporal dimensions. This provides a detailed and valuable basis for timing analysis to optimize linkage strategies and ensure efficient and coordinated operation of smart home devices. This ensures that cross-system linkage is not only executable but also precise, stable, and reliable in terms of temporal logic.

[0131] The device linkage behavior trajectory set is obtained based on the linkage execution records of the key trigger nodes, the actions of each system device in the device linkage behavior trajectory set are analyzed to obtain a third interaction performance dataset, and the execution of the cross-system linkage task is evaluated based on the third interaction performance dataset and the trigger condition dataset to obtain a reliability evaluation result set to be executed. Specifically, the following steps are included:

[0132] According to the linkage execution records of key trigger nodes, the linkage execution timestamps and action sequence data of each system device are collected to generate a device linkage behavior trajectory set;

[0133] Obtaining the device action record corresponding to the first trigger condition set during the linkage execution process to obtain a first behavior trajectory subset;

[0134] Acquire the device action record corresponding to the second trigger condition set during the linkage execution process to obtain a second behavior trajectory subset;

[0135] Calculate the action timing deviation of the first behavior trajectory subset and the second behavior trajectory subset to output a deviation data set;

[0136] The consistency and synchronization of the actions of the devices in each system are judged based on the deviation dataset and the third matching dataset to obtain a third interactive performance dataset;

[0137] Based on the third interactive performance data set and the trigger condition data set, the execution reliability of the cross-system linkage task under abnormal conditions is evaluated to obtain a reliability evaluation result set to be executed.

[0138] When smart home devices interact across systems, their actions are dynamic and complex (for example, in "Home Mode," the door locks, lights, air conditioners, and curtains all activate sequentially or simultaneously). To accurately analyze these action scenarios, the first step is to collect "linkage execution timestamps + action sequence data." The timestamp records the precise time of each device action (for example, door lock unlocks at 18:00:00, lights turn on at 18:00:01), while the action sequence records the sequence and execution content of the device actions (for example, "door lock unlocks → lights turn on → air conditioner starts"). These two types of data are combined to generate a set of device linkage behavior trajectories.

[0139] Smart home interactions are often driven by multiple conditions, including time triggers and state triggers (for example, "away mode" may include both a timer trigger and a door lock close trigger). To accurately analyze device actions under different trigger conditions, the solution needs to separate the behavior trajectory into two subsets:

[0140] The first behavior trajectory subset focuses on the device actions corresponding to the "time trigger condition" (the first trigger condition set). For example, if you want to automatically open the curtains at 7:00 AM, the system will extract the actions triggered by "timed 7:00 AM" (curtain motor rotation and associated smart light brightness adjustment) from the entire linkage trajectory to form the first behavior trajectory subset.

[0141] The second behavior trajectory subset focuses on device actions corresponding to the "state trigger condition" (the second trigger condition set). For example, if "humidity > 80% activates the dehumidifier," the system will extract the actions triggered by "humidity exceeding the standard" (dehumidifier activation, window closing) from the entire linkage trajectory to form the second behavior trajectory subset.

[0142] In theory, device actions driven by different trigger conditions should be coordinated (for example, turning on the lights on a timer and opening the curtains triggered by a status condition should occur simultaneously). However, in practice, device hardware latency and network fluctuations can cause timing deviations (for example, the curtains may move before the lights turn on, resulting in a 2-second delay).

[0143] The time coordinates of the two subsets are aligned (for example, starting the timing from the moment the trigger condition is met). The execution times of the device actions are then compared frame by frame to determine which is faster, which is slower, and by how much. This outputs a deviation dataset. This step is equivalent to "time calibration" of the linkage process, quantifying the time differences between device actions and identifying problems with coordinated execution.

[0144] The action timing deviation is combined with the "device state matching" (the third matching data set) to determine the consistency and synchronization of device actions. Consistency refers to whether the device actions driven by different trigger conditions comply with the preset logic (for example, whether "turning on the lights on time" and "opening the curtains triggered by status" must be executed in "Away Mode"). Synchronicity refers to whether the action timing deviation is within an acceptable range (for example, whether a 2-second delay affects the user experience, and whether a 10-second delay will cause the linkage to fail).

[0145] Based on the "deviation dataset + third matching dataset", the system scores the collaborative performance of device actions and generates a third interactive performance dataset.

[0146] Smart home linkage cannot only be considered in "normal conditions" but also in "abnormal conditions" (such as temporary device offline and sudden network interruption). The reliability of cross-system linkage execution is evaluated by combining the third interactive performance dataset and the trigger condition dataset:

[0147] First, simulate an "abnormal scenario" (for example, deliberately disconnecting a device from the network or modifying the trigger condition threshold) and then check whether the device action can still be executed (for example, whether the local linkage logic is effective after the network is disconnected) and whether the timing deviation is out of control (for example, if the delay increases from 2 seconds to 20 seconds, whether the linkage collapses).

[0148] Based on these performance indicators, the linkage tasks are scored for their resilience to risk, generating a set of reliability assessment results to be executed. This step is equivalent to a "stress test" of the linkage process, ensuring that the smart home can continue to operate stably even in the event of an emergency.

[0149] After comprehensive linkage strategy optimization of the set of linkage tasks to be executed, the set of time series evaluations to be processed, and the set of reliability evaluation results to be executed, a cross-system linkage execution plan is obtained. Specifically, the following steps are included:

[0150] Performing timing conflict detection on the linkage task set to be executed and the first timing evaluation result set to be processed to obtain a first optimization difference result set;

[0151] Performing timing redundancy judgment on the linkage task set to be executed and the second timing evaluation result set to be processed to obtain a second optimization difference result set;

[0152] Perform reliability verification on the linkage task set to be executed and the reliability evaluation result set to be executed to obtain a third optimized difference result set;

[0153] Performing weight distribution processing on the first optimization difference result set, the second optimization difference result set, and the third optimization difference result set to obtain an optimization weight result set;

[0154] Based on the optimization weight result set, the execution order and resource allocation of the linkage task set to be executed are optimized to obtain the linkage strategy optimization result set;

[0155] After performing integrated execution plan generation processing on the cross-system linkage tasks in the linkage strategy optimization result set, a cross-system linkage execution plan is obtained.

[0156] In the cross-system linkage of the smart home in this application, the task execution sequence is prone to problems. The solution first performs two types of basic tests. The timing conflict detection compares the set of linkage tasks to be executed (clarifying "what each task does") with the first set of timing evaluation results to be processed (analyzing "when to do the tasks and whether the order is reasonable"). For example, the "turn on the air conditioner task" requires immediate execution, and the "start the air purifier task" also occupies resources in the same time period. Through detection, the conflict of "multiple tasks grabbing resources at the same time" can be found to generate the first optimized difference result set and mark the conflict point. The timing redundancy judgment matches the set of linkage tasks to be executed with the second set of timing evaluation results to be processed (evaluating "whether the tasks are repeated and whether the processes are redundant"). For example, for the task of "adjusting the brightness of the living room lights", if there is already a "scene mode-cinema mode" that includes dimming, executing it alone may generate a second optimized difference result set after redundancy detection to find the redundant tasks.

[0157] Cross-system linkage requires more than just timing; it also ensures execution under abnormal conditions. The solution combines the set of pending linkage tasks with the set of pending reliability assessment results (recording the tasks' "abnormal risk tolerance") to perform reliability verification. This simulates abnormalities such as device offline and network fluctuations to determine whether the tasks can be executed. For example, if the "smart door lock linked light on" task fails to trigger the light on after the door lock loses network connectivity, this is flagged as a reliability issue, generating a third-order optimization difference result set.

[0158] The three types of optimization difference result sets (conflict, redundancy, and reliability) reflect issues of different dimensions and require differentiated processing priorities. Reliability issues that impact safety (such as fire alarm linkage failure) are given higher weights, while common timing redundancies (such as repeated dimming) are given lower weights. By assigning weights based on task importance and user needs, we generate an optimization weighted result set to guide subsequent optimization.

[0159] With the optimized weighted result set, we can tailor the set of pending linkage tasks to the target. We optimize the execution order based on the weights, prioritizing high-priority, conflict-free tasks. For example, fire alarm linkage tasks can be prioritized. Resource allocation optimization allocates more network and computing resources to critical tasks, such as video surveillance linkage tasks, ensuring bandwidth and preventing lag. This generates a linkage strategy optimization result set for more efficient task execution.

[0160] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one location or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of the present embodiment. Persons of ordinary skill in the art will be able to understand and implement the present invention without inventive effort.

[0161] Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented using software plus a necessary general-purpose hardware platform, or of course, hardware. Based on this understanding, the essence of the above technical solution, or the portion that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a magnetic disk, or an optical disk, and includes a number of instructions for causing a computer device (such as a personal computer, server, or network device) to execute the methods described in each embodiment or certain portions of the embodiments.

[0162] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A cross-system linkage method for smart home entry-level devices, characterized in that: The method comprises the following steps: Collecting device status data information of each system and scene instructions of smart home; wherein, the device status data information includes a device status data set, a trigger condition data set and a linkage execution parameter set; Parse smart home scene commands to obtain target device types and cross-system linkage rules; Perform priority classification analysis on cross-system linkage rules to decompose linkage tasks into hierarchical levels to obtain linkage task result sets; According to the communication protocol of the target device type and the cross-system linkage rules, communication adaptation processing is performed on the tasks at each level in the linkage task result set to obtain the linkage task set to be executed; Extract key trigger nodes from the linkage task result set; Set the system linkage trigger conditions according to the key trigger nodes, and process the system linkage trigger conditions, trigger condition data set, linkage execution parameter set, device status data set and data between each system to obtain the time series evaluation set to be processed; A device linkage behavior trajectory set is obtained based on the linkage execution records of the key trigger nodes, the actions of each system device in the device linkage behavior trajectory set are analyzed to obtain a third interaction performance dataset, and the execution of the cross-system linkage task is evaluated based on the third interaction performance dataset and the trigger condition dataset to obtain a reliability evaluation result set to be executed; After comprehensive linkage strategy optimization of the linkage task set to be executed, the timing evaluation set to be processed and the reliability evaluation result set to be executed, a cross-system linkage execution plan is obtained.

2. The cross-system linkage method of smart home entry-level devices according to claim 1 is characterized in that: According to the communication protocol of the target device type and the cross-system linkage rules, communication adaptation processing is performed on the tasks at each level in the linkage task result set to obtain the linkage task set to be executed, which specifically includes the following steps: Identify the communication protocol of the target device type to obtain a protocol identification result; According to the protocol identification results and the cross-system linkage rules, communication adaptation processing is performed on the tasks at each level in the linkage task result set to obtain the linkage task set to be executed.

3. The cross-system linkage method of smart home entry-level devices according to claim 2 is characterized in that: The system linkage trigger conditions, trigger condition data set, linkage execution parameter set, device status data set and data between each system are processed to obtain the time series evaluation set to be processed, specifically: The first interactive performance data set is obtained based on the matching degree of the system linkage trigger conditions and the device status data set, as well as the data interaction delay results between the systems; the second interactive performance data set is obtained based on the matching degree of the linkage trigger conditions and the device status data set, as well as the data synchronization deviation results between the systems. The execution timing of the cross-system linkage task is evaluated based on the first interactive performance data set, the second interactive performance data set, the device status data set and the linkage execution parameter set to obtain the timing evaluation set to be processed.

4. The cross-system linkage method of smart home entry-level devices according to claim 2, characterized in that: Identifying the communication protocol of the target device type to obtain a protocol identification result specifically includes the following steps: Collect physical interface information and network connection parameters of the target device type; The communication protocol of the device is identified based on the physical interface information and network connection parameters to obtain a protocol identification result.

5. The cross-system linkage method of smart home entry-level devices according to claim 2, characterized in that: According to the protocol identification results and the cross-system linkage rules, communication adaptation processing is performed on the tasks at each level in the linkage task result set to obtain the linkage task set to be executed, which specifically includes the following steps: Adjusting the communication parameters of the linkage task according to the protocol identification result and the priority level of the cross-system linkage rule to obtain a parameter adjustment result; Obtain the execution node positions of tasks at each level in the linkage task result set, convert the communication protocols and process the data formats of tasks at each level in the linkage task result set according to the parameter adjustment results and the execution node positions, and then obtain a standardized task data set; Verify the preconditions and postconditions of each task in the standardized task dataset to obtain a verification result set; Obtain the execution dependency dataset of each level of tasks in the linkage task result set, pre-process and sort the tasks of each level in the linkage task result set according to the dependency dataset and the verification result set to obtain the linkage task set to be executed.

6. The cross-system linkage method of smart home entry-level devices according to claim 5, characterized in that: Extracting key trigger nodes from the linkage task result set includes the following steps: Extract the trigger event data information of the priority task from the verification result set; The key trigger nodes are extracted from the linkage task result set based on the trigger event data information and the execution node positions of tasks at each level.

7. The cross-system linkage method of smart home entry-level devices according to claim 6, characterized in that: Also includes: Based on the time trigger condition of the key trigger node, the scheduled task cycle and execution time window of each system device are marked as a first trigger condition set, and the real-time time synchronization status of the device and the task execution history data are collected to obtain a first device status data set; Based on the state trigger conditions of the key trigger nodes, the operating state thresholds and state change rules of each system device are marked as a second trigger condition set, and the current operating parameters and state feedback signals of the devices are collected to obtain a second device state data set; Based on the combined trigger conditions of key trigger nodes, the multi-system device status combination logic and linkage response rules are marked as a third trigger condition set, and cross-system data interaction logs and linkage execution records are collected to obtain a third device status data set; Wherein, the first trigger condition set, the second trigger condition set and the third trigger condition set are combined into a trigger condition data set; The first device status data set, the second device status data set, and the third device status data set are combined into a device status data set.

8. The cross-system linkage method of smart home entry-level devices according to claim 7, characterized in that: A first interactive performance dataset is obtained based on the matching degree between the system linkage trigger condition and the device status dataset and the data interaction delay results between the systems; a second interactive performance dataset is obtained based on the matching degree between the linkage trigger condition and the device status dataset and the data synchronization deviation results between the systems; and an execution timing of the cross-system linkage task is evaluated based on the first interactive performance dataset, the second interactive performance dataset, the device status dataset, and the linkage execution parameter set to obtain a timing evaluation set to be processed, specifically including the following steps: Counting the matching degree between the system linkage triggering condition and each device status in the device status data set to obtain a third matching degree data set; Predicting the delay time of the data interaction path based on the third matching degree dataset and the multi-system network topology to obtain a first interaction performance dataset; The second interactive performance dataset is obtained by predicting the deviation range of multi-system data synchronization based on the matching degree dataset and the cross-system clock synchronization error; Evaluate the trigger response time and execution order of the linkage tasks according to the first interactive performance data set and the device status data set to obtain a first to-be-processed timing evaluation result set; Evaluating the timing consistency and fault tolerance of the multi-system linkage according to the second interactive performance data set and the linkage execution parameter set to obtain a second to-be-processed timing evaluation result set; The first to-be-processed timing evaluation result set and the second to-be-processed timing evaluation result set are combined into a to-be-processed timing evaluation set.

9. The cross-system linkage method of smart home entry-level devices according to claim 8, characterized in that: The method includes the following steps: obtaining a device linkage behavior trajectory set based on linkage execution records of key trigger nodes, analyzing the actions of each system device in the device linkage behavior trajectory set to obtain a third interaction performance dataset, and evaluating the execution of the cross-system linkage task based on the third interaction performance dataset and the trigger condition dataset to obtain a reliability evaluation result set to be executed: According to the linkage execution records of key trigger nodes, the linkage execution timestamps and action sequence data of each system device are collected to generate a device linkage behavior trajectory set; Obtaining the device action record corresponding to the first trigger condition set during the linkage execution process to obtain a first behavior trajectory subset; Acquire the device action record corresponding to the second trigger condition set during the linkage execution process to obtain a second behavior trajectory subset; Calculate the action timing deviation of the first behavior trajectory subset and the second behavior trajectory subset to output a deviation data set; The consistency and synchronization of the actions of the devices in each system are judged based on the deviation dataset and the third matching dataset to obtain a third interactive performance dataset; Based on the third interactive performance data set and the trigger condition data set, the execution reliability of the cross-system linkage task under abnormal conditions is evaluated to obtain a reliability evaluation result set to be executed.

10. The cross-system linkage method of smart home entry-level devices according to claim 9, characterized in that: After comprehensive linkage strategy optimization of the set of linkage tasks to be executed, the set of time series evaluations to be processed, and the set of reliability evaluation results to be executed, a cross-system linkage execution plan is obtained. Specifically, the following steps are included: Performing timing conflict detection on the linkage task set to be executed and the first timing evaluation result set to be processed to obtain a first optimization difference result set; Performing timing redundancy judgment on the linkage task set to be executed and the second timing evaluation result set to be processed to obtain a second optimization difference result set; Perform reliability verification on the linkage task set to be executed and the reliability evaluation result set to be executed to obtain a third optimized difference result set; Performing weight distribution processing on the first optimization difference result set, the second optimization difference result set, and the third optimization difference result set to obtain an optimization weight result set; Based on the optimization weight result set, the execution order and resource allocation of the linkage task set to be executed are optimized to obtain the linkage strategy optimization result set; After performing integrated execution plan generation processing on the cross-system linkage tasks in the linkage strategy optimization result set, a cross-system linkage execution plan is obtained.

Images