USB-C PD Power Negotiation for Stable SoC Boot Power

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile SoC host systems lack a defined mechanism to control power consumption during USB Type-C power contract negotiation, leading to voltage spikes, current surges, and frequent reboots, which negatively impact user experience and battery life.

Innovation Solution

Implementing a power negotiating sequence that utilizes the USB Type-C PD protocol and timing specification to dynamically control power consumption through a synchronous trigger and interrupt mechanism between the PD controller and embedded controller, ensuring power consumption remains at or below the pSnkStdby limit during boot and active states.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If power consumption is not controlled during Type-C power contract negotiation, then the system can operate without additional control mechanisms, but voltage spikes and current surges occur leading to frequent reboots and reduced reliability

Engineering Contradiction:
Improvesystem reliabilityVSAvoidpower control mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by implementing a power control mechanism that activates specifically during Type-C power contract negotiation transitions. The mechanism preemptively controls power consumption before voltage transitions occur, preventing voltage overshoot and current surges that would otherwise cause system instability and reboots.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamics by creating a dynamic power control mechanism that adapts its operation based on the system state. The power consumption is dynamically adjusted during VBUS voltage transitions to meet the pSnkStdby threshold requirement, while allowing normal operation outside of transition periods.

Inventive Principle:
Principle #15Dynamics

2Duration of action of stationary object

If power consumption is controlled during boot sequence, then battery life is extended and shutdowns are prevented, but the system requires additional power management mechanisms

Engineering Contradiction:
Improvebattery lifeVSAvoidpower management mechanism complexity
Core Design Contradiction:
Duration of action of stationary objectVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by implementing power control during the boot sequence before the operating system fully initializes. The mechanism ensures power consumption remains within safe limits during this critical early phase, preventing battery overload and unexpected shutdowns that would reduce battery life.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by monitoring power consumption during boot and active states, and adjusting power delivery accordingly. The system receives feedback about current power usage and battery status, and uses this information to maintain power consumption within the pSnkStdby threshold, preventing battery overload.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3930137B1Power negotiation sequence to improve user experience and battery life
Publication Date: 2024.08.21 INTEL CORP
  • EP3930137B1 patent drawingFigure 1
  • EP3930137B1 patent drawingFigure 2
  • EP3930137B1 patent drawingFigure 3

AI summary

A power sequence in a power-delivery (PD) mechanism (interaction between host system components and a charger) and a firmware sequence during power contract negotiation reduces the host system power consumption at or below the pSnkStdby power limit to improve user experience and battery life. The power sequence uses USB Type-C PD protocol and timing specification to implement a synchronous trigger or interrupt and interface mechanism. The synchronous trigger or interrupt and interface mechanism between a PD controller and an embedded controller firmware controls the power consumption dynamically during the boot flow sequence to be less than or equal to pSnkStdby power limit while implementing a predictable boot sequence and optimizing boot time. The power negotiating sequence is also applicable when a source (e.g., a charger) is connected to a SoC host system which is in active state (e.g., S0) and when there is an indication of low battery capacity.