IP Library › Granted Patent US 12,627,736
Granted Patent B2
US 12,627,736 · App. 18/514,543 · Granted May 12, 2026

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

Inventors: Mark J. Nixon (Thorndale, TX); Gary K. Law (Georgetown, TX)
Assignee: FISHER-ROSEMOUNT SYSTEMS, INC.
H04L67/12G05B19/058
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,627,736
App. No.
18/514,543
Granted
May 12, 2026
Kind
B2
Abstract

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.

Claims (74)

1 . A method comprising:

receiving at a field device, from a first client device or application, during run-time operations of a process plant, a message indicating a selection of a first one of a plurality of publish categories, the first one of the plurality of publish categories corresponding to a type of information desired by the first client device or application;

transmitting, from the field device to the first client device or application, an identification of each of a plurality of publish lists that are pre-defined and stored on the field device prior to receiving the message from the first client device or application, corresponding to the first one of the plurality of publish categories, the plurality of publish lists stored on the field device and each publish list comprising a particular set of parameters associated with the field device;

receiving at the field device, from the first client device or application, a selection of a first one of the plurality of publish lists identified by the field device; and

transmitting, from the field device to the first client device or application, the particular set of parameters associated with the first one of the plurality of publish lists.

2 . The method according to claim 1 , wherein the field device is a process control field device and wherein the first client device or application is a process controller.

3 . The method according to claim 1 , wherein the field device is a robotic factory automation device and wherein the first client device or application is a factory automation controller.

4 . The method according to claim 1 , wherein the first client device or application is an application executing on a processor communicating with the field device through an edge gateway.

5 . The method according to claim 1 , wherein the first client device or application is an application executing on a cloud-computing platform.

6 . The method according to claim 1 , wherein the first client device or application is another field device.

7 . The method according to claim 1 , wherein receiving the message indicating the selection of the first one of the plurality of publish categories comprises receiving a message specifying a monitor and control category.

8 . The method according to claim 1 , wherein receiving the message indicating the selection of the first one of the plurality of publish categories comprises receiving a message specifying a condition monitoring category.

9 . The method according to claim 1 , wherein transmitting the identification of each of the plurality of publish lists comprises transmitting an identification of one or more manufacturer-defined publish lists, each of the one or more manufacturer-defined publish lists stored on the field device at the time of the field device's manufacture.

10 . The method according to claim 1 , wherein transmitting the identification of each of the plurality of publish lists comprises transmitting an identification of one or more user defined publish lists.

11 . The method according to claim 1 , wherein transmitting the identification of each of the plurality of publish lists comprises transmitting an identification of one or more custom publish lists.

12 . The method according to claim 1 , further comprising:

receiving, at the field device, from a second client device or a second application, a second message indicating a selection of a second one of the plurality of publish categories;

transmitting, from the field device to the second client device or the second application, an identification of each of a second plurality of publish lists corresponding to the second one of the plurality of publish categories received from the second client device or the second application;

receiving at the field device, from the second client device or the second application, a selection of a one of the second plurality of publish lists identified by the field device;

transmitting, from the field device to the second client device or the second application, the particular set of parameters associated with the selection of the one of the second plurality of publish lists received from the second client device or the second application.

13 . The method according to claim 12 , wherein the second message from the second client device or the second application indicating the selection of the second one of the plurality of publish categories is a message indicating a selection of a different one of the plurality of publish categories from the first one of the plurality of publish categories.

14 . The method according to claim 12 , wherein receiving from the second client device or the second application the selection of the one of the second plurality of publish lists identified by the field device comprises receiving a selection of a different one of the plurality of publish lists from the first one of the plurality of publish lists.

15 . The method according to claim 12 , wherein:

receiving from the first client device or application the selection of the first one of the plurality of publish lists further comprises receiving an update rate specifying a frequency with which the particular set of parameters associated with the first one of the plurality of publish lists will be transmitted from the field device to the first client device or application, and/or

receiving from the second client device or the second application the selection of the one of the second plurality of publish lists identified by the field device comprises receiving a second update rate specifying a second frequency with which the particular set of parameters associated with the one of the second plurality of publish lists will be transmitted from the field device to the second client device or the second application.

