Vehicular control device and vehicular control method

The vehicle control device addresses passenger anxiety during U-turns by providing distinct route guidance, allowing passengers to anticipate the U-turn, thereby enhancing their comfort through clear notification and preparation.

WO2024236934A1PCT designated stage expired Publication Date: 2024-11-21DENSO CORP
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/013964
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-10-05
Filing Date
2024-04-04
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Passengers experience anxiety during U-turn control in autonomous vehicles due to the significant change in vehicle direction, as existing technologies do not provide adequate notification or reassurance during this maneuver.

Method used

A vehicle control device and method that includes a plan understanding unit to grasp the travel plan and a notification execution unit to provide distinct route guidance when U-turn control is scheduled, allowing passengers to anticipate and prepare for the U-turn, thereby reducing anxiety.

Benefits of technology

The solution effectively suppresses passenger anxiety by providing clear and emphasized route guidance during U-turn control, ensuring passengers are aware of the planned maneuver and can prepare, thus enhancing their comfort during the operation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024013964_21112024_PF_FP_ABST
    Figure JP2024013964_21112024_PF_FP_ABST
Patent Text Reader

Abstract

An autonomous driving ECU is used in a host vehicle provided with a travel control function for assisting or substituting a driver's driving operation, and functions as a vehicular control device. In the autonomous driving ECU, a travel plan for the host vehicle used by the travel control function is identified. If execution of U-turn control is scheduled in the travel plan, notification of route guidance is performed in a mode different from a case in which execution of U-turn control is not scheduled.
Need to check novelty before this filing date? Find Prior Art

Description

Vehicle control device and vehicle control method CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is based on Patent Application No. 2023-081857 filed in Japan on May 17, 2023, and Patent Application No. 2023-173909 filed in Japan on October 5, 2023, and the contents of the base applications are incorporated by reference in their entirety.

[0002] The disclosure in this specification relates to a vehicle control technology used in a vehicle equipped with a driving control function that assists or substitutes for a driver's driving operation.

[0003] Patent Literature 1 describes a method for generating a route plan for an autonomous vehicle. Specifically, Patent Literature 1 includes a U-turn scenario as one of the driving scenarios based on the planned route.

[0004] Special Publication No. 2020-523552

[0005] When an autonomous vehicle performs a U-turn based on a U-turn scenario such as that described in Patent Document 1, the vehicle changes its direction of travel more significantly than when it performs driving control other than a U-turn (for example, right / left turn control, etc.). As a result, passengers may be more likely to feel uneasy about the behavior of the vehicle when performing U-turn control.

[0006] An object of the present disclosure is to provide a vehicle control device and a vehicle control method that can reduce the anxiety of passengers when U-turn control is performed.

[0007] In order to achieve the above object, one disclosed aspect is a vehicle control device used in a vehicle equipped with a driving control function that assists or acts on behalf of the driver's driving operations, the vehicle control device comprising: a plan understanding unit that understands the driving plan of the vehicle used by the driving control function; and a notification implementation unit that provides route guidance notifications when U-turn control is scheduled to be implemented in the driving plan in a manner different from when U-turn control is not scheduled to be implemented.

[0008] Another disclosed aspect is a vehicle control method used in a vehicle equipped with a driving control function that assists or substitutes for the driver's driving operation, the vehicle control method including, in processing performed by at least one processing unit, a step of grasping the driving plan of the vehicle used by the driving control function, and providing route guidance notification in a manner different from when U-turn control is not scheduled to be performed in the driving plan.

[0009] In these aspects, the route guidance notification when a U-turn is scheduled in the driving plan used by the driving control function is different from the notification when a U-turn is not scheduled. Therefore, the passengers of the vehicle can be informed of the planned U-turn by the route guidance notification that is different from the usual one. As a result, it is possible to reduce the passengers' anxiety when a U-turn is scheduled.

[0010] It should be noted that the reference numerals in parentheses in the claims merely indicate examples of correspondence with specific configurations in the embodiments described below, and do not limit the technical scope in any way. Furthermore, claims not explicitly stated in the claims may be combined together unless there is a particular problem with the combination.

[0011] 1 is a diagram showing an overall picture of an in-vehicle network including an autonomous driving ECU and an HMI control device according to a first embodiment of the present disclosure. FIG. 2 is a block diagram showing details of the autonomous driving ECU. FIG. 3 is a diagram for explaining U-turn control performed by the autonomous driving ECU. FIG. 4 is a diagram for explaining offset control when making a U-turn at an intersection. FIG. 5 is a diagram for explaining offset control when making a U-turn on a connecting road. FIG. 6 is a diagram for explaining U-turn control when protruding into an outside lane. FIG. 7 is a diagram showing a host vehicle status when performing U-turn route guidance. FIG. 8 is a diagram showing a host vehicle status when performing right-turn route guidance. FIG. 9 is a diagram showing a host vehicle status when making a U-turn without temporarily stopping. FIG. 10 is a diagram showing a host vehicle status when a switchback occurs. FIG. 11 is a flowchart showing details of an inquiry process performed by the autonomous driving ECU and the HMI control device. FIG. 12 is a flowchart showing details of a driving plan generation process performed by the autonomous driving ECU. FIG. 13 is a flowchart showing details of a U-turn notification process performed by the autonomous driving ECU and the HMI control device. FIG. 14 is a flowchart showing details of a switchback execution process performed by the autonomous driving ECU. FIG. 15 is a flowchart showing details of a permission / prohibition determination process performed by the autonomous driving ECU according to a second embodiment of the present disclosure. FIG. 16 is a flowchart showing details of an inquiry process performed by the autonomous driving ECU and the HMI control device. 10 is a flowchart showing details of a travel plan generation process executed by an autonomous driving ECU according to a third embodiment of the present disclosure;

[0012] Hereinafter, several embodiments will be described with reference to the drawings. Note that corresponding components in each embodiment are given the same reference numerals, and redundant description may be omitted. When only a portion of the configuration is described in each embodiment, the configuration of another embodiment described previously can be applied to the remaining portion of the configuration. Furthermore, in addition to the combinations of configurations explicitly stated in the description of each embodiment, configurations of several embodiments can also be partially combined together even if not explicitly stated, as long as there is no particular problem with the combination.

[0013] (First embodiment) The functions of a vehicle control device according to a first embodiment of the present disclosure are realized by an automatic driving ECU (Electronic Control Unit) 50b shown in Figures 1 and 2. The automatic driving ECU 50b is mounted on a vehicle (hereinafter, referred to as host vehicle Am) together with a driving assistance ECU 50a. The automatic driving ECU 50b and the driving assistance ECU 50a constitute an automatic driving system 50 of the host vehicle Am. By mounting the automatic driving system 50, the host vehicle Am becomes an automatic driving vehicle equipped with an automatic driving function (driving control function) and is capable of driving using the automatic driving function (autonomous driving control).

[0014] The driving assistance ECU 50a is an in-vehicle ECU that implements driving assistance functions that assist the driver in driving operations in the automated driving system 50. The driving assistance ECU 50a enables advanced driving assistance or partial automated driving at approximately Level 2, according to the automated driving levels defined by the Society of Automotive Engineers. The automated driving performed by the driving assistance ECU 50a is automated driving with a periphery monitoring obligation, which requires the driver to visually monitor the area around the vehicle. For example, driving assistance functions such as ACC (Adaptive Cruise Control), LTC (Lane Trace Control), and LCA (Lane Change Assist) are implemented by the driving assistance ECU 50a.

[0015] The autonomous driving ECU 50b is an in-vehicle ECU that realizes an autonomous driving function that can take over driving operations from the driver. The autonomous driving ECU 50b is capable of autonomous driving at level 3 or higher, where the system is the main controller. Level 3 autonomous driving performed by the autonomous driving ECU 50b is eyes-off autonomous driving, in which the driver is not required to monitor the surroundings and does not need to monitor the area around the vehicle.

[0016] The autonomous driving ECU 50b may be capable of autonomous driving at level 4 or higher. Level 4 autonomous driving is fully autonomous driving in which all driving tasks are performed by the system, and is brain-off autonomous driving in which no request is made to the driver to take over driving. In addition, the autonomous driving ECU 50b performs hands-on autonomous driving or hands-off autonomous driving, which is equivalent to autonomous driving level 2, in a traffic environment on a general road other than a highway where pedestrians and other pedestrians are mixed with vehicles, while the driver is monitoring the surroundings.

[0017] In the autonomous driving system 50, the control state of the autonomous driving function is switched among a plurality of control states including at least driving assistance control by the driving assistance ECU 50a or the autonomous driving ECU 50b, which requires monitoring of the surrounding area, and autonomous driving control by the autonomous driving ECU 50b, which does not require monitoring of the surrounding area. In the following description, autonomous driving control of level 2 or lower by the driving assistance ECU 50a or the autonomous driving ECU 50b will be referred to as "driving assistance control," and autonomous driving control of level 3 or higher by the autonomous driving ECU 50b will be referred to as "autonomous driving control."

[0018] During the autonomous driving period in which the host vehicle Am is driven by the autonomous driving control of the autonomous driving ECU 50b, the driver may be permitted to perform a predetermined specific action other than driving (hereinafter referred to as a second task). The driver is legally permitted to perform the second task until a driving change request is made by the autonomous driving ECU 50b in cooperation with the HMI (Human Machine Interface) control device 100. For example, actions such as watching entertainment content such as videos, operating a device such as a smartphone, and eating are considered as second tasks.

[0019] The driving assistance ECU 50a and the autonomous driving ECU 50b are communicatively connected to a communication bus 99 of an in-vehicle network 1 mounted in the host vehicle Am. The communication bus 99 is connected to an in-vehicle monitor device 29, a periphery monitoring sensor 30, a locator 35, a navigation ECU 38, an in-vehicle communication device 39, a driving control ECU 40, an HMI control device 100, and the like. These nodes connected to the communication bus 99 can communicate with each other. Certain nodes among these ECUs, etc. may be electrically connected directly to each other and be able to communicate without going through the communication bus 99.

[0020] The in-vehicle monitor device 29 includes multiple in-vehicle cameras that capture images of the interior of the vehicle Am and a control unit that controls the multiple in-vehicle cameras. The in-vehicle cameras may be visible light cameras or near-infrared cameras combined with near-infrared light sources. At least one of the multiple in-vehicle cameras is installed so that it can capture images of the passenger (driver) sitting in the driver's seat and functions as a driver monitor. The in-vehicle monitor device 29 provides images captured by the in-vehicle cameras or analysis results of the captured images to the HMI control device 100 or the autonomous driving ECU 50b as in-vehicle monitor information. The in-vehicle monitor information includes driver status information that indicates the position and line of sight of the driver, etc.

[0021] The perimeter monitoring sensor 30 is an autonomous sensor that monitors the environment surrounding the host vehicle Am. The perimeter monitoring sensor 30 includes, for example, one or more of a camera unit, millimeter-wave radar, lidar, and sonar. The perimeter monitoring sensor 30 is capable of detecting moving and stationary objects within a detection range around the host vehicle. The perimeter monitoring sensor 30 provides the detection information of objects around the host vehicle to the driving assistance ECU 50a, the autonomous driving ECU 50b, and the like. In addition, the perimeter monitoring sensor 30 provides the HMI control device 100 with an image of the surroundings of the host vehicle captured by the camera unit (hereinafter, the perimeter monitoring image).

[0022] The locator 35 includes a GNSS (Global Navigation Satellite System) receiver, an inertial sensor, etc. The locator 35 sequentially determines the position and traveling direction of the host vehicle Am by combining positioning signals received from multiple positioning satellites by the GNSS receiver, measurement results from the inertial sensor, and vehicle speed information output to the communication bus 99. The locator 35 sequentially outputs position information and direction information of the host vehicle Am based on the positioning results to the communication bus 99 as locator information.

[0023] The locator 35 also has a map database that stores map data. The map database is primarily composed of a large-capacity storage medium that stores a large amount of three-dimensional map data and two-dimensional map data. The three-dimensional map data is a so-called high-definition (HD) map, and includes road information necessary for autonomous driving. The locator 35 reads map data for the area around the current location from the map database and provides it to the driving assistance ECU 50a, the autonomous driving ECU 50b, etc., along with locator information.

