IP Library › Granted Patent US 12,216,663
Granted Patent B2
US 12,216,663 · App. 18/058,002 · Granted Feb 4, 2025

Adaptive ontology driven dimensions acquisition, automated schema creation, and enriched data in time series databases

Inventors: Bhabesh Chandra Acharya (Bangalore, IN); Prajosh Thaykandy (Bangalore, IN); Swaminath Balaji Akella (Bangalore, IN); Prithviraj Shivajirao Patil (Bangalore, IN); Gurender Singh (Bangalore, IN)
Assignee: Honeywell International Inc.
G06F16/24575G06F16/2246G06F16/287G06F16/211
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,216,663
App. No.
18/058,002
Granted
Feb 4, 2025
Kind
B2
Abstract

Various embodiments described herein relate to a contextualized time series database and/or contextualized time series data consumption. In this regard, a request to generate contextualized time series data related to one or more assets is received. The request includes a user identifier indicating an identity of a user associated with the request. In response to the request, telemetry data associated with the one or more assets is contextualized, based on metadata and a set of data dimensionality filters associated with the user identifier, to generate the contextualized time series data. Furthermore, the contextualized time series data is allocated within a datastore configured for the user identifier to facilitate obtaining one or more insights with respect to the contextualized time series data.

Claims (61)

1. A system, comprising:

one or more processors;

a memory; and

one or more programs stored in the memory, the one or more programs comprising instructions configured to:

receive, via a user-interactive electronic interface, an application programming interface (API) command request to generate contextualized time series data related to one or more assets, the API command request comprising a user identifier indicating an identity of a user associated with the API command request; and

in response to the API command request:

determine whether telemetry data associated with the one or more assets is enriched with metadata;

enrich the telemetry data with functional metadata, spatial metadata, asset metadata, and algorithm parameters based on the determination that the telemetry data is not enriched with the metadata, wherein the metadata includes functional metadata, spatial metadata, asset metadata, and algorithm parameters related to contextualization of the telemetry data;

contextualize, based on (i) the metadata related to the one or more assets and (ii) a set of data dimensionality filters configured based on respective dimensionality information associated with a format structure for a datastore configured for the user identifier, the enriched telemetry data associated with the one or more assets to generate the contextualized time series data;

allocate the contextualized time series data within the datastore configured for the user identifier;

obtain one or more insights with respect to the contextualized time series data allocated within the datastore associated with the user identifier; and

render a visual representation of the one or more insights via the user-interactive electronic interface.

2. The system of claim 1 , wherein the metadata is first metadata, and the one or more programs further comprising instructions configured to:

parse the telemetry data based on second metadata associated with dimensionality for the set of data dimensionality filters.

3. The system of claim 1 , the one or more programs further comprising instructions configured to:

parse the telemetry data based on event data associated with the one or more assets.

4. The system of claim 1 , the one or more programs further comprising instructions configured to:

parse the telemetry data based on alarm data associated with the one or more assets.

5. The system of claim 1 , the one or more programs further comprising instructions configured to:

format the contextualized time series data based on the user identifier.

6. The system of claim 1 , the one or more programs further comprising instructions configured to:

filter the contextualized time series data based on the set of data dimensionality filters.

7. The system of claim 1 , the one or more programs further comprising instructions configured to:

organize the contextualized time series data based on an ontological tree structure that captures relationships among different portions of the contextualized time series data.

8. The system of claim 1 , the one or more programs further comprising instructions configured to:

process the telemetry data related to the one or more assets to determine data related to the one or more assets; and

generate attributes for the one or more assets based on one or more classifications with respect to the data related to the one or more assets.

9. The system of claim 1 , the one or more programs further comprising instructions configured to perform a specific type of operation corresponding to the contextualized time series data based on header data.

10. A method, comprising:

at a device with one or more processors and a memory:

receiving, via a user-interactive electronic interface, an application programming interface (API) command request to generate contextualized time series data related to one or more assets, the API command request comprising a user identifier indicating an identity of a user associated with the API command request; and

in response to the API command request:

determining whether telemetry data associated with the one or more assets is enriched with metadata;

enriching the telemetry data with functional metadata, spatial metadata, asset metadata, and algorithm parameters based on the determination that the telemetry data is not enriched with the metadata, wherein the metadata includes functional metadata, spatial metadata, asset metadata, and algorithm parameters related to contextualization of the telemetry data;

contextualizing, based on (i) the metadata related to the one or more assets and (ii) a set of data dimensionality filters configured based on respective dimensionality information associated with a format structure for a datastore configured for the user identifier, the enriched telemetry data associated with the one or more assets to generate the contextualized time series data;

allocating the contextualized time series data within the datastore configured for the user identifier;

obtaining one or more insights with respect to the contextualized time series data allocated within the datastore associated with the user identifier; and

rendering a visual representation of the one or more insights via the user-interactive electronic interface.

11. The method of claim 10 , wherein the metadata is first metadata, and the contextualizing comprising parsing the telemetry data based on second metadata associated with dimensionality for the set of data dimensionality filters.

12. The method of claim 10 , the contextualizing comprising parsing the telemetry data based on event data associated with the one or more assets.

13. The method of claim 10 , the contextualizing comprising parsing the telemetry data based on alarm data associated with the one or more assets.

14. The method of claim 10 , the contextualizing comprising formatting the contextualized time series data based on the user identifier.

15. The method of claim 10 , the contextualizing comprising filtering the contextualized time series data based on the set of data dimensionality filters.

16. The method of claim 10 , the allocating the contextualized time series data comprising organizing the contextualized time series data based on an ontological tree structure that captures relationships among different portions of the contextualized time series data.

