Dynamic Background Task Scheduling Based on Device Headroom
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Fixed scheduling of background tasks on devices may not account for appropriate system conditions, leading to potential degradation of other processes and user interaction, as it does not consider current device operating conditions such as network connectivity or resource availability.
Innovation Solution
A method and apparatus that schedules and manages background tasks by registering execution criteria based on device component status, monitoring system conditions, and determining available device headroom to launch tasks only when conditions are suitable, with a focus on task importance and time-dependent importance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If background tasks are scheduled to run at a fixed time, then the task execution timing is simple and predictable, but the system conditions may not be appropriate for the task and other processes may be degraded
Solution Approach 1:
The patent implements dynamic task scheduling where the task execution time is not fixed but adjusted based on real-time system conditions. The scheduler continuously monitors system state (battery level, network connectivity, user activity) and dynamically determines the optimal execution time, transforming the static fixed-time scheduling into a dynamic adaptive system that responds to changing conditions.
Solution Approach 2:
The patent changes the scheduling parameter from a fixed timestamp to a condition-based trigger. Instead of specifying when a task must run, the system defines parameter thresholds (e.g., battery level above 20%, network connected, screen off) that, when satisfied, enable task execution. This parameter-based approach allows the system to adapt to varying operational conditions.
2Productivity
If background tasks run regardless of system conditions, then task execution is simple and frequent, but battery life is reduced and device responsiveness deteriorates
Solution Approach 1:
The patent introduces energy consumption as a key parameter in the scheduling decision. By monitoring battery level and estimating task energy cost, the system adjusts task execution timing to minimize power consumption. Tasks are deferred to periods when the device is plugged in or battery level is high, directly addressing the energy conservation goal.
Solution Approach 2:
The system performs preliminary assessment of system conditions before allowing task execution. It checks whether energy thresholds are met and whether deferring the task would be beneficial, making a proactive decision to postpone execution rather than running tasks indiscriminately. This preliminary check prevents unnecessary energy consumption.
3Device complexity
If background tasks are scheduled without considering device headroom, then task scheduling is simple and fast, but device responsiveness and user interaction are degraded
Solution Approach 1:
The patent incorporates device headroom (available CPU, memory, I/O capacity) as a dynamic parameter in scheduling decisions. The scheduler monitors system load and user interaction patterns, adjusting task execution timing based on real-time headroom assessment. This transforms the simple but blind fixed-time scheduling into an intelligent system that adapts to current device capacity.
Solution Approach 2:
The system implements feedback mechanisms where task execution decisions are based on continuous monitoring of system state and user interaction. When user activity is detected or system load increases, the scheduler receives feedback and defers task execution. This feedback loop ensures tasks run only when they will not interfere with user experience or device responsiveness.
Data Source
AI summary
A method and apparatus that schedules and manages a background task for device is described. In an exemplary embodiment, the device registers the background task, where the registering includes storing execution criteria for the background task. The execution criteria indicates a criterion for launching the background task and the execution criteria based on a component status of the device. The device further monitors the running state of the device for an occurrence of the execution criteria. If the execution criteria occurs, the device determines an available headroom with the device in order to perform the background task and launches the background task if the background task importance is greater than the available device headroom, where the background task importance is a measure of how important it is for the device to run the background task.