File Change Tracking Database for Mobile Sync

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems lack efficient file change tracking support for non-volatile memory, particularly in mobile devices, which hinders synchronization across multiple file systems and devices.

Innovation Solution

A file change tracking database table created in non-volatile memory that tracks file changes and modifications, enabling synchronization across multiple file systems and devices by using a unique identification system, logging file modifications, and integrating with the operating system for notifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If file change tracking is implemented in non-volatile memory, then file synchronization capability is improved, but device complexity increases

Engineering Contradiction:
Improvefile synchronization capabilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the file change tracking function by creating a dedicated database table structure with specific columns (file path, modification time, synchronization status) to manage file tracking information separately from the main file system operations. This segmentation allows the tracking mechanism to be implemented in non-volatile memory without complicating the entire device architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of a file change tracking database that mediates between file system operations and synchronization processes. This intermediary structure stores modification information and enables efficient synchronization decisions without requiring complex real-time monitoring across all file systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If file change tracking database table is created in non-volatile memory, then data persistence is improved, but storage space requirement increases

Engineering Contradiction:
Improvedata persistenceVSAvoidstorage space requirement
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system applies local quality by creating a specialized database table structure with optimized columns (file path, modification time, synchronization status) that are specifically tailored for tracking file changes. This localized approach ensures that only the necessary information is stored in non-volatile memory, minimizing storage space requirements while maintaining data persistence for synchronization purposes.

Inventive Principle:
Principle #3Local quality

3Measurement precision

If file modification logging is implemented, then synchronization accuracy is improved, but processing time increases

Engineering Contradiction:
Improvesynchronization accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-creating the file change tracking database table structure with appropriate columns before file synchronization operations begin. This pre-prepared structure enables efficient querying and processing during synchronization, reducing processing time while maintaining high accuracy through comprehensive file modification logging.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7657574B2Persistent storage file change tracking
Publication Date: 2010.02.02 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7657574B2 patent drawing
  • US7657574B2 patent drawing
  • US7657574B2 patent drawing

AI summary

Systems and methodologies that facilitate synchronization of a mobile device with a source, via employing a file change tracking database table created in non-volatile memory to designate files for synchronization. The subject invention includes a file modification logger that detects and track changes to files across multiple file systems. The file change tracking database table has a plurality of columns such as: a unique identification column that identifies a file, a file name, previous time the file was changed, and previous time the file was synchronized with a particular machine. A list of files that have changed between a current time and an earlier time can be designated for synchronization, by evaluating when was the file last changed and/or synchronized with a source device (e.g., a desktop, or a lap top.)