[0024] The navigation ECU 38 acquires information about a destination specified by a passenger such as a driver based on operation information acquired from the HMI control device 100. The navigation ECU 38 acquires vehicle position information and direction information from the locator 35 and sets a route from the current position to the destination. The navigation ECU 38 provides route information indicating the set route to the destination to the driving assistance ECU 50a, the autonomous driving ECU 50b, the HMI control device 100, etc. The navigation ECU 38 works in conjunction with the HMI system 10 (described later) to provide route guidance to the destination by combining screen displays and voice messages, etc., and notifying the driver of the direction of travel of the vehicle Am at intersections IA, branch points, etc. (see FIGS. 7 and 8, etc.).

[0025] Here, a user terminal such as a smartphone or a tablet may be connected to the in-vehicle network 1 or the HMI control device 100. Such a user terminal may provide vehicle position information, direction information, map data, etc. to the driving assistance ECU 50a, the autonomous driving ECU 50b, etc., instead of the locator 35. Furthermore, the user terminal may provide route information to a destination to the driving assistance ECU 50a, the autonomous driving ECU 50b, the HMI control device 100, etc., instead of the navigation ECU 38. Furthermore, the user terminal may play video content, etc., instead of the HMI system 10 described below, or together with the HMI system 10.

[0026] The in-vehicle communication device 39 is an external communication unit mounted on the host vehicle Am and functions as a V2X (Vehicle to Everything) communication device. The in-vehicle communication device 39 transmits and receives information via wireless communication with roadside devices installed on the side of the road. As an example, the in-vehicle communication device 39 receives congestion information, traffic regulation information, and the like from the roadside devices. The congestion information and traffic regulation information are, for example, VICS (registered trademark) information. The in-vehicle communication device 39 may further receive, from the roadside devices, traffic signal information indicating the lighting patterns of traffic signals, as well as detection information of stopped vehicles, parked vehicles, pedestrians, cyclists, and the like. The in-vehicle communication device 39 provides the received congestion information, traffic regulation information, traffic signal information, detection information, and the like to the navigation ECU 38, the autonomous driving ECU 50b, the HMI control device 100, and the like.

[0027] The cruise control ECU 40 is an electronic control device that mainly includes a microcontroller. The cruise control ECU 40 has at least the functions of a brake control ECU, a drive control ECU, and a steering control ECU. The cruise control ECU 40 continuously controls the braking force of each wheel, the output of the on-board power source, and the steering angle based on one of an operation command based on the driver's driving operation, a control command from the driving assistance ECU 50a, and a control command from the autonomous driving ECU 50b.

[0028] The HMI control device 100, together with a plurality of display devices, an audio device 24, an ambient light 25, an operation device 26, etc., constitutes an HMI system 10. The HMI system 10 has an input interface function that accepts operations by a passenger such as a driver of the vehicle Am, and an output interface function that presents information to the driver.

[0029] The display devices present information to the driver's vision by displaying images or the like. The display devices include a meter display 21, a center information display (hereinafter referred to as CID) 22, and a head-up display (hereinafter referred to as HUD) 23. The meter display 21 and the HUD 23 are display devices that present information mainly to the driver. The CID 22 is a display device that can present information not only to the driver but also to passengers (co-passengers) other than the driver. The CID 22 has a touch panel function and detects touch operations on the display screen by the driver or the like.

[0030] The audio device 24 has multiple speakers installed in the vehicle cabin. The audio device 24 reproduces, for example, notification sounds or voice messages through the speakers. The ambient lights 25 are provided on the instrument panel, steering wheel, etc. The ambient lights 25 present information to the driver's peripheral vision through ambient displays that change the color of their emitted light.

[0031] The operation device 26 is an input unit that accepts user operations by the driver or the like. For example, user operations related to activation and deactivation of the autonomous driving function, user operations related to setting a destination for route guidance, etc. are input to the operation device 26. Furthermore, user operations for making settings related to U-turn control, which will be described later, etc. are input to the operation device 26. The operation device 26 includes a steering switch provided on the spokes of the steering wheel, an operation lever provided on the steering column, and a voice input device that recognizes what the driver is saying.

[0032] The HMI control device 100 is a computer that mainly includes a control circuit equipped with a processing unit 11, a RAM 12, a storage unit 13, an input / output interface 14, and a bus connecting these units. The HMI control device 100 functions as a presentation control device. The HMI control device 100 presents information related to autonomous driving in cooperation with the autonomous driving system 50. The HMI control device 100 has an information linking unit 82 and a presentation control unit 88 as functional units related to presentation control, by executing a program (presentation control program) stored in the storage unit 13 using the processing unit 11 (see FIG. 2 ).

[0033] The information linking unit 82 links with the autonomous driving ECU 50b, the navigation ECU 38, etc., and enables information sharing between the autonomous driving system 50, the navigation ECU 38, and the HMI control device 100. The information linking unit 82 provides operation information of user operations input to the operation device 26 to the autonomous driving ECU 50b, the navigation ECU 38, etc. The information linking unit 82 acquires control status information indicating the control state of the autonomous driving function, and a request for implementing notifications related to the autonomous driving function, etc., from the autonomous driving ECU 50b. The information linking unit 82 acquires route information indicating a set route to the destination from the navigation ECU 38.

[0034] The presentation control unit 88 comprehensively controls the presentation of information using multiple display devices, the audio device 24, the ambient light 25, etc. For example, when the autonomous driving ECU 50b plans to end autonomous driving control, the presentation control unit 88 issues a notification requesting the driver to take over driving, based on an implementation request acquired by the information linkage unit 82. The presentation control unit 88 also issues notifications related to route guidance, based on route information generated by the navigation ECU 38 (see FIGS. 7 and 8, etc.).

[0035] Next, the automatic driving ECU 50b will be described in further detail.

[0036] The autonomous driving ECU 50b has higher computing power than the driving assistance ECU 50a and can perform at least driving control equivalent to ACC, LTC, and LCA. In addition to the above-mentioned scenarios in which the vehicle is traveling on public roads, the autonomous driving ECU 50b also performs driving assistance control in place of the driving assistance ECU 50a, in which the driver is responsible for monitoring the surroundings, for example, in scenarios in which the autonomous driving control is temporarily suspended.

[0037] The autonomous driving ECU 50b is a computer that mainly includes a control circuit equipped with a processing unit 51, RAM 52, storage unit 53, input / output interface 54, and a bus connecting these units. The processing unit 51 accesses the RAM 52 to execute various processes (instructions) for implementing the autonomous driving control method and vehicle control method according to the present disclosure. The storage unit 53 stores various programs (autonomous driving control program, vehicle control program, etc.) executed by the processing unit 51. As the processing unit 51 executes the programs, the autonomous driving ECU 50b is configured with an information linkage unit 61, an environment recognition unit 62, an action determination unit 63, a control execution unit 64, etc. as functional units for implementing the autonomous driving function (cruise control function) and vehicle control function (see FIG. 2 ).

[0038] The information linking unit 61 provides information to the HMI control device 100 and acquires information from the HMI control device 100 through information linking with the information linking unit 82 of the HMI control device 100. The information linking unit 61 has an HMI information acquisition unit 71 and a notification request unit 72 as sub-functional units for information linking with the HMI control device 100.

[0039] The HMI information acquisition unit 71 grasps the content of user operations input by the driver or the like to the CID 22 and the operation device 26, etc., based on operation information acquired from the HMI control device 100. The HMI information acquisition unit 71 grasps, for example, a level 2 transition operation that instructs a transition from manual driving to driving assistance control, and a level 3 transition operation that instructs a transition from driving assistance control to autonomous driving control, etc. In addition, the HMI information acquisition unit 71 grasps driver status information through the HMI control device 100, such as the driver's driving posture, line of sight, whether or not surrounding monitoring is being performed, whether or not a second task is being performed, the level of alertness, and whether or not there are any abnormalities in physical condition.

[0040] The notification request unit 72 enables the HMI control device 100 to issue a notification synchronized with the operating state of the autonomous driving function by outputting a notification implementation request to the HMI control device 100. For example, when the end of autonomous driving control is scheduled, the notification request unit 72 outputs a notification implementation request requesting a driver change to the HMI control device 100. The notification request unit 72 also outputs a notification implementation request related to U-turn control (see FIG. 3 , etc.), which will be described later, to the HMI control device 100.

[0041] The environment recognition unit 62 recognizes the driving environment of the host vehicle Am by combining the locator information and map data acquired from the locator 35 with the detection information acquired from the perimeter monitoring sensor 30 and the in-vehicle communication device 39. The environment recognition unit 62 acquires route information from the navigation ECU 38 and provides the acquired route information to the action determination unit 63.

[0042] The environment recognition unit 62 has a target recognition unit 74 and a road recognition unit 75 as sub-functional units for recognizing the driving environment. The target recognition unit 74 recognizes the relative positions and relative speeds of dynamic targets around the vehicle, such as other vehicles traveling around the vehicle Am. The road recognition unit 75 acquires road information related to the road on which the vehicle Am is traveling or the road on which the vehicle Am is scheduled to travel. The environment recognition unit 62 sequentially provides the information recognized by the target recognition unit 74 and the road recognition unit 75, i.e., the recognition results of the driving environment, to the action determination unit 63.

[0043] When the autonomous driving ECU 50b has control of the driving operation, the behavior determination unit 63 determines the behavior to be performed by the host vehicle Am based on the results of recognition of the driving environment by the environment recognition unit 62. The behavior determination unit 63 has a plan generation unit 77 and a control switching unit 78 as sub-function units that execute control related to the autonomous driving function.

[0044] The plan generation unit 77 creates a driving plan (path plan) for driving the host vehicle Am along the set route indicated by the route information, while referring to the driving environment recognition result by the environment recognition unit 62. Specifically, the plan generation unit 77 generates a planned driving line for turning right or left at intersection IA (see FIG. 3 ), a planned driving line for changing lanes at a merging point or branching point, and the like, and outputs the generated planned driving line to the control execution unit 64.

[0045] The control switching unit 78 cooperates with the driving assistance ECU 50a and the HMI control device 100 to control the switching of driving between the autonomous driving system 50 and the driver. Specifically, the control switching unit 78 switches the driving control state of the host vehicle Am between manual driving (control off), level 2 driving assistance control in which the driver is obligated to monitor the surroundings, and level 3 autonomous driving control in which the driver is not obligated to monitor the surroundings. Within the level 2 driving assistance control, the control switching unit 78 may further switch between driving assistance control in which the driver is obligated to hold the steering wheel (hereinafter referred to as hands-on level 2) and driving assistance control in which the driver is not obligated to hold the steering wheel (hereinafter referred to as hands-off level 2). The control switching unit 78 obtains control status information indicating the current driving control state of the autonomous driving system 50 and provides it to the information linking unit 61, etc. The control status information is provided to the HMI control device 100, etc. via the information linking unit 61.

[0046] When the autonomous driving ECU 50b has control of the driving operation, the control execution unit 64 cooperates with the cruise control ECU 40 to execute acceleration / deceleration control, steering control, and the like of the host vehicle Am in accordance with the planned driving line generated by the action determination unit 63. Specifically, the control execution unit 64 generates control commands based on the planned driving line and outputs the generated control commands to the cruise control ECU 40 one after another.

[0047] [U-Turn Control by Autonomous Driving ECU] The autonomous driving ECU 50b described above performs U-turn control at intersection IA (see FIG. 3, etc.), at a gap in the median strip MB (see FIG. 5), etc. Details of the U-turn control performed by the autonomous driving ECU 50b and specific examples of route guidance notifications associated with the U-turn control will be described below with reference to FIGS. 3 to 10 and 1 and 2.

[0048] <Details of U-Turn Control> During an autonomous driving period of level 2 or higher in which the autonomous driving ECU 50b has control of driving operations, the plan generation unit 77 determines whether a U-turn is effective in approaching the destination DST. A U-turn is a turning action in which the direction of travel of the host vehicle Am is changed by approximately 180 degrees, forming a U shape. As an example, in the scene shown in FIG. 3 , a route in which a U-turn is made (hereinafter, U-turn route RtU) can more easily bring the host vehicle Am closer to the destination DST than a normal route in which a U-turn is not made (hereinafter, detour route RtD).

