Hazard event generation method and apparatus, computer device, and storage medium

Abstract

The application relates to a hazard event generation method and device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: acquiring real operation test data of a test vehicle, the test vehicle comprising an intelligent driving system and a line control chassis; the real operation test data comprising first interaction data between a driver and the intelligent driving system, second interaction data between the driver and the line control chassis, third interaction data between the intelligent driving system and the line control chassis, and function transfer data; based on a pre-set failure guide word, failure analysis is performed on the first interaction data, the second interaction data, the third interaction data and the function transfer data respectively, so as to determine a target failure form of the test vehicle; a target hazard behavior corresponding to the target failure form is acquired; a hazard event matched with the target hazard behavior is generated based on an operation scene element library, and the hazard event is used for risk prediction in a user-oriented vehicle. The vehicle driving safety is improved.

Description

Technical Field

[0001] This application relates to the field of automotive technology, and in particular to a method, apparatus, computer device, storage medium, and computer program product for generating hazardous events. Background Technology

[0002] With the development of intelligent connected vehicle technology, intelligent products are becoming increasingly diversified. Among them, intelligent connected vehicles offer autonomous driving capabilities, greatly enhancing the user's driving experience.

[0003] In traditional solutions, intelligent connected vehicles rely on installed sensor devices to detect the surrounding environment in order to make correct driving decisions, but they cannot predict driving risks. Summary of the Invention

[0004] Therefore, it is necessary to provide a method, apparatus, computer device, storage medium, and computer program product that can predict driving risks and generate hazardous events in order to address the above-mentioned technical problems.

[0005] Firstly, this application provides a method for generating hazardous events. The method includes:

[0006] Acquire practical test data from test vehicles, including intelligent driving systems and drive-by-wire chassis; practical test data includes first interaction data between the driver and intelligent driving system, second interaction data between the driver and drive-by-wire chassis, third interaction data between the intelligent driving system and drive-by-wire chassis, and function transfer data;

[0007] Based on pre-set failure guidance words, failure analysis is performed on the first interaction data, the second interaction data, the third interaction data, and the function transfer data to determine the target failure mode of the test vehicle.

[0008] Obtain the target hazard behavior corresponding to the target failure mode; generate hazard events that match the target hazard behavior based on the runtime scenario element library, and use the hazard events to configure risk prediction in user-facing vehicles.

[0009] In one embodiment, the first interactive data includes: control commands issued by the driver to the intelligent driving system and feedback information from the intelligent driving system to the driver; the second interactive data includes: control commands issued by the driver to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the driver; the third interactive data includes: control commands issued by the intelligent driving system to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the intelligent driving system.

[0010] In one embodiment, the pre-set failure prompts include command failure prompts set for control commands, feedback failure prompts set for feedback information, and transfer failure prompts set for function transfer data;

[0011] Based on pre-set failure indicators, failure analysis is performed on the first interaction data, the second interaction data, the third interaction data, and the function transfer data to determine the target failure mode of the test vehicle, including:

[0012] The control commands in the first, second, and third interactive data were analyzed using command failure guide words to obtain command failure analysis results.

[0013] The feedback failure guide words were used to perform failure analysis on the feedback information in the first, second and third interactive data respectively, and the feedback failure analysis results were obtained.

[0014] Failure analysis of functional transfer data was performed using transfer failure guide words to obtain transfer failure analysis results;

[0015] Based on the results of command failure analysis, feedback failure analysis, and transfer failure analysis, the target failure mode of the test vehicle is determined.

[0016] In one embodiment, obtaining the target hazard behavior corresponding to the target failure mode includes:

[0017] Query the target hazard behavior corresponding to the target failure mode from the preset vehicle hazard behavior information mapping table.

[0018] In one embodiment, the hazardous behaviors in the preset vehicle hazardous behavior information mapping table include at least one of the following: longitudinal motion hazards, lateral motion hazards, vertical motion hazards, pitch motion hazards, roll motion hazards, or yaw motion hazards; longitudinal motion hazards include at least one of the following: unintended acceleration, unintended loss of acceleration capability, unintended deceleration, unintended loss of deceleration capability, unintended longitudinal motion, unintended loss of longitudinal motion control, or unintended directional motion; lateral motion hazards include at least one of the following: unintended lateral motion or unintended loss of lateral motion control; vertical motion hazards include at least one of the following: unintended vertical motion or unintended loss of vertical motion control; pitch motion hazards include unintended pitch motion; roll motion hazards include unintended roll motion; and yaw motion hazards include at least one of the following: unintended yaw motion or unintended loss of yaw motion control.

[0019] In one embodiment, the runtime scene element library includes: basic road information, road facilities, target object type, target object status, weather environment, digital information, vehicle actions, and vehicle operations;

[0020] Based on the runtime scenario element library, generate hazard events that match the target hazard behavior, including:

[0021] Search for road conditions matching the target hazardous behavior from the sub-elements included in the road basic information; search for road facility conditions matching the target hazardous behavior from the sub-elements included in the road facilities; search for target types matching the target hazardous behavior from the sub-elements included in the target object type; search for target object movement states matching the target hazardous behavior from the sub-elements included in the target object state; search for environment matching the target hazardous behavior from the sub-elements included in the weather environment; search for digital information matching the target hazardous behavior from the sub-elements included in the digital information; search for actions matching the target hazardous behavior from the sub-elements included in the vehicle actions; search for operations matching the target hazardous behavior from the sub-elements included in the vehicle operations.

[0022] Based on the road conditions, road infrastructure, target type, target movement status, environment, digital information, actions, and operations that match the target harmful behavior, a hazard event matching the target harmful behavior is generated.

[0023] Secondly, this application also provides a hazard event generation device. The device includes:

[0024] The acquisition module is used to acquire the actual test data of the test vehicle, which includes: intelligent driving system and drive-by-wire chassis; the actual test data includes the first interaction data between the driver and intelligent driving system, the second interaction data between the driver and drive-by-wire chassis, the third interaction data between the intelligent driving system and drive-by-wire chassis, and function transfer data;

[0025] The failure analysis module is used to perform failure analysis on the first interaction data, the second interaction data, the third interaction data, and the function transfer data based on pre-set failure prompts, in order to determine the target failure mode of the test vehicle.

