Application Scenario Identification for Terminal Power Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for identifying application scenarios in terminal devices are inaccurate, leading to inefficient power consumption management and affecting user experience, as they rely on monitoring bottom-layer events which can correspond to multiple upper-layer scenarios, resulting in inadequate control over CPU, GPU, and LCD power usage.

Innovation Solution

A method that analyzes application programs through compilation to obtain characteristic data, determining application scenario information from a scenario characteristic data set, which includes correlations between scenario types and program characteristics, to accurately identify scenarios and manage power consumption by generating corresponding control policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If bottom-layer key event monitoring is used to identify application scenarios, then power consumption control can be implemented, but scenario identification accuracy is insufficient

Engineering Contradiction:
Improvescenario identification accuracyVSAvoidmonitoring system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

Instead of monitoring bottom-layer events and inferring scenarios, the patent inverts the approach by directly analyzing upper-layer application program characteristics through compilation to obtain scenario information. This reverses the traditional monitoring direction from hardware events to software characteristics, achieving more accurate scenario identification.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent introduces a scenario identification module as an intermediary that analyzes application program characteristics through compilation. This intermediary layer translates application-level characteristics into scenario information, bridging the gap between application behavior and power consumption control without requiring direct hardware monitoring.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If one-to-many correspondence between bottom-layer events and upper-layer scenarios is considered, then comprehensive scenario coverage is achieved, but identification precision deteriorates

Engineering Contradiction:
Improvescenario coverageVSAvoidscenario identification accuracy
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent segments the scenario identification process by analyzing different application program characteristics (static and dynamic) separately through compilation. By dividing the analysis into distinct characteristic types and combining them, the system achieves both comprehensive coverage and precise identification without the ambiguity of one-to-many event mappings.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameters used for scenario identification from bottom-layer event types to upper-layer application program characteristics. By using compilation to extract multiple characteristic parameters (functions, variables, execution flow) from application programs, the system achieves precise scenario differentiation that resolves the precision-loss problem of event-based approaches.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If application programs are analyzed through compilation, then scenario identification accuracy improves, but processing time increases

Engineering Contradiction:
Improvescenario identification accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by performing compilation analysis of application programs in advance to extract and store characteristic data before runtime scenario identification. This pre-processing allows the system to quickly match observed characteristics against pre-analyzed application profiles, reducing real-time processing time while maintaining high identification accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies partial action by selectively analyzing only the most relevant application program characteristics through compilation rather than performing complete analysis. By focusing on key characteristic data that most strongly indicate scenario type, the system achieves sufficient identification accuracy with reduced processing overhead.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP2950203B1Application scenario identification method, power consumption management method and apparatus and terminal device
Publication Date: 2020.04.22 HUAWEI TECH CO LTD
  • EP2950203B1 patent drawingFigure 1
  • EP2950203B1 patent drawingFigure 2
  • EP2950203B1 patent drawingFigure 3

AI summary

The present invention discloses a method for identifying an application scenario of a terminal device, where the method includes: analyzing an application program running on a terminal device by means of compilation to obtain characteristic data of the application program; and determining, from a scenario characteristic data set according to the characteristic data of the application program, application scenario information corresponding to the characteristic data of the application program, where the scenario characteristic data set includes a correspondence between multiple types of application scenario information and characteristic data of multiple application programs, and the application scenario information corresponding to the characteristic data of the application program is used to indicate an application scenario currently used for the terminal device. Embodiments of the present invention further provide a power consumption management method. Because characteristic data of an application program is more likely to be unique in describing a corresponding application scenario, application scenario information corresponding to the characteristic data of the application program is relatively accurate. Therefore, an application scenario of a terminal device can be relatively accurately identified according to the embodiments of the present invention.