Thermal management layered architecture system, control method, vehicle and storage medium

Abstract

The invention relates to the technical field of thermal management, and discloses a thermal management layered architecture system, a control method, a vehicle and a storage medium, the system comprises a demand definition layer used for obtaining function demand information corresponding to various demands and analyzing the function demand information into corresponding scene description data; the scene management layer is used for generating corresponding use scenes based on the scene description data of various requirements; the control decomposition layer is used for setting a plurality of refrigerant modes for a refrigerant loop of the thermal management system, setting a plurality of cooling liquid modes for a cooling liquid loop of the thermal management system, and determining a corresponding relation among the refrigerant modes, the cooling liquid modes and the use scene models; and the control execution layer is used for configuring a refrigerant control strategy for controlling the refrigerant actuator to work for each refrigerant mode and configuring a cooling liquid control strategy for controlling the cooling liquid actuator to work for each cooling liquid mode. Decoupling is carried out layer by layer, the control strategy of the actuator is simplified, and the management and maintenance difficulty can be reduced.

Description

Technical Field

[0001] The present invention relates to the field of thermal management technology, and in particular to a thermal management layered architecture system, a control method, a vehicle, and a storage medium. Background Art

[0002] With the continuous development of new energy vehicles, vehicle manufacturers have increasingly higher requirements for vehicle energy consumption and comfort. As an important contributor to the above performance, the thermal management system has an increasing demand for the segmentation of usage scenarios and in-depth refinement of control logic.

[0003] In practice, it will be subdivided into multiple usage scenarios, which requires configuring control strategies for each actuator of the thermal management system (such as fans, compressors, etc.) in each usage scenario. The control strategy of the actuator is relatively complex, which will increase management and maintenance costs and is difficult to apply to a large number of usage scenarios. Summary of the Invention

[0004] In view of this, the present invention provides a thermal management layered architecture system, a control method, a vehicle, and a storage medium to solve the problem of complex control strategies for thermal management actuators.

[0005] In a first aspect, the present invention provides a thermal management layered architecture system, comprising:

[0006] The requirement definition layer is used to obtain functional requirement information corresponding to various requirements and parse the functional requirement information into corresponding scenario description data;

[0007] A scenario management layer, configured to generate corresponding usage scenarios based on the scenario description data of various requirements;

[0008] A control decomposition layer is used to set multiple refrigerant modes for the refrigerant circuit of the thermal management system, set multiple coolant modes for the coolant circuit of the thermal management system, and determine the correspondence between the refrigerant modes, the coolant modes, and the usage scenario models; any of the refrigerant modes and / or the coolant modes corresponds to one or more of the usage scenarios;

[0009] The control execution layer is used to configure a refrigerant control strategy for controlling the operation of the refrigerant actuator for each of the refrigerant modes, and to configure a coolant control strategy for controlling the operation of the coolant actuator for each of the coolant modes.

[0010] In some optional implementations, the scenario description data includes a status indicator corresponding to the demand;

[0011] The scenario management layer generates corresponding usage scenarios based on the scenario description data of various requirements, including:

[0012] The status indicators of the multiple requirements are combined to generate corresponding usage scenarios.

[0013] In some optional implementations, the usage scenario corresponds to a unique scenario code; the scenario code includes multiple sub-codes corresponding to the multiple requirements, and the value of each sub-code corresponds to the target state indicator of the corresponding requirement.

[0014] In some optional embodiments, the system further comprises:

[0015] A timing management layer, configured to configure a timing control strategy for the usage scenario according to the timing constraints when the usage scenario has timing constraints; the timing control strategy includes scheduling moments corresponding to multiple control logics;

[0016] Wherein, when there are timing constraints in the usage scenario, the control execution layer configures the refrigerant control strategy corresponding to the corresponding refrigerant mode and the coolant control mode corresponding to the corresponding coolant mode according to the timing control strategy of the usage scenario.

[0017] In some optional implementations, the process of configuring the refrigerant control strategy and the coolant control strategy at the control execution layer includes:

[0018] Determine the status flag corresponding to each scheduling moment according to the timing control strategy of the usage scenario, where different status flags correspond to different control logics;

[0019] The refrigerant control strategy corresponding to the corresponding refrigerant mode is configured with a refrigerant control logic corresponding to each of the status flags, and the coolant control strategy corresponding to the corresponding coolant mode is configured with a coolant control logic corresponding to each of the status flags.

[0020] In some optional embodiments, the control decomposition layer is further used to: integrate usage scenarios in which the same control logic is executed on at least some refrigerant actuators into corresponding refrigerant modes; integrate usage scenarios in which the same control logic is executed on at least some coolant actuators into corresponding coolant modes;

[0021] The control execution layer is also used for:

[0022] In the multiple usage scenarios corresponding to the refrigerant mode, if there are different refrigerant actuators that execute different control logics in different usage scenarios, the execution logics in different usage scenarios are respectively set for the different refrigerant actuators;

[0023] In the multiple usage scenarios corresponding to the coolant mode, if there are different coolant actuators that execute different control logics in different usage scenarios, the execution logics in different usage scenarios are set for the different coolant actuators respectively.

[0024] In a second aspect, the present invention provides a control method for a thermal management system, which is implemented based on a thermal management layered architecture system according to the first aspect or any corresponding embodiment thereof, and the method comprises:

[0025] Determine target function requirement information corresponding to the multiple requirements at the current moment based on the requirement definition layer, and parse the target function requirement information into corresponding target scenario description data;

[0026] Determining target usage scenarios corresponding to the target scenario description data of multiple requirements based on the scenario management layer;

[0027] Determining, based on the control decomposition layer, a target refrigerant mode corresponding to the target usage scenario among a plurality of refrigerant modes corresponding to the refrigerant circuit of the thermal management system, and determining a target coolant mode corresponding to the target usage scenario among a plurality of coolant modes corresponding to the coolant circuit of the thermal management system; the refrigerant mode corresponds to one or more of the usage scenarios, and the coolant mode corresponds to one or more of the usage scenarios;

[0028] Based on the control execution layer, the target refrigerant control strategy corresponding to the target refrigerant mode is determined, and the target coolant control strategy corresponding to the target coolant mode is determined; the corresponding refrigerant actuator is controlled to work according to the target refrigerant control strategy, and the corresponding coolant actuator is controlled to work according to the target coolant control strategy.