16 . The method according to claim 1 , wherein each of the publish lists includes an update rate parameter specifying a frequency with which the particular set of parameters associated with a corresponding publish list will be transmitted from the field device to the client device or application subscribed to the corresponding publish list.

17 . A field device comprising:

a processor; and

a memory device, coupled to the processor, the memory device storing (I) a plurality of pre-defined publish lists, each pre-defined publish list corresponding to one of at least two available publish categories, each pre-defined publish list comprising a particular set of parameters associated with the field device, and (ii) a set of instructions executable by the processor to cause the processor to:

receive, from a client device or application, during run-time operations of a process plant, a message indicating a one of the at least two available publish categories, the one publish category indicating a category of information desired by the client device or application;

transmit, to the client device or application, an identification of each of the plurality of pre-defined publish lists that are stored in the memory device prior to receiving the message from the client device or application, corresponding to the indicated publish category;

receive, from the client device or application, a selection of one of the plurality of pre-defined publish lists identified by the field device; and

transmit, to the client device or application, the particular set of parameters associated with the selected one of the plurality of pre-defined publish lists.

18 . The field device according to claim 17 , wherein the client device or application is another field device.

19 . The field device according to claim 17 , wherein the plurality of pre-defined publish lists include one or more manufacturer-defined publish lists.

20 . The field device according to claim 17 , wherein the plurality of pre-defined publish lists include one or more user-defined publish lists.

21 . The field device according to claim 17 , wherein the plurality of pre-defined publish lists include one or more custom publish lists.

22 . The field device according to claim 17 , wherein the at least two available publish categories include a monitor and control publish category, and wherein publish lists corresponding to the monitor and control publish category include parameters of the field device related to performing control actions.

23 . The field device according to claim 17 , wherein the at least two available publish categories include a condition monitoring category, and wherein publish lists corresponding to the condition monitoring publish category include parameters of the field device related to monitoring a health, maintenance, calibration, or energy consumption state of the field device.

24 . The field device according to claim 17 , wherein at least one of the plurality of pre-defined publish lists comprises an update rate parameter specifying a frequency with which the particular set of parameters in the at least one pre-defined publish list is transmitted to a subscribing client device or application.

25 . The field device according to claim 17 , wherein the field device is configurable to:

transmit a first set of parameters corresponding to a first one of the plurality of pre-defined publish lists to a first client device or application; and

transmit a second set of parameters corresponding to a second one of the plurality of pre-defined publish lists to a second client device or a second application.

26 . The field device according to claim 25 , wherein the first one of the plurality of predefined publish lists corresponds to a first one of the at least two available publish categories and the second one of the plurality of pre-defined publish lists corresponds to a second one of the at least two available publish categories.

27 . The field device according to claim 25 , wherein the first client device or application is a controller controlling one or more field devices including the field device and wherein the second client device or the second application is a condition monitoring application monitoring one or more field devices including the field device.

28 . The field device according to claim 17 , further comprising a communication adapter configured to be coupled to an advanced physical layer (APL) communication network and to receive via the APL communication network a power signal provided by an APL power switch either directly or via one or more APL field switches.

29 . A system comprising:

a controller controlling a plant that performs operations on one or more materials to transform the one or more materials into a product;

a communication network; and

a plurality of field devices coupled by the communication network to the controller, the plurality of field devices receiving commands from the controller and transmitting parameter values to the controller, each of the plurality of field devices comprising:

a processor; and

a memory device, coupled to the processor, the memory device storing (a) a plurality of pre-defined publish lists, each pre-defined publish list corresponding to one of at least two available publish categories, each pre-defined publish list comprising a particular set of parameters associated with a particular field device, and (ii) a set of instructions executable by the processor to cause the processor to:

receive, from a client device or application, during run-time operations of the plant, a message indicating a one of the at least two available publish categories, the one publish category indicating a category of information desired by the client device or application;

transmit, to the client device or application, an identification of each of the plurality of pre-defined publish lists that are stored in the memory device prior to receiving the message from the client device or application, corresponding to the indicated publish category;

receive, from the client device or application, a selection of one of the plurality of pre-defined publish lists identified by the particular field device; and

transmit, to the client device or application, the particular set of parameters associated with the selected one of the plurality of pre-defined publish lists.

30 . The system according to claim 29 , wherein the client device or application is the controller.

31 . The system according to claim 29 , wherein the client device or application is a second field device.

