Distributed Ledger Configuration Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for proving computer system configuration rely on time-consuming and costly paper trails, which can be unreliable due to the potential for falsification or modification, especially in regulated industries where trustworthiness of documentation is a concern.

Innovation Solution

A system utilizing a distributed ledger, such as a blockchain, to cryptographically verify and anchor configuration information, allowing for automated and reliable proof of system configuration at any point in time by comparing historical data with immutable records stored on the ledger.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If paper trails are used to prove system configuration, then documentation can be created and stored, but the process requires significant time and effort and can be falsified or modified

Engineering Contradiction:
Improvetrustworthiness of configuration documentationVSAvoidtime required to generate and store paperwork
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces manual paperwork processes with automated electronic configuration management. Configuration information is automatically captured, stored, and timestamped by a computer system, eliminating the need for manual documentation creation and storage while ensuring reliability through automated integrity verification.

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

Solution Approach 2:

The patent creates and maintains copies of configuration information in structured electronic formats with timestamps and verification mechanisms. These electronic copies serve as reliable proof of configuration state at specific times, replacing physical paper trails with digitally verifiable records that are harder to falsify.

Inventive Principle:
Principle #26Copying

2Reliability

If paper trails are used to prove system configuration, then configuration documentation can be maintained, but significant costs are incurred for compliance

Engineering Contradiction:
Improvetrustworthiness of configuration documentationVSAvoidcosts associated with compliance
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements self-service configuration management where the system automatically captures, stores, and verifies its own configuration information without requiring external manual intervention. This automation reduces compliance costs by eliminating the need for dedicated personnel to manually create and maintain configuration documentation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces costly manual compliance processes with automated electronic systems that continuously track and verify configuration states, reducing the labor and resource costs associated with maintaining reliable configuration documentation.

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

3Ease of operation

If manual paperwork processes are used, then configuration information can be recorded, but the process inherently relies on the trustworthiness of the person generating the paperwork

Engineering Contradiction:
Improvesimplicity of documentation processVSAvoidtrustworthiness of documentation
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent replaces manual paperwork operations with automated electronic configuration capture. The system automatically records configuration states with timestamps and verification data, maintaining simplicity of operation while eliminating reliance on human trustworthiness through automated integrity mechanisms.

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

Solution Approach 2:

The patent creates electronic copies of configuration information that are automatically timestamped and verified, providing simple automated documentation while ensuring reliability through cryptographic or systematic verification that does not depend on human trustworthiness.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10558471B2Proof of configuration
Publication Date: 2020.02.11 MERCK SHARP & DOHME LLC
  • US10558471B2 patent drawing
  • US10558471B2 patent drawing
  • US10558471B2 patent drawing

AI summary

When a system configuration is deployed, the recipe used, the results of the deployment, and/or the results of any qualification tests performed may be anchored to a distributed ledger. Periodically, the system configuration may be audited by verifying the recipe against the anchored version. The results of such audits may also be anchored to the distributed ledger. Thus, what is anchored to the distributed ledger represents a cryptographically verifiable history of the configuration of the system. Consequently, the system configuration at any time can be proven by comparing historical configuration information maintained by the owner of the system to the distributed ledger.