Device Management Infrastructure for Heterogeneous IoT Data Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods face challenges in managing access permissions for devices, providing credentialing mechanisms, and efficiently connecting and managing data from disparate devices, leading to increased complexity and costs in implementing connectivity and data management across various software applications and devices.
Innovation Solution
A device management infrastructure that enables secure, flexible, and configurable management of device access by using a cloud-based service architecture to share data among devices while preserving user security settings, utilizing Representational State Transfer (REST) APIs and JavaScript Object Notation (JSON) for data formatting, and employing gateway devices to translate device-native formats into device-agnostic formats for seamless communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If current methods are used for providing information to and from devices, then device connectivity and data management can be established, but complexity and costs increase significantly
Solution Approach 1:
The patent introduces a device management server as an intermediary component that mediates between multiple devices and software applications. This server centralizes permission management and data routing functions, allowing devices to communicate through a unified interface rather than direct peer-to-peer connections. The intermediary handles authentication, authorization, and data formatting, thereby reducing the complexity that would otherwise exist in managing direct device-to-device connectivity across diverse protocols and formats.
2Loss of information
If comprehensive device information is provided to all users, then data availability is maximized, but security and access control are compromised
Solution Approach 1:
The patent implements local quality by providing different levels of device information to different users based on their authorization status. The device management server filters and selectively transmits information according to user-specific permission sets. Authorized users receive comprehensive device information, while unauthorized users receive limited or no information. This selective information disclosure maintains high data availability for legitimate users while preserving security and access control integrity.
Solution Approach 2:
The device management server acts as an intermediary between devices and users, centrally managing authentication and authorization. It receives device information from devices, processes permission requests, and selectively forwards information to authorized users. This intermediary layer ensures that comprehensive data remains available to authorized users while preventing unauthorized access, thereby balancing data availability with security requirements.
3Reliability
If device-specific formats are used for data communication, then device compatibility is maintained, but integration across disparate devices becomes difficult
Solution Approach 1:
The device management server serves as a translation intermediary that receives device information in device-specific native formats and converts it into a standardized, device-agnostic format for distribution to software applications and users. This format conversion capability allows the system to maintain compatibility with diverse device protocols while achieving seamless integration across the heterogeneous device ecosystem. The server acts as a universal translator that bridges proprietary device formats with standardized communication protocols.
Data Source
AI summary
An example device for providing device information to a device management infrastructure includes a memory subsystem; a communication interface to: receive, from a first device, first device information in a first device-native format; receive, from a second device, second device information in a second device-native format different than the first device-native format; transmit the first device information to a remote server in a device-agnostic format; and transmit the second device information to the remote server in the device-agnostic format; and a device information processor to convert the first device information and the second device information into the device-agnostic format.