Emergency braking data processing method, storage medium, electronic equipment and commercial vehicle

Abstract

The invention discloses an emergency braking data processing method, a storage medium, electronic equipment and a commercial vehicle, and the method comprises the steps: responding to the triggering of an emergency braking system function, and determining a time range of collecting braking event data according to a braking danger level; obtaining vehicle data in the time range, wherein the vehicle data comprises data used for constructing a braking event scene and data used for analyzing a braking event problem; and storing data used for constructing the braking event scene and data used for analyzing the braking event problem. According to the method, more detailed and comprehensive data support is provided for restoration of the braking event scene and analysis of the emergency braking system false triggering reason, and then an important basis is provided for optimization and improvement of a follow-up system, so that the probability of system false triggering is reduced, and the driving safety of the vehicle is improved.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to a method for processing emergency braking data, a non-volatile readable storage medium, an electronic device and a commercial vehicle. Background Art

[0002] With the continuous development of active safety technology in automobiles, the Automatic Emergency Braking System (AEBS) has become one of the key configurations to improve driving safety and has gradually become a standard configuration required by laws and regulations. However, the existing AEBS system still has some shortcomings in practical applications, especially when the system is triggered by mistake, which may cause the vehicle to brake suddenly, thus posing a safety hazard to the driver and passengers.

[0003] In the prior art, when the AEBS system is triggered, it can only simply record basic data inside the vehicle, such as braking status and vehicle speed. Although these data are helpful for post-event analysis to a certain extent, they cannot completely restore the full picture of the braking event. In particular, the existing AEBS systems generally lack image recording of the surrounding environment when the braking event occurs and accurate location information collection. This deficiency leads to the inability to quickly and accurately locate the root cause of the problem when analyzing and dealing with false triggering problems, which in turn affects the effective improvement of the system. In addition, due to the lack of detailed scene data, it is difficult to provide reliable data support for further optimization of the AEBS system in the future. Summary of the invention

[0004] The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, one purpose of the present invention is to propose a method for processing emergency braking data, which provides more detailed and comprehensive data support for the restoration of braking event scenes and the analysis of the causes of false triggering of the emergency braking system, thereby providing an important basis for the optimization and improvement of subsequent systems, thereby helping to reduce the probability of false triggering of the system and improving the driving safety of the vehicle.

[0005] A second object of the present invention is to provide a non-volatile readable storage medium.

[0006] A third objective of the present invention is to provide an electronic device.

[0007] A fourth object of the present invention is to provide a commercial vehicle.

[0008] In order to achieve the above-mentioned purpose, the method for emergency braking data processing of the first aspect of the embodiment of the present invention includes: in response to the emergency braking system function being triggered, determining the time range for collecting braking event data according to the braking hazard level; acquiring vehicle data within the time range, the vehicle data including data for constructing braking event scenarios and data for analyzing braking event problems; and saving the data for constructing braking event scenarios and the data for analyzing braking event problems.

[0009] According to the method for processing emergency braking data in an embodiment of the present invention, by determining the time range for collecting braking event data based on the braking danger level when the emergency braking system function is triggered, the start and end times of data collection can be flexibly adjusted for events of different danger levels. This dynamic adjustment of the time range ensures that all important data related to the event can be fully captured at the critical moment of the event. By acquiring vehicle data within the time range, including surrounding environment data (such as image data, location information, etc.) used to construct the braking event scene and vehicle internal data (such as braking status, vehicle speed, etc.) used to analyze braking event problems, the system can fully record the situation when the braking event occurs. Therefore, the method of the present invention provides more detailed and comprehensive data support for the restoration of braking event scenes and the analysis of the causes of false triggering of the emergency braking system, and thus provides an important basis for the optimization and improvement of subsequent systems, thereby helping to reduce the probability of false triggering of the system and improving the driving safety of the vehicle.

[0010] In some embodiments, the braking risk level is determined based on braking deceleration. The greater the braking deceleration, the higher the braking risk level and the larger the time range for collecting braking event data.

[0011] In some embodiments, the time range includes the braking event triggering moment and a preset time period before and after the braking event triggering moment.

[0012] In some embodiments, determining the time range for collecting braking event data according to the braking risk level includes: when the braking deceleration a satisfies a<-3m / s 2 When the braking risk level is the first level, the time range is [T0-10s, T0+10s], where T0 is the triggering time of the braking event; or when the braking deceleration a satisfies -1m / s 2 >a>-3m / s 2 When the braking risk level is the second level, the time range is [T0-5s, T0+5s], and the risk level of the second level is lower than the risk level of the first level; or, when the braking deceleration a satisfies a>-1m / s 2When , the braking risk level is the third level, the time range is [T0-2s, T0+2s], and the risk level of the third level is lower than the risk level of the second level.

