Intermediation Server Standardizes Data Exchange

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for intermediating between provider systems and client devices face challenges in efficiently exchanging data for travel-related products, as different entities use varying mechanisms and formats, leading to compatibility issues and increased load on provider systems.

Innovation Solution

An intermediation server generates intermediation objects by mapping provider object data into a standardized format, omitting original provider object data and identifiers, and provides these objects to client devices, allowing for encrypted intermediation object identifiers to request further information from provider systems without storing intermediation objects or identifiers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If provider systems and client devices exchange data using different mechanisms and formats, then each entity can maintain its own data standards, but compatibility issues arise and the system complexity increases

Engineering Contradiction:
Improvedata format flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediation server that acts as a mediator between provider systems and client devices. The server receives data in various formats from providers, transforms it into a standardized intermediation format, and forwards it to clients. This intermediary layer enables multiple data formats to coexist without direct compatibility requirements between providers and clients, resolving the contradiction by adding adaptability through standardization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If all provider object data and identifiers are transmitted to client devices, then complete information is provided, but the load on provider systems increases

Engineering Contradiction:
Improveinformation completenessVSAvoidprovider system load
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent extracts only the essential information needed for client-side operations from the complete provider objects. The intermediation server creates simplified intermediation objects that contain necessary data (such as item descriptions and basic identifiers) while omitting detailed provider-specific information. This extraction reduces the data volume transmitted to clients and decreases the processing load on provider systems while maintaining sufficient information for client functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If provider object identifiers are included in data exchanges, then data can be precisely tracked and retrieved, but security and privacy are compromised

Engineering Contradiction:
Improvedata tracking accuracyVSAvoidsecurity risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent creates anonymized copies of provider object identifiers through the intermediation process. Instead of transmitting original provider object identifiers directly to clients, the server generates intermediation object identifiers that serve as functional copies. These copied identifiers enable data tracking and retrieval operations while being decoupled from the original sensitive identifiers, thus maintaining reliability for operational purposes while reducing security risks by preventing direct exposure of provider-internal identifier systems.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3809345B1Device, system and method for intermediation between a provider system that provides provider objects and a client device
Publication Date: 2023.11.29 AMADEUS SAS
  • EP3809345B1 patent drawingFigure 1
  • EP3809345B1 patent drawingFigure 2
  • EP3809345B1 patent drawingFigure 3

AI summary

A server: receives from at least one provider system, at least one provider object that includes provider object data representing at least one item provided by the provider system(s); generates an intermediation object, corresponding to the at least one provider object, including an intermediation object identifier that identifies the intermediation object and intermediation object data populated with at least a subset of the provider object data, the intermediation object and the intermediation object identifier omitting: the provider object data, and any provider object identifier in an original form; and provides the intermediation object, in place of the at least one provider object, to a client device that requested the at least one item, the intermediation object provided. The intermediation object identifier may enable the server to intermediate between the client device and the provider system(s) without storing the provider object and/or any provider object identifier.