JP2023001948A - Alert map generation server, alert device, alert system, alert map generation program, alert program - Google Patents

Abstract

To prevent attention calling from being performed when the attention calling is not necessary.SOLUTION: An information management section generates attention calling map information 600A-600E including positional information where the abnormal behavior of a vehicle has occurred by classification for each vehicle type based on attention calling information. When a transmission request is received from the vehicle, a system control section transmits the attention calling map information 600A-600E corresponding to the vehicle type of the transmission request. The system control section of an attention calling device to be mounted on the vehicle determines whether attention calling is necessary or not based on the attention calling map information 600A-600E including the positional information where the abnormal behavior of another vehicle has occurred for each vehicle type received from an attention calling map generation server, and causes the attention calling to be notified via a monitor when necessity is determined.SELECTED DRAWING: Figure 5

Description

TECHNICAL FIELD The present invention relates to an alert map generation server, an alert device, an alert system, an alert map generation program, and an alert program that perform an appropriate alert for each vehicle type.

A hazard map creation system disclosed in Patent Document 1, for example, is known as a technique for alerting the driver while the vehicle is running. This hazard map creation system uses position information acquisition means for acquiring position information of a vehicle, running condition acquisition means for detecting the running condition of the vehicle, and using the running information acquired by the running condition acquisition means, the vehicle suddenly moves. Abrupt motion determination means for determining whether or not the vehicle has occurred, and information on the occurrence or non-occurrence of the sudden motion determined by the abrupt motion determination means and position information of the vehicle acquired by the position information acquisition means are displayed on a map in association with each other. is.

JP 2020-008949 A

However, the hazard map in the hazard map creation system of Patent Document 1 described above is unified and common to all vehicle types (small commercial vehicles, taxis, ambulances, buses, trucks, etc.). In this case, depending on the type of vehicle, vehicle conditions such as the number of occupants, cargo, etc. differ from one another, so there are cases where the attention is called even when it is not necessary.

The present invention has been made in view of such circumstances, and provides an alert map generation server, an alert device, an alert system, an alert map generation program, and an alert program that can solve the above problems. intended to provide

The alert map generation server of the present invention is a alert map generation server provided with an alert management device, and the alert management device includes a first storage means, an information management unit, and a communication line to connect a vehicle to a vehicle. A first method for instructing the information management unit to manage the alert information and to generate the alert map information based on the alert information when the alert information having the vehicle status information including the type is received. a system control unit, wherein the information management unit generates, based on the alert information, alert map information including location information at which an abnormal behavior of the vehicle has occurred, for each vehicle type; 1 storage means, and when receiving a transmission request from the vehicle, the first system control unit transmits the alert map information suitable for the vehicle type of the transmission request. Characterized by
The attention calling device of the present invention is an attention calling device mounted on a vehicle, wherein the attention calling device generates an abnormal behavior of the other vehicle for each vehicle type received from a monitor and an attention calling map generation server. and a second system control unit that determines whether or not to call attention based on the alert map information including the position information obtained from the system, and notifies the user of the attention via the monitor if it determines that it is necessary. characterized by
The alerting system of the present invention receives alerting information having vehicle status information including vehicle type via a communication line, manages the alerting information in an information management unit, and issues an alert based on the alerting information. a first system control unit for instructing generation of alert map information; and the information management unit generates the alert map information including location information at which the abnormal behavior of the vehicle occurred based on the alert information. It is generated separately for each vehicle type, stored in the first storage means and managed, and when the first system control unit receives a transmission request from the vehicle, the transmission request matches the vehicle type of the transmission request. an alert management device on the alert map generation server side that transmits the alert map information; a monitor; a second system control unit that determines whether or not a warning is necessary based on the warning map information included therein, and notifies the warning via the monitor if it is determined to be necessary, and is mounted on the vehicle; and an alerting device.
The caution map generation program of the present invention receives the caution information having the vehicle status information including the vehicle type via the communication line by the first system control unit, and sends the caution information to the information management unit. a step of instructing management and generation of alert map information based on the alert information, and, upon receiving a transmission request from a vehicle, transmitting the alert map information matching the vehicle type of the transmission request; The information management unit generates, based on the alert information, alert map information including position information at which the abnormal behavior of the vehicle has occurred, for each vehicle type, and stores the alert map information in the first storage means. and the step of managing by a computer that controls the alert management device on the alert map generation server side.
The attention calling program of the present invention includes the step of notifying the attention by the monitor, and the location information of the abnormal behavior of the other vehicle for each vehicle type received from the attention calling map generation server by the second system control unit. A computer that controls an attention calling device mounted on the vehicle; It is characterized by executing
In the alert map creation server, alert device, alert system, alert map creation program, and alert program of the present invention, the first system control unit of the alert management device on the alert map creation server side is connected to the communication line. , and the information management unit, based on the alert information, creates alert map information including location information that caused abnormal vehicle behavior for each vehicle type. When the first system control unit receives a transmission request from a vehicle, it transmits the alert map information that matches the vehicle type of the transmission request.
The second system control unit of the attention calling device mounted on the vehicle, based on the attention calling map information including the location information that caused the abnormal behavior of the other vehicle for each vehicle type received from the calling attention map generation server, It is determined whether or not a warning is necessary, and if it is determined to be necessary, the warning is notified via a monitor.

According to the alert map generation server, alert device, alert system, alert map creation program, and alert program of the present invention, the second system control unit of the alert device receives from the alert map generation server Based on the alert map information including the location information of the abnormal behavior of other vehicles for each vehicle type, it is determined whether or not the alert is necessary, and if it is determined to be necessary, the alert is notified via the monitor. It is possible to prevent the alerting from being performed even when the alerting is unnecessary.

