Driving diagnostic system

Abstract

To provide a drive diagnosis system safely usable by a person to be watched.SOLUTION: A drive diagnosis system 100 comprises a server 30, a first terminal 40 of a person to be watched and a second terminal 140 of a watching person, and executes drive diagnosis for the person to be watched. The server 30 comprises a CPU 31 for executing information processing. The CPU 31 acquires vehicle information, executes the drive diagnosis for the person to be watched about plural diagnosis items based on the acquired vehicle information, acquires a disclosable range of the respective diagnostic items for the person to be watched from the first terminal 40 of the person to be watched, extracts diagnostic information included in the disclosable range as watching information, and transmits the extracted watching information to the second terminal 140 of the watching watched.SELECTED DRAWING: Figure 13

Description

Technical Field

[0001] The present invention relates to a driving diagnosis system for performing driving diagnosis of a person under guardianship.

Background Art

[0002] In recent years, driving diagnosis of drivers has been carried out. For example, in Patent Document 1, based on driving diagnosis, a reference driving skill and a newly diagnosed driving skill are compared, driving items in which the driving skill has changed are specified, and the driving items in which the driving skill has changed and the driving skills corresponding to the driving items are presented to the driver or the guardian.

[0003] Also, Patent Document 2 discloses a method of performing driving diagnosis of a driver based on vehicle information and granting a privilege corresponding to the driving diagnosis result to the beneficiary.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] By the way, when the person under guardianship has a high awareness of privacy, the person under guardianship may feel uneasy about using an application that discloses all diagnosis items and driving skills to the guardian as described in Patent Document 1.

[0006] Therefore, an object of the present disclosure is to provide a driving diagnosis system that can be used with confidence by the person under guardianship.

Means for Solving the Problems

[0007] The driving diagnostic system of this disclosure includes a driving diagnostic device, a first terminal of a person being monitored, and a second terminal of a monitor, and is a driving diagnostic system that performs a driving diagnostic of the person being monitored, wherein the driving diagnostic device includes a processor that performs information processing, the processor acquires vehicle information, performs a driving diagnostic of the person being monitored for a plurality of diagnostic items based on the acquired vehicle information, acquires the scope of disclosure of each diagnostic item to the monitor from the first terminal of the person being monitored, extracts the diagnostic information included in the scope of disclosure as monitoring information, and transmits the extracted monitoring information to the second terminal of the monitor. The first terminal of the person being monitored displays multiple diagnostic items or profiles associated with the content of each diagnostic item, transmits multiple diagnostic items or the content of each diagnostic item associated with the profile selected by the person being monitored to the driving diagnostic device as the scope of disclosure to the monitor, the driving diagnostic device determines the safe driving level of the person being monitored, transmits the safe driving level to the first terminal of the person being monitored, and the first terminal of the person being monitored restricts the profiles that the person being monitored can select based on the received safe driving level. It is characterized by the following.

[0008] In this way, the person being monitored can set the scope of information they are allowed to disclose to their supervisor, so even those with a strong sense of privacy can use the driving diagnostic system with peace of mind. Furthermore, this allows the monitored individual to easily transmit the scope of information they wish to disclose to the driving diagnostic device. In addition, this enables the selection of an appropriate profile according to the monitored individual's safe driving level. For example, if the safe driving level is high, a profile with fewer disclosed items and a higher level of privacy can be selected, while if the safe driving level is low, a profile with a high level of privacy cannot be selected.

[0011] In the driving diagnostic system of this disclosure, the scope of disclosure may be set to multiple levels corresponding to multiple levels of privacy.

[0012] This allows the person being monitored to easily transmit information to the driving diagnostic device, depending on their privacy level.

[0013] In the driving diagnostic system of this disclosure, multiple profiles may be set to correspond to vehicle usage scenarios.

[0014] This allows the person being monitored to easily transmit the scope of information that can be disclosed to the driving diagnostic device according to the vehicle's usage scenario. [Effects of the Invention]

