Markup Language Transactional Subunits for Network Rollback

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems for managing and configuring target devices in computer networks face challenges in rolling back transactions to their pre-execution state upon failure, especially when device-specific scripts are involved, leading to potential errors and partially executed states.

Innovation Solution

The use of a markup language file, such as an XML file, to define and process transactional units composed of subunits, where predefined tags identify subunits and associate parameters, allowing for the creation and execution of transactional units that can be undone in case of failure, thereby maintaining a system's integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If device-specific scripts are used for configuration changes on target devices, then the system can handle device-specific environmental variables, but the system may enter a partially executed state resulting in errors when failure occurs

Engineering Contradiction:

Improvedevice-specific configuration capabilityVSAvoidtransaction rollback reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments a transactional unit into multiple transactional subunits, each representing a discrete configuration operation. This segmentation allows the system to identify and rollback individual subunits upon failure, preventing partially executed states. The markup language file structure divides the transactional unit into identifiable subunit elements that can be independently managed and reversed.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary actions by creating a structured markup language file that defines all transactional subunits and their parameters before execution. This pre-definition allows the system to prepare rollback information in advance, ensuring that when failure occurs, the system can reliably return to the pre-execution state without leaving partial changes.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If a text file is used to define the transactional unit with multiple operations, then the transaction can be rolled back upon failure, but each undo operation must be tailored to the particular target device increasing complexity

Engineering Contradiction:

Improvetransaction rollback capabilityVSAvoidundo operation customization

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal markup language file structure that can define multiple transactional subunits with different parameters for different target devices. This universal structure eliminates the need for device-specific undo operation customization by providing a standardized way to define and execute transactions across diverse devices. The same markup language framework handles all device types uniformly.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent uses parameter changes within the markup language file to adapt transactional subunits for different target devices. Instead of creating custom undo operations for each device, the system modifies parameters in the unified markup language definition to accommodate device-specific requirements. This allows a single universal rollback mechanism to handle diverse device configurations through parameter variation rather than structural complexity.

Inventive Principle:

Principle #35Parameter changes

3Ease of operation

If configuration changes are performed on target devices, then the system can be configured properly, but failure during execution can result in a partially executed state

Engineering Contradiction:

Improveconfiguration executionVSAvoidsystem state integrity

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent implements feedback mechanisms through the structured markup language file that tracks the execution state of each transactional subunit. The system monitors execution progress and provides feedback information that enables automatic rollback to the pre-execution state upon failure. This feedback loop ensures system state integrity by detecting partial execution and triggering appropriate rollback actions.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent prepares rollback information in advance by structuring the markup language file to define all transactional subunits and their associated parameters before execution. This beforehand cushioning ensures that when failure occurs during configuration execution, the system already has the necessary information to revert to the pre-execution state, preventing partially executed states and maintaining system integrity.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS7827480B2System and method of using a transactional unit comprised of transactional subunits

Publication Date: 2010.11.02 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

An exemplary method comprises receiving an identifier of a transactional unit along with parameters for the transactional unit. The transactional unit includes transactional subunits. The method includes determining the transactional subunits for the transactional unit using a markup language file for the transactional unit. The markup language file can include subunit tags which identify the transactional subunits. Parameters for the transactional unit are associated with a transactional subunit.