Multi-root namespace architecture for independent device synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud-based storage or synchronization services face challenges in providing granular control and customization to the synchronization process across multiple devices, including client devices and external storage devices, while maintaining separate and controllable access to each device.

Innovation Solution

A multi-root synchronization architecture is introduced, where each user account is associated with multiple root namespaces, each running an independent instance of the synchronization engine. This allows for individualized synchronization behavior and processes for each user device, supporting tailored synchronization for client devices and external storage devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a single-root synchronization system is used, then device complexity is reduced, but synchronization control and customization capability deteriorates

Engineering Contradiction:
Improvesynchronization control and customization capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the synchronization system into multiple independent root namespaces, each with its own synchronization engine instance. This segmentation allows different synchronization behaviors and processes for different devices (client devices vs. external storage devices) while maintaining overall system coordination through the multi-root architecture.

Inventive Principle:
Principle #1Segmentation

2Reliability

If multiple independent synchronization engines are deployed, then synchronization reliability and speed improve, but resource usage and system complexity increase

Engineering Contradiction:
Improvesynchronization reliabilityVSAvoidresource usage
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The multi-root namespace architecture provides a universal framework that can handle different synchronization scenarios (client devices, external storage devices, backup mechanisms) through a common structure. Each root namespace instance can be independently configured and managed, allowing the system to optimize resource usage for each specific synchronization task while maintaining reliability through independent operation.

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

3Reliability

If separate backup mechanisms are synchronized, then data protection capability improves, but system complexity increases

Engineering Contradiction:
Improvedata protection capabilityVSAvoidsynchronization system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a new dimensional organization for backup mechanisms by creating separate root namespaces for different backup devices. This allows backup synchronization to occur in a separate namespace dimension, independent of the main file system namespace, thereby providing data protection capability without adding complexity to the primary synchronization system.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS12306800B2Multi-root content management system
Publication Date: 2025.05.20 DROPBOX INC
  • US12306800B2 patent drawing
  • US12306800B2 patent drawing
  • US12306800B2 patent drawing

AI summary

The present technology is directed to providing a multi-root architecture for managing devices associated with their own root namespaces. The system can include backing up multiple computing devices to a single user account such that the content items from each computing device are stored in their own respective root namespace at the user account. With each user account having multiple root namespaces, the system can identify which root namespace is receiving changes, identify which changes are necessary to synchronize the system, and then communicate those changes to the content management system. This process is facilitated by running a synchronization engine for each root namespace, thereby controlling synchronization for each root namespace. Each synchronization engine is able to retain its own parameters of operation, which provides the ability to tailor synchronization modes on each synchronization engine.