Software Container Configuration for Electronic Components

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing solutions for configuring electronic components, such as field devices and building technology devices, pose a security risk due to direct communication connections, and they lack efficiency and simplicity in configuration processes.

Innovation Solution

A method using software containers to configure electronic components, where a software container is created and provided to the component, allowing it to be configured based on configuration information, with the component retrieving and executing the container using a pull principle to enhance security and efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If direct communication connections are used between electronic components and configuring entities, then configuration can be performed, but security risks increase

Engineering Contradiction:

Improveconfiguration capabilityVSAvoidsecurity risks

Core Design Contradiction:

Ease of operationVSObject-affected harmful factors

Solution Approach 1:

A software container acts as an intermediary between the configuring entity and the electronic component. The container is created on the component, receives configuration data indirectly, and executes the configuration without requiring a persistent direct communication connection, thereby reducing security exposure while maintaining configuration capability

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The software container is created and prepared on the electronic component before the actual configuration process. This preliminary action allows the component to be configured through the container's execution rather than through direct communication protocols, reducing the security risks associated with ongoing direct connections

Inventive Principle:

Principle #10Preliminary action

2Productivity

If traditional configuration methods are used, then electronic components can be configured, but the process lacks efficiency and simplicity

Engineering Contradiction:

Improveconfiguration efficiencyVSAvoidconfiguration simplicity

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The electronic component autonomously creates and executes the software container for its own configuration. This self-service approach eliminates the need for complex external configuration tools and procedures, thereby improving both efficiency and simplicity of the configuration process

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The configuration process is transformed from a complex procedural operation into a simple parameter-driven process where configuration data is passed to the software container. This changes the nature of configuration from a multi-step operation to a streamlined parameter-setting process, improving efficiency and simplicity

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS20250147791A1Configuration of electronic components based on software containers

Publication Date: 2025.05.08 WAGO VERW GMBH

AI summary

A method for configuring an electronic component is provided. The electronic component may, in particular, be a field device and/or an automation device and/or a building technology device. The method may comprise creating a software container which is executable on the electronic component to configure the electronic component according to configuration information. The method may comprise providing an instruction which, when executed on the electronic component, causes the electronic component to retrieve and/or execute the software container. The method may comprise providing the software container to the electronic component.