Blockchain E-Key Access with Time-Sensitive Encrypted Codes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data communication systems, particularly those using wireless keys, are vulnerable to hacking and interception, leading to unauthorized access and potential data breaches, as they rely on predetermined radio signals that can be easily copied or hijacked.
Innovation Solution
An e-key system utilizing blockchain technology to generate and validate encrypted codes through a mobile device, key fob, and server, ensuring secure access to properties via Bluetooth communication, with access logs stored in a hyperledger, and employing end-to-end encryption to protect communication data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If predetermined radio signals are used for wireless key communication, then ease of operation is improved, but security against hacking and interception deteriorates
Solution Approach 1:
The patent implements dynamic code generation where the encrypted code changes with each access attempt and is valid only for a specific time window. The code is generated by a mobile device, transmitted to a key fob, and then to the computing device, creating a time-sensitive, one-time use credential that cannot be reused or predicted by hackers.
Solution Approach 2:
The system changes the parameters of the access code by encrypting it with a public key and incorporating a timestamp or validity period. The encrypted code is decrypted by a private key stored in the validation module, creating a cryptographic parameter transformation that ensures security while maintaining ease of use.
2Reliability
If blockchain technology is implemented for access validation, then security and tracking capability are improved, but device complexity increases
Solution Approach 1:
The patent introduces a server as an intermediary that hosts the blockchain and manages the hyperledger. The server handles the complex blockchain operations, including validating access codes and storing access logs, while the mobile device and computing device only perform simpler local operations. This distributes the complexity to a dedicated intermediary system.
Solution Approach 2:
The server performs multiple functions: it hosts the blockchain, validates access codes, stores access logs in the hyperledger, and communicates with both mobile devices and computing devices. This multi-functional approach consolidates complexity into a single universal system rather than distributing it across multiple components.
3Reliability
If encrypted codes with time sensitivity are used, then unauthorized access is prevented, but ease of operation may be reduced due to validation requirements
Solution Approach 1:
The mobile device automatically generates the encrypted code without user intervention. The key fob automatically transmits the code when triggered, and the validation module automatically validates the code against the blockchain. This self-service automation eliminates manual steps for users while maintaining security.
Solution Approach 2:
The system performs preliminary actions by pre-generating encrypted codes with embedded validity periods and storing the corresponding private keys in the validation module before access is needed. The blockchain is pre-configured with the public key for validation, so when access is required, the process is already prepared and can proceed quickly.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
Blockchain-based systems and methods are used to control access to property or information. One system includes a mobile device or other smart device, a key fob or other e-key object, and a server. The mobile device generates an encrypted code and transmits it to the key fob. The key fob transmits the encrypted code to the property and the server updates a log in a hyperledger. The property includes a computing device that validates the encrypted code and grants a key fob user access to the property. Another system includes a server that validates an access key and a first station that transmits an access key to a second station via the server and a satellite. The second station transmits data to the first station via the server and the satellite. The server saves a transmission log in a hyperledger and transmits the access key in response to a request.