[0017] This disclosure provides a driving diagnostic system that can be used with peace of mind by those being monitored. [Brief explanation of the drawing]

[0018] [Figure 1]It is a system diagram showing the overall configuration of the operation diagnosis system of the embodiment. [Figure 2] It is a system diagram showing the hardware configuration of the vehicle shown in FIG. 1. [Figure 3] It is a system diagram showing the hardware configuration of the server shown in FIG. 1. [Figure 4] It is a diagram showing the structure of the diagnosis criterion database of the server shown in FIG. 3. [Figure 5] It is a diagram showing the structure of the diagnosis history database shown in FIG. 3. [Figure 6] It is a diagram showing the structure of the user information database shown in FIG. 3. [Figure 7] It is a diagram showing the structure of the monthly comprehensive evaluation disclosure possible range database shown in FIG. 3. [Figure 8] It is a system diagram showing the hardware configuration of the first terminal shown in FIG. 1. [Figure 9] It is a diagram showing the top screen stored in the GUI database shown in FIG. 8. [Figure 10] It is a diagram showing the disclosure possible range initial setting screen stored in the GUI database shown in FIG. 8. [Figure 11] It is a diagram showing the disclosure possible range setting screen of the monthly comprehensive evaluation stored in the GUI database shown in FIG. 8. [Figure 12] It is a diagram showing the setting screen after the second time of the disclosure possible range stored in the GUI database shown in FIG. 8. [Figure 13] It is a sequence diagram showing the overall operation of the operation diagnosis system of the embodiment. [Figure 14] It is a flowchart showing the operation of the first terminal shown in FIG. 1. [Figure 15] It is a continuation of the flowchart shown in FIG. 14. [Figure 16] It is a flowchart showing the operation of the server shown in FIG. 1. [[ID= forty-eight ]]

Embodiments of the Invention

[0019] The driving diagnostic system 100 of the embodiment will be described below with reference to the drawings. As shown in Figure 1, the driving diagnostic system 100 includes a vehicle 10, a server 30 which is a driving diagnostic device, a first terminal 40 which is a mobile terminal of the person being monitored, and a second terminal 140 which is a mobile terminal of the monitor. An in-vehicle terminal 20 is mounted on the vehicle 10. The in-vehicle terminal 20, the server 30, the first terminal 40, and the second terminal 140 are interconnected via a network 90. ​​In Figure 1, one vehicle 10, one in-vehicle terminal 20, one first terminal 40, and one second terminal 140 are connected to one server 30, but the number of vehicles 10, in-vehicle terminals 20, first terminals 40, and second terminals 140 is not limited to this, and there may be two or more of each.

[0020] As shown in Figure 2, the vehicle 10 includes multiple ECUs (Electronic Control Units) 11, multiple in-vehicle devices 13, and an in-vehicle terminal 20.

[0021] ECU11 includes ADAS-ECU11A (Advanced Driver Assistance System-ECU), steering ECU11B, brake ECU11C, engine ECU11D, and auxiliary ECU11E. ADAS-ECU11A, steering ECU11B, brake ECU11C, engine ECU11D, and auxiliary ECU11E are interconnected via bus 12 and exchange information with each other. Vehicle 10 may also include other ECUs.

[0022] The ADAS-ECU11A centrally controls the advanced driver assistance system. The ADAS-ECU11A is connected to the vehicle speed sensor 13A, the yaw rate sensor 13B, and the external sensor 13C, which constitute the in-vehicle equipment 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 area around the vehicle 10, a millimeter-wave radar that transmits probe waves and receives reflected waves, and a lidar that scans the area in front of the vehicle 10.

[0023] The steering ECU 11B controls the power steering. The steering ECU 11B is connected to the steering angle sensor 13D and the steering actuator 13E, which constitute the in-vehicle equipment 13. The steering angle sensor 13D is a sensor that detects the steering angle of the steering wheel. The steering actuator 13E steers the steering wheels of the vehicle 10 in response to the driver's input.

