JP5023026B2 - Eco-drive support device, server and method - Google Patents

Description

  The present invention relates to a method and apparatus for providing eco-driving support information to a driver (driver).

  There is an increasing expectation for a probe car system that uses an automobile as a sensor and collects information. In the probe car system, vehicle information such as vehicle speed, wiper operating status, and airbag operating status is collected from the vehicle and transmitted to the center, and the information collected on the center side is processed into various information for use.

  As a conventional technique related to a probe car system, there is a method of generating and providing traffic information, traffic length, and signal waiting information from vehicle information. For example, as disclosed in Patent Document 1 (Japanese Patent Application Laid-Open No. 2003-281684), traffic information, traffic length, and signal waiting information are provided from traffic information data obtained from a traveling vehicle such as a probe car.

  Also, as a conventional technology related to other probe car systems, traffic flow control and warning to the driver are performed by collecting the discharge concentration of environmentally hazardous substances from the vehicle and identifying the place where the environmental load is excessive. There is a way. For example, as disclosed in Patent Document 2 (Japanese Patent Application Laid-Open No. 2002-203080), it is possible to accurately detect the actual amount of environmental load discharged from the traveling vehicle, and the amount of environmental load discharged in real time can be detected. Can be reflected in traffic control.

JP 2003-281684 A JP 2002-203080 A

  In order to prevent global warming, reduction of carbon dioxide emissions from automobiles is required. It is recommended to practice eco-driving (environmentally friendly vehicle usage) for the purpose of reducing carbon dioxide emissions, that is, fuel consumption. The amount of fuel consumed depends on the performance of the automobile but also on the driving environment. Fuel consumption varies depending on where you are driving, whether it is a general road, a high speed, or an intersection. Therefore, eco-driving can be effectively supported by sharing information on places where fuel is easily consumed in the probe car system. Fuel consumption also depends on the driving skill. Even if you drive the same car on the same road, the fuel consumption varies depending on the driver you drive. Therefore, in order to effectively support eco-driving, it is necessary to provide information that considers driving skills (driving characteristics).

  In eco-driving, the driving method must be suitable for driving conditions such as “start” and “acceleration”. Therefore, in order to support eco-driving, it is necessary to provide information associated with the driving state. On the other hand, Patent Document 1 and Patent Document 2 provide the same information to all drivers as traffic jam information and traffic control information, and the viewpoint of how much the driver's driving technology is considered. Not.

  An object of the present invention is to provide an eco-drive support apparatus and method that provide eco-drive support information corresponding to a driver's driving technique (driving characteristics).

  The eco-drive support device and method according to the present invention acquire vehicle information from a vehicle, and the driver's driving from the acquired vehicle information consumes excessive fuel in response to an excessive factor that the vehicle consumes excessive fuel. The driver determines the over-consumption point where the vehicle is likely to over consume fuel from the diagnosis result by the driver, determines the driver's driving characteristics from the diagnosis result, and notifies the driver based on the driving characteristics The attention point to be selected is selected from the excessive consumption points, and the selected attention point is notified to the driver.

  Other desirable aspects of the present invention include the number of times the vehicle has over consumed fuel, the rate at which the vehicle has over consumed fuel, the sum of vehicle over consumption, and the vehicle At least one of the variances of the excess consumption is calculated as the driving characteristic value, and the driving characteristic of the driver is determined based on the driving characteristic value.

  According to still another desirable aspect of the present invention, the driving characteristic of the driver is determined by using at least one of a comparison between the driving characteristic value and a predetermined threshold and a time series increase / decrease of the driving characteristic value.

  Still another desirable aspect of the present invention notifies a driver of a point of caution using at least one of a display and a speaker.

  Still another desirable aspect of the present invention notifies the driver of the caution point to be notified before the vehicle reaches the caution point to be notified on the travel route of the vehicle.

  According to the present invention, it is possible to provide eco-driving support information corresponding to a driver's driving technique (driving characteristics).

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a system configuration diagram according to the first embodiment. The vehicle 101 is equipped with an eco-drive support device 102, a communication device 109, a GPS 110, an ECU 111, an in-vehicle network 115, a display 112, a speaker 113, and a navigation device 114. The ECU 111 is an electric control unit (electronic control device), and is a device that controls the traveling of the vehicle 101.

  The eco-drive support device 102 and the ECU 111 are connected by an in-vehicle network 115, and the eco-drive support device 102 has an ECU 111 such as a traveling speed (hereinafter, vehicle speed) of the vehicle 101 and a fuel injection amount via the in-vehicle network 115. Information used for control is acquired as vehicle information. The eco-drive support device 102 also acquires position information and time information as vehicle information from the directly connected GPS 110. In the present embodiment, the ECU 111 and the GPS 110 will be described as examples of vehicle information acquisition destinations, but various sensors and the like are connected as necessary via the in-vehicle network or directly as vehicle information acquisition destinations. The eco-drive support device 102 is connected to an output device such as the display 112 and the speaker 113 and the navigation device 114 through a dedicated line.

  The eco-drive support device 102 is connected to the communication device 109 and performs data transmission / reception with the center server (eco-drive support server) 121 via the communication network 120. The communication device 109 may be a communication module built in the vehicle, or a mobile phone connected externally. The center server 121 is connected to the weather management server 131 via the Internet 130. The weather management server 131 is a server that responds to a query (location, time, weather, etc.) at a specified location / time in response to an inquiry using the location / time as a key.

  Each process described below is realized by executing a program by the CPU included in the eco-drive support device 102. The eco-drive support device 102 executes processes of the vehicle information collection unit 103, the driving diagnosis unit 104, the notification unit 106, and the data transmission / reception unit 108. The eco-drive support device 102 includes a diagnosis result management unit 105 and a caution point management unit 107 that store data used for executing these processes.

  The vehicle information collection unit 103 obtains information such as the current position and current time from the GPS 110 and the vehicle speed from the ECU 111 via the in-vehicle network 115 at regular intervals such as one second intervals, and sends them to the driving diagnosis unit 104 and the notification unit 106. Pass the acquired vehicle information. The operation diagnosis unit 104 calculates a factor that consumes excessive fuel (excess factor) and an amount of excessive fuel consumed (excess consumption), adds information on date and time, and a diagnosis result as a diagnosis result. Accumulate in the management unit 105. For example, excess factors are operating conditions such as “start”, “acceleration”, “cruising”, “deceleration”, “idling”, and excessive consumption is “10 cc”. Here, even when the excessive consumption is “0 cc”, the diagnosis result is accumulated in the diagnosis result management unit 105. Types of driving states such as “start”, “acceleration”, “cruising”, “deceleration”, “idling” are defined in advance and stored in the eco-drive support device 102, and the same definition is stored in the center server 121. Also remember.

  The data transmission / reception unit 108 communicates with the data transmission / reception unit 122 of the center server 121 to perform data transmission / reception. In the data transmission, the diagnosis result data stored in the diagnosis result management unit 105 is transmitted with the user ID added. The user ID may be preset in the eco-drive support terminal 102 or may be input by the user. In the data reception, the user ID is transmitted, the attention point data of the attention point management unit 126 corresponding to the user ID is received, and the received attention point data is stored in the attention point management unit 107. Data transmission / reception may be performed at a timing when the user explicitly connects communication, or may be performed by automatic connection periodically. The notification unit 106 determines the content and timing for notifying information, and notifies the driver using the display 112 and the speaker 113.

  Each process described below is realized by the center server 121 executing a program. The center server 121 executes each process of the data transmission / reception unit 122, the driving characteristic determination unit 124, the excessive consumption point specifying unit 125, and the attention point generation unit 127. The center server 121 includes a history management unit 123 and a caution point management unit 126 that store data used for executing these processes.

  The data transmission / reception unit 122 receives the diagnosis result data from the data transmission / reception unit 108 of the eco-drive support device 102, and obtains the weather by inquiring the weather management server 131 using the occurrence date / time 301 and the occurrence location 302 of the diagnosis result as keys. The acquired weather is stored in the history management unit 123 in association with the received diagnosis result. Further, based on a request from the data transmission / reception unit 108 of the eco-drive diagnosis device 102, the attention point management unit 126 is searched using the designated user ID as a key, and the search result is returned to the eco-drive diagnosis device 102.

  The excessive consumption point specifying unit 125 specifies a point where many drivers are likely to excessively consume fuel, and the driving characteristic determination unit 124 determines the driving characteristic for each driver. Then, the caution point generation unit 127 generates caution points for excessive consumption in consideration of driving characteristics for each driver, and accumulates the results in the caution point management unit 126.

  FIG. 2 shows a hardware configuration diagram of the eco-drive support device 102. The eco-drive support device 102 includes a CPU (processor) 201, a RAM 202, a ROM 203, an HDD (hard disk drive) 204 as an external storage device, an external communication interface 205 that transmits and receives data to and from the communication device 109, and an ECU 111 and data via an in-vehicle network 115. The in-vehicle communication interface 206 for transmitting and receiving, the GPS 110, the display 112, the speaker 113, and the navigation terminal 114 are configured by a dedicated communication interface 207 for transmitting and receiving data. The external storage device is not limited to an HDD, and an optical disk (DVD or the like) device, a flash memory device, or the like may be used. The eco-drive support device 102 may be turned on / off by a manual switch as necessary. However, the power is turned on (connected to the storage battery) when the vehicle engine is started, and the power is turned on when the engine is stopped. It is desirable that the operation of the manual switch for turning the power ON / OFF is disabled while the engine is operating.

  The programs of the vehicle information collection unit 103, the driving diagnosis unit 105, the notification unit 106, and the data transmission / reception unit 108 shown in FIG. 1 and the data of the diagnosis result management unit 105 and the attention point management unit 107 are stored in the HDD 204. Yes. These programs and data are loaded from the HDD 204 to the RAM 202 when the eco-drive support device 102 is turned on, and each program is executed. The ROM 203 stores a loader program for loading programs and data into the RAM 202. Although the power is turned off when the engine is stopped, the time for storing the data in the RAM 202 in the HDD 204 is short, so a transitional time for turning off the power is sufficient, but when the amount of data to be stored is large, etc. What is necessary is just to delay power OFF (disconnection from the storage battery of a vehicle). Further, when collecting data including the engine start status, it is only necessary to detect the engine start preparation stage (for example, detection of engine key insertion), turn on the power, and start the execution of the program. In this case, if the program is stored in the ROM 203 and the CPU 201 executes the program in the ROM 203, the time required for loading the program can be shortened, and the power consumption of the storage battery can be reduced according to the shortening.

  FIG. 3 shows a table configuration of the diagnosis result management unit 105. This table is for accumulating the processing results of the driving diagnosis unit 104, and includes an occurrence date and time 301, an occurrence location 302, an excess factor 303, and an excess consumption amount 304. The occurrence date / time 301 and the occurrence location 302 indicate the date / time and location where excessive fuel consumption occurred. The excess factor 303 and the excess consumption amount 304 indicate the cause of excess consumption and the amount of fuel excessively consumed at that time. Specific examples of excess factors include driving conditions such as “start”, “acceleration”, “cruising”, “deceleration”, and “idling”. In the example of the figure, “5 cc” of fuel is excessively consumed by “start”.

  FIG. 4 shows a table configuration of the history management unit 123 of the center server 121. This table is for accumulating diagnosis results uploaded from the eco-drive support device 102, and includes a user ID 401, an occurrence date and time 402, an occurrence location 403, an excess factor 404, an excess consumption 405, and a weather 406. . A user ID 401 indicates a user who has consumed excessive fuel. Occurrence date / time 402, occurrence location 403, excess factor (operating state) 404, and excess consumption 405 correspond to occurrence date / time 301, occurrence location 302, excess factor 303, and excess consumption 304 in FIG. The weather 406 is information acquired from the weather management server 131 and indicates the weather at the occurrence date 402 and the occurrence location 403.

  FIG. 5 shows a table configuration of the attention point management unit 126 of the center server 121. This table is for accumulating caution point information to be distributed to the eco-drive support device 102, and includes a user ID 501, a driving state 502, a place 503, a time zone 504, a day of the week 505, and weather 506. A user ID 501 indicates a user who is a distribution target of caution point information. A driving state 502 indicates a driving state that requires attention at a point of caution. In other words, this indicates an operating state that may become an excessive factor that excessively consumes fuel. A place 503 indicates the latitude and longitude of the attention point. A time zone 504 indicates a time zone in which attention should be paid at the attention point. The time zone 504 may be set every hour, such as “17:00”, or may be designated as “6-12 o'clock”, or in the morning / afternoon. good. The day of the week 505 indicates the day of the week on which attention should be paid at the point of caution. The day of the week 505 may be “Monday”, “Tuesday”, or “Weekday” and “Holiday”. The weather 506 indicates the weather that requires attention at the point of caution. Specifically, “sunny”, “rain”, “snow”, and the like. Points that satisfy the conditions of the driving state 502, the place 503, the time zone 504, the day of the week 505, and the weather 506 are set as caution points. In the example of the figure, attention information is shown that when the weather is fine at 17:00 on weekdays, it is necessary to pay attention to the start at the place “x1, y1”.

  FIG. 6 shows a table configuration of the caution point management unit 107 of the eco-drive support device 102. This table is for accumulating attention point information distributed from the center server 121, and is composed of a driving state 601, a place 602, a time zone 603, a day of the week 604, and a weather 605, and each of the driving states 502 in FIG. , Location 503, time zone 504, day 505, and weather 506.

  FIG. 7 shows a processing flow of the attention point generation unit 127 of the center server 121. First, one user is selected, the driving characteristic determination unit 124 is inquired using the user ID as a key, and a driving state that requires notification of a caution point is acquired (step 701). Details will be described later with reference to FIG. Note that the caution point generation unit 127 has user list information including a user ID and the like, and may be selected in order from the top. Next, one is selected from the operation states obtained in step 701, and the excess consumption point specifying unit 125 is inquired using the operation state as a key to acquire the excess consumption point (step 702). Details will be described later with reference to FIG. From the result of step 702, if there is an excessive consumption point (Yes), the process proceeds to step 704, and if there is no excessive consumption point (No), the process proceeds to step 705 (step 703). The excessive consumption point obtained in step 702 is associated with the driving state and stored in the caution point management unit 704 as caution point information (step 704). If it is confirmed that there is an excessive consumption point (Yes) for all operating states obtained in Step 701, the process proceeds to Step 706, and if there is an unconfirmed operating state (No), the process returns to Step 702 ( Step 705). If attention point information of all users in the user list information has been generated (Yes), the process ends. If not (No), the process returns to Step 701 (Step 706). This processing may be executed at a predetermined date and time, or may be executed at regular intervals, such as every hour or every day, or executed with the end of writing in the history management unit 123 as a trigger. You may do it.

  FIG. 8 shows a processing flow of the driving characteristic determination unit 124 of the center server 121. The driving characteristic determination unit 124 executes processing in response to an inquiry from the caution point generation unit 127 using the user ID as a key. First, a user ID designated as a key is acquired from the caution point generator 127 (step 801). Next, one of the driving states in which the type is stored in advance is selected, and the driving characteristic value is calculated on the condition of the user ID and the driving state (step 802). First, the diagnosis result is searched from the history management unit 123 using the user ID and the operation state as keys. Here, since it is conceivable that the driving skill of the driver is improved, only the latest diagnostic result is used instead of the old diagnostic result. For example, the search from the history management unit 123 is performed by limiting a predetermined period such as the most recent one month, the most recent three months, or the like. As a search result, data of excess consumption ≧ 0 is obtained.

