OS-Based Power Limit Control Across Mixed-Vendor Components

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing power limit management systems are vendor-specific and lack a standard interface, leading to sub-optimal control results and increased project difficulty due to the need for diverse interfaces to communicate with different hardware components, and they fail to optimize power allocation across components with varying power demands.

Innovation Solution

A centralized, operating system-based framework with platform-agnostic input and output interfaces that receive power and operational data, calculate power allocation, and generate control signals to manage power consumption across components, ensuring optimal performance and efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If vendor-specific power limit management interfaces are used, then hardware compatibility is achieved, but device complexity and project difficulty increase due to the need for diverse interfaces

Engineering Contradiction:
Improvehardware compatibilityVSAvoidinterface diversity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal power limit management interface that can communicate with multiple hardware components from different vendors (CPU, GPU, storage, display, etc.). This single standardized interface replaces the need for multiple vendor-specific interfaces, reducing device complexity while maintaining broad hardware compatibility and adaptability

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

2Reliability

If individual component-level power control is implemented, then component-specific optimization is achieved, but overall system power allocation becomes sub-optimal

Engineering Contradiction:
Improvecomponent-specific optimizationVSAvoidoverall power allocation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges individual component power control capabilities into a centralized power limit management system. The controller receives power-related data and operational state data from all components, calculates optimized power allocation across the entire system, and coordinates control signals to actuators for each component. This unified approach ensures overall system power allocation efficiency while maintaining component-specific optimization through targeted control signals

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If centralized power management is implemented, then overall power allocation optimization is achieved, but system complexity increases due to data collection and processing requirements

Engineering Contradiction:
Improvepower allocation optimizationVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a centralized controller as an intermediary component that manages power allocation. The controller receives standardized power-related data and operational state data from various hardware components through a unified interface, processes this information to calculate optimized power allocation, and sends control signals to actuators. This intermediary architecture simplifies the overall system by providing a single point of coordination rather than requiring direct complex interactions between all components

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250370527A1Centralized platform-agnostic power limit management system
Publication Date: 2025.12.04 MICROSOFT TECHNOLOGY LICENSING LLC
  • US20250370527A1 patent drawing
  • US20250370527A1 patent drawing
  • US20250370527A1 patent drawing

AI summary

Systems and methods are provided for implementing centralized platform-agnostic power limit management functionalities. A power limit management system includes an input interface, an output interface, and a controller that is part of an operating system of a computing device and that is configured to: receive, via the input interface, (a) power-related data associated with power supplied from a power source device for the computing device; and (b) operational state-related data associated with computing device components. The controller is further configured to: calculate power allocation for a computing device component(s), based on the power-related data and the operational state-related data; and generate a control signal for controlling power consumption for each computing device component, based on the power allocation. For each computing device component, the controller is further configured to send, via the output interface, the control signal to a corresponding actuator to control power consumption by the computing device component.