[0049] The plan generation unit 77 determines to adopt the U-turn route RtU if making a U-turn can eliminate multiple right or left turns and shorten the travel distance. The plan generation unit 77 generates a planned travel line for making a U-turn based on the decision to adopt the U-turn route RtU. Specifically, the plan generation unit 77 defines a U-shaped planned travel line that runs from the host vehicle's lane (hereinafter referred to as the turn source lane LnS) to an oncoming lane (hereinafter referred to as the turn destination lane LnG) traveling in the opposite direction from the host vehicle's lane. The radius of the U-shaped turning section is set to be approximately the same as or slightly larger than the minimum turning radius based on the minimum turning radius of the host vehicle Am.

[0050] When the road on which the host vehicle Am is traveling has two or more lanes on each side, the plan generation unit 77 determines the innermost lane of the multiple lanes as the turn-source lane LnS. On the other hand, the plan generation unit 77 generally determines the outermost lane of the multiple lanes as the turn-destination lane LnG. However, when the minimum turning radius of the host vehicle Am is sufficiently small compared to the lane width, the plan generation unit 77 may also determine the innermost lane of the multiple lanes as the turn-destination lane LnG.

[0051] The plan generation unit 77 generates a planned driving line that offsets the driving position of the host vehicle Am to the outside within the turn source lane LnS to allow the host vehicle Am to make a smooth U-turn (see FIGS. 4 and 5 ). Through offset control based on the planned driving line, the host vehicle Am is moved toward the outside edge EO of the turn source lane LnS that is located farther from the turn destination lane LnG. The outside edge EO is a dividing line that divides the turn source lane LnS or the edge of the road on which the host vehicle Am is traveling.

[0052] The plan generation unit 77 identifies the type of location where a U-turn is planned (hereinafter, the planned U-turn location UL). Specifically, the plan generation unit 77 determines whether the planned U-turn location UL is an intersection IA. The plan generation unit 77 adjusts the shape of the planned driving line so that the content of U-turn control is changed depending on whether the planned U-turn location UL is an intersection IA. When the planned U-turn location UL is an intersection IA (see FIG. 4), the plan generation unit 77 generates a planned driving line that brings the host vehicle Am closer to the outer edge EO than when the planned U-turn location UL is not an intersection IA (see FIG. 5). In other words, when the lane width of the turn source lane LnS is the same, the amount of outward offset from the center of the turn source lane LnS is larger in a U-turn at the intersection IA than in a U-turn at a location other than the intersection IA. As a result, when a U-turn is made at the intersection IA, the host vehicle Am is closer to the outer edge EO than when a U-turn is made at a location other than the intersection IA.

[0053] Here, the planned U-turn location UL, which is not the intersection IA, is, for example, a connecting road CL (see FIG. 5 ) formed in a gap in the median strip MB. The median strip MB is a strip-shaped structure provided between two lanes (or a group of lanes) traveling in opposite directions. The connecting road CL is a travel area that connects the two lanes separated by the median strip MB.

[0054] The behavior determination unit 63 performs U-turn control of the host vehicle Am based on the planned driving line for the U-turn generated by the plan generation unit 77 so as not to interfere with traffic of other vehicles, pedestrians, etc. If the road on which the host vehicle Am is traveling includes multiple lanes, the behavior determination unit 63 positions the host vehicle Am in the innermost lane in advance based on the decision by the plan generation unit 77 to perform a U-turn. If there are other vehicles, pedestrians, etc. on the planned route of the host vehicle Am, the behavior determination unit 63 temporarily stops the host vehicle Am and causes the host vehicle Am to wait in the turn origin lane LnS while offsetting it to the outside. When there are no other vehicles, pedestrians, etc., left, the behavior determination unit 63 starts the host vehicle Am and resumes traveling along the planned driving line.

[0055] After starting steering control for a turn, the behavior determination unit 63 continuously determines whether a turn is necessary, in other words, whether the turn can be completed without going outside the turn-ahead lane LnG, based on the recognition result of the driving environment by the environment recognition unit 62. The behavior determination unit 63 decides to start the turn-ahead control at the point where it is determined that a turn is necessary, i.e., at the point where the host vehicle Am is stuck (see FIG. 14). During the turn-ahead control, the behavior determination unit 63 moves the host vehicle Am back by about several meters while steering in the opposite direction to that during the U-turn (see FIG. 10). On roads with narrow lane widths, the turn-ahead control may be performed multiple times.

[0056] The HMI information acquisition unit 71 acquires permission to perform U-turn control from a passenger (e.g., the driver) of the vehicle Am. The driver can set in advance whether to permit the execution of U-turn control using a setting screen displayed on the CID 22 or the like. The driver can also permit the execution of U-turn control by responding to an inquiry when the execution of U-turn control is scheduled. The setting regarding the permission of U-turn control may be switched between two levels, "permitted" and "not permitted," or may be switched between three levels, "permitted," "not permitted," and "prohibited."

[0057] The behavior determination unit 63 performs U-turn control when the driver has given permission to perform U-turn control. Specifically, the behavior determination unit 63 performs U-turn control that requires a turnaround only when the driver has given permission to perform it. On the other hand, even when the driver has not given permission to perform it, the behavior determination unit 63 performs U-turn control that does not require a turnaround. Furthermore, when the driver has prohibited U-turn control, the behavior determination unit 63 does not perform U-turn control that does not require a turnaround, nor U-turn control that requires a turnaround.

[0058] As shown in FIG. 6 , when the host vehicle Am is a large vehicle LV or the like and needs to make a U-turn at the planned U-turn location UL, the behavior determination unit 63 determines whether to cause the host vehicle Am to extend into the outer lane LnO. The outer lane LnO is a lane located on the opposite side of the turn destination lane LnG across the turn origin lane LnS. The behavior determination unit 63 determines to execute U-turn control to cause the host vehicle Am to extend into the outer lane LnO, provided that there are no other vehicles (vehicles traveling parallel to the outer lane LnO) and no vehicles behind the turn origin lane LnS (see U-turn route RtU in FIG. 6 ). By allowing the host vehicle Am to extend into the outer lane LnO, the host vehicle Am can make a U-turn that is larger than usual (see the two-dot chain line in FIG. 6 ).

[0059] <Notification of route guidance accompanying U-turn control> When the U-turn control described above is performed by the autonomous driving ECU 50b, the occupants are likely to feel uneasy about the behavior of the host vehicle Am, which makes large changes in its direction of travel. To alleviate such anxiety, when the autonomous driving ECU 50b performs U-turn control, information related to the U-turn control is presented to the occupants. The information related to the U-turn control is notified to the occupants by a change in the state of the host vehicle status StA (see FIG. 7 ) displayed on the meter display 21 or the CID 22.

[0060] The host vehicle status StA notifies the passengers of the status of the host vehicle Am and the surroundings of the host vehicle. The host vehicle status StA is a bird's-eye view content looking down on the host vehicle Am from above and behind. The host vehicle status StA reproduces the traffic environment around the host vehicle on the display. The HMI control device 100 draws the host vehicle status StA using detection information from the surroundings monitoring sensor 30, etc. The HMI control device 100 may obtain the recognition results of the driving environment by the environment recognition unit 62, and draw the host vehicle status StA using the obtained recognition results.

[0061] The host vehicle status StA includes a road background RB, a host vehicle icon IcS, a vehicle icon IcB, and a planned trajectory icon IPP. The road background RB is an image that reproduces the shape of the road around the host vehicle on the display. The host vehicle icon IcS is an image portion that resembles the host vehicle. The host vehicle icon IcS is displayed approximately in the center of the host vehicle status StA.

[0062] The other vehicle icon IcB is an image portion that is displayed based on the detection information or the recognition result and indicates the actual presence of other vehicles traveling around the host vehicle. The other vehicle icon IcB is superimposed on the road background RB in a layout that reflects the relative position of the other vehicle. If there are no other vehicles around the host vehicle, the other vehicle icon IcB is not displayed.

[0063] The planned trajectory icon IPP is an image portion extending in a linear or band shape from the host vehicle icon IcS as a starting point. The planned trajectory icon IPP is drawn based on the information of the planned driving line generated by the plan generating unit 77, and reproduces the planned driving route of the host vehicle Am on the host vehicle status StA.

[0064] The host vehicle status StA has a function of guiding the passenger along the planned driving route of the host vehicle Am by displaying a planned trajectory icon IPP. For example, when a U-turn is to be made, the host vehicle status StA provides U-turn route guidance by displaying a U-shaped planned trajectory icon IPP (see FIG. 7). When a right turn is to be made, the host vehicle status StA provides right-turn route guidance by displaying a right-curved planned trajectory icon IPP (see FIG. 8).

[0065] The host vehicle status StA provides U-turn route guidance when a U-turn is scheduled in the driving plan in a manner different from that when a U-turn is not scheduled. Specifically, when a U-turn is scheduled, the virtual viewpoint position in the host vehicle status StA and the drawing manner of the planned trajectory icon IPP are changed.

[0066] The virtual viewpoint position (see FIG. 7) when a U-turn control is scheduled to be performed is set higher than the virtual viewpoint position (see FIG. 8) when a right turn or the like is made along the detour route RtD, and is set at a position farther away than the host vehicle icon IcS (host vehicle Am). As a result, the host vehicle status StA displays a wide range of conditions around the host vehicle.

[0067] In addition, the planned trajectory icon IPP (see FIG. 7 ) when a U-turn control is scheduled to be performed is emphasized more than the planned trajectory icon IPP (see FIG. 8 ) when a right turn or other normal operation is performed. Specifically, the planned trajectory icon IPP indicating a planned U-turn is drawn in a band shape and is displayed thicker than the planned trajectory icon IPP when a normal operation is performed, which is drawn in a line shape. The planned trajectory icon IPP indicating a planned U-turn may be made more visible than the normal operation by increasing the display brightness or changing the display color. As a result, the U-turn route guidance when a U-turn control is scheduled to be performed is emphasized more than the right turn route guidance when a U-turn control is not scheduled to be performed.

[0068] Furthermore, when U-turn control is performed, a monitoring recommendation icon IcM is additionally displayed on the meter display 21 or the CID 22. The monitoring recommendation icon IcM is an image portion that notifies the driver to monitor the surroundings. The monitoring recommendation icon IcM is displayed together with the host vehicle status StA even when the autonomous driving ECU 50b is performing autonomous driving control that does not require monitoring the surroundings.

[0069] Furthermore, the manner of U-turn route guidance based on the host vehicle status StA changes depending on whether the host vehicle Am is temporarily stopped during U-turn control (see FIG. 7 ) or whether the host vehicle Am is not temporarily stopped during U-turn control (see FIG. 9 ). As an example, when the host vehicle Am is not temporarily stopped during U-turn control, multiple highlighting portions HL are superimposed at intervals on the planned trajectory icon IPP. The highlighting portions HL repeatedly flow over the planned trajectory icon IPP in the traveling direction of the host vehicle Am. By changing the manner of the planned trajectory icon IPP in this way, the U-turn route guidance is emphasized more when the host vehicle Am is not temporarily stopped during U-turn control than when the host vehicle Am is temporarily stopped.

[0070] In addition, the manner of U-turn route guidance by the host vehicle status StA changes depending on whether the host vehicle Am is turned around by U-turn control (see FIG. 10) or not (see FIG. 7). For example, when the host vehicle Am is turned around by U-turn control, a wider range of conditions around the host vehicle are displayed in the host vehicle status StA than when the host vehicle Am is not turned around.

[0071] Specifically, when a turn is performed, the virtual viewpoint position of the host vehicle status StA is set directly above the host vehicle icon IcS (host vehicle Am). In addition, the virtual viewpoint position is set at a position further away from the host vehicle icon IcS. As a result, the host vehicle status StA becomes an around-view display. In the host vehicle status StA, a reverse path icon IPB indicating the movement path of the host vehicle Am as it reverses may be displayed in a manner different from the planned path icon IPP indicating the movement path of the U-turn. Furthermore, at least one peripheral camera image AV is additionally displayed on the meter display 21 or the CID 22. The peripheral camera image AV is a real-time image captured by a camera unit, and notifies the occupant of the situation in the direction of travel of the host vehicle Am.

[0072] [Details of each process related to U-turn control] Next, the details of each process performed by the autonomous driving ECU 50b and the HMI control device 100 to realize the U-turn control and U-turn route guidance described above will be described based on Figures 11 to 14 and with reference to Figures 1 to 10.

