Driving diagnosis apparatus and driving diagnosis method

By identifying and analyzing the detection values ​​of the accelerator pedal and brake pedal, the problem of simultaneous pedaling by the driver is solved, and effective driving diagnosis and behavior improvement are achieved, supporting the development of third-party applications.

CN115140058BActive Publication Date: 2026-01-30TOYOTA JIDOSHA KK
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202210180583.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-03-31
Filing Date
2022-02-25
Publication Date
2026-01-30
Estimated Expiration
2042-02-25

AI Technical Summary

Technical Problem

Existing driver diagnostic equipment has room for improvement in diagnosing accelerator pedal and brake pedal operation, especially in effectively preventing drivers from pressing both pedals simultaneously.

Method used

The event recognition unit obtains the detection values ​​of the accelerator pedal and brake pedal from the vehicle, identifies whether they are pressed at the same time, and sends the data to the cloud computing system for analysis via the Internet transceiver unit. The data is then stored in the database to provide driving diagnostic results.

Benefits of technology

It effectively prevents drivers from simultaneously pressing the accelerator and brake pedals, provides driving diagnostic results images, promotes driver improvement in driving behavior, reduces computational load, and supports the development of third-party applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115140058B_ABST
    Figure CN115140058B_ABST
Patent Text Reader

Abstract

This invention relates to a driving diagnostic device and a driving diagnostic method. The driving diagnostic device includes an event recognition unit capable of acquiring a first detection value and a second detection value from a vehicle, wherein the first detection value indicates that an accelerator pedal installed on the vehicle is depressed, and the second detection value indicates that a brake pedal installed on the vehicle is depressed, and the event recognition unit determines whether the accelerator pedal and the brake pedal are depressed simultaneously based on the acquired first detection value and the acquired second detection value.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to Japanese Patent Application No. 2021-060721, filed on March 31, 2021, which is incorporated herein by reference in its entirety. Technical Field

[0003] This invention relates to a driving diagnostic device and a driving diagnostic method. Background Technology

[0004] Japanese Patent No. 3593502 (JP 3593502 B) and Japanese Patent No. 6648304 (JP6648304 B) disclose a driving diagnostic device that performs calculations and obtains driving diagnostic results, wherein the calculations are based on detection values, which are physical quantities that change based on at least one of the vehicle's driving, steering, and braking. Summary of the Invention

[0005] The driving diagnostic equipment in JP 3593502 B and JP 6648304 B has room for improvement in driving diagnostics regarding the operation of the accelerator pedal and brake pedal.

[0006] In view of the above facts, the object of the present invention is to obtain a driving diagnostic device and a driving diagnostic method that can help drivers avoid simultaneously pressing the accelerator pedal and the brake pedal.

[0007] The driving diagnostic device according to the first aspect of the present invention includes:

[0008] An event recognition unit is provided, which is capable of obtaining a first detection value and a second detection value from the vehicle, wherein the first detection value indicates that the accelerator pedal installed on the vehicle is pressed, and the second detection value indicates that the brake pedal installed on the vehicle is pressed, and the event recognition unit determines whether the accelerator pedal and the brake pedal are pressed simultaneously based on the obtained first detection value and the obtained second detection value.

[0009] According to the first aspect of the driving diagnostic device of the present invention, the event recognition unit is capable of obtaining a first detection value and a second detection value from the vehicle, wherein the first detection value indicates that the accelerator pedal provided on the vehicle is depressed, and the second detection value indicates that the brake pedal provided on the vehicle is depressed. Furthermore, the event recognition unit determines whether the accelerator pedal and the brake pedal are depressed simultaneously based on the obtained first detection value and the obtained second detection value.

[0010] Therefore, the driving diagnostic device according to the first aspect of the present invention can prompt a driver who has recognized the determination result of the event recognition unit as simultaneously pressing the accelerator pedal and the brake pedal to avoid subsequently pressing the accelerator pedal and the brake pedal simultaneously.

[0011] In the driving diagnostic device according to the invention indicated in the second aspect of the invention, and in the invention according to the first aspect of the invention, a transceiver unit is further included, the transceiver unit being capable of receiving the first detection value and the second detection value from the vehicle via the Internet, and the transceiver unit being capable of sending the acquired first detection value and the acquired second detection value to the event recognition unit.

[0012] In the present invention according to a second aspect, the driving diagnostic device further includes a transceiver unit capable of receiving a first detection value and a second detection value from the vehicle via the Internet, and capable of sending the acquired detection values ​​to an event recognition unit. Thus, for example, the driving diagnostic device can be interpreted as a cloud computing system.

[0013] In the driving diagnostic device according to the invention indicated in the third aspect of the invention, in the invention according to the first aspect or the second aspect of the invention, a database unit is included, the database unit storing information on whether the accelerator pedal and the brake pedal are pressed simultaneously, the information being determined by the event recognition unit, and the database unit being connected to the Internet.

[0014] In the invention according to a third aspect, information determined by the event recognition unit as to whether the accelerator pedal and brake pedal are simultaneously depressed is stored in a database unit connected to the Internet. Therefore, a person with access to the database can use this information to develop applications.

[0015] According to a fourth aspect of the present invention, the driving diagnostic method includes the steps of: obtaining a first detection value and a second detection value from a vehicle, wherein the first detection value indicates that an accelerator pedal disposed on the vehicle is depressed, and the second detection value indicates that a brake pedal disposed on the vehicle is depressed; and determining, based on the obtained first detection value and the obtained second detection value, whether the accelerator pedal and the brake pedal are depressed simultaneously.

