Vehicle-road cooperation automatic driving system and safety hazard event trigger condition analysis method
By combining traditional safety analysis methods and STPA, a multi-level hierarchical control structure is established to identify the triggering conditions of safety hazard events of vehicle-road collaborative autonomous driving system, the problem of insufficient expected functional safety analysis in the existing technology is solved and the system safety is improved and accuracy of identification.
Patent Information
- Application Number
- CN202411090669.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-09
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2044-08-09
AI Technical Summary
The existing vehicle-road collaborative autonomous driving system has performance limitations and insufficient specifications in the expected functional safety analysis, which makes it difficult to effectively identify the trigger conditions of safety hazard events, affecting the overall safety of the system.
Combining traditional safety analysis methods and system theoretical process analysis methods (STPA), standardize the functions of vehicle-road collaborative autonomous driving systems, define system design and operation conditions, analyze system decision-making logic processes, clarify system vehicle-level hazards and risk assessments, and establish multi-level Hierarchical control structure, identify unsafe control behaviors, identify system trigger conditions, and improve the accuracy and comprehensiveness of trigger conditions identification of expected functional safety hazard events.
It significantly improves the accuracy and comprehensiveness of the triggering conditions identification of expected functional safety hazard events of vehicle-road collaborative autonomous driving systems, reduces the potential safety risks of the system, enhances the integrity and comprehensiveness of the system control structure, and ensures the accuracy of information flow. and controllability.
Smart Images

