Task Group Resource Quota Allocation for Mobile Computing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multitask computing systems, resource competition between foreground and background tasks often leads to foreground tasks being preempted, causing delays or failure in real-time communication, such as messaging or mail services, due to complete suspension of tasks.

Innovation Solution

A resource management method and system that determines task groups, sets preset task times, and allocates resource usage time quotas to ensure each task runs within a reasonable time frame, reducing competition and saving resources by putting tasks into a waiting state when not in use.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If background tasks are completely suspended to prevent resource competition with foreground tasks, then foreground task execution is ensured, but background tasks cannot communicate with servers in real time causing information feedback delays

Engineering Contradiction:
Improveforeground task execution reliabilityVSAvoidbackground task communication delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements dynamic task scheduling by dividing background tasks into multiple sub-tasks that can be executed in time slices. The system dynamically adjusts the execution state of tasks based on priority levels and resource availability, allowing background tasks to transition between suspended and running states rather than maintaining a fixed suspension state. This resolves the contradiction by enabling real-time communication capability while preserving foreground task execution reliability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent applies periodic action by allocating specific time slices for background task execution within a cyclic scheduling framework. Background tasks are permitted to run periodically in allocated time windows, enabling them to communicate with servers at regular intervals rather than being completely suspended. This periodic execution mechanism ensures both foreground task reliability and background task communication capability.

Inventive Principle:
Principle #19Periodic action

2Adaptability or versatility

If multiple tasks run simultaneously without resource allocation limits, then task execution flexibility is maintained, but resource competition increases causing foreground tasks to be preempted

Engineering Contradiction:
Improvetask execution flexibilityVSAvoidforeground task execution efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the resource usage time quota into separate time allocations for different task groups (foreground, background, system tasks). By dividing the total available time into discrete segments assigned to specific task categories, the system maintains execution flexibility within each segment while preventing resource competition across segments. This segmentation ensures foreground tasks receive dedicated time slots, preventing preemption while preserving overall task flexibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of resource allocation from unlimited simultaneous execution to time-quota-constrained execution. By introducing a resource usage time quota parameter that limits the total execution time of background tasks within a scheduling cycle, the system reduces resource competition while maintaining flexibility through adjustable time allocations. This parameter change directly addresses the productivity issue by capping background task resource consumption.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If background tasks are allowed to run freely, then real-time communication capability is maintained, but resource consumption increases causing power waste

Engineering Contradiction:
Improvebackground task communication capabilityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by allowing background tasks to execute only during allocated time slices rather than continuously. The resource usage time quota specifies a portion of total available time that background tasks may utilize, enabling them to maintain communication capability during active periods while consuming zero power during suspended periods. This partial execution approach resolves the contradiction between communication reliability and power consumption.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent implements periodic action through cyclic task scheduling where background tasks alternate between running and suspended states. During active time slices, background tasks execute and communicate with servers; during inactive periods, they are suspended to conserve power. This periodic pattern ensures communication capability is maintained at regular intervals while dramatically reducing overall power consumption compared to continuous execution.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS10467054B2Resource management method and system, and computer storage medium
Publication Date: 2019.11.05 GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
  • US10467054B2 patent drawing
  • US10467054B2 patent drawing
  • US10467054B2 patent drawing

AI summary

Provided is a resource management method and system, and a computer storage medium. The method comprises: determining tasks within a task group and a preset task time corresponding to each task within the task group (S110); determining whether the sum of the preset task times corresponding to all the tasks in the task group is less than a preset time threshold (S120); if yes, then determining the resource usage time quota of the task group to be the sum of the preset task times corresponding to all the tasks in the task group (S130); if no, then determining the resource usage time quota of the task group to be the time threshold (S140); determining the allowable run time per unit time for each task in the task group (S150); within unit time, when each task in the task group is outside of the corresponding run period, the respective task in the task group are respectively entered into a waiting state (S160).