Data communication system, function management server, in-vehicle system, recommended function distribution program, and recommended function presentation program

Abstract

To increase convenience by appropriately presenting a function effective for driving and a function of interest to a driver.SOLUTION: In a data communication system 1, a function management server 5 that manages a vehicle-related function and an on-vehicle system 3 that is installed on a vehicle perform data communication. The function management server acquires driving data of a driver from the on-vehicle system so as to specify a recommendation function, and distributes recommendation function information regarding the specified recommended function to the on-vehicle system. When the on-vehicle system receives the recommended function information distributed from the function management server, the on-vehicle system presents the recommended function specified by the received recommended function information to the driver.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a data communication system, a function management server, an in-vehicle system, a recommended function distribution program, and a recommended function presentation program.

Background Art

[0002] There is a configuration disclosed in which personal setting information associated with a driver is managed by a server, and in an in-vehicle system, when the personal authentication of the driver is completed and the vehicle power is turned on, the personal setting information of the driver who has completed the personal authentication is acquired from the server (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the method disclosed in Patent Document 1, for example, when the vehicle is replaced due to the sale or purchase of the vehicle, there is a problem that the functions required by the driver cannot be used. Therefore, a technique is considered in which it is determined whether the functions installed in the vehicle in which the driver rides correspond to the personal setting information managed by the server, and when at least a part does not correspond, information regarding the non-corresponding functions is notified to the driver.

[0005] By the way, there are also drivers who have a pain point of "I only use fixed functions according to my preferences in driving, but actually I want to know and try more new functions." Conventionally, it has not been possible to present functions effective for driving or functions of interest to such drivers.

[0006] The present invention has been made in view of the above circumstances, and an object thereof is to provide a data communication system, a function management server, an in-vehicle system, a recommended function distribution program, and a recommended function presentation program that can appropriately present functions effective for driving and functions of interest to a driver, thereby enhancing convenience.

Means for Solving the Problems

[0007] According to the invention described in claim 1, a function management server (5) that manages functions related to a vehicle and an in-vehicle system (3) mounted on the vehicle perform data communication. The function management server acquires the driver's driving data from the in-vehicle system Analyze the driving skills of the driver from the obtained driving data of the driver to identify a recommended function, and distributes recommended function information related to the identified recommended function to the in-vehicle system. When the in-vehicle system receives the recommended function information distributed from the function management server, it presents the recommended function specified by the received recommended function information to the driver.

[0008] In the function management server, the driver's driving data Analyze the driving skills of the driver is used to identify a recommended function, and recommended function information related to the identified recommended function is distributed to the in-vehicle system. In the in-vehicle system, the recommended function specified by the recommended function information is presented to the driver. By setting a function effective for driving based on the driver's driving data as the recommended function, a function effective for driving can be appropriately presented to the driver, thereby enhancing convenience.

[0009] According to the invention described in claim 4, a function management server (5) that manages functions related to a vehicle and an in-vehicle system (3) mounted on the vehicle perform data communication. The function management server acquires the driver's question information in the automatic conversation service to identify a recommended function, and distributes recommended function information related to the identified recommended function to the in-vehicle system. When the in-vehicle system receives the recommended function information distributed from the function management server, it presents the recommended function specified by the received recommended function information to the driver.

[0010] In the function management server, a recommended function is specified based on the driver's question information in the automatic conversation service, and recommended function information regarding the specified recommended function is distributed to the in-vehicle system. In the in-vehicle system, the recommended function specified by the recommended function information is presented to the driver. By setting the function of interest based on the driver's question information in the automatic conversation service as the recommended function, the function of interest can be appropriately presented to the driver, improving convenience.

[0011] According to the invention described in claim 5, a function management server (5) that manages functions related to a vehicle and an in-vehicle system (3) mounted on the vehicle perform data communication. The function management server acquires the driver's speech information in an online communication service using a website to specify a recommended function, and distributes recommended function information regarding the specified recommended function to the in-vehicle system. When the in-vehicle system receives the recommended function information distributed from the function management server, the in-vehicle system presents the recommended function specified by the received recommended function information to the driver.

[0012] In the function management server, a recommended function is specified based on the driver's speech information in an online communication service using a website, and recommended function information regarding the specified recommended function is distributed to the in-vehicle system. In the in-vehicle system, the recommended function specified by the recommended function information is presented to the driver. By setting the function of interest based on the driver's speech information in the online communication service using a website as the recommended function, the function of interest can be appropriately presented to the driver, improving convenience.

Brief Description of the Drawings

[0013]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Best Mode for Carrying Out the Invention

[0014] Hereinafter, a plurality of embodiments will be described with reference to the drawings. In the embodiments described below, the description of the overlapping parts with the preceding embodiments may be omitted.

[0015] (First Embodiment) Hereinafter, the first embodiment will be described with reference to FIGS. 1 to 14. As shown in FIG. 1, the data communication system 1 includes a non-vehicle system 2 outside the vehicle and an in-vehicle system 3 mounted on the vehicle. The non-vehicle system 2 includes a map generation server 4, a function management server 5, and a portable information terminal 6. The portable information terminal 6 is, for example, a smartphone or the like. The map generation server 4, the function management server 5, and the portable information terminal 6 can communicate with the in-vehicle system 3 via a communication network including, for example, a digital communication line. Further, the portable information terminal 6 can communicate with the in-vehicle system 3 while being brought into the vehicle. The in-vehicle system 3 and the map generation server 4 and the function management server 5 are in a plurality-to-one relationship, respectively. That is, a plurality of in-vehicle systems 3 can be connected to communicate with one map generation server 4, and a plurality of in-vehicle systems 3 are connected to communicate with one function management server 5.

[0016] The map generation server 4 is a server managed by an OEM, a data supplier, or the like, and has a function of integrating a plurality of probe data to generate a probe data map. When the map generation server 4 receives and acquires the probe data transmitted from the in-vehicle system 3, it integrates a plurality of probe data to generate a probe data map. The map generation server 4 sequentially updates the probe data map by sequentially reflecting the feature information included in the acquired probe data on the latest probe data map stored at that time every time it receives and acquires the probe data transmitted from the in-vehicle system 3, for example.

[0017] When the transmission condition of the probe data map is satisfied, the map generation server 4 transmits the latest probe data map stored at that time to the in-vehicle system 3. The map generation server 4 manages the probe data map, for example, in units of segments for each section. When it receives and acquires the position of the host vehicle transmitted from the in-vehicle system 3, it identifies the probe data map of the segment corresponding to the acquired position of the host vehicle, and transmits the identified probe data map to the in-vehicle system 3, which is the transmission source of the position of the host vehicle, via the communication network.

[0018] The function management server 5 is a server managed by an OEM, a data supplier, etc., and has a function of managing functions related to the vehicle. As shown in FIG. 2, the function management server 5 includes a driving data acquisition unit 5a, a first recommended function identification unit 5b, a question information acquisition unit 5c, a second recommended function identification unit 5d, a speech information acquisition unit 5e, a third recommended function identification unit 5f, and an information distribution unit 5g. A recommended function distribution program executed by the function management server 5 is realized by these units 5a to 5g.

[0019] The driving data acquisition unit 5a receives and acquires the driving data of the driver transmitted from the in-vehicle system 3. When the driving data of the driver is acquired by the driving data acquisition unit 5a, the first recommended function identification unit 5b identifies a recommended function based on the acquired driving data of the driver.

[0020] The first recommended function identification unit 5b analyzes the driver's driving skills from the driver's driving data. For example, if it determines that the technology for keeping the driving lane is unstable, it determines that lane-keeping assist (hereinafter referred to as LKA (Lane Keeping Asist)), lane-tracing assist (hereinafter referred to as LTA (Lane Tracing Assist)), etc., which are driving support functions, are effective for the driver's driving, and identifies the functions of LKA and LTA determined to be effective for the driving as recommended functions. In this case, the first recommended function identification unit 5b may identify the recommended functions by comparing the driver's driving data acquired from the in-vehicle system 3 with the driving data of other drivers, or by comparing the driving data of other drivers at the same location. That is, the first recommended function identification unit 5b may, for example, identify the predicted route of the target vehicle, and identify the functions already used by other drivers on the identified predicted route as recommended functions.

[0021] The question information acquisition unit 5c has a function of monitoring the usage status of the automatic conversation service used by the driver on the mobile information terminal 6. The automatic conversation service is a cloud service for real-time communication using the Internet by an automatic conversation program that utilizes artificial intelligence, such as a chatbot. The question information acquisition unit 5c monitors the question information regarding the questions posted by the driver in the automatic conversation service, and receives and acquires the driver's question information transmitted from the mobile information terminal 6. If the mobile information terminal 6 can communicate with the in-vehicle system 3 by being brought into the vehicle, the question information acquisition unit 5c receives and acquires the driver's question information from the mobile information terminal 6 via the in-vehicle system 3. That is, the question information acquisition unit 5c may receive the driver's question information transmitted from the mobile information terminal 6 directly, or receive the driver's question information transmitted from the mobile information terminal 6 via the in-vehicle system 3.

[0022] When the second recommended function specifying unit 5d acquires the driver's question information by the question information acquisition unit 5c, it specifies a recommended function based on the acquired driver's question information. When the second recommended function specifying unit 5d analyzes the text of the question posted by the driver and identifies the presence of vocabulary such as "LKA" or "LTA" or vocabulary related to "LKA" or "LTA" in the driver's question information, it determines that the driver is interested in LKA or LTA, and specifies the functions of LKA and LTA that the driver is determined to be interested in as the recommended functions.

[0023] The speech information acquisition unit 5e has a function of monitoring the usage status of an online communication service using a website by the driver's mobile information terminal 6. The online communication service using a website is a social networking service (SNS), such as Facebook, Twitter, LINE, Instagram, etc. The speech information acquisition unit 5e monitors the speech information regarding the speech posted by the driver in the online communication service using a website, and receives and acquires the driver's speech information transmitted from the mobile information terminal 6. If the mobile information terminal 6 can communicate with the in-vehicle system 3 by being brought into the vehicle, the speech information acquisition unit 5e receives and acquires the driver's speech information from the mobile information terminal 6 via the in-vehicle system 3. That is, the speech information acquisition unit 5e may directly receive the driver's speech information transmitted from the mobile information terminal 6 or receive the driver's speech information transmitted from the mobile information terminal 6 via the in-vehicle system 3.

[0024] When the speech information of the driver is acquired by the speech information acquisition unit 5e, the third recommended function specifying unit 5f specifies a recommended function based on the acquired speech information of the driver. When the third recommended function specifying unit 5f analyzes the text of the speech posted by the driver and identifies the presence of vocabulary such as "LKA" or "LTA" or vocabulary related to "LKA" or "LTA" in the speech information of the driver, in this case as well, it is determined that the driver is interested in LKA or LTA, and the functions of LKA and LTA determined that the driver is interested in are specified as the recommended functions.

[0025] When the recommended function is specified by any one of the first recommended function specifying unit 5b, the second recommended function specifying unit 5d, or the third recommended function specifying unit 5f, the information distribution unit 5g transmits recommended function information regarding the specified recommended function to the in-vehicle system 3. Note that the recommended function is not limited to LKA and LTA, and any function may be used as long as it is a function effective for the driver's driving or a function in which the driver is interested.

[0026] When the in-vehicle system 3 receives and acquires the recommended function information transmitted from the function management server 5, it notifies the driver of the acquired recommended function information and presents the recommended function to the driver. Further, the information distribution unit 5g may transmit the recommended function information to the in-vehicle system 3 and also transmit it to the driver's mobile information terminal 6. That is, the driver can recognize the recommended function specified by the function management server 5 when the recommended function is presented by the in-vehicle system 3 inside the vehicle, and can also recognize the recommended function specified by the function management server 5 when the recommended function is presented by the mobile information terminal 6 outside the vehicle.

[0027] As shown in FIG. 3, the in-vehicle system 3 includes a data communication module (hereinafter referred to as DCM (Data Communication Module)) 7, a central ECU (Electronic Control Unit) 8, an ADAS (Advanced Driver Assistance System) domain ECU 9, a cockpit domain ECU 10, a body ECU 11, and a power train domain ECU 12.

[0028] DCM7 and each of the ECUs 8 to 12 are provided with a microcomputer having a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and an I / O (Input / Output). The microcomputer executes a computer program stored in a non-transitory tangible storage medium to execute processing corresponding to the computer program and control the overall operations of DCM7 and each of the ECUs 8 to 12. The microcomputer has the same meaning as a processor. The non-transitory tangible storage medium may share hardware with other computer resources. DCM7 and each of the ECUs 8 to 12 cooperate to control the overall operations of the in-vehicle system 3.

[0029] DCM7 has a V2X (Vehicle to X) communication function as an in-vehicle communication device, and performs communication control on the vehicle side in data communication with infrastructure facilities including the above-described map generation server 4, function management server 5, and mobile information terminal 6.

[0030] The central ECU 8 integrally manages the ADAS domain ECU 9, the cockpit domain ECU 10, and the power train domain ECU 12. The ADAS domain ECU 9 includes a host vehicle position estimation unit 9a, a host vehicle surrounding recognition unit 9b, a caution point specifying unit 9c, a driver state recognition unit 9d, a map quality determination unit 9e, a safety confirmation determination unit 9f, and a driving intervention execution unit 9g. The cockpit domain ECU 10 includes a notification control unit 10a.

[0031] The locator 13 calculates the position coordinates using various parameters included in the GNSS satellite signals received from GNSS (Global Navigation Satellite System) satellites, corrects the calculated position coordinates based on the detection results of a gyro sensor, a vehicle speed sensor, etc., and outputs the corrected position coordinates to the host vehicle position estimation unit 9a. Note that GNSS is a general term for the global positioning satellite system, and various systems such as GPS (Global Positioning System), GLONASS (Global Navigation Satellite System), Galileo, BeiDou, and IRNSS (Indian Regional Navigational Satellite System) have been realized. When the host vehicle position estimation unit 9a inputs the position coordinates from the locator 13, it estimates the host vehicle position using the input position coordinates and outputs the estimated host vehicle position to the DCM 7.

[0032] The millimeter-wave radar 14 irradiates millimeter waves around the host vehicle to sense the surroundings of the host vehicle and outputs the detection results to the host vehicle surrounding recognition unit 9b. The millimeter-wave radar 14 has advantages such as strong straightness, the possibility of miniaturizing the circuit and antenna design, high range resolution and high angle resolution due to a wide bandwidth, and strong resistance to environmental changes such as weather. The sonar 15 irradiates, for example, ultrasonic waves around the host vehicle to sense the surroundings of the host vehicle and outputs the detection results to the host vehicle surrounding recognition unit 9b. The sonar 15 has advantages such as reflecting on glass surfaces and water surfaces.

[0033] The LiDAR (Light Detection and Ranging) 16 irradiates laser light around the host vehicle to sense the area around the host vehicle, and outputs the detection result to the surrounding recognition unit 9b of the host vehicle. The LiDAR 16 has advantages such as being able to reflect off non-metals and being detectable even at night or during rainfall. The camera 17 includes an image sensor such as a CCD (Charge Coupled Device) or CMOS (Complementary Metal Oxide Semiconductor), captures images of the area around the host vehicle, and outputs the captured camera images to the surrounding recognition unit 9b of the host vehicle. The millimeter-wave radar 14, the sonar 15, the LiDAR 16, and the camera 17 are autonomous sensors. Note that it is not necessary to include all of the millimeter-wave radar 14, the sonar 15, the LiDAR 16, and the camera 17, and a configuration including at least any one autonomous sensor is also acceptable. Also, a configuration including an autonomous sensor different from the millimeter-wave radar 14, the sonar 15, the LiDAR 16, and the camera 17 is also acceptable.

[0034] When the surrounding recognition unit 9b of the host vehicle inputs the detection result from the millimeter-wave radar 14, the detection result from the sonar 15, the detection result from the LiDAR 16, and the camera image from the camera 17, it uses the input detection results and camera images to recognize the area around the host vehicle, and outputs the surrounding information of the recognized area around the host vehicle to the DCM 7, the map quality determination unit 9e, the safety confirmation determination unit 9f, and the driving intervention execution unit 9g. The surrounding information includes, as static information, the position and type of lane lines, stop lines, crosswalks, etc. painted on the road surface, the position and type of traffic lights, road signs, etc. erected from the road surface, the road width, road type, number of lanes, and other ground object information. Also, the surrounding information includes, as dynamic and static information, the positions of pedestrians, bicycles, and oncoming vehicles, etc.

[0035] When DCM7 receives the vehicle position from the vehicle position estimation unit 9a and the surrounding information around the vehicle from the vehicle surrounding recognition unit 9b, it transmits probe data in which the input vehicle position, the surrounding information around the vehicle, and the time are associated with each other to the map generation server 4 via the communication network. In this case, DCM7 transmits the probe data to the map generation server 4 via the communication network at, for example, the timing when the travel distance reaches a certain distance, the timing when the elapsed time reaches a certain time, and the like.

[0036] In DCM7, when the probe data map acquisition unit 2a receives the probe data map transmitted from the map generation server 4, it outputs the received probe data map to the attention point specifying unit 9c and the map quality determination unit 9e.

[0037] When the map quality determination unit 9e receives the surrounding information around the vehicle from the vehicle surrounding recognition unit 9b and the probe data map from DCM7, it collates the probe data map with the surrounding information around the vehicle and determines whether the quality of the probe data map is good or bad. The map quality determination unit 9e determines, for example, whether the ground object information indicated by the probe data map matches the surrounding information around the vehicle indicated by the detection result of the autonomous sensor, and determines whether the quality of the probe data map is good or bad. Specifically, the map quality determination unit 9e determines whether the position and type of the ground object indicated by the probe data map match the position and type of the ground object included in the surrounding information around the vehicle indicated by the detection result of the autonomous sensor, and determines whether the quality of the probe data map is good or bad.

[0038] The map quality determination unit 9e quantifies, for example, the degree of coincidence between the feature information indicated by the probe data map and the surrounding information around the host vehicle indicated by the detection result of the autonomous sensor, and compares the quantified value with a threshold value. When the map quality determination unit 9e determines that the deviation between the feature information indicated by the probe data map and the surrounding information around the host vehicle indicated by the detection result of the autonomous sensor is small and the value indicating the degree of coincidence is equal to or greater than the threshold value, it determines that the quality of the probe data map is good. When the map quality determination unit 9e determines that the quality of the probe data map is good, it outputs the probe data map determined to have good quality to the attention point specifying unit 9c. On the other hand, when the map quality determination unit 9e determines that the deviation between the feature information indicated by the probe data map and the surrounding information around the host vehicle indicated by the detection result of the autonomous sensor is large and the value indicating the degree of coincidence is less than the threshold value, it determines that the quality of the probe data map is poor.

[0039] The external array microphone 18 outputs voice information collected around the host vehicle to the attention point specifying unit 9c. The external array microphone 18 is also an autonomous sensor like the above-described millimeter-wave radar 14, sonar 15, LiDAR 16, and camera 17. When the attention point specifying unit 9c inputs the probe data map from the map quality determination unit 9e, it specifies the attention point and outputs the specification result to the safety confirmation determination unit 9f. The attention point is, for example, a blind spot at an intersection, etc., and is a place where the driver needs to confirm safety during driving. In this case, when the attention point specifying unit 9c inputs voice information from the external array microphone 18, it also specifies the attention point with reference to the input voice information. Note that when the attention point specifying unit 9c does not input the probe data map from the map quality determination unit 9e, it specifies the attention point using the detection result of the autonomous sensor and outputs the specification result to the safety confirmation determination unit 9f.

[0040] A driver status monitor (registered trademark) (hereinafter referred to as DSM (Driver Status Monitor)) 19 that monitors the driver's state captures the driver's face with a driver monitor camera, determines the face orientation, line-of-sight direction, head shaking, etc. from the driver's face image, and outputs the determination result to the driver state recognition unit 9d.

[0041] When the driver state recognition unit 9d receives the determination result from the DSM 19, it recognizes the driver state using the determination result, and outputs driver state information indicating the recognized driver state to the DCM 7, the safety confirmation determination unit 9f, and the driving intervention execution unit 9g.

[0042] When the safety confirmation determination unit 9f receives the surrounding information around the host vehicle from the host vehicle surrounding recognition unit 9b and the driver state information from the driver state recognition unit 9d, it determines whether it is necessary to activate an alert using the input surrounding information around the host vehicle and the driver state information. The safety confirmation determination unit 9f determines whether the driver's line of sight direction is directed toward the direction of the attention point in a situation where an attention point has occurred, determines whether the driver is performing a safety confirmation based on the driver state, and determines whether it is necessary to activate an alert.

[0043] When the safety confirmation determination unit 9f determines that the driver's line of sight direction is directed toward the direction of the attention point, it determines that there is no need to activate an alert. On the other hand, when the safety confirmation determination unit 9f determines that the driver's line of sight direction is not directed toward the direction of the attention point, it determines that it is necessary to activate an alert, and outputs a notification instruction to the notification control unit 10a.

[0044] When the notification control unit 10a receives the notification instruction from the safety confirmation determination unit 9f, it outputs a drive instruction to the head-up display (hereinafter referred to as HUD (Head-Up Display)) 20, the center information display (hereinafter referred to as CID (Center Information Display)) 21, the speaker 22, and the ambient light 23, and outputs the notification instruction to the body ECU 11. The notification control unit 10a activates an alert at a location close to the driver's line of sight direction in the HUD 20, CID 21, speaker 22, ambient light 23, and side electronic mirror 24, and notifies the driver of the unexecuted safety confirmation information indicating that the driver has not performed a safety confirmation.

[0045] An alert is, for example, a message or icon that prompts a safety check for a point of attention. If the driver's line of sight is directed straight ahead in the vehicle's traveling direction, the notification control unit 10a causes, for example, a message or icon to be displayed in front of the driver on the HUD 20. If the driver's line of sight is directed slightly forward to the right in the vehicle's traveling direction, the notification control unit 10a causes, for example, a message or icon to be displayed slightly to the right in front of the driver on the HUD 20. If the driver's line of sight is directed slightly forward to the left in the vehicle's traveling direction, the notification control unit 10a causes, for example, a message or icon to be displayed slightly to the left in front of the driver on the HUD 20. Further, the notification control unit 10a may cause, for example, a message or icon that prompts a safety check for a point of attention to be displayed on the CID 21. Further, the notification control unit 10a may cause, for example, a message that prompts a safety check for a point of attention to be output as sound from the speaker 22. By activating the alert in this way, the driver can be made aware that they have been negligent in paying attention to the point of attention.

[0046] Further, when the recommended function information transmitted from the function management server 5 as described above is received by the in-vehicle system 3, the notification control unit 10a causes the received recommended function information to be displayed on the HUD 20 or the CID 21 or output as sound from the speaker 22, and presents the driver with the recommended function specified by the recommended function information. The notification control unit 10a corresponds to the recommended function presentation unit. A recommended function presentation program executed by the in-vehicle system 3 is realized by the notification control unit 10a.

[0047] The fingerprint authentication sensor 25 senses the driver's fingerprint and outputs the detection result to the cockpit domain ECU 10. The palmprint authentication sensor 26 senses the driver's palmprint and outputs the detection result to the cockpit domain ECU 10. When the cockpit domain ECU 10 receives the detection results from the fingerprint authentication sensor 25 and the palmprint authentication sensor 26, it authenticates the driver using the input detection results and outputs the authentication result to the central ECU 8.

[0048] The sensor group 28 attached to the airbag 27 includes, for example, a vehicle speed sensor, an acceleration sensor, and a yaw rate sensor, which respectively detect the vehicle speed, acceleration, and yaw rate, and output the detection results to the driving intervention execution unit 9g. The sensor group 28 may be attached to the ADAS domain ECU 9 or the central ECU 8.

[0049] When the driving intervention execution unit 9g inputs the surrounding information around the host vehicle from the host vehicle surrounding recognition unit 9b, inputs the driver state information from the driver state recognition unit 9d, and inputs the detection results from the sensor group 28 attached to the airbag 27, it is necessary to determine whether to intervene in the driver's driving operation using the input surrounding information around the host vehicle, driver state information, and detection results. The driving intervention execution unit 9g determines, for example, whether the driver's line of sight is directed toward the host vehicle traveling direction, whether the host vehicle traveling direction is dangerous, whether the vehicle speed, acceleration, and yaw rate are normal, etc., and determines whether it is necessary to intervene in the driver's driving operation.

[0050] For example, when the driving intervention execution unit 9g determines that the driver's line of sight is directed toward the host vehicle traveling direction, the host vehicle traveling direction is not dangerous, and the vehicle speed, acceleration, and yaw rate are normal, and determines that the driver's driving is appropriate, it determines that there is no need to intervene in the driver's driving operation. On the other hand, when the driving intervention execution unit 9g determines that, for example, the driver's line of sight is not directed toward the host vehicle traveling direction, the host vehicle traveling direction is dangerous, or the vehicle speed, acceleration, and yaw rate are not normal, and determines that the driver's driving is not appropriate, it determines that it is necessary to intervene in the driver's driving operation, and outputs a driving intervention instruction to the power train domain ECU 12.

[0051] When the power train domain ECU 12 receives a driving intervention instruction from the driving intervention execution unit 9g, it outputs the driving intervention instruction to the braking device 29. The sensor group 30 attached to the braking device 29 includes, for example, a vehicle speed sensor, an acceleration sensor, and a yaw rate sensor, which respectively detect the vehicle speed, acceleration, and yaw rate, and output the detection results to the braking device 29. The sensor group 30 may be attached to the power train domain ECU 12 or the central ECU 8. When the braking device 29 receives a driving intervention instruction from the power train domain ECU 12, it performs collision damage mitigation braking (hereinafter referred to as AEB (Autonomous Emergency Braking)) control using, for example, the detection results of the sensor group 30. In addition to AEB control, steering control, attitude control, etc. may be performed as interventions for driving operations. For example, electronic stability control (hereinafter referred to as ESC) may be performed to prevent skidding.

[0052] Next, the operation of the above-described configuration will be described with reference to FIGS. 4 to 12. The processes performed by the in-vehicle system 3, namely, the personal authentication process, the probe data transmission process, the driving diagnosis process, and the recommended function presentation process, will be described, and the process performed by the function management server 5, namely, the recommended function distribution process, will be described. The function management server 5 performs the recommended function distribution process by means of a recommended function distribution program. The in-vehicle system 3 performs the recommended function presentation process by means of a recommended function presentation program.

[0053] (1-1) Personal authentication process performed by the in-vehicle system 3 (see FIG. 4) When the start condition for the personal authentication process is satisfied upon unlocking the door, in-vehicle system 3 starts the personal authentication process. When in-vehicle system 3 starts the personal authentication process, it determines whether the unlocking of the door is an operation by the portable information terminal 6 (A1). When in-vehicle system 3 determines that the unlocking of the door is an operation by the portable information terminal 6 (A1: YES), it performs personal authentication using the personal authentication data (A2). That is, in-vehicle system 3 receives and acquires the personal authentication data transmitted from the portable information terminal 6, and collates the acquired personal authentication data with the registered data registered in advance. In-vehicle system 3 determines whether the authentication result is correct (A3). When it determines that the personal authentication data matches the registered data and determines that the authentication result is correct (A3: YES), it sets various setting information registered in association with the personal ID (A4) and ends the personal authentication process.

[0054] The various setting information registered in association with the personal ID is, for example, information regarding ADAS, air conditioning, power train, music, cockpit screen, etc. In-vehicle system 3 sets, for example, ADAS, air conditioning, power train, music, cockpit screen, etc. registered in association with the personal ID. Also, when a destination is registered in the navigation app of the portable information terminal 6, in-vehicle system 3 sets the destination registered in the portable information terminal 6. Also, when the history of the driver's question information is stored in the app of the automatic conversation service of the portable information terminal 6, in-vehicle system 3 sets the driver's question information stored in the portable information terminal 6. Further, when the history of the driver's speech information is stored in the app of the online communication service using the website of the portable information terminal 6, in-vehicle system 3 sets the driver's speech information stored in the portable information terminal 6.

[0055] On the other hand, when the in-vehicle system 3 determines that the unlocking of the door is not an operation by the portable information terminal 6 (A1: NO), it performs personal authentication based on the detection result of the fingerprint authentication sensor 25 and the detection result of the palmprint authentication sensor 26 (A5). The in-vehicle system 3 determines whether the authentication result is correct (A6). When it determines that the detection result of the fingerprint authentication sensor 25 and the detection result of the palmprint authentication sensor 26 are correct and the authentication result is correct (A6: YES), in this case as well, it sets various setting information registered in association with the personal ID (A4) and ends the personal authentication process.

[0056] (1-2) Probe data transmission process performed by the in-vehicle system 3 (see Fig. 5) When the start condition of the probe data transmission process is satisfied, for example, when the ignition is turned on, the in-vehicle system 3 starts the probe data transmission process. When the in-vehicle system 3 starts the probe data transmission process, it estimates the vehicle position by the own vehicle position estimation unit 9a using the position coordinates input from the locator 13 (A11). The in-vehicle system 3 recognizes the surroundings of the own vehicle by the own vehicle surroundings recognition unit 9b using the detection result input from the millimeter-wave radar 14, the detection result input from the sonar 15, the detection result input from the LiDAR 16, and the camera image input from the camera 17 (A12). The in-vehicle system 3 generates probe data by associating the vehicle position estimated by the own vehicle position estimation unit 9a, the surrounding information of the surroundings of the own vehicle recognized by the own vehicle surroundings recognition unit 9b, and the time (A13), and stores the generated probe data in the data storage area (A14).

[0057] The in-vehicle system 3 determines whether the transmission condition of the probe data is satisfied (A15). When it determines that the transmission condition of the probe data is satisfied, for example, at the timing when the driving distance reaches a certain distance, the timing when the elapsed time reaches a certain time, etc. (A15: YES), it transmits the probe data stored in the data storage area from the DCM 7 to the map generation server 4 via the communication network (A16).

[0058] The in-vehicle system 3 determines, for example, whether the end condition for the probe data transmission process is satisfied due to the ignition being turned off (A17). If it is determined that the end condition for the probe data transmission process is not satisfied while the ignition is on (A17: NO), the process returns to step A11 described above, and steps A11 and subsequent steps are repeated. When the in-vehicle system 3 determines that the end condition for the probe data transmission process is satisfied due to the ignition being turned off (A17: YES), the probe data transmission process is terminated.

[0059] (1-3) Driving diagnosis process performed by the in-vehicle system 3 (see FIGS. 6 to 10) When the start condition for the driving diagnosis process is satisfied, for example, when the ignition is turned on, the in-vehicle system 3 starts the driving diagnosis process. When the in-vehicle system 3 starts the driving diagnosis process, it estimates the vehicle position by the host vehicle position estimation unit 9a using the position coordinates input from the locator 13 (A21). The in-vehicle system 3 recognizes the surroundings of the host vehicle by the host vehicle surroundings recognition unit 9b using the detection result input from the millimeter-wave radar 14, the detection result input from the sonar 15, the detection result input from the LiDAR 16, and the camera image input from the camera 17 (A22).

[0060] The in-vehicle system 3 transmits the vehicle position estimated by the vehicle position estimation unit 9a from the DCM 7 to the map generation server 4 via the communication network (A23), and waits for the reception of the probe data map from the map generation server 4 (A24). When the map generation server 4 receives the vehicle position transmitted from the in-vehicle system 3, it specifies the probe data map of the segment corresponding to the received vehicle position, and transmits the specified probe data map to the in-vehicle system 3 which is the transmission source of the vehicle position via the communication network. Incidentally, A21 to A23 may be performed in A11 to A16 of the probe data transmission process. That is, the in-vehicle system 3 may transmit the vehicle position by transmitting the probe data. When the map generation server 4 receives the probe data transmitted from the in-vehicle system 3, it specifies the vehicle position from the received probe data, specifies the probe data map of the segment corresponding to the specified vehicle position, and may transmit the specified probe data map to the in-vehicle system 3 which is the transmission source of the vehicle position via the communication network.

[0061] When the in-vehicle system 3 determines that it has received the probe data map transmitted from the map generation server 4 by the DCM 7 (A24: YES), it collates the received probe data map with the surrounding information around the vehicle (A25), and determines the quality of the probe data map by the map quality determination unit 9e (A26). When the in-vehicle system 3 determines that the deviation between the feature information indicated by the probe data map and the surrounding information around the vehicle indicated by the detection result of the autonomous sensor is small and the quality of the probe data map is good (A26: YES), it specifies the attention points using the probe data map determined to have good quality (A27).

[0062] On the other hand, when the in-vehicle system 3 determines that the deviation between the feature information indicated by the probe data map and the surrounding information around the vehicle indicated by the detection result of the autonomous sensor is large and the quality of the probe data map is not good (A26: NO), it specifies the attention points using the detection result of the autonomous sensor (A28).

[0063] The in-vehicle system 3 inputs the determination result of the driver's face image captured by the driver monitoring camera, and recognizes the driver state by the driver state recognition unit 9d (A29). The in-vehicle system 3 determines whether the driver's line of sight direction is directed toward the direction of the attention point in a situation where an attention point has occurred, determines whether the driver is performing a safety check based on the driver state, and determines by the safety check determination unit 9f whether it is necessary to activate an alert (A30).

[0064] When the in-vehicle system 3 determines that the driver's line of sight direction is directed toward the direction of the attention point and determines that it is not necessary to activate an alert (A30: NO), it transmits the driver's driving data from the DCM 7 to the function management server 5 via the communication network (A31).

[0065] On the other hand, when the in-vehicle system 3 determines that the driver's line of sight direction is not directed toward the direction of the attention point and determines that it is necessary to activate an alert (A30: YES), it drives the HUD 20, CID 21, speaker 22, ambient light 23, etc., and activates an alert at a location close to the driver's line of sight direction by the notification control unit 10a (A32), and transmits the driver's driving data from the DCM 7 to the function management server 5 via the communication network (A31).

[0066] That is, as shown in FIG. 8, for example, when the in-vehicle system 3 determines that there is a possibility that a pedestrian B may jump out from behind a building A in front of the left side of the host vehicle, and specifies the front left side of the host vehicle as an attention point, but determines that the driver's line of sight direction is not directed toward the front left side of the host vehicle, it determines that it is necessary to activate an alert. When the in-vehicle system 3 determines that the driver's line of sight direction is directed straight ahead in the traveling direction of the host vehicle, for example, it causes the HUD 20 to display a message M such as "Attention to the Front Left" in front of the driver. Note that as long as the driver can recognize the activation of the alert, the mode of activating the alert may be any mode.

[0067] The in-vehicle system 3 inputs the surrounding information around the host vehicle, inputs the driver state information, inputs the detection results from the sensor group 28 attached to the airbag 27, and determines whether it is necessary to intervene in the driver's driving operation by the driving intervention execution unit 9g (A33). When the in-vehicle system 3 determines that, for example, the driver's line of sight is directed in the host vehicle's traveling direction, the host vehicle's traveling direction is not dangerous, and the vehicle speed, acceleration, and yaw rate are normal, and determines that it is not necessary to intervene in the driver's driving operation (A33: NO), it transmits the driver's driving data from the DCM 7 to the function management server 5 via the communication network (A34).

[0068] On the other hand, when the in-vehicle system 3 determines that, for example, the driver's line of sight is not directed in the host vehicle's traveling direction, the host vehicle's traveling direction is dangerous, or the vehicle speed, acceleration, and yaw rate are abnormal, and determines that it is necessary to intervene in the driver's driving operation (A33: YES), for example, it performs ABS control by the power train domain ECU 12, intervenes in the driver's driving operation (A35), and transmits the driver's driving data from the DCM 7 to the function management server 5 via the communication network (A34).

[0069] The in-vehicle system 3 determines whether the end condition of the driving diagnosis process is satisfied due to, for example, ignition off (A36). When it determines that the ignition is on and the end condition of the driving diagnosis process is not satisfied (A36: NO), it returns to step A21 described above and repeats steps A21 and subsequent steps. When the in-vehicle system 3 determines that the end condition of the driving diagnosis process is satisfied due to ignition off (A36: YES), it displays the driving diagnosis result based on the driver's driving data on the center display, meter display, etc. (A37) and ends the driving diagnosis process. As shown in FIG. 9, the in-vehicle system 3 displays the driving diagnosis results for, for example, six items A to F on the center display, meter display, etc. The six items A to F are each one of the indicators indicating whether the driver's driving is safe, and, for example, evaluate the frequency of sudden acceleration, the frequency of sudden deceleration, the frequency of sudden steering, etc. in five levels.

[0070] Further, as shown in FIG. 10, if the mobile information terminal 6 is in a state where it can communicate with the in-vehicle system 3, when receiving the driving diagnosis result transmitted from the in-vehicle system 3, the received driving diagnosis result may be displayed on the display 6a. Note that, as long as the driver can recognize the driving diagnosis result, the driving diagnosis result displayed on the center display or the meter display of the in-vehicle system 3 and the driving diagnosis result displayed on the display 6a of the mobile information terminal 6 may be displayed in any manner.

[0071] (1-4) Recommended function distribution process performed by the function management server 5 (see FIG. 11) When the start condition of the recommended function distribution process is satisfied, the function management server 5 starts the recommended function distribution process. When starting the recommended function distribution process, the function management server 5 determines whether it has received and acquired the driver's driving data transmitted from the mobile information terminal 6 (B1), determines whether it has received and acquired the driver's question information transmitted from the mobile information terminal 6 (B2), and determines whether it has received and acquired the driver's speech information transmitted from the mobile information terminal 6 (B3).

[0072] When the function management server 5 determines that it has received and acquired the driver's driving data transmitted from the mobile information terminal 6 (B1: YES, corresponding to the driving data acquisition procedure), it identifies a recommended function based on the driver's driving data acquired from the in-vehicle system 3 (B4, corresponding to the first recommended function identification procedure). In this case, the function management server 5 may identify the recommended function by comparing the driver's driving data acquired from the in-vehicle system 3 with the driving data of other drivers at the same location.

[0073] When the function management server 5 determines that it has received and acquired the driver's question information transmitted from the mobile information terminal 6 (B2: YES, corresponding to the question information acquisition procedure), it identifies a recommended function based on the acquired driver's question information (B5, corresponding to the second recommended function identification procedure).

[0074] When the function management server 5 determines that it has received and acquired the driver's speech information transmitted from the mobile information terminal 6 (B3: YES, corresponding to the speech information acquisition procedure), it identifies the recommended function based on the acquired driver's speech information (B6, corresponding to the third recommended function identification procedure).

[0075] When the function management server 5 identifies the recommended function based on any of the driver's driving data, the driver's question information based on the use of the automatic conversation service, and the driver's speech information based on the use of the online communication service using the website in this way, it determines whether the identified recommended function is an already installed function in the vehicle (B7).

[0076] When the function management server 5 determines that the identified recommended function is not already installed in the vehicle and is an uninstalled function (B7: NO), it distributes the software of the identified recommended function to the in-vehicle system 3 (B8), and distributes the recommended function information regarding the identified recommended function to the in-vehicle system 3 (B9, corresponding to the information distribution procedure). On the other hand, when the function management server 5 determines that the identified recommended function is already installed in the vehicle and is an installed function (B7: YES), it distributes the recommended function information to the in-vehicle system 3 without distributing the software of the identified recommended function to the in-vehicle system 3 (B9, corresponding to the information distribution procedure).

[0077] The function management server 5 determines whether the end condition of the recommended function distribution process is satisfied (B10). When it determines that the end condition of the recommended function distribution process is not satisfied (B10: NO), it returns to step B1 described above and repeats steps B1 and subsequent steps. When the in-vehicle system 3 determines that the end condition of the recommended function distribution process is satisfied (B10: YES), it ends the recommended function distribution process.

[0078] (1-5) Recommended function presentation process performed by the in-vehicle system 3 (see FIGS. 12 to 14) When the in-vehicle system 3 receives and acquires the recommended function information transmitted from the function management server 5 and the start condition for the recommended function presentation process is satisfied, the in-vehicle system 3 starts the recommended function presentation process. When the in-vehicle system 3 starts the recommended function presentation process, it determines whether it has received and acquired the software of the recommended function transmitted from the function management server 5 (A41). When the in-vehicle system 3 determines that it has acquired the software of the recommended function (A41: YES), it proceeds to the proposal process when not installed (A42). On the other hand, when the in-vehicle system 3 determines that it has not acquired the software of the recommended function (A41: NO), it proceeds to the proposal process when installed (A43).

[0079] When the in-vehicle system 3 proceeds to the proposal process when not installed, it pre-installs the software of the recommended function downloaded from the function management server 5 (A51), and presents the content of the recommended function specified by the recommended function information by, for example, illustrations or operations (A52, corresponding to the recommended function presentation procedure). The in-vehicle system 3 presents price information regarding the price when purchasing the recommended function, payment information regarding payment, etc. (A53), and waits for the driver to select whether to try or purchase the recommended function (A54, A55).

[0080] When the in-vehicle system 3 determines that the driver has selected to try the recommended function (A54: YES), it temporarily sets the usage right of the recommended function and sets the recommended function to a trialable state (A56). In this case, the in-vehicle system 3 notifies the driver that the recommended function is trialable, for example, by changing the color of the icon display of the recommended function.

[0081] The in-vehicle system 3 sets a deadline for the period of presenting the recommended function, determines whether the preset trial period has elapsed (A57), and when it determines that the trial period has elapsed (A57: YES), it releases the usage right of the recommended function and sets the recommended function to a non-trialable state (A58). In this case, the in-vehicle system 3 notifies the driver that the recommended function is not trialable, for example, by changing the color of the icon display of the recommended function back. The in-vehicle system 3 waits for the completion of the purchase procedure of the recommended function (A59).

[0082] When the in-vehicle system 3 determines that the purchase procedure for the recommended function has been completed because the driver has performed the purchase procedure for the recommended function (A59: YES), the in-vehicle system 3 sets the recommended function to an available state (A60). In this case, the in-vehicle system 3 notifies the driver that the recommended function for which the purchase procedure has been completed is distinguishable from the recommended function for which the purchase procedure has not been completed, for example, by changing the color of the icon display of the recommended function. When the in-vehicle system 3 sets the recommended function to an available state, it ends the proposal process when not installed and returns to the recommended function presentation process, and ends the recommended function presentation process.

[0083] Also, when the in-vehicle system 3 determines that the driver has selected the purchase of the recommended function (A55: YES), it waits for the completion of the purchase procedure for the recommended function without setting the recommended function to a trialable state (A59). When the in-vehicle system 3 determines that the purchase procedure for the recommended function has been completed because the driver has performed the purchase procedure for the recommended function (A59: YES), the in-vehicle system 3 sets the recommended function to an available state (A60).

[0084] On the other hand, when the in-vehicle system 3 shifts to the proposal process at the time of installation, it presents the content of the recommended function specified by the recommended function information by, for example, illustrations or operations (corresponding to the recommended function presentation procedure A61), and sets the available state of the recommended function without presenting the price information, payment information, etc. in the above-mentioned proposal process when not installed (A62). When the in-vehicle system 3 sets the recommended function to an available state, it ends the proposal process at the time of installation, returns to the recommended function presentation process, and ends the recommended function presentation process.

[0085] As described above, according to the first embodiment, the following operational effects can be obtained. In the function management server 5, driving data of the driver is acquired from the in-vehicle system 3 to identify recommended functions, and recommended function information regarding the identified recommended functions is distributed to the in-vehicle system 3. In the in-vehicle system 3, when the recommended function information distributed from the function management server 5 is received and acquired, the recommended functions specified by the acquired recommended function information are presented to the driver. By utilizing the driving data of the driver, identifying functions effective for driving as recommended functions from the analysis results of the driving data, and presenting them to the driver, functions effective for driving can be appropriately presented to the driver, enhancing convenience.

[0086] In the function management server 5, the driving data of the driver is collated with the driving data of other drivers to identify recommended functions. For example, recommended functions can be identified with reference to the driving data of other drivers whose driving operation tendencies are similar.

[0087] In the function management server 5, the driving data of the driver is collated with the driving data of other drivers at the same location to identify recommended functions. For example, recommended functions can be identified with reference to the driving data of other drivers whose driving operation tendencies are similar at the same location, and for example, functions already used by other drivers in the predicted route of the target vehicle can be identified as recommended functions.

[0088] In the function management server 5, question information of the driver in the automatic conversation service is acquired from the portable information terminal 6 to identify recommended functions, and recommended function information regarding the identified recommended functions is distributed to the in-vehicle system 3. In the in-vehicle system 3, when the recommended function information distributed from the function management server 5 is received and acquired, the recommended functions specified by the acquired recommended function information are presented to the driver. By utilizing the question information of the driver in the automatic conversation service, identifying functions of interest as recommended functions from the analysis results of the text of the questions posted by the driver, and presenting them to the driver, functions of interest can be appropriately presented to the driver, enhancing convenience.

[0089] In the function management server 5, driver's speech information in an online communication service using a website is obtained from the mobile information terminal 6 to identify recommended functions, and recommended function information regarding the identified recommended functions is distributed to the in-vehicle system 3. In the in-vehicle system 3, when the recommended function information distributed from the function management server 5 is received and obtained, the recommended functions specified by the obtained recommended function information are presented to the driver. By utilizing the driver's speech information in the online communication service using a website and identifying functions of interest as recommended functions from the analysis results of the text of the driver's posted speech and presenting them to the driver, functions of interest can be appropriately presented to the driver, and convenience can be enhanced.

[0090] In the function management server 5, when it is determined that the recommended function is not installed in the target vehicle, the software of the recommended function is distributed to the in-vehicle system 3. In the in-vehicle system 3, before the driver determines to use the recommended function, the software of the recommended function is downloaded from the function management server 5 and pre-installed. By pre-installing the software of the recommended function before the driver determines to use the recommended function, the driver can immediately use the recommended function when the driver determines to use the recommended function, and convenience can be further enhanced.

[0091] In the function management server 5, the recommended functions are presented to the driver with an expiration date. By attaching an expiration date to the presentation of the recommended functions to the driver, it is possible to avoid presenting functions whose value has disappeared over time as recommended functions to the driver.

[0092] (Second Embodiment) Hereinafter, the second embodiment will be described with reference to FIGS. 15 to 17. The second embodiment is configured to perform driving support when passing by another vehicle as an intervention in the driver's driving operation. The passing-by driving support process performed by the in-vehicle system 3 will be described.

[0093] (2-1) Driving Support Process during Passing by In-Vehicle System 3 (see Figures 15 to 17) When the in-vehicle system 3 determines that it is necessary to intervene in the driver's driving operation and the start condition for the driving support process during passing is satisfied, the in-vehicle system 3 starts the driving support process during passing. When the in-vehicle system 3 starts the driving support process during passing, it determines whether the road condition is such that it is difficult for the host vehicle to pass (A71). For example, when the in-vehicle system 3 determines that the road on which the host vehicle is traveling is a narrow road or it is difficult to secure a forward view from the host vehicle due to an obstacle or the like and determines that the road condition is such that it is difficult for the host vehicle to pass (A71: YES), it defines the timing at which the host vehicle will collide with another vehicle, an obstacle, or the like (A72) and determines whether the current time is more than a predetermined period (for example, 15 seconds before) before the defined timing (A73).

[0094] When the in-vehicle system 3 determines that the current time is more than a predetermined period before the defined timing (A73: YES), it prompts the driver to switch from manual driving to automatic driving (A74) and waits for the driver's approval to switch from manual driving to automatic driving (A75). In this case, the driver can approve the switch from manual driving to automatic driving by, for example, performing a button operation or the like.

[0095] When the in-vehicle system 3 determines that the driver has approved the switch from manual driving to automatic driving (A75: YES), it determines whether it is possible to complete the switch from manual driving to automatic driving before a predetermined period (for example, 10 seconds before) from the start timing of the Minimal Risk Maneuver (hereinafter referred to as MRM) (A76). MRM is vehicle control until reaching the Minimal Risk Condition (MRC) as a countermeasure when an event that cannot drive safely occurs. MRC is the safe state that the vehicle ultimately aims for as a countermeasure when an event that cannot drive safely occurs due to a malfunction of the automatic driving function or the like, and is generally a stopped state in a situation where the accident risk is sufficiently low.

[0096] When the in-vehicle system 3 determines that it is possible to complete the switch from manual driving to autonomous driving more than a predetermined period before the start timing of the MRM (A76: YES), it performs the switch from manual driving to autonomous driving (A77). When the in-vehicle system 3 performs the switch from manual driving to autonomous driving, it starts the oncoming vehicle control, determines whether the oncoming vehicle control is completed (A78), and determines whether an error has occurred before the oncoming vehicle control is completed (A79). When the in-vehicle system 3 determines that the oncoming vehicle control is completed without an error (A78: YES), it stops the host vehicle at a safe location, presents the switch from autonomous driving to manual driving to the driver (A80), and waits for the driver's approval to switch from autonomous driving to manual driving (A81). In this case, the driver can approve the switch from autonomous driving to manual driving by, for example, performing a button operation or the like.

[0097] When the in-vehicle system 3 determines that the driver has approved the switch from autonomous driving to manual driving by performing a button operation or the like (A81: YES), it ends the driving support process during oncoming vehicle control. On the other hand, when the in-vehicle system 3 determines that an error has occurred before the oncoming vehicle control is completed (A79: YES), it reverses the host vehicle, stops it at a safe location, and then retries the oncoming vehicle control (A82), and returns to steps A78 and A79.

[0098] When the in-vehicle system 3 determines that the current time is not more than a predetermined period before the specified timing (A73: NO), or determines that it is not possible to complete the switch from manual driving to autonomous driving more than a predetermined period before the start timing of the MRM (A75: NO), it determines whether the road on which the host vehicle is traveling is a narrow road without lane lines (A83).

[0099] When the in-vehicle system 3 determines that the road on which the host vehicle is traveling is a narrow road without lane markings (A83: YES), it determines whether there is a stopped vehicle or an oncoming vehicle (A84). When the in-vehicle system 3 determines that there is a stopped vehicle or an oncoming vehicle (A84: YES), it determines whether passing is possible (A85). When the in-vehicle system 3 determines that passing is possible (A85: YES), it presents the driving trajectory along the road edge (A86) and ends the driving support process during passing. That is, the driver can perform a driving operation according to the presented driving trajectory along the road edge when the driving trajectory along the road edge is presented.

[0100] When the in-vehicle system 3 determines that the road on which the host vehicle is traveling is not a narrow road without lane markings (A83: NO), it determines whether there is a lane change (A87). When the in-vehicle system 3 determines that there is a lane change (A87: YES), it presents the driving trajectory based on the route direction at the branch, the road conditions at the branch destination, the speed and position of the following vehicle (A88) and ends the driving support process during passing. That is, the driver can perform a driving operation according to the presented driving trajectory based on the route direction at the branch, the road conditions at the branch destination, the speed and position of the following vehicle when the driving trajectory based on the route direction at the branch, the road conditions at the branch destination, the speed and position of the following vehicle is presented.

[0101] When the in-vehicle system 3 determines that there is no stopped vehicle or oncoming vehicle (A84: NO), or determines that there is no lane change (A87: NO), it presents the driving trajectory in the center of the road (A89) and ends the driving support process during passing. That is, the driver can perform a driving operation according to the presented driving trajectory in the center of the road when the driving trajectory in the center of the road is presented. Also, when the in-vehicle system 3 determines that passing is not possible (A85: NO), it presents the driving trajectory to a stoppable position for passing (A90) and ends the driving support process during passing. That is, the driver can perform a driving operation to the stoppable position for passing according to the presented driving trajectory when the driving trajectory to a stoppable position for passing is presented.

[0102] As described above, according to the second embodiment, the following operational effects can be obtained. In the vehicle-mounted system 3, in order to intervene in the driver's driving operation, driving support is provided when the host vehicle passes by another vehicle. Appropriate driving support can be provided when passing by another vehicle.

[0103] (Third Embodiment) Hereinafter, the third embodiment will be described with reference to FIGS. 18 to 19. In the third embodiment, in the vehicle-mounted system 3, after presenting a recommended function to the driver, the driver is asked about the satisfaction level of the presented recommended function, and in the function management server 5, the response results of the satisfaction level of the recommended function from the driver are collected, and the recommended function is specified based on the response results of the satisfaction level. The satisfaction level inquiry process performed by the vehicle-mounted system 3 will be described, and the recommended function specification process based on the satisfaction level performed by the function management server 5 will be described.

[0104] (3-1) Satisfaction Level Inquiry Process Performed by Vehicle-Mounted System 3 (see FIG. 18) When the start condition of the satisfaction level inquiry process is satisfied, the vehicle-mounted system 3 starts the satisfaction level inquiry process. When the vehicle-mounted system 3 starts the satisfaction level inquiry process, after setting the recommended function to the available state as described in the first embodiment, it is determined whether the usage period of the recommended function has reached a predetermined period since the recommended function was set to the available state (A101), and it is determined whether the number of times the recommended function has been used has reached a predetermined number of times since the recommended function was set to the available state (A102).

[0105] In this case, the predetermined period is, for example, a period during which the driver can evaluate the satisfaction level of the recommended function, and it may be a relatively short period if the driver frequently uses the recommended function, and it may be a relatively long period if the driver rarely uses the recommended function. The predetermined number of times is, for example, the number of times the driver can evaluate the satisfaction level of the recommended function, and it may be a relatively large number of times if the usage period per time of the recommended function is relatively short, and it may be a relatively small number of times if the usage period per time of the recommended function is relatively long.

[0106] When in-vehicle system 3 determines that the usage period of the recommended function has reached a predetermined period (A101: YES) since the recommended function was set to the available state, or when it determines that the number of times the recommended function has been used since it was set to the available state has reached a predetermined number (A102: YES), it causes a satisfaction input screen for the recommended function to be displayed on the center display, the meter display, etc. (A103) and waits for an operation input from the driver (A104). The satisfaction input screen is, for example, a screen on which the driver can evaluate the recommended function and input the satisfaction level in five grades.

[0107] When in-vehicle system 3 determines an operation input of satisfaction from the driver (A104: YES), it distributes satisfaction information regarding the operation input satisfaction level to function management server 5 (A105) and ends the satisfaction inquiry process. Note that if the mobile information terminal 6 is in a state where it can communicate with in-vehicle system 3, the satisfaction input screen may be displayed on mobile information terminal 6 and the driver may perform the operation input of satisfaction using mobile information terminal 6. Also, instead of the driver performing the operation input of satisfaction, the voice assistant function may be used and the driver may input the satisfaction level by voice. Further, for a recommended function with a relatively high satisfaction level that the driver has operated and input, in-vehicle system 3 continues to use that recommended function, but for a recommended function with a relatively low satisfaction level that the driver has operated and input, it may stop using that recommended function on the condition that the driver has consented to stop using the recommended function.

[0108] (3-2) Recommended function identification process based on satisfaction performed by function management server 5 (see Fig. 19) When the start condition of the satisfaction level-based recommended function identification process is satisfied, the function management server 5 starts the satisfaction level-based recommended function identification process. When the function management server 5 starts the satisfaction level-based recommended function identification process, it determines whether or not it has received and acquired satisfaction level information transmitted from the in-vehicle system 3 (B101). When it determines that it has received and acquired the satisfaction level information transmitted from the in-vehicle system 3 (B102: YES), the function management server 5 analyzes the satisfaction level identified by the acquired satisfaction level information (B103), identifies a recommended function based on the analysis result (B94), and ends the satisfaction level-based recommended function identification process.

[0109] That is, as described in the first embodiment, the function management server 5 takes satisfaction into consideration when identifying recommended functions based on any one of the driver's driving data, the driver's question information based on the use of an automatic conversation service, and the driver's comment information based on the use of an online communication service using a website. The function management server 5 prioritizes functions that have been rated as having high satisfaction by other drivers of the same vehicle type or model, for example, and identifies functions with relatively high satisfaction as recommended functions, but does not identify functions with relatively low satisfaction as recommended functions.

[0110] Although the above describes an example of a configuration in which the usage period and the number of uses are managed by the in-vehicle system 3, the usage period and the number of uses may be managed by the function management server 5. That is, the in-vehicle system 3 transmits the usage period and the number of uses to the function management server 5, and the function management server 5 manages the usage period and the number of uses for each in-vehicle system 3 and transmits a satisfaction level evaluation instruction to an in-vehicle system 3 whose usage period has reached a predetermined period or whose number of uses has reached a predetermined number. The in-vehicle system 3 may perform a satisfaction level inquiry process upon receiving the satisfaction level evaluation instruction transmitted from the function management server 5.

[0111] As described above, according to the third embodiment, the following advantageous effects can be obtained. In the in-vehicle system 3, after presenting a recommended function to the driver, the driver is asked about the satisfaction level of the presented recommended function, and in the function management server 5, the response results of the satisfaction level of the recommended function from the driver are collected. By specifying the recommended function in reflection of the satisfaction level evaluation, it is possible to present the driver with a recommended function that reflects the satisfaction level evaluation.

[0112] (Fourth Embodiment) Hereinafter, the fourth embodiment will be described with reference to FIGS. 20 to 21. In the fourth embodiment, in the in-vehicle system 3, the function usage history and behavior history of the driver are acquired, the acquired function usage history and behavior history are transmitted to the function management server 5, and in the function management server 5, a recommended function is specified based on the function usage history and behavior history of the driver. The history acquisition process performed by the in-vehicle system 3 will be described, and the recommended function specification process performed by the function management server 5 will be described.

[0113] (4-1) History Acquisition Process Performed by In-Vehicle System 3 (See FIG. 20) When the start condition of the history acquisition process is satisfied, the in-vehicle system 3 starts the history acquisition process. When the in-vehicle system 3 starts the history acquisition process, it acquires the function usage history of the driver (A111), acquires the behavior history of the driver (A112), and saves the acquired function usage history and behavior history in the data storage area (A113). The in-vehicle system 3 determines whether the history transmission condition is satisfied (A114). When it is determined that the history transmission condition is satisfied (A114: YES), it transmits the history information regarding the function usage history and behavior history stored in the data storage area to the function management server 5 (A115), and performs the history acquisition process.

[0114] (4-2) Recommended Function Specification Process Based on History Performed by Function Management Server 5 (See FIG. 21) When the function management server 5 starts the recommended function identification process based on the history, it determines whether it has received and acquired the history information transmitted from the in-vehicle system 3 (B111). When the function management server 5 determines that it has received and acquired the history information transmitted from the in-vehicle system 3 (B111: YES), it analyzes the function usage history and behavior history specified by the acquired history information (B112), identifies the recommended function based on the analysis result (B113), and ends the recommended function identification process based on the history.

[0115] For example, if the in-vehicle system 3 stores, as the function usage history, that the driver activated the Adaptive Cruise Control (hereinafter referred to as ACC) function in the past but could not activate it and ended, and stores, as the behavior history, that the driver plans to drive on an expressway by route search of the navigation app, the function management server 5 identifies the ADAS function including the ACC function as the recommended function.

[0116] In addition, although the above example shows a configuration in which the in-vehicle system 3 manages the driver's function usage history and behavior history, a configuration in which the function management server 5 manages the driver's function usage history and behavior history may also be used. That is, in the in-vehicle system 3, the function usage history and behavior history may be transmitted to the function management server 5, and in the function management server 5, the function usage history and behavior history may be managed for each in-vehicle system 3. Also, the schedule registration function of the mobile information terminal 6 or the like may be used in combination to manage the driver's behavior history.

[0117] As described above, according to the fourth embodiment, the following operational effects can be obtained. In the in-vehicle system 3, the function usage history and behavior history of the driver are acquired, and the acquired function usage history and behavior history are transmitted to the function management server 5. In the function management server 5, recommended functions are specified based on the function usage history and behavior history of the driver, and recommended function information regarding the specified recommended functions is distributed to the in-vehicle system 3. By specifying recommended functions reflecting the function usage history and behavior history of the driver, it is possible to present the driver with recommended functions reflecting the function usage history and behavior history of the driver.

[0118] (Other embodiments) Although the present disclosure has been described based on examples, it is understood that it is not limited to such examples or structures. The present disclosure also includes various modifications and modifications within an equivalent range. In addition, various combinations and forms, and further, other combinations and forms including only one, more, or less than one element thereof, fall within the scope and spirit of the present disclosure.

[0119] The control unit and its method described in the present disclosure may be realized by a dedicated computer provided by configuring a processor and a memory programmed to execute one or more functions embodied by a computer program. Alternatively, the control unit and its method described in the present disclosure may be realized by a dedicated computer provided by configuring a processor with one or more dedicated hardware logic circuits. Or, the control unit and its method described in the present disclosure may be realized by one or more dedicated computers configured by a combination of a processor and a memory programmed to execute one or more functions and a processor configured by one or more hardware logic circuits. Also, the computer program may be stored in a computer-readable non-transitory tangible recording medium as instructions to be executed by a computer.

[0120] It may also cooperate with a driving diagnosis server that performs driving diagnosis based on the driver's driving data, a point function management server that manages points based on the driving diagnosis result and assigns them to the driver, and the like.

Description of Signs

[0121] In the drawings, 1 is a data communication system, 3 is an in-vehicle system, 5 is a function management server, 5a is a driving data acquisition unit, 5b is a first recommended function identification unit, 5c is a question information acquisition unit, 5d is a second recommended function identification unit, 5e is a speech information acquisition unit, 5f is a third recommended function identification unit, 5g is an information distribution unit, and 10a is a notification control unit (recommended function presentation unit).

Claims

1. A data communication system (1) in which a function management server (5) for managing functions related to a vehicle and an in-vehicle system (3) mounted on the vehicle perform data communication, The function management server acquires the driving data of the driver from the in-vehicle system, analyzes the driving technique of the driver from the acquired driving data of the driver to identify a recommended function, and distributes recommended function information regarding the identified recommended function to the in-vehicle system, The in-vehicle system is a data communication system that, when receiving the recommended function information distributed from the function management server, presents the recommended function specified by the received recommended function information to the driver.

2. The data communication system according to claim 1, wherein the function management server identifies the recommended function by comparing the driving data of the driver acquired from the in-vehicle system with the driving data of other drivers.

3. The data communication system according to claim 2, wherein the function management server identifies the recommended function by comparing the driving data of the driver acquired from the in-vehicle system with the driving data of other drivers at the same location.

4. A data communication system (1) in which a function management server (5) for managing functions related to a vehicle and an in-vehicle system (3) mounted on the vehicle perform data communication, The function management server acquires the question information of the driver in the automatic conversation service to identify a recommended function, and distributes recommended function information regarding the identified recommended function to the in-vehicle system, The in-vehicle system is a data communication system that, when receiving the recommended function information distributed from the function management server, presents the recommended function specified by the received recommended function information to the driver.

5. A data communication system (1) in which a function management server (5) for managing functions related to a vehicle and an in-vehicle system (3) mounted on the vehicle perform data communication, The function management server acquires the driver's speech information in an online communication service using a website, identifies a recommended function, and distributes recommended function information regarding the identified recommended function to the in-vehicle system. The in-vehicle system is a data communication system that, when receiving the recommended function information distributed from the function management server, presents the recommended function identified by the received recommended function information to the driver.

6. The function management server determines whether the recommended function is installed in the target vehicle. If it is determined that the recommended function is not installed in the target vehicle, the software of the recommended function is distributed to the in-vehicle system. The in-vehicle system downloads and pre-installs the software of the recommended function from the function management server before the driver decides to use the recommended function. The data communication system according to any one of claims 1 to 5.

7. The in-vehicle system downloads and pre-installs the software of the recommended function from the function management server when presenting the recommended function to the driver. The data communication system according to claim 6.

8. The in-vehicle system presents the recommended function to the driver with a time limit. The data communication system according to claim 7.

9. The in-vehicle system intervenes in the driver's driving operation when it is necessary to do so. The data communication system according to any one of claims 1 to 5.

10. The in-vehicle system intervenes in the driver's driving operation by providing driving assistance when passing by other vehicles. The data communication system according to claim 9.

11. After presenting the recommended function to the driver, the in-vehicle system inquiries the driver about the satisfaction degree of the presented recommended function. The data communication system according to any one of claims 1 to 5, wherein the function management server collects the satisfaction answer results of the recommended functions from the driver.

12. The in-vehicle system acquires a function usage history and a behavior history, The data communication system according to any one of claims 1 to 5, wherein the function management server identifies recommended functions based on the function usage history and behavior history of the driver, and distributes recommended function information regarding the identified recommended functions to the in-vehicle system.

13. A function management server (5) that manages functions related to a vehicle and performs data communication with an in-vehicle system that presents a recommended function identified by the received recommended function information to the driver when receiving the recommended function information distributed from a function management server that manages functions related to the vehicle, A driving data acquisition unit (5a) that acquires driving data of the driver from the in-vehicle system, A first recommended function identification unit (5b) that analyzes the driving skill of the driver from the driving data of the driver to identify a recommended function, An information distribution unit (5g) that distributes recommended function information regarding the recommended function to the in-vehicle system.

14. A function management server (5) that manages functions related to a vehicle and performs data communication with an in-vehicle system that presents a recommended function identified by the received recommended function information to the driver when receiving the recommended function information distributed from a function management server that manages functions related to the vehicle, A question information acquisition unit (5c) that acquires question information of the driver in an automatic conversation service, A second recommended function identification unit (5d) that identifies a recommended function based on the question information of the driver, An information distribution unit (5g) that distributes recommended function information regarding the recommended function to the in-vehicle system.

15. A function management server (5) that performs data communication with an in-vehicle system that presents a recommended function specified by the received recommended function information to a driver when receiving the recommended function information distributed from a function management server that manages functions related to a vehicle. A speech information acquisition unit (5e) that acquires the speech information of a driver in an online communication service using a website. A third recommended function specifying unit (5f) that specifies a recommended function based on the speech information of the driver. A function management server comprising an information distribution unit (5g) that distributes recommended function information related to the recommended function to the in-vehicle system.

16. In a function management server (5) that performs data communication with an in-vehicle system that presents a recommended function specified by the received recommended function information to a driver when receiving the recommended function information distributed from a function management server that manages functions related to a vehicle, A driving data acquisition procedure for acquiring the driving data of the driver from the in-vehicle system, A first recommended function specifying procedure for analyzing the driving technique of the driver from the driving data of the driver and specifying a recommended function, A recommended function distribution program that executes an information distribution procedure for distributing recommended function information related to the recommended function to the in-vehicle system.

17. In a function management server (5) that performs data communication with an in-vehicle system that presents a recommended function specified by the received recommended function information to a driver when receiving the recommended function information distributed from a function management server that manages functions related to a vehicle, A question information acquisition procedure for acquiring the question information of the driver in an automatic conversation service, A second recommended function specifying procedure for specifying a recommended function based on the question information of the driver, A recommended function distribution program that executes an information distribution procedure for distributing recommended function information related to the recommended function to the in-vehicle system.

18. When receiving recommended function information distributed from a function management server that manages functions related to a vehicle, a function management server (5) that performs data communication with an in-vehicle system that presents the recommended functions specified by the received recommended function information to the driver A speech information acquisition procedure for acquiring a driver's speech information in an online communication service using a website, A third recommended function specification procedure for specifying a recommended function based on the driver's speech information, A recommended function distribution program that executes an information distribution procedure for distributing recommended function information related to the recommended function to the in-vehicle system.

19. A data communication system (1) in which a function management server (5) that manages functions related to a vehicle and an in-vehicle system (3) mounted on the vehicle perform data communication, The function management server acquires the driver's driving data from the in-vehicle system, specifies a recommended function, distributes recommended function information related to the specified recommended function to the in-vehicle system, determines whether the recommended function is mounted on the target vehicle, and if it is determined that the recommended function is not mounted on the target vehicle, distributes the software of the recommended function to the in-vehicle system, When the in-vehicle system receives the recommended function information distributed from the function management server, it presents the recommended function specified by the received recommended function information to the driver, and before the driver determines to use the recommended function, downloads and pre-installs the software of the recommended function from the function management server. A data communication system.

20. The data communication system according to claim 19, wherein the function management server identifies the recommended function by comparing the driving data of the driver acquired from the in-vehicle system with the driving data of other drivers.

21. The data communication system according to claim 20, wherein the function management server identifies the recommended function by comparing the driving data of the driver acquired from the in-vehicle system with the driving data of other drivers at the same location. A data communication system (1) in which a function management server (5) for managing functions related to a vehicle and an in-vehicle system (3) mounted on the vehicle perform data communication, The function management server acquires driver's question information in an automatic conversation service, identifies a recommended function, distributes recommended function information regarding the identified recommended function to the in-vehicle system, determines whether the recommended function is mounted on the target vehicle, and when it is determined that the recommended function is not mounted on the target vehicle, distributes the software of the recommended function to the in-vehicle system, The in-vehicle system, when receiving the recommended function information distributed from the function management server, presents the recommended function specified by the received recommended function information to the driver, and downloads and pre-installs the software of the recommended function from the function management server before the driver determines to use the recommended function. A data communication system. The data communication system according to any one of claims 19 to 22, wherein the in-vehicle system downloads and pre-installs the software of the recommended function from the function management server when presenting the recommended function to the driver. The data communication system according to claim 23, wherein the in-vehicle system presents the recommended function to the driver with a time limit.

25. The in-vehicle system intervenes in the driver's driving operation when it is necessary to intervene in the driver's driving operation. The data communication system according to any one of claims 19 to 22.

26. The data communication system according to claim 25, wherein the in-vehicle system performs driving support at the time of passing by another vehicle as an intervention in the driver's driving operation.

27. After presenting the recommended function to the driver, the in-vehicle system inquires the driver about the satisfaction of the presented recommended function, The data communication system according to any one of claims 19 to 22, wherein the function management server collects the satisfaction answer results of the recommended functions from the driver.

28. The in-vehicle system acquires a function usage history and a behavior history, The data communication system according to any one of claims 19 to 22, wherein the function management server identifies recommended functions based on the function usage history and behavior history of the driver, and distributes recommended function information regarding the identified recommended functions to the in-vehicle system.

29. A function management server (5) that manages functions related to a vehicle and performs data communication with an in-vehicle system that presents a recommended function specified by the received recommended function information to a driver when receiving the recommended function information distributed from a function management server that manages functions related to the vehicle, a driving data acquisition unit (5a) that acquires driving data of the driver from the in-vehicle system; a first recommended function identification unit (5b) that identifies a recommended function based on the driving data of the driver; and an information distribution unit (5g) that distributes recommended function information regarding the recommended function to the in-vehicle system. The function management server determines whether the recommended function is installed in the target vehicle, and when it is determined that the recommended function is not installed in the target vehicle, distributes the software of the recommended function to the in-vehicle system.

30. A function management server (5) that manages functions related to a vehicle and performs data communication with an in-vehicle system that presents a recommended function specified by the received recommended function information to a driver when receiving the recommended function information distributed from a function management server that manages functions related to the vehicle, a question information acquisition unit (5c) that acquires question information of the driver in an automatic conversation service; a second recommended function identification unit (5d) that identifies a recommended function based on the question information of the driver; and an information distribution unit (5g) that distributes recommended function information regarding the recommended function to the in-vehicle system. A function management server that determines whether the recommended function is installed in the target vehicle, and if it is determined that the recommended function is not installed in the target vehicle, distributes the software of the recommended function to the in-vehicle system.

31. An in-vehicle system (3) that performs data communication with a function management server that identifies a recommended function based on at least one of the driver's driving data, the driver's question information in an automatic conversation service, and the driver's speech information in an online communication service using a website, distributes recommended function information regarding the identified recommended function to the in-vehicle system, determines whether the recommended function is installed in the target vehicle, and if it is determined that the recommended function is not installed in the target vehicle, distributes the software of the recommended function to the in-vehicle system, An in-vehicle system comprising a recommended function presentation unit (10a) that presents the recommended function identified by the received recommended function information to the driver when receiving the recommended function information distributed from the function management server, and downloads and pre-installs the software of the recommended function from the function management server before the driver determines to use the recommended function.

32. In a function management server (5) that performs data communication with an in-vehicle system that presents the recommended function identified by the received recommended function information to the driver when receiving the recommended function information distributed from a function management server that manages functions related to the vehicle, A driving data acquisition procedure for acquiring the driver's driving data from the in-vehicle system, A first recommended function identification procedure for identifying a recommended function based on the driver's driving data, An information distribution procedure for distributing recommended function information regarding the recommended function to the in-vehicle system, A recommended function distribution program that executes a procedure for determining whether the recommended function is installed in the target vehicle, and if it is determined that the recommended function is not installed in the target vehicle, distributes the software of the recommended function to the in-vehicle system. A function management server (5) that performs data communication with an in-vehicle system that presents a recommended function specified by the received recommended function information to a driver when receiving the recommended function information distributed from a function management server that manages functions related to a vehicle. A question information acquisition procedure for acquiring the driver's question information in an automatic conversation service, A second recommended function specification procedure for specifying a recommended function based on the driver's question information, An information distribution procedure for distributing recommended function information regarding the recommended function to the in-vehicle system, A recommended function distribution program that executes a procedure for determining whether the recommended function is installed in the target vehicle, and if it is determined that the recommended function is not installed in the target vehicle, distributing the software of the recommended function to the in-vehicle system. An in-vehicle system (3) that performs data communication with a function management server that specifies a recommended function based on at least one of the driver's driving data, the driver's question information in an automatic conversation service, and the driver's speech information in an online communication service using a website, and distributes recommended function information regarding the specified recommended function to the in-vehicle system. A recommended function presentation procedure for presenting the recommended function specified by the received recommended function information to the driver when receiving the recommended function information distributed from the function management server, A recommended function presentation program that executes a procedure for downloading and pre-installing the software of the recommended function from the function management server before the driver determines to use the recommended function.

Images