Patch Sequencing Algorithm for Dependency Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual installation of software patches is time-intensive and prone to errors due to the need for manual validation of system architecture, operating systems, and dependencies, which is interdependent and requires significant administrative effort.

Innovation Solution

An interactive graphical user interface (GUI) environment that programmatically validates target systems for patch suitability, checks dependencies, and sequences patches for correct installation order, allowing for parallel installation across multiple devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual patch installation is performed, then system administrator can verify and control each patch installation, but the process becomes time-intensive and error-prone

Engineering Contradiction:
Improvepatch installation accuracyVSAvoidpatch installation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary validation of target systems against patch requirements before installation, checking system architecture, operating system version, and pre-installed packages. Dependencies are pre-verified and patches are sequenced in advance, so that during actual installation, the process can proceed rapidly without manual verification delays while maintaining accuracy through automated checks.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If automated patch installation is implemented, then installation speed increases, but validation accuracy and dependency checking may be compromised

Engineering Contradiction:
Improvepatch installation efficiencyVSAvoidsystem validation accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The system implements automated feedback mechanisms where the patch validation process continuously checks target system attributes (architecture, OS version, installed packages) against patch requirements. The sequencing algorithm receives feedback about dependency relationships and automatically adjusts the installation order. This closed-loop validation ensures high precision in system compatibility verification while maintaining automated high-speed installation.

Inventive Principle:
Principle #23Feedback

3Productivity

If multiple patches are installed simultaneously, then installation productivity increases, but correct sequencing and dependency management become complex

Engineering Contradiction:
Improveparallel installation capabilityVSAvoidpatch sequencing complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces a patch sequencing algorithm as an intermediary layer between the patch repository and target systems. This algorithm analyzes dependency relationships among multiple patches, determines the correct installation sequence, and manages parallel installation workflows. By placing this intelligent mediator in charge of coordination, the system can safely install multiple patches in parallel while automatically handling the complexity of dependency management and sequencing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9009694B2Pre-verification and sequencing of patches
Publication Date: 2015.04.14 SUN MICROSYSTEMS INC
  • US9009694B2 patent drawing
  • US9009694B2 patent drawing
  • US9009694B2 patent drawing

AI summary

The present invention provides an interactive graphical user interface (GUI) patch environment for installing a patch on the targeted systems. A system administrator or other authorized user interfaced with a machine may perform the installation of a patch on the machine using a software wizard. Additionally, the Wizard pre-verifies the patch dependencies (pre-installed software) required by the patch and checks the target systems to ensure the target systems possess the requisite dependencies. Once the target systems have been validated and the required dependencies identified on the target systems, the sequencing algorithm sorts patches in correct order before applying patches to the target systems. The user can remove the patch from the pre-validated patch list about to be applied to the target system. The patch dependency is checked before removing the patch from the pre-validated patch list for proper removal order.