Device access state management method and apparatus, device, and medium

Abstract

This invention relates to the field of smart homes, providing a method, apparatus, device, and medium for managing device access status. The method includes: receiving device information reported by smart home devices; searching and retrieving a target domain model file matching the device type from a locally stored domain model file library based on the device type in the device information, and parsing it; the domain model file is configured based on attribute rules for the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each functional item of the corresponding device type under different operating modes; using the attribute rules of each functional item obtained from the parsing, calibrating the corresponding functional items of the device information, and synchronizing the calibrated device information to the user interface. This invention solves the defect that the cloud is limited by devices or offline interruptions, making it impossible to achieve unified management of mutual exclusion logic for different models of devices, realizing localized deployment and real-time invocation of device control logic, and ensuring system availability in weak network or no network environments.

Description

Technical Field

[0001] This invention relates to the field of smart home technology, and in particular to a method, apparatus, device, and medium for managing device access status. Background Technology

[0002] With the significant improvement in living standards and the rapid development of home appliance networking technology, smart homes are gradually entering the public eye. Users' demands for home appliances have expanded from simply meeting basic functions to a higher pursuit of resource utilization efficiency, ease of operation, and personalized experiences. Against this backdrop, localized control terminals such as wired controllers and wired control panels play an indispensable role in the smart home ecosystem due to their intuitive and convenient operation. Whether it's a dedicated wired controller for a single appliance like an air conditioner or refrigerator, or a centralized controller for managing all appliances in the house, they greatly enhance the user's control experience over the home appliance system.

[0003] Currently, common device access management mainly utilizes wired controllers or central controllers to establish a connection with a cloud server via the Internet. The cloud server collects and analyzes the operating data of each device or system, and determines the control actions of the device or system based on the set control algorithms and strategies combined with the mutual exclusion logic constraints of the device or system, thereby realizing remote control and status monitoring of home appliances.

[0004] However, this control model, which heavily relies on cloud services, has significant limitations. When a device or control terminal is offline, the cloud server cannot receive device status information or issue control commands, causing the mutual exclusion logic verification function based on the cloud domain model to completely fail. In this case, if the user operates the device offline, the mutual exclusion logic of different device models cannot be uniformly processed and constrained, which may lead to device operating status conflicts, increased energy consumption, or even device damage. This strong dependence on network connectivity seriously affects the reliability of the control system and the continuity of the user experience. Summary of the Invention

[0005] This invention provides a device access status management method, apparatus, device, and medium to address the shortcomings of existing technologies where cloud-based systems are limited by devices or offline interruptions, making it impossible to achieve unified management of mutual exclusion logic for different device models. This invention enables localized deployment and real-time invocation of device control logic, ensuring system availability in weak or no-network environments.

[0006] This invention provides a device access status management method, comprising: receiving device information reported by smart home devices; searching and obtaining a target domain model file matching the device type from a locally stored domain model file library according to the device type in the device information; the domain model file is configured based on attribute rules of the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each functional item of the corresponding device type under different operating modes; parsing the target domain model file, using the attribute rules of each functional item obtained from the parsing to calibrate the corresponding functional items of the device information, and synchronizing the calibrated device information to the user interface.

[0007] It should be noted that by receiving device information proactively reported by smart home devices, the system can perceive device status in real time, overcoming the status update delay caused by relying on cloud polling. It also searches for matching domain model files in the local library based on device type to avoid device function cross-validation failures caused by offline access to the cloud rule base. This enables localized deployment and instant invocation of device control logic, ensuring system availability in weak or no-network environments. Furthermore, by generating attribute rules based on mutual exclusion logic, it improves the compatibility and management uniformity of different device models. Moreover, by parsing domain model files and using attribute rules to calibrate device function items, it overcomes data parsing errors and operational conflicts caused by differences in device function definitions. This achieves standardized processing and status compliance checks of multi-source heterogeneous device data, improving the accuracy of information seen by users when synchronizing calibrated information to the interface, and preventing device anomalies and user experience degradation due to status conflicts or illegal values.

[0008] According to a device access status management method provided by the present invention, the device information includes device type, device operating mode, and the current value of at least one device function item; the attribute rules include the writability status and value range of each function item; and the method calibrates the corresponding function items in the device information using the attribute rules of each function item obtained through parsing, including: when it is determined, according to the attribute rules of each function item obtained through parsing, that there is a function item in the corresponding device operating mode whose writability status is non-writable, marking the corresponding device function item in the device information as non-writable; and / or, when it is determined, according to the attribute rules of each function item obtained through parsing, that there is a function item in the corresponding device operating mode whose current value exceeds the value range defined by the attribute rules, correcting the current value to the closest value within the corresponding value range.