[0013] In some embodiments, the data used to construct a braking event scenario and the data used to analyze braking event problems include vehicle perception data, vehicle position information, emergency braking system function triggering time information, vehicle control commands, and vehicle status information.

[0014] In some embodiments, the method further includes: determining the target classification type existing in the saved data for constructing a braking event scenario and the data for analyzing braking event problems; and displaying an icon of the target classification type on a braking event record interface of a vehicle-mounted display device.

[0015] In some embodiments, the method also includes at least one of the following: after obtaining the data for constructing a braking event scenario and the data for analyzing a braking event problem, sending the data for constructing a braking event scenario and the data for analyzing a braking event problem to the cloud for backup; receiving an extraction instruction for extracting the vehicle data, and responding to the extraction instruction when the extraction instruction satisfies the extraction authority.

[0016] In order to achieve the above-mentioned purpose, the non-volatile readable storage medium of the second aspect of the embodiment of the present invention stores a computer program thereon, and is characterized in that when the computer program is executed, the method for emergency braking data processing described in the above embodiment is implemented.

[0017] According to the non-volatile readable storage medium of the embodiment of the present invention, by adopting the method of emergency braking data processing described in the above embodiment, more detailed and comprehensive data support is provided for the restoration of braking event scenes and the analysis of the causes of false triggering of the emergency braking system, thereby providing an important basis for the optimization and improvement of subsequent systems, thereby helping to reduce the probability of false triggering of the system and improving the driving safety of the vehicle.

[0018] In order to achieve the above-mentioned purpose, the electronic device of the embodiment of the third aspect of the present invention includes: at least one processor; a memory communicatively connected to the at least one processor; the memory stores a computer program executable by the at least one processor, and when the at least one processor executes the computer program, it implements the method for emergency braking data processing described in the above embodiment.

[0019] According to the electronic device of the embodiment of the present invention, at least one processor executes a computer program that implements the method of emergency braking data processing described in the above embodiment. When the emergency braking system function is triggered, the time range for collecting braking event data is determined based on the braking danger level, and the start and end time of data collection can be flexibly adjusted for events of different danger levels. This dynamic adjustment of the time range ensures that all important data related to the event can be fully captured at the critical moment of the event. By acquiring vehicle data within the time range, including surrounding environment data (such as image data, location information, etc.) used to construct the braking event scene and vehicle internal data (such as braking status, vehicle speed, etc.) used to analyze the braking event problem, the system can completely record the situation when the braking event occurs. Therefore, the electronic device of the present invention provides more detailed and comprehensive data support for the restoration of the braking event scene and the analysis of the cause of the false triggering of the emergency braking system, and then provides an important basis for the optimization and improvement of the subsequent system, thereby helping to reduce the probability of false triggering of the system and improving the driving safety of the vehicle.

[0020] In order to achieve the above-mentioned purpose, a commercial vehicle in an embodiment of the fourth aspect of the present invention includes the electronic device described in the above embodiment, or the commercial vehicle includes an emergency braking system and a controller, and the controller is connected to the emergency braking system for executing the method for emergency braking data processing described in the above embodiment.

[0021] According to the commercial vehicle of the embodiment of the present invention, by adopting the method of emergency braking data processing described in the above embodiment, when the emergency braking system function is triggered, the controller can dynamically determine the time range of data collection based on the braking hazard level, ensuring that all important data related to the event are fully captured at the critical moment of the event. These data include not only the surrounding environment data (such as image data, location information, etc.) used to construct the braking event scene, but also the vehicle internal data (such as braking status, vehicle speed, etc.) used to analyze the braking event problem. Through the comprehensive collection and preservation of these data, more detailed and comprehensive data support is provided for the restoration of the braking event scene and the analysis of the cause of the false triggering of the emergency braking system, thereby helping to reduce the probability of false triggering of the system and improving the driving safety of commercial vehicles. In addition, these detailed data also provide a solid data foundation for subsequent system optimization and improvement, so that commercial vehicles can continuously improve the performance of the emergency braking system through software upgrades and algorithm optimization, and adapt to more complex driving scenarios.

[0022] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The above and / or additional aspects and advantages of the present invention will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:

