Data Synchronization Suspend and Resume Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data synchronization between organizations in cloud computing environments often fails due to transient connection failures, leading to unnecessary resource consumption and data replication when the connection between primary and secondary organizations is unavailable.

Innovation Solution

Implementing a suspend-and-resume mechanism for data synchronization, allowing the primary organization to pause data synchronization during connection outages and resume it when the connection is re-established, thereby conserving resources and preventing unnecessary data replication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data synchronization continues during connection failures, then data replication is maintained, but resource consumption increases and unnecessary data replication occurs

Engineering Contradiction:
Improvedata synchronization reliabilityVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The synchronization process dynamically transitions between active and suspended states based on connection availability. When connection failures are detected, the system automatically suspends data synchronization to conserve resources. When connectivity is restored, the system resumes synchronization from where it left off, ensuring both reliability and resource efficiency.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system continuously monitors connection status and uses this feedback to control the synchronization process. Upon detecting connection failures, the system receives feedback and suspends synchronization accordingly. When connectivity is restored, the feedback triggers resumption of synchronization, creating a closed-loop control mechanism that optimizes resource usage while maintaining data consistency.

Inventive Principle:
Principle #23Feedback

2Productivity

If data synchronization continues during connection outages, then data sharing is maintained, but unnecessary data replication occurs

Engineering Contradiction:
Improvedata sharing efficiencyVSAvoidunnecessary data replication
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The synchronization mechanism dynamically adapts its operation based on connection status. During connection outages, the system transitions to a suspended state, preventing unnecessary data replication attempts. When connectivity is restored, the system resumes synchronized data sharing, ensuring productivity while avoiding redundant information replication.

Inventive Principle:
Principle #15Dynamics

3Reliability

If connection monitoring is implemented, then suspension and resumption can be detected, but system complexity increases

Engineering Contradiction:
Improveconnection availability detectionVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements connection monitoring through feedback mechanisms that continuously assess connection status. This feedback loop provides reliable detection of connection availability without requiring complex additional infrastructure, maintaining system simplicity while ensuring reliable suspension and resumption detection.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10540369B2Org sync suspend and resume data sync
Publication Date: 2020.01.21 SALESFORCE INC
  • US10540369B2 patent drawing
  • US10540369B2 patent drawing
  • US10540369B2 patent drawing

AI summary

Disclosed are some implementations of systems, apparatus, methods and computer program products for temporarily suspending data synchronization between a primary organization and a secondary organization. The primary organization may suspend data synchronization in response to a manual command. Alternatively, the primary organization may suspend data synchronization automatically upon detection of communication failure(s) between the primary organization and the secondary organization.