SLA-Based Data Verification Using Blockchain Hashing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge lies in efficiently storing large amounts of data for extended periods while ensuring data integrity and reliability, particularly in environments prone to software and hardware failures, tampering, and varying service levels from third-party storage providers, which complicates the enforcement of service level agreements.
Innovation Solution
A system and method utilizing a blockchain network for remote data storage, where service level agreements (SLAs) specify data verification algorithms and timing parameters, ensuring data integrity by comparing hash values and recording operations, and allowing for trusted or untrusted verification procedures, including periodic or on-demand verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If data is stored in third-party cloud storage services, then storage capacity and accessibility are improved, but data integrity and reliability deteriorate due to varying service levels and potential failures
Solution Approach 1:
The system performs preliminary actions by computing and storing hash values of data files before actual storage operations. These hash values are recorded in a local database and blockchain, creating a baseline for future verification. This preliminary hashing enables later integrity checks without requiring data retrieval, thus maintaining reliability while using third-party storage.
Solution Approach 2:
The patent introduces hash values as an intermediary element between the user and the cloud storage service. Instead of directly trusting the cloud provider, the system uses cryptographic hash values as a mediator to verify data integrity. The hash comparison mechanism acts as an intermediary verification layer that ensures data hasn't been corrupted or tampered with, resolving the trust issue with third-party providers.
2Reliability
If verification procedures are performed frequently to ensure data integrity, then reliability is improved, but system complexity and computational overhead worsen
Solution Approach 1:
The patent extracts the verification logic into a separate, standardized procedure that operates independently from the main storage system. The verification module is taken out as a distinct component that simply compares hash values without needing to understand the underlying storage mechanics. This extraction simplifies the overall system by creating a dedicated verification subsystem with clear, isolated responsibilities.
Solution Approach 2:
The system changes parameters by using cryptographic hash values instead of comparing entire data files during verification. This parameter transformation from full data comparison to hash comparison dramatically reduces computational complexity while maintaining verification accuracy. The hash value serves as a condensed representation that enables efficient integrity checks without the overhead of full data retrieval and comparison.
3Adaptability or versatility
If multiple third-party storage vendors are used to increase storage capacity, then storage versatility is improved, but enforcement of service level agreements worsens due to varying interfaces and rules
Solution Approach 1:
The patent implements universality by creating a unified verification interface that works across multiple storage providers. The hash-based verification mechanism is provider-agnostic, meaning the same verification procedure can be applied regardless of which cloud storage service is used. This universal approach allows the system to manage multiple vendors through a single standardized interface, eliminating the need to handle each provider's unique verification protocols separately.
Data Source
AI summary
A system and method is provided for service level agreement (SLA) based data storage and verification. According to one exemplary aspect, a method includes receiving, from a client device, a request to perform data verification of data relating to a file stored on a remote storage computer; accessing, by a processor, at least one SLA to determine a fault tolerance for the file stored on the remote storage computer; sending, by the processor to the remote storage computer, a request to store k derivatives of the file in the remote storage computer; and transmitting, to the client device, an indication of a location of the k derivatives of the file in the remote storage computer.