Central Name Service Agent for Industrial Automation Device Registration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial automation systems face challenges in reliably registering device names with communication network name services, particularly in IPv6 networks, due to the need for separate addresses for each machine in series machines, cumbersome static address assignments, and difficulties in implementing dynamic address configurations, leading to complex and error-prone device replacement and commissioning processes.

Innovation Solution

A method utilizing a central name service agent and decentralized name service agents, with a rule base to determine necessary registrations, enables independent address configuration and device replacement by using an internet protocol-based domain name system, allowing for stateless address autoconfiguration and eliminating the need for a DHCP server, with configuration and authentication centralized for simplicity and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If static assignment of communication network addresses is used, then device name registration is reliable, but device replacement and commissioning become cumbersome and error-prone

Engineering Contradiction:
Improvedevice name registration reliabilityVSAvoiddevice replacement and commissioning ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent divides the name service functionality into two segments: a centralized name service agent that handles registration requests and a distributed name service that provides address-to-name mappings. This segmentation allows reliable centralized management while enabling easy local device replacement without requiring centralized reconfiguration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The centralized name service agent acts as an intermediary between devices and the name service. Devices communicate their identity and address to the agent, which then registers them with the distributed name service. This intermediary handles the complexity of registration, making device replacement simple while maintaining reliable name resolution.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Extent of automation

If DHCP server is used for dynamic address configuration, then address assignment is automated, but system complexity and implementation effort increase

Engineering Contradiction:
Improveaddress configuration automationVSAvoidsystem complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent extracts the address configuration automation functionality from the traditional DHCP server model and integrates it directly into the name service agent. This eliminates the need for a separate DHCP server, reducing system complexity while maintaining automated address assignment capabilities through the name service infrastructure.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The name service agent performs multiple functions: it acts as a DHCP-like address assignment service, a registration authority, and a name resolution coordinator. This multi-functionality consolidates what would otherwise require separate components, reducing overall system complexity while maintaining automation.

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

3Adaptability or versatility

If decentralized name service agents are used, then device independence is improved, but coordination and authentication become more complex

Engineering Contradiction:
Improvedevice independenceVSAvoidcoordination and authentication complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the authentication and coordination functions of all decentralized name service agents into a single centralized name service agent. This centralization simplifies security management and coordination while allowing decentralized agents to maintain device independence for local name resolution operations.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP2975477B1Method for registering device names from an industrial automation system in a communication network name service, central and decentralized name service agent
Publication Date: 2019.04.17 SIEMENS AG
  • EP2975477B1 patent drawingFigure 1
  • EP2975477B1 patent drawingFigure 2

AI summary

To register device names from an industrial automation system with a communication network name service, a rule set is used to define, on a device-by-device basis, which communication devices within the industrial automation system are permitted or required to register their respective device names with the communication network name service. Device-side decentralized name service agents report communication network addresses of communication devices to a central name service agent of the industrial automation system. When a name-address mapping needs to be registered, the central name service agent submits a registration request to the communication network name service, containing the name-address mapping. Within the industrial automation system, only the central name service agent can submit registration requests to the communication network name service for processing.