IoT Field Device Database Connectivity Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The complex, time-consuming, and error-prone process of connecting additional field devices to an IoT platform, such as energy management systems, is inefficient and prone to errors due to the need for manual identification of manufacturer, protocol, and data entry, leading to potential system failures.

Innovation Solution

A database storing device IDs and connectivity data is used to facilitate the connection of field devices by matching device IDs, with AI-assisted image recognition and user input for missing data, enabling efficient and error-reduced integration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If manual identification and data entry methods are used to connect field devices, then connection accuracy can be maintained, but connection time and complexity increase significantly

Engineering Contradiction:
Improveconnection accuracyVSAvoidconnection time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-storing connectivity data (protocols, registers, data addresses) in a database associated with each device ID before actual connection is needed. When a field device connects, the system automatically retrieves the pre-stored connectivity data matching the device ID, eliminating the need for manual identification and data entry during connection, thus reducing connection time while maintaining accuracy through predefined correct parameters

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies self-service by enabling automatic retrieval and configuration of connectivity data through device ID matching. The field device itself provides its identifier (device ID), and the system automatically uses this ID to fetch the corresponding connectivity data from the database, configuring the connection without human intervention. This self-configuration process reduces both connection time and potential for human error

Inventive Principle:
Principle #25Self-service

2Reliability

If manual configuration processes are used, then system reliability can be maintained through careful entry, but operational complexity increases

Engineering Contradiction:
Improvesystem reliabilityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complex connectivity configuration data (protocols, register addresses, data formats) from the manual configuration process and stores it separately in a database. During connection, only the simple device ID needs to be matched, and the complex connectivity parameters are automatically retrieved. This extraction separates the simple identification task from the complex configuration data, reducing operational complexity while maintaining reliability through predefined correct parameters

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system changes the parameter representation by using a simple device ID (string identifier) instead of requiring manual entry of multiple complex parameters (protocols, registers, addresses, data formats). The device ID serves as a key that transforms a complex multi-parameter configuration task into a simple single-parameter lookup operation, reducing operational complexity while ensuring reliability through accurate database-matched parameters

Inventive Principle:
Principle #35Parameter changes

3Loss of information

If comprehensive device data collection is implemented, then data analysis capability improves, but data processing load increases

Engineering Contradiction:
Improvedata completenessVSAvoidprocessing load
Core Design Contradiction:
Loss of informationVSPower

Solution Approach 1:

The patent segments device data into two categories: connectivity data (stored in database for quick retrieval) and operational data (collected during operation). The connectivity data including device specifications, protocols, and register mappings is pre-segmented and stored, enabling fast access. Operational data is collected separately during device operation. This segmentation allows comprehensive data collection while managing processing load by pre-processing and storing structural data

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4405762B1Method for operating a device in an IoT system
Publication Date: 2025.10.01 SIEMENS AG
  • EP4405762B1 patent drawingFigure 1~2

AI summary

The invention relates to a method for operating a device, hereinafter referred to as field device, in a system comprising an IoT platform. For simple connection of a further field device to an IoT platform and improved operation, provision is made for a database that stores connectivity data and further device data from field devices and that the IoT platform is able to access. To connect the further field device, a device ID of the further field device is transmitted to the IoT platform and the associated connectivity data are queried from the database. During operation, the further device data are evaluated and a signal for controlling or regulating the field device or other devices is generated.