TLS 1.3 Terminal ID-Based Encryption Key Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
TLS 1.3 cannot implement ID-based encryption in the same manner as TLS 1.2 due to differences in their specifications, requiring a key exchange protocol that can perform mutual authentication using ID-based encryption in one round of communication.
Innovation Solution
A terminal and server system that performs key exchange with mutual authentication using ID-based encryption by transmitting and receiving identifiers and short-term public keys within the ClientHello and ServerHello messages in TLS 1.3, allowing for the generation of a shared key for encrypting subsequent messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If TLS 1.3 specification is used, then communication security is improved, but ID-based encryption cannot be implemented due to specification differences
Solution Approach 1:
The patent modifies the key exchange parameters and message structure within TLS 1.3 to accommodate ID-based encryption. Specifically, it changes how public keys and identifiers are exchanged in ClientHello and ServerHello messages, allowing ID-based encryption to function within the TLS 1.3 framework while maintaining security requirements.
Solution Approach 2:
The patent segments the key exchange process into distinct phases within TLS 1.3 handshake, separating identifier exchange from key generation. This allows the ID-based encryption mechanism to be integrated as a modular component within the TLS 1.3 protocol structure.
2Reliability
If traditional certificate-based TLS is used, then mutual authentication is achieved, but communication overhead increases
Solution Approach 1:
The patent extracts the certificate verification step from the traditional TLS authentication process and replaces it with direct ID-based encryption. By removing the certificate exchange and verification mechanism, the patent reduces communication overhead while maintaining mutual authentication through cryptographic proof of identity.
Solution Approach 2:
The patent introduces ID-based encryption as an intermediary mechanism that directly binds identity to cryptographic keys without requiring certificate authorities. This eliminates the need for certificate exchange and verification, reducing communication overhead while preserving authentication functionality.
3Quantity of substance
If ID-based encryption is implemented in TLS 1.2, then certificate communication is eliminated, but TLS 1.3 compatibility is lost
Solution Approach 1:
The patent adapts the ID-based encryption mechanism to serve multiple TLS versions simultaneously. By designing the implementation to work within TLS 1.3's handshake structure while eliminating certificate communication, the patent achieves both the benefits of ID-based encryption and compatibility with modern TLS security requirements.
Data Source
AI summary
A terminal for performing authentication through TLS 1.3 with a server connected via a communication network. The terminal includes a memory and a processor configured to execute transmitting, to the server, a ClientHello message including a first identifier and a first short-term public key, which are needed to generate a shared key for encrypting a message during a handshake in the TLS 1.3, through key exchange with mutual authentication using ID-based encryption; receiving, from the server, a ServerHello message including a second identifier and a second short-term public key, which are needed to generate the shared key; and generating the shared key using the first identifier, the first short-term public key, the second identifier, and the second short-term public key.