Vehicle traveling control device

Abstract

A control device detects a first vehicle traveling in front of an own vehicle using a front looking radar device, and detects a second vehicle which is predicted to cut in between the own vehicle and the first vehicle using the front looking radar device and/or front-side looking radar devices. The control device calculates a first target acceleration required for the own vehicle to maintain an inter-vehicle distance between the own vehicle and the first vehicle at a first set inter-vehicle distance; and calculates a second target acceleration required for the own vehicle to maintain an inter-vehicle distance between the own vehicle and the second vehicle at a second set inter-vehicle distance. The control device selects either the first target acceleration or the second target acceleration and controls the own vehicle in such a manner that an actual acceleration of the own vehicle becomes closer to the mediated target acceleration.

Claims

1. A vehicle travelling control device comprising: detecting means for detecting an objective-forward-vehicle traveling in front of an own vehicle and a vehicle which is predicted to cut in between said own vehicle and said objective-forward-vehicle; first calculation means for calculating a first target acceleration for the own vehicle to maintain an inter-vehicle distance between said own vehicle and said objective-forward-vehicle at a first set inter-vehicle distance; second calculation means for calculating a second target acceleration required for said own vehicle to maintain an inter-vehicle distance between said own vehicle and said predicted cut-in vehicle at a second set inter-vehicle distance; mediation means for selecting, as a mediated target acceleration, either said first target acceleration or said second target acceleration, whichever is smaller; and travel control means for controlling a driving force and a brake force of said own vehicle in such a manner that an actual acceleration of said own vehicle becomes closer to said mediated target acceleration, wherein: said detecting means includes a front looking radar device having a front looking detection area, the front looking detection area having a center axis extending in a straight forward direction of said own vehicle, the front looking radar detects a target object to obtain first target object information concerning said target object, and a front-side looking radar device having a front-side detection area, the front-side detection area having a center axis extending in a diagonally forward direction of said own vehicle, the front-side looking radar detects said target object to obtain second target object information concerning said target object; said vehicle travelling control device further comprises predicted cut-in vehicle detecting means for integrating said first target object information and said second target object information to obtain an integrated target object information, and detecting said predicted cut-in vehicle based on said integrated target object information, when said front looking radar device and said front-side looking radar device detect an identical target object, and detecting said predicted cut-in vehicle based on said second target object information but not based on said first target object information, when said front-side looking radar device detects said target object, but said front looking radar device does not detect said target object and said second calculation means calculates .[.said.]. .Iadd.second .Iaddend.first target acceleration in such a manner that said .[.said.]. .Iadd.second .Iaddend.target acceleration is allowed to be a negative acceleration achieved when a brake device of said own vehicle is operated, in a case where said predicted cut-in vehicle is detected based on said integrated target object information, and calculates said .[.said.]. .Iadd.second .Iaddend.target acceleration while providing a limitation on said .[.said.]. .Iadd.second .Iaddend.target acceleration in such a manner that said .[.said.]. .Iadd.second .Iaddend.target acceleration does not become smaller than a negative acceleration achieved when a throttle valve opening of an internal combustion engine serving as a driving force of said own vehicle is set at a minimum value while said brake device of said own vehicle is not operated, in a case where said predicted cut-in vehicle is detected based on said second target object information but not based on said first target object information.

2. A vehicle travelling control device comprising: a radar system that detects an objective-forward-vehicle traveling in front of an own vehicle and a vehicle which is predicted to cut in between said own vehicle and said objective-forward-vehicle; an electronic control unit .Iadd.implemented by at least one processor programmed and .Iaddend.configured to calculate a first target acceleration for the own vehicle to maintain an inter-vehicle distance between said own vehicle and said objective-forward-vehicle at a first set inter-vehicle distance, calculate a second target acceleration required for said own vehicle to maintain an inter-vehicle distance between said own vehicle and said predicted cut-in vehicle at a second set inter-vehicle distance, and select, as a mediated target acceleration, either said first target acceleration or said second target acceleration, whichever is smaller; an engine electronic control unit; and a brake electronic control unit; wherein the engine electronic control unit and the brake electronic control unit control a driving force and a brake force, respectively, of said own vehicle in such a manner that an actual acceleration of said own vehicle becomes closer to said mediated target acceleration, wherein said radar system includes a front looking radar device having a front looking detection area, the front looking detection area having a center axis extending in a straight forward direction of said own vehicle, the front looking radar detects a target object to obtain first target object information concerning said target object, and a front-side looking radar device having a front-side detection area, the front-side detection area having a center axis extending in a diagonally forward direction of said own vehicle, the front-side looking radar detects said target object to obtain second target object information concerning said target object, and wherein said electronic control unit is further configured to integrate said first target object information and said second target object information to obtain an integrated target object information, and detect said predicted cut-in vehicle based on said integrated target object information, when said front looking radar device and said front-side looking radar device detect an identical target object, detect said predicted cut-in vehicle based on said second target object information but not based on said first target object information, when said front-side looking radar device detects said target object, but said front looking radar device does not detect said target object, calculate said .[.first.]. .Iadd.second .Iaddend.target acceleration in such a manner that said .[.first.]. .Iadd.second .Iaddend.target acceleration is allowed to be a negative acceleration achieved when a brake device of said own vehicle is operated, in a case where said predicted cut-in vehicle is detected based on said integrated target object information, and calculate said .[.first.]. .Iadd.second .Iaddend.target acceleration while providing a limitation on said .[.first.]. .Iadd.second .Iaddend.target acceleration in such a manner that said .[.first.]. .Iadd.second .Iaddend.target acceleration does not become smaller than a negative acceleration achieved when a throttle valve opening of an internal combustion engine serving as a driving force of said own vehicle is set at a minimum value while said brake device of said own vehicle is not operated, in a case where said predicted cut-in vehicle is detected based on said second target object information but not based on said first target object information.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 is a schematic diagram of a vehicle travelling control device according to a first embodiment of the present disclosure.

(2) FIG. 2 is a configuration diagram of the vehicle travelling control device shown in FIG. 1.

(3) FIG. 3 is a flowchart showing a routine executed by a CPU of the driving support ECU shown in FIG. 2.

(4) FIG. 4 is a flowchart showing a routine executed by the CPU of the driving support ECU shown in FIG. 2.

(5) FIG. 5 is a look-up table (map) which the CPU of the driving support ECU shown in FIG. 2 refers to in order to detect a predicted cut-in vehicle.

(6) FIG. 6 (A) is a view schematically showing a scene when the other vehicle changes lanes, and FIG. 6 (B) is a view schematically showing another scene when the other vehicle changes lanes.

(7) FIG. 7 is a flowchart showing a routine executed by the CPU of the driving support ECU shown in FIG. 2.

(8) FIG. 8 is a flowchart showing a routine executed by a CPU of a vehicle travelling control device according to a second embodiment of the present disclosure.

