Staggered Background Data Re-enabling to Prevent Network Congestion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Wireless network congestion caused by multiple smartphones in close proximity leads to slow service and dropped calls, as background applications continue to consume network resources without user intervention, exacerbating congestion and requiring additional network infrastructure during peak demand.
Innovation Solution
Mobile devices detect network congestion and independently restrict background application data communications, then stagger the re-enablement of these services to avoid re-introducing congestion by calculating a unique wait time before resuming data communications, thereby distributing the reactivation across devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If background applications are allowed to establish data communications freely, then application functionality is maintained, but network congestion increases during peak usage periods
Solution Approach 1:
The system performs preliminary actions by detecting network congestion conditions and proactively restricting background application data communications before congestion severely impacts service quality. The mobile device monitors network conditions and preemptively blocks background data transmissions when congestion is detected, preventing further deterioration of network performance.
Solution Approach 2:
The system implements periodic action through calculated wait times before re-enabling background data communications. After congestion conditions subside, the device does not immediately restore all background communications, but instead implements a staggered re-enabling approach with randomized delays, allowing the network to recover gradually and avoid re-triggering congestion.
2Object-affected harmful factors
If the wireless network rejects successive requests to relieve congestion, then network load is reduced, but additional load is generated on the network and congestion is exacerbated
Solution Approach 1:
The harmful element of background data communications is extracted and isolated from the overall communication process. The system selectively blocks background application data transmissions while allowing foreground communications to proceed normally. This extraction approach removes the congesting element without disrupting essential user interactions and service operations.
Solution Approach 2:
The mobile device autonomously monitors its own network conditions and self-regulates background data communications without requiring external network control. The device independently detects congestion, implements restrictions, and manages re-enabling of background services, reducing the signaling overhead and control burden on the network infrastructure.
3Reliability
If background application data communications are restricted during congestion, then network service quality is improved, but re-enabling all communications simultaneously may re-introduce congestion
Solution Approach 1:
The system performs preliminary actions by implementing a calculated wait time mechanism before re-enabling background data communications. This preliminary delay allows the network to fully recover from congestion conditions and prevents the immediate re-triggering of congestion when background services are restored. The wait time is randomized to distribute re-enabling events across multiple devices.
Solution Approach 2:
The system implements dynamic control of background data communications by adjusting the re-enabling timing based on network conditions and device-specific factors. The calculated wait time varies between devices and is dynamically determined based on congestion duration, severity, and network recovery status, creating a flexible and adaptive congestion management approach.
Data Source
AI summary
To reduce the potential for renewed network congestion after a need for a restriction of data communications for background applications has been eliminated, the examples implement techniques in which a mobile device calculates a distributed deactivation delay value corresponding to an amount of time to wait before deactivating the restriction. The mobile device may generate a seed value unique to the mobile device for use in generating an initial distributed deactivation delay value and random control values generated by a threshold determination. The threshold determination iterates through generating a respective control value and calculating a respective threshold value until either a relationship between the respective control value and the respective threshold value meets a threshold condition or a maximum number of iterations are performed. Each threshold determination iteration increases the initial distributed deactivation delay value such that the distributed deactivation delay value is relative to a total of performed iterations.