Client Terminal Local Database for Offline Data Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing client terminal systems face productivity losses and data accessibility issues during communication outages, as they store data in application-specific, distributed databases that are not accessible to other applications and lack centralized storage solutions.

Innovation Solution

A local communication device that stores data from multiple sources, including remote and local servers, and client terminal devices, converting data to a predefined format and providing centralized storage and retrieval capabilities, even during network disruptions, using a software agent, storage module, conversion module, and synchronizing module to maintain data version tags and facilitate offline connectivity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is stored in distributed, application-specific databases on client terminals, then each application can access its own data, but other applications cannot access the data and centralized storage is not achieved

Engineering Contradiction:

Improvedata accessibilityVSAvoiddata storage architecture

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple distributed, application-specific databases into a single centralized database on the client terminal. This consolidation allows all applications to access the same data repository, eliminating data silos while reducing architectural complexity through unified management.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The centralized database serves as a universal data storage solution for all applications on the client terminal, rather than having separate databases for each application. This multi-functional approach enables any application to access any data stored in the centralized database, improving overall system versatility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If client terminals rely on remote servers for data storage, then data can be accessed when connected, but data access is lost during communication outages

Engineering Contradiction:

Improvedata access continuityVSAvoidwork continuity during outages

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by downloading and storing data from remote servers to the centralized local database before communication outages occur. This advance preparation ensures that data is available locally when the network is unavailable, maintaining reliability and productivity during outages.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The centralized database acts as an intermediary between remote servers and applications during communication outages. It stores and manages data locally, allowing applications to continue accessing data without direct connection to remote servers, thus bridging the gap during network disruptions.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If multiple applications store data in separate databases, then each application has dedicated storage, but data cannot be shared across applications

Engineering Contradiction:

Improvedata sharing capabilityVSAvoidnumber of databases

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent combines multiple separate application databases into a single centralized database, enabling data sharing across all applications. This merging reduces the total number of databases from many separate ones to one unified repository, improving data sharing capability while reducing quantity.

Inventive Principle:

Principle #5Merging (Combining)

4Ease of operation

If data is stored locally on client terminals in application-specific formats, then offline access is possible, but data format conversion and centralized access are not achieved

Engineering Contradiction:

Improveoffline data accessVSAvoiddata format compatibility

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system implements parameter changes by converting data from various application-specific formats into a standardized format for storage in the centralized database. This format standardization maintains offline access capability while improving data format compatibility across all applications.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS8671155B2System and method of employing a client side device to access local and remote data during communication distruptions

Publication Date: 2014.03.11 IDEAGEN LTD

AI summary

A method and system are provided for locally storing data obtained from a plurality of sources, including a remote server, a local server and a client terminal device. A local communication device is provided to include a plurality of applications that access data stored on at least one of the remote server, the local server and the client terminal device and provides access to the data during time periods when the client terminal device is disconnected from at least one of the local server and the remote server. The local communication device includes applications that gather data from the local server, the remote server and the client terminal device and generate a database to store the gathered data. The local communication device includes a conversion module that generates a predefined format for the gathered data prior to storing the data on the database.