Cached Report Data Freshness Check

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional report generation systems face inefficiencies due to unnecessary processing in on-demand reporting and data staleness in scheduled reporting, leading to wastage of computing resources and outdated reports.

Innovation Solution

A method and system that determine whether cached report data is up-to-date, using it for report creation if not stale, and regenerating data only when necessary from data sources, thereby optimizing processing and resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is gathered from data sources at frequent intervals to maintain data freshness, then data staleness is reduced, but processing overhead increases substantially

Engineering Contradiction:
Improvedata freshnessVSAvoidprocessing overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary actions by gathering data from data sources at scheduled intervals and storing it in a data repository before it is needed for report generation. This advance preparation allows the report generation system to use pre-gathered data without performing real-time data collection, thereby reducing processing overhead while maintaining data freshness within acceptable timeframes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically determines whether to use cached data or regenerate data based on the recency of the data and the current reporting needs. The report generation system checks whether data in the repository is current enough to satisfy the reporting requirement, and only regenerates data when necessary, creating a dynamic balance between data freshness and processing efficiency.

Inventive Principle:
Principle #15Dynamics

2Loss of energy

If data is gathered from data sources at scheduled intervals and stored in a repository, then processing overhead is reduced, but data becomes stale

Engineering Contradiction:
Improveprocessing overheadVSAvoiddata freshness
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The system implements feedback mechanisms where the report generation system checks the age and currency of data in the repository before using it for report generation. This feedback loop allows the system to identify when cached data has become stale and trigger data regeneration only when necessary, ensuring data freshness is maintained while minimizing unnecessary processing.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system dynamically adjusts its data usage strategy based on the current state of the data in the repository. When data is fresh, the system uses cached data to minimize processing. When data becomes stale (as detected through feedback mechanisms), the system dynamically switches to regenerating data from sources, creating an adaptive system that balances processing overhead and data freshness.

Inventive Principle:
Principle #15Dynamics

3Reliability

If processing is performed each time a report generation request is received to ensure up-to-date data, then data freshness is maintained, but computing resources are wasted

Engineering Contradiction:
Improvedata freshnessVSAvoidcomputing resource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of performing all data gathering and processing when a report request is received, the system performs preliminary data gathering at scheduled intervals and stores results in a repository. When a report request arrives, the system only performs minimal processing to check if cached data is sufficient, rather than regenerating all data from sources, thereby maintaining data freshness while improving computing resource efficiency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of data from data sources and stores them in a repository for reuse. When report requests are generated, the system uses these pre-created data copies instead of retrieving and processing raw data from sources each time, significantly reducing computing resource consumption while maintaining the ability to generate reports efficiently.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8452724B2Techniques for creating reports using cached data
Publication Date: 2013.05.28 ORACLE INT CORP
  • US8452724B2 patent drawing
  • US8452724B2 patent drawing
  • US8452724B2 patent drawing

AI summary

Techniques for generating reports from cached data are provided. When a report is requested, a date and time when data in the report data cache was generated is compared with a date and time when data was collected by each of one or more data collectors that gather data used to generate the report data. If one of the data collectors has collected data since the data for the report in the report data cache has been updated, the data for the requested report will be regenerated from the data collected from each of the data collectors associated with the report and the regenerated data inserted into the report data cache. Subsequent requests for the report can be satisfied by generating the report using the data stored in the report data cache rather than regenerating the report data each time a request for a report is received.