Dynamic Device Driver Integration via Verified Model Templates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The heterogeneity and diversity of smart devices in networks, such as home automation and smart energy systems, pose challenges due to limited standards and protocols, making it difficult to establish communication between devices of different types without interfering with the user experience or requiring recompilation, reinstallation, or restart of applications.
Innovation Solution
A method that involves receiving a driver model from a third party, validating its format compliance and syntax, generating a verified file that can dynamically load into a device application module, and adding an integrity check, allowing for integration of new devices without disrupting user experience or requiring recompilation of applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple applications are loaded onto control devices to support different smart devices, then device compatibility is improved, but device complexity increases
Solution Approach 1:
The patent creates a universal driver template system that can support multiple smart device types through a single application. The driver template includes parameter definitions, data types, and communication protocols that can be configured for different devices, eliminating the need for separate applications for each device type.
Solution Approach 2:
The patent segments the device support functionality into modular driver templates that can be independently configured and loaded. Each driver template is a self-contained unit that defines specific device parameters and communication methods, allowing dynamic addition without affecting the core application structure.
2Reliability
If proprietary protocols are used for smart device communication, then device-specific functionality is improved, but system adaptability deteriorates
Solution Approach 1:
The patent introduces a driver template as an intermediary layer between the control application and smart devices. The template translates proprietary device protocols into a standardized communication interface, allowing the application to communicate with diverse devices using a unified approach while maintaining device-specific communication reliability.
Solution Approach 2:
The patent uses parameter-based configuration within driver templates to adapt to different communication protocols. By defining communication parameters, data types, and protocol-specific settings in the template, the system can dynamically adjust to various proprietary protocols without changing the core application logic.
3Adaptability or versatility
If driver models are dynamically loaded, then system flexibility is improved, but system reliability deteriorates
Solution Approach 1:
The patent performs preliminary validation of driver models against a schema before dynamic loading. The system checks whether the driver model conforms to the expected structure, required parameters, and data types, ensuring that only valid drivers are integrated. This pre-validation approach maintains system stability while enabling flexible driver addition.
Solution Approach 2:
The patent implements feedback mechanisms that monitor the integrity and performance of dynamically loaded driver models. The system verifies that loaded drivers function correctly and provides error reporting, allowing the system to maintain reliability through continuous validation and error handling of dynamic components.
Data Source
AI summary
A method includes receiving a driver model for a device. The driver model includes a list of variables associated with the device and one or more characteristics of the variables. The method includes determining whether the driver model is format-compliant and validating syntax of the driver model based at least partially on a driver template that is accessible to a third party. In response to the driver model being format-compliant and the syntax being valid, the method includes generating a verified file that is representative of the driver model. The verified file is formatted to dynamically load into a device application module during operation and to dynamically support the device. The method includes communicating the verified file to a user apparatus and adding an integrity check value thereto. In response to the driver model being format-noncompliant or the syntax being invalid, the method includes communicating an error message.