Stub Folder Data Synchronization Scope Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data synchronization techniques are burdensome and inconvenient, particularly when dealing with large numbers of files and folders, as they require users to manually select and manage synchronization settings across multiple devices, leading to time-, bandwidth-, and capacity-consuming automatic synchronization of all data.

Innovation Solution

The method involves using stub folders and files to represent remotely stored data on a client device, allowing users to selectively synchronize specific folders and files in real-time through a user-friendly interface, without transferring the actual content, thus enabling seamless and specific control over data synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If automatic synchronization of all files and folders is implemented, then data consistency across devices is improved, but bandwidth consumption and storage capacity usage increase significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments the data synchronization process by introducing stub folders that represent remote folders locally. Instead of synchronizing entire folder hierarchies, only selected stub folders are synchronized, allowing users to choose specific portions of data to sync. This segmentation resolves the contradiction by maintaining data consistency for selected items while avoiding bandwidth consumption for unsynchronized portions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by creating local representations (stubs) of remote folders that have different synchronization properties. Each stub folder can be independently configured to sync or not sync, allowing different parts of the file system to have different synchronization qualities. This enables selective synchronization that maintains consistency where needed while conserving bandwidth elsewhere.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If all sub-folders and sub-sub-folders are synchronized when a parent folder is selected, then complete data availability is improved, but storage capacity consumption increases

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage capacity
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts the folder hierarchy structure from the actual file content. Stub folders represent the hierarchical structure locally without containing the actual file data, unless explicitly synchronized. This extraction allows users to navigate and select specific folders for synchronization without requiring all sub-folders to be present locally, resolving the contradiction between data availability and storage capacity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the folder hierarchy into synchronizable units at any level. Users can select individual sub-folders or sub-sub-folders within a parent folder without automatically syncing the entire hierarchy. This segmentation allows selective data availability while minimizing storage capacity usage by only syncing what is explicitly needed.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If manual selection of folders through menu navigation is required, then synchronization scope control is improved, but user operation complexity increases

Engineering Contradiction:
Improvesynchronization scope controlVSAvoiduser operation complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements self-service by allowing users to directly interact with stub folders in the file system interface. Instead of requiring menu navigation, users simply drag and drop stub folders or use context menus on the folders themselves to control synchronization. This self-service approach maintains precise synchronization scope control while dramatically reducing operational complexity by using familiar file system interactions.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces stub folders as intermediaries between the local file system and remote cloud storage. These stubs act as mediators that users can manipulate directly in the file system interface, translating simple user actions into complex synchronization operations. This intermediary mechanism provides both precise control and ease of operation by hiding the complexity of synchronization management behind simple folder interactions.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If complete folder contents are synchronized, then data access reliability is improved, but synchronization time increases

Engineering Contradiction:
Improvedata access reliabilityVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial action by synchronizing only the portions of folders that users explicitly need, rather than complete folder contents. Stub folders enable users to select specific sub-folders or files for synchronization, performing exactly the amount of synchronization needed without excess. This resolves the contradiction by maintaining data access reliability for selected items while minimizing synchronization time through selective syncing.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9282169B1Real-time user interaction-based alterations to the scope of data synchronization between client and remote devices
Publication Date: 2016.03.08 OXYGEN CLOUD
  • US9282169B1 patent drawing
  • US9282169B1 patent drawing
  • US9282169B1 patent drawing

AI summary

Methods, apparatus and systems for altering a scope of data synchronization are disclosed. The scope of data synchronization is altered in real-time via user interactions with the data. In one embodiment, a client device may include folder stubs that reference folders of information stored at a remote server. In response to a user selecting the folder stub, additional folder and/or file stubs provided within the folder are acquired by the client device from the remote server, and a scope of data synchronization is expanded to include the path to the folder referenced by the folder stub. The scope of data synchronization may also be contracted. In response to a user commanding the client device to de-synchronize a synchronized folder, the scope of synchronization may be contracted to exclude the folder and any sub-folders.