Centralized Inventory System Batch Processing for Hotel Data Sync

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current centralized inventory systems face challenges in managing and synchronizing the increasing number of messages related to electronic provider objects, such as hotel room availability and prices, across various distribution channels, leading to unsatisfactory data synchronization.

Innovation Solution

A method involving a centralized inventory system that receives object changes, merges them by category, determines their impact on data pairs, and updates attributes periodically, comparing hash values to detect changes and propagate updates to external platforms, thereby ensuring data synchronization and scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the centralized inventory system processes all object changes individually in real-time, then data synchronization accuracy is improved, but system complexity and processing overhead increase significantly

Engineering Contradiction:
Improvedata synchronization accuracyVSAvoidsystem processing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple object changes of the same category together before processing. Instead of handling each change individually, the system groups changes by category (e.g., price changes, availability changes) and processes them as batches. This reduces the number of queries to external platforms while ensuring all changes are propagated, thereby maintaining data synchronization accuracy while reducing system complexity and processing overhead.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary grouping and categorization of object changes before sending them to external platforms. By pre-organizing changes into categories and determining their impact on data pairs in advance, the system avoids the complexity of real-time individual processing while ensuring accurate synchronization. This preliminary action allows the system to prepare update batches efficiently before external communication occurs.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the system sends every object change immediately to external platforms, then data freshness is improved, but the number of messages and network traffic increase

Engineering Contradiction:
Improvedata freshnessVSAvoidnumber of messages
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple object changes of the same category into single batched updates before transmitting to external platforms. For example, instead of sending 10 separate price change messages, the system groups them into one consolidated update message. This maintains data freshness by ensuring all changes are propagated, while significantly reducing the total number of messages and network traffic.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system employs periodic batch processing of object changes rather than continuous individual transmission. Changes are accumulated and processed in periodic batches based on category and impact analysis. This periodic action reduces message frequency while ensuring data freshness within acceptable timeframes, balancing the need for up-to-date information with network efficiency.

Inventive Principle:
Principle #19Periodic action

3Measurement precision

If the centralized inventory system queries the general database frequently for each object change, then change detection accuracy is improved, but hardware resource consumption increases

Engineering Contradiction:
Improvechange detection accuracyVSAvoidhardware resource consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary determination of change impact on data pairs before executing actual database queries. By analyzing which data pairs are affected by merged object changes and only querying for those specific pairs, the system maintains accurate change detection while minimizing the number of database queries. This preliminary filtering action significantly reduces hardware resource consumption compared to querying for every individual change.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges multiple object changes and determines their combined impact on data pairs before querying the database. Instead of querying for each individual change, the system consolidates changes by category, identifies the union of affected data pairs, and performs queries only for those impacted pairs. This approach maintains comprehensive change detection accuracy while reducing the total number of queries and associated hardware resource consumption.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20240412119A1Method for centralized updating of prices and availability of hotel rooms
Publication Date: 2024.12.12 AMADEUS SAS
  • US20240412119A1 patent drawing
  • US20240412119A1 patent drawing

AI summary

An aspect of the invention relates to a method for centrally updating inventory of electronic provider objects comprising:merging a plurality of object changes from a first queue by change category; for each change category, determining an impact of the merged object changes on a set of data pairs in a general database, each data pair being formed by two given attributes of an electronic provider object placing each impacted data pair in a second queue; determining, for each impacted data pair, an update of the two given attributes of an electronic provider object over a second predetermined period via a query to the general database.