Automation Device Self-Configuration for Fast Device Re-Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In industrial automation, device exchanges require rapid and automated re-identification of devices using unique names, which is challenging due to the reliance on centralized systems and the inefficiency of manual labeling and configuration, especially in scenarios where devices are interchangeable but must perform specific tasks.
Innovation Solution
A method for automatically configuring industrial automation devices by using a device management unit to monitor and manage automation identifiers and node identifiers within a cluster state database, allowing for the generation or update of description objects to ensure correct allocation of tasks without manual intervention, leveraging existing identification systems like AKZ or KKZ.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized IO controller is used to trace and baptize unbaptized devices via alias names, then device identification and task allocation can be achieved, but the system complexity increases and the baptism process becomes slower
Solution Approach 1:
The patent implements self-baptism where automation devices automatically determine their own device names using the domain name system (DNS) without requiring a centralized IO controller to trace and assign names. Each device queries the DNS server with its node identifier to obtain its device name autonomously, eliminating the need for complex centralized tracking mechanisms and alias name calculations.
Solution Approach 2:
The patent extracts the name resolution function from the centralized IO controller and relocates it to individual automation devices. By removing the dependency on the controller for name assignment, the system reduces centralized complexity while maintaining reliable device identification through distributed DNS queries.
2Reliability
If manual labeling and configuration are used for device baptism, then device names can be assigned, but the process becomes time-consuming and administratively burdensome
Solution Approach 1:
The patent enables automation devices to automatically obtain their device names through DNS queries without manual intervention. When a device joins the network or undergoes exchange, it autonomously resolves its device name using its node identifier and the DNS server, eliminating time-consuming manual labeling and configuration processes while ensuring accurate name assignment.
3Adaptability or versatility
If device exchanges occur frequently, then system adaptability improves, but the re-identification process becomes more challenging and time-consuming
Solution Approach 1:
The patent enables rapid re-identification during device exchanges by allowing new devices to automatically query the DNS server for their device names using their node identifiers. This self-service mechanism ensures that regardless of how frequently devices are exchanged, each device can quickly and autonomously obtain its correct name without manual intervention or complex centralized tracking, maintaining system adaptability while minimizing re-identification time.
4Reliability
If a quasi-centralized baptism system is implemented, then device name allocation can be managed, but the productivity of device onboarding decreases
Solution Approach 1:
The patent transforms the quasi-centralized baptism system into a fully automated self-service mechanism where devices independently obtain their names through DNS queries. This eliminates the sequential processing bottleneck of centralized name assignment, allowing multiple devices to be onboarded simultaneously and independently, thereby significantly improving device onboarding speed while maintaining reliable name allocation through the DNS server.
Data Source
AI summary
Automation device, computer program, computer-readable medium and method for automatically configuring an automation device, wherein a) an automation device is provided, b) a device management unit monitors whether an automation identifier is assigned to the automation device, c) upon identifying an assignment of this kind, the device management unit queries a central cluster management unit to determine whether a description object, in which the automation identifier assigned to the automation device is stored, already exists in a cluster state database belonging to the cluster containing description objects for nodes of the cluster, d) if no such description object yet exists, or if such a description object does exist but has been declared inactive, then the device management unit creates, in the cluster state database for a node identifier assigned to the automation device, a description object in which the automation identifier assigned to the automation device is stored.