Vehicle information processing device

Abstract

To provide a device for recommending installation of a driving assistance device to a vehicle user.SOLUTION: A vehicle information processing device provided herein is configured to acquire vehicle information (101), use the acquired vehicle information to compute (105) a frequency of lane changes made by a vehicle while driving in the rain within a predetermined travel distance or time period as a rainy weather lane change frequency, and transmit (108) recommendation information for recommending installation of a driving assistance device to a mobile terminal of a user of the vehicle when the rainy weather lane change frequency is equal to or greater than a specified value (106).SELECTED DRAWING: Figure 8

Description

Technical Field

[0001] The present invention relates to a configuration of a vehicle information processing device that processes vehicle information and transmits predetermined information to a mobile terminal of a user of the vehicle.

Background Art

[0002] Devices for processing vehicle information acquired from a vehicle have been proposed. For example, Patent Document 1 discloses a system that acquires traffic information indicating the position, vehicle speed, and presence or absence of lane changes of a vehicle, and based on the traffic information, acquires the number of lane changes made by the vehicle within a predetermined period, and when the number of lane changes made by the vehicle within the predetermined period is equal to or greater than a predetermined number, performs correction to reduce the vehicle speed indicated by the traffic information.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, recently, various driving support devices for assisting driving operations have been developed and are being mounted on newly sold vehicles. In addition, driving support devices that can be retrofitted have also been developed for vehicles that do not have a previously sold driving support device. Here, whether to retrofit a driving support device to a vehicle depends on the judgment of the user of the vehicle, so there is a need for a device that recommends the installation of a driving support device to the user.

[0005] Therefore, an object of the present disclosure is to provide a device that recommends the installation of a driving support device to a user of a vehicle.

Means for Solving the Problems

[0006] The vehicle information processing device of the present disclosure is a vehicle information processing device including a processor that performs information processing. The processor acquires vehicle information, and based on the acquired vehicle information, calculates the frequency of lane changes during rainy-day driving within a predetermined driving distance or within a predetermined period as the rainy-day lane change frequency. When the rainy-day lane change frequency is equal to or greater than a predetermined specified value, recommendation information for recommending the installation of a driving support device is transmitted to the mobile terminal of the user of the vehicle.

[0007] During rainy days, raindrops adhere to the side windows and door mirrors, making it more difficult to check the surrounding situation compared to sunny days, and drivers often feel more difficulty in driving. Therefore, when the frequency of lane changes during rainy-day driving is equal to or greater than a predetermined specified value, the user of the vehicle, who is the driver, is considered to feel more difficulty in driving. Thus, by recommending the installation of a driving support device to the user in such a case, it is possible to prompt the user to purchase a driving support device.

[0008] In the vehicle information processing device of the present disclosure, the processor calculates the frequency of lane changes during sunny or cloudy-day driving within the predetermined driving distance or within the predetermined period based on the acquired vehicle information as the sunny / cloudy-day lane change frequency. When the rainy-day lane change frequency is less than the predetermined specified value and the rainy-day lane change frequency is smaller than the sunny / cloudy-day lane change frequency, the recommendation information may be transmitted to the mobile terminal of the user.

[0009] In this way, when the rainy-day lane change frequency is less than the predetermined specified value and is smaller than the sunny / cloudy-day lane change frequency, it is considered that the user of the vehicle has an aversion to lane changes and tries to avoid lane changes during rainy days as much as possible. Therefore, by recommending the installation of a driving support device to such a user, it is possible to prompt the user to purchase a driving support device.

[0010] In the vehicle information processing apparatus of the present disclosure, when the rainy-day lane change frequency is less than the predetermined specified value and the rainy-day lane change frequency decreases according to time or travel distance, the processor may transmit the recommendation information to the user's mobile terminal.

[0011] As described above, when the rainy-day lane change frequency is less than the predetermined specified value and the rainy-day lane change frequency decreases according to time or travel distance, it is considered that the user feels difficulty in changing lanes on rainy days and tends to avoid changing lanes on rainy days. Therefore, by recommending the installation of a driving support device to the user at this timing, the user can be induced to purchase a driving support device.

