IP Library › Granted Patent US 12,619,209
Granted Patent B2
US 12,619,209 · App. 17/504,945 · Granted May 5, 2026

Utilizing quality-of-service metrics to facilitate transitions between I/O channels for I/O server services

Inventors: Anthony Amaro, Jr. (Round Rock, TX); Mark J. Nixon (Thorndale, TX)
Assignee: FISHER-ROSEMOUNT SYSTEMS, INC.
G05B19/0425G05B19/0421H04L1/22H04L12/40143H04L45/302H04L67/10G05B2219/21062G05B2219/25428H04L2012/4026
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,619,209
App. No.
17/504,945
Filed
Oct 19, 2021
Granted
May 5, 2026
Kind
B2
Art Unit
2451
USPC
709/223
Abstract

An I/O server service interfaces with multiple containerized controller services each implementing the same control routine to control the same portion of the same plant. The I/O server service may provide the same controller inputs to each of the containerized controller services (e.g., representing measurements obtained by field devices and transmitted by the field devices to the I/O server service). Each containerized controller service executes the same control routine to generate a set of controller outputs. The I/O server service receives each set of controller outputs and forwards an “active” set to the appropriate field devices. The I/O server service may utilize a quality-of-service metric to determine which controller outputs and/or I/O channel is “active.” The I/O server service and other services, such as an orchestrator service, may continuously evaluate performance and resource utilization in the control system, and may dynamically activate and deactivate controller services as appropriate.

Claims (46)

1 . A method of transitioning between containerized controller services in a process control environment, the method comprising:

receiving process control traffic, at one or more I/O server services, from a plurality of controller services by way of a plurality of I/O channels each of which couples the one or more I/O server services to a different one of the plurality of controller services, wherein the plurality of I/O channels includes a first I/O channel that is designated as an active I/O channel and one or more other I/O channels that are designated as inactive I/O channels, wherein each controller service is implemented in a respective container and is executing a same control routine to generate process control traffic including a set of commands to control a same portion of an industrial process via the same one or more field devices and sends the process control traffic including the set of commands to the same portion of the industrial process including the same one or more field devices via the one or more I/O server services;

utilizing, by the one or more I/O server services, the process control traffic received via the first I/O channel to control the one or more field devices to drive one or more process outputs and to thereby control the portion of the industrial process thereby controlling the portion of the industrial process using the process control traffic from a first one of the controller services that is connected to the one or more I/O server services via the first I/O channel;

evaluating a plurality of a quality-of-service (“QoS”) metrics for the plurality of I/O channels, wherein each of the QoS metrics corresponds to a different one of the plurality of I/O channels;

detecting a second I/O channel from the one or more other I/O channels that has a best QoS metric from the plurality of QoS metrics; and

responding to detecting the best QoS metric by transitioning the active I/O channel, including:

(i) designating the second I/O channel as the active I/O channel and the first I/O channel as one of the inactive channels; and

(ii) utilizing process control traffic received via the second I/O channel to control the one or more field devices to drive the one or more process outputs and to thereby control the portion of the industrial process thereby controlling the portion of the industrial process using the process control traffic from a second one of the controller services that is connected to the one or more I/O server services via the second I/O channel.

2 . The method of claim 1 , wherein the QoS metric is a latency metric indicating a length of time associated with delivering the process control traffic to the one or more I/O server services.

3 . The method of claim 1 , wherein the one or more I/O server services is a plurality of I/O server services each executed in a different container, wherein the plurality of I/O server services includes (i) a first I/O server service that has been designated as an active I/O server service and (ii) one or more other I/O server services, wherein receiving the process control traffic comprises receiving the process control traffic at each of the plurality of I/O server services.

4 . The method of claim 3 , further comprising selecting a second I/O server service as the active I/O server service; and

wherein utilizing process control traffic received via the second I/O channel to control the one or more field devices comprises controlling the one or more field devices via the second I/O server service.

5 . The method of claim 3 , further comprising performing a load balancing analysis of the physical resources implementing the plurality of I/O server services; wherein selecting the second I/O server service is responsive to results of the load balancing analysis.

6 . A process control system, comprising:

one or more field devices configured for implementation in a process control system to facilitate controlling a particular portion of an industrial process at a process plant; and

