Charging control method, system, device, charging equipment and readable storage medium

Abstract

This application relates to a charging control method, system, apparatus, charging device, and readable storage medium. The method includes: when a load is connected to the charging channel of the charging control system, acquiring the requested power of the load; based on the requested power, controlling the output power of the charging channel according to local control commands received by a touchscreen and / or remote cloud commands issued by an IoT cloud platform; both the touchscreen and the IoT cloud platform are connected to the main control unit. This method can improve the flexibility of charging protocol scheduling.

Description

Technical Field

[0001] This application relates to the field of battery technology, and in particular to a charging control method, system, device, charging equipment, and readable storage medium. Background Technology

[0002] With the widespread adoption of smart terminals, fast charging technology has been widely applied. Currently, the mainstream fast charging protocols include Universal Serial Bus Power Delivery (USB PD) and the Universal Fast Charging Specification (UFCS). However, most fast chargers or charging stations on the market currently adopt a standalone blind charging mode. After the device is connected, a protocol handshake is automatically initiated, and power is output according to the protocol negotiation result. When multiple devices are connected for charging at the same time, the charging device can only rely on its locally preset fixed logic to complete the power allocation, which is not flexible enough in terms of protocol scheduling. Summary of the Invention

[0003] Therefore, it is necessary to provide a charging control method, system, device, charging equipment, computer-readable storage medium, and computer program product that can improve the flexibility of protocol scheduling in response to the above-mentioned technical problems.

[0004] In a first aspect, this application provides a charging control method applied to the main control unit of a charging control system, comprising:

[0005] When a load is connected to the charging channel of the charging control system, the requested power of the load is obtained.

[0006] Based on the requested power, the output power of the charging channel is controlled according to the local control instructions received by the touchscreen and / or the remote cloud instructions issued by the IoT cloud platform; both the touchscreen and the IoT cloud platform are connected to the main control unit.

[0007] In one embodiment, the charging control system includes at least one of the charging channels;

[0008] The step of controlling the output power of the charging channel based on the requested power, according to local control commands received by the touchscreen and / or remote cloud commands issued by the IoT cloud platform, includes:

[0009] The power budget for each of the charging channels is determined based on the requested power.

[0010] If the sum of the power budgets exceeds a preset threshold, the power budgets are reallocated according to the target control command to obtain the reallocated power budgets for each charging channel; the target control command is determined according to the local control command and / or the remote cloud command, and the preset threshold includes the total output power of the charging control system;

[0011] The output power of the charging channel is controlled according to the redistribution power budget.

[0012] In one embodiment, controlling the output power of the charging channel according to the redistributed power budget includes:

[0013] When the real-time power requested by the load matches the redistribution power budget, the pulse width modulation duty cycle of the power conversion circuit in the charging channel is locked.

[0014] If the real-time power requested by the load does not match the redistribution power budget, a charging anomaly message for the charging channel is reported to the touchscreen and / or the IoT cloud platform.

[0015] In one embodiment, before controlling the output power of the charging channel according to the redistributed power budget, the method further includes:

[0016] A protocol reconstruction instruction is sent to the protocol handshake chip corresponding to the charging channel, so that the protocol handshake chip modifies the protocol message according to the protocol reconstruction instruction and obtains the modified protocol message.

[0017] The protocol handshake chip is controlled to send a reset command to the load, causing the load to respond to the reset command and re-initiate the protocol handshake request according to the modified protocol message; the protocol handshake request includes the real-time power.

[0018] Receive the real-time power reported by the protocol handshake chip.

[0019] In one embodiment, after obtaining the requested power of the load, the method further includes:

[0020] If it is detected that the charging channel is not bound to the IoT cloud platform, a binding prompt message is generated through the touch screen or the IoT communication module; the IoT communication module is used to connect the main control unit to the IoT cloud platform.

[0021] In one embodiment, the IoT cloud platform stores the correspondence between registered account identifiers, charging device identifiers, and powered device identifiers;

[0022] The method further includes:

[0023] Receive a handshake token issued by the IoT cloud platform; the handshake token is associated with whether the power receiving device identifier contains the load identifier of the load;

[0024] Based on the handshake token, determine the power level broadcast by the protocol handshake chip.

[0025] Secondly, this application also provides a charging control system, including a main control unit, a touch screen, an Internet of Things cloud platform, and a multi-channel charging output module. The multi-channel charging output module is configured with charging channels, and the touch screen and the Internet of Things cloud platform are both connected to the main control unit.

[0026] The touchscreen is used to receive local control commands and send the local control commands to the main control unit;

[0027] The IoT cloud platform is used to send remote cloud commands to the main control unit;

[0028] The main control unit is used to obtain the requested power of the load when the charging channel is connected to the load, and control the output power of the charging channel based on the requested power, according to the local control command and / or the remote cloud command.

[0029] Thirdly, this application also provides a charging control device, applied to the main control unit of a charging control system, comprising:

[0030] A load request power acquisition module is used to acquire the requested power of the load when the charging channel of the charging control system is connected to a load.

[0031] The channel output power determination module is used to control the output power of the charging channel based on the requested power, according to the local control command received by the touch screen and / or the remote cloud command issued by the IoT cloud platform; both the touch screen and the IoT cloud platform are connected to the main control unit.

[0032] Fourthly, this application also provides a charging device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described in any of the first aspects above.

[0033] Fifthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in any of the first aspects above.

[0034] Sixthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in any of the first aspects above.

[0035] The aforementioned charging control method, system, device, charging equipment, computer-readable storage medium, and computer program product, when a load is connected to the charging channel of the charging control system, obtain the requested power of the load, and based on the requested power, control the output power of the charging channel according to the local control instructions received by the touch screen and / or the remote cloud instructions issued by the IoT cloud platform. Both the touch screen and the IoT cloud platform are connected to the main control unit, and can dynamically adjust the output power of the charging channel in a comprehensive manner when a load is connected to the charging channel, combining the local instructions provided by the user through the touch screen and the cloud instructions issued by the remote IoT cloud platform, thereby improving the flexibility of protocol scheduling. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0037] Figure 1 This is a structural block diagram of the charging control system in one embodiment;

[0038] Figure 2 This is a schematic diagram of the structure of a smart charging control system based on the binding of the Internet of Things and the UFCS protocol in one embodiment;