BRIEF DESCRIPTION OF THE DRAWINGS It is a figure for demonstrating the outline|summary of the alerting system of this invention. It is a figure for demonstrating the structure of the attention calling management apparatus by the side of the attention calling server of FIG. 1, and the attention calling apparatus by the side of a vehicle. FIG. 2 is a diagram showing an example of a display, etc. of a monitor on the vehicle side of FIG. 1; FIG. FIG. 2 is a diagram showing an example of alert information including vehicle status information and abnormal behavior information transmitted from each vehicle in FIG. 1 to an alert server. It is a figure which shows an example of the alerting map information which the alerting server of FIG. 1 produces|generates. FIG. 2 is a flowchart showing an example of preparation for acquisition and display processing of alert map information on the vehicle side in FIG. 1 ; FIG. FIG. 2 is a flowchart showing an example of abnormal behavior information acquisition processing on the vehicle side in FIG. 1 ; FIG. 4 is a flow chart showing an example of processing for generating and transmitting alert map information on the alert server side of FIG. 1; FIG. 2 is a flowchart showing an example of notification processing for calling attention on the vehicle side in FIG. 1 ; FIG.

An embodiment of the alerting system of the present invention will be described below.
As shown in FIG. 1, the alert system includes an alert management device 300 provided on the alert server 100 side and shown in FIG. Arousing device 400 is provided.

The alert management device 300 manages the alert information 500A to 500E including the vehicle status information 510 and the abnormal behavior information 520 shown in FIG. 4 which will be described later and received from each vehicle, separately for each vehicle type. Further, based on the alert information 500A to 500E, the alert management device 300 generates alert map information 600A to 600E for each vehicle type shown in FIG. 5 which will be described later.

The alert management device 300 transmits the generated alert map information 600A to 600E for each vehicle type to each vehicle that has requested transmission. The attention calling device 400 of each vehicle judges whether or not it is necessary to call attention based on the attention calling map information 600A to 600E for each vehicle type. As examples of vehicles shown in FIG. 1, small commercial vehicles, taxis, ambulances, buses, and trucks are targeted, but special vehicles such as passenger cars and truck cranes may also be targeted.

Next, with reference to FIG. 2, configurations of the alert management device 300 and the alert device 400 will be described.

The alert management device 300 on the alert server 100 side has a system control unit 310 . A ROM (Read Only Memory) 312 , a RAM (Random Access Memory) 313 , an information management section 314 , an external storage device 315 and an antenna 316 are connected to a bus 311 of the system control section 310 .

A system control unit 310 controls the operation of each unit. Further, when the system control unit 310 receives the alert information 500A to 500E from each vehicle, the information management unit 314 manages the alert information 500A to 500E and alerts based on the alert information 500A to 500E. It instructs to generate map information 600A to 600E. When system control unit 310 receives a transmission request for alert map information 600A to 600E from any vehicle, system control unit 310 transmits alert map information 600A to 600E that matches the vehicle type of the transmission request.

A bus 311 is composed of a system bus, a data bus, an address bus, and the like. The ROM 312 stores a procedure for controlling the operation of each unit, a control program for checking the operation of each unit, and the like. A RAM 313 is a work memory for executing programs.

Information management unit 314, in accordance with instructions from system control unit 310, divides alert information 500A to 500E including vehicle status information 510 and abnormal behavior information 520 shown in FIG. management. Further, based on the alert information 500A to 500E, the information management unit 314 generates alert map information 600A to 600E shown in FIG. 5, which will be described later, and manages them by vehicle type. Further, the information management unit 314 causes the external storage device 315 to store the alert information 500A to 500E and the alert map information 600A to 600E divided by vehicle type. Note that the information management unit 314 may manage the alert information 500A to 500E divided by vehicle type, further divided by the number of passengers and cargo information of the vehicle status information 510 .

Here, the alert information 500A and the alert map information 600A correspond to small commercial vehicles, the alert information 500B and the alert map information 600B correspond to taxis, and the alert information 500C and the alert map information 600C correspond to ambulances. Correspondingly, the alert information 500D and the alert map information 600D correspond to the bus, and the alert information 500E and the alert map information 600E correspond to the truck.

The external storage device 315 stores the alert information 500A to 500E received from each vehicle, the alert map information 600A to 600E generated by the information management unit 314, and the like. The antenna 316 exchanges information with the attention calling device 400 of each vehicle via a communication line such as the Internet.

Each vehicle-side attention calling device 400 has a system control unit 410 . The bus 411 of the system control unit 410 includes an antenna 412, a GPS (Global Positioning System) module 413, a vehicle speed acquisition unit 414, an engine speed acquisition unit 415, an acceleration sensor 416, an angular velocity sensor 417, a weight sensor 418, a ROM 419, and an EEPROM. (Electrically Erasable Programmable Read-Only Memory) 420 and a monitor 421 are connected.

A system control unit 410 controls the operation of each unit. In addition, when an abnormal behavior occurs in the vehicle, the system control unit 410 detects the value detected by the GPS module 413, the value obtained by the vehicle speed obtaining unit 414, the value obtained by the engine speed obtaining unit 415, the value detected by the acceleration sensor 416, and the angular velocity. Either the detection value of the sensor 417 or the detection value of the weight sensor 418 is stored in the EEPROM 420 until the abnormal behavior converges. Note that system control unit 410 may continuously store detected values and acquired values in EEPROM 420 from the occurrence of the abnormal behavior to the time it converges, or store them at intervals of 0.5 seconds, for example. may In addition, the system control unit 410 may store the detected values and acquired values from the occurrence of the abnormal behavior until it converges, including the detected values and acquired values immediately before the occurrence of the abnormal behavior.

