Device Resync Engine for Distributed Cloud State Synchronization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Cloud-based distributed systems often operate independently, leading to synchronization issues between two systems, resulting in user failures and system instability due to independent failure rates and maintenance windows, which traditional methods struggle to address effectively.

Innovation Solution

A convergence mechanism, referred to as a device resync engine, is implemented to synchronize device states across distributed systems by using Application Programming Interfaces (APIs) to provide active feedback on user actions, ensuring all devices are in sync through bulk device de-registration and error handling, maintaining low compute expenses and efficient processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional synchronization methods are used with additional systems, then device state synchronization is achieved, but system complexity and compute expenses increase

Engineering Contradiction:

Improvedevice state synchronizationVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a synchronization system that acts as an intermediary between distributed cloud-based systems. This mediator automatically detects and resolves device state discrepancies by comparing device lists across systems and performing bulk de-registration operations, thereby achieving reliable synchronization without requiring complex manual intervention or additional infrastructure.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The synchronization system employs self-service mechanisms where the system automatically monitors its own state consistency, detects synchronization issues, and resolves them through automated bulk device de-registration operations. This self-correcting approach maintains reliability while minimizing the need for external management complexity.

Inventive Principle:

Principle #25Self-service

2Adaptability or versatility

If independent distributed systems operate autonomously, then system independence and maintenance flexibility are improved, but device state synchronization deteriorates

Engineering Contradiction:

Improvesystem independenceVSAvoiddevice state synchronization

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the synchronization system continuously monitors device states across independent distributed systems. When discrepancies are detected (devices present in one system but not another), the system automatically responds by performing bulk de-registration operations to restore consistency, thereby maintaining synchronization reliability while preserving system independence.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system performs preliminary synchronization actions by proactively comparing device lists across distributed systems and resolving discrepancies before they cause user failures. This preventive approach maintains device state consistency without requiring systems to lose their operational independence.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If bulk device de-registration is performed frequently to maintain synchronization, then device state consistency is improved, but compute expenses and processing overhead increase

Engineering Contradiction:

Improvedevice state consistencyVSAvoidcompute expenses

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements periodic synchronization operations where bulk device de-registration is performed only when discrepancies are detected between distributed systems. This event-driven periodic approach maintains device state consistency by syncing only when necessary, thereby avoiding continuous compute overhead while ensuring reliability.

Inventive Principle:

Principle #19Periodic action

4Ease of operation

If device lists are kept identical across systems, then user enrollment and management experience are improved, but system stability deteriorates due to independent failure rates

Engineering Contradiction:

Improveuser enrollment experienceVSAvoidsystem stability

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent extracts the synchronization function into a separate, dedicated mechanism that operates independently from the core distributed systems. This extracted synchronization layer handles device list consistency by performing selective bulk de-registration operations, thereby maintaining user enrollment experience without forcing the core systems to sacrifice their operational independence and stability.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS12021690B2Systems and methods for synchronizing device states across a plurality of distributed systems

Publication Date: 2024.06.25 ZSCALER INC

AI summary

The present disclosure relates to systems and methods for synchronizing device states across two distributed systems. Various embodiments include a convergence mechanism also referred to as a device resync engine. The basis of the present system and methods is that any and every operation done between the two distributed systems, via Application Programming Interfaces (API's), pushes the system towards re-synchronization. This is achieved by providing an active feedback of the user's device state on every user action. For example, a user performs an authentication on one device; the two systems complete the authentication and additionally ensure all states of all devices owned by the user are in sync. By performing these small corrections for every user, the present systems and methods are able to re-converge into a synchronized state while keeping compute expanses low and process efficient.