(9) FIG. 9 is a flowchart showing a routine executed by the CPU of the vehicle travelling control device according to the second embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS

(10) Each of vehicle travelling control devices according to the present disclosure will next be described with reference to the drawings. Firstly, main terms used in the present specification and the drawings are described. The own vehicle: One's own vehicle (subject vehicle that is focused on). The other vehicle: A vehicle other than the own vehicle. The proceeding vehicle: The other vehicle traveling immediately ahead of (in front of) the own vehicle. The objective-forward-vehicle: The proceeding/leading vehicle, which a sensor device (front looking radar device) mounted on the own vehicle detects (acquires), and which the own vehicle should follow up by controlling an acceleration of the own vehicle so as to keep an inter-vehicle distance between the own vehicle and the proceeding vehicle at a predetermined distance. The cut-in vehicle: The other vehicle which cuts in ahead of the own vehicle by changing lanes.

First Embodiment

Structure

(11) As shown in FIG. 1, a vehicle travelling control device (hereinafter, sometimes referred to as a “first device”) 10 according to a first embodiment of the present disclosure is mounted on (applied to) the own vehicle VA. The first vehicle 10 comprises a driving support (assist) ECU 20, an engine ECU 30, and a brake ECU 40. Those ECUs are capable of exchanging data (communicating with each other) through a communication/sensor CAN (Controller Area Network) 100. It should be noted that an “ECU” is an abbreviation of an electric control unit, and is an electronic control circuit having a microcomputer including a CPU, a ROM, a RAM, an interface, and the like, as a main part. The CPU achieves/realizes various functions described later by executing instructions (routines) stored in the memory (e.g., ROM).

(12) Further, the first device 10 comprises a front looking radar device 21, a front-side looking radar device 22R, and a front-side looking radar device 22L. Those radar devices can also exchange data with the driving support ECU 20 through the CAN 100.

(13) More specifically, as shown in FIG. 2, the driving support ECU 20 is connected with an ACC operation switch 23, and a vehicle speed sensor 24, in addition to the front looking radar device 21, the front-side looking radar device 22R, and the front-side looking radar device 22L.

(14) The front looking radar device 21 comprises a millimeter wave transmitter-receiver section, and a processing section. As shown in FIG. 1, the front looking radar device 21 is positioned at the front end of the own vehicle VA, and at the center portion of the own vehicle VA in a body width direction. The millimeter wave transmitter-receiver section transmits a millimeter wave which propagates with a center axis C1 extending in a straight forward direction of the own vehicle VA, and spreads with a predetermined angle θ1 in a left direction as well as with the predetermined angle θ1 in a right direction with respect to the center axis C1. The millimeter wave is reflected by a target object (e.g., proceeding vehicle). The millimeter wave transmitter-receiver section receives the reflected wave. It should be noted that, hereinafter, a vehicle going forward direction along the center axis C1 is defined as an “X-axis”, and a direction orthogonal to the center axis C1 is defined as a “Y-axis.” The X-coordinate is positive in the vehicle's forward direction, and is negative in the vehicle's backward direction. The Y-coordinate is positive in the vehicle's rightward direction, and is negative in the vehicle's leftward direction.

(15) The processing section of the front looking radar device 21 obtains, every elapse of a predetermined time, an inter-vehicle distance (longitudinal distance) Dfx(n), a relative speed Vfx(n), a lateral distance Dfy(n), a relative lateral speed Vfy(n), or the like, with respect to each detected target object (n), based on a phase difference between the transmitted millimeter wave and the received reflected wave, an attenuation level, a time period from the point in time at which the millimeter wave is transmitted to the point in time at which the reflected wave is received, or the like. The data (Dfx(n), Vfx(n), Dfy(n), Vfy(n), etc.) acquired by the front looking radar device 21 are also referred to as “front looking radar obtained information”, as a matter of convenience.

(16) The inter-vehicle distance (longitudinal distance) Dfx(n) is a distance along the center axis C1 between the own vehicle VA and the target object(n) (e.g., the proceeding vehicle).

(17) The relative speed Vfx(n) is a difference (=SPDs−SPDj) between a speed SPDs of the target object(n) (e.g., the proceeding vehicle) and a speed SPDj of the own vehicle VA. It should be noted that the speed SPDs of the target object(n) is a speed of the target object (n) in the direction of travel of the own vehicle VA.

(18) The lateral distance Dfy(n) is a distance along the direction orthogonal to the center axis C1 from the center axis C1 to a “center position of the target object (n) (e.g., a center position of a vehicle width of the proceeding vehicle).” The lateral distance Dfy(n) may also be referred to as a “lateral position.”

(19) The relative lateral speed Vfy(n) is a speed of the center position of the each target object (n) in the direction orthogonal to the center axis C1.

(20) As shown in FIG. 1, the front-side (left) looking radar device 22L is positioned at a left-and-front side of the vehicle body of the own vehicle VA. The front-side looking radar device 22L has a configuration similar to the configuration of the front looking radar device 21. The millimeter wave transmitter-receiver section of the front-side looking radar device 22L transmits a millimeter wave which propagates with a center axis CL extending in a front-left direction of the own vehicle VA, and spreads with a predetermined angle θ2 in a front direction as well as the predetermined angle θ2 in a rear direction with respect to the center axis CL. One of the border lines (CLx) defining the border of the spreading millimeter wave transmitted from the front-side looking radar device 22L is parallel with the center axis C1.

(21) The processing section of the front-side looking radar device 22L obtains, every elapse of a predetermined time, a longitudinal distance DLx, a relative speed VLx, a lateral distance DLy, a relative lateral speed VLy, or the like, with respect to each detected target object, based on a phase difference between the transmitted millimeter wave and the received reflected wave, an attenuation level, a time period from the point in time at which the millimeter wave is transmitted to the point in time at which the reflected wave is received, or the like. A vertical axis of coordinates of those data is the center axis CL, and a horizontal axis of the coordinates of those data is an axis extending in a direction orthogonal to the center axis CL. Those data (DLx, VLx, DLy, VLy, or the like) obtained by the front-side looking radar device 22L are also referred to as “front-left-side looking radar obtained information”, as a matter of convenience. It should be noted that an accuracy of the front-left-side looking radar obtained information is lower than an accuracy of the front looking radar obtained information.

(22) As shown in FIG. 1, the front-side (right) looking radar device 22R is positioned at a right-and-front side of the vehicle body of the own vehicle VA. The front-side looking radar device 22R has a configuration similar to the configuration of the front looking radar device 21 and the front-side looking radar device 22L. The millimeter wave transmitter-receiver section of the front-side looking radar device 22R transmits a millimeter wave which propagates with a center axis CR extending in a front-right direction of the own vehicle VA, and spreads with a predetermined angle θ2 in a front direction as well as the predetermined angle θ2 in a rear direction with respect to the center axis CL. One of the border lines (CRx) defining the border of the spreading millimeter wave transmitted from the front-side looking radar device 22R is parallel with the center axis C1.