A bus 411 is composed of a system bus, a data bus, an address bus, and the like. The antenna 412 exchanges information with the alert management device 300 on the alert server 100 side via a communication line such as the Internet. The GPS module 413 receives signals from GPS satellites and acquires position information such as latitude and longitude. Note that the GPS module 413 may acquire position information indicating the orientation. Vehicle speed acquisition unit 414 acquires the vehicle speed from an ECU (Electronic Control Unit) of each vehicle, for example, via an OBD2 (On Board Diagnosis second generation) connector or the like. Note that the vehicle speed acquisition unit 414 may acquire the vehicle speed from the GPS module 413 when the GPS module 413 has a function of calculating the vehicle speed.

An engine speed acquisition unit 415 acquires, for example, the engine speed from the ECU of each vehicle via an OBD2 connector or the like. Acceleration sensor 416 detects changes in velocity per unit time. The detection result of acceleration sensor 416 can be used, for example, to determine whether or not sudden braking has occurred. Angular velocity sensor 417 detects the rotational angular velocity of the vehicle. The detection result of angular velocity sensor 417 can be used, for example, to determine the presence or absence of occurrence of lateral vibration. Weight sensor 418 detects the gross weight of the vehicle. The detection result of weight sensor 418 can be used, for example, to determine whether or not vibration occurs. A strain gauge or the like can be used as the weight sensor 418 . The weight sensor 418 is attached to, for example, the suspension of each vehicle, and detects the movement according to the load of the suspension, thereby detecting the weight change of each vehicle.

The ROM 419 stores a procedure for controlling the operation of each unit, a control program for checking the operation of each unit, and the like. EEPROM420 is rewritable non-volatile memory. The EEPROM 420 stores values detected by the GPS module 413, values obtained by the vehicle speed obtaining unit 414, values obtained by the engine speed obtaining unit 415, values detected by the acceleration sensor 416, values detected by the angular velocity sensor 417, values detected by the weight sensor 418, It stores attention calling information 500A to 500E shown in FIG. 4, which will be described later, and attention calling map information 600A to 600E shown in FIG. 5, which will be described later. Note that the nonvolatile memory is not limited to the EEPROM 420, and other memory such as a USB memory or a memory card may be used. The monitor 421 is of a touch panel type. The monitor 421 displays information related to alerting, and accepts input of the vehicle status information 510 and the like by touch operation, requests for transmission of the alerting map information 600A to 600E, and the like. Note that the monitor 421 may have a speaker.

Next, an example of the display of the monitor 421 on the vehicle side will be described with reference to FIG. The monitor 421 has a map display field 430, an information input field 440 for inputting the vehicle status information 510 shown in FIG. 4, which will be described later, and a history of occurrence of abnormal behavior based on the alert map information 600A to 600E shown in FIG. 5, which will be described later. , and a display column 460 for displaying the notification contents of alerting and the map display scale. The display of the monitor 421 can be switched by touching a switching button (not shown). Note that switching of the display on the monitor 421, selection input of information, and the like may be performed by remote control operation.

A map corresponding to the map display scale selected in the display field 460 is displayed in the map display field 430 . On the displayed map, a * mark indicating a sudden braking caution based on the caution calling map information 600A to 600E, a ☆ mark indicating a rolling caution, and the like are displayed. It should be noted that the types of marks to be displayed can be changed as appropriate.

The information input field 440 is provided with an input field 440a for inputting the vehicle type and target period, a check box 440b and an input field 440c for inputting the vehicle status, and a send button 440d. When entering a vehicle type in the input field 440a, the applicable vehicle type is selected from a pull-down list displayed by touching a triangular mark, for example. When entering the target period in the input field 440a, the corresponding target period is selected from the pull-down list displayed by the touch operation in the same manner as described above. Note that the term "target period" means that the attention alert map information 600A to 600E in FIG. For example, as shown in the figure, if the start is set to 2020/01/01 and the end is set to 2021/12/03, the alert map information 600A to 600E generated within that period can be received from the alert server 100. can be done.

The check box 440b and the input field 440c can select the contents of the vehicle status by touch operation. The applicable check box 440b is touch-operated, and the applicable number of passengers and cargo type are selected from the pull-down list displayed in the applicable input field 440c. Send button 440d is touched when requesting alert server 100 to send alert map information 600A to 600E. When the send button 440 d is touched, the request attached information indicating the vehicle type, target period, and vehicle status entered in the input field 440 a is included in the send request and sent to the alert server 100 . Note that the alert information 500A to 500E transmitted to the alert server 100 is stored in the EEPROM 420 in accordance with the operation of the send button 440d.

The abnormal behavior history display column 450 displays the date and time of occurrence of an event such as sudden braking and the content of the event based on the alert map information 600A to 600E corresponding to the vehicle type received from the alert server 100. . Further, the abnormal behavior history display column 450 displays the contents of other occurrence events by touching the scroll button indicated by the triangular mark. The display column 460 displays the content of notification of abnormal behavior and the map display scale.

Next, an example of alert information 500A to 500E transmitted from each vehicle to the alert server 100 will be described with reference to FIG. For convenience of explanation, the following description assumes that the abnormal behavior information 520 includes all acquired values and detected values.