[0024] The brake ECU 11C controls the brake system of the vehicle 10. The brake actuator 13F, which constitutes the onboard equipment 13, is connected to the brake ECU 11C. The brake actuator 13F drives the brakes of the vehicle 10 in response to the driver's operation.

[0025] The engine ECU 11D controls the engine of the vehicle 10. The engine ECU 11D is connected to the throttle actuator 13G and sensors 13H, which constitute the on-board equipment 13. The throttle actuator 13G drives the engine throttle in response to the driver's operation. The sensors 13H include, for example, an oil temperature sensor for measuring the oil temperature of the engine oil, an oil pressure sensor for measuring the oil pressure of the engine oil, and a rotation sensor for detecting the engine speed.

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

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

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

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

[0030] As shown in Figure 3, the server 30 is a computer that includes a CPU 31, which is a processor for 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 that is connected to the network 90 and communicates with the in-vehicle terminal 20, the first terminal 40, and the second terminal 140.

[0031] Memory 32 stores a processing program 35, processing program data 36, ​​a diagnostic criteria database 37, a diagnostic history database 38, a user information database 39, and a monthly comprehensive evaluation disclosure scope database 39A. Note that memory 32 may also store other programs and databases.

[0032] The processing program 35 includes a driving diagnostic program that performs a driving diagnostic on the driver of the vehicle 10 and a monitoring information extraction program that extracts diagnostic information included in the scope of disclosure as monitoring information. The processing program 35 is executed by the CPU 31. The processing program data 36 temporarily stores data when the CPU 31 executes the processing program 35, and also stores setting values ​​and other information 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.

[0033] As shown in Figure 4, the diagnostic criteria database 37 is a database that stores the evaluation index and reference score values ​​for each diagnostic item when the CPU 31 performs a driving diagnosis. In the diagnostic criteria database 37, when the diagnostic item is accelerator operation, it is stipulated that maximum acceleration is used as the evaluation index. Furthermore, the diagnostic criteria database 37 stipulates that a maximum acceleration of A or higher is set as the reference value for an accelerator operation score of 1, a maximum acceleration of less than B is set as the reference value for an accelerator operation score of 3, and a maximum acceleration between A and B is set as the reference value for an accelerator operation score of 2. Note that a higher score indicates a higher level of safe driving.

[0034] Similarly, the diagnostic criteria database 37 stipulates that when the diagnostic item is brake operation, maximum deceleration is used as the evaluation index, with a maximum deceleration of C or higher being the standard value for a brake operation score of 1, a maximum deceleration of less than D being the standard value for a brake operation score of 3, and a maximum deceleration between C and D being the standard value for a brake operation score of 2. Furthermore, the diagnostic criteria database 37 stipulates that when the diagnostic item is steering operation, maximum lateral acceleration is used as the evaluation index, with a maximum lateral acceleration of E or higher being the standard value for a steering operation score of 1, a maximum lateral acceleration of less than F being the standard value for a steering operation score of 3, and a maximum lateral acceleration between E and F being the standard value for a steering operation score of 2. Furthermore, the diagnostic criteria database 37 stipulates that when the diagnostic item is following distance, the length of the following distance is used as the basis for the following distance score, and when the diagnostic item is perception / judgment, proximity warnings are used as the evaluation index, the operation of emergency braking is used as the basis for a perception / judgment score of 1, the absence of a warning is used as the basis for a score of 3, and the presence of a warning is used as the basis for a score of 2.

[0035] As shown in Figure 5, the diagnostic history database 38 is a database that stores the following items for each registered person being monitored, which are stored in the user information database 39: driving scene extraction time, driving scene, accelerator operation score, brake operation score, steering operation score, following distance score, perception / judgment score, number of hazard avoidance operations, safe driving level, driving distance, and driving time. Here, the driving scene includes starting, accelerating, decelerating, stopping, turning, changing lanes, merging, parking, etc. Note that the figures for acceleration, stopping, merging, and parking are omitted.

