Intermediation Server Request Reproduction for Provider Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face increased bandwidth usage and processing resource utilization due to inefficient data exchange mechanisms between entities providing travel-related products, particularly in NDC-based data exchanges where many requests result in few bookings, leading to wasted resources.

Innovation Solution

An intermediation server reproduces a requesting step by generating and altering requests based on provider system options stored in memory, narrowing the number of requested provider objects, and caching responses to reduce unnecessary queries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If client devices directly request provider objects from provider systems, then data exchange can occur, but bandwidth usage and processing resources increase unnecessarily

Engineering Contradiction:
Improvedata exchange efficiencyVSAvoidbandwidth usage and processing resources
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

An intermediation server is introduced between client devices and provider systems to reproduce requesting steps. The server generates and alters requests based on stored provider system options, narrowing the number of provider objects requested. This intermediary role reduces unnecessary direct requests from clients to providers, thereby decreasing bandwidth usage and processing resource consumption while maintaining effective data exchange.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If many requests are sent to provider systems, then more provider objects can be retrieved, but resource waste increases since few result in bookings

Engineering Contradiction:
Improveprovider object retrieval capabilityVSAvoidwasted processing resources
Core Design Contradiction:
Adaptability or versatilityVSLoss of substance

Solution Approach 1:

The intermediation server performs preliminary actions by storing provider system options and pre-configuring request parameters before actual client requests occur. When requests are reproduced, the server uses this pre-stored information to narrow down the scope of provider objects requested, ensuring that only relevant objects are retrieved. This preliminary preparation reduces the number of unnecessary requests and minimizes resource waste while maintaining comprehensive provider object retrieval capability.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If client devices send detailed requests without provider object identifiers, then flexibility is maintained, but additional processing steps are required

Engineering Contradiction:
Improverequest flexibilityVSAvoidrequest processing complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The intermediation server creates copied and altered versions of client requests based on stored provider system options. Instead of directly processing detailed requests without identifiers, the server reproduces these requests with appropriate modifications, including generating provider object identifiers where needed. This copying mechanism maintains the flexibility of detailed client requests while simplifying the processing complexity by handling identifier generation and request alteration centrally at the intermediation server.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12437324B2Device, system and method for reproducing a requesting step between a client device and a provider system at an intermediation server
Publication Date: 2025.10.07 AMADEUS SAS
  • US12437324B2 patent drawing
  • US12437324B2 patent drawing
  • US12437324B2 patent drawing

AI summary

A device, system and method for reproducing a requesting step between a client device and a provider system at an intermediation server. An intermediation server reproduces a requesting step for one or more provider objects, including requesting identifiers and price estimates thereof, a provider object representing at least one item provided by a provider system, the reproducing of the requesting step comprising providing request(s) for the provider objects to the provider system, the request(s) being generated and/or altered based on options associated with the provider system, the options to narrow a number of the one or more provider objects requested via the one or more requests. The intermediation server receives, from the provider system, the provider object(s) including the identifier(s) and the price estimates thereof. The intermediation server: provides, to a client device, the one or more provider objects; and/or stores the one or more provider objects.