Blockchain Software Library Metadata Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing software library dependencies and tracking usage across multiple teams in a decentralized manner is challenging due to trust issues and deployment complexities, especially when libraries are consumed by disparate organizations.

Innovation Solution

A blockchain system is used to manage software libraries through metadata stored on a blockchain, utilizing smart contracts for notarization, access control, and reward determination via a machine learning model, ensuring authenticity and compensating library owners based on usage and licensing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used to manage software library metadata, then ease of management and control is improved, but trust and security among untrusting organizations deteriorates

Engineering Contradiction:
Improveease of managementVSAvoidtrust among organizations
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces blockchain technology as an intermediary between organizations to manage software library metadata. The blockchain serves as a neutral, decentralized mediator that all organizations can trust equally, eliminating the need for any single organization to control the metadata while maintaining security and trust among untrusting parties.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a decentralized system is used to manage software library metadata, then trust and security among untrusting organizations is improved, but device complexity and deployment difficulty increases

Engineering Contradiction:
Improvetrust among organizationsVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the metadata management system into distinct blockchain components: metadata storage, chaincode execution for access control, and automated reward distribution. This segmentation allows each component to be independently managed and understood, reducing overall system complexity despite the decentralized nature of the solution.

Inventive Principle:
Principle #1Segmentation

3Reliability

If blockchain is used to store software library metadata, then authenticity and trust are improved, but storage efficiency and data redundancy increase

Engineering Contradiction:
Improveauthenticity of metadataVSAvoidstorage efficiency
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The patent uses cryptographic hashing to create compact representations of software library metadata on the blockchain. Instead of storing full metadata copies across all nodes, the system stores hash values that verify authenticity while minimizing storage requirements. This copying approach maintains trust and authenticity while improving storage efficiency.

Inventive Principle:
Principle #26Copying

4Device complexity

If manual tracking of software library usage is used, then simplicity is maintained, but productivity and accuracy of usage tracking deteriorates

Engineering Contradiction:
Improvesystem simplicityVSAvoidusage tracking efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent implements automated usage tracking through blockchain smart contracts (chaincode) that automatically record when software libraries are accessed, copied, or modified. The system serves itself by automatically detecting usage events and updating metadata without human intervention, dramatically improving tracking efficiency and accuracy while maintaining relatively simple operation through automated processes.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11416474B2Blockchain-based software library access and usage management
Publication Date: 2022.08.16 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11416474B2 patent drawing
  • US11416474B2 patent drawing
  • US11416474B2 patent drawing

AI summary

An example operation includes one or more of receiving a request associated with a software library, identifying metadata of the software library, determining, via chaincode, whether data of the software library has been previously stored on a blockchain, and in response to a determination that the software library has not been previously stored, storing the identified metadata of the software library and a notarization value generated by the chaincode within the blockchain.