JP6264853B2 - Evaluation program, evaluation method, and evaluation apparatus - Google Patents

Evaluation program, evaluation method, and evaluation apparatus Download PDF

Info

Publication number
JP6264853B2
JP6264853B2 JP2013237280A JP2013237280A JP6264853B2 JP 6264853 B2 JP6264853 B2 JP 6264853B2 JP 2013237280 A JP2013237280 A JP 2013237280A JP 2013237280 A JP2013237280 A JP 2013237280A JP 6264853 B2 JP6264853 B2 JP 6264853B2
Authority
JP
Japan
Prior art keywords
performed
number
dangerous
evaluation
vehicle
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
JP2013237280A
Other languages
Japanese (ja)
Other versions
JP2015097051A (en
Inventor
清英 大宮
清英 大宮
Original Assignee
富士通株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社 filed Critical 富士通株式会社
Priority to JP2013237280A priority Critical patent/JP6264853B2/en
Publication of JP2015097051A publication Critical patent/JP2015097051A/en
Application granted granted Critical
Publication of JP6264853B2 publication Critical patent/JP6264853B2/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Description

  The present invention relates to an evaluation program, an evaluation method, and an evaluation apparatus.

  2. Description of the Related Art Conventionally, a technique is known in which driving attributes such as the number of times a driver suddenly brakes and average driving speed are aggregated, and the overall safety of the driving behavior of the driver is evaluated from the driving attributes (for example, Patent Document 1) reference).

JP-A-11-120488

  However, even in the same dangerous operation (including sudden braking operation and rapid acceleration operation), the degree of danger varies depending on the environment in which the dangerous operation is performed. For this reason, there is a possibility that appropriate evaluation cannot be performed even if the driver's evaluation is performed by counting the number of sudden brakings as the traveling attribute as in Patent Document 1.

  In one aspect, an object of the present invention is to provide an evaluation program, an evaluation method, and an evaluation apparatus capable of evaluating an appropriate driving technique.

In one aspect, the evaluation program is an evaluation program for calculating an evaluation value of driving technology from travel data of a vehicle including at least position information, and a dangerous operation of the vehicle is performed on the computer within a predetermined period from the travel data. The number of times that a dangerous operation has been performed in the past by specifying the position where the dangerous operation has been performed and referring to the storage unit that associates and stores the position and the number of times that the dangerous operation has been performed and the position where the dangerous operation has been performed The number of dangerous operations of the vehicle performed within the predetermined period in the dangerous zone specified based on the number of times and the number of dangerous operations of the vehicle performed within the predetermined period outside the dangerous zone are different parameters. using the calculated evaluation values of the driving technique, on the basis of the position specified in a particular processing, and updates the information stored in the storage unit, evaluated to execute processing program It is.

In one aspect, the evaluation method is an evaluation method for calculating an evaluation value of a driving technique from vehicle travel data including at least position information, and the computer performs a dangerous operation of the vehicle within a predetermined period from the travel data. The position where the dangerous operation was performed is identified, and the dangerous operation has been performed in the past with reference to the storage unit that stores the position and the number of times the dangerous operation has been performed in association with each other and the position where the dangerous operation has been performed. The number of times of the dangerous operation of the vehicle performed within the predetermined period in the dangerous zone specified based on the number of times, and the number of times of the dangerous operation of the vehicle performed within the predetermined period outside the dangerous zone are different parameters. wherein calculating an evaluation value of the driving skill by using as, on the basis of the position specified by the process specifying, it updates the information stored in the storage unit is an evaluation method for executing a process.

In one aspect, the evaluation device is an evaluation device that calculates an evaluation value of driving technology from vehicle travel data including at least position information, and stores the position and the number of times that a dangerous operation has been performed in association with each other in the past. A storage unit that performs the dangerous operation in the past with reference to the storage unit and the position where the dangerous operation was performed, the specifying unit that identifies the position where the dangerous operation of the vehicle was performed within a predetermined period from the travel data Of the dangerous operation of the vehicle performed within the predetermined period in the dangerous zone identified based on the number of times the vehicle has been performed, and the dangerous operation of the vehicle performed within the predetermined period outside the dangerous zone. A calculation unit that calculates an evaluation value of the driving technique using the number of times as a different parameter, and an update unit that updates information stored in the storage unit based on the position specified by the specifying unit. Yes.

  Appropriate driving skills can be evaluated.

