Vehicle abnormality notification device and vehicle abnormality notification method

The vehicle abnormality notification device addresses the issue of high user burden and low parts utilization by adjusting notification timing and content based on user behavior, enhancing parts usage and reducing failure risks.

JP7588011B2Active Publication Date: 2024-11-21NISSAN MOTOR CO LTD +1
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2021042216
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-03-16
Publication Date
2024-11-21
Estimated Expiration
2041-03-16

AI Technical Summary

Technical Problem

Existing vehicle failure prediction systems increase the burden on users by prompting immediate repairs, leading to low parts utilization rates.

Method used

A vehicle abnormality notification device that detects abnormalities, references user action history, and sends notifications based on travel distance or time since the first notification, adjusting timing and message content according to user behavior patterns.

Benefits of technology

This approach increases parts utilization rates and reduces user burden by optimizing notification timing and content based on user behavior, thereby minimizing failure risks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007588011000001
    Figure 0007588011000001
  • Figure 0007588011000002
    Figure 0007588011000002
  • Figure 0007588011000003
    Figure 0007588011000003
Patent Text Reader

Abstract

To provide a vehicle abnormality notification apparatus and a vehicle abnormality notification method capable of improving a utilization rate of components to reduce a burden of a user.SOLUTION: A vehicle abnormality notification apparatus 20 includes: a storage apparatus 27 that stores an action history from when a first notification relating to a predetermined action to a vehicle is performed until a user performs the action; and a controller 22. The controller 22 detects an abnormality of the vehicle, refers to the action history stored in the storage apparatus 27, determines a timing of transmitting a second notification different from the first notification relating to the abnormality of the vehicle to the user according to a time period or a travel distance from the first notification until the action is performed, and performs the second notification to the user at the determined timing.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a vehicle abnormality notification device and a vehicle abnormality notification method. [Background technology]

[0002] Conventionally, there are known inventions that warn customers before a breakdown occurs (Patent Document 1). The invention described in Patent Document 1 compares vehicle data from a vehicle that is a target for failure prediction with vehicle data from other vehicles, and predicts the occurrence of a breakdown based on the comparison results. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2004-268633 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, if the user is notified when a failure is predicted, as in the invention described in Patent Document 1, users who act quickly will repair the vehicle immediately, which may result in a low utilization rate of parts and increase the burden on the user.

[0005] The present invention has been made in consideration of the above problems, and its object is to provide a vehicle abnormality notification device and a vehicle abnormality notification method that can increase the utilization rate of parts and reduce the burden on users. [Means for solving the problem]

[0006] A vehicle abnormality notification device according to one embodiment of the present invention detects an abnormality in a vehicle, refers to an action history stored in a storage device, and determines the timing of sending a second notification, different from the first notification, regarding the vehicle abnormality to a user depending on the time or distance traveled from the first notification to the time the action is taken, and sends the second notification to the user at the determined timing. Effect of the Invention

[0007] According to the present invention, it is possible to increase the utilization rate of parts and reduce the burden on users. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic diagram of a vehicle abnormality notification system 10 according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram illustrating the behavior history stored in the database 28. As shown in FIG. [Diagram 3] FIG. 3 is a diagram illustrating an example of notification timing. [Figure 4] FIG. 4 is a flowchart illustrating an example of the operation of the vehicle abnormality notification device 20 according to the first embodiment of the present invention. [Diagram 5] FIG. 5 is a schematic configuration diagram of a vehicle abnormality notification system 10 according to a second embodiment of the present invention. [Figure 6] FIG. 6 is a diagram for explaining the refueling history stored in the database 28. As shown in FIG. [Figure 7] FIG. 7 is a flowchart illustrating an example of the operation of the vehicle abnormality notification device 20 according to the second embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the description of the drawings, the same parts are given the same reference numerals and the description will be omitted.