[0009] It should be noted that by calibrating device information using attribute rules, the defects of device status abnormalities or functional conflicts caused by direct transmission of user commands from the wired controller are overcome. This enables localized adaptive correction of device access status, ensuring consistency between the status displayed on the wired controller and the actual capabilities and operating logic of the device. In specific operating modes, non-writable functional items are marked as non-writable, solving the problem of device malfunction or poor experience caused by users accidentally operating functional items when the device is in specific modes (such as sleep mode or self-test mode). Dynamic disabling of user interface interactive controls improves the user experience and device operation security. Furthermore, when the current value of a functional item exceeds the value range, it is corrected to the closest value to avoid illegal or out-of-bounds status values ​​due to device version differences or historical data residue. This achieves automatic cleaning and standardization of device status data, preventing execution errors or device shutdowns caused by illegal values ​​being sent to the device, thus improving the system's fault tolerance and stability.

[0010] According to a device access status management method provided by the present invention, the method further includes: receiving a control command sent by a user interface, the control command including a target function item of the target smart home device and a target value of the target function item; when it is determined that the writable state of the target function item in the target domain model file is writable, sending the control command to the corresponding smart home device; or, when it is determined that the writable state of the target function item in the target domain model file is non-writable, rejecting the control command and returning a prompt message indicating that the operation is prohibited to the user interface.

[0011] It should be noted that, based on the received control commands containing target function items and target values, the system accurately converts user operation intentions into specific device control parameters. This provides a clear control object and parameter basis for subsequent command verification and execution. Control commands are issued as soon as the writable state is determined, enabling rapid response and transparent transmission of legitimate user control commands. This ensures that user control operations on the device take effect in real time, provided they comply with mutual exclusion logic rules, thereby improving system operating efficiency. When the writable state is determined to be non-writable, the command is rejected and a prompt message is returned. This prevents device malfunction or damage caused by user misoperation or sending commands that violate mutual exclusion logic in specific operating modes. This achieves proactive mutual exclusion protection of device functions and timely blocking of erroneous operations, improving system security, stability, and user interaction experience.

[0012] According to a device access status management method provided by the present invention, before sending control commands to the corresponding smart home devices, the method further includes: determining whether the control command meets preset collaboration triggering conditions based on multi-device collaboration rules in a target domain model file; determining at least one target collaboration device associated with the smart home device based on the device association relationships defined in the multi-device collaboration rules, based on the target value contained in the control command and in conjunction with the multi-device collaboration rules; determining the collaboration control parameters corresponding to the target collaboration device, and generating a collaboration control command containing the collaboration control parameters; sending the control command to the corresponding smart home device and the collaboration control command to the target collaboration device, so as to realize the collaborative operation of multiple devices.

[0013] It should be added that by determining whether the collaborative triggering conditions are met based on the rules in the domain model file before issuing the command, the shortcomings of hard-coded device linkage logic, which cannot flexibly adapt to different device scenarios, are overcome. This enables the prediction of intelligent scene triggers, ensuring that only operations that meet specific strategies (such as mode switching and threshold changes) will trigger subsequent linkages, thereby avoiding invalid or erroneous linkage responses. Furthermore, by utilizing device association relationships to accurately locate target collaborative devices, the cumbersome problem of manually identifying and configuring associated devices in complex smart home environments is solved. This enables automatic search and matching of cross-device collaborative objects, ensuring the accuracy and coverage of collaborative actions. By calculating the control parameters of collaborative devices based on the target value of the master device and the rules, the limitation of only being able to perform simple on / off operations in linkage control is overcome, enabling dynamic association and fine-tuning of parameters between multiple devices. For example, automatically calculating the fresh air speed based on the air conditioner temperature, etc., the automation level and accuracy of collaborative work of the smart home system are improved. Then, the master control command and collaborative command are issued synchronously to achieve the synchronization and consistency of multi-device operation, solving the problem of fragmented user experience caused by independent control of multiple devices, and improving the overall effect of smart home scenario control and user convenience.

[0014] According to a device access status management method provided by the present invention, after synchronizing the calibrated device information to the user interface, the user interface is used to: dynamically render and display the operating status of the corresponding smart home device based on the writability status and value of each functional item in the calibrated device information.

[0015] It should be noted that by using calibrated device information for dynamic rendering and display of the interface, in order to avoid inconsistencies between the content displayed in the user interface and the actual operating capabilities and status of the device, real-time bidirectional synchronization between the user interface and the device logic is ensured, guaranteeing that what the user sees is what they get, while improving the accuracy of user operations and the interactive experience of the system.

[0016] According to a device access status management method provided by the present invention, calibrated device information is synchronized to the user interface, including: storing the calibrated device information in a front-end status manager; binding the data in the status manager with the display content and interaction status of each interactive control in the user interface; The user interface is used to dynamically render and display the operating status of the corresponding smart home device based on the writability status and value of each functional item in the calibrated device information. This includes: updating the interaction status of the corresponding functional item's interactive controls based on the device information stored in the status manager and the writability status of each corresponding device functional item after calibration; and updating the display content of the corresponding functional item's interactive controls based on the value of each corresponding device functional item after calibration. Specifically: when the writability status of the corresponding device functional item is determined to be non-writable, the corresponding interactive control is disabled; when the writability status of the corresponding device functional item is determined to be writable, the corresponding interactive control is enabled to allow its use.

