Battery heating control method, system, and vehicle

Abstract

The embodiment of the application relates to the technical field of vehicle battery, and discloses a battery heating control method, a system and a vehicle, the method comprises the following steps: an interface processing layer receives a battery heating request signal from an application layer; the interface processing layer issues a control calling signal to a capability abstraction layer based on the battery heating request signal; the capability abstraction layer determines execution control parameters of a corresponding heating mode according to the control calling signal, and sends the execution control parameters to an execution control layer; and the execution control layer drives a physical heating executor based on the execution control parameters. The embodiment of the application can realize decoupling and standardized interaction of battery heating control logic, so as to improve the universality and expansion capability of a control system.

Description

Technical Field

[0001] This invention relates to the field of vehicle battery technology, specifically to battery heating control methods, systems, and vehicles. Background Technology

[0002] With the rapid development of new energy vehicle technology, the power battery, as the core energy supply component of the vehicle, has a decisive impact on the vehicle's driving range, charging and discharging efficiency, and battery lifespan due to its operating temperature. In low-temperature environments, the active materials inside the battery degrade and the internal resistance increases significantly. Therefore, preheating or temperature maintenance via a battery heating system is usually necessary to ensure the battery is within its optimal operating temperature range.

[0003] Existing battery heating control solutions typically employ a control mode where a specific control module directly interfaces with the physical heating hardware. In this type of control structure, the upper-layer function request logic is often tightly coupled with the lower-layer hardware driver logic, and control commands and feedback data are mostly transmitted point-to-point through specific dedicated links. With the evolution of battery heating technology, the heating methods available for vehicles are becoming increasingly diverse, and control requirements are also gradually becoming more varied.

[0004] However, the tightly coupled control architecture described above lacks a reasonable logical hierarchy and a unified data interaction mechanism. When it is necessary to change the heating control strategy, add application scenarios, or adapt to different types of physical heating hardware, it is often necessary to modify the software code at all levels involved in the vehicle control loop as a whole, resulting in a long development cycle for the control system, poor cross-platform reusability of the software, and high expansion costs. Summary of the Invention

[0005] In view of the shortcomings of the prior art, the purpose of this application is to provide a battery heating control method, system and vehicle that can achieve decoupling and standardized interaction of battery heating control logic, so as to improve the versatility and scalability of the control system.

[0006] In a first aspect, embodiments of this application provide a battery heating control method, the method comprising: an interface processing layer receiving a battery heating request signal from an application layer; the interface processing layer determining a target heating mode based on the battery heating request signal, and issuing a control call signal to a heating abstract interface corresponding to the target heating mode in a capability abstraction layer; the capability abstraction layer determining execution control parameters corresponding to the target heating mode based on the control call signal and an execution interaction interface, and sending the execution control parameters to an execution control layer; and the execution control layer driving a physical heating actuator based on the execution control parameters. Optionally, the execution control layer may also transmit the state feedback information of the physical heating actuator in reverse to the capability abstraction layer.

[0007] The battery heating control method provided in this application decouples application logic from physical actuators through a hierarchical division of an interface processing layer, a capability abstraction layer, and an execution control layer. The interface processing layer receives requests from the application layer, the capability abstraction layer performs logic transformation and sends execution control parameters to the execution control layer, and the execution control layer drives the physical heating actuator and transmits status feedback information back to the capability abstraction layer. This constructs a clear hierarchical closed-loop control mechanism, avoiding architectural redundancy and difficulties in link changes caused by direct hardware and software binding, and improving the versatility and scalability of the battery heating control system.

[0008] In one possible embodiment, the interface processing layer sends a control call signal to the capability abstraction layer based on the battery heating request signal, including: the interface processing layer performs input parameter compliance verification on the received battery heating request signal; if the input parameter compliance verification passes, the interface processing layer arbitrates multiple concurrent battery heating request signals according to a preset priority strategy to generate the control call signal.

[0009] In this implementation, the interface processing layer verifies the validity of the received signals and arbitrates multiple concurrent requests according to a preset priority strategy after the verification is successful. This eliminates request conflicts and overlapping scenarios caused by multiple independent calls, ensures that high-priority safety requirements are responded to first, and improves the reliability and safety of the vehicle control system.

[0010] In one embodiment, the interface processing layer receives a battery heating request signal from the application layer, including: the interface processing layer receiving a preset heating mode call signal from the application layer through a direct control interface; and / or the interface processing layer receiving a managed heating request signal from the application layer through a combined managed interface.

[0011] For example, when the interface processing layer receives a managed heating request signal from the application layer through a combined managed interface, the step of sending a control call signal to the heating abstract interface in the capability abstraction layer corresponding to the target heating method includes: the interface processing layer obtaining the vehicle configuration word and the executable heating capability information reported by the capability abstraction layer; matching the target heating method from multiple candidate heating methods according to the vehicle configuration word and the executable heating capability information; and sending the control call signal to the target heating abstract interface in the capability abstraction layer corresponding to the target heating method.

[0012] In this implementation, the system provides two access modes: direct control and combined managed access. In combined managed access mode, the interface processing layer combines the vehicle configuration word with the hardware permission capabilities reported in real time by the capability abstraction layer to automatically complete the matching and routing of the target heating method, so that the application layer does not need to be aware of the specific underlying hardware implementation.

[0013] As one possible implementation, the managed heating request signal includes at least one of a timed heating request, an immediate heating request, and a temperature maintenance heating request; the step of sending the control call signal to the target heating abstract interface corresponding to the target heating method in the capability abstraction layer includes: in response to receiving a timed heating request, extracting the target temperature and deadline contained in the timed heating request, selecting the target heating abstract interface corresponding to the matching heating method, and sending the control call signal to perform closed-loop control; in response to receiving an immediate heating request, extracting the heating instruction contained in the immediate heating request, selecting the target heating abstract interface corresponding to the matching heating method according to a preset heating strategy, and sending the control call signal to perform immediate heating; in response to receiving a temperature maintenance heating request, extracting the target maintenance temperature and maintenance deadline contained in the temperature maintenance heating request, selecting the target heating abstract interface corresponding to the matching heating method, and sending the control call signal to perform temperature maintenance control.

[0014] In this implementation, for different scenarios such as timed heating, immediate heating, and temperature-maintaining heating, the corresponding target temperature, maintenance temperature, and time are extracted for closed-loop shunt control, which reduces the development difficulty of the application layer and improves the adaptability to multiple scenarios.

[0015] In some embodiments, determining the execution control parameters for the corresponding heating mode includes: the capability abstraction layer obtaining the current vehicle operating condition parameters; combining the operating condition parameters to perform an availability assessment on the control call signal, determining the current heating mode's availability status and the maximum allowable gear threshold, and generating the execution control parameters based on the maximum gear threshold.

[0016] In this implementation, the capability abstraction layer combines real-time operating condition parameters to perform availability assessment and limits the maximum allowable gear threshold, preventing the underlying hardware from blindly forcing startup when vehicle power is limited or operating conditions are unsuitable. This avoids hardware overload or further deterioration of vehicle operating conditions and improves the safety boundary of the control process.

[0017] In an exemplary embodiment, the status feedback information includes unfiltered raw energy consumption data; the method further includes: after receiving the status feedback information, the capability abstraction layer performs smoothing filtering on the raw energy consumption data to generate real-time processed energy consumption data; the capability abstraction layer sends feedback parameters containing the real-time processed energy consumption data to the interface processing layer.

[0018] In this implementation, the capability abstraction layer performs smoothing filtering on the raw energy consumption data in the front-end link, eliminating high-frequency noise caused by sampling current / voltage fluctuations. This provides a stable and reliable data benchmark for the upper interface processing layer and decision logic, avoiding frequent fluctuations and distortions in the upper control strategy due to data noise.

[0019] In one possible implementation, the heating method includes at least one of the following: variable frequency film heating, non-variable frequency film heating, pulse heating, stalled rotor heating, degraded heating, hydrothermal heating of the heating element, waste heat recovery heating, and heat pump heating. This achieves an abstract encapsulation of the capabilities of diverse and heterogeneous heating hardware such as variable frequency film, pulse, stalled rotor, and heat pump heating.

[0020] Optionally, the capability abstraction layer and the execution control layer transmit data through a fixed execution interaction interface, wherein the input parameters of the execution interaction interface include heating level request parameters or heating control request parameters; the output parameters of the execution interaction interface include at least one of real-time raw energy consumption parameters, function availability status parameters, maximum allowable level parameters, function execution status parameters, remaining heating time parameters, and maximum supported temperature parameters.

[0021] In this implementation, by standardizing input parameters and specializing output parameters (such as remaining heating time and maximum supported temperature) through a fixed execution interaction interface, the differences in heterogeneous hardware control protocols are shielded, facilitating bus data capture and authentication testing, and significantly improving the software's cross-hardware platform compatibility and reusability.

[0022] In one possible implementation, the method further includes: establishing a periodic communication heartbeat monitoring mechanism between the capability abstraction layer and the execution control layer; and, if the capability abstraction layer detects a communication timeout or the status feedback information indicates an abnormality, the capability abstraction layer sends an interrupt command to the execution control layer to terminate the battery heating operation of the physical heating actuator.

[0023] In this implementation, the capability abstraction layer and the execution control layer communicate and monitor each other's hardware status in real time via periodic heartbeat monitoring. In the event of communication interruption or abnormal feedback, an interrupt command is proactively issued to forcibly cut off the heating circuit, achieving proactive safety isolation and fallback protection, effectively eliminating the risk of battery overheating and thermal runaway due to control failure.

[0024] Secondly, embodiments of this application provide a battery heating control system, comprising: an interface processing module, configured to receive a battery heating request signal from an application layer and output a control call signal according to the battery heating request signal; a capability abstraction module, configured to determine the execution control parameters of a corresponding heating mode according to the control call signal and preprocess the received status feedback information; and an execution control module, connected to the capability abstraction module via an execution interaction interface, configured to drive a physical heating actuator based on the execution control parameters and transmit the status feedback information of the physical heating actuator in reverse to the capability abstraction module via the execution interaction interface.

[0025] The battery heating control system provided in this application has a clear division of labor and decoupling between the interface processing module, the capability abstraction module, and the execution control module. The interface processing module is responsible for request reception and call conversion, the capability abstraction module is responsible for logic mapping and data preprocessing, and the execution control module is responsible for hardware driving and state feedback. Each module establishes a closed-loop connection through a fixed interaction interface, which reduces the dependency between modules and improves the stability and platform reusability of the system.

[0026] Thirdly, embodiments of this application provide a vehicle including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method provided by the first aspect or any possible implementation thereof.

[0027] The corresponding effects of the vehicle described in the third aspect can be found in the relevant content of the method described in the first aspect, and will not be repeated here.

[0028] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer instructions that, when executed by a processor, implement the method provided by the first aspect or any possible implementation thereof.

[0029] The effects of the storage medium described in the fourth aspect can be found in the relevant content of the method described in the first aspect, and will not be repeated here.

[0030] The battery heating control method, system, and vehicle provided in this application can achieve the following technical effects: This application establishes an interface processing layer, a capability abstraction layer, and an execution control layer, eliminating the need for the application layer's battery heating requirements to be directly sent to the specific physical heating actuator. The interface processing layer receives and processes application layer requests, the capability abstraction layer converts heating requirements into execution control parameters for the corresponding heating method, and the execution control layer drives the physical heating actuator and provides feedback on its operating status, thereby reducing the coupling between application functions and the underlying heating hardware.

[0031] The interface processing layer can verify the compliance of input parameters of the battery heating request signal and arbitrate multiple concurrent requests according to a preset priority strategy, thereby reducing the conflict or duplicate execution of heating requests from different applications.

[0032] The interface processing layer supports both direct control interfaces and combined managed interfaces. The application layer can specify a specific heating method, or it can only provide timed heating, immediate heating, or temperature-maintaining heating requirements. The interface processing layer automatically selects the appropriate heating method, thereby reducing the application layer's dependence on the underlying hardware configuration and control details.

[0033] The interface processing layer can combine the vehicle configuration word and the executable heating capability information reported by the capability abstraction layer to match the target heating method from multiple candidate heating methods. When the vehicle configuration or physical heating hardware changes, adaptation can be achieved by adjusting the configuration word or adding corresponding heating abstraction interfaces, without having to modify the entire application layer control logic.

[0034] The capability abstraction layer can perform an availability assessment by combining the vehicle's current operating parameters and issue actual execution control parameters based on the maximum permissible gear limit, so that the physical heating actuator can operate within the vehicle's current permissible power and safety boundaries.

[0035] The capability abstraction layer can smooth and filter the raw energy consumption data fed back from the execution control layer, thereby reducing the impact of sampling noise and transient fluctuations on upper-layer task management and energy management, and avoiding multiple applications from repeatedly processing the same raw data.

[0036] By setting up corresponding heating abstract interfaces for variable frequency film heating, non-variable frequency film heating, pulse heating, stall heating, degraded heating, hydrothermal heating of heating components, waste heat recovery heating, and heat pump heating, various heterogeneous heating hardware can be managed in a unified manner, improving the reusability of battery heating control software under different vehicle models and different hardware configurations.

[0037] The capability abstraction layer and the execution control layer transmit data through a fixed execution interaction interface, and uniformly define parameters such as heating request, heating level, original energy consumption, permitted status, maximum permitted level, execution status, remaining heating time, and maximum supported temperature. This helps to isolate the impact on the upper-layer software when changes occur to the execution controller or physical heating actuator.

[0038] By setting up periodic communication monitoring between the capability abstraction layer and the execution control layer, and issuing an interrupt command when communication times out or execution status is abnormal, abnormal heating actions can be terminated in a timely manner, reducing the risk of battery overheating or heating runaway caused by continuous abnormal operation of the physical heating actuator.

[0039] The interface processing layer, capability abstraction layer, and execution control layer can be deployed in the same on-board controller, or they can be distributed and deployed in different controllers according to the vehicle's electronic and electrical architecture. Therefore, they can adapt to centralized, domain-centralized, or distributed vehicle electronic and electrical architectures, improving the flexibility of system deployment. Attached Figure Description

