GUID Compression for File Synchronization via Index Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

File transfer and synchronization protocols, such as MS-FSSHTTP, face significant overhead due to the use of large identifiers for tracking and referencing objects within files, leading to increased memory consumption and inefficiencies in data management.

Innovation Solution

Implementing a method where a globally unique identifier (GUID) component is mapped to a range of indices, allowing objects to use shorter unique indices instead of the full-length GUID, reducing memory usage and improving data synchronization efficiency by reusing indices and generating new GUIDs as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If full-length GUID identifiers are used to track and reference objects, then object identification reliability is improved, but memory consumption and data overhead increase significantly

Engineering Contradiction:
Improveobject identification reliabilityVSAvoidmemory consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent segments the GUID identifier into two components: a GUID component for global uniqueness and an integer component for change tracking. It further segments the GUID component by mapping it to a range of indices, allowing only the necessary portion of the GUID to be stored in each identifier while maintaining uniqueness through the combination of index and integer components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the GUID component from the full extended identifier and separates it from the integer component. By mapping the GUID component to indices and storing only the necessary identifier portions in objects, it reduces memory consumption while maintaining the ability to reliably identify and track objects through the combination of index and integer components.

Inventive Principle:
Principle #2Taking out (Extraction)

2Measurement precision

If large identifiers are used to ensure unique tracking of changes, then synchronization accuracy is improved, but processing efficiency and data manipulation performance deteriorate

Engineering Contradiction:
Improvesynchronization accuracyVSAvoiddata manipulation efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent segments the identifier into GUID component and integer component, where the integer component handles change tracking and the GUID component handles unique identification. By mapping the GUID component to indices, it reduces the size of identifiers used in data manipulation operations while maintaining synchronization accuracy through the combined identifier structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of identifier size by mapping full GUIDs to compressed indices. This parameter change reduces the amount of data that needs to be processed during synchronization operations while maintaining the ability to accurately track and synchronize changes through the extended identifier structure.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8744999B2Identifier compression for file synchronization via soap over HTTP
Publication Date: 2014.06.03 ZHIGU HLDG
  • US8744999B2 patent drawing
  • US8744999B2 patent drawing
  • US8744999B2 patent drawing

AI summary

As changes are made to a document, each change may be assigned an extended identifier comprising a globally unique identifier (GUID) component and an integer component. Upon determining that the same GUID component is used in identifiers for multiple changes, the GUID component may be mapped to a range of indices. Each index of the range of indices may then be used to represent the same GUID component in each extended identifier.