Multi-TTP Identity Verification Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing identity validity verification methods fail to effectively verify identities between entities that trust different trusted third parties, as they require interaction and service provision from the same trusted third party, which is not feasible in all environments.
Innovation Solution
A method involving two trusted third parties (TTPs) where entity A and entity B transmit identity information and random numbers to their respective trusted TTPs, allowing TTP A to verify entity A and TTP B to verify entity B, with subsequent signature verification to confirm identity validity, enabling mutual identity verification between entities trusting different TTPs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single trusted third party TTP is used to provide verification services, then the verification process is simplified and can be completed online, but it cannot accommodate environments where entities trust different TTPs
Solution Approach 1:
The verification system is segmented into multiple independent TTPs (TTP A and TTP B), each responsible for verifying identities within their own trust domain. Entity A trusts TTP A while entity B trusts TTP B, allowing the system to accommodate different trust environments without requiring a single centralized TTP. This segmentation enables the protocol to adapt to distributed trust architectures.
Solution Approach 2:
TTP A acts as an intermediary that receives verification requests from entity A, performs local verification using its own trust credentials, and then forwards the verified identity information to TTP B. This intermediary mechanism allows entities trusting different TTPs to still complete mutual verification by bridging through the respective TTPs.
2Adaptability or versatility
If multiple TTPs are involved in the verification process, then entities trusting different TTPs can be accommodated, but the verification protocol becomes more complex with multiple interaction steps
Solution Approach 1:
The verification processes of TTP A and TTP B are merged into a unified protocol flow where both TTPs cooperate to complete mutual verification. TTP A verifies entity A and TTP B verifies entity B, then they exchange verification results through signed messages. This merging allows the system to support multiple TTPs while maintaining a relatively streamlined interaction sequence.
Solution Approach 2:
Each TTP performs preliminary verification of entity identities before the cross-TTP verification exchange. TTP A pre-verify entity A's identity using its own trust credentials, and TTP B pre-verify entity B's identity. This preliminary action reduces the complexity of the subsequent inter-TTP interaction by ensuring identities are already validated locally.
3Reliability
If inter-TTP interaction and service provision are implemented, then identity validity can be verified between entities trusting different TTPs, but the verification process requires additional message exchanges and signature verifications
Solution Approach 1:
TTP A and TTP B exchange feedback messages containing verification results and digital signatures. TTP A sends a signed verification result for entity A to TTP B, and TTP B sends a signed verification result for entity B to TTP A. This feedback mechanism ensures reliable identity verification by providing cryptographic proof of validity while maintaining efficient bidirectional communication.
Solution Approach 2:
The manual verification process is replaced with automated cryptographic signature verification. Instead of manual identity checking, the system uses digital signatures from TTPs to automatically verify identities. This substitution reduces verification time by enabling rapid cryptographic validation compared to manual processes.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
The invention relates to a multi-TTP-based method and device for verifying whether the identity of an entity is valid. The method comprises: transmitting, by an entity B, a message 1 to an entity A; after receiving the message 1, transmitting, by the entity A, a message 2 to a trusted third party (TTPA); after receiving the message 2, verifying, by the TTPA, whether the identity of the entity A is valid, and transmitting a message 3 to a TTPB; after receiving the message 3, verifying, by the TTPB, whether the identity of the entity B is valid, and transmitting a message 4 to the TTPA; after receiving the message 4, verifying, by the TTPA, a first signature of the TTPB in the message 4, and transmitting a message 5 to the entity A; after receiving the message 5, verifying, by the entity A, a first signature of the TTPA in the message 5, determining whether the identity of the entity B is valid, and transmitting a message 6 to the entity B; and after receiving the message 6, verifying, by the entity B, a second signature of the TTPA, and determining whether the identity of the entity A is valid. The invention realizes verification of validity of the identity of entities trusting different trusted third parties, respectively.