[0039] Figure 3 This is a flowchart illustrating a charging control method in one embodiment;

[0040] Figure 4 This is a flowchart illustrating a smart charging control method based on the binding of the Internet of Things and the UFCS protocol in one embodiment.

[0041] Figure 5 This is a flowchart illustrating the charging control method in another embodiment;

[0042] Figure 6 This is a structural block diagram of a charging control device in one embodiment;

[0043] Figure 7 This is an internal structural diagram of a charging device in one embodiment. Detailed Implementation

[0044] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0045] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0046] Figure 1 A structural block diagram of a charging control system is provided. Figure 1 The charging control system may include a main control unit 100, a touch screen 102, an IoT cloud platform 104, and a multi-channel charging output module 106. The main control unit 100 may be connected to the touch screen 102, the IoT cloud platform 104, and the multi-channel charging output module 106 respectively. The multi-channel charging output module 106 may be configured with one or more charging channels 108, and each charging channel 108 may be plugged into a load.

[0047] In one exemplary embodiment, such as Figure 2 As shown, the charging control system can consist of a control center, an IoT cloud platform, and multiple charging output modules.

[0048] The control center can be, but is not limited to, an industrial touchscreen all-in-one machine or a rack-mounted operation console with a built-in microcontroller unit (MCU) main control board. The control center can integrate the main control unit and the touchscreen, which are electrically connected. The main control unit, also known as an MCU, can be, but is not limited to, various MCU main control boards. The touchscreen can be, but is not limited to, an LCD touchscreen display or a touch panel, used to display the status of each charging channel and receive local control commands from the user.

[0049] An IoT cloud platform can be, but is not limited to, various cloud servers. The main control unit and the IoT cloud platform can be connected via an IoT communication module. The IoT communication module can be a hardware module that provides functions such as data interaction, and can, but is not limited to, supporting Wi-Fi, Bluetooth, ZigBee, or cellular network communication, for data interaction between the control center and the IoT cloud platform, enabling functions such as device binding, remote command reception, and charging data reporting.

[0050] A multi-channel charging output module can be a hardware module that provides functions such as protocol handshaking, power conversion, and multiple outputs. A multi-channel charging output module can include multiple independent charging channels, each of which can be configured with a protocol handshaking chip and a power conversion circuit. The protocol handshaking chip is a dedicated integrated circuit that integrates charging communication protocol logic, and can have built-in PD protocol and UFCS protocol. The power conversion circuit is the electrical circuit that realizes the conversion of electrical energy form.

[0051] In one exemplary embodiment, such as Figure 3 As shown, a charging control method is provided, which is applied to Figure 1 Taking the main control unit 100 as an example, the explanation includes the following steps:

[0052] Step S202: When a load is connected to the charging channel of the charging control system, obtain the requested power of the load.

[0053] The charging channel can be a single channel capable of outputting electrical energy from a multi-channel charging output module, possessing an independent electrical circuit and a port for connecting to the load. The load, also known as the receiving device, includes, but is not limited to, various lithium battery packs, energy storage battery banks, drone batteries, electric vehicle power batteries, portable energy storage power supplies, and various rechargeable energy storage devices. The requested power refers to the power parameters related to the load's request for charging, including but not limited to the requested voltage and current.

[0054] Optionally, when a load is connected to a charging channel of the charging control system, the multi-channel charging output module of the charging control system can obtain the requested power of the load and report the requested power to the main control unit. Correspondingly, the main control unit receives the requested power from the load. In practical applications, when any charging channel of the multi-channel charging output module is connected to a load, the protocol handshake chip of the charging channel can perform a PD and / or UFCS protocol handshake with the load to obtain the requested power parameters of the load, including but not limited to the voltage and current requested by the load. The protocol handshake chip can then report the requested power parameters of the load to the main control unit, enabling the main control unit to obtain the voltage and current requested by the load.

[0055] Step S204: Based on the requested power, control the output power of the charging channel according to the local control command received by the touch screen and / or the remote cloud command issued by the IoT cloud platform; both the touch screen and the IoT cloud platform are connected to the main control unit.

[0056] Local control commands can be control signals generated by the system's local human-machine interaction and sent to the main control unit. Remote cloud commands can be remote control signals generated by the IoT cloud platform and sent to the main control unit via the network. Output power refers to parameters related to the power output of the charging channel, including but not limited to output voltage and current.

[0057] Optionally, after receiving the power request from the load, the main control unit can determine the output power of the charging channels of the multi-channel charging output module based on the local control commands input by the user via the touchscreen and / or the remote cloud commands issued by the IoT cloud platform, and control the corresponding charging channels based on the determined output power. In practical applications, after receiving the power request parameters from the load, the main control unit can determine whether the charging channel has completed device binding and permission verification with the IoT cloud platform. If not bound, the user can be prompted to bind via the touchscreen or IoT communication module. Otherwise, if already bound, the main control unit can generate a power allocation command based on the local control commands input via the touchscreen or the remote cloud commands issued by the IoT cloud platform, combined with the power request parameters from the load. The main control unit can then send the power allocation command to the corresponding charging channel, controlling the power conversion circuit in the multi-channel charging output module to output voltage and current to the load according to the specified PD and / or UFCS protocols.

[0058] The above-mentioned charging control method obtains the requested power of the load when the charging channel of the charging control system is connected to the load. Based on the requested power, the output power of the charging channel is controlled according to the local control command received by the touch screen and / or the remote cloud command issued by the IoT cloud platform. Both the touch screen and the IoT cloud platform are connected to the main control unit. When the charging channel is connected to the load, the output power of the charging channel can be dynamically adjusted in combination with the local command provided by the user through the touch screen and the cloud command issued by the remote IoT cloud platform, which improves the flexibility of protocol scheduling.

[0059] In an exemplary embodiment, the charging control system includes at least one charging channel; step S204 may specifically include: determining the power budget of each charging channel based on the requested power; if the sum of the power budgets exceeds a preset threshold, reallocating the power budget according to a target control command to obtain the reallocated power budget of each charging channel; the target control command is determined based on a local control command and / or a remote cloud command, and the preset threshold includes the total output power of the charging control system; and controlling the output power of the charging channel according to the reallocated power budget.

