Cross-Synchronization Component for Multi-Client Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In client-server systems, synchronizing data between multiple client devices and servers can be complicated due to interference, speed differences, and connectivity issues, leading to inconsistencies and inefficiencies, especially when different synchronization techniques are used across various client-server systems.

Innovation Solution

Implementing a cross-synchronization technique within client devices that utilizes a cross-synchronization component to synchronize data between multiple client databases and devices, maintaining consistency through a consistency group item, which propagates changes efficiently without disrupting existing synchronization operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple independent synchronization techniques are used between client devices and servers, then data can be synchronized across different client-server systems, but synchronization operations may interfere with each other and cause inconsistencies

Engineering Contradiction:
Improveability to synchronize across multiple client-server systemsVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a consistency group as an intermediary mechanism that coordinates synchronization operations across multiple client-server systems. The consistency group maintains state information about data items and manages the synchronization process, preventing interference between independent synchronization techniques while ensuring data consistency across all systems involved.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple synchronization operations are performed simultaneously, then data can be updated across multiple devices, but one synchronization operation may be slower than another and cause delays

Engineering Contradiction:
Improvesynchronization speedVSAvoidsynchronization delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The consistency group performs preliminary actions by pre-establishing coordination protocols and state tracking mechanisms before synchronization operations begin. This allows multiple synchronization operations to proceed in a coordinated manner, preventing delays caused by sequential processing while maintaining productivity through efficient parallel execution.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If independent synchronization techniques are implemented for each client database, then each database can be synchronized separately, but the overall system complexity increases

Engineering Contradiction:
Improveindependent database synchronizationVSAvoidsynchronization system complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The consistency group serves as a universal coordination mechanism that handles synchronization for multiple client databases simultaneously. Instead of implementing separate complex synchronization systems for each database, the consistency group provides a multi-functional framework that manages all databases through a unified approach, reducing overall system complexity while maintaining ease of operation.

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

Data Source

PatentEP2130128B1Techniques to cross-synchronize data
Publication Date: 2019.10.23 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP2130128B1 patent drawingFigure 1
  • EP2130128B1 patent drawingFigure 2
  • EP2130128B1 patent drawingFigure 3

AI summary

Techniques to cross-synchronize data are described. An apparatus may comprise a cross-synchronization component to synchronize multiple data items for different application programs between multiple client devices synchronized using multiple synchronization circuits. The cross-synchronization component may determine whether changes to the multiple data items made at a first client device are propagated to a second client device using consistency information maintained by a consistency group item for a consistency group including the data items. Other embodiments are described and claimed.