[0012] In the vehicle information processing apparatus of the present disclosure, the processor may transmit the recommendation information to the user's mobile terminal on a rainy day.

[0013] On a rainy day, the user feels more difficulty in driving. Therefore, by recommending the installation of a driving support device to the user at this timing, the user can be induced to purchase a driving support device.

Advantages of the Invention

[0014] The present disclosure can provide an apparatus that recommends the installation of a driving support device to a user of a vehicle.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Embodiments for Carrying Out the Invention

[0016] Hereinafter, a vehicle information processing system 100 including a vehicle information processing apparatus according to an embodiment will be described with reference to the drawings. The vehicle information processing system 100 includes a vehicle 10, a server 30 which is a vehicle information processing apparatus, and a user's mobile terminal 40. An in-vehicle terminal 20 is mounted on the vehicle 10. The in-vehicle terminal 20, the server 30, and the user's mobile terminal 40 are interconnected through a network 90. In FIG. 1, one server 30 is connected to one vehicle 10, one in-vehicle terminal 20, and one mobile terminal 40. However, the numbers of the vehicle 10, the in-vehicle terminal 20, and the mobile terminal 40 are not limited to this, and each may be two or more.

[0017] As shown in FIG. 2, the vehicle 10 includes a plurality of ECUs (Electronic Control Units) 11, a plurality of in-vehicle devices 13, and an in-vehicle terminal 20.

[0018] The ECU 11 includes an ADAS-ECU 11A (Advanced Driver Assistance System-ECU), a steering ECU 11B, a brake ECU 11C, an engine ECU 11D, and an accessory ECU 11E. The ADAS-ECU 11A, the steering ECU 11B, the brake ECU 11C, the engine ECU 11D, and the accessory ECU 11E are interconnected by a bus 12 and exchange information with each other. Note that the vehicle 10 may include other ECUs.

[0019] The ADAS-ECU 11A comprehensively controls the advanced driver assistance system. The vehicle speed sensor 13A, yaw rate sensor 13B, and external sensor 13C that make up the in-vehicle device 13 are connected to the ADAS-ECU 11A. The external sensor 13C is a group of sensors used to detect the surrounding environment of the vehicle 10. This external sensor 13C includes, for example, a camera that images the surroundings of the vehicle 10, a millimeter-wave radar that transmits exploration waves and receives reflected waves, and a lidar that scans the front of the vehicle 10.

[0020] The steering ECU 11B controls the power steering. The steering angle sensor 13D and the steering actuator 13E that make up the in-vehicle device 13 are connected to the steering ECU 11B. The steering angle sensor 13D is a sensor that detects the steering angle of the steering wheel. The steering actuator 13E steers the steered wheels of the vehicle 10 according to the driver's operation.

[0021] The brake ECU 11C controls the brake system of the vehicle 10. The brake actuator 13F that makes up the in-vehicle device 13 is connected to the brake ECU 11C. The brake actuator 13F drives the brakes of the vehicle 10 according to the driver's operation.

[0022] The engine ECU 11D controls the engine of the vehicle 10. The throttle actuator 13G that makes up the in-vehicle device 13 is connected to the engine ECU 11D. The throttle actuator 13G drives the throttle of the engine according to the driver's operation.

[0023] The accessory ECU 11E controls the operations of various accessories and receives signals from switches and sensors that drive these accessories. As shown in an example in Figure 2, signals from the wiper lever 13J, the raindrop sensor 13K, and the turn signal switch 13M are input to the accessory ECU 11E. Thereby, the accessory ECU 11E controls the operations of the wiper drive motor 13H and the turn signal lamp 13L.