[0029] In some optional embodiments, the method further comprises:

[0030] Determining whether the target usage scenario is a usage scenario with timing constraints;

[0031] In a case where the target usage scenario is a usage scenario with timing constraints, the target refrigerant control strategy and / or the target coolant control strategy are updated in time periods according to a timing control strategy pre-configured for the target usage scenario.

[0032] In some optional embodiments, determining the target refrigerant control strategy corresponding to the target refrigerant mode and determining the target coolant control strategy corresponding to the target coolant mode include:

[0033] If a target refrigerant actuator exists among the multiple refrigerant actuators controlled under the target refrigerant mode, determine the control logic of the target refrigerant actuator according to the target usage scenario, and update the control logic of the target refrigerant actuator in the target refrigerant control strategy; the target refrigerant actuator is a refrigerant actuator that executes different control logics in different usage scenarios among the multiple usage scenarios corresponding to the target refrigerant mode;

[0034] If a target coolant actuator exists among the multiple coolant actuators controlled under the target coolant mode, the control logic of the target coolant actuator is determined according to the target usage scenario, and the control logic for the target coolant actuator in the target coolant control strategy is updated; the target coolant actuator is a coolant actuator that executes different control logics in different usage scenarios among the multiple usage scenarios corresponding to the target coolant mode.

[0035] In a third aspect, the present invention provides a vehicle comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the control method of the thermal management system of the second aspect or any corresponding embodiment thereof by executing the computer instructions.

[0036] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the control method for a thermal management system according to the second aspect or any corresponding embodiment thereof.

[0037] In a fifth aspect, the present invention provides a computer program product comprising computer instructions for causing a computer to execute the control method for a thermal management system according to the second aspect or any corresponding embodiment thereof.

[0038] The present invention integrates the refrigerant circuit and coolant circuit of the thermal management system for multiple pre-configured usage scenarios, respectively, and integrates them into multiple refrigerant modes and multiple coolant modes. Since the number of modes is less than the number of usage scenarios, it is only necessary to configure the control strategy under the corresponding mode for each actuator, and there is no need to list all the usage scenarios, which greatly simplifies the control strategy of the actuator; this hierarchical architecture can give each level a substantial control range, decouple layer by layer, reduce the difficulty of management and maintenance, and facilitate the realization of a platform-based universal architecture across systems and vehicle models. During subsequent use, the target usage scenario at the current moment can be determined, and the corresponding refrigerant mode and coolant mode can be determined, and then how to control each actuator can be determined. The usage scenario and the control strategy are decoupled layer by layer, and the refrigerant actuator and the coolant actuator can be collaboratively controlled to ensure that the control strategy can meet the requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in related technologies, the following briefly introduces the drawings required for use in the specific embodiments or related technical descriptions. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0040] Figure 1 is a schematic diagram of a thermal management layered architecture system according to an embodiment of the present invention;

[0041] Figure 2 is a flow chart of a control method for a thermal management system according to an embodiment of the present invention;

[0042] Figure 3 is a schematic diagram of a process for configuring control logic according to an embodiment of the present invention;

[0043] Figure 4 is a flow chart of another control method of a thermal management system according to an embodiment of the present invention;

[0044] Figure 5 is a schematic diagram of a data structure of a scene code according to an embodiment of the present invention;

[0045] Figure 6 4 is a schematic diagram of the hardware structure of a vehicle according to an embodiment of the present invention. DETAILED DESCRIPTION

[0046] To make the purpose, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of the present invention.

[0047] Thermal management systems are crucial in new energy vehicles, responsible for controlling battery temperature, in-vehicle air conditioning, and motor cooling, directly impacting energy consumption and comfort. As demands for energy efficiency and comfort increase, the use of thermal management systems is expanding, requiring more sophisticated control logic.

[0048] At present, the logical architecture of thermal management systems mainly has the following two directions:

[0049] Direction 1: decouple the scenario definition classification from the actuator control classification, and design the middle layer logic to achieve the matching of the scenario and actuator control strategy.

[0050] Direction 2: Define scenarios based on actuator control and decouple actuators.

[0051] For the first direction mentioned above, it is necessary to define each scenario in an indiscriminate list format. As the number of scenarios increases and becomes more detailed, the number of listed models increases, and the management cost is high. In addition, there are certain design difficulties in the middle layer between the scenario definition and the actuator control logic, especially for some timing-related scenarios, which will further increase the number of listed scenarios.

[0052] Regarding the second direction mentioned above, although the actuators can be decoupled from each other, in scenarios where collaborative control is required (i.e., collaborative control of multiple actuators), the actuators need to repeatedly identify the required scenarios, and collaborative control blind spots are prone to occur; in addition, there are differences in the collaborative requirements between the actuators, and the logical reusability is relatively poor.

[0053] An embodiment of the present invention provides a thermal management hierarchical architecture system. Based on the above-mentioned direction one, corresponding modes are configured for the refrigerant circuit and the coolant circuit respectively to achieve the merging of usage scenarios, which can reduce the complexity of configuring control logic for the actuator.

[0054] Specifically, the control logic architecture of the thermal management system is divided into multiple layers to form a thermal management layered architecture system. Figure 1 A schematic diagram of a thermal management layered architecture system is shown in FIG. Figure 1 As shown, this embodiment redefines the architecture hierarchy, which is divided from top to bottom into a demand definition layer, a scenario management layer, a timing management layer, a control decomposition layer, and a control execution layer.

[0055] Among them, the requirement definition layer is used to obtain functional requirement information corresponding to multiple requirements and parse the functional requirement information into corresponding scenario description data.

[0056] The scenario management layer is used to generate corresponding usage scenarios based on scenario description data of various requirements.

[0057] The timing management layer is used to define scenarios with timing requirements, such as de-icing conditions that are executed in stages. This allows different control logic to be executed at different timings within a single scenario. Timing management will be described in detail later.

[0058] The control decomposition layer is used to set multiple refrigerant modes for the refrigerant circuit of the thermal management system, set multiple coolant modes for the coolant circuit of the thermal management system, and determine the correspondence between the refrigerant mode, the coolant mode and the usage scenario model; any refrigerant mode and / or coolant mode corresponds to one or more of the usage scenarios.

