Method and device for generating rde verification scheme, electronic equipment and storage medium

By defining multiple simulation conditions in hybrid electric vehicles, inputting the vehicle simulation model to assess emission risks, and screening candidate conditions to generate RDE verification schemes, the problem of low generation efficiency and insufficient comprehensiveness in existing technologies is solved, and efficient and targeted RDE verification is achieved.

CN123116629APending Publication Date: 2026-11-17CHONGQING CHANGAN AUTOMOBILE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611464717.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-20
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing hybrid vehicle RDE verification schemes rely on extensive real-vehicle testing, resulting in low generation efficiency and the potential to overlook high-emission-risk scenarios, failing to guarantee the relevance and comprehensiveness of the schemes.

Method used

By defining multiple simulation conditions, inputting the vehicle simulation model, obtaining engine operating condition data, assessing the risk level of emission pollutants, screening candidate simulation conditions, and generating an RDE verification scheme.

Benefits of technology

It improves the efficiency and comprehensiveness of RDE verification scheme generation, ensures the relevance of the scheme, and reduces verification costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123116629A_ABST
    Figure CN123116629A_ABST
Patent Text Reader

Abstract

The application relates to a method and device for generating an RDE verification scheme, and an electronic storage medium. The method comprises: determining a plurality of simulation conditions, each simulation condition comprising a combination of dimension information corresponding to different preset dimensions in a preset dimension set, the preset dimensions representing parameter variables affecting RDE of a hybrid vehicle; inputting each simulation condition into a corresponding vehicle simulation model of the hybrid vehicle to obtain working condition data of an engine in the hybrid vehicle under each simulation condition; determining a risk degree of emission pollutants of the hybrid vehicle under each simulation condition according to each working condition data; determining each candidate simulation condition from each simulation condition based on each risk degree; and generating an RDE verification scheme corresponding to the hybrid vehicle based on each candidate simulation condition. The application improves the generation efficiency of the RDE verification scheme and ensures that the generated RDE verification scheme is targeted and comprehensive.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of vehicle technology, specifically to a method, apparatus, electronic device, and storage medium for generating an RDE verification scheme. Background Technology

[0002] With the increasing prevalence of hybrid electric vehicles (HEVs), their vehicle emissions testing must meet Real Driving Emissions (RDE) regulations. Due to the diverse energy management modes, driving styles, and varying battery initial states of charge in HEVs, the engine's start-stop logic and operating conditions are significantly influenced by control strategies, resulting in emissions characteristics far more complex than those of traditional gasoline-powered vehicles. Currently, the generation of RDE verification schemes for HEVs primarily relies on extensive real-world road testing for screening. This involves conducting real-world tests in different cities and road conditions, and then retrospectively identifying key operating conditions such as temperature and road spectrum from the collected test data to determine the RDE verification scheme. However, this retrospective screening method typically requires extensive real-world road testing, which not only affects the efficiency of RDE verification scheme generation but also, due to limitations imposed by actual road testing conditions, can easily lead to the omission of some high-emission-risk scenarios, resulting in RDE verification schemes that lack specificity and comprehensiveness. Summary of the Invention

[0003] One objective of this application is to provide a method for generating an RDE verification scheme, which enables the early-stage design to prospectively assess emission risk under different combinations of parameter variables through simulation, and generates an RDE verification scheme accordingly, thereby improving the generation efficiency of the RDE verification scheme and ensuring that the generated RDE verification scheme is targeted and comprehensive. A second objective of this application is to provide an apparatus for generating an RDE verification scheme. A third objective of this application is to provide an electronic device. A fourth objective of this application is to provide a storage medium.

[0004] To achieve the above objectives, firstly, this application provides a method for generating an RDE verification scheme, comprising: Multiple simulation conditions are determined, and each simulation condition includes a combination of dimensional information corresponding to different preset dimensions in a preset dimension set. The preset dimensions represent the parameter variables that affect the RDE of hybrid electric vehicles. Each of the simulation conditions is input into the vehicle simulation model corresponding to the hybrid vehicle to obtain the operating data of the engine in the hybrid vehicle under each of the simulation conditions. Based on the data from each of the aforementioned operating conditions, the risk level of pollutant emissions from the hybrid vehicle under each of the aforementioned simulation conditions is determined; Based on the respective risk levels, candidate simulation conditions are determined from the respective simulation conditions; Based on each of the candidate simulation conditions, an RDE verification scheme corresponding to the hybrid electric vehicle is generated.

[0005] To achieve the above objectives, in a second aspect, this application provides an apparatus for generating an RDE verification scheme, comprising: The determination module is used to determine multiple simulation conditions, each of which includes a combination of dimensional information corresponding to different preset dimensions in a preset dimension set, wherein the preset dimensions characterize the parameter variables that affect the RDE of hybrid electric vehicles; The simulation module is used to input each of the simulation conditions into the vehicle simulation model corresponding to the hybrid vehicle, so as to obtain the operating condition data of the engine in the hybrid vehicle under each of the simulation conditions. The determining module is further configured to determine the risk level of pollutant emissions from the hybrid vehicle under each of the simulation conditions based on the various operating condition data. The determining module is further configured to determine each candidate simulation condition from each simulation condition based on each of the risk levels. The generation module is used to generate the RDE verification scheme corresponding to the hybrid vehicle based on each of the candidate simulation conditions.

[0006] To achieve the above objectives, in a third aspect, this application also provides an electronic device, including: a processor and a memory, wherein the processor is configured to execute a generation program for an RDE verification scheme stored in the memory, so as to implement the RDE verification scheme generation method described above.

[0007] To achieve the above objectives, in a fourth aspect, this application also provides a storage medium storing one or more programs that can be executed by one or more processors to implement the method for generating the RDE verification scheme as described above.

[0008] The beneficial effects of this application are as follows: This application provides a method for generating an RDE verification scheme, comprising: determining multiple simulation conditions, each simulation condition including a combination of dimensional information corresponding to different preset dimensions in a preset dimension set, wherein the preset dimensions characterize the parameter variables affecting the RDE of a hybrid electric vehicle; inputting each simulation condition into a vehicle simulation model corresponding to the hybrid electric vehicle to obtain the operating condition data of the engine in the hybrid electric vehicle under each simulation condition; determining the risk level of pollutant emissions from the hybrid electric vehicle under each simulation condition based on the operating condition data; determining each candidate simulation condition from each simulation condition based on each risk level; and generating an RDE verification scheme corresponding to the hybrid electric vehicle based on each candidate simulation condition. Through the above method, this application combines the dimensional information corresponding to multiple preset dimensions affecting the RDE of a hybrid electric vehicle into multiple simulation conditions, and inputs them into a vehicle simulation model to obtain the operating condition data of the engine under each simulation condition; based on this, it determines the risk level of pollutant emissions from the hybrid electric vehicle under each simulation condition based on the operating condition data, and selects candidate simulation conditions from multiple simulation conditions based on each risk level, thereby generating an RDE verification scheme. This allows for early-stage simulation-based assessment of emission risk under different combinations of parameter variables, enabling the generation of RDE verification schemes. This improves the efficiency of RDE verification scheme generation and ensures that the generated RDE verification schemes are targeted and comprehensive. Attached Figure Description

