File Synchronization Protocol for Cross-Device Transport Negotiation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file synchronization solutions often fail to accommodate the diverse form factors and capabilities of machines and devices, leading to compatibility issues and inefficient data transfer across different platforms.

Innovation Solution

A synchronization protocol that separates file synchronization from data transport, enabling devices to communicate and negotiate the use of multiple data transport protocols for efficient data transfer, using knowledge metadata to identify and coordinate file data synchronization across various devices and networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a single data transport protocol is used for file synchronization, then the system is simpler to implement, but compatibility across diverse devices and platforms is reduced

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

Solution Approach 1:

The patent segments the file synchronization system into two independent protocol layers: a synchronization protocol layer that manages file state tracking and change detection, and a data transport layer that handles actual file transfer. This segmentation allows each layer to operate independently with its own optimized protocol, enabling multi-protocol support without increasing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The synchronization protocol acts as an intermediary between the file synchronization logic and multiple data transport protocols. It receives synchronization requests, determines which files need to be synchronized, and then selects appropriate transport protocols for data transfer, thereby enabling compatibility across diverse devices without requiring each device to implement all transport protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If file synchronization and data transport are combined in a single protocol, then the protocol implementation is simpler, but flexibility in selecting appropriate transport protocols for different devices is reduced

Engineering Contradiction:
Improveprotocol flexibilityVSAvoidprotocol structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent explicitly separates synchronization operations from data transport operations into distinct protocol layers. The synchronization protocol handles file metadata exchange, change detection, and synchronization state management, while transport protocols handle actual data transfer. This segmentation provides flexibility in protocol selection without increasing implementation complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The synchronization protocol is designed as a universal interface that can work with multiple different data transport protocols. It provides consistent synchronization functionality across diverse platforms while allowing the underlying transport mechanism to vary, thereby achieving multi-functionality without increasing the complexity of the synchronization logic.

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

3Adaptability or versatility

If conventional file synchronization protocols are used, then file synchronization can be achieved, but support for arbitrary device topologies and networks is limited

Engineering Contradiction:
Improvetopology supportVSAvoidsynchronization reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a new dimensional approach by completely separating the synchronization control plane from the data transport plane. This allows the synchronization protocol to operate independently of network topology constraints, as it only needs to exchange metadata and synchronization states, while the transport layer adapts to various network configurations and topologies.

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

Solution Approach 2:

The synchronization protocol serves as an intermediary that abstracts away topology-specific details from the synchronization logic. It manages file state information and coordinates synchronization across devices regardless of network topology, while transport protocols handle the actual data movement adapted to specific network configurations, thereby maintaining reliability across diverse topologies.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If multiple data transport protocols are supported, then compatibility with diverse devices is improved, but protocol negotiation and selection complexity increases

Engineering Contradiction:
Improvedevice compatibilityVSAvoidnegotiation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The synchronization protocol acts as an intermediary that simplifies multi-protocol support by handling protocol selection automatically. It receives synchronization requests, identifies the files that need to be synchronized, and selects appropriate transport protocols based on device capabilities, thereby reducing negotiation complexity for the end user while maintaining broad device compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements self-service protocol selection where the synchronization protocol automatically determines the appropriate transport protocol based on the capabilities of the communicating devices and the characteristics of the files to be synchronized. This eliminates the need for complex manual negotiation while achieving optimal protocol selection for device compatibility.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250330520A1Synchronizing file data between computer systems
Publication Date: 2025.10.23 MICROSOFT TECHNOLOGY LICENSING LLC
  • US20250330520A1 patent drawing
  • US20250330520A1 patent drawing
  • US20250330520A1 patent drawing

AI summary

Non-limiting examples of the present disclosure describe implementation of an exemplary synchronization protocol to identify file data for synchronization as well as negotiate how to achieve data transport for synchronization of the file data. In one example, a request for synchronization of data is received from a processing device. In response to receiving the request, a response is generated. The response may comprise: identification of file data for synchronization, instructions for accessing the file data and instructions indicating a data transport protocol to utilize to obtain the file data. The response may be transmitted to the processing device, for example, to enable the processing device to synchronize file data. Other examples are also described.