[0059] The control execution layer is used to configure a refrigerant control strategy for controlling the operation of the refrigerant actuator for each refrigerant mode, and to configure a coolant control strategy for controlling the operation of the coolant actuator for each coolant mode.

[0060] In this embodiment, the demand definition layer can define multiple demands according to different demand sources; Figure 1 As shown in the figure, these requirements include cockpit requirements, battery thermal management requirements, electric drive thermal management requirements, etc. Specifically, each requirement corresponds to corresponding functional requirement information. The requirement definition layer can be used to parse various functional requirement information into corresponding scenario description data.

[0061] Functional requirement information can be user- or system-defined, and each type of functional requirement can be quantified into corresponding scenario description data. This scenario description data is used to quantify the requirement value. For example, the scenario description information may include corresponding status indicators. For example, if the functional requirement information requires cabin cooling in the summer, analyzing it can determine specific status indicators such as the cabin air conditioning temperature. It is understood that if the user directly inputs quantified functional requirement information, the corresponding scenario description data can be directly extracted from it.

[0062] The scenario management layer defines the usage scenarios corresponding to all requirements. Using the different scenario description data corresponding to multiple requirements, corresponding usage scenarios can be generated. In other words, for any two different usage scenarios, the scenario description data for at least some of their requirements will differ. In this embodiment, usage scenarios are of the smallest granularity, meaning they cannot be further subdivided, but new usage scenarios can be added.

[0063] The control decomposition layer decomposes the thermal management system into two parts: refrigerant and coolant, defines the refrigerant circuit mode management and the coolant circuit mode management, and integrates the smallest granularity usage scenarios into corresponding refrigerant mode and coolant mode respectively; and, Figure 1 As shown, control management can also be defined to differentiate and integrate management under the same refrigerant mode or coolant mode. The control management will be described in detail later.

[0064] The control execution layer is defined as the actuator control logic pool for each circuit, hosting the individual actuator control logic units that ultimately achieve control objectives. Specifically, for each refrigerant mode, a corresponding refrigerant control strategy is configured. Subsequent use of the thermal management layered architecture system controls the corresponding refrigerant actuators based on the currently applied refrigerant control strategy. Similarly, for each coolant mode, a corresponding coolant control strategy is also configured.

[0065] Which actuators are included in each control pool depends on the actual situation. Figure 1 For example, the refrigerant actuator control pool includes four refrigerant actuators, namely A1, A2, A3, and A4, and the coolant actuator control pool includes three coolant actuators, namely B1, B2, and B3.

[0066] In this embodiment, based on the thermal management hierarchical architecture system, appropriate control strategies (including refrigerant control strategies and coolant control strategies) can be configured for various usage scenarios. Subsequently, by identifying the current usage scenario, the thermal management system can be adaptively controlled.

[0067] Specifically, in this embodiment, a control method for a thermal management system is provided, which is implemented based on the above-mentioned thermal management layered architecture system. The method can be applied to a controller in a vehicle that controls the thermal management system. Figure 2 FIG. 1 is a flow chart of a control method of a thermal management system according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps.

[0068] Step S201 : determining target function requirement information corresponding to a plurality of requirements at the current moment based on the requirement definition layer, and parsing the target function requirement information into corresponding target scenario description data.

[0069] In this embodiment, Figure 1 As shown, various requirements such as cockpit requirements, battery thermal management requirements, and electric drive thermal management requirements can be pre-configured.

[0070] Each requirement is assigned multiple status indicators (i.e., scenario description data). These status indicators are specific indicators corresponding to the requirement. For example, cabin requirements are passenger-related requirements. For example, in the summer, passengers require air conditioning at 25°C, which is one status indicator; in the winter, heating at 20°C is another status indicator. Battery thermal management requirements require the battery temperature to be kept below a certain temperature, which is another status indicator. And so on.

[0071] In the process of controlling the thermal management system, at the current moment, the target functional requirement information corresponding to various requirements can be analyzed to determine the scene description data required at the current moment, that is, the target scene description data.

[0072] Step S202 : determining target usage scenarios corresponding to target scenario description data of multiple requirements based on the scenario management layer.

[0073] In this embodiment, as shown above, multiple usage scenarios of the thermal management system are pre-configured, and corresponding control logic (or control tasks) are also configured for each usage scenario. Based on the actual state at the current moment, it can be determined which pre-configured usage scenario corresponds to. For ease of description, the usage scenario corresponding to the current moment is referred to as the target usage scenario, i.e., the usage scenario corresponding to the target scenario description data.

[0074] Step S203, based on the control decomposition layer, determines the target refrigerant mode corresponding to the target usage scenario among the multiple refrigerant modes corresponding to the refrigerant circuit of the thermal management system, and determines the target coolant mode corresponding to the target usage scenario among the multiple coolant modes corresponding to the coolant circuit of the thermal management system; the refrigerant mode corresponds to one or more usage scenarios, and the coolant mode corresponds to one or more usage scenarios.

[0075] A vehicle's thermal management system primarily consists of two circuits: the refrigerant circuit and the coolant circuit. The refrigerant circuit transfers heat through phase change (liquid-gas conversion), enabling air conditioning or electric vehicle heat pump systems. The coolant circuit, on the other hand, circulates heat through the coolant, transferring heat to cool or heat components such as the engine, battery, motor, and electronic control system, maintaining optimal operating temperatures.

[0076] Furthermore, each circuit corresponds to multiple actuators. For example, the refrigerant circuit includes multiple refrigerant actuators such as the compressor, condenser, and expansion valve; the coolant circuit includes multiple coolant actuators such as the water pump, radiator, fan, and heater.

[0077] In this embodiment, as shown above, a plurality of control modes, i.e., refrigerant modes, are configured for the refrigerant circuit of the thermal management system by controlling the decomposition layer. Each refrigerant mode corresponds to one or more usage scenarios. In other words, by integrating multiple usage scenarios, a corresponding refrigerant mode can be determined, i.e., a large number of usage scenarios are integrated into a smaller number of refrigerant modes, where the number of refrigerant modes is smaller than the number of usage scenarios. For example, a many-to-one relationship can exist between usage scenarios and modes, i.e., one mode corresponds to multiple usage scenarios.

[0078] After the target usage scenario is determined, the refrigerant mode corresponding to the target usage scenario, ie, the target refrigerant mode, can be determined.

