Auxiliary Data Repository for Dynamic Adjustment Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In communication systems involving multiple computing subsystems, dynamic adjustments to item prices and compositions, such as those in travel-related services, often lead to data conflicts and require costly modifications to existing subsystems, particularly when these adjustments are not reflected in external repositories.

Innovation Solution

An intermediation server manages auxiliary data repositories that store both primary and auxiliary data, allowing for the storage of adjustments, and facilitates the transmission of auxiliary data to provider subsystems, thereby minimizing the need for modifications to existing systems by storing order identifiers and sending auxiliary data separately from primary data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If auxiliary data storing adjustments is implemented, then data conflict resolution is improved, but system complexity increases

Engineering Contradiction:
Improvedata conflict resolutionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an auxiliary repository as an intermediary component between the provider subsystem and external repositories. This repository stores auxiliary data (adjustments) separately from primary data, allowing the system to resolve data conflicts without requiring modifications to existing subsystems. The auxiliary repository acts as a buffer that mediates between the published data and the actual transactions, eliminating direct conflicts while maintaining system simplicity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If separate transmission of auxiliary data is implemented, then subsystem modification needs are reduced, but data transmission complexity increases

Engineering Contradiction:
Improvesubsystem modification needsVSAvoiddata transmission complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent segments the data transmission process into two distinct parts: primary data transmission and auxiliary data transmission. The reporting message contains only primary data (published data) and is sent through existing channels without modification. Auxiliary data (adjustments) is transmitted separately through a different channel. This segmentation allows existing subsystems to remain unchanged while still providing comprehensive data, as the two data types travel through appropriate pathways independently.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If auxiliary repository is introduced, then data management flexibility is improved, but information loss risk increases

Engineering Contradiction:
Improvedata management flexibilityVSAvoidinformation loss risk
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements a feedback mechanism where the system retrieves auxiliary data from the auxiliary repository based on transaction identifiers and sends it to the provider subsystem after processing. This feedback loop ensures that adjustments stored in the auxiliary repository are properly communicated to the provider subsystem when needed, preventing information loss. The system continuously monitors and retrieves auxiliary data to ensure data integrity while maintaining the flexibility benefits of separate storage.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3828727A1System and method of auxiliary data access
Publication Date: 2021.06.02 AMADEUS SAS
  • EP3828727A1 patent drawingFigure 1
  • EP3828727A1 patent drawingFigure 2
  • EP3828727A1 patent drawingFigure 3

AI summary

A method of providing access to auxiliary data for a provider subsystem includes: storing offer data corresponding to an item, the offer data including (i) primary data, and (ii) auxiliary data defining an adjustment between the primary data and corresponding published data stored at an external repository; storing the offer data in an auxiliary repository; in response to an order request from a client subsystem: obtaining an order identifier corresponding to the offer data; and updating the auxiliary repository to store the order identifier in association with the offer data; in response to obtaining the order identifier, generating a reporting message for transmission to a provider subsystem, the reporting message containing the primary data and omitting the auxiliary data; and subsequent to generating the reporting message, retrieving the offer data from the auxiliary repository, and sending at least the auxiliary data to the provider subsystem.