JP6387652B2 - Notification condition generation program, notification condition generation method, and information processing apparatus - Google Patents

Description

  The present application relates to a notification condition generation program, a notification condition generation method, an information processing device, and an in-vehicle device.

  Operation recording instruments such as drive recorders (hereinafter abbreviated as “Doraco” as necessary) mounted on vehicles traveling on roads, etc., are used for driving information such as vehicle position and speed at each predetermined time (travel data) Etc.). Also, from the information (drareco information) obtained from each vehicle's dorareko, the points where dangerous driving such as sudden braking or sudden acceleration was performed are tabulated, and multiple points such as sudden braking are extracted, and the vehicle Notification is made before passing (for example, a point approached by a predetermined distance).

JP 2013-69247 A

  However, the method of performing notification at a point that is close to the frequent occurrence point by a predetermined distance may result in unnecessary notification depending on the subsequent course of the vehicle (for example, going straight at an intersection, turning right, turning left, etc.). For example, at a certain intersection, when a vehicle turning to the left has many sudden brakes, it is preferable to notify only a vehicle passing through a similar route.

  In one aspect, the present invention aims to improve notification accuracy.

In one aspect, when the notification condition generation program generates a notification condition used in a notification system that performs notification according to the travel route of the vehicle, a predetermined operation event is performed based on the travel data of the vehicle. The number of times is divided into the position of the vehicle and whether or not the route has changed after the predetermined operation event or the direction of the route, and the weighting coefficient corresponding to the road condition at the position is multiplied by the number of times of the summation. If the combined value is equal to or greater than a predetermined number , in addition to approaching the position, the presence / absence of the course change matches, or traveling on the same course as the direction of the course change is scheduled. The notification condition including the following is generated, and the notification condition is generated based on any one of the vehicle type, the total vehicle weight, the maximum load capacity, and the vehicle width so that the notification timing is variable. Con Let the computer run it.

  As one aspect, notification accuracy can be improved.

It is a figure which shows an example of schematic structure of a notification system. It is a figure which shows an example of a function structure of a management server. It is a figure which shows an example of a function structure of a vehicle-mounted apparatus. It is a figure which shows an example of the hardware constitutions of a management server. It is a figure which shows an example of the hardware constitutions of a vehicle-mounted apparatus. It is a flowchart which shows an example of the notification condition production | generation process in a management server. It is a flowchart which shows an example of a total process. It is a figure which shows the example of data which a management server has. It is a figure which shows the example of data for setting a notification condition variably. It is a flowchart which shows an example of the notification condition transmission process in a management server. It is a flowchart which shows an example of the process in a vehicle-mounted apparatus. It is a flowchart which shows an example of the process in a driving | running | working condition determination part. It is a figure which shows an example of the example of data which a vehicle has. It is a figure which shows the specific example of a notification.

  Hereinafter, embodiments will be described in detail with reference to the accompanying drawings.