[0024] As shown in FIG. 2, the in-vehicle terminal 20 is a computer including a CPU 21, a memory 22, a wireless communication interface 23, and an in-vehicle communication interface 24. The CPU 21, the memory 22, the wireless communication interface 23, and the in-vehicle communication interface 24 are connected by an internal bus 25.

[0025] The CPU 21 is a processor that performs information processing. In the memory 22, a control program 26 and control data 27 for executing the control program 26 are stored. The CPU 21 realizes various control operations by executing the control program 26 stored in the memory 22.

[0026] The in-vehicle communication interface 24 is connected to the bus 12 of the vehicle 10, and collects vehicle information related to the state and control of the vehicle 10 from the ADAS-ECU 11A, the steering ECU 11B, the brake ECU 11C, the engine ECU 11D, and the accessory ECU 11E of the vehicle 10 via the bus 12 according to the CAN protocol.

[0027] The wireless communication interface 23 is a wireless communication module connected to the network 90 for communicating with the server 30.

[0028] As shown in FIG. 3, the server 30 is a computer including a CPU 31 that performs information processing, a memory 32 that stores data, and a wireless communication interface 33. The CPU 31, the memory 32, and the wireless communication interface 33 are connected by an internal bus 34. The wireless communication interface 33 is a wireless communication module connected to the network 90 for communicating with the in-vehicle terminal 20 and the mobile terminal 40.

[0029] In the memory 32, a processing program 35, processing program data 36, a driving history database 37, a user information database 38, and a monthly driving history database 39 are stored. Note that other programs and databases may be stored in the memory 32.

[0030] The processing program 35 processes the vehicle information received from the in-vehicle terminal 20 of the vehicle 10, calculates the rainy-day lane change frequency and the cloudy-day lane change frequency, and transmits the recommendation information to the user's mobile terminal 40. The processing program 35 is executed by the CPU 31. The data 36 for the processing program temporarily stores data when the CPU 31 executes the processing program 35 and stores setting values and the like necessary for the execution of the processing program 35. The operation of the server 30 is realized by the CPU 31 executing the processing program 35.

[0031] As shown in FIG. 4, the driving history database 37 is a database that stores, for each vehicle number of the vehicle 10, the extraction time of the driving scene, the type of the extracted driving scene, and the weather in association with each other. The vehicle number is a number assigned to each vehicle 10 driven by each user, as will be described later with reference to FIG. 5. Here, the driving scene includes starting, accelerating, decelerating, stopping, turning, lane changing, merging, parking, and the like. Note that the illustration of accelerating, merging, and parking is omitted. Also, "fine / cloudy" in FIG. 4 indicates a situation where the weather is fine or cloudy and no rain is falling, and "rain" indicates a rainy situation.

[0032] As shown in FIG. 5, the user information database 38 is a database that stores, in association with each other, the user name, the email address of the user's mobile terminal 40, the vehicle number of the vehicle 10 driven by the user, and the driving support device mounted on the vehicle 10. Here, the driving support device mounted on the vehicle 10 includes, for example, a pre-crash brake, a following driving system, a blind spot monitor (BSM), and a parking support system.

[0033] Here, a pre-crash brake alerts the driver when the system determines that there is a risk of collision. At this time, when there is an avoidance operation using the brake, it quickly generates a strong braking force. When there is no avoidance operation, it performs brake control and automatically decelerates or stops. Also, a follow-up driving system, in addition to the cruise control function of maintaining a set constant vehicle speed without continuously pressing the accelerator, follows the speed of the preceding vehicle while maintaining a safe inter-vehicle distance when it catches up with the preceding vehicle. BSM detects other vehicles driving in the adjacent lane with a radar, and in addition to other vehicles in the rear-side area that are difficult to confirm with the door mirror, it also detects other vehicles approaching rapidly. When it detects other vehicles, the LED indicator mounted on the door mirror lights up. A parking support system is a system that, after parking beside the space where it wants to park and pressing the start switch, assists with steering, accelerator, and brake operations while monitoring the surroundings to park the vehicle 10.

