Software Component Validation Using a Distributed Ledger

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for vetting and functional validation of software components, particularly in industrial contexts, are complex, time-consuming, and often lack comprehensive documentation, especially for data integrity and authenticity, making it difficult for users to verify the correctness and security of software components.

Innovation Solution

A computer-implemented method utilizing a distributed ledger to write and store software component data, perform functional validation, and provide validation data, enabling users to easily verify authenticity and correctness in a secure, immutable, and verifiable manner, leveraging a decentralized system for increased reliability and transparency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional vetting and functional validation methods are used for software components, then comprehensive security testing and guarantees can be provided, but the process becomes complex and time-consuming

Engineering Contradiction:

Improvesecurity guaranteesVSAvoidvetting process complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a distributed ledger as an intermediary between software component providers and consumers. The ledger stores and verifies digital signatures, hashes, and validation results, acting as a neutral mediator that eliminates the need for complex centralized vetting processes while maintaining security guarantees.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates immutable copies of software component metadata, signatures, and validation results in the distributed ledger. These digital copies serve as permanent verification records that can be independently validated without requiring access to the original complex vetting processes.

Inventive Principle:

Principle #26Copying

2Reliability

If traditional vetting and functional validation methods are used for software components, then security testing can be performed, but the process becomes time-consuming

Engineering Contradiction:

Improvesecurity testingVSAvoidvalidation time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent performs validation actions in advance by storing digital signatures, hashes, and validation results in the distributed ledger before software components are deployed. This preliminary action allows consumers to instantly verify component integrity without undergoing time-consuming validation processes.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The distributed ledger provides immediate feedback on software component validity through programmatically accessible validation results. Consumers can query the ledger to receive instant confirmation of component authenticity, eliminating lengthy manual verification processes.

Inventive Principle:

Principle #23Feedback

3Ease of operation

If software component validation is performed without decentralized storage, then validation data can be maintained privately, but authenticity and correctness verification becomes difficult for users

Engineering Contradiction:

Improveverification easeVSAvoidvalidation data accessibility

Core Design Contradiction:

Ease of operationVSLoss of information

Solution Approach 1:

The patent transitions validation data from private, centralized storage to a decentralized distributed ledger infrastructure. This dimensional change in data architecture allows multiple users to simultaneously access and verify the same validation information without relying on a single central authority, thereby improving both accessibility and verification ease.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

4Reliability

If centralized validation systems are used, then validation processes can be controlled centrally, but the system lacks transparency and immutability

Engineering Contradiction:

ImprovetransparencyVSAvoidsystem architecture

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the validation system into independent, distributed nodes that collectively maintain the ledger. Each node independently stores and validates information, eliminating the need for complex centralized control structures while enhancing transparency through distributed verification.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS12481766B2Vetting and/or functional validation of software components

Publication Date: 2025.11.25 ABB (SCHWEIZ) AG

AI summary

A computer-implemented method for providing vetting and/or functional validation of software components, comprising: providing a software component and software component data indicating the software component; writing the software component data in a distributed ledger; functional validating and/or vetting the software component and providing functional validation and/or vetting data of the software component; writing the functional validation and/or vetting data in the distributed ledger; providing the data written in the distributed ledger to a software component consumer.