Software Update Compatibility Verification via Version Identifier Hashing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Administrators face challenges in ensuring that software packages are correctly installed and updated across computing systems, particularly in large networks, due to the lack of efficient methods to verify the compatibility of software updates.

Innovation Solution

An administrator system generates a version identifier for each computing system based on installed software packages, using a version tool that identifies and orders package data, applies a hash function, and compares it to a test version identifier to determine potential update issues before installation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If administrators manually examine each software package on each computing system to determine correct installation, then installation accuracy is improved, but time consumption and operational complexity increase significantly

Engineering Contradiction:
Improveinstallation verification accuracyVSAvoidtime to verify software packages
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent creates a copy of the software package metadata (name, version, release, arch, checksum) and stores it in a centralized database. This copy can be quickly compared against the actual installed packages without manually examining each system, thereby maintaining verification accuracy while dramatically reducing time consumption.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces a package manager as an intermediary component that automatically tracks and reports software package installation status. This mediator handles the verification process centrally, eliminating the need for administrators to manually check each system while ensuring accurate installation verification through automated metadata collection and comparison.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If administrators manually check software packages across large networks, then compatibility verification is improved, but device complexity and operational difficulty increase

Engineering Contradiction:
Improvesoftware update compatibilityVSAvoidadministrative workload
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent enables the package manager to automatically perform compatibility verification by comparing installed package metadata against update package metadata. The system self-services the compatibility checking function without requiring administrator intervention, thereby maintaining high reliability while significantly improving ease of operation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements a feedback mechanism where the package manager continuously monitors software package installations and automatically notifies administrators of compatibility issues. This feedback loop ensures reliable compatibility verification while reducing operational complexity by automating the entire verification and notification process.

Inventive Principle:
Principle #23Feedback

3Productivity

If users attempt to update software packages without compatibility verification, then update speed is improved, but system reliability deteriorates due to potential installation failures

Engineering Contradiction:
Improvesoftware update speedVSAvoidupdate installation success
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent performs compatibility verification in advance before the actual software update installation. The package manager compares package metadata and identifies potential compatibility issues prior to installation, allowing users to proceed with updates at full speed while maintaining reliability through pre-verification.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies preliminary anti-action by blocking incompatible software updates before they can be installed. The package manager identifies compatibility conflicts in advance and prevents the installation of problematic updates, thereby maintaining update speed for compatible packages while protecting system reliability by stopping incompatible ones before they cause failures.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS8640119B2Determining compatibility of a software package update using a version identifier
Publication Date: 2014.01.28 RED HAT INC
  • US8640119B2 patent drawing
  • US8640119B2 patent drawing
  • US8640119B2 patent drawing

AI summary

An administrator system can generate a version identifier for a computing system based on the software packages installed on a computing system. The administrator system can utilize the version identifier to determine if software package updates will install properly on a computing system. When the computing system request an update to a software package, the administrator system can generate a version identifier for the software package, as installed on the computing system and to be updated. The administrator system can compare the generated version identifier to a test version identifier. The test version identifier can be a version identifier generated for a version of an exemplary software package known to properly install the update. Once compared, the administrator system can notify the user of the computing system of the comparison, for example, if the version identifier and the test version identifier are different indicating potential problems in the update.