[0073] <U-Turn Execution Inquiry Process> The inquiry process shown in Fig. 11 is a process for inquiring of a passenger (such as a driver) about whether or not to permit the execution of U-turn control. The inquiry process is initiated when the vehicle approaches within a predetermined distance (for example, about 1 km) from the planned U-turn location UL. The inquiry process is performed in cooperation with the autonomous driving ECU 50b and the HMI control device 100.

[0074] In S11 of the inquiry process, the road recognition unit 75 acquires information about the planned U-turn location UL. The road recognition unit 75 mainly acquires information about the width of the planned U-turn location UL. In S12, the behavior determination unit 63 determines whether a change of direction is required to make a U-turn at the planned U-turn location UL based on the information about the planned U-turn location UL acquired in S11. As an example, if the distance between the centers of the turn source lane LnS and the turn destination lane LnG is shorter than the minimum turning radius of the host vehicle Am, the behavior determination unit 63 determines that the vehicle cannot complete the turn in one go and that a change of direction is required.

[0075] If it is determined that a turnaround is not required at the planned U-turn location UL (S12: NO), the inquiry process is terminated. On the other hand, if it is determined that a turnaround is required at the planned U-turn location UL (S12: YES), in S13, the notification request unit 72 cooperates with the HMI control device 100 to inquire of the occupant whether or not to permit the execution of U-turn control. As an example, a message such as "Do you permit a U-turn ahead?" may be displayed on the CID 22 or the HUD 23. At this time, icons for selecting "permit" or "do not perform" may be displayed on the CID 22 or the HUD 23.

[0076] In the inquiry at S13, the number of turns required for the U-turn control is presented to the passenger. The number of turns is information for determining whether or not to permit the U-turn control. For example, a message such as "Because the road is narrow, at least one turn is planned" or "Multiple turns are planned" is displayed on the CID 22 or the HUD 23.

[0077] In response to the inquiry made in S13, a passenger such as a driver inputs a user operation to instruct permission or cancellation of the U-turn control. In S14, the HMI information acquisition unit 71 cooperates with the HMI control device 100 to acquire operation information of the user operation input by the passenger. This determines whether or not to perform U-turn control that requires a turnaround.

[0078] The determination in S12 in the inquiry process may be omitted. That is, even if a turn is not required at the planned U-turn location UL, an inquiry as to whether or not to perform U-turn control may be made. In this case, information indicating whether or not a turn is planned to be performed is presented to the passenger instead of or in addition to the number of turns, as information for determining whether or not to permit the U-turn.

[0079] 12 is a process for generating a driving plan (planned driving line) for performing U-turn control. The driving plan generation process is started by the autonomous driving ECU 50b when the vehicle approaches within a predetermined distance (e.g., several hundred meters) from the planned U-turn location UL.

[0080] In S31 of the driving plan generation process, similar to S11 of the inquiry process (see FIG. 11 ), the road recognition unit 75 acquires information on the planned U-turn location UL. In S32, the behavior determination unit 63 determines whether the planned U-turn location UL is wide enough to make a U-turn without turning around, based on the information acquired in S31.

[0081] If it is determined that the planned U-turn location UL is narrow and that a change in direction is necessary (S32: NO), the behavior determination unit 63 acquires the recognition result of the driving environment by the environment recognition unit 62 in S33. Based on the acquired recognition result, the behavior determination unit 63 determines whether or not the host vehicle Am can extend into the outer lane LnO in S34. If it is determined that the host vehicle Am can extend into the outer lane LnO (S34: YES), the behavior determination unit 63 determines in S35 that the host vehicle Am will extend into the outer lane LnO. In this case, the plan generation unit 77 generates a planned driving line that will cause the host vehicle Am to extend from the turn source lane LnS into the outer lane LnO in S40 (see FIG. 6 ).

[0082] On the other hand, if it is determined that the planned U-turn location UL is wide and that a change of direction is not necessary (S32: YES), or if it is determined that it is impossible to extend into the outer lane LnO (S34: NO), the behavior determination unit 63 prohibits extension into the outer lane LnO in S36.

[0083] In S37, the plan generation unit 77 determines whether the planned U-turn location UL is the intersection IA. If the planned U-turn location UL is the intersection IA (S37: YES), in S38, the plan generation unit 77 sets the offset amount of the host vehicle Am in the turn source lane LnS to "large." Based on this setting, in S40, the plan generation unit 77 generates a planned driving line that brings the host vehicle Am closer to the outer edge EO (see FIG. 4).

[0084] On the other hand, if the planned U-turn location UL is a connecting road CL or the like other than the intersection IA (S37: NO), the plan generation unit 77 sets the offset amount of the host vehicle Am in the turn source lane LnS to "small" in S39. Based on this setting, the plan generation unit 77 generates a planned driving line in S40 that moves the host vehicle Am slightly closer to the outer edge EO (see FIG. 5). As described above, the content of the U-turn control is changed depending on whether the planned U-turn location UL is the intersection IA.

[0085] In S41, the behavior determination unit 63 refers to the planned driving line generated in S40 and again determines whether a turn is necessary. If a turn is not necessary (S41: NO), the driving plan generation process ends. In this case, it is determined to perform U-turn control to travel along the U-turn route RtU based on the planned driving line generated in S40.

[0086] On the other hand, if a turnaround is required (S41: YES), the behavior determination unit 63 determines in S42 whether permission to perform U-turn control has been obtained from the passenger. If permission to perform U-turn control is granted by a user operation in response to the inquiry (see S14 in FIG. 11) or by a pre-set setting (S42: YES), the driving plan generation process is terminated. In this case, too, it is determined that U-turn control will be performed along the U-turn route RtU based on the planned driving line generated in S40. As described above, permission from the passenger is required only for U-turn control that requires a turnaround.

[0087] On the other hand, if the execution of the U-turn control is not permitted (S42: NO), the behavior determination unit 63 determines to avoid the execution of the U-turn in S43. In this case, the plan generation unit 77 determines to adopt the detour route RtD (see FIG. 3). The plan generation unit 77 discards the planned driving line generated in S40 and generates a new planned driving line for making a right turn or a left turn.

[0088] <U-Turn Notification Process> The U-turn notification process shown in Fig. 13 is a process for switching the host vehicle status StA (see Fig. 7) to a mode for notifying the planned implementation of U-turn control (U-turn route guidance). The U-turn notification process is started when the adoption of the planned driving line for implementing a U-turn is confirmed in the driving plan generation process (see Fig. 12). The U-turn notification process is performed in cooperation with the autonomous driving ECU 50b and the HMI control device 100.

[0089] In S61 of the U-turn notification process, the plan generation unit 77 determines the driving plan (planned driving line) of the host vehicle Am used by the autonomous driving ECU 50b (driving control function). In S62, the notification request unit 72 cooperates with the HMI control device 100 to switch the mode of the host vehicle status StA. In S62, the virtual viewpoint position of the host vehicle status StA and the drawing mode of the planned trajectory icon IPP are changed (see FIG. 7 ). As a result, the route guidance notification (U-turn route guidance) when a U-turn control is scheduled to be performed is performed in a different and more emphasized mode than when a U-turn control is not scheduled to be performed.

[0090] In S63, a monitoring recommendation icon IcM (see FIG. 7) is additionally displayed on the screen of the display device that displays the host vehicle status StA, thereby encouraging the driver to monitor the surroundings (check the surroundings).

[0091] In S64, the behavior determination unit 63 determines whether or not to temporarily stop the host vehicle Am. If there are no other vehicles or pedestrians on the planned route and the U-turn can be started without temporarily stopping (S64: NO), the planned trajectory icon IPP is highlighted by additionally displaying the highlighting unit HL in S65 (see FIG. 9 ). On the other hand, if a temporary stop is made before starting the U-turn (S64: YES), S65 is skipped and the additional display of the highlighting unit HL is omitted. As described above, the manner of route guidance notification changes depending on whether a temporary stop is made due to U-turn control or not.

[0092] In S66, the behavior determination unit 63 determines whether or not the host vehicle Am will be turned around. If the host vehicle Am will be turned around (S66: YES), in S67, the virtual viewpoint position is moved, and the host vehicle status StA is switched to an around-view display (see FIG. 10 ). In addition, in S67, the surrounding camera image AV is additionally displayed. On the other hand, if the host vehicle Am will not be turned around (S66: NO), S67 is skipped, and neither the virtual viewpoint position is changed nor the surrounding camera image AV is additionally displayed. As a result, when the host vehicle Am is turned around by U-turn control, a wider range of conditions around the host vehicle are reported in the route guidance based on the host vehicle status StA than when the host vehicle Am is not turned around.

[0093] <Turning Execution Process> The turning execution process shown in Fig. 14 is executed by the autonomous driving ECU 50b based on the start of U-turn control. In S81 of the turning execution process, the behavior determination unit 63 acquires the recognition result of the driving environment by the environment recognition unit 62. Then, in S82, the behavior determination unit 63 determines whether the host vehicle Am is stalled after the start of U-turn control. If it is determined that there is no possibility of the host vehicle Am being able to complete the turn and that the host vehicle Am is stalled (S82: YES), the behavior determination unit 63 starts turning control in S83. On the other hand, if it is determined that there is a possibility of the host vehicle Am being able to complete the turn and that the host vehicle Am is not stalled (S82: NO), the turning control in S83 is not started.

[0094] In S84, the behavior determination unit 63 determines whether or not a U-turn can be completed. If it is determined that the host vehicle Am is in a state where it can complete the turn and is able to complete the U-turn (S84: YES), the turning execution process is terminated. On the other hand, if another turning is required (S84: NO), the process of S81 to S84 is repeated. As described above, turning may be performed multiple times.

[0095] (Summary of First Embodiment) In the first embodiment described above, the route guidance notification when the U-turn control is scheduled to be performed in the driving plan used by the driving control function is different from the notification when the U-turn control is not scheduled to be performed. Therefore, the passengers of the host vehicle Am can be informed of the planned U-turn control by the route guidance notification that is different from the usual route guidance. As a result, it is possible to reduce the passengers' anxiety when the U-turn control is performed.

[0096] Additionally, in the first embodiment, the route guidance notification when a U-turn control is scheduled is emphasized more than the route guidance notification when a U-turn control is not scheduled. That is, the U-turn control is performed when an emphasized route guidance notification is being performed based on the host vehicle status StA (see FIG. 7). As a result, the passenger can reliably recognize the emphasized route guidance notification and can be aware in advance that a U-turn control will be performed. As a result, the passenger's anxiety regarding the U-turn control can be further reduced.

[0097] In the first embodiment, the planned U-turn location UL where the U-turn control is scheduled to be performed is determined to be an intersection IA. The content of the U-turn control is changed depending on whether the planned U-turn location UL is an intersection IA. As described above, by changing the control for a U-turn at an intersection IA and a U-turn at a location other than the intersection IA, the behavior determination unit 63 can realize driving of the host vehicle Am that is appropriate for each scenario. As a result, it is possible to reduce the anxiety of the passengers when the U-turn control is performed.

[0098] Furthermore, in the first embodiment, when a U-turn control is performed from the source lane LnS to the destination lane LnG, the host vehicle Am is moved toward the outer edge EO of the source lane LnS that is located farther from the destination lane LnG. This offset control makes it easier to perform a smooth U-turn even on roads that are not wide.

[0099] Additionally, in the first embodiment, when the planned U-turn location UL is an intersection IA, the host vehicle Am is brought closer to the outer edge EO than when the planned U-turn location UL is not an intersection IA. As described above, when making a U-turn at an intersection IA where the environment around the host vehicle changes drastically, the behavior determination unit 63 can control the host vehicle Am so that the vehicle makes the turn in one go without requiring a change of direction. This reduction in the number of changes of direction can alleviate the anxiety of the passengers caused by the U-turn control.

[0100] In the first embodiment, the manner of route guidance notification is changed depending on whether or not the host vehicle Am is temporarily stopped due to U-turn control. As a result, appropriate route guidance notification can be implemented depending on whether or not the host vehicle Am is temporarily stopped due to U-turn control. As a result, it is possible to reduce the anxiety of passengers when U-turn control is performed.

