An automobile emergency power supply self-adaptive output method and system based on dynamic power management

Through protocol identification and dynamic power allocation, the automotive emergency power supply automatically adjusts its output voltage and current modes, solving the problem of unintelligent device identification and power allocation in existing technologies, and realizing a highly efficient and compatible emergency power supply system.

CN120942213BActive Publication Date: 2025-12-09HANGZHOU BAIYU TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202511495226.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2025-10-20
Publication Date
2025-12-09
Estimated Expiration
2045-10-20

AI Technical Summary

Technical Problem

Existing car emergency power supplies cannot automatically identify charging protocols and power requirements based on different devices, resulting in a single output method, unintelligent power distribution, poor interface compatibility, energy waste, and devices failing to charge properly.

Method used

The charging protocol type and power requirements of the device are identified by the protocol handshake signal. Combined with the device priority data and the remaining power of the emergency power supply, the power is dynamically allocated in real time, and the output voltage and current mode are adjusted by the programmable DC-DC converter.

Benefits of technology

It enables intelligent power management of automotive emergency power supplies in multi-device scenarios, improves charging efficiency and device compatibility, reduces energy waste, and ensures orderly power supply to various functional modules and system stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120942213B_ABST
    Figure CN120942213B_ABST
Patent Text Reader

Abstract

The application relates to the technical field of vehicle-mounted emergency power supplies and management thereof, and particularly discloses a method and system for self-adaptive output of a vehicle emergency power supply based on dynamic power management, the method comprising the following steps: acquiring the device connection state of each output port of the vehicle emergency power supply and the residual power of the vehicle emergency power supply in real time; when a device is connected, identifying the charging protocol type and power demand parameters of the device through a protocol handshake signal; acquiring preset device priority data, and dynamically allocating the power of each output port according to the identification result, the device priority data and the residual power of the vehicle emergency power supply; and controlling the output port to switch to a matched voltage and current mode, so that orderly power supply between functional modules is ensured in actual multi-module combination use. In a vehicle-mounted environment, the excellent performance of interface plug-and-play, protocol automatic identification and multi-device dynamic combination output is realized, and the use convenience and safety are obviously improved.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle-mounted emergency power supply and its management, in particular to a method and system for adaptive output of automobile emergency power supply based on dynamic power management. BACKGROUND

[0002] At present, the common automobile emergency power supply on the market is mainly used for vehicle starting and mobile device charging, and generally only has single-port or simple multi-port output function with fixed voltage output. For example, some portable starting power supplies are configured with one USB-A port or a small number of USB ports for charging mobile phones and other devices, but these interfaces can usually only output fixed 5V or 12V voltage and cannot actively adjust the output mode according to the needs of different devices.

[0003] In addition, existing products often lack the ability to identify connected device protocols, and cannot identify charging protocols such as USB PowerDelivery, Qualcomm Quick Charge, and Samsung AFC, resulting in devices being unable to charge at the optimal voltage and current, thereby reducing charging efficiency.

[0004] In multi-functional use scenarios, such as providing high current for automobile emergency starting, wirelessly charging a mobile phone, inflating a tire, powering a car vacuum cleaner or car washing pump, etc., the above defects are particularly evident: on the one hand, due to the single output mode and lack of protocol negotiation, it is often impossible to meet the power supply needs of high-power devices, resulting in power waste or starting failure; on the other hand, when different interface standards and protocols are not compatible, the device may not be able to charge normally or may need to be manually switched, which is inconvenient. For example, if a smartphone supports QC protocol, it can only get 5V output, which significantly reduces the charging speed. In summary, the existing automobile emergency power supply has the following main deficiencies in output mode and power management: single output mode, no support for automatic protocol identification and switching; unintelligent power distribution, unable to dynamically respond to the needs of multi-device scenarios; poor interface compatibility, prone to interface mismatch and energy waste.

[0005] In view of the above deficiencies of the prior art, the present application aims to solve the following technical problems: how to enable an automobile emergency power supply to automatically identify the charging and power supply protocols and power requirements of connected devices and dynamically adjust the output mode and power distribution in a device diversification scenario. Specifically, the technical problems of existing emergency power supplies include:

[0006] Existing power supply interfaces only provide fixed output and cannot automatically switch voltage levels and protocol modes according to different device requirements;

[0007] When facing multiple simultaneously connected devices, existing power supplies cannot intelligently distribute output power, and high-power devices cannot be preferentially powered;

[0008] Current emergency power supplies cannot distinguish the charging protocol types used by connected devices and are not aware of the optimal charging parameters required by each device, resulting in poor compatibility and energy waste. SUMMARY

[0009] The present application aims to provide a dynamic power management-based automotive emergency power supply adaptive output method and system to solve the problems raised in the background art.

[0010] To achieve the above-mentioned purpose, the present application provides the following technical solution: a dynamic power management-based automotive emergency power supply adaptive output method, the method comprising:

[0011] Real-time acquisition of the device connection state of each output port of the automotive emergency power supply and the remaining power of the automotive emergency power supply;

[0012] When a device is connected, identify the charging protocol type and power demand parameters of the device through a protocol handshake signal;

[0013] Acquire preset device priority data and dynamically allocate power to each output port in real time according to the identification result, device priority data, and remaining power of the automotive emergency power supply;

[0014] Control the output port to switch to a matched voltage and current mode.

[0015] As a further solution of the present application, the step of identifying the charging protocol type and power demand parameters of the device through a protocol handshake signal when a device is connected specifically comprises:

[0016] For Type-C interfaces, preferentially use USB PD protocol handshake to acquire the voltage and current request of the device;

[0017] If the PD protocol does not respond, sequentially detect QC protocol handshake signals and AFC protocol pulse signals;

[0018] If no protocol is identified, output preset default safety parameters.

