Precomputed Availability Cache Validation with Selective Segment Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database query systems face challenges in ensuring short response times for large data volumes and maintaining the accuracy of cached query results, as pre-computed data becomes outdated due to underlying data changes.

Innovation Solution

Implementing a precomputed origin and destination availability (PONDA) cache that segments availability requests into smaller blocks, uses validity identifiers for data footprint matching, and updates cache entries when mismatches are detected, ensuring fast and accurate availability searches.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If pre-computed query results are stored in a cache system to shorten query times, then response time is improved, but the cached results become outdated when underlying data changes

Engineering Contradiction:
Improvequery response timeVSAvoidaccuracy of cached results
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent segments the cache validation process into two independent parts: a validity cache that stores only validity identifiers (small data) and a content cache that stores actual query results (large data). This segmentation allows the validity cache to be frequently updated and checked without impacting the content cache performance, resolving the contradiction between fast queries and data freshness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a validity cache as an intermediary layer between the content cache and the underlying data sources. This intermediary stores validity identifiers that mediate the freshness check process, allowing the system to determine whether to serve cached content without directly accessing or updating the underlying data sources frequently, thus maintaining both speed and accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the entire data domain is re-computed frequently to maintain cache freshness, then data accuracy is improved, but processing time and computational resources increase

Engineering Contradiction:
Improvefreshness of cached dataVSAvoidrecomputation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of re-computing the entire data domain, the patent segments recomputation into selective updates based on validity identifiers. Only the specific segments that have changed (indicated by validity identifier updates) need to be re-computed and updated in the content cache, rather than processing the entire domain, thus reducing computational overhead while maintaining freshness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary action by pre-computing and storing validity identifiers along with the content in the validity cache before actual queries are made. This preliminary preparation allows the system to quickly identify which data segments need updating without performing unnecessary recomputations, reducing both time and resource consumption while ensuring data freshness.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If manual re-computation schedules are established to maintain cache accuracy, then data freshness is improved, but system complexity and maintenance overhead increase

Engineering Contradiction:
Improvecache data freshnessVSAvoidcache update mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service by allowing the validity cache to automatically track and communicate data freshness status through validity identifiers. The system automatically determines when content needs updating based on validity identifier changes, eliminating the need for manual scheduling and reducing operational complexity while maintaining reliable data freshness.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent uses feedback mechanisms where validity identifiers provide continuous feedback about data freshness status. This feedback loop automatically triggers content cache updates when validity identifiers change, creating a self-regulating system that maintains freshness without manual intervention and reduces operational complexity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4099180B1Precomputed cache validation
Publication Date: 2025.09.17 AMADEUS SAS
  • EP4099180B1 patent drawingFigure 1
  • EP4099180B1 patent drawingFigure 2A~2B
  • EP4099180B1 patent drawingFigure 2C~2D

AI summary

Methods, systems, and computer program products for implementing a precomputed availability cache that is a database of precomputed availabilities for availability searches. An availability request is received. Segmentation data that includes one or more segments is obtained. An associated segmentation entry within a precomputed availability cache is determined for each of the one or more segments. A validity check of the availability data that indicates that at least one of the availabilities for the segments is invalid is performed. An availability for the at least one of the availabilities for the segments is invalid is determined by accessing an inventory database replication and processing an availability computation for the at least one of the availabilities. The cache is updated with the determined availability for the at least one of the availabilities. Availability results that include availabilities for each of the one or more segments are provided.