Lightweight Local Database for Offline Data Sync

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for Occasionally Connected Devices (OCDs) face challenges in deploying and maintaining lightweight local databases that are synchronizable with Remote Global Databases (RGDbs), leading to performance issues and high maintenance complexity due to structural replicas and relational database complexities, especially in enterprise applications with thousands of users.

Innovation Solution

A system and method for deploying lightweight non-relational local databases on OCDs, using a screen-based approach where only user-accessed screens are cached, with data stored as objects that can be synchronized through a middle layer, business logic layer, and orchestration layer, allowing for easy maintenance and synchronization without replicating the entire RGDb structure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a structural replica of the Remote Global Database is deployed on the Occasionally Connected Device, then data availability offline is improved, but device memory footprint and maintenance complexity increase significantly

Engineering Contradiction:
Improvedata availability offlineVSAvoiddatabase structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts only the necessary data elements required for offline functionality from the complete Remote Global Database structure. Instead of replicating the entire database schema, it selectively caches specific data objects and their relationships that are essential for offline operation, thereby reducing the footprint and complexity on the OCD while maintaining data availability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The database structure is segmented into essential offline-cachable components and non-essential components. The patent divides the database into data objects that can be independently cached and synchronized, allowing the OCD to store only the relevant segments needed for offline operation rather than the complete database structure.

Inventive Principle:
Principle #1Segmentation

2Stability of the object's composition

If a relational database structure is maintained on the Occasionally Connected Device, then data relationship integrity is improved, but operational performance and ease of maintenance deteriorate

Engineering Contradiction:
Improvedata relationship integrityVSAvoiddatabase maintenance ease
Core Design Contradiction:
Stability of the object's compositionVSEase of operation

Solution Approach 1:

The patent uses a simplified copy mechanism that replicates only the essential data relationships needed for offline operation, rather than maintaining a complete relational database structure. This copy approach preserves necessary data integrity while eliminating the complexity of full relational constraints, making the database easier to maintain on resource-constrained devices.

Inventive Principle:
Principle #26Copying

3Speed

If the entire Remote Global Database structure is replicated on the Occasionally Connected Device, then data access speed offline is improved, but synchronization complexity and time increase

Engineering Contradiction:
Improvedata access speed offlineVSAvoidsynchronization time
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The patent extracts and caches only the specific data objects and relationships that are frequently accessed or essential for offline operation. This selective extraction reduces the amount of data that needs to be synchronized, thereby decreasing synchronization time while maintaining fast local data access for critical offline functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

4Quantity of substance

If a lightweight local database is deployed on the Occasionally Connected Device, then device resource consumption is reduced, but data synchronization capability with the Remote Global Database deteriorates

Engineering Contradiction:
Improvedevice memory footprintVSAvoiddata synchronization capability
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent implements a dynamic database structure that adapts to the available device resources and synchronization needs. The local database on the OCD can dynamically adjust its structure and content based on what is cached locally, allowing it to remain lightweight while maintaining synchronization capability through a flexible schema that can evolve with the Remote Global Database without requiring a complete structural replica.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP2556444B1System and method for sharing data between occasionally connected devices and remote global database
Publication Date: 2018.10.10 TATA CONSULTANCY SERVICES LTD
  • EP2556444B1 patent drawingFigure 1
  • EP2556444B1 patent drawingFigure 2A~2B
  • EP2556444B1 patent drawingFigure 2C~3

AI summary

The invention provides system and method for deployment and maintenance of lightweight local databases on the Occasionally Connected Devices OCD) and synchronization of data between the local database and the remote global database (RGDb). The database to be accessed by the user is generally located on at least one remote server. As the OCDs are intended for offline use, a module for local data handling is provided. This module for local data handling is a lightweight non-relational database. The data is stored in the form of objects on the OCD. Each such stored object is captured in the form of a screen instance disposed at the OCD when the user is online. The present invention provides screen based non-relational data sharing, wherein screens are means to capture and display the data shared in an online mode and invoke the data from the stored objects in an offline mode.