[0019] As a further solution of the present application, the step of dynamically allocating power to each output port in real time according to the identification result, device priority data, and remaining power of the automotive emergency power supply specifically comprises:

[0020] Confirm the safety state of the automotive emergency power supply;

[0021] Sort the devices in the identification result according to the priority data based on bubble sort to generate a device list;

[0022] Acquire the remaining power of the automobile emergency power supply, traverse the device list, if the remaining power is sufficient, allocate the required power, if the remaining power is insufficient, allocate 80% of the remaining power or turn off the low-priority device.

[0023] As a further scheme of the present application, the step of switching the output port to a matching voltage-current mode specifically comprises:

[0024] Adjusting the output voltage level through a programmable DC-DC converter;

[0025] Setting the upper limit of the current according to the protocol type;

[0026] Performing voltage safety detection before switching.

[0027] As a further scheme of the present application, it further comprises monitoring the load of each output port and the total load power in real time, and when an overload risk is detected or the total power of multiple ports approaches the power limit, scheduling the power of each output port based on the device priority data.

[0028] The present application also provides an automobile emergency power supply adaptive output system based on dynamic power management, for implementing an automobile emergency power supply adaptive output method based on dynamic power management, the system comprising:

[0029] A data acquisition module for acquiring the device connection state of each output port of the automobile emergency power supply and the remaining power of the automobile emergency power supply in real time;

[0030] A protocol identification module for identifying the charging protocol type and power demand parameters of the device through the protocol handshake signal when the device is connected;

[0031] A dynamic power management module for acquiring preset device priority data, and dynamically allocating the power of each output port in real time according to the identification result, the device priority data, and the remaining power of the automobile emergency power supply;

[0032] An interface adaptation module for controlling the output port to switch to a matching voltage-current mode.

[0033] As a further scheme of the present application, the protocol identification module specifically comprises:

[0034] A PD protocol handshake unit for preferentially using the USB PD protocol handshake for the Type-C interface, and acquiring the voltage and current request of the device;

[0035] A remaining protocol handshake unit for sequentially detecting the QC protocol handshake signal and the AFC protocol pulse signal if the PD protocol is not responded;

[0036] A default output unit for outputting preset default safety parameters if no protocol is identified.

[0037] Compared with the prior art, the application has the following advantages:

[0038] Because the power can be dynamically allocated according to the device protocol and real-time load, the traditional output-demand mismatch problem is solved, and the energy waste is greatly reduced. For example, when charging a smartphone, the system automatically identifies and provides QC or PD fast charging support without manual switching, so that the charging rate approaches the nominal maximum value.

[0039] In actual multi-module combination use, the orderly power supply between the functional modules is ensured. In the vehicle starting scene, the emergency power supply can provide a large current output for the engine; when powering high-power devices such as air pumps or car washing pumps, the system preferentially meets the current use of the device, and other ports are automatically current-limited or powered off, so that the required power can be stably output in various working conditions.

[0040] In a vehicle environment, the application realizes the excellent performance of interface plug-and-play, protocol automatic identification, and multi-device dynamic combination output. Compared with the prior art product, the method significantly improves the convenience and safety of use. The user does not need to pay attention to the voltage protocol required by the device, and the system will automatically adapt and the power output is more stable and reliable, effectively improving the efficiency and reliability of emergency power supply. BRIEF DESCRIPTION OF DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the application, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description only some embodiments of the application.

[0042] Figure 1 A flowchart of a self-adaptive output method of an automobile emergency power supply based on dynamic power management provided by the embodiment of the application.

[0043] Figure 2 A flowchart of a step of identifying the charging protocol type and power demand parameters of a device through a protocol handshake signal when the device is connected, provided by the embodiment of the application.

[0044] Figure 3 A flowchart of a step of dynamically allocating power to each output port in real time according to the identification result, device priority data, and remaining power of the automobile emergency power supply, provided by the embodiment of the application.

[0045] Figure 4 A component structure block diagram of a self-adaptive output system of an automobile emergency power supply based on dynamic power management provided by the embodiment of the application.

[0046] Figure 5 A component structure block diagram of a protocol identification module provided by the embodiment of the application. DETAILED DESCRIPTION

[0047] In order to make the technical problems to be solved by the present application, technical solutions and beneficial effects clearer, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and not used to limit the present application.

[0048] Figure 1 For a flow chart of a self-adaptive output method of an automobile emergency power supply based on dynamic power management, in the embodiment of the present application, a self-adaptive output method of an automobile emergency power supply based on dynamic power management, the method comprises:

[0049] Step S100, real-time acquisition of the device connection state of each output port of the automobile emergency power supply and the remaining power of the automobile emergency power supply;

[0050] Step S200, when a device is connected, identifying the charging protocol type and power demand parameter of the device through a protocol handshake signal;

[0051] Step S300, acquiring preset device priority data, and dynamically allocating the power of each output port in real time according to the identification result, the device priority data and the remaining power of the automobile emergency power supply;

[0052] Step S400, controlling the output port to switch to a matched voltage and current mode.

[0053] In the embodiment, a microcontroller MCU is included, which is the core control unit of the whole system, responsible for real-time monitoring of the connection state and power state of all output interfaces, and unified coordination and management of each functional module. Once a device is detected to be connected, the microcontroller can query the information returned by the protocol identification module to determine the device type and power demand, and send control instructions to the corresponding output interface based on the preset power scheduling algorithm. When it is detected that it is a power supply device, dynamic power management is performed to output the best charging power of the device.

[0054] As shown in Figure 3 As a preferred embodiment of the present application, when a device is connected, the step of identifying the charging protocol type and power demand parameter of the device through a protocol handshake signal specifically comprises:

[0055] Step S201, preferentially adopting USB PD protocol handshake for the Type-C interface to acquire the voltage and current request of the device;

