Hibernation File Management for Fast Computer Boot
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional computer systems require lengthy boot procedures, which hinder quick multimedia functionality and lack efficient data protection mechanisms, leading to high costs and low flexibility in application usage.
Innovation Solution
Implementing a hibernation mode for the operating system, where a hibernation file records the system's state, allowing the OS to quickly transition to normal mode, and using management software to manage access and write requests, ensuring data is not written to the partition and is instead stored in system memory or another partition, with write completion messages handled to maintain system integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the computer system follows the normal boot procedure to load BIOS, detect hardware, and initialize partitions, then the system can reliably boot the operating system, but the boot time is long (30 seconds to several minutes)
Solution Approach 1:
The patent applies preliminary action by pre-loading the operating system into system memory before the user needs to use it. When the user selects fast boot mode, the system loads the OS from the partition into memory in advance, so that when the user activates the device, the OS is already ready to run, eliminating the need for full hardware detection and initialization at boot time. This resolves the contradiction by performing the time-consuming boot preparation work beforehand.
Solution Approach 2:
The patent applies local quality by creating different boot modes with different levels of initialization. The fast boot mode performs only essential operations while the normal boot mode performs complete hardware detection and initialization. This allows the system to have both a fast path for typical use cases and a complete path for reliability, resolving the contradiction between speed and reliability by providing localized optimization for different usage scenarios.
2Adaptability or versatility
If the computer system is designed for multimedia functions with integrated application programs, then the system can provide entertainment functionality, but the software/firmware must be designed for respective hardware, resulting in high cost and low flexibility
Solution Approach 1:
The patent applies universality by making the multimedia application programs independent of specific hardware configurations. The OS loads generic multimedia applications that can run on various hardware platforms without requiring custom firmware development for each device. This allows the same software to be used across different hardware configurations, reducing development costs and increasing flexibility while maintaining multimedia functionality.
Solution Approach 2:
The patent applies copying by using virtualized or emulated hardware environments that replicate the behavior of specific multimedia hardware through software. This allows commercial application programs to run on generic hardware through software emulation, eliminating the need to design and manufacture custom firmware for each hardware configuration, thus reducing costs and improving flexibility.
3Speed
If users turn off electronic multimedia devices directly without a specific shutdown procedure, then the device can be quickly powered down, but data or OS in the partition may be damaged
Solution Approach 1:
The patent applies self-service by implementing an automatic shutdown procedure that is triggered when the user directly powers off the device. The system detects the abrupt power-off and automatically executes data protection routines, including flushing buffers, syncing file systems, and marking partitions as dirty for subsequent checks. This self-protecting mechanism resolves the contradiction by providing fast shutdown for users while automatically ensuring data integrity through programmed protection routines.
Solution Approach 2:
The patent applies preliminary anti-action by implementing protective measures that counteract the potential harm of direct power-off before it occurs. The system continuously monitors system state and prepares protective actions (such as maintaining write-cached buffers, implementing journaling, and setting up file system checks) that automatically activate when abrupt shutdown occurs. This preliminary preparation of protective measures resolves the contradiction between fast shutdown and data protection.
Data Source
AI summary
Boot methods for use in a computer system. The computer system boots from a partition comprising an OS in hibernation mode. The OS exits the hibernation mode to a normal operating mode according to a hibernation file, and marks the hibernation file. The marked hibernation file is modified to the original hibernation file, and access to the partition returns to being monitored. If a write request to the partition is received, the data is discarded or written to another partition or a system memory of the computer system, and a write completion message is replied. If the computer system reboots, the OS also returns to the normal operating mode according to the original hibernation file.