[0009] Figure 1 This diagram illustrates a flowchart of a method for generating an RDE verification scheme according to an embodiment of this application. Figure 2 This diagram illustrates a flowchart of another RDE verification scheme generation method provided in an embodiment of this application. Figure 3 This diagram illustrates a flowchart of a method for generating another RDE verification scheme provided in an embodiment of this application. Figure 4(a) shows a schematic diagram comparing an engine operating condition map under simulation conditions with a baseline operating condition map provided in an embodiment of this application; Figure 4(b) shows a schematic diagram comparing the engine operating condition map under another simulation condition with the baseline operating condition map provided in the embodiment of this application; Figure 4(c) shows a schematic diagram comparing the engine operating condition map under another simulation condition with the baseline operating condition map provided in the embodiment of this application; Figure 5 This diagram illustrates the structure of a device for generating an RDE verification scheme according to an embodiment of this application. Figure 6 This diagram illustrates the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0010] The embodiments of this application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be understood that the preferred embodiments are only for illustrating this application and are not intended to limit the scope of protection of this application.

[0011] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0012] To facilitate understanding of the embodiments of this application, the following will provide further explanation and description with reference to the accompanying drawings and specific embodiments. These embodiments do not constitute a limitation on the embodiments of this application.

[0013] refer to Figure 1 , Figure 1 This application provides a flowchart illustrating a method for generating an RDE verification scheme. The method for generating an RDE verification scheme provided in this application includes the following steps: S101: Define multiple simulation conditions.

[0014] In this embodiment, each simulation condition includes a combination of dimensional information corresponding to different preset dimensions in a preset dimension set. The preset dimensions represent the parameter variables that affect the RDE of the hybrid electric vehicle.

[0015] RDE (Real Driving Emissions) refers to the pollutant emissions generated by a vehicle under actual road driving conditions.

[0016] The preset dimension set refers to a set of key parameter variables that are pre-set to affect the emissions of hybrid vehicles during actual driving. Different combinations of parameter variables will affect the start-stop logic and operating conditions (speed, torque) of the hybrid engine, resulting in significant differences in the pollutants (such as NOx and PN particulate matter) emitted by hybrid vehicles even under the same road conditions and vehicle speed.

[0017] Simulation conditions refer to a complete set of input conditions composed of dimensional information corresponding to different preset dimensions in a preset dimension set. Each simulation condition can represent a specific combination scenario. For example, a set of simulation conditions could be "Energy Management Mode = Intelligent Hybrid, Driving Style = Sport, Initial Battery State of Charge = 50%, Ambient Temperature = 35℃, Altitude = 0m". This combination scenario represents a specific test scenario of driving in intelligent hybrid mode with a sport driving style in a high-temperature plain environment.

[0018] Specifically, key parameter variables affecting the RDE emission results of hybrid electric vehicles are pre-defined, constructing a pre-defined dimension set. Multiple simulation conditions can be obtained by combining the dimensional information corresponding to different pre-defined dimensions in the pre-defined dimension set (e.g., through iterative combinations). The dimensional information corresponding to different pre-defined dimensions in the pre-defined dimension set can be represented by a multi-dimensional influencing factor matrix.

[0019] Furthermore, step S101 defines several simulation conditions, specifically including: Obtain the dimension information corresponding to each preset dimension in the preset dimension set; wherein, the preset dimension set includes state dimension and environment dimension; The dimensional information corresponding to different preset dimensions in the preset dimension set is traversed and combined to determine the various simulation conditions.

[0020] The state dimension includes at least one of energy management mode, driving style, and initial battery state of charge, while the environmental dimension includes at least one of ambient temperature and altitude. The state dimension directly affects the engine's start-stop logic, operating conditions, and power distribution, while the environmental dimension affects the engine's external operating environment.

[0021] Energy management modes refer to the operating modes that affect the power distribution logic between the engine and the electric motor in a hybrid electric vehicle. Examples include pure electric priority mode, fuel priority mode, and intelligent hybrid mode.

[0022] Driving style refers to the driving mode that affects the torque output characteristics required by the driver. Examples include Eco, Sport, and Comfort modes.

[0023] The initial battery state of charge refers to the state of charge (SOC) value of the power battery at the start of the simulation.

[0024] The ambient temperature is determined according to the test temperature range specified in the regulations (e.g., low temperature -7℃, normal temperature 25℃, high temperature 35℃); the altitude is determined according to the altitude boundary specified in the regulations (e.g., plains 0m, plateaus 1300m, high plateaus 2400m).

[0025] Specifically, based on the overall vehicle configuration and RDE verification requirements of the hybrid electric vehicle under test, key parameter variables can be pre-set and categorized into two main types: state dimensions and environment dimensions, thus constructing a preset dimension set. After acquiring the dimension information, each preset dimension corresponds to a set of dimension information lists for subsequent traversal and combination.

[0026] The dimensional information corresponding to each preset dimension is arranged in a preset order to form a dimensional information sequence. For example, the dimensional information of energy management mode is arranged as sequence A = [pure electric priority, fuel priority, intelligent hybrid], the dimensional information of driving style is arranged as sequence B = [economy, comfort, sport], the dimensional information of initial battery state of charge is arranged as sequence C = [20%, 50%, 80%], the dimensional information of ambient temperature is arranged as sequence D = [-7℃, 25℃, 35℃], and the dimensional information of altitude is arranged as sequence E = [0m, 1300m, 2400m]. Then, nested loops are performed on each dimensional information sequence, and one value is taken from each dimensional information sequence to form a complete set of simulation conditions. The simulation conditions include one dimensional information from each preset dimension, forming a quintuple of energy management mode, driving style, initial battery state of charge, ambient temperature, and altitude.

[0027] For example, the preset dimension set includes five preset dimensions: energy management mode (candidate values: pure electric priority, fuel priority, intelligent hybrid), driving style (candidate values: economy, comfort, sport), initial battery state of charge (candidate values: 20%, 50%, 80%), ambient temperature (candidate values: -7℃, 25℃, 35℃), and altitude (candidate values: 0m, 1300m, 2400m). By iterating through and combining these dimensions, 3×3×3×3×3=243 simulation conditions can be obtained. Each simulation condition represents a specific combination scenario of vehicle technical state and environmental conditions.

[0028] Through the above methods, this embodiment acquires dimensional information from multiple preset dimensions, including energy management mode, driving style, initial battery state of charge, ambient temperature, and altitude. By traversing and combining the dimensional information corresponding to different preset dimensions, it can systematically and comprehensively generate simulation conditions covering various technical states and environmental conditions. This avoids missing key high-risk scenarios due to manual selection or experience-based combinations, thereby improving the comprehensiveness and accuracy of subsequent risk assessment of pollutant emissions and enhancing the comprehensiveness and relevance of the generated RDE verification scheme.

[0029] S102: Input each simulation condition into the corresponding vehicle simulation model of the hybrid vehicle to obtain the operating data of the engine in the hybrid vehicle under each simulation condition.

[0030] In this embodiment, the vehicle simulation model refers to a pre-built high-fidelity simulation model used to simulate the overall operating behavior of a hybrid electric vehicle. This vehicle simulation model adopts a co-simulation architecture that separates the physical model and the control model, and coordinates them through interfaces. The vehicle simulation model comprises two main parts: a physical model and a control model.

[0031] The physical model is a forward model built in a professional simulation software environment, including the engine, drive motor, generator, power battery, transmission, and overall vehicle dynamics. The parameters of each component in the physical model (such as the engine universal characteristic diagram, battery internal resistance-capacity curve, etc.) are calibrated based on real vehicle data of hybrid electric vehicles.