Based on the search results, “excess number”, “excess ratio”, “total excess consumption”, and “excess unevenness” are calculated as operation characteristic values. The excess number is the number of records (data number) in which the excess consumption 405 satisfies the condition of “excess consumption> 0”. The excess ratio is the ratio of the excessive number of search results to the number of records (the search result includes a record of excessive consumption = 0). The total excess consumption is the sum of the excess consumption of the search results. Excess unevenness is a dispersion of excessive consumption of search results. For example, when searching with the user ID = “100” and the operation state (excess factor) = “start” as a key, “excess consumption = 5 cc, occurrence date = ...”, “excess consumption = 14 cc, occurrence date = ...” It is assumed that four records of “excess consumption = 0 cc, date of occurrence = ...”, “excess consumption = 9 cc, date of occurrence = ...” are retrieved. At this time, the operation characteristic values are excessive because excess number = 4-1 = 3, excess ratio = 3 ÷ 4 = 0.75, total excess consumption = 5 + 14 + 0 + 9 = 28, and the average value of excess consumption is 28 ÷ 4 = 7. Unevenness = {(5−7) ² + (14−7) ² + (0−7) ² + (9−7) ² } ÷ 4 = 26.5.

  Based on the driving characteristic value calculated in step 702, it is determined whether or not notification of a caution point is necessary (step 803). The necessity of notification of a caution point is determined using “threshold comparison of driving characteristic values” and “time series comparison of driving characteristic values”. In the case of “threshold comparison of driving characteristic value”, a threshold value for notifying the attention point is set in advance, and the determination is made based on whether or not the threshold value is exceeded. The threshold is set for each of “excess number”, “excess ratio”, “total excess consumption”, and “excess unevenness” for each operating state. For example, notification is made when “start excess number> start excess number threshold” holds. In the case of “time series comparison of driving characteristic value”, the determination is made by relative comparison with the previous value, and the determination is made by the increase / decrease (change) of the driving characteristic value in the time series. For example, when the range set in step 802 is the most recent month, notification is made when “the excess number of the start in the most recent month> the excess number of the start in the previous month” holds. If the number of launches in the most recent month is 3 and the number of launches in the previous month is 5, then the excess number of launches in the last month> the excess number of launches in the previous month There is no notification. The comparison method of “threshold comparison of driving characteristic values” and “time series comparison of driving characteristic values” and each driving characteristic value may be used alone to determine whether notification is possible, or may be determined by combination. For example, the determination may be made only by “excess number> threshold number threshold”, or by “excess number> threshold number AND AND excess ratio of the most recent month> excess ratio of the previous month”. good.

  As a result of step 803, if notification is necessary (Yes), the process proceeds to step 804, and if notification is not necessary (No), the process proceeds to step 805. The driving state requiring notification of the caution point is stored (step 804). If it is confirmed whether or not the notice of the cautionary point can be notified for all driving states set in advance (Yes), the process proceeds to Step 806, and if not all confirmed (No), the process returns to Step 802 (Step S802). 805). Finally, the driving state requiring the attention point is returned to the attention point generation unit 127 (step 806).

  FIG. 9 shows a processing flow of the excessive consumption point specifying unit 125 of the center server 121. The excessive consumption point specifying unit 125 performs processing in response to an inquiry from the excessive consumption point specifying unit 125 using the operation state as a key. First, the conditions of “operating state (excess factor)”, “time zone”, “day of the week”, “weather” are set and the history management unit 123 is searched (step 901). Here, the “operating state (excess factor)” specified by the attention point generation unit 127 as a key is used. "Time zone", "day of the week", and "weather" are selected as appropriate combinations. For example, if “time zone” can be selected as “one hour between 0 o'clock and 23 o'clock”, “day of the week” can be selected as “weekday / holiday”, and “weather” can be selected as “clear, rain, snow” First, select the combination of “0:00”, “Weekday”, and “Sunny”. All history information stored in the history management unit 123 may be targeted, or a period restriction such as the latest half year may be added. As a search result, a plurality of candidate points (a plurality of records) that match the specified condition are searched. One of the candidate points is selected as a representative point, and a candidate point near the representative point is searched (step 902). Here, the determination as to whether or not it is near is performed by calculating the Euclidean distance between the two points from the representative point and the candidate point occurrence location 403, and when the distance is equal to or less than the set threshold value, it is determined as being near. It is checked whether or not the result of a user different from the representative point user is included in the neighboring points. If the result is included (Yes), the process proceeds to Step 904. If not included, the result is Step (No). The process proceeds to 905 (step 903). For example, it is assumed that five candidate points A to E have been acquired as the search results in step 901. In step 902, Euclidean distances between A and B, A and C, A and D, and A and E are calculated using A at the top as a representative point, and it is determined whether or not A is in the vicinity. In step 903, when it is determined that B and C are in the vicinity of A, the user IDs 401 of B and C are acquired, and it is confirmed whether or not they are different from the user ID 401 of the representative point A. That is, it is determined whether or not a plurality of users are consuming excessive fuel at the same place and in the same operation state. If there is a point where fuel is excessively consumed by a plurality of users, it is recorded as an excessive consumption point (step 904). If all the retrieved candidate points have been confirmed (Yes), the process proceeds to step 906, and if there are still candidate points remaining (No), the process returns to step 902 (step 905). For example, when five points A to E are first found as candidate points, and B and C are searched as neighboring points with A as a representative point, D and E are unconfirmed. repeat. If over-consumption points are searched for all the combinations regarding the conditions of “time zone”, “day of the week”, and “weather” set in step 901 (Yes), the process proceeds to step 907 and the over-consumption point is still searched. When there is no combination of conditions (No), the process returns to Step 901 (Step 906). Finally, the recorded excessive consumption point is returned to the caution point generation unit 127 (step 907).

  Although illustration is omitted, when only one candidate point is obtained as a search result in step 901, the process proceeds to step 906 to check the presence or absence of the remaining condition.

  FIG. 10 shows a processing flow of the notification unit 106 of the eco-drive support device 102. First, route information is acquired from the navigation device 114 (step 1001). Next, the attention point management unit 107 is searched, and the attention point on the route acquired in step 1001 is acquired (step 1002). Next, information on the current time and current location is acquired from the vehicle information collection unit 103 (step 1003). Next, the weather is estimated from the vehicle information acquired from the vehicle information collection unit 103 (step 1004). For example, “Snow” when “Snow mode signal” is ON, “Rain” when “Snow mode signal” is OFF and “Wiper operation” is ON, “Sunny” when both are OFF presume. If there is a caution point in the caution point acquired in step 1002, it is confirmed whether or not there is a caution point that satisfies the conditions of the current time and current location acquired in step 1003 and the weather estimated in step 1004 (Yes). In step 1006, if there is no caution point (No), the process proceeds to step 1007 (step 1005). Regarding the time, a time zone including the current time or including a time slightly earlier than the current time is a condition. When providing information on a place a little ahead where you plan to run, look for a caution point on the condition a little ahead. If there is a caution point, the user is notified (step 1006). As a notification method, notification may be made by voice from the speaker 113, or icons and characters may be displayed on the display 112. If the vehicle has arrived at the destination (Yes), the process is terminated. If the vehicle has not arrived (No), the process returns to Step 1003 (Step 1007). This process is executed with a destination set in the navigation terminal 114 and triggered by the start of vehicle route guidance toward the destination. If the route is not guided, the processing of the notification unit 106 may be started by starting the engine of the vehicle, and the processing may be ended by stopping the engine.

  According to the present embodiment, it is possible to provide eco-driving support information corresponding to the driving technology of the driver.

  According to the present embodiment, the driver's driving characteristic determination and attention point generation are processed on the center side, so what kind of data is used as the driving characteristic value for driving characteristic determination, and attention is given from the obtained driving characteristic value It is easy to change how the points are generated.

  FIG. 11 is a system configuration diagram according to the second embodiment. In the first embodiment, the driving characteristic determination and attention point generation of the driver are processed on the center side, but in the present embodiment, they are processed on the vehicle side. In FIG. 11, the same components as those in FIG.

  Each process described below is realized by executing a program by the CPU included in the eco-drive support device 102. The eco-drive support device 102 executes processes of a vehicle information collection unit 103, a driving diagnosis unit 104, a notification unit 106, a data transmission / reception unit 1103, a driving characteristic determination unit 1101, and a caution point generation unit 1102. It has a diagnosis result management unit 105 and a caution point management unit 107 that store data used to execute these processes. The processing flow of the driving diagnosis unit 104 and the notification unit 106 is the same as that in the first embodiment. The driving characteristic determination unit 1101 is the same as the driving characteristic determination unit 124 of the first embodiment, and the processing flow is the same as that in FIG. The processing flow of the caution point generator 1102 will be described later with reference to FIG. The data transmission / reception unit 1103 communicates with the data transmission / reception unit 122 of the center server 121 to transmit / receive data. Data transmission is the same as in the first embodiment, and the diagnosis result data accumulated in the diagnosis result management unit 105 is transmitted with the user ID added. In the data reception, an information request is sent, the data of the excessive consumption point management unit 1110 is received, and the received data is passed to the attention point generation unit 1102.

  Each process described below is realized by executing a program by the CPU of the center server 121. The center server 121 executes each process of the data transmitting / receiving unit 122 and the excessive consumption point specifying unit 125. It has a history management unit 123 and an excessive consumption point management unit 1110 that store data used for executing these processes. As in the first embodiment, the data transmission / reception unit 122 receives the diagnosis result data from the eco-drive diagnosis apparatus 102, inquires the weather management server 131, acquires the corresponding weather, and associates the received diagnosis result with the weather. And stored in the history management unit 123. Further, based on the request from the eco-drive diagnosis device 102, the data of the excessive consumption point management unit 1110 is returned. The excessive consumption point specifying unit 125 specifies a point where fuel is likely to be excessively consumed through all users in the user list information, and accumulates the result in the excessive consumption point management unit 1110. The processing flow of the excessive consumption point specifying unit 125 is the same as that in FIG.

  FIG. 12 shows a table configuration of the excessive consumption point management unit 1110 of the center server 121. This table is for accumulating excess consumption point information to be distributed to the eco-drive support device 102, and includes an operation state (excess factor) 1201, a place 1202, a time zone 1203, a day of the week 1204, and weather 1205. An operation state 1201 indicates an operation state that causes an excessive consumption point. A place 1202 indicates the latitude and longitude of the excessive consumption point. A time zone 1203 indicates a time zone in which excessive consumption is likely to occur. A day of the week 1204 indicates a day of the week when excessive consumption is likely to occur. The weather 1205 indicates the weather where excessive consumption is likely to occur. A point that satisfies all the conditions of the driving state 1201, the place 1202, the time zone 1203, the day of the week 1204, and the weather 1205 is defined as an excessive consumption point. In the example of the figure, when the weather is fine at 17:00 on weekdays and the place is “x1, y1”, attention information indicating that it is easy to excessively consume fuel by starting is shown.

  FIG. 13 shows a processing flow of the caution point generator 1102 of the eco-drive support device 102. The outline of the processing is the same as in FIG. First, a list of excess consumption points is acquired from the data transmission / reception unit 1103 (step 1301). Next, the driving characteristic determination unit 1101 is inquired to acquire a driving state that requires notification of a point of interest (step 1302). This is the same processing as step 701 in the first embodiment. Next, one of the operating states obtained in step 1302 is selected, and an excessive consumption point corresponding to the selected operating state is searched from the list of excessive consumption points acquired in step 1301 (step 1303). From the result of step 1303, when there is an excessive consumption point (Yes), the process proceeds to step 1305, and when there is no excessive consumption point (No), the process proceeds to step 1306 (step 1304). The excess consumption point obtained in step 1303 is associated with the driving state and stored in the caution point management unit 107 as caution point information (step 1305). If it is confirmed that there is an excessive consumption point for all the operating states obtained in step 1302 (Yes), the process ends. If there is an unconfirmed operating state (No), the process returns to step 1303 (step 1306). ).

  According to the present embodiment, it is possible to provide eco-driving support information corresponding to the driving technology of the driver.

  According to the present embodiment, the driver's driving characteristic determination and attention point generation are processed on the vehicle side. Therefore, when viewed as the entire eco-drive support system, these processes are distributed to each vehicle and the processing load on the center server is suppressed. it can. That is, even if the number of users (vehicles) registered in the user list information increases and the accumulated data in the history management unit and excess consumption point management unit of the center server increases, the processing of the center server related to these processings The load does not increase.

