Targeted Crash Fix Distribution via Device Bucketing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for distributing crash fixes to client devices often consume excessive network bandwidth and computing resources, as all devices receive updates regardless of whether they have experienced a crash, even though only a small percentage may need them.

Innovation Solution

Client devices experiencing similar crashes are grouped into buckets, allowing targeted crash fixes to be generated and sent only to affected devices, reducing unnecessary resource usage and improving fix effectiveness.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If crash fixes are sent to all client devices, then all devices receive the fix, but network bandwidth and computing power are unnecessarily consumed

Engineering Contradiction:
Improvecrash fix delivery coverageVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent segments client devices into different buckets based on crash signatures. Devices experiencing the same crash are grouped together, allowing targeted distribution of crash fixes only to affected devices rather than all devices. This segmentation resolves the contradiction by maintaining reliable fix delivery to needed devices while reducing unnecessary bandwidth consumption from devices that don't need the fix.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by customizing the crash fix distribution strategy for different device groups based on their specific crash signatures. Each bucket receives tailored crash fixes relevant to their specific crash type, ensuring reliable delivery to devices that need it while avoiding unnecessary transmissions to devices with different crash profiles, thus reducing overall network bandwidth consumption.

Inventive Principle:
Principle #3Local quality

2Reliability

If crash fixes are sent to all client devices, then all devices receive the fix, but computing power is unnecessarily consumed

Engineering Contradiction:
Improvecrash fix delivery coverageVSAvoidcomputing power consumption
Core Design Contradiction:
ReliabilityVSUse of energy by stationary object

Solution Approach 1:

The patent segments client devices into different buckets based on crash signatures. Devices experiencing the same crash are grouped together, allowing targeted distribution of crash fixes only to affected devices rather than all devices. This segmentation resolves the contradiction by maintaining reliable fix delivery to needed devices while reducing unnecessary bandwidth consumption from devices that don't need the fix.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by sending crash fixes only to the subset of devices that actually need them (those in matching buckets), rather than performing the excessive action of sending fixes to all devices. This reduces computing power consumption for both server-side distribution and client-side processing while maintaining reliable delivery to devices that require the fix.

Inventive Principle:
Principle #16Partial or excessive action

3Loss of energy

If crash fixes are targeted to specific devices, then resource consumption is reduced, but fix delivery accuracy must be improved

Engineering Contradiction:
Improvenetwork bandwidth consumptionVSAvoidcrash signature matching accuracy
Core Design Contradiction:
Loss of energyVSMeasurement precision

Solution Approach 1:

The patent implements feedback mechanisms where client devices report crash signatures back to the server, and the server uses this feedback to refine bucket assignments and crash fix distributions. This feedback loop improves measurement precision of crash signature matching over time, ensuring accurate targeted delivery while maintaining reduced network bandwidth consumption.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent replaces traditional mechanical one-size-fits-all crash fix distribution with a data-driven system using crash signatures as identifiers. This substitution enables precise matching between crash types and fixes through signature analysis, improving measurement precision while maintaining the efficiency benefits of targeted distribution.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If multiple crash fixes are generated for different crashes, then specific crashes are addressed, but system complexity increases

Engineering Contradiction:
Improvecrash resolution effectivenessVSAvoidcrash fix management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple crash fix management operations into a unified bucket-based system. Devices experiencing different crashes are assigned to different buckets, and multiple crash fixes can be managed through a single coordinated distribution mechanism. This merging reduces system complexity while maintaining reliable resolution effectiveness for multiple different crash types.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal bucket assignment mechanism that handles multiple crash types through a single system framework. The same bucket assignment and fix distribution infrastructure serves multiple crash scenarios, reducing overall system complexity while maintaining the ability to effectively address specific crashes through targeted deliveries.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10198304B2Targeted crash fixing on a client device
Publication Date: 2019.02.05 VERIZON PATENT & LICENSING INC
  • US10198304B2 patent drawing
  • US10198304B2 patent drawing
  • US10198304B2 patent drawing

AI summary

Client devices having deployed an application may experience a crash of the application. For example, a first client device may experience a first crash having a first crash signature of the application. After experiencing the first crash, a first device identification of the first client device may be assigned to a first bucket designating one or more device identifications of client devices having experienced the first crash. Client devices having device identifications in the first bucket are provided with a first crash fix for the first crash, while a second client device is not provide with the first crash fix, where the application is deployed on the second client device and the second client device was not assigned to the first bucket.