[0079] Similarly, a plurality of control modes, i.e., coolant modes, are also configured for the coolant circuit of the thermal management system through the control decomposition layer; wherein each coolant mode corresponds to one or more usage scenarios. In other words, by integrating multiple usage scenarios, the corresponding coolant mode can be determined, that is, a large number of usage scenarios are integrated into a smaller number of coolant modes, and the number of coolant modes is less than the number of usage scenarios.

[0080] After the target usage scenario is determined, a coolant mode corresponding to the target usage scenario, ie, a target coolant mode, may be determined.

[0081] It's understandable that when integrating usage scenarios into corresponding modes, the integration results for the refrigerant circuit and the coolant circuit will differ slightly. For example, for the refrigerant circuit, you might integrate usage scenarios 1, 2, and 3 into one refrigerant circuit; for the coolant circuit, you might only integrate usage scenarios 1 and 2 into one coolant circuit, while using scenario 3 needs to be integrated into another coolant circuit. The specific integration results will depend on the actual situation.

[0082] In step S204 , a target refrigerant control strategy corresponding to the target refrigerant mode is determined based on the control execution layer, and a target coolant control strategy corresponding to the target coolant mode is determined.

[0083] Step S205 , controlling the corresponding refrigerant actuator to operate according to the target refrigerant control strategy, and controlling the corresponding coolant actuator to operate according to the target coolant control strategy.

[0084] In this embodiment, the control execution layer is pre-configured with a corresponding refrigerant control strategy for each refrigerant mode; correspondingly, a corresponding coolant control strategy is also pre-configured for each coolant mode. The refrigerant control strategy is used to control the operating state of one or more refrigerant actuators, and the coolant execution strategy is used to control the operating state of one or more coolant actuators.

[0085] After determining the target refrigerant mode and the target coolant mode, the corresponding control strategies, ie, the target refrigerant control strategy and the target coolant control strategy, can be determined.

[0086] The target refrigerant control strategy is a refrigerant control strategy that indicates how to control each refrigerant actuator, while the target coolant control strategy is a coolant control strategy that indicates how to control each coolant actuator. Therefore, after determining the target refrigerant control strategy, the corresponding refrigerant actuator can be controlled based on the target refrigerant control strategy; similarly, after determining the target coolant control strategy, the corresponding coolant actuator can be controlled based on the target coolant control strategy.

[0087] For example, the target usage scenario is summer cooling, and the air conditioner needs to be set to 25°C. Based on this target usage scenario, the target refrigerant control strategy for the refrigerant circuit and the target coolant control strategy for the coolant circuit can be determined, thereby controlling each actuator to perform the corresponding action. For example, the target refrigerant control strategy includes controlling the opening of the expansion valve, and the target coolant control strategy includes controlling the fan speed, etc. Based on the target refrigerant control strategy, the expansion valve can be set to the corresponding opening, and based on the target coolant control strategy, the fan speed can be set to the corresponding speed value, ultimately making the air outlet temperature of the air conditioner 25°C, meeting the requirements of the target usage scenario.

[0088] The thermal management hierarchical architecture system provided in this embodiment integrates the refrigerant circuit and coolant circuit of the thermal management system for multiple pre-configured usage scenarios, and integrates them into multiple refrigerant modes and multiple coolant modes. Since the number of modes is less than the number of usage scenarios, each actuator only needs to configure the control strategy under the corresponding mode, and there is no need to list all usage scenarios, which greatly simplifies the control strategy of the actuator. This hierarchical architecture can give each level a substantial control range, decouple layer by layer, reduce the difficulty of management and maintenance, and facilitate the realization of a platform-based universal architecture across systems and vehicle models. In subsequent use, the target usage scenario at the current moment can be determined, and the corresponding refrigerant mode and coolant mode can be determined, and then how to control each actuator can be determined. The usage scenario and the control strategy are decoupled layer by layer, and the refrigerant actuator and the coolant actuator can be collaboratively controlled to ensure that the control strategy can meet the requirements.

[0089] In this embodiment, for Figure 1 The hierarchical control logic architecture shown in the figure first configures the control logic of each actuator in each usage scenario, such as Figure 3 As shown, the process of configuring the control logic includes the following steps.

[0090] Step S301: Acquire functional requirement information corresponding to a plurality of requirements, and parse the functional requirement information into corresponding status indicators; each requirement corresponds to at least one status indicator.

[0091] Step S302: Combine the status indicators of multiple requirements to generate corresponding usage scenarios.

[0092] In the scenario management layer, for each requirement, a status indicator is taken out and the status indicators of multiple requirements are combined to form a usage scenario; since each requirement contains multiple status indicators, multiple usage scenarios can be generated.

[0093] For example, the cockpit requirements include 6 status indicators, the battery thermal management requirements include 5 status indicators, and the electric drive thermal management requirements include 4 status indicators. A total of 6×5×4=120 usage scenarios can be combined, and each usage scenario corresponds to a combination result of the three status indicators.

[0094] Based on steps S301 and S302 above, the process of pre-configuring multiple usage scenarios can be completed. As mentioned above, each usage scenario cannot be further subdivided, but new usage scenarios can be added. For example, by adding status indicators of one or more requirements, a new usage scenario can be added, depending on the actual situation.

[0095] Step S303: pre-configure a corresponding timing control strategy for some usage scenarios belonging to the timing control scenario. The timing control strategy includes multiple time periods, and corresponding control logic is configured for each time period.

[0096] Among them, the control in some use scenarios has a certain time sequence. The traditional thermal management solution will further list the scenarios, resulting in a large number of scenarios and difficult maintenance and management. Figure 1 As shown, the hierarchical thermal management system also includes a timing management layer, which configures timing control strategies for usage scenarios based on timing constraints. A timing control strategy includes multiple scheduling moments corresponding to control logic; each scheduling moment corresponds to a time period. The timing management layer manages usage scenarios that fall within the timing control scenario, enabling timing control without adding additional usage scenarios.

[0097] Taking the de-icing operating scenario as an example, the de-icing operating scenario includes multiple steps, such as heating first and then blowing water. This usage scenario belongs to a timing control scenario. For each de-icing step, there is a corresponding de-icing time period. By pre-configuring the control logic for each de-icing time period, time-sharing control of each actuator can be achieved, ultimately achieving de-icing.

