A method and system for issuing a low-temperature recharge strategy of a sodium-ion start-stop battery in an end-cloud cooperation
By receiving information from the vehicle terminal to perform strategy template matching and parameterization, the problem of adapting low-temperature recharge strategies for sodium-ion start-stop batteries has been solved, achieving self-adaptation and closed-loop iteration, and improving the efficiency and safety of low-temperature recharge.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SHENZHEN LYNNYL TECH CO LTD
- Filing Date
- 2026-03-11
- Publication Date
- 2026-06-30
AI Technical Summary
Existing low-temperature recharge strategies for sodium-ion start-stop batteries are difficult to adapt to the complex operating conditions of different vehicle models and regions, resulting in low low-temperature recharge efficiency, reduced start-stop availability, and a lack of controllable iteration mechanisms, posing safety hazards.
By receiving the charging condition parameters and vehicle configuration information reported by the vehicle terminal, the strategy template is matched in the low-temperature charging strategy library based on the temperature window or regional temperature zone. The strategy is then parameterized and adapted, forming a set of strategy parameters including the upper limit of charging current and voltage response constraints. This set is then packaged into a strategy package and distributed. Combined with anomaly handling rules and version verification, the strategy achieves self-adaptation and closed-loop iteration.
It achieves strategy self-adaptation of sodium-ion start-stop batteries under low-temperature conditions in different vehicle models, battery batches, and regions, improves low-temperature recharge efficiency and start-stop availability, reduces polarization risk and abnormal trigger probability, and has continuous optimization capabilities.
Smart Images
Figure CN122315098A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle power management and battery management technology, and in particular to a method and system for disseminating low-temperature recharge strategies for sodium-ion start-stop batteries in a cloud-edge collaborative manner. Background Technology
[0002] With the increasing prevalence of automotive start-stop systems, vehicles typically require timely recharging of the start-stop battery after engine startup to restore its charge and ensure availability for the next start-stop cycle. Compared to traditional lead-acid batteries, sodium-ion batteries offer advantages such as better resource availability and higher cost potential, leading to their gradual adoption in start-stop battery applications. However, sodium-ion batteries exhibit several drawbacks at low temperatures, including a decrease in electrochemical reaction rate, an increase in internal resistance, and a reduction in charge acceptance. During recharging, issues such as abnormal voltage response, increased polarization, reduced recharging efficiency, and frequent protection triggers can arise. In extremely cold regions, improper recharging strategies after startup can lead to insufficient recharging, degraded start-stop functionality, and even increased risks of complaints and malfunctions. Insufficient recharging constraints can introduce risks of low-temperature polarization, abnormal temperature rises, or safety hazards caused by abnormal connection resistance.
[0003] In existing technologies, vehicle-side battery management systems (BMS) often use fixed threshold tables, temperature window tables, or segmented current limits to control low-temperature recharge. This involves looking up the maximum allowable recharge current from a preset table based on a few parameters such as cell temperature, ambient temperature, and state of charge, and then applying simple protection thresholds. Such solutions typically rely on engineering calibration, have long parameter update cycles, and often employ conservative limits to ensure safety, leading to slow low-temperature recharge speeds, insufficient energy recovery, and reduced start-stop availability. Furthermore, differences in generator characteristics, load conditions, wiring harnesses and connectors between different vehicle models, as well as batch and aging variations in sodium-ion batteries, can cause the same fixed threshold table to become significantly incompatible with different vehicles and regional operating conditions. Especially in extremely cold northern environments, the fixed-table strategy lacks sufficient coverage of complex operating conditions, making it difficult to balance safety, availability, and efficiency.
[0004] Furthermore, existing policy update methods typically involve single-vehicle firmware upgrades or simple parameter distribution, lacking a unified policy library management, version control, and canary release mechanism, as well as systematic closed-loop verification. During policy distribution and execution, communication interruptions, policy mismatches, or differences in vehicle-side execution capabilities can easily lead to policies failing to take effect or uncontrollable recharging behavior. Moreover, existing solutions often handle issues such as low-temperature polarization risks, abnormal voltage response, and abnormal connection resistance in a fragmented manner, lacking a security control link throughout the entire policy distribution and execution process, making it difficult to achieve standardized closed-loop handling of anomaly detection, throttling, disconnection, and reporting. Summary of the Invention
[0005] The purpose of this application is to solve the problems mentioned above, such as the difficulty in adapting low-temperature recharge strategies and the lack of a controllable iterative mechanism.
[0006] According to one aspect of this application, a method for distributing a low-temperature recharge strategy for sodium-ion start-stop batteries with end-to-cloud collaboration is provided, comprising: Receive the charging condition parameter set and vehicle configuration information reported by the on-board terminal of the target vehicle. The vehicle configuration information includes vehicle model information and / or sodium-ion battery model or batch information. Based on the recharge condition parameter set, determine the temperature window or regional temperature zone corresponding to the target vehicle, and match the strategy template in the low temperature recharge strategy library in combination with the vehicle configuration information; Based on the recharge condition parameter set, the strategy template is parameterized to generate a strategy parameter set that includes the upper limit of recharge current, the limit of recharge current variation, the voltage response constraint, pulse temperature recovery and staged control. The strategy parameter set is adapted and verified according to the recharge condition parameter set. If the requirements are not met, the conservative strategy template is switched and regenerated. The strategy parameter set, along with the applicable fields for the working conditions, the abnormal handling rules, the version identifier, and the integrity verification information summarized from the recharge working condition parameter set, are encapsulated into a strategy package and sent to the vehicle terminal. The system receives temperature rise efficiency, recharge efficiency, and abnormal triggering information from the vehicle terminal, which are used to update the low-temperature recharge strategy library entries and / or the parameterized generation rules.
[0007] Preferably, determining the temperature window or regional temperature zone corresponding to the target vehicle based on the recharge condition parameter set includes: Time window statistics are performed on the recharge condition parameter set to obtain temperature statistics and voltage response statistics; The temperature window or regional temperature zone is assigned based on the temperature statistics, and the consistency of the assignment results is checked based on the voltage response statistics. The results of the temperature window or regional temperature zone classification are written into the working condition applicable field, and the strategy template is matched in the low temperature recharge strategy library based on the results of the temperature window or regional temperature zone classification.
[0008] Preferably, the step of matching a strategy template in the low-temperature recharge strategy library and parameterizing the strategy template based on the recharge condition parameter set includes: Using the vehicle model information and / or the sodium-ion battery model or batch information, the temperature window or regional temperature zone as matching conditions, the strategy template is selected from the low-temperature recharge strategy library; Based on the recharge condition parameter set, at least two types of parameters of the strategy template are modified, including any two types of parameters among the recharge current upper limit, recharge current variation limit, voltage response constraint, pulse temperature recovery and staged control. Write the corrected parameters into the policy parameter set.
[0009] Preferably, the adaptation and verification of the strategy parameter set according to the recharge condition parameter set includes: The parameters related to the upper limit of recharge current, the limit of recharge current variation, and the voltage response constraint in the strategy parameter set are checked for consistency with the real-time values and / or time window statistics of the recharge condition parameter set to obtain the consistency check results. When the consistency check result does not meet the preset safety boundary, at least one of the following is executed: tightening the upper limit of the recharge current, tightening the limit on the change of the recharge current, enabling stricter voltage response constraints, increasing the pulse reheat trigger threshold, and switching to conservative strategy template regeneration. The preset safety boundary is determined by the parameter boundary corresponding to the strategy template and / or the parameter boundary corresponding to the temperature window or regional temperature zone.
[0010] Preferably, the pulsed temperature recovery and phased control in the strategy package include at least: The phased control includes a preheating phase and a recharge phase, and specifies the duration range of the preheating phase and the recharge phase, as well as the phase switching conditions. The pulsed temperature recovery includes pulse triggering conditions, pulse duration, pulse interval, and pulse exit conditions; Wherein, at least one of the stage switching condition and / or the pulse triggering condition and / or the pulse exit condition is determined or verified by the recharge condition parameter set.
[0011] Preferably, the exception handling rules include at least: Low-temperature polarization risk anomaly, which is determined at least based on the deviation characteristics of the terminal voltage response and / or the abnormal characteristics of the terminal voltage change rate; The connection resistance is abnormal, and the abnormal connection resistance is determined at least based on the abrupt change characteristics of the equivalent internal resistance or connection resistance characteristic and / or the transient drop characteristics of the terminal voltage. When the abnormal low-temperature polarization risk or the abnormal connection resistance is detected, the following actions are executed in sequence: derating limit, disconnection if necessary, and reporting to the cloud, and a statistical summary of the recharge condition parameter set is generated. The statistical summary of the recharge condition parameter set, along with the applicable fields of the condition and the version identifier and integrity verification information of the strategy package, are reported as the information to be reported.
[0012] Preferably, the cloud management platform performs version consistency verification and canary rollout of the policy package, and includes rollback trigger conditions; When the temperature rise efficiency, the recharge efficiency, and the abnormal trigger information meet the rollback trigger conditions, execute the strategy rollback or switch to the conservative strategy template. The rollback triggering conditions include at least one of the following: recharge efficiency deterioration exceeding a threshold, abnormal trigger count exceeding a threshold, or the occurrence of a preset severe error code.
[0013] The present invention also provides a terminal-cloud collaborative sodium-ion start-stop battery low-temperature recharge strategy distribution system, which applies the sodium-ion start-stop battery low-temperature recharge strategy distribution method described above, including an in-vehicle terminal and a cloud management platform; The vehicle terminal includes a status monitoring module, a recharge control module, and a vehicle communication module. The status monitoring module collects the recharge conditions of the sodium-ion start-stop battery to form a recharge condition parameter set, and sends the recharge condition parameter set and vehicle configuration information to the cloud management platform through the vehicle communication module. The cloud management platform includes a cloud communication module, a strategy generation module, and a low-temperature recharge strategy library. The cloud communication module receives the recharge condition parameter set and the vehicle configuration information and transmits them to the strategy generation module. The strategy generation module generates a strategy package based on the low-temperature recharge strategy library and sends it to the vehicle terminal through the cloud communication module. The strategy package includes a set of strategy parameters, applicable fields for operating conditions, exception handling rules, version identifiers, and integrity verification information. The vehicle terminal, based on the strategy package, uses the recharge control module to perform low-temperature recharge control on the sodium-ion start-stop battery, and transmits temperature rise efficiency, recharge efficiency, and abnormal trigger information back to the cloud management platform through the vehicle communication module.
[0014] Preferably, the cloud management platform further includes a temperature window or regional temperature zone determination module and an adaptation verification module; The temperature window or regional temperature zone determination module outputs the temperature window or regional temperature zone determination result based on the recharge condition parameter set and transmits it to the strategy generation module. The adaptation verification module receives the recharge condition parameter set and the strategy parameter set and outputs the adaptation verification result. The adaptation verification result is transmitted to the strategy generation module to trigger the selection of the conservative strategy template and the regeneration of the strategy package.
[0015] Preferably, the vehicle-mounted terminal further includes a strategy package verification unit and an offline fallback unit; The policy package verification unit verifies the version identifier and integrity verification information of the policy package and outputs the policy package verification result. The offline fallback unit receives communication failure signals, version mismatch signals, and inconsistency signals for applicable working conditions, and outputs a fallback control signal to the recharge control module when the preset fallback conditions are met.
[0016] This application has the following beneficial effects: It receives the charging condition parameter set and vehicle configuration information reported by the vehicle terminal through the cloud management platform, matches the strategy template in the low temperature charging strategy library based on the temperature window or regional temperature zone, and performs parameterization generation and adaptation verification of the template in combination with the charging condition to form a strategy parameter set including the upper limit of charging current, the limit of charging current change, voltage response constraint, pulse temperature recovery and staged control. Then, it is packaged into a strategy package with applicable fields of operating conditions, abnormal handling rules, version identifier and integrity verification information and sent for execution. At the same time, it receives temperature rise efficiency, charging efficiency and abnormal trigger information for updating strategy library entries and / or generation rules. This enables the self-adaptive deployment of strategies for different vehicle models, battery batches, and low-temperature operating conditions in different regions, avoiding mismatches and overly conservative approaches under extremely cold conditions using fixed threshold tables or single calibration strategies, thus improving low-temperature recharge efficiency and start-stop availability. Through adaptation verification and anomaly handling rules, it achieves controlled handling of low-temperature polarization risks and abnormal connection resistance, reducing the risk of anomaly triggering and failure. Through version consistency verification, canary deployment, and rollback trigger conditions, it ensures controllable, traceable, and reversible strategy releases, reducing the uncertainty and maintenance costs associated with strategy updates. A closed-loop iteration mechanism driven by data feedback forms the system, enabling continuous optimization of the low-temperature recharge strategy. Attached Figure Description
[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0018] Figure 1 This is a logic block diagram of the method for disseminating the low-temperature recharge strategy of sodium-ion start-stop battery with end-to-cloud collaboration according to an embodiment of this application. Detailed Implementation
[0019] To facilitate understanding of this application, a more complete description will be provided below with reference to the accompanying drawings. Preferred embodiments of this application are shown in the drawings. However, this application can be implemented in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the disclosure of this application.
[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the specification of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The term "and / or" as used herein includes any and all combinations of one or more of the associated listed items.
[0021] Please refer to Figure 1 One embodiment of this application provides a method for disseminating a low-temperature recharge strategy for sodium-ion start-stop batteries using edge-cloud collaboration, comprising: S10. Receive the charging condition parameter set and vehicle configuration information reported by the target vehicle's onboard terminal. The vehicle configuration information includes vehicle model information and / or sodium-ion battery model or batch information. In this step, it should be noted that the onboard terminal generates the "charging condition parameter set" through status monitoring and estimation logic. This parameter set covers at least temperature, electrical status, and health / connectivity status signals, and carries a timestamp or statistical time window identifier to enable the cloud to identify operating conditions at different time scales. In addition to vehicle model information and sodium-ion battery model or batch information, the vehicle configuration information may also include the onboard terminal's hardware and software version or capability identifier to ensure compatibility between subsequent strategy package fields and edge execution capabilities. The aforementioned charging condition parameter set and vehicle configuration information are uploaded to the cloud management platform via the onboard communication link as input for strategy template matching and strategy parameter generation.
[0022] S20. Determine the temperature window or regional temperature zone corresponding to the target vehicle based on the recharge condition parameter set, and match the strategy template in the low-temperature recharge strategy library in conjunction with the vehicle configuration information. In this step, it should be noted that the cloud management platform categorizes the low-temperature environment of the target vehicle based on the recharge condition parameter set, forming a search key consistent with the entries in the low-temperature recharge strategy library, and completes strategy template matching after combining the vehicle configuration information. The regional temperature zone can be mapped according to a preset regional set or temperature distribution characteristics, and the temperature window can be divided according to the battery's low-temperature sensitive range. Both are used to transform the coarse-grained control of fixed threshold tables into a matching entry point for a "template-based strategy set," thereby providing a differentiated basic strategy framework for different regions and different vehicle models / batches.
[0023] S30. Based on the recharge condition parameter set, the strategy template is parameterized to generate a strategy parameter set that includes the upper limit of the recharge current, the limit of the recharge current variation, the voltage response constraint, pulse temperature recovery, and staged control. In this step, it should be noted that parameterization does not directly output a single current value, but rather forms an executable "strategy parameter set" based on the strategy template. This set includes at least: the control boundary of the upper limit of the recharge current, the safety convergence elements of the recharge current variation limit and voltage response constraint, and the temperature recovery enhancement elements of pulse temperature recovery and staged control. When generating the strategy parameter set, information such as temperature level, state of charge, and voltage response trend reflected in the recharge condition parameter set is referenced, transforming the strategy from a "template" into a set of deployable parameters that matches the current operating condition, and providing a checkable object for subsequent adaptation and verification.
[0024] S40. Adapt and verify the strategy parameter set according to the recharge condition parameter set. If the requirements are not met, switch to the conservative strategy template and regenerate. In this step, it should be noted that the adaptation verification is used to complete the dual check of "availability and safety" before the strategy package is issued. That is, to check the matching between the strategy parameter set and the recharge condition parameter set, so as to avoid parameter combinations that exceed the target vehicle's execution capability or conflict with the current low temperature condition. When the verification fails, the strategy is switched to the conservative strategy template or regenerated to ensure that the issued strategy converges within the safety boundary, reducing the uncertainty caused by repeated protection on the vehicle side, recharge oscillation, or strategy mismatch.
[0025] S50. Encapsulate the strategy parameter set, along with the applicable fields for the working conditions derived from the recharge working condition parameter set, anomaly handling rules, version identifier, and integrity verification information, into a strategy package and distribute it to the vehicle terminal. In this step, it should be noted that the cloud encapsulates the strategy parameter set and the applicable fields for the working conditions derived from the recharge working condition parameter set together to ensure that the vehicle terminal can determine whether the strategy is executable based on its "scope of application." Simultaneously, the anomaly handling rules, version identifier, and integrity verification information are included in the strategy package, giving the strategy verifiable, traceable, and rollback attributes. Distribution can adopt a controlled release method (e.g., gray-scale, batch, or distribution by region / vehicle type), and version consistency verification reduces policy misinstallation, duplicate loading, or field incompatibility.
[0026] S60. Receive temperature rise efficiency, recharge efficiency, and anomaly triggering information from the vehicle terminal, and use this information to update the low-temperature recharge strategy library entries and / or parameterized generation rules. In this step, it should be noted that during the execution of the strategy package, the vehicle terminal sends back temperature rise efficiency, recharge efficiency, and anomaly triggering information. The cloud management platform associates and archives this information with the issued strategy version and applicable operating condition fields, thus forming a closed-loop data structure of "strategy—operating condition—effect." Based on this, the cloud can revise the low-temperature recharge strategy library entries, correct the parameterized generation rules, and achieve continuous optimization for different temperature zones and different vehicle models / batches, while retaining rollback and traceability data to support operation and maintenance and quality analysis.
[0027] The technical solution implemented in this embodiment can, on the cloud side, use a set of recharge condition parameters and vehicle configuration information as input to complete temperature window / regional temperature zone classification, strategy template matching, parameterization generation, and adaptation verification. This is then distributed in a controlled manner as a strategy package with version and verification information. This enables self-adaptation and consistent execution of the strategy under different vehicle models, battery batches, and low-temperature regional conditions, avoiding problems such as insufficient coverage, update difficulties, and excessive conservatism leading to low recharge efficiency and reduced start-stop availability associated with traditional fixed threshold table strategies. Simultaneously, the strategy package incorporates anomaly handling rules and adaptation verification mechanisms, reducing the risks of low-temperature polarization, abnormal voltage response, and abnormal connection resistance causing recharge oscillations and frequent protection triggers, thus improving the safety and stability of low-temperature recharge. Furthermore, by driving the update of strategy library entries and / or generation rules through the transmitted temperature rise efficiency, recharge efficiency, and anomaly trigger information, a closed-loop iteration is formed, enabling the low-temperature recharge strategy to have sustainable optimization capabilities. Combined with version management, strategy releases are traceable and reversible, reducing operational risks and the probability of complaint failures.
[0028] Furthermore, determining the temperature window or regional temperature zone corresponding to the target vehicle based on the recharge condition parameter set includes: S21. Perform time window statistics on the recharge condition parameter set to obtain temperature statistics and voltage response statistics. In this step, it should be noted that the purpose of performing time window statistics on the recharge condition parameter set in the cloud is to smooth the impact of instantaneous sampling noise, communication jitter, and short-term load disturbances on temperature judgment, thereby forming a stable representation that can be used for classification. The time window can be sliced according to the recharge stage after vehicle start-stop, the vehicle driving / idling stage, or a preset statistical period. This generates statistics reflecting the current low temperature level and its changing trend for temperature signals, and simultaneously generates voltage response statistics for the combined changes in voltage and current, used to characterize the voltage response characteristics under low-temperature recharge, so as to reasonably constrain the subsequent determination results of temperature windows or regional temperature zones.
[0029] S22. Obtain the classification results of temperature windows or regional temperature zones based on temperature statistics, and perform consistency verification on the classification results of temperature windows or regional temperature zones based on voltage response statistics. In this step, it should be noted that temperature statistics are used to map the current operating condition of the target vehicle to a preset temperature window or regional temperature zone, thereby determining the operating condition entry point for subsequent strategy library retrieval and template selection; voltage response statistics are used to perform consistency verification on this mapping result, avoiding misclassification caused solely by temperature, such as deviations caused by lag in ambient temperature changes, sampling bias, or short-term recharge disturbances; the consistency verification is manifested in the determination and correction triggering of the credibility of the classification results, making the selection of temperature windows or regional temperature zones more consistent with the actual recharge response characteristics of the vehicle, thereby reducing the probability of strategy template mismatch.
[0030] S23. Write the temperature window or regional temperature zone classification results into the operating condition applicable field, and match the strategy template in the low-temperature recharge strategy library based on the temperature window or regional temperature zone classification results. In this step, it should be noted that writing the temperature window or regional temperature zone classification results into the operating condition applicable field makes the subsequently generated strategy package have a clear "applicable scope identifier", which the vehicle terminal can use to judge the applicability of the strategy and perform pre-execution verification; at the same time, the cloud uses the classification results as one of the search keys in the strategy library to complete the strategy template matching, so that the strategy selection is transformed from the traditional "fixed threshold table" to the selection process of "template-based strategy set", and forms a differentiated strategy entry for different regional temperature zones, supporting regional adaptation under extremely cold conditions in the north.
[0031] The technical solution implemented in this embodiment can obtain more stable temperature and voltage response characteristics through time window statistics, reducing the impact of sampling noise and short-term disturbances on operating condition judgment; by using voltage response statistics to verify the consistency of temperature window or regional temperature zone classification results, it can reduce policy template mismatch caused by temperature classification errors and improve the reliability of policy matching; and by writing the classification results into the operating condition applicable field, it can provide a verifiable basis for the applicable scope of policy package execution, enhance the controllability and traceability of policy issuance and execution, thereby improving the adaptability and stability of the low-temperature recharge policy under low-temperature operating conditions in different regions.
[0032] Furthermore, matching strategy templates in the low-temperature recharge strategy library and parameterizing the strategy templates based on the recharge condition parameter set includes: S31. Select a strategy template from the low-temperature recharge strategy library using vehicle model information and / or sodium-ion battery model or batch information, temperature window, or regional temperature zone as matching conditions. In this step, it should be noted that when selecting a strategy template from the low-temperature recharge strategy library in the cloud, vehicle model information and / or sodium-ion battery model or batch information, temperature window, or regional temperature zone are used as joint matching conditions. The purpose is to first determine the applicable objects of the "strategy framework": vehicle model differences correspond to differences in generator characteristics, start-stop load, and energy recovery requirements; battery model or batch differences correspond to differences in low-temperature tolerance and polarization sensitivity; and temperature window or regional temperature zone corresponds to differences in low-temperature levels and typical environments. By performing template retrieval using the above joint conditions, the strategy templates in the strategy library can be limited to a set consistent with the target vehicle category and low-temperature regional characteristics, providing a bounded starting point for subsequent parameterization generation and avoiding incorrect template selection across vehicle models / batch levels / regions.
[0033] S32. Based on the recharge condition parameter set, at least two types of parameters in the strategy template are modified. These at least two types of parameters include any two of the following: recharge current upper limit, recharge current variation limit, voltage response constraint, pulse temperature recovery, and phased control. In this step, it should be noted that parameterization is not simply replacing a parameter value, but rather adapting the parameter group in the strategy template based on the recharge condition parameter set, transforming the strategy template from a "general framework" into a "configurable structure for the current operating condition." The modification of these at least two types of parameters reflects a coordinated adjustment of safety and availability elements. Specifically, at least two types are selected from the recharge current upper limit, recharge current variation limit, voltage response constraint, pulse temperature recovery, and phased control for linked modification to simultaneously meet the constraints of low-temperature recharge and the requirements for improved temperature recovery efficiency. The temperature level, state of charge, terminal voltage response trend, and load status information provided by the recharge condition parameter set guide the modification direction, making the modified parameters more closely match the target vehicle's current recharge acceptance capability and low-temperature risk level.
[0034] S33. Write the corrected parameters into the strategy parameter set. In this step, it should be noted that writing the corrected parameters into the strategy parameter set is equivalent to solidifying the variable parts of the strategy template into structured, deployable content. The strategy parameter set serves as one of the core inputs for strategy package encapsulation and connects with subsequent adaptation verification and strategy package deployment. Through the structured expression of the strategy parameter set, the cloud can maintain consistent strategy expression under different vehicle and regional temperature conditions, while allowing parameter values to be adjusted according to operating conditions, facilitating version management, canary releases, and subsequent feedback-based iterative updates.
[0035] The technical solution implemented in this embodiment can reduce the selection space of strategy templates and improve the accuracy of template matching by jointly matching vehicle model information and / or sodium-ion battery model or batch information with temperature windows or regional temperature zones, thereby reducing strategy mismatch caused by cross-vehicle, cross-batch, or cross-regional factors. Furthermore, based on the recharge condition parameter set, at least two types of key parameters of the strategy template are modified in a coordinated manner, so that the issued strategy has both low-temperature safety constraints and takes into account the recovery and recharge efficiency, thereby improving the adaptability, stability, and usability of low-temperature recharge. In addition, by solidifying the modification results into a strategy parameter set, it is convenient for subsequent encapsulation and issuance, version management, and closed-loop iteration, reducing the cost of strategy updates and improving the sustainable optimization capability of the strategy system.
[0036] Furthermore, the adaptation and verification of the strategy parameter set according to the recharge condition parameter set includes: S41. Perform a consistency check between the parameters related to the upper limit of recharge current, the limit of recharge current variation, and the voltage response constraint in the strategy parameter set and the real-time values and / or time window statistics of the recharge condition parameter set, and obtain the consistency check result. It should be noted that the adaptation verification occurs after the strategy parameter set is generated and before the strategy package is issued. Its core is to verify the matching of key constraint elements in the strategy parameter set with the current recharge condition of the target vehicle, thereby avoiding situations where "the strategy can be issued but is not applicable" or "the strategy parameter combination is risky under the current condition." The consistency check uses the real-time values and / or time window statistics of the recharge condition parameter set as a benchmark, ensuring that the verification reflects both the vehicle's current instantaneous state and the stable trend during the low-temperature recharge process. The consistency check result is used not only to determine whether continued packaging and issuance are allowed, but also to identify the parameter categories that need to be converged, providing a basis for subsequent safe convergence actions.
[0037] S42. When the consistency check result does not meet the preset safety boundary, execute at least one of the following: tightening the upper limit of the recharge current, tightening the limit on the change of the recharge current, enabling stricter voltage response constraints, raising the pulse recharge temperature trigger threshold, and switching to a conservative strategy template for regeneration. In this step, it should be noted that when the consistency check result does not meet the preset safety boundary, the cloud does not simply refuse to send the data, but rather uses "parameter convergence or strategy rollback" to bring the strategy parameter set back to an executable and controllable range. Parameter convergence includes simultaneously tightening the upper limit of the recharge current and the limit on the change of the recharge current, tightening the voltage response constraints, and raising the pulse recharge temperature trigger threshold, thereby prioritizing safety when the risk of low-temperature polarization increases or the recharge acceptance capability is insufficient. When parameter convergence still cannot meet the preset safety boundary, a switch to a conservative strategy template and regeneration is triggered, causing the strategy to roll back to a more conservative control framework at the template level, avoiding frequent protection triggers or recharge oscillations at the edge.
[0038] The preset safety boundary is determined by the parameter boundaries corresponding to the strategy template and / or the parameter boundaries corresponding to the temperature window or regional temperature zone. It should be noted that the preset safety boundary is not a single threshold, but rather a feasible domain of parameters jointly defined by the parameter boundaries corresponding to the strategy template and / or the parameter boundaries corresponding to the temperature window or regional temperature zone. This domain constrains the value range of the strategy parameter set under different vehicle models, batches, and low-temperature levels. By associating the safety boundary with the strategy template, temperature window, or regional temperature zone, the safety convergence action can be targeted, avoiding an overly conservative approach that applies uniformly to all vehicles.
[0039] The technical solution implemented in this embodiment can verify the consistency between the strategy parameter set and the target vehicle's recharge conditions before the strategy package is issued, reducing recharge instability, frequent protection triggers, or deterioration of recharge efficiency caused by strategy mismatch. When the verification fails, the strategy is safely converged through parameter convergence and conservative strategy template rollback, ensuring that low-temperature recharge remains controllable under extremely cold conditions, connection status fluctuations, or abnormal voltage response, reducing the risk of low-temperature polarization and the probability of abnormal triggering. At the same time, by establishing a preset safety boundary based on the strategy template and temperature window or regional temperature zone, differentiated safety constraints can be implemented for different vehicle models and different regions, improving the availability and coverage of the strategy while ensuring safety.
[0040] Furthermore, the pulse recirculation and staged control in the strategy package include at least: The phased control includes a preheating phase and a recharge phase, and specifies the duration range of the preheating phase and the conditions for phase switching.
[0041] Pulse rewarming includes pulse triggering conditions, pulse duration, pulse interval, and pulse exit conditions.
[0042] Among them, at least one of the stage switching conditions and / or pulse triggering conditions and / or pulse exit conditions is determined or verified by the recharge condition parameter set.
[0043] It should be noted that pulsed temperature recovery and staged control, as control elements within the strategy package, are used to balance "safety constraints" and "temperature recovery efficiency" in scenarios where low-temperature recharge is limited. Staged control divides the low-temperature recharge process into a preheating stage and a recharge stage, allowing the control strategy to first improve the battery temperature and charging acceptance in a gentler, more controlled manner before entering the recharge stage with higher energy recovery efficiency. The stage duration range and stage switching conditions are used to limit the timing and rhythm of stage switching, avoiding premature high-current recharge due to insufficient temperature improvement or load disturbances. Pulse temperature recovery, by setting pulse trigger conditions, pulse duration, pulse interval, and pulse exit conditions, makes the temperature recovery process intermittent, thereby reducing the risk of low-temperature polarization and the probability of abnormal voltage response caused by continuous recharge, and exiting in a timely manner when the temperature recovery effect is insufficient or the risk increases. Furthermore, at least one of the stage switching conditions, pulse triggering conditions, or pulse exit conditions is determined or verified by the recharge condition parameter set, so that the control element can be adaptively adjusted according to changes in the target vehicle's current temperature level, voltage response trend, load status, and other operating conditions, avoiding false triggering or missed triggering caused by fixed threshold triggering.
[0044] The technical solution implemented in this embodiment can transform the low-temperature recharge process from "direct recharge" to "first improve acceptance capacity and then recharge efficiently" by organizing the preheating stage and the recharge stage in stages, thereby improving the problems of slow recharge speed and insufficient recovery under extremely cold conditions. Through the intermittent recharge mechanism of pulse reheating, the risk of low-temperature polarization and abnormal voltage response is suppressed while improving the temperature rise efficiency, reducing frequent protection triggers and recharge oscillations. Furthermore, by determining or verifying the stage switching and pulse triggering / exit through the recharge condition parameter set, the control strategy has better adaptability and stability for different vehicle models, different battery batches, and different regional low-temperature conditions, thereby improving the availability and consistency of low-temperature recharge.
[0045] Furthermore, the rules for handling exceptions should include at least the following: Low-temperature polarization risk anomaly is determined based at least on the deviation characteristics of the terminal voltage response and / or the abnormal characteristics of the terminal voltage change rate.
[0046] Abnormal connection resistance is determined based at least on the abrupt changes in the equivalent internal resistance or connection resistance characteristic and / or the transient drop in terminal voltage.
[0047] When an abnormal low-temperature polarization risk or abnormal connection resistance is detected, the following steps are executed in sequence: derating limit, disconnection if necessary, and reporting to the cloud, and a statistical summary of the recharge condition parameter set is generated.
[0048] The statistical summary of the recharge condition parameter set, along with the version identifier and integrity verification information of the applicable fields and strategy packages, will be reported together.
[0049] In this embodiment, it should be noted that the anomaly handling rules, as a safety control element in the strategy package, run through the strategy issuance and vehicle-side execution process. Their focus includes at least two typical risk scenarios: low-temperature polarization risk anomalies and connection resistance anomalies. For low-temperature polarization risk anomalies, the deviation characteristics of the terminal voltage response and / or the abnormal characteristics of the terminal voltage change rate are used as the judgment criteria. This allows for early identification of risk trends before insufficient low-temperature recharge acceptance and intensified polarization evolve into a serious fault. For connection resistance anomalies, the sudden change characteristics of the equivalent internal resistance or connection resistance characteristic quantity and / or the transient drop characteristics of the terminal voltage are used as the judgment criteria. This allows for rapid identification of abnormal voltage drops caused by wiring harness connections, terminal contacts, or connector deterioration, avoiding recharge control distortion due to abnormal heating or voltage drops. Upon detection of any anomaly, the system is executed in the order of derating, disconnection if necessary, and reporting to the cloud, forming a graded handling path from minor to severe. This ensures that the system can remain usable by derating when the risk is controllable, achieves safety isolation by disconnection when the risk is uncontrollable, and enables quality traceability and strategy correction on the cloud side through reporting. In addition to carrying a statistical summary of the recharge condition parameter set, the reported information also incorporates the applicable fields of the condition and the version identifier and integrity verification information of the policy package. This enables the cloud to accurately associate abnormal events with the current condition, the scope of policy application, and the policy version, providing a consistent data foundation for subsequent policy library item updates, gray-scale rollbacks, or batch quality analysis.
[0050] The technical solution implemented in this embodiment can achieve specific identification and graded handling of low-temperature polarization risks and abnormal connection resistance during low-temperature recharge, reducing recharge oscillations, frequent protection triggers, and potential safety risks caused by abnormal voltage response. Through the sequential handling mechanism of derating, disconnection, and reporting, system availability is maintained while ensuring safety, reducing recharge failures and start-stop unavailability under extremely cold conditions. Furthermore, by carrying reporting information with applicable operating conditions and policy version identifiers, abnormal events and policy versions can be traced, located, and rolled back, supporting closed-loop optimization of the policy library and generated rules in the cloud, thereby reducing the risk of complaints and failures and improving overall stability.
[0051] Furthermore, the cloud management platform performs version consistency verification and canary rollout of the policy package, and includes rollback trigger conditions.
[0052] When the temperature rise efficiency, recharge efficiency, and abnormal trigger information meet the rollback trigger conditions, the strategy is rolled back or switched to the conservative strategy template.
[0053] The rollback trigger conditions include at least one of the following: the recharge efficiency deteriorates beyond a threshold, the number of abnormal triggers exceeds a threshold, or a preset severe exception code appears.
[0054] In this embodiment, it should be noted that the cloud management platform introduces version consistency verification and canary deployment mechanisms before the policy package is distributed, transforming policy release from a "single full replacement" to a "controllable evolution." Version consistency verification ensures that the version identifier of the policy package is consistent with the policy receiving capability of the target vehicle, the valid entries in the policy library, and the integrity verification information, avoiding policy misloading due to version mismatch, duplicate distribution, or transmission anomalies. Canary deployment distributes the new policy package to the target vehicle set in batches according to a preset range. The canary range can be grouped according to regional temperature zone, vehicle model, sodium-ion battery model, or batch information to reduce the concentrated risk of the new policy in extremely cold conditions or specific vehicle groups. The cloud also sets rollback trigger conditions and uses the temperature rise efficiency, recharge efficiency, and abnormal trigger information returned by the vehicle terminal as evaluation inputs. When the rollback trigger conditions are met, the cloud executes policy rollback or switches to a conservative policy template, allowing the policy to quickly recover from the "trial operation state" to a lower-risk policy version or policy framework, thereby maintaining the stability and controllability of low-temperature recharge behavior. The rollback trigger conditions include at least one of the following: the recharge efficiency deterioration exceeds a threshold, the number of abnormal triggers exceeds a threshold, or a preset serious abnormal code appears, to cover three typical risk triggering scenarios: efficiency degradation, increased abnormality, and serious fault signals.
[0055] The technical solution implemented in this embodiment can reduce the risk of policy package mismatch and abnormal loading through version consistency verification, thereby improving the reliability of policy distribution; it can limit the risk of policy change to a controllable range through canary distribution, reducing the concentrated failures and maintenance pressure caused by full release; and it can establish rollback trigger conditions based on temperature rise efficiency, recharge efficiency and abnormal trigger information, so that the policy can be rolled back or switched to a conservative policy template in a timely manner when efficiency deteriorates or rises abnormally, avoiding the continuous amplification of risks of incompatible policies under extremely cold conditions, thereby improving the safety, stability and maintainability of low temperature recharge policy iteration.
[0056] The present invention also provides a terminal-cloud collaborative sodium-ion start-stop battery low-temperature recharge strategy distribution system, which applies the sodium-ion start-stop battery low-temperature recharge strategy distribution method described above, including an in-vehicle terminal and a cloud management platform.
[0057] The vehicle terminal includes a status monitoring module, a recharge control module, and a vehicle communication module. The status monitoring module collects the recharge conditions of the sodium-ion start-stop battery to form a recharge condition parameter set, and sends the recharge condition parameter set and vehicle configuration information to the cloud management platform through the vehicle communication module.
[0058] The cloud management platform includes a cloud communication module, a strategy generation module, and a low-temperature recharge strategy library. The cloud communication module receives the recharge condition parameter set and vehicle configuration information and transmits them to the strategy generation module. The strategy generation module generates a strategy package based on the low-temperature recharge strategy library and sends it to the vehicle terminal through the cloud communication module.
[0059] The strategy package includes a set of strategy parameters, applicable fields for operating conditions, exception handling rules, version identifiers, and integrity verification information.
[0060] According to the strategy package, the vehicle terminal uses the recharge control module to perform low-temperature recharge control on the sodium-ion start-stop battery, and transmits temperature rise efficiency, recharge efficiency and abnormal trigger information back to the cloud management platform through the vehicle communication module.
[0061] It should be noted that this system embodiment uses a closed-loop architecture of "vehicle-side monitoring—cloud generation—policy distribution—vehicle-side execution—feedback transmission" as its basic structure: The vehicle terminal collects and organizes the recharge conditions of the sodium-ion start-stop battery through a status monitoring module, forming a set of recharge condition parameters that can be uploaded. This set of parameters, along with vehicle configuration information, is then uploaded to the cloud management platform via the vehicle communication module. On the cloud management platform side, the cloud communication module handles data access and distribution, while the policy generation module, supported by a low-temperature recharge policy library, generates policy packages, enabling the policies to be implemented. The system package contains a set of policy parameters that can be directly executed by the vehicle, along with applicable operating condition fields, anomaly handling rules, version identifiers, and integrity verification information. This ensures policy applicability constraints, anomaly safety handling, and version traceability. The onboard terminal's recharge control module implements low-temperature recharge control for the sodium-ion start-stop battery based on the policy package. Simultaneously, it transmits the temperature rise efficiency, recharge efficiency, and anomaly trigger information generated during execution back to the cloud via the onboard communication module. This allows the cloud to associate and archive the policy version, applicable operating conditions, and execution results, supporting subsequent policy library maintenance and policy iteration. This system architecture centralizes policy decision-making in the cloud, while the vehicle side maintains lightweight execution and feedback collection, thus balancing policy evolvability with the feasibility of real-time vehicle-side control.
[0062] The technical solution implemented in this embodiment combines vehicle-side operating condition data collection with cloud-based strategy generation to deliver strategy packages tailored to different vehicle models, battery types or batches, and low-temperature operating conditions in different regions. This avoids the problems of fixed threshold table strategies failing to cover diverse operating conditions and incurring high update costs. By carrying applicable operating condition fields, anomaly handling rules, version identifiers, and integrity verification information in the strategy packages, the controllability, verifiability, and traceability of strategy delivery and execution are improved, reducing the risk of strategy mismatch and abnormal loading. Furthermore, the feedback of temperature rise efficiency, recharge efficiency, and anomaly triggering information forms a closed-loop evaluation basis, supporting continuous iterative optimization of the low-temperature recharge strategy library. This improves recharge efficiency and start-stop availability under extremely cold conditions, reducing the risk of low-temperature polarization and the probability of failure caused by abnormal connection status.
[0063] Furthermore, the cloud management platform also includes a temperature window or regional temperature zone determination module and an adaptation verification module.
[0064] The temperature window or regional temperature zone determination module outputs the temperature window or regional temperature zone determination result based on the recharge condition parameter set and transmits it to the strategy generation module.
[0065] The adaptation verification module receives the recharge condition parameter set and the strategy parameter set and outputs the adaptation verification results. The adaptation verification results are passed to the strategy generation module to trigger the selection of conservative strategy templates and the regeneration of strategy packages.
[0066] In this embodiment, it should be noted that the cloud management platform sets up a temperature window or regional temperature zone determination module and an adaptation verification module outside the strategy generation module. The purpose is to separate "operating condition classification" and "strategy availability control" from the strategy generation logic, forming a clearer cloud processing link. The temperature window or regional temperature zone determination module takes the recharge operating condition parameter set as input and outputs the temperature window or regional temperature zone determination result. This determination result serves as an important basis for the strategy generation module to search for and select strategy templates, enabling the strategy generation module to match the low-temperature recharge strategy library with an entry that is more in line with the region and temperature level, reducing the misselection of templates across regions and temperature levels. The adaptation and verification module takes the recharge condition parameter set and strategy parameter set as input and outputs the adaptation and verification results. After the adaptation and verification results are returned to the strategy generation module, they can trigger the selection of conservative strategy templates and the regeneration of strategy packages. This ensures that the strategy packages complete the consistency constraints and convergence of "condition-parameters" before being distributed, avoiding situations where the generated strategy does not match the current low-temperature recharge acceptance capability of the target vehicle. At the same time, the independent settings of the adaptation and verification module facilitate the formation of collaborative constraints with the parameter boundaries of the strategy library, regional temperature zone differences, and vehicle model / batch differences, making the strategy packages output by the strategy generation module easier to release and maintain in a controlled manner.
[0067] The technical solution implemented in this embodiment can provide stable operating condition classification results through the temperature window or regional temperature zone determination module, improve the accuracy and consistency of strategy template matching, and reduce strategy mismatch caused by temperature classification deviation. The adaptation and verification module independently checks the strategy parameter set and the recharge operating condition parameter set, and triggers the regeneration of conservative strategy templates and strategy packages when the verification fails, so that risk convergence is completed before the strategy is issued, reducing frequent vehicle-side protection, recharge oscillation and recharge efficiency degradation. This improves the reliability, controllability and cross-regional adaptability of cloud strategy generation and issuance, and further reduces the risk of complaints and failures under extremely cold conditions.
[0068] Furthermore, the vehicle-mounted terminal also includes a policy package verification unit and an offline fallback unit.
[0069] The policy package verification unit verifies the version identifier and integrity verification information of the policy package and outputs the policy package verification result.
[0070] The offline fallback unit receives communication failure signals, version mismatch signals, and inconsistency signals for applicable operating conditions, and outputs a fallback control signal to the recharge control module when the preset fallback conditions are met.
[0071] In this embodiment, it should be noted that after receiving the policy package from the cloud, the vehicle terminal does not execute it directly and unconditionally. Instead, the policy package verification unit first verifies the version identifier and integrity verification information of the policy package to confirm that the policy package has not been tampered with, has not been damaged during transmission, and matches the current policy parsing and execution capabilities of the vehicle terminal. Based on this, the policy package verification result is output. The policy package verification result serves as one of the bases for whether the recharge control module adopts the policy package. The offline fallback unit is used to handle scenarios where communication or policy is unavailable. Its inputs include at least communication failure signals, version mismatch signals, and inconsistency signals for applicable operating conditions. When any of these signals occurs and the preset fallback conditions are met, the offline fallback unit outputs a fallback control signal to the recharge control module, causing the recharge control module to switch to a locally safe and executable recharge control mode. This ensures that even when the cloud-based policy cannot be reliably obtained or is not applicable to the current operating conditions, the vehicle side can still maintain basic recharge availability and avoid the risk expansion caused by erroneous policies. At the same time, the offline fallback unit enables the end-side to have the ability to self-check the applicability and execution conditions of the policy, forming a closed constraint with the applicable operating conditions fields in the cloud.
[0072] The technical solution implemented in this embodiment can reduce the execution risk caused by incorrect loading, abnormal transmission, or version incompatibility of the strategy package through version and integrity verification of the strategy package verification unit, thereby improving the reliability of strategy issuance and execution. Furthermore, by triggering a fallback control signal through the offline fallback unit when communication fails, version mismatch occurs, or the applicable fields for the working conditions are inconsistent, the vehicle's recharging behavior remains controllable even in extremely cold conditions or unstable network environments. This reduces the risk of recharging interruptions, frequent protection failures, and safety issues caused by strategy unavailability or mismatch, thereby improving the continuous availability and safety of the system in low-temperature recharging scenarios.
[0073] 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 specification.
Claims
1. A method for issuing a low-temperature recharge strategy of a sodium-ion start-stop battery under end-to-cloud collaboration, characterized in that, include: Receive the charging condition parameter set and vehicle configuration information reported by the on-board terminal of the target vehicle. The vehicle configuration information includes vehicle model information and / or sodium-ion battery model or batch information. Based on the recharge condition parameter set, determine the temperature window or regional temperature zone corresponding to the target vehicle, and match the strategy template in the low temperature recharge strategy library in combination with the vehicle configuration information; Based on the recharge condition parameter set, the strategy template is parameterized to generate a strategy parameter set that includes the upper limit of recharge current, the limit of recharge current variation, the voltage response constraint, pulse temperature recovery and staged control. The strategy parameter set is adapted and verified according to the recharge condition parameter set. If the requirements are not met, the conservative strategy template is switched and regenerated. The strategy parameter set, along with the applicable fields for the working conditions, the abnormal handling rules, the version identifier, and the integrity verification information summarized from the recharge working condition parameter set, are encapsulated into a strategy package and sent to the vehicle terminal. The system receives temperature rise efficiency, recharge efficiency, and abnormal triggering information from the vehicle terminal, which are used to update the low-temperature recharge strategy library entries and / or the parameterized generation rules.
2. The method of claim 1, wherein the sodium-ion start-stop battery low-temperature recharge strategy is issued based on the following conditions: the battery temperature is lower than a preset temperature threshold; the battery state of charge is lower than a preset state of charge threshold; and the battery state of health is higher than a preset state of health threshold. Determining the temperature window or regional temperature zone corresponding to the target vehicle based on the recharge condition parameter set includes: Time window statistics are performed on the recharge condition parameter set to obtain temperature statistics and voltage response statistics; The temperature window or regional temperature zone is assigned based on the temperature statistics, and the consistency of the assignment results is checked based on the voltage response statistics. The results of the temperature window or regional temperature zone classification are written into the working condition applicable field, and the strategy template is matched in the low temperature recharge strategy library based on the results of the temperature window or regional temperature zone classification.
3. The method for issuing a low-temperature recharge strategy for sodium-ion start-stop batteries according to claim 1, characterized in that, The step of matching a strategy template in the low-temperature recharge strategy library and generating the strategy template parameterized based on the recharge condition parameter set includes: Using the vehicle model information and / or the sodium-ion battery model or batch information, the temperature window or regional temperature zone as matching conditions, the strategy template is selected from the low-temperature recharge strategy library; Based on the recharge condition parameter set, at least two types of parameters of the strategy template are modified, including any two types of parameters among the recharge current upper limit, recharge current variation limit, voltage response constraint, pulse temperature recovery and staged control. Write the corrected parameters into the policy parameter set.
4. The method for issuing a low-temperature recharge strategy for sodium-ion start-stop batteries according to claim 1, characterized in that, The adaptation and verification of the strategy parameter set according to the recharge condition parameter set includes: The parameters related to the upper limit of recharge current, the limit of recharge current variation, and the voltage response constraint in the strategy parameter set are checked for consistency with the real-time values and / or time window statistics of the recharge condition parameter set to obtain the consistency check results. When the consistency check result does not meet the preset safety boundary, at least one of the following is executed: tightening the upper limit of the recharge current, tightening the limit on the change of the recharge current, enabling stricter voltage response constraints, increasing the pulse reheat trigger threshold, and switching to conservative strategy template regeneration. The preset safety boundary is determined by the parameter boundary corresponding to the strategy template and / or the parameter boundary corresponding to the temperature window or regional temperature zone.
5. The method for issuing a low-temperature recharge strategy for sodium-ion start-stop batteries according to claim 1, characterized in that, The pulse rewarming and phased control in the strategy package includes at least the following: The phased control includes a preheating phase and a recharge phase, and specifies the duration range of the preheating phase and the recharge phase, as well as the phase switching conditions. The pulsed temperature recovery includes pulse triggering conditions, pulse duration, pulse interval, and pulse exit conditions; Wherein, at least one of the stage switching condition and / or the pulse triggering condition and / or the pulse exit condition is determined or verified by the recharge condition parameter set.
6. The method for issuing a low-temperature recharge strategy for sodium-ion start-stop batteries according to claim 1, characterized in that, The exception handling rules include at least the following: Low-temperature polarization risk anomaly, which is determined at least based on the deviation characteristics of the terminal voltage response and / or the abnormal characteristics of the terminal voltage change rate; The connection resistance is abnormal, and the abnormal connection resistance is determined at least based on the abrupt change characteristics of the equivalent internal resistance or connection resistance characteristic and / or the transient drop characteristics of the terminal voltage. When the abnormal low-temperature polarization risk or the abnormal connection resistance is detected, the following actions are executed in sequence: derating limit, disconnection if necessary, and reporting to the cloud, and a statistical summary of the recharge condition parameter set is generated. The statistical summary of the recharge condition parameter set, along with the applicable fields of the condition and the version identifier and integrity verification information of the strategy package, are reported as the information to be reported.
7. The method for issuing a low-temperature recharge strategy for sodium-ion start-stop batteries according to claim 1, characterized in that, The cloud management platform performs version consistency verification and canary rollout on the policy package, and includes rollback trigger conditions. When the temperature rise efficiency, the recharge efficiency, and the abnormal trigger information meet the rollback trigger conditions, execute the strategy rollback or switch to the conservative strategy template. The rollback triggering conditions include at least one of the following: recharge efficiency deterioration exceeding a threshold, abnormal trigger count exceeding a threshold, or the occurrence of a preset severe error code.
8. A cloud-edge collaborative sodium-ion start-stop battery low-temperature recharge strategy distribution system, employing the sodium-ion start-stop battery low-temperature recharge strategy distribution method as described in any one of claims 1-7, characterized in that, Including in-vehicle terminals and cloud management platforms; The vehicle terminal includes a status monitoring module, a recharge control module, and a vehicle communication module. The status monitoring module collects the recharge conditions of the sodium-ion start-stop battery to form a recharge condition parameter set, and sends the recharge condition parameter set and vehicle configuration information to the cloud management platform through the vehicle communication module. The cloud management platform includes a cloud communication module, a strategy generation module, and a low-temperature recharge strategy library. The cloud communication module receives the recharge condition parameter set and the vehicle configuration information and transmits them to the strategy generation module. The strategy generation module generates a strategy package based on the low-temperature recharge strategy library and sends it to the vehicle terminal through the cloud communication module. The strategy package includes a set of strategy parameters, applicable fields for operating conditions, exception handling rules, version identifiers, and integrity verification information. The vehicle terminal, based on the strategy package, uses the recharge control module to perform low-temperature recharge control on the sodium-ion start-stop battery, and transmits temperature rise efficiency, recharge efficiency, and abnormal trigger information back to the cloud management platform through the vehicle communication module.
9. The sodium-ion start-stop battery low-temperature recharge strategy distribution system according to claim 8, characterized in that, The cloud management platform also includes a temperature window or regional temperature zone determination module and an adaptation verification module; The temperature window or regional temperature zone determination module outputs the temperature window or regional temperature zone determination result based on the recharge condition parameter set and transmits it to the strategy generation module. The adaptation verification module receives the recharge condition parameter set and the strategy parameter set and outputs the adaptation verification result. The adaptation verification result is transmitted to the strategy generation module to trigger the selection of the conservative strategy template and the regeneration of the strategy package.
10. The sodium-ion start-stop battery low-temperature recharge strategy distribution system according to claim 8, characterized in that, The vehicle-mounted terminal also includes a strategy package verification unit and an offline fallback unit; The policy package verification unit verifies the version identifier and integrity verification information of the policy package and outputs the policy package verification result. The offline fallback unit receives communication failure signals, version mismatch signals, and inconsistency signals for applicable working conditions, and outputs a fallback control signal to the recharge control module when the preset fallback conditions are met.