[0101] Furthermore, in the first embodiment, the route guidance notification when no temporary stop is made is emphasized compared to when a temporary stop is made during U-turn control (see FIG. 9). In this way, the emphasized route guidance notifies the passengers in advance that a temporary stop will be omitted, thereby making it possible to reduce the passengers' anxiety even when a U-turn is made without a temporary stop.

[0102] In addition, in the first embodiment, the manner of the route guidance notification is changed depending on whether the vehicle Am is to turn around due to the U-turn control or not. As a result, the passenger can know in advance from the route guidance notification that the vehicle will turn around. As a result, it is possible to reduce the passenger's anxiety even when making a U-turn that requires turning around.

[0103] In the first embodiment, when a U-turn is performed, the route guidance notifies a wider range of the situation around the vehicle than when no turning is performed. As a result, the passenger can easily grasp the situation around the vehicle when a turning occurs. As a result, it is possible to reduce the passenger's anxiety during turning.

[0104] Furthermore, in the first embodiment, it is determined that the host vehicle Am is stuck after the start of the U-turn control. Then, a turn is initiated from the point where the stuck state is determined. In this way, by starting the turn control early from the point where the host vehicle Am is stuck, in other words, from the point where it becomes clear that the vehicle cannot complete the turn, a smooth U-turn can be performed even on a road that is not wide enough. As a result, it is possible to reduce the anxiety of the occupants when the U-turn control is performed.

[0105] Additionally, in the first embodiment, permission to perform U-turn control is obtained from the occupant of the host vehicle Am. Then, when permission to perform U-turn control is given by the occupant, U-turn control is performed. In this way, by requiring permission from the occupant for U-turn control, it is possible to avoid forcibly performing a U-turn in a situation where the occupant is likely to feel uneasy. As a result, it is possible to suppress the occupant's anxiety caused by a U-turn.

[0106] In the first embodiment, the number of turns required for the U-turn control is notified to the occupant as information for determining whether to permit the U-turn control. As a result, the occupant can appropriately determine whether to perform the planned U-turn. As a result, it is possible to avoid performing a U-turn in situations where the occupant is likely to feel uneasy.

[0107] Furthermore, in the first embodiment, a U-turn control that requires a turn is performed only when permission is given by the passenger. On the other hand, a U-turn control that does not require a turn is performed even when permission is not given by the passenger. As described above, if permission from the passenger is required only for a U-turn that requires a turn, it is possible to avoid performing a U-turn in a situation where a driver is likely to feel uneasy, while also achieving the effect of improving convenience by performing a U-turn.

[0108] Additionally, in the first embodiment, when a U-turn control is performed, a notification is issued to encourage the driver to monitor the surroundings. Specifically, a monitoring recommendation icon IcM is displayed to encourage the driver to check the surroundings of the vehicle. In this way, by encouraging the driver to check the surroundings when performing a U-turn and directing the driver's attention to driving, it is possible to further reduce the driver's anxiety caused by the U-turn control.

[0109] In the first embodiment, when a U-turn control is performed from the source lane LnS to the destination lane LnG, a determination is made as to whether or not to allow the host vehicle Am to extend into the outer lane LnO, which is located on the opposite side of the source lane LnS from the destination lane LnG. In this way, if extension into the outer lane LnO is permitted, even if the intended U-turn location UL is not wide enough to make a U-turn, it is possible to suppress the occurrence of a reversal of direction and perform a smooth U-turn control.

[0110] In the first embodiment, the autonomous driving ECU 50b corresponds to the “vehicle control device,” the behavior determination unit 63 corresponds to the “control execution unit,” and the HMI information acquisition unit 71 corresponds to the “permission acquisition unit.” Furthermore, the notification request unit 72 corresponds to the “notification execution unit,” and the plan generation unit 77 corresponds to the “plan comprehension unit.”

[0111] Second Embodiment The second embodiment of the present disclosure is a modified example of the first embodiment. The autonomous driving ECU 50b of the second embodiment can further perform a permission / denial determination process and a U-turn proposal process as processes related to U-turn control. In addition, the autonomous driving ECU 50b performs a driving plan generation process that is different from that of the first embodiment. Details of the permission / denial determination process, the U-turn proposal process, and the driving plan generation process of the second embodiment will be described below based on FIGS. 15 to 17 and with reference to FIGS. 1 and 2.

[0112] <U-Turn Control Permission Determination Process> The permission determination process shown in FIG. 15 is a process for determining whether to permit the execution of U-turn control. In the permission determination process, the determination criteria for whether to permit the execution of U-turn control are changed depending on the autonomous driving level to be applied to the U-turn control. The higher the autonomous driving level, the more likely the behavior determination unit 63 is to permit the execution of U-turn control. In other words, the determination criteria applied to autonomous driving level 3 are more lenient than the determination criteria applied to autonomous driving level 2. The permission determination process is, for example, started when route information is provided from the navigation ECU 38 to the environment recognition unit 62.

[0113] In S211 of the permissibility determination process, the plan generation unit 77 identifies the set route indicated by the route information acquired by the environment recognition unit 62. In S212, the plan generation unit 77 determines whether or not the set route includes a planned U-turn location UL. If there is no planned U-turn location UL (S212: NO), the permissibility determination process ends.

[0114] On the other hand, if a planned U-turn location UL is present (S212: YES), the plan generation unit 77 determines in S213 the autonomous driving level to be applied to the U-turn control to be performed at the planned U-turn location UL. In S213, it is determined whether the planned U-turn location UL is within a permitted area in which autonomous driving level 3 (autonomous driving control) is permitted to be performed. If the planned U-turn location UL is outside the permitted area and U-turn control at autonomous driving level 2 is to be performed (S213: NO), the criteria for permitting U-turn control are stricter than when U-turn control at autonomous driving level 3 is to be performed.

[0115] In S214, the plan generation unit 77 determines the type of the planned U-turn location UL. Specifically, the plan generation unit 77 determines whether the planned U-turn location UL is a large intersection IA (see FIG. 3, etc.; hereinafter, referred to as a specific intersection) equipped with traffic signals and including dedicated right- and left-turn lanes. If the planned U-turn location UL is a specific intersection (YES in S214), the behavior determination unit 63 permits the execution of U-turn control at the planned U-turn location UL in S216. On the other hand, if the planned U-turn location UL is not a specific intersection but a small intersection IA or a connecting road CL (see FIG. 3), etc. (NO in S214), the behavior determination unit 63 prohibits the execution of U-turn control in S217. In this case, the behavior determination unit 63 requests the navigation ECU 38 to reconfigure a route that does not include a U-turn.

[0116] The behavior determination unit 63 changes the planned driving line of the host vehicle Am during U-turn control according to the autonomous driving level to be applied to the U-turn control. The higher the autonomous driving level, the more the behavior determination unit 63 sets a planned driving line that does not require a change of direction. Therefore, if the planned U-turn location UL is within the permitted area and U-turn control at autonomous driving level 3 is planned to be performed (S213: YES), the plan generation unit 77 determines in S215 whether a change of direction is required for U-turn control at the planned U-turn location UL. If a change of direction is required for U-turn control (S215: YES), the behavior determination unit 63 disallows U-turn control in S217. Even in this case, the navigation ECU 38 is requested to change to a route that does not include a U-turn. On the other hand, if a change of direction is required for U-turn control (S215: NO), the behavior determination unit 63 allows U-turn control at the planned U-turn location UL in S216.

[0117] If the set route identified in S211 includes multiple planned U-turn locations UL, the behavior determination unit 63 determines whether or not to permit the execution of a U-turn for all of the planned U-turn locations UL. If the behavior determination unit 63 determines that the execution of U-turn control is not permitted for at least one planned U-turn location UL, it requests the navigation ECU 38 to reset the route from the planned U-turn location UL onwards.

[0118] 15 is a process for inquiring of a driver or other passenger about whether to permit the execution of U-turn control within a predetermined area after a reroute has been performed. The inquiry process is started, for example, when the navigation ECU 38 provides the environment recognition unit 62 with a notification indicating the occurrence of a reroute or route information after the reroute.

[0119] Here, rerouting is a process in which the navigation ECU 38 changes the route set for the vehicle Am. For example, a reroute that changes the planned route occurs when the passenger changes their destination, or when an accident or traffic jam occurs on the planned route. Furthermore, if the vehicle Am is a BEV (Battery Electric Vehicle), a reroute may be performed due to a decrease in the remaining battery charge. As described above, a reroute may be performed as appropriate based on the judgment of the passenger, the navigation ECU 38, and the autonomous driving ECU 50b.

[0120] In S221 of the inquiry process, the plan generation unit 77 determines the set route after rerouting indicated by the route information acquired by the environment recognition unit 62. In S222, the plan generation unit 77 determines whether or not a planned U-turn location UL is within a predetermined area. The predetermined area is, for example, within a range of approximately 1 km to several km from the current location. The size of the predetermined area may be changed as appropriate depending on the driving environment around the vehicle. As an example, the predetermined area may be set larger in a driving environment where the driving speed of the vehicle Am is higher. If the planned U-turn location UL is not within the predetermined area (S222: NO), the inquiry process is terminated.

[0121] On the other hand, if a planned U-turn location UL is present within the predetermined area (S222: YES), the plan generation unit 77 determines in S223 whether the planned U-turn location UL within the predetermined area is a recommended U-turn location that satisfies the recommended conditions for U-turn control. The plan generation unit 77 determines that the recommended conditions for U-turn control are met if the reduction rate of the time required to reach the destination DST (see FIG. 3 ) is large. Specifically, if a U-turn would advance the arrival time at the destination DST by more than a predetermined time (e.g., several minutes), the plan generation unit 77 determines that the recommended conditions for U-turn control are met. In addition, if the planned U-turn location UL has a road environment that makes it easy to make a U-turn, the plan generation unit 77 determines that the recommended conditions for U-turn control are met. Specifically, if the planned U-turn location UL is the above-mentioned specific intersection, the plan generation unit 77 determines that the recommended conditions for U-turn control are met. Alternatively, if no turning is required when making a U-turn at the planned U-turn location UL, the plan generating unit 77 determines that the recommended conditions for U-turn control are met.

[0122] The criteria for determining the recommended U-turn location may be changed as appropriate. For example, the plan generating unit 77 may determine a recommended U-turn location that satisfies the recommended conditions for U-turn control when all of the above-mentioned multiple conditions, such as the time condition and road condition, are satisfied.

[0123] If it is determined that the planned U-turn location UL is a U-turn recommended location (S223: YES), a notification is issued in S224 to prompt the driver to select whether or not to permit a U-turn immediately after the reroute. In this case, the notification request unit 72 cooperates with the HMI control device 100 to inquire of the passenger whether or not to permit the execution of U-turn control. In this inquiry, the passenger is presented with the benefits of making a U-turn, and the passenger is actively encouraged to make a U-turn.

[0124] As an example, a message such as "Making a U-turn ahead will speed up your arrival time" or "There is an intersection ahead that is suitable for a U-turn" is displayed on the CID 22 or the HUD 23 along with a message such as "Do you want to allow a U-turn ahead?" In this case, icons for selecting "Allow" or "Do not allow" are also displayed on the CID 22 or the HUD 23.

[0125] On the other hand, if it is determined that the planned U-turn location UL does not satisfy the recommendation conditions and is not a recommended U-turn location (S223: NO), the behavior determination unit 63 does not permit the execution of U-turn control in S225. In this case, the behavior determination unit 63 requests the navigation ECU 38 to reset a route that does not include a U-turn.

[0126] Here, the inquiry as to whether to permit the execution of the U-turn control may be made when the planned U-turn location UL does not satisfy the recommended conditions (S223: NO). That is, the notification for having the driver decide whether to permit the U-turn immediately after the reroute may be made when there is a planned U-turn location UL immediately after the reroute that does not satisfy the recommended conditions. In this form, when the planned U-turn location UL satisfies the recommended conditions (S223: YES), the behavior determination unit 63 automatically permits the execution of the U-turn without relying on the selection of the passenger.

[0127] Furthermore, if the planned U-turn location UL does not satisfy the recommendation conditions (S223: NO), a normal inquiry may be made. In the normal inquiry, the passenger is not informed of the benefits to be gained by making a U-turn, and a message such as "Do you want to allow a U-turn ahead?" is displayed. If the passenger does not allow the U-turn control to be performed in response to such an inquiry, the behavior determination unit 63 determines not to perform the U-turn control.