one or more hosts that are communicatively coupled to the one or more field devices and that are configured to:

(i) receive process control traffic from a plurality of controller services by way of a plurality of I/O channels each of which couples the one or more I/O server services to a different one of the plurality of controller services, wherein the plurality of I/O channels includes a first I/O channel that is designated as an active I/O channel and one or more other I/O channels that are designated as inactive I/O channels, wherein each controller service is implemented in a respective container and is executing a same control routine to generate process control traffic including a set of commands to control a same portion of an industrial process via the same one or more field devices and sends the process control traffic including the set of commands to the same portion of the industrial process including the same one or more field devices via the one or more I/O server services;

(ii) utilize the process control traffic received via the first I/O channel to control the one or more field devices to drive one or more process outputs and to thereby control the portion of the industrial process thereby controlling the portion of the industrial process using the process control traffic from a first one of the controller services that is connected to the one or more I/O server services via the first I/O channel;

(iii) evaluate a plurality of a quality-of-service (“QoS”) metrics for the plurality of I/O channels, wherein each of the QoS metrics corresponds to a different one of the plurality of I/O channels;

(iv) detect a second I/O channel from the one or more other I/O channels that has a best QoS metric from the plurality of QoS metrics; and

(v) respond to detecting the best QoS metric by transitioning the active I/O channel, including:

(a) designate the second I/O channel as the active I/O channel and the first I/O channel as one of the inactive channels; and

(b) utilize process control traffic received via the second I/O channel to control the one or more field devices to drive the one or more process outputs and to thereby control the portion of the industrial process thereby controlling the portion of the industrial process using the process control traffic from a second one of the controller services that is connected to the one or more I/O server services via the second I/O channel.

7 . The process control system of claim 6 , wherein the QoS metric is a latency metric indicating a length of time associated with delivering the process control traffic to the one or more I/O server services.

8 . The process control system of claim 6 , wherein the one or more I/O server services is a plurality of I/O server services each executed in a different container, wherein the plurality of I/O server services includes (i) a first I/O server service that has been designated as an active I/O server service and (ii) one or more other I/O server services, wherein receiving the process control traffic includes receiving the process control traffic at each of the plurality of I/O server services.

9 . The process control system of claim 8 , wherein the one or more I/O server services is configured to select a second I/O server service as the active I/O server service; and

wherein utilizing process control traffic received via the second I/O channel to control the one or more field devices comprises controlling the one or more field devices via the second I/O server service.

10 . The process control system of claim 8 , further comprising an orchestrator service configured to select a second I/O server service as the active I/O server service; and

wherein utilizing process control traffic received via the second I/O channel to control the one or more field devices comprises controlling the one or more field devices via the second I/O server service.

11 . A server configured to facilitate transitioning between containerized controller services in a process control environment, the server comprising:

a communication interface configured to be communicatively coupled to a plurality of I/O channels each of which couples the communication interface to a different one of a plurality of controller services;

one or more processors communicatively coupled to the communication interface; and

one or more memories, communicatively coupled to the one or more processors, storing machine readable instructions that, when executed by the one or more processors, cause the one or more processors to:

(i) receive process control traffic from the plurality of controller services by way of the communication interface, wherein the plurality of I/O channels includes a first I/O channel that is designated as an active I/O channel and one or more other I/O channels that are designated as inactive I/O channels, wherein each controller service is implemented in a respective container and is executing a same control routine to generate process control traffic including a set of commands to control a same portion of an industrial process via the same one or more field devices and sends the process control traffic including the set of commands to the same portion of the industrial process including the same one or more field devices via the one or more I/O server services;

(ii) utilize the process control traffic received via the first I/O channel to control the one or more field devices to drive one or more process outputs and to thereby control the portion of the industrial process thereby controlling the portion of the industrial process using the process control traffic from a first one of the controller services that is connected to the one or more I/O server services via the first I/O channel;

(iii) evaluate a plurality of a quality-of-service (“QoS”) metrics for the plurality of I/O channels, wherein each of the QoS metrics corresponds to a different one of the plurality of I/O channels;

(iv) detect a second I/O channel from the one or more other I/O channels that has a best QoS metric from the plurality of QoS metrics; and

