Patch Converter for Incompatible Software Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current patch management systems are inefficient and burdensome when applying software patches, particularly for incompatible patches that are not monolithic, leading to security vulnerabilities, productivity loss, and software malfunctions due to their inability to install patches with multiple entry points of execution.

Innovation Solution

The method involves creating an executable archive that includes an incompatible patch and a script with pre-processing, installation, and post-processing actions, which can be sent to the patch management system to facilitate the installation of non-monolithic patches, using either self-extracting or non-self-extracting archives, ensuring compatibility and automating the installation process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If current patch management systems are used to apply software patches, then the system can manage patches, but it cannot install incompatible patches with multiple entry points of execution, leading to security vulnerabilities

Engineering Contradiction:
Improveability to install incompatible patchesVSAvoidsecurity vulnerability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary conversion process that transforms incompatible patches with multiple entry points into a compatible monolithic format. The system uses a patch converter that packages the incompatible patch and its multiple entry points into a single executable archive with a standardized interface, allowing the patch management system to install and manage it without direct support for multiple entry points.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the structural parameter of the patch from a multi-entry point format to a monolithic single-entry point format. By converting the patch architecture and packaging it as a self-contained executable unit, the system maintains compatibility with existing patch management infrastructure while enabling installation of previously incompatible patches.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If manual methods are used to apply incompatible patches, then security vulnerabilities may be reduced, but the process is time intensive and burdensome

Engineering Contradiction:
Improvesecurity vulnerabilityVSAvoidtime intensive process
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements self-service automation where the patch management system automatically converts, validates, and installs patched versions of incompatible software. The system performs pre-processing actions before patch installation and post-processing actions after installation, eliminating the need for manual intervention while ensuring security and compatibility.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary actions by converting incompatible patches to compatible format before installation. The system pre-processes the patch content, packages it into a monolithic executable, and validates it beforehand, so that the actual installation process is quick and automated without manual security verification steps.

Inventive Principle:
Principle #10Preliminary action

3Stability of the object's composition

If incompatible patches are not installed, then system stability is maintained, but security vulnerabilities increase and productivity is lost

Engineering Contradiction:
Improvesystem stabilityVSAvoidproductivity loss
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent creates a universal patch format that can handle both compatible and previously incompatible patches through a single standardized interface. The monolithic executable architecture allows the patch management system to uniformly process all patches regardless of their origin or complexity, enabling automated installation while maintaining system stability through controlled deployment.

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

4Device complexity

If the patch management system only supports monolithic patches, then system complexity is reduced, but adaptability to handle incompatible patches is limited

Engineering Contradiction:
Improvesystem complexityVSAvoidpatch compatibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent uses the patch converter as an intermediary layer that handles the complexity of incompatible patches externally. The core patch management system maintains its simple monolithic patch architecture, while the converter translates various patch formats into the supported monolithic format, effectively adding adaptability without increasing core system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12131150B2System and methods for patch management
Publication Date: 2024.10.29 IVANTI INC
  • US12131150B2 patent drawing
  • US12131150B2 patent drawing
  • US12131150B2 patent drawing

AI summary

A method for patch management is described. The method includes downloading a patch that is incompatible with a patch management system. The method also includes creating an archive that is executable by the patch management system. The archive includes the incompatible patch. The method further includes sending the archive to the patch management system.