[0032] The control model is built in a model-based software development environment to accurately reproduce the upper-level energy management strategy and the software logic of the lower-level controllers (such as the PCU power controller, ECU engine controller, and BMS battery management system) of hybrid electric vehicles. The focus of the control model is on the parameterized configuration and switching of energy management modes. For example, the pure electric priority mode can be parameterized to prevent engine start-up when SOC > 15%, and the intelligent hybrid mode can be parameterized to determine engine start-stop based on a lookup table of vehicle speed, required power, and SOC. Through parameterized configuration, different energy management modes and driving styles can be flexibly switched during simulation without modifying the underlying model code.

[0033] The physical model and the control model exchange data in real time through a predefined interface (such as the TCP / IP-based FMI protocol) to simulate the closed-loop interaction between the controller and actuator in a real vehicle. Specifically, the control model exchanges data periodically according to a set simulation step size.

[0034] Operating condition data refers to the runtime sequence data generated when the engine is running under various simulation conditions, reflecting the engine's operating characteristics under those conditions. Operating condition data includes at least the time-series data of the engine's speed-torque changes over time throughout the entire operation process, as well as key statistical information such as the engine's first start-up time, total engine runtime, and number of start-stop cycles.

[0035] Specifically, for each simulation condition, the energy management mode and driving style parameters corresponding to that simulation condition are set in the control model of the vehicle simulation model. For example, when the simulation condition specifies energy management mode = intelligent hybrid and driving style = sport, the control logic parameters in the control model corresponding to the intelligent hybrid mode, such as the SOC maintenance threshold and engine intervention conditions, take effect in the simulation. At the same time, the aggressive accelerator pedal mapping relationship corresponding to the sport driving style is also loaded. Parameters such as the initial battery state of charge, ambient temperature, and altitude are set in the physical model. Then, the simulation is run on the selected baseline driving cycle. During the simulation, the control model dynamically decides on engine start / stop and motor torque distribution according to the loaded energy management strategy based on real-time vehicle speed, power demand, and battery state of charge, and sends control commands to the physical model for execution. The physical model simulates the actual physical response of each component according to the control commands and feeds back the real-time status to the control model. This closed-loop iteration continues until the simulation ends. After the simulation ends, the engine operating data under the simulation conditions is automatically recorded and output.

[0036] S103: Based on the data from various operating conditions, determine the risk level of pollutant emissions from hybrid vehicles under various simulation conditions.

[0037] In this embodiment, the risk level can be understood as the specific pollutant emissions of a hybrid vehicle under a certain simulation condition. A higher risk level indicates that the combination of parameters under that simulation condition is more likely to lead to higher pollutant emissions from the hybrid vehicle.

[0038] Specifically, for each simulation condition, the operating data under that simulation condition is analyzed with the emission baseline data obtained in advance through engine bench tests to assess the correlation between the engine operating conditions under that simulation condition and high emission areas, thereby determining the risk level of pollutant emissions from hybrid vehicles under that simulation condition.

[0039] It should be noted that the initial risk level of pollutant emissions from the hybrid vehicle under various simulation conditions, determined based on data from different operating conditions, can be used. After inputting each simulation condition into the corresponding vehicle simulation model, the conversion efficiency of the aftertreatment device in the hybrid vehicle under each simulation condition can be obtained. The initial risk level is then corrected using the conversion efficiency to obtain the final risk level of pollutant emissions from the hybrid vehicle under each simulation condition. The aftertreatment device can be understood as a device that treats pollutants emitted by the engine. After the simulation, the temperature change curve of the aftertreatment device over time can be obtained. Based on the correlation between temperature and conversion efficiency, the initial conversion efficiency corresponding to each temperature can be determined. The average of these initial conversion efficiencies yields the final conversion efficiency. The conversion efficiency and the initial risk level are then input into the following formula to obtain the final risk level: Risk Level = Initial Risk Level × (1 - Conversion Efficiency). By using the aftertreatment conversion efficiency as intermediate information in the simulation output to correct the initial risk level, the final risk level is made closer to the actual exhaust emission level, improving the accuracy of the subsequently generated RDE verification scheme.

[0040] S104: Based on each level of risk, determine each candidate simulation condition from each simulation condition.

[0041] In this embodiment, candidate simulation conditions can be understood as simulation conditions whose risk level meets preset screening criteria, i.e., simulation conditions with high emission risk that require focused RDE verification. By screening candidate simulation conditions, limited verification resources can be concentrated on scenarios most likely to cause high emissions, avoiding wasting testing resources on low-risk operating conditions.

[0042] Specifically, for each risk level, it is determined whether the risk level exceeds a preset risk level threshold. If the risk level exceeds the preset risk level threshold, the simulation conditions corresponding to the risk level among all simulation conditions are identified as candidate simulation conditions. The preset risk level threshold can be set according to actual needs, such as the average risk level of all simulation conditions or a fixed percentile value. Through this method, this embodiment compares the risk level with the preset risk level threshold to filter out candidate simulation conditions with higher emission risks, effectively excluding simulation conditions with lower emission risks. This allows subsequent RDE verification to focus on high-risk scenarios, thereby improving the generation efficiency of the RDE verification scheme and reducing verification costs.

[0043] S105: Based on each candidate simulation condition, generate the RDE verification scheme for the hybrid electric vehicle.

[0044] In this embodiment, the RDE verification scheme refers to a verification plan that integrates various candidate simulation conditions. This RDE verification scheme specifies the specific boundaries and dimensional combinations that need to be verified. During subsequent testing, relevant personnel only need to execute the test cycle according to this RDE scheme to efficiently complete the targeted verification of the RDE emission risks of the hybrid vehicle.

[0045] This embodiment provides a method for generating an RDE verification scheme. It combines dimensional information corresponding to multiple preset dimensions affecting the RDE of a hybrid electric vehicle (HEV) into multiple simulation conditions, and inputs these conditions into a vehicle simulation model to obtain engine operating data under each simulation condition. Based on this, the risk level of pollutant emissions from the HEV under each simulation condition is determined according to the operating data. Candidate simulation conditions are then selected from the multiple simulation conditions based on each risk level, thereby generating an RDE verification scheme. This allows for early-stage simulation-based proactive assessment of emission risk under different combinations of parameter variables, and the generation of RDE verification schemes accordingly. This improves the efficiency of RDE verification scheme generation and ensures that the generated RDE verification schemes are targeted and comprehensive.

[0046] refer to Figure 2 , Figure 2 This is a flowchart illustrating another method for generating an RDE verification scheme provided in this embodiment. The method for generating an RDE verification scheme provided in this embodiment includes the following steps: S201: Define multiple simulation conditions.

[0047] S202: Input each simulation condition into the corresponding vehicle simulation model of the hybrid vehicle to obtain the operating data of the engine in the hybrid vehicle under each simulation condition.

[0048] Regarding steps S201 and S202, steps S201 and S202 can be referred to in step S101 and S102 respectively, and will not be repeated here in this embodiment.

[0049] S203: For each operating condition data point, generate an engine operating condition map corresponding to the engine based on the operating condition data.

[0050] S204: Obtain the benchmark operating condition map corresponding to the engine obtained from the preliminary test. The benchmark operating condition map includes multiple benchmark correspondences.

[0051] S205: Based on the engine operating condition map and the baseline operating condition map, determine the target emission rate corresponding to each scatter point in the engine operating condition.

[0052] S206: Based on each target emission rate, determine the risk level of pollutant emissions from hybrid vehicles under the simulation conditions corresponding to the operating data.

[0053] S207: Based on each level of risk, determine each candidate simulation condition from each simulation condition.