The alert information 500A to 500E includes vehicle status information 510 and abnormal behavior information 520. FIG. The vehicle status information 510 is the content input on the monitor 421 in FIG. 3, and includes vehicle type, number of passengers, and cargo information. The abnormal behavior information 520 includes the detected value of the GPS module 413 of the attention calling device 400 of each vehicle, the obtained value of the vehicle speed obtaining unit 414, the obtained value of the engine speed obtaining unit 415, the detected value of the acceleration sensor 416, and the angular velocity sensor. 417 detection value and weight sensor 418 detection value are included. These acquired values and detected values indicate that acquisition and detection were performed when abnormal behavior occurred on the vehicle side. In other words, when these acquired values and detected values change abruptly with respect to the values immediately before the occurrence of the abnormal behavior, it means that the abnormal behavior has occurred.

Further, each of the detected values and acquired values included in the abnormal behavior information 520 may be continuous values from the occurrence of the abnormal behavior of the vehicle until it converges, as described above. It may be a value in seconds interval. Further, each detected value and acquired value included in the abnormal behavior information 520 may include the detected value and acquired value immediately before the occurrence of the abnormal behavior, as described above.

Next, referring to FIG. 5, an example of the alert map information 600A to 600E for each vehicle type generated by the information management unit 314 of the alert management device 300 based on the alert information 500A to 500E will be described. Note that, hereinafter, the same reference numerals are given to the same contents as those of the alerting information 500A to 500E in FIG. 4, and overlapping explanations will be omitted. Further, the content of notification information 620 included in alert map information 600A to 600E includes, for example, speed caution, downhill caution, sudden braking caution, rolling caution, vibration caution, and the like. In addition, the alert map information 600A and 600E will be described below. Also, in the following description, a rapid change means a change of a certain amount or more from the value immediately before the occurrence of the abnormal behavior.

The alert map information 600A, 600E includes vehicle condition information 510, judgment position information 610, abnormal behavior information 520, and notification information 620. FIG. The determined position information 610 is information indicating a position, for example, 700 m before the position indicated by the position information of the point where the abnormal behavior occurred in the abnormal behavior information 520 . Based on this judgment position information 610, the attention calling device 400 on the vehicle side judges whether or not it is necessary to call attention 700 m before the point where the abnormal behavior occurred. It is possible to report that abnormal behavior occurred at the previous point. Note that the determined position information 610 is not limited to indicating the position 700 m before, and can be changed as appropriate.

The notification information 620 of the alert map information 600A and 600E is notification content generated by the information management unit 314 based on the abnormal behavior information 520. FIG. In other words, the notification contents of the "abnormal behavior occurrence range" in the alert map information 600A and 600E are contents indicating the section based on the position information from when the abnormal behavior occurs until it converges.

The notification information 620 of the caution map information 600A includes notification contents such as "speed warning", "sudden braking warning", and "rolling warning". The notification content of "speed warning" is based on the fact that the vehicle speed of the abnormal behavior information 520 exceeds the speed at which the accident occurred in the past. The content of the notification of “caution for sudden braking” is based on the sudden change in the acceleration value of the abnormal behavior information 520 . The content of the notification of “warning of rolling” is based on the sudden change in the value of the angular velocity of the abnormal behavior information 520 .

The notification information 620 of the alert map information 600E includes notification contents such as "beware of downhill" and "beware of vibration". The content of the notification of "warning downhill" is based on the sudden change in the value of the vehicle speed and the value of the engine speed in the abnormal behavior information 520 . In other words, if the speed is above a certain level even if the engine speed is below a certain level, it can be understood that the vehicle is going downhill. Note that when the engine speed is below a certain level even if the engine speed is above a certain level, the content of the notification is "beware of going uphill". The notification content of "vibration caution" is based on the sudden change in the values of the vehicle weight and the vehicle speed in the abnormal behavior information 520 .

Next, with reference to FIG. 6, preparation for acquiring and display processing of the alert map information 600A to 600E on the vehicle side will be described.

(Step S010)
System control unit 410 determines whether or not there is vehicle type selection.
In this case, when the touch operation of the vehicle type in the input field 440a of the monitor 421 cannot be confirmed, the system control unit 410 determines that the vehicle type is not selected (step S010: No).
On the other hand, the system control unit 410 can confirm the touch operation of the vehicle type in the input field 440a of the monitor 421, and confirms that the corresponding vehicle type has been selected from the pull-down list displayed by touching the triangular mark. If so, it is determined that the vehicle type has been selected (step S010: Yes), and the process proceeds to step S011.

(Step S011)
The system control unit 410 determines whether or not the target period has been selected.
In this case, if the touch operation for the target period in the input field 440a cannot be confirmed, the system control unit 410 determines that the target period is not selected (step S011: No).
On the other hand, the system control unit 410 can confirm the touch operation of the target period in the input field 440a, and select the corresponding start and end from the pull-down list displayed by touching the triangular mark of the target period. is selected, it is determined that the target period has been selected (step S011: Yes), and the process proceeds to step S012.

(Step S012)
System control unit 410 determines whether or not there is a vehicle condition selection.
In this case, if the touch operation in the check box 440b and the input field 440c for selecting and inputting the vehicle condition cannot be confirmed, the system control unit 410 determines that the vehicle condition is not selected (step S012: No).
On the other hand, the system control unit 410 can confirm the touch operation of the corresponding check box 440b in the check box 440b and the input field 440c, and select the number of passengers and cargo type from the pull-down list displayed in the corresponding input field 440c. If the selection is confirmed, it is determined that the vehicle status has been selected (step S012: Yes), and the process proceeds to step S013.

(Step S013)
System control unit 410 determines whether or not send button 400d has been operated.
In this case, if the touch operation of the send button 440d cannot be confirmed, the system control unit 410 determines that the send button 400d has not been operated (step S013: No).
On the other hand, when the touch operation of the send button 440d can be confirmed, the system control unit 410 determines that the send button 400d has been operated (step S013: Yes), and proceeds to step S014.

