Vehicle information processing device

The vehicle information processing device addresses the need for recommending driving support device installations by analyzing specific driving behaviors and transmitting recommendation information to users' mobile terminals, effectively prompting the purchase of such devices.

JP2025091955APending Publication Date: 2025-06-19TOYOTA JIDOSHA KK
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023207521
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-12-08
Publication Date
2025-06-19

AI Technical Summary

Technical Problem

There is a need for a device that recommends the installation of a driving support device to vehicle users, as the decision to retrofit such devices depends on user judgment.

Method used

A vehicle information processing device that acquires vehicle information and, based on specific driving behaviors like reverse steering followed by steering wheel return during lane changes, recommends the installation of a driving support device to the user's mobile terminal.

Benefits of technology

The device effectively prompts users to purchase driving support devices by recommending their installation based on identified high-risk driving behaviors, thereby enhancing user safety.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025091955000001_ABST
    Figure 2025091955000001_ABST
Patent Text Reader

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), and use the acquired vehicle information to transmit (108) recommendation information for recommending installation of a driving assistance device to a mobile terminal of a user of a vehicle when the user steers back the vehicle while in attempt to change lanes and then retries (106).SELECTED DRAWING: Figure 3
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

Background Art

[0002] An apparatus for processing vehicle information acquired from a vehicle has 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 change of a vehicle, and based on the traffic information, acquires the number of times the vehicle has changed lanes within a predetermined period, and when the number of times the vehicle has changed lanes within the predetermined period is equal to or more 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 driving support devices sold previously. Here, whether to retrofit a driving support device to a vehicle depends on the judgment of the user of the vehicle, and thus 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 according to the present invention 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, when a steering wheel return is performed after a reverse steering is performed during a lane change, recommendation information for recommending the installation of a driving support device is transmitted to the mobile terminal of the user of the vehicle.

[0007] A user of a vehicle who is a driver with a large number of lane changes or a high frequency of lane changes may not be bad at lane changes and may think that they can do without a driving support device. On the other hand, the experience of performing a reverse steering and then a steering wheel return 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 a steering wheel return is performed after a reverse steering is performed during a lane change, the user can be caused to purchase a driving support device.

Advantages of the Invention

[0008] According to the vehicle information processing device of the present invention, it is possible to provide a device that recommends the installation of a driving support device to the user of the vehicle.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Embodiments for Carrying Out the Invention

[0010] 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. 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.

[0011] 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.

[0012] The ECUs 11 include 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.

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

[0014] The steering ECU 11B controls the power steering. The steering ECU 11B is connected to a steering angle sensor 13D and a steering actuator 13E that constitute 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 operation of the driver.

[0015] The brake ECU 11C controls the brake system of the vehicle 10. The brake ECU 11C is connected to a brake actuator 13H that constitutes the in-vehicle device 13. The brake actuator 13H drives the brakes of the vehicle 10 according to the operation of the driver.

[0016] The engine ECU 11D controls the engine of the vehicle 10. The engine ECU 11D is connected to a throttle actuator 13J that constitutes the in-vehicle device 13. The throttle actuator 13J drives the throttle of the engine according to the operation of the driver.

[0017] 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, a signal from a 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.

[0018] As shown in Figure 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.

[0019] 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.

[0020] 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.

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

[0022] Again, as shown in FIG. 1, 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 the network 90 for communicating with the in-vehicle terminal 20 and the mobile terminal 40.

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

[0024] 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 "avoidance action during lane change" during driving, the details of which will be described later, the recommendation information is transmitted to the user's mobile terminal 40. The processing program 35 is executed by the CPU 31. The data for the processing program 36 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.

[0025] 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. Here, the driving scene includes starting, accelerating, decelerating, stopping, turning, lane change, merging, parking, avoidance actions during lane change, and the like.

[0026] 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 follow-up driving system, a blind spot monitor (BSM), and a parking support system.

[0027] 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. The follow-up driving system, in addition to the cruise control function of maintaining a set constant vehicle speed without continuously stepping on the accelerator, follows the vehicle speed of the preceding vehicle while maintaining a safe inter-vehicle distance when catching up with the preceding vehicle. The BSM detects other vehicles running 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. The parking support system is a system that, after stopping beside the space where it wants to park and pressing the start switch, assists the steering, accelerator, and brake operations while monitoring the surroundings to park the vehicle 10.

[0028] In addition, the vehicle 10 may be equipped with other driving support devices or driving support systems, or may be capable of being equipped with them.

[0029] Again, as shown in FIG. 1, 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.

[0030] Next, the operation of the server 30 will be described with reference to FIG. 3. In step 101, the CPU 31 determines whether the vehicle 10 has started running. The CPU 31 may determine that the running has started, for example, when the power switch and the ignition switch are turned ON. If the CPU 31 determines YES in step 101, it proceeds to step 102.

[0031] 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, for example, 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.

[0032] 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. The driving scene includes, for example, starting, accelerating, decelerating, stopping, turning, lane changing, merging, parking, avoidance actions during lane changing, 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.