[0016] As described above, the driving diagnostic device and driving diagnostic method of the present invention have the excellent effect of enabling drivers to avoid simultaneously pressing the accelerator pedal and the brake pedal. Attached Figure Description

[0017] The features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, wherein like reference numerals denote like elements, and wherein:

[0018] Figure 1 This is a view illustrating a vehicle, according to one embodiment, capable of sending detection values ​​to a driver diagnostic device;

[0019] Figure 2 This is a view showing a driving diagnostic device, a vehicle, and a mobile terminal according to an embodiment;

[0020] Figure 3 yes Figure 2 The control block diagram of the first server of the driving diagnostic equipment shown in the figure;

[0021] Figure 4 yes Figure 3 The functional block diagram of the second server shown below;

[0022] Figure 5 yes Figure 2 The control block diagram of the third server of the driving diagnostic equipment shown in the figure;

[0023] Figure 6 yes Figure 2 The functional block diagram of the fourth server of the driving diagnostic equipment shown in the figure;

[0024] Figure 7 yes Figure 2 The functional block diagram of the mobile terminal shown in the figure;

[0025] Figure 8 It is a view that displays a list of scenes;

[0026] Figure 9 It is a view that displays a list of events;

[0027] Figure 10 This is a flowchart illustrating the process executed by the second server;

[0028] Figure 11 This is a flowchart illustrating the process executed by the fourth server;

[0029] Figure 12 It is shown by Figure 2 A flowchart of the process executed by the mobile terminal in the process;

[0030] Figure 13 It is a view showing an image displayed on the display unit of a mobile terminal; and

[0031] Figure 14 It is a view showing the image displayed on the display unit of a mobile terminal. Detailed Implementation

[0032] Hereinafter, embodiments of the driving diagnostic device 10 and driving diagnostic method according to the present invention will be described with reference to the accompanying drawings.

[0033] like Figure 1 As shown, the vehicle 30, capable of communicating data with the driving diagnostic equipment 10 via a network, includes an electronic control unit (ECU) 31, wheel speed sensors 32, accelerometer operation sensors 33, brake switches 34, steering angle sensors 35, turn signal switches 36, a global positioning system (GPS) receiver 37, a wireless communication device 38, and a camera 39. A vehicle ID is attached to the vehicle 30 capable of receiving diagnoses from the driving diagnostic equipment 10. In this embodiment, at least one vehicle 30 capable of receiving diagnoses from the driving diagnostic equipment 10 is manufactured by body A. The wheel speed sensors 32, accelerometer operation sensors 33, brake switches 34, steering angle sensors 35, turn signal switches 36, GPS receivers 37, wireless communication devices 38, and camera 39 are connected to the ECU 31. The ECU 31 includes a central processing unit (CPU: processor), read-only memory (ROM), random access memory (RAM), storage devices, a wireless communication interface (I / F), and input-output I / F. The CPU, ROM, RAM, storage devices, communication I / F, and input-output I / F of ECU 31 are interconnected to enable communication with each other via a bus. These networks include telecommunications operator networks and the Internet. The wireless communication device 38 of vehicle 30 and the mobile terminal (operating terminal) 50 (described later) perform data communication via the network. Furthermore, as... Figure 1 As shown, vehicle 30 has an accelerator pedal 30A, a brake pedal 30B, and a turn signal pole 30C. The turn signal pole 30C can be rotated from a predetermined neutral position (initial position) to a first position on the upper side and a second position on the lower side.

[0034] Wheel speed sensor 32, accelerator operation amount sensor 33, brake switch 34, steering angle sensor 35, turn signal switch 36, and GPS receiver 37 are detection units that repeatedly detect the following physical quantities each time a predetermined amount of time has elapsed. These physical quantities are physical quantities that change based on at least one of the vehicle 30's driving, steering, and braking, or physical quantities that change due to operation of predetermined operating components (such as accelerator pedal 30A, brake pedal 30B, and turn signal lever 30C). The vehicle 30 is equipped with four wheel speed sensors 32. Each wheel speed sensor 32 detects the wheel speed of one corresponding wheel among the four wheels of the vehicle 30. Accelerator operation amount sensor 33 detects the change in accelerator operation amount when accelerator pedal 30A is depressed. Brake switch 34 opens and outputs a detection signal when brake pedal 30B is depressed with an operation amount equal to or greater than a predetermined value, and closes (does not output a detection signal) when the operation amount of brake pedal 30B is less than the predetermined value. When brake switch 34 outputs a detection signal, the braking device (not shown) in vehicle 30 is activated, and the brake lights (not shown) are turned on under the control of ECU 31. Steering angle sensor 35 detects the steering angle of the steering wheel. Turn signal switch 36 detects the operation of turn signal lever 30C. For example, when turn signal switch 36 detects that turn signal lever 30C has moved from the neutral position to the first position, the left-side turn indicator (not shown) in vehicle 30 is turned on under the control of ECU 31. Conversely, when turn signal switch 36 detects that turn signal lever 30C has moved to the second position, the right-side turn indicator (not shown) in vehicle 30 is turned on under the control of ECU 31. By receiving GPS signals transmitted from GPS satellites, GPS receiver 37 obtains information about the location in which vehicle 30 is traveling (hereinafter referred to as "position information"). The detection values ​​detected by the wheel speed sensor 32, accelerator operation sensor 33, brake switch 34, steering angle sensor 35, turn signal switch 36, and GPS receiver 37 are sent to the ECU 31 via the Controller Area Network (CAN) located in the vehicle 30 and stored in the storage device of the ECU 31. Furthermore, the camera 39 repeatedly captures images of objects located outside the vehicle 30 each predetermined time interval. The image data acquired by the camera 39 is sent to the ECU 31 via the network located in the vehicle 30 and stored in the storage device.

