Database Synchronization via Shared Event Containers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Synchronizing databases that store similar or same information related to provider objects is challenging, particularly when individual data containers need to be combined, as determining which containers to combine and what portions to combine is difficult, especially when provider objects are associated with different communication devices and network addresses.

Innovation Solution

A method and device for maintaining an event database and a shared event database, comparing shareable data containers with event data containers, and synchronizing them by adding portions of shareable data containers to event data containers when associated events are identified, while also handling sub-events, requests, and inconsistencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If individual data containers are stored separately in databases for different network addresses, then data can be managed independently at each address, but determining which containers to combine and what portions to combine becomes challenging

Engineering Contradiction:
ImproveIndependent data management at different network addressesVSAvoidComplexity of determining which containers to combine
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a shared database as an intermediary between individual user databases. This shared database stores data containers that can be shared across multiple network addresses, facilitating automatic identification and combination of shareable data without complex manual determination processes. The intermediary shared database resolves the complexity by providing a centralized coordination point for data sharing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If data containers are combined at another database, then information related to provider objects can be consolidated, but it is challenging to determine which individual data containers to combine and what portions to combine

Engineering Contradiction:
ImproveEfficiency of data consolidationVSAvoidDifficulty in identifying which containers and portions to combine
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a feedback mechanism where the shared database provides information about which data containers are shareable and should be combined. The system automatically identifies shareable portions of data containers and provides feedback to the consolidation process, eliminating the difficulty of manual determination. This feedback loop enables automatic and accurate data consolidation based on sharing indicators.

Inventive Principle:
Principle #23Feedback

3Reliability

If databases are synchronized by combining data containers, then accurate and efficient data combination is achieved, but communication and processing resources are consumed

Engineering Contradiction:
ImproveAccuracy of data combinationVSAvoidCommunication and processing resources consumed
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the shareable portions of data containers from individual databases and transfers them to the shared database for consolidation. Rather than synchronizing entire databases or non-shareable data, the system extracts and processes only the relevant shareable portions, reducing communication overhead and processing resource consumption while maintaining accurate data combination for shared information.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20240176800A1Device, system and method for synchronizing databases
Publication Date: 2024.05.30 AMADEUS SAS
  • US20240176800A1 patent drawing
  • US20240176800A1 patent drawing
  • US20240176800A1 patent drawing

AI summary

A device, system and method for synchronizing databases. A device or devices(s) maintain an event database and a shared event database, the event database comprising event data containers indicative of given events associated with a plurality of network addresses, and the shared event database comprising shareable data containers indicative of respective events associated with respective individual network addresses. The device or devices(s) compare a shareable data container, stored at the shared event database, with an event data container, stored at the event database. The device or devices(s), in response to determining that a respective event indicated by the shareable data container is associated with a given event indicated by the event data container, synchronize, via the communication interface, the event database and the shared event database by adding at least a portion of the shareable data container to the event data container.