Polling Manager for Mobile App Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile computing devices face a tradeoff between maintaining application performance through frequent data exchanges and conserving battery life, with existing methods failing to efficiently manage synchronization intervals to prolong battery life, especially in unpredictable network conditions and varying application usage patterns.

Innovation Solution

A system and method that employs a polling manager to dynamically adjust synchronization intervals based on communication activity and tolerance windows for each application, coordinating synchronization times to minimize power drain and extend battery life by synchronizing multiple applications together and adjusting intervals according to network conditions and application priorities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If frequent data exchanges are performed to maintain application performance, then application responsiveness is improved, but battery life deteriorates

Engineering Contradiction:
Improveapplication responsivenessVSAvoidbattery life
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The patent implements dynamic synchronization interval adjustment where the polling manager continuously monitors network conditions and application activity patterns to adaptively modify synchronization frequencies. This allows the system to transition between aggressive synchronization (short intervals) when performance is needed and conservative synchronization (long intervals) when battery conservation is prioritized, resolving the contradiction between application responsiveness and battery life

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of synchronization interval dynamically based on monitored conditions. By adjusting this temporal parameter according to network stability, application priority, and battery status, the system optimizes the balance between data freshness (performance) and energy consumption, directly addressing the contradiction

Inventive Principle:
Principle #35Parameter changes

2Use of energy by moving object

If synchronization interval is extended to conserve energy, then battery life is improved, but application performance deteriorates

Engineering Contradiction:
Improvebattery lifeVSAvoidapplication responsiveness
Core Design Contradiction:
Use of energy by moving objectVSSpeed

Solution Approach 1:

The polling manager performs preliminary monitoring of network conditions and application usage patterns before adjusting synchronization intervals. By anticipating when performance will be needed based on historical patterns and current context, the system can pre-establish appropriate synchronization frequencies, ensuring performance requirements are met while maximizing battery life

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback loops where the polling manager continuously monitors application performance metrics and battery status, then adjusts synchronization intervals accordingly. This closed-loop control ensures that when performance degradation is detected, the system responds by increasing synchronization frequency, while maintaining energy efficiency during normal operation

Inventive Principle:
Principle #23Feedback

3Speed

If multiple applications are synchronized independently, then application-specific performance is maintained, but power consumption increases

Engineering Contradiction:
Improveapplication-specific responsivenessVSAvoidpower drain
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The polling manager merges synchronization operations for multiple applications by coordinating their polling activities. When multiple applications have pending synchronization needs, the system combines them into unified network transactions, reducing the total number of separate wake-ups and network connections. This maintains application-specific performance requirements while significantly reducing overall power drain from coordinated rather than independent synchronization

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8904206B2Mobile computing device and method for maintaining application continuity
Publication Date: 2014.12.02 GOOGLE TECHNOLOGY HOLDINGS LLC
  • US8904206B2 patent drawing
  • US8904206B2 patent drawing
  • US8904206B2 patent drawing

AI summary

A method of maintaining application continuity (900) and mobile computing device (200) are described. The method involves a mobile device running an application in synchronous communication with an application server. The application has a threshold communication null period for maintaining application continuity. The method (900) can include the steps of: operating (910) the application in synchronous communication with an application server, defining an active mode, wherein the synchronous communication is automatically enabled; providing (920) a dormant mode wherein the synchronous communication is automatically disabled in the mobile device for a predetermined duration; and interrupting (930) the dormant mode by momentarily communicating with the application server prior to a threshold communication null period, for maintaining application continuity. Advantageously, prior to a threshold period of communication inactivity, the dormant mode can be interrupted to maintain application connectivity, so the server will not stop the application and data will not be lost.