[0060] Here, power budget refers to the output power allocated by the main control unit to the charging channel. Redistributed power budget refers to the redefined output power allocation for the charging channel. Target control command refers to the final charging control command determined by combining local control commands and remote cloud commands. Total output power refers to the sum of output power that the charging control system can provide when all charging channels are charging simultaneously.

[0061] Optionally, the main control unit can determine the target control command based on the local control command received from the touchscreen and / or the remote cloud command issued by the IoT cloud platform. Combining this with the load's requested power, the main control unit determines the power budget for each charging channel based on the target control command. If the sum of the power budgets for each charging channel does not exceed the total output power of the charging control system, the output power of each charging channel can be controlled according to the power budget. Otherwise, if the sum of the power budgets for each charging channel exceeds the total output power of the charging control system, the power budget for each charging channel can be reallocated based on the target control command, resulting in a reallocated power budget. In practical applications, command priorities can be set internally within the MCU. For example, the priority of safety protection commands can be set higher than that of local control commands, and the priority of local control commands can be set higher than that of remote cloud commands. Safety protection commands are control commands that require protection for safety reasons. When they conflict with local control commands or remote cloud commands, the safety protection commands take precedence. When both local control commands and remote cloud commands are received simultaneously, arbitration can be performed based on priority to generate a target control command. For example, if no safety protection command is set, since the local control command has a higher priority than the remote cloud command, the local control command can be used as the target control command. Based on the local control command and the requested power of the load connected to the charging channel, the power budget of each charging channel is determined. The sum of the power budgets of all charging channels of the multi-channel charging output module is calculated to obtain the total power budget. If the total power budget does not exceed the total output power of the charging device, the output power of each charging channel can be controlled according to the power budget. Otherwise, if the total power budget exceeds the total output power of the charging device, the power budget of each charging channel can be reallocated using methods such as power degradation and reallocation, and the output power of each charging channel can be controlled according to the obtained reallocated power budget.

[0062] In this embodiment, the power budget of each charging channel is determined based on the requested power. When the sum of the power budgets exceeds a preset threshold, the power budget is redistributed according to the target control command to obtain the redistributed power budget of each charging channel. The target control command is determined based on local control commands and / or remote cloud commands. The preset threshold includes the total output power of the charging control system. By controlling the output power of the charging channel according to the redistributed power budget, the limited total power resources of the system can be fully utilized. In the scenario where the total power exceeds the limit, power degradation allocation is completed based on priority, ensuring stable charging of critical channel loads, while avoiding overall power overload, protecting the safety of hardware circuits, and improving the reliability of multi-channel parallel charging operation.

[0063] In an exemplary embodiment, the step of controlling the output power of the charging channel according to the redistribution power budget may specifically include: locking the pulse width modulation duty cycle of the power conversion circuit in the charging channel when the real-time power requested by the load matches the redistribution power budget; and reporting a charging abnormality message of the charging channel to the touch screen and / or the IoT cloud platform when the real-time power requested by the load does not match the redistribution power budget.

[0064] Real-time power refers to the charging power requested by the load in real time. Charging error messages are messages that reflect charging channel abnormalities.

[0065] Optionally, the multi-channel charging output module can report the real-time power requested by the load to the main control unit. The main control unit can compare the real-time power requested by the load with the determined redistribution power budget. If the real-time power matches the redistribution power budget, the pulse width modulation (PWM) duty cycle of the charging channel power conversion circuit can be locked to complete the power allocation. Otherwise, if the real-time power does not match the redistribution power budget, a charging channel charging anomaly message can be reported to the touch screen and / or IoT cloud platform. In practical applications, the protocol handshake chip can report the actual power (real-time power) re-requested by the load to the MCU. The MCU can verify whether the actual power matches the power budget (e.g., they are the same). If they match, the PWM duty cycle of the current power conversion circuit is locked to complete the allocation. If they do not match, the anomaly is recorded and reported to the touch screen or cloud.

[0066] In this embodiment, when the real-time power requested by the load matches the redistribution power budget, the pulse width modulation duty cycle of the power conversion circuit in the charging channel is locked. When the real-time power requested by the load does not match the redistribution power budget, a charging anomaly message of the charging channel is reported to the touch screen and / or IoT cloud platform. This allows for real-time verification of the matching between the actual load power and the channel target budget. By locking the PWM duty cycle, the charging output is stabilized. When the power does not match, anomalies are identified in a timely manner and alarms are pushed, which facilitates maintenance and troubleshooting, and ensures that the charging process is controllable and the system operates safely.

[0067] In an exemplary embodiment, prior to the step of controlling the output power of the charging channel according to the redistributed power budget, the method may further include: sending a protocol reconfiguration instruction to the protocol handshake chip corresponding to the charging channel, causing the protocol handshake chip to modify the protocol message according to the protocol reconfiguration instruction to obtain the modified protocol message; controlling the protocol handshake chip to send a reset instruction to the load, causing the load to respond to the reset instruction and re-initiate the protocol handshake request according to the modified protocol message; the protocol handshake request includes real-time power; and receiving the real-time power reported by the protocol handshake chip.

[0068] The protocol reconfiguration instruction can be a signaling message instructing the protocol handshake chip to reconfigure the protocol messages. The protocol messages can be, but are not limited to, PD protocol or UFCS protocol messages. The reset instruction can be a signaling message instructing the load to perform a soft reset or hard reset. The protocol handshake request is a message from the load requesting protocol negotiation with the protocol handshake chip.

[0069] Optionally, after determining the power budget or reallocating the power budget for each charging channel, the main control unit can send a protocol reconfiguration command to the protocol handshake chip of the charging channel. The protocol handshake chip can modify the protocol message according to the received protocol reconfiguration command to form a modified protocol message. Then, the main control unit can control the protocol handshake chip to send a reset command to the load. The load can respond to the reset command and re-initiate a protocol handshake request to the protocol handshake chip according to the modified protocol message. The protocol handshake request can include the real-time power of the load requesting to charge. The protocol handshake chip can report the real-time power of the load requesting to charge to the main control unit, and the main control unit receives the real-time power reported by the protocol handshake chip.