<Example of schematic configuration of notification system>
FIG. 1 is a diagram illustrating an example of a schematic configuration of a notification system. A notification system 10 illustrated in FIG. 1 includes a management server 11 as an example of an information processing apparatus, one or more vehicles 12-1 to 12-3 (hereinafter referred to as “vehicles 12” as necessary), and operation management. Person terminal 13. The management server 11 and the vehicle 12 are connected in a state where data can be transmitted and received by a communication network 14-1 typified by wireless communication or the like. The management server 11 and the operation manager terminal 13 are connected in a state where data can be transmitted and received by a communication network 14-2 represented by the Internet, a local area network (LAN), and the like. Note that the communication networks 14-1 and 14-2 may be the same network.

  The management server 11 obtains operation information such as the Doraco information transmitted from each vehicle 12 at a predetermined interval (for example, 5 to 10 minutes, etc.). The dorareco information is, for example, information for identifying the vehicle 12 (vehicle ID), vehicle position information (latitude / longitude), speed information, time information, etc. acquired using a Global Positioning System (GPS). It is. The drive information includes at least one of, for example, a change in travel distance and engine speed, a sudden acceleration / deceleration detection, a door opening / closing, an acceleration G [CGS unit system gal (Gal)], and the like. Including. Note that the drive information is not limited to this. The acceleration G is determined by the vertical G (for example, the force that the body brings back and forth with respect to the traveling direction of the car when riding and starting and braking) and the lateral G (for example, the direction of bending due to centrifugal force) On the other hand, it may be a force that is carried with the body.

  In addition, the management server 11 extracts a portion where a predetermined operation event (or behavior of the vehicle 12 due to execution of the operation event) of the driver is generated from the operation information collected from each vehicle 12. Here, the operation event is, for example, a deceleration operation such as a sudden brake, but is not limited thereto, and may be a handle operation such as a sudden acceleration (rapid start) operation or a meandering operation. In addition, the management server 11 counts the candidates for the frequent occurrence points where the operation events occur frequently from the occurrence points of the operation events. In the present embodiment, for example, the operation event occurrence points obtained from the operation information (travel data, etc.) of each vehicle 12 are plotted on a map, and the alarm output target is determined from the points ranked according to the occurrence status. The position to be extracted is extracted. Further, for example, the totaling is performed by dividing the operation event of the vehicle 12 for each direction (route) that has traveled after the occurrence.

  Moreover, the management server 11 acquires the position of the vehicle (a frequent occurrence point) when a predetermined operation event is performed and the presence / absence of the course change or the course direction after the operation event from the count result. The management server 11 generates conditions (notification conditions) for notifying the driver of the vehicle 12, passengers, and the like in advance from the acquired information. For example, in addition to approaching the acquired position (frequent occurrence point), the management server 11 notifies that the presence / absence of the course change matches, or that the traveling on the same course as the course change direction is scheduled. You may produce | generate by including in conditions. For example, different notification conditions may be set according to preset areas (roads, intersections, etc.), for example, different notifications according to the type, weight, driver information, time zone, weather information, etc. of the vehicle 12 Conditions may be set.

  The management server 11 outputs the generated notification conditions, route information, notification data, and the like to the vehicle 12. The route information is information indicating a planned travel route of the vehicle 12, for example. The notification data is information indicating contents to be notified to the driver when the traveling vehicle 12 satisfies the notification condition, for example. This notification is performed, for example, in order to call attention to the user by an alarm or an alarm, for example, just before the vehicle 12 is heading for the frequent occurrence point. By determining the traveling state of the vehicle using the notification condition described above, it is possible to accurately notify the vehicle 12 that meets the condition with higher accuracy.

  The management server 11 is a personal computer (PC), a server, or the like, but is not limited thereto, and may be, for example, a cloud server configured by cloud computing having at least one information processing apparatus.

  The vehicle 12 includes an in-vehicle device 20 that measures a traveling situation. As shown in FIG. 1, the vehicle 12 is a commercial vehicle such as a truck 12-1, a bus 12-2, a taxi 12-3, but the number and type are not limited to this, for example, a general vehicle, A motorcycle such as a motorcycle may be used. The in-vehicle device 20 is equipped with a driving record meter such as a dorareco, etc., and a recording unit such as a memory that records a driving situation every predetermined time (for example, 1 to 5 seconds) during operation (including running and stopping). To record.

  The in-vehicle device 20 transmits the recorded draco information (operation information) to the management server 11 via the communication network 14-1 every predetermined time (for example, 1 to 10 minutes). In addition, when there is a transmission request from the management server 11, the in-vehicle device 20 may transmit the Draco information recorded so far to the management server 11.

  The in-vehicle device 20 acquires notification conditions, route information, notification data, and the like from the management server 11 via the communication network 14-1. The in-vehicle device 20 receives the information (notification conditions, route information, notification data, etc.) described above in the management server 11 via the communication network 14-1 when the driver starts driving the vehicle 12 (for example, when engine driving is started). ) Acquisition request. The in-vehicle device 20 stores various information acquired by the acquisition request in a storage unit or the like.

  The in-vehicle device 20 acquires the travel position, travel direction, and the like of the vehicle 12, determines whether or not the vehicle 12 has approached a predetermined area (point) stored as a notification condition, and enters the predetermined area. When the planned route after entering the vehicle is a predetermined route, the driver 12 is notified within the vehicle 12.

  For notification to a driver in the vehicle 12 (for example, including a passenger), for example, a predetermined voice message may be output by a speaker provided in Dorareco, and a display of a car navigation system mounted on the vehicle 12 or the like. A message notifying danger may be displayed on the screen of the department. The notification method is not limited to this.

  The in-vehicle device 20 may be configured integrally with a car navigation system or the like, for example, or may be configured separately. Moreover, the vehicle-mounted apparatus 20 may be incorporated in the vehicle 12, and may be installed in the vehicle 12 so that attachment or detachment is possible.

  The operation manager terminal 13 is connected to the management server 11 via the communication network 14-2, and aggregated dorareko information (operation information) for each vehicle 12 and predetermined operation events (for example, sudden braking, sudden acceleration, sudden Information on frequently occurring points for each handle etc. is displayed on the screen of the display unit. In addition, although the operation manager terminal 13 is PC etc., for example, it is not limited to this, Information communication terminals, such as a tablet terminal, a smart phone, and a mobile telephone, may be sufficient.

  Each function of the operation manager terminal 13 may be provided in the management server 11, and each function of the management server 11 may be provided in the operation manager terminal 13. That is, the management server 11 and the operation manager terminal 13 may be integrally configured.

<Example of Functional Configuration of Management Server 11>
Next, a functional configuration example of the management server 11 in the notification system 10 described above will be described. FIG. 2 is a diagram illustrating an example of a functional configuration of the management server. The management server 11 illustrated in the example of FIG. 2 includes an operation information reception unit 21, a totaling unit 22, a notification condition generation unit 23, a transmission unit 24, a weather information acquisition unit 25, and a storage unit 26. The storage unit 26 includes operation information 31, road information 32, count results 33, notification conditions 34, vehicle information 35, driver information 36, and weather information 37.

  The operation information receiving unit 21 receives operation information 31 stored for each of the one or more vehicles 12 via the communication network 14-1. The received operation information 31 is stored in the storage unit 26. Therefore, the operation information 31 stored in the storage unit 26 is a set of operation information obtained from one or a plurality of vehicles 12.

  The tabulation unit 22 tabulates data using the operation information 31 stored in the storage unit 26. For example, the totaling unit 22 detects the traveling speed from the traveling position for each vehicle included in the operation information 31 and the displacement of the position for each unit time. Further, the counting unit 22 counts the position where the driver has performed a predetermined operation event on the vehicle 12, the number of times, and the like based on the amount of displacement (for example, the deceleration width) between the travel position and the travel speed. Examples of the predetermined operation event include, but are not limited to, a deceleration operation such as a sudden brake, an acceleration operation such as a sudden start, and a handle operation such as a meandering operation. For example, the totaling unit 22 determines that a sudden braking operation event has occurred when the vehicle decelerates by a predetermined value or more per predetermined distance, and suddenly operates when the vehicle accelerates by a predetermined value or more per predetermined distance. It is determined that a start operation event has occurred. Further, for example, when the acceleration G value in the front-rear direction with respect to the vehicle 12 obtained from the operation information 31 is equal to or greater than a predetermined value, the counting unit 22 performs an operation of sudden braking or sudden start depending on the direction (front or rear). An event may be determined. Further, the totaling unit 22 may determine a steering operation such as a meandering operation when the lateral acceleration G value with respect to the vehicle is equal to or greater than a predetermined value.

  In addition, the counting unit 22 performs classification by counting based not only on the position of the vehicle 12 when the predetermined operation event is performed but also whether or not the vehicle 12 has changed the course after the operation event, the course direction, and the like. May be. Moreover, the totaling unit 22 may perform totaling based on the vehicle type or vehicle weight corresponding to the vehicle ID with reference to the vehicle information 35 stored in the storage unit 26, for example. Moreover, the totaling part 22 may total for every driver based on the driver information 36 which is driving the vehicle 12, for example. Moreover, the totaling part 22 may classify and classify | categorize for every weather based on the weather information 37, for example. The weather information 37 is, for example, from an external server (for example, the Japan Meteorological Agency) connected via the communication network 14-2, the time corresponding to the actual weather for each region at the time of driving, and the driving route of the region to be driven from now on However, the present invention is not limited to this. Moreover, the totaling part 22 may total for every time slot | zone, for example, and may combine multiple among the various totalization mentioned above. The total result 33 totaled by the total unit 22 is stored in the storage unit 26.

  The notification condition generation unit 23 generates a notification condition based on the aggregation result 33 by the aggregation unit 22. For example, when the sudden braking occurrence points are counted as an operation event for the vehicle 12, the notification condition generation unit 23 extracts the points where the number of occurrences of sudden braking is equal to or more than a predetermined number from the counting results as the frequent occurrence points. To do. Further, the notification condition generating unit 23 is based on the operation information (running data) of the vehicle 12, for example, the position of the vehicle 12 when a deceleration operation such as sudden braking is performed, and whether or not there is a course change after the deceleration operation And the direction of the course is extracted. In addition to approaching the position of the extracted frequent occurrence point, the notification condition generation unit 23 matches the presence or absence of a course change of the vehicle 12, or schedules traveling on the same course as the course change direction, etc. Is included in the notification condition 34.

  Note that the notification condition 34 generated by the notification condition generation unit 23 corresponds to, for example, vehicle information 35, driver information 36, weather information 37, and the like, corresponding to the respective aggregation results classified and totaled by the totaling unit 22. You may have the notification conditions for every identification information (for example, vehicle type, driver ID, weather classification).

  The notification condition generator 23 is executed at a preset timing (for example, every predetermined day, every week, every month, every year). The set notification condition 34 is stored in the storage unit 26.

  In response to an acquisition request (inquiry) for the notification condition 34 received from the vehicle 12 via the communication network 14-1, the transmission unit 24 extracts the notification condition 34 from the storage unit 26 and transmits the notification condition 34 to the requested vehicle 12. To do. The transmission unit 24 transmits information such as the operation information 31 and the notification condition 34 to the operation manager terminal 13 via the communication network 14-2. Thereby, the operation manager can display and confirm the operation information 31 and the notification condition 34 of each vehicle 12 acquired from the operation manager terminal 13.

  The transmission unit 24 acquires the vehicle information 35 corresponding to the ID of the vehicle 12 for which acquisition has been requested from the storage unit 26, extracts the notification condition corresponding to the acquired vehicle information, and transmits the notification condition to the vehicle 12. Also good.

  The weather information acquisition unit 25 is made to correspond to the actual weather for each region at the time of driving and the driving route of the region to be driven from an external server (for example, the Japan Meteorological Agency) connected via the communication network 14-2, for example. Get weather forecast for time. The weather information acquisition method by the weather information acquisition unit 25 is not limited to this. For example, the weather may be estimated according to humidity, temperature, or the like included in the operation information 31. For example, the weather can be clear when the humidity is low and the temperature is high, the weather can be rain when the humidity and temperature are high, and the weather can be snow when the humidity is high and the temperature is low. It is not limited. The acquired weather information 37 is stored in the storage unit 26.

  The storage unit 26 reads and writes various information. In addition, the information memorize | stored in the memory | storage part 26 is the operation information 31, the road information 32, the total result 33, the notification condition 34, the vehicle information 35, the driver information 36, and the weather information 37 at least. Although it is one information, it is not limited to this. For example, the storage unit 26 may store the aggregation result by the aggregation unit 22, the transmission result by the transmission unit 24, and the like.

  In the present embodiment, an appropriate notification condition is generated for each vehicle 12 by the configuration of the management server 11 described above, and the generated notification condition is used in accordance with the position of each vehicle 12, the presence / absence of a course change, the course direction, and the like. Notification accuracy can be improved by performing appropriate notification.

<Example of functional configuration of vehicle 12>
Next, a functional configuration example of a device (on-vehicle device 20) mounted on the vehicle 12 in the notification system 10 described above will be described with reference to the drawings. FIG. 3 is a diagram illustrating an example of a functional configuration of the in-vehicle device. In the example of FIG. 3, the in-vehicle device 20 includes a vehicle power supply control detection unit 41, a notification condition acquisition unit 42, an operation information acquisition unit 43, a travel situation determination unit 44, a notification unit 45, and an operation information transmission unit 46. And a storage unit 47. Note that the storage unit 47 includes notification conditions 51, operation information 52, route information 53, and notification data 54.

  The vehicle power source control detection unit 41 detects ON / OFF control of the battery power source for the vehicle 12 using the operation key. When the vehicle power supply control detection unit 41 is turned on, acquisition of the notification condition 51, acquisition of the operation information 52, storage, transmission, and the like are executed.

  When the vehicle power supply control detection unit 41 detects that the vehicle 12 is powered on, the notification condition acquisition unit 42 makes an inquiry about the notification condition 51 to the management server 11 via the communication network 14-1. To obtain the latest notification condition 51.

  The notification condition acquisition unit 42 may inquire about the notification condition once every predetermined period. For example, the notification condition acquisition unit 42 may not make the inquiry every time the vehicle is turned on, that is, several times a day. Therefore, the notification condition acquisition unit 42 may inquire about the notification condition 51 when, for example, the first power-on of the day is detected or when the power-on is detected after a predetermined number of days have elapsed. Furthermore, the notification condition acquisition unit 42 may receive the notification condition automatically transmitted immediately after the management server 11 performs the update regardless of the inquiry.

  Here, the notification condition acquisition unit 42 can also transmit identification information (for example, vehicle ID), driver information, and the like of the vehicle 12 at the time of inquiry. In addition to the notification condition 51, the notification condition acquisition unit 42 may acquire route information 53 and notification data 54 that indicate a schedule for the vehicle 12 to travel from now on. The acquired information such as the latest notification condition 51 is stored in the storage unit 47.

  The operation information acquisition unit 43 acquires information (operation information) during driving of the vehicle 12. The operation information 52 includes time, position (latitude, longitude), traveling speed, etc. every predetermined time (for example, 1 to 3 seconds), but is not limited thereto. The operation information 52 can be obtained from, for example, the above-described dorareco information or the like, but is not limited to this. The acquired operation information 52 is stored in the storage unit 47.

  For example, the traveling state determination unit 44 compares the current traveling state obtained from the operation information 52 acquired every predetermined time and the future course (planned course) obtained from the route information 53 with the notification condition 51. In addition, when the predetermined condition set in the notification condition 51 is satisfied, the traveling state determination unit 44 notifies the vehicle 12 by the notification unit 45. For example, the traveling state determination unit 44 acquires that the vehicle 12 has approached a predetermined area (for example, a sudden braking frequent occurrence point) included in the notification condition 51, and further refers to the route information 53 to go to the predetermined area. When the scheduled route after entering the vehicle matches the stored predetermined route, the notification unit 45 makes a notification in the vehicle 12.

  Here, the route information 53 is not only acquired from the management server 11 but also stored in advance as the set destination when the driver performs destination setting by a car navigation system or the like mounted on the vehicle 12, for example. The route information 53 may be generated from the map information and the like. In addition, the route information 53 may be stored in advance when a route is set in advance such as a traveling bus.

  The notification unit 45 notifies information corresponding to the determination result by the traveling state determination unit 44 to the driver of the vehicle 12, passengers, and the like. Note that the notification unit 45 may be notified by sound from a speaker or the like provided in the vehicle 12 or may be notified by display on a display screen included in the car navigation system in the vehicle 12.

  For example, the notification unit 45 responds to the vehicle 12 when the traveling condition of the vehicle 12 satisfies (matches) the notification condition 51 defined based on dangerous driving or the like that is highly likely to cause an accident such as a collision. Notification based on the notification data 54 is performed. As an example of the notification data 54, for example, “Be careful with dangerous driving”, “High possibility of sudden braking”, “Be careful with driving”, etc., to support the driver for safe driving However, it is not limited to this. For example, it may be a warning or alarm set as the notification data 54, or may be a combination of a plurality of messages, warnings, and alarms.

  Further, in the present embodiment, for example, processing is performed including the direction of travel after sudden braking (for example, the direction of route change) as a condition, so for example, notification in accordance with the travel direction such as “Be careful when turning right” is given. You may go. These data are stored in the notification data 54 in advance.

  The notification unit 45 can also perform notification control such that the same notification is performed only a predetermined number of times (for example, once) within a predetermined time so that the same notification is not performed many times.

  The operation information transmission unit 46 transmits the operation information 52 acquired by the operation information acquisition unit 43 and stored in the storage unit 47 to the management server 11 via the communication network 14-1 at a predetermined timing. The predetermined timing is, for example, an interval of a predetermined time (for example, 5 to 8 minutes), the time when the power is turned off by the vehicle power control detection unit 41, the memory capacity of the storage unit 47 is a predetermined value (for example, the entire capacity 90%) or more, when the condition is satisfied, the information is transmitted to the management server 11. That is, the operation information transmission part 46 collects the operation information 52 acquired every second, for example, for every predetermined time, and transmits to the management server 11.

  In addition, the operation information transmission part 46 may transmit the operation information 52 memorize | stored in the memory | storage part 47 until then, when there is an inquiry of the operation information acquisition from the management server 11. In the operation information 52 to be transmitted, for example, information (driver ID) for identifying a vehicle ID or a driver for driving the vehicle 12 so that the management server 11 can manage which vehicle is the operation information sent from the vehicle. May be added. The operation information transmission unit 46 may delete the operation information 52 normally transmitted to the management server 11 from the storage unit 47 after transmission or after a predetermined time has elapsed.

  The storage unit 47 reads and writes various information. In addition, although the information memorize | stored in the memory | storage part 47 is at least 1 information among the notification conditions 51, the operation information 52, the route information 53, and the notification data 54, it is not limited to this. For example, the determination result by the traveling state determination unit 44 and the notification result by the notification unit 45 may be included.

<Hardware configuration example of the management server 11>
Next, a hardware configuration example of the management server 11 described above will be described with reference to the drawings. FIG. 4 is a diagram illustrating an example of a hardware configuration of the management server. In the example of FIG. 4, the management server 11 includes an input device 61, an output device 62, a drive device 63, an auxiliary storage device 64, a main storage device 65, a central processing unit (CPU) 66, and a communication device 67. These are connected to each other by a system bus B.

  The input device 61 includes a pointing device such as a keyboard and a mouse operated by a user (for example, an administrator), and a voice input device such as a microphone. A program execution instruction from the user, various operation information, Accepts input of information for starting up software and the like.

  The output device 62 includes a display for displaying various windows, data, and the like necessary for operating the computer main body (management server 11) for performing processing in the present embodiment. The output device 62 can display program execution progress, results, and the like by a control program of the CPU 66.

  Here, in the present embodiment, for example, an execution program installed in the computer main body is provided by the recording medium 68 or the like. The recording medium 68 can be set in the drive device 63. Based on the control signal from the CPU 66, the execution program stored in the recording medium 68 is installed from the recording medium 68 into the auxiliary storage device 64 via the drive device 63.

  The auxiliary storage device 64 is storage means such as a hard disk drive (HDD) and a solid state drive (SSD). The auxiliary storage device 64 stores an execution program (notification condition generation program, transmission program) in this embodiment, a control program provided in a computer, and the like based on a control signal from the CPU 66, and performs input / output as necessary. Do. The auxiliary storage device 64 can read and write necessary information from each stored information based on a control signal from the CPU 66 and the like.

  The main storage device 65 stores an execution program read from the auxiliary storage device 64 by the CPU 66. The main storage device 65 is a Read Only Memory (ROM), a Random Access Memory (RAM), or the like.

  The CPU 66 performs processing of the entire computer such as various operations and input / output of data with each hardware component based on a control program such as an operating system (OS) and an execution program stored in the main storage device 65. Control each process. Various information necessary during the execution of the program can be acquired from the auxiliary storage device 64, and the execution result and the like can also be stored.

  Specifically, the CPU 66 executes processing corresponding to the program on the main storage device 65 by causing the program installed in the auxiliary storage device 64 to be executed based on, for example, a program execution instruction obtained from the input device 61. Do. For example, by executing the execution program, the CPU 66 receives the operation information 31 by the operation information receiving unit 21 described above, totals the operation information 31 by the totaling unit 22, and sets the notification condition 34 by the notification condition generating unit 23. Process. The CPU 66 executes processing such as transmission of various information by the transmission unit 24 and acquisition of the weather information 37 by the weather information acquisition unit 25 by executing the execution program. The processing content in the CPU 66 is not limited to the above-described content. The contents executed by the CPU 66 are stored in the auxiliary storage device 64 or the like as necessary.

  The communication device 67 communicates with other external devices via the communication networks 14-1 and 14-2 described above. The communication device 67 acquires an execution program, software, setting information, and the like from an external device or the like by connecting to the communication networks 14-1 and 14-2 based on a control signal from the CPU 66. The communication device 67 may provide an execution result obtained by executing the program to an external device, or may provide the execution program itself in the present embodiment to an external device or the like.

  The recording medium 68 is a computer-readable recording medium that stores an execution program and the like as described above. The recording medium 68 is, for example, a semiconductor memory such as a flash memory, or a portable recording medium such as a CD-ROM or DVD, but is not limited thereto.

  By installing an execution program (for example, a notification condition generation program, a transmission program, etc.) in the hardware configuration shown in FIG. 4, the hardware resource and the software cooperate to generate a notification condition generation process and a transmission process in this embodiment. Etc. can be realized. Note that the hardware configuration shown in FIG. 4 can be applied not only to the management server 11 but also to the operation manager terminal 13, for example.

<Hardware configuration example of in-vehicle device 20>
Next, a hardware configuration example of the in-vehicle device 20 described above will be described with reference to the drawings. FIG. 5 is a diagram illustrating an example of a hardware configuration of the in-vehicle device. In the example of FIG. 5, the in-vehicle device 20 includes an input device 71, an output device 72, a position sensor 73, a speed sensor 74, an auxiliary storage device 75, a main storage device 76, a CPU 77, and a communication device 78. , And a drive device 79, which are connected to each other by a system bus B.

  The input device 71 includes operation buttons operated by a user (for example, a driver or a passenger) and a voice input device such as a microphone. The input device 71 receives a program execution instruction, various operation information, software, and the like from the user. Accepts input of information to start up.

  The output device 72 includes a display for displaying various windows, data, and the like necessary for operating the computer main body (the in-vehicle device 20) for performing the processing in the present embodiment. The output device 72 can display program execution progress, results, and the like by a control program of the CPU 77.

  Here, in the present embodiment, for example, an execution program installed in the computer main body is provided by the recording medium 80 or the like. The recording medium 80 can be set in the drive device 79. Based on the control signal from the CPU 77, the execution program stored in the recording medium 80 is installed in the auxiliary storage device 75 from the recording medium 80 via the drive device 79.

  The position sensor 73 acquires position information having latitude and longitude using, for example, GPS. The method for acquiring the position information is not limited to this.

  The speed sensor 74 acquires the speed of the vehicle 12 based on the displacement of the position of the vehicle 12 every predetermined time. The speed sensor 74 may be acquired from, for example, a tachometer (rotation speed meter) that is separately mounted on the vehicle 12. The speed detection method is not limited to this. The speed sensor 74 may acquire G values in the front-rear direction, the lateral direction, and the vertical direction with respect to the vehicle 12 by an acceleration sensor such as a G sensor.

  The auxiliary storage device 75 is, for example, a storage unit such as an HDD or an SSD. The auxiliary storage device 75 stores an execution program (notification program) in this embodiment, a control program provided in a computer, and the like based on a control signal from the CPU 77, and performs input / output as necessary. The auxiliary storage device 75 can read and write necessary information from each stored information based on a control signal from the CPU 77 and the like.

  The main storage device 76 stores an execution program or the like read from the auxiliary storage device 75 by the CPU 77. The main storage device 76 is a ROM, a RAM, or the like.

  The CPU 77 controls processing of the entire computer, such as various operations and data input / output with each hardware component, based on a control program such as an OS and an execution program stored in the main storage device 76. Realize processing. Various information necessary during the execution of the program can be acquired from the auxiliary storage device 75, and the execution result and the like can also be stored.

  Specifically, the CPU 77 executes processing corresponding to the program on the main storage device 76 by causing the program installed in the auxiliary storage device 75 to be executed based on, for example, a program execution instruction obtained from the input device 71. Do. For example, by executing the notification program, the CPU 77 detects the vehicle power ON / OFF by the vehicle power control detection unit 41 described above, acquires the notification condition 51 by the notification condition acquisition unit 42, and the operation information by the operation information acquisition unit 43. 52 is obtained. In addition, the CPU 77 executes a notification program to perform processing such as traveling state determination by the traveling state determination unit 44, notification by the notification unit 45, transmission by the operation information transmission unit 46, and the like. The processing content in the CPU 77 is not limited to the above-described content. The contents executed by the CPU 77 are stored in the auxiliary storage device 75 or the like as necessary.

  The communication device 78 communicates with other external devices via the communication network 14-1. The communication device 78 acquires an execution program, software, setting information, and the like from an external device or the like by connecting to the communication network 14-1 or the like based on a control signal from the CPU 77. The communication device 78 may provide an execution result obtained by executing the program to an external device, or may provide the execution program itself in the present embodiment to an external device or the like.

  The recording medium 80 is a computer-readable recording medium that stores an execution program and the like as described above. The recording medium 80 is, for example, a semiconductor memory such as a flash memory, or a portable recording medium such as a CD-ROM or DVD, but is not limited thereto.

  By installing an execution program (for example, a notification program or the like) in the hardware configuration shown in FIG. 5, the hardware resource and the software can cooperate to implement the notification processing or the like in the present embodiment.

<Example of processing in the management server 11 (notification condition generation processing)>
Next, a processing example in the management server 11 described above will be described using a flowchart. FIG. 6 is a flowchart illustrating an example of notification condition generation processing in the management server. In the example of FIG. 6, the operation information receiving unit 21 of the management server 11 acquires the operation information of each vehicle 12 (S01). Note that the operation information 31 from each vehicle 12 acquired in the process of S01 may be stored in the storage unit 26.

  Next, the totaling unit 22 of the management server 11 performs totaling under a predetermined condition based on the operation information acquired in the process of S01 (S02). The aggregation result 33 acquired in the process of S02 may be stored in the storage unit 26. A specific example of the counting process in S02 will be described later.

  Next, the notification condition generation unit 23 of the management server 11 generates a notification condition based on the total result 33 obtained in the process of S02. For example, the notification condition generation unit 23 generates a point (for example, a point where the operation event has occurred, for example, every predetermined operation event (for example, deceleration operation such as sudden braking) for the vehicle 12 from the aggregation result 33 obtained by the aggregation process. (Intersection, T-junction), the presence / absence of a course change after the passage of the spot, the course direction, etc. are acquired (S03). Next, the notification condition generation unit 23 sets, as a notification condition, the number of occurrences of the operation event that is greater than or equal to a predetermined number (for example, 30 times) (multiple occurrence points) based on various information acquired in the process of S03. (S04). Note that the occurrence count described above is, for example, the occurrence count within a predetermined period (for example, one week, one month).

  Note that the notification condition 34 generated by the notification condition generation unit 23 in the process of S03 is associated with the respective aggregation results classified and totaled by the totaling unit 22, for example, vehicle information 35, driver information 36, and weather information 37. Notification conditions may be generated for each piece of identification information (for example, vehicle type, driver ID, weather type) corresponding to the above.

  Next, the notification condition generation unit 23 stores the generated notification condition 34 in the storage unit 26 (S04), and the process ends. As a result, in this embodiment, not only the approach to the frequent occurrence point but also the presence / absence of a change in the course of the vehicle 12 is matched, or the vehicle is scheduled to travel on the same course as the course direction, etc. It can be determined whether or not.

  In the notification condition generation process described above, the processes of S01 to S02 and the processes of S03 to S04 may be performed separately. In this case, the total result 33 obtained by the process of S02 is stored in the storage unit 26, and is referred to when executing S03 to S04.

<S02: Total processing example>
Next, an example of the counting process in S02 described above will be described using a flowchart. FIG. 7 is a flowchart illustrating an example of the aggregation process. In the example of FIG. 7, the counting unit 22 refers to the operation information 31 acquired by the process of S01 described above, and acquires one operation information when a predetermined operation event is executed (for example, at the start of the operation event). (S11). An example of the predetermined operation event is a deceleration operation such as a sudden brake, but is not limited to this.

  Next, the totaling unit 22 specifies a place (point ID) where the predetermined operation event is executed from position information (for example, latitude / longitude information) included in the operation information corresponding to the acquired predetermined operation event ( S12). For example, the point ID is obtained by referring to the road information 32 stored in advance in the storage unit 26 and acquiring the point ID associated with a map section (for example, a road section) including a predetermined area including the position of the position information. To do. Next, the totaling unit 22 performs totalization for each identified place (point ID) and each course (for example, whether or not the course has been changed or the traveling direction) after the identified place has passed (S13).

  Next, the totaling unit 22 determines whether there is an unprocessed operation event in the operation information (S14). If there is an unprocessed operation event (YES in S14), the process of S11 is performed. Return to. If there is no unprocessed operation event (NO in S14), the total result 33 is stored in the storage unit 26 (S15), and the process is terminated.

<Example of data that the management server 11 has>
Next, an example of data that the management server 11 has will be described with reference to the drawings. FIG. 8 is a diagram illustrating an example of data included in the management server. 8A shows an example of the operation information 31, FIG. 8B shows an example of the road information 32, FIG. 8C shows an example of extraction data of a predetermined operation event, and FIG. ) Is a diagram showing an example of the total result 33.

  As items of the operation information 31 shown in the example of FIG. 8A, for example, “vehicle ID”, “date and time”, “latitude”, “longitude”, “speed (km / h)”, “G value (front and back)” "," G value (horizontal) "," G value (up and down) ", etc., but is not limited thereto.

  The vehicle ID is information for identifying each vehicle. The operation information 31 of the management server 11 stores operation information of one or more vehicles 12 under the set management.

  The date and time is the date and time information when the operation information for one record (one record) is recorded. Latitude and longitude are position information corresponding to date and time information obtained from a position sensor such as GPS. The speed is speed information of the vehicle 12 obtained from a speed sensor or the like corresponding to the position information. The G value (front and rear), the G value (horizontal), and the G value (up and down) are information indicating the magnitude of acceleration in the front and rear direction, the horizontal direction, and the vertical direction of the vehicle 12 obtained from an acceleration sensor or the like. For example, an operation event such as sudden braking or sudden start can be extracted by comparing the value of G value (front and rear) with a threshold value. Further, for example, the meandering operation of the vehicle 12 can be detected by comparing the value of the G value (horizontal) with a threshold value. Note that the detection method such as sudden braking is not limited to this, and it can be acquired according to, for example, a displacement amount (deceleration amount) of a speed at a predetermined time or a predetermined distance.

  The items of the road information 32 shown in FIG. 8B include, for example, “point ID”, “start latitude”, “start longitude”, “end latitude”, “end latitude”, “end longitude”, “road section” ID "etc., but is not limited to this. The road information 32 can be, for example, a “digital road map” provided by the Japan Digital Road Map Association, but is not limited thereto, and road information such as other electronic map data. Etc. may be used.

  The point ID is information for identifying a point or section assigned to, for example, a digital road map. The start point latitude, start point longitude, end point latitude, and end point longitude are information for specifying the point or the range of the section, and can be represented by an area surrounding each point. The road section ID is information for identifying the road section including the point ID.

  As items of the extracted data of the predetermined operation event shown in the example of FIG. 8C, for example, “event ID”, “latitude”, “longitude”, “road section ID”, “speed (km / h)”, Although there are “deceleration width”, “route road section ID”, etc., it is not limited to this. In the example of FIG. 8C, the extracted data in the case where the predetermined operation event is a deceleration operation such as sudden braking is shown, but the present invention is not limited to this.

  The event ID is information for identifying each of the operation events described above. When the counting unit 22 determines that an event operation has occurred, the counting unit 22 identifies each event operation by this event ID. “Latitude” and “longitude” are position information where the event operation occurred. This position information can be acquired from the operation information 31.

  The road section ID corresponds to, for example, the road section ID of the road information 32 illustrated in FIG. The road section ID is information for identifying a road section including a place (point) of the latitude and longitude. The section may not be a road section. The speed is speed information when a predetermined operation event occurs. The deceleration width is an item corresponding to an operation event corresponding to a deceleration operation such as a sudden brake, for example. In the example of FIG. 8C, as an operation event occurrence condition, for example, a deceleration width of 10 km / h or more is used. Has been extracted.

  The course road section ID is information for identifying the course after the point where the operation event has occurred. This ID is set in correspondence with the point ID of the road information 32. The road section ID and the course road section ID described above are extracted by extracting the ID corresponding to the latitude / longitude obtained from the operation information of the vehicle 12 using the road information 32 such as electronic map data set in advance. ID information is stored. Further, the information stored in the road section ID and the route road section ID is not limited to this, and may be position information or area information using latitude / longitude, for example.

  The items of the tabulation result 33 shown in the example of FIG. 8D include, for example, “point ID”, “road section ID”, “course”, “course road section ID”, “number of times”, “notification target”, and the like. However, the present invention is not limited to this. For example, there is no “notification target”.

  The point ID corresponds to, for example, the point ID of the road information 32 shown in FIG. Note that the spot ID included in the total result 33 in FIG. 8D is information for identifying a spot where a predetermined operation event (for example, deceleration operation such as sudden braking) has occurred. The road section ID and the course road section ID are the same information as each section ID shown in FIG.

  The course is information on the course direction obtained from the relationship between the road section ID and the course road section ID. Further, the route is, for example, a route that is traveling on a road section corresponding to the road section ID, but is not limited thereto, and may be a changed advanced road when the route is changed, for example. Based on the route information, the presence / absence of the route change and the traveling direction can be acquired. The number of times is information obtained by counting extracted data having the same spot ID, road section ID, and course (or course road section ID). Information such as a flag is set as a notification target with the number of times being equal to or greater than the predetermined number as a notification target. Note that the notification condition 34 described above may be information in which only the data to be notified is collected from the aggregation result 33 illustrated in FIG. 8D, and remains as illustrated in FIG. 8D. Also good.

  For example, when the speed reduction width in a predetermined time (for example, in units of 1 second) is greater than or equal to a predetermined value (for example, 10 km / h) from the operation information illustrated in FIG. ) To obtain the extracted data. Further, the totaling unit 22 performs classification according to the course based on the subsequent route information, and in the totaling result 33, sets the number of times equal to or more than a predetermined number (for example, 30 times) as a notification target, and notifies A condition is generated (FIG. 8D).

  In the present embodiment, for example, the notification condition or the like can be variably set for each vehicle type of the vehicle 12 or for each driver who drives the vehicle 12. FIG. 9 is a diagram illustrating an example of data for variably setting the notification condition. FIG. 9A shows an example of the vehicle information 35, and FIG. 9B shows an example of the driver information 36.

  The items of the vehicle information 35 shown in the example of FIG. 9A include, for example, “vehicle ID”, “vehicle type”, “total vehicle weight (kg)”, “maximum loading capacity (kg)”, “vehicle width (mm) ) "Etc., but is not limited to this. The vehicle ID is information for identifying the vehicle 12. The vehicle type is information indicating the type of vehicle. Examples of the vehicle type include a medium-sized vehicle and a large vehicle, but are not limited thereto, and may be specific vehicle type information such as a bus or a taxi. The total vehicle weight is information indicating the weight of the vehicle 12. The maximum load capacity is information indicating the weight that the vehicle 12 can load. The vehicle width is information indicating the width (length) of the vehicle 12. In the present embodiment, the notification conditions can be classified and set for each vehicle information 35 described above. Thereby, notification can be performed under appropriate conditions for each vehicle.

  By using the vehicle information 35 shown in FIG. 9A, for example, if the vehicle weight is heavy, it is possible to perform a process of notifying earlier than the normal notification timing. In addition, since it is difficult to turn right or left at an intersection in a large vehicle than a general vehicle, the presence / absence of notification may be changed depending on the vehicle width and the total length.

  The items of the driver information 36 shown in the example of FIG. 9B include, for example, “vehicle ID”, “start date / time”, “end date / time”, “driver ID”, but are not limited thereto. . For example, the driver information 36 may include information such as the driver's years of experience and personality (for example, whether the person is apt, timid, or a person who tends to speed up).

  The vehicle ID is information for identifying the vehicle 12. The start date / time is date / time information when the driver corresponding to the driver ID starts using the vehicle 12. The end date / time is date / time information when the driver corresponding to the driver ID ends the use of the vehicle 12. The driver ID is information for identifying the driver.

  In this embodiment, drivers such as buses 12-2 and taxis 12-3 as shown in FIG. Therefore, by associating the vehicle and the driver with the driver information 36 as shown in FIG. 9B, it is possible to perform aggregation for each driver or set the notification condition by classifying for each driver. Thereby, an appropriate notification can be performed for each driver.

  As an example of generating a notification condition corresponding to a driver, for example, in the case of an experienced driver (for example, years of experience: 10 years or more), the threshold of the number of times to be notified is set high (for example, 30 times or more → 40 times) Above). In addition, for inexperienced drivers (for example, years of experience: less than 3 years), the threshold value of the number of objects to be notified can be set lower than usual (for example, 30 times or more → 20 times or more). However, the present invention is not limited to this.

  Further, in the present embodiment, the present invention is not limited to this, and it is also possible to perform weighting based on road conditions such as right turn lane presence / absence, sidewalk presence / absence, road width, right turn signal presence / absence. For example, the weight when there is a right turn lane on the ongoing road is “1”, and the weight when there is no right turn lane is “1.2”. In this case, whether or not to include in the notification condition is determined based on whether or not the value (risk level) calculated by “number of times × weight” is equal to or greater than a predetermined number. In general, when there is no right turn lane on the road, the risk of being forced to change lanes is higher, and therefore appropriate notification conditions can be generated by weighting according to such road conditions.

  In addition, the weather (for example, sunny, rain, snow, etc.) at each point obtained from the weather information 37 may affect the visibility and / or slipperiness of the road surface in the case of rain or snow, for example. Alternatively, processing such as calculating the degree of risk described above by increasing each weight may be performed. In the present embodiment, notification conditions may be generated according to time zones.

