Adaptive App Connectivity Control for Power and Network Load

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Contemporary devices consume significant resources, particularly in cellular communications, due to pervasive network connectivity which is inefficient and wasteful.

Innovation Solution

Implementing a dynamic connectivity management system that pauses and throttles network connections based on application-specific settings and user behavior patterns, reducing unnecessary connectivity to conserve power and resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If devices maintain pervasive connectivity to networks, then communication availability is improved, but resource consumption and power usage increase significantly

Engineering Contradiction:
Improvecommunication availabilityVSAvoiddevice resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system dynamically adjusts connectivity state based on real-time conditions. The connectivity manager monitors application requirements, network conditions, and device state to transition between connected and disconnected states, making the connectivity adaptive rather than static. This resolves the contradiction by maintaining connectivity only when necessary for communication availability while conserving resources during disconnection.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the connectivity parameter (connected/disconnected) based on varying conditions. By monitoring application-specific settings, usage patterns, and network conditions, the system adjusts the connectivity state parameter to optimize the balance between communication availability and resource consumption.

Inventive Principle:
Principle #35Parameter changes

2Speed

If devices maintain continuous network connections, then communication responsiveness is improved, but network and server demands increase

Engineering Contradiction:
Improvecommunication responsivenessVSAvoidnetwork load
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

Instead of continuous connection, the system implements periodic reconnection based on predicted usage patterns and application requirements. The connectivity manager schedules disconnections and reconnections periodically, maintaining communication responsiveness when needed while significantly reducing continuous network load on servers and networks.

Inventive Principle:
Principle #19Periodic action

3Loss of energy

If connectivity is paused to conserve resources, then power consumption is reduced, but communication availability decreases

Engineering Contradiction:
Improvepower consumptionVSAvoidcommunication availability
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The system performs preliminary actions by predicting future connectivity needs based on learned usage patterns and application settings. Before pausing connectivity, the system anticipates when disconnection will occur and prepares accordingly, ensuring that reconnection happens promptly when communication is needed, thus minimizing the impact on availability while maximizing energy savings.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The connectivity manager implements feedback mechanisms by monitoring application performance, user behavior, and communication patterns. This feedback loop allows the system to learn from past connectivity decisions and adjust future connectivity states to optimize the balance between power consumption and communication availability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12621229B2Device connectivity management
Publication Date: 2026.05.05 AT&T INTELLECTUAL PROPERTY I L P
  • US12621229B2 patent drawing
  • US12621229B2 patent drawing
  • US12621229B2 patent drawing

AI summary

The disclosed technology is directed towards managing the establishment and maintenance of communication connectivity between a device and service. Condition data can indicate when to initiate a state change of a connection between a device and a server. Current device conditions associated with the device are evaluated to determine whether to initiate a state change, e.g., from a connected state to a paused state, or vice-versa. The connectivity may be managed per connection type, e.g., cellular versus Wi-Fi, and on a per-application basis, e.g., turned on for a social media application, off for mail and messaging applications. Settings can be used to manage connectivity for an application, e.g., sometimes connected, sometimes paused based on information specific to that application. Trends, user practices and schedule data can be used to predict and manage connectivity, as well as to notify the user to take some action.