Hierarchical File System Nodes with Unique Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing file systems face limitations such as restricted maximum size, file size, and type of data that can be stored, along with limited cross-platform compatibility and resource efficiency, particularly on devices with limited RAM.
Innovation Solution
A computer-implemented method for constructing a file system based on a hierarchy of nodes using a unique identifier for each node, allowing direct access and search without additional layers, enabling flexible naming conventions and minimal resource usage through a doubly linked list structure and ASN.1 header encoding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If traditional file systems (NTFS, FAT32, extensible file systems) are used, then file system functionality is provided, but maximum file system size, file size, and number of elements are limited
Solution Approach 1:
The file system is divided into hierarchical nodes (root node, intermediate nodes, leaf nodes), each representing a manageable unit. This segmentation allows the file system to scale indefinitely by adding more nodes without encountering traditional file system size limitations. Each node can independently store metadata and data, enabling the system to handle arbitrarily large file systems and numbers of elements.
Solution Approach 2:
The patent transitions from traditional flat or single-layer file system structures to a multi-dimensional hierarchical tree structure. This dimensional change allows the file system to organize data in multiple levels (root → intermediate → leaf nodes), effectively increasing the capacity to store and manage large numbers of files and directories without hitting size constraints of conventional systems.
2Reliability
If traditional file systems with comprehensive headers are used, then file metadata is stored, but memory usage increases particularly on devices with limited RAM
Solution Approach 1:
The patent extracts the header information from each node, allowing selective storage and processing. Not all nodes require full headers - leaf nodes and intermediate nodes can have simplified or empty headers depending on their function. This extraction principle reduces the amount of metadata that needs to be loaded into memory, particularly benefiting devices with limited RAM while maintaining necessary file system reliability.
Solution Approach 2:
Different node types have different header requirements based on their local quality and function. Root nodes may have comprehensive headers, intermediate nodes have selective headers, and leaf nodes may have minimal or empty headers. This local quality approach ensures that memory is used efficiently by storing only the necessary metadata for each node type, reducing overall memory consumption while maintaining file system reliability.
3Speed
If unique identifiers are used for direct component access, then access speed improves, but system complexity increases
Solution Approach 1:
The patent merges the unique identifier system with the hierarchical node structure. Each node in the hierarchy is identified by a unique identifier, combining the benefits of hierarchical organization with direct access capabilities. This merging allows the system to maintain a relatively simple hierarchical structure while enabling fast direct access through unique identifiers, without significantly increasing overall system complexity.
Solution Approach 2:
The unique identifier serves multiple functions simultaneously: it identifies nodes in the hierarchical structure, enables direct access to components, and can be used for searching and indexing. This multi-functionality reduces the need for separate access mechanisms, thereby maintaining system simplicity while achieving fast component access speeds.
4Stability of the object's composition
If strict naming conventions are enforced, then file organization is maintained, but flexibility in file and directory naming is restricted
Solution Approach 1:
The patent implements dynamic naming conventions where the rules for file and directory names can vary based on the context and node type. Rather than enforcing strict static naming rules throughout the entire file system, the system allows flexibility in naming at different hierarchical levels and for different node types, maintaining organizational stability while adapting to diverse naming needs.
Solution Approach 2:
The system changes the parameters of naming conventions based on the specific requirements of different nodes and contexts. Naming rules are not fixed but can be adjusted according to the type of node, its position in the hierarchy, and its intended use. This parameter change approach maintains file organization stability while providing versatility in naming flexibility.
Data Source
AI summary
This invention relates to computer engineering and operating system components, in particular, it discloses a new method of building a hierarchal file system, which provides new functionality and flexibility, including: unlimited maximum possible file system size (number of elements), unlimited size of a single element, unlimited types of data, that can be represented as a file. In addition, the disclosed file system allows for user-defined types of data and can be used as a registry for OS system components, saving space important for resource-restricted embedded systems. The minimum file system size is 2 Bytes only. File system supports empty or non-unique files naming and natively provides built-in security using specification-based nodes header encoding.This result is achieved by using file systems nodes metadata comprising: the unique identifier (ID), an ASN.1 header with PER encoding, and a doubly linked list of logical blocks of its data. ID is of Unlimited Integer type and consist of 2 parts: preamble (extension bit) and Integer number. Nodes of a special types, for example, system nodes or nodes with new types defined by the developers of OS or related file system manager component, can utilize a special delegated processing. When reading and decoding a header of a node of a non-standard type, the file manager or utilities delegate processing of the node to a custom component that knows how to process this type of node.