Power Consumption Measurement System for Application Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Determining the power consumption of applications across different devices and network conditions is challenging due to various factors affecting battery power, including device components and network conditions, making it difficult to identify suboptimal performance and improve application efficiency.

Innovation Solution

A system and method for determining the quantity of power consumed by test devices executing applications, which involves measuring power usage over time, identifying contributing device and network characteristics, and using multiple methods to increase accuracy, including simulating disconnect states and maintaining charge levels, to isolate power consumption attributed to specific functions and conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If multiple measurement methods are used to determine power consumption, then measurement precision is improved, but device complexity increases

Engineering Contradiction:
Improvepower consumption measurement accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The power consumption measurement system is segmented into multiple independent measurement methods: (1) direct battery state comparison before and after function execution, (2) network disconnect simulation to isolate network-related power consumption, and (3) charge level maintenance monitoring. Each method targets specific aspects of power consumption, allowing comprehensive measurement while keeping individual measurement mechanisms relatively simple and modular.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The measurement system is designed to perform multiple functions using a unified framework: it can measure total power consumption, network-specific power consumption, and component-specific power consumption. The same basic measurement infrastructure (battery state monitoring, timestamp recording) supports all three measurement methods, reducing overall system complexity while achieving comprehensive measurement capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Measurement precision

If network disconnect simulation is performed to isolate power consumption, then measurement precision is improved, but loss of time increases

Engineering Contradiction:
Improvepower consumption attribution accuracyVSAvoidmeasurement time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary network disconnect simulation before actual power consumption measurement. By pre-establishing the disconnect state and verifying it, the system ensures that subsequent power consumption measurements are taken under controlled, known conditions. This preliminary action prevents measurement errors and eliminates the need for repeated measurements, ultimately reducing total measurement time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The measurement system rapidly transitions through the network disconnect state by implementing quick connect/disconnect cycles. The network interface card is configured to enable/disable networking functions in minimal time, and the system skips unnecessary intermediate states or verification steps that do not contribute to measurement accuracy, thus minimizing the time penalty associated with the disconnect simulation.

Inventive Principle:
Principle #21Skipping (Rushing through)

Data Source

PatentUS11650263B1System for determining power consumption by devices
Publication Date: 2023.05.16 PARTNER ONE ACQUISITIONS INC
  • US11650263B1 patent drawing
  • US11650263B1 patent drawing
  • US11650263B1 patent drawing

AI summary

The power consumption associated with use of an application is determined by causing one or more devices to execute the application. The state of the power source for each device is determined before, during, and after execution of the application. The state may include an amount of power discharged by the power source, an amount of power used to maintain a charge level of the power source, or a difference between a baseline power use and the amount of power consumed during use of the application. The determined states for the power sources of each device are used to generate an output that indicates periods of high and low power use. The output may associate these periods of power use with different characteristics of the functions that were performed during those time periods or of the devices. Using the output, a developer may optimize power use associated with an application.