[0128] <Driving Plan Generation Process> The driving plan generation process shown in Figure 16 is a process for generating a driving plan for performing U-turn control, similar to the first embodiment, and is started when the host vehicle approaches within a predetermined distance (e.g., several hundred meters) of the planned U-turn location UL. In the driving plan generation process, the planned driving line of the host vehicle Am during U-turn control is changed depending on whether or not there is a vehicle behind. In addition, in the driving plan generation process, the autonomous driving level during U-turn control is changed depending on the autonomous driving level permitted in the turn-ahead lane LnG (see Figure 3).

[0129] In S231 of the driving plan generation process, the road recognition unit 75 acquires information about the planned U-turn location UL. Furthermore, in S232, the road recognition unit 75 determines whether autonomous driving at level 3 autonomous driving is permitted in the turn-destination lane LnG based on the information about the planned U-turn location UL acquired in S231. If the use of level 3 autonomous driving is permitted in the turn-destination lane LnG (S232: YES), U-turn control is performed while maintaining the driving control state of level 3 autonomous driving.

[0130] On the other hand, if the use of level 3 autonomous driving is not permitted in the turn-destination lane LnG (S232: NO), the control switching unit 78 changes the autonomous driving level of the driving control currently being executed. In this case, while traveling in the turn-source lane LnS (see FIG. 3), the control switching unit 78 lowers the autonomous driving level to level 2 autonomous driving, which is permitted in the turn-destination lane LnG. In addition, the control switching unit 78 changes whether or not the driver is required to hold the steering wheel, depending on the control load of the U-turn control.

[0131] Specifically, in S233, the plan generation unit 77 determines whether or not a change of direction is required for U-turn control at the planned U-turn location UL. If a change of direction is required for U-turn control (YES in S233), the control switching unit 78 determines in S234 to shift control to hands-on level 2. On the other hand, if a change of direction is not required for U-turn control (NO in S233), the control switching unit 78 determines in S235 to shift control to hands-off level 2. Before U-turn control is started, the control switching unit 78 requests a driver change in cooperation with the notification request unit 72, and completes the control switch from autonomous driving level 3 to hands-on level 2 or hands-off level 2.

[0132] In S236, the environment recognition unit 62 acquires a recognition result of the driving environment around the host vehicle. In S236, the target recognition unit 74 recognizes a rear vehicle traveling behind the host vehicle Am. The target recognition unit 74 may be able to recognize not only a rear vehicle traveling in the same lane as the host vehicle Am, but also a rear vehicle traveling in an adjacent lane and a vehicle traveling parallel to the host vehicle Am.

[0133] In S237, the behavior determination unit 63 determines whether or not the host vehicle Am is allowed to stray into the outer lane LnO based on the recognition result acquired by the environment recognition unit 62 in S236. If it is determined that the host vehicle Am is allowed to stray into the outer lane LnO (S237: YES), the behavior determination unit 63 determines in S238 that the host vehicle Am will stray into the outer lane LnO. In this case, in S244, the plan generation unit 77 generates a planned driving line that will cause the host vehicle Am to stray from the turn source lane LnS into the outer lane LnO (see FIG. 6 ).

[0134] On the other hand, if there is a vehicle traveling parallel to the host vehicle Am in the outer lane LnO, or if there is a vehicle behind the host vehicle Am in at least one of the outer lane LnO and the host vehicle's own lane, the behavior determination unit 63 determines that the host vehicle Am cannot extend into the outer lane LnO (S237: NO). In this case, the behavior determination unit 63 prohibits the host vehicle Am from extending into the outer lane LnO in S239. In addition, the behavior determination unit 63 also prohibits the host vehicle Am from extending into the outer lane LnO when making a turn in S240. More specifically, when making a turn, the host vehicle Am temporarily backs up at a planned U-turn location UL, such as an intersection IA or a connecting road CL. If extending into the outer lane when making a turn is prohibited, the behavior determination unit 63 limits the movement range of the host vehicle Am when backing up so that the rear end of the host vehicle Am does not extend into the outer lane LnO or an area extending from the outer lane LnO.

[0135] In S241, the plan generation unit 77 determines whether the planned U-turn location UL is an intersection IA. If the planned U-turn location UL is the intersection IA (S241: YES), in S242 the plan generation unit 77 sets the offset amount of the host vehicle Am in the turn source lane LnS to "large." On the other hand, if the planned U-turn location UL is a connecting road CL or the like (S241: NO), in S243 the plan generation unit 77 sets the offset amount of the host vehicle Am in the turn source lane LnS to "small." The plan generation unit 77 reflects the settings in S242 or S243 and generates a planned driving line in S244 in which the host vehicle Am is offset to the outer edge EO within a range that does not extend into the outer lane LnO.

[0136] (Summary of the Second Embodiment) In the second embodiment described so far, the same U-turn notification process (see FIG. 13) as in the first embodiment is performed, so that the route guidance notification when a U-turn is scheduled is different from the notification when a U-turn is not scheduled. As a result, the same effect as in the first embodiment is achieved, and it is possible to alleviate the anxiety of passengers when a U-turn is scheduled.

[0137] In addition, in the second embodiment, when a reroute occurs that changes the route set for the vehicle Am, an inquiry is made to the occupants of the vehicle Am as to whether or not to permit the execution of a U-turn control after the reroute. In this way, by having the occupants decide whether or not to permit the U-turn control, it is possible to avoid a situation in which the occupants feel strong anxiety due to a U-turn in a situation in which anxiety is likely to be felt after the reroute.

[0138] In the second embodiment, if a recommended U-turn location that satisfies the recommended conditions for U-turn control is on the route after rerouting, the passenger is prompted to perform a U-turn at the recommended U-turn location. This makes it easier to perform a U-turn at the planned U-turn location UL, where U-turn control is easy and anxiety caused by a U-turn is less likely to occur, based on the passenger's decision. As a result, passenger convenience can be further improved.

[0139] Furthermore, in the second embodiment, when a U-turn control is performed from the source lane LnS to the destination lane LnG, the autonomous driving level during the U-turn control is set to the autonomous driving level permitted for the destination lane LnG. This causes the autonomous driving level to be changed before the U-turn control is initiated. This prevents a situation in which the autonomous driving level is changed during a U-turn or after entering the destination lane LnG, which can cause high loads and can easily cause anxiety among passengers.

[0140] Additionally, in the second embodiment, the autonomous driving level of the cruise control function is lowered to the autonomous driving level permitted in the destination lane LnG while the vehicle is traveling in the source lane LnS. This allows the handover of driving from the autonomous driving system 50 to the driver to be completed in the source lane LnS. As a result, a situation in which the behavior of the host vehicle Am becomes unstable due to the autonomous driving level being lowered during a U-turn or after entering the destination lane LnG is avoided.

[0141] In the second embodiment, whether or not the driver is required to hold the steering wheel is changed depending on the control load of the U-turn control. In this way, by appropriately issuing the holding obligation and having the driver hold the steering wheel, it is possible to reduce the anxiety of the passengers during a U-turn. In addition, if the holding obligation is issued when the U-turn becomes a high load due to the occurrence of a turnaround, the anxiety of the passengers can be further reduced. Note that in the second embodiment, the steering wheel corresponds to the "steering operation unit."

[0142] Furthermore, in the second embodiment, the vehicle traveling behind the host vehicle Am is identified. The planned driving line of the host vehicle Am during U-turn control is changed depending on whether or not there is a vehicle behind. This prevents the host vehicle Am performing U-turn control from coming too close to the vehicle behind. As a result, it is possible to reduce the anxiety of the passengers when U-turn control is performed even in a situation where there is a vehicle behind.

[0143] In addition, in the second embodiment, the criteria for determining whether to permit the execution of the U-turn control are changed depending on the autonomous driving level to be applied to the U-turn control. In this way, if the criteria for the execution of the U-turn control are adjusted depending on the autonomous driving level, it becomes easier to more appropriately suppress the anxiety of passengers caused by the U-turn control.

[0144] In the second embodiment, the higher the autonomous driving level, the more likely it is that the U-turn control will be permitted. Therefore, the U-turn control is proactively performed in situations where passengers are unlikely to feel anxious. As a result, the convenience of the U-turn control for passengers can be further improved.

[0145] Furthermore, in the second embodiment, the planned driving line of the host vehicle Am during U-turn control is changed according to the autonomous driving level to be applied to the U-turn control. In this way, if the planned driving line during U-turn control is adjusted according to the autonomous driving level, the vehicle will be able to easily perform a U-turn in a manner that is less likely to cause anxiety to the passengers.

[0146] Additionally, in the second embodiment, the higher the autonomous driving level, the more a planned driving line that does not require a swerve is set. For example, in a driving control state of autonomous driving level 3, where the driver is not required to monitor the surroundings, the driver is not aware of the situation around the vehicle. Therefore, when a swerve occurs, the passengers are likely to feel uneasy. Therefore, when a high level of autonomous driving is performed, the passengers' anxiety can be effectively reduced by avoiding the swerve.

[0147] Third Embodiment A third embodiment of the present disclosure is another modified example of the first embodiment. In the autonomous driving ECU 50b of the third embodiment, U-turn control is not generally performed. The autonomous driving ECU 50b permits the performance of U-turn control only under predetermined conditions based on a restriction release process. Details of the restriction release process performed by the autonomous driving ECU 50b of the third embodiment will be described below based on FIG. 18 and with reference to FIGS. 1 and 2.

[0148] <Removal of Restrictions on U-Turn Control> The restriction removal process shown in Figure 18 is a process for temporarily removing the prohibited U-turn control. According to the restriction removal process, the execution of U-turn control is permitted only in an emergency. The restriction removal process is started by the autonomous driving ECU 50b when driving assistance control or autonomous driving control is activated in the autonomous driving system 50. The restriction removal process is repeatedly performed by the autonomous driving ECU 50b until both driving assistance control and autonomous driving control are turned off.

[0149] In S301 of the restriction release processing, the road recognition unit 75 acquires congestion information, traffic regulation information, and the like received by the in-vehicle communication device 39. In S301, the road recognition unit 75 determines whether a traffic obstruction, such as an accident or traffic congestion, has occurred on the planned route. If a traffic obstruction has occurred (S301: YES), the plan generation unit 77, in cooperation with the navigation ECU 38, determines in S302 whether a route (hereinafter, an alternative route) that bypasses the location of the traffic obstruction and reaches the destination DST (see FIG. 3 ) is available. If an alternative route cannot be set (S302: NO), the behavior determination unit 63 permits the implementation of U-turn control in S304. In this way, if the destination DST cannot be reached without performing U-turn control, the behavior determination unit 63 implements U-turn control.

[0150] If no traffic obstruction has occurred (S301: NO) or an alternative route can be set (S302: YES), the behavior determination unit 63 changes the setting of whether to permit U-turn control depending on the degree of urgency of the reservation time. In this case, the behavior determination unit 63 determines whether the reservation time is urgency based on the positional relationship between the destination DST set for the host vehicle Am and the current location, and the temporal relationship between the reserved arrival time at the destination DST and the current time. The reserved arrival time may be a time input by the passenger when setting the destination DST, or may be a time presented to the passenger by the autonomous driving system 50 when setting the destination DST. In addition, if the host vehicle Am is a service vehicle providing a mobility service, it may be a time presented to the passenger user when making a reservation for the ride.

[0151] If it is estimated that the host vehicle Am will be able to arrive at the destination DST by the reserved arrival time without performing U-turn control, the behavior determination unit 63 determines that the reserved time is not imminent (S303: NO). In this case, the behavior determination unit 63 prohibits the implementation of U-turn control in S305. On the other hand, if it is estimated that the host vehicle Am will not arrive at the destination DST by the reserved arrival time without performing U-turn control, the behavior determination unit 63 determines that the reserved time is imminent (S303: YES). In this case, the behavior determination unit 63 permits the implementation of U-turn control in S304.

[0152] The determination of whether the reservation time is approaching in S303 may be performed continuously or for a limited period of time. For example, the determination of whether the reservation time is approaching may be initiated when the destination DST is reached within a predetermined distance (e.g., several kilometers) or when the arrival reservation time is within a predetermined time (e.g., 10 to 20 minutes). Furthermore, the determination of whether the reservation time is approaching may be performed only once or multiple times when the navigation ECU 38 first searches and determines the route.

