Digital Twin Registration via Cellular Device Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The manual configuration of industrial devices and their digital twins in a production environment is error-prone and costly, especially when dozens to hundreds of similar devices are deployed, due to challenges in identifying the correct digital twin in a shopfloor network.
Innovation Solution
An industrial device connected to a cellular network automatically determines network and communication identifiers, sends a discover request to a management entity, which instantiates a digital twin if necessary, and synchronizes parameters with the device, eliminating the need for manual intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If manual configuration is used to identify and connect industrial devices to their digital twins, then configuration accuracy can be maintained, but the process becomes time-consuming and error-prone when deploying dozens to hundreds of devices
Solution Approach 1:
The industrial device automatically determines its own network address by combining the network identifier and communication identifier, and autonomously sends a discover request to the management entity. This self-service mechanism eliminates the need for manual configuration while maintaining accuracy through automated identifier matching.
Solution Approach 2:
The device pre-determines the network address formulation rule in advance, combining network identifier and communication identifier to construct the management entity's address. This preliminary preparation enables automatic discovery and connection without manual intervention during deployment.
2Reliability
If manual configuration is used for each industrial device, then correct digital twin identification can be achieved, but the complexity and cost of deployment increase significantly
Solution Approach 1:
The device automatically formulates the network address and sends discover requests without manual configuration. The management entity automatically processes these requests and establishes connections, eliminating manual intervention while maintaining reliable device identification through automated identifier matching.
Solution Approach 2:
The management entity serves multiple functions: receiving discover requests from devices, determining device types, instantiating appropriate digital twins, and establishing connections. This universal approach handles all device types through a single automated system, reducing deployment complexity.
3Productivity
If automatic connection is implemented without manual intervention, then deployment speed increases, but the risk of incorrect configuration and errors increases
Solution Approach 1:
The device sends a discover request containing its communication identifier to the management entity. The management entity processes this request, determines the device type, and establishes the connection. This feedback loop ensures automatic configuration while maintaining reliability through systematic verification and matching of device identifiers with their corresponding digital twins.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The application relates to a method for operating an industrial device (100, 400) connected to a cellular network (50), the method comprising determining a network identifier identifying the cellular network, determining a communication identifier by which the industrial device (100, 400) is uniquely identified when communicating in the cellular network, determining a network address of a management entity (200, 500) configured to manage digital twins of a plurality of industrial devices in the cellular network taking into account at least the network identifier and the communication identifier, determining a type identifier identifying a type of device of the industrial device, transmitting a discover request to the management entity (200, 500) based on the determined network address, the discover request comprising at least the communication identifier, and the type identifier.