Self-Repairing Operating System via Reference File Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computer system maintenance and repair methods are inefficient, requiring significant resources and technical intervention, especially when the operating system is non-functional or user data is locked, and they do not account for system changes over time.
Innovation Solution
A method that creates a reference collection of files for an operating system, storing it on a server and a client cache, allowing automatic self-repair by comparing attributes during reboot cycles to restore the system to a usable state without requiring network access or technical support.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If technicians are allocated to repair computer systems, then system reliability is improved, but productivity decreases due to consumption of valuable resources including online time, office resources, and human resources
Solution Approach 1:
The patent implements automatic self-repair functionality where the computer system detects and repairs its own software failures without human intervention. The system includes a repair engine that automatically identifies corrupted files, restores them from backup copies, and returns the system to operational state, eliminating the need for technician allocation while maintaining system reliability.
Solution Approach 2:
The patent employs preventive maintenance mechanisms that create backup copies of system files before failures occur and establish repair rules in advance. When software failures are detected, the pre-prepared backup copies and repair rules enable immediate automated restoration, preventing productivity loss without requiring reactive technician intervention.
2Ease of repair
If software-based maintenance techniques are used, then ease of repair is improved, but reliability worsens when the target operating system is not functioning or files are locked
Solution Approach 1:
The patent introduces a repair engine as an intermediary component that operates independently of the target operating system's functional state. The repair engine can detect software failures, access locked files through specialized mechanisms, and execute repairs even when the OS is non-functional, thereby maintaining reliability while preserving ease of repair through automated processes.
Solution Approach 2:
The patent separates the repair functionality from the operating system by implementing a dedicated repair engine with independent file access capabilities. This segmentation allows the repair mechanism to operate autonomously without being constrained by OS file locking mechanisms or functional requirements, enabling reliable repairs in degraded system states.
3Ease of operation
If non-optimized methods of network and storage access are used, then ease of operation is improved, but productivity decreases due to slowed deployment, update, and repair activities
Solution Approach 1:
The patent implements local caching of repair rules and backup file copies on the client system before they are needed. This preliminary action eliminates the need for real-time network access during repair operations, enabling fast automated repairs without sacrificing ease of operation. The system maintains simplified operation while achieving high productivity through pre-positioned repair resources.
Data Source
AI summary
A system and method is provided for the repair of operating system and application binary files and configuration data files at pre-operating system boot stage by comparing attributes of the files against a reference collection of such files stored on a server during each reboot or restart cycle while creating and restoring a collection of dynamic operating system binary files, configuration data files, file system structures and hardware system attributes unique to the configuration and use of the system on a server for subsequent pre-operating system repair operations.