Vehicle for performing minimum risk maneuver and method of operating same

By defining the termination conditions and processes of the HMI function in an autonomous driving vehicle, and monitoring the vehicle status and environmental information by using the processor, the effective management and notification of minimum risk manipulation is achieved, solving the problem of termination of the minimum risk manipulation function in autonomous driving, reducing the Collision risk and improves traffic safety.

CN118928459APending Publication Date: 2024-11-12HYUNDAI MOTOR CO LTD +1
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202410569905.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-22
Filing Date
2024-05-09
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In autonomous vehicles, the prior art fails to clarify how and when to terminate the HMI function of the lowest risk manipulation function, resulting in the inability to effectively manage and notify vehicle users and surrounding vehicles.

Method used

Provide different termination processes by defining conditions to activate internal and external information human-machine interface (HMI) functions in the vehicle, and using the processor to monitor vehicle status and surrounding environment information, determine whether minimum risk manipulation is required, and control the vehicle's minimum risk of execution Manipulate and notify the user through indicator lights and multiple alerts, ultimately ending the minimum risk manipulation when the user intervenes or the vehicle stops.

Benefits of technology

It realizes effective management and notification of minimum risk manipulation status during autonomous driving, reduces collision risks, and converts the vehicle to a user-drivable state if necessary, improving traffic safety.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118928459A_ABST
    Figure CN118928459A_ABST
Patent Text Reader

Abstract

Embodiments of the invention relate to a vehicle for performing a minimum risk maneuver and a method of operating the same. The autonomous vehicle includes: at least one sensor configured to detect an ambient environment of the vehicle to generate ambient environment information; a controller configured to control an operation of the vehicle; and a processor. The processor is configured to: monitor a vehicle state to generate vehicle state information; determining whether a lowest risk manipulation is required; performing the minimum risk maneuver by causing the controller to control automatic driving of the vehicle based on the need for the minimum risk maneuver; providing an indication of minimum risk maneuver initiation to a user within the vehicle; and turning on and off an external indicator indicating the execution of the lowest risk maneuver.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present invention relate to a vehicle and method of operating the same for performing a minimum risk maneuver. Background Art

[0002] Advanced driver assistance systems (ADAS) have been developed to help drivers. ADAS encompasses a variety of sub-technologies and can provide considerable convenience to users. These ADAS systems are also known as autonomous driving systems or automated driving systems (ADS).

[0003] In the event of an unforeseen accident or failure during autonomous driving, the minimum risk maneuvering function can be executed to minimize the risk of collision with surrounding vehicles and reach the minimum risk state in a short time, and it is beneficial to notify relevant parties outside and inside the vehicle to prevent accidents in advance. Summary of the invention

[0004] In an automated driving vehicle, the conditions for activating the internal information human-machine interface (HMI) function to notify the vehicle user when the minimum risk maneuvering function is activated, and the conditions for activating the external information HMI function to notify surrounding vehicles that the minimum risk maneuvering function has been activated are defined. However, it is not clear when and how the activated HMI function should be terminated.

[0005] Various embodiments of the present invention may provide a vehicle control method that divides an HMI function, which notifies the operation of a lowest risk operation function, into an external interface and an internal interface to enable use of different termination procedures.

[0006] The technical objectives of the present invention are not limited to those described above, and those skilled in the art can clearly understand other objectives not described herein from the following description.

[0007] According to one or more embodiments of the present invention, a vehicle may include: at least one sensor configured to detect the surroundings of the vehicle to generate surrounding information; a controller configured to control the operation of the vehicle; and a processor. The processor may be configured to: monitor the state of the vehicle to generate vehicle state information; and during automatic driving of the vehicle, determine whether a minimum risk maneuver is required based on at least one of the surrounding information or the vehicle state information. The minimum risk maneuver may include controlling the vehicle to reduce the risk of collision. The processor may also be configured to: perform a minimum risk maneuver based on the need for a minimum risk maneuver by causing the controller to control the automatic driving of the vehicle; provide an indication of the start of a minimum risk maneuver to a user in the vehicle; based on the execution of the minimum risk maneuver, turn on an external indicator light indicating the execution of the minimum risk maneuver; and turn off the external indicator light based on the user's operation of the external indicator light button.

[0008] The processor may also be configured to: determine whether to perform a minimum risk maneuver based on the vehicle transitioning to a transition demand (TD) state. In the TD state, the vehicle may be configured to provide one or more notifications to a user to control the vehicle. The processor may also be configured to determine the level of automated driving of the vehicle based on determining that a minimum risk maneuver is performed in the TD state; monitor the user based on the level of automated driving of the vehicle being greater than or equal to a predetermined level of automation; and transition the vehicle to the TD state based on monitoring of the user indicating that the user is in a drivable state.

[0009] The processor may be further configured to provide a first notification requesting a user to take control of the vehicle after the vehicle transitions to the TD state.

[0010] The processor may also be configured to provide a second notification to request the user to control the vehicle based on a predetermined time elapsed after providing the first notification. The second notification has a higher intensity than the first notification.

[0011] The first notification and the second notification may include at least one of an auditory alert, a visual alert, and tactile feedback.

[0012] The processor may also be configured to determine to perform a minimum risk maneuver in the TD state based on a failure to obtain information required for autonomous driving of the vehicle.

[0013] The processor may also be configured to determine to perform a minimum risk maneuver based on detecting a physical fault associated with autonomous driving of the vehicle.

[0014] The processor may also be configured to determine whether to perform a minimum risk maneuver based on the vehicle transitioning to a transition demand (TD) state. In the TD state, the vehicle may be configured to provide one or more notifications to a user to control the vehicle. The processor may also be configured to determine the level of automated driving of the vehicle based on determining that a minimum risk maneuver is performed in the TD state; and transition the vehicle to the TD state based on the level of automated driving of the vehicle being less than or equal to a predetermined level of automation.

[0015] The processor may be further configured to: determine whether the minimal risk maneuver is terminated; and based on the minimal risk maneuver being terminated, clear the indication.

[0016] The processor may be further configured to determine that the minimal risk maneuver has terminated based on the vehicle having stopped and remained stationary.

[0017] According to one or more embodiments of the present invention, a method may include: during automatic driving of a vehicle, a processor determines whether a minimum risk maneuver is required based on at least one of surrounding environment information or vehicle status information. The minimum risk maneuver may include controlling the vehicle to reduce the risk of collision. The method may also include causing the vehicle to perform a minimum risk maneuver based on the need for a minimum risk maneuver; providing an indication of the start of the minimum risk maneuver to a user in the vehicle; based on the execution of the minimum risk maneuver, turning on an external indicator light indicating the execution of the minimum risk maneuver; and turning off the external indicator light based on the user's operation of an external indicator light button.

[0018] The method may also include: determining whether to perform a minimum risk maneuver based on the vehicle transitioning to a transition demand (TD) state. In the TD state, the vehicle may be configured to provide one or more notifications to a user to control the vehicle. The processor may also be configured to determine an autonomous driving level of the vehicle based on determining that a minimum risk maneuver is performed in the TD state; monitoring the user based on the autonomous driving level of the vehicle being greater than or equal to a predetermined automation level; and transitioning the vehicle to the TD state based on monitoring of the user indicating that the user is in a drivable state.