[0035] like Figure 2As shown, the driving diagnostic device 10 includes a first server 12, a second server 14, a third server (database unit) 16, and a fourth server 18. For example, the first server 12, second server 14, third server 16, and fourth server 18 are arranged in a building. The first server 12 and fourth server 18 are connected to the aforementioned network. The first server 12 and second server 14 are connected via a local area network (LAN). The second server 14 and third server 16 are connected via a LAN. The third server 16 and fourth server 18 are connected via a LAN. That is, the driving diagnostic device 10 is configured as a cloud computing system. In this embodiment, the first server 12, second server 14, and third server 16 are managed by entity A. Conversely, the fourth server 18 is managed by entity B.

[0036] Figure 3 The first server 12 shown is configured to include a CPU 12A, ROM 12B, RAM 12C, storage device (detection value storage unit) 12D, wireless communication I / F 12E, and input-output I / F 12F. The CPU 12A, ROM 12B, RAM 12C, storage device 12D, wireless communication I / F 12E, and input-output I / F 12F are connected to enable communication with each other via bus 12Z. The first server 12 can obtain date and time information from a timer (not shown).

[0037] CPU 12A is a central processing unit that executes various programs and controls various units. That is, CPU 12A reads programs from ROM 12B or storage device 12D and uses RAM 12C as its working area to execute programs. CPU 12A controls each configuration and performs various arithmetic operations (information processing) according to the programs recorded in ROM 12B or storage device 12D.

[0038] ROM 12B stores various programs and data. RAM 12C serves as a temporary storage area for programs or data. Storage device 12D consists of a storage device (such as a hard disk drive (HDD) or solid-state drive (SSD)) and stores various programs and data. Communication I / F 12E is the interface for the first server 12 to communicate with other devices. Input / output I / F 12F is the interface for communicating with various devices.

[0039] The detection data, representing the detection values ​​detected by the wheel speed sensor 32, accelerator operation sensor 33, brake switch 34, steering angle sensor 35, turn signal switch 36, and GPS receiver 37 of vehicle 30, as well as the image data acquired by camera 39, are transmitted via the aforementioned network from wireless communication device 38 to transceiver unit 13 of first server 12 after a predetermined amount of time has elapsed. The detection data and image data are also recorded in storage device 12D. All the detection data and image data recorded in storage device 12D includes vehicle ID information, acquisition time information, and location information acquired by GPS receiver 37. That is, the detection data and image data are associated with vehicle ID information, time information, and location information.

[0040] The basic configurations of the second server 14, the third server 16, and the fourth server 18 are the same as those of the first server 12.

[0041] Figure 4 A block diagram illustrates an example of the functional configuration of the second server 14. The second server 14 includes a transceiver unit 141, a scene extraction unit 142, a KPI (Key Performance Indicator) acquisition unit 143, a score calculation unit 144, an event recognition unit 145, and a deletion unit 146 as part of its functional configuration. The transceiver unit 141, scene extraction unit 142, KPI acquisition unit 143, score calculation unit 144, event recognition unit 145, and deletion unit 146 are implemented by the CPU of the second server 14, which reads and executes programs stored in ROM.

[0042] The transceiver unit 141 transmits and receives information from the first server 12 and the third server 16 via the LAN. Detection value data and image data recorded in the storage device 12D of the first server 12 are transmitted to the transceiver unit 141 of the second server 14 while being associated with vehicle ID, time information, and location information. The detection value data and image data transmitted from the first server 12 to the transceiver unit 141 include data groups acquired during a predetermined data detection period. This data detection period is, for example, 30 minutes. The data group (detection value data and image data) acquired during the data detection period corresponding to a vehicle ID will be referred to below as a "detection value data group". The detection value data groups recorded in the first server 12 are transmitted to the transceiver unit 141 sequentially, starting from the earliest acquisition time. More specifically, as described below, when a detection value data group is deleted from the storage device of the second server 14, a newer detection value data group than the aforementioned detection value data group is transmitted from the first server 12 to the transceiver unit 141, and this new detection value data group is stored in the storage device of the second server 14.

[0043] The scene extraction unit 142 identifies the detection value data set stored in the storage device of the second server 14 as data representing specific detection values ​​and other data. More specifically, the scene extraction unit 142 considers the data necessary to obtain the KPIs described later as data representing specific detection values.

[0044] Figure 8 This is a scene list 22 recorded in the ROM of the second server 14. Scene list 22 is defined based on the operation target of the components operated by the driver of vehicle 30, the operation content of the operation target, etc. The categories of the largest items in scene list 22 are "safety" and "comfort". Furthermore, the operation targets included in the "safety" category are the accelerator pedal, brake pedal, and steering wheel. The operation target included in the "comfort" category is the brake pedal. A scene, specific detection value, and extraction conditions are specified for each operation target.

