Mobile Database Update Buffering for Unreliable Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed employees in various industries face challenges in accessing and updating central database data remotely without the need for a network browser, particularly in scenarios where network connectivity is unreliable.

Innovation Solution

A system and process allowing users with mobile devices to wirelessly interact with a remote database using a username, where data records are transmitted in subsets, and updates can be added but not deleted, with the option to store updates locally for later transmission when network conditions are unsuitable.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If data records are transmitted to mobile devices for remote access, then employees can access central database data remotely, but network connectivity issues may cause transmission failures and data loss

Engineering Contradiction:
Improveremote database accessVSAvoiddata transmission reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary actions by storing updates locally in the mobile device's database before successful transmission to the central database. This ensures that data is preserved even if transmission fails, and the update can be retried later without losing the data.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The mobile device's local database acts as an intermediary between the user and the central database. It buffers updates locally and manages transmission to the central database, isolating the user from network connectivity issues while maintaining data integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the system allows multiple users to access and update database records simultaneously, then remote collaboration is improved, but data locking and consistency issues may occur

Engineering Contradiction:
Improvemulti-user access capabilityVSAvoiddata locking
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system segments the database access by allowing each mobile device to maintain its own local copy of updates. Each device works independently with its local database, eliminating the need for centralized locking mechanisms while ensuring data consistency through individual transmission to the central database.

Inventive Principle:
Principle #1Segmentation

3Reliability

If the mobile device stores updates locally for later transmission, then data is preserved during network failures, but device storage space is consumed

Engineering Contradiction:
Improvedata preservationVSAvoiddevice storage usage
Core Design Contradiction:
ReliabilityVSVolume of stationary object

Solution Approach 1:

The system discards local updates from the mobile device's database once they have been successfully transmitted to the central database, recovering storage space. This ensures that storage is used temporarily only when necessary for data preservation during transmission failures.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS11349950B1Remotely interacting with database
Publication Date: 2022.05.31 NATIONWIDE MUTUAL INSURANCE CO
  • US11349950B1 patent drawing
  • US11349950B1 patent drawing
  • US11349950B1 patent drawing

AI summary

A process and system that allows a user with a mobile device to interact with a remote database includes wirelessly coupling the mobile device to the database over a wireless network using a username. Based on the username, and in some cases a role associated with the username, the database transmits a set of data records to the mobile device in one or more subsets of data records. The user selects one of the records and provides an update that includes an item of some sort (e.g., a photograph, a note to the record, etc.). However, the user cannot delete anything associated with the record. If the update can be transmitted to the database, then the mobile device transmits the update. However, if the update cannot be transmitted, then the update is stored for a later transmission. Once the update is transmitted, it is deleted from the mobile device.