[0010] (First embodiment) An example of the configuration of a vehicle abnormality notification system 10 according to the first embodiment will be described with reference to Fig. 1. As shown in Fig. 1, the vehicle abnormality notification system 10 includes a vehicle abnormality notification device 20, a communication network 30, and a vehicle 40.

[0011] The vehicle abnormality notification device 20 communicates with the vehicle 40 via the communication network 30. The vehicle abnormality notification device 20 includes a communication I / F 21, a controller 22, and a storage device 27. The location where the vehicle abnormality notification device 20 is installed is not particularly limited, but the vehicle abnormality notification device 20 is installed, for example, in a management center for managing the vehicle 40.

[0012] The communication I / F 21 is implemented as hardware such as a network adapter, various communication software, or a combination of these, and is configured to realize wired or wireless communication via the communication network 30. In addition, the communication I / F 21 has functions as an input unit and an output unit for transmitting and receiving data.

[0013] The communication network 30 may be configured using either a wireless or wired system, or both, and may include the Internet. In this embodiment, the vehicle abnormality notification device 20 and the vehicle 40 are connected to the communication network 30 using a wireless communication system.

[0014] The controller 22 is a general-purpose microcomputer equipped with a CPU (Central Processing Unit), a memory, and an input / output unit. A computer program for functioning as the vehicle abnormality notification device 20 is installed in the microcomputer. By executing the computer program, the microcomputer functions as a plurality of information processing circuits equipped in the vehicle abnormality notification device 20. Note that here, an example is shown in which the plurality of information processing circuits equipped in the vehicle abnormality notification device 20 are realized by software, but it is of course possible to configure the information processing circuit by preparing dedicated hardware for executing each information process shown below. In addition, the plurality of information processing circuits may be configured by individual hardware. The controller 22 is equipped with a transmission control unit 23, an abnormality determination unit 24, a notification determination unit 25, and a message selection unit 26 as an example of a plurality of information processing circuits.

[0015] The storage device 27 is a storage medium such as a hard disk drive (HDD) or a solid state drive (SSD). A database 28 is stored in the storage device 27. The database 28 stores an action history for each vehicle from when a notification of a predetermined action is made to the vehicle until the user takes the action. The notification of a predetermined action to the vehicle is an alert notification such as "An abnormality has been detected in XX. Please check it." In this case, the predetermined action means requesting, reserving, or carrying out repairs on the vehicle at a predetermined location. That is, the database 28 stores an action history (repair history) of when the user repaired the vehicle after an alert notification was made in the past. This makes it possible to determine whether the user is repairing the vehicle at the timing of a legal inspection or vehicle inspection. The action history also includes an alert notification history. In addition, the database 28 stores a method of notifying an alert for each vehicle. A vehicle may be used by multiple users. The above history and information may be stored in a state where the vehicle and the user are linked to each other.

[0016] The transmission control unit 23 transmits the message to the vehicle 40 at the timing determined by the notification determination unit 25.

[0017] The abnormality determination unit 24 determines, based on the data received from the vehicle 40, whether or not an abnormality has occurred.

[0018] The notification determination unit 25 determines the timing for notifying the vehicle 40 that an abnormality has occurred. Hereinafter, this timing may be simply referred to as the notification timing.

[0019] The message selection unit 26 selects a message to be used when notifying the vehicle 40 that an abnormality has occurred. This message is displayed on the display 42 or a mobile terminal (for example, a smartphone) carried by the user.

[0020] The vehicle 40 includes a communication I / F 41, a display 42, and an ECU 43 (Electronic Control Unit). The function of the communication I / F 41 is the same as that of the communication I / F 21, and therefore a description thereof will be omitted. The display 42 displays a message transmitted from the vehicle abnormality notification device 20. The ECU 43, like the abnormality determination unit 24, determines whether or not an abnormality has occurred in the vehicle 40. The ECU 43 and the abnormality determination unit 24 share the responsibility of abnormality determination according to the type of abnormality or the urgency of the abnormality. It is not essential that the ECU 43 has an abnormality determination function. The vehicle 40 may be a vehicle with or without an automatic driving function. The vehicle 40 may also be a vehicle capable of switching between automatic driving and manual driving.

