Encrypted Filename Metadata for Case-Insensitive File Search
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing file systems face inefficiencies in handling filenames, particularly when encryption is involved, leading to increased processing costs and potential data loss due to corrupted hash values, especially in case insensitive (CI) filename handling.
Innovation Solution
An electronic device generates bit information for uppercase and lowercase letters in filenames, encrypts them to create a case insensitive (CI) filename, calculates a hash value, and records metadata including the encrypted CI filename, length, and bit information, enabling efficient search and detection of corrupted hash values without decryption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a filename is encrypted to protect user files, then security is improved, but hash value corruption cannot be detected without decryption
Solution Approach 1:
The patent performs preliminary hashing of the filename before encryption occurs. The original filename is hashed to generate a first hash value, which is then encrypted along with the filename. This preliminary hashing action allows the system to later verify hash integrity without requiring decryption of the filename itself, thus resolving the contradiction between security and corruption detection.
2Adaptability or versatility
If case insensitive filename conversion is performed, then search flexibility is improved, but processing cost increases
Solution Approach 1:
The patent performs case normalization (converting to lowercase) and hashing of the filename before encryption. By performing these transformations in advance, the system stores only the normalized, hashed version in the encrypted metadata. During search operations, the system can directly compare hashed values without performing additional conversion operations, thus maintaining search flexibility while reducing processing costs.
3Productivity
If hash value verification is skipped to save processing resources, then processing speed is improved, but data integrity is compromised
Solution Approach 1:
The patent introduces an intermediary mechanism where the hash value is encrypted together with the filename in the metadata. During verification, the system decrypts and verifies the hash value as an intermediate step before accessing the actual file data. This intermediary hash verification process enables integrity checking without significantly impacting overall processing speed, thus resolving the contradiction between productivity and reliability.
Data Source
AI summary
An electronic device in an example embodiment may include a communication interface configured to receive an original file, a memory, and a processor. The processor may generate bit information corresponding to uppercase and lowercase letters included in a filename of the original file. The processor may generate a case insensitive (CI) filename in which the filename of the original file is expressed by characters of a first type. The processor may encrypt the CI filename and may calculate a first hash value corresponding to the encrypted CI filename. The processor may record filename metadata including at least one of the encrypted CI filename, a length of the encrypted CI filename, the first hash value, and the bit information, in the memory. The processor may search for a target file to be found based on the filename metadata.