[0036] As shown in Figure 6, the user information database 39 is a database that stores the name of the person being monitored, the age, gender, years of driving experience, the name of the monitor, the result of the safe driving level assessment, and the disclosure scope setting status in association with each other. The person being monitored is often, for example, an elderly person such as person AAA to DDD, and monitors aaa to ddd are often their children, but this is not limited to this. For example, the person being monitored may be a newly licensed child such as EEE, and the monitor may be their parent eee.

[0037] Here, the safe driving level assessment result stores, for example, the safe driving level for the most recent month. In cases where the number of years of driving experience is short and a monthly safe driving level assessment has not been made, such as in the case of the monitored person EEE, the letters "NA" are stored. The disclosure range setting status stores whether or not the monthly overall evaluation, mileage, driving time, and number of hazard avoidances set by the monitored person on the first terminal 40 can be disclosed to the monitor's second terminal 140.

[0038] As shown in Figure 7, the monthly overall evaluation disclosure scope database 39A stores whether or not the following can be disclosed to the caregiver's second terminal 140: the safe driving level, accelerator operation score, brake operation score, steering operation score, following distance score, and cognitive / judgment score during the monthly overall evaluation set by the person being monitored on the first terminal 40.

[0039] Here, the distance traveled, driving time, number of hazard avoidance attempts, safe driving level, accelerator operation score, brake operation score, steering operation score, following distance score, and perception / judgment score constitute the diagnostic information of the driving diagnosis results.

[0040] As shown in Figure 8, the first terminal 40, which is the mobile terminal of the person being monitored, is a smartphone that includes a CPU 41, which is a processor that performs 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. The operation of the first terminal 40 is realized by the CPU 41 executing an application 46.

[0041] Memory 42 stores an application 46 for performing operational diagnostics, application execution data 47, and a GUI database 48. The application execution data 47 temporarily stores data when the CPU 41 executes application 46, as well as setting values ​​and other information necessary for the execution of application 46.

[0042] The GUI database 48 stores image data for the top screen 51, the initial disclosure range setting screen 53, the monthly overall evaluation disclosure range setting screen 54, and the second and subsequent disclosure range setting screens 55, which are displayed on the touch panel 43 as shown in Figures 9 to 12.

[0043] As shown in Figure 9, the top screen 51 is the screen displayed when the driving diagnostic application 46 is executed. The top screen 51 displays the display date and time, fuel efficiency, number of hazard avoidance operations, distance traveled, driving time, and the monthly overall evaluation. The monthly overall evaluation displays scores for each item: safe driving level, accelerator operation, brake operation, steering operation, following distance, and perception / judgment. The score for each item is displayed in a graph. As mentioned earlier, distance traveled, driving time, number of hazard avoidance operations, safe driving level, accelerator operation score, brake operation score, steering operation score, following distance score, and perception / judgment score constitute the diagnostic information of the driving diagnostic results. The initial disclosure range setting screen 53, the monthly overall evaluation disclosure range setting screen 54, and the second and subsequent disclosure range setting screen 55 will be explained later along with the operation explanation.

[0044] The hardware configuration of the second terminal 140 for the monitor is the same as that of the first terminal 40, as explained with reference to Figure 8. However, since the second terminal 140 does not input the scope of disclosure, the GUI database 48 stores the image data of the top screen 51 shown in Figure 9, but does not store the initial disclosure scope setting screen 53, the monthly overall evaluation disclosure scope setting screen 54, or the second and subsequent disclosure scope setting screens 55.

[0045] Next, the operation of the operational diagnostic system 100 of the embodiment will be described with reference to Figures 13 to 16.

[0046] As shown in Figure 13, the driving diagnostic system 100 registers diagnostic information that the monitored person can disclose to the monitor from the first terminal 40 in the user information database 39 and the monthly overall evaluation disclosure range database 39A of the server 30. The server 30 receives vehicle information from the in-vehicle terminal 20 installed in the vehicle 10, performs driving diagnostic processing on the monitored person based on the received vehicle information, stores the diagnostic information in the diagnostic history database 38, and transmits it to the monitored person's first terminal 40. The server 30 also refers to the user information database 39 and the monthly overall evaluation disclosure range database 39A to extract diagnostic information included in the disclosure range as monitoring information, and transmits the extracted monitoring information to the monitor's second terminal 140.