[0098] In step S304 , for the refrigerant circuit of the thermal management system, multiple usage scenarios are integrated to determine a corresponding refrigerant mode; the refrigerant mode corresponds to one or more usage scenarios.

[0099] Step S305 : For the coolant circuit of the thermal management system, multiple usage scenarios are integrated to determine a corresponding coolant mode; the coolant mode corresponds to one or more usage scenarios.

[0100] In this embodiment, for all usage scenarios, the control decomposition layer is used to integrate the refrigerant circuit and the coolant circuit separately, thereby consolidating a large number of usage scenarios into a small number of refrigerant modes and coolant modes. For example, by integrating 120 usage scenarios, 50 refrigerant modes and 60 coolant modes can be determined.

[0101] The principles for dividing the refrigerant mode and coolant mode are: the physical state of the refrigerant circuit / coolant circuit (such as the status of various valves) and the control logic differences of the main actuators.

[0102] Taking the refrigerant circuit as an example, some refrigerant actuators are primary actuators. It's possible to integrate various usage scenarios with the same control logic for these primary refrigerant actuators into a single refrigerant mode. The coolant circuit is similar and will not be further described.

[0103] It is understood that the aforementioned number of usage scenarios, number of refrigerant modes, number of coolant modes, number of actuators, etc. are provided for ease of understanding and are not intended to limit this embodiment. The specific values ​​of the various numbers should be determined based on actual conditions. Furthermore, the aforementioned steps S304 and S305 may also be performed in parallel.

[0104] Step S306, configure a corresponding refrigerant control strategy for each refrigerant mode, and configure a corresponding coolant execution strategy for each coolant mode; the refrigerant control strategy is used to control the working state of one or more refrigerant actuators, and the coolant execution strategy is used to control the working state of one or more coolant actuators.

[0105] In this embodiment, a corresponding control strategy, i.e., a refrigerant control strategy, is configured for each refrigerant mode. Based on each refrigerant control strategy, it is possible to determine which refrigerant actuators in the refrigerant actuator control pool are controlled targets and how to control them, thereby controlling the working status of the corresponding refrigerant actuator.

[0106] Similarly, for each coolant mode, a corresponding control strategy, namely the coolant control strategy, is also configured for it. Based on each coolant control strategy, it can be determined which coolant actuators in the coolant actuator control pool are controlled targets and how to control them, thereby controlling the working status of the corresponding coolant actuator.

[0107] Among them, when there are timing constraints in the usage scenario, the control execution layer configures the refrigerant control strategy corresponding to the corresponding refrigerant mode and the coolant control mode corresponding to the corresponding coolant mode according to the timing control strategy of the usage scenario.

[0108] Optionally, the process of controlling the execution layer to configure the refrigerant control strategy and the coolant control strategy includes: determining the status flag corresponding to each scheduling moment according to the timing control strategy of the usage scenario, and different status flags correspond to different control logics; configuring the refrigerant control logic corresponding to each status flag for the refrigerant control strategy corresponding to the corresponding refrigerant mode, and configuring the coolant control logic corresponding to each status flag for the coolant control strategy corresponding to the corresponding coolant mode.

[0109] In this embodiment, taking the de-icing condition as an example, if the de-icing condition is divided into three time periods, and the status flags of the three time periods are 1, 2, and 3, respectively, then for the refrigerant mode corresponding to the de-icing condition, the refrigerant control strategy includes refrigerant control logic for the three time periods, and the three refrigerant control logics correspond to status flags 1, 2, and 3, respectively. Similarly, the coolant control strategy is also configured with coolant control logic corresponding to each status flag, which will not be repeated here.

[0110] After the above configuration, you can decouple layer by layer according to the above logical architecture based on the current actual usage scenario, and finally determine the corresponding control strategy to achieve coordinated control of each actuator.

[0111] Specifically, another control method for a thermal management system is provided in this embodiment, which can be applied to a controller for controlling a thermal management system in a vehicle. Figure 4 FIG. 1 is a flow chart of a control method of a thermal management system according to an embodiment of the present invention. Figure 4 As shown, the process includes the following steps.

[0112] Step S401: determining a target usage scenario corresponding to the current moment according to a plurality of pre-configured usage scenarios.

[0113] Specifically, the above step S401 “determining the target usage scenario corresponding to the current moment according to multiple pre-configured usage scenarios” includes steps S4011 to S4012.

[0114] Step S4011: determine target state indicators that are respectively hit by multiple demands at the current moment.

[0115] Step S4012: determining corresponding target usage scenarios based on various target status indicators; wherein each requirement corresponds to at least one status indicator, and the usage scenario is determined by combining the status indicators of multiple requirements.

[0116] In this embodiment, as shown in steps S301 and S302 above, multiple status indicators are pre-configured for each demand. At the current moment, the status indicator currently corresponding to each demand, i.e., the target status indicator, can be determined. It is understood that the target status indicator is one of the multiple pre-configured status indicators.

[0117] According to the target state indicators of multiple requirements, the usage scenario corresponding to the current moment can be determined in combination, that is, the target usage scenario. Similarly, the target usage scenario is also one of the multiple pre-configured usage scenarios.

[0118] Optionally, in this embodiment, each usage scenario corresponds to a unique scenario code, and accordingly, the target usage scenario also corresponds to a unique scenario code. The scenario code includes multiple sub-codes corresponding to various requirements, and the value of each sub-code corresponds to the target state indicator of the corresponding requirement.

[0119] Figure 5 A data structure diagram of a scene code is shown in FIG. Figure 5As shown, two bytes are used to represent the scenario code, where the lower four bits of the low-order byte (bits 3 to 0) are used to represent the status indicator of the electric drive thermal management requirements, and different values ​​represent different status indicators. Similarly, the upper four bits of the low-order byte (bits 7 to 4) are used to represent the status indicator of the battery thermal management requirements, and the lower four bits of the high-order byte (bits 3 to 0) are used to represent the status indicator of the cabin requirements. In addition, the upper four bits of the high-order byte (bits 7 to 4) can also be set with special status bits and system-defined bits, so as to identify some special states (for example, adding coolant to the vehicle) and set status indicators of various requirements for different systems. It can be understood that every 4 bits is a sub-code.

[0120] Figure 5 In the

