Field Device Software Containers for Distributed Ledger Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Field devices in industrial installations cannot be easily integrated into distributed ledger technology environments due to limitations in software customization and data selection, restricting rapid integration and participation as secure, tamper-proof nodes.
Innovation Solution
A field device with firmware containing a software container that enables execution of code for communication with distributed ledgers, allowing data processing and transmission, and allowing users to select and load code from third-party providers, facilitating integration without requiring firmware recompilation or adaptation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If field device firmware is customized to integrate with distributed ledger, then integration capability is improved, but firmware complexity and update frequency increase
Solution Approach 1:
The firmware is segmented into a base component and separate software containers. The base firmware provides core field device functionality, while software containers encapsulate distributed ledger integration code. This segmentation allows the base firmware to remain simple and stable, while integration capabilities are added through interchangeable containers that can be loaded and unloaded without modifying the core firmware.
Solution Approach 2:
The software container architecture provides a universal interface for integrating different distributed ledger implementations. A single base firmware can support multiple different ledger protocols and implementations by loading appropriate software containers, making the field device universally adaptable to various distributed ledger environments without requiring firmware recompilation.
2Adaptability or versatility
If field device firmware is customized for each distributed ledger, then specific integration is improved, but integration time and productivity decrease
Solution Approach 1:
Software containers are prepared and validated in advance before being deployed to field devices. The containerization approach allows integration code to be pre-configured, pre-tested, and pre-packaged, so that when a field device needs to integrate with a distributed ledger, the appropriate container can be quickly loaded without on-site firmware compilation or complex configuration procedures.
3Adaptability or versatility
If field device allows user-loaded code, then flexibility is improved, but device security and reliability may worsen
Solution Approach 1:
The software container acts as an intermediary layer between the user-provided integration code and the field device's core operating system. The container encapsulates the loaded code within a controlled environment, managing its execution and resource access. This intermediary structure allows flexible user-loaded code while maintaining device security by preventing direct access to critical system resources.
Solution Approach 2:
The software container creates a localized, isolated execution environment with specific permissions and resource constraints. Within this local quality-defined space, user-loaded code can operate flexibly, but its impact is contained and cannot compromise the overall device reliability. The container enforces local security policies while allowing adaptive functionality.
Data Source
AI summary
An automation technology field device includes operating electronics and a plurality of parameters. The operating electronics are designed to operate the field device based on the parameters and obtain and process data based on the parameters. A firmware is a software container allocated to the operating electronics. The software container is designed to execute the installed code to establish, using the code, a communication connection to a distributed ledger via at least one of the outputs is a higher-level communication network, to integrate the field device in the distributed ledger-and to process and/or combine at least one part of the obtained and processed data into result data and to transmit the result data to the distributed ledger.