[0056] Step S202, if the PD protocol does not respond, QC protocol handshake signals and AFC protocol pulse signals are detected in sequence;

[0057] In step S203, if no protocol is identified, the preset default security parameters are output.

[0058] In this embodiment, the charging and communication protocols used by devices connected to each interface can be detected and identified. For USB, Type-C, DC, and contact interfaces, the protocol identification module monitors the signal on the CC line and obtains the device's power requirements and voltage level through the USB PD protocol's handshake mechanism. The module identifies supported protocols such as Qualcomm Quick Charge QC and Samsung AFC by detecting the voltage levels or protocol handshake signals on the D+ and D- data lines. A dedicated detection circuit is configured for each output interface.

[0059] This module monitors signal line level changes and integrates an IP6518 chip for identifying USB PD, QC, and PD protocols. It also integrates a CHY103 chip for detecting the Apple 2.4A protocol and analyzing device handshake signals. The identified protocol type, voltage, and current requirements are transmitted to the main control MCU via an I2C interface through a data structure. After identification, the module feeds back the required output voltage, current, and other parameters to the microcontroller to guide subsequent output adjustments.

[0060] The following specific algorithms are provided:

[0061] DeviceProtocol identify_protocol(OutputPort port){

[0062] DeviceProtocol result={UNKNOWN,5000,1000}; / / Default 5V / 1A

[0063] Its function is to initialize a default protocol identification result, of type UNKNOWN, with a default output voltage of 5V and a default output current of 1A. This is to provide a safe default value when no protocol is identified.

[0064] if (port.type == TYPE_C) {

[0065] send_pd_source_capabilities(port);

[0066] if(wait_for_pd_response(port,200ms)){

[0067] result=parse_pd_response(port);

[0068] return result;

[0069] }

[0070] }

[0071] Action: If the connected port is Type-C type, try to identify through the USB Power Delivery (PD) protocol. send_pd_source_capabilities(port): Send the power supply capability information of the PD protocol to the device, ask the device to support the voltage and current; wait_for_pd_response(port, 200ms): Wait for the response of the device, the timeout time is 200 milliseconds; parse_pd_response(port): Parse the response of the device, get the supported protocol type, voltage and current demand of the device; if the PD protocol is successfully identified, return the parsed result.

[0072] if(detect_qc_handshake(port)){

[0073] result.protocol_type=QC;

[0074] result.voltage_mV=get_qc_voltage(port);

[0075] return result;

[0076] }

[0077] Action: If the PD protocol identification fails, try to identify the Qualcomm Quick Charge (QC) protocol. detect_qc_handshake(port): Detect the QC protocol handshake signal on the port; get_qc_voltage(port): Get the QC protocol voltage requested by the device (such as 9V, 12V, etc.); if the QC protocol is successfully identified, return the protocol type and voltage.

[0078] if(detect_afc_pulse(port)){

[0079] result.protocol_type=AFC;

[0080] result.voltage_mV=9000;

[0081] return result;

[0082] }

[0083] Action: If the QC protocol recognition fails, try to identify the Samsung AFC protocol. detect_afc_pulse(port): Detect the AFC protocol pulse signal on the port; if the AFC protocol is identified, return the default 9V voltage, and if the AFC protocol is successfully identified, return the protocol type and voltage.

[0084] return result;

[0085] }

[0086] As shown in Figure 3 , as a preferred embodiment of the present application, the step of dynamically allocating power to each output port according to the identification result, device priority data and remaining power of the automobile emergency power supply in real time specifically includes:

[0087] Step S301, confirm the safety state of the automobile emergency power supply;

[0088] Step S302, sort the devices in the identification result according to the priority data based on bubble sort to generate a device list;

[0089] Step S303, obtain the remaining power of the automobile emergency power supply, traverse the device list, if the remaining power is sufficient, allocate the required power, if the remaining power is insufficient, allocate 80% of the remaining power or turn off low-priority devices.

[0090] In this embodiment, the output power distribution of the power supply is dynamically adjusted according to the results of protocol identification and real-time load conditions. In use, the dynamic power management module continuously monitors the remaining power of the built-in battery pack and the current, voltage and other data of each output port. When the system detects that a port has a large load demand or the total power of multiple ports approaches the power limit, the module will start the power scheduling strategy. It ensures the power supply demand of the current high-priority task, and concentrates the available power to the port; limit the current or temporarily close the low-priority output, in order to avoid overload and rapid decline of power. This dynamic scheduling can avoid the power waste of traditional static allocation, improve energy utilization, and ensure the stability and safety of system operation in different scenarios. The algorithm of the dynamic power management module is implemented as follows.

[0091] Device priority division

[0092] Priority Device name Energy demand Highest priority Car emergency start Instant high current, 1500A peak High priority Air pump, car washer, etc. 120W Medium priority Mobile phone supporting PD protocol, etc. 22.5W Low priority Wireless charging 5~15W

[0093] Real-time power monitoring, monitoring the current, voltage and total load power of each port, monitoring the remaining power (SOC) and temperature state of the built-in battery.

[0094] Dynamic power allocation, if it is a single device scenario, directly allocate the maximum power required by the device. If it is a multi-device scenario, the total power available needs to be calculated, and the power is allocated from high to low priority to ensure that high-priority devices run at full power. If there is not enough remaining power, low-priority devices will be throttled or temporarily shut down.

[0095] The following is the specific algorithm flow:

[0096] #include<stdio.h>

[0097] #include<stdbool.h>

[0098] #include<string.h>

[0099] Device type definition:

[0100] typedef enum{

[0101] PRIORITY_EMERGENCY=0, / / Highest priority: car emergency start;

[0102] PRIORITY_HIGH, / / High priority: air pump, car washer;

[0103] PRIORITY_MEDIUM, / / Medium priority: fast charging device;

[0104] PRIORITY_LOW / / Low priority: wireless charging, etc.

[0105] }DevicePriority;