(Step S014)
System control unit 410 transmits to alert server 100 a transmission request for alert map information 600A to 600E.
In this case, the system control unit 410 causes the transmission request to include the request attached information indicating the vehicle type, target period, and vehicle status entered in the input field 440a.
Also, the system control unit 410 causes the EEPROM 420 to store the request attached information together with the transmission request.

(Step S015)
System control unit 410 determines whether or not the requested alert map information 600A to 600E has been received.
In this case, the system control unit 410 waits until the alert map information 600A to 600E is received (step S015: No), and upon confirming that the alert map information 600A to 600E has been received (step S015: Yes), step Move to S016.
Note that the alert map information 600A to 600E requested to be transmitted is information corresponding to the vehicle type included in the transmission request.

(Step S016)
System control unit 410 displays the received alert map information 600A to 600E.
In this case, as shown in FIG. 3, the system control unit 410 notifies the user of the warning by displaying a star mark indicating a sudden braking warning and a star mark indicating a roll warning in the map display field 430. . In addition, the system control unit 410 causes the abnormal behavior history display field 450 to display an event that occurred during the selected target period, such as sudden braking. Further, the system control unit 410 causes the display field 460 to display the contents of notification of the abnormal behavior. Note that the details of the notice of the alert by the system control unit 410 will be described in the notice processing of the alert of FIG. 9 which will be described later.

Next, with reference to FIG. 7, acquisition processing of the abnormal behavior information 520 on the vehicle side will be described.
(Step S101)
The system control unit 410 waits until the power of the attention calling device 400 is turned on (step S101: No), and when confirming that the power of the attention calling device 400 is turned on (step S101: Yes), the process proceeds to step S102. Transition.
Note that when the power is turned on, the system control unit 410 starts monitoring values acquired and detected by the vehicle speed acquisition unit 414, the engine speed acquisition unit 415, the acceleration sensor 416, the angular velocity sensor 417, and the weight sensor 418. .

(Step S102)
System control unit 410 determines whether the location information has changed abruptly.
In this case, if the system control unit 410 cannot confirm a rapid change in the detection value of the GPS module 413, it determines that an abnormal behavior has not occurred (step S102: No), and proceeds to step S104.
On the other hand, if the system control unit 410 can confirm a rapid change in the detection value of the GPS module 413, it determines that an abnormal behavior has occurred (step S102: Yes), and proceeds to step S103.

(Step S103)
The system control unit 410 stores the location information detected by the GPS module 413 in the EEPROM 420 until the abnormal behavior converges.

(Step S104)
System control unit 410 determines whether the vehicle speed has changed abruptly.
In this case, if the system control unit 410 cannot confirm a rapid change in the value acquired by the vehicle speed acquisition unit 414, it determines that an abnormal behavior has not occurred (step S104: No), and proceeds to step S106.
On the other hand, if the system control unit 410 can confirm a rapid change in the value acquired by the vehicle speed acquisition unit 414, it determines that an abnormal behavior has occurred (step S104: Yes), and proceeds to step S105.

(Step S105)
System control unit 410 causes EEPROM 420 to store the value obtained by vehicle speed obtaining unit 414 until the abnormal behavior converges.

(Step S106)
System control unit 410 determines whether the engine speed has changed abruptly.
In this case, if the system control unit 410 cannot confirm a rapid change in the value acquired by the engine speed acquisition unit 415, it determines that abnormal behavior has not occurred (step S106: No), and proceeds to step S108. .
On the other hand, if the system control unit 410 can confirm a rapid change in the value acquired by the engine speed acquisition unit 415, it determines that an abnormal behavior has occurred (step S106: Yes), and proceeds to step S107.

(Step S107)
System control unit 410 causes EEPROM 420 to store the value obtained by engine speed obtaining unit 415 until the abnormal behavior converges.

(Step S108)
System control unit 410 determines whether the acceleration has changed abruptly.
In this case, if the system control unit 410 cannot confirm a rapid change in the detection value of the acceleration sensor 416, it determines that an abnormal behavior has not occurred (step S108: No), and proceeds to step S110.
On the other hand, if the system control unit 410 can confirm a rapid change in the detection value of the acceleration sensor 416, it determines that an abnormal behavior has occurred (step S108: Yes), and proceeds to step S109.

(Step S109)
System control unit 410 causes EEPROM 420 to store the detection value of acceleration sensor 416 until the abnormal behavior converges.

(Step S110)
System control unit 410 determines whether the angular velocity has changed abruptly.
In this case, if the system control unit 410 cannot confirm a rapid change in the detection value of the angular velocity sensor 417, it determines that an abnormal behavior has not occurred (step S110: No), and proceeds to step S112.
On the other hand, if the system control unit 410 can confirm a rapid change in the detection value of the angular velocity sensor 417, it determines that an abnormal behavior has occurred (step S110: Yes), and proceeds to step S111.

(Step S111)
The system control unit 410 stores the detection value of the angular velocity sensor 417 in the EEPROM 420 until the abnormal behavior converges.

(Step S112)
System control unit 410 determines whether the vehicle weight has changed abruptly.
In this case, if the system control unit 410 cannot confirm a rapid change in the detection value of the weight sensor 418, it determines that an abnormal behavior has not occurred (step S112: No), and proceeds to step S114.
On the other hand, if the system control unit 410 can confirm a rapid change in the detection value of the weight sensor 418, it determines that an abnormal behavior has occurred (step S112: Yes), and proceeds to step S113.