[0045] For example, when the scene extraction unit 142 determines, based on the detection value of the accelerometer operation quantity sensor 33, that the accelerometer pedal has been operated under the condition that extraction condition 1, included in the category "Safety," is met, the scene extraction unit 142 refers to the scene list 22 and determines that "the accelerometer pedal is being used to perform a start-up operation." Extraction condition 1 is, for example, that the vehicle speed of the vehicle 30 is equal to or greater than a predetermined first threshold. The vehicle speed of the vehicle 30 is calculated by the scene extraction unit 142 based on the wheel speed, which is included in the detection value data set stored in the storage device of the second server 14 and detected by each wheel speed sensor 32. Furthermore, the scene extraction unit 142 determines whether extraction condition 1 is met based on the calculated vehicle speed and the first threshold. When it is determined that extraction condition 1 is met, the scene extraction unit 142 extracts data related to the accelerometer operation quantity detected by the accelerometer operation quantity sensor 33 in the time region when extraction condition 1 is met from the detection value data set stored in the storage device, as data indicating a specific detection value.

[0046] When the detection value of brake switch 34 determines that the brake pedal has been operated under the condition that extraction condition 2 included in the category "Safety" is met, scene extraction unit 142 refers to scene list 22 and determines that "an overall operation is being performed by using the brake pedal". Extraction condition 2 is, for example, that the vehicle speed of vehicle 30 is equal to or greater than a predetermined second threshold. Scene extraction unit 142 determines whether extraction condition 2 is met based on the calculated vehicle speed and the second threshold. When it is determined that extraction condition 2 is met, scene extraction unit 142 extracts data related to the wheel speed detected by wheel speed sensor 32 in the time region when extraction condition 2 is met from the detection value data set stored in the storage device, as data indicating a specific detection value.

[0047] When the scene extraction unit 142 determines, based on the detection value of the steering angle sensor 35, that the steering wheel has been operated under the condition that extraction condition 3, included in the category "Safety," is met, it refers to the scene list 22 and determines that "a steering wheel cornering operation has been performed." Extraction condition 3 is, for example, that the steering angle (steering amount) of the steering wheel within a predetermined time period is equal to or greater than a predetermined third threshold. The scene extraction unit 142 determines that extraction condition 3 is met based on the steering angle information and the third threshold, wherein the steering angle information is included in a set of detection value data stored in the storage device of the second server 14, and the steering angle information is detected by the steering angle sensor 35. When it is determined that extraction condition 3 is met, the scene extraction unit 142 extracts data related to the steering angle detected by the steering angle sensor 35 in the time region when extraction condition 3 is met from the set of detection value data stored in the storage device, as data indicating a specific detection value.

[0048] When the detection value based on brake switch 34 determines that the brake pedal has been operated under the condition that extraction condition 4, included in the category "Comfort," is met, scene extraction unit 142 refers to scene list 22 and determines that "an overall operation is being performed by using the brake pedal." Extraction condition 4 is, for example, that the vehicle speed 30 is equal to or greater than a predetermined fourth threshold. Scene extraction unit 142 determines whether extraction condition 4 is met based on the calculated vehicle speed and the fourth threshold. When it is determined that extraction condition 4 is met, scene extraction unit 142 extracts data related to the wheel speed detected by wheel speed sensor 32 in the time region when extraction condition 4 is met from the detection value data set stored in the storage device, as data indicating a specific detection value.

[0049] When any extraction condition is met, the KPI acquisition unit 143 acquires (calculates) the KPI corresponding to the extraction condition that is met.

[0050] For example, when extraction condition 1 is met, the KPI acquisition unit 143 obtains the maximum accelerometer operation in the time region when extraction condition 1 is met from the data (specific detection value) on the accelerometer operation volume obtained by the scene extraction unit 142, as the KPI.

[0051] When extraction condition 2 is met, the KPI acquisition unit 143 calculates the minimum front-to-back acceleration of the vehicle 30 in the time region when extraction condition 2 is met as the KPI based on data (specific detection values) related to the wheel speed obtained by the scene extraction unit 142. That is, the KPI acquisition unit 143 uses the wheel speed to obtain the calculated value (derivative value) as the KPI.

[0052] When extraction condition 3 is met, the KPI acquisition unit 143 calculates the turning angle in the time region when extraction condition 3 is met as the KPI based on the data (specific detection value) related to the turning angle obtained by the scene extraction unit 142. That is, the KPI acquisition unit 143 uses the turning angle to obtain the calculated value (second derivative value) as the KPI.

[0053] When extraction condition 4 is met, the KPI acquisition unit 143 calculates the acceleration of vehicle 30 in the time region when extraction condition 4 is met as a KPI based on data (specific detection value) related to the wheel speed obtained by the scene extraction unit 142. That is, the KPI acquisition unit 143 uses the wheel speed to obtain the calculated value (second derivative value) as the KPI.

[0054] As described below, the scoring calculation unit 144 calculates the safety level score, comfort level score, and driving operation score based on the calculated KPIs.

[0055] The event recognition unit 145 references the detection value data set stored in the storage device of the second server 14, and Figure 9 Events are identified by an event list 24 shown and recorded in the ROM of the second server 14. An event is a specific action that occurs in the vehicle 30 due to the driver's operation. The event list 24 defines the type (content) of the event and the conditions (specific conditions) under which it is identified as an event. In the event list 24, "short-time turn signal operation" and "simultaneous pedal depressing" are defined as events.

