Data query interface system in an event historian

Patent metadata

Field	Value
Publication number	US-9842134-B2
Application number	US-201414569214-A
Country	US
Kind code	B2
Filing date	Dec 12, 2014
Priority date	Dec 12, 2014
Publication date	Dec 12, 2017
Grant date	Dec 12, 2017

Abstract

An event historian system receives and responds to queries for event data from a client device over a network connection. The queries comprise parameters indicating a date range and filter limitations defining the desired event data. The system selects storage blocks based on the date range and filters event data in the storage blocks based on the filter limitations. The filtered event data is grouped into a results message and sent to the client system via the network connection.

First claim

What is claimed is:

1. An event historian system comprising:
a processor;
a network connection coupling a client system to the event historian system;
a memory storage device coupled to the processor, said memory storage device storing event storage blocks and processor-executable instructions for receiving and responding to queries, said processor-executable instructions comprising instructions for:
receiving a query via the network connection from the client system, said query comprising a set of parameters;
extracting a result time range from the set of parameters;
extracting one or more filter limitations from the set of parameters;
selecting one or more event storage blocks, said storage blocks containing event data for events which occurred within the result time range;
filtering event data in the selected one or more event storage blocks according to the extracted filter limitations;
grouping the filtered event data into a result message; and
sending the result message via the network connection to the client system.

2. The system of claim 1 , wherein the set of parameters comprises one or more of the following: a start time, an end time, a number of events per batch of results, an order in which to provide the results, and one or more filter limitations.

3. The system of claim 1 , wherein the query is received and the result message is sent using the Open Data Protocol (OData).

4. The system of claim 1 , wherein the query is received and the result message is sent using the Representation State Transfer (REST) Protocol.

5. The system of claim 1 , wherein filtering event data according to filter limitations comprises selecting equivalent event data stored with a data type different than the filter limitations.

6. The system of claim 1 , wherein at least one of the extracted filter limitations comprises a nested logical expression.

7. The system of claim 1 , wherein sending the result message comprises splitting the filtered event data into a plurality of data sets and sending a plurality of result sub-messages, each result sub-message comprising one data set of the plurality of data sets and a skip token, said skip token providing a link to access a next result sub-message.

8. The system of claim 1 , wherein the filtered event data comprises extended properties.

9. The system of claim 1 , wherein filtering event data comprises accessing index files in the event storage blocks to locate event data which meets the filter limitations.

10. The system of claim 9 , wherein filtering event data further comprises loading only the event data located by accessing the index files into memory.

11. A method of handling queries to an event historian system comprising:
receiving, by the event historian system, a query via a network connection from a client system, said query comprising a set of parameters;
extracting, by the event historian system, a result time range from the set of parameters;
extracting, by the event historian system, one or more filter limitations from the set of parameters;
selecting, by the event historian system, one or more event storage blocks, said storage blocks containing event data for events which occurred within the result time range;
filtering, by the event historian system, event data in the selected one or more event storage blocks according to the extracted filter limitations;
grouping, by the event historian system, the filtered event data into a result message; and
sending, by the event historian system, the result message via the network connection to the client system.

12. The method of claim 11 , wherein the set of parameters comprises one or more of the following: a start time, an end time, a number of events per batch of results, an order in which to provide the results, and one or more filter limitations.

13. The method of claim 11 , wherein the query is received and the result message is sent using the Open Data Protocol (OData).

14. The method of claim 11 , wherein the query is received and the result message is sent using the Representation State Transfer (REST) Protocol.

15. The method of claim 11 , wherein filtering event data comprises selecting equivalent event data stored with a data type different than the filter limitations.

16. The method of claim 11 , wherein at least one of the extracted filter limitations comprises a nested logical expression.

17. The method of claim 11 , wherein sending the result message comprises splitting the filtered event data into a plurality of data sets and sending a plurality of result sub-messages, each result sub-message comprising one data set of the plurality of data sets and a skip token, said skip token providing a link to access a next result sub-message.

18. The method of claim 11 , wherein the filtered event data comprises extended properties.

19. The method of claim 11 , wherein filtering event data comprises accessing index files in the event storage blocks to locate event data which meets the filter limitations.

20. The method of claim 19 , wherein filtering event data further comprises loading only the event data located by accessing the index files into memory.

Assignees

• Invensys Sys Inc
• Schneider Electric Software Llc

Inventors

• Erickson Brian Kenneth
• Sista Bala Kamesh
• Manushree Abhijit
• Kamath Vinay T

Classifications

• G06F11/3072

  where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting · CPC title

• G06F11/30

  Monitoring · CPC title

• G06F11/3006

  where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title

• G06F16/245 Primary

  Query processing · CPC title

• G06F2201/86

  Event-based monitoring · CPC title