Software Update Stability Index via Telemetry Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manufacturers of computing devices face challenges in determining the stability of software updates across various hardware and software configurations, leading to potential destabilization of computing systems, especially since they cannot test updates on all possible configurations and configurations.

Innovation Solution

A server system that collects telemetry data from computing devices, determines a stability index based on device configuration and installation events, and provides this index to other devices, allowing users to decide whether to install software updates based on their preferences and the stability index threshold.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If software updates are deployed to all computing devices, then the coverage and utility of updates are improved, but the risk of system instability increases due to untested hardware and software configurations

Engineering Contradiction:
Improvesoftware update coverageVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the software update deployment process by creating configuration-specific stability indices. Instead of treating all devices uniformly, the system divides updates into groups based on hardware and software configurations, calculating separate stability indices for each segment. This allows targeted deployment to specific configuration groups while avoiding instability in other segments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary actions by collecting telemetry data and calculating stability indices before deploying software updates. The system proactively gathers installation events, system stability data, and configuration information in advance, then uses this data to predict which configurations will be stable with the update before actually deploying it, preventing instability rather than reacting to it afterward.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If software updates are tested on all possible hardware and software configurations, then the reliability of updates is improved, but the time and resources required for testing increase significantly

Engineering Contradiction:
Improveupdate stabilityVSAvoidtesting duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements self-service by having computing devices automatically report their own configuration data and installation events to the server. Instead of requiring manual testing on every configuration, the system leverages the devices themselves to generate the test data through normal operation, with telemetry agents collecting and transmitting stability information back to the update server for analysis.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent establishes a feedback loop where telemetry data from deployed updates flows back to the server, which then recalculates stability indices based on real-world performance. This continuous feedback mechanism allows the system to improve reliability over time by learning from actual deployment outcomes, rather than relying solely on pre-deployment testing.

Inventive Principle:
Principle #23Feedback

3Productivity

If users install software updates to maintain system functionality, then the usefulness of the system is improved, but the risk of introducing errors and instability increases

Engineering Contradiction:
Improvesystem functionalityVSAvoiderror-free operation
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies dynamics by making the update deployment decision adaptive rather than static. The system continuously updates stability indices based on incoming telemetry data, allowing the recommendation to install or defer updates to change dynamically as more information becomes available. Users receive customized, time-varying guidance based on their specific configuration's observed stability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of update deployment from a binary yes/no decision to a probabilistic assessment based on stability indices. By transforming the decision parameter into a quantitative measure (the stability index) that incorporates configuration-specific telemetry data, the system enables users to make informed decisions about whether the productivity benefit of an update outweighs the stability risk for their particular system.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10732957B2Determining a stability index associated with a software update
Publication Date: 2020.08.04 DELL PROD LP
  • US10732957B2 patent drawing
  • US10732957B2 patent drawing
  • US10732957B2 patent drawing

AI summary

In some examples, a server may receive telemetry data from a computing device. The server may determine based at least in part on the telemetry data, (1) a device (e.g., hardware and software) configuration associated with the computing device and (2) one or more events (e.g., an installation log, a memory dump, or the like) associated with installing a software package on the computing device. Based at least in part on the one or more events. the server may determine a stability index associated with the software package and associate the stability index with the device configuration. The stability index may indicate a probability of errors not occurring after the software package is installed. After determining that the stability index satisfies a predetermined threshold, the server may provide the software package and the associated stability index for download to one or more additional computing devices.