Software Update Deployment Risk Prediction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manufacturers of computing devices face challenges in deploying software updates across diverse device configurations, leading to high failure rates and customer inconvenience due to the inability to test updates on all possible hardware and software variations.

Innovation Solution

A server determines a risk score for software updates using machine learning models, considering variables such as package size, reboot requirements, and deployment timing, to select an optimal deployment strategy, ensuring successful installation on multiple computing devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If software updates are deployed to all computing devices without prior testing on each configuration, then deployment speed and coverage are improved, but failure rate increases

Engineering Contradiction:
Improvedeployment speedVSAvoidinstallation success rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary testing on a representative sample of computing devices before full deployment. A risk score is calculated based on testing results, package characteristics, and device configurations to predict potential failures. This preliminary assessment allows the system to prepare mitigation strategies in advance, such as staged rollouts or targeted deployments to specific device profiles, thereby maintaining high deployment speed while preventing widespread failures.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If software updates are tested on all possible device configurations, then installation success rate is improved, but testing time and complexity increase

Engineering Contradiction:
Improveinstallation success rateVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system changes the parameter of testing scope from exhaustive (all configurations) to optimized (representative sample). By analyzing device configuration distributions and identifying critical test cases, the system determines a sufficient subset of devices that captures the diversity of the full population. The risk score calculation incorporates package size, complexity, and device compatibility factors to adjust testing requirements dynamically, reducing testing time while maintaining reliability.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If software updates are deployed with high risk scores, then deployment coverage is improved, but customer inconvenience increases

Engineering Contradiction:
Improvedeployment coverageVSAvoidcustomer inconvenience
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The system applies partial deployment strategies based on risk scores. For updates with elevated risk scores, deployment is restricted to specific device configurations, geographic regions, or user segments rather than universal deployment. This partial action allows the system to maintain deployment coverage for low-risk scenarios while protecting high-risk users from potential failures, thereby balancing productivity with customer experience.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If software updates are thoroughly tested and validated before deployment, then installation success rate is improved, but deployment delay increases

Engineering Contradiction:
Improveinstallation success rateVSAvoiddeployment time
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The system performs critical validation checks and risk assessments in advance of full deployment. By pre-calculating risk scores based on package characteristics, historical data, and device compatibility, the system identifies potential issues before they affect end users. This preliminary action enables rapid deployment decisions without sacrificing thoroughness, as the heavy lifting of analysis is completed beforehand.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10789057B2Predicting a success rate of deploying a software bundle
Publication Date: 2020.09.29 DELL PROD LP
  • US10789057B2 patent drawing
  • US10789057B2 patent drawing
  • US10789057B2 patent drawing

AI summary

In some examples, a server may determine a plurality of variables associated with a software package. For example, the plurality of variables may include a size of the software package, a reboot variable associated with the software package indicating whether a reboot is to be performed after installing the software package, and an installation type indicating whether the software package is a first install or an upgrade. The server may execute a machine learning model to determine, based on the plurality of variables, a risk score predicting an installation success rate of the software package. The server may select a deployment strategy from a plurality of deployment strategies based at least in part on the risk score and the plurality of variables. The server may provide the software package to a plurality of computing devices in accordance with the deployment strategy.