Bidirectional Entity Authentication Using Trusted Third Party
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current bidirectional entity authentication methods require entities to possess valid public keys of each other before authentication, which is impractical in communication networks where entities with weak computation capacity struggle with public key calculation, and often cannot access a certificate institution before authentication.
Innovation Solution
A utility bidirectional entity authentication method using a trusted third party, where entities A and B send authentication parameters to the trusted third party, which checks and verifies their legality, and returns verification results, allowing public key management and verification to be centralized, reducing the computational burden on authentication entities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If entities perform bidirectional authentication using conventional methods, then authentication security is maintained, but entities must possess valid public keys of each other in advance and perform complex public key calculations
Solution Approach 1:
The patent introduces a trusted third party (TTP) as an intermediary that manages public key distribution and verification. Instead of entities directly managing each other's public keys, the TTP acts as a mediator that issues certificates and verifies authentication requests, thereby simplifying the public key management process while maintaining security.
Solution Approach 2:
The patent extracts the complex public key management and verification functions from the authentication entities and relocates them to a dedicated trusted third party. This separation allows entities to focus on authentication while the TTP handles the computationally intensive public key operations.
2Reliability
If entities with weak computation capacity perform public key calculations, then authentication can be completed, but the computational burden becomes too heavy for resource-constrained devices
Solution Approach 1:
The trusted third party serves as a computational intermediary that performs the heavy public key calculations on behalf of resource-constrained entities. The TTP has sufficient computational resources to handle these operations, freeing entities with weak computation capacity from performing energy-intensive cryptographic operations.
Solution Approach 2:
The patent implements preliminary action by having entities obtain certificates from the TTP before authentication. The TTP pre-computes and verifies public key pairs, so that during actual authentication, entities only need to present pre-validated certificates rather than performing full public key calculations in real-time.
3Productivity
If entities cannot access certificate institutions before authentication, then network access control cannot be implemented, but this prevents proper authentication setup
Solution Approach 1:
The patent enables preliminary action by allowing entities to obtain certificates from the trusted third party before network access is required. The TTP can issue certificates in advance, so when entities need to access the network, they already possess valid authentication credentials without needing to visit certificate institutions at the moment of access.
Solution Approach 2:
The trusted third party acts as an accessible intermediary that entities can contact for certificate issuance and renewal. This mediator provides a centralized, reliable access point for obtaining authentication credentials, solving the problem of entities being unable to access certificate institutions when needed.
Data Source
Figure 1~2
AI summary
A bidirectional entity authentication method based on the credible third party includes the steps that: entity A receives message 1 sent from entity B including the authentication parameters of said entity B, and sends message 2 to the credible third party TP, said message 2 including the authentication parameters of entity B and the authentication parameters of entity A; entity A receives message 3 sent from said credible third party TP, said message 3 including the checking result after checking that whether said entity A and entity B are legal based on said message 2 by said credible third party TP; entity A gets the authentication result of entity B after authenticating said message 3, and sends message 4 to said entity B to make entity B authenticating based on said message 4 and getting the authentication result of entity A. The Invention simplifies the operation condition of the protocol, reduces the computing capability requirement of the authentication entity, and satisfies the high security requirement of the network device lack of resource.