[0040] Figure 1 A schematic diagram of a conventional battery heating control mechanism is shown. Figure 2 A schematic diagram of a battery heating control mechanism provided in an embodiment of this application is shown; Figure 3 This paper illustrates a network architecture diagram of a battery heating control system provided in an embodiment of this application. Figure 4 This is a flowchart of a battery heating control method provided in an embodiment of this application; Figures 5(a)-(b) show the flowchart of the direct control heating method for battery heating function application; Figures 6(a)-(b) show the flowcharts of the basic combination interface for battery heating applications using timed heating; Figure 7 The flowchart of the control logic call for the timed heating interface is shown; Figures 8(a)-(b) show the flowcharts of the battery heating function application using the instant heating basic combination interface; Figure 9 The flowchart of the control logic for calling the immediate heating interface is shown; Figures 10(a)-(b) show the flowchart of the interface for the battery heating function application using the temperature-controlled heating basic combination interface; Figure 11 The flowchart of the control logic call for the temperature-controlled heating interface is shown. Figure 12 The flowchart of the unified call control logic for each function is shown; Figure 13 The algorithm diagram for selecting the control heating execution mode by calling the basic combined control-timed heating interface is shown. Figure 14 The diagram illustrates the algorithm for selecting the control heating execution mode by calling the basic combined control-temperature heating interface. Figure 15 This application illustrates another battery heating control system provided by an embodiment of the present application. Detailed Implementation

[0041] To gain a more detailed understanding of the features and technical content of the embodiments of this disclosure, the implementation of the embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference and illustration only and are not intended to limit the embodiments of this disclosure.

[0042] The battery heating control method, system, and vehicle provided in this application are mainly applied to the heating control of power batteries in new energy vehicles, but can also be applied to hybrid vehicles, range-extended vehicles, or other vehicles equipped with power batteries and battery heating devices. The control logic involved in each embodiment can be deployed in the vehicle controller, thermal management controller, battery management controller, power domain controller, central computing platform, or other on-board electronic control units, or it can be distributed across multiple on-board electronic control units.

[0043] Unless otherwise stated, the "connection" described in the embodiments of this application may include electrical connection, communication connection or logical call relationship; the communication connection may be implemented through Controller Area Network (CAN), Local Interconnect Network (LIN), FlexRay, automotive Ethernet or software communication mechanism inside the controller.

[0044] Figure 1 A schematic diagram of a conventional battery heating control mechanism is shown. To facilitate understanding of the layered decoupled battery heating control architecture proposed in this invention, we will first combine... Figure 1 This paper explains the battery heating control mechanism of traditional technical solutions and its drawbacks.

[0045] As the penetration rate of new energy vehicles continues to increase globally, the user base of new energy vehicles in cold regions is growing rapidly. Due to the reduced activity and increased internal resistance of the active materials in power batteries at low temperatures, battery temperatures often deviate from their optimal operating temperature range. This directly worsens core functions closely related to user experience, such as charging speed, acceleration performance, low-temperature safety, and air conditioning heating. Therefore, vehicles typically need to incorporate various battery heating functions (such as…) Figure 1 Battery heating functions (such as battery heating function application 1, battery heating function application 2, etc.) include, but are not limited to, charging heating, heat preservation heating, scheduled heating, and driving heating, to maintain the battery temperature within a suitable range. Meanwhile, the physical heating methods used at the vehicle's base are becoming increasingly diverse, with different vehicle models often equipped with different battery heating actuators (such as...). Figure 1 The battery heating actuator 1, battery heating actuator 2, etc., such as PTC hydrothermal components, membrane heaters, or heat pump systems.

[0046] like Figure 1 As shown, in traditional technical solutions, when a battery heating function is required, the control signal is directly sent down to the underlying battery heating execution controller (such as...). Figure 1The battery heating actuator controller 1 and battery heating actuator controller 2, etc., rely on point-to-point signal interaction between them to achieve their functions. This control mode is essentially a many-to-many mesh tightly coupled control structure, which has the following serious defects in actual development and platform applications: When adding or modifying a battery heating function application to meet new user needs (such as adding a "scheduled charging and temperature maintenance" application), a point-to-point functional signal interface must be added between the functional application and the corresponding battery heating execution controller. Simultaneously, the underlying execution controller needs to rely on the new signal interface to identify the request source and rewrite its local logic to determine the priority relationship between new and existing requirements. This results in extensive architectural and code adjustments to the upstream and downstream control software for each added or modified function, severely limiting the scalability of the functionality.

[0047] Each battery heating function application operates as an independent logic module, capable only of determining heating demand based on its own collected information, and unable to perceive the operational status of other applications. When multiple applications simultaneously trigger heating requests (overlapping demands), or when vehicle operating conditions (such as high-voltage overcurrent, grid transient fluctuations, DC-DC load limiting, etc.) impose restrictions on heating execution, the lack of a global overall heating demand assessment and operating condition constraint mechanism can easily lead to control conflicts, and even cause vehicle electrical safety defects under boundary conditions, severely impacting vehicle reliability.

[0048] Because traditional control links lack clear logical layers, once any controller scheme or hardware driver software changes, all controllers in the entire closed-loop control loop must re-examine the impact of the change on their own software and undergo adaptation redevelopment and testing. This results in extremely poor cross-platform reusability of the software, significantly lengthening the R&D cycle and increasing development costs.

[0049] Because the triggering logic of the upper-level heating function application and the execution mode of the lower-level heating component (such as duty cycle drive, communication enable and other specific execution logic) are deeply bound in the software, when the hardware configuration of the vehicle changes (for example, from PTC water heating solution to heat pump heating solution), the software code of the upper-level function application is incompatible and must be reconstructed differently for specific vehicle models, which hinders the generalization and platform design of the software.

[0050] Based on this, this application provides a battery heating control method, system, and vehicle. The battery heating control method is a layered, decoupled battery heating control scheme. Specifically, this application introduces an interface processing layer below the application layer. The battery heating functions in the application layer no longer interact directly with the underlying execution controller; instead, they uniformly send requests to the interface processing layer. The interface processing layer ensures the legitimacy of requests through input parameter compliance verification and arbitrates requests using a preset priority strategy, uniformly generating a unique control call signal. If application layer functions are added or modified subsequently, only the access logic and arbitration table need to be fine-tuned in the interface processing layer; there is no need to modify the underlying capability abstraction and execution control code. Simultaneously, the interface processing layer, acting as a global demand judge and arbitrator, completely eliminates the problems of concurrent request conflicts and cumulative deterioration of operating conditions. Furthermore, this application introduces a capability abstraction layer and an execution control layer, and defines a fixed execution interaction interface between the two layers. The capability abstraction layer is responsible for abstracting various heterogeneous heating methods (such as variable frequency film heating, pulse heating, heat pump heating, etc.) into standardized capability interfaces. It also performs usability assessments by acquiring the current vehicle's operating parameters and dynamically limits the maximum permissible heating level threshold. The underlying execution control layer is specifically responsible for driving the corresponding physical heating actuators and transmitting feedback information in reverse. Because the capability abstraction layer and the execution control layer transmit data through a fixed interface (input heating level / control request, output parameters such as energy consumption, permissible status, and maximum temperature), changes in the underlying physical hardware or the execution control layer's driver software are confined within the execution control layer and will not affect the upper-layer functional logic. This achieves complete decoupling of control and execution, giving the entire battery heating software extremely high cross-vehicle compatibility and platform reusability.

[0051] The functions of the battery heating control system involved in the embodiments of this application will be described below.

[0052] In some implementations, the battery heating control and feedback system of this application is divided from top to bottom into a functional application layer, a heating function interface call processing layer, a basic heating capability abstraction layer, and a heating function execution layer. In software implementation, the functional application layer does not directly control the underlying heating execution controller, but instead calls the general interface of the processing layer through the heating function interface, achieving layer-by-layer transmission and closed-loop control of heating requirements. Clear software isolation strategies are designed between each layer, using general, fixed input / output signal interfaces, combined with compatibility configuration and priority processing mechanisms, to achieve decoupling of hardware and software.

[0053] Figure 2 A schematic diagram of a battery heating control mechanism provided in an embodiment of this application is shown. Figure 3 A schematic diagram of the network architecture of a battery heating control system provided in an embodiment of this application is shown. Figure 2 and Figure 3 As shown, the battery heating system 100 includes an application layer 101, an interface processing layer 102, a capability abstraction layer 103, and an execution control layer 104.

[0054] In this example, in this embodiment, application layer 101 refers to one or more vehicle function modules or software applications (i.e., battery heating function applications) used to generate battery heating requirements.

[0055] For example, the application layer 101 may include a charging heating application, a scheduled heating application, a driving heating application, a heat preservation heating application, an immediate heating application, a low-temperature safety heating application, and other vehicle functional modules with battery heating requirements.

[0056] In terms of physical deployment, the application layer 101 can run in the vehicle master control unit (VMCU), thermal management system controller (TMSC), on-board central computing platform, or other on-board control devices. Each functional application independently generates a heating request signal and sends it to the lower interface processing layer 102 based on the user's vehicle usage needs, the current operating condition of the vehicle, and other inputs.

[0057] It should be understood that the interface processing layer 102 in this embodiment (which may also be called the heating function interface call processing layer in one embodiment) is a software function layer set between the application layer 101 and the capability abstraction layer 103, used to receive battery heating request signals and to identify, verify parameters, arbitrate requests, route interfaces, or manage heating tasks for the battery heating request signals.

[0058] The interface processing layer 102 is not physically limited to a separate physical controller. As long as the corresponding software module or controller can perform interface processing functions, it can serve as the interface processing layer 102 as referred to in this application embodiment. Specifically, it can be software middleware, software service components, application programming interface (API) management modules, or specific program segments running in the vehicle controller.

[0059] Combination Figure 2 As shown, the interface processing layer 102 provides a fixed, general API interface (such as...) for upper-layer functional applications. Figure 2 The "API interface" in the application layer 101 allows multiple functional applications to send work requests to the battery heating main controller (i.e., the software entity corresponding to the interface processing layer 102) through this general API interface.

[0060] To assist in decision-making and matching, the interface processing layer 102 can be configured to receive or obtain the following auxiliary information: Vehicle configuration word: This refers to configuration data used to indicate the heating method or related hardware capabilities actually installed / configured in the current vehicle. It can be represented by one or more binary bits, enumerated values, parameter tables, or specific data structures. Optionally, the interface processing layer 102 can read configuration information from the vehicle's non-volatile memory (such as electrically erasable programmable read-only memory, EEPROM), which includes the vehicle configuration word, used to indicate whether the vehicle supports pulse heating, whether it is equipped with a heat pump, etc.

[0061] Cloud-based weather information: The interface processing layer 102 can periodically or on-demand retrieve weather information from the cloud via an in-vehicle wireless communication module (such as a T-BOX or a 5G / 4G in-vehicle wireless terminal). For example, the weather information includes at least one of the following: real-time ambient temperature within a preset range of the vehicle's current location or destination; predicted ambient temperature within a preset time period; weather condition type (such as sunny, snowy, freezing rain, or cold wave warning); ambient humidity; and solar radiation intensity. This allows the interface processing layer 102 to plan heating strategies in advance upon managed heating requests.

[0062] Optionally, the capability abstraction layer 103 (which may also be referred to as the basic heating capability abstraction layer in one embodiment) is located between the interface processing layer 102 and the execution control layer 104. It is used to abstract the hardware control capabilities of different heating methods into corresponding standard software interfaces, and to perform software functions such as operating condition availability judgment, execution control parameter determination, energy consumption data processing, communication diagnostics, or safety protection. The capability abstraction layer 103 can be deployed as a code module, software service component, or software middleware in the vehicle controller, thermal management controller, battery management controller, or power domain controller, or it can be implemented collaboratively by multiple controllers.

[0063] The capability abstraction layer 103 contains multiple heating abstraction modules, each corresponding to a different heating method. For example... Figure 3 As shown, the multiple heating abstraction modules may specifically include at least one of the following: variable frequency film direct heating function abstraction, non-variable frequency film direct heating function abstraction, pulse heating function abstraction, stalled rotor heating function abstraction, efficiency-reduced heating function abstraction, heating component hydrothermal function abstraction, waste heat recovery heating function abstraction, and heat pump heating function abstraction. Through these abstraction modules, the capability abstraction layer 103 encapsulates the physical heating capabilities of the underlying multi-dimensional heterogeneous hardware into standardized capability indicators for the interface processing layer 102.

[0064] In this embodiment, the capability abstraction layer 103 can match a target heating method from multiple candidate heating methods based on executable heating capability information. It should be noted that executable heating capability information refers to information determined by the capability abstraction layer 103 based on at least one of the following: heating hardware configuration, heating hardware operating status (e.g., whether there is a fault), and the vehicle's current operating conditions (e.g., current battery temperature, state of charge (SOC), vehicle voltage). This information indicates whether the corresponding heating method can currently be invoked and any invocation restrictions.

[0065] Specifically, the executable heating capability information may include at least one of the following: heating mode identifier, function permission status, maximum allowed operating level, remaining heating time, maximum supported temperature, current fault status, and real-time energy consumption. The capability abstraction layer 103 reports this information to the interface processing layer 102 so that the interface processing layer 102 can perceive the underlying real-time hardware capabilities and perform route matching.

[0066] In some implementations, the execution control layer 104 (which may also be referred to as the heating function execution layer in one implementation) refers to the software and hardware control layer used to receive execution control parameters from the capability abstraction layer 103, drive the physical heating actuator to work, and collect the status of the physical heating actuator.