(v) respond to detecting the best QoS metric by transitioning the active I/O channel, including:

(a) designate the second I/O channel as the active I/O channel and the first I/O channel as one of the inactive channels; and

(b) utilize process control traffic received via the second I/O channel to control the one or more field devices to drive the one or more process outputs and to thereby control the portion of the industrial process thereby controlling the portion of the industrial process using the process control traffic from a second one of the controller services that is connected to the one or more I/O server services via the second I/O channel.

12 . The server of claim 11 , wherein the QoS metric is a latency metric indicating a length of time associated with delivering the process control traffic to the one or more I/O server services.

13 . The server of claim 11 , wherein the one or more I/O server services is a plurality of I/O server services each executed in a different container, wherein the plurality of I/O server services includes (i) a first I/O server service that has been designated as an active I/O server service and (ii) one or more other I/O server services, wherein receiving the process control traffic includes receiving the process control traffic at each of the plurality of I/O server services.

14 . The server of claim 13 , wherein the one or more I/O server services is configured to select a second I/O server service as the active I/O server service; and

wherein utilizing process control traffic received via the second I/O channel to control the one or more field devices comprises controlling the one or more field devices via the second I/O server service.

15 . The server of claim 13 , wherein the one or more I/O server services is configured to receive from an orchestrator service ca selection of a second I/O server service as the active I/O server service; and