[0153] (Summary of Third Embodiment) The third embodiment described so far also has the same effects as the first embodiment, and can reduce the anxiety of passengers when U-turn control is performed.

[0154] Additionally, in the third embodiment, if the destination DST can be reached without U-turn control, U-turn control is avoided. On the other hand, if the destination DST cannot be reached without U-turn control, U-turn control is implemented. As described above, a U-turn is permitted when, due to an accident or the like, there is no route to the destination DST and the destination DST can only be reached by a U-turn. In this way, if the setting is such that U-turn control is not implemented as a rule, passenger anxiety caused by U-turn control can be reduced. Furthermore, by limiting the implementation of U-turn control to emergency situations, passengers can be convinced of U-turns and convenience for them can be improved.

[0155] In the third embodiment, the setting of whether to permit the execution of U-turn control is changed depending on at least one of the positional relationship between the destination DST set for the vehicle Am and the current location, and the time relationship between the reserved arrival time at the destination DST and the current time. As described above, when the reserved time is approaching and it is necessary to hurry up and arrive at the destination DST, a route including U-turn control can be temporarily selected. By limiting the execution of U-turn control to emergency situations, it is possible to improve the passenger's convenience while obtaining passenger's consent for the U-turn.

[0156] (Other Embodiments) Although multiple embodiments of the present disclosure have been described above, the present disclosure should not be construed as being limited to the above-described embodiments, and can be applied to various embodiments and combinations within the scope that does not deviate from the gist of the present disclosure.

[0157] Each process in the above embodiment is mainly performed by the autonomous driving ECU 50b. On the other hand, in Modification 1 of the above embodiment, the inquiry process and the U-turn notification process are mainly performed by the HMI control device 100. Specifically, in the U-turn notification process of Modification 1, the information linking unit 82 links with the autonomous driving ECU 50b to grasp the driving plan of the host vehicle Am used by the driving control function. Furthermore, the presentation control unit 88 switches the display mode of the host vehicle status StA and performs U-turn route guidance in a mode different from right turn route guidance, etc. In Modification 1, the HMI control device 100 corresponds to the "vehicle control device," the information linking unit 82 corresponds to the "plan grasping unit," and the presentation control unit 88 corresponds to the "notification implementation unit."

[0158] In a second modification of the above embodiment, the functions of the autonomous driving ECU 50b and the HMI control device 100 are implemented in a single integrated ECU. The integrated ECU has a driving control function related to autonomous driving and an integrated control function for presenting information to passengers. In this second modification, the integrated ECU corresponds to the "vehicle control device," and the presentation control unit 88, instead of the notification request unit 72, corresponds to the "notification implementation unit."

[0159] Furthermore, the autonomous driving ECU 50b and the HMI control device 100 may cooperate to perform the processes of the above-described embodiment. In such a modified example, a system including the autonomous driving ECU 50b and the HMI control device 100 corresponds to the "vehicle control device," and the presentation control unit 88 corresponds to the "alert execution unit."

[0160] The functions of the driving assistance ECU 50a may be implemented in the autonomous driving ECU 50b or the integrated ECU. That is, the driving assistance ECU 50a that realizes the driving control function for autonomous driving level 2 or lower may be omitted. Furthermore, the autonomous driving system 50 may be configured to be capable of only driving assistance control for autonomous driving level 2 or lower.

[0161] In a third modification of the above embodiment, the mode change of the host vehicle status StA associated with the execution of the U-turn control involves moving the virtual viewpoint position upward and farther away and highlighting the planned trajectory icon IPP, but only moving the virtual viewpoint position is implemented. Furthermore, in a fourth modification of the above embodiment, the mode change of the host vehicle status StA associated with the execution of the U-turn control involves only highlighting the planned trajectory icon IPP. As in the third and fourth modifications, the specific method of the mode change associated with the execution of the U-turn control may be changed as appropriate. Furthermore, a voice message or notification sound played by the audio device 24 may be used to notify the route guidance associated with the execution of the U-turn control.

[0162] In the fifth modification of the above embodiment, offset control is not performed in at least one of the U-turn control at intersection IA and the U-turn control at intersections other than IA. In the sixth modification of the above embodiment, the offset amount in the U-turn control at intersection IA is set smaller than the offset amount in the U-turn control at intersections other than IA.

[0163] In a seventh modification of the above embodiment, the emphasis on the notification during U-turn control without a temporary stop is omitted. Furthermore, in an eighth modification of the above embodiment, even when a U-turn is made at the very last moment without a change of direction, in other words, when the vehicle is approaching too close to the outer edge of the turn-ahead lane LnG, the around-view display is implemented. In this case, a peripheral camera image AV showing the outer edge of the turn-ahead lane LnG may be additionally displayed.

[0164] In a ninth modification of the above embodiment, the host vehicle Am starts to turn when the host vehicle Am approaches the outer edge of the turn-ahead lane LnG. As in the ninth modification, the timing of starting the turning may be changed as appropriate in consideration of the traffic environment, etc.

[0165] In the tenth modification of the above embodiment, options such as "actively perform," "perform," "seldom perform," and "never perform" are provided for the U-turn control. The passenger selects one of these options. As a result, the U-turn control can be performed only in situations where the passenger is unlikely to feel anxious.

[0166] In the eleventh modification of the above embodiment, a query for permission to execute U-turn control is made after a reroute when a passenger changes their destination. In contrast, if the navigation ECU 38 automatically changes the route due to a traffic obstruction, a query for permission to execute U-turn control is not made. As described above, a query for permission to execute U-turn control may be made only when a specific reroute occurs.

[0167] In a twelfth modification of the above embodiment, control is performed to raise the autonomous driving level during U-turn control to the autonomous driving level permitted for the turn-destination lane LnG before entering the turn-destination lane LnG. Specifically, the control switching unit 78 switches the control state from hands-off level 2 to autonomous driving level 3 before starting U-turn control or during U-turn control.

[0168] In a thirteenth modification of the above embodiment, if autonomous driving level 3 is not permitted in the turn-ahead lane LnG, the autonomous driving level during U-turn control is set to hands-off level 2 (or hands-on level 2), regardless of whether or not a change in direction is required during U-turn control. Also, in a fourteenth modification of the above embodiment, if a change in direction is required during U-turn control, control is shifted to hands-off level 2, and if a change in direction is not required during U-turn control, control is shifted to hands-on level 2.

[0169] In a fifteenth modification of the above embodiment, the criteria for determining whether to permit the execution of U-turn control are adjusted so that the higher the autonomous driving level to be applied to the U-turn control, the more difficult it is to permit the execution of U-turn control. Also, in a sixteenth modification of the above embodiment, the planned driving line of the host vehicle Am during U-turn control is set so that the lower the autonomous driving level to be applied to the U-turn control, the less turning is required.

[0170] The U-turn route guidance in the above embodiment may be information presented only when autonomous driving control of autonomous driving level 3 or higher is being implemented, or may be information presented only when driving assistance control of autonomous driving level 2 or lower is being implemented.

[0171] In the above embodiments, the functions provided by the autonomous driving ECU and HMI control device can be provided by software and hardware that executes the software, software alone, hardware alone, or a combination of these. Furthermore, when such functions are provided by electronic circuits as hardware, each function can also be provided by digital circuits including multiple logic circuits or analog circuits. Furthermore, the software for realizing such functions may include, at least in part, code automatically generated by, for example, a neural network or language model trained using real-world camera footage.

[0172] Each processing unit in the above embodiments is hardware for arithmetic processing coupled to a RAM. The processing unit includes at least one arithmetic core, such as a central processing unit (CPU) and a graphics processing unit (GPU). The processing unit may further include a field-programmable gate array (FPGA), a neural network processing unit (NPU), and an IP core with other dedicated functions. Such processing units may be individually mounted on a printed circuit board, or may be mounted on an application-specific integrated circuit (ASIC), an FPGA, or the like.

[0173] In the above embodiments, the form of the storage medium (non-transitory tangible storage medium) that stores various programs and the like may be changed as appropriate. Furthermore, the storage medium is not limited to a configuration provided on a circuit board, but may be provided in the form of a memory card or the like, inserted into a slot, and electrically connected to a control circuit such as an autonomous driving ECU. Furthermore, the storage medium may be an optical disk, hard disk drive, solid state drive, or the like that serves as a source from which programs are copied or distributed to the autonomous driving ECU or the like.

[0174] Vehicles equipped with the above-described autonomous driving system and HMI system are not limited to ordinary private passenger cars, but may also be rental cars, manned taxis, ride-sharing vehicles, freight vehicles, buses, etc. Furthermore, vehicles equipped with the autonomous driving system and HMI system may be right-hand drive vehicles or left-hand drive vehicles. Furthermore, the traffic environment in which the vehicle travels may be one based on left-hand traffic or one based on right-hand traffic. Vehicle control according to the present disclosure may be optimized as appropriate according to the road traffic laws of each country and region, as well as the position of the vehicle's steering wheel.

[0175] The controller and methods described herein may be implemented by a special-purpose computer comprising a processor programmed to perform one or more functions embodied in a computer program. Alternatively, the apparatus and methods described herein may be implemented by special-purpose hardware logic circuitry. Alternatively, the apparatus and methods described herein may be implemented by one or more special-purpose computers comprising a processor executing a computer program in combination with one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by a computer on a computer-readable non-transitory storage medium.

[0176] (Disclosure of Technical Ideas) This specification discloses multiple technical ideas described in the following multiple clauses. Some clauses may be described in a multiple dependent form, with the subsequent clause alternatively referring to the preceding clause. Furthermore, some clauses may be described in a multiple dependent form, with the subsequent clause referring to another multiple dependent clause. These multiple dependent clauses define multiple technical ideas.