[0024] Figure 1 is a flowchart of a method for emergency brake data processing according to an embodiment of the present invention;

[0025] Figure 2 is a schematic diagram of a time range for collecting braking event data according to an embodiment of the present invention;

[0026] Figure 3 is a block diagram of an electronic device according to an embodiment of the present invention;

[0027] Figure 4 is a block diagram of a commercial vehicle according to one embodiment of the present invention;

[0028] Figure 5 is a block diagram of a commercial vehicle according to yet another embodiment of the present invention.

[0029] Reference numerals:

[0030] Commercial vehicles 100;

[0031] Electronic device 1; Emergency brake system 2; Controller 3;

[0032] Processor 11; Memory 12. DETAILED DESCRIPTION

[0033] Embodiments of the present invention are described in detail below. The embodiments described with reference to the accompanying drawings are exemplary. Embodiments of the present invention are described in detail below.

[0034] Reference below Figure 1 A method for processing emergency braking data according to an embodiment of the present invention is described.

[0035] Figure 1 is a flow chart of a method for processing emergency brake data according to an embodiment of the present invention. Figure 1 As shown, the method for processing emergency braking data according to the embodiment of the present invention includes steps S1-S3.

[0036] S1, in response to the emergency braking system function being triggered, determining a time range for collecting braking event data according to a braking risk level.

[0037] In some embodiments, the emergency braking system function may be a function of an automatic emergency braking system (AEBS) for automatically performing braking operations when a potential collision risk is detected. Specifically, AEBS can use sensors (such as radars, cameras, etc.) to monitor the vehicle's surroundings in real time, and when a dangerous situation where a collision may occur is detected, the system can automatically start the braking process. Therefore, the main function of AEBS is to reduce the probability of accidents or mitigate the consequences of accidents. By sensing in advance and automatically intervening in braking, it can help the driver respond quickly in an emergency, reduce the driver's burden, and improve driving safety.

[0038] In some embodiments, the emergency braking system function can be triggered in two situations: normal triggering and abnormal triggering. Normal triggering can include the vehicle detecting an obstacle ahead and the distance to the obstacle is within a certain threshold, indicating that a collision may occur. Also, when the vehicle ahead decelerates sharply or stops suddenly, and the driver fails to take timely action, the emergency braking system senses the relative speed change and determines it as a potential collision risk.

[0039] In some embodiments, abnormal triggering may include sensor misjudgment, environmental interference, road type, roadside objects, complex traffic conditions, etc. Specifically, sensor misjudgment may refer to reflections, water accumulation or ice and snow reflections on the road surface, which may be mistaken by the system as obstacles, resulting in false triggering. Environmental interference may refer to the fact that under extreme weather conditions such as heavy rain, dense fog, and blizzards, the sensor may misjudge the distance or detect the wrong object, resulting in false triggering. Road type may refer to the fact that on a steep slope or sharp bend, the system may misjudge the distance and speed of the vehicle or obstacle in front due to limited vision or changes in road conditions, resulting in false triggering. Also, when passing through bridge joints or uneven road surfaces, the system may mistakenly believe that there is an obstacle in front, resulting in false triggering. Roadside objects may refer to stationary objects (such as stop signs, branches, roadside trash cans) close to the lane that may be mistakenly identified by the system as obstacles about to enter the lane, thereby triggering emergency braking. Complex traffic conditions may refer to the fact that on a multi-lane road, when driving side by side with a large truck or bus, the system may mistakenly believe that the vehicle in the adjacent lane is in the lane, triggering emergency braking.

[0040] Therefore, these false triggering situations show that although the emergency braking system plays an important role in improving driving safety, in complex actual environments, the system may still be disturbed by various factors and false triggering may occur. Therefore, in order to reduce the probability of false triggering, it is necessary to continuously optimize the system and comprehensively analyze and handle the false triggering situation.

[0041] In some embodiments, the braking risk level is a classification method for evaluating the urgency of emergency braking events. This classification can be based on a variety of factors, including but not limited to the distance between the vehicle and the obstacle, the vehicle speed, the road conditions, environmental factors, etc. According to different risk levels, the system can dynamically adjust the time range of data collection.

[0042] In some embodiments, the braking risk level can be designed with multiple risk levels (eg, high, medium, and low), corresponding to different data collection time ranges. For a high risk level, the system may collect data in a longer time range.

