Shared File System Management via Change File Mediation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current shared file system implementations restrict access and updates between different operating systems, as they employ proprietary structures and protocols, preventing cross-platform file sharing and management.
Innovation Solution
A method is introduced where a change file is created in non-volatile memory, allowing updated information to be written and managed by a secondary operating system, which is then processed by the primary operating system in control, enabling concurrent and independent operation without conflicts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proprietary file system structures and access protocols are employed by each operating system, then each operating system can maintain control and security over its own file system, but cross-platform file sharing and access between different operating systems becomes impossible
Solution Approach 1:
The patent introduces a mediator mechanism that enables different operating systems to communicate with the shared file system through a common interface. The mediator layer translates proprietary file system structures into a unified access protocol, allowing Linux and Windows systems to share files without requiring both systems to use the same native file system format, thus resolving the contradiction between maintaining proprietary control and enabling cross-platform access
Solution Approach 2:
The patent implements a universal file system access interface that can be used by multiple different operating systems. This universal interface provides common functionality for file creation, reading, writing, and deletion across platforms, while each operating system can maintain its own proprietary structures underneath the unified layer, enabling both cross-platform compatibility and proprietary system control
2Adaptability or versatility
If multiple operating systems attempt to access and update the same shared file system simultaneously, then cross-platform collaboration is enabled, but conflicts and data corruption occur due to lack of coordinated control
Solution Approach 1:
The patent implements preliminary actions by creating a dedicated control structure and locking mechanism before any file updates occur. The system establishes a centralized coordination framework that pre-defines access protocols and conflict resolution procedures, ensuring that when multiple operating systems attempt simultaneous updates, the pre-established mechanisms prevent data corruption by serializing access or coordinating changes in advance
Solution Approach 2:
The patent introduces feedback mechanisms that monitor the state of the shared file system and notify operating systems of concurrent access conditions. When multiple systems attempt to write to the same file simultaneously, the feedback system detects the conflict and coordinates resolution through the mediator layer, preventing data corruption while maintaining the ability for multi-OS collaboration
3Ease of operation
If the operating system without principal control writes directly to the shared file system, then concurrent operation is simplified, but conflicts and data loss occur due to lack of authority
Solution Approach 1:
The patent uses an intermediary mediator layer that sits between operating systems without principal control and the shared file system. This mediator translates write operations from secondary operating systems into coordinated updates that the principal operating system can process safely, enabling concurrent operation without direct conflicts while maintaining data consistency through the mediation layer
Data Source
AI summary
A shared file system may be updated by a non-native operating system writing information to a change file, while a native operating system is in a suspend or hibernation mode; after writing, the non-native operating system is placed in a suspend or hibernation mode and the native system activates and then retrieves the updated information from the change file and writes the updated information to a shared file system. The native operating system returns to a suspend or hibernate state before the non-native operating resumes operation. The updated information may be written as provided by the non-native operating system, or further updated by the native operating system before being written to the shared file system. The change file is created by the native operating system, and may be a reserved portion of the shared file system or may be a separate portion of non-volatile memory. The native and non-native operating systems operate both concurrently and independent of one another; thereby, preventing conflicts during file system updating.