OS Rollback Partitioning for Encrypted User Data Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional operating system rollback methods require users to take their devices to an outlet for manual intervention, as the user data partition in higher versions cannot be decrypted by lower versions, leading to rollback failures.
Innovation Solution
The electronic device autonomously writes system data of the lower version into static and user data partitions in a standby state, enters recovery mode to merge and format the user data partition, and then loads the lower version data, allowing seamless rollback without manual intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the user data partition in higher version is used for rollback, then the rollback process can be simplified, but the lower version cannot decrypt the user data partition leading to rollback failure
Solution Approach 1:
The patent divides the partitioning system into different types (system partition and user data partition) with distinct encryption mechanisms. The system partition uses encryption that lower versions can decrypt, while the user data partition uses encryption specific to higher versions. This segmentation allows the rollback process to selectively access encrypted user data from the user data partition without affecting the system partition, resolving the contradiction between simplified rollback operation and decryption capability.
Solution Approach 2:
The patent introduces an intermediary mechanism where the system partition acts as a mediator between the lower version system and the encrypted user data partition. During rollback, the system partition (which can be decrypted by lower versions) provides necessary system files and boot information, while the user data partition (encrypted with higher version keys) stores user data that can be accessed through the intermediary system partition during the rollback process.
2Ease of operation
If automatic rollback is implemented, then user convenience is improved, but system complexity increases due to encryption and partition management
Solution Approach 1:
The patent implements preliminary action by pre-establishing different encryption mechanisms for system and user data partitions before rollback is needed. The system partition is encrypted with keys accessible to lower versions, while the user data partition uses higher version encryption keys. This preliminary setup enables automatic rollback to work seamlessly without requiring real-time complex decision-making during the rollback process.
Solution Approach 2:
The patent enables self-service automatic rollback by designing the partition management system to automatically handle encryption and decryption processes. The system automatically identifies which partition to access based on version requirements, automatically manages the encryption keys, and automatically executes the rollback process without user intervention, thereby reducing operational complexity despite increasing system-level complexity.
3Device complexity
If manual outlet rollback is used, then system complexity is reduced, but user time consumption increases and accessibility is limited
Solution Approach 1:
The patent replaces the mechanical manual outlet rollback process with an automated software-based system. Instead of requiring physical transport to an outlet and manual intervention, the system uses software mechanisms to automatically manage partition access, encryption/decryption, and data migration. This substitution dramatically reduces user time consumption and improves accessibility while introducing controlled system complexity in the form of automated software management.
Data Source
AI summary
This application discloses an operating system upgrade method and an electronic device in the field of computer technologies. The method involves loading a basic partition, a first static partition, and a dynamic partition to run a first version of the operating system. It obtains a first installation package for a second version, which is lower than the first version, containing first and second system data. The first system data is written into a second static partition and a user data partition. The device then reboots into repair mode, writing the second system data from the user data partition into the dynamic partition and formatting the user data partition. Finally, it reboots to load the basic partition, second static partition, and dynamic partition to run the second version of the operating system. This allows the electronic device to automatically roll back to a lower version without needing service outlet intervention.