[0070] In practical applications, the MCU can send protocol reconfiguration commands to the protocol handshake chip of the corresponding charging channel via the Inter-Integrated Circuit (I2C) bus or the Serial Peripheral Interface (SPI) bus to dynamically modify its source capabilities messages. For example, for the PD protocol, it can modify the broadcast lists of its fixed voltage level (Power Data Object, PDO) and variable voltage level (Augmented PDO, APDO) to remove voltage and / or current levels that exceed the budget; for the UFCS protocol, it can modify the voltage and / or current configuration fields in its UFCS capability information frame to limit the maximum output current and / or shield specific voltage segments. After the message reconfiguration is complete, the MCU can control the protocol handshake chip to send a soft reset or hard reset command to the load, forcibly interrupting the current charging and forcing the load to re-initiate the protocol handshake request based on the new source capabilities message.

[0071] In this embodiment, by sending a protocol reconstruction instruction to the protocol handshake chip corresponding to the charging channel, the protocol handshake chip modifies the protocol message according to the protocol reconstruction instruction, obtains the modified protocol message, controls the protocol handshake chip to send a reset instruction to the load, causes the load to respond to the reset instruction, and re-initiates the protocol handshake request according to the modified protocol message. The protocol handshake request includes real-time power. By receiving the real-time power reported by the protocol handshake chip, the source-end capability message can be dynamically reconstructed and the protocol renegotiation can be triggered. Without modifying the hardware circuit, the output level can be limited according to the power budget, actively guide the load to initiate compliant power requests, avoid power over-limit at the protocol level, and improve the real-time performance and compatibility of multi-channel power scheduling.

[0072] In an exemplary embodiment, after step S202 above, the method may further include: if it is detected that the charging channel is not bound to the IoT cloud platform, generating a binding prompt message through a touch screen or an IoT communication module; the IoT communication module is used to connect the main control unit to the IoT cloud platform.

[0073] Among them, the binding prompt information can be a message indicating that the charging channel is not bound to the IoT cloud platform.

[0074] Optionally, after obtaining the requested power from the load, the main control unit can determine whether the charging channel to which the load is connected is already bound to the IoT cloud platform. If not bound, a binding prompt message can be generated via the touchscreen or IoT communication module, prompting the user to bind the charging channel to the IoT cloud platform. After successful binding, the main control unit can control the output power of the charging channel based on the local control commands input via the touchscreen and / or the remote cloud commands issued by the IoT cloud platform, combined with the requested power from the load. In practical applications, the MCU can determine whether the current charging channel has completed device binding and permission verification with the IoT cloud platform. If not bound, the user can be prompted to bind via the touchscreen or IoT communication module. After successful binding, the MCU can generate power allocation commands for the charging channel based on the local control policies input via the touchscreen or the remote control policies issued by the IoT cloud platform, combined with the requested power from the load.

[0075] In this embodiment, when it is detected that the charging channel is not bound to the IoT cloud platform, a binding prompt message is generated through the touch screen or the IoT communication module. The IoT communication module is used to connect the main control unit to the IoT cloud platform, which can promptly identify the unbound status of the device and push the binding prompt through the local touch screen and the communication module to remind the operator to complete the device network binding, ensure normal data interaction between the MCU and the IoT cloud platform, and ensure the availability of remote monitoring and remote management functions.

[0076] In an exemplary embodiment, the IoT cloud platform stores the correspondence between registered account identifiers, charging device identifiers, and powered device identifiers; the above-mentioned charging control method may further include: receiving a handshake token issued by the IoT cloud platform; associating the handshake token with a load identifier in the powered device identifier to determine whether the load is included; and determining the power level broadcast by the protocol handshake chip based on the handshake token.

[0077] Among these, the registered account identifier refers to the unique identity account generated by the user during registration on the IoT cloud platform. The charging device identifier refers to the identifier of the charging device, such as the charger's serial number (SN). The receiving device identifier refers to the identifier of the receiving device, such as the unique identifier (UID) built into the load to be charged (the receiving device). The handshake token refers to the permission identification data issued by the IoT cloud platform to the main control unit, which can be used, but is not limited to, to mark the trust level of the currently connected load. The power level refers to a standardized combination of voltage and current output published by the charging protocol, representing the charging power specifications that the charging device can provide.

[0078] Optionally, the IoT cloud platform can pre-store the correspondence between the registered account identifier, the charging device identifier, and the powered device identifier. If the load identifier of the load to be charged is identified in the powered device identifier, the load to be charged can be considered a trusted device. In this case, the IoT cloud platform can issue a handshake token with higher privileges to the main control unit. Otherwise, if the load identifier of the load to be charged is not identified in the powered device identifier, the load to be charged is considered an unfamiliar device. In this case, the IoT cloud platform can issue a handshake token with restricted privileges to the main control unit. The main control unit can determine the power level broadcast by the protocol handshake chip based on the received handshake token. For example, an IoT cloud platform can maintain a whitelist mapping table containing the correspondence between IoT accounts, charger serial numbers, and powered device UIDs. When the UID of the access load is identified in the powered device UID list, the access load is determined to be a trusted device, and a "high-privilege handshake token" is issued by the cloud. Otherwise, the access load is determined to be an unfamiliar device, and a "restricted-level handshake token" is issued. After receiving the handshake token issued by the IoT cloud platform, the MCU can intervene in the protocol handshake phase based on the handshake token. For the "high-privilege handshake token," the protocol handshake chip can be allowed to broadcast the complete PD / UFCS maximum power level (e.g., 100W). For the "restricted-level handshake token," the MCU can force the protocol handshake chip to only broadcast the basic security level (e.g., 5V / 2A or PD 18W).

[0079] In this embodiment, by receiving a handshake token issued by the IoT cloud platform, the handshake token is associated with the load identifier in the identifier of the powered device to determine whether the load is included. Based on the handshake token, the power level broadcast by the protocol handshake chip is determined, which can effectively prevent unauthorized devices from occupying high-power fast charging resources, avoid the risk of power theft, and improve the operational safety of shared charging scenarios.

[0080] To facilitate a deeper understanding of the embodiments of this application by those skilled in the art, a specific example will be used for illustration below.

[0081] This application provides a system and method for integrating Internet of Things (IoT) smart control on top of the PD / UFCS protocol, and centrally managing the output of the PD / UFCS protocol via a touchscreen. In an exemplary embodiment, such as... Figure 2 As shown, a smart charging control system based on the Internet of Things and the UFCS protocol is provided. The system includes:

[0082] The control center includes a main control MCU (main control unit) and a touch screen electrically connected to the main control MCU. The touch screen is used to display the status of each charging channel and receive local control commands from the user.