[0047] The operation of the driving diagnostic system 100 will be described in detail below, with reference to the flowcharts in Figures 14 to 16.

[0048] First, the operation of setting the disclosure range of the first terminal 40 will be explained with reference to Figure 14. The CPU 41 of the first terminal 40 executes the driving diagnostic application 46 stored in the memory 42. As shown in step 101 of Figure 14, the CPU 41 decides whether to perform the initial setting of the disclosure range. If the CPU 41 determines YES in step 101 of Figure 1, it proceeds to step 102 of Figure 1, refers to the GUI database 48, and displays the disclosure range initial setting screen 53 shown in Figure 10 on the touch panel 43. As shown in Figure 10, the disclosure range initial setting screen 53 displays multiple profiles according to the usage scenario of the vehicle 10, such as "daily use," "long trip," and "night."

[0049] As shown in step 103 of Figure 14, when the person being monitored operates the touch panel 43 to select one of the multiple profiles by turning it "on", the CPU 41 displays the default privacy level and the default settings for sharing each item with the monitor at the bottom of the screen, as shown in step 104 of Figure 14. In the example shown in Figure 10, the default privacy level is 1, and the screen displays that sharing with the monitor is turned on for each item: monthly overall evaluation, mileage, mileage, and number of hazard avoidances. In other words, the default setting is the lowest privacy level, and all items are set to be disclosable to the monitor.

[0050] The person being monitored can change their privacy level by pressing the down arrow button next to the privacy level. When the privacy level is changed, the default settings for sharing each item with the monitor will be displayed according to the changed privacy level. For example, if the privacy level is changed to 5, a screen will be displayed as shown in Figure 12, where sharing of the monthly overall rating with the monitor is turned on, and sharing of other items with the monitor is turned off. The person being monitored can freely change the setting to turn sharing on or off for each displayed item with the monitor.

[0051] When the person being monitored finishes changing the scope of disclosure and presses the "Finish Settings" button, the information of the changed scope of disclosure displayed on the screen is sent to the server 30, as shown in step 106 of Figure 14. The server 30 stores the received information of the scope of disclosure in the user information database 39 shown in Figure 6. If the person being monitored presses the "Finish Settings" button without changing the scope of disclosure from the default setting, the CPU 41 determines "NO" in step 105 of Figure 14 and proceeds to step 107 of Figure 14, sending the default scope of disclosure to the server 30.

[0052] Furthermore, when the person being monitored presses "Setting the Disclosure Range of the Monthly Overall Evaluation" at the bottom of the screen shown in Figure 9, the CPU 41 refers to the GUI database 48 and displays the Monthly Overall Evaluation Disclosure Range Setting screen 54 on the touch panel 43, as shown in Figure 11. Similar to the Disclosure Range Initial Setup screen 53 described earlier, the default privacy level and the default settings for sharing with the monitor for each item—safe driving level, accelerator score, brake score, steering score, following distance score, and cognitive / judgment score—are displayed. The person being monitored can freely change the privacy level and turn on or off sharing with the monitor for each displayed item on the touch panel 43. Then, when they press the "Finish Settings" button, the information of the changed Monthly Overall Evaluation Disclosure Range displayed on the screen is sent to the server 30. The server 30 stores the received information of the Monthly Overall Evaluation Disclosure Range in the Monthly Overall Evaluation Disclosure Range Database 39A shown in Figure 7.

