Virtual OPC UA Hostnames for IP-Less Automation Device Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Automation devices without an IP stack become inaccessible in IP-based and IP-routed networks, requiring costly and time-consuming expansions of existing Profinet and OPC UA applications to support Layer-2 communication, limiting remote access and interoperability.
Innovation Solution
Implementing a DNS registration module that registers IP-less automation devices in a Domain Name System, allowing them to appear as if they have an IP stack, using a single OPC UA server to provide virtual OPC UA servers with different hostnames, enabling communication through IP addresses and hiding IP address changes from users.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If automation devices use Layer-2 communication without IP stack, then device cost is reduced, but accessibility in IP-based networks is lost
Solution Approach 1:
The patent introduces a gateway device as an intermediary between IP-based networks and Layer-2 automation devices. The gateway translates IP packets into Layer-2 frames and vice versa, enabling IP-less devices to communicate over IP networks without requiring an IP stack, thus resolving the contradiction between cost reduction and accessibility.
Solution Approach 2:
The system segments network functionality by separating the IP stack requirement from the automation device. The gateway handles all IP protocol processing, while automation devices operate purely at Layer-2, dividing the complex networking task into manageable parts that reduce device complexity and cost.
2Adaptability or versatility
If existing Profinet and OPC UA applications are expanded to support Layer-2 communication, then compatibility with IP-less devices is improved, but implementation cost and time increase
Solution Approach 1:
The gateway serves as a mediator that translates between different communication protocols and layers. It converts IP-based Profinet and OPC UA traffic into Layer-2 frames suitable for IP-less devices, enabling existing applications to work with IP-less devices without modification, thus improving compatibility while avoiding implementation complexity.
Solution Approach 2:
The gateway creates virtual representations of IP-less devices that appear as standard IP-addressable devices to existing applications. This virtual copying allows legacy software to interact with IP-less devices through familiar IP-based interfaces without requiring application expansion or modification.
3Ease of operation
If a single OPC UA server provides virtual servers with different hostnames, then user accessibility is improved, but server complexity increases
Solution Approach 1:
The OPC UA server is designed with multi-functionality to handle multiple virtual server instances within a single deployment. It can present different hostnames and communication endpoints to different clients while maintaining a single physical instance, reducing the number of servers needed and simplifying infrastructure while improving user accessibility.
Solution Approach 2:
Multiple virtual OPC UA servers are merged into a single physical server instance. The server consolidates multiple hostname presentations and communication channels into one unified system, reducing infrastructure complexity while maintaining the ability to provide differentiated access to different clients or device groups.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6
AI summary
A system (0) for data transmission between a client device (112), a server device and a plurality of automation devices (101a, 101b), wherein the server device (100) comprises a descriptive representation of each of the plurality of automation devices (101a, 101b), wherein the server device (100) comprises a server instance (112), which server instance (112) is operative to load one of the descriptive representations based on a hostname identifying one of the plurality of automation devices (101a, 101b), and wherein the server instance is operative to transmit data from the automation device (101a, 101b) to a client application on the client device (110) based on the loaded descriptive representation of the automation device (101a, 101b).