Secure Data Transmission via Intermediary Session Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for secure data transfer between devices, particularly for authorization purposes, fail when direct connections or asymmetric encryption are not possible due to resource or computing power limitations, leading to insecure data exchanges.
Innovation Solution
A method involving a first device generating a session ID based on a client ID, sending it to a second device, which processes it with a challenge and sends it back to the first device, which then forwards it to a third device for authenticity verification, generating a second session ID, and using symmetric encryption to ensure secure data transfer without requiring direct or asymmetric encryption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If asymmetric encryption is used for secure data transfer, then security is improved, but device complexity and computing power requirements increase
Solution Approach 1:
The patent introduces a third device as an intermediary that performs the complex asymmetric encryption operations. The first device only needs to generate and transmit simple session IDs, while the third device handles the cryptographic verification and key exchange, thereby reducing the computing burden on the first device while maintaining security.
Solution Approach 2:
The authentication process is divided into multiple segments: the first device generates session IDs, the second device processes challenges, and the third device verifies authenticity and manages keys. This segmentation allows each device to perform only the operations it needs, reducing overall system complexity while maintaining security.
2Reliability
If direct connections are used for data transfer, then security is improved through encryption, but adaptability decreases when resources are limited
Solution Approach 1:
The third device acts as a mediator that enables secure communication without requiring direct encrypted connections between the first and second devices. The third device receives session IDs from the first device, verifies them using asymmetric encryption, and issues challenge-response pairs, allowing resource-constrained devices to participate in secure communications.
Solution Approach 2:
The third device serves multiple functions: it generates session IDs, verifies authenticity using asymmetric encryption, manages challenge-response protocols, and coordinates key exchange. This multi-functionality allows the system to maintain security across diverse device configurations without requiring each device to have full cryptographic capabilities.
3Reliability
If multiple services are accessed through a third device, then authorization verification is improved, but connection security becomes vulnerable to intermediation
Solution Approach 1:
The patent uses the third device as a trusted intermediary that verifies authorization through challenge-response protocols. The third device receives session IDs, generates challenges, and verifies authenticity before allowing resource access. This controlled intermediation maintains security by ensuring that the third device actively verifies credentials rather than passively relaying data.
Solution Approach 2:
The third device performs preliminary authentication actions by verifying session IDs and managing challenge-response pairs before allowing any resource access. This preliminary verification ensures that only authenticated devices can access resources, preventing unauthorized access while maintaining secure intermediation.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
The invention relates to a method comprising: by a first device generating a first session ID based on a client ID and sending the first session ID to a second device via a first connection; by the second device applying a first key to the first session ID and a challenge, storing the challenge, and sending the data processed with the first key to the first device via the first connection; by the first device sending the processed data and the client ID to a third device via a second connection;The third device verifies the authenticity of the processed data using the first key, generates a second session ID based on the client ID, compares the second session ID with the first session ID, checks whether a resource is released, generates a second key, encrypts the second key with the first key, applies the first key to the challenge and the encrypted second key, and sends the data processed with the first key and the unencrypted second key to the first device via the second connection; the first device sends the processed data to the second device via the first connection;The second device verifies the authenticity of the processed data by applying the first key, comparing the challenge with the stored challenge, decrypting the second key, encrypting a resource with the second key, and sending the resource to the first device via the first connection.