Reversible Software Update Activation via Switch Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current enhancement package systems in multi-client computer systems often cause disruption and lack the ability to reverse changes effectively, as new functionality may overwrite or alter existing configuration data, making it difficult to assess and undo installations in a cost- and time-effective manner.

Innovation Solution

The implementation of a reversible activation method using a switch framework that allows for the creation of a test client with isolated logical values and user data, enabling non-disruptive testing and easy reversal of updates, while maintaining productive system integrity by separating test and productive client environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If enhancement packages are installed to provide new functionality, then software capabilities are improved, but system disruption increases and reversibility is lost

Engineering Contradiction:
Improvesoftware capabilitiesVSAvoidsystem disruption
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments the enhancement package installation process into distinct phases: a reversible test phase where changes can be undone, and a final deployment phase. This segmentation allows new functionality to be tested in isolation from the productive system, reducing overall system disruption while maintaining capability improvements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary testing of enhancement packages in a separate test client before deploying to the productive system. This preliminary action allows identification and resolution of issues before they affect the productive system, reducing disruption while enabling capability improvements.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If enhancement packages overwrite existing configuration data, then new functionality is implemented, but ability to reverse changes is lost

Engineering Contradiction:
Improvenew functionalityVSAvoidreversibility
Core Design Contradiction:
Adaptability or versatilityVSEase of repair

Solution Approach 1:

The patent extracts the configuration data and system state from the productive client before testing enhancement packages. By taking out the data and creating a separate test environment, the system can experiment with new functionality without permanently overwriting productive system configurations, maintaining reversibility through the ability to discard test results.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system changes the state parameter of enhancement packages from permanently applied to temporarily applicable during testing. By modifying how enhancement packages are applied (reversibly in test mode vs. permanently in productive mode), the system enables new functionality exploration without losing the ability to revert changes.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If testing is performed in the productive system, then integration is ensured, but operational disruption increases

Engineering Contradiction:
ImproveintegrationVSAvoidoperational disruption
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent creates a copy of the productive client's configuration data and system state in a separate test client. This copying enables testing of enhancement packages with integrated data relationships without disrupting the actual productive system operations, maintaining integration verification while eliminating operational disruption.

Inventive Principle:
Principle #26Copying

4Stability of the object's composition

If configuration data is shared across clients, then consistency is maintained, but testing isolation is lost

Engineering Contradiction:
Improvedata consistencyVSAvoidtesting isolation
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent segments the data access architecture by introducing client-specific data isolation layers. While configuration data remains consistent across clients through the enhancement package framework, test clients are segmented to operate on isolated data copies, enabling both data consistency maintenance and testing isolation simultaneously.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8935670B2System and method for business function reversibility
Publication Date: 2015.01.13 SAP SE
  • US8935670B2 patent drawing
  • US8935670B2 patent drawing
  • US8935670B2 patent drawing

AI summary

Embodiments of the present invention may provide “undo” (e.g., rollback) features, along with data management simplification features, to an update package model of software suite development/evolution. New functions, which may have disruption effects for customers, may be installed into the core configuration data with inactive switches. Upon activation, a switch status may change, and a query filter may use the activated function (e.g., as associated with the switch ID). Original functions may be maintained, giving the user the ability to deactivate an activated function, and thereby reverting the system back to the prior configuration status.