USB PD Dead Battery Charging via Segmented Voltage Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional dead battery protocols for USB Power Delivery (PD) standards face challenges in accurately determining voltage levels, leading to potential errors in role swapping between consumer and provider devices due to difficulties in distinguishing between 4.6V and 4.75V on the VBUS conductor.
Innovation Solution
A power transceiver system that checks the VBUS conductor for voltage greater than vSafe0V, applies vSafeDB voltage if necessary, waits for a bit stream, and transitions to vSafe5V or vSafe0V based on bit stream detection, enabling accurate role swapping by sending capabilities as a source port after the bit stream stops.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If conventional dead battery protocols check voltage on VBUS conductor, then power delivery negotiation can proceed, but voltage measurement precision is insufficient leading to errors in distinguishing 4.6V from 4.75V
Solution Approach 1:
The voltage detection process is segmented into multiple discrete voltage levels (0V, 4.6V, 4.75V, 5V) with clear transition thresholds. The policy engine divides the voltage range into distinct zones, each triggering specific role-swapping actions, thereby improving measurement precision through segmented voltage level recognition.
Solution Approach 2:
The system applies preliminary voltage levels (4.6V or 4.75V) to the VBUS conductor before final role assignment. By pre-applying these distinct voltage levels and observing the partner device's response (bit stream detection), the system ensures accurate role swapping before committing to final provider/consumer assignment.
2Adaptability or versatility
If the system applies vSafeDB voltage to enable dead battery operation, then power can be delivered to a dead battery, but voltage level confusion may occur between 4.6V and 4.75V
Solution Approach 1:
The system uses feedback from the partner device's bit stream response to determine which voltage level (4.6V or 4.75V) was successfully applied. The policy engine monitors whether the partner device detects the voltage and sends appropriate capability messages, allowing the system to confirm the actual voltage level through feedback rather than relying solely on local voltage measurements.
Solution Approach 2:
The bit stream communication acts as an intermediary to convey voltage level information between devices. Instead of directly measuring and comparing voltages, the system uses the partner device's bit stream response as a mediator to indirectly determine which voltage level is present, resolving the voltage distinction problem through communication rather than direct measurement.
3Ease of operation
If the policy engine transitions states based on voltage detection, then role swapping can occur, but timing synchronization between devices may be lost
Solution Approach 1:
The policy engine implements periodic state transitions with defined timing intervals for voltage application and bit stream detection. By using periodic action sequences (apply voltage → wait for bit stream → transition state), the system maintains timing synchronization between provider and consumer devices while automating the role swapping process.
Data Source
AI summary
A VBUS conductor is checked to determine whether a voltage on the VBUS conductor is greater than a vSafe0V voltage within a detect time interval. A device policy manager applies a vSafeDB voltage to the VBUS conductor when the voltage on the VBUS conductor is greater than the vSafe0V voltage. The policy engine waits for a bit stream to be detected within a timer interval. When the bit stream is not detected within the timer interval, the device policy manager is instructed to apply the vSafe0V voltage to the VBUS conductor. The device policy manager applies a vSafe5V voltage to the VBUS conductor when the bit stream is detected, and the policy engine waits for the bit stream to stop within a device ready timer interval. When the bit stream has stopped within the device ready timer interval, the policy engine sends capabilities as a source port.