[0034] In addition, the vehicle 10 may be equipped with other driving assistance devices and driving assistance systems, or it may be capable of being equipped. In Fig. 5, the ○ mark indicates that the driving assistance device has been installed. Also, the △ mark indicates that the driving assistance device can be installed but has not been installed yet. Further, the × mark indicates that the vehicle 10 does not have a structure capable of installing the driving assistance device and the driving assistance device cannot be installed.

[0035] As shown in Fig. 6, the monthly driving history database 39 is a database that stores the monthly rainy-day lane change frequency and the monthly cloudy-day lane change frequency for each vehicle number.

[0036] As shown in Fig. 7, the user's mobile terminal 40 is a smartphone including a CPU 41 which is a processor for performing information processing, a memory 42 for storing data, a touch panel 43 for displaying and inputting information, and a wireless communication interface 44. The CPU 41, the memory 42, the touch panel 43, and the wireless communication interface 44 are connected by an internal bus 45.

[0037] Next, the operation of the server 30 will be described with reference to FIG. 8. In the following description, the predetermined period is set to one month, and the monthly rainy-day lane change frequency and the cloudy-day lane change frequency are calculated from the driving history of the vehicle 10 for one month, and recommendation information is transmitted to the user's mobile terminal 40.

[0038] When the vehicle 10 is started at the beginning of the month, the server 30 starts acquiring the vehicle information of that month from the in-vehicle terminal 20. The in-vehicle terminal 20 mounted on the vehicle 10 acquires vehicle information from a plurality of in-vehicle devices 13 via a plurality of ECUs 11 and transmits it to the server 30. The CPU 31 receives the vehicle information from the in-vehicle terminal 20 in step 101 of FIG. 8. The vehicle information includes the speed of the vehicle 10, the yaw rate, the information on the surrounding environment of the vehicle 10, the steering angle information of the steering wheel, the operation information of the brake, the operation information of the engine, etc. Further, the vehicle information includes the travel distance and travel time information of the vehicle 10, and the operation information of the wiper and the blinker.

[0039] In step 102 of FIG. 8, the CPU 31 extracts the driving scene information and the weather information of the vehicle 10 based on the vehicle information received from the in-vehicle terminal 20. As described with reference to FIG. 4, the driving scene includes, for example, starting, accelerating, decelerating, stopping, turning, lane changing, merging, parking, etc. Then, the CPU 31 stores the driving scene extracted in step 103 of FIG. 8, the time when the driving scene was extracted, and the weather information at that time in the driving history database 37.

[0040] There are various methods for extracting driving scenes. For example, after the turn signal lamp 13L blinks, the steering actuator 13E operates, a small steering angle is detected, and then, when the blinking of the turn signal lamp 13L stops and the steering actuator 13E operates and the steering angle returns to zero, the driving scene of lane change may be extracted. Also, for weather information, for example, when the wiper drive motor 13H is operating, or when the wiper lever 13J is turned on, or when a rain detection signal is input from the rain drop sensor 13K, the weather may be determined to be rainy. On the other hand, when the wiper drive motor 13H is not operating, or when the wiper lever 13J is turned off, or when no rain detection signal is input from the rain drop sensor 13K, the weather may be determined to be sunny or cloudy.

[0041] The CPU 31 determines whether the transmission timing of the recommendation information has arrived in step 104 of FIG. 8. When transmitting the recommendation information based on the driving history of the vehicle 10 for one month as in this example, the timing when the vehicle 10 is started at the beginning of the month following the month when the acquisition of the vehicle information is started becomes the transmission timing of the recommendation information. When the CPU 31 determines NO in step 104 of FIG. 8, it returns to step 101 of FIG. 8 and continues to extract the driving scene information and the weather information. On the other hand, when the CPU 31 determines YES in step 104 of FIG. 8, it proceeds to step 105 of FIG. 8, calculates the clear / cloudy day lane change frequency and the rainy day lane change frequency, generates the monthly driving history data for that month, and stores it in the monthly driving history database 39.