(23) The processing section of the front-side looking radar device 22R obtains, every elapse of a predetermined time, a longitudinal distance DRx, a relative speed VRx, a lateral distance DRy, a relative lateral speed VRy, or the like, with respect to each detected target object, based on a phase difference between the transmitted millimeter wave and the received reflected wave, an attenuation level, a time period from the point in time at which the millimeter wave is transmitted to the point in time at which the reflected wave is received, or the like. A vertical axis of coordinates of those data is the center axis CR, and a horizontal axis of the coordinates of those data is an axis extending in a direction orthogonal to the center axis CR. Those data (DRx, VRx, DRy, VRy, or the like) obtained by the front-side looking radar device 22R are also referred to as “front-right-side looking radar obtained information”, as a matter of convenience. It should be noted that an accuracy of the front-right-side looking radar obtained information is the same as the accuracy of the front-left-side looking radar obtained information, and is lower than the accuracy of the front looking radar obtained information.

(24) As is clear from FIG. 1, the detection area of the front looking radar device 21 and the detection area of the front-side looking radar device 22L have a portion (overlap area AL) that overlaps with each other, and the detection area of the front looking radar device 21 and the detection area of the front-side looking radar device 22R have a portion (overlap area AR) that overlaps with each other. In other words, a target object within the overlap area AL is detected/captured by both of the front looking radar device 21 and the front-side looking radar device 22L, and a target object within the overlap area AR is detected/captured by both of the front looking radar device 21 and the front-side looking radar device 22R.

(25) Referring back to FIG. 2 again, the ACC operation switch 23 is a switch operated by a driver. The term “ACC” means an inter-vehicle distance control (Adaptive Cruise Control), and may also be simply referred to as a “trailing travel control.” When the driver performs a certain operation using the ACC operation switch 23, an ACC start request (including an ACC resume request) and an ACC termination request (cancel request) are generated according to the operation. Further, according to a certain operation using the ACC operation switch 23, a target inter-vehicle time Ttgt described later is set or changed.

(26) The vehicle speed sensor 24 detects a speed (own vehicle speed) Vj of the own vehicle VA, and generates a signal indicative of the own vehicle speed Vj.

(27) The engine ECU 30 is connected with a plurality of engine sensors 31 to receive detected signals from those sensors. The engine sensors 31 are sensors that detect various operation state parameters of an unillustrated own vehicle's “gasoline fuel injection type/spark ignition/internal combustion engine.” The engine sensors 31 include an acceleration pedal operation amount sensor, a throttle valve opening sensor, an engine rotational speed sensor, an intake air-flow sensor, or the like.

(28) Further, the engine ECU is connected with engine actuators 32 including a throttle valve actuator, fuel injectors, or the like. The engine ECU 30 drives the engine actuators 32 to change a torque generated by the internal combustion engine, and thereby, adjusting a driving force of the own vehicle so as to control an acceleration of the own vehicle VA. In addition, the engine ECU 30 performs a “fuel-cut operation” to stop a fuel injection, when the throttle valve opening degree detected by the throttle valve opening sensor is “0 (or the minimum value within a range that the throttle valve opening can become)” (namely, the throttle valve is fully-closed) and the engine rotational speed is higher than an engine rotational speed threshold.

(29) The brake ECU 40 is connected with a plurality of brake sensors 41 to receive detected signals from those sensors. The brake sensors 41 are sensors that detect various parameters used for controlling an unillustrated “brake device (hydraulic type friction brake device) of the own vehicle VA.” The brake sensors 41 include a brake pedal operation amount sensor, a wheel rotational speed sensor detecting a rotational speed of each wheel, or the like.

(30) Further, the brake ECU 40 is connected with brake actuators 42. The brake actuators 42 are actuators for controlling pressure of brake oil. The brake actuators 42 are positioned in an unillustrated hydraulic circuit between an unillustrated master cylinder for pressurizing the brake oil according to a brake pedal force and unillustrated friction brake devices including well-known wheel cylinders provided to wheels. The brake actuators 42 adjust the pressure of the brake oil supplied to the wheel cylinders. The brake ECU 40 drives the brake actuators 42 to generate a brake force (friction brake force) at each of the wheels, to thereby control/adjust the acceleration (negative acceleration, that is, deceleration) of the own vehicle VA.

(31) (Outline of Operation)

(32) The first device specifies a objective-forward-vehicle based on the target object information obtained by the front looking radar device 21, and calculates a target acceleration G1tgt for trailing travel, required to keep a first set inter-vehicle distance with respect to the objective-forward-vehicle.

(33) Further, when the front looking radar device 21 and the front-side looking radar device 22L or 22R detect the same (identical) target object, the first device integrates/merges the target object information detected by the front looking radar device 21 and the target object information detected by the front-side looking radar device 22L or 22R, and determines whether or not there is a predicted cut-in vehicle based on the integrated/merged target object information. Thereafter, when the first device determines that there is the predicted cut-in vehicle, it calculates a target acceleration G2tgt for cut-in vehicle, required to keep a second set inter-vehicle distance with respect to that predicted cut-in vehicle.

(34) Furthermore, when one of the front-side looking radar device 22L and the front-side looking radar device 22R detects the target object, but the front looking radar device 21 does not detect that target object, the first device determines whether or not there is a predicted cut-in vehicle based on the target object information detected by one of the front-side looking radar device 22L and the front-side looking radar device 22R. Thereafter, when the first device determines that there is the predicted cut-in vehicle, it calculates a target acceleration G3tgt for cut-in vehicle, required to keep a third set inter-vehicle distance with respect to that predicted cut-in vehicle.

(35) In addition, the first device selects a minimum (the smallest) target acceleration among the target acceleration G1tgt for trailing travel, the target acceleration G2tgt for cut-in vehicle, and the target acceleration G3tgt for cut-in vehicle (i.e., selects one of G1tgt, G2tgt, and G3tgt, whichever smallest), and sets the selected target acceleration, as a “final target acceleration (mediated/adjusted target acceleration) Gfin.” Thereafter, the first device controls (drives) the engine actuators 32 and the brake actuators 42 in such a manner that the actual acceleration of the own vehicle VA becomes equal to the mediated target acceleration Gfin. As a result, the actual acceleration of the own vehicle VA is made to become equal to the mediated target acceleration Gfin.

(36) (Specific Operation)

(37) The CPU of the driving support ECU 20 (hereinafter, a “CPU” indicates/means the CPU of the driving support ECU 20, unless otherwise noted) executes routines shown in the flowcharts illustrated in FIGS. 4-7, every elapse of a predetermined time, when the ACC start request is generated by the operation using the ACC operation switch 23 while/when the trailing inter-vehicle distance control is not being performed.

