Multi-Cloud Backup Addressing Using Blockchain Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge of managing and securing data across multiple cloud platforms, known as multi-cloud platforms, arises due to the risk of a single-point bottleneck when relying on a single cloud platform, which can lead to data loss and security threats.

Innovation Solution

Implementing a data management method that utilizes a blockchain network for decentralized, secure data management by dividing data into blocks and encoding metadata into backup identifiers, ensuring distributed storage and unified addressing across multi-cloud platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If data is stored on a single cloud platform, then storage simplicity is improved, but data security and reliability deteriorate due to single-point bottleneck

Engineering Contradiction:
Improvestorage simplicityVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments data into multiple data blocks and distributes them across multiple cloud platforms. Each cloud node stores only a portion of the data, eliminating the single-point bottleneck while maintaining storage simplicity through automated distribution management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a blockchain network as an intermediary to manage and coordinate data storage across multiple cloud platforms. The blockchain stores metadata and backup identifiers, enabling unified management without requiring direct complex interactions between cloud platforms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If data is distributed across multiple cloud platforms, then data security is improved, but management complexity worsens

Engineering Contradiction:
Improvedata securityVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The blockchain network serves as an intermediary that simplifies management of distributed data. It stores metadata including backup identifiers that map data blocks to their storage locations across cloud platforms, providing a unified interface for data management operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by pre-storing metadata and backup identifiers in the blockchain before actual data retrieval operations. This advance preparation enables efficient data location and recovery without complex real-time coordination between cloud platforms.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If data is divided and stored in distributed manner, then security is improved, but data query efficiency worsens

Engineering Contradiction:
ImprovesecurityVSAvoiddata query efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The blockchain acts as an intermediary that stores indexing information (backup identifiers and metadata) that enables efficient querying of distributed data. The blockchain's distributed ledger structure allows parallel verification and quick location of data blocks across multiple cloud platforms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system pre-computes and stores backup identifiers and metadata in the blockchain before data retrieval operations. This preliminary indexing enables efficient data location without requiring complex real-time searches across distributed cloud storage systems.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260064542A1Data management method and related device
Publication Date: 2026.03.05 HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
  • US20260064542A1 patent drawing
  • US20260064542A1 patent drawing
  • US20260064542A1 patent drawing

AI summary

A data management method includes a client that receives a backup plan configured by a user for to-be-backed-up data; the client divides the to-be-backed-up data into c data blocks based on a quantity of cloud nodes used for backup and a quantity of backup copies, and stores the c data blocks in n cloud nodes on multi-cloud platforms in a distributed manner, where for at least one data block in the c data blocks, the multi-cloud platforms store b backup copies of the at least one data block; and the client provides, for a blockchain network, metadata of the data stored on the multi-cloud platforms, such that the blockchain network encodes the metadata into a backup identifier, and stores the backup identifier, where the backup identifier is used to address the data stored on the multi-cloud platforms.