Device Abstraction Layer for Networked Device Protocol Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing networked products from different brands within the same product type cannot be controlled using the same commands and methodologies, leading to compatibility issues and increased complexity for developers trying to build applications that integrate with these devices.
Innovation Solution
The Cloud-Assisted Network Device Integration (CANDI) system standardizes actions across different devices by using a uniform device abstraction layer, allowing developers to control various networked devices through a single interface, regardless of the vendor or protocol, and enables the integration of new devices into the system without requiring detailed knowledge of their specific protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If developers build applications to integrate with networked devices from different brands, then device functionality can be accessed, but compatibility issues arise and complexity increases due to different protocols and command structures
Solution Approach 1:
The patent implements a universal device abstraction layer that provides standardized commands and interfaces for controlling diverse networked devices. This layer translates generic control requests into device-specific protocols, enabling a single application to interact with multiple device types (lights, switches, appliances) from different manufacturers without requiring separate integration logic for each device brand.
Solution Approach 2:
The device abstraction layer acts as an intermediary between the application and the actual networked devices. It sits in the middle of the communication chain, receiving standardized commands from applications and translating them into the specific protocols required by individual devices. This mediator approach isolates applications from protocol complexity while maintaining broad device compatibility.
2Adaptability or versatility
If multiple device protocols are supported directly in applications, then device-specific control is achieved, but installation and development costs increase
Solution Approach 1:
The patent extracts protocol-specific complexity from the application layer and relocates it to the device abstraction layer. By separating the standardized interface (used by applications) from the protocol-specific implementation (handled by the abstraction layer), the system reduces development costs for applications while maintaining support for multiple protocols through reusable translation logic.
3Reliability
If device-specific control methods are used, then precise device manipulation is possible, but ease of operation decreases due to needing to know different commands for different devices
Solution Approach 1:
The device abstraction layer provides a universal control interface where users can interact with diverse devices using consistent commands. A single standardized command structure handles different device types (lights, switches, appliances) uniformly, maintaining control precision through proper command translation while presenting a simple, consistent interface to users regardless of the underlying device-specific protocols.
Data Source
AI summary
A system for managing a domain in a premises is described. The system includes: an action identifier coupled with a server, the action identifier identifies an action to be mapped to a device of the at least one device, wherein the device comprises a communication port that supports a first protocol; a device driver determiner coupled with the server, the device driver determiner determines a device driver that supports a second protocol, wherein the second protocol supports the action; a comparer coupled with the server, the comparer compares the second protocol with a domain configuration store comprising device configuration information for the at least one device; and a device driver implementer coupled with the server, the device driver implementer implements, based on the comparing, the device driver when the first protocol corresponds to the second protocol such that the action is enabled for performance.