System and method for historical data retrieval from OPC UA historian without continuation points
Inventors
Shanmugham, Sivasankari • Krishna, Mudunuru Sai • Rathi, Lakhankumar Tarachand
Assignees
Interested in licensing this patent?
MTEC can help explore whether this patent might be available for licensing for your application.
Abstract
Various embodiments described herein relate to a method and system for data communication with OPC UA historian data source that lacks support for continuation points. The system comprises one or more processors and a memory enabling the processor to transmit a first request from an OPC UA client to at least two historian data sources to receive historical data at a first time frame and accordingly receive a first response from a first data source that lacks support for continuation point at a second time frame. Then the processor determines that the second end-time is different from the first end-time and accordingly transmits a second request from the OPC UA client to the first data source with a third time frame. The processor repeats transmission of additional requests to the first data source by incrementing end-time of new time frames to retrieve remaining historical data within the first time frame.
Core Innovation
The invention relates to an OPC UA client retrieving historical data from at least two historian data sources in a network when historical-data retrieval from one historian data source lacks support for continuation point. A first request is transmitted from an OPC UA client to the at least two historian data sources to receive historical data at a first time frame that comprises a first start-time and a first end-time.
At least a first response is received from a plurality of nodes associated with a first data source of the at least two historian data sources at a second time frame that comprises the first start-time and a second end-time. The system determines that the second end-time is different from the first end-time when the first response received during the second time frame differs from the originally requested end-time.
A second request is then transmitted from the OPC UA client to the first data source with a third time frame to receive a second response from the first data source, where the first data source lacks support for continuation point during transmission of the historical data. The third time frame comprises a third start-time and the first end-time, and the third start-time is an incremental value of the second end-time.
Further requests are transmitted and repeated to the first data source until a final end-time matches the first end-time to retrieve the remaining portion of the historical data for the first time frame. After the final end-time matches the first end-time, the system renders, via a user interface of the OPC UA client, one or more notifications associated with retrieval of the historical data from the first data source within the first time frame.
Claims Coverage
The independent claims cover an OPC UA client system and method (and a computer program product) that perform initial historical-data retrieval from at least two historian data sources for a specified time frame, detect when a first historian returns an end-time different from the requested end-time, and then iteratively transmit incremental follow-up requests to a first historian that lacks support for continuation point until the final end-time matches. The inventive features are repeated across independent claim types.
Initial multi-historian request with time frame
transmit a first request from an Open Platform Communication Unified Architecture (OPC UA) client to at least two historian data sources in a network to receive historical data at a first time frame, wherein the first time frame comprises a first start-time and a first end-time
Detect returned end-time mismatch
receive at least a first response from a plurality of nodes associated with a first data source of the at least two historian data sources at a second time frame, wherein the second time frame comprises the first start-time and a second end-time; determine that the second end-time is different from the first end-time
Incremental follow-up for historian lacking continuation point support
transmit a second request from the OPC UA client to the first data source with a third time frame to receive a second response from the first data source, wherein the first data source lacks support for continuation point during transmission of the historical data, wherein the third time frame comprises a third start-time and the first end-time, the third start-time is an incremental value of second end-time
Repeat until final end-time matches requested end-time
repeat transmission of further requests to the first data source until final end-time matches the first end-time to retrieve remaining portion of the historical data for the first time frame
Render notifications after retrieval completes
render, via a user interface of the OPC UA client, one or more notifications associated with retrieval of the historical data from the first data source within the first time frame, when the final end-time matches the first end-time
Across the independent claims, the core inventive coverage is the OPC UA client approach: send an initial request to at least two historian data sources for a time frame, detect when a first historian’s returned end-time differs from the requested end-time, then iteratively issue incremental time-frame follow-up requests to a historian that lacks support for continuation point until the final end-time matches; then render user-interface notifications when retrieval for the time frame completes.
Stated Advantages
Documented Applications
No documented applications found
Interested in licensing this patent?