The system configuration | structure of Example 1 is shown. The hardware configuration of the eco-drive support device is shown. The table structure of a diagnostic result management part is shown. The table structure of a log | history management part is shown. The table structure of the caution point management part of a center server (eco-drive support server) is shown. The table structure of the caution point management part of an eco-drive support device is shown. The flow of a caution point generation part is shown. The flow of an operation characteristic judgment part is shown. The flow of an excessive consumption point specific part is shown. The flow of a notification part is shown. The system configuration | structure of Example 2 is shown. The table structure of the excessive consumption point management part of Example 2 is shown. The flow of the caution point production | generation part of Example 2 is shown.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101: Vehicle, 102: Eco-drive assistance apparatus, 103: Vehicle information collection part, 104: Driving diagnosis part, 105: Diagnosis result management part, 106: Notification part, 107: Caution point management part, 108: Data transmission / reception part, 109 : Communication device, 110: GPS, 111: ECU, 112: Display, 113: Speaker, 114: Navigation device, 115: In-vehicle network, 120: Communication network, 121: Center server (eco-drive support server), 122: Data transmission / reception , 123: History management unit, 124: Driving characteristic determination unit, 125: Excess consumption point specifying unit, 126: Caution point management unit, 127: Caution point generation unit, 130: Internet, 131: Weather management server, 1101: Driving Characteristic determination unit, 1102: Attention point generation unit, 1103: Data transmission / reception unit, 1110: Excess consumption area Management unit.