[0056] The event recognition unit 145 determines whether the turn signal pole 30C has moved from the neutral position to a first position or a second position based on all detection values ​​of the turn signal switch 36 included in the detection value data set stored in the storage device. The first or second position to which the turn signal pole 30C has moved can be referred to as the "operating position". Furthermore, when the event recognition unit 145 detects that the turn signal pole 30C has moved to the operating position, the event recognition unit 145 determines, based on information about the time when the detection value of the turn signal switch 36 was obtained, whether the duration of the continuous time the turn signal pole 30C is in the operating position is less than a predetermined fifth threshold. When it is determined that the duration is less than the fifth threshold, the event recognition unit 145 identifies the date and time when the turn signal pole 30C was in the operating position less than the fifth threshold as an event, and identifies the location information at the time this state occurred as an event. This fifth threshold is determined, for example, based on the regulations of the country where the road the vehicle 30 is currently traveling on is located. For example, if the regulations of that country require the driver to position the turn signal pole 30C in the operating position for 3 seconds or longer, then the fifth threshold is "3 (seconds)".

[0057] Whether the accelerator pedal 30A and brake pedal 30B are simultaneously depressed is determined by the event recognition unit 145 based on all detection values ​​(first detection values) of the accelerator operation quantity sensor 33 and all detection values ​​(second detection values) of the brake switch 34 included in the detection value data group stored in the storage device. More specifically, the event recognition unit 145 determines whether the state of the vehicle speed of the vehicle 30 being equal to or greater than a predetermined value, the state of the accelerator operation quantity as detected by the accelerator operation quantity sensor 33 being equal to or greater than a predetermined value, and the state of the brake switch 34 outputting a detection signal occur simultaneously. When the accelerator pedal 30A and brake pedal 30B are depressed simultaneously, an unnecessarily large load may be applied to the braking device and drive system of the vehicle 30. When it is determined that these states occur simultaneously, the event recognition unit 145 specifies the date and time when the state occurs and the location information when the state occurs as an event. In this case, the predetermined value of the vehicle speed is, for example, "5 (km / h)," and the predetermined value of the accelerator operation quantity is, for example, "15%."

[0058] When the scene extraction unit 142, KPI acquisition unit 143, score calculation unit 144, and event recognition unit 145 complete the aforementioned processing of a set of detection value data recorded in the storage device, the obtained safety level score, comfort level score, driving operation score, and data about the specified event are sent by the transceiver unit 141 along with the vehicle ID information to the third server 16. The data related to the event includes information about the date and time when each specified event occurs, location information, and image data acquired by the camera 39 over a predetermined time period including the time when the event occurred.

[0059] After the scene extraction unit 142, KPI acquisition unit 143, score calculation unit 144 and event recognition unit 145 have completed the above processing of a detection value data group, the deletion unit 146 deletes the detection value data group from the storage device of the second server 14.

[0060] The third server 16 receives security level scores, comfort level scores, driving operation scores, and data related to identified events sent from the second server 14. For example... Figure 5 As shown, the third server 16 has a transceiver unit 161 configured as a functional component. The transceiver unit 161 is implemented by the CPU of the third server 16, which reads and executes a program stored in ROM. Data received by the transceiver unit 161 is recorded in the storage device of the third server 16. Data regarding safety level scores, comfort level scores, driving operation scores, and specified events are sequentially sent from the second server 14 to the third server 16, and the third server 16 records all received data in its storage device.

[0061] The fourth server, 18, functions at least as a web server and a web application server. For example... Figure 6 As shown, the fourth server 18 has a transceiver control unit 181 and a data generation unit 182 configured as functional components. The transceiver control unit 181 and the data generation unit 182 are implemented by the CPU of the fourth server 18, which reads and executes programs stored in ROM. The transceiver control unit 181 controls the transceiver unit 19 of the fourth server 18.

[0062] Figure 2 The mobile terminal 50 shown includes a CPU, ROM, RAM, storage device, communication I / F, and input-output I / F. The mobile terminal 50 is, for example, a smartphone or tablet computer. The CPU, ROM, RAM, storage device, communication I / F, and input-output I / F of the mobile terminal 50 are interconnected to enable communication with each other via a bus. The mobile terminal 50 can obtain date and time information from a timer (not shown). The mobile terminal 50 is provided with a display unit 51 having a touch panel. The display unit 51 is connected to the input-output I / F of the mobile terminal 50. Furthermore, map data is recorded in the storage device of the mobile terminal 50. The mobile terminal 50 has a transceiver unit 52.

[0063] Figure 7 A block diagram illustrates an example of the functional configuration of mobile terminal 50. Mobile terminal 50 includes a transceiver control unit 501 and a display unit control unit 502 as part of the functional configuration. The transceiver control unit 501 and the display unit control unit 502 are implemented by a CPU that reads and executes programs stored in ROM. Mobile terminal 50 is owned, for example, by a driver of vehicle 30, which has a vehicle ID. A pre-defined driving diagnostic display application is installed on mobile terminal 50.

[0064] The transceiver unit 52, controlled by the transceiver control unit 501, sends data to the transceiver unit 19 of the fourth server 18 and receives data from it.

[0065] The display unit control unit 502 controls the display unit 51. That is, the display unit control unit 502 causes the display unit 51 to display, for example, information received from the transceiver unit 19 via the transceiver unit 52 and information input via the touch panel. Information input via the touch panel of the display unit 51 can be transmitted to the transceiver unit 19 by the transceiver unit 52.

[0066] Operation and Effect

[0067] The operation and effects of this embodiment will be described next.

[0068] Next, we will use Figure 10 The flowchart describes the process executed by the second server 14. The second server 14 repeats the process each time a predetermined amount of time has elapsed. Figure 10 The process of creating a flowchart.

[0069] First, in step S10, the transceiver unit 141 of the second server 14 determines whether the detection value data group has been received from the first server 12. In other words, the transceiver unit 141 determines whether the detection value data group has been recorded in the storage device of the second server 14.