[0106] Device structure:

[0107] typedef struct{

[0108] char name

[20] ;

[0109] DevicePriority priority;

[0110] float requested_power;

[0111] float allocated_power;

[0112] bool is_enabled;

[0113] }Device;

[0114] Battery status structure:

[0115] typedef struct{

[0116] float soc;

[0117] float temperature;

[0118] bool is_safe;

[0119] }BatteryStatus;

[0120] Effect: Define a clear device priority system (emergency start > air pump / car washer > fast charging device > wireless charging), which is the basis of power dynamic allocation; The device structure not only records the requested power, but also records the actual allocated power and the enabled state, providing data support for dynamic adjustment; The battery status structure contains the power, temperature and safety flag, realizing the comprehensive state monitoring of the power supply system.

[0121] Dynamic power management function:

[0122] void dynamic_power_management(Device *devices,int device_count,BatteryStatus *battery){

[0123] const float TOTAL_POWER_LIMIT=200.0f;

[0124] float allocated_power=0.0f;

[0125] battery->is_safe=(battery->soc>10.0f&&battery->temperature<60.0f);

[0126] Sort devices by priority (simple bubble sort):

[0127] for(int i=0;i<device_count-1;i++){

[0128] for(int j=0;j<device_count-i-1;j++){

[0129] if(devices[j].priority>devices[j+1].priority){

[0130] Device temp=devices[j];

[0131] devices[j] = devices[j + 1];

[0132] devices[j + 1] = temp;

[0133] }

[0134] }

[0135] }

[0136] Dynamically allocate power:

[0137] for (int i = 0; i < device_count; i++) {

[0138] if (allocated_power + devices[i].requested_power <= TOTAL_POWER_LIMIT && battery->is_safe) {

[0139] Allocate full power:

[0140] devices[i].allocated_power = devices[i].requested_power;

[0141] devices[i].is_enabled = true;

[0142] allocated_power += devices[i].requested_power;

[0143] } else {

[0144] Allocate remaining power or turn off devices:

[0145] float remaining_power = TOTAL_POWER_LIMIT - allocated_power;

[0146] if (remaining_power > 0) {

[0147] devices[i].allocated_power = remaining_power * 0.8f;

[0148] devices[i].is_enabled = true;

[0149] } else {

[0150] devices[i].allocated_power = 0.0f;

[0151] devices[i].is_enabled = false;

[0152] }

[0153] }

[0154] }

[0155] }

[0156] Action:

[0157] Battery Safety Check: Check if the battery level is >10% and temperature <60°C to ensure the system works within a safe range, with an innovative double protection mechanism to prevent over-discharge and overheating.

[0158] Device Priority Sorting: Use bubble sort to arrange devices by priority from high to low, ensuring that high-priority devices are allocated power first.

[0159] Power Allocation Logic: First, traverse the sorted device list. If the total power is sufficient and the battery is safe, allocate all the requested power to the device. If the power is insufficient, calculate the remaining power and allocate 80%. If it is completely insufficient, turn off low-priority devices. This has a dynamic adjustment and safety buffer mechanism.

[0160] Print Device Status (for debugging):

[0161] void print_device_status(Device *devices, int device_count) {

[0162] printf("Device Status:\n");

[0163] printf("Name\t\tPriority\tRequested(W)\tAllocated(W)\tEnabled\n");

[0164] printf("-------------------------------------------------------\n");

[0165] for (int i = 0; i < device_count; i++) {

[0166] printf("%s\t\t%d\t\t%.1f\t\t%.1f\t\t%s\n",

[0167] devices[i].name,

[0168] devices[i].priority,

[0169] devices[i].requested_power,

[0170] devices[i].allocated_power,

[0171] devices[i].is_enabled?"Yes":"No");

[0172] }

[0173] printf("\n");

[0174] }

[0175] Main function (simulating test scenario):

[0176] int main(){

[0177] Initialize device list:

[0178] Device devices[]={

[0179] {"Car Starter",PRIORITY_EMERGENCY,150.0f,0.0f,false}, / / Car start (instantaneous high power);

[0180] {"Air Pump",PRIORITY_HIGH,120.0f,0.0f,false}, / / Air pump;

[0181] {"Phone Fast",PRIORITY_MEDIUM,22.5f,0.0f,false}, / / Fast charging for mobile phones;

[0182] {"Wireless",PRIORITY_LOW,10.0f,0.0f,false} / / Wireless charging;

[0183] };

[0184] int device_count=sizeof(devices) / sizeof(devices[0]);

[0185] Initialize battery status (50% charge, 40°C):

[0186] BatteryStatus battery = { 50.0f, 40.0f, true};

[0187] Simulate dynamic power management:

[0188] printf("===Initial State===\n");

[0189] print_device_status(devices, device_count);

[0190] printf("===After Power Allocation===\n");

[0191] dynamic_power_management(devices, device_count, &battery);

[0192] print_device_status(devices, device_count);

[0193] Simulate low battery scenario:

[0194] printf("===Low Battery Scenario (SOC=5%%)===\n");

[0195] battery.soc = 5.0f;

[0196] dynamic_power_management(devices, device_count, &battery);

[0197] print_device_status(devices, device_count);

[0198] return 0;

[0199] }

[0200] Purpose: Provide detailed device status output for debugging and verifying the algorithm. Contains complete test cases to simulate power allocation in different scenarios.

[0201] As a preferred embodiment of the present application, the step of switching the control output port to the matching voltage and current mode specifically includes:

[0202] Adjusting the output voltage gear through a programmable DC-DC converter;

[0203] Set the current upper limit according to the protocol type;

[0204] Perform voltage safety detection before switching.