<Example of processing in management server 11 (notification condition transmission processing)>
Next, an example of processing for transmitting the above-described notification conditions and the like from the management server 11 to the vehicle 12 will be described using a flowchart.

  FIG. 10 is a flowchart illustrating an example of notification condition transmission processing in the management server. In the example of FIG. 1, the transmission unit 24 of the management server 11 determines whether or not there is an inquiry about the notification condition 34 from the vehicle 12 (S21), and when there is an inquiry (YES in S21), the storage unit The notification condition 34 (notification condition 51 shown in FIG. 3) corresponding to the vehicle information (vehicle type, vehicle weight), driver information, weather, etc. of the vehicle 12 inquired is acquired from the notification condition 34 stored in 26 (S22). ). Note that the method for acquiring the notification condition 51 is not limited to this, and for example, only the notification condition 51 corresponding to the inquired vehicle ID may be acquired.

  Next, the transmission unit 24 transmits the notification condition 51 and the like acquired in the process of S22 to the vehicle 12 that has inquired (S23). In the process of FIG. 10, the notification condition 51 is transmitted by an inquiry from the vehicle 12. However, the present embodiment is not limited to this. For example, the notification condition is updated regularly or irregularly. When performed, the notification condition 51 may be automatically transmitted to each vehicle 12. Further, in the processing of S23, the transmission unit 24 may transmit not only the notification condition 51 but also the notification data 54 in which the route information 53 including the planned traveling route information of the vehicle 12, for example, is set. .

