IoT Gateway Authentication Database for Autonomous Data Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IoT systems lack a secure and ad-hoc networking solution for connecting low power IoT devices directly to servers without the need for intermediate devices like smartphones, limiting their ability to exchange data autonomously and efficiently.
Innovation Solution
A data exchange system and gateway module that utilize a device detecting unit, authentication database, and data sending unit to establish a secure connection between IoT devices and servers, using device identifiers to map data types to corresponding destinations and apply data rules, with the option of a blockchain-based authentication database for enhanced security and transparency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IoT devices connect through intermediate gateway devices like smartphones, then device connectivity and data exchange are enabled, but system complexity increases and autonomous data exchange is limited
Solution Approach 1:
The patent extracts the authentication and data routing logic from the smartphone gateway into a dedicated authentication database. This allows IoT devices to exchange data autonomously without requiring the smartphone to interpret and forward data, reducing system complexity while maintaining connectivity capabilities.
Solution Approach 2:
The patent introduces an authentication database as an intermediary component that stores device identifiers, data types, and destination mappings. This mediator enables direct peer-to-peer data exchange between IoT devices and servers, eliminating the need for smartphone-mediated communication and enhancing autonomous operation.
2Reliability
If traditional pairing and installation processes are required for IoT device connections, then secure authentication can be established, but user operation time and complexity increase
Solution Approach 1:
The patent implements preliminary action by pre-storing device identifiers, data types, and destination server mappings in the authentication database during device provisioning. This allows the system to perform rapid authentication and data routing decisions without requiring time-consuming pairing processes when devices need to communicate.
Solution Approach 2:
The authentication database enables self-service authentication where devices can autonomously query their credentials and routing information without user intervention. The system automatically matches device identifiers with stored data types and destinations, eliminating manual pairing steps while maintaining security.
3Ease of manufacture
If all data from IoT devices is sent to a single destination, then data collection is simplified, but data processing efficiency and relevance decrease
Solution Approach 1:
The patent applies segmentation by dividing data routing into multiple destination paths based on data type. The authentication database stores mappings that direct different types of data (e.g., sensor readings, device status, logs) to different destination servers, allowing parallel processing and reducing bottlenecks while maintaining simple collection at the source.
Solution Approach 2:
The patent implements local quality by assigning specific data types to specific destination servers based on their processing capabilities and relevance. Each data type receives customized routing to the most appropriate server, optimizing processing efficiency while keeping the overall collection mechanism simple through centralized authentication database management.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Data exchange system for exchanging data between a data containing device and a server, the system comprising: a device detecting unit to detect the device and obtain from the device a device identifier; an authentication database to store therein a mapping between the device identifier and at a data type, and to store a corresponding data destination, wherein the data type is representative of the type of data that is stored on the device and the data destination is representative of a destination server to which the corresponding data type is to be sent; an authentication obtaining unit to obtain from the authentication database the data type and data destination based on the device identifier; a data obtaining unit to obtain the data from the device based on the data type; and a data sending unit to direct the data to the corresponding destination server based on the data destination.