Targeted Software Update Deployment via Device Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software updates often introduce unexpected side-effects on diverse devices due to varying hardware, software, and network conditions, requiring extensive validation across a wide range of devices without clear information on impacted devices, leading to unnecessary risks and inefficiencies.

Innovation Solution

A method and system for selectively communicating software updates to a subset of devices based on collected information about device characteristics and usage patterns, using agents to gather data and an analysis center to determine which devices should receive updates, simulating updates to identify beneficial deployments and avoid detrimental effects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If all application updates are published to all targeted devices, then the update coverage is maximized, but the risk of introducing side-effects increases

Engineering Contradiction:
Improveupdate deployment speedVSAvoidupdate stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the target device population into distinct groups based on device characteristics, usage patterns, and performance metrics. By dividing the update deployment into targeted segments rather than universal distribution, the system can control the spread of updates to minimize side-effects while maintaining deployment efficiency. Each segment receives updates based on its specific profile, allowing controlled rollout strategies.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameters of update deployment by introducing device-specific criteria such as device type, operating system version, hardware configuration, and usage patterns. Instead of using a single universal update parameter, the system adjusts update distribution based on multiple device parameters, enabling selective deployment that balances speed and stability.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If updates are validated across a huge range of devices, then the reliability of updates improves, but the time and resources required for validation increase

Engineering Contradiction:
Improveupdate validation completenessVSAvoidvalidation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial validation by focusing testing efforts on representative device profiles and critical update components rather than exhaustively testing every possible device configuration. By validating updates on a strategically selected subset of devices that represent the broader population, the system achieves sufficient reliability without the prohibitive time cost of complete validation across all devices.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent performs preliminary validation by pre-testing updates on device profiles that are predicted to be most susceptible to side-effects based on historical data and device characteristics. This preliminary action identifies potential issues before full deployment, allowing the system to maintain high reliability while reducing the overall validation time through targeted early testing.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If updates are deployed to devices without specific targeting, then the deployment process is simplified, but unnecessary risks are introduced

Engineering Contradiction:
Improvedeployment process simplicityVSAvoidside-effects on unaffected devices
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent implements self-service by enabling devices to automatically report their characteristics, performance metrics, and update responses to a central system. This self-reported data allows the system to automatically segment and target devices for updates without manual intervention, maintaining deployment simplicity while introducing intelligent targeting to prevent side-effects on unsuitable devices.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces feedback mechanisms where device performance data and update response information are continuously collected and used to refine targeting criteria. This feedback loop allows the system to learn from past update deployments and improve its targeting accuracy over time, reducing side-effects while maintaining operational simplicity through automated decision-making.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10572244B1Apparatus, computer program, and method for communicating an update to a subset of devices
Publication Date: 2020.02.25 AMDOCS DEV LTD
  • US10572244B1 patent drawing
  • US10572244B1 patent drawing
  • US10572244B1 patent drawing

AI summary

An apparatus, computer program, and method are provided for communicating an update to a subset of devices. In operation, information is received in association with a plurality of devices that have at least one application installed thereon. Further, an update for the at least one application is identified. Still yet, a subset of the plurality of devices is determined, based on the information. Such update for the at least one application is communicated to the subset of the plurality of devices.