[0043] In some embodiments, the time range of the braking event data may refer to the data collection time period selected by the system before and after the braking event occurs. This time range includes a period of time before the event occurs and a period of time after the event occurs, and is used to fully capture the entire process of the event. For example, for events with a lower risk level, the system may only need to collect data for a short period of time, while for events with a high risk level, a longer period of data may be required to fully restore the entire event process. By determining a reasonable time range, it can be ensured that all important data before and after the event is recorded. This helps to more accurately restore the scene where the event occurred and conduct detailed analysis. Therefore, the selection of the time range helps to capture system status and environmental changes in the period before and after the event, thereby more effectively identifying the root cause of the problem.

[0044] S2, acquiring vehicle data within a time range, where the vehicle data includes data for constructing a braking event scenario and data for analyzing braking event problems.

[0045] In some embodiments, the data used to construct the braking event scene may include a record of the external environment during vehicle travel. For example, these data may include images taken by the front, side, and rear cameras of the vehicle, which may display other vehicles, pedestrians, road signs, and traffic signals. These data may also include distance and speed information of surrounding objects detected by a laser radar or millimeter wave radar. In addition, the data used to construct the braking event scene may also include GPS (Global Positioning System) data, which can provide the precise location when the event occurred. These data combined help to accurately restore the external environment when the braking event occurred and support a comprehensive analysis of the event.

[0046] In some embodiments, the data used to analyze the brake event problem may be the operating status of the vehicle to help understand the internal cause of the event, including the vehicle's brake status (such as brake pressure, brake pedal position), power system status (such as engine speed, torque output), ABS (anti-lock brake system) working status, and ECU (Electronic Control Unit) data related to vehicle control, etc. These data can help technicians analyze and identify the root cause of the problem, such as whether the brake system is working properly, whether the speed and position of the vehicle are appropriate, etc.

[0047] S3, saves data used to construct braking event scenarios and data used to analyze braking event problems.

[0048] In some embodiments, data used to construct braking event scenarios and data used to analyze braking event problems can be stored in non-volatile memory to ensure that the data can still be completely saved after the vehicle is powered off or restarted. For ease of management and access, the stored data can be placed in a dedicated folder or partition for easy management and retrieval. This classified storage method can avoid confusion with other vehicle data and ensure that relevant data of the triggering event can be quickly and accurately located and extracted. In addition, the data must include at least the video records of the last five emergency braking system function triggering events and related vehicle information. In this way, the most recent event data can be retrieved and analyzed at any time to help with problem diagnosis and system optimization.

[0049] In some embodiments, if the non-volatile memory does not have enough storage space to record new trigger event data, the system can overwrite the previous event data in chronological order. This means that the earliest recorded data will be replaced by the latest data. This "first in, first out" overwriting strategy ensures that the system always retains the most recent trigger event data, even if the storage space is limited, it can ensure that the latest data is not lost.

[0050] According to the method for processing emergency braking data in an embodiment of the present invention, by determining the time range for collecting braking event data based on the braking danger level when the emergency braking system function is triggered, the start and end times of data collection can be flexibly adjusted for events of different danger levels. This dynamic adjustment of the time range ensures that all important data related to the event can be fully captured at the critical moment of the event. By acquiring vehicle data within the time range, including surrounding environment data (such as image data, location information, etc.) used to construct the braking event scene and vehicle internal data (such as braking status, vehicle speed, etc.) used to analyze braking event problems, the system can fully record the situation when the braking event occurs. Therefore, the method of the present invention provides more detailed and comprehensive data support for the restoration of braking event scenes and the analysis of the causes of false triggering of the emergency braking system, and thus provides an important basis for the optimization and improvement of subsequent systems, thereby helping to reduce the probability of false triggering of the system and improving the driving safety of the vehicle.

[0051] In some embodiments, the braking risk level is determined based on the braking deceleration, which can be the rate of change of the vehicle's speed during braking, usually in meters per square second (m / s 2 ) is a critical parameter that directly reflects the braking strength of a vehicle. The greater the braking deceleration (i.e., the vehicle decelerates rapidly in a shorter period of time), the higher the risk that the vehicle may face. The higher the braking risk level, the larger the time range for collecting braking event data. This is to ensure that all important information related to the event can be fully captured in high-risk situations.

[0052] In some embodiments, the time range includes the braking event triggering moment and the preset time period before and after the braking event triggering moment. This means that the system not only records the data when the braking event occurs, but also collects data for a period of time before and after the event occurs, so as to fully cover the entire braking event process.

