Selective Cloud Data Synchronization via Priority Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Synchronizing data between a client device and a cloud storage repository can be resource-intensive, requiring significant network bandwidth and potentially slowing down the synchronization process, especially when bandwidth is limited or sporadic, and can frustrate the benefits of offsite storage by duplicating large volumes of data locally.

Innovation Solution

Implementing a method that selectively synchronizes data based on metrics such as priority scores, access timestamps, popularity scores, and relevancy scores, prioritizing the synchronization of frequently used and priority data ahead of other content, using selection criteria to identify and copy the most important files first, and adjusting synchronization settings based on available bandwidth and storage capacity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If all cloud storage content is synchronized to local storage, then data accessibility and speed are improved, but network bandwidth consumption increases and synchronization time extends

Engineering Contradiction:
Improvedata accessibilityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The patent segments the cloud storage content into multiple priority levels (first priority, second priority, third priority) based on file characteristics and access patterns. The synchronization process selectively transfers only high-priority files first, rather than synchronizing all content simultaneously. This segmentation allows the system to improve data accessibility for critical files while reducing overall network bandwidth consumption by deferring or skipping lower-priority content.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements partial synchronization by transferring only a subset of cloud content (specifically, files meeting certain priority criteria) rather than completing full synchronization. The system performs 'enough' synchronization to meet immediate access needs without the excessive action of copying every file, thereby balancing accessibility improvements against bandwidth consumption.

Inventive Principle:
Principle #16Partial or excessive action

2Speed

If large volumes of data are synchronized locally, then data access speed is improved, but local storage requirements increase

Engineering Contradiction:
Improvedata access speedVSAvoidlocal storage volume
Core Design Contradiction:
SpeedVSVolume of stationary object

Solution Approach 1:

The patent divides cloud storage content into priority-based segments and selectively synchronizes only the first priority files to local storage. This segmentation strategy ensures that local storage volume is occupied only by the most critical and frequently accessed data, improving data access speed for essential files while minimizing the total storage volume required on local devices.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different synchronization qualities to different files based on their priority classification. High-priority files receive full local synchronization for fast access, while lower-priority files are either partially synchronized or accessed remotely. This local quality differentiation optimizes the balance between local storage volume and data access speed.

Inventive Principle:
Principle #3Local quality

3Reliability

If complete synchronization is performed, then data consistency is improved, but synchronization time extends

Engineering Contradiction:
Improvedata consistencyVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary filtering and classification of cloud files into priority groups before executing the synchronization transfer. By pre-identifying which files require immediate synchronization (first priority) versus which can be synchronized later (second or third priority), the system establishes a staged synchronization plan that maintains data consistency for critical files while significantly reducing the initial synchronization time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent accepts partial synchronization as sufficient for many use cases, completing only the necessary transfers of high-priority files rather than forcing complete synchronization of all content. This partial action approach maintains adequate data consistency for essential operations while dramatically reducing the time investment required for synchronization.

Inventive Principle:
Principle #16Partial or excessive action

4Ease of operation

If frequently accessed files are prioritized for synchronization, then data accessibility is improved, but selection complexity increases

Engineering Contradiction:
Improvedata accessibilityVSAvoidsynchronization selection logic
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements dynamic priority assignment that adapts based on file characteristics, access patterns, and user behavior. The system automatically adjusts which files receive first priority synchronization status based on real-time or near-real-time metrics, making the synchronization process more responsive to actual user needs while managing selection complexity through automated dynamic rules rather than static manual configuration.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9330106B2Selective synchronization of remotely stored content
Publication Date: 2016.05.03 PROGRESS SOFTWARE CORP
  • US9330106B2 patent drawing
  • US9330106B2 patent drawing
  • US9330106B2 patent drawing

AI summary

Described herein are methods and systems for selectively synchronizing locally stored data with data stored in a cloud storage repository. A client application can synchronize a portion of the locally or remotely stored content by choosing to synchronize data that is frequently used, data that is marked as priority data or data that was modified or otherwise accessed during a predetermined period of time. Other selective synchronization optimizations include predictively synchronizing data or content associated with frequently use or priority data and synchronizing data according to a priority score.