[0019] The method may further include providing a first notification to request a user to control the vehicle after the vehicle is transitioned to the TD state.

[0020] The method may also include providing a second notification to request the user to control the vehicle based on a predetermined time elapsed after providing the first notification. The second notification has a higher intensity than the first notification.

[0021] The first notification and the second notification may include at least one of an auditory alert, a visual alert, and tactile feedback.

[0022] The method may also include: determining to perform a minimum risk maneuver in the TD state based on a failure to obtain information required for autonomous driving of the vehicle.

[0023] The method may also include determining to perform a minimum risk maneuver based on detecting a physical fault associated with autonomous driving of the vehicle.

[0024] The method may also include: determining whether to perform a minimum risk maneuver based on the vehicle transitioning to a transition demand (TD) state. In the TD state, the vehicle may be configured to provide one or more notifications to a user to control the vehicle. The processor may also be configured to determine an automated driving level of the vehicle based on determining that a minimum risk maneuver is performed in the TD state; and transitioning the vehicle to the TD state based on the automated driving level of the vehicle being less than or equal to a predetermined automation level.

[0025] The method may also include: determining whether the minimal risk maneuver is terminated; and based on the minimal risk maneuver being terminated, clearing the indication.

[0026] The method may further include determining that the minimal risk maneuver has terminated based on the vehicle having stopped and remaining stationary. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 is a block diagram illustrating a vehicle according to various embodiments of the present invention;

[0028] Figure 2A is a diagram illustrating operation of an automated driving vehicle in a longitudinal fault level 1 or level 2 situation according to one embodiment;

[0029] Figure 2B is a diagram showing the operation of an autonomous driving vehicle in the case of longitudinal fault level 3 to level 5 according to another embodiment;

[0030] Figure 3 is a diagram showing a vehicle state-specific minimum risk maneuver (MRM) strategy according to various embodiments of the present invention;

[0031] Figure 4 is a diagram showing an exemplary screen layout on a display when the Highway Driving Pilot (HDP) function is activated;

[0032] Figure 5 is a flowchart illustrating a process of executing an MRM strategy in a vehicle according to various embodiments of the present invention;

[0033] Figure 6 is a flowchart illustrating a process of executing an MRM strategy in a vehicle according to various embodiments of the present invention;

[0034] Figure 7 is a flowchart illustrating vehicle operation when the MRM function is activated according to various embodiments of the present invention; and

[0035] Figure 8 is a flowchart illustrating an operation of a vehicle performing MRM according to various embodiments of the present invention. DETAILED DESCRIPTION

[0036] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0037] The construction of the present invention and its operational effects will be apparent from the detailed description provided below, which helps to clearly understand. Before the detailed explanation of this article, it should be noted that, whenever possible, the same reference numerals will be used for the same components even if shown on different drawings, and detailed descriptions of well-known components will be omitted to avoid obscuring the subject matter of the present invention.

[0038] Prior to the detailed explanation herein, the terms used herein may be defined as follows.

[0039] Vehicle refers to a vehicle that is equipped with an automated driving system (ADS) and is capable of automated driving. For example, the vehicle may perform at least one of steering, acceleration, deceleration, lane change, and stop (or parking) through the ADS without user intervention. The ADS may include, for example, at least one of a pedestrian detection and collision mitigation system (PDCMS), a lane change decision aid system (LCDAS), a lane departure warning system (LDWS), an adaptive cruise control (ACC), a lane keeping assist system (Lane Keeping Assistance System, LKAS), a road boundary departure prevention system (RBDPS), a curve speed warning system (CSWS), a forward vehicle collision warning system (FVCWS), and a low speed following (LSF).

[0040] Users are people who use the vehicle and can obtain services from the autonomous driving system.

[0041] Vehicle control authority refers to the authority to control at least one component and / or function of the vehicle. At least one function of the vehicle may include, for example, at least one of a steering function, an acceleration function, a deceleration function (or a braking function), a lane change function, a lane detection function, a lateral control function, an obstacle detection and distance sensing function, a powertrain control function, a safety zone detection function, an engine on / off function, a power on / off function, and a vehicle lock / unlock function. The listed vehicle functions are examples provided for illustrative purposes, and embodiments of the present invention are not limited thereto.

[0042] The shoulder refers to the space between the outermost road boundary (or outermost lane boundary) in the direction of vehicle travel and the edge of the road (such as curb, guardrail).

[0043] Figure 1is a block diagram illustrating a vehicle according to various embodiments of the present invention.

[0044] Figure 1 The vehicle configuration shown is provided as an exemplary embodiment, and each component may be configured as a chip, a component, or an electronic circuit, or a combination of chips, components, and / or electronic circuits. Figure 1 Some of the components shown may be divided into a plurality of components and configured as different chips, different components, or different electronic circuits, and some of the components may be combined to be configured as one chip, one component, or one electronic circuit. Figure 1 A portion of the components shown in the figure may be included, or other components not shown may be added.

[0045] Figure 2A is a diagram showing the operation of an automated driving vehicle in a longitudinal fault level 1 or level 2 situation according to one embodiment, Figure 2B is a diagram showing the operation of an autonomous driving vehicle in the case of longitudinal fault level 3 to level 5 according to another embodiment.

[0046] The longitudinal fault level can be considered to represent the severity of the faults that affect longitudinal control based on the severity of the fault. According to one embodiment, the longitudinal fault level can be defined from level 1 to level 5, where higher numbers represent more severe. For example, longitudinal fault level 1 is similar to normal vehicle driving, and can be a fault level where the autonomous vehicle can drive autonomously while maintaining a safe distance. On the other hand, longitudinal fault level 5 can represent a fault level where the autonomous vehicle is in a state where it cannot decelerate and requires user intervention for braking.

[0047] refer to Figure 1 , the vehicle 100 may include a sensor unit 110 , a controller 120 , a processor 130 , a display 140 , a communication device 150 , and a memory 160 .

[0048] According to various embodiments, the sensor unit 110 may detect the surroundings of the vehicle 100 using at least one sensor, and generate data related to the surroundings based on the detection results. In an embodiment, the sensor unit 110 may acquire road information, information about objects around the vehicle (e.g., other vehicles, pedestrians, objects, curbs, guardrails, lanes, obstacles), and / or position information of the vehicle based on the sensing data obtained from the at least one sensor. The road information may include, for example, lane position, lane shape, lane color, lane type, number of lanes, the presence of a shoulder, or the size of a shoulder. The objects around the vehicle may include, for example, the position of the object, the size of the object, the shape of the object, the distance to the object, and the relative speed of the object.

