Categorized Provider Object Cache for Travel Data Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the context of travel-related products, existing systems face challenges in efficiently exchanging data between various entities due to different mechanisms employed by airlines, travel agencies, and reservation systems, leading to inefficiencies in data retrieval and increased bandwidth usage.
Innovation Solution
A system and method that categorize provider objects by reusability and context characteristics, storing them in a cache for quick retrieval, allowing intermediation servers to provide valid objects directly from the cache rather than requesting new ones from provider systems, reducing response time and bandwidth usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If provider objects are requested from provider systems for each data exchange, then data accuracy is maintained, but response time increases and bandwidth usage increases
Solution Approach 1:
The system performs preliminary actions by receiving and storing provider objects in a cache before they are actually needed for data exchange. The cache pre-processes and categorizes provider objects by reusability and context characteristics, so when a request comes in, the object can be quickly retrieved without needing to contact the provider system, thus maintaining accuracy while reducing response time.
Solution Approach 2:
The cache acts as an intermediary between the requesting system and the provider system. Instead of directly requesting provider objects from the provider system for every data exchange, the cache mediates by providing stored copies of provider objects that meet the requested criteria, reducing the frequency of direct communications with provider systems while maintaining data accuracy through validation against reusability and context characteristics.
2Reliability
If provider objects are requested from provider systems for each data exchange, then data freshness is ensured, but bandwidth usage increases
Solution Approach 1:
The system creates and stores copies of provider objects in the cache instead of repeatedly requesting the same objects from provider systems. These cached copies are validated against reusability and context characteristics to ensure they remain appropriate for use, allowing multiple requests to be served from local copies rather than generating continuous bandwidth usage for fetching the same data.
Solution Approach 2:
The cache performs preliminary storage of provider objects before they are needed, categorizing them by reusability and context characteristics. This preliminary action reduces the need for repeated bandwidth-intensive requests to provider systems, as the cache can serve multiple requests from pre-fetched and validated copies.
3Speed
If provider objects are cached without categorization, then retrieval speed increases, but system complexity increases
Solution Approach 1:
The cache categorizes provider objects into different segments based on reusability and context characteristics. This segmentation allows for organized storage and efficient retrieval by matching request criteria against categorized objects, improving retrieval speed without creating excessive complexity through structured classification rather than unorganized storage.
Solution Approach 2:
The system changes the parameters of provider objects by adding metadata tags for reusability and context characteristics during caching. This parameter enrichment enables faster matching and retrieval based on specific criteria, while the structured approach to parameter addition maintains manageable system complexity through consistent classification rules.
4Reliability
If cached provider objects are validated against reusability and context characteristics, then data accuracy is maintained, but processing resources increase
Solution Approach 1:
The cache performs partial validation of provider objects by checking only the essential reusability and context characteristics rather than complete validation against all possible criteria. This partial action maintains sufficient data accuracy for most use cases while reducing the processing resources required compared to exhaustive validation of every cached object.
Data Source
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.