Incremental Conflated Record Updates Without Full Refresh

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face inefficiencies in updating conflated data records due to the time and resource-intensive nature of full refreshes, particularly when only a small number of updates are received from data sources, leading to inaccuracies and the need for recursive regrouping.

Innovation Solution

Implementing incremental updates to conflated data records by generating a new conflated data record that replaces the affected 'dirty' record, using a processor to identify and re-process associated data records based on conflation algorithms and snapshot updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full refresh is performed to update conflated data records, then accuracy and consistency are maintained, but time consumption and resource usage increase significantly

Engineering Contradiction:

Improveaccuracy and consistency of conflated data recordsVSAvoidtime consumption for updates

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the update process by identifying and isolating only the affected conflated data records that need updating, rather than performing a complete refresh of all records. This is achieved by tracking which records are impacted by source data changes and selectively re-processing only those specific segments, thereby reducing time consumption while maintaining accuracy.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by performing incremental updates on only the necessary portion of conflated data records rather than a full refresh. The system determines the minimal set of records that require updates based on change detection mechanisms, executing updates only where needed to preserve accuracy while minimizing time and resource expenditure.

Inventive Principle:

Principle #16Partial or excessive action

2Reliability

If full refresh is performed to update conflated data records, then accuracy and consistency are maintained, but processing resource consumption increases significantly

Engineering Contradiction:

Improveaccuracy and consistency of conflated data recordsVSAvoidprocessing resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the processing workload by identifying only the specific conflated data records that require updates, separating them from the rest of the dataset. This segmentation allows the system to allocate processing resources efficiently, focusing computational energy only on the affected records rather than wasting resources on unchanged data, thus maintaining accuracy while reducing overall resource consumption.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements partial processing by executing updates only on the subset of conflated data records that are actually affected by source changes. This partial action approach prevents excessive resource consumption by avoiding redundant processing of unchanged records, while still ensuring that all necessary updates are applied to maintain data accuracy and consistency.

Inventive Principle:

Principle #16Partial or excessive action

3Productivity

If incremental updates are implemented to reduce processing time, then efficiency improves, but system complexity increases due to recursive regrouping requirements

Engineering Contradiction:

Improveupdate efficiencyVSAvoidsystem complexity for recursive regrouping

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-establishing tracking mechanisms that identify affected conflated data records before the update process begins. This preliminary identification of impacted records simplifies the incremental update process by providing a clear roadmap of what needs to be updated, reducing the complexity of recursive regrouping operations while maintaining high update efficiency.

Inventive Principle:

Principle #10Preliminary action

4Productivity

If incremental updates are implemented to reduce resource consumption, then efficiency improves, but update accuracy may be compromised without proper re-processing

Engineering Contradiction:

Improveresource efficiencyVSAvoidupdate accuracy

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent implements partial re-processing of affected conflated data records to ensure update accuracy while maintaining resource efficiency. By selectively re-processing only the identified affected records rather than all records, the system achieves the necessary level of accuracy verification without the excessive resource consumption of a full refresh, thus balancing productivity and reliability.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS12554703B2Incremental updates of conflated data records

Publication Date: 2026.02.17 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

According to examples, an apparatus may include a processor and a memory on which are stored machine-readable instructions that when executed by the processor, may cause the processor to receive an updated data record from a data source and may determine a first conflated data record. The first conflated data record may be associated with the updated data record and include data records in a first grouping from among a plurality of data sources. The processor may identify the data records included in the first conflated data record and may generate a second conflated data record that updates conflations among the updated data record and the identified data records. The second conflated data record may include a second grouping of data records. The processor may replace the first conflated data record with the second conflated data record to incrementally update a set of conflated data records.