[0017] It's important to note that by storing the calibrated device information in the state manager and binding it to UI controls, the code redundancy and maintenance difficulties caused by manually updating UI controls one by one in traditional development are avoided. This achieves automatic synchronization between data and view, improving the maintainability of the front-end code and the responsiveness of UI updates. Furthermore, the writability status and value of device information are used to update the state and display content of interactive controls, achieving a precise mapping between the displayed content and interactive capabilities. This improves the accuracy of user interface information and the intuitiveness of operation, ensuring users can clearly understand the current device status and available operations. Additionally, disabling the corresponding interactive control when a function is determined to be unwritable overcomes the problem of users clicking incorrectly or performing accidental operations due to an inability to intuitively determine function availability, leading to device errors. This proactive mutual exclusion interception at the front-end interaction level improves the success rate of user operations and the robustness of the system. Enabling the corresponding interactive control when a function is determined to be writable ensures users can successfully control the device within their legal permissions, achieving good interactive responsiveness and preventing situations where users cannot use device functions normally due to incorrect control state locking.

[0018] According to a device access status management method provided by the present invention, the domain model file library includes local domain model files and model update packages. The local domain model files are obtained by requesting updates from the cloud based on the online status. The model update packages are generated by the cloud based on the latest version of the domain model and the local domain model during a previous offline period, determining the corresponding logical differences, and combining the corresponding offline duration to predict the risk of mismatch between the corresponding local domain model file and the corresponding latest version of the cloud domain model file during the next offline period. Based on the offline status, after obtaining the target domain model file matching the device type, the method includes: obtaining the model update package and using the model update package to correct the corresponding target domain model file.

[0019] It should be noted that by constructing the domain model file library as a combination structure containing basic files (local domain model files) and dynamic patches (model update packages), layered and flexible model management is achieved, improving the efficiency of partial model updates, avoiding the waste of resources that require downloading the full model file every time, and actively requesting updates from the cloud and obtaining local domain model files when online, solving the problem of local model version lag causing incompatibility with the latest device functions, and achieving real-time synchronization between the local rule base and the cloud standard base, thereby ensuring the accuracy of device calibration logic.

[0020] The present invention also provides a device access status management device, comprising: an information receiving module for receiving device information reported by smart home devices; a file search module for searching and obtaining a target domain model file matching the device type from a locally stored domain model file library according to the device type in the device information; the domain model file is configured based on attribute rules of the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each functional item of the corresponding device type under different operating modes; and a calibration update module for parsing the target domain model file, using the attribute rules of each functional item obtained from the parsing to calibrate the corresponding functional items of the device information, and synchronizing the calibrated device information to the user interface.

[0021] It should be noted that the information receiving module receives device information proactively reported by smart home devices to perceive device status in real time, overcoming the status update delay problem caused by relying on cloud polling. The file search module searches for matching domain model files in the local library based on device type, avoiding the failure of device function cross-validation due to inaccessibility to the cloud rule base in offline states. This enables localized deployment and instant invocation of device control logic, ensuring system availability in weak or no network environments. Simultaneously, attribute rules generated based on mutual exclusion logic improve the compatibility and management uniformity of different device models. Furthermore, the calibration update module parses the domain model file and uses attribute rules to calibrate device function items, overcoming data parsing errors and operational conflicts caused by differences in device function definitions. This achieves standardized processing and status compliance checks of multi-source heterogeneous device data, improving the accuracy of information seen by the user when synchronizing calibrated information to the interface, and avoiding device anomalies and user experience degradation caused by status conflicts or illegal values.

[0022] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the device access state management method as described above.

[0023] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the device access state management method as described above.

[0024] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the device access status management method as described above. Attached Figure Description

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

[0026] Figure 1 This is a flowchart illustrating the device access status management method provided by the present invention; Figure 2 This is a schematic diagram of the device access status management device provided by the present invention; Figure 3 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0028] Figure 1 This is a flowchart illustrating the device access status management method provided by the present invention, as shown below. Figure 1 As shown, the method includes the following: S11 receives device information reported by smart home devices; S12, based on the device type in the device information, search for and retrieve the target domain model file that matches the device type from the locally stored domain model file library; the domain model file is configured based on the attribute rules of the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each functional item of the corresponding device type in different operating modes; S13, parse the target domain model file, use the attribute rules of each function item obtained from the parsing to calibrate the function items corresponding to the device information, and synchronize the calibrated device information to the user interface.