[0049] According to an embodiment, the sensor unit 110 may include at least one of a camera, a light detection and ranging (LiDAR), a radio detection and ranging (RADAR), an ultrasonic sensor, an infrared sensor, and a position measurement sensor. The listed sensors are provided only as examples for illustrative purposes, and the sensors included in the sensor unit 110 in the present invention are not limited thereto. The camera may capture images around the vehicle to generate image data, including lanes and / or surrounding objects in front of, behind, and / or on the side of the vehicle 100. The LiDAR may use light (or laser) to generate information about objects located in front of, behind, and / or on the side of the vehicle 100. The RADAR may use electromagnetic waves (or radio waves) to generate information about objects located in front of, behind, and / or on the side of the vehicle 100. The ultrasonic sensor may use ultrasonic waves to generate information about objects located in front of, behind, and / or on the side of the vehicle 100. The infrared sensor may use infrared rays to generate information about objects located in front of, behind, and / or on the side of the vehicle 100. The position measurement sensor may measure the current position of the vehicle. The position measurement sensor may include at least one of a global positioning system (GPS) sensor, a differential global positioning system (DGPS) sensor, and a global navigation satellite system (GNSS) sensor. The position measurement sensor may generate position data of the vehicle based on a signal generated by at least one of the GPS sensor, the DGPS sensor, and the GNSS sensor.

[0050] According to various embodiments, the controller 120 may control the operation of at least one component of the vehicle 100 and / or at least one function of the vehicle under the control of the processor 130. The at least one function may include, for example, at least one of a steering function, an acceleration function or a longitudinal acceleration function, a deceleration function or a longitudinal deceleration function, a braking function, a lane change function, a lane detection function, an obstacle detection and distance detection function, a lateral control function, a power system control function, a safety zone detection function, an engine on / off, a power on / off, and a vehicle lock / unlock function.

[0051] According to an embodiment, the controller 120 may control the operation of at least one component of the vehicle and / or at least one function of the vehicle under the control of the processor 130 to achieve automatic driving and / or minimum risk maneuvering (MRM) of the vehicle 100. The minimum risk maneuvering function may be a vehicle maneuvering function for minimizing (e.g., reducing) a known risk of collision with surrounding vehicles to achieve a minimum (e.g., reduced) risk state. For example, the controller 120 may perform the minimum risk maneuvering function by controlling the operation of at least one of a steering function, an acceleration function, a deceleration function, a lane change function, a lane detection function, a lateral control function, an obstacle detection and distance detection function, a powertrain control function, and a safety zone detection function.

[0052] According to various embodiments, the processor 130 may control the overall operation of the vehicle 100. In an embodiment, the processor 130 may include an electronic control unit (ECU) that is capable of overall control of components within the vehicle 100. For example, the processor 130 may include a central processing unit (CPU) or a microprocessing unit (MCU) that is capable of performing computing tasks.

[0053] According to various embodiments, the processor 130 may activate an advanced driver assistance system (ADAS) when a predetermined event occurs, thereby controlling components within the vehicle 100 to achieve autonomous driving. The predetermined event may occur when autonomous driving is requested by a user, when vehicle control authority is granted by a user, or when conditions specified by a user and / or a designer are met.

[0054] According to various embodiments, the processor 130 may determine whether autonomous driving is feasible based on at least one of vehicle state information and surrounding environment information during autonomous driving. When autonomous driving is determined to be not feasible, the processor 130 may determine and control the execution of the MRM strategy. Here, the MRM strategy may include an MRM type.

[0055] refer to Figure 2A , which shows the behavior changes of the autonomous driving vehicle when a level 1 or level 2 longitudinal fault event occurs in the autonomous driving vehicle. When the autonomous driving is started and operates normally, the processor 130 can perform a dynamic driving task (DDT) function to autonomously drive the vehicle.

[0056] According to an embodiment, the processor 130 may monitor the mechanical and / or electrical status of internal vehicle components (e.g., sensors, actuators, etc.) starting from the activation of autonomous driving and the start of the DDT function to obtain vehicle status information indicating whether mechanical and / or electrical failures occur in the internal vehicle components.

[0057] From the time when the autonomous driving is activated and the DDT function is started, the processor 130 may obtain environmental information around the vehicle using the sensor unit 110 and / or the communication device 150. According to an embodiment, the processor 130 may obtain road information of the vehicle's driving position through the sensor unit 110, obtain map information from an external device (e.g., another vehicle or a server) through the communication device 150, and obtain road information of the vehicle's driving position from the map information.

[0058] According to one embodiment, the processor 130 may obtain information about objects around the vehicle (e.g., other vehicles, pedestrians, objects, curbs, guardrails, lanes, obstacles) through the sensor unit 110. For example, the processor 130 may obtain the distance and relative speed of at least one vehicle located in front of, to the side of, and / or behind the vehicle.

[0059] According to an embodiment, the processor 130 may determine whether the functions required for autonomous driving are operating normally based on the vehicle state information. The functions required for autonomous driving may include, for example, lane detection, lane change, lateral control, deceleration (or braking control), powertrain control, safety area detection, and at least one of obstacle detection and distance sensing. When at least one function required for autonomous driving cannot operate normally, the processor 130 may determine that normal autonomous driving is not feasible.

[0060] According to an embodiment, the processor 130 may determine whether the vehicle state is suitable for normal operating conditions based on the vehicle state information. For example, the processor 130 may determine whether the mechanical state information of the vehicle (such as tire pressure information or engine overheating information) meets the requirements of normal operating conditions. When it is detected that the vehicle state does not meet the requirements of normal operating conditions, the processor 130 may determine that normal autonomous driving is not feasible. For example, when the tire pressure is not suitable for driving or when the engine is overheated, the processor 130 may determine that the vehicle cannot operate normally.

[0061] According to an embodiment, the processor 130 may also determine whether the surrounding environment meets the operational design domain (ODD) requirements of autonomous driving based on at least one surrounding environment information. The operational design domain represents the conditions under which autonomous driving operates effectively. When it is detected that the surrounding environment information does not meet the requirements of the ODD, the processor 130 may determine that normal autonomous driving is not feasible.

[0062] Once it is determined that normal autonomous driving is not possible, the processor 130 may determine a longitudinal fault level corresponding to the detected fault.

[0063] According to an embodiment, if a fault such as sensor occlusion occurs, the processor 130 may determine whether the fault is a longitudinal control fault, and specifically, which level of longitudinal control fault it is, based on the fault response control strategy. If the processor 130 determines that the fault is a longitudinal control fault, the automatic driving state of the vehicle may be immediately switched from the DDT state 210 to the transition demand (TD) state 220, such as Figure 2A As shown. The transition demand state 220 may refer to a state in which the vehicle provides a notification (e.g., a warning, a request, etc.) to the driver (e.g., within a predetermined time period) for a predetermined time period to take over the control of the vehicle. According to another embodiment, when the processor 130 finally determines that the fault is a longitudinal fault of level 1 or level 2, it may also transition the autonomous driving state of the vehicle to the transition demand state 220.

