Work Unit Data Synchronization for Offline Conflict Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing field data collection systems face challenges with intermittent and unreliable network connectivity, leading to inefficient bandwidth usage and potential data conflicts due to continuous synchronization requirements.

Innovation Solution

Implementing deferred data synchronization, where modifications are made offline and stored in priority queues on client devices, with synchronization occurring at optimal network conditions, using hash functions to identify modified data and conflict resolution rules to manage updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If continuous synchronization is implemented between mobile device and central server, then data consistency is improved, but bandwidth consumption increases significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements periodic synchronization instead of continuous synchronization. The system determines whether synchronization is needed by comparing hash values of local data with server data, and only performs synchronization when necessary. This periodic check approach reduces bandwidth consumption while maintaining data consistency, directly resolving the contradiction between reliable data synchronization and bandwidth usage.

Inventive Principle:
Principle #19Periodic action

2Reliability

If continuous data updating is performed, then data freshness is improved, but network connectivity requirements increase

Engineering Contradiction:
Improvedata freshnessVSAvoidnetwork connectivity adaptability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent performs preliminary hash value comparison before initiating data synchronization. By calculating and comparing hash values locally first, the system can determine whether synchronization is actually needed, avoiding unnecessary network communication. This preliminary action enables the system to maintain data freshness while adapting to intermittent network connectivity conditions.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If all data is synchronized every time, then data completeness is improved, but synchronization time increases

Engineering Contradiction:
Improvedata completenessVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential identification information (hash values) for comparison purposes, rather than transferring all data during synchronization checks. By using hash values as data fingerprints, the system can quickly determine what needs to be synchronized without transmitting complete datasets, thus maintaining data completeness while significantly reducing synchronization time and bandwidth usage.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20260072942A1Deferred synchronization for work unit-related data
Publication Date: 2026.03.12 GUIDEWIRE SOFTWARE INC
  • US20260072942A1 patent drawing
  • US20260072942A1 patent drawing
  • US20260072942A1 patent drawing

AI summary

Deferred data synchronization includes obtaining at least a portion of a copy of a work unit from a system of record, the work unit comprising a plurality of categories, each category comprising a set of one or more elements; while a client device is offline with respect to the system of record, performing an offline action that includes a modification to an element of the copy of the work unit, recording locally the modification to the element of the copy of the work unit, and deferring synchronization of the modification with the system of record; and synchronizing the modification with the system of record, including causing the system of record to detect whether the modification is in conflict with the work unit on the system of record.