[0054] Regarding steps S203 to S207 above, the engine operating condition map includes multiple scatter points, each representing the correspondence between engine speed and engine torque. In other words, the engine operating condition map can be understood as a map formed by converting the speed-torque time-series data generated during engine operation in the simulation into a set of scatter points on the speed-torque plane.

[0055] A baseline emission profile is a high-resolution emission profile obtained in advance through engine bench testing; it can also be called a raw emission profile or original emission profile. This baseline emission profile uses contour lines to mark the baseline emission rates of pollutants (such as NOx and PN particulate matter) under different baseline speed-torque conditions. The contour line format means that points with the same baseline emission rate are connected by curves on the speed-torque plane, forming an effect similar to contour lines on a topographic map, thus visually displaying the distribution of emission rates across the entire speed-torque range. The baseline emission profile contains multiple baseline correspondences, each representing the relationship between the engine's baseline speed, baseline torque, and the baseline emission rate of the pollutants.

[0056] Specifically, for the operating data under each simulation condition, time-series data showing the engine's speed-torque variation over time throughout the entire simulation are extracted from the operating data. Since the simulation output is time-series data sampled at a fixed simulation step size (e.g., 0.01 seconds), a single simulation may generate thousands or even tens of thousands of data points. The speed and torque values ​​at each moment in the time-series data are mapped to a scatter point on the speed-torque plane, and all scatter points constitute the engine operating condition map for that simulation condition.

[0057] To obtain a baseline operating condition graph, the engine under test was mounted on a dynamometer during engine bench testing. Steady-state or transient emission tests were conducted at different speeds and torque points. Emission detection equipment was used to obtain baseline emission rate data for pollutants such as NOx and PN at each operating point. These test data were then interpolated and fitted to form a baseline operating condition graph with speed as the horizontal axis, torque as the vertical axis, and emission rates as contour lines. It should be noted that the baseline operating condition graph was obtained through bench testing of a specific engine model and reflects the inherent emission characteristics of that engine; it is unrelated to vehicle-level control strategies.

[0058] After obtaining the engine operating condition map and the baseline operating condition map, each scatter point (speed, torque) in the engine operating condition map is mapped onto the baseline operating condition map, as shown in Figure 4. Since the coordinates (speed, torque) of the scatter points in the engine operating condition map are consistent with the coordinate system of the baseline operating condition map (both are in the speed-torque plane), they can be directly spatially superimposed. For each scatter point, the baseline emission rate of the pollutant corresponding to that scatter point location is obtained from the contour data of the baseline operating condition map by looking up a table or interpolation calculation (such as bilinear interpolation), and this is used as the target emission rate. For example, if the coordinates of a scatter point are (speed = 2000 rpm, torque = 150 Nm), and the baseline NOx emission rate for that location is found to be 350 ppm in the baseline operating condition map, then the target emission rate for that scatter point is 350 ppm. After performing the above operation on all scatter points in the engine operating condition map, the target emission rate corresponding to each scatter point can be obtained.

[0059] After obtaining the target emission rate corresponding to each scatter point in the engine operating condition map, the risk level of pollutant emissions from the hybrid vehicle under the simulation conditions is calculated based on each target emission rate using a preset risk assessment algorithm.

[0060] In this embodiment, by generating an engine operating condition map with multiple scattered points for each operating condition data point and obtaining a baseline operating condition map obtained in advance through bench testing, the target emission rate corresponding to each scattered point is determined based on the engine operating condition map and the baseline operating condition map. Then, the risk level is determined based on each target emission rate. This allows the simulation-obtained engine operating condition data to be correlated with the emission baseline data obtained from bench testing, thus realizing the assessment of the risk level of pollutants emitted by hybrid electric vehicles under each simulation condition and providing reliable data support for subsequent screening of high-risk scenarios.

[0061] In one embodiment, step S206 specifically includes: Based on each target emission rate, the target scatter points are determined from the engine operating condition map; Determine the total number of the first scatter points of all target scatter points and the total number of the second scatter points of all scatter points in the engine operating condition map; Determine the first ratio between the total number of the first scatter points and the total number of the second scatter points; The first ratio is determined as the risk level of pollutant emissions from hybrid vehicles under the simulated conditions corresponding to the operating data.

[0062] The target emission rate corresponding to the target scatter plot is greater than the preset emission rate threshold. The preset emission rate threshold can be understood as the emission rate critical value used to determine whether the engine operating point is in the high emission zone. For example, the preset emission rate threshold for pollutant NOx can be set to 400 ppm.

[0063] Specifically, each scatter point in the engine operating condition graph is traversed, and the target emission rate corresponding to that scatter point is compared with a preset emission rate threshold. Scatter points whose target emission rate is greater than the preset emission rate threshold are identified as target scatter points. The number of all target scatter points is counted to obtain the first total number of scatter points N_high. At the same time, the number of all scatter points in the engine operating condition graph is counted to obtain the second total number of scatter points N_total. A first ratio R = N_high / N_total is calculated, and this first ratio R is determined as the risk level of pollutants from hybrid vehicles under a simulation condition. This first ratio reflects the proportion of engine operating points falling into the high emission zone; the larger the ratio, the higher the emission risk.

[0064] For example, in a certain simulation, the engine operating condition map contained 5000 scatter points (N_total=5000), of which 2100 scatter points (N_high=2100) had a target emission rate exceeding the preset emission rate threshold of 400ppm. Therefore, the risk level R = 2100 / 5000 = 0.42, meaning that 42% of the engine operating points were in the high emission region. This value intuitively reflects the risk level of pollutant emissions from hybrid vehicles under the conditions of this simulation.

[0065] In this embodiment, by identifying target scatter points with a target emission rate greater than a preset emission rate threshold from the engine operating condition map, calculating the first ratio between the total number of first scatter points of the target scatter points and the total number of second scatter points of all scatter points, and determining the first ratio as the risk level, an assessment of risk level based on proportion is achieved. The calculation is simple and easy to compare between different simulation conditions, thus providing a basis for subsequent screening of high-risk scenarios.

[0066] In another embodiment, step S206 specifically includes: Based on the operating condition data, determine the duration of engine operation at each scatter point in the engine operating condition map. For each scatter point in the engine operating condition map, the emission contribution of the scatter point is determined based on the corresponding operating duration and target emission rate. The total emission contribution of the engine is obtained by summing up the emission contributions corresponding to all scatter points in the engine operating condition graph. Based on the total emission contribution, the risk level of pollutant emissions from hybrid vehicles under the simulation conditions corresponding to the operating data is determined.

[0067] The operating duration refers to the length of time the engine continuously operates near a specific point (operating condition point) in the engine operating condition map. Since the simulation output is time-series data sampled at a fixed step size, each point corresponds to one or more time steps. The operating duration can be obtained by multiplying the number of time-series data points near that point by the simulation step size. For example, if the simulation step size is 0.01 seconds, and there are 50 consecutive data points near a certain point, then the operating duration corresponding to that point is 50 × 0.01 = 0.5 seconds.

[0068] Emission contribution refers to the amount of pollutant emissions generated by an engine under the operating conditions represented by a certain scatter point during the corresponding operating duration of that scatter point.

[0069] Specifically, for each scatter point in the engine operating condition map, based on the statistical mapping of the operating condition data to the number of data points within a preset neighborhood of that scatter point, the number of data points is multiplied by the simulation sampling step size (e.g., 0.01 seconds) to obtain the duration of engine operation near the operating condition point represented by that scatter point.

