Mobile IoT Control via Token Relay and Near-Range Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional IoT devices face issues of high power consumption, high manufacturing costs, and the need for network infrastructure deployment, particularly when using multiple communication protocols, and lack secure authorization mechanisms.
Innovation Solution
A mobile device acts as a conduit between an IoT device and a management device, supporting near-range protocols like BT, BTLE, or NFC, and enabling secure communication and authorization through cryptographic tokens, reducing the need for long-range protocols and network infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If an IoT device employs multiple communication means (wired and wireless protocols) to support network connectivity, then the network connectivity capability is improved, but the manufacturing cost increases
Solution Approach 1:
The mobile device serves as an intermediary between the IoT device and the network infrastructure. The IoT device communicates with the mobile device using near-range protocols (Bluetooth, BTLE, or NFC), and the mobile device handles long-range communication via WLAN or cellular networks. This eliminates the need for the IoT device to implement multiple communication protocols, reducing manufacturing costs while maintaining network connectivity capability.
2Length of moving object
If an IoT device implements long-range protocols (such as WLAN) to extend communication range, then the communication range is improved, but the power consumption increases
Solution Approach 1:
The communication function is segmented between the IoT device and the mobile device. The IoT device uses low-power near-range protocols (Bluetooth, BTLE, or NFC) for short-distance communication, while the mobile device handles long-range communication tasks. This segmentation allows the battery-driven IoT device to maintain extended communication range capability without the power consumption penalty of implementing long-range protocols.
3Ease of operation
If conventional IoT devices are deployed in security critical environments with basic authorization mechanisms, then the deployment simplicity is improved, but the security level deteriorates
Solution Approach 1:
The mobile device acts as a secure intermediary that mediates between the IoT device and external entities. It implements robust authorization mechanisms including device identification, access token generation, and secure credential verification. The mobile device can establish secure communication channels (e.g., TLS/SSL encrypted connections) with cloud services and other IoT devices, thereby enhancing security without complicating the IoT device deployment.
4Adaptability or versatility
If an established network connection is required for IoT device operation, then the network infrastructure capability is improved, but the power consumption and device complexity increase
Solution Approach 1:
The mobile device serves as a portable network gateway and intermediary. The IoT device establishes a simple local connection with the mobile device using near-range protocols, while the mobile device maintains the network connection to external networks (WLAN, cellular, etc.). This approach provides full network infrastructure capability without requiring the IoT device to maintain active network connections, thereby reducing power consumption and device complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention provides a mobile device (100) for controlling an Internet of Thing (IoT) device (200), wherein the mobile device (100) is configured to obtain a first access token (101) from a management device (300); provide a request for authorization (102) of the mobile device (100) to the management device (300), based on the first access token (101); forward a request for authorization (103) of the IoT device 200 to the management device (300); obtain a second access token (104) from the management device (300), based on authorization of the mobile device (100) and based on authorization of the IoT device (200); and control the IoT device (200) based on the second access token (104).