Client Server Data Transmission with Hash Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional data transmission methods between servers and clients face inefficiencies due to time synchronization errors and lengthy key exchange processes, leading to decreased system efficiency and increased loading.

Innovation Solution

A data transmission method involving the generation of initial values, verification hash codes, and random variables by both clients and servers, ensuring independent connect verifications and preventing duplicate package transmission, thereby enhancing data accuracy and efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional time verification manner is used to verify data transmission, then data accuracy is improved, but time synchronization errors occur and system efficiency decreases

Engineering Contradiction:
Improvedata transmission accuracyVSAvoidsystem efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent applies preliminary action by pre-establishing a trusted relationship between client and server through public key infrastructure (PKI) before actual data transmission. The client obtains the server's public key in advance and stores it locally, eliminating the need for time synchronization and real-time key exchange during data transmission. This preliminary setup resolves the contradiction by enabling accurate verification without the time synchronization errors and efficiency losses of traditional methods.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If encryption key exchange manner is used to verify data transmission, then data security is improved, but handshaking time increases and system loading increases

Engineering Contradiction:
Improvedata transmission securityVSAvoidhandshaking time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the key exchange process from the real-time data transmission flow. Instead of performing encryption key exchange during each communication session, the system separates key establishment into a preliminary phase where the client obtains and stores the server's public key beforehand. This extraction eliminates the time-consuming handshaking process during actual data transmission while maintaining strong security through cryptographic verification using the pre-established keys.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If traditional verification methods are used, then data transmission security is maintained, but duplicate package transmission occurs and accuracy decreases

Engineering Contradiction:
Improvedata transmission securityVSAvoiddata transmission accuracy
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The patent implements feedback through a verification mechanism where the server signs data packets with its private key, and the client verifies each received packet using the pre-stored public key. This feedback loop ensures that every transmitted packet is authentically verified, preventing duplicate or malicious packets from being processed. The verification result feeds back into the transmission process, allowing the client to accept only genuinely authorized packets, thereby eliminating duplicate transmission issues while maintaining security.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9866390B2Data transmitting method suitable to client and server, data transmitting system and data transmitting method for client suitable to transmit and receive data to and from server
Publication Date: 2018.01.09 THROUGHTEK TECH SHENZHEN
  • US9866390B2 patent drawing
  • US9866390B2 patent drawing
  • US9866390B2 patent drawing

AI summary

A data transmitting method suitable to a client and a server is provided. The method includes the following steps. The client generates an initial value. The server generates a first time in response to the initial value. The client generates a second time and a first verification hash code related with the first time and the second time. The server generates a random variable and a second verification hash code related with the first time, the random variable and the first verification hash code. The client generates a first transmitting data and a third verification hash code related with the first transmitting data, the first verification hash code and the second verification hash code. The server generates a first response message and a fourth verification hash code related with the first response message, the second verification hash code and the third verification hash code.