# US 12,225,093 B2 · Systems and methods for providing a hydrocarbon refining train IIoT service > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,225,093 B2 - Document ID: US12225093B2 - Status: Granted - Kind: B2 - Application number: 18/358,669 - Filed: 2023-07-25 - Published: 2024-07-04 - Granted: 2025-02-11 - Earliest claimed: 2022-12-28 - Assignees: Saudi Arabian Oil Company - Applicants: Saudi Arabian Oil Company - Inventors: Md Fazlul Alam Chowdhury - Web page: https://patentgrep.com/patent/US12225093B2 ## CPC - G06F 9/226: {Microinstruction function, e.g. input/output microinstruction; diagnostic microinstruction; microinstruction format} - H04L 67/50: Network services - G16Y 40/35: Management of things, i.e. controlling in accordance with a policy or in order to achieve specified objectives - G16Y 40/50: Safety; Security of things, users, data or systems - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G16Y: INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT] ## Abstract Provided is a system for an industrial IoT (IIoT) service that includes a control system with a processor and a memory, the system being configured to provide an application programming interface (API) gateway to create a first microservice API that connects with a first plurality of networks of a first type that host a respective plurality of first IoT devices, and create a second microservice API that connects with a second plurality of networks of a second type that host a respective plurality of second IoT devices. The system may receive a request for device data from an IoT device, determine that the IoT device is located in one of the first plurality of networks, and communicate the request from a parameter output translation module to the first microservice API. ## Claims ### Claim 1 A hydrocarbon refining train industrial internet of things (IIoT) system for providing an IIoT service, comprising: a first plurality of refining train internet of things (IoT) devices coupled to a first network of a first type; a second plurality of refining train IoT devices coupled to a second network of a second type; a first refining train parameter module coupled to at least one of the first plurality of IoT devices, the first refining train parameter module configured to request data for the at least one of the first plurality of refining train IoT devices; a second refining train parameter module coupled to at least one of the second plurality of refining train IoT devices, the second refining train parameter module configured to request data for the at least one of the first plurality of refining train IoT devices; a hydrocarbon refining train parameter control system that includes a processor, a refining train parameter memory, a memory component, and a refining train parameter output translation module, the memory component storing a refining train control architecture that, when executed by the processor, causes the hydrocarbon refining train IIoT system to perform at least the following: creating a first microservice API that connects with the first network that hosts the first plurality of refining train IoT devices, wherein the first microservice API stores routing data associated with the first plurality of refining train IoT devices; creating a second microservice API that connects with the second network of the second type that hosts the second plurality of refining train IoT devices, wherein the second microservice API stores routing data associated with the second plurality of refining train IoT devices; receiving a request for device data for a refining train IoT device of the first plurality of IoT devices or the second plurality of refining train IoT devices, wherein the request includes a tag name, a network type, time data, and a requester identity; determining from the network type that the refining train IoT device is located in the first network of a plurality of networks of the first type; communicating the request from the refining train parameter output translation module to the first microservice API, wherein the first microservice API utilizes the routing data to determine which of the plurality of networks the refining train IoT device resides and establishes a tunnel with the refining train IoT device; and communicating, via the refining train parameter output translation module, the device data via the tunnel to the refining train IoT device; wherein the logic further causes the hydrocarbon refining train IIoT system to provide a content delivery network (CDN) that is configured to control a speed and volume of delivery of the device data. ### Claim 2 (depends on 1) The hydrocarbon refining train IIoT system of claim 1, wherein the first microservice API includes at least one of the following a data historian service component, an open data protocol (ODATA) service component, a DVR system, or a lab information system. ### Claim 3 (depends on 1) The hydrocarbon refining train IIoT system of claim 1, wherein the first microservice API utilizes the requester identity to determine whether the refining train IoT device that requested the refining train IoT device is authorized to access the device data. ### Claim 4 (depends on 1) The hydrocarbon refining train IIoT system of claim 1, wherein the refining train control architecture further creates a third microservice API that connects with a third plurality of networks of a third type that host a respective plurality of third refining train IoT devices, wherein the third microservice API stores routing data associated with the respective plurality of third refining train IoT devices. ### Claim 5 (depends on 1) The hydrocarbon refining train IIoT system of claim 1, wherein the logic further causes the hydrocarbon refining train IIoT system to provide a service client that is configured to receive the request for the device data and provide the request to an refining train API gateway of the refining train control architecture. ### Claim 6 (depends on 1) The hydrocarbon refining train IIoT system of claim 1, wherein the logic further causes the hydrocarbon refining train IIoT system to provide an identity provider that is configured to confirm an identity of the refining train IoT device that requested the device data. ### Claim 7 (depends on 1) The hydrocarbon refining train IIoT system of claim 1, wherein the logic further causes the hydrocarbon refining train IIoT system to provide a service discovery component that is configured to detect refining train IoT devices and microservices on the first network. ### Claim 8 (depends on 1) The hydrocarbon refining train IIoT system of claim 1, wherein the logic further causes the hydrocarbon refining train IIoT system to provide a management component that is configured to establish the tunnel with the refining train IoT device for communicating the device data. ### Claim 9 (depends on 1) The hydrocarbon refining train IIoT system of claim 1, wherein the logic further causes the hydrocarbon refining train IIoT system to provide a static content component that is configured to store and transfer static device data. ### Claim 10 A method comprising: creating a first microservice API that connects with a first plurality of networks of a first type that host a respective plurality of first internet of things (IoT) devices, wherein the first microservice API stores routing data associated with the respective plurality of first IoT devices; creating a second microservice API that connects with a second plurality of networks of a second type that host a respective plurality of second IoT devices, wherein the second microservice API stores routing data associated with the respective plurality of second IoT devices; receiving a request for device data from an IoT device, wherein the request includes a tag name, a network type, time data, and a requester identity; determining from the network type that the IoT device is located in one of the first plurality of networks; communicating the request to the first microservice API, wherein the first microservice API utilizes the routing data to determine which of the first plurality of networks the IoT device resides and establishes a tunnel with the IoT device; receiving the device data via the tunnel; and providing a content delivery network (CDN) that is configured to control a speed and volume of delivery of the device data. ### Claim 11 (depends on 10) The method of claim 10, further comprising retrieving device data for end systems via ODATA services, DVR system, or a lab information system. ### Claim 12 (depends on 10) The method of claim 10, further comprising isolating the device data and employing multi-level security. ### Claim 13 (depends on 12) The method of claim 12, wherein the multi-level security uses disk encryption and/or two-factor authentication. ### Claim 14 (depends on 10) The method of claim 10, further comprising utilizing a requester identity to determine whether the IoT device that requested the IoT device is authorized to access the device data. ### Claim 15 (depends on 10) The method of claim 10, further comprising creating a third microservice API that connects with a third plurality of networks of a third type that host a respective plurality of third IoT devices, wherein the third microservice API stores routing data associated with the respective plurality of third IoT devices. ### Claim 16 A non-transitory computer readable medium comprising computer readable instructions, which stores logic that, when executed by a computing device, causes the computing device to perform at least the following: creating a first microservice API that connects with a first plurality of networks of a first type that host a respective plurality of first internet of things (IoT) devices, wherein the first microservice API stores routing data associated with the respective plurality of first IoT devices; creating a second microservice API that connects with a second plurality of networks of a second type that host a respective plurality of second IoT devices, wherein the second microservice API stores routing data associated with the respective plurality of second IoT devices; receiving a request for device data from a IoT device, wherein the request includes a tag name, a network type, time data, and a requester identity; determining from the network type that the IoT device is located in one of the first plurality of networks; communicating the request to the first microservice API, wherein the first microservice API utilizes the routing data to determine which of the first plurality of networks the IoT device resides and establishes a tunnel with the IoT device; receiving the device data via the tunnel; and providing a content delivery network (CDN) that is configured to control a speed and volume of delivery of the device data. ### Claim 17 (depends on 16) The non-transitory computer readable medium of claim 16, wherein the first microservice API includes at least one of the following a data historian service component, an open data protocol (ODATA) service component, a DVR system, or a lab information system. ### Claim 18 (depends on 16) The non-transitory computer readable medium of claim 16, wherein the first microservice API utilizes the requester identity to determine whether the IoT device that requested the IoT device is authorized to access the device data. ### Claim 19 (depends on 16) The non-transitory computer readable medium of claim 16, wherein the logic further creates a third microservice API that connects with a third plurality of networks of a third type that host a respective plurality of third IoT devices, wherein the third microservice API stores routing data associated with the respective plurality of third IoT devices.