Distributed Blockchain Ledger for Software Component Ecosystem Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing computing ecosystems for sharing software components face challenges with centralized control, including high infrastructure costs, scalability issues, and the need for robust management, which can be inefficient and costly.

Innovation Solution

A distributed blockchain ledger system is used to manage and secure transactions within a software component ecosystem, allowing for decentralized control, verification, and updating of software components without a central controller, through nodes that run software for maintaining the blockchain and propagating transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized control system is used to manage software component ecosystems, then transaction verification and ecosystem control can be efficiently implemented, but infrastructure costs and management complexity increase significantly

Engineering Contradiction:

Improvetransaction verificationVSAvoidmanagement infrastructure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the centralized control function into distributed control nodes across the ecosystem. Each participant runs a catalog instance that maintains a local copy of the blockchain ledger, eliminating the need for a single centralized management infrastructure while maintaining transaction verification capabilities through distributed consensus.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system enables self-service through automated transaction verification using cryptographic signatures. Participants can independently verify transactions against the blockchain ledger without requiring centralized authentication, and the system automatically handles transaction propagation and ledger updates across all nodes.

Inventive Principle:

Principle #25Self-service

2Reliability

If centralized management infrastructure is implemented, then ecosystem control and transaction monitoring are possible, but scalability and disaster recovery become problematic

Engineering Contradiction:

Improveecosystem controlVSAvoidscalability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent divides the ecosystem control function across multiple independent nodes rather than relying on a single centralized system. Each node maintains autonomy and can operate independently, allowing the ecosystem to scale by simply adding more nodes without creating bottlenecks or single points of failure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system changes the fundamental parameter of control from centralized to distributed architecture. This transformation enables the ecosystem to dynamically adapt to varying scales by adjusting the number of participating nodes, while maintaining consistent control mechanisms through the shared blockchain ledger.

Inventive Principle:

Principle #35Parameter changes

3Device complexity

If a distributed blockchain ledger system is used, then infrastructure costs and management overhead are reduced, but transaction verification complexity increases

Engineering Contradiction:

Improvemanagement infrastructureVSAvoidtransaction verification

Core Design Contradiction:

Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent uses cryptographic copying of transaction data across the blockchain ledger. Each transaction is replicated and stored in identical form across all distributed nodes, allowing verification through simple comparison of copies rather than complex analysis. The cryptographic signatures serve as verifiable copies that can be independently checked by any node.

Inventive Principle:

Principle #26Copying

4Productivity

If centralized control is implemented, then transaction processing can be efficiently managed, but the cost of staffing and operation increases

Engineering Contradiction:

Improvetransaction processingVSAvoidoperational cost

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The system replaces paid centralized management staff with automated self-service mechanisms. Transaction processing is handled automatically by the distributed nodes using pre-programmed verification logic and cryptographic validation, eliminating the need for human operators while maintaining processing efficiency through automated consensus protocols.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS11775285B2System and method for managing a public software component ecosystem using a distributed ledger

Publication Date: 2023.10.03 ORACLE INT CORP

AI summary

Embodiments include systems and methods that facilitate implementation of software component ecosystems using a distributed ledger, e.g., as implemented in part as a distributed blockchain, that is maintained by ecosystem full nodes, called catalog instances. Various registration transactions, e.g., developer registrations, namespace registrations, usage registrations, and so on, may be added to the distributed blockchain by one or more catalog instances. Adding blocks to the blockchain may including using a tree hash of tending transactions to generate a block hash for the new block. The new block also includes or incorporates a hash of an immediately prior block.