Distributed Ledger Object Integrity Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is no guarantee that objects stored in an untrusted cloud storage system will remain identical or be deleted as intended, leading to disputes between users and cloud providers regarding data integrity and compliance with regulations like GDPR and DMCA, as existing ledger technologies lack assurance on object corruption or deletion.

Innovation Solution

The use of a distributed ledger that attests to the object's integrity through hash signatures and smart contracts, allowing clients and cloud providers to verify transactions and ensure that objects are stored, read, and deleted correctly, with mechanisms for determining fault and providing remedies in case of discrepancies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional ledger technologies are used to store objects in cloud storage, then storage capacity and accessibility are improved, but data integrity assurance and fault determination capability deteriorate

Engineering Contradiction:
Improvestorage capacityVSAvoiddata integrity assurance
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by computing and recording hash values of objects at the time of storage in the distributed ledger. This pre-computed hash serves as a baseline for future integrity verification, allowing the system to proactively establish a reference point before any potential corruption occurs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously verifying object integrity through hash comparison. When an object is retrieved, its hash is computed and compared against the stored hash in the distributed ledger, providing feedback on whether the object has been corrupted or tampered with during storage.

Inventive Principle:
Principle #23Feedback

2Ease of operation

If cloud storage systems allow flexible object deletion, then ease of operation is improved, but accountability and compliance verification deteriorate

Engineering Contradiction:
Improvedeletion flexibilityVSAvoidcompliance verification
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The distributed ledger acts as an intermediary that mediates between the cloud storage system and compliance requirements. It records all deletion operations and maintains verifiable evidence of whether objects were deleted as requested, serving as a neutral third party that both the user and cloud provider can trust.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system records deletion requests and their status in the distributed ledger before actual deletion occurs. This preliminary recording ensures that there is a verifiable trail of what was requested, when it was requested, and whether it was fulfilled, enabling subsequent compliance verification.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If hash verification is performed on every object read, then data integrity is improved, but processing time and system complexity worsen

Engineering Contradiction:
Improvedata integrityVSAvoidverification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of verifying the entire object, the system computes and verifies only a hash value (a compact representation) of the object. This hash acts as a copy or summary of the object's content, allowing rapid verification without processing the full object data.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system transforms the verification process from checking entire objects to checking hash values. By changing the parameter being verified from the full object content to a condensed hash representation, the verification time is dramatically reduced while maintaining integrity assurance.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If distributed ledgers are used to track all object transactions, then accountability is improved, but device complexity and implementation difficulty worsen

Engineering Contradiction:
ImproveaccountabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The distributed ledger serves multiple functions simultaneously: it stores object hashes for integrity verification, records deletion requests for compliance tracking, provides audit trails for accountability, and enables dispute resolution. This multi-functionality reduces the need for separate systems for each purpose.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system enables self-service verification where users can independently verify object integrity and deletion compliance by querying the distributed ledger and comparing hashes, without requiring complex intermediary verification systems or manual audit processes.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11106811B2Object storage for guaranteed content for backup and retention
Publication Date: 2021.08.31 EMC IP HLDG CO LLC
  • US11106811B2 patent drawing
  • US11106811B2 patent drawing
  • US11106811B2 patent drawing

AI summary

Systems, apparatus and methods for managing an object's lifecycle in an object store. A distributed ledger is used to record transactions between a client and an object store. The distributed ledger records the transaction and also attests to the object authenticity. Thus, the transactions can be verified and may assist in resolving issues that arise with respect to the stored objects.