Decentralized Node Authentication for Secure Device Authorization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing device authorization systems face challenges in securely and efficiently authenticating client devices, leading to potential misappropriation and resource inefficiencies.
Innovation Solution
A decentralized node database system is implemented, assigning roles to nodes randomly and using a multi-layer authentication process involving certificate generator, access token generator, hash code generator, and encryption key generator nodes to securely authenticate client devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized authorization system is used, then device authentication can be managed centrally, but security vulnerabilities and single point of failure risks increase
Solution Approach 1:
The system divides the centralized authorization function into multiple independent nodes (certificate generator nodes, access token generator nodes, hash code generator nodes, encryption key generator nodes) distributed across the network. Each node performs a specific authentication function, eliminating the single point of failure while maintaining centralized control through cryptographic hashing and validation mechanisms.
Solution Approach 2:
The patent introduces a decentralized node database as an intermediary between client devices and resource servers. This intermediary validates client credentials, generates authorization mechanisms, and manages encryption keys without requiring direct trust between clients and servers, thereby enhancing security while distributing system complexity.
2Reliability
If multiple authentication layers are implemented, then authentication security improves, but processing time and computational resources increase
Solution Approach 1:
The system performs preliminary authentication actions by validating client credentials against the decentralized node database before resource access is granted. Certificate generator nodes pre-issue digital certificates, and encryption key generator nodes pre-generate cryptographic keys, so that during actual resource access, only lightweight verification is needed rather than full re-authentication.
Solution Approach 2:
The patent implements partial authentication by having different nodes perform different levels of validation based on the specific access requirement. Not all authentication layers are executed for every request - the system selectively engages certificate validation, token generation, or hash code verification depending on the resource access level, reducing unnecessary computational overhead.
3Reliability
If decentralized node database is used, then system reliability and security improve, but device complexity and implementation difficulty increase
Solution Approach 1:
The decentralized node database is designed as a universal platform that handles multiple authentication functions through standardized interfaces. Certificate generator nodes, access token generator nodes, hash code generator nodes, and encryption key generator nodes all communicate using the same protocol, allowing client devices to interact with the system uniformly regardless of which specific node is involved, thereby simplifying implementation.
Solution Approach 2:
The system uses cryptographic copying and hashing to distribute trust across multiple nodes. Instead of requiring unique authentication mechanisms at each node, the patent copies the same cryptographic validation logic across all nodes, allowing them to function as interchangeable replicas that maintain system reliability while reducing implementation complexity through code reuse.
Data Source
AI summary
Systems, computer program products, and methods are described herein for authorizing devices using a decentralized node database. The present disclosure is configured to initiate an authorization request to a resource server, wherein the authorization request comprises encrypted client credentials, and wherein the client credentials are transmitted from a client device; assign roles to nodes, wherein the roles are assigned randomly to the nodes; validate, using the nodes, the client credentials; create a smart contract, wherein the smart contract comprises the authorization request and an authorization mechanism; generate a side chain, wherein the side chain comprises a hash code, the authorization request, and the authorization mechanism; validate, using the hash code, the client device; and generate an encryption key, wherein the client device uses the encryption key to access the resource server.