[0064] According to the Society of Automotive Engineers (SAE), the automation levels of autonomous vehicles can be classified as follows. At level 0, the SAE classification standard may correspond to "no automation", where the autonomous driving system temporarily involves emergency situations (e.g., automatic emergency braking) and / or only provides warnings (e.g., blind spot warnings, lane departure warnings, etc.), and the driver is required to operate the vehicle. At level 1, the SAE classification standard may correspond to "driver assistance", where the system performs a portion of the driving functions (e.g., steering, acceleration, braking, lane centering, adaptive cruise control, etc.) while the driver operates the vehicle on normal operating sections, and the driver is expected to be responsible for determining the operating state and / or timing of the system, performing other driving functions, and responding to (e.g., resolving) emergency situations. At level 2, the SAE classification standard may correspond to "partial automation", where the system performs steering, acceleration, and / or braking under the supervision of the driver, and the driver is expected to be responsible for determining the operating state and / or timing of the system, performing other driving functions, and responding to (e.g., resolving) emergency situations. At level 3 of automated driving, the SAE classification standard may correspond to "conditional automation", in which the system drives the vehicle (e.g., performs driving functions such as steering, acceleration, and / or braking) under limited conditions, but transfers driving control to the driver when the required conditions are not met, and the driver is expected to be responsible for determining the operating state and / or timing of the system and taking over control in emergency situations, but not otherwise operating the vehicle (e.g., steering, acceleration, and / or braking). At level 4 of automated driving, the SAE classification standard may correspond to "high automation", in which the system performs all driving functions, and the driver is responsible for controlling the vehicle only in emergency situations. At level 5 of automated driving, the SAE classification standard may correspond to "full automation", in which the system performs all driving functions without any assistance from the driver, including in emergency situations, and the driver is not responsible for performing any driving functions other than determining the operating state of the system.

[0065] According to an embodiment, for a vehicle operating at automated driving level 3 (eg, conditional automation), the vehicle may enter a transition demand state 220 when a level 1 or level 2 longitudinal fault occurs due to a predetermined expected event or an unexpected event.

[0066] According to another embodiment, for a vehicle operating at automated driving level 4 (eg, highly automated), the processor 130 may monitor the user and only request or enter the transition required state 220 when it is determined based on the monitoring information that a handover to the user is feasible.

[0067] For example, when it is determined based on the weight and / or angle sensor of the seat that the user is sitting in the driver's seat, or when it is determined that the seat condition (eg, angle) is suitable for driving, the processor 130 may deem the user to be in a state where he or she can take over the vehicle.

[0068] According to another embodiment, when it is determined that the user sitting in the driver's seat is paying attention to the front through eye gaze recognition and tracking using a camera, the processor 130 may consider that the user is in a state capable of taking over the vehicle.

[0069] According to another embodiment, the processor 130 may determine that the user is in a transferable state based on vehicle status information indicating the user's driving ability (e.g., not in a serious vehicle failure state), and when camera image analysis detects that the user is not holding any items (e.g., writing utensils, work materials, books, food, etc.), or a perceptible auditory warning is available to the user (e.g., not wearing headphones, watching media at a volume below a certain threshold, etc.).

[0070] exist Figure 2A In the example of , when a vehicle autonomously driving in the DDT state detects a fault at time point 215 and determines that the fault corresponds to longitudinal fault level 1 or level 2, the autonomous driving state of the vehicle can be immediately transitioned from the DDT state 210 to the TD state 220.

[0071] In the TD state 220 , when there is no user intervention to take over control within a predetermined time period 225 , the autonomous driving vehicle or processor 130 may transition from the TD state 220 to the MRM state 230 to initiate a minimum risk maneuver (MRM).

[0072] According to an embodiment, when the vehicle 100 is traveling on a highway, a highway driving pilot (HDP) function may be activated so that the vehicle 100 can be controlled in the DDT state 210, and when the user does not deactivate the activated HDP function within a predetermined time period 225 in the TD state 220, the state may be transitioned to the MRM state 230 to initiate a minimum risk maneuver (MRM).

[0073] At the same time, according to Figure 2B In an embodiment, when the processor 130 ultimately determines through a fault response control strategy that a fault occurring in the vehicle corresponds to one of longitudinal fault levels 3 to 5, the processor 130 may immediately switch to the MRM state 230 to initiate a minimum risk maneuver (MRM), regardless of whether the current autonomous driving state is in the DDT state 210 or the TD state 220.

[0074] Once a minimum risk maneuver (MRM) is initiated, the processor 130 may determine a minimum risk maneuver (MRM) strategy.

[0075] According to various embodiments, once the minimum risk operation is initiated, the processor 130 may select one of a plurality of MRM strategies. The MRM strategy may include, for example, Figure 3For example, the MRM strategy may include a lane parking strategy 301 including type 1 and type 2 and a shoulder parking strategy 303 including type 3 and type 4.

[0076] The lane parking strategy 301 may include type 1 straight-through parking 311 and type 2 in-lane parking 312. The shoulder parking strategy 303 may include type 3 half-shoulder parking 313 and type 4 full-shoulder parking 314.

[0077] The straight stop 311 of type 1 involves using only the deceleration control 323, which is a longitudinal deceleration function, and does not involve lateral control. For example, the straight stop 311 may be performed in a case where lane detection is not feasible or lateral control is not feasible due to an actuator failure. In the straight stop 311 of type 1, the acceleration control 322 and the lane change 324 are prohibited, and the function of detecting a potential parking position 325 outside the lane may be unnecessary. Here, detecting a potential parking position outside the lane may refer to a function of detecting a position of a safety area (such as a shoulder or a rest area) located outside the lane.

[0078] Type 2 in-lane parking 312 refers to parking within the boundaries of the lane in which the vehicle is traveling. For example, in-lane parking 312 may mean parking within the boundaries of the lane in which the vehicle is traveling using lateral control 321 and / or deceleration control 323. The lane in which the vehicle is traveling may refer to the lane in which it is traveling when it is determined that the lowest risk maneuver is required. During in-lane parking 312, acceleration control 322 and lane change 324 are prohibited, and the function of detecting a potential parking position outside the lane 325 may be unnecessary.

[0079] Type 3 half shoulder stop 313 means that a portion of the vehicle stops on the shoulder, and type 4 full shoulder stop 314 means that the entire vehicle stops on the shoulder. During half shoulder stop 313 and full shoulder stop 314, functions of lateral control 321, deceleration control 323, lane change 324, and detection of potential parking positions outside the lane 325 may be utilized, while acceleration control 322 may be used only to maintain the current speed.

[0080] According to an embodiment, the priorities of the above-mentioned MRM types may be determined based on the road, the surrounding environment, and the vehicle's fail-operation capability. For example, in order to minimize the risk during parking, the priority of the MRM type corresponding to the shoulder parking strategy 303 may be set higher than the priority corresponding to the lane parking strategy 301. In addition, the priority of full shoulder parking 313 may be set higher than the half shoulder parking 314, and the priority of in-lane parking 312 may be set higher than the straight parking 311. That is, the priority of the MRM type may be set to decrease in the order of full shoulder parking 314, half shoulder parking 313, in-lane parking 312, and straight parking 311.

[0081] According to various embodiments, the processor 130 may select an MRM strategy based on at least one of vehicle state information and surrounding environment information.

