Gateway Protocol Conversion for Fieldbus Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing serial fieldbus systems face challenges in efficiently transmitting data between spatially separated networks, leading to increased data volume and complexity in implementing virtual automation networks.

Innovation Solution

The method involves using web service telegrams for data exchange by converting serial fieldbus protocols into web service protocols and vice versa, with gateways functioning as fieldbus slaves on the fieldbus side and web service clients on the Ethernet side, utilizing data transformation modules and event mechanisms to manage data exchange efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Length of stationary object

If serial fieldbus protocols are used for direct communication between master and slave devices, then real-time control capability is maintained, but data transmission distance is limited and network complexity increases when connecting spatially separated networks

Engineering Contradiction:
Improvetransmission distanceVSAvoidnetwork complexity
Core Design Contradiction:
Length of stationary objectVSDevice complexity

Solution Approach 1:

The patent introduces web service gateways as intermediary devices that convert serial fieldbus protocol messages into web service protocol messages and vice versa. These gateways enable communication between spatially separated fieldbus networks by mediating protocol translation, thereby extending transmission distance without directly increasing network complexity through protocol tunneling

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates virtual copies of fieldbus devices through web service interfaces. Instead of physically connecting master and slave devices across long distances using fieldbus protocols, the system generates web service message representations that replicate the original fieldbus communication functionality, allowing remote access without physical protocol constraints

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If virtual automation networks are implemented using protocol tunneling, then data transmission between separated networks is enabled, but data volume increases and transmission efficiency decreases

Engineering Contradiction:
Improvenetwork connectivityVSAvoiddata volume
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential data elements from complete fieldbus protocol messages and transmits them as compact web service messages. Instead of tunneling entire protocol frames with their overhead, the system identifies and transmits only the critical data components, significantly reducing data volume while maintaining network connectivity

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent transforms data from serial fieldbus protocol format to web service protocol format, changing the parameter representation. This format transformation optimizes data compactness by using XML-based web service messages that encode only necessary parameters, reducing overall data volume compared to direct protocol tunneling

Inventive Principle:
Principle #35Parameter changes

3Speed

If direct fieldbus connections are used between master and slave devices, then communication speed is maintained, but physical distance limitations and network topology constraints apply

Engineering Contradiction:
Improvecommunication speedVSAvoidphysical distance
Core Design Contradiction:
SpeedVSLength of moving object

Solution Approach 1:

The patent uses web service gateways as mediators that maintain communication speed by implementing efficient protocol conversion. The gateways process and forward messages without significant delay, preserving real-time communication capabilities while enabling longer physical distances through the intermediary web service infrastructure

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2932684B1Method for the interchange of device-specific data between devices and/or systems of various network systems, and bus system for performing said method
Publication Date: 2018.04.11 SCHNEIDER ELECTRIC AUTOMATION
  • EP2932684B1 patent drawingFigure 1
  • EP2932684B1 patent drawingFigure 2~3
  • EP2932684B1 patent drawingFigure 4

AI summary

The invention relates to a method and a bus system for the interchange of device-specific data between fieldbus slaves (FBS) of a first fieldbus (FB1) and a fieldbus master (FBM) of a second fieldbus (FB2), wherein the first fieldbus (FB1) is connected for communication to a common Ethernet network (EN) via a first gateway (G1) and the second fieldbus (FB2) is connected for communication to a common Ethernet network (EB) via a second gateway (G2), wherein the communication via the Ethernet network (EN) occurs according to the client-server communication principle, wherein the first gateway (G1) reacts on the network side as a fieldbus master (FBM) and on the Ethernet side as a web service server (WSS), and wherein the second gateway (G2) reacts on the fieldbus side as a fieldbus slave (FBS) and on the Ethernet side as a web service client (WSC). In order to accelerate the transmission of data between spatially separate fieldbuses and to reduce the data volume, according to the invention the fieldbus slaves (FBS) and the data thereof are configured in a database (DB) of the web service client (WSC), the web service client (WSC) transmits a list of required data to the web service server (WSS), and the web service server (WSS) cyclically extracts the required data from the fieldbus slaves (FBS) and returns only changes in data values to the web service client (WSC), wherein the database (DB) is updated in the web service client (WSC) on the basis of the changed data values.