32 . The system according to claim 29 , wherein the client device or application is an application communicating with the particular field device over the communication network using an edge gateway device.

33 . The system according to claim 29 , wherein the client device or application is an application executing on a cloud-computing platform and communicating with the particular field device over the communication network.

34 . The system according to claim 29 , wherein each of the plurality of field devices is configured to receive, from each of multiple different client devices or applications, a corresponding selection of one of the plurality of pre-defined publish lists, and to transmit, to each of the multiple different client devices or applications, the particular set of parameters associated with the particular pre-defined publish list selected by the particular client device or application.

35 . The system according to claim 29 , wherein each of the plurality of field devices is configured to receive, from a single client device or application, a selection of more than one of the plurality of pre-defined publish lists, and to transmit to the single client device or application, the particular set of parameters associated with each of the more than one of the plurality of pre-defined publish lists.

36 . The system according to claim 29 , wherein the communication network comprises:

advanced physical layer (APL) Ethernet wiring comprising ruggedized, two-wire, twisted pair Ethernet cable configured to provide loop-powered Ethernet connectivity;

one or more APL power switches each configured to provide Ethernet connectivity to other Ethernet devices and each including a power supply to provide power via the APL

Ethernet wiring; and

one or more APL field switches, each receiving power from one of the one or more APL power switches via the APL Ethernet wiring, and each configured to distribute both communication signals and power signals to the plurality of field devices communicatively coupled by APL Ethernet wiring to a respective APL field switch while complying with intrinsic safety requirements.

37 . The system according to claim 29 , wherein the plurality of pre-defined publish lists stored in the memory device of each of the plurality of field devices is specific to a type of the particular field device.

38 . The system according to claim 37 , wherein the type of the particular field device is one of: valve, flow measurement, pressure measurement, level measurement, and temperature measurement.

39 . A method comprising:

transmitting to a field device during run-time operations of a process plant, a message indicating a selection of a first one of a plurality of publish categories, each of the plurality of publish categories corresponding to a type of information;

receiving, from the field device, an identification of each of a plurality of publish lists that are pre-defined and stored on the field device prior to receiving the message, the identification corresponding to the first one of the plurality of publish categories, each of the plurality of publish lists comprising a particular set of parameters associated with the field device;

transmitting to the field device a selection of a first one of the plurality of publish lists identified by the field device; and

