File-Level Restore With DHT Routing and Ledger Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized data restoration solutions suffer from long restoration times, high costs, and security vulnerabilities due to data transmissions across wide-area networks.

Innovation Solution

Implementing a decentralized backup and recovery system using distributed ledger technology and edge computing, with distributed hash and ledger tables to manage data storage and restoration across multiple nodes, ensuring secure and efficient data retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If centralized backup and recovery system is implemented, then data restoration can be performed, but restoration times are long and latencies are increased

Engineering Contradiction:
Improvedata restoration capabilityVSAvoidrestoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The centralized backup system is segmented into multiple distributed edge nodes that store backup data locally. Each edge node operates independently to handle restoration requests, eliminating the single-point bottleneck and enabling parallel data retrieval operations, thus significantly reducing restoration time.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transitions from a single-dimensional centralized architecture to a multi-dimensional distributed architecture across geographically dispersed edge nodes. This spatial distribution enables simultaneous data access from multiple locations, reducing latency and restoration time through parallel operations.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If centralized backup and recovery system is implemented, then data restoration can be performed, but costs are high due to data transmissions across wide-area networks

Engineering Contradiction:
Improvedata restoration capabilityVSAvoidtransmission cost
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

Backup data is cached locally at edge nodes close to the data source, enabling restoration operations to be performed using local resources rather than transmitting data across wide-area networks. This localizes the restoration process and eliminates expensive long-distance data transmissions.

Inventive Principle:
Principle #3Local quality

3Reliability

If centralized backup and recovery system is implemented, then data restoration can be performed, but security breaches are increased due to data transmissions

Engineering Contradiction:
Improvedata restoration capabilityVSAvoidsecurity vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The restoration process extracts and performs operations locally at edge nodes, eliminating the need to transmit backup data across networks. By taking the restoration function out of the centralized network environment, the system removes the security vulnerabilities associated with data transmission.

Inventive Principle:
Principle #2Taking out (Extraction)

4Loss of time

If distributed ledger technology and edge computing are used, then restoration times are reduced, but device complexity is increased

Engineering Contradiction:
Improverestoration timeVSAvoidsystem architecture complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

Each edge node is designed as a universal, multi-functional unit that can perform backup, storage, and restoration operations independently. This standardization simplifies the overall system architecture by replacing complex centralized control with multiple simple, identical nodes that follow the same protocols.

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

Data Source

PatentUS12455795B2Efficient and secure file-level restore
Publication Date: 2025.10.28 DELL PROD LP
  • US12455795B2 patent drawing
  • US12455795B2 patent drawing
  • US12455795B2 patent drawing

AI summary

A method for restoring data on a client node in a network includes receiving, by a first node and from the client node, a restoration request for a first version of a requested data asset; querying, by the first node, a distributed hash table (DHT) to identify a second node in a plurality of nodes storing a second version of the requested data asset; verifying, using a distributed ledger table (DLT), that the second version of the requested data asset stored on the second node matches the first version; and initiating, based on the verifying, a data transfer of the second version of the requested data asset from the second node to the client node.