Component Update Failure Management via Metadata Classification

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Information handling systems face challenges in managing failures during component updates, particularly in distinguishing between critical and non-critical components and applying appropriate remediation policies to ensure system stability and efficiency.

Innovation Solution

The implementation of an update management computing module that identifies component classifications based on metadata, applies remediation policies such as rollback for critical components and logging for non-critical components, and prevents or allows update package applications accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If update packages are applied to all components uniformly, then system-wide updates are achieved, but critical system stability is compromised when failures occur

Engineering Contradiction:

Improveupdate application speedVSAvoidsystem stability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent segments components into critical and non-critical subsets based on metadata classification. This segmentation allows differential update management where critical components (those affecting system stability) receive rollback protection while non-critical components proceed with updates, thus resolving the contradiction between update speed and system stability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by implementing different update policies for different component subsets. Critical components receive protective rollback mechanisms while non-critical components receive permissive update policies, allowing the system to optimize for both speed and stability in appropriate locations.

Inventive Principle:

Principle #3Local quality

2Reliability

If rollback protection is applied to all components, then system stability is maintained, but update efficiency decreases due to unnecessary rollbacks of non-critical components

Engineering Contradiction:

Improvesystem stabilityVSAvoidupdate efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of update policy protection based on component classification. By dynamically adjusting the level of protection (rollback enabled vs. rollback disabled) according to component criticality metadata, the system optimizes both stability and efficiency.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If component classifications are implemented, then appropriate remediation policies can be applied, but system complexity increases due to metadata management

Engineering Contradiction:

Improvefailure management accuracyVSAvoidmetadata management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary classification of components into critical and non-critical subsets before update operations begin. By pre-establishing metadata classifications and remediation policies, the system avoids complex real-time decision-making during updates, simplifying the update execution process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces metadata as an intermediary layer between components and update policies. This metadata classification system acts as a mediator that automatically determines appropriate remediation actions, reducing the complexity of direct policy-component matching.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Loss of information

If failures are logged for non-critical components, then failure information is captured, but additional processing overhead is introduced

Engineering Contradiction:

Improvefailure information retentionVSAvoidupdate processing speed

Core Design Contradiction:

Loss of informationVSProductivity

Solution Approach 1:

The patent segments failure management actions based on component classification. Non-critical components receive logging-only treatment while critical components receive rollback protection, optimizing the balance between information retention and processing speed for different component types.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11593211B2Applying a failure management policy during updating of components at an information handling system

Publication Date: 2023.02.28 DELL PROD LP

AI summary

Applying failure policy during updating of components, including receiving metadata of each of the components, the metadata indicating a respective classification of each of the components; sorting the components based on the metadata, including identifying a first subset of the components as critical components and a second subset of the components as non-critical components; receiving a first update package for a first component; detecting a failure to apply the first update package to the first component; in response to detecting the failure to apply the first update package to the first component: determining that the first component belongs to the first subset of components; in response to determining that the first component belongs to the first subset of components, identifying a remediation policy associated with critical components; applying the remediation policy to the first component, including rollback of the first update package at the first component.