[0053] like Figure 2 As shown in the figure, the braking event triggering time is T0, the preset time before the braking event triggering time is delta0, and the preset time after the braking event triggering time is delta1. Then the vehicle data from T0-delta0 to T0+delta1 will be collected and recorded. By recording the vehicle data before the braking event is triggered, the system can capture the cause of emergency braking, such as changes in the road conditions ahead, the behavior of other vehicles, and the driver's operation. These data are very important for understanding the cause of the braking event. By recording the vehicle data after the braking event is triggered, it is helpful to analyze the results of emergency braking, such as whether the vehicle stops successfully, whether a collision occurs, and the reactions of the driver and the vehicle during this period. These data provide a reliable basis for post-analysis and system improvement.

[0054] In some embodiments, the time range for collecting braking event data is determined according to the braking risk level, including: when the braking deceleration a satisfies a<-3m / s 2 , it means that the vehicle is braking very urgently. In this case, the system classifies the braking risk level as the first level and sets a longer time range [T0-10s, T0+10s], where T0 is the triggering time of the braking event. This setting ensures that vehicle data within 20 seconds before and after the braking event is collected, providing comprehensive information for subsequent analysis.

[0055] Or, when the braking deceleration a satisfies -1m / s 2 >a>-3m / s 2 When the vehicle is in a moderate emergency braking state, the system divides the braking risk level into the second level, and the set time range is [T0-5s, T0+5s]. The second level of risk is lower than the first level of risk.

[0056] Or, when the braking deceleration a satisfies a>-1m / s 2 When , it means that the vehicle is performing light braking. In this case, the system divides the braking danger level into the third level, with a time range of [T0-2s, T0+2s]. The third level of danger is lower than the second level of danger. In other words, the 4-second period before and after the braking event is enough to capture the key points of the braking event, while avoiding unnecessary data storage and processing burden.

[0057] In some embodiments, the data used to construct a braking event scenario and the data used to analyze braking event problems include vehicle perception data, vehicle position information, emergency braking system function triggering time information, vehicle control commands, and vehicle status information.

[0058] Among them, vehicle perception data may include data types obtained by various sensors, such as image data of continuous frames of the camera, obstacle data recognized by the camera, obstacle data provided by radar sensors, lane line data where the vehicle is located, etc.

[0059] In some embodiments, the image data of continuous frames of the camera may refer to a sequence of images continuously captured by the vehicle-mounted camera at a certain frame rate (such as 30 frames per second or 60 frames per second) while the vehicle is driving. These image data are continuous and can be used to analyze changes in dynamic scenes. These image data are used to identify and track surrounding objects, pedestrians, traffic signs, etc. to help build a complete braking event scene.

[0060] In some embodiments, the obstacle data identified by the camera may refer to the ability of the camera to identify obstacles that may affect the driving of the vehicle from the captured image through image processing algorithms, such as vehicles, pedestrians, bicycles, obstacles, etc. in front. By identifying obstacles, the system can warn of potential dangerous situations in advance. If the camera identifies that an obstacle suddenly appears in the driving path, the system can trigger emergency braking or perform other emergency operations.

[0061] In some embodiments, radar sensors detect the distance, speed, and direction of surrounding objects by emitting and receiving electromagnetic waves. Unlike cameras, radars do not rely on light conditions, so they can still work effectively at night or in bad weather. Obstacle data provided by radar sensors can be used to detect high-speed moving objects, such as the closing speed and distance of other vehicles.

[0062] In some embodiments, obstacle data fusion can be generated by fusing obstacle data obtained by cameras and radar sensors to generate more accurate and reliable obstacle information. Fusion obstacle data can improve the system's perception accuracy in complex environments, such as scenes with large changes in light or multiple fast-moving objects. Through fusion technology, the system can better judge threats in the surrounding environment and make smarter decisions.

[0063] In some embodiments, the lane line data of the vehicle may refer to the lane line that the vehicle is currently in as identified by a camera. This includes the position and shape information of the left and right lane lines, which helps determine the position of the vehicle on the road. The lane line data can help the system understand the vehicle's driving trajectory, which is important for building accurate driving scenarios and restoring the specific position and direction of movement of the vehicle in braking event analysis.

[0064] In some embodiments, the vehicle location information may be the geographic location data of the vehicle at the time of the braking event obtained through GPS or other positioning systems, including the current map location, road information, etc. The location data can help locate the specific location of the event, and further analyze the external environment of the event in combination with the perception data. For example, understanding the road type (such as highways, urban roads) and surrounding geographical features when the event occurred can help determine whether the braking event is related to specific terrain or road conditions.