(38) 1. Calculation of the Target Acceleration for Trailing Travel

(39) Therefore, at an appropriate point in time, the CPU starts processing from step 300 shown in FIG. 3 to execute processes from step 310 to step 340 described below in this order, and then, proceeds to step 395 so as to end the present routine tentatively. The routine shown in FIG. 3 is a routine for calculating the target acceleration for trailing travel.

(40) Step 310: The CPU selects/specifies the objective-forward-vehicle based on the front looking radar obtained information. More specifically, the CPU applies the lateral distance Dfy(n) and the inter-vehicle distance Dfx(n) to a map (look-up table) shown in a block of step 310 so as to select/specify, as the objective-forward-vehicle (a), the other vehicle (n) existing in an objective-forward-vehicle area defined by the map. It should be noted that, if there are a plurality of the other vehicles in the objective-forward-vehicle area, the CPU specifies one of the other vehicles, that has the shortest inter-vehicle distance Dfx(n), as the objective-forward-vehicle. Further, if there is no objective-forward-vehicle, the CPU controls the acceleration of the own vehicle VA in such a manner that the speed of the own vehicle VA becomes equal to a target speed depending on (according to) the target inter-vehicle time Ttgt. This point does not directly relate to the present disclosure, and thus, is not described in detail.

(41) Step 320; The CPU calculates the target inter-vehicle distance Dtgt by multiplying the target inter-vehicle time Ttgt by the speed Vj of the own vehicle. The target inter-vehicle time Ttgt is separately set based on the operation of the ACC operation switch 23, however, it may be constant. It should be noted that the target inter-vehicle distance Dtgt obtained at step 320 is also referred to as a “first set inter-vehicle distance.”

(42) Step 330; The CPU calculates an inter-vehicle deviation (difference) ΔD1 by subtracting the target inter-vehicle distance Dtgt from the inter-vehicle distance Dfx(a) of the objective-forward-vehicle (a) selected/specified at step 310.

(43) Step 340; The CPU calculates the target acceleration G1tgt for trailing travel using either one of a formula (1) described below and a formula (2) described below. The target acceleration G1tgt for trailing travel is also referred to as a “first target acceleration”, as a matter of convenience.

(44) In the formulas (1) and (2), the Vfx(a) is the relative speed of the objective-forward-vehicle (a) selected/specified at step 310, and K1 and K2 are predetermined positive gains (coefficients). The CPU uses the formula (1) below when a value (K1.Math.ΔD1+K2.Math.Vfx(a)) is positive. Ka1 is a positive gain (coefficient) for acceleration, and set to a value equal to or smaller than “1.”. The CPU uses the formula (2) below when a value (K1.Math.ΔD1+K2.Math.Vfx(a)) is negative. Kd1 is a gain (coefficient) for deceleration, and set to “1” in the present example.
G1tgt(for acceleration)=Ka1.Math.(K1.Math.ΔD1+K2.Math.Vfx(a))  (1)
G1tgt(for deceleration)=Kd1.Math.(K1.Math.ΔD1+K2.Math.Vfx(a))  (2)

(45) The target acceleration G1tgt for deceleration calculated based on the formula (2) above is calculated in such a manner that the target acceleration G1tgt is allowed to be an acceleration (negative acceleration) realized/achieved when the brake device of the own vehicle VA is operated (in other words, the target acceleration G1tgt may be a value obtained under a condition that it is allowed to be a negative acceleration realized/achieved when the brake device is operated). In the above manner, the target acceleration G1tgt for trailing travel based solely/only on the front looking radar obtained information is acquired.

(46) 2. Calculation of the Target Acceleration for Cut-in Vehicle

(47) Further, at an appropriate point in time, the CPU starts processing from step 400 in a “routine for calculation of the target acceleration for cut-in vehicle” shown in FIG. 4 to proceed to step 405. At step 405, the CPU transforms coordinates concerning the position of the target object and the relative speed, obtained by the front-side looking radar device 22L and the front-side looking radar device 22R (that is, the front-left-side looking radar obtained information, and the front-right-side looking radar obtained information) to the “X-Y coordinates of the front looking radar device 21.” Consequently, the “coordinate transformed front-side looking radar information FSXn”, including an inter-vehicle distance Dsx, a relative speed Vsx, a lateral distance Dsy, and a relative lateral speed Vsy, is obtained.

(48) Subsequently, the CPU proceeds to step 410 to compare the front looking radar obtained information FRXn with/to the coordinate transformed front-side looking radar information FSXn in order to determine whether or not there is a “target object which at least one of the front-side looking radar device 22L and the front-side looking radar device 22R detects” among the target objects which the front looking radar device 21 detects and which are different from (other than) the objective-forward-vehicle (a).

(49) When the determination at step 410 is positive (affirmative), the CPU proceeds to step 415 at which the CPU integrates/merges the target object information according to a formula (3) described below. That is, at step 415, the CPU obtains integrated target object information. α(t) in the formula (3) described below is a filtering coefficient (weighting coefficient), and is obtained by applying a time t to a look up table Mapα(t) shown in a block B1 in FIG. 4. The time t is an elapsed time from a point in time at which the front looking radar device 21 starts to detect the “target object” which either one of the front-side looking radar device 22L and the front-side looking radar device 22R has been detecting. According to the table Mapα(t), α(t) is obtained as a value which gradually becomes closer to “1” from a value α0 between “0” and “1” as the elapsed time t becomes longer. It should be noted that α(t) may be a constant value between “0” and “1”, which does not change depending upon the elapsed time t.
Integrated value=α(t).Math.FRXn+(1−α(t)).Math.FSXn  (3)

(50) The front looking radar obtained information FRXn in the formula (3) above includes “an inter-vehicle distance Dfx (b), a relative speed Vfx(b), a lateral distance Dfy(b), and a relative lateral speed Vfy(b)” concerning the “target object (hereinafter, referred to as a “common target object (b)”) which was determined at step 410 to be detected by not only the front looking radar device 21 but also either one of the front-side looking radar device 22L and the front-side looking radar device 22R. The coordinate transformed front-side looking radar information FSXn in the formula (3) above includes “a coordinate transformed inter-vehicle distance Dsx, a coordinate transformed relative speed Vsx, a coordinate transformed lateral distance Dsy, and a coordinate transformed relative lateral speed Vsy” concerning the common target object (b). Accordingly, as shown in formulas from (4) to (7) described below, “an integrated inter-vehicle distance Dmx, an integrated relative speed Vmx, an integrated lateral distance Dmy, and an integrated relative lateral speed Vmy” serving as the integrated values are obtained.
Dmx=α(t).Math.Dfx(b)+(1−α(t))−Dsx  (4)
Vmx=α(t).Math.Vfx(b)+(1−α(t)).Math.Vsx  (5)
Dmy=α(t).Math.Dfy(b)+(1−α(t)).Math.Dsy  (6)
Vmy=α(t)−Vfy(b)+(1−α(t)).Math.Vsy   (7)