[0083] The IoT communication module connects to the main control MCU and is used to interact with the control center and the IoT cloud platform to enable device binding, remote command reception and charging data reporting.

[0084] A multi-channel charging output module, connected to the main control MCU, includes multiple independent charging channels. Each charging channel is equipped with a protocol handshake chip and a power conversion circuit, supporting PD protocol and UFCS protocol.

[0085] The main control MCU is configured to control the PD / UFCS protocol handshake strategy and power output allocation of each charging channel in the multi-channel charging output module according to the local control commands received by the touch screen or the remote cloud commands received by the IoT communication module.

[0086] In one embodiment, the IoT communication module supports Wi-Fi, Bluetooth, ZigBee, or cellular network communication; the system binds the Media Access Control (MAC) address or device ID with the user's mobile terminal or smart home gateway through the IoT communication module to achieve exclusive binding between UFCS protocol devices and IoT accounts.

[0087] In one embodiment, the protocol handshake chip has built-in PD protocol and UFCS protocol. When a load is connected, the protocol handshake chip first tries the UFCS protocol handshake. If the handshake fails, it degrades to the PD protocol handshake and reports the handshake result and the voltage and current parameters requested by the load to the main control MCU.

[0088] In one embodiment, the control interface of the touch screen may include a channel status display area, a power allocation setting area, a timing control area, and a protocol preference setting area; the user can force a certain charging channel to output only the UFCS protocol or only the PD protocol through the protocol preference setting area.

[0089] In one exemplary embodiment, such as Figure 4 As shown, a smart charging control method based on the binding of the Internet of Things and the UFCS protocol is provided and applied to the above-mentioned charging control system. The method may include the following steps:

[0090] Step S301: The load is connected to any charging channel of the multi-channel charging output module. The protocol handshake chip performs a PD / UFCS protocol handshake with the load to obtain the load's requested power parameters and report them to the main control MCU.

[0091] In step S302, the main control MCU determines whether the current charging channel has completed device binding and permission verification with the IoT cloud platform; if not, it prompts the user to bind the device via the touch screen or IoT communication module.

[0092] Step S303: After successful binding, the main control MCU generates a power allocation command based on the local control policy input on the touch screen or the remote control policy issued by the IoT cloud platform, combined with the requested power parameters.

[0093] In step S304, the main control MCU sends the power distribution command to the corresponding charging channel, and controls the power conversion circuit to output the corresponding voltage and current to the load according to the specified PD or UFCS protocol standard;

[0094] In step S305, during the charging process, the main control MCU collects the voltage (V), current (I) and temperature data of each channel in real time, displays them locally on the touch screen, and synchronizes them to the IoT cloud platform through the IoT communication module.

[0095] In one embodiment, a specific processing flow for the control protocol handshake strategy and power output allocation is provided. The control process of the main MCU is refined into a low-level hardware interaction flow that sequentially executes instruction arbitration, protocol message reconstruction, triggers renegotiation, and performs closed-loop feedback. This allows for deep intervention at the charging protocol's underlying level, rather than simple on / off control. The specific processing flow is as follows:

[0096] Step 1, Instruction Arbitration and Priority Resolution: The main control MCU maintains an instruction priority state machine. When it receives local touch screen instructions (local control instructions) and remote cloud instructions at the same time, it arbitrates according to the priority of security protection instructions > local manual intervention instructions (local control instructions) > remote regular scheduling instructions and remote cloud instructions to generate the final control strategy.

[0097] Step 2, Global Power Pool Update and Budget Recalculation: The main control MCU maintains a global power state pool (PowerBudget Pool). According to the control strategy, it recalculates the target power budget for each charging channel. If the sum of the target power of all channels exceeds the total system power, the power degradation and reallocation algorithm is triggered.

[0098] Step 3, Dynamic Reconstruction of Protocol Messages: The main control MCU sends configuration commands to the protocol handshake chip of the corresponding charging channel via the I2C / SPI bus to dynamically modify its source-side capability messages. For the PD protocol, the broadcast lists of its PDO and APDO are modified to remove voltage / current levels that exceed the budget; for the UFCS protocol, the voltage / current configuration fields in its UFCS capability information frame are modified to limit the maximum output current or block specific voltage segments.

[0099] Step 4, Trigger Protocol Renegotiation: After the message reconstruction is completed, the main control MCU controls the protocol handshake chip to send a soft reset or hard reset command to the load, forcibly interrupting the current charging and forcing the load to re-initiate the handshake request based on the new source capability message.

[0100] Step 5, Closed-loop feedback and status locking: The protocol handshake chip reports the actual power requested by the load to the main control MCU. The main control MCU checks whether the actual output power is consistent with the target budget. If they are consistent, it locks the PWM duty cycle of the current power conversion circuit and completes the allocation. If they are inconsistent, it records the abnormality and reports it to the touch screen or cloud.

[0101] In one embodiment, a permission verification and binding process for a charging control method is provided. Traditional methods only operate at the network layer (such as MAC address binding) or the physical layer (plug and charge), while this application implements a two-layer deep binding of network layer accounts combined with protocol layer device fingerprints, solving the problems of traditional methods being unable to identify pure charging devices that are not connected to Wi-Fi and being unable to perform power-level permission control.

[0102] Specifically, traditional smart sockets or chargers typically bind users via Wi-Fi MAC addresses, but many powered devices (such as mobile phones and tablets) cannot obtain MAC addresses when only charging and not connected to the internet; furthermore, traditional methods can only control power on / off, not the output protocol or power level. This application's protocol-layer device fingerprint extraction, when a load is connected, the protocol handshake chip not only negotiates power but also actively reads the underlying hardware fingerprint (such as VID / PID, device serial number UID, or UFCS device certificate) of the powered device through the Vendor Defined Message (VDM) of the PD protocol or the device identification information frame of the UFCS protocol. The main control MCU reports this protocol-layer UID to the cloud platform via the IoT module.

[0103] The two-layer mapping and dynamic permission issuance mechanism includes: the cloud platform maintains a three-layer whitelist mapping table of an IoT account, charger SN code, and powered device UID. When the UID of the access device is identified as belonging to the trusted device of the account, the cloud issues a high-privilege handshake token; if it is an unfamiliar device UID, a restricted-level handshake token is issued.