(Step S113)
System control unit 410 causes EEPROM 420 to store the detection value of weight sensor 418 until the abnormal behavior converges.

(Step S114)
System control unit 410 determines whether there is an abnormal behavior.
In this case, the system control unit 410 determines that an abnormal behavior has occurred if a rapid change in the acquired or detected values of the vehicle speed, engine speed, acceleration, angular velocity, and vehicle weight can be confirmed (step S114: No), the process proceeds to step S102.
On the other hand, if the system control unit 410 cannot confirm a rapid change in each acquired value or detected value, it determines that there is no abnormal behavior (step S114: Yes), and proceeds to step S115.

(Step S115)
System control unit 410 transmits alert information 500A to 500E including abnormal behavior information 520 to alert server 100 .

In step S102, although a sudden change in position information could not be confirmed, a sudden change in any of the vehicle speed, engine speed, acceleration, angular velocity, and vehicle weight acquired or detected could be confirmed. In this case, the position information may be stored together with the storage of the acquired value or detected value that could be confirmed first. Further, when storing the position information, the engine speed, the acceleration, the angular velocity, and the vehicle weight, as described above, the detected value or the obtained value immediately before the occurrence of the abnormal behavior may be stored.

Next, with reference to FIG. 8, an example of processing for generating and transmitting the alert map information 600A to 600E on the alert server 100 side will be described.

(Step S201)
System control unit 310 determines whether or not alert information 500A to 500E has been received.
In this case, the system control unit 310 waits until it receives the alert information 500A to 500E (step S201: No), and when it receives the abnormal behavior information 520 (step S201: Yes), proceeds to step S202.

(Step S202)
The system control unit 310 instructs the information management unit 314 to store the received alert information 500A to 500E and to generate the alert map information 600A to 600E based on the alert information 500A to 500E.
Here, as shown in FIG. 4, the information management unit 314 manages the alerting information 500A to 500E received from each vehicle separately for each vehicle type.
Further, information management unit 314 proceeds to generate alert map information 600A-600E based on alert information 500A-500E. The information management unit 314 generates notification contents based on the abnormal behavior information 520 of the alert information 500A to 500E, as described above. In this case, the information management unit 314, if any of the acquired value or detected value of vehicle speed, engine speed, acceleration, angular velocity, or vehicle weight has a sudden change below a certain level, It is also possible not to generate notification content based on the detected value.

(Step S203)
System control unit 310 determines whether generation of alert map information 600A to 600E by information management unit 314 has been completed.
In this case, the system control unit 310 determines that the generation of the attention map information 600A to 600E has not been completed unless there is a notification indicating the completion of generation from the information management unit 314 (step S203: No).
On the other hand, the system control unit 310 determines that the generation of the alert map information 600A to 600E has been completed if there is a notification indicating the completion of generation from the information management unit 314 (step S203: Yes), and step S204. transition to

(Step S204)
System control unit 310 determines whether or not there is a transmission request for alert map information 600A to 600E.
In this case, if there is no transmission request from each vehicle, the system control unit 310 waits (step S204: No), and when confirming that there is a transmission request from each vehicle, the process proceeds to step S205.
Here, as described in FIG. 4, the transmission request from each vehicle includes request attached information indicating the content entered in the input field 440a of the monitor 421, such as the vehicle type, the target period, and the vehicle status. there is

(Step S205)
System control unit 310 transmits alert map information 600A to 600E to vehicles that have requested transmission.
The system control unit 310 transmits the alert map information 600A to 600E corresponding to the specified target period and vehicle type to the vehicle that requested the transmission.
At this time, on the alerting device 400 side of each vehicle, the system control unit 410 causes the EEPROM 420 to store the alerting map information 600A to 600E received from the alerting server 100 .

Note that in step S202, the information management unit 314 manages the alert information 500A to 500E received from each vehicle separately for each vehicle type. Furthermore, the vehicle status information 510 may be managed separately for each number of passengers and cargo information.

Further, in step S205, the alert map information 600A to 600E corresponding to the target period and vehicle type specified by the system control unit 310 is transmitted to the vehicle that requested the transmission. In addition to the alert information 500A to 500E, the alert map information 600A to 600E divided according to the number of passengers and cargo information of the vehicle condition information 510 may be transmitted to the vehicle that requested the transmission.

Next, with reference to FIG. 9, the notification process for calling attention on each vehicle will be described. In the following description, the values detected by the GPS module 413, the values obtained by the vehicle speed obtaining unit 414, the values obtained by the engine speed obtaining unit 415, and the detection values by the acceleration sensor 416 are described while the system control unit 410 is running. value, the detection value of the angular velocity sensor 417, and the detection value of the weight sensor 418 are always checked.

Further, in the following description, for example, a light commercial vehicle issues a transmission request to alert server 100 and receives alert map information 600A of FIG. In addition, the number of alert map information 600A received from the alert server 100 is, for example, from 2020/01/01 to 2021/12/03 entered in the target period of the input field 440a of the monitor 421. For example, 100 described as. In addition, it is assumed that notification information 620 of alert map information 600A includes notification contents such as speed warning, sudden braking warning, and rolling warning, as shown in the figure.

(Step S401)
The system control unit 410 waits until the power of the attention calling device 400 is turned on (step S401: No), and when confirming that the power of the attention calling device 400 is turned on (step S401: Yes), the process proceeds to step S402. Transition.

(Step S402)
System control unit 410 reads alert map information 600A stored in EEPROM 420 .

