Application Upgrade Scheduling with Dependency Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The time taken to upgrade applications on computing devices often interrupts their operation, and existing methods lack efficiency in managing reboots and dependencies during the upgrade process.

Innovation Solution

A method and system that utilize device emulation to estimate the time required for application upgrades, perform reboot-upgrade dependency analysis, and schedule upgrades optimally, while also monitoring and resolving issues using an issue analyzing model to minimize downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If application upgrades are performed on computing devices, then application versions are updated, but operation interruption time increases

Engineering Contradiction:
Improveapplication version currencyVSAvoidoperation interruption time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by analyzing upgrade dependencies and scheduling upgrades in advance. The server determines the optimal upgrade sequence by analyzing dependencies between applications and their associated reboots, then schedules upgrades during periods of low device usage, thereby reducing actual operation interruption time while ensuring applications are updated to current versions.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple application upgrades are performed sequentially, then all upgrades are completed, but total upgrade time increases

Engineering Contradiction:
Improveupgrade completionVSAvoidtotal upgrade time
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The system merges multiple upgrade operations by identifying applications that can be upgraded simultaneously without conflict. The dependency analysis determines which applications have no inter-dependent reboots, allowing their upgrades to be combined into a single coordinated operation, thereby reducing total upgrade time while ensuring all upgrades are completed reliably.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system dynamically adjusts the upgrade schedule based on real-time dependency analysis. Rather than following a fixed sequential order, the server continuously evaluates which upgrades can proceed in parallel by analyzing reboot dependencies, dynamically optimizing the upgrade timeline to minimize total duration while maintaining reliability.

Inventive Principle:
Principle #15Dynamics

3Reliability

If reboot operations are performed for each application upgrade, then all upgrades are applied, but device downtime increases

Engineering Contradiction:
Improveupgrade application successVSAvoiddevice downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system applies preliminary anti-action by identifying and eliminating redundant reboot operations before they occur. The dependency analysis detects when multiple application upgrades share common reboot requirements, and the scheduler consolidates these into a single reboot operation, thereby preventing unnecessary downtime while ensuring all upgrades are successfully applied.

Inventive Principle:
Principle #9Preliminary anti-action

Solution Approach 2:

The system creates a logical model of upgrade dependencies and reboot requirements, then uses this copied representation to optimize the actual upgrade execution. By analyzing the dependency graph and identifying shared reboot operations, the system can schedule upgrades to minimize redundant reboots, reducing device downtime while maintaining upgrade success rates.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11960873B2System and method for managing a model for solving issues using a set of actions performed on the client environment
Publication Date: 2024.04.16 DELL PROD LP
  • US11960873B2 patent drawing
  • US11960873B2 patent drawing
  • US11960873B2 patent drawing

AI summary

A method for managing a client environment includes obtaining, by a client environment watcher of a production host environment, a set of actions performed by the client environment operatively connected to the production host environment, in response to obtaining the set of actions: performing an action filtering on the set of actions to obtain a set of filtered actions, wherein the set of filtered actions is associated with an attempt to resolve an issue with performing an application upgrade on the client environment, determining, using the set of filtered actions, a client-applied action set, and initiating an update to an issue analyzer model to obtain an updated issue analyzer model.