It is a figure showing roughly the composition of the evaluation system concerning one embodiment. It is a hardware block diagram of a server. It is a functional block diagram of a vehicle-mounted apparatus and a server. It is a figure which shows an example of the data structure of evaluation index DB before correction | amendment. FIG. 5A is a diagram illustrating an example of the data structure of the sudden braking event DB, and FIG. 5B is a diagram illustrating an example of the data structure of the sudden braking frequent occurrence point DB. FIG. 6A is a diagram illustrating an example of a data structure of the sudden braking occurrence number DB, and FIG. 6B is a diagram illustrating an example of a data structure of the corrected evaluation index DB. It is a flowchart which shows the process which an exponent calculation part and a sudden brake information recording part perform. It is a flowchart which shows the specific process of step S16 of FIG. It is a flowchart which shows the process which the exponent correction | amendment part 26 performs.

  Hereinafter, an evaluation system according to an embodiment will be described in detail with reference to FIGS.

  FIG. 1 shows a schematic configuration of the evaluation system 100. The evaluation system 100 is a system that evaluates the driving technology of a driver who drives a vehicle (such as a truck), and includes a plurality of in-vehicle devices 10 and a server 20 as an evaluation device, as shown in FIG. The plurality of in-vehicle devices 10 and the server 20 are connected to a network 80 such as the Internet.

  The in-vehicle device 10 is a device called a digital tachograph (digital tachograph) mounted on a vehicle. The in-vehicle device 10 detects various information (running data) such as the position and speed of the vehicle at predetermined time intervals (for example, every second), and transmits the detected information to the server 20 via the network 80. Note that the in-vehicle device 10 is actually in a state capable of wireless communication with a base station connected to the network 80, and transmits information to the server 20 via the base station.

  Here, the in-vehicle device 10 includes a CPU, a RAM, a ROM, and the like. As illustrated in FIG. 3 which is a functional block diagram of the in-vehicle device 10 and the server 20, the CPU executes a program, whereby the speed information acquisition unit 12 is executed. The functions as the position information acquisition unit 14 and the speed / position information transmission unit 16 are realized.

  The speed information acquisition unit 12 acquires the speed of the vehicle at a predetermined time interval (for example, every 1 second) from the detection result of a speed sensor (not shown) installed in the vehicle.

  The position information acquisition unit 14 obtains position information of latitude and longitude where the vehicle is located from a GPS satellite received by a GPS (Global Positioning System) receiver (not shown) installed in the vehicle at predetermined time intervals (for example, 1 second interval).

  The speed / position information transmission unit 16 transmits the travel data to the server 20 (information) via the network 80 every time information (also referred to as “travel data”) is acquired by the speed information acquisition unit 12 and the position information acquisition unit 14. To the acquisition unit 21).

  Returning to FIG. 1, the server 20 calculates an evaluation index related to ecology and safety as an evaluation value of the driving technique based on the information (travel data) transmitted from the in-vehicle device 10. Further, the server 20 corrects and outputs an evaluation index related to ecology and safety based on the number and position of dangerous operations such as sudden braking and sudden acceleration (in this embodiment, sudden braking operation). .

  FIG. 2 shows the hardware configuration of the server 20. As shown in FIG. 2, the server 20 includes a CPU 90, a ROM 92, a RAM 94, a storage unit (HDD (Hard Disk Drive)) 96, a network interface 97, a display unit 93, an input unit 95, and a portable storage medium drive. 99, etc., and each component of the server 20 is connected to a bus 98. The display unit 93 includes a liquid crystal display or the like, and the input unit 95 includes a keyboard, a mouse, or the like. In the server 20, the CPU 90 executes a program (including an evaluation program) stored in the ROM 92 or the HDD 96 or a program (including an evaluation program) read from the portable storage medium 91 by the portable storage medium drive 99. Thus, the function of each unit in FIG. 3 is realized.

  In the server 20, when the CPU 90 executes the program, the information acquisition unit 21, the exponent calculation unit 22, the sudden brake information recording unit 23, the sudden brake information acquisition unit 24, the exponent correction unit 26, and the output unit 28 illustrated in FIG. As a function is realized. FIG. 3 shows an information DB (Database) 30 stored in the HDD 96 or the like, a pre-correction evaluation index DB 32, a sudden braking event DB 34, a sudden braking frequent occurrence point DB 36, a sudden braking occurrence number DB 38, and a correction. A post-evaluation index DB 40 is also illustrated.

  The information acquisition unit 21 receives speed information and position information (travel data) transmitted from the in-vehicle device 10 (speed / position information transmission unit 16), and stores the information in the information DB 30. Note that the information DB 30 stores position information (latitude, longitude) and speed information of each driver at each time (every second).

  The index calculation unit 22 uses, for example, the method disclosed in Japanese Patent No. 3944549 to calculate the speed from the speed information and the position information (information stored in the information DB 30) transmitted from the in-vehicle device 10 in a month. Once, each driver's evaluation index (eco and safety index) is calculated. The index calculation unit 22 stores the calculated result in the evaluation index DB 32 before correction. Here, the evaluation index DB 32 before correction has a data structure as shown in FIG. 4 as an example. That is, the pre-correction evaluation index DB 32 includes fields of “driver ID”, “target month”, and “evaluation index” as shown in FIG. The “driver ID” field stores the driver identifier, and the “target month” field stores the year and month when the evaluation index is calculated. In the “evaluation index” field, the evaluation index of each driver calculated by the index calculation unit 22 is stored. In the present embodiment, the smaller the value of the evaluation index, the more ecological and safe it is, and the higher the driving skill is.

  Returning to FIG. 3, the sudden brake information recording unit 23 specifies the position where the sudden brake operation is performed from the travel data stored in the information DB 30 and records the position in the sudden brake event DB 34. The sudden brake information recording unit 23 records, in the sudden brake event DB 34, which driver has applied the sudden brake at which point based on the speed information recorded every second. The sudden brake information recording unit 23 determines that sudden braking has occurred when the deceleration width is equal to or greater than a predetermined value (for example, 10 km / h or more per second).

  FIG. 5A shows an example of the data structure of the sudden brake event DB 34. As shown in FIG. 5A, the sudden brake event DB 34 includes “driver ID”, “latitude”, “longitude”, “date / time”, “deceleration width (km / h)”, “speed (km / h)”. ”Field. The “driver ID” field stores the driver identifier, and the “latitude” and “longitude” fields store information on the position where it is determined that a sudden braking operation has occurred. In the “date and time” field, information on the date and time at which it was determined that the sudden braking operation was performed is stored. Further, the value of the deceleration width in one second is stored in the “deceleration width (km / h)” field, and the speed value before deceleration is stored in the “speed (km / h)” field. .

  In addition, whenever the sudden brake information recording unit 23 determines that there is a sudden brake operation, the sudden brake frequent occurrence point DB 36 updates (counts up) the number of sudden brakes in the region where the sudden brake operation is performed. FIG. 5B shows an example of the data structure of the sudden braking frequent occurrence point DB 36. As shown in FIG. 5B, the sudden braking frequent occurrence point DB 36 stores “No”, “start latitude”, “start longitude”, “end latitude”, “end longitude”, “number of sudden brakes”, “rank”. Each field.

  In the “No” field, the serial number of the point is stored. Further, the “start latitude” and “start longitude” fields store the position information of the start point (corner) of the rectangular area, and the “end latitude” and “end longitude” fields store the start point ( The position information of the diagonal (end point) of the corner is stored. In addition, the number of times of sudden braking in the area is stored in the “number of sudden braking” field, and the ranking of the number of sudden brakings (ranked in descending order) is stored in the “order” field. Is done. Each time the sudden brake information recording unit 23 determines that there is a sudden brake operation, the sudden brake information recording unit 23 counts up the number of sudden brakes in the region corresponding to the position where the sudden brake operation is performed. The sudden brake information recording unit 23 also updates the rank field when the rank is changed by the count-up.

  Further, every time the sudden brake information recording unit 23 determines that there is a sudden brake operation, the sudden brake occurrence number DB 38 is also updated. FIG. 6A shows an example of the data structure of the sudden braking occurrence number DB 38. The sudden brake occurrence frequency DB 38 has fields of “driver ID”, “target month”, “rapid brake occurrence frequency (multiple occurrence points)”, and “sudden brake occurrence frequency (outside frequent occurrence points)”. In the field of “the number of sudden braking occurrences (multiple occurrence points)”, an area included in the upper predetermined rank (for example, 100th place) of the frequent braking point DB 36 or the number of sudden braking occurrences is a predetermined number (for example, 30 or more). Stores the number of times of sudden braking operation (dangerous operation) in the area (a sudden braking frequent point as a dangerous zone). Further, the number of times of sudden braking operation (dangerous operation) in an area other than the sudden braking frequent point is stored in the field of “number of sudden braking occurrences (outside frequent frequent braking points)”. It should be noted that the number of times that the sudden braking operation is executed at the sudden braking frequent occurrence point corresponds to a first parameter used in correction of an evaluation index described later. In addition, the number of times that the sudden braking operation is performed outside the sudden braking frequent occurrence point corresponds to a second parameter used in correction of an evaluation index, which will be described later.

  The sudden braking frequent occurrence point DB 36 stores the average of the number of sudden braking operations performed by all drivers at the number of sudden braking occurrences (multiple occurrence points), and all drivers perform sudden braking operations other than the number of sudden braking occurrences (multiple occurrence points). Stores the average number of visits.

  Returning to FIG. 3, the sudden brake information acquisition unit 24 acquires the value of the number of sudden braking occurrences in the target month (multiple points, out of frequent points) of the driver to be processed. Further, the sudden brake information acquisition unit 24 transmits the acquired value to the exponent correction unit 26.

  The index correction unit 26 corrects the pre-correction evaluation index in the target month of the driver to be processed, using the value of the number of sudden braking occurrences (multiple points, outside the frequent points) acquired from the sudden brake information acquisition unit 24. The index correction unit 26 stores the corrected evaluation index in the corrected evaluation index DB 40. Here, FIG. 6B shows an example of the data structure of the corrected evaluation index DB 40. As shown in FIG. 6B, the post-correction evaluation index DB 40 has fields of “driver ID”, “target month”, and “post-correction evaluation index”. In the “corrected evaluation index” field, the value of the evaluation index corrected by the index correction unit 26 is stored.

  The output unit 28 acquires the corrected evaluation index from the corrected evaluation index DB 40, displays it on the display unit 93, and outputs it.

  Next, the processing of the server 20 will be described in detail along the flowcharts of FIGS.

  First, processing executed by the index calculation unit 22 and the sudden brake information recording unit 23 will be described with reference to FIGS. 7 and 8 are processes performed once a month, for example, at the end of the month.

  In the process of FIG. 7, first, in step S <b> 10, the exponent calculation unit 22 specifies a process target driver and a target month. For example, it is assumed that the exponent calculation unit 22 specifies the driver ID “300001” and the target month “2013/05”.

  Next, in step S <b> 12, the index calculation unit 22 acquires travel data of the target month of the processing target driver from the information DB 30. Next, in step S14, the index calculation unit 22 calculates an evaluation index for the identified driver and target month. Specifically, as described above, the index calculation unit 22 uses, for example, a method disclosed in Japanese Patent No. 3944549 for one month transmitted from the in-vehicle device 10 (May 2013). Min)), the evaluation index of the driver to be processed is calculated. The index calculation unit 22 stores the calculated evaluation index in the evaluation index DB 32 before correction. In the pre-correction evaluation index DB 32 of FIG. 4, it is assumed that “20” is stored as the evaluation index of the driver ID “30,0001” and the target month “2013/05”.

  Next, in step S16, the sudden brake information recording unit 23 executes a sudden brake recording process subroutine. In step S16, specifically, processing according to the flowchart of FIG. 8 is executed.

  In the process of FIG. 8, first, in step S30, the sudden brake information recording unit 23 extracts, for example, travel data along a time series, and the deceleration width from the travel data immediately before (1 second before) is 10 km / h. It is determined whether or not there has been a sudden braking operation by determining whether or not it has exceeded. If the determination is negative, the process of step S30 is repeated. If the determination is positive, the process proceeds to step S32.

  When the process proceeds to step S32, the sudden brake information recording unit 23 stores the sudden brake operation information (rapid brake event) in the sudden brake event DB 34. In this case, the sudden brake information recording unit 23 stores the driver ID, latitude, longitude, date and time, deceleration width, and speed (speed immediately before the sudden brake) in the sudden brake event DB 34.

  Next, in step S34, the sudden brake information recording unit 23 updates the sudden brake frequent occurrence point DB 36. In this case, the sudden brake information recording unit 23 increments the number of sudden brakes in the region corresponding to the latitude and longitude stored in the sudden brake event DB 34 by one. Further, when the rank changes due to the sudden braking update, the rank field is also updated.

  Next, in step S36, the sudden brake information recording unit 23 updates the sudden brake occurrence number DB 38. In this case, the sudden brake information recording unit 23 records that the number of sudden brakes updated in Step S34 in the sudden brake frequent occurrence point DB 36 is within a predetermined rank (for example, within 100th place) or the number of sudden brakes is equal to or greater than a predetermined number ( For example, it is determined whether or not 30 times or more. When this determination is affirmed, the sudden brake information recording unit 23 increments the value of the corresponding sudden brake occurrence number (multiple occurrence point) field in the sudden brake occurrence number DB 38 by one. On the other hand, if the determination is negative, the value of the corresponding number of sudden braking occurrences (outside the frequent occurrence point) field in the sudden braking occurrence number DB 38 is incremented by one.

  Next, in step S38, the sudden brake information recording unit 23 determines whether or not traveling data remains. If the determination here is affirmed, the process returns to step S30 and the above-described processing is repeated. However, if the determination is negative, all the processes in FIG. 8 are terminated, and the process proceeds to step S18 in FIG. .

  Returning to FIG. 7, when the process proceeds to step S <b> 18, the exponent calculation unit 22 determines whether there is an unprocessed driver or target month. If the determination here is affirmed, the process returns to step S10. If the determination is negative, all the processes in FIG. 7 are terminated.

  7 and FIG. 8, the evaluation index of each driver in the target month can be obtained, and the sudden braking frequent occurrence point DB 36 and the sudden braking occurrence number DB 38 can be updated with information on sudden braking.

  Next, the process of correcting the evaluation index calculated in the process of step S14 of FIG. 7 will be described along the flowchart of FIG.

  In the process of FIG. 9, first, in step S50, the exponent correction unit 26 specifies a process target driver and a target month. For example, it is assumed that the exponent correction unit 26 specifies a driver having a driver ID = “30,0001” as a processing target driver and specifies “2013/05” as a target month.

  Next, in step S <b> 52, under the instruction of the exponent correction unit 26, the sudden brake information acquisition unit 24 acquires the number of sudden brake occurrences in the target month of the processing target driver from the sudden brake occurrence number DB 38 and transmits it to the exponent correction unit 26. To do. For example, the sudden brake information acquisition unit 24 sets “the number of sudden braking occurrences (multiple occurrence points)” = “2” and “the number of sudden braking occurrences (outside frequent occurrence points)” in the first record in FIG. “8” is acquired and transmitted to the exponent correction unit 26. The exponent correction unit 26 acquires the number of sudden braking occurrences (frequent occurrence points) and sudden braking occurrences (outside the frequent occurrence points) that have been transmitted.

  Next, in step S54, the index correction unit 26 acquires an evaluation index corresponding to the target month of the processing target driver from the evaluation index DB 32 before correction. For example, the index correction unit 26 acquires “evaluation index” = “20” of the first record in the evaluation index DB 32 before correction in FIG.

In step S56, the index correction unit 26 corrects the evaluation index. Here, as an example, the index correction unit 26 sets the evaluation index before correction to x, the number of sudden braking occurrences of the driver to be processed at the frequent occurrence point y1, and the average number of sudden braking occurrences of all the drivers at the frequent occurrence point z1. , Y2 is the number of sudden braking occurrences of the driver to be processed outside the frequent occurrence point, z2 is the average number of sudden braking occurrences of all drivers outside the frequent occurrence point, and the evaluation index P after correction based on the following equation (1) Ask for.
P = (0.7 × x) + (0.2 × x) × y1 / z1
+ (0.1 × x) × y2 / z2 (1)

For example, as described above, when the evaluation index is “20”, the number of sudden braking occurrences (frequent occurrence points) is “2”, and the number of sudden braking occurrences (out of frequent occurrence points) is “8”, the above equation (1) ,
P = (0.7 × 20) + (0.2 × 20) × 2 / 3.83
+ (0.1 × 20) × 8 / 21.5≈16.83
It becomes.

  The index correction unit 26 stores the corrected index in the corrected evaluation index DB 40. In the present embodiment, the index correction unit 26 executes correction of the evaluation index using the above equation (1), so that the number of sudden braking occurrences (first parameter) at the sudden braking frequent occurrence point and the frequent frequent braking The evaluation index is corrected (calculated) using the number of sudden braking occurrences (second parameter) outside the point.

  Next, in step S58, the exponent correction unit 26 determines whether or not an unprocessed driver and target month remain. If the determination is affirmed, the process returns to step S50, and the processes of steps S50 to S56 are executed for the unprocessed driver and the target month. On the other hand, if the determination in step S58 is negative, the process proceeds to step S60.

  In step S <b> 60, the output unit 28 outputs the evaluation index by displaying it on the display unit 93. Here, the output unit 28 outputs the transition of the individual evaluation index according to the instruction of the user of the server 20 (server administrator or the like), or outputs the evaluation index at different times of the individual in a comparable state. Can be. Further, the output unit 28 can output the evaluation indexes of different drivers in a comparable state.

  As described above, after the process of step S60 is completed, the entire process of FIG. 9 is terminated.

  Here, the evaluation index of the driver up to the sixth person (driver ID = 300001 to 300006) shown in FIG. 4 is obtained by using the number of sudden braking occurrences (multiple points, outside the frequent points) shown in FIG. The correction is made as shown in FIG. The corrected evaluation index can be said to be an evaluation index reflecting the number of sudden braking occurrences of each driver at a sudden braking frequent occurrence point and the number of sudden braking occurrences of each driver outside a sudden braking frequent occurrence point. For example, even if the total number of sudden braking is the same, the evaluation index is corrected (larger) as the number of sudden braking occurrences at the frequent occurrence point of sudden braking increases. In other words, the evaluation index indicates that the more the number of sudden braking operations at a sudden braking frequent point, the more dangerous and the driving technique is low.

  As can be seen from the above description, in the present embodiment, the index calculation unit 22, the sudden brake information recording unit 23, and the index correction unit 26 realize a function as a calculation unit that calculates an evaluation value of the driving skill of the driver. ing.

  As described above in detail, according to this embodiment, the position where the dangerous operation of the vehicle is performed is identified from the travel data (S30, S32), and the sudden braking frequent occurrence point is stored in association with the position information. Using the brake frequent occurrence point DB 36 and the position where the sudden brake operation is performed, the number of sudden brake operations performed at the sudden brake frequent occurrence point and the number of sudden brake operations performed outside the sudden braking frequent point are used as different parameters. An evaluation value of the driving technique is calculated (S50 to S56). Thus, considering the point where the sudden braking operation was performed, that is, considering the risk of the point where the sudden braking operation was performed, the evaluation index (evaluation value of driving technology) for ecology and safety was appropriately set. It can be corrected.

  Further, in the present embodiment, the index correction unit 26 indicates that the sudden braking operation performed at the sudden braking frequent point is a driving technique lower than the sudden braking operation performed at other than the sudden braking frequent point. Use parameters. As a result, a driver who frequently performs a sudden braking operation at a sudden braking frequent occurrence point can appropriately correct the evaluation index under the assumption that there is a high possibility of unsafe eyes (unsafe).

  In the above-described embodiment, the case where it is determined based on actual traveling data whether or not there is a sudden braking frequent occurrence point has been described. However, the present invention is not limited to this. That is, when a storage unit that stores in advance the position information of sudden braking points can be prepared, the storage unit may be used to determine whether or not there is a sudden braking point.

  In addition, the coefficient (0.7, 0.2, 0.1) of each term of the above equation (1) is an example. That is, the administrator of the server 20 may change the ratio of each item as appropriate. The above formula (1) is an example. Therefore, any other formula can be used as long as it can calculate the evaluation index after correction using the number of sudden braking occurrences at the sudden braking frequent occurrence point, the number of sudden braking occurrences outside the sudden braking frequent occurrence point, and the evaluation index before correction. It is good also as adopting.

  In the above embodiment, a case has been described in which the evaluation index is corrected using both the number of sudden braking occurrences at a sudden braking frequent occurrence point and the number of sudden braking occurrences outside a sudden braking frequent occurrence point. However, the present invention is not limited to this. Absent. For example, the evaluation index may be corrected using either one of the number of sudden braking occurrences at the sudden braking frequent occurrence point and the number of sudden braking occurrences outside the sudden braking frequent occurrence point.

  In the above-described embodiment, the case where the dangerous operation of the vehicle is the sudden brake operation has been described. In this case, the danger zone may be a sudden acceleration frequent occurrence point. Further, the dangerous operation of the vehicle may be a sudden brake operation and a sudden acceleration operation.

  In the above-described embodiment, the case where a sudden braking frequent occurrence point is adopted as the danger zone and the sudden braking frequent occurrence point is determined based on the travel data has been described, but the present invention is not limited to this. For example, even when a sudden braking frequent occurrence point is adopted as the danger zone, the sudden braking frequent occurrence point may be determined in advance on the basis of a result of a survey performed in advance. Further, the dangerous zone is not limited to a point where sudden braking frequently occurs, but an intersection with a poor visibility, a school road, a point where accidents frequently occur, and the like may be determined in advance.

  The above processing functions can be realized by a computer. In that case, a program describing the processing contents of the functions that the processing apparatus should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium (except for a carrier wave).

  When the program is distributed, for example, it is sold in the form of a portable recording medium such as a DVD (Digital Versatile Disc) or a CD-ROM (Compact Disc Read Only Memory) on which the program is recorded. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. Further, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

  The above-described embodiment is an example of a preferred embodiment of the present invention. However, the present invention is not limited to this, and various modifications can be made without departing from the scope of the present invention.

In addition, the following additional remarks are disclosed regarding description of the above embodiment.
(Supplementary note 1) An evaluation program for calculating an evaluation value of a driving technique from travel data of a vehicle including at least position information,
On the computer,
Identify the location where the dangerous operation of the vehicle was performed from the travel data,
The storage unit that stores the dangerous zone in association with the position information and the position where the dangerous operation is performed are referred to, the number of the dangerous operations performed in the dangerous zone, and the dangerous that is performed outside the dangerous zone. Calculating an evaluation value of the driving technique using the number of operations as a different parameter;
An evaluation program characterized by causing processing to be executed.
(Supplementary Note 2) The parameter is used to indicate that the dangerous operation of the vehicle performed in the dangerous zone is a lower driving technique than the dangerous operation of the vehicle performed outside the dangerous zone. The evaluation program according to appendix 1, characterized by:
(Appendix 3) An evaluation method for calculating an evaluation value of a driving technique from travel data of a vehicle including at least position information,
Computer
Identify the location where the dangerous operation of the vehicle was performed from the travel data,
Referring to the storage unit that stores the dangerous zone in association with the position information and the position where the dangerous operation is performed, the number of the dangerous operations performed in the dangerous zone, and the performed in other than the dangerous zone Calculating an evaluation value of the driving technique using the number of dangerous operations as a different parameter;
An evaluation method characterized by executing processing.
(Supplementary Note 4) The parameter is used to indicate that the dangerous operation of the vehicle performed in the dangerous zone is a lower driving skill than the dangerous operation of the vehicle performed outside the dangerous zone. The evaluation method according to supplementary note 3, characterized by:
(Supplementary Note 5) An evaluation device that calculates an evaluation value of a driving technique from travel data of a vehicle including at least position information,
A storage unit for storing the danger zone in association with the position information;
A specifying unit for specifying a position where a dangerous operation of the vehicle is performed from the travel data;
With reference to the storage unit and the position where the dangerous operation was performed, the number of dangerous operations performed in the dangerous zone and the number of dangerous operations performed outside the dangerous zone are used as different parameters. A calculation unit for calculating an evaluation value of the driving technique;
An evaluation apparatus comprising:
(Appendix 6) The calculation unit is configured to indicate that the dangerous operation of the vehicle performed in the dangerous zone is a lower driving technique than the dangerous operation of the vehicle performed outside the dangerous zone. The evaluation apparatus according to appendix 5, wherein a parameter is used.

20 servers (evaluation equipment)
36 Sudden braking frequent occurrence point DB (memory part)
23 Sudden brake information recording part (part of calculation part)
22 Index calculation part (part of calculation part)
26 Index correction part (part of the calculation part)
28 Output section

Claims (4)

  1. An evaluation program for calculating an evaluation value of driving technology from vehicle travel data including at least position information,
    On the computer,
    Identify the location where the dangerous operation of the vehicle was performed within a predetermined period from the travel data,
    A storage unit that stores a position and the number of times that a dangerous operation has been performed in the past in association with each other and a dangerous zone that is identified based on the number of times that the dangerous operation has been performed in the past with reference to the position where the dangerous operation has been performed in the a number of dangerous operation of the vehicle performed within a predetermined time period, the evaluation value of the driving skill by using the number of unsafe operation of the vehicle performed within the predetermined period than the danger zone as a different parameter is calculated,
    Updating the information stored in the storage unit based on the position specified in the specifying process;
    An evaluation program characterized by causing processing to be executed.
  2.   The parameter is used to indicate that the dangerous operation performed in the dangerous zone is a lower driving skill than the dangerous operation of the vehicle performed outside the dangerous zone. Item 2. The evaluation program according to Item 1.
  3. An evaluation method for calculating an evaluation value of driving technology from travel data of a vehicle including at least position information,
    Computer
    Identify the location where the dangerous operation of the vehicle was performed within a predetermined period from the travel data,
    A risk that is identified based on the number of times that a dangerous operation has been performed in the past with reference to a storage unit that stores the position and the number of times that the dangerous operation has been performed in association with each other and the position where the dangerous operation has been performed and the number of dangerous operation of the vehicle performed within the predetermined period zone, the evaluation of the driving skill by using the different number of unsafe operation parameters of the vehicle that is performed within the predetermined period than the danger zone to calculate the value,
    Updating the information stored in the storage unit based on the position specified in the specifying process;
    An evaluation method characterized by executing processing.
  4. An evaluation device for calculating an evaluation value of driving technology from travel data of a vehicle including at least position information,
    A storage unit that associates and stores a position and the number of times a dangerous operation has been performed in the past ;
    A specifying unit for specifying a position where a dangerous operation of the vehicle is performed within a predetermined period from the travel data;
    The number of dangerous operations of the vehicle performed within the predetermined period in a dangerous zone identified based on the number of dangerous operations performed in the past with reference to the storage unit and the position where the dangerous operation was performed A calculation unit that calculates an evaluation value of the driving technique using the number of dangerous operations of the vehicle performed outside the danger zone within the predetermined period as a different parameter;
    An update unit that updates information stored in the storage unit based on the position specified by the specifying unit;
    An evaluation apparatus comprising:
JP2013237280A 2013-11-15 2013-11-15 Evaluation program, evaluation method, and evaluation apparatus Active JP6264853B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2013237280A JP6264853B2 (en) 2013-11-15 2013-11-15 Evaluation program, evaluation method, and evaluation apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2013237280A JP6264853B2 (en) 2013-11-15 2013-11-15 Evaluation program, evaluation method, and evaluation apparatus

Publications (2)

Publication Number Publication Date
JP2015097051A JP2015097051A (en) 2015-05-21
JP6264853B2 true JP6264853B2 (en) 2018-01-24

Family

ID=53374309

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2013237280A Active JP6264853B2 (en) 2013-11-15 2013-11-15 Evaluation program, evaluation method, and evaluation apparatus

Country Status (1)

Country Link
JP (1) JP6264853B2 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105427405A (en) * 2015-11-17 2016-03-23 北京奇虎科技有限公司 Vehicle traveling information restoring method and system and vehicle traveling information restoring method of server
JP6086515B1 (en) * 2016-04-11 2017-03-01 株式会社オファサポート Driving skill evaluation device, server device, driving skill evaluation system, program, and driving skill evaluation method

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4367431B2 (en) * 2005-10-26 2009-11-18 トヨタ自動車株式会社 Vehicle driving support system
JP5057167B2 (en) * 2008-10-30 2012-10-24 アイシン・エィ・ダブリュ株式会社 Safe driving evaluation system and safe driving evaluation program
JP4849148B2 (en) * 2009-03-30 2012-01-11 アイシン・エィ・ダブリュ株式会社 Vehicle operation diagnosis device, vehicle operation diagnosis method, and computer program

Also Published As

Publication number Publication date
JP2015097051A (en) 2015-05-21

Similar Documents

Publication Publication Date Title
US9672569B2 (en) System and method for actual and smartphone telematics data based processing
US8036822B2 (en) Travel time determination
CN101676689B (en) Driving evaluation system and driving evaluation method
US20130164715A1 (en) Using social networking to improve driver performance based on industry sharing of driver performance data
US20170076594A1 (en) Traffic flow rates
EP1507245A1 (en) Vehicle operation information management evaluation system
JP6006641B2 (en) Traffic signal map creation and detection
US8855912B2 (en) Travel route evaluation system and travel route evaluation program
US8248223B2 (en) Speed reporting for providing conditional driver treatment
US8855915B2 (en) Navigation system, navigation apparatus, method and server
US20150046197A1 (en) Systems and methods for providing driver feedback using a handheld mobile device
US9108640B2 (en) Systems and methods for monitoring and reporting road quality
US8698649B2 (en) Data mining in a digital map database to identify decreasing radius of curvature along roads and enabling precautionary actions in a vehicle
US20130046510A1 (en) Systems and Methods for Controlling the Collection of Vehicle Use Data Using a Mobile Device
JP5763074B2 (en) Computer-implemented methods, computer program products, and devices that ensure user privacy
ES2629201T3 (en) Fuel consumption calculations and warnings
US8930231B2 (en) Methods using a mobile device to provide data for insurance premiums to a remote computer
EP2387698A1 (en) Method for creating speed profiles for digital maps
EP2823329B1 (en) Point of interest database maintenance system
EP2182501B1 (en) Safe driving evaluation system and safe driving evaluation program
US9135759B2 (en) Driver measurement and incentive system for improving fuel-efficiency
US20130297097A1 (en) Safe driving monitoring system
US20130346396A1 (en) Automatically updating a query
US20130046526A1 (en) Selecting a Vehicle to Optimize Fuel Efficiency for a Given Route and a Given Driver
US20090213002A1 (en) Context sensitive mobile device utilization tracking

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20160804

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20170419

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20170425

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20170621

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20171128

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20171211

R150 Certificate of patent or registration of utility model

Ref document number: 6264853

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R150