[0026] The generation module is used to obtain the target hazard behavior corresponding to the target failure mode; it generates hazard events that match the target hazard behavior based on the runtime scenario element library, and the hazard events are used to configure risk prediction in user-facing vehicles.

[0027] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0028] Acquire practical test data from test vehicles, including intelligent driving systems and drive-by-wire chassis; practical test data includes first interaction data between the driver and intelligent driving system, second interaction data between the driver and drive-by-wire chassis, third interaction data between the intelligent driving system and drive-by-wire chassis, and function transfer data;

[0029] Based on pre-set failure guidance words, failure analysis is performed on the first interaction data, the second interaction data, the third interaction data, and the function transfer data to determine the target failure mode of the test vehicle.

[0030] Obtain the target hazard behavior corresponding to the target failure mode; generate hazard events that match the target hazard behavior based on the runtime scenario element library, and use the hazard events to configure risk prediction in user-facing vehicles.

[0031] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0032] Acquire practical test data from test vehicles, including intelligent driving systems and drive-by-wire chassis; practical test data includes first interaction data between the driver and intelligent driving system, second interaction data between the driver and drive-by-wire chassis, third interaction data between the intelligent driving system and drive-by-wire chassis, and function transfer data;

[0033] Based on pre-set failure guidance words, failure analysis is performed on the first interaction data, the second interaction data, the third interaction data, and the function transfer data to determine the target failure mode of the test vehicle.

[0034] Obtain the target hazard behavior corresponding to the target failure mode; generate hazard events that match the target hazard behavior based on the runtime scenario element library, and use the hazard events to configure risk prediction in user-facing vehicles.

[0035] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0036] Acquire practical test data from test vehicles, including intelligent driving systems and drive-by-wire chassis; practical test data includes first interaction data between the driver and intelligent driving system, second interaction data between the driver and drive-by-wire chassis, third interaction data between the intelligent driving system and drive-by-wire chassis, and function transfer data;

[0037] Based on pre-set failure guidance words, failure analysis is performed on the first interaction data, the second interaction data, the third interaction data, and the function transfer data to determine the target failure mode of the test vehicle.

[0038] Obtain the target hazard behavior corresponding to the target failure mode; generate hazard events that match the target hazard behavior based on the runtime scenario element library, and use the hazard events to configure risk prediction in user-facing vehicles.

[0039] The aforementioned hazard event generation method, apparatus, computer equipment, storage medium, and computer program product acquire practical test data from test vehicles, including intelligent driving systems and drive-by-wire chassis. The practical test data includes first interaction data between the driver and the intelligent driving system, second interaction data between the driver and the drive-by-wire chassis, third interaction data between the intelligent driving system and the drive-by-wire chassis, and function transfer data. Based on pre-set failure indicators, failure analysis is performed on the first, second, third, and function transfer data to determine the target failure mode of the test vehicle. The target hazard behavior corresponding to the target failure mode is obtained. Hazard events matching the target hazard behavior are generated based on a runtime scenario element library. These hazard events are used to configure risk prediction in user-facing vehicles. This improves vehicle driving safety. Attached Figure Description

[0040] Figure 1 This is a flowchart illustrating a hazard event generation method in one embodiment;

[0041] Figure 2 This is a schematic diagram of interactive data in one embodiment;

[0042] Figure 3 This is a schematic diagram of scene elements in one embodiment;

[0043] Figure 4 This is a flowchart illustrating a hazard event generation method in another embodiment;

[0044] Figure 5 This is a structural block diagram of a hazard event generation device in one embodiment;

[0045] Figure 6 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0047] In one embodiment, such as Figure 1 As shown, a method for generating hazardous events is provided. This embodiment illustrates the application of this method to a terminal. It is understood that this method can also be applied to a server, and further to a system including both a terminal and a server, and is implemented through interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0048] Step 102: Obtain the practical test data of the test vehicle, which includes: intelligent driving system and drive-by-wire chassis; the practical test data includes the first interaction data between the driver and intelligent driving system, the second interaction data between the driver and drive-by-wire chassis, the third interaction data between the intelligent driving system and drive-by-wire chassis, and function transfer data.

[0049] The first interaction data between the driver and the intelligent driving system can include: data sent by the driver to the intelligent driving system and data fed back by the intelligent driving system to the driver. The second interaction data between the driver and the drive-by-wire chassis can include: data sent by the driver to the drive-by-wire chassis and data fed back by the drive-by-wire chassis to the driver. The third interaction data between the intelligent driving system and the drive-by-wire chassis can include: data sent by the intelligent driving system to the drive-by-wire chassis and data fed back by the drive-by-wire chassis to the intelligent driving system. Function transfer data can be data related to function transfer generated by the test vehicle during practical testing.

[0050] Among them, the data sent by the driver to the intelligent driving system, the data sent by the driver to the drive-by-wire chassis, and the data sent by the intelligent driving system to the drive-by-wire chassis can be called control commands; the data fed back by the intelligent driving system to the driver, the data fed back by the drive-by-wire chassis to the driver, and the data fed back by the drive-by-wire chassis to the intelligent driving system can be called feedback information.

[0051] Step 104: Based on the pre-set failure guidance words, perform failure analysis on the first interaction data, the second interaction data, the third interaction data, and the function transfer data respectively to determine the target failure mode of the test vehicle.

[0052] The pre-set failure prompts can include: command failure prompts set for control commands, feedback failure prompts set for feedback information, and transfer failure prompts set for function transfer data.

[0053] The first, second, and third interactive data all include control commands. Failure analysis can be performed on these control commands using command failure indicators to obtain command failure analysis results. The first, second, and third interactive data also include feedback information. Failure analysis can be performed on this feedback information using feedback failure indicators to obtain feedback failure analysis results. Failure analysis can be performed on function transfer data using transfer failure indicators to obtain transfer failure analysis results. Based on the command failure analysis results, feedback failure analysis results, and transfer failure analysis results, the target failure mode of the test vehicle is determined.

[0054] Step 106: Obtain the target hazard behavior corresponding to the target failure mode; generate hazard events that match the target hazard behavior based on the runtime scenario element library, and use the hazard events to configure risk prediction in user-facing vehicles.

[0055] Among them, a vehicle hazard behavior information mapping table can be predefined. After determining the target failure mode of the intelligent connected vehicle, the hazard behavior corresponding to the target failure mode can be queried from the predefined vehicle hazard behavior information mapping table, and the hazard behavior found is taken as the target hazard behavior.

