IoT Device Authentication via Mobile Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Internet of Things (IoT) devices, such as electronic locks, face security challenges when communicating with cloud servers through mobile devices, as these communications can be vulnerable to tampering, particularly in scenarios where direct network connections are not available.
Innovation Solution
A method involving a random number challenge generated by the cloud server, sent through a mobile device to an IoT device, and verified against a public key, ensuring secure communication by using private key signatures, either directly between the IoT device and cloud server or through a mobile device, utilizing various wireless protocols like Wi-Fi, Bluetooth, and others.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IoT devices communicate with cloud servers through mobile devices using applications, then connectivity and remote functionality are enabled, but security is compromised due to application vulnerability to tampering
Solution Approach 1:
The patent introduces a cloud server as an intermediary that performs mutual authentication with both the IoT device and mobile device. The server verifies device credentials and establishes secure communication channels, preventing direct untrusted access between the mobile application and IoT device while maintaining connectivity functionality.
Solution Approach 2:
The system performs authentication and security verification before establishing communication channels. The IoT device and cloud server authenticate each other using digital certificates and cryptographic keys in advance, ensuring that only verified devices can communicate securely through the mobile application intermediary.
2Reliability
If direct network connection is used between IoT device and server, then security is improved, but adaptability is reduced as not all IoT devices can establish direct connections
Solution Approach 1:
The cloud server is designed to handle multiple communication scenarios: direct IoT-to-server connections for capable devices, and intermediary mobile device connections for devices with limited networking capabilities. This universal architecture supports both connection types while maintaining security protocols for each.
Solution Approach 2:
The mobile device acts as a mediator for IoT devices that cannot connect directly to the cloud. The intermediary role enables these limited-capability devices to access cloud services through the mobile device's network connection while the server maintains security verification through the established authentication framework.
3Reliability
If authentication protocols are implemented between IoT device and server, then security is enhanced, but device complexity increases
Solution Approach 1:
The authentication system is segmented into separate components: the cloud server handles complex cryptographic verification and certificate validation, while the IoT device only needs to store credentials and perform simpler authentication operations. This segmentation reduces the computational burden and complexity on resource-constrained IoT devices.
Solution Approach 2:
The cloud server acts as an intermediary that manages the complexity of authentication protocols. It handles certificate verification, key management, and security token validation, freeing IoT devices from implementing complex authentication logic locally while maintaining strong security through server-side verification.
Data Source
AI summary
Methods and systems for authenticating an Internet of Things device, such as an electronic lock, are disclosed. One method includes generating a first challenge at a server; transmitting the first challenge to the Internet of Things device; receiving a first signed certificate from the Internet of Things device, the first signed certificate being the first random number challenge signed with a private key associated with the internet of things device; and verifying the first signed certificate with the first challenge and a public key associated with the Internet of Things device. Mutual authentication of the server from the Internet of Things device is also provided.