[0082] According to an embodiment, the processor 130 may determine feasible MRM types among the described MRM types based on vehicle state information (including normal functions and / or fault characteristics required for autonomous driving). For example, when the function of the lateral control 321 operates normally, it may be determined that all MRM types are feasible, including straight parking 311, lane parking 312, half shoulder parking 313, and full shoulder parking 314. In another example, when the function of the lateral control 321 does not operate normally, it may be determined that the straight parking 311 is feasible.

[0083] When only one feasible MRM type is identified based on the vehicle state information, the processor 130 may determine the corresponding MRM type as an MRM strategy. For example, the processor 130 may determine the straight parking 311 as an MRM strategy because only the straight parking 311 is feasible when the function of the lateral control 321 cannot operate normally. In another example, the processor 130 may determine the straight parking 311 as an MRM strategy because only the straight parking 311 is feasible when the driving lane is not detected due to sensor failure and / or external environment.

[0084] When multiple feasible MRM types are identified based on the vehicle state information, the processor 130 may determine the feasible MRM type within a specified minimum risk condition (MRC) range. According to an embodiment, the specified MRC range may be set and / or modified by an operator and / or a designer. According to an embodiment, the specified MRC range may be set differently according to vehicle performance, vehicle type, and / or external environmental factors (e.g., weather, time, etc.).

[0085] According to an embodiment, the processor 130 may determine the feasible MRM types within the MRC range based on whether there is a shoulder within the specified MRC range. When there is no shoulder within the specified MRC range, the processor 130 may determine the feasible MRM types within the MRC range as lane parking 312 and straight parking 311.

[0086] When there is a shoulder within the specified MRC range, the processor 130 may determine the feasible MRM type within the MRC range based on the size of the shoulder. When the size of the shoulder within the specified MRC range is greater than or equal to a predetermined size, the processor 130 may determine the feasible MRM type within the MRC range as full shoulder parking 314, half shoulder parking 313, lane parking 312, and straight parking 311. The predetermined size may be determined based on the size of the vehicle. When the size of the shoulder is less than the predetermined size, the processor 130 may determine the feasible MRM type within the MRC range as half shoulder parking 313, lane parking 312, and straight parking 311.

[0087] According to various embodiments, when there are a plurality of executable MRM types within a specified MRC range, the processor 130 may select a final MRM strategy by considering priorities and / or surrounding object information.

[0088] According to an embodiment, when there are multiple executable MRM types within the specified MRC range, the processor 130 may select the MRM type with the highest priority among the feasible MRM types within the specified MRC range as the final MRM policy.

[0089] The processor 130 may control the controller 120 of the vehicle 100 to perform a minimum risk maneuver according to the determined MRM strategy.

[0090] When the minimum risk maneuver begins, the processor 130 can immediately light up the emergency lights to alert the surrounding environment and keep the emergency lights on until the maneuver ends. The emergency lights can only be deactivated when the user intentionally operates (e.g., presses the emergency light button).

[0091] When the user does not disable the automatic driving function (eg, the HDP function), the processor 130 may control the vehicle to decelerate according to the determined MRM strategy to stop the vehicle.

[0092] During minimal risk operation, when the user deactivates the autonomous driving function, the processor 130 may immediately terminate the minimal risk maneuver, enabling a transition to the user driving mode.

[0093] In the event that a critical fault or warning occurs during an emergency maneuver (EM) operation and a minimum risk maneuver is required, the processor 130 may initiate the minimum risk maneuver after the risk of an imminent collision has been mitigated.

[0094] The autonomous driving function executed by the processor 130 may maintain lane and vehicle spacing in both the DDT state 210 and the TD state 220 , while in the MRM state 230 the processor 130 may control the vehicle speed to decelerate and eventually stop the vehicle, thereby ensuring minimum risk conditions.

[0095] Once the vehicle is completely stopped, the processor 130 responsible for the autonomous driving function can engage the electronic parking brake (EPB), shift the gear to P, verify that the vehicle remains stationary, deactivate the autonomous driving function (e.g., Highway Driving Pilot HDP), and notify the user that the autonomous driving function is deactivated.

[0096] In addition, the processor 130 may display information related to autonomous driving, including minimal risk maneuvers, to in-vehicle users and external stakeholders.

[0097] The processor 130 may display information for the in-vehicle user on the in-vehicle display 140. According to an embodiment, the in-vehicle display 140 may include a head-up display (HUD) disposed on the front windshield of the vehicle.

[0098] Figure 4 is a diagram showing an exemplary screen layout on a display when the Highway Driving Pilot (HDP) function is activated.

[0099] Processor 130 may provide various screen layouts customized for the activated autonomous driving function. Figure 4 An exemplary display layout is shown when the Highway Driving Pilot (HDP) function is activated, which is an autonomous function available when the vehicle is traveling on a highway. Figure 4 Unlike the screen layout in the embodiment, in other embodiments where there are multiple displays, each part that makes up the screen layout can be displayed on a different display.

[0100] refer to Figure 4 , the display may include a HUD screen 410. The HUD screen 410 displayed on the front windshield of the vehicle may display symbols indicating the operation of the highway driving pilot, auxiliary symbols for lane keeping, and other notification and warning messages.

[0101] The display screen may include a driving assistance screen 420. The driving assistance screen 420 may display the road surface in distinguishable colors and display the detected object at the corresponding position of the detected object. In addition, the driving assistance screen 420 may intuitively display the current driving state of the vehicle performed by the highway driving pilot function.

[0102] The display screen may include a full pop-up screen 430. The full pop-up window may display a notification, such as activation / deactivation of highway driving pilot, and request a user response to the TD / MRM / EM status.

[0103] The display screen may include a driving assistance summary screen 440. The driving assistance summary screen 440 may display a brief summary of the highway automated driving status, display a simplified view from the side of the vehicle, and also display the speed of the vehicle.

[0104] The display screen may include a mini pop-up screen 450. When the automatic driving is requested to be performed, for example, when the user presses a button to activate Highway Driving Pilot (HDP) in a situation where activation is impossible, the mini pop-up screen 450 may display the reason why the activation cannot be performed. When the automatic driving state of the vehicle is converted to the TD state or the MRM state, the mini pop-up screen 450 may also display the reason why the corresponding TD state or MRM state occurs.

[0105] The processor 130 may use at least one display equipped in the vehicle to provide information to the user. According to an embodiment, the at least one display may be configured to provide Figure 4 The screen displayed in the , and various other information.

[0106] The processor 130 may provide relevant information to the user by displaying various screens customized for different autonomous driving states on at least one display.

[0107] According to an embodiment, when the automatic driving state of the vehicle is converted to the TD state 220, the processor 130 may display a message directly requesting the user to directly control the vehicle or an icon depicting a steering wheel and a hand shape on the full pop-up screen 430 to request user intervention. In addition, the processor 130 may provide an alarm to the user through an auditory or tactile warning. According to an embodiment, when the user does not deactivate the automatic driving function (e.g., HDP function) within a predetermined time period in the TD state 220, the processor 130 may increase the warning level over time and generate a corresponding warning sound. The processor 130 may also use a light to notify the user of the alarm. According to an embodiment, when the automatic driving function (e.g., HDP function) is not deactivated within 4 seconds in the TD state 220, the processor 130 may increase the warning level.