<Example of processing in in-vehicle device 20>
Next, an example of processing (notification processing) in the in-vehicle device 20 of the present embodiment will be described using a flowchart. FIG. 11 is a flowchart illustrating an example of processing in the in-vehicle device. In the example of FIG. 11, the vehicle power supply control detection unit 41 of the in-vehicle device 20 detects the power ON of the vehicle 12 (S31). When the notification condition acquisition unit 42 of the in-vehicle device 20 acquires the detection of the power supply for the vehicle 12 by the process of S31, the notification condition acquisition unit 42 inquires the management server 11 about the notification condition 51 (S32).

  Next, the notification condition acquisition unit 42 receives the notification condition 51 via the communication network 14-1 (S33). The received notification condition 51 is stored in the storage unit 47. The inquiry about the notification condition 51 is preferably acquired before driving. The notification condition 51 may be inquired once every predetermined period, for example, and may not be inquired every time the vehicle 12 is turned on.

  Next, the operation information acquisition unit 43 acquires operation information of the vehicle 12 being driven by the driver (S34). The acquired operation information 52 is stored in the storage unit 47 and transmitted to the management server 11 at a predetermined timing. Next, the traveling state determination unit 44 of the vehicle 12 compares the current traveling information 52 and the planned traveling route included in the route information 53 stored in the storage unit 47 with the notification condition 51 (S35). It is determined whether or not the current driving situation (driver's driving) and the subsequent scheduled route (for example, whether or not the route has been changed, the direction of the route) are subject to notification such as a message or warning (S36).

  The traveling state is, for example, the behavior of the vehicle 12 due to a predetermined operation event, and the predetermined operation event is, for example, a deceleration operation such as a sudden brake, an acceleration operation such as a sudden start, a meandering operation, etc. However, the present invention is not limited to this. In the process of S36, it is determined that the current running state of the vehicle 12 and the subsequent scheduled route are objects to be notified in the vehicle 12 when the notification condition is satisfied.

  When the traveling state determination unit 44 is a notification target (YES in S36), the notification unit 45 notifies the information corresponding to the determination result (S37). The notification content can be acquired from the notification data 54 stored in the storage unit 47, but is not limited thereto. In addition, the traveling state determination unit 44 determines whether or not to end the process after the process of S37 if it is not a notification target (NO in S36) (S38) and does not end the process (NO in S38). ), The process returns to S34. The determination as to whether or not to end the process may be, for example, when the vehicle power supply control detection unit 41 of the in-vehicle device 20 detects that the vehicle 12 is turned off, but is not limited thereto. In-vehicle device 20 ends the notification process when the process ends (YES in S38).

  By the above-described processing, the vehicle 12 having the in-vehicle device 20 moves to the same route as the direction of the route change, for example, in addition to approaching a predetermined position (multi-point), whether or not the route change is matched. Appropriate notifications can be received based on whether the plan is met or not. Thereby, the driver can drive the vehicle 12 safely.

