SoC Domain Throttling Priority Order for Power and Thermal Limits

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional System on a Chip (SoC) technologies do not support extending throttling mechanisms to non-computing IP blocks and lack a mechanism to prioritize the order in which these blocks are throttled to stay within power and thermal limits.

Innovation Solution

Assign throttling priorities to various domains within the SoC, determining a systematic order for throttling and un-throttling based on these priorities, using a constraint headroom parameter to manage power and thermal budgets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If throttling mechanisms are extended to non-computing IP blocks, then power and thermal budget management is improved, but device complexity increases

Engineering Contradiction:
Improvepower budget managementVSAvoidthrottling mechanism complexity
Core Design Contradiction:
Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The throttling mechanism is extended from computing IP blocks to non-computing IP blocks, making the power management system universal across all domain controllers in the SoC. This allows a single throttling framework to manage power consumption across diverse component types (CPU, GPU, display, audio, etc.), improving overall power budget management without requiring separate mechanisms for each block

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

Solution Approach 2:

The SoC is divided into multiple domains, each with its own domain controller that independently manages throttling for specific IP blocks. This segmentation allows distributed power management where each domain controller handles only its assigned blocks, reducing the complexity burden on any single controller while achieving system-wide power management

Inventive Principle:
Principle #1Segmentation

2Reliability

If a systematic throttling order is implemented based on priorities, then power and thermal constraint management is improved, but control mechanism complexity increases

Engineering Contradiction:
Improvepower constraint adherenceVSAvoidcontrol mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Throttling priorities are assigned to each domain controller in advance, establishing a predetermined throttling order before power constraints are violated. When power or thermal limits are approached, the system follows this pre-established priority sequence to throttle domains, ensuring reliable adherence to constraints without requiring complex real-time decision-making algorithms

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Each domain controller autonomously monitors its own power consumption and thermal conditions, and independently executes throttling decisions for its assigned IP blocks based on its priority level. This self-service approach allows distributed control where each domain manages itself according to the global priority framework, reducing the need for complex centralized control mechanisms

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20260037054A1Throttling of components using priority ordering
Publication Date: 2026.02.05 INTEL CORP
  • US20260037054A1 patent drawing
  • US20260037054A1 patent drawing
  • US20260037054A1 patent drawing

AI summary

An apparatus is provided, where the apparatus includes a plurality of components, wherein an individual component has a corresponding throttling priority of a plurality of throttling priorities. The apparatus further includes logic to selectively throttle one or more of the plurality of components. In an example, an order in which the one or more of the plurality of components are to be throttled may be based on the plurality of throttling priorities.