(51) Subsequently, the CPU proceeds to step 420 to determine whether or not the there is a predicted cut-in vehicle (i.e., whether or not a vehicle which is predicted to cut in exists). More specifically, the CPU obtains a cut-in event probability P by applying “the integrated lateral distance Dmy and the integrated relative speed Vmy” to an area map WS shown in FIG. 5.

(52) For example, when a vehicle traveling in front and diagonally to the left of the own vehicle VA cuts in between the own vehicle VA and the objective-forward-vehicle (a), a trajectory (locus) of a point defined by the integrated lateral distance Dmy and the integrated relative lateral speed Vmy changes as shown by a broken line TL in FIG. 5. The area map WS is made in consideration of such trajectories, and is stored in the ROM beforehand. Generally speaking, the cut-in event probability P obtained using the area map WS becomes higher as an magnitude of the integrated lateral distance Dmy becomes closer to “0”, and becomes higher as a magnitude |Vmy| of the integrated relative lateral speed Vmy becomes larger when the integrated relative lateral speed Vmy is a value indicating that the vehicle is approaching the center portion of the width of the own vehicle.

(53) The CPU determines that there is the “predicted cut-in vehicle”, when the CPU determines that the cut-in event probability P obtained using the area map WS is equal to or higher than a predetermined value (e.g., 60%). That is, the CPU specifies that target object as the predicted cut-in vehicle.

(54) When it is determined that there is the predicted cut-in vehicle, the CPU makes a “Yes” determination at step 420 to execute processes of step 430 and step 435 described below in this order, and then, proceeds to step 495 so as to end the present routine tentatively.

(55) Step 430: The CPU calculates an inter-vehicle deviation (difference) ΔD2 by subtracting the target inter-vehicle distance Dtgt from the integrated inter-vehicle distance Dmx. It should be noted that the target inter-vehicle distance Dtgt used at step 430 is referred to as a “second set inter-vehicle distance”, as a matter of convenience. The second set inter-vehicle distance may be the same as the first set inter-vehicle distance, or may be a value which becomes closer to the first set inter-vehicle distance from a value smaller than the first set inter-vehicle distance by a positive first value as an “elapsed time t from a point in time at which it was determined that there was the predicted cut-in vehicle” becomes longer. In this case, the target inter-vehicle time for calculating the second set inter-vehicle distance may be a time obtained by multiplying the “target inter-vehicle time Ttgt used when the first set inter-vehicle distance is calculated” by a “coefficient s(t)” which comes closer to and converges on “1” from a value between “0” and “1” as the above mentioned time t becomes longer.

(56) Step 435: The CPU calculates the target acceleration G2tgt for cut-in vehicle according to either one of a formula (8) and a formula (9) described below. The target acceleration G2tgt for cut-in vehicle is referred to as a “second target acceleration”, as a matter of convenience. Further, the CPU sets a target acceleration G3tgt for cut-in vehicle described later at an “imaginary acceleration G3infinite” which is larger than a maximum acceleration that the own vehicle VA can realize.

(57) In the formula (8) and the formula (9), Vmx is the integrated relative speed of the target object which was determined to be the predicted cut-in vehicle at step 420, and “K1, and K2” are the same gains as the “K1, and K2” used in the formula (1) and the formula (2), respectively. The CPU uses the formula (8) below when a value (K1.Math.ΔD2+K2.Math.Vmx) is positive.

(58) Ka2 is a positive gain (coefficient) for acceleration, and set at a value smaller than the gain Ka1 used in the formula (1) above.

(59) The CPU uses the formula (9) below when the value (K1.Math.ΔD2+K2.Math.Vmx) is negative.

(60) Kd2 is a positive gain (coefficient) for deceleration, and set at a value smaller than the gain Kd1 used in the formula (2) above.
G2tgt(for acceleration)=Ka2.Math.(K1.Math.ΔD2+K2.Math.Vmx)  (8)
G2tgt(for deceleration)=Kd2.Math.(K1.Math.ΔD2+K2.Math.Vmx)  (9)

(61) The target acceleration G2tgt for cut-in vehicle for deceleration calculated based on the formula (9) above is calculated in such a manner that the target acceleration G2tgt is allowed to be an acceleration (negative acceleration) realized/achieved when the brake device of the own vehicle VA is operated, similarly to the target acceleration G1tgt for trailing travel. In other words, the target acceleration G2tgt for cut-in vehicle may become a value obtained under the condition that it is allowed to be a negative acceleration realized/achieved when the brake device is operated. In the above manner, the target acceleration G2tgt for cut-in vehicle is calculated based on the integrated/merged information (integrated values) obtained by integrating the front looking radar obtained information and the coordinate transformed front-side looking radar information.

(62) In contrast, when the CPU determines that there is no predicted cut-in vehicle upon the execution of step 420, the CPU makes a “No” determination at step 420 to proceed to step 425, at which the CPU sets the target acceleration G2tgt for cut-in vehicle at an “imaginary acceleration G2infinite” which is larger than the maximum acceleration that the own vehicle VA can realize, and sets the target acceleration G3tgt for cut-in vehicle described later at the “imaginary acceleration G3infinite” which is larger than the maximum acceleration that the own vehicle VA can realize. Thereafter, the CPU proceeds to step 495 to end the present routine tentatively.

(63) On the other hand, when the determination at step 410 is negative (unaffirmative), the CPU makes a “No” determination. Then, the CPU proceeds to step 440, at which the CPU determines whether or not there is a predicted cut-in vehicle. In this case, the CPU obtains the cut-in event probability P by applying “the coordinate transformed lateral distance Dsy in place of the integrated lateral distance Dmy, and the coordinate transformed relative lateral speed Vsy in place of the integrated relative speed Vmy” to the area map WS shown in FIG. 5. Thereafter, the CPU determines that there is the “predicted cut-in vehicle”, when the cut-in event probability P is equal to or larger than the predetermined value (e.g., 60%), similarly to step 420. That is, the CPU specifies that target object as the predicted cut-in vehicle.

(64) When it is determined that there is the predicted cut-in vehicle, the CPU makes a “Yes” determination at step 440 to proceed to step 450, at which the CPU determines whether or not a lane change (changing lanes) of the predicted cut-in vehicle occurs in front of the own vehicle VA.

(65) For example, as shown in (A) of FIG. 6, when the vehicle VC is cutting in while the own vehicle VA is following the objective-forward-vehicle VB, it is determined that the vehicle VC is the predicted cut-in vehicle. In this case, if the speed Vj of the own vehicle VA is 80 km/h, and the speed of the predicted cut-in vehicle VC is 85 km/h, it is likely that the predicted cut-in vehicle VC will cut in between the own vehicle VA and the objective-forward-vehicle VB.