[0053] Furthermore, if the CPU 41 determines NO in step 101 of Figure 14, that is, if the person being monitored is setting the disclosure scope for the second time or later, it proceeds to step 121 of Figure 15 to determine whether it has received the safe driving level from the server 30. If the CPU 41 determines YES in step 121 of Figure 15, it proceeds to step 122 of Figure 15 to determine whether the safe driving level is 4 or higher. If the CPU 41 determines YES in both steps 121 and 122 of Figure 15, it proceeds to step 123 of Figure 15 to display the second and subsequent disclosure scope setting screen 55 as shown in Figure 12. On the second and subsequent disclosure scope setting screen 55, the profile "Daily Use for Safe Drivers" is added to the profile settings area. The default privacy level is set to 5, sharing of the monthly overall evaluation with the monitor is turned on, and the default settings are displayed with sharing of other items with the monitor turned off.

[0054] On the other hand, if CPU 41 determines NO in either step 121 or step 122 of Figure 15, it proceeds to step 124 of Figure 15, restricting the display of the "Daily Use for Safe Drivers" profile shown in Figure 12, and instead displays the three profiles "Daily Use," "Long-Distance Trips," and "Nighttime."

[0055] After CPU 41 displays the profile in step 123 or step 124 of Figure 15, it proceeds to step 103 of Figure 14 and sends the information on the scope of disclosure, which has been modified by the person being monitored, to server 30. Server 30 stores this information in user information database 39.

[0056] Next, the operation of the server 30 will be explained with reference to Figure 16. When the driving diagnostic system 100 is activated, the in-vehicle terminal 20 installed in the vehicle 10 acquires vehicle information from multiple in-vehicle devices 13 via multiple ECUs 11 and transmits it to the server 30. The CPU 31 receives vehicle information from the in-vehicle terminal 20 in step 201 of Figure 16. The vehicle information includes the vehicle's speed, yaw rate, information on the vehicle's surrounding environment, steering angle information, brake operation information, engine operation information, etc. The vehicle information also includes the vehicle's fuel consumption information, mileage, and driving time information.

[0057] The CPU 31 executes the diagnostic program within the processing program 35. In step 202 of Figure 16, the CPU 31 extracts the driving scenes of the vehicle 10 based on the vehicle information received from the in-vehicle terminal 20. The driving scenes include, for example, starting, accelerating, decelerating, stopping, turning, changing lanes, merging, parking, etc. The driving scenes define the period for which the driving diagnosis will be performed.

[0058] In step 203 of Figure 16, the CPU 31 refers to the diagnostic criteria database 37 shown in Figure 4 and performs a driving diagnosis of the monitored person, who is the driver during the extracted driving scene period. As shown in Figure 4, the CPU 31 extracts maximum acceleration, maximum deceleration, maximum lateral acceleration, following distance, and presence or absence of proximity warning from the vehicle information during the driving scene period, and calculates scores for accelerator operation, brake operation, steering operation, following distance, and perception / judgment as diagnostic results by referring to the diagnostic criteria database 37. In addition, if, for example, sudden braking or sudden steering operation is extracted, the CPU 31 counts the number of times a hazard avoidance operation was performed and includes it in the diagnostic results. Then, based on the calculated scores and the number of hazard avoidance operations, the CPU 31 calculates the safe driving level of the monitored person in the driving scene. Then, in step 204 of Figure 16, the CPU 31 stores the score of each driving operation extracted in step 204 of Figure 16, the number of hazard avoidance operations, the calculated safe driving level, the distance traveled up to the time the driving scene was extracted, and the driving time as diagnostic information in the diagnostic history database 38.

[0059] In step 205 of Figure 16, the CPU 31 determines whether it is time to send diagnostic information to the person being monitored. The sending timing is, for example, a predetermined date and time at the end of the month when sending a monthly overall evaluation to the person being monitored, as shown in Figure 9. If the CPU 31 determines YES in step 205 of Figure 16, it proceeds to step 206 of Figure 16 and sends the diagnostic information to the first terminal 40 of the person being monitored. The first terminal 40 receives the diagnostic information for all items stored in the diagnostic history database 38 in Figure 16, as well as the fuel efficiency information of the vehicle 10.