[0070] For each scatter point in the engine operating condition map, the corresponding operating duration is calculated along with the target emission rate found in the baseline operating condition map to determine the emission contribution of that scatter point. The total emission contribution is obtained by summing the emission contributions of all scatter points in the engine operating condition map. This total emission contribution reflects the cumulative emissions of pollutants generated by the engine throughout the entire simulation operation, taking into account both the emission rate at each operating point and the engine's residence time at each operating point. Finally, based on the total emission contribution, the risk level of pollutant emissions from the hybrid vehicle under the simulation conditions corresponding to this operating condition data is determined.

[0071] By combining the target emission rate and operating duration corresponding to each scattered point, this embodiment accumulates the total emission contribution of the engine and determines the risk level accordingly. This reflects the impact of the engine's residence time at different operating points on the cumulative emission risk, avoiding the assessment bias caused by only counting the proportion of scattered points and ignoring the time factor, thereby improving the accuracy of assessing the emission pollutant risk of hybrid vehicles.

[0072] In the above, based on the operating duration and target emission rate corresponding to the scatter points, the emission contribution corresponding to each scatter point is determined, including: Determine the first product between the operating duration corresponding to the scatter point and the target emission rate, and use the first product to determine the emission contribution corresponding to the scatter point.

[0073] Based on the total emission contribution, the risk level of pollutants from hybrid vehicles under the simulation conditions corresponding to the operating data is determined, including: Obtain the preset emission contribution threshold; Determine a second ratio between the total emission contribution and the preset emission contribution threshold; The second ratio is determined as the risk level of pollutant emissions from hybrid vehicles under the simulated conditions corresponding to the operating data.

[0074] The emission contribution can be expressed as: Emission contribution = Operating duration × Target emission rate. The risk level can be expressed as: Risk level = Total emission contribution / Preset emission contribution threshold.

[0075] In this embodiment, by determining the emission contribution as the first product of the running duration of the scatter points and the target emission rate, the emission contribution of each scatter point simultaneously reflects information from two dimensions: the emission rate level at that operating point and the engine's residence time at that operating point. This allows for a more precise differentiation of the severity of pollutant emissions at different operating points. By determining the risk level as the second ratio of the total emission contribution to the preset emission contribution threshold, the actual emission contribution of the engine can be intuitively measured relative to the allowable limit. This facilitates horizontal comparisons between different simulation conditions and provides a basis for screening high-risk candidate simulation conditions.

[0076] S208: Based on each candidate simulation condition, generate the RDE verification scheme corresponding to the hybrid electric vehicle.

[0077] In this embodiment, step S208 specifically includes: For each candidate simulation condition, based on the corresponding operating condition data, the cause type of pollutant emission risk of hybrid electric vehicles under the candidate simulation condition is determined; Based on the cause type, determine the RDE verification strategy corresponding to the candidate simulation conditions; The candidate simulation conditions and their corresponding RDE verification strategies are used to generate an RDE verification scheme for hybrid electric vehicles.

[0078] The causal type can be understood as a classification identifier of the engineering mechanism underlying the high emission risk of hybrid vehicles under candidate simulation conditions. Different causal types correspond to different causes of high emission risk. By classifying the causes of high emission risk, a basis can be provided for configuring differentiated verification strategies, enabling the verification scheme to not only identify high-risk scenarios but also the reasons for their occurrence.

[0079] RDE (Real-Time Detection) strategy refers to the focus of a verification scheme configured for high emission risks of a specific cause type. Different cause types correspond to different verification focuses.

[0080] Specifically, for each candidate simulation condition, key characteristic parameters that can reflect the causes of emission risks are extracted from the operating data corresponding to that candidate simulation condition, and the cause type of pollutant emission risk of hybrid vehicles under the candidate simulation conditions is determined based on the key characteristic parameters.

[0081] Based on the cause type, the corresponding RDE verification strategy is queried from the preset correspondence between cause types and RDE verification strategies, and the RDE verification strategy is determined as the RDE verification strategy corresponding to the candidate simulation conditions.

[0082] The various candidate simulation conditions and their corresponding RDE verification strategies are integrated to form the final RDE verification scheme. This scheme not only clarifies the specific parameter combinations that need to be verified, but also specifies the verification focus for each verification scenario, enabling the testing team to perform verification in a targeted manner.

[0083] Through the above methods, this embodiment determines the cause type of pollutant emission risk based on the corresponding operating condition data for each candidate simulation condition, determines the corresponding RDE verification strategy according to the cause type, and integrates the candidate simulation conditions and their corresponding RDE verification strategies into an RDE verification scheme. This achieves a complete closed loop from risk identification to mechanism analysis to verification strategy configuration, so that the final RDE verification scheme can not only cover high-risk scenarios, but also configure differentiated verification focuses for the causes of different high-risk scenarios, thereby improving the effectiveness of RDE verification.

[0084] In the above, based on the operating condition data corresponding to the candidate simulation conditions, the causal types of pollutant emission risks of hybrid vehicles under the candidate simulation conditions are determined, including: The engine's first start time, total engine running time, and number of engine start-stop cycles are determined from the operating condition data corresponding to the candidate simulation conditions. Based on the initial startup time, total running time, and number of starts and stops, target rules that match the initial startup time, total running time, and number of starts and stops are determined from the preset rule set; Based on the target rule, the cause type corresponding to the target rule is determined from the first association relationship. The first association relationship stores multiple sets of correspondences between preset rules and cause types. The cause type corresponding to the target rule is determined as the cause type of pollutant emission risk of hybrid vehicles under candidate simulation conditions.

[0085] Based on the cause type, determine the RDE verification strategy corresponding to the candidate simulation conditions, including: Based on the cause type, the RDE verification strategy corresponding to the cause type is determined from the second association relationship. The second association relationship stores the correspondence between multiple cause types and RDE verification strategies. The RDE verification strategy corresponding to the cause type is determined as the RDE verification strategy corresponding to the candidate simulation conditions.

[0086] The initial start-up time refers to the moment when the engine starts running from a stopped state during a simulation run. The timing of the initial start-up time directly affects the cold start emission risk.

[0087] Total running time refers to the cumulative running time of the engine throughout the entire simulation process.

[0088] The number of start-stop cycles refers to the number of start-stop cycles the engine completes during the entire simulation process. The more start-stop cycles, the more transient emissions (such as emissions when the catalytic converter is not ignited) accumulate during each engine start.

[0089] A preset rule set can be understood as a pre-established set of rules used to determine the cause type of emission risk based on engine operating characteristic parameters. The preset rule set stores multiple sets of preset rules, each defining the condition range corresponding to the first start time, total running time, and number of start-stop cycles. By matching the target rules, the operating characteristics of candidate simulation conditions can be mapped to the corresponding cause type.

[0090] Specifically, for each candidate simulation condition, the moment when the engine first switches from the shutdown state to the running state is extracted from the corresponding operating condition data (i.e., engine running sequence data) as the first start time; the cumulative time the engine is in the running state throughout the entire simulation process is counted as the total running time; and the number of complete cycles from shutdown to start and then back to shutdown during the entire simulation process is counted as the start-stop count.

[0091] The initial start time of the candidate simulation conditions is compared with the condition range of the initial start time in each group of preset rules in the preset rule set. The total running time is compared with the condition range of the total running time in each group of preset rules in the preset rule set. The number of start-stops is compared with the condition range of the number of start-stops in each group of preset rules in the preset rule set. The preset rule that simultaneously satisfies the three conditions of initial start time, total running time, and number of start-stops is determined as the target rule.

[0092] After obtaining the target rule, the first association relationship is queried using the target rule, and the cause type corresponding to the target rule is determined as the cause type of pollutant emission risk of hybrid vehicles under candidate simulation conditions.