[0042] The clear / cloudy day lane change frequency is the frequency of lane change during sunny or cloudy driving, and the rainy day lane change frequency is the frequency of lane change during rainy driving, and is calculated by, for example, the following formula. Clear / cloudy day lane change frequency (times / day) =(Number of lane changes during sunny or cloudy driving in one month) / (Number of driving days in one month) ···(Formula 1) Rainy day lane change frequency (times / day) =(Number of lane changes during rainy-day driving in one month) / (Number of driving days in one month) ···(Equation 2)

[0043] The CPU 31 determines in step 106 of FIG. 8 whether the rainy-day lane change frequency for that month is equal to or greater than a predetermined specified value. Here, the predetermined specified value can be freely set, for example, it may be 5.0 / day. And when the rainy-day lane change frequency for that month is equal to or greater than the predetermined specified value, the CPU 31 determines YES in step 106 of FIG. 8 and proceeds to step 107 of FIG. 8.

[0044] In step 107 of FIG. 8, the CPU 31 refers to the user information database 38 shown in FIG. 5 and determines whether the user's vehicle 10 is not equipped with BSM and whether BSM can be installed. Specifically, if a △ is stored in the BSM column of the user information database 38, the CPU 31 determines YES in step 107, and if a 〇 or × is stored in the BSM column of the user information database 38, the CPU 31 determines NO in step 107.

[0045] If the CPU 31 determines YES in step 107 of FIG. 8, it proceeds to step 108 of FIG. 8 and transmits information recommending the installation of BSM to the user's mobile terminal 40. There are various ways of transmission. When sending an email to the user, the CPU 31 refers to the user information database 38 to obtain the user's email address and sends a recommendation email to that email address.

[0046] Thus, the CPU 31 finishes the processing for one month. And when the vehicle 10 is started at the beginning of the next month, the server 30 starts to acquire the vehicle information for the next month.

[0047] On the other hand, if the CPU 31 determines NO in step 106 of FIG. 8, it proceeds to step 109 of FIG. 8 to determine whether the frequency of lane changes on rainy days in that month is less than the frequency of lane changes on cloudy days in that month. Then, if the CPU 31 determines YES in step 109 of FIG. 8, it proceeds to step 107 of FIG. 8 to determine whether the user's vehicle is not equipped with BSM and can be equipped with BSM. Then, if it determines YES in step 107 of FIG. 8, it proceeds to step 108 of FIG. 8 to send a recommendation email for BSM installation to the user's mobile terminal 40, and ends the processing for one month.

[0048] On the other hand, if the CPU 31 determines NO in step 107 of FIG. 8, or determines NO in step 109, it ends the processing for one month without sending a recommendation email.

[0049] As described above, when the frequency of lane changes during rainy-day driving by the server 30, which is a vehicle information processing device, is equal to or higher than a predetermined specified value and it is considered that the user feels difficult to drive, the server 30 recommends the installation of BSM to the user. Therefore, it is possible to cause the user to take a purchasing action for BSM.

[0050] In addition, when the frequency of lane changes on rainy days is less than a predetermined specified value and is also less than the frequency of lane changes on cloudy days, and it is considered that the user tries to avoid lane changes on rainy days as much as possible, the server 30 recommends the installation of BSM to the user. Therefore, it is possible to cause the user to take a purchasing action for BSM.

[0051] Note that in step 108 of FIG. 8, the CPU 31 may not send a recommendation email to the user immediately after the end of a predetermined period, but may send a recommendation email on a rainy day after the end of the predetermined period.

[0052] On rainy days, the user feels more difficulty in driving. Therefore, by sending a recommendation email to the user on a rainy day, it is possible to cause the user to take a purchasing action for BSM.

[0053] Next, other operations of the CPU 31 will be described with reference to FIG. 9. The operation shown in FIG. 9 is different from the operation in step 109 of FIG. 8 in that in step 201 of FIG. 9, it is determined whether the frequency of lane changes in rainy weather is decreasing over time. If it is determined as YES in step 201, a recommendation email is sent to the user's mobile terminal 40. Since the other operations are the same as those described with reference to FIG. 8, the same step numbers are assigned and the description is omitted.

