Cloud Data Integrity via Time-Lock Puzzle Replicas

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud storage solutions require users to pre-process and upload multiple replicas of their data, leading to significant overhead and hindering the large-scale integration of remote integrity verification techniques, as users are reluctant due to concerns about data integrity and liability.

Innovation Solution

A method where users transmit only the original data file and authentication tags to the cloud, where configurable time-lock puzzles are computed to generate replicas, allowing for efficient verification of data integrity without pre-processing, using non-parallelizable functions like RSA-based time-lock puzzles and homomorphic authentication tags.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users pre-process and upload multiple replicas of their data to ensure data availability and integrity verification, then data security and reliability are improved, but user overhead and complexity increase significantly

Engineering Contradiction:
Improvedata integrity verificationVSAvoiduser overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables self-service by allowing the cloud storage provider to automatically generate and manage replicas using cryptographic proofs, eliminating the need for users to manually pre-process and upload multiple replicas. The cryptographic verification mechanism automatically ensures data integrity without user intervention in replica management.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Cryptographic proofs serve as an intermediary mechanism between the user and the cloud storage system. Instead of users directly managing replicas, the cryptographic proof system mediates the verification process, allowing users to verify data integrity through mathematical proofs without handling the complex task of replica management.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If users upload multiple pre-processed replicas to verify data integrity remotely, then data availability is ensured, but the time and computational resources required increase

Engineering Contradiction:
Improvedata availabilityVSAvoidpre-processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary cryptographic processing on the original data file before upload, generating authentication tags and cryptographic proofs in advance. This preliminary action ensures that data availability and integrity can be verified later without requiring time-consuming pre-processing of multiple replicas at upload time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of requiring users to create and upload multiple physical copies of their data, the system uses cryptographic copying where a single original file with cryptographic proofs enables the generation and verification of multiple logical replicas through mathematical transformations, significantly reducing upload time and computational overhead.

Inventive Principle:
Principle #26Copying

3Reliability

If cloud providers implement full replication to guarantee service availability, then service reliability is improved, but storage costs and system complexity increase

Engineering Contradiction:
Improveservice availabilityVSAvoidstorage redundancy
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system changes the parameter of data representation by using cryptographic transformations and proofs instead of storing multiple full data copies. This parameter change allows the system to maintain service availability guarantees while significantly reducing the quantity of stored data through mathematical representations rather than physical replication.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10873631B2Method for storing data in a cloud and network for carrying out the method
Publication Date: 2020.12.22 NEC CORP
  • US10873631B2 patent drawing

AI summary

A method for storing data in a cloud includes receiving at least one data file to be stored together with a predefined number t of replicas of the at least one data file within the cloud, at least one authentication tag corresponding to the at least one data file and t functions that are configurable to take at least a predefined time to compute; storing the at least one data file within the cloud; computing t solutions of the t functions within the cloud; generating the t replicas of the at least one data file based on the t solutions of the t functions and the at least one data file within the cloud, wherein each of the t functions is used for at least one of the t replicas of the at least one data file; and storing the t replicas within the cloud.