File System Directory Entry Encoding Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file systems face challenges in supporting access to files named with multiple different character encodings, as they often rely on specific encoding standards, making it difficult for clients using different encodings to access files created by others.

Innovation Solution

A file system architecture that uses an indexed data structure, such as a B-tree, to store filenames with encoding tags, allowing conversion and lookup of filenames across various encodings, enabling access by clients using different character encodings by converting and hashing filenames to a standard encoding for efficient matching.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a file system uses a specific character encoding standard for storing filenames, then the storage and retrieval process is simple and efficient, but it cannot support access by clients using different character encodings

Engineering Contradiction:
Improveencoding compatibilityVSAvoiddata structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements nesting by storing multiple encoding representations of the same filename within a single directory entry. Each filename is stored with its corresponding encoding type标识, creating a nested structure where one entry contains multiple encoding variants. This allows the file system to support multiple encodings without requiring separate directory structures for each encoding type.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent introduces an intermediary conversion mechanism that translates filenames from one encoding to another during lookup operations. When a client searches for a filename, the system converts the search query into the encoding used by the stored filename, enabling cross-encoding access without requiring the client to know the actual storage encoding.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a file system stores filenames in multiple different character encodings with separate data structures, then clients using different encodings can access files, but the system complexity and lookup time increase significantly

Engineering Contradiction:
Improvemulti-encoding supportVSAvoidlookup time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-converting and storing filenames in multiple encodings during the file creation process. Instead of converting at lookup time, the system performs the encoding conversions in advance and stores all variants, so that lookup operations can directly compare strings without performing time-consuming conversions during access.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a universal directory entry structure that handles multiple encodings through a unified interface. The directory entry contains encoding-specific fields that can accommodate different character encodings while presenting a consistent API to clients, allowing the same data structure to serve multiple encoding purposes efficiently.

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

3Productivity

If a file system converts all filenames to a standard encoding for storage, then lookup efficiency is improved, but the original encoding information is lost and clients cannot access files in their native encoding

Engineering Contradiction:
Improvelookup efficiencyVSAvoidoriginal encoding information
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent applies local quality by making the encoding representation specific to each filename entry rather than applying a single global encoding to all filenames. Each directory entry contains encoding-specific fields that preserve the original encoding characteristics of that particular filename, allowing the system to maintain both lookup efficiency through standardized processing and encoding fidelity through localized encoding preservation.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8060521B2Systems and methods of directory entry encodings
Publication Date: 2011.11.15 EMC IP HLDG CO LLC
  • US8060521B2 patent drawing
  • US8060521B2 patent drawing
  • US8060521B2 patent drawing

AI summary

In general, the invention relates to supporting multiple different character encodings in the same file system. In one embodiment, a method is provided for filename lookup that supports multiple character encodings. The method comprises storing filename data in a first character encoding into an indexed data structure. The method further comprises receiving filename data in a second encoding. The method also comprises looking up filename data in the indexed data structure using the second encoding.