Change operation assisting device

Abstract

The present application relates to a change operation assisting device, there is a function for a driver to switch a request state thereof between an off state and an on state in a driving assistance function provided by a vehicle to the driver, there is a possibility that the request state of the driving assistance function unintended by the driver is changed due to a misoperation and a misunderstanding of the driver. When a prescribed specific condition is established, the change operation assisting device of the vehicle executes a setting change confirmation process. The setting change confirmation process is a process of providing confirmation information for confirming whether or not to change the request state of a confirmation target function in the driving assistance function to the driver and changing the request state of the confirmation target function in a case where the driver has performed a prescribed consent operation in accordance with the confirmation information.

Description

[0001] This application is a divisional application of application number 202010058195.0 filed with the China National Intellectual Property Administration on January 19, 2020, entitled "Modified Operation Auxiliary Device". Technical Field

[0002] This invention relates to a change operation assistance device that assists the driver in changing the setting status of driving assistance functions provided by the vehicle. Background Technology

[0003] It is known that there are vehicles that provide driver assistance functions to assist the driver. These driver assistance functions include, for example, radar cruise control (RCC), lane tracing assist (lane keeping assist), forward vehicle start notification, and autonomous driving functions.

[0004] Several configurations of driving assistance functions enable the driver to activate or deactivate them. Furthermore, several configurations of driving assistance functions allow the driver to set / change the control parameters required for the assistance provided by the driving assistance system (e.g., the target inter-vehicle distance in RCC function). When a vehicle is configured to provide multiple driving assistance functions, and / or when the number of configurable / modifiable items for each driving assistance function is large, the operations required to change the setting of a driving assistance function may become cumbersome.

[0005] In view of this, if one of the existing operation assistance devices (hereinafter also referred to as the "existing device") is in a state where the vehicle can provide automatic driving function when the driver operates the first switch, the operation of the automatic driving function is initiated. On the other hand, if the existing device is in a state where the vehicle cannot provide automatic driving function when the driver operates the first switch, the operation of a driving assistance function with a lower level of assistance than the automatic driving function is initiated. According to the existing device, since the initiation of the operation of two driving assistance functions can be specified by one operation of a switch, the number of switches used to change the setting state of the driving assistance function can be reduced. Therefore, the existing device simplifies the operation required to change the setting state of the driving assistance function (see, for example, Patent Document 1).

[0006] Patent Document 1: Japanese Patent Application Publication No. 2018-75873

[0007] Furthermore, there is a possibility that the driver may accidentally operate the control switch (such as the first switch mentioned above) used to change the setting status of the driving assistance function. Alternatively, the driver may operate the control switch without correctly understanding "the setting item to be changed by operating the control switch".

[0008] Therefore, there is a concern that driver error or misunderstanding could lead to changes in the setting of a driver assistance function (e.g., whether the request state is in the off or on state) against the driver's intention. When a driver assistance function is requested to be in the off state, it will not be activated even if the function should be activated. That is, driver assistance based on that function is prohibited. On the other hand, when a driver assistance function is requested to be in the on state, it will be activated if the situation warrants its activation. That is, driver assistance based on that function is permitted.

[0009] However, existing devices do not take into account preventing changes in the request status of driver assistance functions due to misoperation or misunderstanding (i.e., missetting). Summary of the Invention

[0010] In view of this, one of the objectives of the present invention is to provide a change operation assistance device that can avoid missetting of the request state involved in driving assistance functions caused by driver misoperation and misunderstanding.

[0011] The change operation assistance device (hereinafter also referred to as "the device of the present invention") for achieving the above-mentioned objectives includes a driving assistance control unit, an operation unit, and an information provision unit.

[0012] The aforementioned driving assistance control unit (driving assistance ECU 20) is configured to store a "setting state" which includes a "request state as either a disconnected state or an on state" related to the driving assistance functions of the vehicle (10), and is able to provide the aforementioned driving assistance functions based on the setting state.

[0013] The aforementioned operating unit (operating switch 60) is configured to be used in an "operation" performed by the driver of the vehicle to change the aforementioned set state, including a prescribed "request state change operation" to change the aforementioned request state, and is capable of outputting information related to the operation performed by the driver to the aforementioned driving assistance control unit.

[0014] The aforementioned information providing unit (display 27) is configured to be controlled by the aforementioned driving assistance control unit and to provide information related to the aforementioned setting state to the aforementioned driver.

[0015] Furthermore, when the specified "specific conditions" are met, the aforementioned driver assistance control unit performs a "setting change confirmation process".

[0016] The aforementioned setting change confirmation process is a process in which the information providing unit provides the driver with "confirmation information" to confirm whether to change the request status of the "confirmation target function" in the aforementioned driving assistance function, and changes the request status of the confirmation target function when the driver performs the prescribed "agreement operation" using the operation unit based on the confirmation information.

[0017] When specific conditions are met (i.e., when the setting change confirmation process is executed), if the driver agrees based on the confirmation information provided by the information providing unit, the request state of the confirmed function is changed. That is, the request state of the confirmed function is switched between a disconnected state and an on state. In other words, if the driver mistakenly performs a request state change operation, or if the driver misunderstands the steps of the request state change operation, the driver does not agree, and therefore the request state remains unchanged. Therefore, according to the device of the present invention, it is possible to avoid erroneous settings of the request state related to driving assistance functions caused by driver error or misunderstanding.

[0018] In one embodiment (first embodiment) of the apparatus of the present invention,

[0019] The aforementioned driver assistance control unit is configured as follows:

