Automation Component Authentication via Distributed Registry Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current automation systems lack comprehensive, tamperproof, and up-to-date identification and tracking of automation components across manufacturers and supply chains, leading to difficulties in ensuring authenticity and traceability, especially for small manufacturers, due to proprietary and closed systems that do not allow for manufacturer- and system-independent collaboration.

Innovation Solution

A distributed registry system is implemented to authenticate and securely store component data, using digital twins and blockchain technology for tamperproof and continuous updating, allowing for manufacturer-independent collaboration and real-time tracking of automation components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If proprietary and closed systems are used for automation component identification and tracking, then manufacturer-specific data storage is achieved, but comprehensive manufacturer- and system-independent collaboration is prevented

Engineering Contradiction:
Improvemanufacturer-independent collaborationVSAvoidsystem heterogeneity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal identification system using ISO/IEC 18004-5 compliant data matrices that can store component data in a standardized format readable by any system. This allows different manufacturers' systems to collaborate independently while maintaining their own operational autonomy, resolving the contradiction between universality and system independence.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If serial numbers and proprietary databases are used for component identification, then simple implementation is achieved, but tamperproof authentication and comprehensive tracking are limited

Engineering Contradiction:
Improveauthentication securityVSAvoiddata management system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent embeds machine-readable data matrices directly onto automation components, nesting identification and authentication data within the physical component itself. This layered approach provides tamperproof authentication while maintaining manageable system complexity through standardized data storage and retrieval protocols.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The system implements continuous feedback loops where component data is read, authenticated, verified for tampering, and updated in real-time. This feedback mechanism ensures authentication security through constant verification while managing complexity through automated validation processes.

Inventive Principle:
Principle #23Feedback

3Loss of information

If historical state data is stored in centralized databases, then data storage is achieved, but real-time updates and comprehensive traceability are prevented

Engineering Contradiction:
Improvedata currencyVSAvoiddata synchronization system
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent pre-encodes unique identification and authentication data into machine-readable formats on components during manufacturing. This preliminary action ensures data currency from the outset, eliminating the need for complex centralized synchronization systems while maintaining real-time traceability throughout the component lifecycle.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11616838B2Securing an automation component
Publication Date: 2023.03.28 SIEMENS AG
  • US11616838B2 patent drawing
  • US11616838B2 patent drawing
  • US11616838B2 patent drawing

AI summary

The invention relates to a method for securing component data assigned to an automation component (D1, D2, DN), wherein the component data is transmitted to at least one portion of computing nodes of a distributed registry (BN1, BN2, BN3), wherein the distributed registry (BN1, BN2, BN3) functions to authenticate the component data, preferably component data of multiple automation components (BN1, BN2, BN3).