[0029] It should be noted that the execution entity of this method is the control terminal, which will be discussed in detail below. Figure 2 The present invention describes a device access status management method.

[0030] Step S11: Receive device information reported by smart home devices. It should be noted that the device information includes device type, device operating mode, and the current value of at least one device function item. Device function items characterize the corresponding device's function, such as air conditioner temperature or fan speed, and are specifically determined based on the actual smart home devices involved.

[0031] Step S12: Based on the device type in the device information, search for and obtain the target domain model file that matches the device type from the locally stored domain model file library; the domain model file is configured based on the attribute rules of the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each functional item of the corresponding device type in different operating modes.

[0032] In one optional embodiment, the domain model file library includes local domain model files and model update packages; the local domain model files are obtained by requesting updates from the cloud based on the online status; the model update packages are generated by the cloud based on the latest version of the domain model and the local domain model during the previous offline period, determining the corresponding logical differences, and combining the corresponding offline duration to predict the risk of mismatch between the corresponding local domain model file and the corresponding latest version of the cloud domain model file during the next offline period.

[0033] Accordingly, based on the offline state, after obtaining the target domain model file that matches the device type, the process includes: obtaining the model update package and using the model update package to correct the corresponding target domain model file.

[0034] It should be noted that by constructing the domain model file library as a combination structure containing basic files (local domain model files) and dynamic patches (model update packages), layered and flexible model management is achieved, improving the efficiency of partial model updates, avoiding the waste of resources that require downloading the full model file every time, and actively requesting updates from the cloud and obtaining local domain model files when online, solving the problem of local model version lag causing incompatibility with the latest device functions, and achieving real-time synchronization between the local rule base and the cloud standard base, thereby ensuring the accuracy of device calibration logic.

[0035] Furthermore, the cloud compares the latest version of the domain model with the local domain model from the previous offline period to determine the corresponding logical differences. This overcomes the shortcomings of simply judging whether the version is outdated based on a simple timestamp without knowing the specific changes. It achieves precise location of model change points and, combined with the corresponding offline duration, predicts the risk of mismatch during the next offline period. This avoids serious logical conflicts caused by large model version differences when the device suddenly comes online after a long period of offline or goes offline again. It improves the robustness and security of device control in offline scenarios, avoids device anomalies or security risks caused by the use of outdated rules, and ensures that after finding the local domain model file, the model update package is obtained based on the offline state to correct the local domain model file. This enables dynamic hot updates of model files in the offline state, improves the intelligence level of device access state management, and allows the device to automatically load the latest rule patches even in the offline state, ensuring the correctness of the running logic during offline periods.

[0036] Specifically, the cloud compares the latest version of the domain model file with the local domain model file used during the previous offline period to determine the corresponding logical differences. This includes: if the version number of the latest version of the domain model file in the cloud is the same as the version number of the local domain model file used during the previous offline period, it is determined that there is no logical difference and no model update package is generated; if the version numbers are different, the attribute rules of the inconsistent parts are extracted and combined with the offline duration to generate a model update package.

[0037] It should be noted that the cloud compares the latest version of the domain model file with the local domain model file used during the previous offline period. This overcomes the shortcomings of relying solely on timestamps to determine version updates, which fails to reveal specific rule changes. This enables precise location and difference analysis of model file changes. When version numbers match, no logical differences are identified, and no model update package is generated. This addresses the issue of wasted network bandwidth and computational resources caused by sending invalid data when rules have not changed, improving system processing efficiency and avoiding unnecessary model file refresh operations. Furthermore, when version numbers match, the attribute rules of the inconsistent parts are extracted and combined with the offline duration to generate a model update package. This resolves serious logical conflicts that may occur after prolonged offline periods due to large model version differences. This allows for dynamic trimming and targeted delivery of update content, ensuring the logical correctness of offline device operation while reducing the amount of data transmitted, thus improving the intelligence and robustness of device access status management.

[0038] It should be added that the domain model file is stored in JSON format. The domain model file defines trigger objects. The trigger object contains name, value and action fields. The action field contains data type, name, rewrite fields and writable state fields, which are used to define calibration rules for specific functional items.

[0039] Step S13: Parse the target domain model file, use the attribute rules of each function item obtained from the parsing to calibrate the function items corresponding to the device information, and synchronize the calibrated device information to the user interface.

[0040] In this embodiment, the device information includes the device type, device operating mode, and the current value of at least one device function item; the attribute rules include the writability status and value range of each function item; the corresponding function item in the device information is calibrated using the attribute rules of each function item obtained through parsing, including: when it is determined, according to the attribute rules of each function item obtained through parsing, that there is a function item in the corresponding device operating mode whose writability status is non-writable, marking the corresponding device function item in the device information as non-writable; and / or, when it is determined, according to the attribute rules of each function item obtained through parsing, that there is a function item in the corresponding device operating mode whose current value exceeds the value range defined by the attribute rules, correcting the current value to the closest value within the corresponding value range.