[0177] (Technical Idea 1) A vehicle control device used in a host vehicle (Am) equipped with a driving control function that assists or substitutes for a driver's driving operation, the vehicle control device comprising: a plan grasping unit (77, 82) that grasps a driving plan of the host vehicle used by the driving control function, and a notification implementation unit (72, 88) that implements route guidance notification when a U-turn control is scheduled to be performed in a manner different from a manner in which the U-turn control is not scheduled to be performed. (Technical Idea 2) The vehicle control device according to Technical Idea 1, wherein the notification implementation unit implements the route guidance notification when a U-turn control is scheduled to be performed in a manner that is more emphasized than the route guidance notification when a U-turn control is not scheduled to be performed. (Technical Idea 3) The vehicle control device according to Technical Idea 1 or 2, wherein the plan understanding unit understands whether a planned U-turn location (UL) where the U-turn control is planned to be performed is an intersection (IA), and further includes a control implementation unit (63) that performs the U-turn control, and the control implementation unit changes content of the U-turn control depending on whether the planned U-turn location is the intersection. (Technical Idea 4) The vehicle control device according to Technical Idea 3, wherein, when performing the U-turn control from a turn source lane (LnS) to a turn destination lane (LnG), the control implementation unit moves the host vehicle closer to an outer edge (EO) of the turn source lane that is located farther from the turn destination lane. (Technical Idea 5) The vehicle control device according to Technical Idea 4, wherein, when the U-turn location is the intersection, the control implementation unit moves the host vehicle closer to the outer edge than when the U-turn location is not the intersection. (Technical Idea 6) The vehicle control device according to any one of Technical Ideas 1 to 5, wherein the notification implementation unit changes the manner of the route guidance notification depending on whether the host vehicle is forced to temporarily stop during the U-turn control or not. (Technical Idea 7) The vehicle control device according to Technical Idea 6, wherein the notification implementation unit emphasizes the route guidance notification when the host vehicle is not forced to temporarily stop compared to when the host vehicle is forced to temporarily stop during the U-turn control.(Technical Idea 8) The vehicle control device according to any one of Technical Ideas 1 to 7, wherein the notification implementation unit changes the manner of the notification of the route guidance depending on whether the host vehicle is turned around during the U-turn control or not. (Technical Idea 9) The vehicle control device according to Technical Idea 8, wherein the notification implementation unit notifies of a wider range of conditions around the host vehicle during the route guidance when the host vehicle is turned around during the U-turn control than when the host vehicle is not turned around. (Technical Idea 10) The vehicle control device according to Technical Idea 8 or 9, further comprising a control implementation unit (63) that implements the U-turn control, wherein the control implementation unit determines whether the host vehicle has reached an impasse after initiation of the U-turn control, and starts the turning around from the point where it has determined that the host vehicle has reached an impasse. (Technical Idea 11) The vehicle control device according to any one of Technical Ideas 1 to 10, further comprising: a permission acquisition unit (71) that acquires permission from a passenger of the vehicle to perform the U-turn control; and a control execution unit (63) that executes the U-turn control when the passenger has given permission to perform the U-turn control. (Technical Idea 12) The vehicle control device according to Technical Idea 11, wherein the notification execution unit notifies the passenger of the number of turns required for the U-turn control as information for determining whether to permit the U-turn control to be performed. (Technical Idea 13) The vehicle control device according to Technical Idea 11 or 12, wherein the control execution unit executes the U-turn control that requires turns only when the passenger has given permission to perform it, and executes the U-turn control that does not require turns even when the passenger has not given permission to perform it. (Technical Idea 14) The vehicle control device according to any one of Technical Ideas 1 to 13, wherein, when a reroute occurs that changes the route set for the vehicle, the notification implementation unit inquires of an occupant of the vehicle whether or not to permit the implementation of the U-turn control after the reroute. (Technical Idea 15) The vehicle control device according to Technical Idea 14, wherein, when a recommended U-turn location that satisfies a recommendation condition for the U-turn control is on the route after the reroute, the notification implementation unit suggests to the occupant that the U-turn control be implemented at the recommended U-turn location.(Technical Idea 16) The vehicle control device according to any one of Technical Ideas 1 to 15, further comprising a control execution unit (63) that avoids the implementation of the U-turn control when the destination (DST) set for the host vehicle can be reached without performing the U-turn control, and that implements the U-turn control when the destination cannot be reached without performing the U-turn control. (Technical Idea 17) The vehicle control device according to any one of Technical Ideas 1 to 16, further comprising a control execution unit (63) that implements the U-turn control, wherein, when implementing the U-turn control from a turn origin lane (LnS) to a turn destination lane (LnG), the control execution unit sets the autonomous driving level in the U-turn control to the autonomous driving level permitted for the turn destination lane. (Technical Idea 18) The vehicle control device according to Technical Idea 17, wherein the control execution unit lowers the autonomous driving level in the driving control function to the autonomous driving level permitted for the turn destination lane while the vehicle is traveling in the turn origin lane. (Technical Idea 19) The vehicle control device according to Technical Idea 17 or 18, wherein the control implementation unit changes whether or not the driver is obligated to grip a steering operation unit in accordance with a control load of the U-turn control. (Technical Idea 20) The vehicle control device according to any one of Technical Ideas 1 to 19, wherein the notification implementation unit issues a notification to encourage the driver to monitor their surroundings when the U-turn control is implemented. (Technical Idea 21) The vehicle control device according to any one of Technical Ideas 1 to 20, further comprising: a target recognition unit (74) that recognizes a rear vehicle traveling behind the host vehicle; and a control implementation unit (63) that implements the U-turn control, wherein the control implementation unit changes a planned driving line of the host vehicle during the U-turn control in accordance with the presence or absence of the rear vehicle. (Technical Idea 22) A vehicle control device according to any one of Technical Ideas 1 to 21, further comprising a control execution unit (63) that executes the U-turn control, wherein the control execution unit determines whether or not to cause the vehicle to extend into an outer lane (LnO) located on the opposite side of the turn destination lane from the turn source lane when executing the U-turn control from the turn source lane (LnS) to the turn destination lane (LnG).(Technical Idea 23) The vehicle control device according to any one of Technical Ideas 1 to 22, further comprising a control execution unit (63) that implements the U-turn control, wherein the control execution unit changes criteria for determining whether to permit the implementation of the U-turn control in accordance with an autonomous driving level to be applied to the U-turn control. (Technical Idea 24) The vehicle control device according to Technical Idea 23, wherein the control execution unit is more likely to permit the implementation of the U-turn control as the autonomous driving level becomes higher. (Technical Idea 25) The vehicle control device according to any one of Technical Ideas 1 to 24, further comprising a control execution unit (63) that implements the U-turn control, wherein the control execution unit changes a planned driving line of the host vehicle in the U-turn control in accordance with an autonomous driving level to be applied to the U-turn control. (Technical Idea 26) The vehicle control device according to Technical Idea 25, wherein the control execution unit sets the planned driving line that does not require a change of direction in accordance with a higher autonomous driving level. (Technical Idea 27) The vehicle control device according to any one of Technical Ideas 1 to 26, further comprising a control execution unit (63) that executes the U-turn control, wherein the control execution unit changes a setting of whether to permit the execution of the U-turn control in accordance with at least one of a positional relationship between a destination set for the host vehicle and a current position, and a time relationship between a scheduled arrival time at the destination and the current time. (Technical Idea 28) A vehicle control program used in a host vehicle (Am) that has a cruise control function that assists or performs driving operations on behalf of a driver, the vehicle control program causing at least one processing unit (11, 51) to execute processes including: grasping a driving plan for the host vehicle that is used by the cruise control function (S61), and providing route guidance when the execution of a U-turn control is scheduled in the driving plan in a manner different from when the execution of the U-turn control is not scheduled (S62).

Claims

1. A vehicle control device used in a host vehicle (Am) equipped with a driving control function that assists or substitutes for a driver's driving operations, comprising: a plan understanding unit (77, 82) that understands a driving plan of the host vehicle used by the driving control function; and a notification implementation unit (72, 88) that provides route guidance notification when a U-turn control is scheduled to be performed in the driving plan in a manner different from that when the U-turn control is not scheduled to be performed.

2. A vehicle control device as described in claim 1, wherein the notification implementation unit implements the route guidance notification when the U-turn control is scheduled to be implemented in a more emphasized manner than the route guidance notification when the U-turn control is not scheduled to be implemented.

3. The vehicle control device described in claim 1, further comprising a control implementation unit (63) that grasps whether the planned U-turn location (UL) where the U-turn control is planned to be implemented is an intersection (IA) or not, and that implements the U-turn control, and the control implementation unit changes the content of the U-turn control depending on whether the planned U-turn location is the intersection or not.

4. A vehicle control device as described in claim 3, wherein when the control implementation unit performs the U-turn control from the turn origin lane (LnS) to the turn destination lane (LnG), the control implementation unit moves the vehicle toward the outer end (EO) of the turn origin lane that is located farther from the turn destination lane.

5. A vehicle control device as described in claim 4, wherein the control implementation unit brings the vehicle closer to the outer edge when the planned U-turn location is the intersection than when the planned U-turn location is not the intersection.

6. A vehicle control device as described in claim 1, wherein the notification implementation unit changes the manner in which the route guidance notification is made depending on whether the U-turn control causes the vehicle to temporarily stop or not.

7. The vehicle control device according to claim 6, wherein the notification implementation unit emphasizes the route guidance notification when the U-turn control does not involve a temporary stop more than when the U-turn control involves a temporary stop.

8. A vehicle control device as described in claim 1, wherein the notification implementation unit changes the manner in which the route guidance notification is made depending on whether the vehicle is turned around during the U-turn control or not.

9. The vehicle control device according to claim 8, wherein the notification unit notifies a wider range of conditions around the vehicle in the route guidance when the U-turn control is performed and the vehicle is turned around, compared to when the U-turn control is not performed.

10. A vehicle control device as described in claim 8 or 9, further comprising a control implementation unit (63) that implements the U-turn control, wherein the control implementation unit determines whether the vehicle has reached an impasse after the start of the U-turn control, and starts the turning from the point where the impasse has been determined.

11. The vehicle control device as described in claim 1, further comprising: a permission acquisition unit (71) that acquires permission from an occupant of the vehicle to perform the U-turn control; and a control implementation unit (63) that implements the U-turn control when permission from the occupant to perform the U-turn control is given.

12. A vehicle control device as described in claim 11, wherein the notification execution unit notifies the passenger of the number of turns required for the U-turn control as information for determining whether or not to permit the execution of the U-turn control.

13. A control device for a vehicle as described in claim 11, wherein the control execution unit executes the U-turn control that requires a turn only when the passenger has given permission to do so, and executes the U-turn control that does not require a turn even when the passenger has not given permission to do so.

14. A vehicle control device as described in claim 1, wherein, when a reroute occurs that changes the route set for the vehicle, the notification implementation unit inquires of an occupant of the vehicle as to whether or not to permit the implementation of the U-turn control after the reroute.

15. A control device for a vehicle as described in claim 14, wherein the notification implementation unit suggests to the passenger that the U-turn control be performed at a recommended U-turn location that satisfies the recommended conditions for the U-turn control if the recommended U-turn location is on the route after the reroute.

16. The vehicle control device as described in claim 1, further comprising a control implementation unit (63) that avoids implementing the U-turn control when the destination (DST) set for the vehicle can be reached without implementing the U-turn control, and implements the U-turn control when the destination cannot be reached without implementing the U-turn control.

17. A vehicle control device as described in claim 1, further comprising a control implementation unit (63) that implements the U-turn control, wherein when the control implementation unit implements the U-turn control from the turn origin lane (LnS) to the turn destination lane (LnG), it sets the autonomous driving level in the U-turn control to the autonomous driving level permitted in the turn destination lane.

18. A vehicle control device as described in claim 17, wherein the control implementation unit lowers the autonomous driving level in the driving control function to the autonomous driving level permitted in the destination lane while traveling in the source lane.

19. The vehicle control device according to claim 17, wherein the control execution unit changes whether or not the driver is required to hold the steering operation unit depending on the control load of the U-turn control.

20. The vehicle control device according to claim 1, wherein the notification execution unit issues a notification to encourage the driver to monitor the surroundings when the U-turn control is performed.

21. A vehicle control device as described in claim 1, further comprising a target recognition unit (74) that recognizes a rear vehicle traveling behind the vehicle, and a control implementation unit (63) that performs the U-turn control, wherein the control implementation unit changes the planned driving line of the vehicle during the U-turn control depending on the presence or absence of the rear vehicle.

22. A vehicle control device as described in claim 1, further comprising a control implementation unit (63) that implements the U-turn control, wherein the control implementation unit determines whether or not to cause the vehicle to extend into an outer lane (LnO) located on the opposite side of the turn destination lane from the turn origin lane when implementing the U-turn control from the turn origin lane (LnS) to the turn destination lane (LnG).

23. A vehicle control device as described in claim 1, further comprising a control implementation unit (63) that implements the U-turn control, wherein the control implementation unit changes the criteria for determining whether or not to permit the implementation of the U-turn control depending on the autonomous driving level to be applied to the U-turn control.

24. The vehicle control device according to claim 23, wherein the control execution unit is configured to more easily permit execution of the U-turn control as the autonomous driving level becomes higher.

25. A vehicle control device as described in claim 1, further comprising a control implementation unit (63) that implements the U-turn control, wherein the control implementation unit changes the planned driving line of the vehicle in the U-turn control according to the autonomous driving level that is planned to be applied to the U-turn control.

26. A vehicle control device as described in claim 25, wherein the control implementation unit sets the planned driving line such that steering is not required as the autonomous driving level becomes higher.

27. A vehicle control device as described in claim 1, further comprising a control execution unit (63) that executes the U-turn control, wherein the control execution unit changes a setting of whether or not to permit the execution of the U-turn control in accordance with at least one of the positional relationship between a destination set in the vehicle and a current position, and the time relationship between a scheduled time of arrival at the destination and the current time.

28. A vehicle control method used in a host vehicle (Am) equipped with a driving control function that assists or substitutes for a driver's driving operation, the vehicle control method including the steps of: grasping a driving plan of the host vehicle used by the driving control function (S61); and providing route guidance when a U-turn control is scheduled to be performed in the driving plan in a manner different from when the U-turn control is not scheduled to be performed (S62), in processing performed by at least one processing unit (11, 51).

Citation Information

Patent Citations

  • Navigator

    JP1998227649A

  • Navigation system

    JP2002340585A

  • Direction change supporting system

    JP2006190237A

  • Navigation system, navigation method, and program

    JP2008128745A

  • Navigation system

    JP2009115476A