Distributed Context Synchronization for Multi-Server Reservation Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern travel reservation systems face challenges in synchronizing Passenger Name Record (PNR) data across different platforms and protocols during migration or operation, leading to consistency and resource overhead issues.

Innovation Solution

A distributed context synchronization mechanism that maintains a local context version on each server, using a shared context storage area to ensure the most up-to-date PNR data is used, with lazy synchronization only occurring when necessary, and employing a Distributed Context Correlator to manage context sharing across heterogeneous platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If batch synchronization of PNRs is implemented across multi-server systems, then data consistency is improved, but resource overhead increases significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidresource overhead
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements event-driven synchronization that triggers periodically only when specific events occur (PNR updates, context changes). This avoids continuous batch synchronization while maintaining data consistency, reducing resource overhead by activating synchronization mechanisms only when necessary rather than on fixed schedules or continuously

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

Each server maintains its own local context version and autonomously determines whether synchronization is needed by comparing version identifiers. Servers self-manage their synchronization needs without requiring centralized batch coordination, reducing overall system resource overhead while ensuring data consistency through decentralized decision-making

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If progressive migration from legacy mainframe to open system is performed, then system adaptability is improved, but synchronization complexity increases

Engineering Contradiction:
Improvesystem adaptabilityVSAvoidsynchronization complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a shared context storage area that acts as an intermediary between legacy mainframe systems and open systems. This mediator layer handles protocol differences and data format conversions, allowing progressive migration while managing synchronization complexity through a standardized interface that abstracts the heterogeneity between different platforms

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The shared context storage area serves multiple functions simultaneously: it stores PNR data, maintains version identifiers, tracks last update timestamps, and provides a common interface for both mainframe and open systems. This multi-functional component reduces synchronization complexity by consolidating multiple synchronization tasks into a single universal mechanism that works across heterogeneous platforms

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Speed

If multiple servers maintain local context versions of PNR, then access speed is improved, but data consistency becomes challenging

Engineering Contradiction:
Improveaccess speedVSAvoiddata consistency
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where each server continuously monitors the shared context storage area for version identifier changes. When a server detects that its local context version is outdated compared to the shared storage, it automatically retrieves the updated version. This feedback loop ensures data consistency is maintained across all servers without requiring continuous synchronization, preserving fast local access while ensuring reliability

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP2500832B1Method and system for synchronization mechanism on multi-server reservation system
Publication Date: 2018.07.25 AMADEUS SAS
  • EP2500832B1 patent drawingFigure 1
  • EP2500832B1 patent drawingFigure 2
  • EP2500832B1 patent drawingFigure 3

AI summary

The method and system according to a preferred embodiment of the present invention allows synchronizing the PNR values across a multi-server (possibly multi-platform) reservation system with an efficient and consistent mechanism. The mechanism addresses the consistency and performance issues thanks to its versioning and its lazy behaviour (the synchronization occurs only when required). It can be used as a solution during a migration phase from one system to another with progressive migration of applications sharing data, and also as a permanent solution for distributed applications across different platforms. According to a preferred embodiment of the present invention, the reservation services are distributed between two different platforms (e.g. mainframe and open platforms) they require sharing the same Passenger Name Record (PNR) contextual data in read and write mode to perform their business functionalities. The method and system of a preferred embodiment of the present invention allows the synchronization of data (e.g. PNR data) which are shared in read and write mode across different platforms and across protocols of communication (e.g. TPF mainframe and open systems) so that the systems can share the same up-to-date PNR context data