File Management System Using System Call Interception for Consistent Naming

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing file management systems face challenges in systematically managing files across multiple user groups, leading to difficulties in tracking edited contents and potential deadlocks due to arbitrary file naming and path determination, which limits file sharing and synchronization across local devices and servers.

Innovation Solution

A method and device that manage files by detecting system calls and applying preset file management policies to determine file names and paths based on attributes like creation date, modification date, owner, and access privileges, allowing automatic file naming and synchronization across devices, including local and server environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users arbitrarily determine file names and paths, then users have flexibility in file management, but systematic file management becomes difficult and file sharing across multiple users deteriorates

Engineering Contradiction:

Improveuser flexibility in file namingVSAvoidsystematic file management

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent changes the parameters of file naming from arbitrary user-defined names to structured names composed of multiple attributes (filename, extension, creator, creation date, modification date). This parameter transformation enables systematic management while preserving user flexibility through customizable attribute selection and weighting.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The patent segments the file identification system into multiple independent attributes (filename, extension, creator, creation date, modification date) rather than using a single arbitrary name. This segmentation allows each attribute to be managed independently according to preset rules, improving systematic management while maintaining user flexibility in attribute configuration.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If multiple users edit and process the same file, then collaboration is enabled, but tracking and managing edited contents becomes difficult and content loss or contradiction may occur

Engineering Contradiction:

Improvemulti-user collaborationVSAvoidtracking edited contents

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements feedback mechanisms by automatically recording and updating file attributes (creator, creation date, modification date) whenever a user edits the file. This feedback loop enables automatic tracking of edited contents, preventing information loss and content contradictions while supporting multi-user collaboration.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent performs preliminary actions by establishing preset file management policies before multi-user editing begins. These policies define how file attributes are generated, updated, and used for tracking, ensuring that collaboration proceeds smoothly with automatic tracking from the outset rather than requiring post-hoc tracking solutions.

Inventive Principle:

Principle #10Preliminary action

3Extent of automation

If hooking techniques are used to automatically designate file names and paths, then file saving automation is achieved, but deadlocks occur with other applications using identical hooking techniques

Engineering Contradiction:

Improvefile saving automationVSAvoidsystem stability

Core Design Contradiction:

Extent of automationVSReliability

Solution Approach 1:

The patent changes the approach from hooking into system calls to directly intercepting and processing file operations at the application level. This parameter change in the interception mechanism avoids the deadlock issues associated with hooking while maintaining automation of file naming and path designation.

Inventive Principle:

Principle #35Parameter changes

4Ease of operation

If file management policies are applied at the user level, then ease of use is maintained, but kernel-level control and topmost privilege are not achieved

Engineering Contradiction:

Improveuser-level management simplicityVSAvoidkernel-level control

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent introduces an intermediary file management device that operates between the user application and the operating system kernel. This intermediary captures file operation requests, applies preset policies, and executes controlled operations, achieving both user-level simplicity and kernel-level control through the mediating layer.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10417179B2Method for managing files and apparatus using the same

Publication Date: 2019.09.17 GAEASOFT

AI summary

A method for managing files is provided. The method includes steps of: a file managing device (a) detecting a system call corresponding to a file access request from a program executed by the device; and (b) performing, by referring to the detected system call and parameters thereof, at least one of (i) execution of a procedure corresponding to the system call and (ii) supporting execution of the procedure corresponding to the system call, based on at least one file management policy; wherein the policy includes a local file naming policy to determine at least one of a file name and a file path among the parameters, by referring to an attribute thereof, which has at least part of a creation date and time, a modification date and time, a type, a name, an owner, a creator, an access privilege, origin information, version, situational information, a keyword and a subtitle.