System Update Rollback via Reverse Operation Planning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current system update methods require significant resources to prepare rollback procedures for all possible states during an update operation, which can be inefficient and time-consuming, especially when exceptions occur, as they often rely on generating procedures from scratch or preparing extensive reverse operations.
Innovation Solution
A system update device and method that includes a reverse operation generation unit to create reverse operations from update procedures, a first procedure generation unit to generate reverse execution procedures for non-reversible operations, and a planning unit to plan operations for transitioning to the initial state, combining these to generate rollback procedures efficiently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If rollback procedures are prepared for all possible states during update operation, then system reliability is improved, but device complexity and resource requirements increase significantly
Solution Approach 1:
The patent applies preliminary action by generating reverse operations from the update procedure in advance, before the actual update execution. The reverse operation generation unit creates inverse operations that can restore the system to its initial state, storing these prepared reverse operations for quick retrieval and execution when rollback is needed, thus ensuring reliability without requiring complex pre-prepared rollback procedures for all possible states
Solution Approach 2:
The patent applies inversion by generating reverse operations that execute in the opposite direction of the update operations. Instead of preparing explicit rollback procedures, the system creates inverse operations (e.g., if an update operation installs software version A to B, the reverse operation removes version B to restore version A), allowing the system to rollback by executing these inverted operations in reverse order
2Reliability
If rollback procedures are prepared for all possible states, then exception handling capability is improved, but loss of time in preparation and execution increases
Solution Approach 1:
The system performs preliminary generation of reverse operations from the update procedure before update execution begins. These reverse operations are stored and can be quickly retrieved when needed, eliminating the time-consuming preparation of rollback procedures for all possible states at runtime while maintaining comprehensive exception handling capability
Solution Approach 2:
The system dynamically generates appropriate rollback procedures based on the actual update procedure executed, rather than having static pre-prepared rollback procedures for all possible states. The reverse operation generation unit creates context-specific reverse operations that match the actual update operations performed, reducing unnecessary preparation time while ensuring appropriate exception handling
3Speed
If rollback procedures are prepared in advance for all states, then rollback execution speed is improved, but resource requirements and storage needs increase
Solution Approach 1:
The system prepares reverse operations in advance from the update procedure and stores them efficiently. When rollback is needed, these pre-generated reverse operations are retrieved and executed quickly, achieving fast rollback execution without requiring extensive storage of pre-prepared rollback procedures for all possible system states
Solution Approach 2:
The reverse operations generated serve multiple purposes: they can be executed individually or in sequence, can handle different types of exceptions, and can be applied to various states reached during update execution. This universal approach reduces the need for separate rollback procedures for each possible state, lowering resource requirements while maintaining execution speed
Data Source
AI summary
A system update device 10 includes a first procedure generation unit 12 which generates a reverse execution procedure, which is a procedure including multiple reverse operations generated on the basis of a part of the update procedure that does not include operations for which a reverse operation cannot be generated, wherein said multiple reverse operations are arranged in a reverse order of the predetermined order; a planning unit 13 which plans an operation procedure for transitioning, from an arbitrary state during execution of the update procedure to the current state, the state of a state element which corresponds to a part of the update procedure that includes operations for which a reverse operation cannot be generated; and a second procedure generation unit 14 which generates a rollback procedure by combining the generated reverse execution procedure and the planned procedure.