[0041] It should be noted that by calibrating device information using attribute rules, the defects of device status abnormalities or functional conflicts caused by direct transmission of user commands from the wired controller are overcome. This enables localized adaptive correction of device access status, ensuring consistency between the status displayed on the wired controller and the actual capabilities and operating logic of the device. In specific operating modes, non-writable functional items are marked as non-writable, solving the problem of device malfunction or poor experience caused by users accidentally operating functional items when the device is in specific modes (such as sleep mode or self-test mode). Dynamic disabling of user interface interactive controls improves the user experience and device operation security. Furthermore, when the current value of a functional item exceeds the value range, it is corrected to the closest value to avoid illegal or out-of-bounds status values ​​due to device version differences or historical data residue. This achieves automatic cleaning and standardization of device status data, preventing execution errors or device shutdowns caused by illegal values ​​being sent to the device, thus improving the system's fault tolerance and stability.

[0042] In one optional embodiment, after synchronizing the calibrated device information to the user interface, the user interface is used to: dynamically render and display the operating status of the corresponding smart home device based on the writability status and value of each functional item in the calibrated device information.

[0043] It should be noted that by using calibrated device information for dynamic rendering and display of the interface, in order to avoid inconsistencies between the content displayed in the user interface and the actual operating capabilities and status of the device, real-time bidirectional synchronization between the user interface and the device logic is ensured, guaranteeing that what the user sees is what they get, while improving the accuracy of user operations and the interactive experience of the system.

[0044] Specifically, the calibrated device information is synchronized to the user interface, including: storing the calibrated device information in the front-end state manager; and binding the data in the state manager with the display content and interaction state of each interactive control in the user interface.

[0045] Accordingly, the user interface is used to dynamically render and display the operating status of the corresponding smart home device based on the writability status and value of each functional item in the calibrated device information. This includes: updating the interaction status of the corresponding functional item interactive control based on the device information stored in the status manager and the writability status of each corresponding device functional item after calibration; and updating the display content of the corresponding functional item interactive control based on the value of each corresponding device functional item after calibration. Specifically: when the writability status of the corresponding device functional item is determined to be non-writable, the corresponding interactive control is disabled; when the writability status of the corresponding device functional item is determined to be writable, the corresponding interactive control is enabled to allow the use of the corresponding interactive control.

[0046] It's important to note that by storing the calibrated device information in the state manager and binding it to UI controls, the code redundancy and maintenance difficulties caused by manually updating UI controls one by one in traditional development are avoided. This achieves automatic synchronization between data and view, improving the maintainability of the front-end code and the responsiveness of UI updates. Furthermore, the writability status and value of device information are used to update the state and display content of interactive controls, achieving a precise mapping between the displayed content and interactive capabilities. This improves the accuracy of user interface information and the intuitiveness of operation, ensuring users can clearly understand the current device status and available operations. Additionally, disabling the corresponding interactive control when a function is determined to be unwritable overcomes the problem of users clicking incorrectly or performing accidental operations due to an inability to intuitively determine function availability, leading to device errors. This proactive mutual exclusion interception at the front-end interaction level improves the success rate of user operations and the robustness of the system. Enabling the corresponding interactive control when a function is determined to be writable ensures users can successfully control the device within their legal permissions, achieving good interactive responsiveness and preventing situations where users cannot use device functions normally due to incorrect control state locking.

[0047] In an optional embodiment, the method further includes: receiving a control instruction sent by a user interface, the control instruction including a target function item of the target smart home device and a target value of the target function item; when it is determined that the writable state of the target function item in the target domain model file is writable, sending the control instruction to the corresponding smart home device; or, when it is determined that the writable state of the target function item in the target domain model file is non-writable, rejecting the control instruction and returning a prompt message indicating that the operation is prohibited to the user interface.

[0048] It should be noted that, based on the received control commands containing target function items and target values, the system accurately converts user operation intentions into specific device control parameters. This provides a clear control object and parameter basis for subsequent command verification and execution. Control commands are issued as soon as the writable state is determined, enabling rapid response and transparent transmission of legitimate user control commands. This ensures that user control operations on the device take effect in real time, provided they comply with mutual exclusion logic rules, thereby improving system operating efficiency. When the writable state is determined to be non-writable, the command is rejected and a prompt message is returned. This prevents device malfunction or damage caused by user misoperation or sending commands that violate mutual exclusion logic in specific operating modes. This achieves proactive mutual exclusion protection of device functions and timely blocking of erroneous operations, improving system security, stability, and user interaction experience.