[0065] In some embodiments, the emergency braking system function triggering time information may be the specific moment when the emergency braking system function is triggered, including: year, month, day, hour, minute, and second. By accurately recording the triggering time, the system can clearly define the start and end time of data collection to ensure that the key moments before and after the braking event are fully covered. This is of great significance for the timeline analysis of the event and the reproduction of the response process.

[0066] In some embodiments, the vehicle control command may be a specific type of vehicle control command specifically used to adjust the deceleration of the vehicle during braking.

[0067] In some embodiments, the vehicle state information may include vehicle posture, vehicle speed, brake pedal state, steering system state, etc. Among them, the vehicle posture helps to determine the exact position of the vehicle on the road and its direction of travel. Vehicle speed is crucial to analyzing the dynamic behavior of the vehicle. In a braking event, the vehicle speed can help evaluate the braking effect and deceleration, and determine whether further intervention or optimization is needed. Brake pedal state information can be the current state of the brake pedal, including whether the pedal is depressed, the degree of depression, etc. This information helps to judge the driver's braking intention and actual braking behavior. Steering system state information can be the current state of the vehicle's steering system, including steering angle, steering force, etc. Steering system state information is used to understand the vehicle's handling. During braking, steering information can help analyze whether the vehicle is stable, whether there is slippage or loss of control. It helps to evaluate the coordination between the braking system and the steering system, as well as the vehicle behavior in complex driving scenarios.

[0068] In some embodiments, the method for emergency braking data processing further includes: determining the target classification type present in the data stored for constructing the braking event scenario and the data for analyzing the braking event problem. The target classification type may refer to different types of targets or objects identified in the collected vehicle data. The target classification may include pedestrians, other vehicles, traffic signs, traffic lights, etc. An icon of the target classification type is displayed on the braking event recording interface of the vehicle-mounted display device.

[0069] In some embodiments, the vehicle-mounted display device may be a display screen inside the vehicle, such as a touch screen on a center console or a dashboard display screen. The display device is used to provide real-time information and system feedback to the driver. The braking event record interface may be a specific interface in the vehicle-mounted display device, which is used to display information about braking events, including detailed records of events, analysis results, etc.

[0070] In some embodiments, the method for emergency braking data processing further includes at least one of the following: after acquiring data for constructing a braking event scenario and data for analyzing a braking event problem, the data for constructing a braking event scenario and data for analyzing a braking event problem are sent to the cloud for backup. Backing up data to the cloud ensures the security and durability of the data, and the data can still be recovered even in the event of damage or loss of the device. This also allows remote access and analysis, making it easier for technicians and R&D teams to further use and study the data.

[0071] In some embodiments, an extraction instruction for extracting vehicle data is received, and when the extraction instruction satisfies the extraction authority, the extraction instruction is responded to and a data extraction operation is performed. The data access authority control in this process ensures that only authorized personnel or systems can extract and access sensitive data, thereby effectively preventing unauthorized access. Such control measures can prevent data leakage, tampering or deletion, and protect the security and integrity of data.

[0072] In some embodiments, the system will use the collected data for playback, and can analyze the root cause of the system's false triggering problem. This includes using recorded video images, camera captured data, radar detection distance, and collision time information. With this data, the user can confirm whether the emergency braking system is triggered at the right time and whether the system reacts in the right situation. This helps to identify possible errors or deficiencies and improve the performance of the system.

[0073] In some embodiments, the software of the emergency braking system is optimized based on the actual collected data. Specifically, it includes: improving the training process of the perception algorithm by analyzing the collected video images, and improving the system's ability to recognize different dangerous situations. The training data can be used to optimize the deep learning model, so that the system can more accurately recognize and respond to various driving scenarios. The optimized software is tested in a simulation environment, simulating the same triggering scenario to verify the optimization effect. This simulation test helps to evaluate the performance of the software in actual scenarios, so as to further iterate and improve the system.

[0074] In some embodiments, emergency braking data can also be used to extract points of interest (POI). This involves collecting location information of road sections that are prone to triggering the emergency braking system. For these specific sections, newly developed models can be specially tested and verified to ensure that these models can also work effectively in similar scenarios. This targeted testing can help identify and solve problems that may exist in specific environments, ensuring that the AEBS system of new models can perform well in actual use.

