Intelligent Resource Synchronization via Activity-Based Prioritization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data synchronization techniques are inefficient, particularly when dealing with large amounts of data and devices with limited memory capacity, as they often require manual user intervention or rule-based systems that can be cumbersome and fail to automatically prioritize data importance.

Innovation Solution

A system that determines access information, estimates future use, and synchronizes resources based on user desires, using a formula to calculate the importance of data files, ensuring efficient bandwidth use and automatic prioritization of data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If complete on-line backup of user's data is performed, then data availability on all devices is improved, but synchronization time becomes excessively long (weeks)

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

Solution Approach 1:

The patent segments the data synchronization process by dividing files into different categories (important, less important, not important) based on activity analysis. This allows selective synchronization of only necessary files first, rather than syncing all files completely, thus reducing synchronization time while maintaining data availability for critical files.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements partial action by performing incomplete or incremental backups initially, focusing on copying only the most important files based on activity weights. This partial synchronization provides immediate data availability for critical files without requiring weeks for complete backup, and can be followed by incremental updates.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If all user data is copied to all devices, then data accessibility is improved, but device storage capacity is exceeded on devices with limited memory

Engineering Contradiction:
Improvedata accessibilityVSAvoiddata volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by making different parts of the data set have different synchronization priorities across different devices. Important files (high activity weight) are synchronized to all devices, while less important files are selectively synchronized based on device storage capacity and usage patterns, allowing data accessibility for critical files without exceeding device storage limits.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements partial action by copying only a subset of files (those with highest activity weights) to devices with limited storage capacity, rather than attempting to copy all user data. This provides adequate data accessibility for essential files while respecting device storage constraints.

Inventive Principle:
Principle #16Partial or excessive action

3Ease of operation

If manual rule-based system is used for data copying, then user control over data selection is improved, but system complexity and user burden increase

Engineering Contradiction:
Improveuser controlVSAvoidrule management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements self-service by automatically analyzing file access patterns and activity weights to determine which files should be synchronized to which devices, eliminating the need for users to manually create and maintain complex synchronization rules. The system serves itself by making intelligent decisions based on observed usage patterns, thus reducing user burden while maintaining effective control.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent uses feedback mechanisms by continuously monitoring file access patterns and updating activity weights based on actual usage. This automated feedback loop allows the system to adaptively determine synchronization priorities without requiring manual user intervention, simplifying operation while maintaining effective data selection based on actual needs.

Inventive Principle:
Principle #23Feedback

4Extent of automation

If rule-based synchronization is implemented, then data transfer automation is improved, but new files created without rules are not transferred

Engineering Contradiction:
Improvedata transfer automationVSAvoidhandling of new files
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by pre-establishing activity weight parameters and synchronization criteria that automatically apply to all files, including new files created in the future. When new files are created, they inherit the activity weight system and are automatically evaluated for synchronization based on their initial access patterns and predefined criteria, ensuring they are transferred without requiring separate rule creation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements universality by creating a general-purpose activity-based synchronization system that applies to all files regardless of when they were created or what type they are. The activity weight mechanism serves multiple functions: it prioritizes existing files, automatically handles new files, and adapts to changing usage patterns, making the system versatile without requiring file-specific rules.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8290906B1Intelligent resource synchronization
Publication Date: 2012.10.16 EMC IP HLDG CO LLC
  • US8290906B1 patent drawing
  • US8290906B1 patent drawing
  • US8290906B1 patent drawing

AI summary

Synchronizing resources shared among a plurality of devices includes determining access information about each of the resources, determining activity for each of the resources on at least a subset of the devices based on the access information, estimating future use of the devices, providing an estimate of a desire to have particular resources on particular devices according to the activity and future use, and synchronizing resources according to the estimate of a desire to have particular resources on particular devices. The resources may be data files. Access information may include information about when the resources were read and/or may include information about when the resources were renamed, created, and modified. Estimating a desire to have particular resources on particular devices may take into account a user's desire to maintain backup files and/or maintain certain types of files on certain devices.