Data Integrity Verification via Payload Hashing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data integrity is compromised during transit to storage due to malicious activities or errors, leading to potential loss of access to data.

Innovation Solution

Generating and including integrity verification data with the payload allows for identification of modifications after the data leaves the application's control, enabling verification processes to ensure data integrity before storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is transmitted to storage without integrity verification, then storage operations are fast and simple, but data integrity cannot be ensured and modified data may be stored

Engineering Contradiction:
Improvedata integrityVSAvoidverification process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system generates integrity verification data (such as hash values) for the payload before transmission to storage. This preliminary action ensures that when data arrives at storage, the verification can be performed efficiently without complex real-time analysis, as the expected integrity state is already established and can be compared against the received data

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where integrity verification data is generated from the payload, transmitted along with it, and then used to verify the payload upon receipt at storage. This closed-loop feedback ensures that any modifications to the payload during transmission can be detected by comparing the verification data against the actual received payload

Inventive Principle:
Principle #23Feedback

2Reliability

If integrity verification data is generated and transmitted with payload, then data integrity can be verified, but transmission data volume increases

Engineering Contradiction:
Improvedata integrityVSAvoiddata transmission volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system extracts only the essential integrity verification data (such as hash values or checksums) from the payload and transmits this condensed representation alongside the payload. This extraction approach provides sufficient verification capability without transmitting the entire payload twice, thus minimizing the additional data volume required for integrity verification

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system transforms the payload into a different parameter representation (such as converting data into hash values or checksums) that is much smaller in size but retains the essential integrity verification properties. This parameter transformation allows verification to be performed on a compact representation rather than requiring transmission of the full payload for verification purposes

Inventive Principle:
Principle #35Parameter changes

3Reliability

If verification process checks all data before storage, then data integrity is ensured, but storage processing time increases

Engineering Contradiction:
Improvedata integrityVSAvoidstorage processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs the computationally intensive verification calculations in advance, generating integrity verification data (hash values, checksums) before the payload is transmitted to storage. This preliminary computation shifts the processing burden to before transmission, allowing the actual storage operation to use simple comparison operations rather than complex verification algorithms, thus minimizing storage processing time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system performs a focused verification on specific critical portions of the data (such as header information or key fields) rather than exhaustive verification of every byte of the payload. This partial verification approach provides sufficient integrity assurance for the most important data elements while significantly reducing the time required for the verification process compared to checking the entire payload

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12204767B2System and method for managing data storage to identify undesired data modification
Publication Date: 2025.01.21 DELL PROD LP
  • US12204767B2 patent drawing
  • US12204767B2 patent drawing
  • US12204767B2 patent drawing

AI summary

Methods and systems for managing data storage are disclosed. The storage of data may be managed by implementing a framework for checking whether payloads requested for storage have been modified prior to storage. The checks may be performed using integrity verification data that is based on corresponding payloads. The payloads and integrity verification data may be generated by an application, and both may be directed to storage. Once received, the storage may perform the checks using the integrity verification data.