Dual OS Partition Architecture for Instant System State Rollback

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current computing systems face challenges in efficiently returning to a previous state after software updates, as the process of uninstalling or reverting updates is often lengthy and may be unsuccessful, especially for substantial updates that alter the system extensively, preventing a return to the original state.

Innovation Solution

The implementation of a dual-operating system partition architecture allows users to load a second system state and request a return to a first system state, enabling immediate access to the original state without the need for uninstalling software, by rebooting with the first operating system partition and restricting further application of the previous modification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software updates are uninstalled or reverted to return to a previous state, then the system can be returned to an earlier state, but the process is very lengthy and may be unsuccessful

Engineering Contradiction:

Improvesuccess rate of returning to previous stateVSAvoidtime required for uninstallation process

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system divides the operating system into multiple partitions (first operating system partition and second operating system partition), each containing different system states. This segmentation allows the system to switch between partitions instantly rather than performing lengthy uninstallation processes, thereby reducing time loss and improving reliability of returning to a previous state.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system prepares multiple operating system partitions in advance, each containing a complete system state. When a user wants to return to a previous state, the system simply switches to the pre-prepared partition containing that state, eliminating the need for time-consuming uninstallation processes and ensuring reliable restoration.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If substantial updates are applied to the operating system, then the system gains new features and improvements, but the system cannot return to a previous state because it has changed too extensively

Engineering Contradiction:

Improveability to apply substantial updatesVSAvoidability to return to previous state

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments the operating system into separate partitions, allowing substantial updates to be applied to one partition while preserving the original system state in another partition. This enables the system to adapt to new features while maintaining the reliability of returning to previous states by switching partitions.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system creates a copy of the operating system in a separate partition before applying substantial updates. This copy serves as a backup that can be restored by switching partitions, allowing the system to gain new features while preserving the ability to return to the original state.

Inventive Principle:

Principle #26Copying

3Device complexity

If a single operating system partition is used, then the system structure is simple, but the system cannot efficiently return to a previous state without lengthy uninstallation processes

Engineering Contradiction:

Improveoperating system partition structureVSAvoidtime for uninstallation process

Core Design Contradiction:

Device complexityVSLoss of time

Solution Approach 1:

The system uses multiple operating system partitions instead of a single partition. While this increases structural complexity, it eliminates the need for lengthy uninstallation processes by allowing instant switching between partitions, thereby significantly reducing time loss.

Inventive Principle:

Principle #1Segmentation

4Loss of time

If multiple operating system partitions are maintained, then the system can quickly switch between states, but the system complexity increases

Engineering Contradiction:

Improvetime to return to previous stateVSAvoidnumber of operating system partitions

Core Design Contradiction:

Loss of timeVSDevice complexity

Solution Approach 1:

The system implements multiple operating system partitions to enable quick switching between states. The management system coordinates these partitions to provide efficient state restoration while maintaining organized system structure.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system introduces a partition management system that acts as an intermediary between the user and multiple operating system partitions. This mediator handles the complexity of managing multiple partitions, allowing users to benefit from quick state switching without directly dealing with the underlying complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10013259B2User initiated data rollback using operating system partitions

Publication Date: 2018.07.03 GOOGLE LLC

AI summary

Methods for returning a computing system to a previous state are provided. In one aspect, a method includes loading a second system state of a second operating system partition, and receiving a request to return to a first system state of a first operating system partition while operating in a second system state of the second operating system partition. The method also includes loading the first system state of the first operating system partition. Systems and machine-readable media are also provided.