Application Version Management via Crash Threshold Switching

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing application management systems face challenges in efficiently identifying and addressing issues caused by specific versions of applications that result in frequent crashes, leading to user dissatisfaction and increased support costs.

Innovation Solution

A computer-implemented method and system that analyzes crash reports from multiple computing devices to determine when a threshold of crashes is exceeded, allowing for automatic switching to a different version of the application that has corrected the issue, ensuring users receive updates from the stable version, thereby preventing further crashes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If a single version of an application is distributed to multiple devices, then deployment simplicity is improved, but system reliability deteriorates when that version contains bugs causing crashes

Engineering Contradiction:

Improvedeployment simplicityVSAvoidapplication stability

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The patent segments the application into multiple version groups (first group of versions, second group of versions) that can be independently distributed. When crashes are detected in one version group, the system can switch to a different version group without requiring complete redeployment, thus maintaining reliability while preserving deployment simplicity through automated version management.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system changes the version parameter dynamically based on crash detection. When the first version group causes excessive crashes, the system automatically switches to providing a second version group, adjusting the version parameter to restore reliability without manual intervention.

Inventive Principle:

Principle #35Parameter changes

2Measurement precision

If crash reports are manually analyzed to identify problematic versions, then diagnostic accuracy is improved, but response time deteriorates

Engineering Contradiction:

Improvediagnostic accuracyVSAvoidresponse time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The system performs self-service by automatically analyzing crash reports, identifying problematic version groups, and switching to alternative versions without human intervention. The crash reporting mechanism automatically collects data, the system processes this data to determine version stability, and autonomously makes version switching decisions, eliminating manual analysis delays while maintaining diagnostic accuracy through systematic evaluation of crash patterns.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The system implements continuous feedback loops where crash reports from multiple devices are collected and analyzed to determine version stability. This feedback mechanism automatically triggers version group switching when crash thresholds are exceeded, enabling rapid response time while maintaining diagnostic accuracy through systematic evaluation of crash patterns across the device fleet.

Inventive Principle:

Principle #23Feedback

3Reliability

If multiple version groups are maintained for different devices, then application reliability is improved, but system complexity increases

Engineering Contradiction:

Improveapplication stabilityVSAvoidversion management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a version management intermediary system that handles the complexity of managing multiple version groups. This intermediary automatically selects which version group to provide to devices based on crash analysis, shielding end users and device operators from the complexity of version management while maintaining high reliability through automated version switching.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs self-service by automatically managing multiple version groups without requiring manual intervention. The version management system autonomously monitors crash patterns, determines version stability, and switches between version groups as needed, reducing perceived complexity for users while maintaining the benefits of multiple versions for reliability.

Inventive Principle:

Principle #25Self-service

4Productivity

If automatic version switching is implemented based on crash thresholds, then productivity is improved by reducing support costs, but measurement precision requirements increase

Engineering Contradiction:

Improvesupport efficiencyVSAvoidcrash threshold accuracy

Core Design Contradiction:

ProductivityVSMeasurement precision

Solution Approach 1:

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS8892954B1Managing groups of application versions

Publication Date: 2014.11.18 GOOGLE LLC

AI summary

The subject matter of this specification can be implemented in, among other things, a computer-implemented method for application lifecycle management. The method includes receiving crash reports from a first version of an application at multiple initial computing devices. The first version of the application is from a first group of versions. The method further includes determining that the crash reports include more than a threshold amount of crash reports. The method further includes determining that a second version of the application from a second group of versions corrects a cause of the crash reports. The method further includes providing instructions to the initial computing devices to retrieve updates to the application from the second group of versions rather than the first group of versions.