[0205] In this embodiment, the interface adaptation module enables a single output interface to be compatible with multiple protocols and automatically switch the output mode. Specifically, each output interface is configured with a programmable DC-DC converter and a multi-gear output circuit on the hardware. Under the guidance of the protocol identification result, the module can automatically adjust the voltage level and current upper limit of the interface output. For example, when it is identified that a mobile phone device supports the USB PD protocol and requests a 9V output, the interface adaptation module will switch the output to the 9V mode; if the device only needs standard 5V charging, it will output in the 5V mode; if it is connected to other devices that require 12V, 15V or even higher voltage, it can also be switched to the 12V, 15V mode accordingly. By controlling the programmable power supply chip, the module can smoothly switch between several common voltage gears, realizing the compatibility of the interface with multiple protocols such as PD, QC, AFC, etc. In this way, no matter what standard voltage demand the device proposes, the interface can quickly match and provide output voltage and current that meet the specifications.

[0206] The interface adaptation module is responsible for dynamically adjusting the voltage and current parameters of the output interface according to the protocol identification result, and realizes multi-protocol compatibility through the control of the programmable DC-DC converter. It receives the output parameters of the protocol identification module, controls the power supply chip to switch the output voltage gear, and monitors the output state in real time and feeds back the adjustment.

[0207] The specific program of the interface adaptation algorithm is as follows:

[0208] #include<stdint.h>

[0209] #include<stdbool.h>

[0210] Define the supported output voltage gears (unit: mV):

[0211] typedef enum{

[0212] VOLTAGE_5V=5000,

[0213] VOLTAGE_9V=9000,

[0214] VOLTAGE_12V=12000,

[0215] VOLTAGE_15V=15000,

[0216] VOLTAGE_20V=20000

[0217] }OutputVoltage;

[0218] Function: Define the supported output voltage steps (5V, 9V, 12V, 15V, 20V), covering common fast charging protocol requirements to ensure compatibility.

[0219] Device protocol type (consistent with the protocol identification module):

[0220] typedef enum{

[0221] PROTOCOL_UNKNOWN = 0,

[0222] PROTOCOL_PD,

[0223] PROTOCOL_QC,

[0224] PROTOCOL_AFC,

[0225] PROTOCOL_APPLE_2_4A

[0226] }DeviceProtocol;

[0227] Function: Define the device protocol type, align with the output results of the protocol identification module, ensure data consistency between modules.

[0228] DC-DC chip control structure:

[0229] typedef struct{

[0230] uint8_t i2c_addr;

[0231] float current_limit;

[0232] bool is_ready;

[0233] }DCDC_Controller;

[0234] Function: Encapsulate the control parameters of DC-DC converter, including hardware address, current limit and state flag, provide data structure support for hardware control.

[0235] Interface adaptation state machine:

[0236] typedef enum{

[0237] STATE_IDLE,

[0238] STATE_VOLTAGE_CHANGE,

[0239] STATE_CURRENT_ADJUST,

[0240] STATE_SAFE_CHECK,

[0241] STATE_ACTIVE

[0242] }AdapterState;

[0243] Purpose: Define the states of the state machine, ensuring the safety and order of the voltage switching process.

[0244] Interface adapter main control structure:

[0245] typedef struct{

[0246] OutputPort port;

[0247] OutputVoltage target_voltage;

[0248] float target_current;

[0249] DeviceProtocol protocol;

[0250] AdapterState state;

[0251] DCDC_Controller dc_dc;

[0252] uint32_t retry_count;

[0253] }InterfaceAdapter;

[0254] Purpose: Integrate all parameters and states of the interface adapter, including target output, protocol type, hardware controller, etc., providing unified management for the core logic.

[0255] Initialize the DC-DC controller:

[0256] bool dcdc_init(DCDC_Controller* controller){

[0257] Simulate I2C initialization:

[0258] controller->is_ready=true;

[0259] return controller->is_ready;

[0260] }

[0261] Function: Initialize the DC-DC controller and mark it as ready. In practical applications, verify the chip is working properly through I2C communication. Hardware abstraction design facilitates the adaptation of different models of DC-DC chips.

[0262] Set DC-DC output voltage:

[0263] bool dcdc_set_voltage(DCDC_Controller* controller, OutputVoltage voltage){

[0264] printf("[DC-DC] Setting voltage to %dmV\n", voltage);

[0265] return true;

[0266] }

[0267] Function: Set the output voltage of the DC-DC chip through I2C commands, support multi-gear dynamic switching, meet the flexible voltage requirements of PD / QC protocols, etc.

[0268] Set DC-DC output current limit:

[0269] bool dcdc_set_current_limit(DCDC_Controller* controller, float current){

[0270] Analog current limit setting:

[0271] printf("[DC-DC] Setting current limit to %.2fA\n", current);

[0272] controller->current_limit = current;

[0273] return true;

[0274] }

[0275] Function: Dynamically adjust the current limit according to the protocol type to prevent overload. Protocol-aware current management balances efficiency and safety.

[0276] Voltage switching safety detection:

[0277] bool voltage_change_safe_check(InterfaceAdapter* adapter){

[0278] printf("[Safety] Performing pre-change check...\n");

[0279] return true;

[0280] }

[0281] Effect: Detect the load state before voltage switching to avoid hard switching caused by hardware damage, hardware protection mechanism, and improve system reliability.

[0282] Interface adapter state machine processing function:

