Context-Aware Maintenance Window Identification for IHS

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional firmware update maintenance windows in high-component, hyperconverged infrastructure systems are often disruptive due to their agnostic approach to workload and clustering, leading to long service disruptions as they are not context-aware.

Innovation Solution

The system estimates completion time of maintenance operations using historical logs and adds a buffer, predicts future usage through multivariate time series analysis, and identifies optimal maintenance windows based on usage patterns and context information such as user distance and device posture.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional maintenance window schedules are used for firmware updates, then updates can be performed systematically, but service disruption time increases due to lack of workload awareness

Engineering Contradiction:
Improvefirmware update completionVSAvoidservice disruption time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The maintenance window identification is made dynamic by continuously analyzing workload patterns, usage statistics, and performance metrics to adaptively determine optimal update timing. The system transitions from static scheduled maintenance to dynamic context-aware maintenance that responds to real-time system conditions, thereby reducing service disruption while ensuring update completion.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary analysis of workload patterns and usage statistics before determining maintenance windows. By proactively identifying periods of low activity and predicting future usage patterns, the system can schedule firmware updates in advance during optimal times, minimizing service disruption while ensuring updates are completed before high-demand periods.

Inventive Principle:
Principle #10Preliminary action

2Ease of manufacture

If maintenance windows are scheduled without context awareness, then scheduling is simple, but system performance and availability are negatively impacted

Engineering Contradiction:
Improvemaintenance scheduling simplicityVSAvoidsystem availability
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The system performs self-service by automatically analyzing its own workload patterns, usage statistics, and performance metrics to identify optimal maintenance windows. This eliminates the need for manual context assessment while maintaining high system availability, as the system autonomously determines when to schedule firmware updates based on its own operational characteristics.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring workload patterns, usage statistics, and performance metrics, then using this information to refine maintenance window identification. This closed-loop approach ensures that maintenance scheduling progressively improves system availability while maintaining operational simplicity through automated decision-making.

Inventive Principle:
Principle #23Feedback

3Duration of action of moving object

If firmware updates are performed during high-usage periods, then maintenance can be completed quickly, but service disruption and performance degradation increase

Engineering Contradiction:
Improveupdate completion speedVSAvoidservice disruption impact
Core Design Contradiction:
Duration of action of moving objectVSObject-affected harmful factors

Solution Approach 1:

The system identifies and skips high-usage periods for maintenance operations by analyzing workload patterns in real-time. When high-demand periods are detected, the system automatically reschedules firmware updates for lower-usage times, effectively skipping the harmful high-traffic windows while maintaining efficient update completion through proactive timing.

Inventive Principle:
Principle #21Skipping (Rushing through)

Data Source

PatentUS11921735B2Context-aware maintenance window identification
Publication Date: 2024.03.05 DELL PROD LP
  • US11921735B2 patent drawing
  • US11921735B2 patent drawing
  • US11921735B2 patent drawing

AI summary

Systems and methods are provided for context-aware maintenance window identification. In some embodiments, an Information Handling System (IHS) may include a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution, cause the IHS to: estimate a completion time of a maintenance operation; predict future usage of the IHS; identify a time window for the maintenance operation based upon the estimation and the prediction.