[0108] When the vehicle is parked during the TD state 220 and the autonomous driving function (e.g., HDP function) is not immediately disabled after a certain period of time, the processor 130 may activate the emergency lights to notify external stakeholders. According to an embodiment, the emergency lights are not automatically disabled, but require intentional user intervention, such as pressing an emergency light button.

[0109] When the autonomous driving function (eg, HDP function) is not disabled during a predetermined period of time in the TD state 220 , the processor 130 may enter the MRM state 230 and perform a minimum risk maneuver so that the vehicle is in a parking state satisfying minimum risk conditions.

[0110] After the minimum risk maneuver is completed and the vehicle is in an emergency stop state, the full pop-up screen 430 may display a message indicating that the vehicle is in an emergency stop state and requesting manual driving. As another method, the processor 130 may display a steering wheel (whose color may be different from the steering wheel in the TD state) and a moving hand on the full pop-up screen 430 to indicate that the vehicle is in an emergency stop state and requesting manual driving.

[0111] With the transition to the MRM state 230 via the TD state 220, the processor 130 may display the reason for the transition to the MRM state 230 on the mini pop-up screen 450, and in addition, provide an auditory warning or a tactile warning similar to that in the TD state 220. In this case, the auditory warning may be provided with a warning sound different from the warning sound indicating the TD state 220.

[0112] According to an embodiment, in the MRM state 230, the processor 130 may activate the taillights to indicate to the external environment that the vehicle is currently in the MRM state 230. According to another embodiment, the processor 130 may indicate that the vehicle is in the MRM state 230 using lights other than the taillights or a separate display visible from the outside.

[0113] In addition, when the vehicle 100 has a vehicle-to-everything (V2X) function that allows communication with surrounding vehicles or infrastructure via the communication device 150, the processor 130 may send a message or notification containing location information to the surrounding vehicles and / or infrastructure via the communication device 150 when entering the MRM state 230, indicating the location where the MRM occurs.

[0114] The above notification process can also be similarly applied when transitioning directly from the DDT state 221 to the MRM state 230.

[0115] When the vehicle stops and remains stationary due to user intervention or completion of a minimum risk maneuver, identifying the end of the minimum risk maneuver, the processor 130 may automatically clear the notification displayed on the internal display and deactivate various audible or tactile warnings. On the other hand, unless the user intervenes, the processor 130 may maintain the emergency lights activated or the displayed content on the external display for external notification. For example, the emergency lights may remain activated unless the user presses the emergency lights button to turn them off. The indicator lights or notifications inside the vehicle indicating the execution of the minimum risk maneuver will turn on / off with the initiation and completion of the TD and MRM without user intervention, while the emergency lights or tail lights indicating the execution of the minimum risk maneuver, or the display on the external display visible from the outside of the vehicle, will automatically turn on with the initiation of the MRM but not with the completion of the MRM, requiring user intervention.

[0116] Figure 5is a flowchart illustrating a process of executing an MRM strategy in a vehicle according to various embodiments of the present invention. In the following embodiments, the operations may be performed sequentially, but they do not necessarily have to be performed sequentially. For example, the order of the operations may be changed, and at least two operations may be performed in parallel at the same time. In addition, the operations may be performed by the processor 130 and / or at least one other component (e.g., the sensor unit 110 and / or the controller 120) equipped in the vehicle 100, or implemented as instructions that can be executed by the processor 130 and / or at least one other component (e.g., the sensor unit 110 and / or the controller 120).

[0117] refer to Figure 5 , the vehicle 100 determines whether the dynamic driving task (DDT) function of the autonomous driving vehicle is being executed in step 502. When the autonomous driving is enabled and operating normally, the vehicle 100 may execute the dynamic driving task (DDT) function.

[0118] When executing the DDT function, in step 504 , the vehicle 100 may obtain vehicle status information or environmental information around the vehicle since the DDT function is started together with the activation of the automatic driving.

[0119] The vehicle status information indicates whether there is a mechanical or electrical failure in the internal components of the vehicle (e.g., sensors, actuators, etc.). The environmental information may include surrounding object information and lane information. The surrounding object information may include the distance and relative speed of at least one vehicle located in front of, to the side of, and / or behind the vehicle.

[0120] In step 506, the vehicle 100 determines whether normal autonomous driving is feasible based on the vehicle state information or the environment information. According to an embodiment, the processor 100 may determine whether the vehicle state meets normal operating conditions based on the vehicle state information. For example, when the tire pressure is not suitable for driving or when the engine is overheated, the vehicle 100 may determine that the vehicle cannot operate normally. According to an embodiment, the vehicle 100 may also determine whether the surrounding environment meets the requirements of the operational design domain (ODD) of autonomous driving based on at least one piece of surrounding environment information. When it is detected that the surrounding environment information does not meet the requirements of the ODD, the vehicle 100 may determine that normal autonomous driving is not feasible.

[0121] Once it is determined that normal autonomous driving is not possible, the vehicle 100 may determine a longitudinal fault level corresponding to the detected fault in step 508. The longitudinal fault level may be considered an indication of the severity of the fault that affects the longitudinal autonomous driving of the vehicle.

[0122] Longitudinal fault level 1 or level 2 may correspond to a situation where the vehicle cannot obtain information required for autonomous driving. Longitudinal fault level 1 or level 2 may correspond to situations such as sensor occlusion or sensor / camera failure, for example.

[0123] Longitudinal fault level 3 or higher may correspond to a physical fault related to vehicle operation. Longitudinal fault level 3 or higher may correspond to a situation such as insufficient tire pressure for running or engine overheating.

[0124] After determining the longitudinal fault level, the vehicle 100 may determine whether the determined longitudinal fault level is level 3 or higher in step 510. When the fault is determined to be level 3 or higher, the vehicle 100 may initiate a minimum risk maneuver (MRM) in step 512.

[0125] Figure 6 is a flowchart illustrating a process of executing an MRM strategy in a vehicle according to various embodiments of the present invention.

[0126] When the fault corresponds to longitudinal fault level 2 or lower, the vehicle 100 then determines whether the vehicle is at autonomous driving level 4 or higher in step 514. When the vehicle is at autonomous driving level 4 or higher, the vehicle monitors the user in step 518. In step 518, the vehicle 100 determines whether the user is in a drivable state, that is, whether the vehicle can hand over control to the user.

[0127] When it is determined that the user is unable to take over control, the vehicle 100 initiates a minimum risk maneuver in step 532 .

[0128] When it is determined based on the monitoring information that the user can take over the vehicle control, in step 520 , the vehicle 100 may transition the vehicle state from the DDT state to the TD state, in which the vehicle 100 requests the user to take over the control.

[0129] For example, when it is determined based on the seat weight and / or angle sensor that the user is sitting in the driver's seat or the seat condition (e.g., angle) is suitable for driving, the vehicle 100 may consider that the user is in a state where he or she can take over the vehicle. According to another embodiment, when it is determined by using the gaze recognition and tracking of the camera that the user sitting in the driver's seat is paying attention to the front, the vehicle 100 may consider that the user is in a state where he or she can take over the vehicle.