[0093] After obtaining the cause type of emission risk, the second correlation is queried using the cause type to determine the RDE verification strategy corresponding to the cause type as the RDE verification strategy corresponding to the candidate simulation condition. For example, when the cause type is cold start type, the corresponding RDE verification strategy focuses on cold start emission verification under low temperature environment, paying attention to the emission control during the catalyst ignition time and engine warm-up stage.

[0094] Through the above methods, this embodiment extracts the engine's first start time, total running time, and number of start-stop cycles from the operating condition data corresponding to the candidate simulation conditions. Based on the first start time, total running time, and number of start-stop cycles, it matches target rules from a preset rule set. The cause type corresponding to the target rule is determined through a first correlation relationship, and the RDE verification strategy corresponding to the cause type is determined through a second correlation relationship. This realizes the automatic classification of emission risk causes and the configuration of differentiated verification strategies based on engine operating characteristic parameters. This enables the final RDE verification scheme to focus on the corresponding verification priorities of verification strategies for different cause types, thereby improving the effectiveness of RDE verification.

[0095] This embodiment provides a method for generating an RDE verification scheme. It combines dimensional information corresponding to multiple preset dimensions affecting the RDE of a hybrid electric vehicle (HEV) into multiple simulation conditions, and inputs these conditions into a vehicle simulation model to obtain engine operating data under each simulation condition. Based on this, the risk level of pollutant emissions from the HEV under each simulation condition is determined according to the operating data. Candidate simulation conditions are then selected from the multiple simulation conditions based on each risk level, thereby generating an RDE verification scheme. This allows for early-stage simulation-based proactive assessment of emission risk under different combinations of parameter variables, and the generation of RDE verification schemes accordingly. This improves the efficiency of RDE verification scheme generation and ensures that the generated RDE verification schemes are targeted and comprehensive.

[0096] The following is an example for reference. Figure 3 The following is a detailed description of the entire RDE verification scheme generation process: Step S1: First, build a high-fidelity simulation platform in the simulation computer.

[0097] Physical Model Building: In the GT-SUITE software environment, a complete forward physical model is built based on the actual parameters of the hybrid vehicle, including the engine, drive motor, generator, power battery, final drive, and overall vehicle dynamics. The engine model requires input of its actual universal characteristic data and fuel consumption / emissions MAP; the battery model requires calibration of its open-circuit voltage-internal resistance-state of charge (SOC) characteristic curves. This model is used to simulate the vehicle's physical response after receiving drive commands.

[0098] Control Model Construction: In the MATLAB / Simulink environment, accurately reproduce the core software logic of the vehicle's upper-level energy management strategy and lower-level controllers (VCU, ECU, BMS). The focus is on implementing parameterized interfaces for energy management modes. For example, the pure electric priority mode is parameterized as follows: when SOC > 15%, the engine is prohibited from starting. The intelligent hybrid mode is parameterized as follows: engine start / stop is determined by looking up a table based on vehicle speed, required power, and SOC.

[0099] Model Coupling: Through a defined communication interface (such as the FMI protocol based on TCP / IP), the control model in Simulink and the physical model in GT-SUITE exchange data in real time at a fixed simulation step size (such as 0.01 seconds), forming a closed-loop simulation environment at the hardware-in-the-loop (HIL) level.

[0100] Define the influencing factor matrix (i.e., the dimensional information corresponding to each preset dimension in the preset dimension set): Based on this simulation environment, define the combination of input variables that need to be traversed for verification to form the influencing factor matrix, for example: Technical status dimension: Energy management mode = [pure electric priority, fuel priority, intelligent hybrid]; Driving style = [economy, comfort, sport]; Initial SOC = [20%, 50%, 80%].

[0101] Environmental dimensions: Ambient temperature = [-7℃, 25℃, 35℃]; Altitude = [0m, 1300m, 2400m].

[0102] By iterating and combining the dimensional information corresponding to different preset dimensions in the influencing factor matrix, multiple simulation conditions are obtained.

[0103] Step S2: Perform batch simulations based on multiple simulation conditions.

[0104] Use script automation tools to iterate through all simulation conditions. For example, one simulation condition might be set as follows: [Energy Management Mode = "Intelligent Hybrid", Driving Style = "Sport", Initial SOC = 50%, Temperature = 35℃, Altitude = 2400m]. The control model will run according to the logic parameters for "Intelligent Hybrid" and "Sport" driving styles.

[0105] Initiate the simulation under these conditions. During the simulation, the control model dynamically outputs commands such as engine start / stop and motor torque distribution to the physical model for execution based on real-time vehicle speed, power demand, and SOC status.

[0106] After the simulation is completed, the engine full-condition timing data file (i.e., condition data) for this run is automatically recorded and output. The condition data includes at least: the engine speed-torque change curve over time in the entire baseline driving cycle, the time of the first engine start, the number of engine start-stop cycles and the total running time in this cycle.

[0107] Step S3: Regression analysis and risk screening of engine operating condition and baseline operating condition maps.

[0108] Data preprocessing: The engine speed-load time series data output from each simulation in step S2 are processed into a scatter set to form an engine operating condition map under each simulation condition.

[0109] Regression Comparison: Each engine operating condition map was spatially overlaid with the original NOx emission map (baseline operating condition map) of the engine model obtained in advance through engine bench testing. The original emission map clearly marked the NOx emission rate corresponding to different speed-torque regions in the form of contour lines.

[0110] Risk quantification and screening: Using image processing algorithms, the number and proportion of points in each overlay image where the engine operating condition falls into the NOx emission concentration >400ppm (high emission threshold, i.e., preset emission rate threshold) region are counted, and this proportion is used as the risk level of pollutant emissions from hybrid vehicles under simulation conditions.

[0111] All simulations were ranked by risk level, and simulation conditions with a risk level greater than a preset risk level threshold were selected as candidate simulation conditions. For example, it was found that the engine operating points of the combination [intelligent hybrid, sport, SOC=50%, 35℃, 0m] were located in the high emission zone more than 40% of the time, with a significantly higher risk ratio than other combinations. Therefore, it was marked as a high emission risk data group (i.e., candidate simulation conditions).

[0112] Step S4: Mechanism analysis and technical status extraction of risk scenarios.

[0113] For each candidate simulation condition, the engine's first start time, total running time, and number of start-stop cycles are extracted from its operating data. Based on a preset rule set, target rules are matched, and the cause type is determined through the first association relationship. For example, under a certain candidate simulation condition, if the engine's first start time is early (e.g., the engine starts within 5 seconds of the simulation starting) and the number of start-stop cycles is high (e.g., more than 8 start-stop cycles in one cycle), the cause type of cold start and frequent start-stop cycles is matched, indicating that the high emission risk in this scenario mainly stems from repeated emissions when the catalytic converter does not fully ignite.

[0114] Based on the cause type, the corresponding RDE verification strategy is determined through the second association relationship. For example, when the cause type is cold start and frequent start-stop, the corresponding verification strategy focuses on cold start emission verification under low temperature environment and emission verification under urban congestion conditions.

[0115] Step S5: Generation of RDE verification scheme.

[0116] Based on the selected candidate simulation conditions and their corresponding RDE verification strategies, an RDE verification scheme for the hybrid vehicle is generated.

[0117] For example: Verification scheme 1: Energy management mode = "intelligent hybrid", driving style = "sport", initial battery state of charge = 50%, temperature = 35℃, altitude = 0m, verification focus = high temperature and high torque emission verification.

