Fieldbus Device Emulating Remote Automation for Distributed Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing fieldbus systems in industrial automation technology are limited in connecting automation devices at different locations, making it challenging to implement efficient communication between spatially distributed devices, especially as existing solutions are often retained due to their long service lives and the complexity of replacing them.

Innovation Solution

A fieldbus device that emulates a remote automation device, allowing communication via established fieldbus standards like Profibus or Profinet, by encapsulating fieldbus signals in data frames and transmitting them through a communication network, enabling efficient communication between spatially distributed devices while maintaining existing fieldbus infrastructures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If existing fieldbus systems are used for communication between automation devices, then communication between locally neighboring devices is enabled, but connection of automation devices at different locations is limited

Engineering Contradiction:
Improveconnection capability between distributed devicesVSAvoidcommunication system architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces fieldbus devices as intermediary components that bridge local fieldbus networks and remote automation devices. These fieldbus devices act as mediators by receiving fieldbus signals from local devices, encapsulating them in data frames, and transmitting them over communication networks to remote locations, thereby enabling distributed device connection without directly modifying existing fieldbus systems

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The communication system is segmented into distinct functional components: local fieldbus networks, fieldbus devices for signal encapsulation, communication networks for data transmission, and remote fieldbus devices for signal decapsulation. This segmentation allows each component to operate independently according to its capabilities while achieving overall system integration

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If existing fieldbus infrastructures are replaced to enable distributed communication, then connection capability improves, but system complexity and implementation difficulty increase

Engineering Contradiction:
Improvedistributed communication capabilityVSAvoidsystem implementation ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The fieldbus devices are pre-configured with encapsulation and decapsulation functions before deployment. The system establishes communication protocols and data frame structures in advance, allowing existing fieldbus infrastructures to be integrated without requiring complex real-time modifications or reconfiguration during operation

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The fieldbus devices are designed with multi-functionality, serving as both fieldbus interfaces and network communication nodes. They can handle multiple communication protocols and adapt to different fieldbus standards, making the solution universally applicable to various existing fieldbus infrastructures without requiring device-specific customization

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Speed

If fieldbus signals are transmitted over communication networks, then real-time communication between distributed devices is enabled, but data format compatibility challenges arise

Engineering Contradiction:
Improvecommunication response timeVSAvoiddata frame encapsulation complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent implements nested data structures where fieldbus signals are encapsulated within data frames that contain additional communication metadata. The fieldbus signal (inner layer) is nested within a data frame structure (outer layer) that includes headers, footers, and control information, allowing simultaneous preservation of original signal integrity and addition of network communication capabilities

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The fieldbus devices create copies of the original fieldbus signals and transmit them as encapsulated data frames over communication networks. The receiving fieldbus device decapsulates and reconstructs the original signal, ensuring that the transmitted data is an accurate copy of the source signal while enabling transmission over different physical media

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3485614B1Field bus apparatus for communicating with a remote automation device
Publication Date: 2020.05.27 DEUTSCHE TELEKOM AG
  • EP3485614B1 patent drawingFigure 1
  • EP3485614B1 patent drawingFigure 2
  • EP3485614B1 patent drawingFigure 3

AI summary

The invention relates to a fieldbus device (100) for communicating with a remote automation device via a communication network, wherein the field bus device (100) can be connected to a group of locally adjacent automation devices via a fieldbus. The fieldbus device (100) according to the invention comprises a fieldbus interface (101) for emulating the remote automation device, in respect of communication technology, wherein the fieldbus interface (101) is designed to receive a fieldbus signal over the fieldbus, said fieldbus signal being intended for the remote automation device. The fieldbus device (100) according to the invention furthermore comprises a network interface (103) for communicating over the communication network, wherein the network interface (103) is designed to encapsulate the fieldbus signal in a data frame and to transmit the data frame to the remote automation device via the communication network.