Data Synchronization Using Operation Flags and Differential Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data synchronization systems face issues with data loss and redundant data accumulation due to network interruptions and inefficient data transmission processes, leading to instability and resource burden in distributed management systems.

Innovation Solution

A data synchronization method that uses operation flags and status flags to determine the completion of data synchronization operations, allowing for selective data transmission and avoiding redundant data storage by only updating the most recent data, thereby enhancing efficiency and preventing data loss.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If complete data is transmitted during synchronization, then data completeness is improved, but network bandwidth consumption increases and transmission time increases

Engineering Contradiction:
Improvedata completenessVSAvoidtransmission time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent applies partial action by transmitting only the necessary portion of data. The server determines whether to transmit complete data or only changed fields based on synchronization status. When data is already synchronized, only the difference portion (changed fields) is transmitted, rather than all data, thus reducing transmission time while maintaining data completeness.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent segments data transmission into different portions based on synchronization state. Data is divided into complete data transmission and differential data transmission (only changed fields). This segmentation allows the system to optimize transmission by sending only what is necessary, reducing overall transmission time while ensuring data completeness is maintained.

Inventive Principle:
Principle #1Segmentation

2Reliability

If all data is synchronized repeatedly, then data consistency is improved, but redundant data accumulation increases and system resources are burdened

Engineering Contradiction:
Improvedata consistencyVSAvoidredundant data volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts and transmits only the changed fields from the complete data set. Instead of synchronizing all data repeatedly, the system identifies and transmits only the portions that have changed since the last synchronization. This extraction approach maintains data consistency while eliminating redundant data transmission and accumulation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs partial synchronization by transmitting only the necessary changed fields rather than complete data sets. This partial action approach ensures data consistency is maintained while significantly reducing the volume of redundant data that would otherwise accumulate in the system.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of information

If data synchronization is performed frequently, then data freshness is improved, but network bandwidth consumption increases and system stability decreases due to interruptions

Engineering Contradiction:
Improvedata freshnessVSAvoidsystem stability
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent implements partial synchronization by transmitting only changed fields rather than complete data sets during each synchronization cycle. This reduces the data volume and time required for each transmission, making the system more resilient to network interruptions while maintaining data freshness through frequent but lightweight synchronization operations.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system enables quick resumption of synchronization after interruptions by using differential data transmission. Since only changed fields are transmitted, the synchronization process can be completed rapidly even if interrupted, allowing the system to skip lengthy retransmissions and maintain stability while ensuring data freshness.

Inventive Principle:
Principle #21Skipping (Rushing through)

4Productivity

If critical fields only are extracted for transmission, then transmission efficiency is improved, but data accuracy decreases due to loss of complete information

Engineering Contradiction:
Improvetransmission efficiencyVSAvoiddata accuracy
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The patent transmits partial data (only changed fields) rather than complete data sets, achieving high transmission efficiency. The system maintains data accuracy by ensuring that the transmitted changed fields contain all necessary information for updating the local data set, making the partial transmission as accurate as complete transmission for the purposes of data synchronization.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8850074B2Data synchronization method
Publication Date: 2014.09.30 DIMERCO EXPRESS TAIWAN CORP
  • US8850074B2 patent drawing
  • US8850074B2 patent drawing
  • US8850074B2 patent drawing

AI summary

The present invention provides a data synchronization method applied to a host and at least a client. First, the host transmits a request for synchronization operation to the client. The client replies at least a piece of connection information to the host. The host judges if the connection information contains operation flags. If not, the host transmits a request for data transmission to the client for driving the client to transmit the corresponding data of the connection information to the host. When the host completes receiving the data, the host stores an operation flag to the connection information and transmits it to the client for overwriting the connection information in the client.