[0021] Next, with reference to FIG. 2, an example of the "behavior history from when a notification regarding a predetermined behavior with respect to the vehicle is given to when the user actually performs the behavior" stored in the database 28 will be described.

[0022] The user of vehicle X is X1. The user of vehicle Y is Y1. The "content" shown in FIG. 2 is the content of a message previously notified to vehicle X and vehicle Y by vehicle abnormality notification device 20. The specific content of the message is "An abnormality has occurred in the starter. Please check it." Such a message is shown on display 42.

[0023] As shown in Figure 2, the date and time when the first notification was made to vehicle X is 14:01:30 on January 1, 2019. Such notifications are repeated at a predetermined cycle until the abnormality is resolved. The "latest notification date and time" in Figure 2 indicates the date and time when the last notification was made. In the case of user X1, the "first notification date and time" and the "latest notification date and time" are the same, so the number of notifications is one. User X1 had the repair done at 18:21:30 on January 3, 2019. In other words, user X1 had the repair done two days after receiving the first notification. The distance traveled by vehicle X after receiving the first notification is 20 km.

[0024] As shown in Figure 2, the date and time when the first notification was made to vehicle Y is 14:02:30 on January 1, 2019. The latest notification date and time is 16:02:30 on January 21, 2019. Although omitted in Figure 2, one more notification was made between the first notification and the latest notification, so the number of notifications is three. User Y1 had the vehicle repaired at 10:12:30 on January 22, 2019. In other words, user Y1 had the vehicle repaired 21 days after receiving the first notification. The distance traveled by vehicle Y after receiving the first notification is 195 km.

[0025] As can be seen from Figure 2, users can be classified into two types: those who want repairs done early (user X1) and those who want to delay repairs as long as possible (user Y1). In other words, assuming that the user pays for the repair costs of the starter malfunction shown in Figure 2, and assuming that they do not repair something that is still fully usable, users can be classified into two types: those who want to repair it early if there is a possibility of a major breakdown to feel secure (user X1) and those who want to use up parts until they are on the verge of breaking down (user Y1). Of course, the classification is not limited to these two types, but the following explanation will be given assuming two types.

[0026] Here, it is assumed that the distance traveled from the first notification until the starter actually breaks down is 200 km. In this case, since the user X1 repairs the starter when the user X1 has driven 20 km after the first notification, the utilization rate of the starter is low. As a result, from a long-term perspective, the burden on the user X1 (repair cost burden, replacement cost burden, etc.) will increase. Therefore, in order to increase the utilization rate of the starter and reduce the burden on the user X1, it is possible to delay the first notification to the user X1. When the abnormality determination unit 24 detects an abnormality, it can determine the remaining drivable distance until the vehicle needs to be repaired, which corresponds to the detected abnormality. The above 200 km corresponds to the remaining drivable distance. The remaining drivable distance corresponding to the detected abnormality is set in advance through experiments and simulations.

[0027] On the other hand, since user Y1 had the starter repaired 195 km after the first notification, the usage rate of the starter is high. However, since there is a risk of breakdown, it is possible to mitigate the risk of breakdown by notifying user Y1 earlier or by changing the notification message.

[0028] Therefore, the vehicle abnormality notification device 20 according to this embodiment changes the notification timing or the notification message according to the type of user. A specific example will be described with reference to Fig. 3. Note that the "type of user" can be classified by referring to the behavior history.

[0029] As shown in Fig. 3, for user X1 who repairs early, the first notification is sent when the remaining driving distance before the breakdown is 100 km. In the example shown in Fig. 2, the first notification was sent when the remaining driving distance before the breakdown was 200 km, so the notification timing is delayed compared to Fig. 2. If user X1 subsequently does not repair the vehicle and the remaining driving distance before the breakdown is 50 km, a second notification is sent. Of course, if user X1 repairs the vehicle before the remaining driving distance before the breakdown is 50 km, the second notification is not sent.

