Automation Plant Usage Data Authentication via Ledger Checksums

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack a reliable and manipulation-proof method for verifying and authenticating usage data of automation plants, particularly in leasing and usage-based rental scenarios, where credibility and trust are essential for financial security and compliance with regulations.

Innovation Solution

A system comprising an edge device, a service for forming checksums using cryptographic hash functions, and an auditing service integrated with a distributed ledger network, which collects and generates manipulation-proof usage data, forms and stores checksums, and allows third-party verification of data integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If usage data is stored locally without external verification, then data access is fast and simple, but data integrity and trustworthiness cannot be guaranteed

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a distributed ledger network as an intermediary between the automation plant and third-party assessors. The ledger stores checksums of usage data, serving as a trusted mediator that verifies data integrity without requiring complex point-to-point verification systems. This resolves the contradiction by providing reliable data verification through a centralized trust mechanism rather than complex distributed verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a cryptographic copy (checksum) of the usage data and stores it in the distributed ledger. This checksum copy serves as a verification token that proves the original data's integrity without requiring the entire dataset to be stored or transmitted. This resolves the contradiction by using a simplified copy mechanism to ensure data reliability.

Inventive Principle:
Principle #26Copying

2Reliability

If physical inspections are conducted to verify machine condition, then data credibility is established, but time and operational efficiency are reduced

Engineering Contradiction:
Improvedata credibilityVSAvoidinspection time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces physical inspection mechanisms with cryptographic verification mechanisms. Instead of physically examining machines or manually verifying usage data, the system uses cryptographic checksums stored in the distributed ledger to automatically verify data integrity. This substitution eliminates time-consuming physical inspections while maintaining or enhancing data credibility.

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

Solution Approach 2:

The automation plant automatically generates and stores cryptographic checksums of its usage data in the distributed ledger without requiring external verification. This self-service approach allows the system to prove its own data integrity automatically, eliminating the need for time-consuming third-party physical inspections while maintaining data credibility.

Inventive Principle:
Principle #25Self-service

3Reliability

If trusted employees or third parties are deployed to inspect machines, then data verification is possible, but costs and operational disruptions increase

Engineering Contradiction:
Improveverification trustworthinessVSAvoidoperational efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent replaces human inspection mechanisms with automated cryptographic verification. The distributed ledger system automatically verifies usage data through cryptographic checksums without requiring human inspectors to travel to, physically examine, or manually verify machine operations. This substitution eliminates productivity losses associated with human inspections while maintaining verification trustworthiness.

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

Solution Approach 2:

The system performs self-verification by automatically generating and storing cryptographic proofs of data integrity in the distributed ledger. This eliminates the need for external trusted parties to be deployed, allowing continuous operation without disruption while maintaining verification trustworthiness through automated cryptographic processes.

Inventive Principle:
Principle #25Self-service

4Reliability

If complete usage data is stored in distributed ledger, then verification completeness is maximized, but storage costs and network load increase

Engineering Contradiction:
Improveverification completenessVSAvoiddata storage volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential verification element (cryptographic checksum) from the complete usage data and stores it in the distributed ledger. The full usage data remains stored locally in the automation plant, while the extracted checksum provides sufficient information for verification. This resolves the contradiction by storing only the necessary verification component rather than the entire dataset.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a condensed cryptographic copy (checksum) of the usage data that contains verification information in a compact form. This checksum copy is stored in the distributed ledger, providing verification completeness without requiring storage of the entire large-volume usage dataset. The checksum serves as a compact representation that enables full verification.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12204305B2Systems and methods for digital authentication of usage data of an automation plant
Publication Date: 2025.01.21 SIEMENS AG
  • US12204305B2 patent drawing
  • US12204305B2 patent drawing
  • US12204305B2 patent drawing

AI summary

A system includes a first module configured to collect automation plant-related data that include at least operating data, and to generate based on the operating data manipulation-proof usage data which are then transmitted to a second module configured to determine at least a part of the manipulation-proof usage data, to form a checksum from the at least one part of the manipulation-proof usage data, to transfer the checksum to at least one node of a distributed ledger network, and to store the manipulation-proof usage data in an area outside the distributed ledger network. A third module participates in the distributed ledger network and is configured to obtain the manipulation-proof usage data from the area and to check the correctness of the manipulation-proof usage data by forming a checksum.