[0130] According to another embodiment, the vehicle 100 may determine that the user is in a transferable state when it is determined through camera image analysis that the user is not holding any items (e.g., writing utensils, work materials, books, food, etc.), or a perceptible auditory warning is available to the user (e.g., not wearing headphones, watching media at a volume below a certain threshold, etc.).

[0131] Furthermore, when it is determined in step 514 that the vehicle is at autonomous driving level 3 or below, in step 520 , the vehicle may transition the autonomous driving state from the DDT state to the TD state, at which point the vehicle 100 requests the user to take over control.

[0132] After entering the TD state, the vehicle may provide or generate a first warning or notification to the user in step 522. The first warning or notification is to prompt or urge the user to take over control of the vehicle because the vehicle's autonomous driving state is in the TD state. In this case, the user can take over control of the vehicle by disabling an autonomous driving function (such as a Highway Driving Pilot (HDP) function). The first warning or notification may include an audible alarm, seat belt tactile feedback, a pop-up display, or a combination of these.

[0133] refer to Figure 4 , the vehicle 100 may prompt the user to take over manual control via a visual warning (e.g., by displaying a message requesting manual driving on the full pop-up screen 430 or displaying a steering wheel or hand-shaped icon on the full pop-up screen 430). In addition, the vehicle 100 may notify the user of the alarm through an auditory warning or a tactile feedback warning. The auditory warning may be implemented, for example, by the appearance of an alarm sound. The tactile warning may be implemented, for example, by tactile feedback in the seat belt.

[0134] After the first warning or notification occurs, the vehicle 100 may activate a timer in step 524 and determine whether the user takes over control of the vehicle in step 524. When the user takes over control of the vehicle, the vehicle 100 may hand over control of the vehicle to the user in step 527.

[0135] If the user does not take over the vehicle control, the vehicle 100 determines whether the timer has expired in step 528 and waits for the user to take over the control until the timer expires. In this case, the vehicle 100 can continue to drive automatically while maintaining a predetermined distance from the vehicle ahead until the user takes over the control of the vehicle.

[0136] When the timer expires, the vehicle 100 may generate a second warning or notification to the user in step 530. The second warning or notification may have a higher intensity than the first warning or notification.

[0137] For example, the second warning or notification may be performed in a manner different from the first warning or notification. In the case of an auditory alarm, the sound of the second warning may have a higher sound level than the first warning, or may have a sound or content different from the warning sound of the first warning. In the case of a tactile warning, the tactile feedback of the second warning on the seat belt may be different from the tactile feedback of the first warning. In the case of a visual warning, the display color of the first warning may be different from the color of the second warning. The display color of the second warning may be a stronger color (e.g., red) than the display color of the first warning. The aforementioned second warning may occur one or more times until the timer expires. For example, the second warning may be executed at regular intervals to increase the intensity of the warning.

[0138] According to an embodiment, when the autonomous driving function (e.g., HDP function) is not deactivated within 4 seconds in the TD state, that is, when the user does not take over the vehicle control, the vehicle may increase the warning level. As the warning level increases, the auditory alarm may have a louder sound level and the seat belt haptic feedback may have a higher intensity.

[0139] When the timer expires, the vehicle 100 may initiate a minimal risk maneuver in step 532 .

[0140] Figure 7 is a flowchart illustrating vehicle operation when the MRM function is activated according to various embodiments of the present invention.

[0141] refer to Figure 7 In step 602, the vehicle 100 determines whether the minimum risk maneuver is activated. When the minimum risk maneuver is activated, in step 604, the vehicle 100 may select an MRM strategy based on at least one of the vehicle state information and the surrounding environment information. Specifically, the vehicle 100 may select one of a plurality of available minimum risk maneuver strategies.

[0142] MRM strategies can include four types, such as Figure 3 For example, the MRM strategy may include a lane parking strategy 301 including type 1 and type 2 and a shoulder parking strategy 303 including type 3 and type 4. The lane parking strategy 301 may include type 1 straight-through parking 311 and type 2 in-lane parking 312. The shoulder parking strategy 303 may include type 3 half-shoulder parking 313 and type 4 full-shoulder parking 314.

[0143] Next, the vehicle 100 determines whether there are multiple types of minimum risk maneuvers in the selected MRM strategy in step 606. When there are multiple types of minimum risk maneuvers, the vehicle 100 may select a final MRM type by considering priority and / or surrounding object information in step 608.

[0144] When only one feasible MRM type is identified based on the vehicle state information, the processor 100 may determine the corresponding MRM type as an MRM strategy. For example, the vehicle 100 may determine the straight parking 311 as an MRM strategy because only the straight parking 311 is feasible when the function of the lateral control 321 does not operate normally.

[0145] In addition, the vehicle 100 may determine feasible MRM types among the above-mentioned MRM types based on the vehicle status information, including normal operation and / or fault characteristics required for autonomous driving.

[0146] Once the final MRM type is selected, the vehicle may perform a minimum risk maneuver according to the MRM strategy in step 610 .

[0147] Figure 8 is a flowchart illustrating vehicle operations for performing MRM according to various embodiments of the present invention.

[0148] refer to Figure 8 , the vehicle 100 may determine whether to perform a minimum risk maneuver in step 620. When performing a minimum risk maneuver, the vehicle 100 may turn on an interior indicator light or notification in step 622 to indicate that the MRM is in progress.

[0149] Next, in step 624, the vehicle 100 may turn on an external indicator light. The external indicator light may be, for example, an emergency light of the vehicle 100, but the embodiments of the present invention are not limited thereto.

[0150] Accordingly, other vehicles around the vehicle 100 may perceive that the vehicle 100 is in the MRM state.

[0151] Although not shown in the figure, when the MRM is activated, the vehicle 100 can perform braking to reduce the speed of the vehicle within the lane at a constant deceleration rate, thereby minimizing collisions with surrounding vehicles or obstacles (including rear vehicles or obstacles). Therefore, when the MRM is activated, the vehicle 100 can stop after a certain period of time.

[0152] After turning on the exterior indicator lights, the vehicle 100 determines whether the MRM is terminated in step 626. The MRM may be terminated when the vehicle 100 is parked. Alternatively, the MRM may be terminated when the vehicle user manually terminates the MRM or controls the vehicle (e.g., by deactivating the HDP). User control of the vehicle may include selecting a soft button or a physical button to deactivate the HDP, or physically operating the vehicle's braking system.

[0153] When the MRM is terminated, the vehicle 100 may turn off an internal notification or indicator light indicating that the MRM is in progress. In other words, in the case of user intervention, or when the MRM has been terminated, the vehicle 100 may automatically clear the notification displayed on the internal display, and may also disable various audible or tactile alarms. In this case, when the vehicle 100 is parked and the vehicle 100 remains parked, the vehicle 100 may recognize that the MRM is terminated. Parking of the vehicle 100 means, for example, that the vehicle 100 remains stationary for a predetermined period of time.

