Patch Upgrade File Processing via Partition Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software upgrade methods, particularly differential package upgrades, are inefficient for quick bug fixes due to large upgrade packages and high workload, as they require multiple upgrades and slow upgrading speeds, failing to meet the requirement for quick patching and increasing server workload.
Innovation Solution
A patch-upgrade-based file processing method that saves patch packages in a separate partition, establishing an association between original and patch file paths, allowing direct access to patch files for quick upgrades, reducing the need for large upgrade packages and improving system security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If differential package upgrade mode is used, then upgrade package size is reduced compared to full image reversion, but upgrading speed is still slow and workload remains high
Solution Approach 1:
The patent divides the upgrade package into two segments: a base differential package containing common updates, and separate patch packages containing emergency bug fixes. This segmentation allows the small patch package to be applied independently without requiring the full differential package, thus improving upgrading speed while keeping package sizes manageable.
Solution Approach 2:
The patent applies patches to the latest version in advance to create a pre-upgraded reference version. This preliminary action allows emergency bug fixes to be prepared beforehand and applied directly to older versions through version mapping, eliminating the need for multiple sequential upgrades and significantly accelerating the patching process.
2Ease of operation
If multiple upgrade packages are released for different earlier versions, then each version can be patched directly, but server workload increases hugely
Solution Approach 1:
The patent creates a universal patch application mechanism that can handle multiple version scenarios through version mapping. Instead of preparing separate patch packages for each version combination, the system uses a single patch package combined with version mapping technology to achieve direct patching for any earlier version, thereby reducing server workload while maintaining ease of operation.
Solution Approach 2:
The patent introduces version mapping as an intermediary layer between the patch package and different terminal versions. This intermediary establishes correspondence relationships between various versions and the latest version, enabling the system to apply a single patch package to multiple versions without requiring multiple separate packages, thus reducing server complexity and workload.
3Reliability
If sequential upgrades are performed (current version to latest version, then apply patch), then patch compatibility is ensured, but total upgrading time increases significantly
Solution Approach 1:
The patent performs the time-consuming differential upgrade in advance to create a pre-upgraded reference version with emergency bugs already fixed. This preliminary action shifts the upgrade workload to a background process, allowing emergency patches to be applied directly to older versions without requiring sequential upgrades, thus maintaining patch compatibility while dramatically reducing user-facing upgrading time.
Solution Approach 2:
The patent creates a copy of the latest version (pre-upgraded reference version) that serves as the basis for patch application. This copying approach allows the system to apply patches directly to older versions by referencing the pre-upgraded version, eliminating the need for sequential upgrades and significantly reducing total upgrading time while ensuring patch compatibility through the reference version.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
The present disclosure provides a patch-upgrade-based file processing method and apparatus, a terminal, and a storage medium. The method includes: receiving a file access request, where the file access request includes storage path information; if the storage path information indicates a first partition, determining whether the storage path information exists in an association relationship that is between original file path information and patch upgrade file path information and that is in a preconfigured system; if the storage path information exists in the association relationship, querying the association relationship that is between the original file path information and the patch upgrade file path information and that is in the preconfigured system, to obtain patch upgrade file path information corresponding to the storage path information; and obtaining, from a target partition that is indicated by the corresponding patch upgrade file path information, a patch upgrade file that matches the patch upgrade file path information. According to the technical solutions provided in the present disclosure, quick upgrading by using a small patch can be implemented, and workload is reduced.