[0070] When the result is determined to be "yes" in step S10, the second server 14 proceeds to step S11, and the scene extraction unit 142 extracts data representing specific detection values ​​that meet the extraction conditions from the detection value data group stored in the storage device. Furthermore, the KPI acquisition unit 143 acquires (calculates) each KPI based on the data representing the extracted specific detection values.

[0071] The second server 14, having completed step S11, proceeds to step S12, and the scoring calculation unit 144 calculates the safety level score, comfort level score, and driving operation score.

[0072] For example, when in Figure 8 When extraction condition 1 is met, if the obtained KPI (maximum accelerator operation) is a predetermined value or greater, the KPI score is 5 points. Conversely, when the KPI is less than the predetermined value, the KPI score is 100 points.

[0073] For example, when in Figure 8 When extraction condition 2 is met, if the obtained KPI (minimum forward and backward acceleration) is lower than the predetermined value, the KPI score is 5 points. Conversely, when the KPI is equal to or greater than the predetermined value, the KPI score is 100 points.

[0074] For example, when in Figure 8 When extraction condition 3 is met, if the obtained KPI (acceleration of steering angle) is a predetermined value or greater, the KPI score is 5 points. Conversely, when the KPI is less than the predetermined value, the KPI score is 100 points.

[0075] The safety level score is the value (average) obtained by dividing the total score of each KPI corresponding to extraction condition 1 to extraction condition 3 by the number of items in the category "safety" (3).

[0076] For example, when the condition is met Figure 8When extraction condition 4 is met, if the obtained KPI (average jerk) is a predetermined value or greater, the safety level score of that KPI is 5 points. Conversely, when the KPI is less than the predetermined value, the safety level score of that KPI is 100 points.

[0077] The comfort level score is the average value obtained by dividing the total score of the KPIs in the "Comfort" category by the number of items in the "Comfort" category. However, in this embodiment, since the number of items in the "Comfort" category is "1", the score associated with the KPI corresponding to extraction condition 4 is the comfort level score.

[0078] Furthermore, the scoring calculation unit 144 calculates the driving operation score based on the calculated safety level score and comfort level score. Specifically, the scoring calculation unit 144 obtains the driving operation score as the average value obtained by dividing the total score of the safety level score and comfort level score by the sum of the number of items in the safety level score and comfort level score (4).

[0079] The second server 14, having completed step S12, proceeds to step S13, and the event recognition unit 145 recognizes the event based on the detection value data set stored in the storage device of the second server 14.

[0080] The second server 14, which has completed step S13, proceeds to step S14, and the transceiver unit 141 sends the data on safety level score, comfort level score, driving operation score and specified event along with the vehicle ID information to the third server 16.

[0081] The second server 14, having completed step S14, proceeds to step S15, and the deletion unit 146 deletes the detection value data group from the storage device of the second server 14.

[0082] When a "No" is determined in step S10, or when the process in step S15 is completed, the second server 14 temporarily terminates. Figure 10 The process of creating a flowchart.

[0083] Next, we will refer to Figure 11 The flowchart describes the process executed by the fourth server 18. The fourth server 18 repeats this process each time a predetermined amount of time has elapsed. Figure 11 The process of creating a flowchart.

[0084] First, in step S20, the transceiver unit 181 of the fourth server 18 determines whether a display request has been sent from the transceiver control unit 501 (transceiver unit 52) ​​of the mobile terminal 50, where the driving diagnostic display application is activated, to the transceiver unit 19. That is, the transceiver control unit 181 determines whether there is an access operation from the mobile terminal 50. This display request includes information about the vehicle ID associated with the mobile terminal 50.

[0085] When "yes" is determined in step S20, the fourth server 18 proceeds to step S21, and the transceiver control unit 18 (transceiver unit 19) communicates with the third server 16. The transceiver control unit 181 (transceiver unit 19) receives data from the transceiver unit 161 of the third server 16 regarding security level scores, comfort level scores, driving operation scores, and specified events corresponding to the vehicle ID associated with the mobile terminal 50 that sent the display request.

[0086] Having completed step S21, the fourth server 18 proceeds to step S22, and the data generation unit 182 uses the data received in step S21 to generate data representing the driving diagnostic result image 55 (see...). Figure 13 The driving diagnostic result image 55 can be displayed on the display unit 51 of the mobile terminal 50 in which the driving diagnostic display application is activated.

[0087] The fourth server 18, having completed step S22, proceeds to step S23, and the transceiver unit 19 sends the data generated by the data generation unit 182 in step S22 to the transceiver control unit 501 (transceiver unit 52) ​​of the mobile terminal 50.

[0088] The fourth server 18 temporarily terminates when the result is "No" in step S20, or when the process of step S23 is completed. Figure 11 The process of creating a flowchart.

[0089] Next, we will refer to Figure 12 The flowchart describes the process executed by the mobile terminal 50. The mobile terminal 50 repeats this process each time a predetermined amount of time has elapsed. Figure 12 The process of creating a flowchart.

[0090] In step S30, the display unit control unit 502 of the mobile terminal 50 determines whether the driving diagnostic display application is running.

[0091] When it is determined to be "yes" in step S30, the mobile terminal 50 proceeds to step S31 and determines whether the transceiver control unit 501 (transceiver unit 52) ​​has received data representing the driving diagnostic result image 55 from the transceiver unit 19 of the fourth server 18.

[0092] When the result is "yes" in step S31, the mobile terminal 50 proceeds to step S32, and the display unit control unit 502 causes the display unit 51 to display the driving diagnostic result image 55.