[15] , each requirement is represented by a 4-bit status indicator, for a total of 16 status indicators. Different values ​​correspond to different status indicators. For example, if the value corresponding to the cabin requirement is 1, it represents the first cabin requirement status indicator. The specific meaning of this indicator can be predefined, such as the air conditioning setting of 25°C. In addition, if there are a large number of status indicators, more bits (e.g., 8 bits) can be used to represent the status indicators of each requirement. This is not limited in this embodiment.

[0121] In this embodiment, the scenario code is divided into multiple sub-codes corresponding to various requirements. The value of each sub-code can be defined according to the actual requirements, which enhances the readability and logical practicality of the scenario code and facilitates configuration. In addition, by giving the scenario code practical meaning, after the introduction of a new system, it is only necessary to define the meaning of the usage scenario according to the current rules and divide it into the refrigerant mode and coolant mode of this thermal management system. All downstream actuator control logic pools can still be used, ensuring the control logic platform between different thermal management systems, reserving the scalability of subsequent new systems, and reducing the scope of change.

[0122] For example, the scenario code 0x0231 indicates that there is no special state. For the default system, the usage scenario corresponds to the second state indicator of the cockpit requirements, the third state indicator of the battery thermal management requirements, and the first state indicator of the electric drive thermal management requirements.

[0123] In some optional embodiments, such as Figure 1 As shown, the timing management layer performs timing control on some usage scenarios. Accordingly, after the above step S401 "determining the target usage scenario corresponding to the current moment", the method further includes steps C1 to C2.

[0124] Step C1: determine whether the target usage scenario belongs to a timing control scenario.

[0125] Step C2: When the target usage scenario belongs to a sequential control scenario, the target refrigerant control strategy and / or the target coolant control strategy are updated in different time periods according to the sequential control strategy pre-configured for the target usage scenario.

[0126] In this embodiment, it is predefined which usage scenarios belong to the timing control scenario. Therefore, after determining the target usage scenario, it can be determined whether the target usage scenario belongs to the timing control scenario. If the target usage scenario does not belong to the timing control scenario, there is no need to perform timing control, and the subsequent steps S402 and S403 can be directly performed.

[0127] If the target usage scenario belongs to a timing control scenario, it is necessary to determine the timing control strategy corresponding to the target usage scenario. As mentioned above, the timing control strategy includes multiple time periods, and each time period is configured with corresponding control logic.

[0128] When subsequently determining the target refrigerant control strategy and / or target coolant control strategy, the corresponding target refrigerant control strategy and / or target coolant control strategy must be updated for each time period based on the control logic for each time period in the sequential control strategy. Whether to update either or both of the target refrigerant control strategy and target coolant control strategy depends on the control logic pre-configured in the sequential control strategy and is not detailed here.

[0129] This embodiment configures a suitable timing control strategy for each timing control scenario separately, thereby achieving time-segmented timing control without increasing the number of usage scenarios, thereby meeting timing control requirements.

[0130] Optionally, the above step C2 “updating the target refrigerant control strategy and / or the target coolant control strategy in time periods according to the timing control strategy pre-configured for the target usage scenario” includes steps C21 to C22.

[0131] Step C21 : determining the status flags corresponding to the respective time periods according to the timing control strategy pre-configured for the target usage scenario, wherein different status flags correspond to different control logics.

[0132] Step C22: after reaching the corresponding time period, updating the target refrigerant control strategy and / or the target coolant control strategy according to the control logic corresponding to the status flag.

[0133] In this embodiment, taking the de-icing condition corresponding to the target usage scenario as an example, if it is divided into three time periods, and the status flags of the three time periods are 1, 2, and 3 respectively, then after reaching the corresponding time period, the target refrigerant control strategy and / or the target coolant control strategy are adaptively updated based on the status flag.

[0134] For example, Figure 1Taking the logical architecture shown in the figure as an example, in the first period, the timing management layer outputs a status flag of 1. The refrigerant circuit mode management layer of the control decomposition layer determines the corresponding target refrigerant control strategy based on the target refrigerant mode corresponding to the target usage scenario. Based on the status flag of 1, the target refrigerant control strategy is adaptively adjusted, such as enabling the heating function, to update the target refrigerant control strategy. The operating principle of coolant circuit mode management is similar to that of refrigerant circuit mode management and will not be repeated here.

[0135] In this embodiment, the timing management layer outputs a status flag as a timing representation, which can simply and conveniently implement different control logics at different timings for usage scenarios with the same requirements.

[0136] Step S402 : determining a target refrigerant mode corresponding to a target usage scenario among a plurality of refrigerant modes corresponding to a refrigerant circuit of the thermal management system; the refrigerant mode corresponds to one or more usage scenarios.

[0137] Step S403 , determining a target coolant mode corresponding to a target usage scenario among a plurality of coolant modes corresponding to a coolant circuit of the thermal management system; the coolant mode corresponds to one or more usage scenarios.

[0138] For details, please see Figure 2 Step S203 of the illustrated embodiment will not be described in detail here.

[0139] In step S404 , a target refrigerant control strategy corresponding to the target refrigerant mode is determined based on the control execution layer, and a target coolant control strategy corresponding to the target coolant mode is determined.

[0140] For details, please see Figure 2 Step S204 of the illustrated embodiment will not be described in detail here.

[0141] In some optional implementations, the process of integrating the refrigerant modes in step S304 and configuring the refrigerant control strategy in step S306 specifically includes the following steps D1 to D2.

[0142] In step D1 , usage scenarios in which the same control logic is executed on at least some refrigerant actuators are integrated into corresponding refrigerant modes.

[0143] Step D2: If, among the multiple usage scenarios corresponding to the refrigerant mode, there are different refrigerant actuators that execute different control logics in different usage scenarios, the execution logics in different usage scenarios are respectively set for the different refrigerant actuators.

[0144] Similarly, the process of integrating the coolant modes in step S305 and configuring the coolant control strategy in step S306 specifically includes the following steps D3 to D4.

[0145] Step D3: integrating usage scenarios in which the same control logic is executed on at least some of the coolant actuators into corresponding coolant modes.

[0146] Step D4: In the multiple usage scenarios corresponding to the coolant mode, if there are different coolant actuators that execute different control logics in different usage scenarios, the execution logics in different usage scenarios are set for the different coolant actuators.

[0147] In this embodiment, taking the refrigerant circuit as an example, it includes multiple refrigerant actuators; for different usage scenarios, the control logic of some refrigerant actuators is the same. Even if the control logic of another part of the refrigerant actuators is not exactly the same, these usage scenarios can be merged to determine the corresponding refrigerant mode.

