DRX Data Request Tagging for Wireless Power Savings

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Wireless computing devices face significant power consumption issues due to continuous data requests from background applications, which reduce the uptime on a single battery charge, especially when operating in discontinuous reception (DRX) mode, as existing systems immediately respond to all data requests disrupting scheduled radio downtime and reducing power savings.

Innovation Solution

Implementing a method to tag application-generated data requests as high-priority or low-priority, where high-priority requests are handled immediately and low-priority requests are delayed until scheduled active times within DRX mode, optimizing power savings by minimizing operations outside of scheduled inactive states.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If the radio system immediately responds to all data requests from applications, then data access performance is improved, but power consumption increases and DRX mode effectiveness is reduced

Engineering Contradiction:
Improvedata access speedVSAvoidpower consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The patent applies local quality by differentiating between high-priority and low-priority data requests. High-priority requests (from foreground applications) are handled immediately with conventional techniques, while low-priority requests (from background applications) are delayed until scheduled active times in DRX mode. This selective approach optimizes power savings for non-critical operations while maintaining responsive performance for user-facing applications.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If background applications continuously check for updates, then application functionality is improved, but battery life decreases

Engineering Contradiction:
Improveapplication functionalityVSAvoidbattery life
Core Design Contradiction:
Adaptability or versatilityVSDuration of action of stationary object

Solution Approach 1:

The patent implements periodic action by scheduling low-priority data requests to occur only during designated active periods in DRX mode cycles. Background applications maintain their update-checking functionality, but these operations are periodically batched and executed only when the radio system is scheduled to be active, rather than running continuously. This reduces power consumption while preserving application functionality.

Inventive Principle:
Principle #19Periodic action

3Loss of energy

If the radio duty cycle is reduced in DRX mode, then power savings increase, but data request response time worsens

Engineering Contradiction:
Improvepower savingsVSAvoiddata request response time
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The patent applies preliminary action by having the system proactively identify and tag low-priority data requests before they would normally be processed. By anticipating which requests can be delayed and scheduling them for upcoming active periods, the system prepares in advance to minimize the impact on response times while maximizing power savings during inactive periods.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9872333B2Method and system for scheduling application-generated data requests in discontinuous reception (DRX) mode
Publication Date: 2018.01.16 APPLE INC
  • US9872333B2 patent drawing
  • US9872333B2 patent drawing
  • US9872333B2 patent drawing

AI summary

The invention provides a technique for managing application-generated data requests within a wireless communication device comprising a baseband component operating in discontinuous reception (DRX) mode. The technique includes the steps of receiving a data request from an application, tagging the data request as a low-priority data request or a high-priority data request in accordance with a manner in which the application is executing, forwarding the tagged data request to the baseband component, determining a next-scheduled active time based on parameters associated with the DRX mode, and causing a scheduling request to be issued at or substantially proximate to the next-scheduled active time.