Field Device Publish-Subscribe Architecture for Automation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing process control systems face complexity in integrating advanced communication protocols like Ethernet and IP-based protocols with traditional field devices, leading to cumbersome communication setups and reduced effectiveness due to the need for multiple I/O devices and protocols, which hampers efficient data exchange and security in process control and factory automation environments.

Innovation Solution

A highly versatile field device capable of operating as a data server, supporting multiple applications and communication protocols, including IP-based protocols, through a common communication network infrastructure, enabling direct communication with various client devices and systems while maintaining high security features such as root of trust, secure boot, and endpoint identity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional field devices use specialized communication protocols with separate I/O devices for each protocol, then protocol-specific communication reliability is improved, but system complexity and integration difficulty increase

Engineering Contradiction:

Improvecommunication reliabilityVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The field device is designed with multi-functionality to support multiple communication protocols (HART, Fieldbus, Profibus, Ethernet/IP, Profinet) simultaneously through a single device interface, eliminating the need for separate I/O devices for each protocol while maintaining reliable communication for all protocols

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple separate I/O devices are used to support different field device protocols, then protocol compatibility is improved, but ease of operation and installation deteriorate

Engineering Contradiction:

Improveprotocol compatibilityVSAvoidease of installation

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

A single field device incorporates support for multiple communication protocols including HART, Fieldbus, Profibus, Ethernet/IP, and Profinet, allowing seamless integration with different control systems without requiring separate I/O devices for each protocol type

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Multiple protocol support capabilities are merged into a single field device unit, consolidating what would traditionally require multiple separate I/O devices into one integrated solution that simplifies installation and operation

Inventive Principle:

Principle #5Merging (Combining)

3Reliability

If field devices communicate through centralized controllers using traditional protocols, then control security is improved, but communication efficiency and data exchange speed deteriorate

Engineering Contradiction:

Improvecontrol securityVSAvoidcommunication efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The communication architecture is segmented to allow field devices to communicate directly with control systems and other field devices through Ethernet/IP and Profinet protocols, bypassing the need for all communications to route through centralized controllers while maintaining security through protocol-specific communication paths

Inventive Principle:

Principle #1Segmentation

4Device complexity

If traditional field devices support only single protocol communication, then device simplicity is improved, but adaptability to different systems deteriorates

Engineering Contradiction:

Improvedevice simplicityVSAvoidsystem adaptability

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20240089326A1Publish-subscribe communication architecture for field devices in control and automation systems

Publication Date: 2024.03.14 FISHER ROSEMOUNT SYST INC

AI summary

A method includes receiving at a field device, from a first client device or application, a message indicating a selection of a first one of a plurality of publish categories corresponding to a type of information desired by the first client device or application. The method further includes transmitting, from the field device to the first client device or application, an identification of each of a plurality of publish lists corresponding to the first one of the selected publish category. The publish lists are stored on the field device and each includes a set of parameters associated with the field device. The method includes receiving at the field device, from the first client device or application, a selection of a publish list identified by the field device, and transmitting, from the field device to the first client device or application, the set of parameters associated with the selected publish list.