Caching Provider Objects by Reusability and Context

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for providing travel-related products and services face inefficiencies in data exchange due to different mechanisms employed by entities, leading to challenges in quickly and efficiently responding to user requests for travel-related items like flights and hotel reservations.

Innovation Solution

A method and system that categorize provider objects by reusability and context characteristics, using machine learning models to determine their validity and store them in a cache, allowing for rapid retrieval and response to user requests without needing to recreate provider objects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If provider objects are stored and retrieved from a cache, then response time is reduced, but cache management complexity increases

Engineering Contradiction:
Improveresponse timeVSAvoidcache management complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The cache is segmented into multiple caches, each dedicated to storing provider objects for specific providers. This segmentation simplifies cache management by allowing independent operation and validation of each cache, reducing the overall complexity compared to managing a single large cache with diverse content.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Provider objects are pre-validated by determining their estimated validity period in advance. This preliminary validation action allows the system to quickly check whether cached objects are still valid without complex real-time validation logic, reducing response time while keeping cache management straightforward.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If provider objects are validated for current validity, then data accuracy is improved, but processing resources increase

Engineering Contradiction:
Improvedata accuracyVSAvoidprocessing resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system performs partial validation by determining only the estimated validity period of provider objects rather than complete real-time validation. This partial action approach ensures data accuracy for objects within their validity period while avoiding the excessive processing resources that would be required for comprehensive validation of all cached objects.

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If provider objects are categorized by reusability and context, then request processing efficiency is improved, but categorization complexity increases

Engineering Contradiction:
Improverequest processing efficiencyVSAvoidcategorization complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Provider objects are categorized into distinct groups based on reusability characteristics and context. This segmentation allows the system to efficiently retrieve appropriate cached objects by matching request characteristics with category definitions, improving request processing efficiency while maintaining manageable categorization through clear, defined criteria.

Inventive Principle:
Principle #1Segmentation

4Loss of energy

If cached provider objects are used, then bandwidth usage is reduced, but cache hit rate decreases with diverse requests

Engineering Contradiction:
Improvebandwidth usageVSAvoidcache hit rate
Core Design Contradiction:
Loss of energyVSProductivity

Solution Approach 1:

The system changes parameters by determining estimated validity periods and reusability characteristics of provider objects. These parameter changes enable the cache to adapt to diverse requests by providing validity information that helps determine whether cached objects can be reused, thereby maintaining high cache hit rates while reducing bandwidth usage even when request diversity increases.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP3809276A1Device, system and method for providing provider objects from a cache
Publication Date: 2021.04.21 AMADEUS SAS
  • EP3809276A1 patent drawingFigure 1
  • EP3809276A1 patent drawingFigure 2
  • EP3809276A1 patent drawingFigure 3

AI summary

A device, system and method for providing provider objects from a cache is provided. Provider objects are received representing items provided by provider systems. The provider objects are categorized by reusability and/or context characteristics and stored as categorized. A request is received for one or more items provided by the one or more provider systems. A stored and categorized provider object is determined to meet criteria associated with the request, including one or more of a respective reusability and respective context characteristics of the provider object. In response to determining that the provider object, that meets the criteria, is estimated to be currently valid, a response corresponding to the provider object is provided.