Claims (11)

  The vehicle information is acquired from the vehicle, the driver's driving from the acquired vehicle information is diagnosed as to whether or not the vehicle has excessively consumed fuel in response to an excessive factor that excessively consumes fuel, and the driver An over-consumption point where the vehicle easily consumes fuel is identified from the diagnosis result of driving, the driving characteristic of the driver is determined from the diagnostic result, and the driver is notified based on the determination result of the driving characteristic An eco-driving support method comprising: selecting an attention point from the excessive consumption point and notifying the driver of the selected attention point.   The determination of the driving characteristics corresponds to the excess factor of the diagnosis result in a predetermined period, the number of times that the vehicle has excessively consumed fuel, the ratio that the vehicle has excessively consumed fuel, the sum of excess consumption of the vehicle, 2. The eco-driving support method according to claim 1, wherein at least one of dispersion of excess consumption of the vehicle is calculated as a driving characteristic value, and the driving characteristic of the driver is determined based on the driving characteristic value. .   The determination of the driving characteristic of the driver based on the driving characteristic value is performed by using at least one of a comparison between the driving characteristic value and a predetermined threshold value and a time series increase / decrease of the driving characteristic value. The eco-driving support method according to claim 2, wherein: The eco-drive support method according to any one of claims 1 to 3 , wherein at least one of a display and a speaker is used for notifying the driver of the caution point. Before the vehicle to the attention point to be the notification on the travel path of the vehicle reaches, eco according to any one of claims 1 to 4, and notifies the attention point to the driver Drive support method.   A history management unit for managing a diagnosis result received from a vehicle and indicating whether or not the driver of the vehicle has excessively consumed fuel in response to an excessive factor that the vehicle excessively consumes fuel; and An over-consumption point identifying unit that identifies an over-consumption point where the vehicle is likely to excessively consume fuel from the diagnosis result of driving by the driver; a driving characteristic determining unit that determines the driving characteristic of the driver from the diagnosis result; and the driving An eco-drive support server comprising: a caution point generation unit that selects a caution point to be notified to the driver from the excessive consumption point based on a determination result of characteristics.   The driving characteristic determination unit corresponds to the excess factor of the diagnosis result in a predetermined period, the number of times that the vehicle has excessively consumed fuel, a ratio that the vehicle has excessively consumed fuel, a total of excessive consumption of the vehicle, The eco-drive support server according to claim 6, wherein at least one of dispersion of excess consumption of the vehicle is calculated as a driving characteristic value, and the driving characteristic of the driver is determined based on the driving characteristic value. .   The determination of the driving characteristic of the driver based on the driving characteristic value is performed by using at least one of a comparison between the driving characteristic value and a predetermined threshold value and a time series increase / decrease of the driving characteristic value. The eco-drive support server according to claim 7, wherein:   A vehicle information acquisition unit that acquires vehicle information from a vehicle, and diagnoses whether or not the driver's driving from the acquired vehicle information has consumed excessive fuel in response to an excessive factor that the vehicle consumes excessive fuel A driving diagnosis unit that determines a driving characteristic of the driver from the diagnosis result, a data receiving unit that receives from the center server an excessive consumption point at which the vehicle is likely to excessively consume fuel, and the driving characteristic An eco-drive support device comprising: a caution point generation unit that selects a caution point to be notified to the driver from the excessive consumption point based on a determination result; and a notification unit that notifies the driver of the caution point .   The driving characteristic determination unit corresponds to an excess factor of the diagnosis result in a predetermined period, the number of times the vehicle has excessively consumed fuel, a ratio that the vehicle has excessively consumed fuel, a total of excessive consumption of the vehicle, and The eco-drive support device according to claim 9, wherein at least one of the variances of the excess consumption of the vehicle is calculated as a driving characteristic value, and the driving characteristic of the driver is determined based on the driving characteristic value.   The determination of the driving characteristic of the driver based on the driving characteristic value is performed by using at least one of a comparison between the driving characteristic value and a predetermined threshold and a time series increase / decrease of the driving characteristic value. The eco-drive support device according to claim 10.

Images