<Example of Processing in Traveling State Determination Unit 44>
Next, an example of processing in the above-described traveling state determination unit 44 will be described using a flowchart. FIG. 12 is a flowchart illustrating an example of processing in the traveling state determination unit. Note that the example of FIG. 12 corresponds to the above-described processes of S35 to S37. Further, in the following example, as an example of the notification condition, an example in which the vehicle 12 having a high probability of occurrence of a predetermined deceleration operation such as a sudden brake is illustrated, but the determination target is not limited to this. Other operation events may be targeted.

  In the example of FIG. 12, the traveling state determination unit 44 acquires the current position information of the vehicle 12 (S41). The current position information may be, for example, information on latitude and longitude that can be acquired from the operation information 52, and information on a point corresponding to the latitude and longitude (for example, a setting area such as an intersection of the point A) ( For example, point ID etc. may be sufficient. Further, the position information may be a distance from the current position to the point (for example, an intersection), an approach direction after passing the point, or the like.

  Next, the traveling state determination unit 44 compares the current position information with the notification condition 51 (S42), and determines whether or not the position of the vehicle 12 is within the notification target range (S43). In the process of S43, for example, it is possible to determine whether or not the current position is within a predetermined range from a point extracted as a point where frequent sudden braking is performed, but the present invention is not limited to this. When the vehicle 12 is within the notification target range (YES in S43), the traveling state determination unit 44 acquires route information 53 (S44). Next, the traveling state determination unit 44 determines whether or not the route road section to be notified included in the notification condition 51 exists on the planned route after passing the point included in the route information 53 (S45). . Note that, in the process of S45, for example, it may be determined whether or not there is a change in course.

  The driving state determination unit 44 determines to notify the driver when there is a route road section to be notified on the route (YES in S45) (S46). In addition, in the process of S43, the traveling state determination unit 44 is not within the notification target range (NO in S43), and in the process of S45, when the route road section to be notified does not exist on the route (NO in S45) ) Or after the process of S16, the process is terminated.