[0148] Among them, if a refrigerant mode corresponds to multiple usage scenarios and the control logic for each refrigerant actuator is the same, no additional configuration is required, that is, a unique refrigerant control strategy can be configured for the refrigerant mode.

[0149] On the contrary, if for a certain refrigerant mode, some refrigerant actuators execute different control logics in different usage scenarios, it is necessary to additionally configure the control logic for each usage scenario for these refrigerant actuators. For ease of description, these refrigerant controllers are called differential refrigerant actuators.

[0150] Generally speaking, when performing scenario integration, multiple usage scenarios with the same control logic of the main refrigerant actuator need to be integrated into one refrigerant mode, and the secondary refrigerant actuator can be ignored. In other words, the differential refrigerant actuator is the secondary refrigerant actuator.

[0151] by Figure 1 Taking the architecture shown as an example, if usage scenarios 1, 2, and 3 are integrated into refrigerant mode A, and the control logic of refrigerant actuators A1, A2, and A3 is the same in usage scenarios 1, 2, and 3, but the control logic of refrigerant actuator A4 is different in different usage scenarios, for example, if refrigerant actuator A4 is a fan, its required speed values ​​are different in usage scenarios 1, 2, and 3. In this case, refrigerant actuator A4 is a differential refrigerant actuator, and the refrigerant control strategy of refrigerant mode A only applies to refrigerant actuators A1, A2, and A3. The control logic of refrigerant actuator A4 needs to be determined based on the specific usage scenario.

[0152] The configuration process of the coolant circuit is similar to the above, so steps D3 to D4 will not be described in detail.

[0153] Optionally, the above step S404 of “determining a target refrigerant control strategy corresponding to the target refrigerant mode, and determining a target coolant control strategy corresponding to the target coolant mode” may include step E1 and step E2.

[0154] In step E1, if a target refrigerant actuator exists among the multiple refrigerant actuators controlled under the target refrigerant mode, a control logic for the target refrigerant actuator is determined based on the target usage scenario, and the control logic for the target refrigerant actuator in the target refrigerant control strategy is updated. The target refrigerant actuator is a refrigerant actuator that executes different control logics in different usage scenarios corresponding to the target refrigerant mode. It is understood that the target refrigerant actuator is a differentiated refrigerant actuator.

[0155] In step E2, if the target coolant actuator exists among the multiple coolant actuators controlled in the target coolant mode, the control logic of the target coolant actuator is determined based on the target usage scenario, and the control logic for the target coolant actuator in the target coolant control strategy is updated. The target coolant actuator is a coolant actuator that executes different control logics in different usage scenarios among the multiple usage scenarios corresponding to the target coolant mode. It is understood that the target coolant actuator is a differentiated coolant actuator.

[0156] In this embodiment, for multiple usage scenarios corresponding to the target refrigerant mode, if there is a refrigerant actuator that executes different control logics in different usage scenarios, for the convenience of description, the refrigerant actuator is called the target refrigerant actuator. The target refrigerant actuator is a differential refrigerant actuator. For example, the target refrigerant actuator is the refrigerant actuator A4 illustrated in the above explanation of steps D1 to D2.

[0157] In this case, in addition to determining the refrigerant control strategy for the target refrigerant mode, the control logic for the target refrigerant actuator must also be determined based on the target usage scenario. This control logic is pre-configured. Once the control logic for the target refrigerant actuator is determined, the control logic for the target refrigerant actuator in the target refrigerant control strategy can be adjusted accordingly. This adjusted target refrigerant control strategy allows for accurate control and differentiation between different usage scenarios.

[0158] like Figure 1 As shown, the control management module defines the control logic for the target refrigerant actuator. Specifically, after integration at the scenario management layer, the scenario code for the target usage scenario is output. Based on this scenario code, the refrigerant circuit mode management module determines the corresponding target refrigerant mode, and the coolant circuit mode management module determines the corresponding target coolant mode.

[0159] If the target refrigerant mode has a target refrigerant actuator (a differential refrigerant actuator), the control management can determine the control logic of the target refrigerant actuator based on the scenario code of the target usage scenario, and then correctly control the corresponding target refrigerant actuator based on the control logic, thereby achieving differentiated control of a certain refrigerant actuator under the same refrigerant mode.

[0160] The differential control principle of the coolant circuit is similar to that of the refrigerant circuit, so step E2 will not be described in detail.

[0161] Step S405 , controlling the corresponding refrigerant actuator to operate according to the target refrigerant control strategy, and controlling the corresponding coolant actuator to operate according to the target coolant control strategy.

[0162] For details, please see Figure 1 Step S205 of the illustrated embodiment will not be described in detail here.

[0163] The control method for the thermal management system provided in this embodiment can effectively shield the impact of changes in demand usage scenarios on the control of downstream actuators through multi-level management. At the scenario management level, the usage scenarios can be refined with the smallest granularity to ensure that they can be applied to a variety of usage scenarios; the usage scenarios can be classified and integrated into corresponding modes through the control decomposition layer, which can not only ensure that the definition of subdivided scenarios is used for the refinement of control logic, but also configure the control logic of each actuator according to a small number of modes, which can reduce management difficulty and maintenance costs. By defining the control logic of differential actuators, differential management under the same refrigerant mode or coolant mode can be achieved, which is applicable to a variety of usage scenarios.

[0164] The embodiment of the present invention also provides a vehicle, see Figure 6 , Figure 6 : is a structural diagram of a vehicle provided by an optional embodiment of the present invention, such as Figure 6 As shown, the vehicle includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components are connected to each other using different buses and can be installed on a common motherboard or in other ways as needed. The processor can process instructions executed in the vehicle, including instructions stored in or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used with multiple memories. Figure 6 A processor 10 is taken as an example.

[0165] The processor 10 may be a central processing unit, a network processor, or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic, or any combination thereof.

[0166] The memory 20 stores instructions that can be executed by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0167] The memory 20 may include a program storage area and a data storage area. The program storage area may store an operating system and applications required for at least one function; the data storage area may store data generated based on vehicle usage, etc. Furthermore, the memory 20 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state memory device. In some optional embodiments, the memory 20 may optionally include a memory remotely located relative to the processor 10, and such remote memory may be connected to the vehicle via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0168] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0169] The vehicle further includes a communication interface 30 for the vehicle to communicate with other vehicles or a communication network.