Figure CN119025856A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of autonomous driving, and specifically relates to a vehicle-road cooperative autonomous driving system and a method for analyzing triggering conditions of safety hazard events. Background Art
[0002] The vehicle-road cooperative automatic driving system is a collaborative working system that combines vehicles and road infrastructure. It realizes information exchange and collaborative operation between vehicles and road infrastructure through vehicle networking technology. In recent years, with the widespread application of vehicle-road cooperative automatic driving technology in intelligent network environment, the safety of vehicle-road cooperative automatic driving system has received increasing attention and research. The safety system of vehicle-road cooperative automatic driving covers five aspects: passive safety, behavioral safety, information security, functional safety and intended functional safety. According to the definition of ISO 21448, the intended functional safety (Safety Of The Intended Functionality, SOTIF) aims to avoid unreasonable risks of harm caused by functional design defects or insufficient implementation through targeted safety design. Due to performance limitations, insufficient specifications or reasonably foreseeable misuse, the intended functional safety problems caused by them are gradually exposed, becoming a key problem restricting the safety assurance of vehicle-road cooperative automatic driving system. If the triggering conditions of the intended functional safety hazard events of the vehicle-road cooperative automatic driving system cannot be effectively and comprehensively identified, it will have a serious impact on the vehicle-road cooperative automatic driving system in the intelligent network environment.
[0003] Traditional safety analysis methods mainly focus on specific software and hardware failures or electronic failures, and rely heavily on expert experience and knowledge. The analysis of hazard events and risk trigger sources is not clear and thorough enough. The analysis of trigger conditions for expected functional safety hazard events mainly uses the System Theoretical Process Analysis (STPA) method to identify functional insufficiency hazard trigger conditions. STPA regards the system as a whole and the safety issues of the system as control issues. Through the analysis of the system, it defines vehicle-level hazards and safety constraints, establishes a system-level hierarchical control structure, identifies unsafe control behaviors, and identifies typical causal scenarios to analyze trigger conditions, thereby avoiding the occurrence of hazardous accidents. However, there is currently a lack of combining traditional safety analysis methods with STPA methods to conduct expected functional safety analysis for vehicle-road cooperative autonomous driving systems. Therefore, combining traditional safety analysis methods with STPA methods and applying them to vehicle-road cooperative autonomous driving systems to analyze the trigger conditions for expected functional safety hazard events is an urgent problem to be solved. Summary of the invention
[0004] The purpose of the embodiments of the present invention is to provide a method for analyzing trigger conditions of a vehicle-road cooperative automatic driving system and safety hazard events, the main steps of which are to standardize the functions of the vehicle-road cooperative automatic driving system, define the system design operating conditions (Operational Design Condition, ODC), and analyze the system decision-making logic process; clarify the system vehicle-level hazard and risk assessment, identify performance limitations and trigger conditions, and establish a multi-level hierarchical control structure of the system; identify unsafe control behaviors that may cause danger, trace the cause and effect of hazardous events or unsafe control behaviors, and identify system trigger conditions. The analysis method provided by the present invention can significantly improve the accuracy and comprehensiveness of the identification of trigger conditions for expected functional safety hazard events of the vehicle-road cooperative automatic driving system, thereby solving at least one technical problem involved in the background technology.
[0005] In order to solve the above-mentioned technical problems, the present invention is achieved as follows:
[0006] On the one hand, an embodiment of the present invention provides a method for analyzing trigger conditions of safety hazard events of vehicle-road cooperative autonomous driving, comprising the following steps:
[0007] Step 1: Standardize the functions of the vehicle-road cooperative autonomous driving system, define the system design and operation conditions, and analyze the system decision-making logic process;
[0008] Step 2: Clarify the system vehicle-level hazards and define the safety constraints corresponding to the system vehicle-level hazards; conduct risk assessment based on the system functional specifications and safety constraint requirements, preliminarily build performance limitations and trigger condition tables, and establish a multi-level hierarchical system control structure. The first-level hierarchical control structure models the overall system structure, and the second-level hierarchical control structure combines the environment to refine the modeling of the system sub-modules;
[0009] Step three: Identify unsafe control behaviors that may lead to danger based on the control structure at different levels of the system, and identify the system performance limitations and corresponding trigger conditions for hazardous events or unsafe control behaviors.
[0010] On the other hand, the present invention further provides a control structure of a vehicle-road cooperative automatic driving system for implementing the method, comprising a first-level hierarchical control structure and a second-level hierarchical control structure, wherein the first-level hierarchical control structure comprises a driver module, an HMI system, a vehicle-side module, a roadside module, a cloud module and an environmental information module, wherein:
[0011] The environmental information module is used to collect environmental information and send the corresponding environmental information to the driver module, the vehicle-side module, the cloud module and the roadside module respectively;
[0012] The driver module is used to receive environmental information and send driver status information and system control switch information to the HMI system module;
[0013] The HMI system module is used to receive driver status information and system control switch information and send system operation status system switch control information to the vehicle-side module for control;
[0014] The vehicle-side module is used to receive environmental information and send vehicle status information to other road participants in the environmental information module;
[0015] The roadside module is used to receive environmental information and send all vehicle status information of the road section to the cloud module and the vehicle-side module;
[0016] The cloud module is used to receive and process control information, and then feed back the collaborative decision-making control information of each vehicle to the vehicle-side module and other road participants in the environmental information module through the roadside module. The vehicle-side module then feeds back the system operation status and system request information of the vehicle-side to the driver module through the HMI system module to form a closed-loop control;
[0017] The cloud module also receives environmental information, and performs overall processing on the vehicle status information sent by the roadside module, the vehicle status information sent by the vehicle-side module, and the vehicle request information, and feeds back the dispatch information, other vehicle information, and road information to the vehicle-side module, and feeds back the decision control information of each vehicle to the roadside module;
[0018] The second-level hierarchical control structure analyzes the control architecture of the roadside module, the cloud module and the vehicle-side module in combination with specific environmental conditions.
[0019] Compared with the prior art, the present invention has the following beneficial effects:
[0020] 1. The present invention provides a method for analyzing trigger conditions of safety hazard events based on the vehicle-road cooperative automatic driving system. It combines the advantages of FTA in easily identifying key failure modes of complex systems, and combines STPA with the FTA method. Compared with the traditional STPA analysis method, it can accurately identify the trigger conditions and performance limitations of expected functional safety hazard events of the high-speed ramp cooperative lane merging system; compared with the completely traditional safety analysis method (FTA), it can comprehensively and meticulously consider the interaction relationship between system components and software type hazards, and fully improve the comprehensiveness of system safety analysis.
[0021] 2. The proposed functional specifications of the vehicle-road cooperative autonomous driving system provide a basis for the system to construct vehicle-level hazards, establish safety constraints, and model multi-level hierarchical control structures. It provides an effective solution for the safety of vehicle-road cooperative autonomous driving technology in an intelligent network environment and reduces the potential safety risks of the system.
[0022] 3. Compared with the hierarchical control structure of the traditional STPA system level, the proposed multi-level hierarchical control structure defines the information interaction relationship between subsystems in detail, ensures the accuracy of information flow, improves the overall responsiveness of the system, clarifies the definition of the internal components of the subsystem, helps to better understand the internal operation mechanism of the system, and systematically manages the information interaction relationship between the internal components of the subsystem, ensuring the orderliness and controllability of information flow within the system. By constructing the hierarchical control structure in a hierarchical and detailed manner, the monitoring and prediction capabilities of the system behavior are enhanced, ensuring the integrity and comprehensiveness of the system control structure. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work, among which:
[0024] Figure 1 A first-level hierarchical control structure diagram of the vehicle-road cooperative automatic driving system provided by the present invention;
[0025] Figure 2 A hierarchical control structure diagram of the roadside module provided by the present invention;
[0026] Figure 3 A hierarchical control structure diagram of the vehicle-side module provided by the present invention;
[0027] Figure 4 A hierarchical control structure diagram of the cloud module provided by the present invention;
[0028] Figure 5 A flow chart of the method for analyzing trigger conditions of safety hazard events provided by the present invention;
[0029] Figure 6 A schematic diagram of system functions in an intelligent network environment provided by the present invention;
[0030] Figure 7 A decision logic process diagram of the vehicle cooperative merging function provided by the present invention;
[0031] Figure 8 A logical flow chart of the method for analyzing the triggering conditions of safety hazard events provided by the present invention. DETAILED DESCRIPTION
[0032] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0033] The terms "first", "second", etc. in the specification and claims of the present invention are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second", etc. are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0034] See also Figure 1 As shown, an embodiment of the present invention provides a vehicle-road cooperative automatic driving system, including a first-level hierarchical control structure and a second-level hierarchical control structure, wherein the first-level hierarchical control structure includes a driver module 1, an HMI system 2, a vehicle-side module 3, a roadside module 4, a cloud module 5 and an environmental information module 6.
[0035] The environmental information module 6 is used to collect environmental information and send the corresponding environmental information to the driver module 1, the vehicle-side module 3, the cloud module 5 and the roadside module 4 respectively.
[0036] The environmental information includes road information, road facility information, target object information, vehicle status information, external weather status information, sensor perception information and traffic flow information.
[0037] The driver module 1 is used to receive environmental information and send driver status information and system control switch information to the HMI system module 2 .
[0038] Specifically, the environmental information received by the driver module 1 includes road information, weather information, road facility information and target object information.
[0039] The HMI system module 2 is used to receive driver status information and system control switch information and send system operation status system switch control information to the vehicle-end module 3 for control.
[0040] The vehicle-side module 3 is used to receive environmental information and send vehicle status information to other road participants in the environmental information module 6 .
[0041] Specifically, the environmental information received by the vehicle-side module 3 includes external weather status information, sensor perception information and other vehicle status information.
[0042] The roadside module 4 is used to receive environmental information and send all vehicle status information in the road section to the cloud module 5.
[0043] The environmental information received by the roadside module 4 includes road section information, vehicle status information, road facility information and road participant information.
[0044] The cloud module 5 is used to receive and process control information, and then feed back the collaborative decision-making control information of each vehicle to the vehicle-side module 3 and other road participants in the environmental information module 6 through the roadside module 4. The vehicle-side module 3 then feeds back the system operating status and system request information of the vehicle-side to the driver module 1 through the HMI system 2 module to form a closed-loop control.
[0045] The cloud module 5 also receives environmental information, and performs overall processing on the vehicle status information sent by the roadside module 4 and the vehicle status information and vehicle request information sent by the vehicle-end module 3, and feeds back scheduling information, other vehicle information and road information to the vehicle-end module 3, and feeds back the decision-making control information of each vehicle to the roadside module 4.
[0046] Specifically, the environmental information received by the cloud module 5 includes weather information, road section condition information and traffic flow information.
[0047] The second-level hierarchical control structure analyzes the control architecture of the roadside module 4, the cloud module 5, and the vehicle-side module 3 in combination with the specific environmental conditions (intelligent network environment).
[0048] Recombination Figure 2As shown, the roadside module 4 includes a roadside perception module 41, a roadside computing module 42 and a roadside communication module 43. The roadside perception module 41 receives environmental information (road section information, vehicle status information, road facilities, road participant information) from the environmental information module and vehicle-side perception information and cloud-side perception information from the roadside communication module 43, and then sends control information (vehicle position, speed, acceleration, external environment, traffic flow data information, roadside and vehicle-side collaborative perception information) to the roadside computing module 42. The roadside computing module 42 then sends the control information calculated and processed by the roadside edge computing unit MEC to the roadside communication module 43. The roadside communication module 43 feeds back the information reception result to the roadside computing module 42, and the roadside computing module 42 feeds back the calculation result to the roadside perception module 41 to form a closed-loop control.
[0049] The roadside communication module 43 communicates with the vehicle-side OBU (On Board Unit) through the roadside communication unit RSU, receives the vehicle decision control scheme, vehicle perception information and collaborative perception information of the roadside perception module from the vehicle-side module 3 and transmits it to the cloud module 5 in the form of a vehicle status information stream, and at the same time receives the collaborative decision control scheme and cloud environment information fed back from the cloud module 5, and transmits the information to the roadside perception module 41 and the vehicle-side module 3 through the roadside communication unit RSU in the roadside communication module 43 to form a closed-loop feedback.
[0050] Recombination Figure 3As shown, the vehicle-side module 3 includes a communication module 31, a perception module 32, a decision control module 33, an execution module 34 and a sensor 35. The sensor 35 includes a speed sensor, an acceleration sensor, etc., which is used to receive sensor information (external environment information, distance, speed, position, road environment and road attributes of the target object) and send it to the perception module 32. The perception module 32 also receives information from the road side communication unit RSU (Road Side The control module 33 receives the positioning perception information output by the perception module 32 and the collaborative decision control instructions of the roadside and the cloud to select a decision strategy, generate a path planning, and obtain control instructions. The execution module 34 receives the decision information and control instructions from the decision control module 33 and the system status execution monitoring information transmitted by the driver through the HMI system to control the steering, drive control, and brake control execution operations. After completing the execution operation, the execution module 34 feeds back the execution status to the communication module 31 and the decision control module 33. The decision control module 33 then feeds back the decision control status to the perception module 32 to form a closed-loop control. At the same time, the decision control module 33 feeds back the vehicle-side decision control request to the road side, the cloud side, the driver, and the HMI system side through the communication module 31, and the system as a whole forms feedback.
[0051] It should be noted that the perception module 32 includes a millimeter wave radar and a camera.
[0052] Recombination Figure 4 As shown, the cloud module 5 includes an application platform 51, a data receiving and sending module 52, a data processing and computing module 53 and a database 54. The application platform 51 receives regional cloud information (meteorological information, high-precision map information, video entertainment information, road condition information), and transmits the regional cloud information to the data receiving and sending module 52. At the same time, the data receiving and sending module 52 also receives perception information from the vehicle side and the road side, and sends the regional road section and vehicle status information flow formed by the information combination and classification to the data processing and computing module 53. The data processing and computing module 53 performs multi-source data fusion processing on the transmitted data to obtain a multi-source fusion data set and stores it in the database 54. The database 54 then feeds back the data processing and computing results to the data processing and computing module 53. The data receiving and sending module 53 receives the calculation result feedback and feeds back the collaborative decision control information to the vehicle-road side according to the received information, and feeds back the regional vehicle status information flow to the application platform 51, forming a system overall feedback.
[0053] It should be noted that the data processing and computing module 53 includes cloud computing, big data processing, etc.
[0054] See also Figure 5 As shown, the present invention also provides a method for analyzing trigger conditions of vehicle-road cooperative automatic driving safety hazard events based on the vehicle-road cooperative automatic driving system, comprising the following steps:
[0055] Step S1, standardize the functions of the vehicle-road cooperative automatic driving system, define the system design and operation conditions, and analyze the system decision-making logic process;
[0056] Step S2, clarify the system vehicle-level hazards and define the safety constraints corresponding to the system vehicle-level hazards; conduct risk assessment based on the system function specifications and safety constraint requirements, preliminarily build performance limitations and trigger condition tables, and establish a multi-level hierarchical system control structure. The first-level hierarchical control structure models the overall system structure, and the second-level hierarchical control structure combines the environment to refine the modeling of the system submodules;
[0057] Step S3, identifying unsafe control behaviors that may cause danger according to the control structures at different levels of the system, and identifying system performance limitations and corresponding triggering conditions for hazardous events or unsafe control behaviors.
[0058] In step one, the main functions of the vehicle-road cooperative automatic driving system include the roadside communication unit RSU obtaining all vehicle information within the communication coverage area, the roadside edge computing unit MEC (Mobile Edge Computing) making collaborative decisions and controls on vehicles in the road section, and the vehicles in the road section executing the decision-making and control information transmitted by the roadside communication unit RSU.
[0059] Define the system design operating conditions based on the system functional specifications. The design operating conditions cover the design operating scope ODD (Operational Design Domain), vehicle status, driver and passenger status and other necessary conditions, clarify the requirements for elements within the system ODC, and define the system design operating conditions.
[0060] Based on the system function specification and the system design operating condition definition, the system decision logic process is analyzed. First, the perception end uses the road-side perception module and the vehicle-side perception module to jointly perceive the environmental information, and the system decision logic process is regulated by the road-side calculation module 42. Finally, the decision control information is sent to the vehicles within the road-side communication coverage through the road-side communication module 43.
[0061] In step 2, vehicle-level hazards include collision with the vehicle in front, collision with the obstacle in front, rear-end collision with the vehicle behind, HMI system unable to process driver takeover information, roadside communication unit RSU communication interruption, collision with vehicles within the communication range of the roadside communication unit RSU, etc.
[0062] Safety constraints are conditions or behaviors that the system must meet to prevent danger and ultimately prevent losses. Based on the defined vehicle-level hazards, system-level safety constraints can be clarified, mainly including maintaining a minimum safe distance from the vehicle in front, the perception unit should identify obstacles to avoid collisions, the roadside communication unit RSU collaborative decision-making to control the speed and distance of vehicles within the roadside communication coverage to avoid unexpected control behaviors on the vehicle side, the vehicle side should respond to the driver's takeover information in a timely and correct manner, the roadside communication unit RSU should ensure normal communication, and vehicles within the communication range of the roadside communication unit RSU should avoid collisions.
[0063] Risk assessment determines whether the vehicle-level hazard is related to the expected functional safety and is uncontrollable, and is evaluated using severity and controllability. The severity assessment of hazardous events and their potential consequences is defined as severity S. Unlike the specific S, E, and C levels in ISO26262, the value of S in SOTIF is limited to 0 and greater than 0. When S is greater than 0, it means that the severity of the hazardous event is unacceptable; when S is equal to 0, it means that the severity of the hazardous event is acceptable. Controllability C is an assessment of the controllability of hazardous events and their potential consequences, and it also only takes two values: 0 and greater than 0. When C is greater than 0, it means that the occurrence of the hazardous event is uncontrollable; when C is equal to 0, it means that the occurrence of the hazardous event is controllable. Hazardous events are only considered acceptable when both S and C are 0. In any other case, hazardous events are unacceptable and corresponding measures need to be taken to prevent their occurrence. A multi-level hierarchical system control structure is established. The first-level hierarchical control structure models the overall system structure, and the second-level hierarchical control structure refines the modeling of the system sub-modules in combination with the environment.
[0064] In step three, unsafe control behavior refers to control behavior that causes harm to the entire vehicle under specified circumstances and the worst environment. The specific process is to conduct a safety analysis on the control behavior of each controller in the control structure based on the STPA hierarchical control structure and STPA guide words to identify unsafe control behaviors that cause vehicle-level harm to the system.
[0065] Then, the Fault Tree Analysis (FTA) method is used to analyze downward from hazardous events and unsafe control behaviors in the form of AND or OR, considering why unsafe control behaviors occur and why control behaviors are poorly executed or not executed, leading to danger, so as to obtain the risk trigger source and trigger mechanism of hazardous events (the trigger source is an element with specific attributes and characteristics that can cause system performance limitations. The trigger mechanism is the way in which the trigger conditions are formed by the trigger mode and trigger factors. The trigger mode is the way in which the trigger conditions are formed at different working stages of the system under the direct influence of the trigger source. The trigger factor is the key attribute that affects the system function or performance at different working stages under different trigger modes).
[0066] By analyzing the unsafe control behaviors of the vehicle-road cooperative autonomous driving system in the intelligent network environment, the vehicle-side system structure is refined into perception, decision-making, control, communication, etc., and the two relational operators "and" and "or" are used to trace the hazards, and the causes of unacceptable hazardous events in risk assessment are obtained. The performance limitations are matched with the trigger conditions, so as to analyze and evaluate the performance limitation table and trigger condition table of hazardous events.
[0067] The vehicle-road cooperative automatic driving method provided by the present invention is described in detail below with reference to specific embodiments.
[0068] Example
[0069] Recombination Figure 6 As shown in the figure, the high-speed ramp cooperative lane merging system in the vehicle-road cooperative automatic driving system is used as an example to illustrate the applicability and advantages of this method. First, the function of the high-speed ramp cooperative lane merging system is described. The vehicle control in the ramp merging area under the intelligent network environment is mainly divided into four areas, namely the upstream merging area, the early lane change area, the cooperative merging area and the downstream merging area. The following is a detailed introduction to the details of the four major partitions and the functions performed.
[0070] 1. The upstream of the merging area is located in the collaborative merging starting area. The roadside communication unit RSU is responsible for detecting road information, vehicle information, and vehicle service request information within its communication coverage. Once a vehicle is detected passing through the main road or ramp, the roadside communication unit RSU immediately transmits this information to the roadside edge computing unit MEC for further processing and decision-making.
[0071] 2. The early lane change area is located upstream of the merging area. Its core function is to coordinate the lane changes of the main road fleet and calculate the coordinated speed and merging point. After the main road fleet enters the early lane change area, the roadside communication unit RSU will receive service request information and vehicle status information flow from all vehicles within the roadside communication coverage area, and pass the information to the roadside edge computing unit MEC to determine whether the fleet on the main road 1 needs to change lanes. Then, the coordinated speed and merging position of the vehicle are calculated in the roadside edge computing unit MEC, and finally the decision control information and merging position of the fleet and ramp vehicles are sent to the cooperative vehicle through the roadside communication unit RSU.
[0072] 3. The collaborative merging area is a key area for coordinating vehicle speeds, adjusting fleet gaps, and completing merging operations. In this area, the roadside communication unit RSU detects the speed, position, acceleration, vehicle requests, and other information of the fleet and ramp vehicles at any position in real time. The roadside communication unit RSU ensures that the collaborative vehicles follow the decision-making control information it provides, and the driver ensures that the vehicle does not perform abnormal control (lane changes, arbitrary acceleration and deceleration, overtaking) and other behaviors. In addition, the roadside communication unit RSU is also responsible for regulating the speed of the main road fleet and ramp vehicles, creating a reasonable gap at the merging point, thereby ensuring that ramp vehicles can merge smoothly and safely.
[0073] 4. The downstream of the merging area is the area after the merging operation is completed. In this area, vehicles continue to drive normally based on their own status and the latest decision-making control information provided by the roadside communication unit RSU, thereby ensuring smooth and safe traffic flow.
[0074] Design operating conditions refer to the general term for various conditions applicable to the functional operation of the driving automation system determined during the design, including the design operating range, vehicle status, driver and passenger status, and other necessary conditions. Compared with the single-vehicle automatic driving system, the highway ramp cooperative lane merging system ODC has the following requirements: to ensure the normal operation of the roadside module and cloud module sub-functions, the main road lane lines are greater than or equal to 2, the road surface quality is good, there are clear traffic signs, the lane lines are clear and complete, the lane driving direction is to drive on the right, the daily rainfall is less than 10mm, the wind speed does not exceed level 4, the visibility is greater than 2km, there is no snow and fog, and the vehicle functional status meets the system design requirements.
[0075] Design of decision logic process of cooperative lane merging system on highway ramp Figure 7 As shown in the figure, based on the operation characteristics of vehicles in the merging area, the vehicle decision-making logic process in the intelligent connected environment can be summarized into the following steps:
[0076] 1. Obtain vehicle information in the ramp merging area;
[0077] 2. Determine whether the vehicle on the main road needs to change lanes;
[0078] 3. The roadside edge computing unit MEC makes collaborative decisions to control the merging vehicles to coordinate their speed;
[0079] 4. Vehicles on the main road and ramp complete the ramp merger.
[0080] After completing the system function description, the key control action (system identification of ramp vehicles) is analyzed in combination with the specific environment (intelligent network environment) and STPA guide words (required but not provided), and then the severity and controllability are used to evaluate the hazardous event. The evaluation result is unacceptable (S>0, the ramp vehicle has a high speed, C>0, and the high-speed vehicle cannot brake in time to avoid a collision). The next step is to model the system control structure. First, the system is initially divided into six modules: driver module, HMI system, vehicle-side module, roadside module, cloud module, and environmental information module. Then the roadside module is further decomposed into roadside perception module, roadside communication module, and roadside computing module.
[0081] A hazardous event or an unsafe control behavior in the STPA analysis method is taken as the top event of the FTA analysis method, and performance limitations and trigger conditions are taken as the bottom events of the FTA analysis method. Figure 8 The FTA analysis method is used to analyze the failure of the system to identify the ramp vehicles as a hazardous event when the main road fleet and the ramp vehicles merge in collaboratively, and a performance limitation table and a trigger condition table are summarized.
[0082] FTA analysis process Figure 8 As shown in the figure, when the main road fleet and the ramp vehicle merge in coordination, the system fails to identify the ramp vehicle as the top event of the FTA analysis method. First, it is divided into the driver module, roadside module, vehicle-side module, cloud module and other links. Then, according to the failure of the roadside perception module, roadside communication module, and roadside calculation module in the second-level hierarchical control structure to identify the ramp vehicle as an intermediate event, the roadside perception module is further subdivided into three major components: millimeter-wave radar, laser radar, and camera. Finally, the performance limitations and trigger conditions that may lead to the occurrence of harmful events are analyzed. Table 1 and Table 2 are the performance limitation table and trigger condition table of the roadside perception module, respectively.
[0083] Table 1 System performance limitations
[0084] serial number Performance Limitations (PL) PL-1 Millimeter wave radar uses low frequency PL-2 Millimeter wave radar has low resolution PL-3 Millimeter wave radar has a low detection angle PL-4 Millimeter wave radar detection distance is too short PL-5 Millimeter wave radar detection accuracy is insufficient PL-6 The operating temperature range of millimeter wave radar is too small PL-7 Millimeter-wave radar is blocked PL-8 The millimeter wave radar is installed in the wrong position PL-9 The camera sampling frequency is low PL-10 The camera is affected by visibility and its perception ability is reduced PL-11 Camera affected by humidity PL-12 Camera affected by temperature PL-13 Camera pixel is too low PL-14 Camera detection distance is insufficient PL-15 The camera is not installed in the correct position PL-16 Too much camera distortion PL-17 The camera has low contrast and is affected by lighting PL-18 LiDAR is blocked PL-19 …
[0085] Table 2 System trigger conditions
[0086]
[0087]
[0088] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.
[0089] In addition, it should be noted that the scope of the methods and systems in the embodiments of the present invention is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.
[0090] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the enlightenment of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.
Claims
1. A method for analyzing trigger conditions of safety hazard events in vehicle-road cooperative automatic driving, characterized in that: The steps include: Step 1: Standardize the functions of the vehicle-road cooperative autonomous driving system, define the system design and operation conditions, and analyze the system decision-making logic process; Step 2: Identify the system vehicle-level hazards and define the safety constraints corresponding to the system vehicle-level hazards; Based on the system functional specifications and safety constraints, risk assessment is conducted, performance limitations and trigger condition tables are initially constructed, and a multi-level hierarchical system control structure is established. The first-level hierarchical control structure models the overall system structure, and the second-level hierarchical control structure combines the environment to refine the modeling of the system submodules. Step three: Identify unsafe control behaviors that may lead to danger based on the control structure at different levels of the system, and identify the system performance limitations and corresponding trigger conditions for hazardous events or unsafe control behaviors.
2. The method according to claim 1, characterized in that In step 1, the functions of the vehicle-road cooperative automatic driving system include the roadside communication unit RSU obtaining all vehicle information within the communication coverage area, the roadside edge computing unit MEC making collaborative decision-making and control on the vehicles in the road section, and the vehicles in the road section executing the decision-making and control information transmitted by the roadside communication unit RSU; Define the system design operating conditions, including the design operating conditions covering the design operating range ODD, vehicle status, driver and passenger status and other necessary conditions, clarify the requirements of the elements in the system ODC, and define the system design operating conditions; The decision logic process of the parsing system includes firstly using the roadside perception module and the vehicle-side perception module to jointly perceive the environmental information at the perception end, regulating the decision logic process of the system through the roadside calculation module, and finally sending the decision control information to the vehicles within the coverage of the roadside communication through the roadside communication module.
3. The method according to claim 1, characterized in that: In step 2, vehicle-level hazards include collision with the vehicle ahead, collision with the obstacle ahead, rear-end collision with the vehicle behind, the HMI system cannot process the driver takeover information, the roadside unit RSU communication is interrupted, and the vehicle within the RSU communication range collides; Safety constraints include maintaining a minimum safe distance from the vehicle in front, the perception unit should identify obstacles to avoid collisions, the roadside communication unit RSU should make collaborative decisions to control vehicles within the roadside communication coverage to adjust the speed and distance so that the vehicle side can avoid unexpected control behavior, the vehicle side should respond to the driver's takeover information in a timely and correct manner, the roadside communication unit RSU should ensure normal communication, and vehicles within the communication range of the roadside communication unit RSU should avoid collisions.
4. The method according to claim 1, characterized in that: In step three, unsafe control behavior refers to control behavior that causes harm to the entire vehicle under specified circumstances and the worst environment, including: conducting safety analysis on the control behavior of each controller in the control structure based on the STPA hierarchical control structure and STPA guide words, and identifying unsafe control behaviors that cause vehicle-level harm to the system.
5. The method according to claim 4, characterized in that Identify system performance limitations and corresponding triggering conditions for hazardous events or unsafe control behaviors, including: The fault tree analysis method is used to analyze downward from hazardous events and unsafe control behaviors in the form of AND or OR, considering why unsafe control behaviors occur and why control behaviors are poorly executed or not executed, leading to danger, so as to obtain the risk trigger source and trigger mechanism of hazardous events. By analyzing the unsafe control behaviors of the vehicle-road cooperative autonomous driving system in the intelligent network environment, the vehicle-side system structure is refined into perception, decision-making, control and communication, and the two relational operators "AND" and "OR" are used to trace the hazards, and the causes of unacceptable hazardous events in risk assessment are obtained. The performance limitations are matched with the trigger conditions, so as to analyze and evaluate the performance limitation table and trigger condition table of hazardous events.
6. A vehicle-road cooperative automatic driving system control structure for implementing the method described in any one of claims 1 to 5, characterized in that: It includes a first-level hierarchical control structure and a second-level hierarchical control structure, wherein the first-level hierarchical control structure includes a driver module, an HMI system, a vehicle-side module, a roadside module, a cloud module and an environmental information module, wherein: The environmental information module is used to collect environmental information and send the corresponding environmental information to the driver module, the vehicle-side module, the cloud module and the roadside module respectively; The driver module is used to receive environmental information and send driver status information and system control switch information to the HMI system module; The HMI system module is used to receive driver status information and system control switch information and send system operation status system switch control information to the vehicle-side module for control; The vehicle-side module is used to receive environmental information and send vehicle status information to other road participants in the environmental information module; The roadside module is used to receive environmental information and send all vehicle status information of the road section to the cloud module and the vehicle-side module; The cloud module is used to receive and process control information, and then feed back the collaborative decision-making control information of each vehicle to the vehicle-side module and other road participants in the environmental information module through the roadside module. The vehicle-side module then feeds back the system operation status and system request information of the vehicle-side to the driver module through the HMI system module to form a closed-loop control; The cloud module also receives environmental information, and performs overall processing on the vehicle status information sent by the roadside module, the vehicle status information sent by the vehicle-side module, and the vehicle request information, and feeds back the dispatch information, other vehicle information, and road information to the vehicle-side module, and feeds back the decision control information of each vehicle to the roadside module; The second-level hierarchical control structure analyzes the control architecture of the roadside module, the cloud module and the vehicle-side module in combination with specific environmental conditions.
7. The vehicle-road cooperative automatic driving system control structure according to claim 6, characterized in that: The environmental information collected by the environmental information module includes road information, road facility information, target object information, vehicle status information, external weather status information, sensor perception information and vehicle flow information.
8. The vehicle-road cooperative automatic driving system control structure according to claim 7, characterized in that: The roadside module includes a roadside perception module, a roadside computing module and a roadside communication module. The roadside perception module receives environmental information from the environmental information module and vehicle-side perception information and cloud-side perception information from the roadside communication module, and then sends control information to the roadside computing module. The roadside computing module then sends the control information calculated and processed by the roadside edge computing unit MEC to the roadside communication module. The roadside communication module feeds back the information reception result to the roadside computing module, and the roadside computing module then feeds back the calculation result to the roadside perception module to form a closed-loop control. The roadside communication module communicates with the vehicle-side OBU through the roadside communication unit RSU, receives the vehicle decision control scheme, vehicle perception information and collaborative perception information of the roadside perception module from the vehicle-side module and transmits them to the cloud module in the form of vehicle status information stream, and at the same time receives the collaborative decision control scheme and cloud environment information fed back from the cloud module, and transmits the information to the roadside perception module and the vehicle-side module through the roadside communication unit RSU in the roadside communication module to form a closed-loop feedback.
9. The vehicle-road cooperative automatic driving system control structure according to claim 8, characterized in that: The vehicle-side module includes a communication module, a perception module, a decision control module, an execution module and a sensor. The sensor receives sensing information and sends it to the perception module. The perception module simultaneously receives roadside information and other vehicle status information transmitted from the roadside communication unit RSU through the communication module for data processing, scenario understanding and data fusion processing. The decision control module receives the positioning perception information output by the perception module and the collaborative decision control instructions of the roadside and the cloud to select a decision strategy, generate a path planning and obtain control instructions. The execution module receives the decision information and control instructions from the decision control module and the system status execution monitoring information transmitted by the driver through the HMI system to control steering, drive control and brake control execution operations. After completing the execution operation, the execution module feeds back the execution status to the communication module and the decision control module. The decision control module then feeds back the decision control status to the perception module to form a closed-loop control. At the same time, the decision control module feeds back the vehicle-side decision control request to the road side, the cloud side, the driver and the HMI system side through the communication module, and the system as a whole forms feedback.
10. The vehicle-road cooperative automatic driving system control structure according to claim 9, characterized in that: The cloud module includes an application platform, a data receiving and sending module, a data processing and computing module and a database. The application platform receives regional cloud information and transmits the regional cloud information to the data receiving and sending module. At the same time, the data receiving and sending module also receives perception information from the vehicle side and the road side, and sends the regional road section and vehicle status information flow formed by the information combination and classification to the data processing and computing module. The data processing and computing module performs multi-source data fusion processing on the transmitted data to obtain a multi-source fusion data set and stores it in the database. The database then feeds back the data processing and computing results to the data processing and computing module. The data receiving and sending module receives the calculation result feedback and feeds back the collaborative decision-making control information to the vehicle-road side according to the received information, and feeds back the regional vehicle status information flow to the application platform to form overall system feedback.
Citation Information
Patent Citations
Automatic driving decision-making system trigger event construction method
CN113887057A
Automatic driving expected function safety triggering condition model evaluation method and system
CN114091256A
Control method, roadside equipment and system for vehicle-road cooperative automatic driving
CN114995451A
Control method, roadside equipment, cloud control platform and system for vehicle-road cooperative automatic driving
CN115016474A
Cited By
Vehicle cloud collaborative perception decision-making high-speed automatic auxiliary navigation driving method
CN120246019A
