# US 12,113,777 B2 · Secure remote access to historical data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,113,777 B2 - Document ID: US12113777B2 - Status: Granted - Kind: B2 - Application number: 18/391,016 - Filed: 2023-12-20 - Published: 2024-04-11 - Granted: 2024-10-08 - Earliest claimed: 2020-04-27 - Assignees: Real Innovations International LLC - Applicants: Real Innovations International LLC - Inventors: Andrew S. Thomas - Web page: https://patentgrep.com/patent/US12113777B2 ## CPC - H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes} - H04L 63/0218: {Distributed architectures, e.g. distributed firewalls} - H04L 63/108: {when the policy decisions are valid for a limited amount of time} - H04L 41/147: for predicting network behaviour - H04L 41/149: for prediction of maintenance - H04L 43/0876: Network utilisation, e.g. volume of load or congestion level - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Methods, systems, and computer products facilitate access to historical data via a real-time tunnel within an architectural framework that encompasses an operational technology (OT) network, a de-militarized zone (DMZ), and an information technology (IT) network. Real-time data is retrieved from a data source using a first connector, which comprises a first tunneller, a first history-writer, and a first history-tunneller. The mechanisms involve interleaving real-time data and historical data over a first tunnel connection, a first firewall, and a second firewall by (a) executing pull replication of the historical data, (b) daisy-chaining the historical data, or (c) a combination of both (a) and (b). Subsequently, the real-time data is written to the first tunneller. ## Claims ### Claim 1 A method for providing access to historical data over a real-time tunnel in an architecture including an operational technology (OT) network, a de-militarized zone (DMZ) and an information technology (IT) network, comprising: obtaining from a data source, by a first connector, real-time data, wherein the first connector includes a first tunneller, a first history-writer and a first history-tunneller; interleaving the real-time data and historical data over a first tunnel connection, a first firewall and a second firewall by (a) performing pull replication of the historical data, (b) daisy chaining the historical data, or (c) a combination of (a) and (b); and writing the real time data to the first tunneller to store and forward the real time data by the first tunneller. ### Claim 2 (depends on 1) The method of claim 1, further comprising: closing the first firewall and the second firewall to all inbound connection requests, thereby isolating the IT network and the OT network from DMZ. ### Claim 3 (depends on 1) The method according to claim 1, further comprising: writing the real time data to the first history-writer. ### Claim 4 (depends on 1) The method according to claim 1, further comprising: writing the real-time data, by the first history writer, to a first historian. ### Claim 5 (depends on 4) The method according to claim 4, wherein the first historian is external from the first connector. ### Claim 6 (depends on 4) The method according to claim 4, wherein the first historian is an application external from the first connector. ### Claim 7 (depends on 4) The method according to claim 4, further comprising: obtaining from the data source, by the first historian. ### Claim 8 (depends on 4) The method according to claim 4, further comprising: obtaining, from the data source by the first historian, the real-time data via the first history-writer. ### Claim 9 (depends on 4) The method according to claim 4, further comprising: retrieving, from the first historian, historical data; and propagating, by the first history-tunneller, the historical data retrieved from the first historian to the first tunneller. ### Claim 10 (depends on 1) The method according to claim 1, further comprising: establishing the first tunnel connection from the first tunneller to a first DMZ tunneller by an outbound connection request from the OT network including the first tunneller to the DMZ including the first DMZ tunneller. ### Claim 11 (depends on 10) The method according to claim 10, further comprising: re-establishing, by the first tunneller, a lost connection to the first DMZ tunneller; re-initiating, by the first history-tunneller, transmission of missed historical data; retrieving, by the first history-tunneller the historical data from the first historian; transmitting, by the first history-tunneller, missed historical data via the first tunneller over the first tunnel connection to the first DMZ tunneller; and propagating the historical data from the first DMZ tunneller to a second historian via a second history-writer, where the first DMZ tunneller, the second historian and the second history-writer are in the DMZ. ### Claim 12 (depends on 11) The method according to claim 11, wherein an initial connection of the first tunnel connection and a first initiation of transmission of a historical data flow via the first tunnel connection is equivalent to a network reconnection. ### Claim 13 (depends on 11) The method according to claim 11, further comprising: sending, by the second historian, a confirmation response to the second history-writer confirming receipt of missed historical data. ### Claim 14 (depends on 13) The method according to claim 13, further comprising: delivering, via the first DMZ tunneller and the first tunneller, the confirmation response to first history-tunneller. ### Claim 15 (depends on 11) The method according to claim 11, further comprising: establishing a second tunnel connection from a third tunneller in the IT network to a second DMZ tunneller in the DMZ by an outbound connection request from the IT network to the DMZ. ### Claim 16 (depends on 15) The method according to claim 15, further comprising: re-establishing, by the third tunneller, a lost connection to the second DMZ tunneller; sending, by the third tunneller a request to the second history-tunneller to re-initiate transmission of historical data; retrieving, by a second history-tunneller the historical data from the second historian; and transmitting, via the second DMZ tunneller over the second tunnel connection to the third tunneller, the historical data. ### Claim 17 (depends on 15) The method according to claim 15, wherein the historical data flow is sent from the second DMZ tunneller to a third historian via a third history-writer. ### Claim 18 (depends on 17) The method according to claim 17, wherein the first historian, the second historian and the third historian are built into one or more of the first connector, second connector, and third connector, respectively. ### Claim 19 A system for providing access to historical data over a real-time tunnel, comprising: an operational technology (OT) network an operational technology (OT) network including one or more processors configured to: obtain from a data source, by a first connector, real-time data, wherein the first connector includes a first tunneller, a first history-writer and a first history-tunneller; interleave the real-time data and historical data over a first tunnel connection, a first firewall and a second firewall in conjunction with a de-militarized zone (DMZ) and an information technology (IT) network by (a) performing pull replication of the historical data, (b) daisy chaining the historical data, or (c) a combination of (a) and (b); and write the real time data to the first tunneller to store and forward the real time data by the first tunneller. ### Claim 20 (depends on 19) The system of claim 19, wherein at least one of the one or more processors is configured to: close the first firewall and the second firewall to all inbound connection requests, thereby isolating the IT network and the OT network from DMZ. ### Claim 21 (depends on 19) The system of claim 19, wherein at least one of the one or more processors is configured to: write the real time data to the first history-writer. ### Claim 22 (depends on 19) The system of claim 19, wherein at least one of the one or more processors is configured to: write the real-time data, by the first history writer, to a first historian. ### Claim 23 (depends on 22) The system of claim 22, wherein the first historian is external from the first connector. ### Claim 24 (depends on 22) The system of claim 22, wherein the first historian is an application external from the first connector. ### Claim 25 (depends on 22) The system of claim 22, wherein at least one of the one or more processors is configured to: obtain from the data source, by the first historian. ### Claim 26 (depends on 22) The system of claim 22, wherein at least one of the one or more processors is configured to: obtain, from the data source by the first historian, the real-time data via the first history-writer. ### Claim 27 (depends on 22) The system of claim 22, wherein at least one of the one or more processors is configured to: retrieve, from the first historian, historical data; and propagate, by the first history-tunneller, the historical data retrieved from the first historian to the first tunneller. ### Claim 28 (depends on 19) The system of claim 19, wherein at least one of the one or more processors is configured to: establish the first tunnel connection from the first tunneller to a first DMZ tunneller by an outbound connection request from the OT network including the first tunneller to the DMZ including the first DMZ tunneller. ### Claim 29 (depends on 28) The system of claim 28, wherein at least one of the one or more processors is configured to: re-establish, by the first tunneller, a lost connection to the first DMZ tunneller; re-initiate, by the first history-tunneller, transmission of missed historical data; retrieve, by the first history-tunneller the historical data from the first historian; transmit, by the first history-tunneller, missed historical data via the first tunneller over the first tunnel connection to the first DMZ tunneller; and propagate the historical data from the first DMZ tunneller to a second historian via a second history-writer, where the first DMZ tunneller, the second historian and the second history-writer are in the DMZ. ### Claim 30 (depends on 29) The system of claim 29, wherein an initial connection of the first tunnel connection and a first initiation of transmission of a historical data flow via the first tunnel connection is equivalent to a network reconnection. ### Claim 31 (depends on 29) The system of claim 29, wherein at least one of the one or more processors is configured to: send, by the second historian, a confirmation response to the second history-writer confirming receipt of missed historical data. ### Claim 32 (depends on 31) The system of claim 31, wherein at least one of the one or more processors is configured to: deliver, via the first DMZ tunneller and the first tunneller, the confirmation response to first history-tunneller. ### Claim 33 (depends on 29) The system of claim 29, wherein at least one of the one or more processors is configured to: establish a second tunnel connection from a third tunneller in the IT network to a second DMZ tunneller in the DMZ by an outbound connection request from the IT network to the DMZ. ### Claim 34 (depends on 33) The system of claim 33, wherein at least one of the one or more processors is configured to: re-establish, by the third tunneller, a lost connection to the second DMZ tunneller; send, by the third tunneller a request to the second history-tunneller to re-initiate transmission of historical data; retrieve, by a second history-tunneller the historical data from the second historian; and transmit, via the second DMZ tunneller over the second tunnel connection to the third tunneller, the historical data. ### Claim 35 (depends on 33) The system of claim 33, wherein the historical data flow is sent from the second DMZ tunneller to a third historian via a third history-writer. ### Claim 36 (depends on 35) The system of claim 35, wherein the first historian, the second historian and the third historian are built into one or more of the first connector, second connector, and third connector, respectively. ### Claim 37 A non-transitory computer-readable medium having stored thereon one or more sequences of instructions, which when executed by one or more hardware processors, cause the one or more hardware processors to provide access to historical data over a real-time tunnel in an architecture including an operational technology (OT) network, a de-militarized zone (DMZ) and an information technology (IT) network by: obtaining from a data source, by a first connector, real-time data, wherein the first connector includes a first tunneller, a first history-writer and a first history-tunneller; interleaving the real-time data and historical data over a first tunnel connection, a first firewall and a second firewall by (a) performing pull replication of the historical data, (b) daisy chaining the historical data, or (c) a combination of (a) and (b); and writing the real time data to the first tunneller to store and forward the real time data by the first tunneller.