Embedded IoT Device Authentication for Multiple Controllers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IoT systems face challenges in identifying and authenticating multiple controllers without direct connection to a central control server, particularly in scenarios where network connectivity is unreliable or unavailable, necessitating mechanisms to verify controller authenticity and assign permissions dynamically.
Innovation Solution
A system that enables IoT devices to authenticate and assign permissions to multiple controllers using device certificates and shared secrets, allowing direct communication between controllers and embedded devices without reliance on a central server, using mechanisms like device certificates, shared secrets, and root certificates to verify authenticity and permissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a central control server is used to authenticate controllers and set permissions, then authentication and permission management can be centralized, but the system requires continuous network connectivity to the server which may not be available
Solution Approach 1:
The patent segments the authentication system into distributed components: each controller stores its own certificate and permissions locally, and the embedded device maintains a whitelist of authorized controllers. This eliminates the need for a central server while maintaining authentication reliability through local verification of controller identities and permissions.
2Adaptability or versatility
If multiple controllers are allowed to control an embedded device, then system versatility is improved, but security risks increase without centralized authentication
Solution Approach 1:
The patent implements preliminary authentication by requiring controllers to present certificates and obtain permission tokens before being added to the embedded device's whitelist. This pre-verification of controller authenticity and permissions prevents unauthorized access while allowing multiple legitimate controllers to operate the device.
3Ease of operation
If device certificates and permission tokens are stored locally in controllers, then network connectivity to central server is not required, but the complexity of local authentication mechanisms increases
Solution Approach 1:
The patent introduces simplified intermediaries: a standardized certificate format that controllers obtain from manufacturers, and a whitelist mechanism in the embedded device that automatically manages authorized controllers. These intermediaries reduce the complexity of local authentication by providing pre-configured trust relationships rather than requiring complex local verification logic.
Data Source
AI summary
Systems, methods and devices to identify and authenticate controllers of embedded devices without direct connection to a server. The system has a plurality of controllers including a first controller and a second controller. The system has an embedded device configured to obtain a first device certificate from the first controller, obtain a second device certificate from the second controller, extract a first user identifier and a first set of device control privileges from the first device certificate, extract a second user identifier and a second set of device control privileges from the second device certificate, determine whether the second user identifier within the second device certificate is the same as to the first user identifier within the first device certificate, and allow or prevent access to the embedded device by the second controller based on the determining whether the second user identifier is the same as the first user identifier.