[0104] The token-based handshake intervention mechanism includes: after the main control MCU receives the token, it intervenes during the protocol handshake phase. For high-privilege handshake tokens, the protocol handshake chip is allowed to broadcast the complete UFCS / PD maximum power level (e.g., 100W); for restricted-level handshake tokens, the main control MCU forces the protocol handshake chip to broadcast only the basic security level (e.g., 5V / 2A or PD18W).

[0105] In this way, precise access control is achieved by recognizing the device, not the cable. Even if a stranger uses the same charging cable to plug into the charger, they cannot steal the high-power fast charging access, thus completely solving the problems of power theft and battery safety hazards in shared charging scenarios.

[0106] The present application will now be described in further detail with reference to the accompanying drawings and specific embodiments.

[0107] In one embodiment, the system hardware architecture is as follows: Figure 2 As shown, this system mainly includes a control center, an IoT communication module, and a multi-channel charging output module. The core of the control center is a main control MCU (such as an ARM Cortex-M series chip), which is connected to a capacitive touchscreen (such as a 7-inch or 10-inch LCD screen). The IoT communication module uses a Wi-Fi + Bluetooth dual-mode chip, responsible for communicating with the home router and cloud server. The multi-channel charging output module includes four Type-C charging ports. Each port is independently configured with a UFCS / PD dual-protocol identification chip and a corresponding DC-DC power conversion circuit. The main control MCU communicates with each protocol identification chip via I2C or UART bus.

[0108] In one embodiment, a method for binding the Internet of Things (IoT) and the UFCS protocol is provided. Upon first use, the user scans the device's QR code via a mobile app, and the IoT communication module binds the device's unique serial number (SN) to the user's cloud account. Simultaneously, the system records the UID of the load device (such as a UFCS-enabled mobile phone) connected to the charger. When the phone is connected again, the system confirms it as a bound, trusted device using the device identification field in the UFCS protocol, automatically unlocking the highest fast charging capability (e.g., UFCS 100W). If an unbound, unfamiliar device is connected, the system prompts the user for confirmation via the touchscreen, or defaults to standard PD 18W slow charging to ensure electrical safety.

[0109] In one embodiment, a touchscreen control and power scheduling method is provided, assuming the total system power is 200W and includes four interfaces. When interface 1 is connected to a laptop (requesting PD 100W) and interface 2 is connected to a mobile phone (requesting UFCS 66W), the user can perform the following operations on the touchscreen in the control center:

[0110] Check status: The screen displays in real time that interface 1 outputs 20V / 5A (PD) and interface 2 outputs 11V / 6A (UFCS);

[0111] Manual intervention: If the user wants the phone to be fast charged first, they can click "Interface 2 priority" on the touch screen. After receiving the instruction, the main control MCU will re-handshake with the laptop at Interface 1 using the PD protocol, reduce its voltage to 15V / 3A (45W), and allocate the saved power to Interface 2 to ensure the phone is fully charged.

[0112] Protocol Lock: Users can force interface 3 to be locked to "UFCS Only Mode" on the touch screen. In this mode, if a device that only supports proprietary protocols or ordinary PD is connected, interface 3 will refuse to output or only output 5V / 2A basic safety voltage.

[0113] In one embodiment, a remote control and smart electricity usage method is provided, whereby the IoT cloud platform can issue control strategies based on the grid's peak-valley electricity price periods. During peak electricity consumption periods, the cloud sends a "power limiting command" to the main control MCU via the IoT communication module. The main control MCU then controls all charging channels to reduce their maximum output power and displays "Currently in energy-saving mode" on the touchscreen. During off-peak hours at night, full-power UFCS / PD fast charging output is automatically restored.

[0114] In one embodiment, a manual intervention bucking method is provided, which elevates manual intervention bucking from a simple action description to a dynamic power redistribution algorithm based on priority and protocol level alignment with a mathematical model. The specific algorithm model and implementation steps are as follows:

[0115] When the user manually intervenes on the touchscreen (such as setting "Interface 2 priority"), it increases the total power demand of the system. Greater than the total available power of the system At this time, the main control MCU executes the following algorithm:

[0116] Step 1, Parameter Initialization and Gap Calculation: Obtain the current requested power for each channel. and user-defined priority weights (For example, preferred interface) Standard interface ), calculate the power gap: .

[0117] Step 2, Theoretical Power Reduction Allocation (based on the inverse of weights): Calculate the theoretical power reduction amount that each channel should bear. The lower the priority of a channel, the greater the reduction; calculation formula: ; Calculate the theoretical target power for each channel: .

[0118] Step 3, Protocol Alignment (PDO / APDO Mapping): Since the PD / UFCS protocol does not support arbitrary continuous voltage / current output, it is necessary to... Align to the standard discrete voltage levels supported by the protocol (such as PD's 5V / 9V / 12V / 15V / 20V, or UFCS's continuous voltage adjustment step). The main control MCU searches for values ​​less than or equal to in the registers of the protocol handshake chip. The maximum standard protocol level is used as the actual power allocation. The constraints can be: It must be greater than the minimum sustaining power allowed by the channel protocol. (e.g., 5V / 0.5A), otherwise directly reduce to... .

[0119] Step 4, Secondary Compensation for the Difference (Closed-Loop Correction): Due to the rounding down of the protocol gear alignment, an unallocated residual power difference will occur: The main control MCU will Compensation is given to the highest priority channel that has not yet reached its requested power, and protocol level alignment is performed again until... The power level is less than the minimum protocol step power or all high-priority channels are at full power.

[0120] In one embodiment, a specific example of a power degradation redistribution algorithm is provided.

[0121] Assuming a total power consumption of 200W, interface 1 (laptop) requests 100W (PD 20V / 5A), and interface 2 (mobile phone) requests 66W (UFCS11V / 6A). The total demand is 166W < 200W, so full output is used. At this time, interface 3 connects to a tablet requesting 60W, increasing the total demand to 226W, resulting in a shortfall. Users can set interface 2 as the preferred interface (weight 10) on the touchscreen, while interfaces 1 and 3 are set to normal (weight 1).

[0122] The specific calculation process of the power degradation and redistribution algorithm can be summarized as follows:

[0123] Step 1: Do not reduce interface 2; reduce interfaces 1 and 3 by 13W each.