17. The method of claim 10 , further comprising:

processing the telemetry data related to the one or more assets to determine data related to the one or more assets; and

generating attributes for the one or more assets based on one or more classifications with respect to the data related to the one or more assets.

18. A computer program product comprising at least one computer-readable storage medium having program instructions embodied thereon, the program instructions executable by a processor to cause the processor to:

receive, via a user-interactive electronic interface, an application programming interface (API) command request to generate contextualized time series data related to one or more assets, the API command request comprising a user identifier indicating an identity of a user associated with the API command request; and

in response to the API command request:

determine whether telemetry data associated with the one or more assets is enriched with metadata;

enrich the telemetry data with functional metadata, spatial metadata, asset metadata, and algorithm parameters based on the determination that the telemetry data is not enriched with the metadata, wherein the metadata includes functional metadata, spatial metadata, asset metadata, and algorithm parameters related to contextualization of the telemetry data;

contextualize, based on (i) the metadata related to the one or more assets and (ii) a set of data dimensionality filters configured based on respective dimensionality information associated with a format structure for a datastore configured for the user identifier, the enriched telemetry data associated with the one or more assets to generate the contextualized time series data;

allocate the contextualized time series data within the datastore configured for the user identifier;

obtain one or more insights with respect to the contextualized time series data allocated within the datastore associated with the user identifier; and render a visual representation of the one or more insights via the user-interactive electronic interface.

19. The computer program product of claim 18 , wherein the metadata is first metadata, and the program instructions further executable by the processor to cause the processor to:

parse the telemetry data based on second metadata associated with dimensionality for the set of data dimensionality filters.

20. The computer program product of claim 18 , the program instructions further executable by the processor to cause the processor to:

parse the telemetry data based on event data associated with the one or more assets.

21. The computer program product of claim 18 , the program instructions further executable by the processor to cause the processor to:

parse the telemetry data based on alarm data associated with the one or more assets.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 22, 2022
From: ACHARYA, BHABESH CHANDRA; THAYKANDY, PRAJOSH; AKELLA, SWAMINATH BALAJI; PATIL, PRITHVIRAJ SHIVAJIRAO; SINGH, GURENDER
To: HONEYWELL INTERNATIONAL INC.
Reel/Frame 061855/0641 →
Priority Claims (1)
IN 202111054475 · Nov 25, 2021 · national
Continuity (1)
Related Publication 20230161777A1 · May 25, 2023
References Cited (32)
US 10540358B2 · Wu et al. · 2020 [cited by applicant]
US 11144042B2 · Thomsen et al. · 2021 [cited by applicant]
US 11182748B1 · Neckermann et al. · 2021 [cited by applicant]
US 20100100456A1 · West · 2010 [cited by examiner]
US 20110071365A1 · Lee et al. · 2011 [cited by applicant]
US 20160370338A1 · Sayfan · 2016 [cited by applicant]
US 20170262446A1 · McLaughlin · 2017 [cited by applicant]
US 20170364561A1 · Wu · 2017 [cited by examiner]
US 20180253344A1 · Deligia et al. · 2018 [cited by applicant]
US 20190064787A1 · Maturana · 2019 [cited by applicant]
US 20190340290A1 · Dang et al. · 2019 [cited by applicant]
US 20200210647A1 · Panuganty et al. · 2020 [cited by applicant]
US 20200295879A1 · Jas · 2020 [cited by applicant]
US 20210019063A1 · Lee · 2021 [cited by examiner]
US 20210211471A1 · Crabtree et al. · 2021 [cited by applicant]
US 20210337014A1 · Cameron · 2021 [cited by applicant]
US 20220327538A1 · Kumar et al. · 2022 [cited by applicant]
US 20220374402A1 · Hawkins et al. · 2022 [cited by applicant]
US 20230401191A1 · Conradi et al. · 2023 [cited by applicant]
Supplementary European search report Mailed on Mar. 27, 2023 for EP Application No. 22209334, 7 page(s). [cited by applicant]
EP Office Action Mailed on Dec. 12, 2023 for EP Application No. 22209334, 5 page(s). [cited by applicant]
Department of Energy, Internet of Things-enabled Devices and the Grid, Jun. 1, 2017 (accessed Feb. 24, 2024 at https://www.energy.gov/articles/internet-things-enabled-devices-and-grid) (Year: 2017). [cited by applicant]
Electric Power Group, [cited by applicant]
Examiner Interview Summary Record (PTOL-413) Mailed on Feb. 14, 2024 for U.S. Appl. No. 17/748,417, 2 page(s). [cited by applicant]
Final Rejection Mailed on Jun. 18, 2024 for U.S. Appl. No. 17/748,417, 23 page(s). [cited by applicant]
Final Rejection Mailed on Nov. 9, 2023 for U.S. Appl. No. 17/748,417, 20 page(s). [cited by applicant]
[cited by applicant]
Non-Final Rejection Mailed on Feb. 29, 2024 for U.S. Appl. No. 17/748,417, 21 page(s). [cited by applicant]
Non-Final Rejection Mailed on Jun. 8, 2023 for U.S. Appl. No. 17/748,417, 23 page(s). [cited by applicant]
Office Action Appendix Mailed on Feb. 14, 2024 for U.S. Appl. No. 17/748,417, 1 page(s). [cited by applicant]
Non-Final Rejection Mailed on Nov. 13, 2024 for U.S. Appl. No. 17/748,417, 29 page(s). [cited by applicant]
Non-Final Rejection Mailed on Dec. 12, 2024 for U.S. Appl. No. 18/320,548, 43 page(s). [cited by applicant]