(66) In contrast, as shown in (B) of FIG. 6, when the own vehicle VA is following (i.e., trailing) the objective-forward-vehicle VB at 80 km/h, and the speed of the predicted cut-in vehicle VC is 60 km/h, it is likely that the predicted cut-in vehicle VC will change lanes to travel behind the own vehicle VA, after the own vehicle VA passes the predicted cut-in vehicle VC.

(67) Step 450 is for determining which situation is occurring, the situation shown in (A) of FIG. 6, or the situation shown in (B) of FIG. 6. More specifically, the CPU determines whether or not the coordinate transformed relative speed Vsx is equal to or higher than a predetermined threshold Vth so as to determine whether or not the changing lanes of the predicted cut-in vehicle occurs in front of the own vehicle VA. It should be noted the predetermined threshold Vth may be set at a value larger than a negative certain value.

(68) When it is determined that the changing lanes of the predicted cut-in vehicle occurs in front of the own vehicle VA (i.e., when it is determined that the coordinate transformed relative speed Vsx is equal to or higher than the predetermined threshold Vth), the CPU makes a “Yes” determination at step 450 to execute processes of step 455 and step 460 described below in this order, and then, proceeds to step 495 so as to end the present routine tentatively.

(69) Step 455: The CPU calculates an inter-vehicle deviation (difference) ΔD3 by subtracting the target inter-vehicle distance Dtgt from the coordinate transformed inter-vehicle distance Dsx. It should be noted that the target inter-vehicle distance Dtgt used at step 455 is referred to as a “third set inter-vehicle distance”, as a matter of convenience. The third set inter-vehicle distance may be the same as the second set inter-vehicle distance, or may be a value which becomes closer to the first set inter-vehicle distance from a value smaller than the second set inter-vehicle distance by a positive first value as the “elapsed time t from the point in time at which it was determined that there was the predicted cut-in vehicle” becomes longer. In this case, the target inter-vehicle time for calculating the third set inter-vehicle distance may be a time obtained by multiplying the “target inter-vehicle time Ttgt used when the first set inter-vehicle distance is calculated” by a “coefficient u(t)” which comes closer to and converges on “1” from a value between “0” and “1” and smaller than the coefficient s(t)=s(0) as the above mentioned time t becomes longer. It should be noted that the coefficient u(t) is adjusted so as to be equal to or smaller than the coefficient s(t).

(70) Step 460: The CPU calculates the target acceleration G3tgt for cut-in vehicle according to either one of a formula (10) and a formula (11) described below. The target acceleration G3tgt for cut-in vehicle is referred to as a “third target acceleration”, as a matter of convenience. Further, the o CPU sets the target acceleration G2tgt for cut-in vehicle at the “imaginary acceleration G2infinite” which is larger than the maximum acceleration that the own vehicle VA can realize.

(71) In the formula (10) and the formula (11), Vsx is the coordinate transformed relative speed of the target object which was determined to be the predicted cut-in vehicle at step 440, and “K1, and K2” are the same gains as the “K1, and K2” used in the formula (1) and the formula (2), respectively. The CPU uses the formula (10) below when a value (K1.Math.ΔD3+K2.Math.Vsx) is positive.

(72) Ka3 is a positive gain (coefficient) for acceleration, and set at a value smaller than (or equal to) the gain Ka2 used in the formula (8) above.

(73) The CPU uses the formula (1) below when the value (K1.Math.ΔD3+K2.Math.Vsx) is negative.

(74) Kd3 is a positive gain (coefficient) for deceleration, and set at a value smaller than (or equal to) the gain Kd2 used in the formula (9) above.
G3tgt(for acceleration)=Ka3.Math.(K1.Math.ΔD3+K2.Math.Vsx)  (10)
G3tgt(for deceleration)=Kd3.Math.(K1.Math.ΔD3+K2.Math.Vsx)  (11)

(75) Note that G3tgt is limited so as to be larger than an acceleration (G@TA=0) obtained when the throttle valve opening TA is equal to 0 (G3tgt≤G@TA=0).

(76) The target acceleration G3tgt for cut-in vehicle for deceleration calculated based on the formula (11) above is limited so as not to be equal to or smaller than an acceleration (negative acceleration) G@TA=0 realized/achieved when the throttle valve opening of the internal combustion engine is “0 (or the minimum value within a range that the throttle valve opening can become)” (namely, the throttle valve is fully-closed) while the brake device of the own vehicle VA is not operated. That is, a process for limiting with a lower limit that is the throttle valve fully closed acceleration G@TA=0 on the target acceleration G3tgt for cut-in vehicle is performed. The throttle valve fully closed acceleration G@TA=0 may be said to be a minimum acceleration which the own vehicle VA can realize/achieve without operating the brake device of the own vehicle VA.

(77) More specifically, at step 460, the CPU calculates the target acceleration G3tgt for cut-in vehicle according to either the above formula (10) or the above formula (11). The CPU sets the thus calculated target acceleration G3tgt for cut-in vehicle at the throttle valve fully closed acceleration G@TA=0 if the thus calculated target acceleration G3tgt is smaller than the throttle valve fully closed acceleration G@TA=0. It should be noted that the CPU separately calculates the throttle valve fully closed acceleration G@TA=0 based on the engine rotational speed NE and a gear position of an unillustrated transmission of the own vehicle VA on the assumption that the CPU operates the internal combustion engine under the fuel cut state when the throttle valve opening is “0.” In this manner, the target acceleration G3tgt for cut-in vehicle is obtained based solely/only on the (coordinate transformed) front-side looking radar information.

(78) In contrast, when the CPU makes a “No” determination at either step 440 or step 450, the CPU proceeds to step 445. The CPU sets the target acceleration G2tgt for cut-in vehicle at the “imaginary acceleration G2infinite” which is larger than the maximum acceleration that the own vehicle VA can realize, and sets the target acceleration G3tgt for cut-in vehicle at the “imaginary acceleration G3infinite” which is larger than the maximum acceleration that the own vehicle VA can realize. Thereafter, the CPU proceeds to step 495 to end the present routine tentatively.

(79) 3. Mediation/Adjustment of Target Acceleration and Vehicle Travel Control

(80) At an appropriate point in time, the CPU starts processing from step 700 of a “routine for mediation of target acceleration and vehicle travel control” shown in FIG. 7, to execute processes of step 710 and step 720 in this order, and proceeds to step 795 to end the present routine tentatively.