[0124] Step 2, Interface 1 theoretical target: 100-13=87W. The main control MCU performs protocol level alignment, searching downwards in the PD protocol to match 15V / 5A (75W) or 20V / 4A (80W). Let's assume alignment is to 20V / 4A (80W).

[0125] Step 3, Interface 3 theoretical target: 60-13=47W. Align to PD 15V / 3A (45W);

[0126] Step 4, remaining difference: (87-80)+(47-45)=9W. This 9W is compensated to the highest priority interface 2. Interface 2 originally requested 66W, plus 9W, it becomes 75W, which is aligned to UFCS 11V / 6.8A (74.8W) or 15V / 5A (75W).

[0127] Step 5: Finally, the main control MCU sends out the reconstructed PDO / APDO to trigger renegotiation.

[0128] The aforementioned charging control system and method allow users to intuitively view the charging status of each interface and manually intervene or allocate the output power of each interface in multi-device charging scenarios (such as homes, offices, and public places), achieving centralized management and visual control. Furthermore, it enables deep integration of charging devices with smart home or IoT cloud platforms, achieving remote authorization, timed charging, electricity consumption data statistics, and intelligent scheduling based on grid load, realizing IoT linkage capabilities. Moreover, when multiple devices are connected simultaneously, dynamic adjustments can be made based on the user's actual priority needs or strategies issued by the IoT cloud, further improving the flexibility of protocol scheduling.

[0129] In one exemplary embodiment, such as Figure 5 As shown, a charging control method is provided, which includes the following steps:

[0130] Step S401: When a load is connected to the charging channel of the charging control system, obtain the requested power of the load.

[0131] Step S402: Determine the power budget for each charging channel based on the requested power.

[0132] Step S403: If the sum of the power budgets exceeds a preset threshold, the power budgets are reallocated according to the target control command to obtain the reallocated power budgets for each charging channel. The target control command is determined based on the local control command received by the touch screen and / or the remote cloud command issued by the IoT cloud platform. Both the touch screen and the IoT cloud platform are connected to the main control unit. The preset threshold includes the total output power of the charging control system.

[0133] Step S404: Send a protocol reconfiguration instruction to the protocol handshake chip corresponding to the charging channel, so that the protocol handshake chip modifies the protocol message according to the protocol reconfiguration instruction and obtains the modified protocol message.

[0134] Step S405: The control protocol handshake chip sends a reset command to the load, causing the load to respond to the reset command and re-initiate the protocol handshake request according to the modified protocol message; the protocol handshake request includes the real-time power requested by the load.

[0135] Step S406: Receive the real-time power reported by the protocol handshake chip;

[0136] Step S407: If the real-time power matches the redistribution power budget, lock the pulse width modulation duty cycle of the power conversion circuit in the charging channel; if the real-time power does not match the redistribution power budget, report a charging abnormality message of the charging channel to the touch screen and / or IoT cloud platform.

[0137] Optionally, the main control unit can determine the target control command based on the local control command received from the touchscreen and / or the remote cloud command issued by the IoT cloud platform. When a load is connected to the charging channel of the charging control system, the protocol handshake chip of the charging channel can report the requested power of the load to the main control unit. The main control unit can determine the power budget of each charging channel of the charging control system based on the received requested power. When the sum of the power budgets of each charging channel exceeds the total output power of the charging control system, the power budget is reallocated according to the target control command to obtain the reallocated power budget of each charging channel. Afterwards, the main control unit can send a protocol reconstruction command to the protocol handshake chip. The protocol handshake chip modifies the protocol message according to the received protocol reconstruction command to form a modified protocol message. The main control unit can also control the protocol handshake chip to send a reset command to the load. The load responds to the reset command and re-initiates the protocol handshake request according to the modified protocol message. The protocol handshake request can include the real-time power requested by the load. The protocol handshake chip can report the real-time power requested by the load to the main control unit. The main control unit can compare the real-time power requested by the load with the determined redistribution power budget. If the real-time power matches the redistribution power budget, the PWM duty cycle of the charging channel power conversion circuit can be locked to complete the power distribution. Otherwise, if the real-time power does not match the redistribution power budget, a charging channel charging abnormality message can be reported to the touch screen and / or IoT cloud platform.

[0138] The above-mentioned charging control method can dynamically adjust the output power of the charging channel by combining local commands provided by the user through the touch screen and cloud commands issued by the remote IoT cloud platform when there is a load connected to the charging channel, thereby improving the flexibility of protocol scheduling.

[0139] In one exemplary embodiment, a charging control system is provided, including a main control unit, a touch screen, an Internet of Things (IoT) cloud platform, and a multi-channel charging output module. The multi-channel charging output module is configured with charging channels, and the touch screen and the IoT cloud platform are both connected to the main control unit.

[0140] The touchscreen is used to receive local control commands and send them to the main control unit.

[0141] The Internet of Things (IoT) cloud platform is used to send remote cloud commands to the main control unit;

[0142] The main control unit is used to obtain the requested power of the load when the charging channel is connected to a load, and based on the requested power, control the output power of the charging channel according to local control instructions and / or remote cloud instructions.

[0143] Optionally, when a load is connected to the charging channel of the charging control system, the multi-channel charging output module of the charging control system can obtain the requested power of the load and report the requested power to the main control unit. After receiving the requested power of the load, the main control unit can determine the output power of the charging channel of the multi-channel charging output module based on the local control command input by the user through the touch screen and / or the remote cloud command issued by the IoT cloud platform, and control the corresponding charging channel based on the determined output power.

[0144] Since the specific processing procedures of the main control unit, touch screen, IoT cloud platform and multi-channel charging output module have been described in detail in the aforementioned embodiments, they will not be repeated here.

[0145] The aforementioned charging control system can dynamically adjust the output power of the charging channel by combining local commands provided by the user through the touch screen and cloud commands issued by the remote IoT cloud platform when there is a load connected to the charging channel, thereby improving the flexibility of protocol scheduling.

[0146] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0147] Based on the same inventive concept, this application also provides a charging control device for implementing the charging control method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more charging control device embodiments provided below can be found in the limitations of the charging control method described above, and will not be repeated here.

[0148] In one exemplary embodiment, such as Figure 6 As shown, a charging control device is provided, including: a load request power acquisition module and a channel output power determination module, wherein:

[0149] The load request power acquisition module 502 is used to acquire the requested power of the load when the charging channel of the charging control system is connected to a load.