[0056] The runtime scenario element library includes multiple scenario dimensions, and each scenario dimension includes multiple sub-elements. Information matching the target harmful behavior can be searched within the sub-elements of each scenario dimension. Based on the search information corresponding to each of the multiple scenario dimensions, a harmful event matching the target harmful behavior is generated.

[0057] In this application, the vehicle mentioned in the embodiments can be an intelligent connected vehicle. The hazard event generation method provided in this application can be applied in the development stage of intelligent connected vehicles. After determining the hazard event, the hazard event can be configured in the user-facing intelligent connected vehicle. During the actual driving process of the intelligent connected vehicle, the hazard event can be used as a reference for risk prediction.

[0058] In the above embodiments, practical test data of the test vehicle is acquired. The test vehicle includes an intelligent driving system and a drive-by-wire chassis. The practical test data includes first interaction data between the driver and the intelligent driving system, second interaction data between the driver and the drive-by-wire chassis, third interaction data between the intelligent driving system and the drive-by-wire chassis, and function transfer data. Based on pre-set failure guidance words, failure analysis is performed on the first interaction data, second interaction data, third interaction data, and function transfer data to determine the target failure mode of the test vehicle. The target hazardous behavior corresponding to the target failure mode is acquired. Hazardous events matching the target hazardous behavior are generated based on the runtime scenario element library. These hazardous events are used to configure risk prediction in user-facing vehicles. This improves vehicle driving safety.

[0059] In some embodiments, the first interactive data includes: control commands issued by the driver to the intelligent driving system and feedback information from the intelligent driving system to the driver; the second interactive data includes: control commands issued by the driver to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the driver; the third interactive data includes: control commands issued by the intelligent driving system to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the intelligent driving system.

[0060] Among them, see Figure 2 As shown, the control commands issued by the driver to the intelligent driving system may include at least one of the following: enabling the intelligent driving system, disabling the intelligent driving system, a preset target distance for longitudinal control, or a preset target speed for longitudinal control.

[0061] Among them, see Figure 2 As shown, the feedback information that the intelligent driving system sends to the driver may include: the working status of the intelligent driving system, warning information, or a takeover request sent to the driver.

[0062] Among them, see Figure 2 As shown, the control commands issued by the driver to the drive-by-wire chassis may include at least one of the following: accelerator, brake, steering, gear, parking, or sound and light.

[0063] Among them, see Figure 2 As shown, the feedback information that the drive-by-wire chassis provides to the driver may include at least one of the following: vehicle status, steering status, braking status, or driving status.

[0064] Among them, see Figure 2 As shown, the control commands issued by the intelligent driving system to the drive-by-wire chassis may include at least one of the following: accelerator, brake, steering, gear, parking, or sound and light.

[0065] Among them, see Figure 2 As shown, the feedback information that the drive-by-wire chassis sends to the intelligent driving system may include at least one of the following: vehicle status, steering status, braking status, or driving status.

[0066] In the above embodiments, the first interactive data includes: control commands issued by the driver to the intelligent driving system and feedback information from the intelligent driving system to the driver; the second interactive data includes: control commands issued by the driver to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the driver; the third interactive data includes: control commands issued by the intelligent driving system to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the intelligent driving system. Subsequent failure analysis is performed based on this information, resulting in a more comprehensive and thorough analysis.

[0067] In some embodiments, the pre-set failure guide words include command failure guide words set for control commands, feedback failure guide words set for feedback information, and transfer failure guide words set for function transfer data. Based on the pre-set failure guide words, failure analysis is performed on the first interaction data, second interaction data, third interaction data, and function transfer data respectively to determine the target failure mode of the test vehicle. This includes: using command failure guide words to perform failure analysis on the control commands in the first interaction data, second interaction data, and third interaction data respectively to obtain command failure analysis results; using feedback failure guide words to perform failure analysis on the feedback information in the first interaction data, second interaction data, and third interaction data respectively to obtain feedback failure analysis results; using transfer failure guide words to perform failure analysis on the function transfer data to obtain transfer failure analysis results; and determining the target failure mode of the test vehicle based on the command failure analysis results, feedback failure analysis results, and transfer failure analysis results.

[0068] Specifically, based on the control commands in the first, second, and third interactive data, analysis can be performed on driving failures caused by incorrect control command execution. Based on the feedback information in the first, second, and third interactive data, analysis can be performed on failure modes caused by incorrect state feedback. Based on function transfer data, analysis can be performed on failure modes caused by incorrect function transfer.

[0069] Among them, the command failure prompt words set for control commands may include at least one of the following: not provided when control is needed, provided when control is not needed, providing excessive control strength, providing insufficient control strength, providing control too early, providing control too late, providing control for too long, providing control for too short, and controlling in the opposite direction.

[0070] The feedback failure prompts set for feedback information may include at least one of the following: no feedback when feedback is needed, providing feedback when feedback is not needed, feedback value is too large, feedback value is too small, feedback period is too long, and feedback period is too short.

[0071] This allows for pre-defining the actions of the intelligent driving system in different functions and the triggering conditions for function transfers. Transfer failure prompts set for function transfers can include at least one of the following: the function should have been activated but wasn't, the function should have been deactivated but wasn't, the function should have transferred but wasn't, or a transfer error. For example, if function A should have transferred to function B but instead transferred to function C / D / … / N, then a transfer error is considered.

[0072] In some embodiments, for each control instruction in the first interactive data, the second interactive data, and the third interactive data, it is determined whether it belongs to one of the following guiding words: not provided when control is needed, provided when control is not needed, providing excessive control force, providing insufficient control force, providing control too early, providing control too late, providing control for too long, providing control for too short, or having the opposite control direction. If it belongs to one of these guiding words, the corresponding command failure analysis result is determined based on the control instruction.

[0073] For example, if the driver issues an accelerator command to the drive-by-wire chassis, and after analysis, it is determined that the command is an accelerator command given when no accelerator command is needed, then the command failure analysis result is considered as giving an accelerator command given when no accelerator command is needed.

