# US 12,182,017 B2 · Database management for modifying data related to industrial assets using an intelligent data queue for data ingestion > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,182,017 B2 - Document ID: US12182017B2 - Status: Granted - Kind: B2 - Application number: 18/194,315 - Filed: 2023-03-31 - Published: 2024-10-03 - Granted: 2024-12-31 - Earliest claimed: 2023-03-31 - Assignees: Honeywell International Inc. - Applicants: Honeywell International Inc. - Inventors: Bhabesh Chandra Acharya; Jyoti Ranjan Senapati - Web page: https://patentgrep.com/patent/US12182017B2 ## CPC - G06F 12/0802: Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches - G06F 16/254: {Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses} - G06F 2212/60: Details of cache memory - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Various embodiments relate to managing a database to modify data related to industrial assets using an intelligent data queue for data ingestion. Embodiments are configured to receive a data modification payload associated with a request to modify a portion of data stored in a time series database. Embodiments are also configured to parse the data modification payload to identify a type of modification with respect to the data stored in the time series database. Embodiments are also configured to store the data modification payload in at least one of a first data cache configured for storing pending data modification payloads and a second data cache configured for processing data modification payloads. In response to a determination that the data modification payload is stored in the second data cache, the data stored in the time series database is modified based at least in part on the type of modification. ## Claims ### Claim 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 a data modification payload associated with a request to modify one or more portions of asset data stored in a time series database, wherein the asset data digitally represents one or more assets within an industrial environment; parse the data modification payload to identify a type of modification with respect to the asset data stored in the time series database; store the data modification payload in at least one of a first data cache configured for storing pending data modification payloads and a second data cache configured for processing data modification payloads; and in response to a determination that the data modification payload is stored in the second data cache, modify, based at least in part on the type of modification, the asset data stored in the time series database to facilitate one or more asset data queries for the one or more assets via the time series database. ### Claim 2 (depends on 1) The system of claim 1, the one or more programs further comprising instructions configured to: parse the data modification payload to identify one or more data attributes associated with the data modification payload; and in response to the determination that the data modification payload is stored in the second data cache, modify the asset data stored in the time series database based at least in part on the type of modification and the one or more data attributes. ### Claim 3 (depends on 1) The system of claim 1, the one or more programs further comprising instructions configured to: parse the data modification payload to identify a data source identifier associated with the time series database; and in response to the determination that the data modification payload is stored in the second data cache, modify the asset data stored in the time series database based at least in part on the type of modification and the data source identifier. ### Claim 4 (depends on 1) The system of claim 1, the one or more programs further comprising instructions configured to: parse the data modification payload to identify a start time for an interval of time associated with the asset data stored in the time series database; parse the data modification payload to identify an end time for the interval of time associated with the asset data stored in the time series database; and in response to the determination that the data modification payload is stored in the second data cache, modify the asset data stored in the time series database based at least in part on the type of modification and the interval of time associated with the start time and the end time. ### Claim 5 (depends on 1) The system of claim 1, the one or more programs further comprising instructions configured to: store the data modification payload in the first data cache in response to a determination that the data modification payload conflicts with another data modification payload stored in the second data cache. ### Claim 6 (depends on 5) The system of claim 5, the one or more programs further comprising instructions configured to: move the data modification payload stored in the first data cache into the second data cache in response to a determination that the data modification payload does not conflict with another data modification payload stored in the second data cache. ### Claim 7 (depends on 1) The system of claim 1, the one or more programs further comprising instructions configured to: store the data modification payload in the first data cache in response to a determination that one or more data attributes of the data modification payload conflicts with at least one data attribute of another data modification payload stored in the second data cache. ### Claim 8 (depends on 1) The system of claim 1, the one or more programs further comprising instructions configured to: store the data modification payload in the first data cache in response to a determination that a data source associated with the data modification payload conflicts with another data modification payload stored in the second data cache. ### Claim 9 (depends on 1) The system of claim 1, the one or more programs further comprising instructions configured to: store the data modification payload in the first data cache in response to a determination that an interval of time for modifying data associated with the data modification payload conflicts with another data modification payload stored in the second data cache. ### Claim 10 A computer-implemented method comprising: receiving a data modification payload associated with a request to modify one or more portions of asset data stored in a time series database, wherein the asset data digitally represents one or more assets within an industrial environment; parsing the data modification payload to identify a type of modification with respect to the asset data stored in the time series database; storing the data modification payload in at least one of a first data cache configured for storing pending data modification payloads and a second data cache configured for processing data modification payloads; and in response to a determination that the data modification payload is stored in the second data cache, modifying, based at least in part on the type of modification, the asset data stored in the time series database to facilitate one or more asset data queries for the one or more assets via the time series database. ### Claim 11 (depends on 10) The computer-implemented method of claim 10, further comprising: parsing the data modification payload to identify one or more data attributes associated with the data modification payload; and in response to the determination that the data modification payload is stored in the second data cache, modifying the asset data stored in the time series database based at least in part on the type of modification and the one or more data attributes. ### Claim 12 (depends on 10) The computer-implemented method of claim 10, further comprising: parsing the data modification payload to identify a data source identifier associated with the time series database; and in response to the determination that the data modification payload is stored in the second data cache, modifying the asset data stored in the time series database based at least in part on the type of modification and the data source identifier. ### Claim 13 (depends on 10) The computer-implemented method of claim 10, further comprising: parsing the data modification payload to identify a start time for an interval of time associated with the asset data stored in the time series database; parsing the data modification payload to identify an end time for the interval of time associated with the asset data stored in the time series database; and in response to the determination that the data modification payload is stored in the second data cache, modifying the asset data stored in the time series database based at least in part on the type of modification and the interval of time associated with the start time and the end time. ### Claim 14 (depends on 10) The computer-implemented method of claim 10, further comprising: storing the data modification payload in the first data cache in response to a determination that the data modification payload conflicts with another data modification payload stored in the second data cache. ### Claim 15 (depends on 14) The computer-implemented method of claim 14, further comprising: moving the data modification payload stored in the first data cache into the second data cache in response to a determination that the data modification payload does not conflict with another data modification payload stored in the second data cache. ### Claim 16 (depends on 10) The computer-implemented method of claim 10, further comprising: storing the data modification payload in the first data cache in response to a determination that at least one of one or more data attributes or a data source of the data modification payload conflicts with at least one data attribute of another data modification payload stored in the second data cache. ### Claim 17 (depends on 10) The computer-implemented method of claim 10, further comprising: storing the data modification payload in the first data cache in response to a determination that an interval of time for modifying data associated with the data modification payload conflicts with another data modification payload stored in the second data cache. ### Claim 18 A computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising an executable portion configured to: receive a data modification payload associated with a request to modify one or more portions of asset data stored in a time series database, wherein the asset data digitally represents one or more assets within an industrial environment; parse the data modification payload to identify a type of modification with respect to the asset data stored in the time series database; store the data modification payload in at least one of a first data cache configured for storing pending data modification payloads and a second data cache configured for processing data modification payloads; and in response to a determination that the data modification payload is stored in the second data cache, modify, based at least in part on the type of modification, the asset data stored in the time series database to facilitate one or more asset data queries for the one or more assets via the time series database. ### Claim 19 (depends on 18) The computer program product of claim 18, the computer-readable program code portions further comprising an executable portion configured to: parse the data modification payload to identify a data source identifier associated with the time series database; and in response to the determination that the data modification payload is stored in the second data cache, modify the asset data stored in the time series database based at least in part on the type of modification and the data source identifier. ### Claim 20 (depends on 18) The computer program product of claim 18, the computer-readable program code portions further comprising an executable portion configured to: parse the data modification payload to identify a start time for an interval of time associated with the asset data stored in the time series database; parse the data modification payload to identify an end time for the interval of time associated with the asset data stored in the time series database; and in response to the determination that the data modification payload is stored in the second data cache, modify the asset data stored in the time series database based at least in part on the type of modification and the interval of time associated with the start time and the end time.