Background Task Time Slicing for Resource Contention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multitask computing systems, background tasks often interfere with foreground tasks by competing for resources, leading to potential delays and inefficiencies, especially when background tasks require real-time communication, and suspending them entirely can result in information delays or other issues.

Innovation Solution

A task management method and system that monitors and limits the running time of background tasks within a unit time, allowing them to run only during designated periods and entering a waiting state during the rest, ensuring that the sum of their running times does not exceed a preset threshold, while also considering the priorities of foreground and background tasks to optimize resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If background tasks are completely suspended, then resource contention with foreground tasks is reduced, but real-time communication capability is lost

Engineering Contradiction:
Improveforeground task execution efficiencyVSAvoidbackground task communication reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements periodic time slicing where background tasks are allowed to execute during specific time intervals and suspended during others. The system divides time into units and allocates background task execution windows periodically, ensuring that background tasks can communicate with servers during their active periods while preventing resource contention during foreground task execution periods.

Inventive Principle:
Principle #19Periodic action

2Reliability

If background tasks run continuously, then real-time communication is maintained, but resource contention with foreground tasks increases

Engineering Contradiction:
Improvebackground task communication reliabilityVSAvoidforeground task execution efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic task scheduling where the system continuously monitors foreground and background task states and adjusts resource allocation in real-time. When a foreground task requires resources, the system dynamically suspends background tasks; when foreground tasks are inactive, background tasks are resumed. This dynamic adjustment optimizes resource utilization based on current system conditions.

Inventive Principle:
Principle #15Dynamics

3Productivity

If background tasks are limited to specific time periods, then resource utilization efficiency is improved, but task completion time may increase

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidbackground task execution duration
Core Design Contradiction:
ProductivityVSDuration of action of moving object

Solution Approach 1:

The system performs preliminary classification of background tasks into different priority levels and communication requirements. High-priority tasks that require real-time communication are allocated more frequent execution windows, while lower-priority tasks receive less frequent windows. This preliminary classification ensures that time-limited execution does not critically impact task completion for urgent operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10802877B2Task management methods and system, and computer storage medium
Publication Date: 2020.10.13 GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
  • US10802877B2 patent drawing
  • US10802877B2 patent drawing
  • US10802877B2 patent drawing

AI summary

A task management method and system, and a computer storage medium include: monitoring the operation of background tasks; determining the allowed operation time of a specific background task in a unit time, the sum of the operation times allowed for all the specific background tasks within the unit time being less than or equal to a preset time threshold; and the respective specific background tasks are brought into a waiting state when the specific background tasks are outside of the corresponding operation period within the unit time.