Database Mapping for Faster Cross-Device Data Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data synchronization methods involve piece-by-piece data transfer and format conversion, leading to low synchronization speed and efficiency.

Innovation Solution

Implement database-level data synchronization by mapping databases as a whole, eliminating the need for format conversion and enabling simultaneous synchronization of data across devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is synchronized piece by piece with format conversion, then data compatibility is improved, but data synchronization speed deteriorates

Engineering Contradiction:
Improvedata compatibilityVSAvoiddata synchronization speed
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The patent segments the data synchronization process into two distinct phases: (1) database structure mapping at the schema level to establish compatibility rules, and (2) bulk data transfer at the storage level to achieve high-speed synchronization. This segmentation allows format conversion to be performed once at the structure level rather than repeatedly during data transfer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a mapping database as an intermediary component that stores the correspondence relationships between different database schemas. This mapping database acts as a mediator that translates data formats during synchronization, eliminating the need for real-time format conversion and enabling direct high-speed data transfer between devices with different database structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If data format conversion is performed during read/write process, then data compatibility between devices is improved, but time consumption increases

Engineering Contradiction:
Improvedata compatibilityVSAvoidtime consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs format conversion preparation in advance by establishing database structure mappings before actual data synchronization occurs. The mapping relationships between different database schemas are pre-defined and stored, so that during data synchronization, no real-time format conversion is needed, thus eliminating time consumption associated with format transformation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a mapping database that copies and stores the structural correspondence relationships between different database schemas. Instead of performing complex format conversion during data transfer, the system uses this pre-created mapping copy to directly guide high-speed data synchronization, replacing time-consuming conversion operations with efficient lookup and transfer operations.

Inventive Principle:
Principle #26Copying

3Speed

If database-level mapping is implemented, then data synchronization speed is improved, but system complexity increases

Engineering Contradiction:
Improvedata synchronization speedVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent extracts the format conversion functionality from the data synchronization process and places it in a separate mapping database. This extraction allows the main synchronization engine to focus solely on high-speed data transfer while the mapping database handles format compatibility independently, reducing the complexity of the core synchronization system while maintaining data compatibility.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The mapping database serves multiple functions: it stores structure correspondence relationships, guides data synchronization processes, and enables format translation between different devices. This multi-functionality consolidates what would otherwise require separate components, achieving database-level mapping capability without proportionally increasing system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12524436B2Data transmission method, electronic device, and computer readable storage medium
Publication Date: 2026.01.13 HUAWEI TECH CO LTD
  • US12524436B2 patent drawing
  • US12524436B2 patent drawing
  • US12524436B2 patent drawing

AI summary

A method includes: A second electronic device receives a first event from a first electronic device, where the first event includes first database version information; creates a first empty mapping database of a first source database based on the first database version information, where the first source database is a local database of the second electronic device; virtualizes the first source database and the first empty mapping database to obtain a first virtual database; performs data mapping in the first virtual database to map data in the first source database to the first empty mapping database, to obtain a first database in which data mapping is completed; obtains a first mapping database based on the first database; and sends the first mapping database to the first electronic device.