<Example of data the vehicle 12 has>
Next, the data example which the vehicle 12 has is demonstrated using figures. In addition, about operation information, since the structure similar to the operation information which the management server 11 mentioned above has can be used, detailed description here is abbreviate | omitted.

  FIG. 13 is a diagram illustrating an example of a data example included in the vehicle. FIG. 13A shows an example of the notification condition 51, and FIG. 13B shows an example of route information.

  The items of the notification condition 51 shown in FIG. 13A include, for example, “point ID”, “route”, “route road section ID”, but are not limited thereto. The notification condition 51 shown in the example of FIG. 13A is obtained by extracting only the notification target from the information (total result 33) shown in FIG. 8D described above, but the information itself shown in FIG. It may be.

  The point ID and the route road section ID may include latitude / longitude information acquired from the road information 32.

  The items of the route information 53 shown in FIG. 13B include, for example, “route ID”, “sequence number”, “road section ID”, and the like, but are not limited thereto. The “route ID” is information for identifying a route set for one destination with the vehicle 12. This ID is set in correspondence with the point ID of the road information 32. The sequence number is a number in which different road section IDs are set in the route order in the route. That is, the vehicle 12 travels on each route in order of the sequence number. Therefore, for example, when passing through the same road section (for example, in the case of a round trip route), different sequence numbers are set for the same road section ID. The traveling direction is the traveling direction when traveling along the route of the route ID. The route information 53 is set for each vehicle 12 by the management server 11.