[0093] like Figure 13 As shown, the driving diagnostic result image 55 includes a safety and comfort level display unit 56, a score display unit 57, and an event display unit 58. Safety level scores and comfort level scores are displayed on the safety and comfort level display unit 56. Driving operation scores are displayed on the score display unit 57. Information for each specified event is displayed on the event display unit 58. The information for each event includes the date and time when the event occurred, as well as the details.

[0094] The mobile terminal 50, having completed step S32, proceeds to step S33, where the display unit control unit 502 determines whether the user's hand has touched the event display unit 58 of the display unit 51 (touch panel).

[0095] When the result is determined to be "yes" in step S33, the mobile terminal 50 proceeds to step S34, and the display unit control unit 502 causes the display unit 51 to... Figure 14 The map data shown is map image 60. Here, it is assumed that the driver touched "Event 1" in the event display unit 58. In this case, map image 60 includes map information of the location where Event 1 occurred and its surrounding environment, and the location where Event 1 occurred is indicated by a star. Furthermore, when the user touches the star, event image 61 is displayed, which is represented by image data acquired by camera 39 within a predetermined time period (including the time when Event 1 occurred). This predetermined time period is, for example, 10 seconds.

[0096] Having completed step S34, the mobile terminal 50 proceeds to step S35, and the display unit control unit 502 determines whether the user's hand has touched the return operation unit 62 on the map image 60. When "yes" is determined in step S35, the display unit control unit 502 of the mobile terminal 50 proceeds to step S32, and the display unit 51 displays the driving diagnostic result image 55.

[0097] When the result is "No" in step S30, step S33, or step S35, the mobile terminal 50 temporarily terminates. Figure 12 The process of creating a flowchart.

[0098] As described above, in the system 10 and driving diagnostic method of this embodiment, when the event recognition unit 145 determines that the duration of the turn signal pole 30C being in the operating position is less than a fifth threshold, information indicating that the duration is less than the fifth threshold is included in the driving diagnostic result image 55. Therefore, the system 10 and driving diagnostic method of this embodiment can encourage a driver who has already recognized the duration being less than the fifth threshold by viewing the driving diagnostic result image 55 to suppress the duration of the turn signal pole 30C from becoming less than the fifth threshold when subsequently moving the turn signal pole 30C to the operating position.

[0099] Furthermore, in the driving diagnostic method and system 10 of this embodiment, when the event recognition unit 145 determines that the accelerator pedal 30A and the brake pedal 30B are pressed simultaneously, the information that the accelerator pedal 30A and the brake pedal 30B are pressed simultaneously is included in the driving diagnostic result image 55. Therefore, the system 10 and driving diagnostic method of this embodiment can help drivers who have recognized by viewing the driving diagnostic result image 55 that the accelerator pedal 30A and the brake pedal 30B are pressed simultaneously to avoid pressing the accelerator pedal 30A and the brake pedal 30B simultaneously when performing driving operations of the vehicle 30 later.

[0100] Furthermore, the image data included in the data set sent from the second server 14 to the third server 16 is only the image data at the time the event occurred. Therefore, the amount of data accumulated in the storage device of the third server 16 is less than the case where all the image data recorded in the storage device of the second server 14 were sent from the second server 14 to the third server 16.

[0101] Furthermore, in the driving diagnostic device 10 and driving diagnostic method of this embodiment, driving operation scores (KPIs) and events are used to perform driving diagnostics. Therefore, the driver who sees the driving diagnostic result image 55 can understand the characteristics of their driving operation from a broad perspective.

[0102] Furthermore, the KPI acquisition unit 143 calculates the KPI using only specific detection values ​​from the detection value data set. Therefore, compared to performing KPI calculation using all detection value data sets, the computational load on the KPI acquisition unit 143 is lower. Consequently, the computational load on the driving diagnostic device 10 and the driving diagnostic method in this embodiment is small.

[0103] Furthermore, in the driving diagnostic device 10 and driving diagnostic method of this embodiment, a subject B, different from subject A which manages the first server 12, the second server 14, and the third server 16 and manufactures vehicles, can access data stored in the third server 16. Therefore, a person (organization) different from subject A can create an application (driving diagnostic display application) that uses the driving diagnostic results obtained through the driving diagnostic device 10 and driving diagnostic method of this embodiment. Thus, the development of such applications can be facilitated.

[0104] Although the driving diagnostic device 10 and driving diagnostic method according to this embodiment have been described above, the design of the driving diagnostic device 10 and driving diagnostic method may be appropriately changed without departing from the scope of the present invention.

[0105] For example, the event recognition unit 145 can determine whether the state where the accelerator operation amount detected by the accelerator operation amount sensor 33 is equal to or greater than a predetermined value, and whether the state where the brake switch 34 outputs a detection signal occurs simultaneously. In other words, the event recognition unit 145 can determine whether the accelerator pedal 30A and the brake pedal 30B are pressed simultaneously, regardless of the vehicle speed 30.

[0106] Vehicle 30 may include a sensor (not shown) that detects the pressure (hydraulic pressure) of brake hydraulic fluid in the master cylinder when the brake pedal 30B is depressed. Then, when the hydraulic pressure detected by the sensor is equal to or exceeds a predetermined value, event recognition unit 145 can determine that "brake pedal 30B has been depressed." The predetermined value is, for example, 0.07 MPa.