[0030] For user Y1 who wants to use up the parts until they break down, the first notification is specific and with a margin of error. For example, as shown in Figure 3, the notification is "The starter will break down in about 200 km." This message is more specific than the message "An abnormality has occurred in the starter. Please check it" described in Figure 2, so it is possible to encourage user Y1 to repair it early. If user Y1 does not repair it and the remaining driving distance before the breakdown is 100 km, a second notification is sent. Of course, if user Y1 repairs it before the remaining driving distance before the breakdown is 100 km, the second notification is not sent. The timing of the first notification is, for example, the same as the timing when the abnormality is detected. Normally, it is thought that there is a slight delay between the detection of the abnormality and the notification, but by sending the notifications at the same time, an earlier notification can be achieved.

[0031] As shown in Fig. 3, by changing the notification timing or the notification message depending on the type of user, it is possible to increase the utilization rate of parts, reduce the burden on users, and mitigate the risk of breakdowns.

[0032] Although the user types are classified according to the distance traveled from the first notification until repair, the classification method is not limited to this. The user types may also be classified according to the time between the first notification and repair. The shorter the time until repair, the more likely the user is to want to repair the vehicle early. On the other hand, the longer the time until repair, the more likely the user is to want to use up parts until the vehicle breaks down. As an example of the length of time until repair, as shown in FIG. 2, if the time between the first notification and repair is two days, it is considered to be short, and if it is 21 days, it is considered to be long. However, this time can be changed as appropriate depending on the type of abnormality.

[0033] Next, an example of the operation of the vehicle abnormality notification device 20 according to the first embodiment will be described with reference to the flowchart of FIG.

[0034] In step S101, the controller 22 refers to the database 28 and collects an action history from when a notification regarding a predetermined action on the vehicle is given until the user actually takes the action. The process proceeds to step S103, where the controller 22 classifies users based on the collected action history and creates teacher data by linking it with data such as notification messages. The process proceeds to step S105, where the controller 22 creates a learning model that uses gradient boosting to classify vehicles and users into predetermined patterns. This model creation process is for the purpose of improving the classification accuracy by machine learning, but is not necessarily required.

[0035] The process proceeds to step S107, where the abnormality determination unit 24 determines whether or not an abnormality has occurred based on the data received from the vehicle 40. If the detected abnormality is of high urgency (YES in step S109), the process proceeds to step S121, where the transmission control unit 23 issues a notification. An abnormality of high urgency refers to one that immediately affects driving safety. For example, the steering wheel is stuck, the brake pedal is stuck, etc. The notification message when an abnormality of high urgency is detected is, for example, "Perform an emergency stop."

[0036] If the detected abnormality is of low urgency (NO in step S109), the process proceeds to step S111, where the notification determination unit 25 refers to the database 28. An example of an abnormality of low urgency is the abnormality of the starter described in Figs. 2-3. In this embodiment, the notification timing is changed for an abnormality of low urgency, or the notification message is changed. If, in the past action history, the user of the vehicle in which the abnormality was detected this time repaired the vehicle before traveling 50 km from the first notification (YES in step S113), the process proceeds to step S117. In the past action history, the user who repaired the vehicle before traveling 50 km from the first notification is the user X1 described in Fig. 2. The user X1 repaired the vehicle when traveling 20 km from the first notification. Since the user X1 is a type that repairs the vehicle early, the notification timing is delayed (step S117). That is, in this flowchart, the user who repairs the vehicle before traveling 50 km from the first notification is classified as a type that repairs the vehicle early, and the user who does not repair the vehicle before traveling 50 km from the first notification is classified as a type that wants to use up parts until the vehicle is about to break down.