(81) Step 710: The CPU selects one of the target acceleration G1tgt for trailing travel, the target acceleration G2tgt for cut-in vehicle, and the target acceleration G3tgt for cut-in vehicle, whichever is smallest, and sets the selected target acceleration as the “final target acceleration (mediated/adjusted target acceleration) Gfin.” That is, the CPU mediates among three kinds of target accelerations. In other words, when the target acceleration G2tgt for cut-in vehicle, and the target acceleration G3tgt for cut-in vehicle are considered to be a single target acceleration for cut-in vehicle, the CPU selects either the target acceleration for trailing travel or the target acceleration for cut-in vehicle, whichever is smaller, as the mediated target acceleration Gfin.

(82) Step 720: The CPU sends the mediated target acceleration Gfin to the engine ECU 30 and the brake ECU 40 in order to make the acceleration of the own vehicle VA become equal to the mediated target acceleration Gfin. The engine ECU 30 and the brake ECU 40 control (drive) the engine actuators 32 and the brake actuators 42, respectively, based on the mediated target acceleration Gfin. As a result, the actual acceleration of the own vehicle VA is made to become equal to the mediated target acceleration Gfin. In this manner, the trailing inter-vehicle distance control is performed.

(83) As described above, the first device calculates the target acceleration G1tgt for trailing travel, the target acceleration G2tgt for cut-in vehicle, and the target acceleration G3tgt for cut-in vehicle, and sets the minimum (the smallest) target acceleration among them, as the “final target acceleration (mediated/adjusted target acceleration) Gfin.”

(84) Accordingly, when the target acceleration (one of G2tgt and G3tgt) for cut-in vehicle is selected as the mediated target acceleration Gfin in a case where the predicted cut-in vehicle is detected, the own vehicle VA decelerates so as to increase the inter-vehicle distance between the own vehicle VA and the objective-forward-vehicle. Thus, when the predicted cut-in vehicle actually cuts in, the inter-vehicle distance with respect to the cut-in vehicle (i.e., distance between the own vehicle VA and the predicted cut-in vehicle that is now an actual cut-in vehicle) becomes appropriate in a short time. In addition, if the objective-forward-vehicle starts to rapidly decelerate after a point in time at which the predicted cut-in vehicle is detected, it is likely that the target acceleration G1tgt for trailing travel is selected as the mediated target acceleration Gfin. Therefore, in this case, the own vehicle VA decelerates so as to ensure/acquire an appropriate inter-vehicle distance with respect to the objective-forward-vehicle (i.e., appropriate inter-vehicle distance between the own vehicle VA and the objective-forward-vehicle). As a result, the inter-vehicle distance between the own vehicle VA and the objective-forward-vehicle becoming excessively short can be avoided, in a case where the predicted cut-in vehicle does not actually cut in.

(85) In addition, when the front looking radar device 21 and the front-side looking radar device (22L, 22R) detect the same (identical) target object, the first device integrates/merges the target object information (first target object information) that the front looking radar device 21 obtains and the target object information (second target object information) that the front-side looking radar device (22L, 22R) obtains so as to obtain the integrated target object information. Thereafter, the first device determines the presence or absence of the predicted cut-in vehicle based on the integrated target object information, and further, calculates the target acceleration (G2tgt) for cut-in vehicle regarding (for) the predicted cut-in vehicle when the predicted cut-in vehicle is determined to exist. The target acceleration (G2tgt) for cut-in vehicle may be set at a value obtained on the assumption that the brake device is operated. In other words, the target acceleration (G2tgt) for cut-in vehicle is allowed to become a “negative acceleration whose absolute value is large (i.e., large deceleration)”.

(86) On the other hand, when the predicted cut-in vehicle is detected based solely/only on the “second target object information obtained by the front-side looking radar device”, the first device obtains the target acceleration (G3tgt) for cut-in vehicle while providing the limitation on the target acceleration (G3tgt) for cut-in vehicle in such a manner that the target acceleration (G3tgt) for cut-in vehicle does not become smaller than the “negative acceleration realized/achieved when the throttle valve opening of the internal combustion engine of the own vehicle VA is “0 (or, the throttle valve is fully-closed)” while the brake device of the own vehicle VA is not operated”. Accordingly, when the cutting-in does not actually occur, the strong deceleration of the own vehicle VA due to the predicted cut-in vehicle does not occur. Thus, the driver avoids the odd feeling of rapid deceleration.

Second Embodiment

(87) A vehicle travelling control device according to the second embodiment of the present disclosure (hereinafter, referred to as a “second device”) will next be described. The second device is different from the first device only in the following points.

(88) (1) The second device neither comprises the front-side looking radar device 22L nor the front-side looking radar device 22R.

(89) (2) The second device executes a routine shown in FIG. 8 in place of the routines shown in FIGS. 3 and 4, and executes a routine shown in FIG. 9 in place of FIG. 7.

(90) Those different points will next be mainly described.

(91) The CPU of the second device executes the “target acceleration calculation routine” shown in FIG. 8, every elapse of a predetermined time. It should be noted that the reference number given to the step shown in FIG. 3 is given to a step shown in FIG. 8 whose process is the same as the process of step shown in FIG. 3. The detailed description about such a step will be omitted.

(92) At an appropriate point in time, the CPU starts processing from step 800 shown in FIG. 8 to execute the processes from step 310 to step 340 in this order. Consequently, the target acceleration G1tgt for trailing travel is calculated.

(93) Subsequently, the CPU proceeds to step 810 to determine if there is a predicted cut-in vehicle. In this case, the CPU applies the lateral distance Dfy(n) and the lateral relative speed Vfy(n) of each of “target objects other than the target object which is determined to be the objective-forward-vehicle (a) at step 310, among the target objects (n) that the front looking radar device 21 detects” to the area map WS shown in FIG. 5, so as to obtain the cut-in event probability P of each of the target objects. The CPU determines that there is a predicted cut-in vehicle when there is a target object whose cut-in event probability P is equal to or higher than the predetermined value (e.g., 60%), similarly to step 420. That is, the CPU specifies that target object as the predicted cut-in vehicle.

(94) When it is determined that there is the predicted cut-in vehicle, the CPU makes a “Yes” determination at step 810 to execute processes of step 820 and step 830 described below in this order, and then, proceeds to step 895 so as to end the present routine tentatively.

(95) Step 820: The CPU calculates an inter-vehicle deviation (difference) ΔD4 by subtracting the target inter-vehicle distance Dtgt from the inter-vehicle distance Dfx(b). The inter-vehicle distance Dfx(b) is the inter-vehicle distance Dfx(n) of the target object (b) which is determined to be the predicted cut-in vehicle at step 810. It should be noted that the target inter-vehicle distance Dtgt used at step 820 is referred to as a “fourth set inter-vehicle distance”, as a matter of convenience. The fourth set inter-vehicle distance may be the same as the first set inter-vehicle distance, or may be a value which becomes closer to the first set inter-vehicle distance from a value smaller than the first set inter-vehicle distance by a positive first value as an “elapsed time t from a point in time at which it was determined that there was the predicted cut-in vehicle” becomes longer. In this case, the target inter-vehicle time for calculating the fourth set inter-vehicle distance may be a time obtained by multiplying the “target inter-vehicle time Ttgt used when the first set inter-vehicle distance is calculated” by the “coefficient s(t)” which comes closer to and converges on “1” from a value between “0” and “1” as the above mentioned time t becomes longer.

