Traffic jam judgment device for vehicle and display control device for vehicle
Patent Information
- Application Number
- JP2023190332
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-11-07
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-08-21
Smart Images

Figure 0007586270000001 
Figure 0007586270000002 
Figure 0007586270000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a vehicle congestion determination device and a vehicle display control device used in a vehicle having an automatic driving function. [Background technology]
[0002] For example, there is known a vehicle control device described in Patent Document 1. In the vehicle control device of Patent Document 1, for example, when driving on a highway, if it is determined from congestion information provided by a system such as VICS (Vehicle information and communication System, registered trademark) that a congestion has occurred and that the congestion section is a predetermined distance or more, automatic driving (control for maintaining a constant distance from a traffic-congested vehicle ahead and following the vehicle) is started, and if an automatic driving stop condition is satisfied after automatic driving has started, automatic driving is stopped.
[0003] This means that the driver will no longer have to go through the hassle of judging traffic congestion conditions and operating the autonomous driving switch themselves, and the autonomous driving function will be able to automatically start and stop appropriately in response to traffic jams. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2005-324661 A Summary of the Invention [Problem to be solved by the invention]
[0005] In the above Patent Document 1, it can be read as if automatic driving corresponding to the congestion is smoothly started from the start point of the congestion section obtained by VICS. However, in the device that controls automatic driving, conditions are set for whether or not automatic driving can be started (for example, vehicle speed conditions that enable automatic driving to be started). In order to realize a safe and reliable transition to automatic driving, the vehicle speed conditions that enable the start of automatic driving may be set to a vehicle speed (for example, 10 km / h) that is lower than the vehicle speed conditions (for example, 40 km / h) set in VICS to grasp the congestion section.
[0006] Therefore, even if the vehicle enters a congested section as determined by VICS while driving, a situation may occur in which automatic driving will not start as long as the vehicle speed condition for automatic driving to start is not met. Therefore, the user may feel uncomfortable that automatic driving does not start even though the vehicle has entered a congested section.
[0007] In view of the above problems, an object of the present disclosure is to provide a traffic congestion judgment device for a vehicle that can accurately judge traffic congestion conditions, and a display control device for a vehicle that can clearly inform the user of the transition to autonomous driving. [Means for solving the problem]
[0008] In order to achieve the above object, the present disclosure employs the following technical means.
[0009] In a first disclosure, a traffic congestion determination device for a vehicle is provided, which is configured to determine the travel speed of another vehicle ahead of the vehicle or the vehicle speed of the vehicle. Is expected Below the first threshold set By First information indicating the occurrence of a traffic jam and a second threshold value that is a condition under which the autonomous driving function of the vehicle can start autonomous driving during the traffic jam. When the driving speed or vehicle speed falls below an acquisition unit (50, 81) that acquires second information indicating the occurrence of a traffic jam; a control unit (160) that executes a first algorithm for determining the occurrence of congestion using a first threshold value and a second algorithm for determining the occurrence of congestion using a second threshold value; The control unit is characterized in that it determines whether or not to display on the display unit (120) a message indicating that autonomous driving is not possible, based on the result of the first algorithm and the result of the second algorithm.
[0010] According to this disclosure, the control unit executes the first algorithm and the second algorithm to determine the occurrence of traffic congestion, and therefore, it is possible to accurately determine the occurrence status of traffic congestion.
[0011] In addition, in a second disclosure, there is provided a vehicle display control device that controls a display unit (120) that displays information about a vehicle, The speed of other vehicles in front of your vehicle or the vehicle's speed Is expected Below the first threshold set By First information indicating the occurrence of a traffic jam and a second threshold value that is a condition under which the autonomous driving function of the vehicle can start autonomous driving during the traffic jam. and the driving speed or vehicle speed and an acquisition unit (50, 81) that acquires second information indicating whether autonomous driving is possible or not based on the information. The device is characterized by comprising a display control unit (160) that allows the display unit to display a message indicating that autonomous driving is not possible when the driving speed or the vehicle speed is not below at least one of a first threshold value in the first information or a second threshold value in the second information.
[0012] According to this disclosure, even if it is known from the first information that a traffic jam has occurred, the display control unit does not display a message indicating that the traffic jam has occurred unless the second information indicates that the traffic jam has occurred below the second threshold. , own In other words, the transition to autonomous driving can be communicated to the user in an easy-to-understand manner.
[0013] The reference characters in parentheses for each of the above means indicate the corresponding relationship with the specific means described in the embodiments below. [Brief description of the drawings]
[0014] [Figure 1]1 is an explanatory diagram showing the configuration of a vehicle congestion determination device and a vehicle display control device mounted on a vehicle having an automatic driving function in a first embodiment. [Diagram 2] This is an explanatory diagram showing traffic congestion information from VICS and the possible levels of autonomous driving (levels 2 and 3). [Diagram 3] 1 is a flowchart (first half) showing the procedure for display control performed by the HCU 160 in the first embodiment. [Figure 4] 11 is a flowchart (second half) showing the procedure for display control performed by HCU 160 in the first embodiment. [Diagram 5] 3 is an explanatory diagram showing a display state at a traveling position A in FIG. 2. [Figure 6] 3 is an explanatory diagram showing a display state at a traveling position Ba in FIG. 2. [Figure 7] 3 is an explanatory diagram showing a display state at a traveling position Bb in FIG. 2. [Figure 8] 3 is an explanatory diagram showing a display state at a traveling position C in FIG. 2. FIG. [Figure 9] 3 is an explanatory diagram showing a display state at a traveling position D in FIG. 2. FIG. [Figure 10] 3 is an explanatory diagram showing a display state at a traveling position E in FIG. 2. FIG. [Figure 11] FIG. 11 is an explanatory diagram illustrating a display state (one example) in the second embodiment. [Figure 12] FIG. 11 is an explanatory diagram illustrating a display state (another example) in the second embodiment. [Figure 13] FIG. 11 is an explanatory diagram for explaining a display state (one example) in another embodiment. [Figure 14] FIG. 11 is an explanatory diagram for explaining a display state (another example) in another embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0015] Hereinafter, a number of embodiments for carrying out the present disclosure will be described with reference to the drawings. In each embodiment, the same reference numerals may be used to designate parts corresponding to matters described in the preceding embodiment, and duplicated descriptions may be omitted. In each embodiment, when only a part of the configuration is described, other embodiments described previously may be applied to other parts of the configuration. In addition to combinations of parts that are specifically indicated as being possible in each embodiment, it is also possible to partially combine embodiments even if not indicated, as long as there is no particular problem with the combination.
[0016] (First embodiment) A traffic congestion judgment device 100 for a vehicle and a display control device 101 for a vehicle according to a first embodiment will be described with reference to Figs. 1 to 10. The traffic congestion judgment device 100 for a vehicle and the display control device 101 for a vehicle according to the first embodiment are mounted (applied) on a vehicle having an automatic driving function. Hereinafter, the traffic congestion judgment device 100 for a vehicle will be referred to as the traffic congestion judgment device 100, and the display control device 101 for a vehicle will be referred to as the display control device 101.
[0017] As shown in Fig. 1, the traffic jam determination device 100 and the display control device 101 each include an HCU (Human Machine Interface Control Unit) 160. The traffic jam determination device 100 determines the occurrence of traffic jams, and the display control device 101 displays various vehicle information on a display unit (e.g., a meter display 120). The various vehicle information includes, for example, vehicle travel information (vehicle speed, etc.), the occurrence of traffic jams when traffic jams occur while driving on an expressway, the availability of automatic driving, and the like.
[0018] The traffic congestion judgment device 100 and the display control device 101 are connected to a DSM (Driver Status Monitor) 20, a locator 30, a surrounding monitoring sensor 40, an in-vehicle communication device 50, a first automatic driving ECU 60, a second automatic driving ECU 70, and a vehicle control ECU 80 installed in the vehicle via a communication bus 90, etc.
[0019] The DSM 20 includes a near-infrared light source, a near-infrared camera, and a control unit for controlling them. The DSM 20 is installed, for example, on the upper surface of the steering column or the upper surface of the instrument panel with the near-infrared camera facing the headrest of the driver's seat. The DSM 20 uses the near-infrared camera to capture an image of the driver's head illuminated with near-infrared light from the near-infrared light source. The image captured by the near-infrared camera is analyzed by the control unit. The control unit extracts information such as the position and line of sight of the driver from the captured image, and provides the extracted driver's condition information (sleepiness, looking away, illness, etc.) to the HCU 160, etc., via the communication bus 90.
[0020] Locator 30 generates vehicle position information, etc., by composite positioning that combines a plurality of pieces of acquired information. Locator 30 includes a Global Navigation Satellite System (GNSS) receiver 31, an inertial sensor 32, a map database (hereinafter, “map DB”) 33, a locator ECU 34, etc.
[0021] The GNSS receiver 31 receives positioning signals from a plurality of positioning satellites.
[0022] The inertial sensor 32 is a sensor that detects an inertial force acting on the vehicle and includes, for example, a gyro sensor and an acceleration sensor.
[0023] The map DB 33 is a non-volatile memory and stores map data such as link data, node data, road shapes, structures, etc. The map data may be a three-dimensional map consisting of a point cloud of characteristic points of road shapes and structures. The three-dimensional map may be generated based on captured images by REM (Road Experience Management). The map data may also include traffic regulation information, road construction information, weather information, traffic signal information, etc. The map data stored in the map DB 33 is updated periodically or as needed based on the latest information received by the in-vehicle communication device 50 described later.
[0024] Locator ECU 34 mainly includes a microcomputer equipped with a processor, a memory, an input / output interface, and a bus connecting these, etc. Locator ECU 34 sequentially locates the position of the vehicle (hereinafter, the vehicle position) by combining the positioning signal received by GNSS receiver 31, the measurement results of inertial sensor 32, and the map data of map DB 33.
[0025] The vehicle position may be expressed by, for example, latitude and longitude coordinates. The vehicle position may be determined by using a travel distance calculated from signals successively output from an on-board sensor 81 (such as a vehicle speed sensor) mounted on the vehicle. When a three-dimensional map consisting of a point cloud of characteristic points of road shapes and structures is used as map data, the locator ECU 34 may specify the vehicle position by using the three-dimensional map and the detection results of the periphery monitoring sensor 40 without using the GNSS receiver 31.
[0026] The perimeter monitoring sensor 40 is an autonomous sensor that monitors the environment around the vehicle. The perimeter monitoring sensor 40 can detect moving objects such as pedestrians, cyclists, animals other than humans, and other vehicles from a detection range around the vehicle, as well as road markings such as fallen objects on the road, guardrails, curbs, road signs, lane lines, and median strips, and stationary objects such as roadside structures. The perimeter monitoring sensor 40 provides detection information of objects around the vehicle to the first automatic driving ECU 60, the second automatic driving ECU 70, and the like through a communication bus 90. The perimeter monitoring sensor 40 has, for example, a front camera 41 and a millimeter wave radar 42 as detection components for object detection.
[0027] The front camera 41 outputs at least one of image data capturing an image of the area in front of the vehicle and an analysis result of the image data as detection information.
[0028] A plurality of millimeter wave radars 42 are arranged at intervals on the front and rear bumpers of the vehicle, for example. The millimeter wave radar 42 irradiates millimeter waves or quasi-millimeter waves toward the front range, front side range, rear range, rear side range, etc. of the vehicle. The millimeter wave radar 42 generates detection information by processing to receive reflected waves reflected by moving objects, stationary objects, etc. Note that the perimeter monitoring sensor 40 may include other detection configurations, such as LiDAR (Light Detection and Ranging / Laser Imaging Detection and Ranging) that detects a point cloud of feature points of features, and sonar that receives reflected ultrasonic waves.
[0029] The in-vehicle communication device 50 is a communication module mounted on a vehicle. The in-vehicle communication device 50 has at least a function of V2N (Vehicle to cellular Network) communication according to communication standards such as LTE (Long Term Evolution) and 5G, and transmits and receives radio waves to and from base stations around the vehicle. The in-vehicle communication device 50 may further have functions such as vehicle to roadside infrastructure (hereinafter "V2I") communication and vehicle to vehicle (hereinafter "V2V") communication. The in-vehicle communication device 50 enables cooperation between the cloud and the in-vehicle system (Cloud to Car) through V2N communication. By mounting the in-vehicle communication device 50, the vehicle becomes a connected car that can be connected to the Internet.
[0030] The in-vehicle communication device 50 acquires road traffic information such as congestion conditions on roads and traffic regulations from FM multiplex broadcasts and beacons installed on roads by using, for example, VICS (Vehicle information and communication System). In VICS, for example, a judgment speed (first threshold) is determined in advance for each type of road (general road, expressway, etc.), and if the vehicle speed of a traveling vehicle on each type of road falls below the judgment speed, it is determined that congestion has occurred. For example, a value of 10 km / h is used as this judgment speed for general roads, and 40 km / h is used for expressways. The in-vehicle communication device 50 corresponds to an acquisition unit that acquires first information (occurrence of congestion according to VICS) based on the first threshold.
[0031] The in-vehicle communication device 50 communicates with a plurality of vehicles ahead of the vehicle through a predetermined center base station or between vehicles, for example, by using a DCM (Data Communication Module) or vehicle-to-vehicle communication. The in-vehicle communication device 50 obtains information such as the vehicle speed and position of the vehicle traveling ahead of the vehicle, and obtains the congestion occurrence status (congested area) ahead of the vehicle in real time. In the DCM (or vehicle-to-vehicle communication), a judgment speed (second threshold) is set in advance to grasp the occurrence of actual congestion, and if the obtained vehicle speed falls below the judgment speed, it is determined that congestion has occurred. For example, a value such as 10 km / h is used as the judgment speed on a highway. The in-vehicle communication device 50 corresponds to an acquisition unit that acquires second information (occurrence of congestion due to DCM) based on the second threshold, as in the above case.
[0032] The in-vehicle communication device 50 provides traffic congestion information based on the VICS or DCM to the second automatic driving ECU 70, the HCU 160, and the like.
[0033] The first automatic driving ECU 60 and the second automatic driving ECU 70 are mainly composed of a computer equipped with memories 61, 71, processors 62, 72, an input / output interface, and a bus connecting these, etc. The first automatic driving ECU 60 and the second automatic driving ECU 70 are ECUs capable of executing automatic driving control that controls part or all of the driving of the vehicle.
[0034] The first automatic driving ECU 60 has a partial automatic driving function that partially takes over the driving operation of the driver. The second automatic driving ECU 70 has an automatic driving function that can take over the driving operation of the driver. As an example, in the automatic driving levels defined by the Society of Automotive Engineers, the first automatic driving ECU 60 enables partial automatic driving control (advanced driving assistance) of level 2 or lower. That is, the first automatic driving ECU 60 can implement automatic driving control that requires the driver to monitor the surroundings. In other words, the first automatic driving ECU 60 can implement automatic driving in which the second task described below is prohibited.
[0035] For example, the first automatic driving ECU 60 can execute one or both of longitudinal and lateral control of the vehicle. Here, the longitudinal direction is the direction that coincides with the front-rear direction of the vehicle, and the lateral direction is the direction that coincides with the width direction of the vehicle. The first automatic driving ECU 60 executes control of acceleration and deceleration of the vehicle as longitudinal control, and executes steering angle control of the steering wheels of the vehicle as lateral control.
[0036] The first automatic driving ECU 60 constructs a plurality of functional units that realize the above-mentioned advanced driving assistance by having the processor 62 execute a plurality of instructions in accordance with a driving assistance program stored in the memory 61.
[0037] The first automatic driving ECU 60 recognizes the driving environment around the vehicle based on the detection information acquired from the periphery monitoring sensor 40. As an example, the first automatic driving ECU 60 generates information (lane information) indicating the relative positions and shapes of the left and right dividing lines or road edges of the lane in which the vehicle is currently traveling (hereinafter, the current lane) as analyzed detection information. In addition, the first automatic driving ECU 60 generates information (preceding vehicle information) indicating the presence or absence of a preceding vehicle preceding the vehicle in the current lane, and the position and speed of the preceding vehicle if there is one, as analyzed detection information. The first automatic driving ECU 60 may be configured to recognize MD areas, AD areas, ST sections, and non-ST sections, which will be described later.
[0038] The first automatic driving ECU 60 executes ACC (Adaptive Cruise Control) control, which realizes constant speed driving of the vehicle at a target speed or driving following the preceding vehicle, based on the preceding vehicle information. The first automatic driving ECU 60 executes LTA (Lane Tracing Assist) control, which maintains the vehicle driving within the lane, based on the lane information. Specifically, the first automatic driving ECU 60 generates control commands for acceleration / deceleration or steering angle, and sequentially provides them to the vehicle control ECU 80, which will be described later. The ACC control is an example of longitudinal control, and the LTA control is an example of lateral control.
[0039] The first automatic driving ECU 60 executes both the ACC control and the LTA control to realize automatic driving of Level 2. Note that the first automatic driving ECU 60 may be capable of realizing automatic driving of Level 1 by executing either the ACC control or the LTA control.
[0040] On the other hand, the second automatic driving ECU 70 enables automatic driving control of level 3 or higher among the above automatic driving levels. That is, the second automatic driving ECU 70 enables automatic driving in which the driver is permitted to interrupt surrounding monitoring. In other words, the second automatic driving ECU 70 enables automatic driving in which the second task is permitted.
[0041] Here, the second task is an action other than driving permitted to the driver, and is a specific action that is specified in advance. During the automatic driving period in which the vehicle is automatically driven by the level 3 automatic driving function of the second automatic driving ECU 70, the driver in this case is a person (passenger) who takes over the driving control from the automatic driving system when leaving a limited area or in an emergency. The driver may be legally permitted to perform the second task until a request to perform driving operation by the automatic driving system, that is, a request to take over driving (Take Over Request) occurs.
[0042] The second task may be called a secondary activity or other activity. The second task must not prevent the driver from responding to a request from the automated driving system to take over driving operations. Examples of the second task include watching content such as videos (watching movies and TV), operating a smartphone, reading, and eating.
[0043] The second automatic driving ECU 70 constructs a plurality of functional units that realize the above-mentioned automatic driving by causing the processor 72 to execute a plurality of instructions in accordance with an automatic driving program stored in the memory 71.
[0044] The second automatic driving ECU 70 recognizes the driving environment around the vehicle based on the vehicle's own position and map data acquired from the locator ECU 34, the detection information acquired from the surrounding monitoring sensor 40, and the communication information (traffic congestion information) acquired from the in-vehicle communication device 50. For example, the second automatic driving ECU 70 recognizes the position of the vehicle's current lane, the shape of the current lane, the relative positions and relative speeds of moving objects around the vehicle, the traffic congestion situation, and the like.
[0045] In addition, the second automatic driving ECU 70 distinguishes between manual driving areas (MD areas) and automatic driving areas (AD areas) in the area in which the vehicle is traveling, and distinguishes between ST sections and non-ST sections in the AD areas, and provides the recognition results to the HCU 160 sequentially.
[0046] The MD area is an area where automated driving is prohibited. In other words, the MD area is an area where the driver is required to perform all of the vehicle's longitudinal control, lateral control, and periphery monitoring. For example, the MD area is an area where the driving route is a general road.
[0047] An AD area is an area where autonomous driving is permitted. In other words, an AD area is an area where a vehicle can take over one or more of longitudinal control, lateral control, and perimeter monitoring. For example, an AD area is an area where the driving road is a highway or a road for motor vehicles only.
[0048] AD areas are divided into non-ST sections where automated driving of level 2 or lower is possible, and ST sections where automated driving of level 3 or higher is possible. In this embodiment, it is assumed that non-ST sections where automated driving of level 1 is permitted are equivalent to non-ST sections where automated driving of level 2 is permitted.
[0049] The ST section is, for example, a travel section where congestion occurs (congested section). The ST section is, for example, a travel section where a high-precision map is provided. The HCU 160 determines that the section is an ST section when the travel speed of the vehicle continues to be within a threshold (second threshold) range for a predetermined period of time. Alternatively, the HCU 160 may determine whether the section is an ST section using the vehicle's position and congestion information obtained from the in-vehicle communication device 50 by the DCM. Furthermore, the HCU 160 may determine whether the section is an ST section based on conditions (corresponding to the third information of the present disclosure) such as the road on which the vehicle is travelling has two or more lanes, there are other vehicles around the vehicle (in the same lane and the adjacent lane), there is a median strip on the road on which the vehicle is travelling, and high-precision map data is held in addition to the travel speed of the vehicle (congested travel section condition).
[0050] In addition to congested sections, HCU160 may also classify sections where specific conditions other than congestion are met regarding the vehicle's surrounding environment (such as sections where constant speed driving without congestion on a highway, following driving, LTA (lane keeping driving)) and other possible sections (corresponding to the fourth information of this disclosure) as ST sections.
[0051] The autonomous driving system including the first and second autonomous driving ECUs 60, 70 described above enables the vehicle to perform at least autonomous driving equivalent to levels 2 and 3. In what follows, the state in which autonomous driving equivalent to level 2 is being performed may be referred to as "level 2 execution mode," and the state in which autonomous driving equivalent to level 3 is being performed may be referred to as "level 3 execution mode."
[0052] The vehicle control ECU 80 is an electronic control device that performs acceleration / deceleration control and steering control of the vehicle. The vehicle control ECU 80 includes a power unit control ECU and a brake ECU that perform acceleration / deceleration control, and a steering ECU that performs steering control. The vehicle control ECU 80 acquires detection signals output from each sensor, such as a vehicle speed sensor and a steering angle sensor, mounted on the vehicle, and outputs control signals to each driving control device, such as an electronically controlled throttle, a brake actuator, and an EPS (Electric Power Steering) motor. The vehicle control ECU 80 acquires a control instruction for the vehicle from the first automatic driving ECU 60 or the second automatic driving ECU 70, and controls each driving control device to realize automatic driving according to the control instruction.
[0053] The vehicle control ECU 80 is also connected to an on-board sensor 81 that detects driving operation information of the driving members by the driver. The on-board sensor 81 includes, for example, a pedal sensor that detects the amount of depression of the accelerator pedal, and a steering sensor that detects the amount of steering. In addition, the on-board sensor 81 also includes a vehicle speed sensor that detects the traveling speed of the vehicle, a rotation sensor that detects the operating speed of the traveling drive parts (engine, traveling motor, etc.), and a shift sensor that detects the shift position of the transmission. The vehicle control ECU 80 sequentially provides the detected driving operation information, vehicle operation information, etc. to the HCU 160.
[0054] Next, the configurations of the traffic congestion determination device 100 and the display control device 101 will be described. The traffic congestion determination device 100 includes an on-board communication device 50 and an on-board sensor 81 as an acquisition unit, and an HCU 160 as a control unit. The display control device 101 includes a plurality of display devices as a display unit, an on-board communication device 50 and an on-board sensor 81 as an acquisition unit, and an HCU 160 as a display control unit. In addition, each of the devices 100 and 101 is provided with an audio device 140, an operation device 150, etc.
[0055] The multiple display devices include a head-up display (hereinafter, HUD) 110, a meter display 120, and a center information display (hereinafter, CID) 130. The multiple display devices may further include displays EMB (rear display), EML (left display), and EMR (right display) of an electronic mirror system. The HUD 110, the meter display 120, and the CID 130 are display units that present image content, such as still images or videos, to the driver as visual information.
[0056] In this embodiment, the meter display 120 is described as a main display unit (display unit), and the CID 130 is described as a sub-display unit.
[0057] Based on the control signal and image data acquired from the HCU 160, the HUD 110 projects the light of the image formed in front of the driver onto a projection area defined on the vehicle's front windshield or the like. The light of the image reflected by the front windshield into the passenger compartment is perceived by the driver sitting in the driver's seat. In this way, the HUD 110 displays a virtual image in the space ahead of the projection area. The driver visually recognizes the virtual image within the field of view displayed by the HUD 110 as being superimposed on the view in front of the vehicle.
[0058] The meter display 120 and the CID 130 are mainly configured to include, for example, a liquid crystal display or an OLED (Organic Light Emitting Diode) display. The meter display 120 and the CID 130 display various images on the display screen based on a control signal and video data acquired from the HCU 160. The meter display 120 is installed, for example, in front of the driver's seat. The CID 130 is provided in a central area in the vehicle width direction in front of the driver. For example, the CID 130 is installed above a center cluster in an instrument panel. The CID 130 has a touch panel function and detects, for example, a touch operation and a swipe operation on the display screen by the driver or the like.
[0059] Audio device 140 has a plurality of speakers installed in the vehicle cabin. Audio device 140 presents an alarm sound, a voice message, or the like as auditory information to the driver based on a control signal and voice data acquired from HCU 160. In other words, audio device 140 is an information presentation device capable of presenting information in a form different from visual information.
[0060] The operation device 150 is an input unit that accepts user operations by a driver or the like. User operations related to, for example, starting and stopping each level of an autonomous driving function are input to the operation device 150. The operation device 150 includes, for example, a steering switch provided on the spokes of the steering wheel, an operation lever provided on the steering column, a voice input device that recognizes the contents of the driver's speech, and an icon (switch) for touch operation in the CID 130.
[0061] The HCU 160 judges the occurrence of traffic congestion and controls the presentation of information to the driver (display on a display device) based on information from the above-mentioned in-vehicle communication device 50, vehicle control ECU 80 (first automatic driving ECU 60 and second automatic driving ECU 70), etc. The HCU 160 mainly includes a computer equipped with a memory 161, a processor 162, an input / output interface, and a bus connecting these.
[0062] The memory 161 is at least one type of non-transitory tangible storage medium, such as a semiconductor memory, a magnetic medium, an optical medium, etc., that non-temporarily stores or stores computer-readable programs and data, etc. The memory 161 stores various programs executed by the processor 162, such as a presentation control program described below.
[0063] The processor 162 is hardware for arithmetic processing, and includes at least one type of core selected from a central processing unit (CPU), a graphics processing unit (GPU), and a reduced instruction set computer (RISC)-CPU.
[0064] The processor 162 executes a plurality of instructions included in the presentation control program stored in the memory 161. In this way, the HCU 160 configures a plurality of functional units for controlling presentation to the driver. In this way, in the HCU 160, the presentation control program stored in the memory 161 causes the processor 162 to execute a plurality of instructions, thereby configuring a plurality of functional units.
[0065] The HCU 160 acquires the recognition result of the driving environment from the first automatic driving ECU 60 or the second automatic driving ECU 70. The HCU 160 grasps the surrounding state of the vehicle based on the acquired recognition result. Specifically, the HCU 160 grasps the approach to an AD area, the entry into an AD area, the approach to an ST section (congested section), the entry into an ST section, etc. The HCU 160 may grasp the surrounding state based on information acquired directly from the locator ECU 34, the surrounding monitoring sensor 40, etc., instead of the recognition result acquired from the first and second automatic driving ECUs 60, 70.
[0066] The HCU 160 grasps the above-mentioned ST section (congested section) by integrating the judgment of the occurrence of traffic congestion based on VICS information by the vehicle-mounted communication device 50 (traffic congestion judgment by executing the first algorithm) with the judgment of the occurrence of traffic congestion using DCM information by the vehicle-mounted communication device 50 and vehicle speed information by the vehicle-mounted sensor 81 (vehicle speed sensor) (traffic congestion judgment by executing the second algorithm).
[0067] The HCU 160 estimates the driver's state based on information from the DSM 20, the vehicle control ECU 80, etc. For example, the HCU 160 estimates whether each body part of the driver is involved in the driving operation as the driver's state. Specifically, the HCU 160 determines whether the driver's eyes are monitoring the surroundings based on state information related to the line of sight of the driver acquired from the DSM 20, etc. Also, the HCU 160 determines whether the driver is holding the steering wheel with his / her hands based on the steering amount acquired from the vehicle control ECU 80. Also, the HCU 160 determines whether the driver is placing his / her foot on the accelerator pedal based on the accelerator pedal depression amount acquired from the vehicle control ECU 80.
[0068] Furthermore, the HCU 160 judges from the driver's state information acquired from the DSM 20 whether the driver is drowsy, looking away, or has an illness.
[0069] In the following, the state in which the eyes are monitoring the surroundings may be referred to as eyes on, and the state in which they are not monitoring the surroundings may be referred to as eyes off. Also, the state in which the hands are holding the steering wheel may be referred to as hands on, and the state in which the hands are not holding the steering wheel may be referred to as hands off. In addition, the state in which the foot is placed on the accelerator pedal may be referred to as leg on, and the state in which the foot is not placed on the accelerator pedal may be referred to as leg off.
[0070] The HCU 160 determines the driving state related to autonomous driving in cooperation with the first autonomous driving ECU 60 and the second autonomous driving ECU 70. Specifically, the HCU 160 determines the autonomous driving level permitted to the driver and the autonomous driving level to be actually executed as the driving state.
[0071] The HCU 160 determines that automated driving cannot be permitted when the vehicle is traveling in an MD area. On the other hand, the HCU 160 determines that automated driving of level 2 or higher can be permitted when the vehicle is traveling in an AD area. Furthermore, the HCU 160 determines that automated driving of level 2 can be permitted when the vehicle is traveling in a non-ST section of an AD area, and determines that automated driving of level 3 can be permitted when the vehicle is traveling in an ST section.
[0072] In what follows, the state in which Level 2 autonomous driving is permitted may be referred to as the "Level 2 permitted state," and the state in which Level 3 autonomous driving is permitted may be referred to as the "Level 3 permitted state." Additionally, the state in which autonomous driving itself is prohibited may be referred to as the "autonomous driving prohibited state."
[0073] In addition, when it is determined that level 2 autonomous driving is permitted, the HCU 160 determines whether or not to permit hands-off driving at level 2. Specifically, the HCU 160 determines whether or not to permit hands-off driving when certain conditions are met based on the execution state of the LTA, the presence or absence of high-precision map data around the vehicle, lane conditions, the driver's surrounding monitoring state, the road shape around the vehicle, and the like.
[0074] The specific conditions include, for example, at least one of the following: LTA control is being executed, there is high-precision map data around the vehicle, at least one of the left and right dividing lines of the current lane can be detected, it can be determined that the driver is monitoring the surroundings, and the driving section is not a section with a complex road structure (for example, a merging section or a branching section, etc.). In the following, a state in which hands-off is permitted may be referred to as a "hands-off permitted state," and a state in which hands-off is prohibited may be referred to as a "hands-off prohibited state."
[0075] Furthermore, the HCU 160 permits leg off when at least ACC is being executed in autonomous driving of level 2 or lower. In the following, the state in which leg off is permitted may be referred to as the "leg off permitted state," and the state in which leg off is prohibited may be referred to as the "leg off prohibited state." In addition, the HCU 160 permits eyes off when level 3 autonomous driving is permitted. In other words, the level 3 permitted state can also be referred to as the eyes off permitted state.
[0076] The HCU 160 determines the autonomous driving level to actually be executed based on the vehicle's surrounding conditions, the driver's condition, the currently permitted autonomous driving level, and input information to the operation device 150. That is, when an instruction to start the currently permitted autonomous driving level is acquired as input information, the HCU 160 decides to execute the autonomous driving level.
[0077] The HCU 160 controls the presentation of content related to autonomous driving. Specifically, the HCU 160 selects content to be presented on each of the display devices 110, 120, and 130 based on various information.
[0078] The HCU 160 arbitrates the contents to be displayed on the display devices 110, 120, and 130. The HCU 160 comprehensively determines the priority of each content based on various information. The HCU 160 selects the content determined to have a high priority as the content to be presented. In addition, the HCU 160 can sequentially change the display size and display layout of each content to be displayed on the display devices 110, 120, and 130 according to the priority. As an example, the HCU 160 increases the display size of content with a higher priority. As another example, the HCU 160 positions content with a higher priority toward the front of each display area.
[0079] The HCU 160 generates control signals and video data to be provided to each of the display devices 110, 120, and 130, and generates control signals and audio data to be provided to the audio device 140. The HCU 160 outputs the generated control signals and each data to each presentation device, thereby presenting information on each of the display devices 110, 120, and 130.
[0080] The configurations of the traffic congestion determination device 100 and the display control device 101 are as described above. Hereinafter, the operation and effects of the device will be described with reference to Figs. 2 to 10.
[0081] This embodiment mainly targets control over determining whether or not traffic congestion has occurred when driving on expressways, and how to provide information to the driver to switch to autonomous driving level 3 (where the driver does not need to monitor the surroundings) when traffic congestion occurs.
[0082] Figure 2 shows a schematic diagram of congestion information from VICS when driving on an expressway (thick lines in the figure indicate sections where congestion occurs), sections where Level 2 autonomous driving is possible in response to congestion information from the vehicle speed sensor and DCM, and sections where Level 3 autonomous driving is possible. Note that the letters in Figure 2 indicate driving positions over time (A, Ba, Bb, C, etc.).
[0083] The HCU 160 acquires information from the VICS from the in-vehicle communication device 50 and judges whether or not there is a traffic jam ahead of the vehicle (execution of the first algorithm). That is, the HCU 160 judges that a traffic jam has occurred (first information) based on the VICS information when, for example, the vehicle speed (travel speed) of another vehicle ahead of the vehicle traveling on the expressway falls below a first predetermined threshold (for example, 40 km / h). From this traffic jam information, the HCU 160 can grasp the start and end points of the traffic jam ahead of the vehicle.
[0084] Furthermore, the HCU 160 acquires information from the vehicle speed sensor and DCM from the on-board sensor 81 and the on-board communication device 50, and determines whether or not there is congestion ahead of the vehicle (ahead of the vehicle) (execution of the second algorithm). That is, the HCU 160 determines that congestion has occurred (second information) when, for example, the vehicle speed (traveling speed) of the vehicle traveling on a highway or another vehicle ahead of the vehicle in the information from the vehicle speed sensor and DCM falls below a second predetermined threshold (for example, 10 km / h). The occurrence of congestion corresponding to the second information indicates an area in which level 3 autonomous driving is permitted (enabled) when traveling in congestion on a highway.
[0085] The HCU 160 integrates the first information indicating the occurrence of traffic congestion with the second information to grasp the occurrence status of traffic congestion, and presents the information to the driver (displays it on the display unit) as described below.
[0086] The HCU 160 controls the display state of the display unit. Here, the display unit will be described as using the meter display 120. As shown in Fig. 5, the HCU 160 displays, for example, a vehicle speed value (80 km / h in Fig. 5) in the upper center of the meter display 120, and displays lanes (two lanes in this case) and the vehicle's own vehicle and the preceding vehicle in the lane in real time below the vehicle speed value. In addition, the HCU 160 displays information to be presented to the driver ("There is a traffic jam ahead" in Fig. 5) according to the occurrence status of traffic congestion, as described below, in an area that does not obstruct the display of the vehicle speed value, the vehicle's own vehicle, and the preceding vehicle.
[0087] Hereinafter, the display form (information presentation) on the meter display 120 according to the occurrence state of traffic congestion will be described with reference to the flowcharts of FIG. 3 and FIG.
[0088] (1) Display at driving position A (Fig. 2, Fig. 5) For example, the vehicle is traveling at 80 km / h on a highway, and the vehicle speed and images of the vehicle and the preceding vehicle are displayed on the meter display 120. When the HCU 160 receives information about the occurrence of a traffic jam from the VICS, it displays, for example, "There is a traffic jam ahead" on the meter display 120 to inform the driver of the occurrence of the traffic jam. At this time, the autonomous driving level is Level 2.
[0089] (2) Display at traveling position Ba (Fig. 2, Fig. 6) In step S100, when the vehicle enters a congestion occurrence section based on VICS and the vehicle speed based on the vehicle speed sensor decreases, the HCU 160 changes the vehicle speed value display on the meter display 120 (for example, to about 40 km / h) and further displays "entered a congestion area" (to inform the driver). However, since the vehicle speed at this stage is a driving speed (40 km / h) that indicates congestion in VICS and does not satisfy the vehicle speed condition that allows level 3 autonomous driving in a congestion (for example, a condition of being below 10 km / h), level 2 is maintained as the autonomous driving level.
[0090] At this time, in step S110, HCU 160 also displays "Transition to automated driving level 3 is not possible" on meter display 120 so that the driver does not feel uncomfortable. The driver feels uncomfortable because the automated driving level during congestion has not been transitioned to level 3 even though the VICS information indicates that the vehicle is in a congested section. Note that the congestion occurrence information may be obtained by on-board sensor 81 such as a sensor or a camera instead of based on VICS.
[0091] (3) Display at driving position Bb (Fig. 2, Fig. 7) Next, in step S120, when the vehicle enters a congestion section based on VICS and the vehicle speed based on the vehicle speed sensor decreases, the HCU 160 changes the vehicle speed value display on the meter display 120 (for example, 10 km / h). If the vehicle speed at this time falls below the vehicle speed that permits transition to autonomous driving level 3 (second information), in step S130, the HCU 160 displays "Transition to autonomous driving level 3 possible" on the meter display 120 and also displays "Do you want to execute autonomous driving level 3?" (transition proposal).
[0092] Based on this, the driver performs an input operation on the operation device 150 (such as a steering switch or an operating lever), and level 3 autonomous driving during traffic jams is executed (the driving responsibility is transferred from the driver to the autonomous driving system).
[0093] In addition, with respect to the display format described above, the HCU 160 may display “Transition to autonomous driving level 3 not possible” on the meter display 120 while the conditions for transitioning to autonomous driving level 3 are not met, and may display “Transition to autonomous driving level 3 possible” once the conditions for transitioning to autonomous driving level 3 are met, and may also be configured to execute autonomous driving level 3 when the driver performs an input operation on the operating device 150 to transition.
[0094] (4) Display at driving position C (Fig. 2, Fig. 8) Next, when the autonomous driving level 3 is entered in step S140, the HCU 160 displays information corresponding to the autonomous driving level 3 on the meter display 120 in step S150. The HCU 160 displays, for example, an image of a person relaxing, and displays a second task that is permitted for the driver while the autonomous driving level 3 is being executed. The second task is, for example, watching a movie, watching television, operating a smartphone, reading, etc.
[0095] (5) Display at driving position D (Fig. 2, Fig. 9) Next, in step S160, when the vehicle speed values of the vehicle itself and the preceding vehicle are increasing based on information based on the vehicle speed sensor and the DCM and the traffic congestion situation begins to ease, in step S170, the HCU 160, for example, flashes a display of "Autonomous driving level 3 compatible" to indicate that the vehicle will soon leave the section where autonomous driving level 3 is permitted due to congestion. In addition, the HCU 160 displays "Autonomous driving will be canceled. Please take over driving" and transitions from the autonomous driving mode to the driver driving mode. When the driver performs an input operation for transition to the operation device 150, the autonomous driving mode is transitioned to level 2.
[0096] (6) Display at driving position E (Fig. 2, Fig. 10) Next, when the system transitions to autonomous driving level 2 in step S180, even if the information from VICS is "traffic jam occurs" in step S190 (even if the traffic jam has not ended), the HCU 160 displays the vehicle speed value, images of the vehicle and the preceding vehicle on the meter display 120, and also displays "Autonomous driving level 3 not possible." After step S200, the system returns to step S120.
[0097] On the other hand, if the result of step S180 is negative (the driver has not taken over driving), the HCU 160 proceeds to evacuation driving in step S210 and ends this control flow. When the driver has not taken over driving, for example, the driver may be dozing or suddenly ill, and the HCU 160 safely stops the vehicle on the roadside or the like as evacuation driving.
[0098] If a negative judgment is made in step S190 (information from VICS is "no traffic jam"), and if "traffic jam will occur" is again displayed in step S220, the process proceeds to step S200, and the HCU 160 continues to display "Autonomous driving level 3 not possible." If a negative judgment is made in step S220, the HCU 160 ends this control flow.
[0099] As described above, in this embodiment, the traffic congestion determination device 100 and the HCU 160 of the display control device 101 integrate the first information (traffic congestion information by VICS) acquired by the in-vehicle communication device 50 and the second information (traffic congestion information by DCM and vehicle speed sensor) acquired by the in-vehicle communication device 50 and the in-vehicle sensor 81, and perform a traffic congestion occurrence determination by the first algorithm and a traffic congestion occurrence determination by the second algorithm. This allows the occurrence of traffic congestion to be accurately determined.
[0100] Furthermore, the HCU 160 determines whether or not to display the impossibility of autonomous driving on the meter display (display unit) 120 based on the result of the first algorithm and the result of the second algorithm. This makes it possible to clearly present to the driver that autonomous driving is not possible.
[0101] Furthermore, when the first threshold is satisfied by the first algorithm and the second threshold is not satisfied by the second algorithm, the HCU 160 displays that autonomous driving is not possible. As a result, even if the HCU 160 knows from the first information that a traffic jam has occurred, if the second threshold is not satisfied based on the second information, the HCU 160 displays on the display unit 120 that autonomous driving is not possible, so that the user can be clearly informed that transition to autonomous driving is not yet possible. In other words, the transition to autonomous driving can be communicated to the user in an easy-to-understand manner.
[0102] Furthermore, if the occurrence of traffic congestion based on the first information has not ended after the autonomous driving has ended, the HCU 160 displays that autonomous driving is not possible. This eliminates the need to frequently switch the display to the driver between "autonomous driving possible" and "autonomous driving not possible," which is bothersome to the driver.
[0103] In addition, even if there is no traffic jam based on the first information, if there is another traffic jam based on the first information in the future, the HCU 160 continues to display that automatic driving is not possible. As a result, as in the above, the display to the driver does not need to be frequently switched between "automatic driving possible" and "automatic driving not possible", which is not bothersome to the driver.
[0104] Second embodiment The display form in the second embodiment is shown in Fig. 11 and Fig. 12. In the second embodiment, during autonomous driving, driving-related information for the driver is displayed not only on the meter display 120, which is the main display, but also on the CID 130 (or HUD 110), which is the sub-display. Fig. 11 and Fig. 12 show, for example, a state (driving position Bb) in which the vehicle is about to transition to autonomous driving level 3 while driving on a highway (Fig. 7 in the first embodiment).
[0105] As shown in Fig. 11, for example, at driving position Bb, the information described in Fig. 7 of the first embodiment is displayed on meter display 120. In addition, CID 130 displays map data from locator 30, the expressway on which the vehicle is traveling on the map data, and the vehicle's current position, and also displays an approximate time required until the vehicle can transition to an autonomous driving level. Fig. 11 shows a case where the display contents on meter display 120 and CID 130 are different.
[0106] As shown in FIG. 12, the display contents of the meter display 120 and the CID 130 may be the same.
[0107] In this way, by displaying various relevant information to the driver using multiple display units during autonomous driving, the driver is able to ensure that no information is missed and can also reliably understand whether or not surrounding monitoring is required depending on the level of autonomous driving.
[0108] Third embodiment In the third embodiment, the conditions for starting autonomous driving are changed. The HCU 160 further acquires third information, which is different from the second information (vehicle speed value), as an autonomous driving start condition from the surroundings monitoring sensor 40 as an acquisition unit and the locator 30. As described above, the third information is, for example, information that the road has two or more lanes, that there are other vehicles around the vehicle (in the same lane and the adjacent lane), that there is a median strip in the center of the road, and that high-precision map data is held.
[0109] When the first threshold (traffic jam information from VICS) and the second threshold (vehicle speed value from the vehicle speed sensor) are satisfied and the third information is also satisfied, the HCU 160 displays on the display unit that automatic driving is possible or displays the start of automatic driving. This improves the reliability of grasping the occurrence of traffic jams.
[0110] (Fourth embodiment) In the fourth embodiment, the conditions for starting the autonomous driving are further changed. The HCU 160 further acquires fourth information, which is an autonomous driving start condition not limited to when there is a traffic jam, from the surroundings monitoring sensor 40 as an acquisition unit. As described above, the fourth information is, for example, information indicating a section on a highway where constant speed driving, following driving, LTA (lane keeping driving), etc. are possible without traffic jams.
[0111] When the vehicle is in a state indicated by the fourth information, the HCU 160 displays on the display unit that autonomous driving is possible regardless of the first and second information. This makes it possible to present to the driver a wide range of options for transitioning to autonomous driving, not limited to autonomous driving during traffic jams.
[0112] (Other embodiments) During autonomous driving, as described in the first embodiment (FIG. 8), a second task is permitted, so that, for example, television or a movie may be displayed on one of the multiple display devices (CID130) as shown in FIG. 13 and FIG. 14.
[0113] Also, instead of displaying "Level 3 autonomous driving not possible" as described in the first embodiment (FIGS. 6 and 10), it may be possible to display what the driver must do or what the driver must not do, such as "Peripheral monitoring required" or "Second task not possible."
[0114] Also, instead of displaying "Transition to autonomous driving level 3 possible" as described in the first embodiment (Figure 7), it may be possible to display what the driver does not need to do or what the driver can do, such as "No need to monitor the surroundings" or "Second task possible".
[0115] The disclosure in this specification and drawings, etc. is not limited to the exemplified embodiments. The disclosure includes the exemplified embodiments and modifications by those skilled in the art based thereon. For example, the disclosure is not limited to the combination of parts and / or elements shown in the embodiments. The disclosure can be implemented by various combinations. The disclosure can have additional parts that can be added to the embodiments. The disclosure includes the omission of parts and / or elements of the embodiments. The disclosure includes the substitution or combination of parts and / or elements between one embodiment and another embodiment. The disclosed technical scope is not limited to the description of the embodiments. Some disclosed technical scopes are indicated by the description of the claims, and should be interpreted as including all modifications within the meaning and scope equivalent to the description of the claims.
[0116] The control unit and the methodology described in this disclosure are implemented by a special purpose computer provided by configuring a processor and memory programmed to execute one or more functions embodied in a computer program.
[0117] However, the controller and the techniques described herein may also be implemented in a special purpose computer provided by configuring a processor with one or more dedicated hardware logic circuits.
[0118] Alternatively, the control unit and the techniques described herein may be implemented by one or more special purpose computers configured with a processor and memory programmed to perform one or more functions, in combination with a processor configured with one or more hardware logic circuits.
[0119] The computer program may also be stored in a computer-readable non-transitory tangible recording medium as instructions to be executed by a computer. [Explanation of symbols]
[0120] 50 In-vehicle communication device (acquisition part) 81 Vehicle-mounted sensor (acquisition unit) 100 Traffic jam judgment device for vehicles 101 Vehicle display control device 120 Meter display (display unit) 130 Center information display (sub-display section) 160 Human Machine Interface Control Unit (Control Unit, Display Control Unit)
Claims
1. an acquisition unit (50, 81) that acquires first information indicating the occurrence of a traffic jam when the traveling speed of another vehicle ahead of the vehicle or the vehicle speed of the vehicle falls below a predetermined first threshold, and second information indicating the occurrence of the traffic jam when the traveling speed or the vehicle speed of the vehicle falls below a second threshold, which is a condition for starting automatic driving by an automatic driving function of the vehicle during the traffic jam; a control unit (160) that executes a first algorithm for determining the occurrence of the congestion using the first threshold value and a second algorithm for determining the occurrence of the congestion using the second threshold value; The control unit is a traffic congestion judgment device for a vehicle that determines whether or not to display a message indicating that autonomous driving is not possible on a display unit (120) based on the results of the first algorithm and the results of the second algorithm.
2. A vehicle display control device that controls a display unit (120) that displays information about a vehicle, an acquisition unit (50, 81) that acquires first information indicating the occurrence of a traffic jam due to the traveling speed of another vehicle ahead of the vehicle or the vehicle speed of the vehicle falling below a predetermined first threshold, and second information indicating whether the autonomous driving can be performed based on a second threshold, which is a condition for starting autonomous driving in the traffic jam by an autonomous driving function of the vehicle, and the traveling speed or the vehicle speed of the vehicle; and a display control unit (160) that permits the display unit to display a message indicating that the autonomous driving is not possible when the driving speed or the vehicle speed of the vehicle is not below at least one of the first threshold value in the first information or the second threshold value in the second information.
Citation Information
Patent Citations
Running support road system
JP2002269683A
Vehicular control device
JP2005324661A
Congestion avoidance system, server, information terminal device, and program
JP2017142079A
Vehicle control system, vehicle control method and vehicle control program
JP2017200786A
Information notification device, information notification system, information notification method, and information notification program
JP2019036012A
