Database Background Synchronization via Snapshot Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In mobile computing environments, data synchronization between remote systems and centralized databases is resource-intensive and often requires restrictive access, diminishing performance and efficiency due to the lack of concurrent transactional access during synchronization operations.

Innovation Solution

Implementing a background synchronization process using metadata to allow transactional access while synchronizing data, employing a 'snapshot' of data with row state metadata to identify changes and manage upload states, enabling efficient data integrity maintenance without restricting access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data synchronization is performed between remote systems and consolidated database, then data integrity is maintained, but concurrent transactional access is restricted and performance diminishes

Engineering Contradiction:
Improvedata integrityVSAvoidconcurrent transactional access performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the database into multiple snapshots (first snapshot, second snapshot) that can be accessed concurrently. Each snapshot represents a consistent state of the database at a specific point in time, allowing multiple transactions to proceed simultaneously without interfering with each other or with the synchronization process.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates snapshots of the database before synchronization operations begin. These pre-created snapshots serve as read-only copies that can be accessed during synchronization, eliminating the need to restrict access to the current database state and enabling concurrent transactions to proceed without waiting for synchronization to complete.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If background synchronization is implemented using snapshots and metadata, then concurrent access is enabled, but system complexity increases

Engineering Contradiction:
Improveconcurrent transactional accessVSAvoidsynchronization system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces metadata as an intermediary layer between the snapshots and the application layer. This metadata layer manages the complexity of snapshot management, version tracking, and synchronization state by providing a standardized interface, thereby isolating the complexity from the rest of the system and making the concurrent access mechanism more manageable.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent uses copies of the database (snapshots) instead of directly accessing the live database during synchronization. These copies are created and maintained with the help of metadata, which tracks their state and validity. This copying approach enables concurrent access while the metadata management system handles the complexity of maintaining multiple versions.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP2380090B1Data integrity in a database environment through background synchronization
Publication Date: 2019.04.10 IANYWHERE SOLUTIONS INC
  • EP2380090B1 patent drawingFigure 1
  • EP2380090B1 patent drawingFigure 2
  • EP2380090B1 patent drawingFigure 3

AI summary

Systems, methods and computer program products for maintaining data integrity in a database environment are described. In operation, a synchronization process is initiated in a remote database system for synchronization of remote data from the remote database system with consolidated data of a consolidated database. Metadata for each row of the remote data is utilized to allow transactional access to the remote data while the synchronization process occurs.