Automated Patch Compatibility Testing via Virtual Differencing Disks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current patch compatibility testing methods are manual, time-consuming, and resource-intensive, lacking standardized processes for vetting hardware and application compatibility with operating systems, which can lead to business interruptions and increased costs due to incompatible patches.

Innovation Solution

An automated patch compatibility testing system creates a testing image of a target computing system, installs patches, and conducts performance functionality tests on a differencing disk for each application, generating a report on compatibility based on predefined thresholds, providing real-time analysis and business intelligence for informed decision-making.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual compatibility testing is performed, then testing thoroughness is improved, but testing time and resource consumption increase significantly

Engineering Contradiction:
Improvetesting thoroughnessVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system creates a virtual copy (testing image) of the target computing system in a hypervisor environment. This virtual copy can be repeatedly cloned and used for compatibility testing without affecting the actual production system. The differencing disk creates another layer of copying that isolates test changes from the base image, enabling thorough testing while reducing time through reusable test environments.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs compatibility testing before actually deploying patches to production systems. By pre-testing applications against the patched testing image in advance, the system identifies compatibility issues beforehand, preventing business interruptions and reducing the need for emergency remediation work.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual compatibility testing is performed, then testing thoroughness is improved, but labor resources and costs increase

Engineering Contradiction:
Improvetesting thoroughnessVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system automates the compatibility testing process through scripted actions that automatically install applications, execute performance functionality tests, and collect results. The hypervisor environment self-manages the testing image creation, patch installation, and test execution without requiring manual intervention, reducing labor resources while maintaining thoroughness.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system replaces manual mechanical testing operations with automated computer-based testing. Instead of manually installing applications and checking compatibility, the system uses automated scripts and the hypervisor's virtualization capabilities to perform these operations programmatically, reducing both time and human resource requirements.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Productivity

If patches are installed without compatibility testing, then patch deployment speed is improved, but system reliability and business continuity deteriorate

Engineering Contradiction:
Improvepatch deployment speedVSAvoidsystem reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs compatibility testing in advance before patch deployment to production. By pre-validating application compatibility with the patched testing image, the system ensures reliability is established beforehand, allowing faster subsequent deployment without the risk of compatibility failures.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The hypervisor creates an intermediary testing image that sits between the original unpatched system image and the production environment. This intermediary allows safe experimentation and validation of patches in isolation, acting as a buffer that protects production systems from compatibility issues while enabling rapid deployment of verified patches.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If comprehensive compatibility testing is performed, then application compatibility assurance is improved, but testing infrastructure complexity increases

Engineering Contradiction:
Improvecompatibility assuranceVSAvoidtesting infrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The hypervisor platform provides universal functionality for creating, managing, and destroying testing images, as well as for executing automated tests. A single hypervisor environment handles multiple testing scenarios, application installations, and performance measurements, reducing overall infrastructure complexity while maintaining comprehensive testing capability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses nested virtualization structures where a differencing disk is created within the testing image, and applications are installed on the differencing disk. This nesting allows isolated testing environments within larger test frameworks, enabling comprehensive compatibility assurance while keeping individual test units simple and manageable.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS11442848B1System and method for automated patch compatibility of applications
Publication Date: 2022.09.13 APPCELER8 LLC
  • US11442848B1 patent drawing
  • US11442848B1 patent drawing

AI summary

Automated patch compatibility testing systems, methods, and computer program products are disclosed. The automated compatibility testing systems, methods, and computer program products disclosed herein enable an entity to check the functionality of applications following patches applied to an original image so that the enterprise can determine how its target computing systems will react to such patches before those patches are actually installed/deployed to the target computing systems. The automated compatibility testing systems, methods, and computer program products disclosed herein helps enterprises ensure that patches do not adversely impact the target computing systems and the operations thereof, and enable the enterprise to operate with minimal disruptions, stay current with patches, and take proactive and informed business decisions in managing the enterprise's computer infrastructure.