Optimal Time Slot Determination for Application Upgrades

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The process of upgrading applications on computing devices often interrupts their operation due to the time required for reboots and dependency analysis, which is inefficient and disruptive.

Innovation Solution

A method and system that utilize device emulation to estimate the time needed for application upgrades, perform reboot-upgrade dependency analysis, and schedule upgrades optimally, allowing for parallel execution of reboots and applications to minimize downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If application upgrades are performed on computing devices, then the application version is updated, but the operation of the computing devices is interrupted due to reboots and dependency analysis

Engineering Contradiction:
Improveapplication versionVSAvoidoperation interruption time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs upgrade time estimation and dependency analysis before the actual application upgrade is executed. By analyzing the upgrade requirements and estimating the time needed for reboots and dependencies in advance, the system can schedule upgrades during periods of minimal impact, thus reducing operation interruption time while ensuring the upgrade is properly executed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically schedules application upgrades based on real-time conditions such as device usage patterns, criticality levels, and estimated upgrade times. Instead of using a static upgrade schedule, the system adapts the timing and sequencing of upgrades to minimize disruption to computing device operations while ensuring all necessary reboots and dependencies are accommodated.

Inventive Principle:
Principle #15Dynamics

2Reliability

If reboots are performed during application upgrades, then the upgrade can be completed, but the computing device operation is disrupted

Engineering Contradiction:
Improveupgrade completionVSAvoiddevice operation continuity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs reboot-upgrade dependency analysis before executing upgrades, identifying which devices require reboots and when they are needed. By knowing the reboot requirements in advance, the system can schedule reboots during maintenance windows or low-usage periods, ensuring upgrade completion while minimizing disruption to device operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system monitors the status of computing devices during the upgrade process and adjusts the schedule based on real-time feedback. If a device is experiencing high usage or critical operations, the system can delay non-critical reboots or upgrades, providing feedback-driven dynamic scheduling that balances upgrade completion with operational continuity.

Inventive Principle:
Principle #23Feedback

3Ease of manufacture

If application upgrades are scheduled without optimization, then the upgrade process is simple, but the number of reboots and interruption time increases

Engineering Contradiction:
Improveupgrade scheduling simplicityVSAvoidupgrade efficiency
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The system performs comprehensive upgrade time estimation and dependency analysis before scheduling upgrades. By calculating the time required for each upgrade, including reboots and dependencies, in advance, the system can generate an optimized schedule that minimizes total interruption time and coordinates reboots efficiently, thereby improving upgrade efficiency without significantly complicating the scheduling process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses dynamic scheduling algorithms that automatically optimize upgrade sequences based on device criticality, usage patterns, and dependency relationships. This dynamic approach improves upgrade efficiency by reducing the number of reboots and minimizing interruption time, while the automation keeps the ease of manufacture at an acceptable level.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11922180B2System and method for an optimal time slot determination for an application upgrade in a customer environment
Publication Date: 2024.03.05 EMC IP HLDG CO LLC
  • US11922180B2 patent drawing
  • US11922180B2 patent drawing
  • US11922180B2 patent drawing

AI summary

A method for managing a client environment includes obtaining, by a client device upgrade manager, an upgrade estimation for a client device executing in the client environment, wherein the upgrade estimation corresponds to an application upgrade for an application, in response to the upgrade estimation: performing an optimal time slot analysis for the client device to identify a set of optimal time slots, presenting the set of optimal time slots to the client device, obtaining, by the client device, a requested time slot for the application, and in response to the requested time slot, initiating an installation of an application upgrade of the application.