[0283] void adapter_state_machine(InterfaceAdapter* adapter){

[0284] switch(adapter->state){

[0285] case STATE_IDLE:

[0286] if(adapter->target_voltage!=VOLTAGE_5V){

[0287] adapter->state=STATE_VOLTAGE_CHANGE;

[0288] }

[0289] break;

[0290] case STATE_VOLTAGE_CHANGE:

[0291] if(voltage_change_safe_check(adapter)){

[0292] if(dcdc_set_voltage(&adapter->dc_dc,adapter->target_voltage)){

[0293] adapter->state=STATE_CURRENT_ADJUST;

[0294] }

[0295] }else{

[0296] printf("[WARNING] Unsafe voltage change detected!\n");

[0297] adapter->state=STATE_IDLE;

[0298] }

[0299] break;

[0300] case STATE_CURRENT_ADJUST:

[0301] Set current limit according to protocol type:

[0302] switch(adapter->protocol){

[0303] Case PROTOCOL_PD:

[0304] dcdc_set_current_limit(&adapter->dc_dc,3.0f); / / Typical value for PD protocol

[0305] break;

[0306] case PROTOCOL_QC:

[0307] dcdc_set_current_limit(&adapter->dc_dc,2.0f);

[0308] break;

[0309] default:

[0310] dcdc_set_current_limit(&adapter->dc_dc,2.4f); / / Default limit

[0311] }

[0312] adapter->state=STATE_SAFE_CHECK;

[0313] break;

[0314] case STATE_SAFE_CHECK:

[0315] Simulate post safety check:

[0316] printf("[Safety] Output stabilized at %dmV\n",adapter->target_voltage);

[0317] adapter->state=STATE_ACTIVE;

[0318] break;

[0319] case STATE_ACTIVE:

[0320] break;

[0321] }

[0322] }

[0323] Function: Through the state machine to orderly manage the voltage switching process, to ensure the safety and reliability of each step of operation, phased operation process for voltage switching, current adjustment, safety confirmation, to avoid transient overload; Can dynamically match the current limit according to the protocol type; When the safety detection fails, automatically return to the idle state.

[0324] Interface adapter main function:

[0325] void interface_adapter_task(InterfaceAdapter* adapter,DeviceProtocolprotocol,

[0326] OutputVoltage voltage,float current){

[0327] Update target parameters:

[0328] adapter->protocol=protocol;

[0329] adapter->target_voltage=voltage;

[0330] adapter->target_current=current;

[0331] Processing state machine:

[0332] adapter_state_machine(adapter);

[0333] Exception handling (simplified version):

[0334] if(adapter->retry_count>3){

[0335] printf("[ERROR] Adapter failed after 3 retries!\n");

[0336] emergency_shutdown(adapter->port);

[0337] }

[0338] }

[0339] Function: Receives the output parameters (protocol type, voltage, current) of the protocol identification module, drives the state machine to run, handles abnormal situations, and responds to the protocol identification results in real time; shuts down in an emergency after a retry failure to prevent hardware damage.

[0340] Example use cases:

[0341] int main(){

[0342] / / Initialize the interface adapter;

[0343] InterfaceAdapter usb_c_adapter={

[0344] .dc_dc={.i2c_addr=0x20,.current_limit=0.0f},

[0345] .state=STATE_IDLE,

[0346] .target_voltage=VOLTAGE_5V / / Default 5V standby

[0347] };

[0348] Initialize the DC-DC controller:

[0349] if(!dcdc_init(&usb_c_adapter.dc_dc)){

[0350] printf("DC-DC init failed!\n");

[0351] return -1;

[0352] }

[0353] Analog protocol identification result (PD protocol request 20V / 3A):

[0354] printf("===PD Device Connected ===\n");

[0355] interface_adapter_task(&usb_c_adapter, PROTOCOL_PD, VOLTAGE_20V, 3.0f);

[0356] Simulate state machine running (actual application needs to be executed in a loop):

[0357] for (int i = 0; i < 5; i++) {

[0358] adapter_state_machine(&usb_c_adapter);

[0359] }

[0360] return 0;

[0361] }

[0362] Effect: Simulate PD device access scenarios, show the complete process from initialization to voltage switching, verify the feasibility of the algorithm through actual use cases, and cover typical fast charging protocols.

[0363] As a preferred embodiment of the present application, it also includes real-time monitoring of the load of each output port and the total load power. When an overload risk or the total power of multiple ports approaches the power limit is detected, the output port power is scheduled based on device priority data.

[0364] In this embodiment, by dynamically monitoring the change of port load, the microcontroller MCU can adjust the output strategy at any time during device use, such as reducing or cutting off the output in time when an overload risk is detected, to protect the safety of the power supply.

[0365] An interactive interface is provided for users, allowing manual parameter setting under special working conditions. User-defined algorithms allow users to manually adjust device priority, output voltage and current limits of specific interfaces, total power distribution strategy, and special working condition mode selection. Physical buttons and small OLED display modules are installed on the device to allow users to manually adjust.

[0366] User-defined algorithm:

[0367] typedef struct {

[0368] DevicePriority custom_priority[MAX_DEVICES];

[0369] float custom_voltage[MAX_PORTS];

[0370] float custom_current[MAX_PORTS];

[0371] bool eco_mode;

[0372] bool force_high_power;

[0373] uint8_t temperature_threshold;

[0374] }UserConfig;

[0375] Purpose: Store user-defined configuration parameters, including: device priority (allow users to manually adjust the power supply priority of different devices), output voltage and current (manually set fixed voltage and current for specific interfaces), running mode (energy-saving mode and forced high-power mode), temperature threshold (custom battery overheat protection threshold, default 60℃, user can adjust to 50℃ or 70℃), users can adjust the power supply behavior according to the scene demand, taking into account individualization and safety; through the flag bit to quickly enable special mode (such as energy-saving or high-power), without complex settings.

[0376] User configuration saved to Flash:

[0377] void save_user_config(UserConfig* config){

[0378] Implement Flash write operation:

[0379] Contains CRC check to ensure data integrity:

[0380] }