[0118] Verification Scheme 2: Energy Management Mode = "Pure Electric Priority", Driving Style = "Economy", Initial Battery State of Charge = 20%, Temperature = -7℃, Altitude = 0m, Verification Focus = Low Temperature Cold Start Emission Verification.

[0119] Once the RDE verification scheme for this vehicle model is generated, the testing team only needs to execute these refined test cycles on the chassis dynamometer or on actual roads according to this scheme to efficiently complete the targeted verification of the RDE emission risks of this vehicle model.

[0120] refer to Figure 5 , Figure 5 This is a schematic diagram of a device for generating an RDE verification scheme according to an embodiment of this application. The device includes a determination module 10, a simulation module 20, and a generation module 30. The determination module 10 is used to determine multiple simulation conditions, each simulation condition including a combination of dimensional information corresponding to different preset dimensions in a preset dimension set, where the preset dimensions represent parameter variables affecting the RDE of a hybrid electric vehicle. The simulation module 20 is used to input each simulation condition into a vehicle simulation model corresponding to the hybrid electric vehicle to obtain the operating condition data of the engine in the hybrid electric vehicle under each simulation condition. The determination module 10 is also used to determine the risk level of pollutant emissions from the hybrid electric vehicle under each simulation condition based on the operating condition data. The determination module 10 is also used to determine candidate simulation conditions from the simulation conditions based on the risk levels. The generation module 30 is used to generate an RDE verification scheme corresponding to the hybrid electric vehicle based on the candidate simulation conditions.

[0121] In this embodiment, the determining module 10 is further configured to: For each of the operating condition data, an engine operating condition map is generated based on the operating condition data. The engine operating condition map includes multiple scatter points, and each scatter point represents the correspondence between the engine speed and the engine torque. Obtain the benchmark operating condition map corresponding to the engine obtained from the preliminary test. The benchmark operating condition map includes multiple benchmark correspondences. Each benchmark correspondence characterizes the correspondence between the engine's benchmark speed, benchmark torque, and benchmark emission rate of pollutants. Based on the engine operating condition map and the baseline operating condition map, the target emission rate corresponding to each scatter point in the engine operating condition is determined; Based on each of the target emission rates, the risk level of pollutant emissions from the hybrid vehicle under each of the simulation conditions is determined.

[0122] In this embodiment, the determining module 10 is further configured to: Based on each of the target emission rates, each target scatter point is determined from the engine operating condition map, and the target emission rate corresponding to the target scatter point is greater than a preset emission rate threshold. Determine the total number of first scattered points for all the target scattered points and the total number of second scattered points for all the scattered points in the engine operating condition map; Determine a first ratio between the total number of the first scatter points and the total number of the second scatter points; The first ratio is determined as the risk level of pollutant emissions from the hybrid vehicle under the simulation conditions corresponding to the operating data.

[0123] In this embodiment, the determining module 10 is further configured to: For each of the stated risk levels, determine whether the risk level is greater than a preset risk level threshold; When the risk level is greater than the preset risk level threshold, the simulation condition corresponding to the risk level among the various simulation conditions is determined as a candidate simulation condition.

[0124] In this embodiment, the generation module 30 is further configured to: For each candidate simulation condition, based on the operating condition data corresponding to the candidate simulation condition, the cause type of pollutant emission risk of the hybrid vehicle under the candidate simulation condition is determined; Based on the cause type, determine the RDE verification strategy corresponding to the candidate simulation conditions; The candidate simulation conditions and their corresponding RDE verification strategies are used to generate the RDE verification scheme for the hybrid electric vehicle.

[0125] In this embodiment, the generation module 30 is further configured to: The engine's first start time, total engine operating time, and number of engine start-stop cycles are determined from the operating condition data corresponding to the candidate simulation conditions. Based on the initial startup time, the total running time, and the number of start-stops, target rules that match the initial startup time, the total running time, and the number of start-stops are determined from a preset rule set; Based on the target rule, the cause type corresponding to the target rule is determined from the first association relationship, wherein the first association relationship stores multiple sets of preset rules and the correspondence between the cause type; The cause type corresponding to the target rule is determined as the cause type of pollutant emission risk of the hybrid vehicle under the candidate simulation conditions; Based on the cause type, the RDE verification strategy corresponding to the cause type is determined from the second association relationship. The second association relationship stores multiple sets of correspondences between the cause type and the RDE verification strategy. The RDE verification strategy corresponding to the cause type is determined as the RDE verification strategy corresponding to the candidate simulation conditions.

[0126] In this embodiment, the determining module 10 is further configured to: Obtain the dimension information corresponding to each preset dimension in the preset dimension set; wherein, the preset dimension set includes state dimension and environment dimension, the state dimension includes at least one of energy management mode, driving style, and initial battery state of charge, and the environment dimension includes at least one of ambient temperature and altitude; The dimension information corresponding to different preset dimensions in the preset dimension set is traversed and combined to determine each simulation condition.

[0127] This embodiment provides an apparatus for generating a Reliable Detection and Evaluation (RDE) verification scheme. It combines dimensional information corresponding to multiple preset dimensions affecting the RDE of a hybrid electric vehicle (HEV) into multiple simulation conditions, and inputs these conditions into a vehicle simulation model to obtain engine operating data under each simulation condition. Based on this, the risk level of pollutant emissions from the HEV under each simulation condition is determined according to the operating data. Candidate simulation conditions are then selected from the multiple simulation conditions based on each risk level, thereby generating an RDE verification scheme. This allows for early-stage simulation-based proactive assessment of emission risk under different combinations of parameter variables, and the generation of RDE verification schemes accordingly. This improves the efficiency of RDE verification scheme generation and ensures that the generated RDE verification schemes are targeted and comprehensive.

[0128] refer to Figure 6 As shown, Figure 6This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device 600 in this embodiment may include: at least one processor 601, a memory 602, at least one network interface 604, and other user interfaces 603. The various components in the electronic device 600 are coupled together via a bus system 605. It is understood that the bus system 605 is used to implement communication between these components. In addition to a data bus, the bus system 605 also includes a power bus, a control bus, and a status signal bus. However, for clarity, all buses are referred to as bus system 605.

[0129] The user interface 603 may include a display, keyboard, or clicking device (e.g., mouse, trackball, touchpad, or touchscreen).

[0130] It is understood that the memory 602 in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 602 described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0131] In some implementations, memory 602 stores elements, executable units or data structures, or subsets thereof, or extended sets thereof: operating system 6021 and application program 6022.

[0132] The operating system 6021 includes various system programs, such as a framework layer, a core library layer, and a driver layer, used to implement various basic business functions and handle hardware-based tasks. The application program 6022 includes various applications, such as a media player and a browser, used to implement various application functions. Programs implementing the methods of the embodiments of this application can be included in application program 6022.

[0133] In this embodiment of the application, the processor 601 executes the methods provided in each method embodiment by calling the program or instructions stored in the memory 602, specifically the program or instructions stored in the application program 6022.

[0134] The methods disclosed in the embodiments of this application can be applied to or implemented by processor 601. Processor 601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in processor 601. The processor 601 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or can be executed by a combination of hardware and software units in the decoding processor. The software units may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 602. Processor 601 reads the information in memory 602 and completes the above method in conjunction with its hardware.

[0135] It is understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described herein, or combinations thereof.

[0136] For software implementation, the techniques described herein can be implemented by units that perform the functions described herein. The software code can be stored in memory and executed by a processor. The memory can be implemented in the processor or external to the processor.

