Server Proxy Mapping 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
A system and method that uses a server device with descriptive representations of automation devices, allowing data transmission between client and server devices, and enables IP-less automation devices to appear as if they have an IP stack, using protocols like NAT, ALG, and proxies to facilitate communication through a DNS registration module, making them accessible via IP like IP-capable devices.
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 network accessibility and interoperability are lost
Solution Approach 1:
A gateway device is introduced as an intermediary between IP-based networks and Layer-2 automation devices. The gateway performs protocol conversion, translating IP-based communication protocols (such as OPC UA, MQTT) into Layer-2 fieldbus protocols, enabling IP-less devices to access IP-based networks without requiring an IP stack.
Solution Approach 2:
The system is segmented into distinct functional layers: an IP-based network layer for cloud connectivity and a Layer-2 fieldbus layer for device communication. The gateway device bridges these layers, allowing automation devices to remain simple and cost-effective while still enabling remote access through the IP network infrastructure.
2Adaptability or versatility
If existing Profinet and OPC UA applications are expanded to support Layer-2 communication, then IP-less device accessibility is improved, but development time and cost increase
Solution Approach 1:
The gateway device autonomously handles protocol conversion and translation between IP-based and Layer-2 protocols. Existing Profinet and OPC UA applications can continue to operate unchanged while the gateway automatically performs the necessary protocol translations, eliminating the need for time-consuming modifications to existing applications.
Solution Approach 2:
The gateway device provides multi-functional support for multiple protocol standards (Profinet, OPC UA, MQTT, and various Layer-2 fieldbus protocols), making it a universal solution that can interface with different IP-based applications without requiring custom development for each protocol.
3Device complexity
If IP stack is omitted from automation devices, then device complexity is reduced, but remote access capability is lost
Solution Approach 1:
The gateway device serves as a mediator that provides remote access capabilities to IP-less automation devices. By handling all IP-based communication protocols and cloud connectivity at the gateway level, simple automation devices can be remotely accessed and monitored without requiring complex IP stacks or network infrastructure.
Solution Approach 2:
The gateway device creates a virtual representation of the Layer-2 automation devices in the IP-based network environment. Through protocol translation and data mapping, the gateway presents IP-less devices as if they were native IP devices, enabling standard IP-based tools and applications to access and control them remotely.
Data Source
AI summary
A system for data transmission between a client device, a server device and a plurality of automation devices, wherein the server device includes a descriptive representation of each of the plurality of automation devices, wherein the server device includes a server instance, which server instance is configured to load one of the descriptive representations based on a hostname identifying one of the plurality of automation devices, and wherein the server instance is configured to transmit data from the automation device to a client application on the client device based on the loaded descriptive representation of the automation device.