[0075] In some embodiments, the collected data can also be used to build a database of dangerous scenarios. This includes collecting detailed video images and radar data of various dangerous scenarios. These data will be used for model training of perception algorithms, that is, to train machine learning models so that they can better identify and handle different dangerous scenarios. At the same time, these data are also used for generalization testing to test whether the algorithm can be effectively applied and identified in unseen scenarios. In this way, the overall robustness and reliability of the system can be improved.

[0076] The embodiment of the present invention also provides a non-volatile readable storage medium, on which a computer program is stored, and when the computer program is executed, the method for processing emergency braking data described in the above embodiment is implemented. The specific implementation process of the method for processing emergency braking data can refer to the description of the above embodiment.

[0077] In some embodiments, the non-volatile readable storage medium may include, but is not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical or magnetic storage media, which are not listed here one by one.

[0078] According to the non-volatile readable storage medium of the embodiment of the present invention, by adopting the method of emergency braking data processing described in the above embodiment, more detailed and comprehensive data support is provided for the restoration of braking event scenes and the analysis of the causes of false triggering of the emergency braking system, thereby providing an important basis for the optimization and improvement of subsequent systems, thereby helping to reduce the probability of false triggering of the system and improving the driving safety of the vehicle.

[0079] Reference below Figure 3 An electronic device according to an embodiment of the present invention is described.

[0080] Figure 3 is a block diagram of an electronic device according to an embodiment of the present invention, such as Figure 3 As shown, the electronic device 1 includes: a memory 12 and at least one processor 11.

[0081] In some embodiments, the at least one processor 11 may be one processor 11, or may be two processors 11, three processors 11, five processors 11, eight processors 11, ten processors 11, or a plurality of processors 11. These processors 11 may be various types of general or special processors, such as a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), etc. It depends on the design and purpose of the electronic device 1.

[0082] In some embodiments, the memory 12 may be a random access memory (RAM), a read-only memory (ROM), a flash memory (Flash Memory), a solid-state drive (SSD), etc. The selection of the memory 12 depends on the needs and performance of the processor to ensure that it can support real-time requirements and large-scale data processing. These memories 12 play an important role in storing and managing data, programs, and configuration information in the electronic device 1 to ensure normal operation of the system and data security.

[0083] In some embodiments, the electronic device 1 may be a control unit of an emergency braking system, a vehicle controller, other domain controllers of the vehicle, a vehicle terminal, or other devices.

[0084] According to the electronic device 1 of the embodiment of the present invention, at least one processor 11 executes a computer program that implements the method for processing emergency braking data described in the above embodiment. When the emergency braking system function is triggered, the time range for collecting braking event data is determined based on the braking risk level, and the start and end time of data collection can be flexibly adjusted for events of different risk levels. This dynamic adjustment of the time range ensures that all important data related to the event can be fully captured at the critical moment of the event. By acquiring vehicle data within the time range, including surrounding environment data (such as image data, location information, etc.) used to construct the braking event scene and vehicle internal data (such as braking status, vehicle speed, etc.) used to analyze the braking event problem, the system can completely record the situation when the braking event occurs. Therefore, the electronic device 1 of the present invention provides more detailed and comprehensive data support for the restoration of the braking event scene and the analysis of the cause of the false triggering of the emergency braking system, and then provides an important basis for the optimization and improvement of the subsequent system, thereby helping to reduce the probability of false triggering of the system and improving the driving safety of the vehicle.

[0085] Reference below Figure 4-Figure 5 A commercial vehicle according to an embodiment of the present invention is described.

[0086] Figure 4 is a block diagram of a commercial vehicle according to an embodiment of the present invention, such as Figure 4 As shown, the commercial vehicle 100 includes the electronic device 1 described in the above embodiment. The electronic device 1 integrates the entire emergency braking data processing function into a single device. This electronic device 1 can operate independently, directly obtain data from various sensors and systems of the vehicle, and analyze and process emergency braking events based on these data. This configuration is suitable for commercial vehicles 100 with high system integration requirements, especially when it is necessary to reduce complex communications between different control units. By integrating all functions into one electronic device 1, the response speed and reliability of the system can be significantly improved, and delays and data loss caused by multi-device communications can be reduced.

[0087] Figure 5 is a block diagram of a commercial vehicle according to yet another embodiment of the present invention, Figure 5As shown, the commercial vehicle 100 includes an emergency braking system 2 and a controller 3, wherein the emergency braking system 2 can be a system for automatically detecting and triggering braking operations to avoid or reduce the risk of collision. The controller 3 is connected to the emergency braking system 2 and is used to execute the method for emergency braking data processing described in the above embodiment. This configuration uses the controller 3 as an independent unit to work in collaboration with the emergency braking system 2. The controller 3 receives the trigger signal of the emergency braking system 2 and dynamically determines the time range for data collection based on the braking hazard level to ensure that all important data related to the event are fully captured at the critical moment of the event.

