Queryable cache in real-time data management system

• US 7,464,077 B1
• Filed: 07/29/2004
• Issued: 12/09/2008
• Est. Priority Date: 07/29/2004
• Status: Expired due to Fees

• Current Assignee: Starview, Inc., Starview Technology, Inc. (Starview, Inc.)
• Original Assignee: Starview Technology, Inc. (Starview, Inc.)
• Inventors: Baunach, Stephen, Tham, Haam
• Primary Examiner(s): Ly; Cheyne D
• Application Number:
  US10/903,862
• Time in Patent Office: 1,594 Days
• Field of Search: 707 2- 5, 707/100, 707/205, 711/138
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24568 Data stream processing; Continuous queries
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

In order to provide real-time data analysis of high speed data, a query control mechanism may be provided and coupled to one or more caches. The caches may temporarily store the incoming high-speed data, and the data from the caches may be periodically swept into a relational database. Upon receipt of a query for real-time data, the query control may determine if one of the caches can fulfill the query. If so, the query is transferred to that cache. If not, the query may be transferred to the relational database. If so, the query is transferred to that cache. If not, the query may be transferred to the relational database. The query control can accomplish this by tracking the time frame of information stored in each cache, such that it is aware of whether or not a particular cache can fulfill a query without first contacting the cache.

Claims

1. A data management system comprising:

a processor;

a relational database;

one or more caches coupled to one or more data sources, wherein each of the caches contain information sampled and received only during a particular time frame;

a query control coupled to said one or more caches and to said relational database, said query control designed to determine if an incoming query can be fulfilled by one of said one or more caches, and to pass said query to said relational database if it cannot, wherein the determining includes comparing a time frame of data requested by the incoming query to the particular time frame contained in the cache, wherein said query control is further designed to pass said query to one of said one or more caches if the incoming query can be fulfilled by said one of said one or more caches; and

a feedback system coupled to said query control and to said one or more data sources, said feedback system designed to send one or more queries to said query control and to adjust operation of said one or more data sources based on information resulting from said one or more queries.

2. The data management system of claim 1, wherein each of said one or more caches corresponds to a single data source.

3. The data management system of claim 1, wherein each of said data sources is a manufacturing machine having sensors.

4. The data management system of claim 1, further comprising:

a persisted backup storage coupled to each of said caches.

5. The data management system of claim 1, wherein said caches are configured to be loaded with all data from a machine as the data is received.

6. The data management system of claim 1, further comprising:

a storage coordinator coupled to said one or more caches and to said relational database, said storage coordinator designed to funnel information from said one or more caches for storage in said relational database.

7. The data management system of claim 6, wherein said storage coordinator is further designed to precondition said information from said one or more caches in a string table, floating point table, or integer table, as well as a mapping layer indicating which portions of said string table, floating point table, or integer table contain said information.

8. The data management system of claim 1, further comprising:

one or more event caches coupled to said one or more caches.

9. The data management system of claim 1, wherein said query control is designed to use event identifications in said event caches to lookup time markers which can be used to lookup data in said one or more caches or said relational database.

10. A method for managing data from one or more high-speed sources, the method comprising:

storing the data in one or more caches;

periodically coordinating storage of data from said one or more caches into a relational database;

receiving a query for real-time data;

determining if said query for real-time data can be fulfilled by information in one of said one or more caches, wherein the one of said one or more caches contains only data sampled and received during a particular time frame, wherein the determining includes comparing a time frame of data requested in the incoming query to the particular time frame;

transferring said query to said one of said one or more caches if said query can be fulfilled by information in said one of said one or more caches; and

transferring said query to said relational database if said query cannot be fulfilled by information in one of said one or more caches.

11. The method of claim 10, wherein each of said one or more caches corresponds to a single data source.

12. The method of claim 10, wherein each of said data sources is a manufacturing machine having sensors.

13. The method of claim 10, further comprising backing up said data from said one or more caches into one or more persisted backup storages coupled to each of said caches.

14. The method of claim 10, wherein said determining includes:

examining information as to a time frame of information being stored in each of said one or more caches; and

determining if a time indicated by said query is inside said time frame of information for a cache corresponding to a data source indicated by said query.

15. The method of claim 10, wherein said periodically coordinating includes:

parsing the data into a string table, a floating point table, or an integer table; and

creating a mapping layer indicating which portions of said string table, floating point table, or integer table contain the data.

16. The method of claim 15, wherein said string table, floating point table, or integer table contains two axes and a body, one of said axes corresponding to time and a second of said axes corresponding to name, wherein said body contains values of said data for corresponding name/time combinations.

17. The method of claim 10, wherein said determining includes using event identifications stored in an event cache associated with each cache to look up time markers.

18. An apparatus for managing data from one or more high-speed sources, the apparatus comprising:

means for storing the data in one or more caches;

means for periodically coordinating storage of data from said one or more caches into a relational database;

means for receiving a query for real-time data;

means for determining if said query for real-time data can be fulfilled by information in one of said one or more caches, wherein the one of said one or more caches contains only data sampled and received during a particular time frame, wherein the determining includes comparing a time frame of data requested in the incoming query to the particular time frame;

means for transferring said query to said one of said one or more caches if said query can be fulfilled by information in said one of said one or more caches; and

means for transferring said query to said relational database if said query cannot be fulfilled by information in one of said one or more caches.

19. The apparatus of claim 18, wherein each of said one or more caches corresponds to a single data source.

20. The apparatus of claim 18, wherein each of said data sources is a manufacturing machine having sensors.

21. The apparatus of claim 18, further comprising means for backing up said data from said one or more caches into one or more persisted backup storages coupled to each of said caches.

22. The apparatus of claim 18, wherein said means for determining includes:

means for examining information as to a time frame of information being stored in each of said one or more caches; and

means for determining if a time indicated by said query is inside said time frame of information for a cache corresponding to a data source indicated by said query.

23. The apparatus of claim 18, wherein said means for coordinating includes:

means for parsing the data into a string table, a floating point table, or an integer table; and

means for creating a mapping layer indicating which portions of said string table, floating point table, or integer table contain the data.

24. The apparatus of claim 23, wherein said string table, floating point table, or integer table contains two axes and a body, one of said axes corresponding to time and a second of said axes corresponding to name, wherein said body contains values of said data for corresponding name/time combinations.

25. The apparatus of claim 18, wherein said means for determining includes using event identifications stored in an event cache associated with each cache to look up time markers.

26. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a method for managing data from one or more high-speed sources, the method comprising:

storing the data in one or more caches;

periodically coordinating storage of data from said one or more caches into a relational database;

receiving a query for real-time data;

determining if said query for real-time data can be fulfilled by information in one of said one or more caches, wherein the one of said one or more caches contains only data sampled and received during a particular time frame, wherein the determining includes comparing a time frame of data requested in the incoming query to the particular time frame;

transferring said query to said one of said one or more caches if said query can be fulfilled by information in said one of said one or more caches; and

transferring said query to said relational database if said query cannot be fulfilled by information in one of said one or more caches.