TLCP Handshake Certificate Compression for Faster Identity Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In weak network environments, the transmission of certificates during a TLCP handshake process consumes significant bandwidth and time, leading to reduced negotiation efficiency.

Innovation Solution

Implementing a certificate compression function in the handshake process, where the client and serving end support certificate compression, allowing for the transmission of compressed certificates and subsequent decompression for identity verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a certificate is transmitted during the TLCP handshake process, then identity verification can be performed, but bandwidth consumption increases and negotiation efficiency decreases

Engineering Contradiction:
Improveidentity verificationVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts the essential verification information from the complete certificate by identifying and retaining only the public key and certificate signature, while removing redundant components such as version information, serial number, issuer details, and validity period. This extraction approach maintains identity verification capability while significantly reducing the data transmission volume during the TLCP handshake process.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If a certificate is transmitted during the TLCP handshake process, then identity verification can be performed, but the handshake time increases

Engineering Contradiction:
Improveidentity verificationVSAvoidhandshake time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential verification elements (public key and certificate signature) from the complete certificate, creating a streamlined verification data structure. This extraction eliminates the need to transmit and process redundant certificate information, thereby reducing the time required for the handshake process while maintaining secure identity verification.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If a complete certificate is transmitted, then comprehensive verification information is provided, but data transmission volume increases

Engineering Contradiction:
Improveverification information completenessVSAvoiddata transmission volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies extraction by identifying and removing redundant information from the complete certificate structure, retaining only the public key and certificate signature which are sufficient for verification. This reduces data transmission volume from the full certificate size to just the essential verification components.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies local quality by assigning different levels of importance to different parts of the certificate data. The public key and certificate signature are identified as high-priority elements that must be transmitted for verification, while other parts of the certificate are deemed lower priority or redundant for the specific verification purpose, allowing selective transmission.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20250330494A1Identity verification method for handshake process for TLCP protocol
Publication Date: 2025.10.23 ALIPAY (HANGZHOU) INFORMATION TECH CO LTD
  • US20250330494A1 patent drawing
  • US20250330494A1 patent drawing
  • US20250330494A1 patent drawing

AI summary

One or more embodiments of this specification provide an identity verification method in a handshake process for a TLCP protocol. The method includes: A client sends a client hello message to a serving end. The client hello message includes a certificate compression function field, and the certificate compression function field indicates that the client supports a certificate compression function. The serving end sends a serving end certificate message to the client when the serving end receives the client hello message. The serving end certificate message includes a compressed serving end certificate. In response to the serving end certificate message, the client decompresses the compressed serving end certificate included in the message, and performs identity verification on the serving end based on an obtained decompressed serving end certificate.