[0054] In step 201 of FIG. 9, the CPU 31 refers to the monthly driving history database 39 shown in FIG. 4 and determines YES when the frequency of lane changes in rainy weather this month is smaller than that of the previous month, and then sends a recommendation email to the user's mobile terminal 40. Also, the CPU 31 refers to the driving history database 37 shown in FIG. 4, calculates the frequency of lane changes in rainy weather at the beginning, middle, and end of this month, and if the frequency of lane changes in rainy weather is gradually decreasing, it may determine YES in step 201 of FIG. 9 and send a recommendation email.

[0055] The operation shown in FIG. 9 sends a recommendation email to the user's mobile terminal 40 when it is considered that the user has difficulty changing lanes. Therefore, this can prompt the user to purchase a BSM.

[0056] In the descriptions of FIGS. 8 and 9, the predetermined period is set as one month, and the monthly frequency of lane changes in rainy weather and the frequency of lane changes in cloudy weather are calculated from the driving history of the vehicle 10 for one month, and recommendation information is sent to the user's mobile terminal 40. However, it is not limited to this. For example, instead of the predetermined period, a predetermined driving distance may be used, and the frequency of lane changes in rainy weather and the frequency of lane changes in cloudy weather are calculated from the driving history within the predetermined driving distance of the vehicle 10, and recommendation information may be sent to the user's mobile terminal 40.

[0057] In this case, the frequency of lane changes in cloudy weather and the frequency of lane changes in rainy weather are calculated by, for example, the following formula. Frequency of lane changes in cloudy weather (times / km) =(Number of lane changes during clear weather driving or cloudy weather driving within a specified driving distance) / (Specified driving distance) ···(Equation 3) Rainy day lane change frequency (times / km) =(Number of lane changes during rainy day driving within a specified driving distance) / (Specified driving distance) ···(Equation 4)

[0058] In addition, the server 30 has a database structure similar to the monthly driving history database 39 shown in FIG. 4 in the memory 32, and stores a specified driving distance operation history database (not shown) that stores the rainy day lane change frequency and the clear / cloudy day lane change frequency between specified driving distances for each vehicle number.

[0059] When the vehicle information processing system 100 for the vehicle 10 starts operating, the CPU 31 starts accumulating the driving distance of the vehicle 10, starts acquiring vehicle information shown in step 101 of FIG. 8, and determines YES in step 104 of FIG. 8 when the driving distance reaches the specified driving distance. Then, in step 105 of FIG. 8, the CPU 31 may generate specified driving distance operation history data instead of creating monthly driving history data and store it in the specified driving distance operation history database, and when the rainy day lane change frequency is equal to or greater than a specified value, in step 108 of FIG. 8, send a recommendation email to the user's mobile terminal 40. At this time, the specified value can be freely set, for example, it may be set to 1 time / km.

[0060] In addition, in the case of other operations shown in FIG. 9, in step 201 of FIG. 9, refer to the specified driving distance operation history database instead of the monthly driving history database 39 shown in FIG. 6, and determine YES when the rainy day lane change frequency within the previous specified driving distance is smaller than the rainy day lane change frequency within the current specified driving distance, and send a recommendation email to the user's mobile terminal 40. Also, the CPU 31 refers to the driving history database 37 shown in FIG. 4, calculates the rainy day lane change frequencies in the previous period, middle period, and later period within the specified driving distance, and when the rainy day lane change frequency is gradually decreasing, determine YES in step 201 of FIG. 9 and send a recommendation email.