[0088] According to the commercial vehicle 100 of the embodiment of the present invention, by adopting the method of emergency braking data processing described in the above embodiment, when the emergency braking system function is triggered, the controller 3 can dynamically determine the time range of data collection based on the braking danger level, ensuring that all important data related to the event are fully captured at the critical moment of the event. These data include not only the surrounding environment data (such as image data, location information, etc.) used to construct the braking event scene, but also the vehicle internal data (such as braking state, vehicle speed, etc.) used to analyze the braking event problem. Through the comprehensive collection and preservation of these data, more detailed and comprehensive data support is provided for the restoration of the braking event scene and the analysis of the cause of the false triggering of the emergency braking system 2, thereby helping to reduce the probability of false triggering of the system and improving the driving safety of the commercial vehicle 100. In addition, these detailed data also provide a solid data foundation for subsequent system optimization and improvement, so that the commercial vehicle 100 can continuously improve the performance of the emergency braking system 2 through software upgrades and algorithm optimization, and adapt to more complex driving scenarios.

[0089] In some embodiments, the commercial vehicle 100 may be various types of vehicles used for commercial purposes, such as freight trucks, buses, delivery vehicles, maintenance vehicles, special work vehicles, etc.

[0090] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example.

[0091] Although the embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

Claims

1. A method for processing emergency braking data, characterized in that: include: In response to the emergency braking system function being triggered, determining a time range for collecting braking event data according to a braking risk level; Acquiring vehicle data within the time range, the vehicle data including data for constructing a braking event scenario and data for analyzing a braking event problem; The data used to construct the braking event scenario and the data used to analyze the braking event problem are saved.

2. The method according to claim 1, characterized in that The braking risk level is determined according to the braking deceleration. The greater the braking deceleration, the higher the braking risk level and the larger the time range for collecting braking event data.

3. The method according to claim 2, characterized in that The time range includes the braking event triggering moment and a preset time period before and after the braking event triggering moment.

4. The method according to claim 3, characterized in that The time range for collecting braking event data is determined based on the braking risk level, including: When the braking deceleration a satisfies a<-3m / s 2 When , the braking risk level is the first level, and the time range is [T0-10s, T0+10s], where T0 is the braking event triggering time; Or, when the braking deceleration a satisfies -1m / s 2 >a>-3m / s 2 When the braking risk level is the second level, the time range is [T0-5s, T0+5s], and the risk level of the second level is lower than the risk level of the first level; Or, when the braking deceleration a satisfies a>-1m / s 2 When , the braking risk level is the third level, the time range is [T0-2s, T0+2s], and the risk level of the third level is lower than the risk level of the second level.

5. The method according to any one of claims 1 to 4, characterized in that: The data used to construct a braking event scenario and the data used to analyze braking event problems include vehicle perception data, vehicle position information, emergency braking system function triggering time information, vehicle control commands and vehicle status information.

6. The method according to claim 1, characterized in that The method further comprises: Determining the target classification type present in the stored data for constructing the braking event scenario and the data for analyzing the braking event problem; An icon of the target classification type is displayed on a braking event record interface of an on-vehicle display device.

7. The method according to claim 1, characterized in that The method further comprises at least one of the following: After acquiring the data for constructing the braking event scenario and the data for analyzing the braking event problem, sending the data for constructing the braking event scenario and the data for analyzing the braking event problem to the cloud for backup; An extraction instruction for extracting the vehicle data is received, and when the extraction instruction satisfies an extraction authority, the extraction instruction is responded to.

8. A non-volatile readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed, the method for processing emergency braking data according to any one of claims 1 to 7 is implemented.

9. An electronic device, characterized in that: include: at least one processor; a memory communicatively coupled to the at least one processor; The memory stores a computer program that can be executed by the at least one processor, and the at least one processor implements the method for processing emergency braking data according to any one of claims 1 to 7 when executing the computer program.

10. A commercial vehicle, characterized in that: The commercial vehicle includes the electronic device described in claim 9, or the commercial vehicle includes an emergency braking system and a controller, and the controller is connected to the emergency braking system for executing the method for emergency braking data processing described in any one of claims 1-7.

Images