Multi-Master Sync Infrastructure for Loose Coupling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional synchronization systems are inflexible and inefficient, particularly in multi-master environments with dynamic network topologies and unpredictable connectivity, leading to high server resource burdens and inadequate offline synchronization capabilities.

Innovation Solution

A multi-master synchronization infrastructure using standardized REST-based interfaces enables efficient synchronization across loosely coupled devices, allowing for offline application experiences by caching data locally and minimizing network traffic, with a synchronization layer that handles changes and conflicts independently of data semantics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dedicated master-client synchronization is used, then synchronization reliability is improved, but device complexity and server resource burden increase in dynamic multi-device environments

Engineering Contradiction:
Improvesynchronization reliabilityVSAvoidserver resource burden
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the centralized master-client model into multiple independent master nodes that can each handle synchronization autonomously. Each device becomes a potential master node capable of independent synchronization operations, dividing the server's burden across multiple distributed nodes while maintaining reliability through redundancy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The synchronization system implements universal master node capability where any device can function as a master node for different data sets or time periods. This multi-functionality allows the system to dynamically allocate synchronization responsibilities based on connectivity and resource availability, reducing the burden on any single server while maintaining reliable synchronization.

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

2Ease of manufacture

If static synchronization setup is used, then device configuration is simplified, but adaptability to dynamic network topology and device connectivity deteriorates

Engineering Contradiction:
Improvedevice configuration simplicityVSAvoidadaptability to dynamic connectivity
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The system transitions from static configuration to dynamic topology discovery where master nodes and client nodes can dynamically assume roles based on current network conditions. Devices automatically discover available master nodes and establish synchronization relationships without pre-configuration, enabling seamless adaptation to changing connectivity while maintaining simple device interfaces.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The synchronization system implements self-service through automatic topology discovery and dynamic role assignment. Devices autonomously identify available master nodes, establish connections, and manage their own synchronization relationships without requiring manual configuration or centralized coordination, thereby adapting to dynamic networks while keeping device complexity low.

Inventive Principle:
Principle #25Self-service

3Measurement precision

If custom synchronization models with extensive metadata tracking are used, then synchronization precision is improved, but system complexity and scalability deteriorate

Engineering Contradiction:
Improvesynchronization precisionVSAvoidmetadata tracking complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system changes the fundamental parameters of synchronization by using version identifiers and change tokens instead of extensive metadata tracking. Each data set is associated with simple version parameters that enable precise change detection and synchronization without requiring complex metadata structures, thereby maintaining synchronization precision while reducing system complexity.

Inventive Principle:
Principle #35Parameter changes

4Stability of the object's composition

If centralized master node synchronization is used, then data consistency is improved, but offline synchronization capability and system resilience deteriorate

Engineering Contradiction:
Improvedata consistencyVSAvoidoffline synchronization capability
Core Design Contradiction:
Stability of the object's compositionVSReliability

Solution Approach 1:

The system segments the centralized consistency model into distributed consistency zones where each master node maintains data consistency for its assigned data sets independently. This segmentation enables offline synchronization by allowing multiple independent consistency points, so if one master node is unavailable, other nodes continue to maintain consistency for their respective data, thereby improving both data consistency and offline capability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9135321B2Synchronization infrastructure for networked devices, applications and services in a loosely coupled multi-master synchronization environment
Publication Date: 2015.09.15 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9135321B2 patent drawing
  • US9135321B2 patent drawing
  • US9135321B2 patent drawing

AI summary

The subject disclosure relates to an efficient multi-master synchronization infrastructure is provided enabling loosely coupled networked client and server devices, applications and services to efficiently convey and receive synchronization knowledge across interconnecting network(s). A set of synchronization methods and standardized interfaces are also provided that enable rich offline application experiences and collaboration among devices, applications and services predicated on the efficient synchronization infrastructure.