<Specific example of notification>
Next, a specific example of notification will be described with reference to the drawings. FIG. 14 is a diagram illustrating a specific example of notification. In the example of FIG. 14, an intersection 90 is shown as an example of a predetermined area. In the example of FIG. 14A, the state of occurrence of sudden braking is acquired from the operation information for each behavior of the vehicles 12a, 12b, and 12c.

  In the example of FIG. 14A, an operation event of sudden braking has occurred in the vehicle 12a, but since this is poor in visibility due to the building 91, an operation event (deceleration operation such as sudden braking) occurs at a point 92-1. It has occurred. In this case, the management server 11 manages information that “turns left after the operation event occurs”.

  Further, when the vehicle 12c makes a right turn at the intersection 90, a sudden braking event occurs at the point 92-2. This occurs because the right turn lane is short and the behavior of the vehicle 12b ahead suddenly changes. In this case, the management server 11 manages information that “turns right after an operation event occurs”.

  The management server 11 aggregates these pieces of information and generates a notification condition using the traveling direction of the vehicle 12 after the operation event has occurred as described above. Thus, the vehicle 12 compares the current position, the future route, and the notification condition, and based on the event occurrence point, the presence / absence of the course change after the passage of the point, and the traveling direction, the driver of the vehicle 12 It is possible to give notice of danger appropriately. The content of the notification is set in advance in the notification data 54 or the like, and for example, information such as “Please be careful about driving” may be displayed on the in-vehicle device 20 or the car navigation system, or may be processed to output sound. Yes, but not limited to this.

  In the present embodiment, as shown in the example of FIG. 14B, the notification condition set based on the total result of the sudden braking points is satisfied, and the subsequent travel route (traveling direction) 93 also matches the condition. In this case, a corresponding predetermined notification is made. In the example of FIG. 14 (B), a case where a sudden braking frequent point near the intersection 90 is approached and the traveling direction after passing the sudden braking frequent point is north is a notification target. In the example of FIG. 14B, since the course is changed after passing the sudden braking frequent occurrence point, even if the condition “the course is changed” is set as a notification target.

  Further, in the present embodiment, the notification point 94 is set before (a predetermined distance before) the sudden braking frequent occurrence point. This notification point can be changed according to the vehicle type, weather, and the like. Thus, in the present embodiment, for example, when reaching a few meters before a sudden braking frequent occurrence point, a notification can be given when the direction in which the number of sudden braking occurrences by route matches the traveling route. In addition, as a specific example of the above-described notification, for example, the notification content for a deceleration operation such as a sudden brake such as “Beware of sudden braking” is not limited thereto. In addition, the above-described processing can perform appropriate notification according to each notification condition by the same processing for other operation events.

  As described above, according to the present embodiment, an appropriate notification condition is generated for each vehicle in the management server, and the generated driving condition (current position, presence / absence of route change, route direction) is generated using the generated notification condition. ) Etc., the notification accuracy can be improved. In addition, an appropriate notification can be given to the driver. Moreover, this embodiment can notify not only a driver but an operation manager via the operation manager terminal 13. Thereby, the operation state for every vehicle to manage can be grasped more appropriately.

  Although the embodiments have been described in detail above, the invention is not limited to the specific embodiments, and various modifications and changes can be made within the scope described in the claims. Moreover, it is also possible to combine a part or all of each Example mentioned above.

