Update Management Module Delaying System Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computing systems face challenges in updating software components, as updates may require reboots or alter approved software versions, disrupting critical processes or system configurations, leading to administrative overhead and potential performance issues.

Innovation Solution

An update management module configures the system to delay updates by determining whether an update should be blocked and reconfiguring the system to operate without the targeted configuration, using alternative settings to avoid necessary updates and minimize disruption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If system updates are applied automatically, then software components are kept up-to-date and security is improved, but system stability deteriorates due to required reboots and potential disruption of critical processes

Engineering Contradiction:
Improvesystem stabilityVSAvoidcontinuous operation
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary evaluation of update descriptors against configured criteria before applying updates. The update management module determines in advance whether an update should be blocked by checking if the computing system can be reconfigured to avoid the update, thereby preventing disruptive reboots before they occur.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts update behavior based on real-time system state and configured criteria. The update management module can block or allow updates based on current conditions, enabling flexible control that adapts to changing system requirements and operational contexts.

Inventive Principle:
Principle #15Dynamics

2Productivity

If system updates are delayed to avoid reboots, then continuous operation is maintained, but software security and functionality deteriorate due to unpatched vulnerabilities

Engineering Contradiction:
Improvecontinuous operationVSAvoidsoftware security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system evaluates update descriptors in advance and determines whether updates should be blocked based on pre-configured criteria. This preliminary action allows the system to maintain continuous operation when updates are non-critical while still having a mechanism to apply security updates when necessary.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The update management module uses feedback from update descriptors and system state to make intelligent decisions about when to block updates. The system continuously monitors whether updates can be safely delayed based on current operational conditions and configured priorities.

Inventive Principle:
Principle #23Feedback

3Reliability

If update criteria are strictly enforced to maintain approved software versions, then system compliance is improved, but system flexibility deteriorates due to inability to adapt to changing operational needs

Engineering Contradiction:
Improvecompliance with approved versionsVSAvoidsystem flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically adjusts update behavior based on real-time system state and configured criteria. The update management module can block or allow updates based on current conditions, enabling flexible control that adapts to changing system requirements while maintaining compliance when necessary.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes operational parameters based on update descriptor analysis. By modifying criteria evaluation results dynamically, the system can maintain compliance with approved software versions in some contexts while allowing flexibility in others, depending on the specific update characteristics and system state.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9426028B2Configuring a computing system to delay a system update
Publication Date: 2016.08.23 LENOVO GLOBAL TECHNOLOGIES SWITZERLAND INTERNATIONAL GMBH
  • US9426028B2 patent drawing
  • US9426028B2 patent drawing
  • US9426028B2 patent drawing

AI summary

Configuring a computing system to delay a system update, including: receiving, by an update management module, an update descriptor associated with an available system update, the update descriptor including information identifying a targeted system configuration to be updated by the available system update; determining, by the update management module, whether the available system update should be blocked; responsive to determining that the available system update should be blocked, determining, by the update management module, whether the computing system can be reconfigured such that the computing system does not operate using the targeted system configuration; and responsive to determining that the computing system can be reconfigured such that the computing system does not operate using the targeted system configuration, reconfiguring, by the update management module, the computing system to operate without using the targeted system configuration.