[0107] Figure 8 The categories, operational objectives, scenarios, specific detection values, extraction conditions, and KPIs shown are not limited to... Figure 8 As shown in the diagram. For example, there can be multiple operational goals, scenarios, specific detection values, extraction conditions, and KPIs for the category "comfort".

[0108] Figure 9 The event types described herein are not limited to Figure 9 The event types described herein. In addition to "short-duration turn signal operation" and "simultaneous pedal depressing", event list 24 may also include other events. For example, event recognition unit 145 may designate at least one of the following as events: sudden steering, activation of anti-lock braking system (ABS), activation of pre-collision safety system (PCS), and detection of collision with obstacle.

[0109] The driver diagnostic device 10 can be implemented with a different configuration than described above. For example, the first server 12, the second server 14, the third server 16, and the fourth server 18 can be implemented by a single server. In this case, for example, by using a management program, the internal space of the server can be virtually divided into multiple areas corresponding to the first server 12, the second server 14, the third server 16, and the fourth server 18.

[0110] The detection unit that acquires the set of detection value data can be any device, as long as it acquires a physical quantity that changes based on at least one of the vehicle's driving, steering, and braking, or a physical quantity that changes when a predetermined operating component is operated. For example, the detection unit can be a sensor for measuring the engine's coolant temperature, a yaw rate sensor, a gearshift lever position sensor, etc. Furthermore, the number of detection units can be any.

[0111] The driving diagnostic device 10 may not obtain driving operation scores, but may only obtain events. In this case, only the events are stored in the storage device of the third server 16.

[0112] The methods for obtaining (calculating) KPIs and calculating driving operation scores may differ from those described above. For example, safety level scores and comfort level scores can be calculated simultaneously when weighting each KPI.

[0113] The driver diagnostic device 10 does not need to be connected to the Internet. In this case, for example, the set of test value data obtained from the vehicle is recorded on a portable recording medium (e.g., USB), and the set of test value data in the recording medium is copied to the first server 12.

[0114] When the third server 16 receives an access request from the fourth server 18, the third server 16 may have the function of confirming access permissions. In this case, the fourth server 18 can only receive data on the security level score, comfort level score, driving operation score, and specified event from the third server 16 after the third server 16 confirms that the fourth server 18 has the access permissions.

[0115] A constant restriction can be imposed on access by subject B (fourth server 18) to a portion of data recorded on the storage device of third server 16. For example, information indicating that the data is subject to restriction can be added to a group of data recorded on the storage device of third server 16. Access by subject B (fourth server 18) to the data for which the information indicating that access is subject to restriction is added is prohibited (even if the user has the aforementioned access permissions). The data for which the information indicating that access is subject to restriction is added is, for example, location information.

[0116] Instead of GPS receiver 37, vehicle 30 may include a receiver capable of receiving information from satellites of global navigation satellite systems other than GPS (e.g., Galileo).

[0117] The mobile terminal 50 can read map data from the web server and display the map image on the display unit 51.

Claims

1. A driving diagnosis apparatus comprising an event recognition unit, a scene extraction unit, a key performance indicator acquisition unit, a score calculation unit, a data generation unit, and a display unit, The event recognition unit can obtain the first detection value and the second detection value from the vehicle, wherein the first detection value indicates that an accelerator pedal provided on the vehicle is depressed, and the second detection value indicates that a brake pedal provided on the vehicle is depressed, and the event recognition unit determines whether the accelerator pedal and the brake pedal are simultaneously depressed based on the acquired first detection value and the acquired second detection value, when the event recognition unit determines that the accelerator pedal and the brake pedal are simultaneously depressed, information of the simultaneous depression of the accelerator pedal and the brake pedal is included in a driving diagnosis result image, wherein the event recognition unit specifies a date and time when the simultaneous depression occurs and location information when the simultaneous depression occurs as an event; the scene extraction unit extracts data indicating a specific detection value satisfying an extraction condition from a detection value data group stored in a storage device; the key performance indicator acquisition unit calculates each key performance indicator based on the extracted data indicating the specific detection value; the score calculation unit calculates a safety level score, a comfort level score, and a driving operation score based on the calculated key performance indicators, a value obtained by dividing a total score of key performance indicators of the category "comfort" by the number of items of the category "comfort" is the comfort level score; the data generation unit generates data indicating the driving diagnosis result image using data about the event, the display unit displays the driving diagnosis result image, wherein the driving diagnosis result image has a safety comfort level display unit, a driving operation score display unit, and an event display unit, a safety level score and a comfort level score are displayed on the safety comfort level display unit, a driving operation score is displayed on the driving operation score display unit, and information of the event is displayed on the event display unit, wherein when a user's hand touches the event in the event display unit of the driving diagnosis result image on the display unit, the display unit displays a map image including map information of a place where the event occurred and its surrounding environment.

2. The driving diagnosis apparatus according to claim 1, further comprising a transceiving unit capable of receiving the first detection value and the second detection value from the vehicle via the Internet, and the transceiving unit is capable of transmitting the acquired first detection value and the acquired second detection value to the event recognition unit.

3. The driving diagnosis apparatus according to claim 1 or 2, further comprising a database unit storing information of whether the accelerator pedal and the brake pedal are simultaneously depressed determined by the event recognition unit, and the database unit is connected to the Internet.

Citation Information

Patent Citations

  • Memory system

    JP2021060721A

  • Vehicle driving skill diagnostic system and its components, driving skill diagnostic method

    JP3593502B2

  • Driving assistance device, driving assistance system, program, and control method for driving assistance device

    JP6648304B2

  • Telematics terminal and method for notifying emergency conditions using the same

    US20100085171A1