In addition, the following additional remarks are disclosed regarding the above Example.
(Appendix 1)
When generating a notification condition used in a notification system that performs notification according to the travel route of the vehicle, based on the travel data of the vehicle, the position of the vehicle when a predetermined operation event is performed, and the predetermined Extract the presence / absence of the course change after the operation event or the course direction,
In addition to approaching the extracted position, the computer generates a notification condition including whether or not the route change matches, or that the vehicle is scheduled to travel on the same route as the direction of the route change. Notification condition generation program to be executed.
(Appendix 2)
From the running data of the vehicle, count the number of times based on the position where the predetermined operation event was performed and the traveling direction from the position,
The notification condition generation program according to appendix 1, wherein the notification condition is generated as a target to be notified when the counted number of times is equal to or greater than a predetermined number.
(Appendix 3)
The notification condition generation program according to appendix 2, wherein the predetermined number is variably set based on at least one of driver information, vehicle information, and weather information for the vehicle.
(Appendix 4)
The notification condition generation program according to any one of appendices 1 to 3, wherein the generated notification condition is transmitted to the vehicle.
(Appendix 5)
Information processing device
When generating a notification condition used in a notification system that performs notification according to the travel route of the vehicle, based on the travel data of the vehicle, the position of the vehicle when a predetermined operation event is performed, and the predetermined Extract the presence / absence of the course change after the operation event or the course direction,
In addition to approaching the extracted position, it generates a notification condition that includes whether or not the route change matches, or that the vehicle is scheduled to travel on the same route as the direction of the route change. Notification condition generation method to be performed.
(Appendix 6)
A counting unit that counts the position of the vehicle when a predetermined operation event is performed based on travel data of the vehicle, and whether or not there is a course change after performing the predetermined operation event, or a course direction;
From the counting result obtained by the counting unit, in addition to approaching the position, notification that the presence / absence of the course change matches, or that traveling on the same course as the direction of the course change is scheduled An information processing apparatus comprising: a notification condition generation unit that generates a condition.
(Appendix 7)
In an in-vehicle device that performs notification in a vehicle when a predetermined condition is satisfied,
Based on the driving situation of the vehicle, in addition to the vehicle approaching the point set under the predetermined condition, whether or not there is a course change after passing through the point, or the direction of the course change A traveling state determination unit that determines whether or not the traveling on the same route as that matches,
An in-vehicle device, comprising: a notification unit that performs notification within the vehicle when the traveling state matches by the traveling state determination unit.

10 Notification System 11 Management Server (Information Processing Device)
DESCRIPTION OF SYMBOLS 12 Vehicle 13 Operation manager terminal 14 Communication network 20 In-vehicle apparatus 21 Operation information receiving part 22 Total part 23 Notification condition generation part 24 Transmission part 25 Weather information acquisition part 26, 47 Storage part 31, 52 Operation information 32 Road information 33 Count result 34, 51 Notification conditions 35 Vehicle information 36 Driver information 37 Weather information 41 Vehicle power supply control detection unit 42 Notification condition acquisition unit 43 Operation information acquisition unit 44 Travel condition determination unit 45 Notification unit 46 Operation information transmission unit 53 Route information 54 Notification data 61 , 71 Input device 62, 72 Output device 63, 79 Drive device 64, 75 Auxiliary storage device 65, 76 Main storage device 66, 77 CPU
67, 78 Communication device 68, 80 Recording medium 90 Intersection 91 Building 92 Point 93 Traveling route (traveling direction)
94 Notification points

Claims (4)

When generating a notification condition used in a notification system that performs notification according to a travel route of a vehicle, the number of times that a predetermined operation event is performed based on the travel data of the vehicle, the position of the vehicle, and the predetermined Totaled separately according to the presence or absence of the course change or the course direction after the operation event of
When a value obtained by multiplying the weighting coefficient according to the road condition at the position by the total number of times is a predetermined number or more, in addition to approaching the position, the presence or absence of the course change matches, or Generate a notification condition that includes planning to travel to the same route as the direction of the route change,
The notification condition is generated so that the notification timing is variable based on any one of the vehicle type, the total vehicle weight, the maximum loading capacity, and the vehicle width, and the notification condition for causing the computer to execute the process. Generation program. The notification condition generation program according to claim 1 , wherein the generated notification condition is transmitted to the vehicle. Information processing device
When generating a notification condition used in a notification system that performs notification according to a travel route of a vehicle, the number of times that a predetermined operation event is performed based on the travel data of the vehicle, the position of the vehicle, and the predetermined Totaled separately according to the presence or absence of the course change or the course direction after the operation event of
When a value obtained by multiplying the weighting coefficient according to the road condition at the position by the total number of times is a predetermined number or more, in addition to approaching the position, the presence or absence of the course change matches, or Generate a notification condition that includes planning to travel to the same route as the direction of the route change,
The notification condition generation method, wherein the notification condition is generated such that the notification timing is variable based on any one of a vehicle type, a total vehicle weight, a maximum load capacity, and a vehicle width. A totaling unit that counts the number of times that a predetermined operation event has been performed based on vehicle travel data according to the position of the vehicle and whether or not the route has changed after the predetermined operation event or the direction of the route. When,
In the case where a value obtained by multiplying the weighting coefficient according to the road condition at the position by the totaling result obtained by the totaling unit is a predetermined number or more, in addition to approaching the position, the presence / absence of the course change matches Or a notification condition generation unit that generates a notification condition that includes planning to travel to the same route as the direction of the route change,
2. The information processing apparatus according to claim 1, wherein the notification condition is generated so that the notification timing is variable based on any one of a vehicle type, a total vehicle weight, a maximum load capacity, and a vehicle width.

Images