[0049] Furthermore, before sending control commands to the corresponding smart home devices, the process includes: determining whether the control commands meet preset collaborative triggering conditions based on the multi-device collaboration rules in the target domain model file; determining at least one target collaborative device associated with the smart home device based on the device association relationships defined in the multi-device collaboration rules, based on the target value contained in the control commands and in conjunction with the multi-device collaboration rules; determining the collaborative control parameters corresponding to the target collaborative device based on the target value contained in the control commands and in conjunction with the multi-device collaboration rules, and generating a collaborative control command containing the collaborative control parameters; sending the control commands to the corresponding smart home devices and sending the collaborative control commands to the target collaborative devices to achieve collaborative operation of multiple devices.

[0050] It should be added that multi-device collaboration rules are used to characterize the mechanism by which controlling one device automatically triggers other related devices to perform corresponding actions according to preset rules. For example, when the air conditioner is in cooling mode, if the light sensor value is determined to be greater than the strong light threshold, the associated curtain device is searched, and based on the difference between the light sensor value and the strong light threshold, combined with the corresponding multi-device collaboration rules, the corresponding curtain closing ratio is determined, and the corresponding collaborative control command is generated. No further limitations are made here.

[0051] Furthermore, by determining whether the collaborative triggering conditions are met based on rules in the domain model file before issuing commands, the shortcomings of hard-coded device linkage logic, which cannot flexibly adapt to different device scenarios, are overcome. This enables the prediction of intelligent scene triggers, ensuring that only operations that conform to specific strategies (such as mode switching and threshold changes) will trigger subsequent linkages, thereby avoiding invalid or erroneous linkage responses. Furthermore, by utilizing device association relationships to accurately locate target collaborative devices, the cumbersome problem of manually identifying and configuring associated devices in complex smart home environments is solved. This enables automatic search and matching of cross-device collaborative objects, ensuring the accuracy and coverage of collaborative actions. By calculating the control parameters of collaborative devices based on the target value of the master device and rules, the limitations of simple on / off operations in linkage control are overcome, enabling dynamic association and fine-tuning of parameters between multiple devices. For example, automatically calculating the fresh air speed based on the air conditioner temperature, etc., improves the automation level and accuracy of collaborative work in the smart home system. Finally, master control commands and collaborative commands are issued synchronously, achieving synchronization and consistency of multi-device operation, solving the problem of fragmented user experience caused by independent control of multiple devices, and improving the overall effect of smart home scenario-based control and user convenience.

[0052] In summary, this invention receives device information proactively reported by smart home devices to perceive device status in real time, overcoming the status update delay caused by relying on cloud polling. It also searches for matching domain model files in a local library based on device type to avoid device function cross-validation failures due to offline access to the cloud rule base. This enables localized deployment and immediate invocation of device control logic, ensuring system availability in weak or no-network environments. Furthermore, attribute rules generated based on mutual exclusion logic improve compatibility and management consistency across different device models. By parsing domain model files and using attribute rules to calibrate device function items, it overcomes data parsing errors and operational conflicts caused by differences in device function definitions. This achieves standardized processing and status compliance checks of multi-source heterogeneous device data, improving the accuracy of user-visible information when synchronizing calibrated information to the interface and preventing device anomalies and user experience degradation due to status conflicts or illegal values.

[0053] The device access status management device provided by the present invention is described below. The device access status management device described below and the device access status management method described above can be referred to in correspondence.

[0054] Figure 2 A schematic diagram of a device access status management device is shown. The device includes: Information receiving module 21 receives device information reported by smart home devices; The file search module 22 searches for and retrieves the target domain model file that matches the device type from the locally stored domain model file library based on the device type in the device information. The domain model file is configured based on the attribute rules of the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each function item of the corresponding device type in different operating modes. The calibration update module 23 parses the target domain model file, uses the attribute rules of each function item obtained from the parsing to calibrate the corresponding function items of the device information, and synchronizes the calibrated device information to the user interface.

[0055] In one optional embodiment, the domain model file library includes local domain model files and model update packages; the local domain model files are obtained by requesting updates from the cloud based on the online status; the model update packages are generated by the cloud based on the latest version of the domain model and the local domain model during the previous offline period, determining the corresponding logical differences, and combining the corresponding offline duration to predict the risk of mismatch between the corresponding local domain model file and the corresponding latest version of the cloud domain model file during the next offline period.

[0056] Accordingly, the file search module 22 is also used to: based on the offline state, after obtaining the target domain model file that matches the device type, obtain the model update package, and use the model update package to correct the corresponding target domain model file.

[0057] Specifically, in the cloud, it is also used for: if the latest version of the domain model file in the cloud has the same version number as the local domain model file used during the previous offline period, then it is determined that there is no logical difference and no model update package is generated; if the version numbers are inconsistent, the attribute rules of the inconsistent parts are extracted and combined with the offline duration to generate a model update package.

