Cloud-Based API Deployment Using Segmented Distributed Ledger Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed ledger systems face increased resource usage and decreased performance due to decentralization, storage, bandwidth, and computing power requirements, especially as the database size grows.

Innovation Solution

A cloud-based system deployment using a distributed ledger system that employs smart contracts to manage system coalitions, API deployments, and data writes to a distributed ledger, optimizing resource use and enhancing security and performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If decentralization and consensus-based validation are implemented in distributed ledger systems, then data integrity and security are improved, but resource usage increases and performance decreases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system segments the distributed ledger network into multiple node types (full nodes, light nodes, and cloud-based nodes) with different functional responsibilities. Full nodes maintain complete copies of the blockchain for security and validation, while light nodes and cloud-based nodes access only necessary data through APIs, reducing their resource requirements and improving overall system performance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces cloud-based nodes as intermediaries between traditional distributed ledger participants and the blockchain network. These cloud nodes handle resource-intensive operations such as data storage, synchronization, and complex computations, allowing other participants to access blockchain services without directly bearing the full resource burden, thus improving system performance while maintaining data integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If the size of the decentralized database grows, then more data and functionality are available, but storage, bandwidth, and computing power requirements increase

Engineering Contradiction:
Improvedatabase sizeVSAvoidcomputing power requirement
Core Design Contradiction:
Quantity of substanceVSUse of energy by moving object

Solution Approach 1:

The system implements local quality by allowing different nodes to store and process different portions of the blockchain data based on their capabilities and needs. Full nodes store complete blockchain histories, while light nodes and applications only store and access the specific data blocks and transactions relevant to their operations, reducing overall computing power requirements while maintaining access to the full database functionality.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent employs copying strategies where critical blockchain data is replicated across multiple cloud-based nodes and made accessible through centralized API endpoints. This allows applications to access blockchain data without each application independently maintaining full copies of the database, reducing redundant computing power consumption while preserving data availability.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If decentralization is implemented, then no central administrator is needed, but system complexity and coordination overhead increase

Engineering Contradiction:
Improvedecentralized controlVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces multi-functional smart contract modules that can perform various blockchain operations (data validation, transaction routing, resource allocation) within a single decentralized framework. These universal modules reduce system complexity by consolidating multiple coordination functions into standardized, reusable components that maintain decentralized control while simplifying overall system architecture.

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

Data Source

PatentUS12354109B2Deploying a cloud-based system using a distributed ledger
Publication Date: 2025.07.08 AMERICAN EXPRESS TRAVEL RELATED SERVICES CO INC
  • US12354109B2 patent drawing
  • US12354109B2 patent drawing
  • US12354109B2 patent drawing

AI summary

Systems and methods for the deployment of an application programming interface to cloud-based systems using a distributed ledger are disclosed. The system may include a cloud provider system and a distributed ledger. The cloud provider system may be configured to deploy cloud-based systems and/or APIs to enable one or more participant systems to leverage cloud-based resources. The distributed ledger may record events, functionalities, and operations from the cloud provider system, the participant systems, and the deployed cloud-based systems and APIs.