System Mapping Table Backup for Low-Memory File Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing system backup methods occupy a large amount of storage space in electronic device memory, affecting operational performance.

Innovation Solution

Backup system mapping tables before system file updates, retain original file data, and store incremental data, updating the mapping table to minimize storage requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system file data is fully backed up in the memory, then the system update failure can be avoided, but the storage space in the memory is occupied

Engineering Contradiction:
Improvesystem update reliabilityVSAvoidmemory storage space
Core Design Contradiction:
ReliabilityVSVolume of stationary object

Solution Approach 1:

The patent segments the backup data into two parts: the system mapping table (small size, essential for recovery) and the original system file data (large size, retained in place). Only the mapping table is copied to backup storage, while the actual file data remains in its original location. This segmentation allows the backup mechanism to function with minimal additional storage space.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a copy of the system mapping table (a data structure containing file metadata and location information) rather than copying the actual system file data. This copy is stored in the memory as a backup, while the original large files remain in their primary storage location. The mapping table copy serves as a pointer system that enables recovery without duplicating the entire file set.

Inventive Principle:
Principle #26Copying

2Reliability

If the system file data is retained in the memory during update, then the original system can be restored if update fails, but the operational performance is affected

Engineering Contradiction:
Improvesystem recovery capabilityVSAvoiddevice operational performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent separates the backup functionality into a lightweight mapping table that can coexist with active system files. The mapping table contains only metadata (file names, sizes, locations) rather than the actual file content, allowing it to occupy minimal space and not interfere with system file access and execution performance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system mapping table acts as an intermediary data structure that enables backup and recovery functionality without directly interfering with system file operations. It serves as a reference layer that maps logical file names to physical storage locations, allowing the system to maintain normal operational performance while the mapping table provides the backup mechanism.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12499014B2Method and apparatus for system backup, memory, and electronic device
Publication Date: 2025.12.16 BEIJING XIAOMI MOBILE SOFTWARE CO LTD
  • US12499014B2 patent drawing
  • US12499014B2 patent drawing
  • US12499014B2 patent drawing

AI summary

A method for a system backup, includes: backing up a system mapping table before a system file is updated, wherein the system mapping table includes at least one first storage address, and each first storage address corresponds to an address where first system file data is currently stored in a memory; retaining, in response to that the system file is updated, the first system file data in the memory; and storing updated second system file data in the memory and determining an updated system mapping table.