(96) Step 830: The CPU calculates the target acceleration G4tgt for cut-in vehicle according to either one of a formula (12) and a formula (13) described below. The target acceleration G4tgt for cut-in vehicle is referred to as a “fourth target acceleration”, as a matter of convenience.

(97) In the formula (12) and the formula (13), Vfx(b) is the relative speed Vfx(n) of the target object (b) which was determined to be the predicted cut-in vehicle at step 810, and “K1, and K2” are the same gains as the “K1, and K2” used in the formula (1) and the formula (2), respectively. The CPU uses the formula (12) below when a value (K1.Math.ΔD4+K2.Math.Vfx(b)) is positive.

(98) Ka4 is a positive gain (coefficient) for acceleration, and is set at a value which is equal to or smaller than the gain Ka1 used in the above formula (1) (or than the gain Kat used at step 340 shown in FIG. 8).

(99) The CPU uses the formula (13) below when the value (K1.Math.ΔD4+K2.Math.Vfx(b)) is negative.

(100) Kd4 is a positive gain (coefficient) for deceleration, and is set at a value which is equal to or smaller than the gain Kd1 used in the above formula (2) (or than the gain Kd1 used at step 340 shown in FIG. 8).
G4tgt(for acceleration)=Ka4.Math.(K1.Math.ΔD4+K2.Math.Vfx(b)).Math.  (12)
G4tgt(for deceleration)=Kd4.Math.(K1.Math.ΔD4+K2.Math.Vfx(b))  (13)

(101) The target acceleration G4tgt for cut-in vehicle for deceleration calculated based on the formula (13) above is calculated in such a manner that the target acceleration G4tgt is allowed to be an acceleration (negative acceleration) realized/achieved when the brake device of the own vehicle VA is operated, similarly to the target acceleration G1tgt for trailing travel. In the above manner, the target acceleration G4tgt for cut-in vehicle is calculated based solely/only on the front looking radar obtained information.

(102) In contrast, when the CPU determines that there is no predicted cut-in vehicle upon the execution of step 810, the CPU makes a “No” determination at step 810 to proceed to step 840, at which the CPU sets the target acceleration G4tgt for cut-in vehicle at the “imaginary acceleration G4infinite” which is larger than the maximum acceleration that the own vehicle VA can realize. Thereafter, the CPU proceeds to step 895 to end the present routine tentatively.

(103) Further, at an appropriate point in time, the CPU starts processing from step 900 a “routine for mediation of target acceleration and vehicle travel control” shown in FIG. 9, to execute processes of step 910 and step 920 in this order, and proceeds to step 995 to end the present routine tentatively.

(104) Step 910: The CPU selects either one of the target acceleration G1tgt for trailing travel and the target acceleration G4tgt for cut-in vehicle, whichever is smaller, and sets the selected target acceleration as the “final target acceleration (mediated/adjusted target acceleration) Gfin.” That is, the CPU mediates among two kinds of target accelerations.

(105) Step 920: The CPU sends the mediated target acceleration Gfin to the engine ECU 30 and the brake ECU 40 in order to make the acceleration of the own vehicle VA become equal to the mediated target acceleration Gfin. The engine ECU 30 and the brake ECU 40 control (drive) the engine actuators 32 and the brake actuators 42, respectively, based on the mediated target acceleration Gfin. As a result, the actual acceleration of the own vehicle VA is made to become equal to the mediated target acceleration Gfin. In this manner, the trailing inter-vehicle distance control is performed.

(106) As described above, the second device calculates the target acceleration G1tgt for trailing travel, and the target acceleration G4tgt for cut-in vehicle, and sets the smaller target acceleration among them as the “final target acceleration (mediated/adjusted target acceleration) Gfin.”

(107) Accordingly, similarly to the first device, when the target acceleration G4tgt for cut-in vehicle is selected as the mediated target acceleration Gfin in a case where the predicted cut-in vehicle is detected, the own vehicle VA decelerates so as to increase the inter-vehicle distance between the own vehicle VA and the objective-forward-vehicle. Thus, when the predicted cut-in vehicle actually cuts in, the inter-vehicle distance with respect to the cut-in vehicle (i.e., distance between the own vehicle VA and the predicted cut-in vehicle that is now an actual cut-in vehicle) becomes appropriate in a short time. In addition, if the objective-forward-vehicle starts to rapidly decelerate after a point in time at which the predicted cut-in vehicle is detected, it is likely that the target acceleration G1tgt for trailing travel is selected as the mediated target acceleration Gfin. Therefore, in this case, the own vehicle VA decelerates so as to ensure/acquire an appropriate inter-vehicle distance with respect to the objective-forward-vehicle (i.e., appropriate inter-vehicle distance between the own vehicle VA and the objective-forward-vehicle). As a result, the inter-vehicle distance between the own vehicle VA and the objective-forward-vehicle becoming excessively short can be avoided, in a case where the predicted cut-in vehicle does not actually cut in.

(108) The present disclosure is not limited to the embodiments described above, and various modifications may be adopted within the scope of the present disclosure. For example, as shown in FIGS. 1 and 2, each of the first device and the second device may comprise a stereo camera 101 which can communicate with the driving support ECU through the CAN 100. The stereo camera 101 is positioned at an upper portion of a front window within a passenger room, and acquires a stereo image in a straight forward direction of the own vehicle VA. From the stereo image, the stereo camera 101 obtains the target object information, and lane markers (white lines). The stereo camera 101 can recognize the running lane based on the lane markers, and the like. In this case, the first device and the second device may obtain the objective-forward-vehicle and the predicted cut-in vehicle from the target object information that the front looking radar device 21 and the stereo camera 101 acquire. Further, the first device and the second device may estimate a course of the own vehicle VA based on the information concerning the running lane obtained from the stereo camera 101, and may modify the target information which is obtained by the front looking radar device 21 and/or the front-side looking radar device 22L, 22R in consideration of the estimated course, for example, in such a manner that the lateral position of the target object become a target position in a direction orthogonal to the estimated course.

(109) Further, the first device and the second device may be configured to determine whether or not there is a predicted cut-in vehicle using a map other than the map shown in FIG. 5. For example, the first device and the second device may be configured to determine whether or not there is a predicted cut-in vehicle in consideration of not only the lateral position and the lateral relative speed of the vehicles other than the objective-forward-vehicle but also the inter-vehicle distance of the vehicles.