Bijective GUID Transformation for Database Storage Compression

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional database compression methods, such as dictionary compression, are inefficient for globally unique identifiers (GUIDs) as they require significant storage for mapping information, leading to increased memory consumption, especially in in-memory databases where GUIDs are large and rarely duplicated.

Innovation Solution

A bijective transformation function is used to convert GUIDs into smaller, locally unique reduced identifiers, eliminating the need for a mapping table and reducing storage requirements by storing only the transformation function, which can regenerate the GUID if needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If dictionary compression is used to compress GUIDs, then storage space is reduced, but mapping information requires additional memory consumption

Engineering Contradiction:
Improvestorage spaceVSAvoidmapping information storage
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent extracts and removes the need for mapping tables by using a deterministic hash function. The GUID itself is transformed directly into a compressed form through the hash function, eliminating the separate mapping structure that dictionary compression requires. This is achieved by applying a hash function that maps the large GUID space to a smaller compressed space without requiring external mapping storage.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a deterministic copy of the GUID through hashing. Instead of storing original GUIDs and creating separate mapping tables, the system generates a compressed copy via hash function that can be regenerated deterministically from the original GUID, eliminating the need for persistent mapping storage while preserving the compression benefit.

Inventive Principle:
Principle #26Copying

2Reliability

If GUIDs are stored in their original form, then uniqueness is maintained, but storage occupancy is significant

Engineering Contradiction:
ImproveuniquenessVSAvoidstorage occupancy
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent changes the parameter representation of GUIDs by applying a hash function that transforms the 16-byte GUID into a smaller compressed form. This parameter transformation maintains the uniqueness property through the deterministic nature of the hash function, allowing the same GUID to always produce the same compressed value while reducing storage requirements from 16 bytes to a smaller size.

Inventive Principle:
Principle #35Parameter changes

3Speed

If in-memory database is used for fast access, then retrieval speed is improved, but memory consumption is high

Engineering Contradiction:
Improveretrieval speedVSAvoidmemory consumption
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent applies parameter transformation through hashing to compress GUIDs stored in memory. By transforming the 16-byte GUID into a smaller compressed representation using a deterministic hash function, the system reduces the memory footprint of in-memory database entries while maintaining fast access speeds, as the compressed form can be processed and compared just as efficiently as the original.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11086839B2Bijective transformation for compression of GUID
Publication Date: 2021.08.10 SAP SE
  • US11086839B2 patent drawing
  • US11086839B2 patent drawing
  • US11086839B2 patent drawing

AI summary

Provided is a method and system for transforming a GUID of a database entry into a reduced identifier. The transformation may be performed by a bijective function. In one example, the method may include one or more of receiving a database entry which includes a global unique identifier (GUID) which uniquely identifies the database entry, identifying a transformation function associated with the database entry, transforming the GUID into a reduced identifier based on the transformation function wherein the reduced identifier has a reduced size with respect to a size of the GUID, and storing the database entry based on the reduced identifier.