[0074] In some embodiments, for each piece of feedback information in the first interactive data, the second interactive data, and the third interactive data, it is determined whether it belongs to the category of not providing feedback when feedback value is required, providing feedback value when feedback is not required, and one of the following: feedback value is too large, feedback value is too small, feedback period is too large, or feedback period is too small. If it belongs to one of these categories, the corresponding feedback failure analysis result is determined based on the feedback information.

[0075] In some embodiments, for each function transfer data, it is determined whether it belongs to one of the following: function not being enabled when it should have been enabled, function not being exited when it should have been exited, function not being transferred when it should have been transferred, or transfer error. If it belongs to one of these, the corresponding transfer failure analysis result is determined based on the function transfer data.

[0076] In some embodiments, command failure analysis results, feedback failure analysis results, and transfer failure analysis results can all be used as the target failure mode of the test vehicle.

[0077] In the above embodiments, it is possible not only to identify failures caused by abnormal control commands, but also to identify failures caused by abnormal feedback information and failures caused by abnormal function transfer, resulting in a more comprehensive identification outcome.

[0078] In some embodiments, obtaining the target hazard behavior corresponding to the target failure mode includes: querying the target hazard behavior corresponding to the target failure mode from a preset vehicle hazard behavior information mapping table.

[0079] The preset vehicle hazard behavior information mapping table includes at least one of the following: longitudinal motion hazard, lateral motion hazard, vertical motion hazard, pitch motion hazard, roll motion hazard, or yaw motion hazard; longitudinal motion hazard includes at least one of the following: unintended acceleration, unintended loss of acceleration capability, unintended deceleration, unintended loss of deceleration capability, unintended longitudinal motion, unintended loss of longitudinal motion control, or unintended directional motion; lateral motion hazard includes at least one of the following: unintended lateral motion or unintended loss of lateral motion control; vertical motion hazard includes at least one of the following: unintended vertical motion or unintended loss of vertical motion control; pitch motion hazard includes unintended pitch motion; roll motion hazard includes unintended roll motion; and yaw motion hazard includes at least one of the following: unintended yaw motion or unintended loss of yaw motion control.

[0080] For example, if a driver issues an accelerator command to the drive-by-wire chassis, analysis reveals that this command is an accelerator command issued when no accelerator command is needed. Therefore, issuing an accelerator command when no accelerator command is needed can be classified as a target failure mode. The pre-defined vehicle hazard behavior information mapping table can be used to find that the corresponding hazard behavior for this target failure mode is unintended acceleration.

[0081] In the above embodiments, after determining the target failure mode of the test vehicle, the target hazardous behavior corresponding to the target failure mode can be queried from the preset vehicle hazardous behavior information mapping table. Based on the target hazardous behavior, a hazardous event matching the target hazardous behavior is generated for risk prediction, thereby improving vehicle driving safety.

[0082] In some embodiments, the runtime scenario element library includes: basic road information, road facilities, target object type, target object status, weather environment, digital information, vehicle actions, and vehicle operations; generating hazard events matching the target hazard behavior based on the runtime scenario element library includes: searching for road conditions matching the target hazard behavior from the sub-elements included in the basic road information; searching for road facility conditions matching the target hazard behavior from the sub-elements included in the road facilities; searching for target types matching the target hazard behavior from the sub-elements included in the target object type; searching for target object movement states matching the target hazard behavior from the sub-elements included in the target object status; and searching for target movement states matching the target hazard behavior from the sub-elements included in the weather environment. The environment for matching hazardous behaviors; searching for digital information matching the target hazardous behavior from the sub-elements contained in the digital information; searching for actions matching the target hazardous behavior from the sub-elements contained in the vehicle actions; searching for operations matching the target hazardous behavior from the sub-elements contained in the vehicle operations; generating hazardous events matching the target hazardous behavior based on road conditions matching the target hazardous behavior, road infrastructure conditions matching the target hazardous behavior, target type matching the target hazardous behavior, target object movement state matching the target hazardous behavior, environment matching the target hazardous behavior, digital information matching the target hazardous behavior, actions matching the target hazardous behavior, and operations matching the target hazardous behavior.

[0083] Among them, the system sets up a library of operating scenario elements based on the scenario constraints of intelligent connected vehicles, which includes, but is not limited to, a combination of multiple parameters such as driving location, driving operation, environmental conditions, road conditions, and the status of traffic participants.

[0084] Among them, see Figure 3 As shown, the sub-elements of basic road information include: road type, road surface, road geometry, lane features, road edges, and road intersections. Road facilities include: traffic control facilities, road infrastructure, special facilities, and temporary road facilities. Target object type includes: motor vehicles, non-motor vehicles, pedestrians, animals, and obstacles. Target object status includes: location, acceleration, deceleration, merging, merging out, and crossing. Weather environment includes: rain, snow, wind, fog / particulate matter, temperature, and light intensity. Digital information includes: V2X information and location information. Vehicle actions include: start, stop, forward, reverse, straight, turn, lane change, and close. Vehicle operations include: deceleration, acceleration, constant speed, and parking.

[0085] When there are multiple target failure modes, for each target failure mode, the corresponding target hazard behavior can be queried from the preset vehicle hazard behavior information mapping table, resulting in multiple target hazard behaviors. For each target hazard behavior, a corresponding hazard event can be generated, ultimately resulting in multiple hazard events.

[0086] In some embodiments, for a target harmful behavior, matching information can be manually searched for in road basic information, road facilities, target object type, target object status, weather environment, digital information, vehicle actions, and vehicle operation. The event formed by combining the found information is used as the harmful event matching the target harmful behavior.

[0087] In some embodiments, elements from the sub-elements of road infrastructure information that may exhibit hazard when combined with the target hazardous behavior can be used as road conditions matching the target hazardous behavior; elements from the sub-elements of road facilities that may exhibit hazard when combined with the target hazardous behavior can be used as road facility conditions matching the target hazardous behavior; elements from the sub-elements of target object type that may exhibit hazard when combined with the target hazardous behavior can be used as target types matching the target hazardous behavior; and elements from the sub-elements of target object status that may exhibit hazard when combined with the target hazardous behavior can be used as target types matching the target hazardous behavior. The target object's motion state can be matched; elements within the weather environment that may pose a hazard when combined with the target hazardous behavior can be considered as the environment matching the target hazardous behavior; elements within the digital information that may pose a hazard when combined with the target hazardous behavior can be considered as the digital information matching the target hazardous behavior; elements within the vehicle's actions that may pose a hazard when combined with the target hazardous behavior can be considered as the actions matching the target hazardous behavior; elements within the vehicle's operations that may pose a hazard when combined with the target hazardous behavior can be considered as the operations matching the target hazardous behavior.