[0170] The embodiment of the present invention also provides a computer-readable storage medium. The above-mentioned method according to the embodiment of the present invention can be implemented in hardware, firmware, or implemented as a computer code that can be recorded in a storage medium, or implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and downloaded through a network and will be stored in a local storage medium, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor or hardware, the method shown in the above embodiment is implemented.

[0171] A portion of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the form in which the computer program instruction exists in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc. Accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium that can be accessed by the computer.

[0172] Although the embodiments of the present invention have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations should all be included in the scope of protection of the present invention.

Claims

1. A thermal management layered architecture system, characterized in that: The system comprises: The requirement definition layer is used to obtain functional requirement information corresponding to various requirements and parse the functional requirement information into corresponding scenario description data; A scenario management layer, configured to generate corresponding usage scenarios based on the scenario description data of various requirements; A control decomposition layer is used to set multiple refrigerant modes for the refrigerant circuit of the thermal management system, set multiple coolant modes for the coolant circuit of the thermal management system, and determine the correspondence between the refrigerant modes, the coolant modes, and the usage scenario models; any of the refrigerant modes and / or the coolant modes corresponds to one or more of the usage scenarios; The control execution layer is used to configure a refrigerant control strategy for controlling the operation of the refrigerant actuator for each of the refrigerant modes, and to configure a coolant control strategy for controlling the operation of the coolant actuator for each of the coolant modes.

2. The system according to claim 1, wherein: The scenario description data includes status indicators corresponding to the requirements; The scenario management layer generates corresponding usage scenarios based on the scenario description data of various requirements, including: The status indicators of the multiple requirements are combined to generate corresponding usage scenarios.

3. The system according to claim 2, characterized in that Each of the usage scenarios corresponds to a unique scenario code; the scenario code includes multiple sub-codes corresponding to the multiple requirements, and the value of each sub-code corresponds to the target state indicator of the corresponding requirement.

4. The system according to claim 1, wherein: The system further comprises: A timing management layer, configured to configure a timing control strategy for the usage scenario according to the timing constraints when the usage scenario has timing constraints; the timing control strategy includes scheduling moments corresponding to multiple control logics; Wherein, when there are timing constraints in the usage scenario, the control execution layer configures the refrigerant control strategy corresponding to the corresponding refrigerant mode and the coolant control mode corresponding to the corresponding coolant mode according to the timing control strategy of the usage scenario.

5. The system according to claim 4, characterized in that The process of configuring the refrigerant control strategy and the coolant control strategy at the control execution layer includes: Determine the status flag corresponding to each scheduling moment according to the timing control strategy of the usage scenario, where different status flags correspond to different control logics; The refrigerant control strategy corresponding to the corresponding refrigerant mode is configured with a refrigerant control logic corresponding to each of the status flags, and the coolant control strategy corresponding to the corresponding coolant mode is configured with a coolant control logic corresponding to each of the status flags.

6. The system according to claim 1, wherein: The control decomposition layer is further used to: integrate the use scenarios of executing the same control logic on at least part of the refrigerant actuators into corresponding refrigerant modes; integrate the use scenarios of executing the same control logic on at least part of the coolant actuators into corresponding coolant modes; The control execution layer is also used for: In the multiple usage scenarios corresponding to the refrigerant mode, if there are different refrigerant actuators that execute different control logics in different usage scenarios, the execution logics in different usage scenarios are respectively set for the different refrigerant actuators; In the multiple usage scenarios corresponding to the coolant mode, if there are different coolant actuators that execute different control logics in different usage scenarios, the execution logics in different usage scenarios are set for the different coolant actuators respectively.

7. A control method for a thermal management system, characterized in that: Based on the thermal management layered architecture system according to claims 1 to 6, the method includes: Determine target function requirement information corresponding to the multiple requirements at the current moment based on the requirement definition layer, and parse the target function requirement information into corresponding target scenario description data; Determining target usage scenarios corresponding to the target scenario description data of multiple requirements based on the scenario management layer; Determining, based on the control decomposition layer, a target refrigerant mode corresponding to the target usage scenario among a plurality of refrigerant modes corresponding to the refrigerant circuit of the thermal management system, and determining a target coolant mode corresponding to the target usage scenario among a plurality of coolant modes corresponding to the coolant circuit of the thermal management system; the refrigerant mode corresponds to one or more of the usage scenarios, and the coolant mode corresponds to one or more of the usage scenarios; Based on the control execution layer, the target refrigerant control strategy corresponding to the target refrigerant mode is determined, and the target coolant control strategy corresponding to the target coolant mode is determined; the corresponding refrigerant actuator is controlled to work according to the target refrigerant control strategy, and the corresponding coolant actuator is controlled to work according to the target coolant control strategy.

8. The method according to claim 7, characterized in that The method further comprises: Determining whether the target usage scenario is a usage scenario with timing constraints; In a case where the target usage scenario is a usage scenario with timing constraints, the target refrigerant control strategy and / or the target coolant control strategy are updated in time periods according to a timing control strategy pre-configured for the target usage scenario.

9. The method according to claim 7, characterized in that The determining of the target refrigerant control strategy corresponding to the target refrigerant mode and the determining of the target coolant control strategy corresponding to the target coolant mode include: If a target refrigerant actuator exists among the multiple refrigerant actuators controlled under the target refrigerant mode, determine the control logic of the target refrigerant actuator according to the target usage scenario, and update the control logic of the target refrigerant actuator in the target refrigerant control strategy; the target refrigerant actuator is a refrigerant actuator that executes different control logics in different usage scenarios among the multiple usage scenarios corresponding to the target refrigerant mode; If a target coolant actuator exists among the multiple coolant actuators controlled under the target coolant mode, the control logic of the target coolant actuator is determined according to the target usage scenario, and the control logic for the target coolant actuator in the target coolant control strategy is updated; the target coolant actuator is a coolant actuator that executes different control logics in different usage scenarios among the multiple usage scenarios corresponding to the target coolant mode.

10. A vehicle, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the control method of the thermal management system according to any one of claims 7 to 9 by executing the computer instructions.

11. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the control method of the thermal management system according to any one of claims 7 to 9.

Images