[0137] This application also provides a storage medium (computer-readable storage medium). This storage medium stores one or more programs. The storage medium may include volatile memory, such as random access memory; it may also include non-volatile memory, such as read-only memory, flash memory, hard disk, or solid-state drive; and it may also include combinations of the above types of memory.

[0138] When a storage medium contains one or more programs that can be executed by one or more processors, and when the storage medium is used in an electronic device, the method described above for execution in the electronic device can be implemented. The processor executes the electronic device program stored in the memory to implement the method described above for execution in the electronic device.

[0139] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0140] It should be noted that the terms "one implementation," "embodiment," "exemplary embodiment," and "some embodiments" used in the specification indicate that the described embodiment may include a specific feature, structure, or characteristic, but not every embodiment necessarily includes that specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a specific feature, structure, or characteristic is described in connection with an embodiment, implementing such a feature, structure, or characteristic in conjunction with other embodiments, whether explicitly described or not, is within the knowledge scope of those skilled in the art.

[0141] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, or article that comprises a list of elements, or not only those elements, but also other elements not expressly listed, or elements inherent to such a process, method, or article. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, or article that includes said element.

[0142] The above embodiments are merely preferred embodiments provided to fully illustrate this application, and the scope of protection of this application is not limited thereto. Equivalent substitutions or modifications made by those skilled in the art based on this application are all within the scope of protection of this application.

Claims

1. A method for generating an RDE verification scheme, characterized in that, include: Multiple simulation conditions are determined, and each simulation condition includes a combination of dimensional information corresponding to different preset dimensions in a preset dimension set. The preset dimensions represent the parameter variables that affect the RDE of hybrid electric vehicles. Each of the simulation conditions is input into the vehicle simulation model corresponding to the hybrid vehicle to obtain the operating data of the engine in the hybrid vehicle under each of the simulation conditions. Based on the data from each of the aforementioned operating conditions, the risk level of pollutant emissions from the hybrid vehicle under each of the aforementioned simulation conditions is determined; Based on the respective risk levels, candidate simulation conditions are determined from the respective simulation conditions; Based on each of the candidate simulation conditions, an RDE verification scheme corresponding to the hybrid electric vehicle is generated.

2. The method for generating the RDE verification scheme according to claim 1, characterized in that, The step of determining the risk level of pollutant emissions from the hybrid vehicle under each of the simulation conditions based on the various operating condition data includes: For each of the operating condition data, an engine operating condition map is generated based on the operating condition data. The engine operating condition map includes multiple scatter points, and each scatter point represents the correspondence between the engine speed and the engine torque. Obtain the benchmark operating condition map corresponding to the engine obtained from the preliminary test. The benchmark operating condition map includes multiple benchmark correspondences. Each benchmark correspondence characterizes the correspondence between the engine's benchmark speed, benchmark torque, and benchmark emission rate of pollutants. Based on the engine operating condition map and the baseline operating condition map, the target emission rate corresponding to each scatter point in the engine operating condition is determined; Based on each of the target emission rates, the risk level of pollutant emissions from the hybrid vehicle under each of the simulation conditions is determined.

3. The method for generating the RDE verification scheme according to claim 2, characterized in that, The determination of the risk level of pollutant emissions from the hybrid vehicle under each of the aforementioned target emission rates under each of the aforementioned simulation conditions includes: Based on each of the target emission rates, each target scatter point is determined from the engine operating condition map, and the target emission rate corresponding to the target scatter point is greater than a preset emission rate threshold. Determine the total number of first scattered points for all the target scattered points and the total number of second scattered points for all the scattered points in the engine operating condition map; Determine a first ratio between the total number of the first scatter points and the total number of the second scatter points; The first ratio is determined as the risk level of pollutant emissions from the hybrid vehicle under the simulation conditions corresponding to the operating data.

4. The method for generating an RDE verification scheme according to claim 1, characterized in that, The process of determining candidate simulation conditions from each of the simulation conditions based on each of the aforementioned risk levels includes: For each of the stated risk levels, determine whether the risk level is greater than a preset risk level threshold; When the risk level is greater than the preset risk level threshold, the simulation condition corresponding to the risk level among the various simulation conditions is determined as a candidate simulation condition.

5. The method for generating an RDE verification scheme according to claim 1, characterized in that, The step of generating an RDE verification scheme for the hybrid vehicle based on each of the candidate simulation conditions includes: For each candidate simulation condition, based on the operating condition data corresponding to the candidate simulation condition, the cause type of pollutant emission risk of the hybrid vehicle under the candidate simulation condition is determined; Based on the cause type, determine the RDE verification strategy corresponding to the candidate simulation conditions; The candidate simulation conditions and their corresponding RDE verification strategies are used to generate the RDE verification scheme for the hybrid electric vehicle.

6. The method for generating the RDE verification scheme according to claim 5, characterized in that, The determination of the cause type of pollutant emission risk of the hybrid vehicle under the candidate simulation conditions based on the operating condition data corresponding to the candidate simulation conditions includes: The engine's first start time, total engine running time, and number of engine start-stop cycles are determined from the operating condition data corresponding to the candidate simulation conditions. Based on the initial startup time, the total running time, and the number of start-stops, target rules that match the initial startup time, the total running time, and the number of start-stops are determined from a preset rule set; Based on the target rule, the cause type corresponding to the target rule is determined from the first association relationship, wherein the first association relationship stores multiple sets of preset rules and the correspondence between the cause type; The cause type corresponding to the target rule is determined as the cause type of pollutant emission risk of the hybrid vehicle under the candidate simulation conditions; The step of determining the RDE verification strategy corresponding to the candidate simulation conditions based on the cause type includes: Based on the cause type, the RDE verification strategy corresponding to the cause type is determined from the second association relationship. The second association relationship stores multiple sets of correspondences between the cause type and the RDE verification strategy. The RDE verification strategy corresponding to the cause type is determined as the RDE verification strategy corresponding to the candidate simulation conditions.

7. The method for generating an RDE verification scheme according to claim 1, characterized in that, The determination of multiple simulation conditions includes: Obtain the dimension information corresponding to each preset dimension in the preset dimension set; wherein, the preset dimension set includes state dimension and environment dimension, the state dimension includes at least one of energy management mode, driving style, and initial battery state of charge, and the environment dimension includes at least one of ambient temperature and altitude; The dimension information corresponding to different preset dimensions in the preset dimension set is traversed and combined to determine each simulation condition.

8. An apparatus for generating an RDE verification scheme, characterized in that, include: The determination module is used to determine multiple simulation conditions, each of which includes a combination of dimensional information corresponding to different preset dimensions in a preset dimension set, wherein the preset dimensions characterize the parameter variables that affect the RDE of hybrid electric vehicles; The simulation module is used to input each of the simulation conditions into the vehicle simulation model corresponding to the hybrid vehicle, so as to obtain the operating condition data of the engine in the hybrid vehicle under each of the simulation conditions. The determining module is further configured to determine the risk level of pollutant emissions from the hybrid vehicle under each of the simulation conditions based on the various operating condition data. The determining module is further configured to determine each candidate simulation condition from each simulation condition based on each of the risk levels. The generation module is used to generate the RDE verification scheme corresponding to the hybrid vehicle based on each of the candidate simulation conditions.

9. An electronic device, characterized in that, include: A processor and a memory, wherein the processor is configured to execute a program for generating an RDE verification scheme stored in the memory, to implement the method for generating an RDE verification scheme according to any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium stores one or more programs, which can be executed by one or more processors to implement the method for generating the RDE verification scheme according to any one of claims 1 to 7.