Driving support function suggestion system, and suggestion method for driving support function suggestion system
The system addresses the issue of bothersome suggestions by using probe vehicle data to propose driving support functions only when relevant, enhancing user experience.
Patent Information
- Application Number
- JP2023073003
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-27
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2043-04-27
AI Technical Summary
Conventional driving support function proposal systems fail to consider driver preferences, leading to unnecessary and bothersome suggestions.
A system that proposes driving support functions based on the operation history of probe vehicles, considering factors like vehicle position, speed, and driver behavior to avoid suggesting functions when not needed.
Prevents drivers from feeling annoyed by unnecessary suggestions by tailoring proposals to their needs and circumstances.
Smart Images

Figure 2024158113000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a driving assistance function proposal system and a proposal method for the driving assistance function proposal system. [Background technology]
[0002] Japanese Patent Application Laid-Open Publication No. 2019-74803 is a known technical document related to a driving assistance function suggestion system. This publication discloses a server device that acquires vehicle information as big data from multiple vehicles and stores recommended driving conditions that recommend the use of vehicle functions possessed by the vehicles. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2019-74803 A Summary of the Invention [Problem to be solved by the invention]
[0004] In the conventional server device described above, when the driving situation of the vehicle becomes a recommended driving situation determined based on big data acquired from multiple vehicles, the server device proposes vehicle functions corresponding to the recommended driving situation to the driver of the vehicle. Therefore, the proposal of vehicle functions may not match the preferences of the driver of the vehicle, and the driver may feel annoyed by the unnecessary proposal. [Means for solving the problem]
[0005] One aspect of the present invention is a driving assistance function proposal system that acquires operation history of driving assistance functions including location information from multiple probe vehicles, and when it is determined that the proposed vehicle will reach a proposed location set based on the operation history, suggests to the driver of the proposed vehicle the use of a driving assistance function corresponding to the proposed location; if the frequency or number of prior uses of the driving assistance function of the proposed vehicle at the proposed location is equal to or greater than a no-suggestion threshold, the system does not suggest to the driver the use of the driving assistance function.
[0006] According to a driving assistance function proposal system of one embodiment of the present invention, it is assumed that the driver of the vehicle for which the proposal is made does not understand the usefulness of the driving assistance function at the proposed location before implementing the driving assistance function, and therefore it is possible to prevent the driver from feeling annoyed by unnecessary suggestions.
[0007] In the above-described driving assistance function suggestion system, if the turn signal of the proposal target vehicle determined to reach the proposal point is on, it is not necessary to suggest to the driver that the driving assistance function be used. According to this driving assistance function suggestion system, when the turn signal of the vehicle for which the suggestion is being made is on, it is assumed that the driver is consciously intending to make a right turn, left turn, or change lanes. Therefore, by not suggesting the use of a driving assistance function, it is possible to prevent the suggestion from being an annoyance to the driver.
[0008] In the above-described driving assistance function proposal system, if the vehicle speed of the proposal target vehicle determined to reach the proposal point is equal to or greater than the vehicle speed threshold, the use of the driving assistance function does not need to be proposed to the driver. According to this driving assistance function suggestion system, when the vehicle for which the suggestion is being made is traveling at a high speed, the driver may be in a hurry to reach the destination, so by not suggesting the use of driving assistance functions, the system can prevent the suggestion from being an annoyance to the driver.
[0009] In the above-mentioned driving assistance function proposal system, even if the vehicle speed of the proposed vehicle determined to reach the proposed location is equal to or greater than a vehicle speed threshold, the use of the driving assistance function may be suggested to the driver if the post-proposal assistance start frequency, which is the frequency at which the driver starts using the driving assistance function after a proposal at the proposed location, is equal to or greater than a proposal-dependent threshold. According to this driving assistance function suggestion system, even if the driver is in a hurry to reach the destination, it is assumed that the driver will rely on suggestions of driving assistance functions, and therefore the driver is unlikely to find suggestions to use driving assistance functions bothersome. Therefore, by making the suggestions, it is possible to promote the use of driving assistance functions.
[0010] In the above-mentioned driving assistance function proposal system, if there is an uninstalled function, which is a driving assistance function that is not installed in the proposed vehicle and can be purchased by downloading from a server for the proposed vehicle, when it is determined that the proposed vehicle is located at a proposal location associated with the uninstalled function, the driver may be suggested to purchase the uninstalled function. According to this driving assistance function proposal system, it is possible to propose to the driver the purchase of a function that has not yet been installed at a proposal point where the driver can concretely imagine the benefits of purchasing the driving assistance function.
[0011] Another aspect of the present invention is a proposal method for a driving assistance function proposal system that acquires operation history of driving assistance functions including position information from multiple probe vehicles, and when it is determined that the proposed target vehicle will reach a proposed location set based on the operation history, suggests to the driver of the proposed target vehicle the use of a driving assistance function corresponding to the proposed location, and if the frequency of use of the driving assistance function of the proposed target vehicle at the proposed location is equal to or greater than the vehicle usage determination threshold, does not suggest to the driver the use of the driving assistance function.
[0012] According to the proposal method of the driving assistance function proposal system of another aspect of the present invention, it is assumed that the driver does not understand the usefulness of the driving assistance function at the proposed location before executing the driving assistance function, and therefore it is possible to prevent the driver from feeling annoyed by unnecessary suggestions. Effect of the Invention
[0013] According to one aspect of the present invention, it is possible to prevent the driver from feeling annoyed by the suggestion of unnecessary driving assistance functions. [Brief description of the drawings]
[0014] [Figure 1] FIG. 2 is a block diagram showing a server of the driving assistance function proposal system according to one embodiment. [Diagram 2] FIG. 2 is a block diagram showing an example of a configuration of a server. [Diagram 3] FIG. 2 is a block diagram showing an example of a configuration of a proposed vehicle. [Figure 4] FIG. 13 is a diagram for explaining an example of a proposal for a driver to use a driving assistance function. [Diagram 5] 11 is a flowchart illustrating an example of a proposal point setting process of the driving assistance function proposal system. [Figure 6] 4 is a flowchart showing an example of a driving assistance function proposal process of the driving assistance function proposal system. [Figure 7] 10 is a flowchart showing an example of an addition determination process that can be added to the driving assistance function proposal process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0015] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
[0016] Fig. 1 is a block diagram showing a server 10 of a driving assistance function proposal system 100 according to an embodiment. As shown in Fig. 1, the driving assistance function proposal system 100 includes a server 10 communicably connected to a probe vehicle 2 and a proposal target vehicle 3. The driving assistance function proposal system 100 is a system that proposes use of a driving assistance function to the driver of the proposal target vehicle 3 by using information (big data) collected from the probe vehicle 2.
[0017] In the driving assist function proposal system 100, a plurality of probe vehicles 2 (probe vehicles 2A to 2Z) and a proposal target vehicle 3 are communicably connected to a server 10 via a network N. The network N is a wireless communication network such as the Internet.
[0018] The driving assistance function is a function that assists the driver in driving operations. The driving assistance function includes, for example, functions related to ADAS [Advanced Driver Assistance Systems]. The driving assistance function may include at least one of ACC [Adaptive Cruise Control], LKA [Lane Keeping Assist], automatic overtaking function, automatic merging function, collision mitigation brake (e.g., pre-crash safety), rear side warning function (e.g., blind spot monitor), night vision function (e.g., night view), sign recognition function (e.g., road sign assist), driver abnormality stopping support, driver abnormality response function, headlight automatic adjustment support (e.g., adaptive front lighting), parking support (e.g., intelligent parking assist), lane change support, deceleration and steering support for obstacles (e.g., proactive driving assist), preceding vehicle departure notification function (e.g., preceding vehicle departure alarm), crossing vehicle notification function (e.g., front cross traffic alert), deceleration support function, headlamp light distribution control, parking support, blind spot support, pedal misapplication prevention, reverse driving prevention, and the like. The deceleration support function is executed at locations where deceleration is required, such as intersections, roundabouts, and points where emergency deceleration is frequent. The headlamp light distribution control includes at least one of automatic on / off switching of the headlamps, automatic switching between high beam and low beam, and spot light distribution. The driving support function may include a package (e.g., advanced drive) that combines multiple functions.
[0019] The probe vehicle 2 is a vehicle that is the subject of information collection regarding the proposal of a driving assistance function for the vehicle. The probe vehicle 2 is not a fully automated driving vehicle, but a vehicle that is driven by a driver. The probe vehicles 2 do not need to be vehicles with the same configuration, and may be of different models. The probe vehicle 2 has a function to recognize the position information of the vehicle on a map using a GNSS [Global Navigation Satellite System] or the like. In addition, the probe vehicle 2 has a function to store various driving assistance functions and the operation history of each driving assistance function.
[0020] The operation history is acquired in association with the position information of the probe vehicle 2. The operation history includes the operation start position and the operation end position of the driving assistance function. The operation history also includes the usage time of the driving assistance function. The operation history is acquired for each type of driving assistance function.
[0021] The probe vehicle 2 transmits various vehicle information including the operation history of the driving assistance function to the server 10. The vehicle information may include an identification ID [identification] for individually identifying the probe vehicle 2. The identification ID may be associated with information such as the vehicle type of the probe vehicle 2 and available driving assistance functions. The number of probe vehicles 2 connected to the server 10 is not particularly limited. The number of probe vehicles 2 may be one, ten, or even a hundred or more. The probe vehicles 2 are not limited to vehicles dedicated to information collection, and may include general vehicles that have agreed to provide information. The probe vehicles 2 may be composed of only general vehicles.
[0022] The proposed vehicle 3 is a vehicle for which a driving assistance function is proposed, and is a vehicle for which the driver has permitted the driving assistance function proposal service. The proposed vehicle 3 is not particularly limited to a particular vehicle type as long as the driving assistance function is available. The proposed vehicle 3 connected to the server 10 may be one vehicle, ten vehicles, or even a hundred or more vehicles. The proposed vehicle 3 may also serve as the probe vehicle 2. The proposed vehicle 3 may be a vehicle for which a new driving assistance function can be purchased and downloaded from the server 10.
[0023] The driving assistance function proposal system 100 acquires proposal target vehicle information including location information from the proposal target vehicle 3. The driving assistance function proposal system 100 proposes use of a driving assistance function to the driver of the proposal target vehicle 3 according to the location of the proposal target vehicle 3.
[0024] [Server configuration] Hereinafter, the configuration of the server 10 of the driving assistance function proposal system 100 will be described with reference to FIG. 2. FIG. 2 is a block diagram showing an example of the configuration of the server. The server 10 is provided in a facility such as an information management center. The server 10 does not necessarily have to be provided in a facility, and may be mounted on a moving object such as a vehicle or a ship. The server 10 may be formed on a cloud. The server 10 may be composed of a plurality of server computers.
[0025] As shown in FIG. 2, the server 10 is configured as a general computer including a processor 11, a storage unit 12, a communication unit 13, and a user interface 14.
[0026] The processor 11 controls the server 10 by running, for example, an operating system. The processor 11 is an arithmetic unit such as a CPU (Central Processing Unit) including a control device, an arithmetic device, a register, etc. The processor 11 controls a storage unit 12, a communication unit 13, and a user interface 14. The storage unit 12 is configured to include at least one of a memory and a storage. The memory is a recording medium such as a ROM (Read Only Memory) or a RAM (Random Access Memory). The storage is a recording medium such as a HDD (Hard Disk Drive).
[0027] The communication unit 13 is a communication device for performing communication via the network N. A network device, a network controller, a network card, etc. can be used as the communication unit 13. The user interface 14 is a device including output devices such as a display and a speaker, and an input device such as a touch panel.
[0028] The server 10 is connected to an operation history database 15. The operation history database 15 is a database that stores operation history of the driving assistance function acquired from the probe vehicle 2. The operation history database 15 may store various information such as an identification ID of the probe vehicle 2 in addition to the operation history. The operation history database 15 may have the same configuration as a well-known database.
[0029] Next, a functional configuration of the processor 11 will be described. As shown in Fig. 3, the processor 11 has an operation history acquisition unit 11a, a proposal location setting unit 11b, a proposal target vehicle information acquisition unit 11c, and a driving support function proposal unit 11d. Note that some of the functions of the processor 11 may be executed in the proposal target vehicle 3.
[0030] The operation history acquisition unit 11a acquires the operation history of the driving assistance function transmitted from the probe vehicle 2. The operation history acquisition unit 11a stores the operation history of the driving assistance function in the operation history database 15. The operation history acquisition unit 11a may store the operation history in the operation history database 15 after classifying data such as the type of driving assistance function operated by the probe vehicle 2, the use time of the driving assistance function, and the use section of the driving assistance function.
[0031] The proposed point setting unit 11b sets a proposed point based on the operation history of the probe vehicle 2 stored in the operation history database 15. A proposed point is a point on a map used to propose the use of a driving assistance function. A proposed point is set for each type of driving assistance function. The proposed point may be set by distinguishing the traveling direction of the road, or may be set for each lane.
[0032] Specifically, the proposed location setting unit 11b judges whether or not there is a candidate location where the usage frequency of the driving assistance function of the probe vehicles 2 is equal to or greater than the frequency judgment threshold based on the operation history. The usage frequency corresponds to the number of probe vehicles 2 that have used the driving assistance function among the probe vehicles 2 that have passed the location. The usage frequency is calculated for each type of driving assistance function.
[0033] A candidate point is a point that is a candidate for a proposed point. The candidate points may be narrowed down to a connecting point of a road, a start point of a curve, an entrance point of an intersection, a point where congestion is likely to occur, etc., or may be narrowed down statistically to a point where the use of a driving assistance function is frequently started based on an operation history. The frequency determination threshold is a threshold value that is set in advance. The frequency determination threshold may be set to a different value for each type of driving assistance function. Hereinafter, the threshold value described in this embodiment means a threshold value having a preset value.
[0034] In addition, the calculation of the use frequency may include conditions according to the type of driving support function. For example, in the case of a night vision function, the proposed location setting unit 11b may determine the candidate locations using the use frequency limited to nighttime.
[0035] When it is determined that the above-mentioned candidate point exists, the proposed point setting unit 11b determines whether the average usage time of the driving support function of the probe vehicle 2 at the candidate point is equal to or longer than a predetermined time. The average usage time of the driving support function is the average time that the driving support function used at the proposed point is continuously used. The predetermined time may be set to a different value for each type of driving support function. The proposed point setting unit 11b sets the candidate point where the average usage time of the driving support function is equal to or longer than a predetermined time as a proposed point.
[0036] In addition, the proposed point setting unit 11b may set a road where the usage frequency of the driving support function is equal to or greater than a frequency judgment threshold and the average usage time of the driving support function is equal to or greater than a predetermined time as a proposed target road. The proposed point setting unit 11b may set an entrance point of the proposed target road from another road as a proposed point. The proposed target may be an intersection instead of a road. The method of setting the proposed point is not limited to the above. Note that the server 10 does not necessarily need to have the proposed point setting unit 11b. The proposed point may be set in another server that does not constitute the driving support function proposal system 100.
[0037] The proposed target vehicle information acquisition unit 11c acquires proposed target vehicle information transmitted from the proposed target vehicle 3. The proposed target vehicle information includes the identification ID and location information of the proposed target vehicle 3. The proposed target vehicle information includes information on the driving assistance functions installed in the proposed target vehicle 3. The proposed target vehicle information also includes the operation history of the driving assistance functions associated with the location information of the proposed target vehicle 3. The proposed target vehicle information may include the driver's driving tendencies, and may include driver preference information regarding the driver's preferences for driving assistance functions. The proposed target vehicle information may include vehicle type information of the proposed target vehicle 3.
[0038] The driving support function proposal unit 11d proposes the use of driving support functions to the driver of the proposal target vehicle 3. The driving support function proposal unit 11d does not propose the use of driving support functions that are already being used at the present time. The driving support function proposal unit 11d also does not propose the use of driving support functions that the driver is permitted to start using automatically at the system's discretion. In addition, the driving support function proposal unit 11d does not propose the use of driving support functions when the proposal target vehicle 3 is performing autonomous driving and the driver is not driving.
[0039] The driving assistance function proposal unit 11d determines whether the proposal target vehicle 3 will reach the proposed point based on the position information of the proposal target vehicle 3 and the proposed point set by the proposal point setting unit 11b. For example, the driving assistance function proposal unit 11d determines that the proposal target vehicle 3 will reach the proposed point when the distance between the proposed point and the proposal target vehicle 3 is less than a distance threshold. The driving assistance function proposal unit 11d may determine that the proposal target vehicle 3 will reach the proposed point when the remaining time until the proposal target vehicle 3 reaches the proposed point is less than a remaining time threshold. The distance threshold and the remaining time threshold may be set to different values depending on the type of driving assistance function associated with the proposed point.
[0040] When it is determined that the proposal target vehicle 3 will reach the proposed point, the driving assistance function proposal unit 11d determines whether or not the driving assistance function for the proposed point is not installed in the proposal target vehicle 3. The driving assistance function proposal unit 11d makes the above determination by comparing the driving assistance function corresponding to the proposed point with the driving assistance function installed in the proposal target vehicle 3.
[0041] When it is determined that the driving assistance function at the proposed location is not installed, the driving assistance function proposal unit 11d may determine whether the driving assistance function at the proposed location is an uninstalled function that can be purchased by download from the server 10 for the proposed vehicle 3. The driving assistance function proposal unit 11d makes the above determination based on a pre-stored list of driving assistance functions available for download sale and driving assistance functions that can be installed by download and are linked to the identification ID of the proposed vehicle 3. Note that the server that sells the driving assistance function is not limited to the server 10, and may be a different server.
[0042] When the driving assistance function proposal unit 11d determines that the driving assistance function at the proposal point is an uninstalled function that can be purchased by downloading, the driving assistance function proposal unit 11d may propose the purchase of the uninstalled function to the driver of the proposal target vehicle 3. The driving assistance function proposal unit 11d proposes the purchase of the uninstalled function to the driver through a display, a speaker, or the like of the proposal target vehicle 3 by transmitting purchase proposal information to the proposal target vehicle 3. This makes it possible to propose the purchase of the uninstalled function to the driver at the proposal point where the advantage of purchasing the driving assistance function can be specifically imagined.
[0043] When the driving assistance function proposal unit 11d determines that the driving assistance function at the proposed location is installed in the proposal target vehicle 3, it determines whether the frequency of prior use of the driving assistance function of the proposal target vehicle 3 at the proposed location is greater than or equal to the proposal unnecessary threshold.
[0044] The pre-use frequency corresponds to the ratio of the number of times the proposal target vehicle 3 has used a driving assistance function (a driving assistance function associated with the proposed location) in advance to the number of times the proposal target vehicle 3 has passed the proposed location. The no-proposal threshold is set to a value that can determine that the proposal is unnecessary because, for example, the driver understands the usefulness of the driving assistance function at the proposed location but is not using the driving assistance function this time. The pre-use frequency may be updated at regular intervals.
[0045] The driving assistance function proposal unit 11d may use the number of advance uses instead of the frequency of advance use. The driving assistance function proposal unit 11d determines whether the number of advance uses of the driving assistance function of the proposal target vehicle 3 at the proposed point is less than the proposal no longer necessary threshold. The number of advance uses is the number of times that the proposal target vehicle 3 has used the driving assistance function (the driving assistance function associated with the proposed point) in advance when passing through the proposed point. The number of advance uses may be updated at regular intervals. When both the frequency of advance use and the number of advance uses are used, the corresponding values of the proposal no longer necessary threshold will be different.
[0046] When the driving support function suggestion unit 11d determines that the frequency or number of prior uses of the driving support function of the proposal target vehicle 3 at the proposal point is equal to or greater than the proposal unnecessary threshold, it does not suggest to the driver of the proposal target vehicle 3 that the driving support function be used, since it is highly likely that the driver has understood the usefulness of the driving support function at the proposal point but has not executed the driving support function this time. This makes it possible to suppress making unnecessary suggestions to the driver.
[0047] In addition, if the proposed vehicle 3 has a personal authentication function for the driver, the driving assistance function proposal unit 11d may acquire the driver's personal authentication information as the proposed vehicle information, and count the frequency or number of pre-use of the driving assistance function for each driver.
[0048] When the driving assistance function proposal unit 11d determines that the advance use frequency or advance use count of the driving assistance function of the proposal target vehicle 3 at the proposal point is not less than the proposal unnecessary threshold, the driving assistance function proposal unit 11d proposes the use of the driving assistance function to the driver of the proposal target vehicle 3. The driving assistance function proposal unit 11d proposes the use of the driving assistance function to the driver through a display, speaker, or the like of the proposal target vehicle 3 by transmitting proposal information to the proposal target vehicle 3.
[0049] The driving assistance function suggestion unit 11d may notify the driver of the frequency or number of probe vehicles 2 using the driving assistance function at the proposed point. The frequency of use corresponds to the ratio of the number of times the driving assistance function (the driving assistance function associated with the proposed point) is used among the number of times the probe vehicle 2 passes through the proposed point. The number of vehicles using the driving assistance function is the number of probe vehicles 2 that used the driving assistance function associated with the proposed point when passing through the proposed point. The frequency of use and the number of vehicles using the driving assistance function may be updated at regular intervals. In this way, by specifically notifying the driver of the proposed vehicle 3 of the frequency of use and the number of vehicles using the driving assistance function, the hurdle for the driver to try using the driving assistance function can be lowered.
[0050] The driving support function suggestion unit 11d may make a decision to suggest a driving support function based on the weather, the day / night distinction, the traffic congestion around the proposal target vehicle 3, and the like. The driving support function suggestion unit 11d may change the conditions according to the type of driving support function. When the driving support function associated with the proposed location is a nighttime night vision function, the driving support function suggestion unit 11d may suggest use to the driver when it is determined that the day / night distinction is nighttime.
[0051] The driving assistance function suggestion unit 11d may make a decision to suggest a driving assistance function based on the vehicle speed and illumination of a turn signal of the proposal target vehicle 3. When the turn signal of the proposal target vehicle 3 that is determined to reach the proposal point is illuminated, the driving assistance function suggestion unit 11d may not suggest to the driver the use of the driving assistance function. When the turn signal of the proposal target vehicle 3 is illuminated, it is considered that the driver is consciously intending to perform a driving operation such as turning right or left, or changing lanes. Therefore, by not suggesting the use of the driving assistance function, it is possible to prevent the suggestion from being bothersome to the driver.
[0052] The driving support function suggestion unit 11d may suggest the use of some types of driving support functions even when the turn indicator of the proposal target vehicle 3 is on. For example, the driving support function suggestion unit 11d may suggest the use of a crossing vehicle notification function when turning right at an intersection in a country or region where traffic is on the left. The driving support function suggestion unit 11d may suggest the use of a crossing vehicle notification function when turning left at an intersection in a country or region where traffic is on the right.
[0053] The driving assistance function suggestion unit 11d may be configured not to suggest to the driver the use of the driving assistance function when the vehicle speed of the proposal target vehicle 3 determined to reach the proposal point is equal to or higher than the vehicle speed threshold.
[0054] The vehicle speed threshold may be set to a different value depending on the proposed location. The vehicle speed threshold may be set to a different value for expressways and general roads. The vehicle speed threshold may be set to an appropriate value for determining that the driver of the proposed vehicle 3 is in a hurry based on the driving history of the driver. The vehicle speed threshold may be set to a value obtained by adding a predetermined value to the average vehicle speed of the driver. If the vehicle speed of the proposed vehicle 3 is high, the driver may be in a hurry to arrive at the destination, so by not suggesting the use of the driving assistance function, it is possible to prevent the suggestion from being an annoyance to the driver.
[0055] In addition, even if the vehicle speed of the proposal target vehicle 3 is equal to or higher than the vehicle speed threshold, if the post-proposal support start frequency, which is the frequency at which the driver starts using the driving support function after the proposal at the proposal point, is equal to or higher than the proposal dependency threshold, the driving support function proposal unit 11d may propose the use of the driving support function. The value of the proposal dependency threshold is not particularly limited. The proposal dependency threshold may be set to an appropriate value for determining that the driver relies on the proposal to use the driving support function.
[0056] The post-proposal support start frequency is the number of times that the driver of the proposal target vehicle 3 started using the driving support function after the proposal was made to the driver of the proposal target vehicle 3 at the proposal point. As a result, if the driver frequently relies on the proposal of the driving support function, the driver is likely not to find the proposal bothersome, so the use of the driving support function can be promoted by making the proposal. Note that, when the driving support function proposal unit 11d has acquired the driver's personal authentication information as the proposal target vehicle information, the driving support function proposal unit 11d may calculate the post-proposal support start frequency for each driver.
[0057] [Proposed vehicle configuration] Next, an example of the configuration of the proposal target vehicle 3 will be described with reference to Fig. 3. Fig. 3 is a block diagram showing an example of the configuration of the proposal target vehicle 3.
[0058] As shown in Fig. 3, the proposed vehicle 3 includes an ECU [Electronic Control Unit] 30. The ECU 30 is an electronic control unit having a CPU, a ROM, a RAM, and the like. For example, the ECU 30 loads a program stored in the ROM into the RAM, and executes the program loaded into the RAM with the CPU, thereby achieving various functions. The ECU 30 may be composed of multiple electronic units.
[0059] The ECU 30 is connected to a GNSS (Global Navigation Satellite System) receiver 21 , an external sensor 22 , an internal sensor 23 , a map database 24 , a communication unit 25 , an HMI (Human Machine Interface) 26 , and an actuator 27 .
[0060] The GNSS receiver 21 measures the position of the proposal target vehicle 3 (for example, the latitude and longitude of the proposal target vehicle 3) by receiving signals from three or more positioning satellites. The GNSS receiver 21 transmits the measured position information of the proposal target vehicle 3 to the ECU 30. The GNSS receiver 21 may be a GPS [Global Positioning System] receiver.
[0061] The external sensor 22 is a detection device that detects the external environment of the proposal target vehicle 3. The external sensor 22 includes at least one of a camera and a radar sensor. The camera is an imaging device that captures an image of the external environment of the proposal target vehicle 3. The radar sensor is a detection device that detects objects around the proposal target vehicle 3 using radio waves (e.g., millimeter waves) or light. The radar sensor includes, for example, a millimeter wave radar or a lidar (Light Detection and Ranging: LIDAR).
[0062] The internal sensor 23 is a detection device that detects the vehicle state of the proposal target vehicle 3. The internal sensor 23 includes a vehicle speed sensor, an acceleration sensor, and a yaw rate sensor. The internal sensor 23 may include a turn signal detection unit that detects whether or not the turn signal of the proposal target vehicle 3 is on. The internal sensor 23 may include a driving operation detection unit that detects the driving operation (steering, accelerator operation, brake operation, shift lever operation, etc.) of the driver. The internal sensor 23 may detect the on / off state of various driving assistance functions.
[0063] The map database 24 is a database that stores map information. The map database 24 is formed in a storage device such as a HDD mounted on the proposal target vehicle 3. The map information includes road position information, road shape information (e.g., curvature information), and intersection and branch point position information. The map information may include traffic regulation information such as legal speed limits associated with the position information.
[0064] The communication unit 25 is a communication device that controls wireless communication with the outside of the proposal target vehicle 3. The communication unit 25 transmits and receives various information to the server 10 via the network N. The communication unit 25 transmits various information to the server 10 in response to a signal from the ECU 30.
[0065] The HMI 26 is an interface for inputting and outputting information between the ECU 30 and the driver. The HMI 26 includes, for example, a display and a speaker provided in the vehicle cabin. The HMI 26 outputs images from the display and sounds from the speaker in response to a control signal from the ECU 30. The display may be a HUD [Head Up Display] or a display of a mobile terminal of the driver connected to the ECU 30 for communication.
[0066] The actuators 27 are devices used to control the proposal target vehicle 3. The actuators 27 include a drive actuator that controls the engine output or the motor output, a brake actuator, and a steering actuator. The actuators 27 execute various driving assistance functions by controlling the traveling of the proposal target vehicle 3 in response to a control signal from the ECU 30.
[0067] Next, a description will be given of the functional configuration of the ECU 30. As shown in Fig. 3, the ECU 30 has a vehicle position recognition unit 31, a vehicle information transmission unit 32, a proposal unit 33, and a driving support execution unit .
[0068] The vehicle position recognition unit 31 recognizes the position on the map of the proposal target vehicle 3 based on the position information of the GNSS receiver unit 21 and the map information of the map database 24. The vehicle position recognition unit 31 may recognize the position on the map of the proposal target vehicle 3 by SLAM [Simultaneous Localization and Mapping] technology using position information of fixed obstacles such as utility poles included in the map information of the map database 24 and the detection results of the external sensor 22. The vehicle position recognition unit 31 may recognize the position on the map of the proposal target vehicle 3 by other well-known methods.
[0069] The vehicle information transmission unit 32 transmits various information including the position information of the proposed vehicle 3 to the server 10 as proposed vehicle information. The proposed vehicle information also includes the identification ID of the proposed vehicle 3. The proposed vehicle information also includes the operation history of the driving assistance function associated with the position information. The proposed vehicle information may include vehicle speed information of the proposed vehicle 3 and may include turn signal illumination information. The proposed vehicle information may include information on the post-proposal assistance start frequency, which is when the driver starts using the driving assistance function after the proposal. The vehicle information transmission unit 32 transmits other necessary information to the server 10.
[0070] The suggestion unit 33 suggests to the driver the use of the driving support function based on an instruction from the server 10. The suggestion unit 33 suggests to the driver the use of the driving support function through a display, a speaker, etc. by transmitting a control signal to the HMI 26.
[0071] Fig. 4 is a diagram for explaining an example of a proposal to a driver to use a driving assistance function. As shown in Fig. 4, the proposal unit 33 proposes to the driver of the proposal target vehicle 3, for example by voice or text display, that many drivers activate Advanced Drive for an average of 5 minutes or more on a road including the proposed point. Note that the illustrated Advanced Drive includes some of a plurality of driving assistance functions as a package. The proposal to use the driving assistance function also includes the proposal as a package.
[0072] The suggestion unit 33 may have a voice recognition function. When the suggestion unit 33 recognizes a voice instruction of the driver to use a driving support function via a microphone of the HMI 26, the suggestion unit 33 may start the driving support function.
[0073] The driving assistance execution unit 34 executes driving assistance functions of the proposal target vehicle 3. The driving assistance execution unit 34 executes various driving assistance functions by transmitting control signals to the HMI 26 or the actuator 27. A detailed description of the execution of the driving assistance functions will be omitted.
[0074] In addition, the driving assistance function proposal system 100 may cause at least a part of the functions of the driving assistance function proposal unit 11d of the server 10 to be performed on the proposal target vehicle 3 side. The proposal unit 33 of the proposal target vehicle 3 may determine whether or not the proposal target vehicle 3 will reach the proposal point by acquiring information on the proposal point from the server 10. The proposal unit 33 may determine whether or not the driving assistance function of the proposal point is not yet installed in the proposal target vehicle 3 based on the driving assistance function associated with the proposal point. The proposal unit 33 may determine whether or not the driving assistance function of the proposal point is an uninstalled function that can be purchased by download from the server 10 for the proposal target vehicle 3 by communication with the server 10. When the proposal unit 33 determines that the driving assistance function of the proposal point is an uninstalled function that can be purchased by download, it may propose to the driver of the proposal target vehicle 3 to purchase the uninstalled function.
[0075] In addition, when the proposal unit 33 determines that the driving support function at the proposed location is installed in the proposal target vehicle 3, the proposal unit 33 may determine whether or not the pre-use frequency of the driving support function of the proposal target vehicle 3 at the proposed location is less than the proposal unnecessary threshold. When the proposal unit 33 determines that the pre-use frequency or the pre-use count of the driving support function is not less than the proposal unnecessary threshold, the proposal unit 33 may propose the use of the driving support function to the driver of the proposal target vehicle 3, and when the proposal unit 33 determines that the pre-use frequency or the pre-use count of the driving support function is less than the proposal unnecessary threshold, the proposal unit 33 may not propose the use of the driving support function to the driver of the proposal target vehicle 3. In addition, the proposal unit 33 may be capable of executing all the functions of the driving support function proposal unit 11d. In the driving support function proposal system 100, when the proposal unit 33 is capable of executing all the functions of the driving support function proposal unit 11d described above, the server 10 does not need to have the driving support function proposal unit 11d.
[0076] [Processing of driving assistance function proposal system] Next, the processing of the driving support function proposal system 100 in this embodiment will be described with reference to the drawings. Fig. 5 is a flowchart showing an example of a proposed location setting process of the driving support function proposal system 100. The proposed location setting process is periodically executed by the server 10, for example.
[0077] 5, the server 10 of the driving support function proposal system 100 acquires the operation history of the driving support function of the probe vehicle 2 by the operation history acquisition unit 11a in S10. The operation history acquisition unit 11a recognizes, for example, the type of driving support function activated by the probe vehicle 2, the use time of the driving support function, and the use section of the driving support function. After that, the server 10 proceeds to S11.
[0078] In S11, the server 10 judges whether or not there is a candidate point where the usage frequency of the driving support function of the probe vehicle 2 is equal to or greater than the frequency judgment threshold by the proposed point setting unit 11b. If it is judged that there is a candidate point, the server 10 proceeds to S12. If it is not judged that there is a candidate point, the server 10 ends the proposed point setting process.
[0079] In S12, the server 10 judges whether the average usage time of the driving support function of the probe vehicle 2 at the candidate point is equal to or longer than a predetermined time by the proposed point setting unit 11b. If the server 10 judges that the average usage time of the driving support function is equal to or longer than the predetermined time, the server 10 proceeds to S13. If the server 10 does not judge that the average usage time of the driving support function is equal to or longer than the predetermined time, the server 10 ends the proposed point setting process.
[0080] In S13, the server 10 sets the candidate point as a proposed point by the proposed point setting unit 11b. The proposed point setting unit 11b sets the candidate point where the average usage time of the driving support function is equal to or longer than a predetermined time as a proposed point. After that, the server 10 ends the proposed point setting process. Note that the proposed point is re-evaluated at regular intervals, and may be deleted if it does not satisfy the conditions of S11 and S12.
[0081] 6 is a flowchart showing an example of a driving support function proposal process (a method for proposing a driving support function) of the driving support function proposal system 100. The driving support function proposal process is executed when the driver of the proposal target vehicle 3 permits a driving support function proposal service. The driving support function proposal process is executed repeatedly at regular time intervals, for example.
[0082] As shown in FIG. 6, the server 10 determines, in S20, whether or not the proposal target vehicle 3 will reach the proposed point by the driving assistance function proposal unit 11d. For example, when the distance between the proposal point and the proposal target vehicle 3 is less than a distance threshold, the driving assistance function proposal unit 11d determines that the proposal target vehicle 3 will reach the proposed point. When it is determined that the proposal target vehicle 3 will reach the proposed point, the server 10 proceeds to S21. When it is not determined that the proposal target vehicle 3 will reach the proposed point, the server 10 ends the driving assistance function proposal process.
[0083] In S21, the server 10 determines, by the driving assistance function proposal unit 11d, whether or not the driving assistance function of the proposed point is not yet installed in the proposal target vehicle 3. If it is determined that the driving assistance function of the proposed point is not yet installed in the proposal target vehicle 3, the server 10 proceeds to S22. If it is not determined that the driving assistance function of the proposed point is not yet installed in the proposal target vehicle 3, the server 10 proceeds to S24.
[0084] In S22, the server 10 determines whether the driving assistance function at the proposed point is a not-installed function that can be purchased by download from the server 10 for the proposal target vehicle 3 by the driving assistance function proposal unit 11d. If the server 10 determines that the driving assistance function is a not-installed function that can be purchased by download, the process proceeds to S23. If the server 10 does not determine that the driving assistance function is a not-installed function that can be purchased by download, the process ends.
[0085] In S24, the server 10 determines whether the advance use frequency or advance use count of the driving assistance function of the proposal target vehicle 3 at the proposal point is less than the proposal unnecessary threshold by the driving assistance function proposal unit 11d. If the server 10 determines that the advance use frequency or advance use count is less than the proposal unnecessary threshold, the server 10 proceeds to S25. If the server 10 determines that the advance use frequency or advance use count is not less than the proposal unnecessary threshold, the server 10 ends the driving assistance function proposal process.
[0086] In S25, the server 10 uses the driving support function proposal unit 11d to propose use of the driving support function to the driver of the proposal target vehicle 3. The driving support function proposal unit 11d proposes use of the driving support function to the driver of the proposal target vehicle 3 through the HMI 26 of the proposal target vehicle 3 by transmitting proposal information to the proposal target vehicle 3. Thereafter, the server 10 ends the driving support function proposal process.
[0087] Fig. 7 is a flowchart showing an example of an additional determination process that can be added to the driving support function proposal process. The server 10 of the driving support function proposal system 100 can execute the additional determination process of the flowchart shown in Fig. 7 instead of the process of S25 in Fig. 6, for example.
[0088] 7, the server 10 determines whether or not the turn indicator of the proposal target vehicle 3 is on by the driving assistance function proposal unit 11d in S30. If it is determined that the turn indicator of the proposal target vehicle 3 is on, the server 10 ends the driving assistance function proposal process including the additional determination process. If it is determined that the turn indicator of the proposal target vehicle 3 is not on, the server 10 proceeds to S31.
[0089] In S31, the server 10 determines whether or not the vehicle speed of the proposal target vehicle 3 is less than the vehicle speed threshold by the driving assistance function proposal unit 11d. If the server 10 determines that the vehicle speed of the proposal target vehicle 3 is less than the vehicle speed threshold, the server 10 proceeds to S33. If the server 10 determines that the vehicle speed of the proposal target vehicle 3 is not less than the vehicle speed threshold, the server 10 proceeds to S32.
[0090] In S32, the server 10 determines whether the post-proposal support start frequency of the proposal target vehicle 3 at the proposal point is equal to or greater than the proposal-dependent threshold by the driving support function proposal unit 11d. If the server 10 determines that the post-proposal support start frequency is equal to or greater than the proposal-dependent threshold, the server 10 proceeds to S33. If the server 10 determines that the post-proposal support start frequency is not equal to or greater than the proposal-dependent threshold, the server 10 ends the driving support function proposal process including the additional determination process.
[0091] In S33, the server 10, through the driving assist function proposal unit 11d, proposes the use of the driving assist function to the driver of the proposal target vehicle 3. After that, the server 10 ends the driving assist function proposal process.
[0092] According to the driving assistance function proposal system 100 and the driving assistance function proposal method of the driving assistance function proposal system 100 of this embodiment described above, it is considered that the driver of the proposed vehicle 3 does not understand the usefulness of the driving assistance function at the proposed location before executing the driving assistance function, so it is possible to prevent the driver from feeling annoyed by unnecessary suggestions.
[0093] In addition, in the driving assistance function proposal system 100, when the turn signal of the target vehicle 3 is on, it is assumed that the driver is consciously intending to perform a driving maneuver such as turning right, turning left, or changing lanes, and therefore by not suggesting the use of a driving assistance function, it is possible to prevent the proposal from being annoying to the driver.
[0094] Furthermore, in the driving assistance function proposal system 100, since it is possible that the driver is in a hurry to arrive at the destination when the vehicle speed of the proposed vehicle 3 is high, the driving assistance function proposal system 100 can prevent the proposal from being an annoyance to the driver by not proposing the use of the driving assistance function when the vehicle speed is above a vehicle speed threshold.
[0095] In addition, in the driving assistance function proposal system 100, even if the vehicle speed of the vehicle to which a proposal is made is equal to or greater than the vehicle speed threshold, if the frequency of post-proposal assistance start at the proposed location is equal to or greater than the proposal dependency threshold, it is considered that the driver relies on the proposal of the driving assistance function, and therefore it is highly likely that the driver will not find the proposal to use the driving assistance function annoying, and therefore it is possible to promote the use of the driving assistance function by making the proposal.
[0096] Although the embodiment of the present invention has been described above, the present invention is not limited to the above-mentioned embodiment. The present invention can be embodied in various forms including the above-mentioned embodiment and various modifications and improvements based on the knowledge of those skilled in the art.
[0097] The driving support function proposal system 100 does not necessarily have to determine the uninstalled functions and propose the purchase of the uninstalled functions. The server that sets the proposal point and the server that proposes the use of the driving support function may be separate. [Explanation of symbols]
[0098] 2...probe vehicle, 3...proposed target vehicle, 10...server, 11...processor, 11a...operation history acquisition unit, 11b...proposed location setting unit, 11c...proposed target vehicle information acquisition unit, 11d...driving assistance function proposal unit, 100...driving assistance function proposal system.
Claims
1. A driving assistance function proposal system that acquires operation history of a driving assistance function including position information from a plurality of probe vehicles, and when it is determined that a proposal target vehicle will reach a proposal point set based on the operation history, proposes to a driver of the proposal target vehicle use of the driving assistance function corresponding to the proposal point, A driving assistance function suggestion system that does not suggest to the driver the use of the driving assistance function if the frequency or number of prior uses of the driving assistance function of the proposed vehicle at the proposed location is equal to or greater than a no-suggestion threshold.
2. The driving assistance function suggestion system according to claim 1 , wherein when the turn signal of the proposal target vehicle determined to reach the proposal point is on, the system does not suggest to the driver that the driver use the driving assistance function.
3. 3. The driving assistance function suggestion system according to claim 1, wherein if the vehicle speed of the proposed vehicle determined to reach the proposed location is equal to or greater than a vehicle speed threshold, the system does not suggest to the driver that the driver use the driving assistance function.
4. The driving assistance function proposal system of claim 3, further comprising: a vehicle speed threshold value that is a threshold value for determining whether the vehicle speed of the proposed vehicle is to reach the proposed location; and a post-proposal assistance start frequency that is a frequency at which the driver starts using the driving assistance function after a proposal at the proposed location is equal to or greater than a proposal-dependent threshold value.
5. 3. The driving assistance function proposal system of claim 1 or 2, wherein when there is an uninstalled function that is a driving assistance function that is not installed in the proposed vehicle and that the proposed vehicle can purchase by downloading from a server, when it is determined that the proposed vehicle is located at the proposal point associated with the uninstalled function, the driving assistance function proposal system proposes to the driver to purchase the uninstalled function.
6. A proposal method for a driving assistance function proposal system, which acquires operation history of a driving assistance function including position information from a plurality of probe vehicles, and when it is determined that a proposal target vehicle will reach a proposal point set based on the operation history, proposes to a driver of the proposal target vehicle use of the driving assistance function corresponding to the proposal point, A proposal method for a driving assistance function proposal system, which does not propose to the driver the use of the driving assistance function if the frequency or number of prior uses of the driving assistance function of the proposed vehicle at the proposed location is equal to or greater than a no-proposal threshold.
Citation Information
Patent Citations
Server device and vehicle system
JP2019074803A
