File Metadata Preservation During Atomic Save Operations

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current file management systems face challenges in preserving file metadata during atomic save operations, leading to loss of metadata when new files replace old ones, and struggle with ubiquitous access, synchronization, and data backup across multiple devices, especially during collaboration and in case of device failures.

Innovation Solution

A method is introduced to store create, delete, and rename operations in a log, determining atomic save operations, and associating metadata of the old file with the new file, ensuring that globally unique file identifiers and access permissions are transferred, thereby preserving metadata across file versions and devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If atomic save operations replace old files with new files, then file updates are completed, but file metadata is lost

Engineering Contradiction:
Improvefile update completionVSAvoidmetadata loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent creates a copy of the metadata from the old file and applies it to the new file. The metadata copy mechanism preserves file identifiers, permissions, and other attributes during the atomic save operation, ensuring metadata survival while completing the file update.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent performs preliminary metadata extraction and preservation before the atomic save operation completes. By preparing the metadata copy in advance and applying it to the new file, the system ensures metadata is preserved before the old file is fully replaced.

Inventive Principle:
Principle #10Preliminary action

2Loss of information

If file operations are logged and processed, then metadata preservation is achieved, but system complexity increases

Engineering Contradiction:
Improvemetadata preservationVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent introduces a log file as an intermediary structure to track file operations and their associated metadata. This log serves as a mediator between the atomic save operation and the metadata preservation mechanism, organizing the complexity into a manageable intermediate representation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the file operation processing into distinct components: operation logging, atomic save execution, and metadata preservation. By dividing the process into separate manageable steps, the system reduces overall complexity while achieving metadata preservation.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10289692B2Preserving file metadata during atomic save operations
Publication Date: 2019.05.14 GOOGLE LLC
  • US10289692B2 patent drawing
  • US10289692B2 patent drawing
  • US10289692B2 patent drawing

AI summary

A method of preserving file metadata associated with an edited file, performed on a client device, includes storing in a log information denoting a plurality of create, delete, and rename operations on one or more files in a file system, and determining when two or more operations denoted in the log, including an operation involving a first file and another operation involving a second file, comprise an atomic save of a respective file, the first file comprising a first version of the respective file, and the second file comprising a second version of the respective file, the first file and second file each having associated metadata. The method further includes associating a subset of the metadata of the first file with the second file, such that at least one of a globally unique file identifier and file access permissions associated with the first file become associated with the second file.