(Step S403)
System control unit 410 determines whether or not the point is a warning point.
In this case, the system control unit 410 determines that the location is not a location for attention when the location information indicated by the determination location information 610 of the attention-activation map information 600A read from the EEPROM 420 does not match the location information detected by the GPS module 413. (Step S403: No).
On the other hand, if the position information indicated by the determined position information 610 of the caution map information 600A read from the EEPROM 420 matches the position information detected by the GPS module 413, the system control unit 410 determines that it is the caution point. It judges (step S403: Yes), and moves to step S404.

(Step S404)
System control unit 410 determines whether or not attention is required.
In this case, system control unit 410 checks notification information 620 of, for example, 100 alerting map information 600A, and if none of alerting map information 600A includes the alert content indicated by alerting information 620, alert It is determined that arousal is not necessary (step S404: No).
On the other hand, if any of the alert map information 600A includes the notification content indicated by the notification information 620, the system control unit 410 determines that an alert is necessary (step S404: Yes), and Move to S405.

(Step S405)
System control unit 410 determines whether or not it is a speed alert.
In this case, if the alert information 620 of the alert map information 600A does not include the notification content of the speed alert, the system control unit 410 determines that it is not the speed alert (step S405: No), and Move to S407.
On the other hand, if the alert information 620 of the alert map information 600A includes the alert content of the speed alert, the system control unit 410 determines that the alert is about the speed (step S405: Yes), The process proceeds to step S406.

(Step S406)
System control unit 410 notifies speed warning via monitor 421 .

(Step S407)
System control unit 410 determines whether or not the warning is for sudden braking.
In this case, when the notification information 620 of the caution map information 600A does not include the notification content of the warning of sudden braking, the system control unit 410 determines that the warning is not of the sudden braking (step S407: No). , the process proceeds to step S409.
On the other hand, when the notification information 620 of the caution map information 600A includes the notification contents of the warning of sudden braking, the system control unit 410 determines that the warning is of the sudden braking (step S407:
Yes), go to step S408.

(Step S406)
System control unit 410 notifies a sudden braking warning via monitor 421 .

(Step S409)
System control unit 410 determines whether or not there is a warning for rolling.
In this case, if the notification information 620 of the caution map information 600A does not include the notification content of the rolling caution, the system control unit 410 determines that it is not the rolling caution (step S409: No). , terminate the process.
On the other hand, if the notification information 620 of the caution map information 600A includes the notification content of the alert for rolling, the system control unit 410 determines that the alert is for rolling (step S409: Yes). ), and the process proceeds to step S410.

(Step S410)
The system control unit 410 notifies the roll caution via the monitor 421 .

In step S404, system control unit 410 determines that an alert is necessary if any of alert map information 600A includes the alert content indicated by alert information 620. It may be determined whether or not a warning is necessary by comparing with the stored vehicle condition information 510 of the own vehicle.

That is, when the content of notification is included and the number of passengers and cargo information in the vehicle status information 510 are the same, it may be determined that a warning is necessary. Also, even if the notification content is included, the number of passengers and cargo information in the vehicle status information 510 of the own vehicle stored in the EEPROM 420 are different (the number of passengers and the number of cargo may be different). In some cases, it may be determined that calling attention is not necessary. In this way, by including the vehicle status information 510 in determining whether or not a warning is necessary, it is possible to improve the accuracy of the determination.

In step S402, when the system control unit 410 reads the caution map information 600A stored in the EEPROM 420, the warning map information 600A is divided into the EEPROM 420 according to the vehicle type, and further divided according to the number of passengers and cargo information of the vehicle status information 510. When the alerting map information 600A is stored, the alerting map information 600A divided according to the number of passengers and cargo information may be read. In this case, the number of pieces of alert map information 600A required for confirmation can be narrowed down, and it is possible to quickly determine whether or not alert is necessary.

In addition, a function of changing the accuracy of determination by the system control unit 410 may be added in determining whether or not attention is necessary in step S404. Specifically, for example, the accuracy of judgment can be set to two levels, and if the accuracy is set to high, for example, 20 cases of notification contents such as "speed warning" are included in the 100 cases of caution map information 600A. If it is less than that, it may not be possible to call attention to "beware of speed". Further, when the accuracy is set to be low, if there are 20 or more cases of "speed warning", "speed warning" may be called.

Further, system control unit 410, even if, for example, 20 or more items of alert map information 600A include the notification content of speed caution, when an abnormal behavior occurs, system control unit 410 can prevent the speed of the own vehicle from exceeding 20 items. If the speed is slower than the speed of the abnormal behavior information 520 of the caution map information 600A, the warning of the speed in step S406 may not be notified.

Further, system control unit 410, for example, even when 20 or more items of caution map information 600A include the notification content of speed caution, when the number of passengers in vehicle status information 510 is one, If there is no cargo after transporting the cargo, the warning about speed may not be notified in step S406.

In addition, in a vehicle such as a bus with a fixed number of seats, the system control unit 410 may issue an alert only when there are more passengers than the number of seats (or when there are standing passengers). . The number of passengers, etc., can be confirmed by image recognition based on images captured by the in-vehicle camera.

Further, the system control unit 410 may not determine whether or not to call attention when a vehicle such as a bus or a taxi is being forwarded. It is possible to notify the system control unit 410 via the monitor 421 that the file is being forwarded.

As described above, in the present embodiment, the system control unit 310 of the alert management device 300 on the alert map generation server 100 side generates the alert information 500A to 500A having the vehicle status information 510 including the vehicle type via the antenna 316. 500E, based on the alert information 500A to 500E, the information management unit 314 generates the alert map information 600A to 600E including the location information of the abnormal behavior of the vehicle for each vehicle type, and controls the system. When unit 310 receives a transmission request from a vehicle, it transmits alert map information 600A to 600E matching the vehicle type of the transmission request.