[0067] The execution control layer 104 may include one or more execution master controllers (i.e. Figure 2 (The "battery heating execution controller" in the text). Optionally, the execution main controller can be a microcontroller integrated in the physical heating device, or it can be an electronic control unit (ECU) in the vehicle used to control the motor, electric drive inverter, heat pump, heating film or hydrothermal components.

[0068] like Figure 3 As shown, the multiple execution master controllers in the execution control layer 104 may include at least one of the following: variable frequency film heating execution master controller, non-variable frequency film heating execution master controller, pulse heating execution master controller, stalled rotor heating execution master controller, efficiency-reduced heating execution master controller, heating component hydrothermal execution master controller, waste heat recovery execution master controller, and heat pump execution master controller. It is worth noting that the aforementioned multiple execution master controllers in the execution control layer 104 have a one-to-one corresponding call and data feedback relationship with the aforementioned multiple heating abstract modules in the capability abstraction layer 103.

[0069] The output of the execution control layer 104 is connected to and controls the physical heating actuator. The physical heating actuator refers to a physical hardware device that can directly or indirectly raise the temperature of the power battery. Corresponding to the aforementioned execution main controller, the physical heating actuator includes at least one of the following: a variable frequency heating film, a non-variable frequency heating film, a battery pulse heating circuit, a motor and its electric drive inverter, a heating component (such as a high-voltage PTC heater), a coolant circulation pump, a valve, a heat exchanger, a waste heat recovery device, and a heat pump device.

[0070] like Figure 2 and Figure 3 As shown, the capability abstraction layer 103 and the execution control layer 104 are connected through an execution interaction interface. This execution interaction interface is used to transmit execution control parameters and status feedback information.

[0071] In terms of software architecture, the execution interaction interface can be a software application programming interface (API) within the same controller, or a structured message interface transmitted between controllers via CAN / LIN bus, vehicle Ethernet, or other physical communication links.

[0072] In this embodiment, "fixing" the execution interaction interface means that the input parameter type, output parameter type, parameter meaning, or data format of the interface is predetermined during the development stage, and the interface definition remains unchanged or remains backward compatible when the application function layer changes or the underlying physical hardware is replaced.

[0073] It should be noted that "fixing" refers to the interface definition structure, not that the parameter values ​​transmitted in the interface cannot change dynamically. By fixing the interface, the capability abstraction layer 103 can issue instructions using standardized control protocols (such as heating level request parameters) and receive feedback using standardized feedback structures (such as real-time raw energy consumption parameters, supported maximum temperature parameters, etc.), thus eliminating the tight coupling between the upper-layer software and the lower-layer driver software.

[0074] Based on the above-described battery heating control system, the following describes the process flow of the battery heating control method provided in the embodiments of this application.

[0075] Figure 4 This is a flowchart of a battery heating control method provided in an embodiment of this application. Figure 4 As shown, this battery heating control method can be applied to, for example... Figure 3 The battery heating control system shown herein achieves battery heating control through data interaction between the application layer, interface processing layer, capability abstraction layer, and execution control layer, and may specifically include the following steps S101-S104.

[0076] S101: The interface processing layer receives a battery heating request signal from the application layer.

[0077] In this step, the interface processing layer receives a battery heating request signal from the application layer.

[0078] For example, the battery heating request signal may be generated by a charging heating application, a scheduled heating application, a driving heating application, a low-temperature safety heating application, or a temperature-maintaining heating application. The battery heating request signal may include at least one of the following: requester identifier, heating request status, target temperature, deadline, target heating method, request level, or request priority.

[0079] For example, a battery heating request signal can use the following data structure: Table 1 Example of Battery Heating Request Signal Data Structure

[0080] The data structures and specific values ​​described above are for illustrative purposes only. In other embodiments, the battery heating request signal can be transmitted via function call parameters, shared memory data, service requests, or vehicle bus messages.

[0081] S102: The interface processing layer determines the target heating method based on the battery heating request signal and sends a control call signal to the heating abstract interface corresponding to the target heating method in the capability abstraction layer.

[0082] Specifically, the process of determining the target heating method may include at least one of the direct specification mode and the dynamic matching mode.

[0083] In direct control mode, the interface processing layer parses the battery heating request signal, directly extracts the heating method explicitly specified in the battery heating request signal by the application layer (such as specifying frequency conversion film heating or pulse heating), and uses the specified heating method as the target heating method. In the combined managed mode, the interface processing layer receives managed heating request signals (such as timed heating requests, immediate heating requests, or temperature-maintaining heating requests) sent by the application layer. It combines preset vehicle configuration data (such as vehicle configuration words) with heating capability information reported in real time by the capability abstraction layer (such as the available status and maximum gear of each hardware component) and dynamically matches and determines the target heating method from multiple candidate heating methods according to preset energy efficiency strategies or heating speed strategies.

[0084] After determining the target heating method, the interface processing layer converts the non-standardized or heterogeneous data formats used by different application layer functional modules into a standardized and unified data format that the capability abstraction layer can recognize, and generates a control call signal. For example, the control call signal may include at least one of the following: target heating method identifier, heating request status (such as request to turn on or request to turn off), request level (such as level 1 to level 5), target temperature (such as 15℃ or 20℃), task deadline (such as a precise time point or remaining countdown), and task type (such as timed / immediate / temperature maintenance).

[0085] Furthermore, based on the determined target heating method, the interface processing layer routes the control call signal and sends it to the target heating abstract interface in the capability abstraction layer that matches the target heating method. For example: When the target heating method is determined to be heat pump heating, the interface processing layer sends a control call signal to the heat pump heating abstract interface in the capability abstraction layer. When the target heating method is determined to be hydrothermal heating component, the interface processing layer sends a control call signal to the hydrothermal heating component abstract interface in the capability abstraction layer. When the target heating method is determined to be pulse heating, the interface processing layer sends a control call signal to the pulse heating abstract interface in the capability abstraction layer.

[0086] Through the above process of determining the target heating method, unifying the format conversion, and accurately routing the target abstract interface by the interface processing layer, the upper layer application is prevented from directly perceiving the specific heating abstract interface details of the lower layer. This achieves standardized access and decoupled routing of application layer heating requirements to specific hardware capabilities of the capability abstract layer.

[0087] S103: The capability abstraction layer determines the execution control parameters corresponding to the target heating method based on the control call signal and the execution interaction interface, and sends the execution control parameters to the execution control layer.

[0088] Specifically, the execution interaction interface, serving as a standardized data channel between the capability abstraction layer and the execution control layer, pre-defines the input parameter formats and output parameter specifications corresponding to different heating methods, thereby shielding the differences in underlying control protocols between different physical heating hardware. Upon receiving a control call signal, the capability abstraction layer parses the heating requirement (such as requested gear level, target temperature, or heating on / off status) and performs data mapping and transformation through the execution interaction interface to generate execution control parameters suitable for the corresponding execution control layer.

[0089] For example, the control parameters may include at least one of the following: heating start command, heating stop command, requested setting, requested power, target temperature, control duty cycle, or allowed operating time. For example: When the target heating method is variable frequency film heating, the execution control parameters generated by the capability abstraction layer through the execution interaction interface mapping can include a specific requested gear from a preset gear range (such as gear 1 to gear 5); When the target heating method is non-frequency conversion film heating, the execution control parameters generated by the capability abstraction layer through the execution interaction interface can include switch-type on or off requests; When the target heating method is hydrothermal heating of the heating component, the execution control parameters generated by the capability abstraction layer through the execution interaction interface may include the heating component power request (e.g., 2kW~8kW), the coolant circulation pump speed request, or the valve opening request. When the target heating method is heat pump heating, the control parameters to be executed may include compressor target speed request, electronic expansion valve opening request, or fan speed request.

[0090] After determining the execution control parameters based on the execution interaction interface, the capability abstraction layer sends the execution control parameters to the execution control layer. In a homogeneous deployment scenario (i.e., the capability abstraction layer and the execution control layer are deployed within the same controller), the execution control parameters can be directly transmitted through the controller's internal software function interfaces (such as API calls, shared memory, or software middleware channels). In a heterogeneous distributed deployment scenario (i.e., the capability abstraction layer and the execution control layer are distributed within different vehicle electronic control units), the execution control parameters can be encapsulated as Controller Area Network (CAN) messages, in-vehicle Ethernet (Ethernet) messages, FlexRay messages, or Local Area Network (LIN) messages, and sent to the corresponding execution master controller in the execution control layer via the in-vehicle communication bus.

[0091] Through the parameter determination and distribution process based on the execution interaction interface, the capability abstraction layer realizes the standardized conversion of upper-layer abstract instructions to lower-layer physical execution instructions, avoiding the upper-layer logic from directly perceiving the specific hardware driver protocol at the lower level, and ensuring the layered decoupling and general adaptability of the control link.

[0092] S104: The execution control layer drives the physical heating actuator and provides feedback on its status.

[0093] In this step, the execution control layer receives the execution control parameters, and the corresponding execution master controller drives the physical heating actuator based on the execution control parameters.

[0094] For example, the variable frequency membrane heating actuator main controller can adjust the voltage, current or pulse width modulation signal output to the heating membrane according to the requested gear; the heating component hydrothermal actuator main controller can control the heating component, circulation pump and valves to make the heated coolant flow through the battery heat exchange circuit; the heat pump actuator main controller can adjust the compressor speed, electronic expansion valve opening and circulation pump speed to provide heat to the power battery.

[0095] During the process of driving the physical heating actuator, the execution control layer acquires the status feedback information of the physical heating actuator and transmits the status feedback information back to the capability abstraction layer. The status feedback information may include at least one of the following: real-time raw energy consumption, function execution status, maximum allowable operating level, function availability status, remaining heating time, maximum supported temperature, and fault status.

[0096] For example, the execution control layer can periodically transmit status feedback information. For instance, the execution control layer can transmit status feedback information at preset intervals of 10 milliseconds, 20 milliseconds, 50 milliseconds, 100 milliseconds, or other preset intervals. The specific feedback interval can be determined based on the vehicle network bandwidth, the dynamic response speed of the heating method, and the control safety level.

[0097] Through the above steps, the application layer does not directly control the physical heating actuator. Instead, the interface processing layer, capability abstraction layer, and execution control layer sequentially transmit control information, and the execution control layer transmits the status feedback information of the physical heating actuator back to the capability abstraction layer, thus forming a layered battery heating control link.

[0098] The following is an exemplary description of the implementation examples for input parameter compliance verification and priority arbitration.

[0099] In some embodiments, the interface processing layer sends a control call signal to the capability abstraction layer based on the battery heating request signal, which may include the following sub-steps.

[0100] S1021: Perform input parameter compliance verification on the battery heating request signal.

[0101] In this step, the interface processing layer performs input parameter compliance verification on the received battery heating request signal. Input parameter compliance verification may include at least one of the following: requester identity verification, request parameter integrity verification, parameter type verification, parameter value range verification, request timing verification, and request interface permission verification.

[0102] For example, the interface processing layer can set the allowable range of the target temperature for a timed heating request to -10℃ to 40℃, and the allowable range of the deadline to 0 minutes to 24 hours after the current time. If the received target temperature is 80℃, it is determined that the target temperature exceeds the allowable range, and the request is rejected or the target temperature is limited to the preset upper limit.

[0103] As another example, the interface processing layer can verify whether the requester identifier is included in the pre-registered requester list. If the requester identifier cannot be identified, the interface processing layer may not send the corresponding control call signal to the capability abstraction layer and may record illegal call diagnostic information.

[0104] The aforementioned temperature and time ranges are for illustrative purposes only. Actual ranges can be calibrated based on battery type, vehicle safety requirements, and thermal management control needs.

[0105] Step S1022: Priority arbitration is performed on multiple concurrent requests.

[0106] If the input parameter compliance verification passes, when the interface processing layer receives multiple concurrent battery heating request signals, it arbitrates according to the preset priority strategy and generates a control call signal.

[0107] Preset priority strategies can be implemented using a fixed priority table, dynamic priority calculation, state machine, or request weight calculation. For example, the following priorities can be set: Table 2 Examples of Preset Priority Strategies

[0108] In Table 2, smaller values ​​indicate higher priority. The above priority relationships are merely examples and do not limit the scope of protection of this application.

[0109] When two requests can be executed simultaneously without conflicts in energy consumption, power, or hardware resources, the interface processing layer can also merge the two requests. For example, if the target temperatures of a charging heating request and a temperature maintenance heating request are the same or similar, they can be merged into a single heating task. When two requests conflict with each other, the higher-priority request can be retained, the lower-priority request can be paused, or multiple requests can be limited and executed in parallel based on power resources.

[0110] The interface processing layer can also record the requester's identifier, receiving time, priority, task status, and termination condition for each request, so as to resume the suspended low-priority requests after the high-priority requests have ended.

[0111] The following provides exemplary embodiments of the direct control interface and the combined managed interface.

[0112] In some embodiments, the interface processing layer can receive a battery heating request signal from the application layer through at least one of a direct control interface and a combined managed interface.

[0113] The direct control interface is used to receive call signals generated by the application layer for preset heating methods. The application layer specifies the heating method to be invoked and the corresponding control parameters through the direct control interface.

[0114] For example, a test application or a specific vehicle function can request to start the variable frequency membrane heating at level 3 via the direct control interface. After completing identity verification, parameter verification, and conflict arbitration, the interface processing layer sends the control call signal to the variable frequency membrane heating abstract interface in the capability abstraction layer.

[0115] In some implementations, the functional application layer can directly call the heating function interface to call the direct control interface for each heating method provided by the processing layer, so as to preset the heating method and corresponding request parameters.

[0116] Optionally, the direct control interface may include at least one of the following: a variable frequency film heating direct control interface, a non-variable frequency film heating direct control interface, a pulse heating direct control interface, a locked rotor heating direct control interface, a degraded heating direct control interface, a heating component hydrothermal direct control interface, a waste heat recovery direct control interface, and a heat pump heating direct control interface.

[0117] Figures 5(a)-(b) show the flowchart of the direct-control heating method for battery heating function. As shown in Figures 5(a)-(b), the control process may include the following steps: S101a: After the physical heating actuator is woken up, it performs a self-check on its own hardware status and sends hardware parameter information to the corresponding execution master controller.

[0118] S102b: The execution control layer determines at least one of the following based on the hardware parameters and operating status of the physical heating actuator: the maximum allowable level of the corresponding heating mode, the remaining heating time, the function allowable status, the maximum supported temperature, or the fault status. The execution control layer then sends the relevant information to the capability abstraction layer 103 through the heating execution interaction interface.

[0119] S103c: The capability abstraction layer determines whether the corresponding heating method is currently allowed to be executed based on the vehicle status, current operating conditions, diagnostic results, and safety protection conditions. If execution is not allowed, it reports to the interface processing layer 102 that the maximum allowed operating level is 0, the remaining heating time is 0, and / or the function permission status is not allowed; if execution is allowed, it reports to the interface processing layer 102 the actual maximum allowed operating level, the remaining heating time, the highest supported temperature, and the function permission status.

[0120] S104d: The interface processing layer reads the vehicle configuration word and determines whether the current vehicle is configured with or supports the corresponding heating method. If supported, it feeds back the executable heating capability information reported by the capability abstraction layer to the functional application layer; if not supported, it feeds back to the functional application layer that the maximum allowed heating level is 0, the remaining heating time is 0, and / or the function permission status is not allowed.

[0121] S105e: When the first battery heating function application determines that there is an execution requirement for a corresponding heating method based on the executable heating capacity information, it calls the corresponding direct control interface and sends the first interface caller ID and the first request level; for the on / off heating method, the heating request is sent as a request to heat.

[0122] S106f: When the second battery heating function application determines that there is an execution requirement for a corresponding heating method based on the executable heating capacity information, it calls the same direct control interface and sends the second interface caller ID and the second request level; for the on / off heating method, the heating request is sent as a request to heat.

[0123] S107g: The interface processing layer receives call parameters from multiple battery heating function applications and verifies the identity of the interface caller, parameter integrity, parameter type, parameter range, interface permissions, and request sequence. After successful verification, the layer records and latches the requests corresponding to each caller according to their interface caller ID.

[0124] For a level-based heating method, the interface processing layer can determine the highest requested level among multiple valid level requests as a candidate valid level for that heating method. For a switch-type heating method, as long as there is at least one valid heating request signal, a candidate valid request can be determined as a heating request. The candidate valid requests are further arbitrated by a unified call control system of various functional abstractions.

[0125] S108h: The capability abstraction layer receives control call signals from the interface processing layer and determines the final execution control parameters based on the vehicle status, vehicle operating condition, fault status, and safety protection conditions. If execution is allowed, it sends the corresponding gear request or heating request to the execution control layer; if execution is not allowed, it sends a 0 gear or no heating request to the execution control layer.

[0126] S109i: The execution control layer controls the corresponding physical heating actuator to work according to the execution control parameters.

[0127] S110j: The physical heating actuator performs heating and sends its own hardware status, actual power, or execution status to the main controller.

[0128] S111k: The execution control layer monitors the operation of the physical heating actuator and periodically feeds back to the capability abstraction layer at least one of the following: real-time raw energy consumption, function execution status, maximum allowable operating level, remaining heating time, and fault status.

[0129] S112l: The capability abstraction layer filters, calibrates, or performs validity processing on the real-time raw energy consumption and feeds back the processed real-time energy consumption and function execution status to the interface processing layer.

[0130] S113m: The interface processing layer 102 establishes a correspondence between the interface caller's identity ID and the interface caller's identity ID-feedback, and sends the real-time energy consumption and function execution status after processing to the corresponding battery heating function application with a valid request.

[0131] S114n: When the second battery heating function application no longer has the corresponding heating requirement, send the second interface caller's identity ID and a 0-level request or no heating request through the direct control interface.

[0132] S115o: The interface processing layer clears or updates the latched request corresponding to the identity ID of the second interface caller, and re-traverses the remaining valid requests. If the second request threshold was originally higher than the first request threshold, the valid threshold is lowered to the first request threshold; if the second request threshold is not higher than the first request threshold, the current valid threshold can be maintained.

[0133] S116p: When the first battery heating function application no longer has the corresponding heating requirement, the first interface caller ID and a 0-level request or no heating request are sent through the direct control interface.

[0134] S117q: After determining that none of the callers have a valid heating request, the interface processing layer 102 sends a 0-level request or no heating request to the capability abstraction layer 103 through the unified call control of each function abstraction.

[0135] S118r: When the second battery heating function application no longer has the corresponding heating requirement, the capability abstraction layer is invoked to send the execution control parameters for stopping heating to the execution control layer.

[0136] S119s: The execution control layer 104 controls the physical heating actuator to stop heating and feeds back the function execution status as not executed to the capability abstraction layer 103.

[0137] S120t: The capability abstraction layer receives the call parameters from the interface processing layer, requesting to stop heating, and requests work from the execution control layer by sending: gear request = 0 gear (heating request = no request).

[0138] S121u: The execution control layer, based on the capability abstraction layer, controls the battery heating execution controller's operating parameters to stop heating.

[0139] S122v: The physical heating actuator stops heating and sends its own hardware parameter information to the main controller.

[0140] S123w: The execution control layer monitors the heating process of the physical heating actuator and sends the function execution status to the capability abstraction layer as 0 (not executed).

[0141] Through the above process, the interface processing layer can uniformly record and aggregate multiple caller requests for the same heating method, avoiding multiple application layer functions directly competing for the underlying executor.

[0142] For example, the combined managed interface is used to receive managed heating request signals from the application layer. In this mode, the application layer can provide only the target temperature, deadline, or heating request without specifying the specific heating method at the underlying level. The interface processing layer then selects the target heating method based on the vehicle configuration and the actual capabilities of each heating method.

[0143] Optionally, the combined managed interface may include at least one of a timed heating interface, an immediate heating interface, and a temperature-maintaining heating interface. The interface processing layer can maintain the task state machine corresponding to different combined managed interfaces and manage the establishment, initiation, continuation, switching, completion, and exit of heating tasks.

[0144] Figures 6(a)-(b) show the flowcharts of the battery heating application using the timed heating basic combination interface. As shown in Figures 6(a)-(b), in a specific process example, the application call process of the timed heating combination managed interface is implemented as follows: the functional application layer can call the heating function control API - basic combination interface - timed heating interface in the interface processing layer to implement the timed heating function. The specific call flow is as follows: S201: When the first battery heating function application recognizes that there is a battery heating demand at a future preset time, it sends the first interface caller ID, the requested heating status, the timed heating target temperature, and the timed heating end time to the basic combination interface - timed heating in the heating function control API.

[0145] S202: When the second battery heating function application recognizes that there is a battery heating requirement at a preset time in the future, it sends the second interface caller ID, the requested heating status, the target temperature for timed heating, and the timed heating end time to the basic combination interface - timed heating.

[0146] S203: Basic Combination Interface - Timed Heating receives input parameters from one or more callers, verifies the identity of the interface caller and the rationality of the parameters, and establishes a timed heating task corresponding to the identity ID of each interface caller after the verification is passed.

[0147] Each timed heating task can record at least the API caller's ID, target temperature, deadline, task status, selected heating method, estimated heating duration, planned start time, and termination conditions.

[0148] S204: The interface processing layer reads the vehicle configuration word, the battery pack temperature drop map stored in the EEPROM, and the battery pack temperature rise map corresponding to different heating methods, and obtains the executable heating capability information reported by the capability abstraction layer and the weather information provided by the cloud.

[0149] The basic combined control - timed heating interface call control determines the target heating method based on the timed heating target temperature, cutoff time, current battery temperature, current ambient temperature, predicted ambient temperature, and the temperature rise capability of each candidate heating method, according to at least one of energy consumption, heating speed, target temperature attainability, and current permissible state, and calculates the vehicle wake-up time and the planned start heating time.

[0150] If heating needs to start immediately, set the task status to running; if heating does not need to start immediately, create a future wake-up task and set the task status to waiting to be executed.

[0151] S205: Upon reaching the planned start time for heating, the interface processing layer re-acquires vehicle configuration, weather information, current battery temperature, and executable heating capacity information, and recalculates the heating method and request parameters based on the latest operating conditions. If it is determined that heating needs to be started, a request for a specific setting or heating request is sent to the corresponding capability abstraction interface through the unified call control of each functional abstraction.

[0152] S206: The capability abstraction layer performs a condition availability check. If execution is allowed, the corresponding execution control parameters are sent to the execution control layer; if execution is not allowed, a request for 0 gears or no heating is sent, and feedback that the condition is not met is sent to the interface processing layer.

[0153] S207: The execution control layer, based on the capability abstraction layer, controls the battery heating execution controller's working parameters to execute heating, and then proceeds to S208.

[0154] S208: The physical heating actuator performs the heating action, sends its own hardware parameter information to the main controller, and enters S209.

[0155] S209: The execution control layer monitors the heating process of the physical heating actuator and continuously updates and sends the following to the capability abstraction layer: real-time raw energy consumption (unfiltered) = xkw; function execution status = 0 to N (in execution), then proceeds to S210.

[0156] S210: The capability abstraction layer receives execution information feedback from the execution control layer, filters the real-time raw energy consumption (unfiltered), and continuously updates and sends the following to the interface processing layer: Real-time energy consumption (processed) = xkw; Function execution status = 0 to N (in execution), then proceeds to S211.

[0157] S211: The interface processing layer, based on the actual status of each timed heating task, provides feedback to the task that is currently executing, and to the task that has not yet reached its execution time, provides feedback that it is waiting to execute. The status is then sent to the corresponding caller via the interface caller's identity ID.

[0158] S212: When the target temperature corresponding to a certain caller has been reached before the deadline, or the completion conditions of the corresponding timed heating task are met, the interface processing layer sets the task to be completed and sends feedback to the corresponding caller that the task has been completed.

[0159] S213: When all timed heating tasks have been completed, canceled, or abnormally terminated, the interface processing layer sends a 0-level or no-heating request to the corresponding capability abstraction interface through the unified call control of each function abstraction, and the execution control layer controls the physical heating actuator to stop working.

[0160] S214: If the interface processing layer determines that the timed heating task of the second battery heating function application has been completed, it sends an execution status feedback = execution completed to the second battery heating function application, and sends an execution status feedback = waiting to execute to the first battery heating function application. It also sends the corresponding feedback of the interface caller ID and the interface caller ID-feedback, and then calls the corresponding capability abstraction layer of each heating method to send: gear request = 0 gear (heating request = no request).

[0161] S215: The first battery heating function application identifies the feedback information receiver based on the interface caller's identity ID in the interface processing layer and receives it; execution status feedback = waiting to execute.

[0162] S216: The second battery heating function application identifies the feedback information receiver based on the interface caller's identity ID-feedback in the interface processing layer, and receives it; execution status feedback = execution completed.

[0163] S217: For the timed heating task execution flowchart of the first battery heating function application, refer to the above execution and interaction flowchart of the second battery heating function application.

[0164] S218: The capability abstraction layer receives the call parameters from the interface processing layer, requests to stop heating, requests work from the execution control layer, and sends: gear request = 0 gear (heating request = no request).

[0165] S219: The execution control layer, based on the capability abstraction layer, controls the battery heating execution controller's operating parameters to stop heating.

[0166] S220: The physical heating actuator stops heating and sends its own hardware parameter information to the main controller.

[0167] S221: The execution control layer monitors the heating process of the physical heating actuator and sends the function execution status to the capability abstraction layer as 0 (not executed).

[0168] Next, the control logic for calling the timed heating interface will be explained with an example.

[0169] Figure 7The flowchart of the control logic call for the timed heating interface is shown. Figure 7 As shown, in some embodiments, the internal control process of the basic combination control - timed heating interface call control in the interface processing layer may include the following steps S501-S526.

[0170] S501: The battery heating main controller is woken up and starts running after initialization.

[0171] S502: Basic combination control - timed heating interface call control determines whether the basic combination interface has received a call from the functional application layer. If a call is received, proceed to S503; otherwise, proceed to S504.

[0172] S503: Basic combined control - timed heating interface call control. This checks the validity of the interface caller ID in the call parameters and verifies whether the timed heating request, target temperature, and deadline meet the preset definitions. If the verification passes, proceed to S505; otherwise, reject the call, record diagnostic information, and proceed to S504.

[0173] S504: Basic combined control - timed heating interface call control determines whether there is a timed heating task that has not yet been completed. If so, proceed to S510; otherwise, proceed to S526.

[0174] S505: Basic combined control - timed heating interface calls the control to read the mapping relationship between the current ambient temperature, the current battery pack temperature and the temperature drop rate stored in the EEPROM, and obtains real-time weather information or forecast weather information provided by the cloud.

[0175] The basic combined control – timed heating interface call control – calculates the estimated cooling time required for the battery temperature to naturally decrease to the target temperature of the corresponding timed heating task based on the current ambient temperature, predicted ambient temperature, and current battery temperature. If the current battery temperature is less than or equal to the target temperature, the estimated cooling time is set to 0.

[0176] S506: Basic combined control - timed heating interface call control traverses all timed heating tasks and calculates the remaining time before the deadline for each task according to the following formula: Remaining time before task deadline = Timed heating deadline - Current time.

[0177] S507: Basic combined control - timed heating interface call control to determine whether the remaining time before the task deadline is less than or equal to the corresponding estimated cooling time.

[0178] If the remaining time before the task deadline is less than or equal to the estimated cooling time, it means that without active heating, the predicted battery temperature will still be no lower than the target temperature at the deadline, and the process can proceed to S518; otherwise, proceed to S508.

[0179] S508: Basic Combination Control - Timed Heating Interface Call Control. Based on the request status, target temperature and deadline sent by the corresponding caller, the timed heating task is established, updated or cleared, and the correspondence between the target temperature and the deadline is recorded.

[0180] S509: Basic Combination Control - Timed Heating Interface Call Control establishes pre-wake-up tasks based on the deadline of each timed heating task. The pre-wake-up time can be set to a time earlier than the corresponding deadline by a preset duration. For tasks in a waiting state, Basic Combination Control - Timed Heating Interface Call Control can use the basic combination interface to provide feedback to the corresponding caller indicating that execution is pending.

[0181] S510: Basic combined control - timed heating interface call control to obtain the heating methods supported by the vehicle model represented by the vehicle configuration word, and obtain the executable heating capability information provided by the capability abstraction layer, thereby determining the currently available candidate heating methods.

[0182] S511: Basic combined control - timed heating interface calls the control to read the mapping relationship between the current ambient temperature, current battery pack temperature and temperature rise rate stored in the EEPROM corresponding to each candidate heating method, and calculates the estimated heating time required to heat the battery to the target temperature of each task by using each candidate heating method, in conjunction with the weather information provided by the cloud.

[0183] If the current battery temperature is greater than or equal to the target temperature, the estimated heating time is set to 0. For heating methods with multiple settings, the estimated heating time for each setting can be calculated separately.

[0184] S512: Basic Combination Control - Timed Heating Interface Call Control: Based on the estimated heating duration corresponding to each candidate heating method, calculate the planned start time for each timed heating task when using the corresponding heating method. Planned start time of heating = Timed heating end time - Estimated heating duration.

[0185] S513: Basic combined control - timed heating interface call control determines whether there is a heating mode where the planned start time has arrived or is earlier than the current time. If so, proceed to S520; otherwise, proceed to S514. (See reference here.) Figure 13 , Figure 13 The algorithm diagram for selecting the heating execution mode by calling the basic combined control-timed heating interface is shown.

[0186] S514: Basic Combination Control - Timed Heating Interface Call Control selects the combination whose planned start time is closest to the current time from the combination of tasks and heating methods that have not yet reached the planned start time of heating, as the target combination for the future wake-up task to be established.

[0187] S515: Basic Combination Control - Timed Heating Interface Call Control estimates the predicted battery temperature at the planned start time of the target combination based on the temperature drop map, current ambient temperature, predicted ambient temperature, and current battery temperature.

[0188] S516: Basic combined control - timed heating interface call control calculates the temperature drop compensation time required to heat the predicted battery temperature to the current battery temperature or the preset reference temperature according to the temperature rise Map corresponding to the target heating method.

[0189] S517: Basic combined control - timed heating interface call control determines the corrected future wake-up time according to the following formula: Future wake-up time = Target plan start heating time - Temperature drop compensation time.

[0190] The basic combination control - timed heating interface calls the control to establish the corresponding wake-up task, and wakes up the whole vehicle when the future wake-up time is reached, and then enters S526.

[0191] S518: Basic combination control - timed heating interface call control clears or does not create timed heating tasks that do not currently require active heating.

[0192] S519: Basic Combination Control - Timed Heating Interface Call Control. Based on the interface caller ID in the input parameters of the basic combination interface, the control sends feedback to the corresponding task party that the execution is complete and returns to S502.

[0193] S520: Basic Combination Control - Timed Heating Interface Call Control selects the target heating method that is closest to the current time and is currently in an available state from the combination of tasks and heating methods whose planned start time has arrived or is earlier than the current time.

[0194] When multiple candidate methods are available, the target heating method can be selected by comprehensively considering factors such as energy consumption, heating rate, target temperature attainability, remaining heating time, and noise.

[0195] S521: Basic combined control - timed heating interface call control to determine whether the battery maximum temperature overheating, high voltage overcurrent, insulation abnormality, low SOC, heating device failure, or other safety monitoring restrictions have been triggered. If a restriction is triggered, proceed to S525; otherwise, proceed to S522.

[0196] S522: Basic combined control - timed heating interface call control forms a call requirement for the target heating method, and the corresponding heating abstract interface in the unified call control capability abstract layer of each function abstraction requests the execution of heating.

[0197] S523: Basic combined control - timed heating interface call control judgment capability abstraction layer feedback on successful execution. If successful, proceed to S524; otherwise, proceed to S525.

[0198] S524: Basic combination control - timed heating interface call control. Based on the interface caller's identity ID, it reports the execution status to the corresponding task party and returns to S502 to continue monitoring the task execution status.

[0199] S525: Basic combined control - timed heating interface call control can re-execute S522 and S523 according to a preset number of times or a preset time interval. If it still fails to execute successfully after multiple retries, the corresponding heating request is stopped, the task is set as an abnormal interrupt, and the abnormal interruption is reported to the corresponding task party according to the interface caller's identity ID, and then returns to S502.

[0200] S526: When there are no pending timed heating tasks or only a future wake-up task has been established, the current round of control ends and the P800_battery heating main controller enters sleep mode.

[0201] Next, the application call process of the Immediate Heating Combined Managed Interface will be illustrated with an example.

[0202] Figures 8(a)-(b) show the flowchart of the battery heating function application using the instant heating basic combination interface. As shown in Figures 8(a)-(b), in another specific embodiment, the function application layer can call the heating function control API - basic combination interface - instant heating interface to implement the instant heating function. Specifically, this includes steps S301 to S319.

[0203] S301: The first battery heating function application recognizes that there is an immediate heating demand and sends an immediate heating request signal to the immediate heating combination interface of the interface processing layer. The immediate heating request signal contains the first requester identifier (ID1) and heating request status parameters indicating that heating is requested, and then proceeds to S302.

[0204] S302: The second battery heating function application recognizes that there is an immediate heating demand and sends an immediate heating request signal to the immediate heating combination interface of the interface processing layer. The immediate heating request signal contains the second requester identifier (ID2) and heating request status parameters indicating that heating is requested, and then proceeds to S303.

[0205] S303: The interface processing layer receives an immediate heating request signal from the first requester identifier and the second requester identifier through the immediate heating combination interface, and performs input parameter compliance verification on the immediate heating request signal; after the verification is passed, the interface processing layer matches the target heating method according to the preset heating rate priority strategy, and after checking the allowable status of the corresponding target heating method in the capability abstraction layer, sends a control call signal containing the target request level or heating request instruction to the target heating abstraction interface corresponding to the target heating method in the capability abstraction layer, and enters S304.

[0206] S304: The capability abstraction layer receives the control call signal from the interface processing layer and performs an availability assessment of the control call signal in conjunction with the vehicle's current operating parameters, diagnostic information, and safety control strategy. If the assessment indicates no restriction, the capability abstraction layer sends execution control parameters containing the target gear request to the execution control layer based on the control call signal. If the assessment indicates a restriction, the capability abstraction layer sends execution control parameters containing gear 0 or no heating request to the execution control layer, and proceeds to S305.

[0207] S305: The execution control layer configures the working parameters of the physical heating execution controller according to the execution control parameters issued by the capability abstraction layer to drive the physical heating actuator to perform heating action, and enters S306.

[0208] S306: The physical heating actuator responds to the drive action to perform battery heating and feeds back its own hardware operating parameter information to the execution master controller in the execution control layer in real time, and enters S307.

[0209] S307: The execution control layer monitors the heating process of the physical heating actuator and periodically updates and sends status feedback information to the capability abstraction layer. The status feedback information includes unfiltered raw energy consumption data and function execution status parameters indicating that the function is in execution. Then proceed to S308.

[0210] S308: After receiving the status feedback information, the capability abstraction layer performs smoothing filtering on the original energy consumption data to generate real-time processed energy consumption data, and sends the feedback parameters containing the real-time processed energy consumption data and the function execution status parameters to the interface processing layer, and proceeds to S309.

[0211] S309: The interface processing layer receives the feedback parameters sent by the capability abstraction layer. If it is determined that the immediate heating task is being executed normally, the function execution status is mapped to the task execution status feedback indicating that it is being executed. The corresponding feedback mapping relationship is established in combination with the received requester identifier. The task execution status feedback is fed back to each requester in the application layer respectively, and then proceeds to S310 and S311.

[0212] S310: The first battery heating function application identifies the feedback information that matches itself according to the feedback mapping relationship, and obtains the indication as the task execution status feedback.

[0213] S311: The second battery heating function application identifies the feedback information that matches itself according to the feedback mapping relationship, obtains the indication as the task execution status feedback, and enters S312.

[0214] S312: When the second battery heating function determines that the battery temperature has reached the preset condition or the heating termination condition is met, it determines to cancel the immediate heating requirement, sends a control signal containing the second requester identifier (ID2) and a heating request status parameter indicating no request to the immediate heating combination interface of the interface processing layer, and enters S313.

[0215] S313: The interface processing layer receives the control signal from the second battery heating function application. After the input parameter compliance verification is passed, it clears the immediate heating task corresponding to the second requester identifier and feeds back the task execution status indicating exit to the second battery heating function application. At the same time, the interface processing layer recognizes that the immediate heating task corresponding to the first requester identifier (ID1) still exists, and continues to send the control call signal of the current target heating method to the capability abstraction layer to keep heating execution, and enters S314.

[0216] S314: The interface processing layer triggers the safety fallback protection logic. When it detects an abnormal communication with the controller where the first battery heating function application is located or the battery's maximum temperature exceeds a preset safety threshold, it actively terminates the heating process, sends a task execution status feedback indicating exit to the first battery heating function application, and sends a control call signal containing 0 levels or no heating request to the abstract interface of the corresponding target heating mode in the capability abstraction layer, thus entering S315 and S316.

[0217] S315: The first battery heating function application receives the task execution status feedback indicating exit based on the feedback information from the interface processing layer.

[0218] S316: The capability abstraction layer receives a stop heating control call signal from the interface processing layer, sends execution control parameters containing a 0-level or no heating request to the execution control layer, and proceeds to S317.

[0219] S317: The execution control layer adjusts the working parameters of the physical heating execution controller to shut down the physical heating action based on the execution control parameters issued by the capability abstraction layer, and then proceeds to S318.

[0220] S318: The physical heating actuator stops heating and sends the hardware operation parameter information in the stopped state to the execution master controller in the execution control layer in real time, and then proceeds to S319.

[0221] S319: The execution control layer monitors the stopping process of the physical heating actuator, updates and sends status feedback information containing the 0 gear or non-executed function execution status parameters to the capability abstraction layer, and completes the immediate heating control process.

[0222] Next, the control logic for calling the immediate heating interface will be illustrated with an example.

[0223] Figure 9 The flowchart of the control logic for the immediate heating interface call is shown. Figure 9 As shown, the internal control process of the basic combined control - immediate heating interface call control may include the following steps: S601: The battery heating main controller is woken up and starts running after initialization.

[0224] S602: Basic Combination Control - Immediate Heating Interface Call Control determines whether the Basic Combination Control - Immediate Heating interface has received a call from the functional application layer. If received, proceed to S603; otherwise, proceed to S604.

[0225] S603: Basic combined control - immediate heating interface call control determines whether the interface caller ID in the input parameters is valid and whether the heating request conforms to the preset definition. If the verification passes, proceed to S605; otherwise, reject the call and proceed to S604.

[0226] S604: Basic combination control - Immediate heating interface call control determines whether there are still any immediate heating tasks that have not yet exited. If so, proceed to S606; otherwise, proceed to S612.

[0227] S605: Basic Combination Control - Immediate Heating Interface Call Control: Based on the heating request sent by the corresponding caller, immediately create, update, or clear the immediate heating task in real time.

[0228] S606: Basic Combination Control - Immediate Heating Interface Call Control traverses all immediate heating tasks to determine if at least one valid heating request task exists. In one example, since the immediate heating interface does not have a target temperature parameter set, all valid immediate heating tasks can be merged into a single immediate heating request, and the caller can cancel the request or use preset safety conditions to control task exit.

[0229] S607: Basic combined control - immediate heating interface call control obtains the heating methods supported by the vehicle model in the vehicle configuration word and the executable heating capability information reported by the capability abstraction layer, determines the currently available candidate heating methods, and selects the target heating method according to the comprehensive strategy of prioritizing heating speed.

[0230] S608: Basic Combination Control - Immediate Heating Interface Call Control determines whether battery over-temperature, high-voltage overcurrent, low SOC, insulation abnormality, heating device malfunction, or other safety monitoring restrictions have been triggered. If a restriction is triggered, sending a valid heating request is prohibited and the process proceeds to S610; otherwise, it proceeds to S609.

[0231] S609: Basic combination control - immediate heating interface call control forms a call requirement for the target heating method, and the corresponding heating abstract interface in the unified call control capability abstraction layer of each function abstraction requests the execution of heating.

[0232] S610: Basic Combination Control - Immediate Heating Interface Call Control. Based on the interface caller ID in the Basic Combination Interface - Immediate Heating input parameters, the system feeds back the task execution status to the corresponding task party. It reports "Executing" when heating is successful; and reports "Exit" when the caller cancels the request or triggers an exit condition.

[0233] S611: Basic combined control - Immediate heating interface call control determines whether all immediate heating tasks have been canceled, exited, or abnormally terminated. If so, it sends a 0-level or no heating request through the unified call control of each function abstraction and enters S612; otherwise, it returns to S602.

[0234] S612: This round of tasks is over, and the battery heating main controller enters sleep mode.

[0235] Next, the application call process of the temperature control and heating combination managed interface will be illustrated by example.

[0236] Figures 10(a)-(b) show the flowchart of the battery heating function application using the temperature maintenance heating basic combination interface. As shown in Figures 10(a)-(b), in some implementations, the functional application layer can call the basic combination interface - temperature maintenance heating function control API - basic combination interface - temperature maintenance heating interface to implement the temperature maintenance heating function. The specific calling process includes S401-S422.

[0237] S401: The first battery heating function application recognizes that there is a need to maintain the battery temperature within a preset time period in the future, and sends a temperature maintenance heating request signal to the temperature maintenance heating combination interface of the interface processing layer. The temperature maintenance heating request signal includes the first requester identifier (ID1), the temperature maintenance request status parameter indicating that heating is requested, the target maintenance temperature (x℃) and the maintenance deadline (year / month / day / hour / minute), and then proceeds to S403.

[0238] S402: The second battery heating function application recognizes that there is a need to maintain the battery temperature within a preset time period in the future, and sends a temperature maintenance heating request signal to the temperature maintenance heating combination interface of the interface processing layer. The temperature maintenance heating request signal includes the second requester identifier (ID2), temperature maintenance request status parameters indicating that heating is requested, target maintenance temperature (x℃) and maintenance end time (year / month / day / hour / minute), and proceeds to S403.

[0239] S403: The interface processing layer receives the temperature maintenance heating request signal from the first requester identifier and the second requester identifier through the temperature maintenance heating combination interface, and performs input parameter compliance verification on the temperature maintenance heating request signal; after the verification is passed, temperature maintenance heating tasks corresponding to the first requester identifier and the second requester identifier are established respectively, and proceed to S404.

[0240] S404: The interface processing layer obtains the vehicle configuration word and combines it with the battery pack temperature drop mapping table and the battery pack temperature rise mapping table of each heating method stored in the non-volatile memory (EEPROM). Based on the highest maintenance temperature and maintenance end time of each temperature maintenance heating task in different time periods, the target heating method is matched according to the lowest energy consumption priority strategy, and the estimated start heating time and vehicle wake-up time are calculated to ensure that the lowest battery temperature is not lower than the target maintenance temperature during the temperature maintenance period. If it is determined that immediate heating is required, heating control is started and the application layer is fed back an indication that the task is in progress. If it is determined that immediate heating is not required, a future wake-up task is established based on the estimated start heating time and the application layer is fed back an indication that the task is waiting to be executed. At the same time, a mapping relationship between the requester identifier and the feedback information is established, and the process proceeds to S405, S406 and S407.

[0241] S405: The first battery heating function application receives feedback information corresponding to its own request according to the mapping relationship, and obtains the feedback of the task execution status as indicated.

[0242] S406: The second battery heating function application receives feedback information corresponding to its own request according to the mapping relationship, and obtains the task execution status feedback indicating that it is in progress.

[0243] S407: When the interface processing layer detects that the estimated start time of heating has been reached, it re-acquires the vehicle configuration word and the latest temperature drop / temperature rise mapping table, and checks the maintenance cutoff time with the target maintenance temperature; when it is determined that heating is required immediately, it sends a control call signal containing the target request level or heating request instruction to the target heating abstract interface corresponding to the target heating method in the capability abstract layer according to the lowest energy consumption priority strategy, and enters S408.

[0244] S408: The capability abstraction layer receives the control call signal from the interface processing layer and performs an availability assessment of the control call signal in conjunction with the vehicle's current operating parameters, diagnostic information, and safety control strategy; if the assessment is unrestricted, the capability abstraction layer sends execution control parameters containing the target gear request to the execution control layer based on the control call signal; if the assessment is restricted, it sends execution control parameters containing gear 0 or no heating request to the execution control layer, and proceeds to S409.

[0245] S409: The execution control layer configures the working parameters of the physical heating execution controller according to the execution control parameters issued by the capability abstraction layer to drive the physical heating actuator to perform heating action, and enters S410.

[0246] S410: The physical heating actuator responds to the drive action to perform battery heating and feeds back its own hardware operating parameter information to the execution master controller in the execution control layer in real time, and enters S411.

[0247] S411: The execution control layer monitors the heating process of the physical heating actuator and periodically updates and sends status feedback information to the capability abstraction layer. The status feedback information includes unfiltered raw energy consumption data and function execution status parameters indicating that the function is in execution. Then proceed to S412.

[0248] S412: After receiving the status feedback information, the capability abstraction layer performs smoothing filtering on the original energy consumption data to generate real-time processed energy consumption data, and sends the feedback parameters containing the real-time processed energy consumption data and the function execution status parameters to the interface processing layer, and proceeds to S413.

[0249] S413: When the interface processing layer determines that the temperature maintenance heating task corresponding to the second requester identifier (ID2) has been completed, it provides feedback to the second battery heating function application indicating that the task execution status has been completed; at the same time, it determines that the temperature maintenance heating task corresponding to the first requester identifier (ID1) still needs to be executed, provides feedback to the first battery heating function application indicating that the task execution status is being executed, and maintains the feedback mapping relationship of each requester identifier, and proceeds to S414, S415 and S416.

[0250] S414: The first battery heating function application obtains the task execution status feedback indicating that it is being executed based on the feedback mapping relationship, and proceeds to S417.

[0251] S415: The second battery heating function application obtains the task execution status feedback indicating completion based on the feedback mapping relationship.

[0252] S416: The interface processing layer continues to execute the temperature maintenance heating task corresponding to the first requester identifier (ID1) in the aforementioned execution manner; if there is a difference between the target maintenance temperature of the first requester identifier and the target maintenance temperature of the completed second requester identifier, the interface processing layer readjusts and calls the heating control strategy of the capability abstraction layer.

[0253] S417: When the first battery heating function determines that there is no current temperature maintenance requirement, it sends a temperature maintenance heating request signal to the temperature maintenance heating combination interface of the interface processing layer. The temperature maintenance heating request signal contains the first requester identifier (ID1) and a temperature maintenance request status parameter indicating that there is no request. Then proceed to S418.

[0254] S418: The interface processing layer determines that the temperature maintenance heating tasks corresponding to the first requester identifier have no heating requirements, ends the temperature maintenance heating process, sends a task execution status feedback indicating completion to the first battery heating function application, and sends a control call signal containing 0 levels or no heating request to the abstract interface of the corresponding target heating mode in the capability abstraction layer, and proceeds to S419.

[0255] S419: The capability abstraction layer receives a stop heating control call signal from the interface processing layer, sends execution control parameters containing a 0-level or no heating request to the execution control layer, and proceeds to S420.

[0256] S420: The execution control layer adjusts the operating parameters of the physical heating execution controller to shut down the physical heating action based on the execution control parameters issued by the capability abstraction layer, and then proceeds to S421.

[0257] S421: The physical heating actuator stops heating and sends the hardware operation parameter information in the stopped state to the execution master controller in the execution control layer in real time, and then proceeds to S422.

[0258] S422: The execution control layer monitors the stopping process of the physical heating actuator, updates and sends status feedback information containing the execution status parameters of 0 gear or no function to the capability abstraction layer, and completes the temperature maintenance heating control process.

[0259] Next, the control logic for calling the temperature heating interface will be explained by example.

[0260] Figure 11 The flowchart of the control logic for the temperature-controlled heating interface is shown. Figure 11 As shown, in some other embodiments, the internal control process of the basic combination control-temperature heating interface call control may include the following steps S701-S716.

[0261] S701: The battery heating main controller is woken up and starts running after initialization.

[0262] S702: Basic Combination Control - Temperature Heating Interface Call Control determines whether the Basic Combination Control - Temperature Heating interface has received a call from the functional application layer. If received, proceed to S703; otherwise, proceed to S704.

[0263] S703: Basic combined control - temperature maintenance and heating interface call control. This checks the validity of the interface caller ID in the input parameters and verifies whether the battery temperature maintenance request, target temperature, and cutoff time conform to the preset definitions. If the verification passes, proceed to S705; otherwise, reject the call and proceed to S704.

[0264] S704: Basic combined control - temperature maintenance heating interface call control determines whether there are any unfinished temperature maintenance heating tasks. If so, proceed to S706; otherwise, proceed to S716.

[0265] S705: Basic Combination Control - Temperature Maintenance Heating Interface Call Control: Based on the request status, temperature maintenance target temperature, and deadline sent by the corresponding caller, temperature maintenance heating tasks are created, updated, or cleared in real time.

[0266] S706: Basic combined control - temperature maintenance and heating interface call control traverses all valid temperature maintenance and heating tasks, determines the highest temperature maintenance target temperature and corresponding cutoff time within the current time period.

[0267] When the effective time periods of different temperature maintenance tasks do not completely overlap, the temperature maintenance cycle can be divided into multiple sub-time periods according to the time axis, and the highest effective temperature maintenance target temperature in each sub-time period can be determined.

[0268] S707: Basic combined control - temperature control interface call control to obtain the heating methods supported by the vehicle model in the vehicle configuration word and the executable heating capability information reported by the capability abstraction layer, and determine the currently available candidate heating methods.

[0269] S708: Basic combined control - temperature maintenance and heating interface call control to determine whether the current battery temperature is higher than the highest temperature maintenance target temperature in the current time period. If it is higher, proceed to S709; otherwise, proceed to S711.

[0270] S709: Basic combined control - temperature control and heating interface call to read the mapping relationship between the current ambient temperature, current battery pack temperature and temperature drop rate stored in EEPROM, and combine it with the weather information provided by the cloud to estimate the estimated cooling time required for the battery temperature to naturally drop to the highest temperature target temperature.

[0271] S710: Basic Combined Control - Temperature Control Interface Call Control calculates the future wake-up time based on the current time and estimated cooling duration: Future wake-up time = Current time + Estimated cooling duration. (See reference here.) Figure 14 , Figure 14 The diagram illustrates the algorithm for selecting the heating execution mode by calling the basic combined control-temperature heating interface.

[0272] The basic combination control - temperature control interface calls the control to establish the corresponding wake-up task, and wakes up the whole vehicle when the future wake-up time is reached, and then enters S716.

[0273] In practical applications, a preset control margin can be subtracted from the aforementioned future wake-up time to avoid model errors causing the battery temperature to fall below the target temperature.

[0274] S711: Basic combined control - temperature control interface call control to determine whether battery over-temperature, high voltage overcurrent, low SOC, insulation abnormality, actuator failure, or other safety monitoring restrictions have been triggered. If no restriction is triggered, proceed to S712; if a restriction is triggered, the corresponding task is set to abnormal interruption or temporarily unexecutable, and proceed to S713.

[0275] S712: The basic combined control - temperature maintenance and heating interface call control generates a call request for the target heating method, and the corresponding heating abstract interface in the unified call control capability abstraction layer of each function abstraction requests the execution of heating. The basic combined control - temperature maintenance and heating interface call control can maintain the battery temperature within the preset temperature range corresponding to the target temperature through intermittent start / stop, gear adjustment, or heating mode switching.

[0276] S713: Basic Combination Control - Temperature Maintenance Heating Interface Call Control. Based on the interface caller ID in the Basic Combination Interface - Temperature Maintenance Heating input parameters, the system feeds back the task execution status to the corresponding task party. It reports "Execution in Progress" when heating is normal or during temperature maintenance management; and reports "Abnormal Interruption" when execution cannot continue due to safety restrictions.

[0277] S714: Basic combined control - temperature maintenance heating interface call control to determine whether the temperature maintenance deadline time corresponding to the current highest temperature maintenance target temperature has been reached. If reached, proceed to S715; otherwise, return to S702.

[0278] S715: Basic combined control - Temperature maintenance and heating interface call control clears temperature maintenance tasks that have reached their deadline and sends a completion notification to the corresponding task party based on the interface caller's identity ID. If other valid temperature maintenance tasks still exist, return to S702 and redetermine the highest temperature maintenance target temperature according to the remaining temperature maintenance tasks.

[0279] S716: When continuous operation is not required or a future wake-up task has been established, the current round of control ends and the battery heating main controller enters sleep mode.

[0280] Next, we will provide an exemplary description of the unified call control for each function.

[0281] In some implementations, a unified call control for abstracting various functions is set up in the interface processing layer to monitor and summarize the interface call requests generated by the entire interface processing layer to the capability abstraction layer. For example, the interface call requests can come from the direct control interfaces of various heating methods, such as the basic combination control - timed heating interface call control, the basic combination control - immediate heating interface call control, the basic combination control - temperature maintenance heating interface call control, and other interface processing modules with battery heating requirements.

[0282] The unified call control for each function abstraction can establish request records separately according to the heating method, and generate unique and valid call parameters for each heating abstraction interface within the same control cycle. Figure 12 The flowchart of the unified call control logic for each function is shown, such as... Figure 12 As shown, its control process may include the following steps S801-S804.

[0283] S801: The battery heating main controller is woken up and starts running after initialization.

[0284] S802: The unified call control for each function abstraction determines whether there is a need to call the interface of the capability abstraction layer in the interface processing layer. If so, proceed to S803; otherwise, proceed to S804.

[0285] S803: The unified call control of each function abstracts through all valid requests in the interface processing layer and performs unified arbitration according to the request source, target heating method, request level, task priority, hardware resource usage relationship and security constraints.

[0286] For multiple compatible requests pointing to the same heating mode, the highest valid request level can be used as the final call level for that heating mode; for multiple compatible requests pointing to the same on / off heating mode, as long as at least one request is for heating, the final call status can be determined as for heating.

[0287] For multiple requests that target different heating methods and have conflicts in power, electrical, thermal management loops, or hardware resources, the unified abstraction and control of each function can select one request to execute according to a preset priority strategy, or limit the power of multiple requests. The preset priority can include the priority relationship between low-temperature safety heating requests, charging heating requests, driving heating requests, immediate heating requests, timed heating requests, and temperature maintenance heating requests.

[0288] After completing unified arbitration, the unified call control of each function abstraction calls the corresponding abstract interface in the capability abstraction layer and sends at least one of the following: final request level, heating request, task type, or target temperature.

[0289] S804: This round of unified control has ended. The battery heating main controller enters sleep mode when there is no need for continuous operation.

[0290] By setting up a unified call control for each function abstraction, the direct control interface and each combined managed interface do not directly call the underlying capability abstraction interface in parallel. Instead, the requirements are first aggregated into the unified call control module. This ensures that the same heating method receives only one valid control request after arbitration within the same control cycle, avoiding duplicate calls, mutual overwriting, or control conflicts from multiple upper-level modules.

[0291] Based on the aforementioned direct control interface, combined managed interface, and unified call control mechanism, the functional application layer can select different calling methods according to the complexity of the function.

[0292] For test functions, diagnostic functions, or special vehicle functions that require explicit specification of the underlying heating method, a direct control interface can be used, specifying the request level or heating request. For ordinary vehicle functions that only care about the target temperature, deadline, or whether to heat immediately, the basic combination interface - timed heating, basic combination interface - immediate heating, or basic combination interface - stabilization heating can be used. The interface processing layer automatically completes the following processing: verifying the identity of the interface caller and input parameters; creating, updating, or clearing the corresponding task; reading the vehicle configuration word; obtaining executable heating capability information reported by the capability abstraction layer; obtaining the temperature rise map and temperature drop map stored in the EEPROM; obtaining weather information provided by the cloud; calculating the estimated temperature rise duration, estimated temperature drop duration, and vehicle wake-up time; selecting the target heating method and request level; uniformly arbitrating multiple call requests through unified call control of each function abstraction; calling the capability abstraction layer; monitoring the execution status of the physical heating actuator; and providing feedback to the corresponding functional application on the status of waiting to execute, executing, executing, exiting, or abnormally interrupted based on the interface caller's identity ID.

[0293] Therefore, when adding new application-layer functions, existing direct control interfaces or combined managed interfaces can be reused first, without the need to re-establish point-to-point control links between the new application and each underlying execution controller. When the underlying heating hardware or execution control method changes, only the corresponding capability abstraction module and execution control module need to be adjusted, without modifying the application-layer task logic, thereby achieving layered decoupling between application functions, task management, basic heating capabilities, and physical execution control.

[0294] Next, an exemplary embodiment of the matching based on vehicle configuration words and executable heating capacity information will be described.

[0295] In one scenario, when the interface processing layer receives a managed heating request signal through a combined managed interface, the interface processing layer can obtain the vehicle configuration word and the executable heating capability information reported by the capability abstraction layer, and match the target heating method from multiple candidate heating methods based on the vehicle configuration word and the executable heating capability information.

[0296] In one example, the vehicle configuration word can be 16 bits of unsigned data, and the meaning of each bit is as follows: Table 3. Examples of the meanings of each data bit in the vehicle configuration word.

[0297] The remaining data bits can be reserved or used to represent new heating methods. The above bit definition is only one possible example; in a specific implementation, an enumeration table, vehicle configuration file, or hardware capability list can also be used to represent the vehicle configuration.

[0298] The capability abstraction layer can report the executable heating capability information of each heating method to the interface processing layer according to a preset period. For example: Table 4 Examples of executable heating capacity information

[0299] The interface processing layer can first exclude heating methods that are not configured in the vehicle based on the vehicle configuration information, and then exclude heating methods that are not currently allowed to be executed based on the executable heating capacity information, thus obtaining a set of candidate heating methods.

[0300] The interface processing layer can match the target heating method from the set of candidate heating methods based on a preset heating strategy. The preset heating strategy may include an energy consumption priority strategy, a heating speed priority strategy, a noise priority strategy, a target temperature reachability priority strategy, and a weighted combination of multiple strategies.

[0301] For example, the following condition matrix can be used: When the ambient temperature is greater than or equal to -10℃, the heat pump heating is in a permissible state, and the maximum temperature supported by the heat pump is not lower than the target temperature, the heat pump heating should be selected first. When the maximum temperature supported by the heat pump is lower than the target temperature, select water heating component, or use heat pump heating first and then switch to water heating component; When the vehicle is charging, pulse heating is available and the remaining heating time meets the task requirements, pulse heating can be selected. When the selected heating method fails or the permitted status becomes prohibited, the target heating method is reselected from the remaining candidate heating methods. When no candidate heating method meets the execution conditions, the task status is set to temporarily unexecutable, and the corresponding status is reported back to the application layer.

[0302] In another implementation, a matching score can be calculated for each candidate heating method:

[0303] in, This represents the energy efficiency evaluation value of the i-th heating method. This represents the heating rate evaluation value. This represents the target temperature attainability evaluation value. This represents the usability evaluation value. to This indicates the corresponding weight. The interface processing layer can select the heating method with the highest matching score and in an enabled state as the target heating method.

[0304] For example, in energy-priority mode, it can be Set to 0.4, Set to 0.2, Set to 0.25, Set to 0.15; in rapid heating mode, you can... Set to 0.2, Set to 0.5, Set to 0.2, Set to 0.1. The above weight values ​​are for illustrative purposes only and can be adjusted through vehicle calibration.

[0305] After determining the target heating method, the interface processing layer sends a control call signal to the target heating abstract interface corresponding to the target heating method in the capability abstraction layer. For example, when the target heating method is heat pump heating, the control call signal is sent to the heat pump heating abstract interface; when the target heating method is water heating of the heating component, the control call signal is sent to the water heating of the heating component abstract interface.

[0306] Next, exemplary embodiments of timed heating, immediate heating, and temperature-maintaining heating will be described.

[0307] In some implementations, the managed heating request signal may include at least one of a timed heating request, an immediate heating request, and a temperature-maintaining heating request.

[0308] For example, in response to receiving a timed heating request, the interface processing layer extracts the target temperature and deadline contained in the timed heating request, selects the target heating abstract interface corresponding to the matching heating method, and sends a control call signal to execute closed-loop control.

[0309] For example, a user sets the vehicle to heat the battery to 15°C before 07:30 the next day. The interface processing layer obtains the current battery temperature as -10°C and determines the expected heating duration based on the expected temperature rise rate of the candidate heating methods.

[0310] If the expected heating rate of the target heating method is 0.5℃ per minute, then the theoretical heating time is:

[0311] The interface processing layer can add a 10-minute buffer to the theoretical heating time, setting the task start time to 06:30. Once the task start time is reached, the interface processing layer sends a control call signal to the target heating abstract interface.

[0312] During the heating process, the interface processing layer or capability abstraction layer can adjust the heating level based on the difference between the real-time battery temperature and the target temperature. For example, when the temperature difference is greater than 10°C, level 5 is requested; when the temperature difference is greater than 5°C but less than or equal to 10°C, level 3 is requested; and when the temperature difference is less than or equal to 5°C, level 1 is requested. The timed heating task ends when the battery temperature reaches 15°C or when 07:30 is reached.

[0313] The heating rate, reserve time, and gear divisions mentioned above are just examples. Actual parameters can be calibrated based on battery thermal capacity, ambient temperature, heating power, and heat loss.

[0314] For example, in response to receiving an immediate heating request, the interface processing layer extracts the heating instructions contained in the immediate heating request, selects the target heating abstract interface corresponding to the matching heating method according to the preset heating strategy, and sends a control call signal to perform immediate heating.

[0315] For example, when a user selects "Preheat Now" on the vehicle terminal, the application layer sends an immediate heating request to the interface processing layer. The interface processing layer selects the target heating method based on the vehicle configuration, the currently available heating capacity, and the vehicle's power margin.

[0316] If the current vehicle is equipped with both heat pump heating and water-cooled heating components, and the heat pump supports a maximum temperature higher than the target temperature, then the heat pump heating with lower energy consumption can be selected first; if the battery temperature is lower than the effective operating temperature limit of the heat pump, then the water-cooled heating components can be selected, or the water-cooled heating components can be used to raise the battery temperature to the effective operating range of the heat pump before switching to heat pump heating.

[0317] For example, in response to receiving a temperature maintenance heating request, the interface processing layer extracts the target maintenance temperature and maintenance time contained in the temperature maintenance heating request, selects the target heating abstract interface corresponding to the matching heating method, and sends a control call signal to perform temperature maintenance control.

[0318] For example, the target maintenance temperature is 10°C, and the maintenance time is 8:00. The temperature control hysteresis can be set to 2°C: heating is started when the battery temperature is less than or equal to 9°C, and heating is stopped when the battery temperature is greater than or equal to 11°C. This temperature hysteresis reduces the frequency of starting and stopping the physical heating actuator.

[0319] In other implementations, temperature control can be performed using proportional-integral control, fuzzy control, model predictive control, or other closed-loop temperature control methods.

[0320] Next, an exemplary embodiment of the operational availability assessment of the capability abstraction layer will be described.

[0321] In some implementations, determining the execution control parameters for the corresponding heating mode may include: the capability abstraction layer obtaining the current vehicle's operating condition parameters; combining the operating condition parameters to perform an availability assessment on the control call signal, determining the current heating mode's availability status and the maximum gear threshold allowed for call, and generating execution control parameters based on the maximum gear threshold.

[0322] Optionally, vehicle operating parameters may include at least one of the following: battery temperature, battery state of charge (SOC), battery allowable discharge power, battery allowable charging power, high-voltage bus voltage, motor temperature, electric drive inverter temperature, coolant temperature, ambient temperature, vehicle operating status, charging status, collision status, and insulation status.

[0323] Taking pulse heating as an example, the capability abstraction layer can determine the permissible state of pulse heating based on the following conditions: the battery SOC is greater than or equal to 20%; the high-voltage system is powered on; the battery temperature is below 10°C; there is no insulation fault in the battery system; there is no over-temperature or over-current fault in the pulse heating device; and the remaining heating time is greater than the preset minimum time, for example, greater than 5 minutes.

[0324] When all the above conditions are met, the permissible state of pulse heating can be set to allowed; if any safety-related condition is not met, the permissible state can be set to prohibited.

[0325] Taking the determination of heating levels as an example, five heating levels can be set, and the maximum level can be determined according to the battery's allowable power: Table 5 Example of Heating Level Determination

[0326] As shown in Table 5, when the interface processing layer requests level 5 and the capability abstraction layer determines that the maximum allowed level is level 3, the capability abstraction layer can restrict the execution control parameters to level 3 instead of sending the level 5 request directly to the execution control layer.

[0327] In one implementation, the capability abstraction layer can determine the actual gear position as follows:

[0328] in, For the actual gear position issued, For the interface processing layer request block, The maximum permissible gear is determined based on the vehicle's operating conditions. The maximum available hardware gear for executing control layer feedback.

[0329] The SOC threshold, temperature threshold, power threshold, and number of settings mentioned above are just examples. Specific thresholds can be calibrated based on the battery type and heating hardware capabilities, and stored in the controller's non-volatile memory.

[0330] Next, an exemplary embodiment of the raw energy consumption data filtering method will be described.

[0331] In some embodiments, the status feedback information includes unfiltered raw energy consumption data. It should be understood that the raw energy consumption data may be the instantaneous power calculated by the execution control layer based on the real-time voltage and real-time current of the physical heating actuator, or it may be the energy consumption value accumulated over a preset period.

[0332] After receiving the status feedback information, the capability abstraction layer performs smoothing filtering on the raw energy consumption data to generate real-time processed energy consumption data, and sends the feedback parameters containing the real-time processed energy consumption data to the interface processing layer.

[0333] In one implementation, a first-order low-pass filtering algorithm can be used:

[0334] in, This represents the real-time energy consumption data after processing in the k-th cycle. This represents the raw energy consumption data for the k-th cycle. This represents the energy consumption data after real-time processing in the previous cycle. These are the filter coefficients.

[0335] For example, the state feedback period is 100 milliseconds, and the filter coefficient... It can be set to 0.2. When the original power of this cycle is 5.5kW and the power after processing in the previous cycle is 5.0kW, the power after processing in this cycle is:

[0336] In another implementation, a moving average filter can be used, selecting the raw energy consumption data from the most recent 5 or 10 sampling periods to calculate the average value. The filtering algorithm, filtering window, and filtering coefficients can be set according to the response speed of different heating methods.

[0337] Feedback parameters sent from the capability abstraction layer to the interface processing layer may include real-time processed energy consumption, availability status, maximum allowable setting, function execution status, fault status, and current heating mode identifier. The interface processing layer may further send at least some of these feedback parameters to the application layer for interface display, task management, or energy management.

[0338] Next, various heating methods and their capabilities will be illustrated by abstract embodiments.

[0339] In some implementations, the capability abstraction layer may include at least one of the following heating abstraction interfaces, each corresponding to a different heating method: variable frequency film heating abstraction interface, non-variable frequency film heating abstraction interface, pulse heating abstraction interface, stalled rotor heating abstraction interface, degraded efficiency heating abstraction interface, heating component hydrothermal abstraction interface, waste heat recovery heating abstraction interface, or heat pump heating abstraction interface.

[0340] It should be understood that variable frequency film heating refers to a heating method that changes the heating power by adjusting the operating frequency, voltage, current, duty cycle, or power level of the heating film. Non-variable frequency film heating refers to a heating method where the primary control method is on / off operation, or that does not support continuous power adjustment. Pulse heating refers to a heating method that generates heat inside the battery by applying alternating current, pulse current, or other periodic electrical excitation. Stall-rotor heating refers to a heating method where, under vehicle safety conditions, the motor is controlled to be in a controlled state where it generates little or no driving torque, and heat is generated through the current loss of the motor and electric drive system. Degraded efficiency heating refers to adjusting the operating parameters of the electric drive system or other power conversion system to generate heat that can be used to heat the battery by reducing energy conversion efficiency. Hydrothermal heating components can be PTC hydrothermal heating, which refers to a heating method that uses heating components to heat the coolant and transfers the heat to the power battery through the coolant circulation loop. Waste heat recovery heating refers to a heating method that recovers waste heat generated by the motor, electric drive inverter, engine, range extender, or other heat-generating components of the vehicle and transfers the waste heat to the power battery. Heat pump heating refers to a heating method that absorbs heat from the environment or vehicle components through a compressor, heat exchanger, expansion device, and refrigerant circulation loop, and transfers the heat to the power battery.

[0341] Each heating abstraction interface can shield the underlying control details of the corresponding execution control layer and provide a unified or similar data format to the interface processing layer. When a new heating method is added to the vehicle, an abstraction interface corresponding to that heating method can be added to the capability abstraction layer, without requiring the application layer to directly adapt to the execution controller of that heating method.

[0342] Next, an exemplary embodiment of the fixed execution interaction interface will be described.

[0343] In some implementations, data transmission between the capability abstraction layer and the execution control layer can be achieved through a fixed execution interaction interface. The input parameters of the execution interaction interface may include heating level request parameters or heating control request parameters; the output parameters of the execution interaction interface may include at least one of the following: real-time raw energy consumption parameters, function availability status parameters, maximum allowable heating level parameters, function execution status parameters, remaining heating time parameters, and maximum supported temperature parameters.

[0344] In one example, the interactive interface can be implemented using the following general data structure: Table 6 Examples of Input Parameters

[0345] Table 7 Examples of Output Parameters

[0346] The above parameters can be selected according to the specific heating method; not every heating method needs to include all parameters.

[0347] As a specific example, for variable frequency membrane heating, the input parameters for executing the interactive interface may include heating level request parameters, and the output parameters may include real-time raw energy consumption, maximum allowable operating level, and function execution status.

[0348] For non-frequency conversion film heating, the input parameters of the interactive interface can include heating control request parameters, and the output parameters can include real-time raw energy consumption, function availability status, and function execution status.

[0349] For pulse heating, stall heating, or reduced-efficiency heating, the input parameters for the interactive interface can include heating level request parameters, and the output parameters can include real-time raw energy consumption, maximum allowable heating level, function execution status, and remaining heating time.

[0350] For hydrothermal heating components, the input parameters for the interactive interface can include heating level request parameters, and the output parameters can include real-time raw energy consumption, maximum allowed operating level, and function execution status.

[0351] For waste heat recovery heating or heat pump heating, the input parameters for the interactive interface can include heating level request parameters, and the output parameters can include real-time raw energy consumption, maximum allowable operating level, function execution status, and maximum supported temperature.

[0352] In this example, the capability abstraction layer can convert the underlying states fed back by different execution control layers into a unified state enumeration value. For example, the "Running", "Active" or the value 2 used by different execution master controllers can be uniformly converted into the "Executing" state, so that the interface processing layer does not need to recognize the underlying state definitions of different hardware.

[0353] The following is an exemplary description of the communication monitoring and security fallback implementation.

[0354] In some embodiments, a periodic communication heartbeat monitoring mechanism is established between the capability abstraction layer and the execution control layer.

[0355] The execution control layer can send heartbeat data to the capability abstraction layer according to a preset period. The heartbeat data can be transmitted independently of the status feedback information, or it can be transmitted as a cycle count value, timestamp, or active status bit in the status feedback information.

[0356] For example, the execution control layer can send status feedback information every 100 milliseconds, with a count value that increments cyclically from 0 to 255 in the feedback information. If the capability abstraction layer does not receive new status feedback information within 5 consecutive feedback cycles, or if the received cyclic count value remains unchanged for 5 consecutive cycles, it can determine that a communication timeout has occurred. Therefore, the corresponding communication timeout threshold is 500 milliseconds.

[0357] In other implementations, the feedback period can be from 20 milliseconds to 500 milliseconds, and the communication timeout threshold can be set to 2 to 10 times the feedback period. Specific values ​​can be calibrated based on the communication network load and the safety requirements of the heating hardware.

[0358] The capability abstraction layer can also determine whether the physical heating actuator is malfunctioning based on status feedback information. These malfunctions may include: a function execution status indication failure; actual heating power exceeding the allowable power; actual heating level exceeding the maximum allowable level; over-temperature, over-current, or insulation faults reported by the execution control layer; a stop request being issued by the capability abstraction layer, but the execution status continues to indicate execution; and the deviation between the requested power and the actual power continuously exceeding a preset threshold.

[0359] For example, if the requested power is 5kW, but the actual power exceeds 6.5kW for one second consecutively, a power anomaly can be identified; if more than 500 milliseconds pass after the capability abstraction layer issues a stop request, and the execution control layer still reports an "in execution" status, a stop response anomaly can be identified. The aforementioned thresholds and durations can be calibrated based on the characteristics of the heating hardware.

[0360] If the capability abstraction layer detects a communication timeout or an abnormal status feedback, it sends an interrupt command to the execution control layer to terminate the battery heating operation of the physical heating actuator.

[0361] For example, the interrupt command may include: setting the heating request status to off; setting the request level to 0; setting the request power to 0; issuing an execution controller reset request; disconnecting the relay or contactor corresponding to the heating actuator; and requesting the high-voltage control module to disconnect the corresponding power supply branch.

[0362] Optionally, while the execution control layer maintains communication, the capability abstraction layer can continuously send multiple interrupt commands and wait for the execution control layer to report a stop status. If communication is interrupted, the corresponding physical heating actuator can be shut down via a separate hardwired connection, another communication link, or a high-voltage power distribution control module. The capability abstraction layer can also report the fault status to the interface processing layer, which will then suspend the corresponding heating task and prevent the re-invocation of the faulty heating mode.

[0363] For example, when a heat pump heating communication times out, the capability abstraction layer can set the allowed state of the heat pump heating abstraction interface to disabled and notify the interface processing layer to rematch the target heating method. If the water heating component is still allowed, the interface processing layer can switch the current heating task to the water heating component; if there are no other executable heating methods, the current heating task is terminated and the application layer is notified of the task's abnormal status.

[0364] To make the battery heating control method provided in this application embodiment clearer, a detailed description of the complete control process will be given below.

[0365] Specifically, the following uses the example of a vehicle performing a timed heating task to illustrate the complete control process of this application.

[0366] The vehicle configuration word is a binary value of 10000001, where Bit[0] and Bit[7] are 1, indicating that the vehicle is equipped with variable frequency film heating and heat pump heating. The user sets the power battery temperature to 15℃ before 07:30 through the application layer settings.

[0367] After receiving the timed heating request, the interface processing layer performs compliance checks on the target temperature and the deadline. The target temperature of 15℃ is within the preset allowable range of -10℃ to 40℃, and the deadline is later than the current time; therefore, the check passes.

[0368] The interface processing layer obtains the executable heating capability information reported by the capability abstraction layer. Currently, the heat pump heating is permitted with a maximum setting of 4 and a maximum supported temperature of 20℃; the inverter film heating is permitted with a maximum setting of 5. Since the target temperature of 15℃ does not exceed the maximum supported temperature of the heat pump, and the current ambient temperature meets the heat pump's operating conditions, the interface processing layer selects heat pump heating as the target heating method based on an energy consumption priority strategy.

[0369] The interface processing layer sends a control call signal to the heat pump heating abstract interface, including the target temperature of 15°C and the heating request status. The heat pump heating abstract interface obtains the current battery temperature, ambient temperature, battery SOC, and the vehicle's allowable heating power, and determines that the heat pump heating is in an enabled state, with a maximum allowable level of 4.

[0370] If the interface processing layer requests level 5, the heat pump heating abstract interface will limit the actual execution level to level 4 and send the level 4 request to the heat pump execution master controller through the fixed execution interaction interface. The heat pump execution master controller controls the operation of the compressor, electronic expansion valve, and circulation pump, and periodically provides feedback on real-time raw energy consumption, maximum allowable operating level, function execution status, and maximum supported temperature.

[0371] The capability abstraction layer uses a first-order low-pass filtering algorithm to process the real-time raw energy consumption and sends the processed energy consumption data and availability status to the interface processing layer. When the battery temperature reaches 15°C, the interface processing layer issues a stop control call signal, and the capability abstraction layer further sends a 0-level request to the heat pump execution master controller.

[0372] If the status feedback information of the heat pump execution master controller is not updated for 500 consecutive milliseconds during the heating process, the capability abstraction layer determines that the communication has timed out, sends an interrupt command to the heat pump execution master controller, and sets the heat pump heating enabled status to disabled. The interface processing layer selects variable frequency film heating to continue executing the task based on the updated executable heating capability information, or terminates the task and reports the abnormal status to the application layer if no other available heating method exists.

[0373] Figure 15 This application illustrates another battery heating control system provided by an embodiment of the present application. For example... Figure 15 As shown in the figure, this application embodiment also provides a battery heating control system 700, including an interface processing module 701, a capability abstraction module 702, and an execution control module 703.

[0374] For example, the interface processing module 701 is used to receive a battery heating request signal from the application layer and output a control call signal according to the battery heating request signal.

[0375] In one specific implementation, the interface processing module 701 may include a verification and arbitration unit and a combined hosting unit. The verification and arbitration unit is used to perform compliance verification and priority arbitration on the battery heating request signal. The combined hosting unit is used to receive the hosted heating request signal through a preset hosting interface and match the target heating method by combining the vehicle configuration word and the capability information reported by the capability abstraction module 702.

[0376] The interface processing module 701 may further include a direct control unit, a request identity management unit, a task status management unit, and an interface routing unit. The direct control unit is used to receive preset heating mode call signals; the request identity management unit is used to identify the requester and determine whether the requester has interface call permissions; the task status management unit is used to maintain the status of timed heating tasks, immediate heating tasks, and temperature maintenance heating tasks; and the interface routing unit is used to send control call signals to the target heating abstract interface corresponding to the target heating mode.

[0377] The capability abstraction module 702 is used to determine the execution control parameters of the corresponding heating mode based on the control call signal, and to preprocess the received status feedback information.

[0378] In some implementations, the capability abstraction module 702 may include a condition assessment unit and a signal filtering unit. The condition assessment unit is used to determine the permissible heating state and the maximum permissible gear based on the vehicle's current operating parameters; the signal filtering unit is used to perform smoothing filtering on the raw energy consumption data in the state feedback information.

[0379] The capability abstraction module 702 may also include multiple heating abstraction units, a communication diagnostic unit, and a safety protection unit. The multiple heating abstraction units correspond to different heating methods; the communication diagnostic unit monitors the communication status between the capability abstraction module and the execution control module; and the safety protection unit outputs an interrupt command when communication times out or when the status feedback information indicates an abnormality.

[0380] The execution control module 703 is connected to the capability abstraction module 702 through the execution interaction interface. It is used to drive the physical heating actuator based on the execution control parameters and transmit the status feedback information of the physical heating actuator to the capability abstraction module 702 via the execution interaction interface.

[0381] The execution control module 703 may include one or more execution master controllers. Each execution master controller may control one type of physical heating actuator, or one execution master controller may control multiple physical heating actuators.

[0382] The interface processing module 701, capability abstraction module 702, and execution control module 703 can be deployed in the same controller or distributed across different controllers. For example, the interface processing module 701 and capability abstraction module 702 can be deployed in the thermal management domain controller, and the execution control module 703 can be deployed in the heat pump controller, electric drive controller, and heating component controller, respectively. The deployment method of each module does not constitute a limitation on the scope of protection of this application.

[0383] This application also provides a vehicle, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the processor executes the computer program, it implements the battery heating control method described in any of the foregoing embodiments.

[0384] The memory may include read-only memory, random access memory, non-volatile memory, flash memory, or other storage devices capable of storing computer programs and calibration parameters. The processor may include a central processing unit, a microcontroller, a digital signal processor, a system-on-a-chip, or other processing devices with data processing and control functions.

[0385] The vehicle may also include a power battery, temperature sensors, a heating device, a vehicle communication bus, and at least one electronic control unit. The processor communicates with at least one electronic control unit via the vehicle communication bus and controls the heating device to heat the power battery through the execution control layer.

[0386] This application also provides a computer-readable storage medium storing computer instructions, which, when executed by a processor, implement the battery heating control method described in any of the foregoing embodiments.

[0387] The computer-readable storage medium may include magnetic storage media, optical storage media, semiconductor storage media, or other non-transitory storage media. The computer instructions may be divided into multiple program modules for implementing the interface processing layer, capability abstraction layer, and execution control layer, or may be implemented by a single program.

[0388] It should be understood that the application of this application is not limited to the examples above. Those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims. Those skilled in the art can understand that implementing all or part of the processes of the above embodiments and making equivalent changes according to the claims of this application still fall within the scope of this application.

Claims

1. A battery heating control method, characterized in that, include: The interface processing layer receives a battery heating request signal from the application layer; The interface processing layer determines the target heating method based on the battery heating request signal, and sends a control call signal to the heating abstract interface in the capability abstraction layer that corresponds to the target heating method. The capability abstraction layer determines the execution control parameters corresponding to the target heating method based on the control call signal and the execution interaction interface, and sends the execution control parameters to the execution control layer. The execution control layer drives the physical heating actuator based on the execution control parameters.

2. The battery heating control method according to claim 1, characterized in that, The interface processing layer determines the target heating method based on the battery heating request signal, and sends a control call signal to the heating abstract interface corresponding to the target heating method in the capability abstraction layer, including: The interface processing layer performs input parameter compliance verification on the received battery heating request signal; If the input parameter compliance verification passes, the interface processing layer arbitrates multiple concurrent battery heating request signals according to a preset priority strategy to generate the control call signal.

3. The battery heating control method according to claim 1, characterized in that, The interface processing layer receives a battery heating request signal from the application layer, including: The interface processing layer receives preset heating mode call signals from the application layer via a direct control interface; and / or The interface processing layer receives managed heating request signals from the application layer through a combined managed interface.

4. The battery heating control method according to claim 3, characterized in that, When the interface processing layer receives a managed heating request signal from the application layer through the combined managed interface, the step of sending a control call signal to the heating abstract interface corresponding to the target heating method in the capability abstraction layer includes: The interface processing layer obtains the vehicle configuration word and the executable heating capability information reported by the capability abstraction layer; Based on the vehicle configuration information and the executable heating capacity information, a target heating method is matched from multiple candidate heating methods; The control call signal is sent to the target heating abstract interface in the capability abstraction layer that corresponds to the target heating method.

5. The battery heating control method according to claim 4, characterized in that, The managed heating request signal includes at least one of timed heating request, immediate heating request, and temperature-maintaining heating request. Sending the control call signal to the target heating abstract interface corresponding to the target heating method in the capability abstraction layer includes: In response to receiving a timed heating request, the target temperature and cutoff time contained in the timed heating request are extracted, and the control call signal is sent to the target heating abstract interface corresponding to the matching heating method to execute closed-loop control. In response to receiving an immediate heating request, the heating instruction contained in the immediate heating request is extracted, and the target heating abstract interface corresponding to the matching heating method is selected according to the preset heating strategy to send the control call signal to perform immediate heating; In response to receiving a temperature maintenance heating request, the system extracts the target maintenance temperature and maintenance time contained in the temperature maintenance heating request, selects the target heating abstract interface corresponding to the matching heating method, and sends the control call signal to perform temperature maintenance control.

6. The battery heating control method according to any one of claims 1-5, characterized in that, The determination of the execution control parameters corresponding to the target heating method includes: The capability abstraction layer obtains the current vehicle's operating parameters; The availability of the control call signal is evaluated based on the operating condition parameters to determine the availability status of the current heating mode and the maximum gear threshold that can be called, and the execution control parameters are generated based on the maximum gear threshold.

7. The battery heating control method according to any one of claims 1-5, characterized in that, The status feedback information includes unfiltered raw energy consumption data; the method further includes: After receiving the status feedback information, the capability abstraction layer performs smoothing filtering on the original energy consumption data to generate real-time processed energy consumption data. The capability abstraction layer sends feedback parameters containing the real-time processed energy consumption data to the interface processing layer.

8. The battery heating control method according to any one of claims 1-5, characterized in that, The heating method includes at least one of the following: frequency conversion film heating, non-frequency conversion film heating, pulse heating, stall heating, degraded heating, hydrothermal heating of heating components, waste heat recovery heating, and heat pump heating.

9. The battery heating control method according to any one of claims 1-5, characterized in that, The capability abstraction layer and the execution control layer exchange data through an execution interaction interface; The input parameters of the execution interaction interface include heating level request parameters or heating control request parameters; the output parameters of the execution interaction interface include at least one of the following: real-time raw energy consumption parameters, function availability status parameters, maximum allowable level parameters, function execution status parameters, remaining heating time parameters, and maximum supported temperature parameters.

10. The battery heating control method according to claim 1, characterized in that, The method further includes: A periodic communication heartbeat monitoring mechanism is established between the capability abstraction layer and the execution control layer; If the capability abstraction layer detects a communication timeout or the status feedback information indicates an abnormality, the capability abstraction layer sends an interrupt command to the execution control layer to terminate the battery heating operation of the physical heating actuator.

11. A battery heating control system, characterized in that, include: The interface processing module is used to receive a battery heating request signal from the application layer and output a control call signal according to the battery heating request signal; The capability abstraction module is used to determine the execution control parameters of the corresponding heating mode based on the control call signal, and to preprocess the received status feedback information; The execution control module is connected to the capability abstraction module through an execution interaction interface. It is used to drive the physical heating actuator based on the execution control parameters and transmit the status feedback information of the physical heating actuator to the capability abstraction module via the execution interaction interface.

12. The battery heating control system according to claim 11, characterized in that, The interface processing module includes: The verification and arbitration unit is used to perform compliance verification and priority arbitration on the battery heating request signal; The combined hosting unit is used to receive a hosted heating request signal through a preset hosting interface, and match the target heating method by combining the vehicle configuration word with the capability information reported by the capability abstraction module.

13. The battery heating control system according to claim 11, characterized in that, The capability abstraction module includes: The operating condition assessment unit is used to determine the permissible heating status and the maximum permissible gear by combining the current operating condition parameters of the vehicle. The signal filtering unit is used to perform smoothing filtering on the raw energy consumption data in the status feedback information.

14. A vehicle, characterized in that, The device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the battery heating control method according to any one of claims 1-10.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the battery heating control method according to any one of claims 1-10.

Images