Break Event Coordination for Mobile Platform Power Saving

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional mobile computing platforms experience uncoordinated break events from IO devices and software applications, preventing them from entering and staying in lower power states, leading to shorter battery life and increased power consumption.

Innovation Solution

A method and apparatus that detect and coordinate break events from different sources based on runtime information, deferring non-essential events to align them with essential ones, allowing the platform to enter deeper power-saving states for extended periods.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If break events from multiple IO devices and software applications are generated independently, then device responsiveness and application functionality are maintained, but the platform cannot enter lower power states and battery life is reduced

Engineering Contradiction:
Improvepower consumptionVSAvoiddevice responsiveness
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The patent introduces a break event coordination mechanism that acts as an intermediary between multiple event sources (IO devices, applications) and the platform power management system. This coordinator consolidates break events from multiple sources, determines whether they represent genuine user interaction requiring immediate response, and coordinates their timing to allow the platform to enter and remain in lower power states. The intermediary filters and schedules events to balance power savings with responsiveness requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Duration of action of moving object

If the platform frequently transitions to lower power states to save energy, then battery life is extended, but device responsiveness and application performance may be degraded

Engineering Contradiction:
Improvebattery lifeVSAvoiddevice responsiveness
Core Design Contradiction:
Duration of action of moving objectVSSpeed

Solution Approach 1:

The patent implements dynamic power management by continuously monitoring break event patterns from multiple sources and adapting the platform's power state transitions in real-time. The system dynamically determines whether to enter lower power states based on the current stream of events, extending idle periods when events are minimal while quickly responding when genuine user interaction occurs. This dynamic approach optimizes battery life without permanently degrading responsiveness.

Inventive Principle:
Principle #15Dynamics

3Loss of energy

If break events are coordinated and deferred to maximize power savings, then the platform stays in lower power states longer, but event processing delay may increase

Engineering Contradiction:
Improvepower savingsVSAvoidevent processing delay
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The patent applies partial coordination to break events by selectively deferring only those events that do not represent genuine user interaction or critical system needs. The coordination mechanism uses heuristics to identify events that can be safely delayed or consolidated, while allowing critical events to be processed immediately. This partial action approach achieves meaningful power savings without excessive event processing delays.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9513964B2Coordinating device and application break events for platform power saving
Publication Date: 2016.12.06 INTEL CORP
  • US9513964B2 patent drawing
  • US9513964B2 patent drawing
  • US9513964B2 patent drawing

AI summary

Systems and methods of managing break events may provide for detecting a first break event from a first event source and detecting a second break event from a second event source. In one example, the event sources can include devices coupled to a platform as well as active applications on the platform. Issuance of the first and second break events to the platform can be coordinated based on at least in part runtime information associated with the platform.