[0154] Subsequently, in step 630, the vehicle 100 may determine whether the exterior indicator lights are turned off by the user. Specifically, the vehicle 100 keeps the exterior indicator lights on unless the user selects a soft button or a physical button to turn off the exterior indicator lights. When the user selects the soft button or the physical button to turn off the exterior indicator lights, in step 632, the vehicle 100 turns off the exterior indicator lights. In this case, unless the user intervenes, the vehicle 100 may keep the emergency lights activated or display content for external notification on the exterior display. For example, the emergency lights may remain activated unless the user presses the emergency light button to turn them off.

[0155] That is, the interior display / notification is turned on / off based on the activation and termination of the TD and / or MRM, but the exterior indicators remain on unless the user or driver manipulates the exterior indicator light's off function.

[0156] According to various embodiments of the present invention, a vehicle that performs minimal risk maneuvers during automated driving is able to minimize risk and improve safety by clearly informing external stakeholders and internal users of situations and changes in situations.

Claims

1. A vehicle, include: at least one sensor configured to detect the surrounding environment of the vehicle to generate surrounding environment information; a controller configured to control the operation of the vehicle under the control of the processor, the processor configured to: monitoring the status of the vehicle to generate vehicle status information; During the autonomous driving of the vehicle, determining whether a minimum risk maneuver is required based on at least one of the surrounding environment information or the vehicle state information, wherein the minimum risk maneuver includes controlling the vehicle to reduce a risk of collision; Based on the need for the minimal risk maneuver, performing the minimal risk maneuver by causing the controller to control automated driving of the vehicle; providing an indication of initiation of the minimal risk maneuver to a user in the vehicle; Based on the execution of the minimal risk maneuver, turning on an external indicator light indicating the execution of the minimal risk maneuver; and Based on a user operation of an external indicator light button, the external indicator light is turned off.

2. The vehicle according to claim 1, in, The processor is further configured to: determining whether to perform the minimal risk maneuver based on the vehicle transitioning to a transition demand state, wherein the vehicle is configured to provide one or more notifications to the user to take over control of the vehicle in the transition demand state; determining a level of automated driving for the vehicle based on determining that the lowest risk maneuver is performed in the transition requirement state; monitoring the user based on the autonomous driving level of the vehicle being greater than or equal to a predetermined automation level; and Based on monitoring of the user indicating that the user is in a drivable state, the vehicle is transitioned to the transition-required state.

3. The vehicle according to claim 2, in, The processor is further configured to provide a first notification requesting the user to take over control of the vehicle after the vehicle transitions to the transition demand state.

4. The vehicle according to claim 3, in, The processor is further configured to provide a second notification requesting the user to take over control of the vehicle based on a predetermined time elapsed after providing the first notification, The strength of the second notification is higher than the strength of the first notification.

5. The vehicle according to claim 4, in, The first notification and the second notification include at least one of an audible alert, a visual alert, and tactile feedback.

6. The vehicle according to claim 2, in, The processor is further configured to determine to perform the minimum risk maneuver in the transition requirement state based on a failure to obtain information required for autonomous driving of the vehicle.

7. The vehicle according to claim 2, in, The processor is further configured to determine to perform the lowest risk maneuver based on detecting a physical fault associated with autonomous driving of the vehicle.

8. The vehicle according to claim 1, in, The processor is further configured to: determining whether to perform the minimal risk maneuver based on the vehicle transitioning to a transition demand state, wherein the vehicle is configured to provide one or more notifications to the user to take over control of the vehicle in the transition demand state; determining a level of automated driving for the vehicle based on determining that the lowest risk maneuver is performed in the transition requirement state; Based on the autonomous driving level of the vehicle being lower than or equal to a predetermined automation level, the vehicle is transitioned to the transition required state.

9. The vehicle according to claim 1, in, The processor is further configured to: determining whether the minimal risk operation is terminated; and Based on the lowest risk maneuver being terminated, the indication is cleared.

10. The vehicle according to claim 1, in, The processor is further configured to determine that the minimal risk maneuver has been terminated based on the vehicle being stopped and remaining stationary.

11. A method, the method comprising: The following steps are involved: determining, by a processor, during autonomous driving of a vehicle, based on at least one of surrounding environment information or vehicle state information, whether a minimum risk maneuver is required, wherein the minimum risk maneuver includes controlling the vehicle to reduce a risk of a collision; causing the vehicle to perform the minimal risk maneuver based on the need for the minimal risk maneuver; providing an indication of initiation of the minimal risk maneuver to a user in the vehicle; Based on the execution of the minimal risk maneuver, turning on an external indicator light indicating the execution of the minimal risk maneuver; and Based on a user operation of the external indicator light button, the external indicator light is turned off.

12. The method according to claim 11, further comprising: include: determining whether to perform the minimal risk maneuver based on the vehicle transitioning to a transition demand state, wherein the vehicle is configured to provide one or more notifications to the user to take over control of the vehicle in the transition demand state; determining a level of automated driving for the vehicle based on determining that the lowest risk maneuver is performed in the transition requirement state; monitoring the user based on the autonomous driving level of the vehicle being greater than or equal to a predetermined automation level; and Based on monitoring of the user indicating that the user is in a drivable state, the vehicle is transitioned to the transition-required state.

13. The method according to claim 12, further comprising: include: After the vehicle transitions to the transition demand state, a first notification is provided to request the user to take over control of the vehicle.

14. The method according to claim 13, further comprising: include: providing a second notification to request the user to take over control of the vehicle based on a predetermined time elapsed after providing the first notification, The strength of the second notification is higher than the strength of the first notification.

15. The method according to claim 14, in, The first notification and the second notification include at least one of an audible alert, a visual alert, and tactile feedback.

16. The method according to claim 12, further comprising: include: Based on a failure to obtain information required for autonomous driving of the vehicle, determining to perform the minimum risk maneuver in the transition requirement state.

17. The method according to claim 12, further comprising: include: Based on detecting a physical fault related to autonomous driving of the vehicle, determining to perform the lowest risk maneuver.

18. The method according to claim 11, further comprising: include: determining whether to perform the minimal risk maneuver based on the vehicle transitioning to a transition demand state, wherein the vehicle is configured to provide one or more notifications to the user to take over control of the vehicle in the transition demand state; determining a level of automated driving for the vehicle based on determining that the lowest risk maneuver is performed in the transition requirement state; Based on the autonomous driving level of the vehicle being lower than or equal to a predetermined automation level, the vehicle is transitioned to the transition required state.

19. The method according to claim 11, further comprising: include: Determining whether the minimum risk operation is terminated; as well as Based on the lowest risk maneuver being terminated, the indication is cleared.

20. The method according to claim 11, further comprising: include: Based on the vehicle having stopped and remained stationary, it is determined that the minimal risk maneuver has been terminated.

Citation Information

Cited By

  • Vehicle control method and device, computer equipment, readable storage medium and program product

    CN119611411A

  • Vehicle control methods, devices, computer equipment, readable storage media and program products

    CN119611411B