[0060] When the first terminal 40 receives diagnostic information and fuel efficiency information from the server 30, it stores each of the transmitted pieces of information in its memory 42. Then, when the person being monitored starts the driving diagnostic application 46 on the first terminal 40, the CPU 41 displays the top screen 51 shown in Figure 9 on the touch panel 43, reads the information from the memory 42, and displays it on the screen.

[0061] Next, the CPU 31 executes the monitoring information extraction program included in the processing program 35. In step 207 of Figure 16, the CPU 31 determines whether it is time to send monitoring information to the caregiver. The transmission timing may be the same as the timing for sending diagnostic information, etc., to the person being monitored.

[0062] If the CPU 31 determines YES in step 207 of Figure 16, it proceeds to step 208 of Figure 16, where it refers to the user information database 39 shown in Figure 6 and the monthly overall evaluation disclosure range database 39A shown in Figure 7, and extracts diagnostic information for each item that can be disclosed to the monitor as monitoring information. For example, in the case of a monitored person AAA, the disclosure of mileage, mileage, and number of hazard avoidance operations is not possible, and the disclosure of the safe driving level in the monthly overall evaluation is not possible. Therefore, the CPU 31 extracts the access operation score, brake operation score, steering operation score, following distance score, and cognitive / judgment score from the monthly overall evaluation as monitoring information.

[0063] Then, the CPU 31 proceeds to step 209 in Figure 16 and transmits the extracted monitoring information to the monitor's second terminal 140.

[0064] The monitor's second terminal 140 stores the information received from the server 30 in its memory 42. When the monitor starts the driving diagnostic application 46 on the second terminal 140, the CPU 41 displays the top screen 51 shown in Figure 9 on the touch panel 43, reads the monitoring information received from the memory 42, and displays it on the screen. If the monitor is "aaa", the top screen 51 displays the date, fuel efficiency information, and the monthly overall rating excluding the safe driving level.

[0065] As explained above, the driving diagnostic system 100 allows the person being monitored to set diagnostic information that can be disclosed on the monitor's second terminal 140 using the first terminal 40, and the server 30 extracts items included in the scope of disclosure from the diagnostic information of the driving diagnostic results as monitoring information and displays them on the monitor's second terminal 140. Therefore, even people being monitored who are highly conscious of their privacy can use the driving diagnostic system 100 with peace of mind.

[0066] Furthermore, in the driving diagnostic system 100, the first terminal 40 of the person being monitored displays multiple diagnostic items or profiles associated with the content of each diagnostic item, and transmits the multiple diagnostic items or the content of each diagnostic item associated with the profile selected by the person being monitored to the server 30 as the scope of information that can be disclosed to the monitor. The server 30 then stores the information of the scope of information that can be disclosed transmitted from the first terminal 40 in the user information database 39 or the monthly overall evaluation disclosure scope database 39A. In addition, multiple profiles are set up to correspond to the usage scenarios of the vehicle 10. Furthermore, the scope of information that can be disclosed is set to correspond to multiple levels of privacy.

[0067] This allows the person being monitored to easily send the scope of information they wish to disclose to the server 30, and to easily set the scope of information they wish to disclose according to their privacy level. In addition, the person being monitored can easily set the scope of information they wish to disclose according to the usage scenario of the vehicle 10.

[0068] Furthermore, the first terminal 40 restricts the profiles that the monitored person can select based on the received safe driving level, allowing the monitored person to select an appropriate profile according to their safe driving level and set the scope of disclosure. In addition, as the safe driving level increases, a disclosure scope with a higher level of privacy is displayed by default, which motivates the monitored person to prioritize safe driving.

[0069] In the above explanation, it was assumed that the CPU 31 of the server 30 executes steps 201 to 203 in Figure 16, but this is not limited to this. For example, the diagnostic program in the processing program 35 and the diagnostic criteria database 37 may be stored in the memory 22 of the in-vehicle terminal 20, the CPU 21 may refer to the diagnostic criteria database 37 to perform a driving diagnosis, and send the diagnostic information of the diagnosis result to the server 30. Then the CPU 31 of the server 30 executes the processes in steps 204 to 209 in Figure 16. In this case, the in-vehicle terminal 20 and the server 30 constitute a driving diagnostic device.