[0037] If the user of the vehicle in which the abnormality was detected this time has not repaired the vehicle within 50 km of driving from the first notification in the past action history (NO in step S113), the process proceeds to step S115. The user who has not repaired the vehicle within 50 km of driving from the first notification is user Y1 described in FIG. 2. User Y1 is the type of person who wants to use up parts until they are about to break down, so the notification determination unit 25 determines to notify early. For example, the timing of the first notification is the same as the timing when the abnormality is detected.

[0038] In step S119, the message selection unit 26 selects a notification message depending on the notification timing. If the notification timing is delayed, the notification message will be "The starter will break down soon," as shown in Fig. 3. If the notification is made earlier, the notification message will be "The starter will break down in approximately 200 km," as shown in Fig. 3.

[0039] In step S121, the transmission control unit 23 transmits the message selected in step S119 to the vehicle at the timing determined in step S115 or step S117. The message is then displayed on the display 42.

[0040] (Action and effect) As described above, the vehicle abnormality notification device 20 according to the first embodiment provides the following advantageous effects.

[0041] The vehicle abnormality notification device 20 includes a storage device 27 that stores an action history from when a first notification regarding a predetermined action on the vehicle is made until the user takes the action, and a controller 22. The controller 22 detects an abnormality in the vehicle, refers to the action history stored in the storage device 27, and determines the timing of sending a second notification, different from the first notification, regarding the abnormality in the vehicle to the user according to the time or the travel distance from the first notification to the action. The controller 22 issues the second notification to the user at the determined timing. The first notification is a notification in the past. It is possible to classify the user type as a type that wants to repair early or a type that wants to delay repair as much as possible from the action history. The timing of notification is delayed for users who want to repair early. This makes it possible to increase the utilization rate of parts and reduce the burden on the user. On the other hand, it is possible to notify early for users who want to delay repair as much as possible. This makes it possible to mitigate the risk of failure.

[0042] Furthermore, the controller 22 delays the timing of the second notification for a user who takes a shorter time or driving distance from the first notification to take action. For user X1 who wants to have the vehicle repaired early, as shown in Fig. 3, the first notification is sent when the driving distance until the starter actually breaks down is 100 km, rather than when the driving distance until the starter actually breaks down is 200 km. This makes it possible to increase the utilization rate of parts and reduce the burden on the user.

[0043] Furthermore, when an abnormality is detected, the controller 22 determines the remaining distance that the vehicle can travel before repairs are required, determines the timing of sending the second notification according to the remaining distance and the time or distance traveled from the first notification until the action is taken, and displays the remaining distance when sending the second notification to the user. This makes it possible to increase the utilization rate of parts and reduce the burden on the user.

[0044] The predetermined behavior is defined as requesting, reserving, or carrying out repairs on a vehicle at a predetermined location, and the behavior history includes a repair history. By referring to such behavior history, the controller 22 can accurately classify the user into which type the user is.

[0045] Second embodiment Next, a second embodiment of the present invention will be described with reference to Figs. 5 to 7. The second embodiment differs from the first embodiment in that the controller 22 further includes a user identification unit 29 as shown in Fig. 5. Configurations that overlap with the first embodiment will be referred to by reference numerals and their description will be omitted. The following description will focus on the differences.

[0046] The user identification unit 29 identifies the user sitting in the driver's seat of the vehicle. The database 28 stores users and their driving characteristics in association with each other. The driving characteristics include the timing of depressing the accelerator pedal, the timing of depressing the brake pedal, and the manner of turning the steering wheel. The user identification unit 29 can identify the user sitting in the driver's seat of the vehicle by referring to the driving characteristics stored in the database 28. The method of identifying the user is not limited to the driving characteristics, and the user may be identified by a personal authentication technology in cooperation with a mobile terminal (e.g., a smartphone) carried by the user.

[0047] In addition, the database 28 stores the remaining amount of fuel when the user refuels (hereinafter, may be referred to as the remaining amount at the time of refueling) in association with the user who actually refueled. By using such a refueling history, it is possible to notify an abnormality at an appropriate time according to the user type, even when it is the first time that an abnormality is notified.