[0058] In this embodiment, the device information includes the device type, device operating mode, and the current value of at least one device function item; the attribute rules include the writability status and value range of each function item; the calibration update module 23 includes: a status correction unit, which, according to the parsed attribute rules of each function item, determines that when there is a function item in the corresponding device operating mode whose writability status is non-writable, marks the corresponding device function item in the device information as non-writable; and / or a value correction unit, which, according to the parsed attribute rules of each function item, determines that when the current value of a function item in the corresponding device operating mode exceeds the value range defined by the attribute rules, corrects the current value to the closest value within the corresponding value range.

[0059] In one optional embodiment, after synchronizing the calibrated device information to the user interface, the user interface is used to: dynamically render and display the operating status of the corresponding smart home device based on the writability status and value of each functional item in the calibrated device information.

[0060] Specifically, the calibration update module 23 also includes: an update unit that stores the calibrated device information into the front-end state manager; the data in the state manager is bound to the display content and interaction state of each interactive control in the user interface.

[0061] Accordingly, the user interface is also used to: update the interaction state of the corresponding function item interactive control based on the device information stored in the state manager and the writability state of each corresponding calibrated device function item; and update the display content of the corresponding function item interactive control based on the value of each corresponding calibrated device function item, wherein: when the writability state of the corresponding device function item is determined to be non-writable, the corresponding interactive control is disabled; when the writability state of the corresponding device function item is determined to be writable, the corresponding interactive control is enabled to allow the use of the corresponding interactive control.

[0062] In an optional embodiment, the device further includes: an instruction receiving module for receiving control instructions sent by a user interface, the control instructions including target function items of the target smart home device and target values ​​of the target function items; an instruction issuing module for issuing control instructions to the corresponding smart home device when it is determined that the target function item is writable in the target domain model file; or, a prompting module for rejecting control instructions and returning a prompt message indicating that the operation is prohibited to the user interface when it is determined that the target function item is not writable in the target domain model file.

[0063] Furthermore, the device also includes: a condition judgment module, which determines whether the control command meets preset collaborative triggering conditions based on the multi-device collaboration rules in the target domain model file before sending the control command to the corresponding smart home device; a device determination module, which determines that the control command meets the preset collaborative triggering conditions and determines at least one target collaborative device associated with the smart home device based on the device association relationships defined in the multi-device collaboration rules; an instruction generation module, which determines the collaborative control parameters corresponding to the target collaborative device based on the target value contained in the control command and in combination with the multi-device collaboration rules, and generates a collaborative control command containing the collaborative control parameters; and a collaborative control module, which sends the control command to the corresponding smart home device and the collaborative control command to the target collaborative device to achieve collaborative operation of multiple devices.

[0064] In summary, this embodiment of the invention receives device information proactively reported by smart home devices through an information receiving module to perceive device status in real time, overcoming the status update delay problem caused by relying on cloud polling. A file search module searches for matching domain model files in a local library based on device type to avoid device function cross-validation failures caused by offline access to the cloud rule base. This enables localized deployment and immediate invocation of device control logic, ensuring system availability in weak or no-network environments. Furthermore, attribute rules generated based on mutual exclusion logic improve the compatibility and management uniformity of different device models. A calibration update module further parses the domain model file and uses attribute rules to calibrate device function items, overcoming data parsing errors and operational conflicts caused by differences in device function definitions. This achieves standardized processing and status compliance checks of multi-source heterogeneous device data, improving the accuracy of user-visible information when synchronizing calibrated information to the interface and avoiding device anomalies and user experience degradation due to status conflicts or illegal values.

[0065] Figure 3 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 3 As shown, the electronic device may include a processor 310, a communications interface 320, a memory 330, and a communication bus 340. The processor 310, communications interface 320, and memory 330 communicate with each other via the communication bus 340. The processor 310 can call logical instructions stored in the memory 330 to execute a device access status management method. This method includes: receiving device information reported by the smart home device; searching for and retrieving a target domain model file matching the device type from a locally stored domain model file library based on the device type in the device information; the domain model file is configured based on attribute rules for the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each functional item under different operating modes of the corresponding device type; parsing the target domain model file, using the parsed attribute rules for each functional item to calibrate the corresponding functional item of the device information, and synchronizing the calibrated device information to the user interface.

[0066] Furthermore, the logical instructions in the aforementioned memory 330 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0067] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the device access status management method provided by the above methods. The method includes: receiving device information reported by smart home devices; searching for and obtaining a target domain model file matching the device type from a locally stored domain model file library according to the device type in the device information; the domain model file is configured based on attribute rules of the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each functional item of the corresponding device type under different operating modes; parsing the target domain model file, using the attribute rules of each functional item obtained from the parsing, calibrating the functional items corresponding to the device information, and synchronizing the calibrated device information to the user interface.

[0068] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements the device access status management method provided by the above methods. The method includes: receiving device information reported by a smart home device; searching for and obtaining a target domain model file matching the device type from a locally stored domain model file library according to the device type in the device information; the domain model file is configured based on attribute rules of the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each functional item of the corresponding device type under different operating modes; parsing the target domain model file, using the attribute rules of each functional item obtained from the parsing, calibrating the functional items corresponding to the device information, and synchronizing the calibrated device information to the user interface.

