Industrial Automation Device Name Autoconfiguration via Topological Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial automation systems face issues with communication link interruptions and resource conflicts in Ethernet-based networks, leading to delayed or lost data frames due to time-critical requirements and frequent short message traffic, which can cause system disturbances and errors.

Innovation Solution

A communication device and method that checks for topological or hierarchical name components to generate complete device names, allowing for decentralized automated configuration and autoconfiguration of IPv6 addresses using router advertisements and dynamic DNS, enabling domain name formation and registration without manual administration tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If real-time communication protocols are used for time-critical automation devices, then communication reliability is improved, but network resource consumption increases due to frequent short message traffic

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidnetwork resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the device identification process into hierarchical components (domain name, subdomain, device name) that can be independently managed and transmitted. This allows the system to use efficient unicast communication for stable device identifiers while reserving multicast for essential service announcements, reducing overall network resource consumption while maintaining reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements periodic device name verification and update mechanisms where devices check their name allocation status at regular intervals. This periodic action ensures communication reliability through consistent name resolution while avoiding continuous message traffic, thereby reducing network resource consumption.

Inventive Principle:
Principle #19Periodic action

2Manufacturing precision

If manual device name administration is performed, then device name accuracy is improved, but system complexity increases due to manual configuration requirements

Engineering Contradiction:
Improvedevice name accuracyVSAvoidsystem complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent enables devices to automatically generate, verify, and update their device names through integrated name service clients. Devices independently query name servers, validate their identifiers, and perform self-configuration without manual intervention. This self-service mechanism maintains device name accuracy while eliminating the complexity of manual configuration processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements feedback loops where devices continuously verify their device name allocation status through name service queries. The system receives feedback from name servers about name availability and validity, automatically adjusting configurations based on this feedback. This ensures accurate device naming while reducing system complexity through automated closed-loop control.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If decentralized automated configuration is implemented, then ease of operation is improved, but communication overhead increases due to additional name service messages

Engineering Contradiction:
Improveease of configurationVSAvoidcommunication overhead
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The patent segments communication traffic into essential name service messages (device name queries and responses) and regular automation traffic. By separating these communication streams and using efficient protocols for each, the system achieves decentralized automated configuration while minimizing communication overhead through targeted, necessary messages only.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If device names with topological components are generated automatically, then adaptability is improved, but device complexity increases due to name generation algorithms

Engineering Contradiction:
Improvedevice name adaptabilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces name service servers as intermediaries between devices and the naming system. Instead of implementing complex name generation algorithms directly in each device, devices delegate name generation and validation to specialized intermediary servers. This approach provides adaptable, topologically-aware device names while keeping individual device complexity low.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10069789B2Communication device and method for providing a name service within an industrial automation system
Publication Date: 2018.09.04 SIEMENS AG
  • US10069789B2 patent drawing
  • US10069789B2 patent drawing
  • US10069789B2 patent drawing

AI summary

A method for providing a name service within an industrial automation system, wherein communication devices of the industrial automation system each check via a name service component whether a device name with a topological or hierarchical name component, which essentially completely designates a spatial or hierarchical arrangement of the respective communication device, is allocated to the respective communication device, where in cases of a positive check result, the communication devices each designate their associated device name as complete device name, and where in cases of a negative check result, the communication devices each independently generate their complete device name from topological or hierarchical name components distributed via messages with router advertisements and a name component unambiguous within their respective subnetwork.