Autonomic Software Upgrade Management via Event-Driven Policy Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing automatic update tools for software and hardware are inefficient, often requiring users to manually search for and evaluate upgrades, which can introduce new problems, waste time, and lead to outdated systems due to large download sizes and lack of bandwidth considerations, resulting in potential security vulnerabilities.

Innovation Solution

An autonomic, event-driven method for upgrading computer hardware, operating systems, and software that connects to an upgrade management server to detect necessary updates based on user-defined policies, selectively downloads and installs recommended modules, and notifies users of the upgrade status, allowing for efficient and configurable maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If automatic update tools are used to download and install software upgrades, then software currency is improved, but download time and network bandwidth consumption increase unreasonably

Engineering Contradiction:
Improvesoftware currencyVSAvoiddownload time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential upgrade information (upgrade ID, version, description, file size) from the full upgrade package and transmits it first. Users can then evaluate and select specific upgrades without downloading complete packages, dramatically reducing initial network time and bandwidth consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary actions by first checking for available upgrades, presenting them to users for evaluation, and obtaining user selection before initiating actual download and installation. This preliminary phase allows users to assess upgrade necessity and size commitments without time pressure.

Inventive Principle:
Principle #10Preliminary action

2Manufacturing precision

If users manually search for and evaluate upgrades, then upgrade selection accuracy is improved, but time and effort required increase considerably

Engineering Contradiction:
Improveupgrade selection accuracyVSAvoidtime for searching and evaluating upgrades
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system enables self-service by automatically detecting system configuration, identifying compatible upgrades, and presenting relevant options to users. This eliminates manual searching while maintaining accurate upgrade selection through automated compatibility checking and user-controlled evaluation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The upgrade management system performs multiple functions: automatic system analysis, upgrade compatibility checking, upgrade presentation, download management, and installation coordination. This multi-functional approach consolidates what would otherwise require separate manual operations into a single integrated process.

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

3Object-affected harmful factors

If latest software upgrades are installed to fix security vulnerabilities, then system security is improved, but risk of introducing new problems increases

Engineering Contradiction:
Improvesecurity vulnerabilitiesVSAvoidsystem stability
Core Design Contradiction:
Object-affected harmful factorsVSReliability

Solution Approach 1:

The system incorporates feedback mechanisms where users can report problems after upgrading, and the system tracks upgrade performance. This feedback loop allows for monitoring of newly installed upgrades and enables rollback or corrective actions if issues arise, balancing security improvements with system stability.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system prepares cushioning measures by maintaining backup versions of software components and enabling rollback capabilities before applying upgrades. This beforehand cushioning protects against potential upgrade failures while still allowing security-critical updates to be applied.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Reliability

If comprehensive upgrade checking is performed to ensure compatibility, then upgrade reliability is improved, but complexity of the upgrade process increases

Engineering Contradiction:
Improveupgrade compatibilityVSAvoidupgrade process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The upgrade process is segmented into distinct phases: system analysis, upgrade identification, compatibility verification, user presentation, selection, download, and installation. This segmentation makes the complex process more manageable and transparent to users while maintaining thorough compatibility checking in each phase.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7624393B2Computer application and methods for autonomic upgrade maintenance of computer hardware, operating systems and application software
Publication Date: 2009.11.24 GOOGLE LLC
  • US7624393B2 patent drawing
  • US7624393B2 patent drawing
  • US7624393B2 patent drawing

AI summary

The present invention provides methods and a computer-readable program for providing autonomic, event driven upgrade maintenance of one or more software modules residing on a computer system. In a preferred embodiment, a method begins by detecting a predefined triggering event on the computer system indicative of a potential maintenance issue. Next the computer system connects to an upgrade management server, where the upgrade maintenance server creates a list of recommended upgrade modules to download to the computer system, the list based upon the triggering event and a set of selection policies. The method then downloads the list of recommended upgrade modules from the upgrade management server to the computer system, and selectively installs upgrade modules chosen from the list of recommended upgrade modules on the computer system. The user is then notified of the status of the upgrade maintenance operation.