[0061] Also, in the above description, the CPU 31 has been described as sending a recommendation email to the user's mobile terminal 40 to recommend the installation of the BSM, but this is not the only case. For example, a user who feels difficulty in changing lanes may also feel difficulty in reverse parking. Therefore, the CPU 31 determines whether the parking assistance system shown in FIG. 5 can be installed but is not installed in step 107 of FIG. 8. If it is determined to be YES, information recommending the installation of the parking assistance system may be sent to the user's mobile terminal 40. Thereby, the user can be made to purchase the parking assistance system.

[0062] Also, in the above description, the user's mobile terminal 40 has been described as a smartphone, but it is not limited to this. For example, it may be a tablet terminal having a communication function or a portable PC having a communication function. Also, the recommendation information may be sent by means other than email. For example, an application related to the driving support device may be installed on the user's mobile terminal 40, and the recommendation information may be sent by the notification function of the application.

[0063] Also, in the above description, the CPU 31 of the server 30 has been described as executing the processing program 35 to perform the processing shown in FIGS. 8 and 9, but this is not the only case. For example, the processing program 35, the processing program data 36, the driving history database 37 of the vehicle 10, the user information database 38, and the monthly driving history database 39 of the vehicle 10 shown in FIG. 3 may be stored in the memory 22 of the in-vehicle terminal 20, and the CPU 21 of the in-vehicle terminal 20 may execute the processing program 35 to execute the processing shown in FIGS. 8 and 9. In this case, the in-vehicle terminal 20 constitutes a vehicle information processing device.

Description of Reference Numerals

[0064] 10 Vehicle, 11 ECU, 11A ADAS-ECU, 11B Steering ECU, 11C Brake ECU, 11D Engine ECU, 11E Auxiliary ECU, 12 Bus, 13 In-vehicle device, 13A Vehicle speed sensor, 13B Yaw rate sensor, 13C External sensor, 13D Steering angle sensor, 13E Steering actuator, 13F Brake actuator, 13G Throttle actuator, 13H Wiper drive motor, 13J Wiper lever, 13K Raindrop sensor, 13L Turn signal lamp, 13M Turn signal switch, 20 In-vehicle terminal, 21, 31, 41 CPU, 22, 32, 42 Memory, 23 Wireless communication interface, 24 In-vehicle communication interface, 25 Internal bus, 26 Control program, 30 Server, 31 CPU, 32 Memory, 33 Wireless communication interface, 34 Internal bus, 35 Processing program, 36 Data for processing program, 37 Driving history database, 38 User information database, 39 Monthly driving history database, 40 Mobile terminal, 43 Touch panel, 44 Wireless communication interface, 45 Internal bus, 90 Network, 100 Vehicle information processing system.

Claims

1. A vehicle information processing device including a processor that performs information processing, wherein the processor, acquires vehicle information, based on the acquired vehicle information, calculates the frequency of lane changes during rainy weather within a predetermined driving distance or within a predetermined period as the rainy-weather lane change frequency, and when the rainy-weather lane change frequency is equal to or greater than a predetermined specified value, transmits recommendation information for recommending installation of a driving assistance device to a mobile terminal of a user of the vehicle. A vehicle information processing device characterized by the above.

2. The vehicle information processing device according to claim 1, wherein the processor calculates the frequency of lane changes during fine or cloudy weather within the predetermined driving distance or within the predetermined period as the fine / cloudy-weather lane change frequency based on the acquired vehicle information, and when the rainy-weather lane change frequency is less than the predetermined specified value and the rainy-weather lane change frequency is smaller than the fine / cloudy-weather lane change frequency, transmits the recommendation information to the mobile terminal of the user. A vehicle information processing device characterized by the above.

3. The vehicle information processing device according to claim 1, wherein the processor, when the rainy-weather lane change frequency is less than the predetermined specified value and the rainy-weather lane change frequency decreases according to time or driving distance, transmits the recommendation information to the mobile terminal of the user. A vehicle information processing device characterized by the above.

4. The vehicle information processing device according to any one of claims 1 to 3, wherein the processor transmits the recommendation information to the mobile terminal of the user on a rainy day. A vehicle information processing device characterized by the above.

Images