receiving, from the field device, the particular set of parameters associated with the first one of the plurality of publish lists.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 21, 2023
From: NIXON, MARK J.; LAW, GARY K.
To: FISHER-ROSEMOUNT SYSTEMS, INC.
Reel/Frame 065640/0075 →
Continuity (2)
Continuation 17017399 · Sep 10, 2020
Related Publication 20240089326A1 · Mar 14, 2024
References Cited (123)
US 8060012B2 · Sklovsky et al. · 2011 [cited by applicant]
US 8332567B2 · Burr et al. · 2012 [cited by applicant]
US 8516095B2 · Eisener et al. · 2013 [cited by applicant]
US 8898481B1 · Osburn, III et al. · 2014 [cited by applicant]
US 9699022B2 · Bale et al. · 2017 [cited by applicant]
US 9804647B2 · Nicholas et al. · 2017 [cited by applicant]
US 10999734B1 · Alexander et al. · 2021 [cited by applicant]
US 11076001B1 · Mohamed · 2021 [cited by applicant]
US 11256238B1 · Nixon et al. · 2022 [cited by applicant]
US 11275861B2 · Neitzel et al. · 2022 [cited by applicant]
US 11281650B2 · Okamura · 2022 [cited by applicant]
US 20020077711A1 · Nixon et al. · 2002 [cited by applicant]
US 20020163427A1 · Eryurek · 2002 [cited by examiner]
US 20040078600A1 · Nilsen et al. · 2004 [cited by applicant]
US 20050007249A1 · Eryurek et al. · 2005 [cited by applicant]
US 20060140209A1 · Cassiolato et al. · 2006 [cited by applicant]
US 20060238364A1 · Keefe et al. · 2006 [cited by applicant]
US 20070055391A1 · Schneider et al. · 2007 [cited by applicant]
US 20080133721A1 · Danz et al. · 2008 [cited by applicant]
US 20090292524A1 · Anne et al. · 2009 [cited by applicant]
US 20100280636A1 · Holland et al. · 2010 [cited by applicant]
US 20110258426A1 · Mujtaba et al. · 2011 [cited by applicant]
US 20140107808A1 · Yamamoto et al. · 2014 [cited by applicant]
US 20140277656A1 · Nixon · 2014 [cited by examiner]
US 20150066979A1 · Zhang et al. · 2015 [cited by applicant]
US 20150095789A1 · Hyde · 2015 [cited by applicant]
US 20150127120A1 · Telljohann et al. · 2015 [cited by applicant]
US 20160254609A1 · Larsson et al. · 2016 [cited by applicant]
US 20160378101A1 · Leonard · 2016 [cited by applicant]
US 20170102678A1 · Nixon · 2017 [cited by examiner]
US 20170199843A1 · Nixon et al. · 2017 [cited by applicant]
US 20170351226A1 · Bliss · 2017 [cited by applicant]
US 20180024847A1 · Campbell et al. · 2018 [cited by applicant]
US 20180026942A1 · De Ligt · 2018 [cited by examiner]
US 20180101152A1 · Jundt et al. · 2018 [cited by applicant]
US 20180107179A1 · Nixon · 2018 [cited by examiner]
US 20180210429A1 · Jundt · 2018 [cited by applicant]
US 20180299274A1 · Moghe et al. · 2018 [cited by applicant]
US 20180299849A1 · Martin et al. · 2018 [cited by applicant]
US 20190115785A1 · Kallamkote et al. · 2019 [cited by applicant]
US 20190138375A1 · Dinh et al. · 2019 [cited by applicant]
US 20190244517A1 · Moustafa et al. · 2019 [cited by applicant]
US 20190258214A1 · Iwayama · 2019 [cited by applicant]
US 20190320025A1 · Breter · 2019 [cited by applicant]
US 20190320451A1 · Hansen et al. · 2019 [cited by applicant]
US 20190334860A1 · Albrecht et al. · 2019 [cited by applicant]
US 20200081426A1 · Kane et al. · 2020 [cited by applicant]
US 20200235949A1 · Jones et al. · 2020 [cited by applicant]
US 20200287895A1 · Hottgenroth · 2020 [cited by applicant]
US 20200334402A1 · Grefen · 2020 [cited by applicant]
US 20200351089A1 · Wentz · 2020 [cited by applicant]
US 20200366513A1 · Yoneda · 2020 [cited by examiner]
US 20210081346A1 · Nixon et al. · 2021 [cited by applicant]
US 20210089278A1 · Dunn et al. · 2021 [cited by applicant]
US 20210233115A1 · Kardesler et al. · 2021 [cited by applicant]
US 20210266346A1 · Gordon et al. · 2021 [cited by applicant]
US 20230097557A1 · Ryecroft et al. · 2023 [cited by applicant]
US 20230314173A1 · Welle · 2023 [cited by examiner]
CN 101141339A · 2008 [cited by applicant]
CN 101232421A · 2008 [cited by applicant]
CN 101588262A · 2009 [cited by applicant]
CN 101651720A · 2010 [cited by applicant]
CN 102047223A · 2011 [cited by applicant]
CN 102073316A · 2011 [cited by applicant]
CN 102271053A · 2011 [cited by applicant]
CN 102594579A · 2012 [cited by applicant]
CN 104767682A · 2015 [cited by applicant]
CN 104823121A · 2015 [cited by applicant]
CN 104950837A · 2015 [cited by applicant]
CN 106506230A · 2017 [cited by applicant]
CN 107272480A · 2017 [cited by applicant]
CN 108028068A · 2018 [cited by applicant]
CN 108718110A · 2018 [cited by applicant]
CN 109143992A · 2019 [cited by applicant]
CN 109189008A · 2019 [cited by applicant]
CN 110109427A · 2019 [cited by applicant]
CN 111314495A · 2020 [cited by applicant]
CN 111600754A · 2020 [cited by applicant]
DE 19510247A1 · 1996 [cited by applicant]
DE 102017123821A1 · 2019 [cited by applicant]
EP 2897299A1 · 2015 [cited by applicant]
GB 2355082A · 2001 [cited by applicant]
GB 2568379A · 2019 [cited by applicant]
JP 2010524082A · 2010 [cited by applicant]
JP 2012068947A · 2012 [cited by applicant]
JP 2012090194A · 2012 [cited by applicant]
JP 2012182599A · 2012 [cited by applicant]
JP 2013089204A · 2013 [cited by applicant]
JP 2014507917A · 2014 [cited by applicant]
JP 2015503803A · 2015 [cited by applicant]
JP 2018014108A · 2018 [cited by applicant]
JP 2019106172A · 2019 [cited by applicant]
KR 1020190097744A · 2019 [cited by applicant]
WO WO2014051632A1 · 2014 [cited by applicant]
WO WO2018005479A1 · 2018 [cited by applicant]
WO WO2022008071A1 · 2022 [cited by applicant]
“FieldComm Group,” (2018). Retrieved from the Internet at: <URL:https://fieldcommgroup.org/sites/default/files/global/Singapore/5%20FCG-181012_APLinAnutshell_1v0.5pptx.pdf>. [cited by applicant]
“IEEE Computer Society, IEEE Standard for Ethernet Amendment 5: Phyical Layers Specification and Management Parameters for 10/Mb/s Operation and Associated Power Delievery Over a Single Balanced Pair of Conductors,” (Fe… [cited by applicant]
Alexander “DHCP Options and BOOTP Vendor Extensions,” Network Working Gropu (Mar. 1997). [cited by applicant]
Anonymous, “Advanced Physical Layer,” Wikipedia (2020). [cited by applicant]
Anonymous, “Ethernet-APL White Paper,” (2022). [cited by applicant]
Anonymous, “Programmable Logic Controller,” Wikipedia (2020). [cited by applicant]
Anonymous, “Public Key Infrastructure,” Wikipedia (2018). [cited by applicant]
Anonymous, “Time-Sensitive Networking,” Wikipedia (2020). [cited by applicant]
FieldComm Group “Ethernet To the Field,” (2020). [cited by applicant]
Hoffman “The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA,” Internet Engineering Task Force (Aug. 2012). [cited by applicant]
Larson, “Advanced Physical Layer Standard to Make Field-Level Ethernet a Reality,” (Jun. 2020). Retrieved from the Internet at: URL:https://www/controlglobal.com/articles/2020/advanced-physical-layer-standard-to-make-fi… [cited by applicant]
Search Report for Application No. GB2112178.5, dated May 4, 2022. [cited by applicant]
Search Report for Application No. GB2112206.4, dated Jan. 21, 2022. [cited by applicant]
Search Report for Application No. GB2112855.8, dated May 5, 2022. [cited by applicant]
Search Report for Application No. GB2112857.4, dated May 12, 2022. [cited by applicant]
Search Report for Application No. GB2112858.2, dated May 13, 2022. [cited by applicant]
Notification of the First Office Action for Chinese Application No. 202111062270.1, dated Oct. 21, 2024. [cited by applicant]
Notification of the First Office Action for Chinese Application No. 202111063528.X, dated Oct. 19, 2024. [cited by applicant]
First Chinese Office Action for Application No. 202111063387.1, dated Nov. 12, 2024. [cited by applicant]
Yufei et al., “Design and implement of data communication interface for power plant,” Electric Power Automation Equipment, 30(6) (2010). [cited by applicant]
IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks, IEEE Std 802. IQ-2018 (Revision of IEEE Std 802. IQ-2014), May 7, 2018, p. 197-205. <URL:https://ieeexplore.ieee.org/document/8403927>. [cited by applicant]
Office Action for Chinese Application No. 202111061968.1, dated Mar. 20, 2025. [cited by applicant]
Office Action for Chinese Application No. 202111063855.5, dated Mar. 18, 2025. [cited by applicant]
Office Action for Japanese Application No. 2021-136996, dated Mar. 18, 2025. [cited by applicant]
Office Action for Japanese Application No. 2021-142626, dated Mar. 25, 2025. [cited by applicant]
Office Action for Japanese Application No. 2021-142646, dated Apr. 7, 2025. [cited by applicant]
Takahashi, Japan Field Comm Group, Explosion-proof Ethernet (APL), Mar. 8, 2019. <URL:https://www.fieldcommgroup.org/sites/default/files/imce_files/technology/documents/4_apl.pdf>. [cited by applicant]