Vehicle information processing device
The vehicle information processing apparatus addresses the need for recommending driving support device installations by alerting users to purchase such devices after an emergency braking operation during a lane change, effectively prompting users through timely recommendation transmissions.
Patent Information
- Application Number
- JP2023207397
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-12-08
- Publication Date
- 2025-06-19
- Estimated Expiration
- 2043-12-08
AI Technical Summary
There is a need for a device that recommends the installation of driving support devices to vehicle users, as the decision to retrofit such devices often depends on user judgment.
A vehicle information processing apparatus that acquires vehicle information and recommends the installation of a driving support device to the user's mobile terminal when an emergency braking operation is performed during a lane change, thereby prompting the user to purchase the device.
The apparatus effectively prompts users to purchase driving support devices by transmitting recommendation information to the user's mobile terminal while the memory of an emergency braking operation during a lane change is still fresh, enhancing user awareness and likelihood of purchasing the devices.
Smart Images

Figure 2025091873000001_ABST
Abstract
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, acquires the number of lane changes made by the vehicle within a predetermined period based on the traffic information, and performs correction to reduce the vehicle speed indicated by the traffic information when the number of lane changes made by the vehicle within the predetermined period is equal to or greater than a predetermined number.
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 installed in newly sold vehicles. In addition, driving support devices that can be retrofitted have also been developed for vehicles that do not have previously sold driving support devices installed. Here, whether to retrofit a driving support device to a vehicle depends on the judgment of the user of the vehicle, and thus a device for recommending the installation of a driving support device to the user is required.
[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 apparatus according to the present invention is a vehicle information processing apparatus including a processor that performs information processing. The processor acquires vehicle information, and based on the acquired vehicle information, when an emergency braking operation is performed during a lane change, recommends information for recommending the installation of a driving support device to a mobile terminal of a user of the vehicle, and transmits the information.
[0007] Here, a user of a vehicle who is a driver with a large number of lane change times or frequency may not be poor at lane changes and may think that it is okay without a driving support device. On the other hand, an experience of stepping on the emergency brake during a lane change strongly remains in the user's memory even if an accident does not actually occur. Therefore, by recommending the installation of a driving support device to the user when an emergency braking operation is performed during a lane change, it is possible to cause the user to take a purchasing action of the driving support device.
[0008] In the vehicle information processing apparatus according to the present invention, it is preferable that the processor transmits the recommendation information to the mobile terminal of the user of the vehicle at the end of traveling.
[0009] With the above configuration, by transmitting the recommendation information to the user while there is still a memory of actually performing an emergency braking operation during a lane change, it is possible to cause the user to take a purchasing action of the driving support device.
[0010] In the vehicle information processing apparatus according to the present invention, it is preferable that the recommendation information includes position information where an emergency braking operation is performed during a lane change.
[0011] With the above configuration, it is possible to make the user remember that an emergency braking operation was performed during a lane change and cause the user to take a purchasing action of the driving support device.
Effects of the Invention
[0012] According to the vehicle information processing apparatus of the present invention, it is possible to provide an apparatus that recommends the installation of a driving support device to a user of a vehicle.
Brief Description of the Drawings
[0013]
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Embodiments for Carrying Out the Invention
[0014] Hereinafter, a vehicle information processing system 100 including the vehicle information processing apparatus according to the embodiment will be described with reference to the drawings. As shown in FIG. 1, 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, but the numbers of the vehicle 10, the in-vehicle terminal 20, and the mobile terminal 40 are not limited to this, and may be two or more respectively.
[0015] 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.
[0016] 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 via a bus 12 to exchange information with each other. Note that the vehicle 10 may include other ECUs.
[0017] The ADAS-ECU 11A comprehensively controls the advanced driver assistance system. Connected to the ADAS-ECU 11A are a vehicle speed sensor 13A, a yaw rate sensor 13B, and an external sensor 13C that make up the in-vehicle device 13. 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 detection waves and receives reflected waves, and a lidar that scans the front of the vehicle 10.
[0018] The steering ECU 11B controls the power steering. Connected to the steering ECU 11B are a steering angle sensor 13D and a steering actuator 13E that make up the in-vehicle device 13. 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.
[0019] The brake ECU 11C controls the brake system of the vehicle 10. Connected to the brake ECU 11C are a brake pedal stroke sensor 13F, a brake hydraulic pressure sensor 13G, and a brake actuator 13H that make up the in-vehicle device 13. The brake pedal stroke sensor 13F is a sensor that detects the stroke amount of the brake pedal. The brake hydraulic pressure sensor 13G is a sensor that detects the hydraulic pressure of the brake. The brake actuator 13H drives the brakes of the vehicle 10 according to the driver's operation.
[0020] The engine ECU 11D controls the engine of the vehicle 10. A throttle actuator 13J that constitutes the in-vehicle device 13 is connected to the engine ECU 11D. The throttle actuator 13J drives the throttle of the engine according to the driver's operation.
[0021] 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 FIG. 2, a signal from the turn signal switch 13K is input to the accessory ECU 11E. Thereby, the accessory ECU 11E controls the operation of the turn signal lamp 13L.
[0022] 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.
[0023] The CPU 21 is a processor that performs information processing. The memory 22 stores a control program 26 and control data 27 for executing the control program 26. The CPU 21 realizes various control operations by executing the control program 26 stored in the memory 22.
[0024] 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.
[0025] The wireless communication interface 23 is a wireless communication module connected to the network 90 for communicating with the server 30.
[0026] As shown in FIG. 3, the server 30 is a computer including a CPU 31 which is a processor for performing information processing, a memory 32 for storing 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 a network 90 for communicating with the in-vehicle terminal 20 and the mobile terminal 40.
[0027] Stored in the memory 32 are a processing program 35, data 36 for the processing program, a driving history database 37, and a user information database 38. Note that other programs and databases may also be stored in the memory 32.
[0028] The processing program 35 processes the vehicle information received from the in-vehicle terminal 20 of the vehicle 10, and when there is at least one "sudden braking during lane change" during driving, the details of which will be described later, it transmits 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.
[0029] 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 and the type of the extracted driving scene 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, sudden braking during lane change, and the like.
[0030] As shown in FIG. 5, the user information database 38 is a database that stores by associating a 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.
[0031] Here, the 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 by the brake, it quickly generates a strong braking force, and when there is no avoidance operation, it performs brake control and automatically decelerates or stops. Also, the following driving system, in addition to the cruise control function of maintaining a set constant vehicle speed without continuously stepping on the accelerator, when catching up with the preceding vehicle, follows the speed of the preceding vehicle while maintaining a safe inter-vehicle distance. The 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, also detects other vehicles approaching rapidly. Then, when detecting other vehicles, the LED indicator mounted on the door mirror lights up. The parking support system is a system that, after parking beside the space where it wants to park and pressing the start switch, assists in steering, accelerator, and brake operations while monitoring the surroundings to park the vehicle 10.
[0032] In addition, the vehicle 10 may be equipped with other driving support devices or driving support systems, or it may be possible to be equipped with them. In FIG. 5, the ○ mark indicates that the driving support device has been installed. Also, the △ mark indicates that the driving support device can be installed but has not been installed yet. Also, the × mark indicates that the vehicle 10 does not have a structure that can mount the driving support device and the driving support device cannot be installed.
[0033] As shown in FIG. 6, 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.
[0034] Next, the operation of the server 30 will be described with reference to FIG. 7. In step 101, the CPU 31 determines whether the vehicle 10 has started running. For example, when the power switch and the ignition switch are turned on, the CPU 31 may determine that the running has ended. If the CPU 31 determines YES in step 101, it proceeds to step 102.
[0035] In step 102, the CPU 31 receives vehicle information from the in-vehicle terminal 20 mounted on the vehicle 10. The vehicle information is obtained by the in-vehicle terminal 20 from a plurality of in-vehicle devices 13 via a plurality of ECUs 11. The vehicle information includes the speed of the vehicle 10, the yaw rate, the position information 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 of the vehicle 10, the information of the travel time, and the operation information of the wiper and the turn signal.
[0036] In step 103, the CPU 31 extracts the driving scene 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 scenes include, for example, starting, accelerating, decelerating, stopping, turning, lane changing, merging, parking, sudden braking during driving, etc. Then, in step 104, the CPU 31 stores the extracted driving scene, the time when the driving scene was extracted, and the position information where the driving scene was extracted in the driving history database 37.
[0037] There are various methods for extracting driving scenes. In this embodiment, the driving scene of "emergency braking during lane change" will be described. For example, within a predetermined time, if the driving scene of "lane change" is extracted and the driving scene of "emergency braking" is extracted, the driving scene of "emergency braking during lane change" may be extracted. Also, for the driving scene of "lane change", after the turn signal lamp 13L blinks, the steering actuator 13E operates, a small steering angle is detected, then the blinking of the turn signal lamp 13L stops, the steering actuator 13E operates, and when the steering angle returns to zero, the driving scene of "lane change" may be extracted. Further, for the driving scene of "emergency braking", if the brake hydraulic pressure changes by a predetermined amount within a predetermined time, or if the deceleration is equal to or greater than a predetermined deceleration, the driving scene of "emergency braking" may be extracted.
[0038] In step 105, the CPU 31 determines whether the running of the vehicle 10 has ended. For example, when the power switch and the ignition switch are turned off, the CPU 31 may determine that the running has ended. If the CPU 31 determines YES in step 105, it proceeds to step 106.
[0039] In step 106, the CPU 31 determines whether the driving scene of "emergency braking during lane change" described above has been extracted at least once. If the CPU 31 determines YES in step 106, it proceeds to step 107.
[0040] In step 107, 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 triangle is stored in the BSM column of the user information database 38, the CPU 31 determines YES in step 107, and if a circle or a cross is stored in the BSM column of the user information database 38, the CPU 31 determines NO in step 107.
[0041] When the CPU 31 determines YES in step 107, it proceeds to step 108 and transmits information recommending the installation of the 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.
[0042] The information recommending the installation of the BSM preferably includes position information on the location where the driving scene of "sudden braking during lane change" occurred. The position information may be an address or may be position information using a specific place name such as "500M north from the XX intersection on the XX line". Thereby, it is possible to make the user recall that a sudden braking operation was performed during lane change and to prompt the user to purchase a driving assistance device.
[0043] As described above, when the server 30, which is a vehicle information processing device, detects that a sudden braking operation has been performed at least once during lane change during driving, it recommends to the user the installation of the BSM. Therefore, it is possible to prompt the user to purchase the BSM. By transmitting the recommendation information to the user at the end of driving when there is a memory of actually performing a sudden braking operation during lane change, it is possible to prompt the user to purchase a driving assistance device.
[0044] For example, in the above description, the CPU 31 has been described as sending a recommendation email recommending the installation of the BSM to the user's mobile terminal 40, but it is not limited to this. Since a user who feels difficulty in changing lanes is considered to also feel difficulty in reverse parking, for example, the CPU 31 determines in step 107 whether a parking assistance system is not installed and can be installed. If it determines YES, it may transmit information recommending the installation of the parking assistance system to the user's mobile terminal 40. Thereby, it is possible to prompt the user to purchase the parking assistance system.
[0045] In the above description, the user's mobile terminal 40 is described as a smartphone, but it is not limited to this. For example, it may also be a tablet terminal equipped with a communication function or a mobile PC equipped with a communication function. Also, the transmission of the recommendation information may be performed 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 transmitted by the notification function of the application.
[0046] In the above description, it is explained that the CPU 31 of the server 30 executes the processing program 35 to perform the processing shown in FIG. 7, but it is not limited to this. For example, the processing program 35, the processing program data 36, the driving history database 37 of the vehicle 10, and the user information database 38 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 FIG. 7. In this case, the in-vehicle terminal 20 constitutes a vehicle information processing device.
Explanation of Reference Numerals
[0047] 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 pedal stroke sensor, 13G Brake hydraulic pressure sensor, 13H Brake actuator, 13J Throttle actuator, 13K Turn signal switch, 13L Turn signal lamp, 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, 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, and based on the acquired vehicle information, when an emergency braking operation is performed during a lane change, transmits recommendation information for recommending the installation of a driving support device to a mobile terminal of a user of the vehicle, and is characterized by the above.
2. The vehicle information processing device according to claim 1, wherein the processor transmits the recommendation information to the mobile terminal of the user of the vehicle at the end of driving, and is characterized by the above.
3. The vehicle information processing device according to claim 1, wherein the recommendation information includes position information where the emergency braking operation was performed during the lane change, and is characterized by the above.
Citation Information
Patent Citations
Data communication system, function management server, on-vehicle system, recommended function delivery program and recommended function presentation program
JP2023072635A
Information management device, information management method, and program
JP2025030693A
Information processing device, information processing system, and information processing method
JP2025078447A
Data communication system, function management server, in-vehicle system, and non-transitory computer readable storage medium
US20240289105A1
Traffic information analysis system, method and program
JP2014164452A