Handshake-Free Encrypted Communication Channel
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication protocols, such as HTTPS and TCP, require handshakes that introduce delays, particularly noticeable in mobile networks with long round-trip times, which degrade the user experience by adding unnecessary steps before initiating encrypted request-response interactions.
Innovation Solution
The proposed solution involves a handshake-free encrypted communication method that leverages an ongoing communication relationship between devices to cache encryption secrets, using symmetric encryption for bulk communication and asymmetric encryption for initial key exchange, eliminating the need for handshake processes by establishing a secure channel without the four-message handshake typically required in HTTPS.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a four-message handshake process is used to establish secure communication (as in HTTPS/TCP), then security and reliability are improved, but communication delay increases significantly
Solution Approach 1:
The patent applies preliminary action by establishing the secure communication channel before the actual data transfer begins. The four-message handshake process (SYN, SYN-ACK, ACK, and application-layer handshake) is executed in advance to set up encryption contexts, security associations, and communication state, allowing subsequent data transmission to occur without repeated handshakes. This preliminary establishment of security infrastructure resolves the contradiction by front-loading the time cost into an initial setup phase rather than having it recur with each communication event.
Solution Approach 2:
The patent uses copying by reusing the security context and encryption parameters established during the initial handshake for subsequent communication sessions. Instead of creating new security associations each time, the system copies and reuses the existing security context, encryption keys, and communication state, thereby eliminating the need for repeated handshakes while maintaining security. This copying approach significantly reduces communication delay while preserving the security guarantees.
2Reliability
If multiple handshake messages are exchanged to establish encryption keys, then secure communication is achieved, but the number of network round-trips increases
Solution Approach 1:
The patent merges the key exchange process with the communication establishment process by combining the TLS handshake, TCP handshake, and application-layer protocol handshake into a single integrated sequence of four messages. Rather than performing separate key exchange, connection establishment, and protocol negotiation in distinct phases, the system merges these functions into one coordinated handshake process that accomplishes multiple objectives simultaneously. This merging reduces the total number of round-trips required while maintaining secure communication.
Solution Approach 2:
The patent ensures continuity of useful action by maintaining the secure communication channel established during the handshake for the entire duration of the data transfer session. The encryption context and security associations created during the initial four-message handshake remain active and reusable, allowing continuous encrypted communication without interruption or repeated key exchange. This continuity eliminates idle periods and repeated setup phases, thereby improving communication speed while preserving security.
Data Source
AI summary
Techniques for handshake-free encrypted communication are described. An apparatus may comprise a reception component and a precomputation component. The reception component may be operative to receive a priming message from a client using a stateless network protocol, to establish a communication channel to the client, and to transmit a response to the priming message over the communication channel to the client. The precomputation component may be operative to determine the response in response to the reception of the priming message from the client. Other embodiments are described and claimed.