[0150] The channel output power determination module 504 is used to control the output power of the charging channel based on the requested power, according to the local control command received by the touch screen and / or the remote cloud command issued by the IoT cloud platform; both the touch screen and the IoT cloud platform are connected to the main control unit.

[0151] In an exemplary embodiment, the channel output power determination module 504 is further configured to determine the power budget of each charging channel based on the requested power; if the sum of the power budgets exceeds a preset threshold, reallocate the power budget according to a target control instruction to obtain a redistributed power budget for each charging channel; the target control instruction is determined based on the local control instruction and / or the remote cloud instruction, and the preset threshold includes the total output power of the charging control system; and control the output power of the charging channel according to the redistributed power budget.

[0152] In an exemplary embodiment, the channel output power determination module 504 is further configured to lock the pulse width modulation duty cycle of the power conversion circuit in the charging channel when the real-time power requested by the load matches the redistribution power budget; and to report a charging abnormality message of the charging channel to the touch screen and / or the Internet of Things cloud platform when the real-time power requested by the load does not match the redistribution power budget.

[0153] In an exemplary embodiment, the channel output power determination module 504 is further configured to send a protocol reconstruction instruction to the protocol handshake chip corresponding to the charging channel, so that the protocol handshake chip modifies the protocol message according to the protocol reconstruction instruction to obtain the modified protocol message; control the protocol handshake chip to send a reset instruction to the load, so that the load responds to the reset instruction and re-initiates the protocol handshake request according to the modified protocol message; the protocol handshake request includes the real-time power; and receive the real-time power reported by the protocol handshake chip.

[0154] In an exemplary embodiment, the charging control device further includes a channel binding identification module, which generates binding prompt information via the touch screen or the IoT communication module when it is detected that the charging channel is not bound to the IoT cloud platform; the IoT communication module is used to connect the main control unit to the IoT cloud platform.

[0155] In an exemplary embodiment, the charging control device further includes a power level determination module, configured to receive a handshake token issued by the IoT cloud platform; the handshake token is associated with whether the power receiving device identifier contains the load identifier of the load; and the power level broadcast by the protocol handshake chip is determined based on the handshake token.

[0156] Each module in the aforementioned charging control device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of the charging device in hardware form or independent of it, or stored in the memory of the charging device in software form, so that the processor can call and execute the operations corresponding to each module.

[0157] In one exemplary embodiment, a charging device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 7 As shown, the charging device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores charging control data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network. When the computer program is executed by the processor, it implements a charging control method.

[0158] Those skilled in the art will understand that Figure 7 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the charging device to which the present application is applied. A specific charging device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0159] In one exemplary embodiment, a charging device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0160] In one exemplary embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above-described method embodiments.

[0161] In one exemplary embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0162] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0163] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0164] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0165] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A charging control method, characterized in that, The main control unit used in the charging control system includes: When a load is connected to the charging channel of the charging control system, the requested power of the load is obtained. Based on the requested power, the output power of the charging channel is controlled according to the local control instructions received by the touchscreen and / or the remote cloud instructions issued by the IoT cloud platform; both the touchscreen and the IoT cloud platform are connected to the main control unit.

2. The method according to claim 1, characterized in that, The charging control system includes at least one of the charging channels; The step of controlling the output power of the charging channel based on the requested power, according to local control commands received by the touchscreen and / or remote cloud commands issued by the IoT cloud platform, includes: The power budget for each of the charging channels is determined based on the requested power. If the sum of the power budgets exceeds a preset threshold, the power budgets are reallocated according to the target control command to obtain the reallocated power budgets for each charging channel; the target control command is determined according to the local control command and / or the remote cloud command, and the preset threshold includes the total output power of the charging control system; The output power of the charging channel is controlled according to the redistribution power budget.

3. The method according to claim 2, characterized in that, Controlling the output power of the charging channel according to the redistributed power budget includes: When the real-time power requested by the load matches the redistribution power budget, the pulse width modulation duty cycle of the power conversion circuit in the charging channel is locked. If the real-time power requested by the load does not match the redistribution power budget, a charging anomaly message for the charging channel is reported to the touchscreen and / or the IoT cloud platform.

4. The method according to claim 3, characterized in that, Before controlling the output power of the charging channel according to the redistributed power budget, the method further includes: A protocol reconstruction instruction is sent to the protocol handshake chip corresponding to the charging channel, so that the protocol handshake chip modifies the protocol message according to the protocol reconstruction instruction and obtains the modified protocol message. The protocol handshake chip is controlled to send a reset command to the load, causing the load to respond to the reset command and re-initiate the protocol handshake request according to the modified protocol message; the protocol handshake request includes the real-time power. Receive the real-time power reported by the protocol handshake chip.

5. The method according to claim 1, characterized in that, After obtaining the requested power of the load, the process also includes: If it is detected that the charging channel is not bound to the IoT cloud platform, a binding prompt message is generated through the touch screen or the IoT communication module; the IoT communication module is used to connect the main control unit to the IoT cloud platform.

6. The method according to any one of claims 1 to 5, characterized in that, The IoT cloud platform stores the correspondence between registered account identifiers, charging device identifiers, and powered device identifiers; The method further includes: Receive a handshake token issued by the IoT cloud platform; the handshake token is associated with whether the power receiving device identifier contains the load identifier of the load; Based on the handshake token, determine the power level broadcast by the protocol handshake chip.

7. A charging control system, characterized in that, It includes a main control unit, a touch screen, an IoT cloud platform, and a multi-channel charging output module. The multi-channel charging output module is configured with charging channels. The touch screen and the IoT cloud platform are both connected to the main control unit. The touchscreen is used to receive local control commands and send the local control commands to the main control unit; The IoT cloud platform is used to send remote cloud commands to the main control unit; The main control unit is used to obtain the requested power of the load when the charging channel is connected to the load, and control the output power of the charging channel based on the requested power, according to the local control command and / or the remote cloud command.

8. A charging control device, characterized in that, The main control unit used in the charging control system includes: A load request power acquisition module is used to acquire the requested power of the load when the charging channel of the charging control system is connected to a load. The channel output power determination module is used to control the output power of the charging channel based on the requested power, according to the local control command received by the touch screen and / or the remote cloud command issued by the IoT cloud platform; both the touch screen and the IoT cloud platform are connected to the main control unit.

9. A charging device, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images