The system control unit 410 of the attention calling device 400 mounted on the vehicle generates the attention calling map information 600A to 600E including the position information of the abnormal behavior of the other vehicle for each vehicle type received from the calling map generation server 100. Based on this, it is determined whether or not the attention is required, and if it is determined to be necessary, the attention is notified via the monitor 421, thereby preventing the attention from being issued even when the attention is not required.

In this embodiment, the information management unit 314 on the alert server 100 side generates the alert map information 600A to 600E based on the alert information 500A to 500E managed separately for each vehicle type, and generates the alert map information 600A to 600E. Although it is managed separately for each, it is not limited to this example. For example, the information management unit 314 may further manage the generated alert map information 600A to 600E for each certain range (for example, each prefecture). As a result, the vehicle side can receive the required range of the alert map information 600A to 600E, and the time required for the alert device 400 to determine whether to alert the vehicle can be shortened.

Further, in the present embodiment, the information management unit 314 on the alert server 100 side generates notification contents based on the abnormal behavior information 520 of the alert information 500A to 500E. Audio data may also be added to the content. In this case, on the vehicle side, the warning can also be confirmed by the sound from the speaker.

Further, in the present embodiment, the information management unit 314 on the alert server 100 side generates notification contents based on the abnormal behavior information 520 of the alert information 500A to 500E. The contents may be generated by the system control unit 410 of the attention calling device 400 on the vehicle side. In this case, the alerting device 400 can arbitrarily change the notification contents.

100 Alert server 300 Alert management device 310, 410 System control unit 311, 411 Bus 312, 419 ROM
313 RAM
314 Information management unit 315 External storage device 316, 412 Antenna 400 Alert device 400d Send button 413 GPS module 414 Vehicle speed acquisition unit 415 Engine speed acquisition unit 416 Acceleration sensor 417 Angular velocity sensor 418 Weight sensor 420 EEPROM
421 Monitor 430 Map display column 440 Information input columns 440a, 440c Input column 440b Check box 440d Send button 450 Abnormal behavior history display column 460 Display columns 500A to 500E Alert information 510 Vehicle status information 520 Abnormal behavior information 600A to 600E Alert map Information 610 Determined position information 620 Notification information

Claims (8)

An alert map generation server comprising an alert management device,
The alert management device is
a first storage means;
Information Management Department;
When alert information having vehicle status information including vehicle type is received via a communication line, the information management unit manages the alert information and generates alert map information based on the alert information. and a first system control unit that instructs
Based on the alert information, the information management unit generates alert map information including location information where the abnormal behavior of the vehicle has occurred, for each vehicle type, and stores the alert map information in the first storage means. manage and
The alert map generation server, wherein the first system control unit, upon receiving a transmission request from the vehicle, transmits the alert map information that matches the vehicle type of the transmission request. The vehicle status information includes information indicating the number of passengers and/or cargo,
2. The caution according to claim 1, wherein the information management unit further divides and generates the alert map information classified for each vehicle type, further for each information indicating the number of passengers and/or cargo capacity. Evocation map generation server. A warning device mounted on a vehicle,
The alert device is
a monitor;
Based on the alert map information for each vehicle type received from the alert map generation server and including the position information of the abnormal behavior of the other vehicle, it is determined whether or not the alert is necessary, and if it is determined to be necessary, the monitor and a second system control unit that notifies the user of the warning via the warning device. 4. The alerting device according to claim 3, wherein the alerting map information for each vehicle type is further divided according to information indicating the number of passengers and/or cargo. information acquisition means for acquiring information indicating abnormal behavior of the vehicle;
a second storage means;
The second system control unit
determining that an abnormal behavior has occurred when the value obtained by the information obtaining means changes rapidly, and storing the obtained value in the second storage means until the abnormal behavior converges;
If it is determined that there is no abnormal behavior, alert information indicating abnormal behavior information indicating the obtained value and vehicle status information including the vehicle type of the own vehicle is sent to the alert map generation server via a communication line. 5. The alerting device according to claim 3 or 4, characterized by transmitting to. When alert information having vehicle status information including vehicle type is received via a communication line, an information management unit is instructed to manage the alert information and generate alert map information based on the alert information. having a first system control unit that
Based on the alert information, the information management unit generates alert map information including location information of the abnormal behavior of the vehicle for each vehicle type, and stores and manages the alert map information in the first storage means. death,
the first system control unit, when receiving a transmission request from the vehicle, transmits the attention map information matching the vehicle type of the transmission request;
a monitor;
Based on the alert map information including the location information of the abnormal behavior of the other vehicle for each vehicle type received from the alert map generation server, it is determined whether or not the alert is necessary. and a second system control unit that issues an alert through a monitor, and an alert device mounted on the vehicle. When the first system control unit receives the alert information having the vehicle status information including the vehicle type via the communication line, the information management unit manages the alert information and performs the alert based on the alert information. a step of instructing the generation of alert map information, and upon receiving a transmission request from a vehicle, transmitting the alert map information that matches the vehicle type of the transmission request;
The information management unit generates, based on the alert information, alert map information including location information where the abnormal behavior of the vehicle has occurred, for each vehicle type, and stores the alert map information in the first storage means. A caution map generation program characterized by causing a computer that controls a caution management device on the side of a caution map generation server to execute the step of managing. a step of notifying an alert by a monitor;
The second system control unit determines whether a warning is necessary based on the warning map information including the location information of the abnormal behavior of other vehicles for each vehicle type received from the warning map generation server. and causing a computer that controls an attention calling device mounted on the vehicle to execute a step of notifying the attention through the monitor if it is determined to be necessary.

Images