Blockchain-Based Synchronization for Distributed Cloud Components

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed cloud computing environments, status and synchronization discrepancies among multiple components lead to asynchronous data replication, resulting in downtime and service issues, as existing technologies lack efficient methods to accurately and securely synchronize data across interdependent cloud networks.

Innovation Solution

A computer-implemented method and system that monitors transactions in a blockchain to determine the status of component members, identifies discrepancies, and updates the blockchain to resolve these discrepancies, ensuring synchronized data replication through multi-level blockchain ledgers and secure authorization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is replicated across multiple component members in a distributed computing environment, then data availability and service continuity are improved, but synchronization discrepancies and status inconsistencies occur leading to downtime

Engineering Contradiction:
Improveservice continuityVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system continuously monitors the status of replicated data across component members and feeds this information back to detect synchronization discrepancies. When discrepancies are detected, the system triggers automated resolution processes that update affected components, thereby maintaining service continuity while minimizing downtime caused by status inconsistencies.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary mechanism that mediates between replicated data instances across different component members. This intermediary facilitates coordinated updates and resolves synchronization conflicts by acting as a central coordinator that ensures all components reach consensus on data status, thus preventing downtime while maintaining data availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If existing synchronization methods are used, then data replication occurs, but accurate and secure synchronization across interdependent cloud networks cannot be achieved

Engineering Contradiction:
Improvedata synchronization accuracyVSAvoidsynchronization security
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent employs blockchain technology as an intermediary layer that ensures both accurate and secure synchronization. The blockchain acts as a trusted mediator that records and verifies data replication events, providing cryptographic proof of data integrity and authorization. This intermediary mechanism simultaneously achieves accurate data replication and secure authorization across interdependent cloud networks.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system replaces traditional mechanical or protocol-based synchronization mechanisms with blockchain-based cryptographic verification. This substitution eliminates the need for complex trust relationships and manual synchronization protocols, providing both accurate data replication and secure authorization through cryptographic proofs inherent in blockchain technology.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS10897499B2Resolving status and synchronization discrepancies in a distributed computing environment using blockchains
Publication Date: 2021.01.19 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10897499B2 patent drawing
  • US10897499B2 patent drawing
  • US10897499B2 patent drawing

AI summary

A computer-implemented method including: monitoring, by a computing device, transactions in a blockchain, wherein the transactions are associated with a set of data replicated across a plurality of component members in a distributed computing environment; determining, by the computing device, a status of each of the cloud component members based on the monitoring; determining, by the computing device, a discrepancy in the status between a first component member of the plurality of component members, and a second component member of the plurality of component members; resolving, by the computing device, the discrepancy in the status; and updating, by the computing device, the blockchain to reflect the resolved discrepancy.