Driving Recorder FAT32 Storage Using Uniform Hidden Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional driving recorders using SD cards with FAT32 file allocation suffer from fragmentation due to non-sequential storage of new data, reducing reading and writing efficiency.

Innovation Solution

A method for managing driving record files involves formatting the storage medium with hidden files of uniform size, sequential data arrangement, and directory entries of uniform size, along with error detection and repair procedures to maintain contiguous data storage and prevent fragmentation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If FAT32 file allocation is used on SD card, then storage capacity is utilized, but data becomes scattered in non-sequential manner causing fragmentation

Engineering Contradiction:
Improvestorage capacity utilizationVSAvoiddata sequential arrangement
Core Design Contradiction:
Quantity of substanceVSStability of the object's composition

Solution Approach 1:

The system performs preliminary actions by creating a directory table with pre-defined uniform directory entries before storing actual data. Each directory entry reserves a fixed size and structure, ensuring that data is allocated in contiguous blocks from the beginning, preventing future fragmentation while maintaining storage capacity utilization.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If old files are deleted to make space for new data, then storage space is freed, but reading and writing efficiency decreases due to fragmentation

Engineering Contradiction:
Improveavailable storage spaceVSAvoidreading and writing efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The system changes the parameter of directory entry uniformity and data allocation strategy. By maintaining fixed-size directory entries and allocating data in sequential contiguous blocks, the system ensures that even as files are deleted and new ones created, the data remains organized sequentially, preserving reading and writing efficiency while providing available storage space.

Inventive Principle:
Principle #35Parameter changes

3Stability of the object's composition

If uniform directory entries are created for all files, then data storage becomes contiguous, but error detection and repair complexity increases

Engineering Contradiction:
Improvecontiguous data storageVSAvoiderror detection and repair mechanism
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The system applies homogeneity by creating uniform directory entries for all files with identical structure, size, and format. This standardized approach simplifies error detection and repair mechanisms because the system only needs to handle one type of entry structure, making the complexity manageable while ensuring contiguous data storage through uniform allocation.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS20250328490A1Method for managing driving record files
Publication Date: 2025.10.23 MITAC DIGITAL TECH CORP
  • US20250328490A1 patent drawing
  • US20250328490A1 patent drawing

AI summary

A method for managing driving record files is adapted for a driving recorder that includes a processor and a storage medium supporting FAT32. The method is implemented by the processor and includes: performing a formatting process on the storage medium by generating multiple files as hidden files with uniform file size in a directory, where each file is named with a file name according to a naming rule and stores multiple data pieces that are successively arranged in a sequential order, and generating multiple directory entries respectively for the files, where the directory entries have a uniform size and are in a directory table that corresponds to the directory; when a first-type error has occurred in the directory table, performing a first repairing procedure for repairing the first-type error; and when a second-type error has occurred in the directory table, performing a second repairing procedure for repairing the second-type error.