[0381] Purpose: Write user configuration to non-volatile memory Flash, which can still be retained after power failure, and user settings can be effective for a long time after setting once, improving user convenience; CRC check prevents configuration data anomalies from causing system failure.

[0382] Load user configuration from Flash:

[0383] void load_user_config(UserConfig* config) {

[0384] Implement Flash read operation:

[0385] }

[0386] Purpose: Read user configuration from Flash when the system starts, restore the last settings, users do not need to repeat the settings, use it as soon as possible after starting; CRC check ensures that the loaded configuration data is correct and accurate.

[0387] User interface processing function:

[0388] void user_interface_task(void){

[0389] }

[0390] Function: Manage user interaction logic: key input (adjust parameters through physical keys or touch screen), OLED display (real-time display of current configuration, output status and alarm information), module coordination (pass user settings to dynamic power management module and notify interface adaptation module to switch output voltage).

[0391] The invention is verified by experiments and theoretical analysis. Compared with the prior art, the invention can greatly improve the output efficiency and device compatibility of the emergency power supply, and the system can automatically identify the device protocol and dynamically adjust the output, truly realizing plug and play. The specific technical effects include:

[0392] Improve output efficiency and compatibility: Since the method can dynamically allocate power according to the device protocol and real-time load, the traditional output and demand mismatch problem is solved, greatly reducing energy waste. For example, when charging a smartphone, there is no need for manual switching, the system automatically identifies and provides QC or PD fast charging support, making the charging rate close to the nominal maximum value.

[0393] Meet the needs of multi-functional scenarios: In actual multi-module combination use, the method ensures orderly power supply between functional modules. In the vehicle starting scenario, the emergency power supply can provide a large current output for the engine; when powering high-power devices such as air pumps or car wash pumps, the system prioritizes the currently used device, and other ports are automatically current-limited or powered off, so that the required power can be stably output in various working conditions.

[0394] Experimental verification: The automobile emergency power supply controlled by the invention performs excellently in actual tests. The experimental results show that the engine starting success rate is more than 95% during emergency starting; when charging the built-in battery of the power supply using the Type-C fast charging protocol, a conventional large-capacity battery can be fully charged in 4 hours; the power distribution algorithm automation accuracy is more than 98%, that is, the system can correctly adjust the output according to the load demand without misoperation.

[0395] Comprehensive performance improvement: In a vehicle environment, the invention realizes the excellent performance of interface plug and play, protocol automatic identification, and multi-device dynamic combination output. Compared with existing technology products, the method significantly improves the convenience and safety of use. Users do not need to pay attention to the voltage protocol required by the device, the system will automatically adapt and the power output is more stable and reliable, effectively improving the efficiency and reliability of emergency power supply.

[0396] As Figure 4 shown in the embodiments of the present application, a dynamic power management based automobile emergency power supply adaptive output system is also provided for implementing a dynamic power management based automobile emergency power supply adaptive output method, and the system comprises:

[0397] A data acquisition module 100 is configured to acquire the device connection state of each output port of the automobile emergency power supply and the remaining power of the automobile emergency power supply in real time.

[0398] A protocol identification module 200 is configured to identify the charging protocol type and power demand parameter of the device through a protocol handshake signal when the device is connected.

[0399] A dynamic power management module 300 is configured to acquire preset device priority data and dynamically allocate the power of each output port in real time according to the identification result, the device priority data and the remaining power of the automobile emergency power supply.

[0400] An interface adaptation module 400 is configured to control the output port to switch to a matched voltage and current mode.

[0401] The system further comprises a master control module, which is realized by a microcontroller MCU and is the core control unit of the entire system. The master control module is responsible for real-time monitoring of the connection state and power state of all output interfaces and unified coordination and management of each functional module. Once a device is detected to be connected, the master control module can query the information returned by the protocol identification module to determine the device type and power supply demand and send a control instruction to the corresponding output interface based on a preset power scheduling algorithm. When a device is detected, the master control module controls the dynamic power management module to output the optimal charging power of the device. Through dynamic monitoring of the port load change, the master control module can adjust the output strategy at any time during the use of the device, such as timely reducing or cutting off the output to protect the power supply safety when an overload risk is detected.

[0402] The protocol identification module is configured to detect and identify the charging and communication protocols used by the devices connected to each interface. For USB, Type-C, DC and contact interfaces, the protocol identification module monitors the signal on the CC line to obtain the power demand and voltage level of the device through the USB PD protocol handshake mechanism. The voltage level or protocol handshake signal on the D+, D- data line is detected to identify the protocol type supported by the device, such as Qualcomm Quick Charge QC, Samsung AFC, etc. A dedicated detection circuit is configured for each output interface.

[0403] The integrated IP6518 chip is used for monitoring the level change of the signal line, identifying the USB PD protocol, QC protocol and PD protocol, the integrated CHY103 chip is used for detecting the Apple 2.4A protocol, the handshake signal of the device is parsed, the identified protocol type, voltage and current demand are transmitted to the host MCU through the I2C interface through the data structure, and the output voltage, current and other parameters required by the device are fed back to the host module after identification is completed, so as to guide subsequent output adjustment. Through the module, the power supply interface can have the ability of actively inquiring the requirement of the device and automatically responding.

[0404] The dynamic power management module dynamically adjusts the power output power distribution according to the protocol identification result and the real-time load condition. In the use process, the dynamic power management module continuously monitors the remaining power of the built-in battery pack and the current, voltage and other data of each output port. When the system detects that a port has a large load demand or the total power of multiple ports is close to the power limit, the module will start the power scheduling strategy. The power supply demand of the current high-priority task is ensured, and the available power is concentrated and distributed to the port; the low-priority output is current-limited or temporarily closed to avoid overload and rapid power drop. This dynamic scheduling can avoid the power waste of traditional static allocation, improve energy utilization, and ensure the stability and safety of system operation in different scenarios.