[0088] For example, if a driver issues an accelerator command to the drive-by-wire chassis, analysis reveals that this command is an accelerator command issued when no accelerator command is needed. Therefore, issuing an accelerator command when no accelerator command is needed can be classified as a target failure mode. The pre-defined vehicle hazard behavior information mapping table can be used to find that the corresponding hazard behavior for this target failure mode is unintended acceleration. The elements that may pose a hazard after combining unexpected acceleration with the sub-elements found in the road infrastructure information are: road intersections; traffic control facilities; pedestrians; crossing; snow; V2X information; turning; and acceleration. Therefore, the scenario consisting of road intersections, traffic control facilities, pedestrians, crossing, snow, V2X information, turning, and acceleration is considered a hazard event matching the target hazard behavior.

[0089] In the above embodiments, a predefined runtime scenario element library is used to search for hazardous scenario elements. Based on the searched scenario elements, hazardous events are generated, which can accurately identify hazardous events and improve vehicle driving safety.

[0090] In some embodiments, see Figure 4 As shown, a method for generating hazardous events is provided, the method comprising:

[0091] Step 401: Obtain practical test data of the test vehicle, which includes: intelligent driving system and drive-by-wire chassis; practical test data includes first interaction data between driver and intelligent driving system, second interaction data between driver and drive-by-wire chassis, third interaction data between intelligent driving system and drive-by-wire chassis, and function transfer data.

[0092] Step 402: Use command failure guide words to perform failure analysis on the control commands in the first interaction data, the second interaction data and the third interaction data respectively, and obtain command failure analysis results.

[0093] Step 403: Using feedback failure guide words, perform failure analysis on the feedback information in the first interaction data, the second interaction data, and the third interaction data respectively to obtain feedback failure analysis results.

[0094] Step 404: Use transfer failure guide words to perform failure analysis on the function transfer data to obtain the transfer failure analysis results.

[0095] Step 405: Based on the command failure analysis results, feedback failure analysis results, and transfer failure analysis results, determine the target failure mode of the test vehicle.

[0096] Step 406: Query the target hazard behavior corresponding to the target failure mode from the preset vehicle hazard behavior information mapping table.

[0097] Step 407: Generate a hazard event that matches the target hazard behavior based on the runtime scenario element library.

[0098] In the above embodiments, practical test data of the test vehicle is acquired. The test vehicle includes an intelligent driving system and a drive-by-wire chassis. The practical test data includes first interaction data between the driver and the intelligent driving system, second interaction data between the driver and the drive-by-wire chassis, third interaction data between the intelligent driving system and the drive-by-wire chassis, and function transfer data. Based on pre-set failure guidance words, failure analysis is performed on the first interaction data, second interaction data, third interaction data, and function transfer data to determine the target failure mode of the test vehicle. The target hazardous behavior corresponding to the target failure mode is acquired. Hazardous events matching the target hazardous behavior are generated based on the runtime scenario element library. These hazardous events are used to configure risk prediction in user-facing vehicles. This improves vehicle driving safety.

[0099] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0100] Based on the same inventive concept, this application also provides a hazard event generation apparatus for implementing the hazard event generation method described above. The solution provided by this apparatus is similar to the solution described in the above method; therefore, the specific limitations in one or more hazard event generation apparatus embodiments provided below can be found in the limitations of the hazard event generation method described above, and will not be repeated here.

[0101] In one embodiment, such as Figure 5 As shown, a hazard event generation device is provided, comprising:

[0102] The acquisition module 501 is used to acquire the actual test data of the test vehicle, which includes: intelligent driving system and drive-by-wire chassis; the actual test data includes the first interaction data between the driver and intelligent driving system, the second interaction data between the driver and drive-by-wire chassis, the third interaction data between the intelligent driving system and drive-by-wire chassis, and function transfer data;

[0103] The failure analysis module 502 is used to perform failure analysis on the first interaction data, the second interaction data, the third interaction data and the function transfer data based on the pre-set failure guide words, so as to determine the target failure mode of the test vehicle.

[0104] The generation module 503 is used to obtain the target hazard behavior corresponding to the target failure mode; and to generate hazard events that match the target hazard behavior based on the runtime scenario element library. The hazard events are used to configure risk prediction in user-facing vehicles.

[0105] In some embodiments, the first interactive data includes: control commands issued by the driver to the intelligent driving system and feedback information from the intelligent driving system to the driver; the second interactive data includes: control commands issued by the driver to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the driver; the third interactive data includes: control commands issued by the intelligent driving system to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the intelligent driving system.

[0106] In some embodiments, the pre-set failure guide words include command failure guide words set for control commands, feedback failure guide words set for feedback information, and transfer failure guide words set for function transfer data; the failure analysis module 502 is specifically used to perform failure analysis on the control commands in the first interaction data, the second interaction data, and the third interaction data using the command failure guide words respectively, to obtain command failure analysis results; to perform failure analysis on the feedback information in the first interaction data, the second interaction data, and the third interaction data using the feedback failure guide words respectively, to obtain feedback failure analysis results; to perform failure analysis on the function transfer data using the transfer failure guide words, to obtain transfer failure analysis results; and to determine the target failure mode of the test vehicle based on the command failure analysis results, the feedback failure analysis results, and the transfer failure analysis results.

[0107] In some embodiments, the generation module 503 is specifically used to query the target hazard behavior corresponding to the target failure mode from a preset vehicle hazard behavior information mapping table.

[0108] In some embodiments, the hazardous behaviors in the preset vehicle hazardous behavior information mapping table include at least one of the following: longitudinal motion hazards, lateral motion hazards, vertical motion hazards, pitch motion hazards, roll motion hazards, or yaw motion hazards; longitudinal motion hazards include at least one of the following: unintended acceleration, unintended loss of acceleration capability, unintended deceleration, unintended loss of deceleration capability, unintended longitudinal motion, unintended loss of longitudinal motion control, or unintended directional motion; lateral motion hazards include at least one of the following: unintended lateral motion or unintended loss of lateral motion control; vertical motion hazards include at least one of the following: unintended vertical motion or unintended loss of vertical motion control; pitch motion hazards include unintended pitch motion; roll motion hazards include unintended roll motion; and yaw motion hazards include at least one of the following: unintended yaw motion or unintended loss of yaw motion control.