[0048] Next, an example of a method for classifying users using refueling history will be described with reference to FIG. 6. As shown in FIG. 6, the average remaining amount of fuel at the time of refueling for user X1 is 8.4L, the maximum is 15.5L, the minimum is 1.2L, and the standard deviation is 3.2L. The average remaining amount of fuel for user X2 is 6.7L, the maximum is 14.1L, the minimum is 3.0L, and the standard deviation is 2.5L. The average remaining amount of fuel for user Y1 is 1.1L, the maximum is 3.1L, the minimum is 0.1L, and the standard deviation is 0.5L. By using such refueling history, users X1 and X2 are classified as a type that refuels early, and user Y1 is classified as a type that does not refuel until it is almost depleted. In light of the above-mentioned types regarding repairs, users X1 and X2 are classified as a type that wants to repair early, and user Y1 is classified as a type that wants to use up parts until it is almost broken. Therefore, even if behavioral history (repair history) is not stored in database 28, the same effect can be obtained as by referring to the behavioral history (repair history) by changing the notification timing or notification message using the refueling history.

[0049] In the example shown in FIG. 6, the users X1 and X2 are the same type, but let us consider a case where the user X2 is the type who does not refuel until the fuel is almost depleted, like the user Y1. In this case, the users X1 and X2 are different types. The users X1 and X2 use the vehicle X (for example, if it is a family, multiple people may use the same vehicle). In this case, the notification timing differs depending on whether the user driving the vehicle X is X1 or X2. If the user driving the vehicle X is X1, the notification timing is delayed, and if the user is X2, the notification timing is early. In this case, the user identification unit 29 identifies the user driving the vehicle X by the above-mentioned method. This enables the vehicle abnormality notification device 20 to notify according to the type of the user driving the vehicle X. When the user is in the vehicle and driving, the vehicle abnormality notification device 20 may notify the user via the display 42, and when the user is not in the vehicle, the vehicle abnormality notification device 20 may notify the user to a mobile terminal carried by the user. When the user is not in the vehicle, the vehicle abnormality notification device 20 may identify the user who last drove the vehicle and notify the mobile terminal of the identified user.

[0050] In addition, when both the behavior history and the refueling history from when the user is notified of a predetermined behavior with respect to the vehicle until the user actually performs the behavior are stored in the database 28, the notification determination unit 25 may change the notification timing or the notification message using both data. By using both data, the user type can be classified with high accuracy.

[0051] Next, an operation example of the vehicle abnormality notification device 20 according to the second embodiment will be described with reference to the flowchart of Fig. 7. However, since the processes of steps S203 to 211 and 215 to 221 are similar to the processes of steps S103 to 111 and 115 to 121 shown in Fig. 4, the description thereof will be omitted as appropriate.

[0052] In step S201, the controller 22 refers to the database 28 to collect the refueling history. If the user of the vehicle in which the abnormality was detected this time is the type who refuels early (YES in step S213), the process proceeds to step S217. On the other hand, if the user of the vehicle in which the abnormality was detected this time is the type who does not refuel until the fuel is almost depleted (NO in step S213), the process proceeds to step S215. In step S217, the notification determination unit 25 delays the notification timing. On the other hand, in step S215, the notification determination unit 25 decides to notify early.

[0053] (Action and effect) As described above, the vehicle abnormality notification device 20 according to the second embodiment provides the following advantageous effects.

[0054] The controller 22 identifies the user who owns the vehicle, and issues a second notification to the identified user. When identifying the user, it is not essential that the user is in the vehicle and driving. The user may or may not be in the vehicle. When a vehicle is shared by multiple people, the user who last drove the vehicle corresponds to the "user who owns the vehicle." When a vehicle is owned by one person, the driver is equal to the owner. Identifying the user makes it possible to notify the user at a timing appropriate for that user.

[0055] The controller 22 refers to the action history of the identified user and determines the timing of transmitting the second notification, thereby making it possible to send a notification at a timing suitable for the identified user.

