Identity-Based Authenticated Key Agreement Protocol
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing identity-based encryption (IBE) protocols face a key escrow issue where the Key Generation Function (KGF) can decrypt all exchanges, compromising security if compromised, and require large-scale public key infrastructure (PKI), which is challenging to manage.
Innovation Solution
An improved identity-based authenticated key agreement protocol using public key encryption, where each party computes a random key component and encrypts it with the other party's public key, ensuring that only the parties involved can decrypt and agree on a session key without relying on PKI, thus avoiding key escrow and providing perfect forward and backward secrecy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If Identity Based Encryption (IBE) protocols are used to simplify PKI requirements, then the complexity of public key infrastructure is reduced, but the Key Generation Function becomes a key escrow server that can decrypt all exchanges
Solution Approach 1:
The patent extracts the key escrow functionality from the Key Generation Function by introducing a separate Key Recovery Agent. The KGF generates private keys without retaining decryption capability, while the KRA is specifically authorized to recover keys under controlled conditions. This separation eliminates the inherent key escrow problem in traditional IBE while maintaining key recovery capabilities.
Solution Approach 2:
The patent introduces a Key Recovery Agent as an intermediary between the Key Generation Function and the parties needing key recovery. This mediator handles key recovery requests without having access to all private keys, providing a controlled mechanism for key recovery while preventing unauthorized decryption of all exchanges.
2Adaptability or versatility
If traditional public key protocols are used, then flexibility in communication is improved, but the requirement for certificates and large scale public key infrastructure becomes challenging
Solution Approach 1:
The patent makes identities (such as email addresses or domain names) serve multiple functions: they act as both the public key and the certificate authority reference. This universal use of identities eliminates the need for separate certificate infrastructure while maintaining the flexibility of public key protocols.
Solution Approach 2:
The patent extracts the certificate verification function from the traditional PKI model by allowing parties to directly use their identities as public keys. This eliminates the need for external certificate authorities and large-scale PKI infrastructure while preserving communication flexibility.
Data Source
Figure 1
Figure 2
AI summary
A key agreement protocol between a first party and a second party comprises the following steps from the first party perspective. An encrypted first random key component is sent to the second party, the first random key component being encrypted using a public key of the second party in accordance with an identity based encryption operation. An encrypted random key component pair is received from the second party, the random key component pair being formed from the first random key component and a second random key component computed at the second party, and encrypted at the second party using a public key of the first party in accordance with the identity based encryption operation. The second random key component, in encrypted form, is sent to the second party, the second random key component being encrypted using the public key of the second party. A key for use in subsequent communications between the first party and the second party is computable at both the first party and the second party from the first and second random key components.