[0069] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0070] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part 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, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0071] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for managing device access status, characterized in that, include: Receive device information reported by smart home devices; Based on the device type in the device information, a target domain model file matching the device type is searched and obtained from the locally stored domain model file library; the domain model file is configured based on the attribute rules of the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each function item of the corresponding device type in different operating modes; The target domain model file is parsed, and the attribute rules of each functional item obtained from the parsing are used to calibrate the functional items corresponding to the device information, and the calibrated device information is synchronized to the user interface.

2. The device access status management method according to claim 1, characterized in that, The device information includes device type, device operating mode, and the current value of at least one device function item; the attribute rules include the writability status and value range of each function item. Using the attribute rules of each functional item obtained from the parsing, the functional items corresponding to the device information are calibrated, including: Based on the attribute rules of each functional item obtained from the parsing, when it is determined that there is a functional item in the corresponding device operation mode that is in a writable state, the corresponding device functional item in the device information is marked as a writable state. And / or, Based on the attribute rules of each function item obtained from the analysis, when it is determined that the current value of a function item in the corresponding device operation mode exceeds the value range defined by the attribute rules, the current value is corrected to the closest value within the corresponding value range.

3. The device access status management method according to claim 1, characterized in that, The method further includes: Receive control instructions sent by the user interface, the control instructions including the target function items of the target smart home device and the target values ​​of the target function items; When the target function item is determined to be writable in the target domain model file, the control command is sent to the corresponding smart home device; or, When it is determined that the writable state of the target function item in the target domain model file is not writable, the control command is rejected and a prompt message indicating that the operation is prohibited is returned to the user interface.

4. The device access status management method according to claim 3, characterized in that, Before sending the control commands to the corresponding smart home devices, the method further includes: Based on the multi-device collaboration rules in the target domain model file, determine whether the control command meets the preset collaboration triggering conditions; Determine that the control command meets the preset collaborative triggering conditions, and determine at least one target collaborative device associated with the smart home device according to the device association relationship defined in the multi-device collaboration rules; Based on the target value contained in the control command, and in conjunction with the multi-device collaboration rules, the collaboration control parameters corresponding to the target collaboration device are determined, and a collaboration control command containing the collaboration control parameters is generated. The control commands are sent to the corresponding smart home devices, and the collaborative control commands are sent to the target collaborative devices to enable collaborative work among multiple devices.

5. The device access status management method according to claim 1, characterized in that, After synchronizing the calibrated device information to the user interface, the user interface is used for: Based on the writability status and values ​​of each function item in the calibrated device information, the operating status of the corresponding smart home device is dynamically rendered and displayed.

6. The device access status management method according to claim 5, characterized in that, Synchronize the calibrated device information to the user interface, including: The calibrated device information is stored in the front-end state manager; the data in the state manager is bound to the display content and interaction state of each interactive control in the user interface; The user interface is used to dynamically render and display the operating status of the corresponding smart home device based on the writability status and values ​​of each functional item in the calibrated device information, including: Based on the device information stored in the state manager, the interaction state of the corresponding function item's interactive control is updated according to the writability status of each calibrated device function item, and the display content of the corresponding function item's interactive control is updated according to the value of each calibrated device function item, wherein: When the writability status of the corresponding device function item is determined to be non-writable, the corresponding interactive control is disabled; When the writability status of the corresponding device function item is determined to be writable, the corresponding interactive control is enabled to allow its use.

7. The device access status management method according to any one of claims 1-6, characterized in that, The domain model file library includes local domain model files and model update packages; The local domain model file is obtained by requesting updates from the cloud based on the online status; The model update package is generated by the cloud based on the latest version of the domain model and the local domain model during the previous offline period, determining the corresponding logical differences, and combining the corresponding offline duration to predict the risk of mismatch between the local domain model file and the latest version of the cloud domain model file during the next offline period. Based on the offline status, after obtaining the target domain model file matching the device type, the process includes: Obtain the model update package and use the model update package to correct the corresponding target domain model file.

8. A device access status management device, characterized in that, include: The information receiving module receives device information reported by smart home devices; The file search module searches for and retrieves a target domain model file that matches the device type from the locally stored domain model file library based on the device type in the device information. The domain model file is configured based on the attribute rules of the corresponding device type, and the attribute rules are generated based on the mutual exclusion logic of each function item of the corresponding device type in different operating modes. The calibration update module parses the target domain model file, uses the attribute rules of each function item obtained from the parsing to calibrate the function items corresponding to the device information, and synchronizes the calibrated device information to the user interface.

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 processor executes the computer program, it implements the steps of the device access status management method as described in any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the device access state management method as described in any one of claims 1 to 7.

Images