Application Update Notification Thresholds

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network-based application distribution systems face challenges in providing a user-friendly experience for software updates, as current authorization and notification protocols are often non-intuitive and burdensome, leading to inefficient update processes that can disrupt user activities and incur unnecessary cellular charges.

Innovation Solution

Implementing server-based user authentication, batching notifications, and optimizing update prompts based on network conditions and user preferences, including only prompting users when a threshold of updates is available or when connected to a Wi-Fi network, to streamline the update process and reduce interruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If frequent authorization checks are implemented to ensure security, then system security is improved, but user experience deteriorates due to tedious and burdensome prompts

Engineering Contradiction:
Improvesystem securityVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary authentication by obtaining user identification information in advance and verifying it against account information stored on the server. This preliminary check establishes user identity before the update process begins, allowing subsequent authorization steps to be streamlined or eliminated, thus maintaining security while reducing the burden of frequent prompts during the update process

Inventive Principle:
Principle #10Preliminary action

2Productivity

If users are prompted frequently to check for updates, then application update timeliness is improved, but user experience deteriorates due to overwhelming notifications and interruptions

Engineering Contradiction:
Improveapplication update timelinessVSAvoiduser experience
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

Instead of continuous or frequent prompting, the system implements periodic update checks at predetermined intervals. The server automatically checks for updates at these intervals and only notifies users when updates are actually available, reducing notification frequency while ensuring timely update delivery when needed

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system enables automatic update checking and notification delivery without requiring active user initiation. The server autonomously manages the update checking process and selectively notifies users based on update availability, reducing unnecessary user interactions while maintaining update timeliness

Inventive Principle:
Principle #25Self-service

3Reliability

If updates are downloaded immediately when available, then application security and functionality are improved, but cellular data costs increase and network resources are wasted

Engineering Contradiction:
Improveapplication securityVSAvoidcellular data usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary checks to determine update availability and evaluates network conditions before initiating downloads. By checking network type and user preferences in advance, the system can identify optimal download opportunities that balance security needs with data conservation, downloading only when conditions are favorable

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts update download behavior based on real-time network conditions and user preferences. When connected to Wi-Fi or when data usage is acceptable, updates are downloaded; when cellular data would be excessive, downloads are deferred or blocked, creating a flexible approach that adapts to changing conditions

Inventive Principle:
Principle #15Dynamics

4Reliability

If multiple authorization requests are presented sequentially for each update, then security verification is improved, but update installation time increases due to tedious user interactions

Engineering Contradiction:
Improveauthorization securityVSAvoidupdate installation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system merges multiple authorization requests into a single consolidated notification presented to the user. Instead of requiring separate user interactions for each update's authorization, the system combines all necessary authorizations into one batched request, maintaining security verification while dramatically reducing the time and user effort required

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12019750B2Authentication and notification heuristics
Publication Date: 2024.06.25 APPLE INC
  • US12019750B2 patent drawing
  • US12019750B2 patent drawing
  • US12019750B2 patent drawing

AI summary

Systems and methods for providing updates to an electronic device are provided. Upon receiving an update statement, indicating availability of an update to an application on an electronic device, a determination is made as to whether an update notification threshold has been met at the electronic device based upon the indication of availability of the update to the application. When the update notification threshold has been met at the electronic device, a graphical indication of the availability of the update to the application is provided. However, when the update notification threshold has not been met, the graphical indication of the availability of the update to the application is not provided.