File Homing Configuration for Cloud Sync

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for synchronizing files across multiple cloud storage servers lack flexibility and robustness, requiring costly maintenance as they rely on folder structures and static configuration lists, which become cumbersome when files are moved or copied.

Innovation Solution

Embedding homing configurations within files themselves, allowing them to determine the appropriate synchronization server and connector, enabling seamless synchronization regardless of file location, and encrypting configurations for security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If files are grouped into different folders for different synchronization servers, then file synchronization can be organized, but the system becomes complex and maintenance becomes costly when files are moved or copied

Engineering Contradiction:
ImproveflexibilityVSAvoidmaintenance complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent embeds homing configuration data within individual files rather than relying on folder-level configurations. This segmentation allows each file to independently specify its synchronization server, enabling files to be moved or copied without requiring reconfiguration of folder structures or maintenance of static lists.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each file contains its own homing configuration data that identifies which synchronization server it should be synchronized with. This self-service approach eliminates the need for external configuration management systems to track and update synchronization settings when files are moved or copied, significantly reducing maintenance complexity.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If a static list of files is maintained for synchronization, then configuration can be stored centrally, but the system lacks flexibility when files are moved or copied to different locations

Engineering Contradiction:
ImproveflexibilityVSAvoidrobustness
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

Instead of maintaining a centralized static list, the patent segments the configuration data and embeds it within each individual file. This allows files to be accessed and synchronized independently of their location in the file system, providing flexibility when files are moved or copied while maintaining reliable synchronization through the embedded configuration data.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If homing configuration is embedded within each file, then files can be synchronized independently regardless of location, but security risks increase due to exposed configuration data

Engineering Contradiction:
ImproveflexibilityVSAvoidsecurity risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies different quality characteristics to different parts of the system: homing configuration data is embedded in plain text within files for ease of access and flexibility, while sensitive information within that configuration is encrypted using public key infrastructure. This local quality approach allows the system to simultaneously achieve flexibility through embedded configurations and security through selective encryption of sensitive data.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9141636B2Homing data
Publication Date: 2015.09.22 IVANTI US LLC
  • US9141636B2 patent drawing
  • US9141636B2 patent drawing
  • US9141636B2 patent drawing

AI summary

Systems and methods are described for homing data. A computerized method of homing data includes embedding a first homing configuration within a first file on a host, intercepting an access attempt to the first file by the host, retrieving the first homing configuration embedded within the first file, determining a first data homing connector based on the first homing configuration, and synchronizing the first file through the first data homing connector with a first synchronization server based on the first homing configuration.