[0109] In some embodiments, the running scene element library includes: basic road information, road facilities, target object type, target object status, weather environment, digital information, vehicle actions, and vehicle operations; the generation module 503 is specifically used to search for road conditions matching the target hazard behavior from the sub-elements included in the basic road information; search for road facility conditions matching the target hazard behavior from the sub-elements included in the road facilities; search for target types matching the target hazard behavior from the sub-elements included in the target object type; search for target object movement states matching the target hazard behavior from the sub-elements included in the target object status; and search for environmental conditions matching the target hazard behavior from the sub-elements included in the weather environment. The system searches for digital information matching the target harmful behavior from the sub-elements contained in the digital information; searches for actions matching the target harmful behavior from the sub-elements contained in the vehicle actions; searches for operations matching the target harmful behavior from the sub-elements contained in the vehicle operations; and generates a harmful event matching the target harmful behavior based on the road conditions matching the target harmful behavior, the road infrastructure conditions matching the target harmful behavior, the target type matching the target harmful behavior, the target object's movement state matching the target harmful behavior, the environment matching the target harmful behavior, the digital information matching the target harmful behavior, the actions matching the target harmful behavior, and the operations matching the target harmful behavior.

[0110] Each module in the aforementioned hazardous event generation device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0111] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 6 As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores practical test data and hazardous events. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When executed by the processor, the computer program implements a hazardous event generation method.

[0112] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0113] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0114] Acquire practical test data from test vehicles, including intelligent driving systems and drive-by-wire chassis; practical test data includes first interaction data between the driver and intelligent driving system, second interaction data between the driver and drive-by-wire chassis, third interaction data between the intelligent driving system and drive-by-wire chassis, and function transfer data;

[0115] Based on pre-set failure guidance words, failure analysis is performed on the first interaction data, the second interaction data, the third interaction data, and the function transfer data to determine the target failure mode of the test vehicle.

[0116] Obtain the target hazard behavior corresponding to the target failure mode; generate hazard events that match the target hazard behavior based on the runtime scenario element library, and use the hazard events to configure risk prediction in user-facing vehicles.

[0117] In one embodiment, the first interactive data includes: control commands issued by the driver to the intelligent driving system and feedback information from the intelligent driving system to the driver; the second interactive data includes: control commands issued by the driver to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the driver; the third interactive data includes: control commands issued by the intelligent driving system to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the intelligent driving system.

[0118] In one embodiment, the pre-set failure guide words include command failure guide words set for control commands, feedback failure guide words set for feedback information, and transfer failure guide words set for function transfer data. When the processor executes the computer program, it also performs the following steps: using the command failure guide words to perform failure analysis on the control commands in the first interactive data, the second interactive data, and the third interactive data respectively, and obtain command failure analysis results; using the feedback failure guide words to perform failure analysis on the feedback information in the first interactive data, the second interactive data, and the third interactive data respectively, and obtain feedback failure analysis results; using the transfer failure guide words to perform failure analysis on the function transfer data, and obtain transfer failure analysis results; and based on the command failure analysis results, the feedback failure analysis results, and the transfer failure analysis results, determining the target failure mode of the test vehicle.

[0119] In one embodiment, when the processor executes the computer program, it also performs the following steps: querying the target hazard behavior corresponding to the target failure mode from a preset vehicle hazard behavior information mapping table.

[0120] In one embodiment, the hazardous behaviors in the preset vehicle hazardous behavior information mapping table include at least one of the following: longitudinal motion hazards, lateral motion hazards, vertical motion hazards, pitch motion hazards, roll motion hazards, or yaw motion hazards; longitudinal motion hazards include at least one of the following: unintended acceleration, unintended loss of acceleration capability, unintended deceleration, unintended loss of deceleration capability, unintended longitudinal motion, unintended loss of longitudinal motion control, or unintended directional motion; lateral motion hazards include at least one of the following: unintended lateral motion or unintended loss of lateral motion control; vertical motion hazards include at least one of the following: unintended vertical motion or unintended loss of vertical motion control; pitch motion hazards include unintended pitch motion; roll motion hazards include unintended roll motion; and yaw motion hazards include at least one of the following: unintended yaw motion or unintended loss of yaw motion control.

[0121] In one embodiment, the running scenario element library includes: basic road information, road facilities, target object types, target object states, weather conditions, digital information, vehicle actions, and vehicle operations; when the processor executes the computer program, it further implements the following steps: searching for road conditions matching the target hazard behavior from the sub-elements included in the basic road information; searching for road facility conditions matching the target hazard behavior from the sub-elements included in the road facilities; searching for target types matching the target hazard behavior from the sub-elements included in the target object types; searching for target object movement states matching the target hazard behavior from the sub-elements included in the target object states; and searching for target movement states matching the target hazard behavior from the sub-elements included in the weather conditions. The system analyzes the environment, searches for digital information matching the target harmful behavior from the sub-elements contained in the digital information, searches for actions matching the target harmful behavior from the sub-elements contained in the vehicle actions, searches for operations matching the target harmful behavior from the sub-elements contained in the vehicle operations, and generates a hazard event matching the target harmful behavior based on the road conditions matching the target harmful behavior, the road facilities matching the target harmful behavior, the target type matching the target harmful behavior, the target object's movement state matching the target harmful behavior, the environment matching the target harmful behavior, the digital information matching the target harmful behavior, the actions matching the target harmful behavior, and the operations matching the target harmful behavior.

[0122] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0123] Acquire practical test data from test vehicles, including intelligent driving systems and drive-by-wire chassis; practical test data includes first interaction data between the driver and intelligent driving system, second interaction data between the driver and drive-by-wire chassis, third interaction data between the intelligent driving system and drive-by-wire chassis, and function transfer data;

[0124] Based on pre-set failure guidance words, failure analysis is performed on the first interaction data, the second interaction data, the third interaction data, and the function transfer data to determine the target failure mode of the test vehicle.

