Timed Iterator Event Loop Task Scheduling

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Mobile devices face challenges in maintaining responsiveness to user interactions while performing multiple tasks without increasing CPU consumption, as single-threaded designs are often unstable and multithreaded approaches drain battery life.

Innovation Solution

Implementing a timed iterator within the event loop that processes tasks without spawning new threads, allowing for task execution within a specified timeout and relinquishing control to the caller, thereby managing resource usage efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If multiple threads are used to handle multiple tasks simultaneously, then the application responsiveness to user interactions is improved, but the CPU consumption increases and battery life decreases

Engineering Contradiction:

Improveapplication responsivenessVSAvoidCPU consumption

Core Design Contradiction:

Ease of operationVSUse of energy by moving object

Solution Approach 1:

The patent segments the task execution process into discrete time slots within a single thread's event loop. Instead of using multiple concurrent threads, the system divides time into intervals and executes different tasks in sequence during these time slots, achieving task parallelism in time rather than in threads. This segmentation allows the application to remain responsive while avoiding the overhead of multiple threads.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements periodic action by using an event loop that continuously cycles through tasks in time slots. The event loop periodically wakes up, checks for new tasks, executes them within allocated time slots, and repeats the cycle. This periodic execution pattern enables the single thread to handle multiple tasks efficiently without requiring continuous CPU allocation, thus reducing energy consumption while maintaining responsiveness.

Inventive Principle:

Principle #19Periodic action

2Use of energy by moving object

If a single thread is used to handle all tasks, then the CPU consumption is reduced and battery life is extended, but the application becomes unresponsive to user interactions

Engineering Contradiction:

Improvebattery lifeVSAvoidapplication responsiveness

Core Design Contradiction:

Use of energy by moving objectVSEase of operation

Solution Approach 1:

The patent introduces dynamics by making the single thread's behavior adaptive through the event loop mechanism. The thread dynamically adjusts its execution pattern by periodically checking for tasks and executing them in time slots rather than running continuously or remaining idle. This dynamic execution model allows the thread to be active when tasks are pending and less active when the system is idle, maintaining responsiveness while optimizing battery life.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent ensures continuity of useful action through the event loop that continuously monitors and executes tasks. Instead of the single thread being blocked or idle, the event loop maintains continuous operation by periodically waking up to check for tasks, execute them in time slots, and return to idle state. This continuous cycling ensures the application remains responsive to user interactions while minimizing CPU consumption during idle periods.

Inventive Principle:

Principle #20Continuity of useful action

3Productivity

If multiple threads are spawned to perform tasks in parallel, then the task execution speed is improved, but the device complexity and resource management become more difficult

Engineering Contradiction:

Improvetask execution speedVSAvoidthread management complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent merges the functionality of multiple threads into a single thread by combining task scheduling, execution, and management into one event loop. Instead of having separate threads that need to be coordinated and managed, the event loop consolidates these functions, executing tasks in time slots within the same thread context. This merging eliminates the complexity of thread management while maintaining parallel task execution capabilities through time-based multiplexing.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The event loop serves multiple functions: it acts as a task scheduler, task executor, time manager, and coordination mechanism all in one. This universal component replaces the need for multiple specialized threads, each handling specific tasks. The event loop's multi-functionality simplifies the system architecture by providing a single point of control for all task management operations, reducing device complexity while maintaining productivity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9229770B2Invoking timed iterator for executing tasks within timeout constraint without spawning new thread

Publication Date: 2016.01.05 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A computer implemented method for processing tasks is disclosed. The method includes invoking a timed iterator, during an event loop pass, without spawning a new thread, wherein the invoking includes passing a task list and a timeout constraint to the timed iterator. The method further includes executing one or more tasks in the task list for a period of time as specified in the timeout constraint, and relinquishing program control to a caller after the period of time.