Server Push Schedule for Mobile Battery and Data Conservation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices face challenges in managing resource consumption, particularly in extending battery life and reducing network data transfer usage, as existing methods do not effectively control when to wake devices and transfer data, leading to inefficient battery usage and potential data limit exceedance.
Innovation Solution
A method where a server pushes a 'wake' command and content updates to mobile devices periodically, maintaining schedules for waking and data transfer to control resource consumption, prioritizing power-efficient devices and optimizing data usage based on network connectivity and charging status.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the device wakes frequently to check for content updates, then the user receives timely content, but battery life is reduced
Solution Approach 1:
The system implements periodic wake schedules where the device wakes at predetermined intervals to check for content updates. This periodic action balances content freshness with battery conservation by not waking the device continuously or too frequently, thus reducing energy consumption while still maintaining reasonable content update timeliness.
Solution Approach 2:
The wake schedule is dynamically adjusted based on device characteristics (power-efficient vs. less power-efficient devices), network conditions, and charging status. Power-efficient devices may wake more frequently, while less power-efficient devices wake less often, especially when battery level is low or the device is charging, optimizing the balance between content updates and battery usage.
2Reliability
If the device transfers data frequently to sync content, then the content is up-to-date, but network data usage increases
Solution Approach 1:
Data transfer occurs periodically according to the wake schedule rather than continuously. The device transfers data only when waking to check for updates, which reduces overall network data consumption while still maintaining content synchronization at acceptable intervals.
Solution Approach 2:
The device performs partial data transfers by only retrieving new content or updates since the last wake event, rather than transferring all data continuously. This partial action approach maintains synchronization while minimizing unnecessary data consumption.
3Reliability
If the device wakes more often, then content freshness is improved, but uniform battery life across devices is compromised
Solution Approach 1:
The system applies different wake schedules and content update frequencies to different devices based on their individual characteristics. Power-efficient devices receive more frequent updates, while less power-efficient devices receive less frequent updates, especially when charging. This local quality approach ensures each device operates within its battery constraints while maintaining acceptable content freshness for its capabilities.
Solution Approach 2:
The system changes key parameters (wake frequency, data transfer timing) based on device power efficiency characteristics and battery status. By adjusting these parameters dynamically, the system achieves uniform battery life consumption patterns across diverse devices while still providing content freshness appropriate to each device's capabilities.
4Use of energy by moving object
If the device delays waking events to save battery, then battery life is extended, but content update timeliness deteriorates
Solution Approach 1:
Instead of continuous or on-demand waking, the system uses periodic wake schedules that extend intervals between wakes to conserve battery. This periodic approach accepts delayed content updates as a trade-off for significant battery savings, which is appropriate for devices in low-power states or when content urgency is low.
Solution Approach 2:
The system dynamically adjusts wake timing based on battery level, charging status, and device power efficiency. When battery is low or device is charging, wakes are delayed or reduced. When battery is sufficient or device is power-efficient, wakes occur more frequently. This dynamic adjustment optimizes the trade-off between battery conservation and content update responsiveness based on real-time conditions.
Data Source
Figure 1
Figure 2A~2B
Figure 2C~2E
AI summary
In one embodiment, a method includes determining a power consumption profile for a device. Status information for the device may be received, wherein the status information comprises power status and network connectivity status. Using a resource-control algorithm and based on the status information and the power consumption profile, a schedule for sending push events to the device may be determined. Content to be provisioned to the device may be identified, and the scheduled push events may be sent to the device, in order to provision the identified content to the device. The resource-control algorithm may be further based on one or more device-based consumption factors, such as a periodic data usage transfer limit with respect to a specified network and a data usage status with respect to the specified network, or system-wide consumption factors, such as a power threshold that applies across all devices.