IP Library Granted Patent US 9,158,530
Granted Patent B2
US 9,158,530 · App. 14/059,787 · Granted Oct 13, 2015

Assigning severity to a software update

Inventors: Albert D. Bennah (Cary, NC); Adrian X. Rodriguez (Durham, NC)
Assignee: International Business Machines Corporation
G06F8/65G06F3/1204G06F3/1207
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,158,530
App. No.
14/059,787
Granted
Oct 13, 2015
Kind
B2
Abstract

Assigning severity to a software update, including: receiving, by an update manager, version information for a software application from a computing system, the version information describing a version of the software application installed on the computing system; determining, by the update manager, a severity level of one or more available updates for the software application in dependence upon the version information and update version information; and providing, by the update manager to the computing system, the severity level for each of the one or more available updates.

Claims (13)

1. A processor-implemented method of assigning severity to a software update, the method comprising:

receiving, by an update manager, version information for a software application from a computing system, the version information describing a version of the software application installed on the computing system;

determining, by the update manager, a severity level of one or more available updates for the software application in dependence upon the version information and update version information, including:

determining a number of updates between the version of the software application installed on the computing system and each of the one or more available updates for the software application; and

determining the severity level of one or more available updates for the software application in dependence upon a plurality of predetermined thresholds and the number of updates between the version of the software application installed on the computing system and each of the one or more available updates for the software application; and

providing, by the update manager to the computing system, the severity level for each of the one or more available updates;

determining, by the update manager, an update path between the version of the software application installed on the computing system and each of the one or more available updates for the software application;

selecting, in dependence upon the severity level for each of the one or more available updates, an update for installation on the computing system; and

installing the update selected for installation on the computing system, including installing each update in the update path between the version of the software application installed on the computing system and the update selected for installation on the computing system.

2. The method of claim 1 wherein determining the severity level of one or more available updates for the software application in dependence upon the version information and update version information further comprises:

determining a criticality level associated with each of the one or more available updates for the software application; and

determining the severity level of one or more available updates for the software application in dependence upon the criticality level associated with each of the one or more available updates for the software application.

3. The method of claim 1 wherein the computing system is configured to automatically update based on the severity level of one or more available updates for the software application.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 22, 2013
From: BENNAH, ALBERT D.; RODRIGUEZ, ADRIAN X.
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 031467/0251 →
Continuity (2)
Continuation 14057378 · Oct 18, 2013
Related Publication 20150113517A1 · Apr 23, 2015