Dynamic Power Profiles for Mobile Application Code Sections

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing power management techniques for mobile network applications often compromise on functionality or require precompiled energy profiles, failing to adapt efficiently to changing energy constraints.

Innovation Solution

A method that assigns profiles to sections of application code based on energy demand, functional priority, and accuracy, allowing for dynamic operation mode determination and selective execution of application sections to optimize power usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If dynamic voltage and frequency scaling (DVFS) is used to reduce power consumption, then energy efficiency is improved, but application functionality is compromised because important functions may be slowed down or interrupted

Engineering Contradiction:
Improvepower consumptionVSAvoidapplication functionality
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The patent segments the application code into multiple sections with different power profiles (first power profile, second power profile, third power profile) based on their functional importance and power consumption characteristics. This allows selective execution of sections based on available power resources, ensuring critical functions maintain full performance while non-critical functions are scaled back during power constraints.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic power management by determining operation modes at runtime based on current power resource availability. The system can switch between different operation modes (first operation mode, second operation mode, third operation mode) that correspond to different power consumption levels, allowing the application to adapt its behavior dynamically rather than using static frequency scaling.

Inventive Principle:
Principle #15Dynamics

2Use of energy by moving object

If approximate computing framework is used to save energy, then power consumption is reduced, but dynamicity is compromised because the application is precompiled with one particular energy consumption profile

Engineering Contradiction:
Improveenergy consumptionVSAvoiddynamicity
Core Design Contradiction:
Use of energy by moving objectVSAdaptability or versatility

Solution Approach 1:

The patent enables runtime adaptability by determining operation modes based on current power resource conditions rather than using fixed precompiled profiles. The system can dynamically switch between multiple operation modes during execution, allowing the application to adapt to changing power availability while maintaining different energy consumption levels for different application sections.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes operational parameters (power profiles, operation modes) based on power resource availability. Instead of compiling for a single energy profile, the system maintains multiple power profiles and selects appropriate ones at runtime, effectively changing the operational parameters to match current power conditions.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If empirical measurements are performed to evaluate resource consumption metrics, then accuracy of resource management is improved, but power consumption increases because measurements still need to be performed during power shortages

Engineering Contradiction:
Improveresource consumption metricsVSAvoidpower consumption
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent performs power profile assignments and operation mode determinations in advance or based on pre-characterized sections. The system divides application code into sections with known power consumption characteristics before execution, allowing it to make informed decisions about which sections to execute without needing to perform measurements during runtime power constraints.

Inventive Principle:
Principle #10Preliminary action

4Use of energy by moving object

If per-processor power management with P-states is used, then energy consumption is reduced when full processing power is not required, but all applications executing on the same processor are affected indiscriminately

Engineering Contradiction:
Improveenergy consumptionVSAvoidapplication-specific control
Core Design Contradiction:
Use of energy by moving objectVSAdaptability or versatility

Solution Approach 1:

The patent segments the application code into multiple sections with different power profiles, allowing fine-grained control over power consumption at the application level rather than processor level. This enables different parts of the same application or different applications to have different power management policies applied to their respective code sections.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different power management policies to different sections of application code based on their local characteristics (functional importance, power consumption profile). Critical sections can maintain higher performance while non-critical sections are scaled back, allowing localized optimization rather than uniform processor-wide scaling.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12314111B2Power resource management
Publication Date: 2025.05.27 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US12314111B2 patent drawing
  • US12314111B2 patent drawing
  • US12314111B2 patent drawing

AI summary

There is provided a method for managing power resources of a mobile network application program including application code, the method comprising: assigning a profile to each section of the application code, wherein each profile comprises information indicative of at least one of: a level of energy demand of the respective section, a level of functional priority of the respective section, and a level of accuracy of the functionality associated with the respective section; determining an operation mode for running the application program, wherein the operation mode includes one or more criteria which are to be satisfied by a profile assigned to a section of the application code in order for the respective section to be executed; selecting one or more sections of the application code which satisfy the criteria included in the operation mode; a running the application program by only executing the selected one or more sections.