[0125] Obtain the target hazard behavior corresponding to the target failure mode; generate hazard events that match the target hazard behavior based on the runtime scenario element library, and use the hazard events to configure risk prediction in user-facing vehicles.

[0126] In one embodiment, the first interactive data includes: control commands issued by the driver to the intelligent driving system and feedback information from the intelligent driving system to the driver; the second interactive data includes: control commands issued by the driver to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the driver; the third interactive data includes: control commands issued by the intelligent driving system to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the intelligent driving system.

[0127] In one embodiment, the pre-set failure guide words include command failure guide words set for control commands, feedback failure guide words set for feedback information, and transfer failure guide words set for function transfer data. When the computer program is executed by the processor, it further performs the following steps: using the command failure guide words to perform failure analysis on the control commands in the first interactive data, the second interactive data, and the third interactive data respectively, and obtain command failure analysis results; using the feedback failure guide words to perform failure analysis on the feedback information in the first interactive data, the second interactive data, and the third interactive data respectively, and obtain feedback failure analysis results; using the transfer failure guide words to perform failure analysis on the function transfer data, and obtain transfer failure analysis results; and based on the command failure analysis results, the feedback failure analysis results, and the transfer failure analysis results, determining the target failure mode of the test vehicle.

[0128] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: querying the target hazard behavior corresponding to the target failure mode from a preset vehicle hazard behavior information mapping table.

[0129] In one embodiment, the hazardous behaviors in the preset vehicle hazardous behavior information mapping table include at least one of the following: longitudinal motion hazards, lateral motion hazards, vertical motion hazards, pitch motion hazards, roll motion hazards, or yaw motion hazards; longitudinal motion hazards include at least one of the following: unintended acceleration, unintended loss of acceleration capability, unintended deceleration, unintended loss of deceleration capability, unintended longitudinal motion, unintended loss of longitudinal motion control, or unintended directional motion; lateral motion hazards include at least one of the following: unintended lateral motion or unintended loss of lateral motion control; vertical motion hazards include at least one of the following: unintended vertical motion or unintended loss of vertical motion control; pitch motion hazards include unintended pitch motion; roll motion hazards include unintended roll motion; and yaw motion hazards include at least one of the following: unintended yaw motion or unintended loss of yaw motion control.

[0130] In one embodiment, the running scenario element library includes: basic road information, road facilities, target object type, target object status, weather environment, digital information, vehicle actions, and vehicle operations; when the computer program is executed by the processor, it further performs the following steps: searching for road conditions matching the target hazard behavior from the sub-elements included in the basic road information; searching for road facility conditions matching the target hazard behavior from the sub-elements included in the road facilities; searching for target types matching the target hazard behavior from the sub-elements included in the target object type; searching for target object movement states matching the target hazard behavior from the sub-elements included in the target object status; and searching for target movement states matching the target hazard behavior from the sub-elements included in the weather environment. The matching environment; searching for digital information matching the target harmful behavior from the sub-elements contained in the digital information; searching for actions matching the target harmful behavior from the sub-elements contained in the vehicle actions; searching for operations matching the target harmful behavior from the sub-elements contained in the vehicle operations; generating a hazard event matching the target harmful behavior based on the road conditions matching the target harmful behavior, the road facilities matching the target harmful behavior, the target type matching the target harmful behavior, the target object's movement state matching the target harmful behavior, the environment matching the target harmful behavior, the digital information matching the target harmful behavior, the actions matching the target harmful behavior, and the operations matching the target harmful behavior.

[0131] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0132] Acquire practical test data from test vehicles, including intelligent driving systems and drive-by-wire chassis; practical test data includes first interaction data between the driver and intelligent driving system, second interaction data between the driver and drive-by-wire chassis, third interaction data between the intelligent driving system and drive-by-wire chassis, and function transfer data;

[0133] Based on pre-set failure guidance words, failure analysis is performed on the first interaction data, the second interaction data, the third interaction data, and the function transfer data to determine the target failure mode of the test vehicle.

[0134] Obtain the target hazard behavior corresponding to the target failure mode; generate hazard events that match the target hazard behavior based on the runtime scenario element library, and use the hazard events to configure risk prediction in user-facing vehicles.

[0135] In one embodiment, the first interactive data includes: control commands issued by the driver to the intelligent driving system and feedback information from the intelligent driving system to the driver; the second interactive data includes: control commands issued by the driver to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the driver; the third interactive data includes: control commands issued by the intelligent driving system to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the intelligent driving system.

[0136] In one embodiment, the pre-set failure guide words include command failure guide words set for control commands, feedback failure guide words set for feedback information, and transfer failure guide words set for function transfer data. When the computer program is executed by the processor, it further performs the following steps: using the command failure guide words to perform failure analysis on the control commands in the first interactive data, the second interactive data, and the third interactive data respectively, and obtain command failure analysis results; using the feedback failure guide words to perform failure analysis on the feedback information in the first interactive data, the second interactive data, and the third interactive data respectively, and obtain feedback failure analysis results; using the transfer failure guide words to perform failure analysis on the function transfer data, and obtain transfer failure analysis results; and based on the command failure analysis results, the feedback failure analysis results, and the transfer failure analysis results, determining the target failure mode of the test vehicle.

[0137] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: querying the target hazard behavior corresponding to the target failure mode from a preset vehicle hazard behavior information mapping table.

[0138] In one embodiment, the hazardous behaviors in the preset vehicle hazardous behavior information mapping table include at least one of the following: longitudinal motion hazards, lateral motion hazards, vertical motion hazards, pitch motion hazards, roll motion hazards, or yaw motion hazards; longitudinal motion hazards include at least one of the following: unintended acceleration, unintended loss of acceleration capability, unintended deceleration, unintended loss of deceleration capability, unintended longitudinal motion, unintended loss of longitudinal motion control, or unintended directional motion; lateral motion hazards include at least one of the following: unintended lateral motion or unintended loss of lateral motion control; vertical motion hazards include at least one of the following: unintended vertical motion or unintended loss of vertical motion control; pitch motion hazards include unintended pitch motion; roll motion hazards include unintended roll motion; and yaw motion hazards include at least one of the following: unintended yaw motion or unintended loss of yaw motion control.