wherein utilizing process control traffic received via the second I/O channel to control the one or more field devices comprises controlling the one or more field devices via the second I/O server service.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 20, 2021
From: AMARO, ANTHONY, JR.; NIXON, MARK J.
To: FISHER-ROSEMOUNT SYSTEMS, INC.
Reel/Frame 057844/0718 →
Continuity (2)
Provisional Application 63211535 · Jun 16, 2021
Related Publication 20220404789A1 · Dec 22, 2022
References Cited (215)
US 7281250B2 · Ohsawa et al. · 2007 [cited by applicant]
US 7293080B1 · Clemm et al. · 2007 [cited by applicant]
US 8924103B2 · Dammeyer et al. · 2014 [cited by applicant]
US 9183560B2 · Abelow et al. · 2015 [cited by applicant]
US 9451012B1 · Neill et al. · 2016 [cited by applicant]
US 9521115B1 · Woolward · 2016 [cited by applicant]
US 9934671B1 · Anderson et al. · 2018 [cited by applicant]
US 9992726B2 · Shepard et al. · 2018 [cited by applicant]
US 10303576B1 · Seymour et al. · 2019 [cited by applicant]
US 10360050B2 · He et al. · 2019 [cited by applicant]
US 10382203B1 · Loladia et al. · 2019 [cited by applicant]
US 10547521B1 · Roy et al. · 2020 [cited by applicant]
US 10574729B2 · Hadfield et al. · 2020 [cited by applicant]
US 10663956B2 · Jundt et al. · 2020 [cited by applicant]
US 10915081B1 · Nixon et al. · 2021 [cited by applicant]
US 10977070B2 · Li et al. · 2021 [cited by applicant]
US 11126469B2 · Reque et al. · 2021 [cited by applicant]
US 11281492B1 · Rebeja et al. · 2022 [cited by applicant]
US 11513877B2 · Biernat et al. · 2022 [cited by applicant]
US 11541447B2 · Beyfuss et al. · 2023 [cited by applicant]
US 11637918B2 · Yarvis et al. · 2023 [cited by applicant]
US 11960588B2 · Amaro, Jr. et al. · 2024 [cited by applicant]
US 20020126620A1 · Heckel et al. · 2002 [cited by applicant]
US 20030023795A1 · Packwood et al. · 2003 [cited by applicant]
US 20040114605A1 · Karaoguz · 2004 [cited by examiner]
US 20040260404A1 · Russell · 2004 [cited by applicant]
US 20050160413A1 · Broussard · 2005 [cited by applicant]
US 20050220127A1 · Cane et al. · 2005 [cited by applicant]
US 20060167886A1 · Kantesaria et al. · 2006 [cited by applicant]
US 20070006228A1 · Grobman et al. · 2007 [cited by applicant]
US 20070076742A1 · Du · 2007 [cited by examiner]
US 20090083843A1 · Wilkinson, Jr. et al. · 2009 [cited by applicant]
US 20090327606A1 · Galloway et al. · 2009 [cited by applicant]
US 20100235831A1 · Dittmer et al. · 2010 [cited by applicant]
US 20100263025A1 · Neitzel et al. · 2010 [cited by applicant]
US 20100290351A1 · Toepke · 2010 [cited by examiner]
US 20110021131A1 · Chen · 2011 [cited by applicant]
US 20110125921A1 · Karenos · 2011 [cited by examiner]
US 20110265077A1 · Collison et al. · 2011 [cited by applicant]
US 20120102492A1 · Iwata et al. · 2012 [cited by applicant]
US 20120259436A1 · Resurreccion · 2012 [cited by examiner]
US 20130031249A1 · Gunzert · 2013 [cited by examiner]
US 20130031294A1 · Feng et al. · 2013 [cited by applicant]
US 20130086594A1 · Cottrell · 2013 [cited by applicant]
US 20130212129A1 · Lawson et al. · 2013 [cited by applicant]
US 20140019491A1 · Hamel · 2014 [cited by applicant]
US 20140344269A1 · Dong · 2014 [cited by examiner]
US 20150378356A1 · Hefeeda · 2015 [cited by examiner]
US 20160019084A1 · Forestiero et al. · 2016 [cited by applicant]
US 20160033006A1 · Leverington · 2016 [cited by applicant]
US 20160043866A1 · Nixon · 2016 [cited by applicant]
US 20160134596A1 · Kovacs et al. · 2016 [cited by applicant]
US 20160164743A1 · Cimprich et al. · 2016 [cited by applicant]
US 20160165516A1 · Shepard · 2016 [cited by examiner]
US 20160299772A1 · Seenappa et al. · 2016 [cited by applicant]
US 20160373310A1 · Banikazemi · 2016 [cited by examiner]
US 20170026677A1 · Kim et al. · 2017 [cited by applicant]
US 20170095405A1 · Afsarifard et al. · 2017 [cited by applicant]
US 20170149843A1 · Amulothu et al. · 2017 [cited by applicant]
US 20170279770A1 · Woolward · 2017 [cited by applicant]
US 20170308330A1 · Suresh · 2017 [cited by examiner]
US 20170344408A1 · Tan et al. · 2017 [cited by applicant]
US 20170359245A1 · Dintenfass et al. · 2017 [cited by applicant]
US 20170366551A1 · Brandwine · 2017 [cited by applicant]
US 20180052628A1 · Endo et al. · 2018 [cited by applicant]
US 20180067848A1 · Baldwin et al. · 2018 [cited by applicant]
US 20180112795A1 · Anderson et al. · 2018 [cited by applicant]
US 20180113442A1 · Nixon et al. · 2018 [cited by applicant]
US 20180114414A1 · Law et al. · 2018 [cited by applicant]
US 20180144144A1 · Luo et al. · 2018 [cited by applicant]
US 20180164791A1 · Debes et al. · 2018 [cited by applicant]
US 20180227369A1 · DuCray et al. · 2018 [cited by applicant]
US 20180299849A1 · Martin et al. · 2018 [cited by applicant]
US 20180316729A1 · Chauvet et al. · 2018 [cited by applicant]
US 20180341241A1 · Song · 2018 [cited by applicant]
US 20180375936A1 · Chirammal et al. · 2018 [cited by applicant]
US 20190041824A1 · Chavez et al. · 2019 [cited by applicant]
US 20190041830A1 · Yarvis et al. · 2019 [cited by applicant]
US 20190042378A1 · Wouhaybi et al. · 2019 [cited by applicant]
US 20190109820A1 · Clark et al. · 2019 [cited by applicant]
US 20190140918A1 · Xu et al. · 2019 [cited by applicant]
US 20190294124A1 · Law et al. · 2019 [cited by applicant]
US 20190317465A1 · Wei et al. · 2019 [cited by applicant]
US 20190324431A1 · Cella et al. · 2019 [cited by applicant]
US 20190369574A1 · Val et al. · 2019 [cited by applicant]
US 20190379590A1 · Rimar et al. · 2019 [cited by applicant]
US 20200067789A1 · Khuti et al. · 2020 [cited by applicant]
US 20200092254A1 · Goeringer et al. · 2020 [cited by applicant]
US 20200092271A1 · Kumar et al. · 2020 [cited by applicant]
US 20200099531A1 · Chidambaram et al. · 2020 [cited by applicant]
US 20200102507A1 · Sun et al. · 2020 [cited by applicant]
US 20200112442A1 · Wentz · 2020 [cited by applicant]
US 20200174462A1 · Sirohi et al. · 2020 [cited by applicant]
US 20200209816A1 · Cebasek et al. · 2020 [cited by applicant]
US 20200225649A1 · Cahill et al. · 2020 [cited by applicant]
US 20200226123A1 · Nixon et al. · 2020 [cited by applicant]
US 20200228316A1 · Cahill · 2020 [cited by applicant]
US 20200228342A1 · Nixon et al. · 2020 [cited by applicant]
US 20200241903A1 · Wang et al. · 2020 [cited by applicant]
US 20200310394A1 · Wouhaybi et al. · 2020 [cited by applicant]
US 20200322286A1 · Mehta et al. · 2020 [cited by applicant]
US 20200387136A1 · Pöschmann et al. · 2020 [cited by applicant]
US 20200387144A1 · Nixon et al. · 2020 [cited by applicant]
US 20200387145A1 · Nixon et al. · 2020 [cited by applicant]
US 20200387146A1 · Nixon et al. · 2020 [cited by applicant]
US 20200396225A1 · Bhatia et al. · 2020 [cited by applicant]
US 20200401116A1 · McLaughlin et al. · 2020 [cited by applicant]
US 20210011772A1 · Zhou et al. · 2021 [cited by applicant]
US 20210044564A1 · Victor et al. · 2021 [cited by applicant]
US 20210058399A1 · Kapoor et al. · 2021 [cited by applicant]
US 20210089015A1 · Law et al. · 2021 [cited by applicant]
US 20210089354A1 · Nixon · 2021 [cited by examiner]
US 20210089526A1 · Nixon et al. · 2021 [cited by applicant]
US 20210089542A1 · Nixon et al. · 2021 [cited by applicant]
US 20210089592A1 · Nixon et al. · 2021 [cited by applicant]
US 20210089593A1 · Nixon et al. · 2021 [cited by applicant]
US 20210092173A1 · Nixon et al. · 2021 [cited by applicant]
US 20210109658A1 · Mallick · 2021 [cited by examiner]
US 20210149637A1 · Hallman, Jr. et al. · 2021 [cited by applicant]
US 20210271489A1 · Singhal · 2021 [cited by applicant]
US 20210294659A1 · Amit · 2021 [cited by applicant]
US 20210356944A1 · Chauvet et al. · 2021 [cited by applicant]
US 20210384058A1 · Harada et al. · 2021 [cited by applicant]
US 20220012137A1 · Xiao et al. · 2022 [cited by applicant]
US 20220019475A1 · Dobson et al. · 2022 [cited by applicant]
US 20220058012A1 · Kaushik et al. · 2022 [cited by applicant]
US 20220070112A1 · Mazzitelli et al. · 2022 [cited by applicant]
US 20220091583A1 · Biernat et al. · 2022 [cited by applicant]
US 20220103580A1 · Manickam et al. · 2022 [cited by applicant]
US 20220108806A1 · Kommalapati et al. · 2022 [cited by applicant]
US 20220128982A1 · Mansfield · 2022 [cited by applicant]
US 20220229707A1 · Lange et al. · 2022 [cited by applicant]
US 20220283571A1 · Vieira et al. · 2022 [cited by applicant]
US 20220404788A1 · Amaro, Jr. et al. · 2022 [cited by applicant]
US 20220404798A1 · Amaro, Jr. et al. · 2022 [cited by applicant]
US 20220404812A1 · Amaro, Jr. et al. · 2022 [cited by applicant]
US 20240004688A1 · Shigemori · 2024 [cited by applicant]
US 20240031370A1 · Ubach et al. · 2024 [cited by applicant]
CN 115052033A · 2022 [cited by applicant]
DE 102019119714A1 · 2021 [cited by applicant]
EP 1492310A2 · 2004 [cited by applicant]
EP 2790101A1 · 2014 [cited by applicant]
EP 3382546A1 · 2018 [cited by applicant]
GB 2403043A · 2004 [cited by applicant]
GB 2410573A · 2005 [cited by applicant]
GB 2481753A · 2012 [cited by applicant]
GB 2575758A · 2020 [cited by applicant]
GB 2589710A · 2021 [cited by applicant]
WO WO2014124701A1 · 2014 [cited by applicant]
WO WO2016090292A1 · 2016 [cited by applicant]
WO WO2017064560A1 · 2017 [cited by applicant]
WO WO2017066304A1 · 2017 [cited by applicant]
WO WO2017121928A1 · 2017 [cited by applicant]
WO WO2018234741A1 · 2018 [cited by applicant]
WO WO2020202126A1 · 2020 [cited by applicant]
WO WO2020251828A1 · 2020 [cited by applicant]
WO WO2021079357A1 · 2021 [cited by applicant]
Computer and Information Security Handbook, 3rd Edition (2017). Select pages. [cited by applicant]
Emerson & PreScouter, “Software Defined Architecture for Embedded Applications,” Research Support Service (2020). [cited by applicant]
Koziolek et al., “Self-Commissioning Industrial IoT-Systems in Process Automation,” IEEE International Conference on Software Architecture, pp. 196-205 (2018). [cited by applicant]
Madiwalar et al., “Plug and produce for Industry 4.0 using software-defined networking and OPC UA”, 24th IEEE International Conference on Emerging Technologies and Factory Automation (ETFA), pp. 126-133 (Sep. 2019). [cited by applicant]
NAMUR Recommendation, NAMUR Open Architecture NOA Concept (2020). [cited by applicant]
Pribis et al., “An Industrial Communication Platform for Industry 4.0—Case Study,” Cybernetics & Informatics, pp. 1-8 (2020). [cited by applicant]
Profanter et al., “OPC UA for Plug & Produce: Automatic Device Discovery Using LDS-ME, ” 22nd IEEE Interational Conference on Emerging Technologies and Factory Automation, pp. 1-8 (2017). [cited by applicant]
Search Report for Application No. GB2208755.5, dated Feb. 10, 2023. [cited by applicant]
Search Report for Application No. GB2208757.1, dated Feb. 10, 2023. [cited by applicant]
Search Report for Application No. GB2208758.9, dated Dec. 16, 2022. [cited by applicant]
Search Report for Application No. GB2208759.7, dated Dec. 16, 2022. [cited by applicant]
Search Report for Application No. GB2208766.2, dated Feb. 16, 2023. [cited by applicant]
Search Report for Application No. GB2208768.8, dated Dec. 7, 2022. [cited by applicant]
Search Report for Application No. GB2208769.6, dated Dec. 7, 2022. [cited by applicant]
Search Report for Application No. GB2208770.4, dated Dec. 7, 2022. [cited by applicant]
Search Report for Application No. GB2208771.2, dated Dec. 12, 2022. [cited by applicant]
Search Report for Application No. GB2208794.4, dated Jan. 17, 2023. [cited by applicant]
Search Report for Application No. GB2208795.1, dated Jan. 17, 2023. [cited by applicant]
Search Report for Application No. GB2208796.9, dated Nov. 10, 2022. [cited by applicant]
Search Report for Application No. GB2208797.7, dated Dec. 1, 2022. [cited by applicant]
Search Report for Application No. GB2208857.9, dated Nov. 18, 2022. [cited by applicant]
Search Report for Application No. GB2208858.7, dated Nov. 18, 2022. [cited by applicant]
Sung et al., “Description lookup based UPnP extension for wireless sensor networks”, Proceedings of the 2009 6th annual international mobile and ubiquitous systems: Networking & Services, MobiQuitous (Jul. 2009). [cited by applicant]
“Kubernetes—Web UI (Dashboard),” (2021). [cited by applicant]
Aftab et al., “Analysis of identifiers in IoT platforms”, Digital Communications and Networks, 6(3):333-340 (2019). [cited by applicant]
Alaasam et al., “Stateful Stream Processing for Digital Twins,” International Multi-Conference on Engineering, Computer and Information Sciences (Oct. 21, 2019). [cited by applicant]
Bellini et al., “High Level Control of Chemical Plant by Industry 4.0 Solutions,” Journal of Industrial Information Integration, vol. 26 (Sep. 2, 2021). [cited by applicant]
Dobaj et al., “A Microservice Architecture for the Industrial Internet-Of-Things”, Computational Biology and Bioinformatics (Jul. 4, 2018). [cited by applicant]
Greevenbosch, “Use Cases and Requirements for Authentication, Authorisation and Revocation in the Internet of Things; draft-greevenbrosch-dice-authent-author-revoc-00.txt,” Standardworkingdraft, Internet Society (2013). [cited by applicant]
Hmaity et al. “Virtual Network Function Placement for Resilient Service Chain Provisioning”, 978-4673-9023-1, 2016, IEEE (Year: 2016). [cited by applicant]
Houmani et al., “Enhancing microservices architectures using data-driven service discovery and QoS guarantees”, 2020 20th IEEE/ACM International Symposium on Cluster, Cloud and Internet Computing (CCGRID), IEEE (May 11,… [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/027978, dated Dec. 11, 2023. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/027988, dated Oct. 25, 2023. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/028003, dated Oct. 25, 2023. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/028005, dated Oct. 26, 2023. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/028027, dated Nov. 7, 2023. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/028029, dated Oct. 27, 2023. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/033926, dated Mar. 18, 2024. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/034272, dated Jan. 22, 2024. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/034349, dated Jan. 18, 2024. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/034351, dated Jan. 22, 2024. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/035611, dated Jan. 25, 2024. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/035613, dated Jan. 26, 2024. [cited by applicant]
International Search Report and Written Opinion for Application No. PCT/US2023/035618, dated Mar. 21, 2024. [cited by applicant]
Jairo et al., “Deliverable D1.1. Review of Reference Architectures for IoT Enabled Agriculture Development. Consultandy Design of a reference architecture for an IoT sensor network. Company International Center for Trop… [cited by applicant]
Jin et al., “Secure Edge Computing Management Based on Independent Microservices Providers for Gateway-Centric IoT Networks”, IEEE Access, IEEE, 8:187975-187990 (2020). [cited by applicant]
Kashyap: “Yokogawa Cloud Architecture for Smart Manufacturing”, Yokogawa technical report (Nov. 10, 2023). [cited by applicant]
Khalyly et al., “Smart Agent Edge Microservices Deployment pproach”, 2020 International Conference on Decision AID Ciences and Application (DASA), IEEE (Nov. 8, 2020). [cited by applicant]
Malakuti et al., “A Four-Layer Architecture Pattern for Constructing and Managing Digital Twins,” Advances in Databases and Information Systems, 231-246 (2019). [cited by applicant]
Pontarolli et al., “Towards Security Mechanisms for an Industrial Microservice-Oriented Architecture,” 14th IEEE International Conference on Industry Applications (2021). [cited by applicant]
Radchenko et al., “Micro-Workflow: Kafka and Keplar Fusion to Support Digital Twins of Industrial Processes,” IEEE/ACM International Conference on Utility and Cloud Computing Companion (Dec. 17, 2018). [cited by applicant]
Search Report for Application No. GB2208756.3, dated Feb. 23, 2023. [cited by applicant]
Search Report for Application No. GB2208780.3, dated Feb. 22, 2023. [cited by applicant]
Search Report for Application No. GB2208821.5, dated Mar. 31, 2023. [cited by applicant]
Search Report for Application No. GB2208856.1, dated Jan. 18, 2023. [cited by applicant]
Steindl et al., “Semantic Microservice Framework for Digital Twins,” Applied Sciences, 11(12):1-19 (2021). [cited by applicant]
Tomarchio et al., “TORCH: A TOSCA-Based Orchestrator of Multi-Cloud Containerised Applications,” Journal of Grid Computing (2021). [cited by applicant]
Tundo et al., “Declarative Dashboard Generation,” IEEE Internation Symposium on Software Reliability Engineering Workshops (2020). [cited by applicant]