Mobile Device Background Data Restriction Service

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Smartphone users experience slow service and dropped calls due to wireless network congestion caused by multiple devices attempting data communications in close proximity, which existing technologies fail to effectively mitigate without reducing user functionality.

Innovation Solution

Implementing a background application data restriction service in mobile devices that detects network congestion and restricts data communications from background applications, allowing essential user interactions while reducing network load.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the wireless network allows all applications to establish data communications freely, then application functionality is maintained, but network congestion increases causing slow service and dropped calls

Engineering Contradiction:

Improveapplication functionalityVSAvoidnetwork service quality

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments data communication requests into foreground and background applications. Foreground applications (actively used by users) are allowed to communicate freely, while background applications (running without user interaction) are restricted during congestion periods. This segmentation resolves the contradiction by maintaining full functionality for essential user interactions while limiting non-essential traffic that contributes to congestion.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic traffic management where the network adapts its behavior based on real-time congestion conditions. When congestion is detected, the network dynamically adjusts by applying different policies to different applications (foreground vs. background). This dynamic approach allows the system to maintain reliability during congestion while preserving application versatility when conditions permit.

Inventive Principle:

Principle #15Dynamics

2Loss of energy

If the wireless network rejects successive data communication requests to relieve congestion, then network load is reduced, but additional load is generated and congestion is exacerbated

Engineering Contradiction:

Improvenetwork loadVSAvoidcongestion management effectiveness

Core Design Contradiction:

Loss of energyVSReliability

Solution Approach 1:

The patent applies local quality by treating different types of traffic differently rather than applying a uniform rejection policy. Background application traffic is selectively restricted while foreground application traffic continues uninterrupted. This targeted approach reduces network load from non-essential sources without generating the additional load that comes from blanket rejection mechanisms, thereby improving congestion management effectiveness.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent introduces an intermediary mechanism (the background application restriction service) that mediates between background applications and the network. This intermediary filters and controls background traffic before it reaches the network, reducing load proactively rather than reactively rejecting requests. This prevents the exacerbation of congestion that occurs when rejection mechanisms generate additional signaling and processing load.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If background application data communications are restricted during congestion, then network congestion is reduced, but user experience may be impacted

Engineering Contradiction:

Improvenetwork congestion controlVSAvoiduser experience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent segments applications into foreground and background categories, ensuring that only background applications are restricted during congestion. Foreground applications, which represent active user interactions, continue to operate without limitation. This segmentation resolves the contradiction by protecting user experience (through foreground application continuity) while achieving congestion control (through background application restriction).

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system automatically detects congestion conditions and applies appropriate restrictions without requiring user intervention or awareness. Users experience no impact on their active applications, while the system self-manages the restriction of background traffic to control congestion. This self-service approach maintains ease of operation while achieving reliability goals.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS9277444B2Restriction of background application data during congestion

Publication Date: 2016.03.01 CELLCO PARTNERSHIP INC

AI summary

To reduce the contribution of data communications for background applications to network congestion, the examples implement techniques in which congestion detection leads a mobile device to impose restriction on data communications by any application running in the background. The mobile device may detect congestion and/or the need to restrict background data communications in response to a message or instruction received from a node of the network; or the mobile device may itself more directly detect congestion from monitoring and analysis of device/network interaction behavior and trends. Upon detecting congestion, the mobile device turns on a background data restriction. For example, with the restriction on, all applications only running in the background without direct user interaction are blocked from sending requests for data communication to/through the network. However, with the restriction active, the mobile device can still provide data communication in response to user interaction with the device.