[0405] The interface adaptation module enables a single output interface to be compatible with multiple protocols and automatically switch the output mode. Specifically, each output interface is configured with a programmable DC-DC converter and a multi-gear output circuit on the hardware. Under the guidance of the protocol identification result, the module can automatically adjust the voltage level and current upper limit of the interface output. For example, when a mobile phone device supporting the USB PD protocol is identified and requests a 9V output, the interface adaptation module will switch the output to the 9V mode; if the device only needs standard 5V charging, the 5V mode is output; if other devices requiring 12V, 15V or even higher voltage are connected, the 12V, 15V mode can be switched accordingly. By controlling the programmable power chip, the module can smoothly switch between several common voltage gears, realizing the compatibility of the interface to multiple protocols such as PD, QC, AFC, etc. In this way, no matter what standard voltage demand the device proposes, the interface can quickly match and provide the output voltage and current that meet the specifications.

[0406] The interface adaptation module is responsible for dynamically adjusting the voltage and current parameters of the output interface according to the protocol identification result, and realizes multi-protocol compatibility through the control of the programmable DC-DC converter. The output parameters of the protocol identification module are received, the power chip is controlled to switch the output voltage gear, and the output state is monitored and feedback is adjusted in real time.

[0407] As a preferred embodiment of the present application, a user self-defined module is further included, which provides an interactive interface for the user to manually set parameters under special working conditions. The user self-defined algorithm allows the user to manually adjust the device priority, the output voltage and current limit of a specific interface, the total power distribution strategy and the selection of special working condition modes. Physical buttons and a small OLED display module are installed on the device to allow the user to manually adjust.

[0408] The above-mentioned functional modules work together to achieve adaptive control of the output of the automobile emergency power supply. The specific process is as follows: the main control module first scans whether there is a device connected to each output port; the protocol identification module performs a quick handshake on the connected device to determine the supported protocol and required voltage level; based on the protocol and load information, the dynamic power management module calculates the current allocatable power of each port and notifies the interface adaptation module to switch to the matching mode.

[0409] As shown in Figure 5 As a preferred embodiment of the present application, the protocol identification module specifically includes:

[0410] The PD protocol handshake unit 201 is used to preferentially perform USB PD protocol handshake on the Type-C interface to obtain the voltage and current request of the device;

[0411] The remaining protocol handshake unit 202 is used to sequentially detect QC protocol handshake signals and AFC protocol pulse signals if the PD protocol does not respond.

[0412] The default output unit 203 is used to output preset default safety parameters if no protocol is identified.

[0413] The above-mentioned only describes the preferred embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for adaptive output of an automotive emergency power supply based on dynamic power management, characterized in that, The method comprises: Real-time acquisition of the device connection state of each output port of the automobile emergency power supply and the remaining power of the automobile emergency power supply; When a device is connected, the charging protocol type and power demand parameters of the device are identified through a protocol handshake signal; Pre-set device priority data is acquired, and the power of each output port is dynamically allocated in real time according to the identification result, the device priority data and the remaining power of the automobile emergency power supply; The output port is controlled to switch to a matched voltage and current mode; The step of identifying the charging protocol type and power demand parameters of the device through a protocol handshake signal when a device is connected specifically comprises: The USB PD protocol handshake is preferentially adopted for a Type-C interface to acquire the voltage and current request of the device; If the PD protocol does not respond, QC protocol handshake signals and AFC protocol pulse signals are sequentially detected; If no protocol is identified, preset default safety parameters are outputted; The step of dynamically allocating the power of each output port in real time according to the identification result, the device priority data and the remaining power of the automobile emergency power supply specifically comprises: The safety state of the automobile emergency power supply is confirmed; The devices in the identification result are sorted according to the priority data based on bubble sorting to generate a device list; The remaining power of the automobile emergency power supply is acquired, the device list is traversed, if the remaining power is sufficient, the required power is allocated, and if the remaining power is insufficient, 80% of the remaining power is allocated or low-priority devices are turned off; The step of controlling the output port to switch to a matched voltage and current mode specifically comprises: The output voltage gear is adjusted through a programmable DC-DC converter; The current upper limit is set according to the protocol type; Voltage safety detection is performed before switching.

2. The adaptive output method of an automobile emergency power supply based on dynamic power management according to claim 1, wherein, Real-time monitoring of the load of each output port and the total load power is further included, when an overload risk or the total power of multiple ports approaches the power limit, the power of each output port is scheduled based on the device priority data.

3. A dynamic power management based automotive emergency power supply adaptive output system for implementing the dynamic power management based automotive emergency power supply adaptive output method of claim 1 or 2, characterized in that, The system comprises: A data acquisition module for real-time acquisition of the device connection state of each output port of the automobile emergency power supply and the remaining power of the automobile emergency power supply; A protocol identification module for identifying the charging protocol type and power demand parameters of the device through a protocol handshake signal when a device is connected; A dynamic power management module for acquiring pre-set device priority data and dynamically allocating the power of each output port in real time according to the identification result, the device priority data and the remaining power of the automobile emergency power supply; An interface adaptation module for controlling the output port to switch to a matched voltage and current mode.

4. The adaptive output system of emergency power supply for vehicle based on dynamic power management according to claim 3, characterized in that, The protocol identification module specifically comprises: A PD protocol handshake unit for preferentially adopting the USB PD protocol handshake for a Type-C interface to acquire the voltage and current request of the device; A remaining protocol handshake unit for sequentially detecting QC protocol handshake signals and AFC protocol pulse signals if the PD protocol does not respond; A default output unit for outputting preset default safety parameters if no protocol is identified.

Citation Information

Patent Citations

  • Emergency power supply system for intelligent door and intelligent door

    CN114899934A

  • Distribution management system and method for automobile emergency power supply

    CN116207835A