[0033] There are various methods for extracting driving scenarios. In this embodiment, the driving scenario of "avoidance behavior during lane change" will be described. "Avoidance behavior during lane change" refers to the behavior of avoiding a vehicle by steering as a result of attempting to change lanes despite a vehicle traveling beside it. Specifically, in "avoidance behavior during lane change", after reverse steering is performed during lane change, a return steering is then performed.

[0034] FIG. 4 shows an example of the blinking of the turn signal lamp 13L and the steering angle of the steering wheel when "avoidance behavior during lane change" is performed. As shown in FIG. 3, "avoidance behavior during lane change", as described above, for example, when attempting to change lanes to the right, the vehicle is slightly steered to the right (point A in FIG. 3), steered significantly to the left (reverse steering: point B in FIG. 3), and then steered significantly to the right (return steering: point C in FIG. 3). Therefore, by capturing the key points of this feature, it is extracted as the driving scenario of "avoidance behavior during lane change".

[0035] For example, like the transition from point A to point B in FIG. 4, when the turn signal lamp 13L is blinking and the steering speed in the reverse direction (the slope of the steering angle in the graph of FIG. 4) is equal to or higher than a predetermined speed, the driving scenario of "avoidance behavior during lane change" may be extracted. Also, like the transition from point B to point C in FIG. 4, when the turn signal lamp 13L is blinking and the return steering speed (the slope of the steering angle in the graph of FIG. 4) is equal to or higher than a predetermined speed, the driving scenario of "avoidance behavior during lane change" may be extracted. Furthermore, as shown at point B in FIG. 4, when the turn signal lamp 13L is blinking and the steering angle in the reverse direction is equal to or greater than a predetermined angle, the driving scenario of "avoidance behavior during lane change" may be extracted. Additionally, like the difference between point B and point C in FIG. 4, when the absolute value of the steering angle of the steering wheel from reverse steering to return steering is equal to or greater than a predetermined angle, the driving scenario of "avoidance behavior during lane change" may be extracted.

[0036] 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.

[0037] In step 106, the CPU 31 determines whether the driving scene of the above-described "avoidance behavior during lane change" has been extracted at least once. If the CPU 31 determines YES in step 106, it proceeds to step 107.

[0038] In step 107, the CPU 31 refers to the user information database 38 and determines whether the user's vehicle 10 is not equipped with a BSM and whether it is possible to install a BSM.

[0039] If the CPU 31 determines YES in step 107, it proceeds to step 108 and transmits information recommending the installation of a 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.

[0040] The information recommending the installation of a BSM preferably includes the position information where the driving scene of "avoidance behavior during lane change" occurred. The position information may be an address or position information using a specific place name such as "500M north from the XX intersection on the XX line". Thereby, the user can be reminded of having performed an avoidance behavior during lane change, and the user can be induced to purchase a driving assistance device.

[0041] As described above, when the server 30, which is a vehicle information processing device, performs an avoidance action at least once during a lane change while the vehicle is in motion, it recommends to the user that they install a BSM. For this reason, it is possible to prompt the user to purchase a BSM. By sending recommendation information to the user at the end of a drive when there is a record of having actually performed an avoidance action during a lane change, it is possible to prompt the user to purchase a driving support device.

[0042] For example, in the above description, the CPU 31 has been described as sending a recommendation email to the user's mobile terminal 40 to recommend installing a BSM, but this is not the only way. A user who feels difficulty in changing lanes is likely to also feel difficulty in reverse parking, for example. Therefore, the CPU 31 determines in step 107 whether a parking support system is not installed and can be installed. If it determines YES, it may send information recommending installation of the parking support system to the user's mobile terminal 40. Thereby, it is possible to prompt the user to purchase a parking support system.

[0043] Also, in the above description, the user's mobile terminal 40 has been described as being a smartphone, but this is not the only case. For example, it may be a tablet terminal equipped with a communication function, or a portable PC equipped with 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 using the notification function of that application.

[0044] 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 FIG. 3, but this is not the only case. For example, the processing program 35, the data for the processing program 36, the driving history database 37 of the vehicle 10, and the user information database 38 shown in FIG. 1 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 perform the processing shown in FIG. 3. In this case, the in-vehicle terminal 20 constitutes a vehicle information processing device.

Description of Symbols

[0045] 10 Vehicle, 11 ECU, 11A ADAS-ECU, 11B Steering ECU, 11C Brake ECU, 11D Engine ECU, 11E Auxiliary Equipment ECU, 12 Bus, 13 On-vehicle Equipment, 13A Vehicle Speed Sensor, 13B Yaw Rate Sensor, 13C External Sensor, 13D Steering Angle Sensor, 13E Steering Actuator, 13H Brake Actuator, 13J Throttle Actuator, 13K Winker Switch, 13L Winker Lamp, 20 On-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, 27 Control Data, 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

【Claim 1】 A vehicle information processing apparatus including a processor that performs information processing, wherein the processor, acquires vehicle information, and based on the acquired vehicle information, when a return is performed after a reverse steering 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. A vehicle information processing apparatus characterized by the above.

Citation Information

Patent Citations

  • Vehicle having over-steer inhibitory control adjusted to driver's counter steer

    JP2007131296A

  • Steering support device

    JP2018203121A

  • Traffic information analysis system, method and program

    JP2014164452A