[0056] The behavioral history includes a refueling history that indicates the amount of fuel remaining when the user refuels. By using the refueling history, it is possible to accurately classify the user into which type they are even if the repair history has not been accumulated.

[0057] The controller 22 identifies the user by referring to the driving characteristic history that indicates the driving characteristics of the user and is stored in the storage device 27. This makes it possible to identify the user with high accuracy.

[0058] Each of the functions described in the above embodiments may be implemented by one or more processing circuits. A processing circuit includes a programmed processing device, such as a processor including electrical circuitry. A processing circuit also includes devices such as application specific integrated circuits (ASICs) or circuit components arranged to perform the described functions.

[0059] As described above, the embodiment of the present invention has been described, but the description and drawings forming a part of this disclosure should not be understood as limiting this invention. From this disclosure, various alternative embodiments, examples and operating techniques will become apparent to those skilled in the art. [Explanation of symbols]

[0060] 10. Vehicle Abnormality Notification System 20 Vehicle abnormality notification device 22 Controller 23 Transmission control section 24 Abnormality determination section 25 Notification Determination Department 26 Message Selection Section 27 Storage device 28 Database 29 User Identification Part 30 Communication Network 40 vehicles

Claims

1. a storage device that stores an action history from when a first notification regarding a predetermined action on a vehicle is issued to when a user performs the action; and a controller. The controller: Detecting an abnormality in the vehicle; referring to the action history stored in the storage device, and determining a timing for transmitting a second notification, different from the first notification, to the user regarding the abnormality of the vehicle, according to a time or a travel distance from the first notification to the performance of the action; The second notification is given to the user at the determined timing. A vehicle abnormality notification device characterized by the above.

2. The controller: The timing of issuing the second notification is delayed for a user who has a shorter time or a shorter running distance from the first notification to the execution of the action.

2. The vehicle abnormality notification device according to claim 1,

3. The controller: If the anomaly is detected, determining a remaining mileage of the vehicle before repair is required; determining a timing for transmitting the second notification in accordance with the remaining travelable distance and the time or traveled distance from the first notification to the time the action is taken; The remaining driving distance is displayed when the second notification is given to the user.

3. The vehicle abnormality notification device according to claim 1 or 2.

4. The predetermined action is defined as requesting, reserving, or carrying out repairs on the vehicle at a predetermined location; The behavioral history includes a repair history.

4. The vehicle abnormality notification device according to claim 1, wherein the vehicle abnormality notification device is a vehicle abnormality notification device.

5. The behavior history includes a refueling history indicating the amount of fuel remaining when the user refuels.

5. A vehicle abnormality notification device according to claim 1, wherein the vehicle abnormality notification device is a vehicle abnormality notification device.

6. The controller: Identifying a user who owns the vehicle; The second notification is sent to the specified user.

6. A vehicle abnormality notification device according to claim 1,

7. The controller: Refer to the behavior history of the identified user and determine the timing for transmitting the second notification.

7. The vehicle abnormality notification device according to claim 6.

8. The controller: Identifying the user by referring to a driving characteristic history indicating the driving characteristics of the user stored in the storage device 8. The vehicle abnormality notification device according to claim 1,

9. A vehicle abnormality notification method for a vehicle abnormality notification device including a storage device that stores an action history from when a first notification regarding a predetermined action on a vehicle is made to when a user performs the action, and a controller. The controller determines an abnormality in the vehicle, the controller refers to the action history stored in the storage device, and determines a timing to transmit a second notification, which is different from the first notification, to the user regarding the abnormality of the vehicle, according to a time or a traveling distance from the first notification to the performance of the action; The controller issues the second notification to the user at the determined timing. A vehicle abnormality notification method comprising:

Citation Information

Patent Citations

  • Car-mounted collision-prevention warning device

    JP1995072246A

  • Information noticing device

    JP1998260050A

  • Remote damage prediction system

    JP2004268633A

  • Occupant specifying device

    JP2008222167A

  • Driver identifying device

    JP2012069037A