[0070] Furthermore, the above explanation assumes that the second terminal 140 of the caregiver does not input the scope of disclosure and does not store the initial disclosure scope setting screen 53, the monthly overall evaluation disclosure scope setting screen 54, and the second and subsequent disclosure scope setting screen 55, but this is not limited to this. For example, the second terminal 140 may store the initial disclosure scope setting screen 53, the monthly overall evaluation disclosure scope setting screen 54, and the second and subsequent disclosure scope setting screen 55 in the GUI database 48 and enable input of the scope of disclosure. If the caregiver inputs the scope of disclosure, and the person being cared for approves the input, the input may be stored in the user information database 39 and the monthly overall evaluation disclosure scope database 39A of the server 30.

[0071] Furthermore, while the above explanation describes the CPU 31 performing operational diagnostics by referring to the diagnostic criteria database 37, it is not limited to this. For example, the CPU 31 may perform operational diagnostics using maps or functions. [Explanation of symbols]

[0072] 10 Vehicle, 11 ECU, 11A ADAS-ECU, 11B Steering ECU, 11C Brake ECU, 11D Engine ECU, 11E Auxiliary ECU, 12 Bus, 13 In-vehicle equipment, 13A Vehicle speed sensor, 13B Yaw rate sensor, 13C External sensors, 13D Steering angle sensor, 13E Steering actuator, 13F Brake actuator, 13G Throttle actuator, 13H Sensors, 20 In-vehicle terminal, 21, 31, 41 CPU, 22, 32, 42 Memory, 23, 33, 44 Wireless communication interface, 24 In-vehicle communication interface, 25, 34, 45 Internal bus, 26 Control program, 30 Server, 35 Processing program, 36 Data for processing program, 37 Diagnostic criteria database, 38 Diagnostic history database, 39 User information database, 39A Monthly comprehensive evaluation disclosure scope database, 40 Terminal 1, 43 Touch panel, 46 Application, 47 Application execution data, 48 GUI database, 51 Top screen, 53 Initial disclosure scope setting screen, 54 Monthly overall evaluation disclosure scope setting screen, 55 Subsequent disclosure scope setting screen, 90 Network, 100 Driving diagnostic system, 140 Terminal 2.

Claims

1. A driving diagnostic system comprising a driving diagnostic device, a first terminal for the person being monitored, and a second terminal for the monitor, which performs a driving diagnostic for the person being monitored, The aforementioned driving diagnostic device includes a processor that performs information processing, The aforementioned processor, Obtain vehicle information, Based on the acquired vehicle information, a driving diagnosis of the person being monitored is performed on multiple diagnostic items. The scope of disclosure of each diagnostic item to the caregiver is obtained from the first terminal of the person being monitored. The diagnostic information included in the aforementioned scope of disclosure is extracted as monitoring information. The extracted monitoring information is transmitted to the monitor's second terminal. The first terminal of the person being monitored displays multiple diagnostic items or multiple profiles associated with the content of each diagnostic item. The driver diagnostic device transmits to the monitor the contents of multiple diagnostic items or the contents of each diagnostic item associated with the profile selected by the person being monitored as the scope of disclosure to the monitor. The driving diagnostic device determines the safe driving level of the person being monitored and transmits the safe driving level to the first terminal of the person being monitored. The first terminal of the person being monitored restricts the profiles that the person being monitored can select based on the received safe driving level. A driving diagnostic system characterized by the following features.

2. A driving diagnostic system according to claim 1, The aforementioned scope of disclosure is set to correspond to multiple levels of privacy. A driving diagnostic system characterized by the following features.

3. A driving diagnostic system according to claim 1, The aforementioned profiles are set up in multiple ways to correspond to the vehicle's usage scenarios. A driving diagnostic system characterized by the following features.

Images