[0139] In one embodiment, the running scenario element library includes: basic road information, road facilities, target object type, target object status, weather environment, digital information, vehicle actions, and vehicle operations; when the computer program is executed by the processor, it further performs the following steps: searching for road conditions matching the target hazard behavior from the sub-elements included in the basic road information; searching for road facility conditions matching the target hazard behavior from the sub-elements included in the road facilities; searching for target types matching the target hazard behavior from the sub-elements included in the target object type; searching for target object movement states matching the target hazard behavior from the sub-elements included in the target object status; and searching for target movement states matching the target hazard behavior from the sub-elements included in the weather environment. The matching environment; searching for digital information matching the target harmful behavior from the sub-elements contained in the digital information; searching for actions matching the target harmful behavior from the sub-elements contained in the vehicle actions; searching for operations matching the target harmful behavior from the sub-elements contained in the vehicle operations; generating a hazard event matching the target harmful behavior based on the road conditions matching the target harmful behavior, the road facilities matching the target harmful behavior, the target type matching the target harmful behavior, the target object's movement state matching the target harmful behavior, the environment matching the target harmful behavior, the digital information matching the target harmful behavior, the actions matching the target harmful behavior, and the operations matching the target harmful behavior.

[0140] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0141] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0142] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for generating a hazardous event, characterized in that, The method includes: Acquire practical test data of the test vehicle, which includes an intelligent driving system and a drive-by-wire chassis; the practical test data includes first interaction data between the driver and the intelligent driving system, second interaction data between the driver and the drive-by-wire chassis, third interaction data between the intelligent driving system and the drive-by-wire chassis, and function transfer data; Based on pre-set failure prompts, failure analysis is performed on the first interaction data, the second interaction data, the third interaction data, and the function transfer data to determine the target failure mode of the test vehicle. Obtain the target hazard behavior corresponding to the target failure mode; generate a hazard event matching the target hazard behavior based on the running scenario element library, and the hazard event is used to configure risk prediction in user-facing vehicles.

2. The method according to claim 1, characterized in that, The first interactive data includes: control commands issued by the driver to the intelligent driving system and feedback information from the intelligent driving system to the driver; the second interactive data includes: control commands issued by the driver to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the driver; the third interactive data includes: control commands issued by the intelligent driving system to the drive-by-wire chassis and feedback information from the drive-by-wire chassis to the intelligent driving system.

3. The method according to claim 2, characterized in that, The pre-set failure prompts include command failure prompts set for control commands, feedback failure prompts set for feedback information, and transfer failure prompts set for function transfer data; The method involves performing failure analysis on the first interaction data, the second interaction data, the third interaction data, and the function transfer data based on pre-set failure prompts to determine the target failure mode of the test vehicle, including: The control commands in the first interactive data, the second interactive data, and the third interactive data are analyzed for failure using the command failure guide words to obtain command failure analysis results. The feedback failure guide words are used to perform failure analysis on the feedback information in the first interactive data, the second interactive data and the third interactive data respectively, and the feedback failure analysis results are obtained. The aforementioned transfer failure guide word is used to perform failure analysis on the functional transfer data to obtain transfer failure analysis results; Based on the command failure analysis results, the feedback failure analysis results, and the transfer failure analysis results, the target failure mode of the test vehicle is determined.

4. The method according to claim 1, characterized in that, The step of obtaining the target hazard behavior corresponding to the target failure mode includes: The target hazard behavior corresponding to the target failure mode is queried from the preset vehicle hazard behavior information mapping table.

5. The method according to claim 4, characterized in that, The preset vehicle hazard behavior information mapping table includes at least one of the following: longitudinal motion hazard, lateral motion hazard, vertical motion hazard, pitch motion hazard, roll motion hazard, or yaw motion hazard; the longitudinal motion hazard includes at least one of the following: unintended acceleration, unintended loss of acceleration capability, unintended deceleration, unintended loss of deceleration capability, unintended longitudinal motion, unintended loss of longitudinal motion control, or unintended directional motion; the lateral motion hazard includes at least one of the following: unintended lateral motion or unintended loss of lateral motion control; the vertical motion hazard includes at least one of the following: unintended vertical motion or unintended loss of vertical motion control; the pitch motion hazard includes unintended pitch motion; the roll motion hazard includes unintended roll motion; and the yaw motion hazard includes at least one of the following: unintended yaw motion or unintended loss of yaw motion control.

6. The method according to any one of claims 1-5, characterized in that, The runtime scenario element library includes: basic road information, road facilities, target object type, target object status, weather environment, digital information, vehicle actions, and vehicle operations; The generation of hazard events based on the runtime scenario element library that match the target hazard behavior includes: The system searches for road conditions matching the target hazardous behavior from the sub-elements included in the road basic information; searches for road facility conditions matching the target hazardous behavior from the sub-elements included in the road facilities; searches for target types matching the target hazardous behavior from the sub-elements included in the target object type; searches for target object movement states matching the target hazardous behavior from the sub-elements included in the target object state; searches for environments matching the target hazardous behavior from the sub-elements included in the weather environment; searches for digital information matching the target hazardous behavior from the sub-elements included in the digital information; searches for actions matching the target hazardous behavior from the sub-elements included in the vehicle actions; and searches for operations matching the target hazardous behavior from the sub-elements included in the vehicle operation. Based on the road conditions matching the target harmful behavior, the road infrastructure conditions matching the target harmful behavior, the target type matching the target harmful behavior, the target object movement state matching the target harmful behavior, the environment matching the target harmful behavior, the digital information matching the target harmful behavior, the actions matching the target harmful behavior, and the operations matching the target harmful behavior, a harmful event matching the target harmful behavior is generated.

7. A hazard event generation device, characterized in that, include: The acquisition module is used to acquire practical test data of the test vehicle, which includes an intelligent driving system and a drive-by-wire chassis. The practical test data includes first interaction data between the driver and the intelligent driving system, second interaction data between the driver and the drive-by-wire chassis, third interaction data between the intelligent driving system and the drive-by-wire chassis, and function transfer data. The failure analysis module is used to perform failure analysis on the first interaction data, the second interaction data, the third interaction data, and the function transfer data based on pre-set failure guidance words, so as to determine the target failure mode of the test vehicle. The generation module is used to obtain the target hazard behavior corresponding to the target failure mode; and to generate a hazard event that matches the target hazard behavior based on the running scenario element library. The hazard event is used to configure risk prediction in user-facing vehicles.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images