Partial Data Verification With Merged Collective Fingerprints

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data verification systems face challenges in verifying partial data without sending the entire initial data set, leading to increased security risks and storage space consumption.

Innovation Solution

A data verification system that uses a trusty collective data fingerprint to verify partial data by generating an unrequested data fingerprint and merging it with a requested data fingerprint, eliminating the need for storing all data fingerprints.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the provider end sends the entire initial data to the receiver end for verification, then the receiver end can verify data correctness using collective data fingerprint, but the risk of data disclosure increases and storage space consumption increases

Engineering Contradiction:

Improvedata verification correctnessVSAvoiddata disclosure risk

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts only the necessary portion of data (requested part) from the complete initial data cluster, rather than transmitting the entire dataset. The provider end computer apparatus separates the data cluster into requested and unrequested parts, processes only the unrequested part to generate its fingerprint, and transmits both the requested data and the unrequested data fingerprint to the receiver end for verification.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the data cluster into two distinct parts: the requested part (which is transmitted in plaintext) and the unrequested part (which is processed to generate a fingerprint). This segmentation allows the receiver end to verify the integrity of the requested data without exposing the unrequested data, thereby reducing data disclosure risk while maintaining verification reliability.

Inventive Principle:

Principle #1Segmentation

2Reliability

If all data fingerprints of sub-data are stored at the third party for verification, then complete data verification is enabled, but storage space consumption increases significantly

Engineering Contradiction:

Improvedata verification capabilityVSAvoidstorage space consumption

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent eliminates the requirement for the third party to store all data fingerprints by extracting and processing only the unrequested part data on-the-fly. The provider end computer apparatus generates the unrequested data fingerprint dynamically when a verification request is received, rather than pre-storing all possible fingerprints, thereby significantly reducing storage space consumption at the third party.

Inventive Principle:

Principle #2Taking out (Extraction)

3Object-affected harmful factors

If the provider end sends only the requested part of data, then data exposure risk is reduced, but the receiver end cannot verify the correctness of the received data

Engineering Contradiction:

Improvedata exposure riskVSAvoiddata verification capability

Core Design Contradiction:

Object-affected harmful factorsVSReliability

Solution Approach 1:

The patent introduces the unrequested data fingerprint as an intermediary element that enables verification without requiring transmission of the unrequested data itself. The provider end generates this fingerprint from the unrequested part, and the receiver end uses it to verify the integrity of the requested data by comparing it with a fingerprint generated from the complete data cluster, thus maintaining verification capability while minimizing data exposure.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12445304B2Data verification system

Publication Date: 2025.10.14 AUTHME

AI summary

A data verification system includes a provider-end apparatus and a request-end apparatus. The provider-end apparatus receives a request of data from the request-end apparatus, retrieves a data cluster designated in the request of data, executes a first fingerprint process on an unrequested part of the data cluster to obtain an unrequested data fingerprint, and returns a requested part of the data cluster and the unrequested data fingerprint to the request-end apparatus. The request-end apparatus retrieves a trusty collective data fingerprint of the data cluster, executes the first fingerprint process on the requested part for obtaining a request data fingerprint, executes a merging process on the unrequested data fingerprint and the request data fingerprint for obtaining a merges collective data fingerprint, and determines that the requested part is correct when the merged collective data fingerprint is consistent with the trusty collective data fingerprint.