Token-Based Authentication Reducing Handshake Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional methods for establishing secure communication connections in mobile environments require numerous round-trip communications, leading to delays and compromising security by often forgoing encryption and authentication to speed up connections, making users vulnerable to cyber threats.

Innovation Solution

A system that enables the establishment of an authenticated and encrypted communication connection between devices with minimal round-trip handshaking, utilizing a token with an extended lifetime to reduce the number of required communications, allowing for either one or two round-trips depending on recent communication activity, and employing a session key generated using a shared secret and encryption schemes like RC4 for secure data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional authentication and encryption methods are used, then security is improved, but connection establishment time increases due to multiple round-trip communications

Engineering Contradiction:
ImprovesecurityVSAvoidconnection establishment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary authentication by providing a token or challenge to the client device before the actual connection is established. This token remains valid for a specified duration, allowing the client to initiate connections without requiring full authentication handshaking each time. The server performs the authentication work in advance by issuing the token, which the client can then use to quickly establish subsequent connections within the token's validity period.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple round-trip communications are performed for authentication, then authentication reliability is improved, but communication overhead increases

Engineering Contradiction:
Improveauthentication reliabilityVSAvoidcommunication overhead
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts the authentication challenge and response mechanism from the regular connection establishment process. Instead of performing complete mutual authentication handshaking for every connection, the system separates the authentication phase (where the server issues a token) from the connection phase (where the client uses the token). This extraction reduces the communication overhead of subsequent connections while maintaining authentication reliability through the token validation mechanism.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If encryption is maintained during connection establishment, then security is improved, but processing complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidprocessing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by establishing encryption keys and authentication credentials before the actual data transmission begins. The token issued to the client contains or enables the encryption credentials needed for secure communication. Once the token is validated, the encryption framework is already in place, reducing the processing complexity during active communication while maintaining security throughout the connection lifecycle.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10841106B1Combined authentication and encryption
Publication Date: 2020.11.17 WHATSAPP LLC
  • US10841106B1 patent drawing
  • US10841106B1 patent drawing
  • US10841106B1 patent drawing

AI summary

A system and methods are provided for establishing an authenticated and encrypted communication connection between two devices with at most two round-trip communications. During establishment of an initial authenticated, encrypted communication connection (or afterward), a first device (e.g., a server) provides the second device (e.g., a client) with a token (e.g., a challenge) that lives or persists beyond the current connection. After that connection is terminated and the second device initiates a new connection, it uses the token as part of the handshaking process to reduce the necessary round-trip communications to one.