[0020] The condition is met when a "pre-determined similar operation" is performed on the aforementioned operating unit (in Figure 19 If the condition in step 1920 is determined to be "yes", then the specific condition mentioned above is deemed to be met.

[0021] The aforementioned "pre-determined similar operation" is an operation that differs from the request status change operation used to change the request status of the aforementioned confirmed object function to the enabled state, and there is a possibility that the driver may perform the operation in order to change the request status to the enabled state.

[0022] When a driver performs an operation similar to the request for a change in the status of a specific driver assistance function (specifically, the function to be confirmed), a setting change confirmation process is executed. Alternatively, if the driver performs an "agree" operation during the setting change confirmation process, the request status of the function to be confirmed is changed. Therefore, according to the first method, even if the driver performs a similar operation due to misoperation or misunderstanding, the request status of the function to be confirmed can be changed to the desired status by the driver's "agree" operation.

[0023] In other aspects (second aspect) of the device of the present invention,

[0024] The aforementioned driver assistance control unit is configured as follows:

[0025] The condition is met when a request status change operation is performed on the aforementioned confirmed object function to change the request status of the aforementioned driving assistance function to a disconnected state (in Figure 20 If the condition is determined to be "yes" in step 2015, then the above specific condition is determined to be true.

[0026] Sometimes there are driver assistance functions that are suitable for maintaining the request status in the active state unless there is a specific reason. If such a driver assistance function is pre-selected as the confirmation target function, then even if the driver performs an operation to change the request status of the confirmation target function to the deactivated state (i.e., a request status change operation), the request status will not be changed to the deactivated state unless the driver further agrees. Therefore, according to the second method, it is possible to avoid the request status of the confirmation target function being mistakenly changed to the deactivated state.

[0027] In other embodiments (third embodiment) of the device of the present invention,

[0028] The aforementioned driver assistance control unit is configured as follows:

[0029] The condition is met when the request status of the aforementioned driver assistance function is in the off state at the time the request status change operation of "the aforementioned driver assistance function that has been pre-associated with the aforementioned confirmed function but is different from the aforementioned confirmed function" is performed (in Figure 21 If the condition in step 2120 is determined to be "yes", then the above specific condition is determined to be met.

[0030] There are situations where executing a certain driver assistance function (function A) requires the execution of other driver assistance functions (function B). Alternatively, there may be situations where executing function B expands the scope of application of function A. In such cases, for convenience, function B, relative to function A, is also referred to as a "prerequisite function".

[0031] If the prerequisite function for function A (function B in this example) is pre-associated as the confirmation target function, then when the driver performs an operation to change the request status of function A to the enabled state (i.e., a request status change operation), if the request status of the prerequisite function (function B) is disabled, a setting change confirmation process is executed. Furthermore, if the driver agrees during the execution of this setting change confirmation process, the request status of the prerequisite function (function B) is switched to the enabled state. Therefore, according to the third method, even if the driver forgets to set the request status of the prerequisite function to the enabled state, or even if the driver is unaware of the existence of the prerequisite function, the request status of the prerequisite function can be easily switched to the enabled state.

[0032] In other embodiments (fourth embodiment) of the device of the present invention,

[0033] The aforementioned driver assistance control unit is configured as follows:

[0034] The condition is met when the vehicle's driving state meets the "specific driving state predetermined for the aforementioned confirmation object function" and the aforementioned request state of the aforementioned confirmation object function is in the off state. Figure 22 If the condition in step 2220 is determined to be "yes", then the above specific condition is determined to be met.

[0035] Sometimes there are driver assistance functions (driving state-related functions) that are particularly useful when the vehicle's driving state meets a specific driving condition. If a driving state-related function is a confirmation target function, and the vehicle's driving state becomes a specific driving state when the request state of the driving state-related function is in the off state, then a setting change confirmation process is performed for that driving state-related function. Furthermore, if the driver agrees during the execution of this setting change confirmation process, the request state of the driving state-related function is switched to the on state. Therefore, according to the fourth method, even if the driver forgets to set the request state of the driving state-related function to the on state, or is unaware of the usefulness of the driving state-related function, the request state of the driving state-related function can be easily switched to the on state.

[0036] In other embodiments (fifth embodiment) of the device of the present invention,

[0037] The aforementioned driver assistance control unit is configured as follows:

[0038] When the conditions for the aforementioned request status change operation corresponding to the aforementioned confirmed object function are met, it is determined that the aforementioned specific condition is met.

[0039] Ideally, the steps for setting up and changing driving assistance functions should be simple. However, if the steps are overly simple, the possibility of drivers accidentally changing the request status of driving assistance functions increases. However, in the fifth method, if the "driving assistance function with simple setup and change steps" is the function to be confirmed, then when the request status of that driving assistance function is changed, a setting change confirmation process is performed. Therefore, according to the fifth method, the accidental change of the request status of driving assistance functions can be avoided.

[0040] In other embodiments of the device of the present invention (sixth embodiment),

[0041] The aforementioned driver assistance control unit is configured as follows:

[0042] If the above-mentioned setting change confirmation process is performed after the ignition-on operation of the aforementioned vehicle, even if the specific conditions mentioned above are met before the ignition-off operation of the aforementioned vehicle is subsequently performed, the setting change confirmation process will not be performed again (in...). Figure 19 In step 1925, it is determined to be "No".

[0043] The period from the operation of turning on the ignition switch of the vehicle (i.e., ignition on operation) to the operation of turning off the ignition switch is also referred to as the "stroke". In the sixth method, the repeated execution of setting change confirmation processing within the same stroke can be avoided. Alternatively, when the device of the present invention performs multiple setting change confirmation processes (i.e., when there are multiple specific conditions and setting change confirmation processes are performed for each of these specific conditions), the repeated execution of the same type of setting change confirmation process (i.e., corresponding to a single specific condition) within the same stroke can be avoided. Therefore, according to the sixth method, the driver can avoid feeling cumbersome from the multiple executions of setting change confirmation processes within the same stroke.

[0044] In the foregoing description, to aid in understanding the invention, parentheses have been used to denote the names and / or reference numerals used in the embodiments described below. However, the constituent elements of the invention are not limited to the embodiments specified by the foregoing names and / or reference numerals. Other objects, features, and incidental advantages of the invention can be readily understood from the following description of embodiments of the invention with reference to the accompanying drawings. Attached Figure Description

[0045] Figure 1 This is a simplified diagram of a vehicle (this vehicle) that can be equipped with the change operation assistance device (this assistance device) according to the embodiments of the present invention.

[0046] Figure 2 This is a block diagram of the vehicle.

[0047] Figure 3 This is a diagram showing the instrument panel of the display unit (monitor) on which this auxiliary device is installed.

[0048] Figure 4 This is a diagram showing the steering wheel from which the operating section of this auxiliary device is installed.

[0049] Figure 5 This is a table showing a list of the driving assistance functions provided by this auxiliary device.

[0050] Figure 6 This is a diagram showing the home screen displayed on the monitor by this auxiliary device.

[0051] Figure 7This diagram shows the vehicle settings screen displayed on the monitor by this auxiliary device.

[0052] Figure 8 This is a diagram showing the setting screen for the pre-collision safety function displayed on the monitor by this auxiliary device.

[0053] Figure 9 This is a diagram showing the setting screen for the forward vehicle start notification function displayed on the monitor by this auxiliary device.

[0054] Figure 10 This is a diagram showing the change confirmation screen involved in the RCC start confirmation process performed by this auxiliary device.

[0055] Figure 11 This is a diagram showing the change notification screen involved in the RCC confirmation process performed by this auxiliary device.

[0056] Figure 12 This is a diagram showing the change confirmation screen involved in the work stop confirmation process performed by this auxiliary device.

[0057] Figure 13 This is a diagram showing the change notification screen related to the work stop confirmation process performed by this auxiliary device.

[0058] Figure 14 This is a diagram showing the change confirmation screen that indicates the prerequisite function being performed by this auxiliary device has begun processing.

[0059] Figure 15 This is a diagram showing the first change notification screen involved in the processing of the prerequisite functions performed by this auxiliary device.

[0060] Figure 16 This is a diagram showing the second change notification screen that indicates the start of processing of the prerequisite functions performed by this auxiliary device.

[0061] Figure 17 This is a diagram indicating that the work performed by this auxiliary device has begun and a change confirmation screen has been created.

[0062] Figure 18 This is a diagram showing the screen indicating that the work performed by this auxiliary device has begun and the change notification involved in the proposed processing has been displayed.

[0063] Figure 19 This is a flowchart representing the RCC start confirmation process routine executed by this auxiliary device.

[0064] Figure 20 This is a flowchart representing the work stop confirmation process performed by this auxiliary device.

[0065] Figure 21This is a flowchart indicating the pre-function start processing routine performed by this auxiliary device.

[0066] Figure 22 This is a flowchart indicating the start of the work proposal processing routine performed by this auxiliary device.

[0067] Explanation of reference numerals in the attached figures:

[0068] 10…Vehicle; 20…Driver Assist ECU; 26…Map Database; 27…Display; 28…Speaker; 29…Instrument Panel; 55…Steering Wheel; 60…Operating Switch; 61…Cruise Control Switch; 62…Cancel Switch; 63…Distance Setting Switch; 64…LTA Switch; 65…Selector Switch; 66…OK Switch; 67…Return Switch. Detailed Implementation

[0069] Hereinafter, the modification operation assistance device (hereinafter also referred to as "this assistance device") according to the embodiments of the present invention will be described with reference to the accompanying drawings. This assistance device is applied to... Figure 1 The vehicle 10 is shown. In addition, the block diagram of vehicle 10 is as follows: Figure 2 As shown. This auxiliary device includes "driving assistance ECU20, engine ECU31, brake ECU32 and EPS-ECU33" which are electronic control units (ECUs).

[0070] The driver assistance ECU 20 comprises a microcomputer as its main component, equipped with a CPU, non-volatile memory, and RAM. The CPU performs data reading, numerical calculations, and output of results by sequentially executing prescribed programs (routines). The non-volatile memory, composed of flash memory, stores the programs executed by the CPU, the lookup tables (setting tables) referenced during program execution, and the setting states of the driver assistance functions (described later). The RAM temporarily stores the data referenced by the CPU.

[0071] The engine ECU 31, brake ECU 32, and EPS-ECU 33, like the driver assistance ECU 20, each include a microcomputer as their main component. These ECUs can communicate (exchange data) with each other via CAN (Controller Area Network) 34. Furthermore, these ECUs can receive output values ​​from sensors connected to other ECUs via CAN 34.

[0072] The driver assistance ECU 20 is connected to a front camera 21, a millimeter-wave radar 22, a vehicle speed sensor 23, an acceleration sensor 24, a GPS receiver 25, a map database 26, a multi-information display 27, and a speaker 28.

[0073] Front camera 21 (reference) Figure 1 The system acquires images of the area in front of the vehicle 10 (hereinafter also referred to as "front image") and outputs a signal representing the front image to the driver assistance ECU 20 every specified time interval.

[0074] The millimeter-wave radar 22 includes a front central radar 22a, a left front radar 22b, a right front radar 22c, a left rear radar 22d, and a right rear radar 22e (see reference). Figure 1 ).

[0075] The front central radar 22a detects objects located in the area in front of the vehicle 10. The left front radar 22b detects objects located in the area in front left of the vehicle 10. The right front radar 22c detects objects located in the area in front right of the vehicle 10. The left rear radar 22d detects objects located in the area in front left of the vehicle 10. The right rear radar 22e detects objects located in the area in front right of the vehicle 10.

[0076] The radar device included in the millimeter-wave radar 22 obtains information such as the orientation, distance and relative speed of the target by transmitting (radiating) millimeter-wave radio waves (millimeter waves) and receiving the reflected waves of the transmitted millimeter waves. It outputs the target information to the driving assistance ECU 20 every specified time interval.

[0077] Vehicle speed sensor 23 detects the vehicle speed Vt of vehicle 10 and outputs a signal representing vehicle speed Vt to driver assistance ECU 20. Acceleration sensor 24 detects the forward and backward acceleration As of vehicle 10 and outputs a signal representing acceleration As to driver assistance ECU 20.

[0078] The GPS receiver 25 obtains the current position Pn of the vehicle 10 based on the signal (radio wave) received from the positioning satellite (GPS satellite in this embodiment), and outputs a signal indicating the current position Pn to the driver assistance ECU 20.

[0079] Map database 26 consists of a hard disk drive (HDD) and stores map information. Map database 26 includes information (map information) related to "nodes," "road segments," and "facilities." Nodes are intersections and endpoints, etc. Road segments are roads connecting nodes to each other. Facilities are buildings adjacent to road segments, parking lots, etc. Information related to road segments includes the road type (whether it is a general road, a highway, or a dedicated motorway).

[0080] Figure 3The instrument panel 29 shown includes a multi-information display 27. The instrument panel 29 is located within the passenger compartment of the vehicle 10 at a position visible to the driver (specifically, in front of the driver), providing the driver with information related to the driving status of the vehicle 10. The multi-information display 27 is also simply referred to as display 27.

[0081] The display 27 is equipped with a liquid crystal display (LCD). The text and graphics displayed on the display 27 are controlled by the driver assistance ECU 20. The display 27 shows the execution status of the driver assistance functions.

[0082] A speaker 28 is installed inside the passenger compartment of the vehicle 10. Warning sounds and voice messages reproduced by the speaker 28 are controlled by the driver assistance ECU 20. When switching the screen displayed on the display 27 and when the driver operates the operation switch 60 (described later), the driver assistance ECU 20 causes the speaker 28 to reproduce a prescribed beep tone appropriately.

[0083] In addition, the driver assistance ECU 20 is connected to the ignition switch 35. In this embodiment, the ignition switch 35 is a button. If the ignition switch 35 is operated when the driver assistance ECU 20 is in the off state (hereinafter also referred to as "ignition on operation"), the driver assistance ECU 20 will become in the on state.

[0084] In addition, if an ignition is turned on, the driver assistance ECU20 will switch the operating status of the engine ECU31, brake ECU32 and EPS-ECU33 from the off state to the on state. At this time, the engine ECU31 will start the operation of the engine 41, which will be described later.

[0085] On the other hand, the operation of the ignition switch 35 when the driver assistance ECU 20 is in the on state will also be referred to as the "ignition disconnection operation". If the ignition disconnection operation is performed, the driver assistance ECU 20 switches the operating states of the engine ECU 31, brake ECU 32, and EPS-ECU 33 from the on state to the off state. At this time, the engine ECU 31 stops the engine 41. Furthermore, the driver assistance ECU 20 becomes disconnected.

[0086] like Figure 4 As shown, Figure 2 The operating switch 60 shown is disposed on the steering wheel 55. The operating switch 60 includes a cruise control switch 61, a cancel switch 62, a vehicle distance setting switch 63, an LTA switch 64, a selector switch 65, an OK switch 66, and a return switch 67. The cruise control switch 61 is also referred to simply as the CC switch 61.

[0087] The driver assistance ECU 20 is connected to each of the operation switches 60 and receives information related to the driver's operation of each operation switch 60. That is, the driver assistance ECU 20 can detect whether the operation switch 60 is pressed or canceled. As described later, the driver of vehicle 10 can change the setting of the driver assistance function by operating the operation switches 60.

[0088] CC switch 61 is a so-called "cross-shaped key" containing four directional switches (up, down, left, and right). The right side of CC switch 61 functions as the main switch; that is, pressing the right side of CC switch 61 is equivalent to pressing the main switch. Similarly, the upper part of CC switch 61 functions as a reset switch, and the lower part of CC switch 61 functions as a setting switch.

[0089] Selector switch 65, like CC switch 61, is a so-called "cross-shaped directional pad". The right side of selector switch 65 operates as a right-side switch. The left side of selector switch 65 operates as a left-side switch. The upper part of selector switch 65 operates as an upper-side switch. The lower part of selector switch 65 operates as a lower-side switch.

[0090] (Control of driving force)

[0091] The engine ECU 31 adjusts the driving force of the vehicle 10 by controlling the engine 41 and the transmission 42 (see reference). Figure 2 The engine ECU 31 is connected to various engine sensors 43 and receives the output values ​​of these sensors. Engine sensors 43 are sensors that detect the operating state (parameters) of the engine 41. Engine sensors 43 include an accelerator pedal operation amount (pedaling amount) sensor, a throttle opening sensor, an internal combustion engine speed sensor, and an intake air volume sensor, etc. The engine ECU 31 determines the requested drive torque Dreq (the requested value of drive torque Dd, described later) based on the vehicle speed Vt and the output values ​​of the engine sensors 43.

[0092] In addition, the engine ECU 31 is connected to the engine actuator 44, which includes a throttle actuator and a fuel injection valve, and controls the torque generated by the engine 41 by controlling these actuators. The engine ECU 31 controls the engine actuator 44 and the transmission 42 in such a way that the drive torque Dd transmitted to the drive wheels of the vehicle 10 is consistent with the requested drive torque Dreq, thereby controlling the acceleration As.

[0093] Furthermore, if the engine ECU 31 receives a "drive force control request" including the target drive torque Ddtg from the driver assistance ECU 20, it controls the engine actuator 44 and the transmission 42 in such a way that the actual drive torque Dd is consistent with the target drive torque Ddtg.

[0094] (Control of braking force)

[0095] The brake ECU 32 controls the hydraulic friction braking device, i.e., the braking mechanism 45, mounted on the vehicle 10. The brake ECU 32 is connected to various brake sensors 46 and receives the output values ​​of these sensors. The brake sensors 46 are sensors that detect state quantities used to control the braking mechanism 45, including brake pedal operation sensors and brake fluid pressure sensors acting on the braking mechanism 45. The brake ECU 32 determines the requested braking force Breq (the requested value of braking force Bf, described later) based on the vehicle speed Vt and the output values ​​of the brake sensors 46.

[0096] In addition, the brake ECU32 is connected to the hydraulic control actuator of the brake mechanism 45, namely the various brake actuators 47. The brake ECU32 controls the brake actuators 47 in such a way that the frictional braking force generated by each wheel, namely the braking force Bf, is consistent with the requested braking force Breq, thereby controlling the acceleration As (in this case, the degree of reduction of the magnitude of the vehicle speed Vt, i.e., deceleration).

[0097] Furthermore, if the brake ECU32 receives a "braking force control request" including the target braking force Bftg from the driver assistance ECU20, it controls the brake actuator 47 in such a way that the actual braking force Bf is consistent with the target braking force Bftg.

[0098] (Control of steering assist torque and steering angle)

[0099] The EPS-ECU33 is connected to the torque sensor 51 and the steering angle sensor 52, receiving detection signals from these sensors. The torque sensor 51 applies force to the steering wheel 55 (see reference 52) by the driver. Figure 4 The steering torque Ts of the steering wheel 55 is detected, and a signal representing the steering torque Ts is output. The steering angle sensor 52 detects the rotation angle of the steering wheel 55, i.e., the steering angle θs, and outputs a signal representing the steering angle θs.

[0100] The EPS-ECU33 determines the target value of the torque (assistance torque) that assists the driver's operation of the steering wheel 55 based on vehicle speed Vt, steering torque Ts, and steering angle θs.

[0101] EPS-ECU33 is connected to drive circuit 53. Drive circuit 53 supplies power to steering motor 54. Steering motor 54 generates torque Tm that rotates the steering shaft. EPS-ECU33 controls drive circuit 53 in a manner that the torque Tm matches the target auxiliary torque Tatg.

[0102] Furthermore, if the EPS-ECU33 receives a "steering angle control request" including the target steering angle θstg from the driver assistance ECU20, it controls the steering motor 54 in such a way that the actual steering angle θs is consistent with the target steering angle θstg.

[0103] (Overview of driving assistance functions)

[0104] The driver assistance ECU 20 provides various driver assistance functions to assist the driver in driving the vehicle 10. A list of the driver assistance functions provided by the driver assistance ECU 20 is available at [link to list]. Figure 5 The information is presented in table form. The following is a summary of the driver assistance functions.

[0105] (1) Pre-collision safety (PCS)

[0106] The pre-collision safety function is a function that warns the driver and generates braking force Bf when there is a high probability of collision with an object (specifically, other vehicles, bicycles, pedestrians, etc.) located in front of the vehicle 10 while the vehicle 10 is moving forward. The warnings and notifications to the driver involved in the pre-collision safety function and other driving assistance functions are delivered via the display 27 and the speaker 28.

[0107] (2) Lane Tracing Assist (LTA)

[0108] Lane tracing assist (hereinafter also referred to as "LTA function") includes the functions described below: "lane departure warning function", "lane departure prevention function" and "lane keeping assist function".

[0109] The Lane Departure Warning function warns the driver when the vehicle 10 attempts to leave its lane while traveling on a designated lane (specifically, a highway lane or dedicated vehicle lane). The Lane Departure Prevention function controls the steering angle θs to prevent the vehicle 10 from leaving its lane while traveling on a designated lane. The Lane Keeping Assist function controls the steering angle θs to keep the vehicle 10 within its lane while traveling on a designated lane, based on the radar cruise control function described later. The Lane Tracing Assist function is also known as Lane Keeping Assist (LKA).

[0110] (3) Road Sign Assistance (RSA)

[0111] The road sign assist function is a function that identifies road signs located in front of the vehicle 10 and displays the symbols representing the identified road signs on the display 27. In addition, the road sign assist function is a function that warns the driver if the driving state of the vehicle 10 violates the "traffic rules represented by the identified road signs".

[0112] exist Figure 6 In the example of the screen displayed on the display 27 (the home screen 71 described later), sign 71a indicates a speed limit sign recognized by the road sign assist function.

[0113] (4) Radar cruise control

[0114] Radar cruise control (hereinafter also referred to as "RCC function") is a function that controls acceleration As in a manner that maintains the distance between vehicle 10 and the preceding vehicle (the vehicle being followed) at a predetermined target value, even when the driver does not operate the accelerator pedal. During the execution of RCC function, if the vehicle being followed is not present, acceleration As is controlled at a speed Vt that matches the "set speed Vset set through the setting steps described later". RCC function is also known as adaptive cruise control (ACC) function.

[0115] The setting involved in the RCC function is the "target inter-vehicle distance". The driver can set the target inter-vehicle distance to any of the following: "long (i.e., a relatively long distance)," "medium (i.e., a moderate distance)," and "short (i.e., a relatively short distance)".

[0116] exist Figure 6 In the top screen 71 shown, vehicle symbol 10a represents vehicle 10, and vehicle symbol 71b represents the vehicle being followed. Vehicle distance symbol 71c indicates that the target vehicle distance is set to "long".

[0117] (5) Notification of the vehicle in front starting

[0118] The forward vehicle start notification function is a function that informs the driver if the vehicle 10 continues to stop even if the forward vehicle starts moving when the vehicle 10 is stopped behind the parked forward vehicle.

[0119] The setting for the forward vehicle start notification function is "Notification Distance". The driver can set the notification distance to any of "Long", "Medium", or "Short". If the distance between the forward vehicle and vehicle 10 is greater than the notification distance, the notification will be initiated.

[0120] (6) Blind Spot Monitoring (BSM)

[0121] The blind spot monitoring function is a function that warns the driver of the presence of an object if there is one behind or to the side of the vehicle when the vehicle changes lanes.

[0122] (7) Gap sonar

[0123] The gap sonar function is a function that warns the driver of the presence of an obstacle (especially a stationary object, such as a wall) in the vicinity of the vehicle 10.

[0124] (8) Rear Cross Traffic Alert (RCTA)

[0125] The rear cross traffic warning function is a feature that warns the driver of the presence of an object (especially another vehicle) approaching from the rear side when the vehicle is reversing.

[0126] (9) Parking Assist Brake (PKSB)

[0127] The parking assist braking function is a function that warns the driver and generates braking force Bf if there is a high probability of collision with objects (especially walls and other vehicles) when the vehicle is traveling at low speed.

[0128] To implement these driver assistance functions, the driver assistance ECU 20 utilizes the forward image received from the forward camera 21 and the target information received from the millimeter-wave radar 22. In addition, to achieve these driver assistance functions, the driver assistance ECU 20 controls the engine ECU 31, brake ECU 32, and EPS-ECU 33 as needed. That is, the driver assistance ECU 20 sends drive force control requests, braking force control requests, and steering angle control requests to the corresponding ECUs as needed.

[0129] For example, during the execution of the RCC function, the driver assistance ECU 20 acquires (determines) the target acceleration Astg after a predetermined period of time. To acquire the target acceleration Astg, the driver assistance ECU 20 obtains the distance and relative speed between the target vehicle and vehicle 10 based on object information. If there is no target vehicle, the driver assistance ECU 20 calculates the target acceleration Astg with the vehicle speed Vt matching the set vehicle speed Vset. In addition, the driver assistance ECU 20 controls the engine ECU 31 and the brake ECU 32 with the actual acceleration As matching the target acceleration Astg.

[0130] Alternatively, during the execution of the LTA function (more specifically, during the execution of the lane keeping assist function), at predetermined intervals, the driver assistance ECU 20 acquires (determines) the target steering angle θstg and sends a steering angle control request, including the target steering angle θstg, to the EPS-ECU 33. In order to acquire the target steering angle θstg, the driver assistance ECU 20 extracts (identifies) the pair of lane dividing lines (i.e., the left dividing line and the right dividing line) contained in the image ahead using known methods.

[0131] Furthermore, the driver assistance ECU 20 obtains the "set of center points in the left and right directions of the lane extending forward of the vehicle 10" as the lane centerline based on the positions of the left and right dividing lines relative to the vehicle 10. Moreover, the driver assistance ECU 20 calculates the deviation between the lane centerline and the actual driving path of the vehicle 10, and calculates the target steering angle θstg based on this deviation, assuming the vehicle 10 is traveling on the lane centerline.

[0132] (Changes to settings related to driver assistance functions)

[0133] The driver assistance ECU 20 changes the settings related to the driver assistance functions based on the driver's operation of the operating switch 60, and provides the aforementioned driver assistance functions according to the changed settings. The steps for changing the settings of the driver assistance functions will be explained in the order of RCC function, LTA function, and other driver assistance functions.

[0134] If the driver presses the main switch of CC switch 61 when the RCC function request state is off, and then presses the setting switch of CC switch 61 before a predetermined time has elapsed, the driver assistance ECU 20 will switch the RCC function request state to on. In addition, the driver assistance ECU 20 will set the set vehicle speed Vset to a value equal to the vehicle speed Vt at that moment.

[0135] When the RCC function request state is active (i.e., the RCC function is in operation), pressing the reset switch of CC switch 61 increases the set vehicle speed Vset by a predetermined amount. Conversely, when the RCC function is in operation, pressing the setting switch of CC switch 61 decreases the set vehicle speed Vset by a predetermined amount. When the RCC function is in operation, pressing the cancel switch 62, or operating the brake pedal, switches the RCC function request state from active to disabled.

[0136] The operation performed to switch the request status of a certain driving assistance function from the off state to the on state is also referred to as the "activation operation". That is, the activation operation of the RCC function is the operation of pressing the setting switch within a specified time after pressing the main switch of CC switch 61. On the other hand, the operation performed to switch the request status of a certain driving assistance function from the on state to the off state is also referred to as the "disconnection operation". That is, the disconnection operation of the RCC function is the operation of pressing the cancel switch 62 and the operation of the brake pedal. For convenience, the activation and disconnection operations of driving assistance functions are also collectively referred to as "request status change operation".

[0137] The vehicle distance setting switch 63 is used to set the vehicle distance target value for the RCC function. Specifically, whenever the vehicle distance setting switch 63 is pressed, the driver assistance ECU 20 switches the vehicle distance target value in the order of "long", "medium", "short" and "long".

[0138] The LTA switch 64 is used to change the request state of the LTA function. Specifically, whenever the LTA switch 64 is pressed, the driver assistance ECU 20 toggles the request state of the LTA function between an on and off state.

[0139] To change the setting status of driver assistance functions other than "RCC function and LTA function", the driver operates the selection switch 65 and the OK switch 66 while referring to the screen displayed on the display 27. The driver uses the selection switch 65 (more specifically, the right switch, left switch, top switch and bottom switch of the selection switch 65) to switch the highlighted buttons among the buttons displayed on the display 27 (specifically, the button elements displayed on the display 27) and presses the OK switch 66 to "select" the desired button.

[0140] For example, after the ignition is turned on and the driver assistance ECU 20 starts working, if the driver does not operate the control switch 60, the home screen 71 will be displayed on the monitor 27. Figure 6 The image shows an example of the home screen 71 when the road sign assist function and RCC function are being executed. The home screen 71 includes menu buttons 81a to 81e.

[0141] exist Figure 6 And other examples of images described later (i.e. Figures 7-18 In the diagram, the outline of the highlighted buttons is represented by a thick line. Figure 6 In the example, the highlight emphasizes the menu button 81e. If the driver selects the menu button 81e, then... Figure 7 The vehicle settings screen 72 shown is displayed on the monitor 27.

[0142] The vehicle settings screen 72 includes function buttons 82a to 82g, which are associated with driver assistance functions other than the "RCC function and LTA function," and a return button 83a. If the return button 83a is selected, the home screen 71 is displayed on the monitor 27. Similarly, if the return switch 67 is pressed while the vehicle settings screen 72 is displayed on the monitor 27, the home screen 71 is displayed on the monitor 27.

[0143] If the return switch 67 is pressed when the screens of the return buttons 83b to 83h (described later) are displayed on the display 27, the driving assistance ECU 20 performs the same process as when the "return button displayed on the display 27" is selected (specifically, the process of screen migration).

[0144] Returning to the instructions for changing the settings of driver assistance functions. For example, if function button 82a on the vehicle settings screen 72 is selected, then... Figure 8 The pre-collision safety function setting screen 73 is displayed on the monitor 27. The setting screen 73 includes an on button 84a, an off button 84b, and a return button 83b. If the return button 83b is selected, the vehicle setting screen 72 is displayed on the monitor 27.

[0145] When the screen displayed on monitor 27 transitions to setting screen 73, if the pre-collision safety function request status is enabled at that moment, then as follows: Figure 8 As shown in the example, the activation button 84a is highlighted. On the other hand, when the displayed screen transitions to the setting screen 73, if the request state of the pre-collision safety function is in the off state, the deactivation button 84b is highlighted.

[0146] The driver can switch (change) the request state of the pre-collision safety function between the off and on states by selecting either the on button 84a or the off button 84b (that is, by operating the selection switch 65 to change the button that is highlighted between the on button 84a and the off button 84b and pressing the OK switch 66).

[0147] On the other hand, if you choose Figure 7 The function button 82c in the vehicle settings screen 72, then Figure 9The setting screen 74 for the forward vehicle start notification function is displayed on the monitor 27. The setting screen 74 includes an on button 85a, an off button 85b, distance buttons 86a-86c, and a return button 83c. The on button 85a and off button 85b correspond to the request status of the forward vehicle start notification function. The distance buttons 86a-86c correspond to the notification distance, which is a setting item for the forward vehicle start notification function. If the return button 83c is selected, the vehicle setting screen 72 is displayed on the monitor 27.

[0148] according to Figure 8 as well as Figure 9 This can be understood as: in the settings screen of a driver assistance function that includes settings other than the requested state (additional settings), a button is displayed for selecting to change the setting state of the additional settings. Figure 9 In the example, the driver can change the informed distance (i.e., add a setting) by selecting any one of the distance buttons 86a to 86c.

[0149] (Setting up a change confirmation process)

[0150] When the specified conditions (also referred to as "specific conditions" for convenience) are met, the driver assistance ECU 20 performs a "setting change confirmation process" to confirm with the driver whether to switch the driver assistance function (also referred to as "confirmation target function") corresponding to the specific condition between the disconnected and on states.

[0151] When performing a setting change confirmation process, in order to confirm whether to switch the request status of the driving assistance function (i.e., the function to be confirmed) corresponding to the setting change confirmation process, the driving assistance ECU 20 will display a change confirmation screen (e.g., as described later) on the screen to confirm whether to switch the request status of the driving assistance function (i.e., the function to be confirmed). Figure 10 The change confirmation screen 75a) shown is displayed on the monitor 27. For convenience, the information conveyed to the driver through the change confirmation screen is also referred to as "confirmation information".

[0152] The change confirmation screen includes an "Agree" button (e.g.) Figure 10 (See the Agree button 87a). If the driver selects the Agree button based on the confirmation information, the driver assistance ECU 20 changes the request status of the function corresponding to the confirmation information. For convenience, the operation of selecting the Agree button is also referred to as the "Agree operation".

[0153] In this embodiment, the configuration change confirmation process includes RCC start confirmation process, work stop confirmation process, prerequisite function start process, and work start proposal process. The configuration change confirmation processes will be described in turn below.

[0154] (Settings change confirmation process - RCC initiates confirmation process)

[0155] If the setting switch of CC switch 61 is pressed when the RCC function request state is off (the main switch of CC switch 61 is not pressed), the driver assistance ECU 20 will perform an "RCC start confirmation process" to confirm with the driver whether the RCC function request state should be switched to the on state. That is, regarding the RCC start confirmation process, the RCC function must meet the confirmation criteria. For convenience, the operation of pressing the setting switch of CC switch 61 when the RCC function request state is off (the main switch of CC switch 61 is not pressed) is also referred to as a "similar operation".

[0156] At the start of the RCC confirmation process, the driver assistance ECU 20 will Figure 10 The change confirmation screen 75a, which involves the RCC start confirmation process, is displayed on the monitor 27. This change confirmation screen 75a includes an agree button 87a and a refuse button 87b. In addition, the change confirmation screen 75a includes a description (i.e., confirmation information) indicating that the RCC function has been changed to the on state through the RCC function activation operation (i.e., pressing the setting switch within a specified time after pressing the main switch of CC switch 61) and the selection of the agree button 87a.

[0157] If the driver selects the "agree" button 87a, the driver assistance ECU 20 will switch the RCC function request status to "on" and set the set vehicle speed Vset to a value equal to the vehicle speed Vt at that moment. In addition, in this case, the driver assistance ECU 20 will... Figure 11 The change notification screen 75b, which indicates that the RCC has begun to confirm the processing, is displayed on the display 27, informing the driver that the request status of the RCC function has changed to the enabled state.

[0158] The change notification screen 75b includes a return button 83d. If the driver selects the return button 83d, or if a predetermined display time Td elapses after the change notification screen 75b is displayed without selecting the return button 83d, the driver assistance ECU 20 displays the screen that immediately precedes the display of the change confirmation screen 75a on the display 27d. Hereinafter, the screen that immediately precedes the start of the change confirmation process will also be referred to as the "immediate screen".

[0159] On the other hand, if the driver selects the deny button 87b when the change confirmation screen 75a is displayed, the driver assistance ECU 20 maintains the RCC function request status as disconnected. Alternatively, if neither the agree button 87a nor the deny button 87b is selected for a duration Td after the change confirmation screen 75a is displayed, the driver assistance ECU 20 also maintains the RCC function request status as disconnected. In all other cases, the driver assistance ECU 20 displays the immediate preceding screen on the display 27. While displaying the immediate preceding screen on the display 27, the driver assistance ECU 20 terminates the execution of the RCC start confirmation process.

[0160] Furthermore, the period from the ignition on operation to the ignition off operation is also referred to as a "stroke". The driver assistance ECU 20 does not perform multiple RCC start confirmation processes within a stroke. That is, during the period from the end of the RCC start confirmation process to the ignition off operation, if the RCC function request status is off (the main switch of CC switch 61 is not pressed), the driver assistance ECU 20 will not perform the RCC start confirmation process even if the setting switch of CC switch 61 is pressed. In other words, the RCC start confirmation process is performed at most once within a stroke.

[0161] (Settings for change confirmation - Work stoppage confirmation)

[0162] If the driver performs a specified disengagement operation for a driving assistance function, the driving assistance ECU 20 executes a "work stop confirmation process" to verify whether the operation is what the driver intended. The driving assistance function that executes the work stop confirmation process when a disengagement operation is performed (hereinafter also referred to as the "work stop confirmation object function") is... Figure 5 The table shown indicates driver assistance functions circled in column Cm1. The work stop confirmation function is the function involved in the work stop confirmation process. The work stop confirmation function is a driver assistance function suitable for maintaining the requested state as active unless there is a specific reason.

[0163] The work stop confirmation process will be explained using the disconnection operation of the pre-collision safety function, which is the object of the work stop confirmation function, as an example. If the disconnection button 84b on setting screen 73 is selected when the request state of the pre-collision safety function is enabled (see...). Figure 8 (That is, if a disconnection operation is performed), the driver assistance ECU20 will start working to stop the confirmation process.

[0164] At the start of the work stop confirmation process, the driver assistance ECU 20 will Figure 12The example work stop confirmation process is displayed on the monitor 27 via a change confirmation screen 76a. This change confirmation screen 76a includes an agree button 88a and a refuse button 88b.

[0165] If the driver selects the "agree" button 88a, the driver assistance ECU 20 will switch the pre-collision safety function request status to the "disabled" status. Otherwise, in this situation, the driver assistance ECU 20 will... Figure 13 The example of a work stop confirmation process is displayed on screen 27, showing a change notification screen 76b that informs the driver that the request status of the pre-collision safety function has changed to the off state.

[0166] The change notification screen 76b includes a return button 83e. If the driver selects the return button 83e, or if the display time Td elapses after the change notification screen 76b is displayed and the driver does not select the return button 83e, the driver assistance ECU 20 will display the immediate screen on the display 27.

[0167] On the other hand, if the driver selects the "Deny" button 88b when the change confirmation screen 76a is displayed, the driver assistance ECU 20 will maintain the pre-collision safety function request status as "On". Alternatively, if neither the "Agree" button 88a nor the "Deny" button 88b is selected for a duration Td after the change confirmation screen 76a is displayed, the driver assistance ECU 20 will also maintain the pre-collision safety function request status as "On". In addition, in these cases, the driver assistance ECU 20 will display the immediate scene on the display 27.

[0168] (Configuration change confirmation process - prerequisite function begins processing)

[0169] As described above, the lane keeping assist function included in the LTA function is not executed if the RCC function is not activated. In other words, the RCC function is a prerequisite function for the lane keeping assist function. Therefore, when the driver activates the LTA function, if the request status of the RCC function (i.e., the prerequisite function) is off, the driver assistance ECU 20 performs a "prerequisite function initiation process" to confirm with the driver whether the request status of the RCC function, in addition to the LTA function's request status, has also been switched to the on state. That is, if the LTA switch 64 is pressed when both the LTA and RCC function request statuses are off, the driver assistance ECU 20 begins the prerequisite function initiation process for the LTA function (more specifically, the lane keeping assist function). The RCC function is the function to be confirmed in the prerequisite function initiation process.

[0170] At the start of the prerequisite function processing, the driver assistance ECU 20 will Figure 14The change confirmation screen 77a, which indicates that the prerequisite function has begun processing, is displayed on the monitor 27. This change confirmation screen 77a includes an agree button 89a and a refuse button 89b.

[0171] If the driver selects the "agree" button 89a, the driver assistance ECU 20 will switch the request status of both the LTA and RCC functions to the "on" state and set the set vehicle speed Vset to a value equal to the vehicle speed Vt at that moment. In addition, in this case, the driver assistance ECU 20 will... Figure 15 The first change notification screen 77b, which is involved in the processing of the prerequisite function, is displayed on the display 27, informing the driver that the request status of both the LTA function and the RCC function has changed to the on state.

[0172] The first change notification screen 77b includes a return button 83f. If the driver selects the return button 83f, or if a display time Td elapses after the first change notification screen 77b is displayed without selecting the return button 83f, the driver assistance ECU 20 will display the immediate screen on the display 27.

[0173] On the other hand, if the driver selects the "Deny" button 89b when the change confirmation screen 77a is displayed, the driver assistance ECU 20 switches the LTA function request status to the "On" state, while maintaining the RCC function request status in the "Off" state. Alternatively, if neither the "Agree" button 89a nor the "Deny" button 89b is selected for a duration Td after the change confirmation screen 77a is displayed, the driver assistance ECU 20 similarly switches the LTA function request status to the "On" state, while maintaining the RCC function request status in the "Off" state. In these cases, Figure 16 The second change notification screen 77c, which is involved in the processing of the prerequisite function, is displayed on the display 27, informing the driver that the LTA function is switched to the on state.

[0174] The second change notification screen 77c includes a return button 83g. If the driver selects the return button 83g, or if a display time Td elapses after the second change notification screen 77c is displayed without selecting the return button 83g, the driver assistance ECU 20 will display the immediate screen on the display 27.

[0175] (Setting up change confirmation process - Work start proposal process)

[0176] Figure 5The driver assistance functions circled in column Cm2 of the table shown (i.e., LTA function, RCC function, and blind spot monitoring function) are particularly useful when vehicle 10 is traveling on highways and dedicated motor vehicle lanes. For convenience, the state in which vehicle 10 is traveling on these roads is also referred to as a "specific driving state". However, when vehicle 10 is in a specific driving state, there is a possibility that some or all of these driver assistance functions (i.e., driver assistance functions circled in column Cm2, hereinafter also referred to as "driving state-related functions") may be in a deactivated state. Hereinafter, the driver assistance functions (driving state-related functions) circled in column Cm2 whose deactivated state is also referred to as "proposed target functions".

[0177] If the current location Pn is located on a "segment" in map database 26 representing either a highway or a dedicated road, then the driver assistance ECU 20 determines that the vehicle 10 is in a specific driving state. If a proposed object function exists when the vehicle 10 is in a specific driving state, then the driver assistance ECU 20 executes a "work start proposal processing" to suggest to the driver that the request state of the proposed object function be switched to the enabled state. The proposed object function is the confirmation object function involved in the work start proposal processing.

[0178] At the start of the work commencement process, the driver assistance ECU 20 will... Figure 17 The example of a work start proposal process involving a change confirmation screen 78a is displayed on the display 27. In this example, the request status of the LTA function is enabled, while the request status of the RCC function and the blind spot monitoring function are both disabled. Therefore, the RCC function and the blind spot monitoring function are the proposed functions. In this case, the driver assistance ECU 20 displays the change confirmation screen 78a to propose to the driver that the request status of the proposed functions (i.e., the RCC function and the blind spot monitoring function) be changed to enabled.

[0179] The change confirmation screen 78a includes an "Agree" button 90a and a "Deny" button 90b. If the driver selects the "Agree" button 90a, the driver assistance ECU 20 will switch the request status of the proposed function (in this example, the RCC function and the blind spot monitoring function) to the "On" state. In addition, in this case, the driver assistance ECU 20 will... Figure 18 The change notification screen 78b, which indicates that the proposed function has been changed to an enabled state, is displayed on the monitor 27 to inform the driver that the proposed function's request status has changed.

[0180] The change notification screen 78b includes a return button 83h. If the driver selects the return button 83h, or if a display time Td elapses after the change notification screen 78b is displayed without selecting the return button 83h, the driver assistance ECU 20 will display the immediate screen on the display 27.

[0181] On the other hand, if the driver selects the reject button 90b when the change confirmation screen 78a is displayed, the driver assistance ECU 20 will maintain the request status of the proposed function as disconnected. Alternatively, if neither the agree button 90a nor the reject button 90b is selected for a duration Td after the change confirmation screen 78a is displayed, the driver assistance ECU 20 will also maintain the request status of the proposed function as disconnected. In all other cases, the driver assistance ECU 20 will display the immediate screen on the display 27.

[0182] (Setting up a change confirmation process – specific tasks)

[0183] Next, refer to Figures 19-22 The specific procedures involved in confirming settings changes for the driver assistance ECU 20 are explained. At predetermined intervals, the CPU (hereinafter referred to as "CPU") of the driver assistance ECU 20 executes... Figure 19 The flowchart shows the "RCC Start Confirmation Processing Routine".

[0184] Therefore, if the timing is right, the CPU will... Figure 19 Step 1900 begins processing and proceeds to step 1905, determining whether the change notification screen 75b involved in the RCC confirmation process is not displayed on display 27. Figure 11 ) state.

[0185] (Scenario 1A)

[0186] Assuming that the RCC function request status is off at the current moment, the home screen 71 is displayed on the display 27, and the driver has not operated the CC switch 61 after the ignition is turned on.

[0187] Based on this assumption, since the change notification screen 75b is not displayed on the monitor 27, the CPU determines "yes" in step 1905 and proceeds to step 1910 to process the change confirmation screen 75a involved in whether it is an RCC confirmation process. Figure 10 The state that is not displayed on the monitor 27 is determined.

[0188] Based on the above assumptions, since the change confirmation screen 75a is not displayed, the CPU determines "yes" in step 1910 and proceeds to step 1915 to determine whether the request status of the RCC function is disconnected. Based on the above assumptions, since the request status of the RCC function is disconnected, the CPU determines "yes" in step 1915 and proceeds to step 1920 to determine whether the setting switch of CC switch 61 has been pressed during the period from the last execution of this routine to the current time.

[0189] Based on the above assumptions, since no operation was performed on CC switch 61 (i.e., since the setting switch of CC switch 61 was not pressed), the CPU determines "no" in step 1920 and directly proceeds to step 1995, ending the processing of this routine.

[0190] (Scenario 1B)

[0191] Then, it is assumed that this routine is being executed for the first time after the setting switch of CC switch 61 is pressed. In addition, it is assumed that the main switch of CC switch 61 has not been pressed yet.

[0192] In this case, the CPU determines "yes" in step 1920 and proceeds to step 1925 to determine whether the processing of step 1925 is being executed for the first time in the current process.

[0193] Based on the above assumptions, since the setting switch is pressed for the first time in the current process, the CPU determines "yes" in step 1925 and proceeds to step 1930, displaying the change confirmation screen 75a on the display 27. At this time, the CPU stores the screen that was immediately displayed on the display 27 before the change confirmation screen 75a (in this assumption, the home screen 71) as the preceding screen in RAM. Next, the CPU proceeds to step 1995.

[0194] (Scenario 1C)

[0195] Then, assume that no display time Td has elapsed after the change confirmation screen 75a is displayed, and that neither the agree button 87a nor the refuse button 87b on the change confirmation screen 75a is selected.

[0196] In this case, the CPU determines "No" in step 1910 and proceeds to step 1935 to determine whether the "Agree" button 87a was selected during the period from the last execution of this routine to the current time. Based on the above assumption, since the "Agree" button 87a was not selected, the CPU determines "No" in step 1935 and proceeds to step 1950 to determine whether the display end condition of the change confirmation screen 75a is met.

[0197] The condition for ending the display of the change confirmation screen 75a is that at least one of the following conditions (1a) and condition (1b) is met.

[0198] Condition (1a): The "Reject" button 87b was selected.

[0199] Condition (1b): Display time Td has elapsed since the change confirmation screen 75a was displayed.

[0200] Based on the above assumptions, since neither condition (1a) nor condition (1b) is met, the display end condition for the change confirmation screen 75a is not met. Therefore, the CPU determines "No" in step 1950 and proceeds directly to step 1995.

[0201] (Scenario 1D)

[0202] Then, assume that the "agree" button 87a on the change confirmation screen 75a was selected before the display time Td elapsed from the time the change confirmation screen 75a was displayed.

[0203] In this case, the CPU determines "yes" in step 1935 and proceeds to step 1940, switching the RCC function request status to the enabled state. Next, the CPU proceeds to step 1945, displaying the change notification screen 75b related to the RCC start confirmation processing on the display 27. Then, the CPU proceeds to step 1995.

[0204] (Scenario 1E)

[0205] Then, assume that no display time Td has elapsed since the change notification screen 75b was displayed, and the return button 83d of the change notification screen 75b has not been selected.

[0206] In this case, the CPU determines "No" in step 1905 and proceeds to step 1955 to determine whether the display end condition of the change notification screen 75b is met. The display end condition of the change notification screen 75b is a condition that is met when at least one of the following conditions (1c) and condition (1d) is met.

[0207] Condition (1c): The return button 83d was selected.

[0208] Condition (1d): Display time Td has elapsed since the change notification screen 75b was displayed.

[0209] Based on the above assumptions, since conditions (1c) and (1d) are both not met, the display end condition for the change notification screen 75b is not met. Therefore, the CPU determines "No" in step 1955 and directly proceeds to step 1995.

[0210] Then, if the return button 83d is selected (i.e., if condition (1c) is met before condition (1d) is met), or if display time Td has elapsed since the change notification screen 75b was displayed (i.e., condition (1d) is met), the CPU determines "yes" in step 1955 and proceeds to step 1960, displaying the immediate screen (home screen 71 in this assumption) on the display 27. Then, the CPU proceeds to step 1995.

[0211] (Scenario 1F)

[0212] Then, assume that the RCC function is disconnected and the main switch of CC switch 61 is pressed instead of the setting switch. In addition, assume that after the processing of step 1930 in the above (case 1B) was performed, the ignition disconnection operation was not performed.

[0213] In this case, the CPU determines "No" in step 1925 and proceeds directly to step 1995. That is, in this case, the RCC start confirmation process is not executed, and the request status of the RCC function remains disconnected.

[0214] (Scenario 1G)

[0215] Next, it is assumed that the display end condition of the change confirmation screen 75a is met when the change confirmation screen 75a is not displayed on the display 27 (that is, at least one of the above conditions (1a) and (1b) is met).

[0216] In this case, the CPU determines "yes" in step 1950 and proceeds to step 1960. That is, in this case, the request status of the RCC function is maintained in the off state, and the preceding screen is displayed on the display 27.

[0217] (Scenario 1H)

[0218] Next, we assume that the request status for the RCC function is enabled.

[0219] In this case, the CPU determines "no" in step 1915 and proceeds directly to step 1995.

[0220] If the RCC function is enabled when the request state of the RCC function is disabled (i.e., if the setting switch of CC switch 61 is pressed after the main switch of CC switch 61 is pressed), the request state of the RCC function will be switched to enabled by other routines (not shown) executed by the CPU.

[0221] Next, for Figure 20The "Work Stop Confirmation Processing Routine" is illustrated in the flowchart. The CPU executes this routine at predetermined intervals. Therefore, if the timing is appropriate, the CPU will... Figure 20 Step 2000 begins processing and proceeds to step 2005, where the change notification screen 76b is used to confirm whether the work is completed. Figure 13 The state that is not displayed on the monitor 27 is determined.

[0222] (Scenario 2A)

[0223] Assuming that the vehicle setting screen 72 is currently displayed on the monitor 27, and no disconnection operation of the work stop confirmation object function has been performed.

[0224] Based on this assumption, since the change notification screen 76b is not displayed on the monitor 27, the CPU determines "yes" in step 2005 and proceeds to step 2010, stopping the change confirmation screen 76a involved in the confirmation process for whether it is a work-related issue. Figure 12 The state that is not displayed on the monitor 27 is determined.

[0225] Based on the above assumptions, since the change confirmation screen 76a is not displayed, the CPU determines "yes" in step 2010 and proceeds to step 2015 to determine whether a disconnection operation for the work stop confirmation object function has been performed during the period from the last execution of this routine to the current time. Based on the above assumptions, since no disconnection operation for the work stop confirmation object function has been performed, the CPU determines "no" in step 2015 and directly proceeds to step 2095, ending the processing of this routine.

[0226] (Scenario 2B)

[0227] Then, assume that this routine is executed for the first time after a disconnection operation is performed on any of the functions in the work stop confirmation object function.

[0228] Based on this assumption, the CPU determines "yes" in step 2015 and proceeds to step 2020, displaying the change confirmation screen 76a on the display 27. At this time, the CPU stores the screen immediately preceding the display of the change confirmation screen 76a on the display 27 (in this assumption, the vehicle setting screen 72) as the preceding screen in RAM. Next, the CPU proceeds to step 2095.

[0229] (Scenario 2C)

[0230] Then, assume that no display time Td has elapsed after the change confirmation screen 76a is displayed, and that neither the agree button 88a nor the refuse button 88b on the change confirmation screen 76a is selected.

[0231] In this case, the CPU determines "No" in step 2010 and proceeds to step 2025 to determine whether the "Agree" button 88a was selected during the period from the last execution of this routine to the current time. Based on the above assumption, since the "Agree" button 88a was not selected, the CPU determines "No" in step 2025 and proceeds to step 2040 to determine whether the display end condition of the change confirmation screen 76a is met.

[0232] The condition for ending the display of the change confirmation screen 76a is that at least one of the following conditions (2a) and condition (2b) is met.

[0233] Condition (2a): The "Reject" button 88b was selected.

[0234] Condition (2b): Display time Td has elapsed since the change confirmation screen 76a was displayed.

[0235] Based on the above assumptions, since neither condition (2a) nor condition (2b) is met, the display end condition for the change confirmation screen 76a is not met. Therefore, the CPU determines "No" in step 2040 and proceeds directly to step 2095.

[0236] (Scenario 2D)

[0237] Then, assume that the "agree" button 88a on the change confirmation screen 76a was selected before the display time Td elapsed from the time the change confirmation screen 76a was displayed.

[0238] In this case, the CPU determines "yes" in step 2025 and proceeds to step 2030, switching the request status of the work stop confirmation object function that has undergone a disconnection operation to a disconnected state. Next, the CPU proceeds to step 2035, displaying the change notification screen 76b related to the work stop confirmation process on the display 27. Then, the CPU proceeds to step 2095.

[0239] (Scenario 2E)

[0240] Then, assume that no display time Td has elapsed since the change notification screen 76b was displayed, and the return button 83e of the change notification screen 76b has not been selected.

[0241] In this case, the CPU determines "No" in step 2005 and proceeds to step 2045 to determine whether the display end condition of the change notification screen 76b is met. The display end condition of the change notification screen 76b is met when at least one of the following conditions (2c) and condition (2d) is met.

[0242] Condition (2c): The return button 83e was selected.

[0243] Condition (2d): Display time Td elapsed after the change notification screen 76b was displayed.

[0244] Based on the above assumptions, since conditions (2c) and (2d) are both not met, the display end condition for the change notification screen 76b is not met. Therefore, the CPU determines "No" in step 2045 and directly proceeds to step 2095.

[0245] Then, if the return button 83e is selected (i.e., if condition (2c) is met before condition (2d) is met), or if display time Td has elapsed after the display of the change notification screen 76b (i.e., if condition (2d) is met), the CPU determines "yes" in step 2045 and proceeds to step 2050, displaying the preceding screen (in this assumption, the vehicle setting screen 72) on the display 27. Then, the CPU proceeds to step 2095.

[0246] (Scenario 2F)

[0247] Next, it is assumed that the display end condition of the change confirmation screen 76a is met when the change confirmation screen 76a is displayed on the display 27 (that is, at least one of the above conditions (2a) and (2b) is met).

[0248] In this case, the CPU determines "yes" in step 2040 and proceeds to step 2050. That is, in this case, the request status of the work stop confirmation object function that was disconnected in this assumption is maintained in the open state, and the preceding screen is displayed on the display 27.

[0249] Next, for Figure 21 The flowchart illustrates the "Prerequisite Function Start Processing Routine." The CPU executes this routine at regular intervals. Therefore, if the timing is appropriate, the CPU will start from... Figure 21 Step 2100 begins processing and proceeds to step 2105, where the first change notification screen 77b is involved in processing whether it is a prerequisite function. Figure 15 ) and the second change notification screen 77c ( Figure 16 None of them were displayed on the monitor 27 for status determination.

[0250] (Scenario 3A)

[0251] Assuming that at the current moment, the homepage screen 71 is displayed on the monitor 27, the request status of both the LTA function and the RCC function is disconnected, and the activation operation of both the LTA function and the RCC function has not been performed.

[0252] Based on this assumption, since neither the first change notification screen 77b nor the second change notification screen 77c is displayed on the display 27, the CPU determines "yes" in step 2105 and proceeds to step 2110 to process the change confirmation screen 77a related to whether it is a prerequisite function. Figure 14 The state that is not displayed on the monitor 27 is determined.

[0253] Based on the above assumptions, since the change confirmation screen 77a is not displayed, the CPU determines "yes" in step 2110 and proceeds to step 2115 to determine whether an LTA function activation operation has been performed since the last execution of this routine until the current time. Based on the above assumptions, since no LTA function activation operation has been performed, the CPU determines "no" in step 2115 and directly proceeds to step 2195, ending the processing of this routine.

[0254] (Scenario 3B)

[0255] Then, assume that this routine is being executed for the first time after the LTA function is enabled.

[0256] Based on this assumption, the CPU determines "yes" in step 2115 and proceeds to step 2120 to determine whether the RCC function request status is disconnected. Based on the above assumption, since the RCC function request status is disconnected, the CPU determines "yes" in step 2120 and proceeds to step 2125, displaying the change confirmation screen 77a on the display 27. At this time, the CPU stores the screen immediately preceding the display of the change confirmation screen 77a on the display 27 (in this assumption, the home screen 71) as the preceding screen in RAM. Next, the CPU proceeds to step 2195.

[0257] (Scenario 3C)

[0258] Then, assume that no display time Td has elapsed after the change confirmation screen 77a is displayed, and that neither the agree button 89a nor the refuse button 89b on the change confirmation screen 77a is selected.

[0259] In this case, the CPU determines "No" in step 2110 and proceeds to step 2130 to determine whether the "Agree" button 89a has been selected during the period from the last execution of this routine to the current time. Based on the above assumption, since the "Agree" button 89a has not been selected, the CPU determines "No" in step 2130 and proceeds to step 2150 to determine whether the display end condition of the change confirmation screen 77a is met.

[0260] The condition for ending the display of the change confirmation screen 77a is that at least one of the following conditions (3a) and condition (3b) is met.

[0261] Condition (3a): The "Reject" button was selected (89b).

[0262] Condition (3b): Display time Td has elapsed after the change confirmation screen 77a is displayed.

[0263] Based on the above assumptions, since conditions (3a) and (3b) are both false, the display end condition for the change confirmation screen 75a is not met. Therefore, the CPU determines "no" in step 2150 and proceeds directly to step 2195.

[0264] (Scenario 3D)

[0265] Then, assume that the "agree" button 89a on the change confirmation screen 77a was selected after the display time Td elapsed following the display of the change confirmation screen 77a.

[0266] In this case, the CPU determines "yes" in step 2130 and proceeds to step 2135, displaying the first change notification screen 77b related to the commencement of prerequisite function processing on the display 27. Next, the CPU proceeds to step 2140, switching the request status of the RCC function to the enabled state. Furthermore, the CPU proceeds to step 2145, switching the request status of the LTA function to the enabled state. Finally, the CPU proceeds to step 2195.

[0267] (Scenario 3E)

[0268] Then, assume that no display time Td has elapsed after the first change notification screen 77b is displayed, and the return button 83f of the first change notification screen 77b is not selected.

[0269] In this case, the CPU determines "No" in step 2105 and proceeds to step 2160 to determine whether the display end conditions of the first change notification screen 77b and the second change notification screen 77c are met. The display end conditions of the first change notification screen 77b and the second change notification screen 77c are met when at least one of the following conditions (3c) and conditions (3d) is met.

[0270] Condition (3c): The return button 83f or the return button 83g was selected.

[0271] Condition (3d): Display time Td has elapsed after the first change notification screen 77b or the second change notification screen 77c is displayed.

[0272] Based on the above assumptions, since conditions (3c) and (3d) are both false, the termination condition is not met. Therefore, the CPU determines "No" in step 2160 and proceeds directly to step 2195.

[0273] Then, if the return button 83f is selected (i.e., if condition (3c) is met before condition (3d) is met, or if display time Td has elapsed after the first change notification screen 77b is displayed (i.e., if condition (3d) is met), the CPU determines "yes" in step 2160 and proceeds to step 2165, displaying the immediate screen (home screen 71 in this assumption) on the display 27. Then, the CPU proceeds to step 2195.

[0274] (Scenario 3F)

[0275] Next, it is assumed that the display end condition of the change confirmation screen 77a is met when the change confirmation screen 77a is displayed on the display 27 (that is, at least one of the above conditions (3a) and (3b) is met).

[0276] In this case, the CPU determines "yes" in step 2150 and proceeds to step 2155, displaying the second change notification screen 77c related to the commencement of prerequisite function processing on the display 27. Next, the CPU proceeds to step 2145, and then to step 2195. In this case, the request status of the RCC function is maintained in the off state and does not switch to the on state, while the request status of the LTA function switches to the on state.

[0277] (Scenario 3G)

[0278] Next, assuming that at the current moment, the homepage screen 71 is displayed on the monitor 27, the request status of the RCC function is enabled, and the LTA function has been enabled.

[0279] Based on this assumption, the CPU determines "no" in step 2120 and proceeds to step 2145.

[0280] Next, for Figure 22 The flowchart illustrates the "Work Start Proposal Processing Routine." The CPU executes this routine at regular intervals. Therefore, if the timing is appropriate, the CPU will... Figure 22 Step 2200 begins processing, proceeding to step 2205, where a change notification screen 78b is displayed to indicate whether a work has been initiated. Figure 18 The state that is not displayed on the monitor 27 is determined.

[0281] (Scenario 4A)

[0282] Assuming that at the current moment, the vehicle setting screen 72 is displayed on the monitor 27, the request status of the RCC function and the blind spot monitoring function are both in the off state, the request status of the LTA function is in the on state, and the driving state of the vehicle 10 is not a specific driving state.

[0283] Based on this assumption, since the change notification screen 78b is not displayed on the monitor 27, the CPU determines "yes" in step 2205 and proceeds to step 2210, proposing to process the change confirmation screen 78a involved in whether or not the work has begun. Figure 17 The state not displayed on monitor 27 is determined.

[0284] Based on the above assumptions, since the change confirmation screen 78a is not displayed, the CPU determines "yes" in step 2210 and proceeds to step 2215 to determine whether the driving state of vehicle 10 is a specific driving state. Based on the above assumptions, since the driving state of vehicle 10 is not a specific driving state, the CPU determines "no" in step 2215 and directly proceeds to step 2295, ending the processing of this routine.

[0285] (Scenario 4B)

[0286] Then, assume that this routine is executed for the first time after the driving state of vehicle 10 becomes a specific driving state.

[0287] In this case, the CPU determines "yes" in step 2215 and proceeds to step 2220 to determine whether a proposed object function exists. Based on the above assumptions, at the current moment, the RCC function and the blind spot monitoring function meet the requirements for a proposed object function.

[0288] Therefore, the CPU determines "yes" in step 2220 and proceeds to step 2225, displaying the change confirmation screen 78a involved in the work start proposal processing on the display 27. At this time, the CPU stores the screen that was immediately displayed on the display 27 before the change confirmation screen 78a (in this assumption, the vehicle setting screen 72) as the preceding screen in RAM. Next, the CPU proceeds to step 2295.

[0289] (Scenario 4C)

[0290] Then, assume that no display time Td has elapsed after the change confirmation screen 78a is displayed, and that neither the agree button 90a nor the refuse button 90b on the change confirmation screen 78a is selected.

[0291] In this case, the CPU determines "No" in step 2210 and proceeds to step 2230 to determine whether the "Agree" button 90a was selected during the period from the last execution of this routine to the current time. Based on the above assumption, since the "Agree" button 90a was not selected, the CPU determines "No" in step 2230 and proceeds to step 2245 to determine whether the display end condition of the change confirmation screen 78a is met.

[0292] The condition for ending the display of the change confirmation screen 78a is that at least one of the following conditions (4a) and condition (4b) is met.

[0293] Condition (4a): The "Reject" button 90b was selected.

[0294] Condition (4b): Display time Td has elapsed after the change confirmation screen 78a is displayed.

[0295] Based on the above assumptions, since conditions (4a) and (4b) are both false, the display end condition for the change confirmation screen 78a is not met. Therefore, the CPU determines "no" in step 2245 and proceeds directly to step 2295.

[0296] (Scenario 4D)

[0297] Then, assume that the "agree" button 90a on the change confirmation screen 78a was selected after the display time Td elapsed following the display of the change confirmation screen 78a.

[0298] In this case, the CPU determines "yes" in step 2230 and proceeds to step 2235, switching the request status of the proposed object function (in this assumption, the request status of the RCC function and the blind spot monitoring function) to the enabled state.

[0299] Next, the CPU proceeds to step 2240, displaying the change notification screen 78b related to the work start proposal processing on the monitor 27. Then, the CPU proceeds to step 2295.

[0300] (Scenario 4E)

[0301] Then, assume that no display time Td has elapsed after the change notification screen 78b is displayed, and the return button 83h of the change notification screen 78b is not selected.

[0302] In this case, the CPU determines "No" in step 2205 and proceeds to step 2250 to determine whether the display end condition of the change notification screen 78b is met. The display end condition of the change notification screen 78b is met when at least one of the following conditions (4c) and condition (4d) is met.

[0303] Condition (4c): The return button 83h was selected.

[0304] Condition (4d): Display time Td elapsed after the change notification screen 78b was displayed.

[0305] Based on the above assumptions, since conditions (4c) and (4d) are both not met, the display end condition for the change notification screen 78b is not met. Therefore, the CPU determines "No" in step 2250 and directly proceeds to step 2295.

[0306] Then, if the return button 83h is selected (i.e., if condition (4c) is met before condition (4d) is met), or if display time Td has elapsed after displaying the change notification screen 78b (i.e., if condition (4d) is met), the CPU determines "yes" in step 2250 and proceeds to step 2255, displaying the preceding screen (in this assumption, the vehicle setting screen 72) on the display 27. Then, the CPU proceeds to step 2295.

[0307] (Scenario 4F)

[0308] Next, it is assumed that the display end condition of the change confirmation screen 78a is met when the change confirmation screen 78a is displayed on the display 27 (that is, at least one of the above conditions (4a) and (4b) is met).

[0309] In this case, the CPU determines "yes" in step 2245 and proceeds to step 2255. That is, in this case, the request status of the proposed object function is maintained in the disconnected state, and the preceding screen is displayed on the display 27.

[0310] (Scenario 4G)

[0311] Next, it is assumed that there is no proposed object function when the driving state of vehicle 10 becomes a specific driving state.

[0312] In this case, the CPU determines "no" in step 2220 and proceeds directly to step 2295.

[0313] (Modifications of the implementation method)

[0314] Next, a variation of this embodiment will be described. This variation differs from the embodiment described above only in that the main switch of CC switch 61 is omitted, and pressing the setting switch of CC switch 61 activates the RCC function.

[0315] When the RCC function request state is off, if the setting switch of CC switch 61 is pressed, the driving assistance ECU 20 will display the change confirmation screen 75a (refer to) related to the RCC start confirmation process. Figure 10 The information is displayed on display 27. That is, the driver assistance ECU 20 begins the RCC start confirmation process involved in this variation. In this variation, the change confirmation screen 75a includes an explanation indicating that the RCC function has been changed to the enabled state by selecting the consent button 87a.

[0316] If the "Agree" button 87a is selected after the change confirmation screen 75a is displayed and before the display time Td has elapsed, the driver assistance ECU 20 will switch the RCC function request status to the "On" state. In addition, the driver assistance ECU 20 will display the change notification screen 75b (see [reference]) related to the RCC start confirmation processing. Figure 11 (Displayed on monitor 27.)

[0317] As explained above, the driver assistance ECU 20 can prevent the request status of the driver assistance function from being changed due to driver error or misunderstanding by performing a setting change confirmation process. More specifically, according to the RCC start confirmation process, even if the driver performs a similar operation due to error or misunderstanding (in this embodiment, pressing the setting switch of CC switch 61 instead of pressing the main switch of CC switch 61), the request status of the RCC function can be easily switched to the enabled state.

[0318] In addition, the work stop confirmation process can prevent the request status of the work stop confirmation function from being mistakenly changed to the off state. Based on the prerequisite function start process, even if the driver forgets to set the request status of the prerequisite function (i.e., the RCC function relative to the LTA function) to the on state, or if the driver is unaware of the existence of the prerequisite function, the request status of the prerequisite function can be easily switched to the on state.

[0319] Furthermore, based on the start of the work proposal process, even if the driver forgets to set the request status of the proposed object function (specifically, the driving status-related function) to the enabled state, or if they are unaware of the usefulness of the proposed object function, the request status of the proposed object function can be easily switched to the enabled state.

[0320] Furthermore, since the RCC start confirmation process is executed only once within the same process, it avoids the need to modify the confirmation screen during the execution of the RCC start confirmation process (i.e., Figure 10 The driver who understands the operation of activating the RCC function repeatedly displays the change confirmation screen 75a). That is, it can avoid the situation where the driver repeatedly performs the RCC start confirmation process when the driver accidentally presses the setting switch instead of pressing the main switch 61 when the RCC function is off, which will cause the driver annoyance.

[0321] The embodiments of the operation assistance device according to the present invention have been described above. However, the present invention is not limited to the above embodiments, and various modifications can be made without departing from the purpose of the present invention. For example, the driving assistance ECU 20 performs RCC start confirmation processing, work stop confirmation processing, prerequisite function start processing, and work start proposal processing as setting change confirmation processing. However, the driving assistance ECU 20 may also be configured to not perform some of these setting change confirmation processes.

[0322] In addition, in this embodiment, if the setting switch of CC switch 61 is pressed when the request state of RCC function is off (without pressing the main switch of CC switch 61), the driving assistance ECU 20 performs RCC start confirmation processing. That is, if a pre-determined operation similar to the RCC function activation operation is performed, the driving assistance ECU 20 confirms with the driver whether to switch the RCC function to the on state. However, the driving assistance ECU 20 can also perform the same confirmation processing for driving assistance functions different from RCC function. For example, if the LTA function activation operation is to press the "basic switch" (not shown) provided on the steering wheel 55 and then press the LTA switch 64 before a predetermined time has elapsed, it can be configured such that if the LTA switch 64 is pressed while the LTA function is off without pressing the basic switch, the driving assistance ECU 20 will confirm with the driver whether to switch the RCC function to the on state. Figure 10 A similar screen to the change confirmation screen 75a is displayed on the display 27 to confirm with the driver whether the LTA function has been switched to the on state.

[0323] In addition, in this embodiment, the driving assistance ECU 20 performs RCC start confirmation processing only once per trip. However, the driving assistance ECU 20 may also perform RCC start confirmation processing multiple times per trip. Alternatively, the driving assistance ECU 20 may be configured to perform setting change confirmation processing other than performing RCC start confirmation processing only once per trip.

[0324] In addition to the above, in this embodiment, the confirmation information is provided to the driver via a change confirmation screen displayed on the display 27, but it can also be provided to the driver by other methods. For example, the confirmation information can be provided to the driver by sound reproduced by the speaker 28. Furthermore, in this embodiment, the consent operation is the operation of the operation switch 60, but it can also be a different operation. For example, the consent operation can also be achieved by the driver speaking "I agree to this content" into a microphone connected to the driver assistance ECU 20.

[0325] In addition, in this embodiment, if the "agree" button 89a is not selected when the prerequisite function begins processing (specifically, if the display end condition of the change confirmation screen 77a is met), the driver assistance ECU 20 switches the request state of the LTA function to the "on" state. However, when the display end condition of the change confirmation screen 77a is met, the driver assistance ECU 20 may not switch the request state of the LTA function to the "on" state. That is, in this case, the request states of both the LTA function and the RCC function can be kept in the "off" state.

[0326] In addition, in this embodiment, the specific driving state involved in the work commencement proposal processing is the state in which vehicle 10 is traveling on a highway or a dedicated vehicle lane. Furthermore, the driving state-related function involved in the work commencement proposal processing is the driver assistance function circled in column Cm2. However, the specific driving state and the driving state-related function may differ from these. For example, if the current location Pn is located on "facilities" in map database 26, the driver assistance ECU 20 may determine that the driving state of vehicle 10 is a specific driving state. In this case, the driving state-related function could be... Figure 5 The table shown has circles marked in column Cm3 for the driver assistance functions (i.e., gap sonar function, rear cross traffic warning function, and parking assist braking function).

[0327] In addition, in this embodiment, if the request status of the RCC function is off when the driver performs the LTA function activation operation, the driver assistance ECU 20 executes the prerequisite function start processing. However, the combination of driver assistance functions that triggers the execution of the prerequisite function start processing (in this embodiment, the combination of the LTA function and the RCC function as a prerequisite function) can be different. For example, the combination of driver assistance functions that triggers the execution of the prerequisite function start processing can also be the combination of the RCC function and the "vehicle-to-vehicle communication function" as a prerequisite function. That is, if the request status of the vehicle-to-vehicle communication function is off when the driver performs the RCC function activation operation, the driver assistance ECU 20 performs setting change confirmation processing (prerequisite function start processing) by treating the vehicle-to-vehicle communication function as the confirmation target function.

[0328] Vehicle-to-vehicle communication is a well-known function that involves wireless communication and the transmission and reception of information related to driving status (driving information) from other vehicles. In this case, if both the RCC function and the vehicle-to-vehicle communication function request status are enabled and the driving status is received from the vehicle being followed via vehicle-to-vehicle communication, the driver assistance ECU 20 determines the target acceleration Astg based on the driving information of the vehicle being followed, thereby quickly following the vehicle according to changes in its speed.

Claims

1. A change operation auxiliary device, comprising: The driver assistance control unit is configured to store setting states related to the vehicle's driver assistance functions, including request states that are either in a disconnected state or an on state, and is capable of providing the driver assistance functions based on the setting states. The operation unit is configured to be used in an operation performed by the driver of the vehicle to change the set state, including a predetermined request state change operation for changing the requested state, and is capable of outputting information related to the operation performed by the driver to the driving assistance control unit; and The information providing unit is configured to be controlled by the driving assistance control unit and to provide information related to the set state to the driver. in, The driving assistance control unit is configured as follows: When specific conditions are met, a configuration change confirmation process will be executed. This setting change confirmation process involves controlling the information providing unit to provide the driver with confirmation information regarding whether to change the request status of the confirmed function in the driving assistance function, and then changing the request status of the confirmed function if the driver performs a prescribed consent operation using the operation unit based on the confirmation information. The driving assistance control unit is configured as follows: When a condition that would have been met when a similar, predetermined operation was performed on the operating unit is met, the specific condition is determined to have been met. The similar operation is different from the request status change operation used to change the request status of the confirmed object function to the enabled state, and there is a possibility that the driver may perform the operation in order to change the request status to the enabled state.

2. A change operation auxiliary device, comprising: The driver assistance control unit is configured to store setting states related to the vehicle's driver assistance functions, including request states that are either in a disconnected state or an on state, and is capable of providing the driver assistance functions based on the setting states. The operation unit is configured to be used in an operation performed by the driver of the vehicle to change the set state, including a predetermined request state change operation for changing the requested state, and is capable of outputting information related to the operation performed by the driver to the driving assistance control unit; and The information providing unit is configured to be controlled by the driving assistance control unit and to provide information related to the set state to the driver. in, The driving assistance control unit is configured as follows: When specific conditions are met, a configuration change confirmation process will be executed. This setting change confirmation process involves controlling the information providing unit to provide the driver with confirmation information regarding whether to change the request status of the confirmed function in the driving assistance function, and then changing the request status of the confirmed function if the driver performs a prescribed consent operation using the operation unit based on the confirmation information. The driving assistance control unit is configured as follows: When a request status change operation is performed to change the request status of a driving assistance function that is pre-associated with the confirmation object function but is different from the confirmation object function to an "on" state, and the condition that the request status of the confirmation object function is "off" is met, the specific condition is determined to be met.

3. A change operation auxiliary device, comprising: The driver assistance control unit is configured to store setting states related to the vehicle's driver assistance functions, including request states that are either in a disconnected state or an on state, and is capable of providing the driver assistance functions based on the setting states. The operation unit is configured to be used in an operation performed by the driver of the vehicle to change the set state, including a predetermined request state change operation for changing the requested state, and is capable of outputting information related to the operation performed by the driver to the driving assistance control unit; and The information providing unit is configured to be controlled by the driving assistance control unit and to provide information related to the set state to the driver. in, The driving assistance control unit is configured as follows: When specific conditions are met, a configuration change confirmation process will be executed. This setting change confirmation process involves controlling the information providing unit to provide the driver with confirmation information regarding whether to change the request status of the confirmed function in the driving assistance function, and then changing the request status of the confirmed function if the driver performs a prescribed consent operation using the operation unit based on the confirmation information. The driving assistance control unit is configured as follows: If the setting change confirmation process is performed after the vehicle's ignition is turned on, the setting change confirmation process will not be performed again even if the specific conditions are met before the vehicle's ignition is turned off.

Images