JP7578448B2 - Vehicle management device, vehicle management system, and vehicle management program - Google Patents

Description

The present invention relates to a vehicle management device, a vehicle management system, and a vehicle management program.

Technologies related to vehicle management during disasters have been proposed (see, for example, Patent Documents 1 to 3). Patent Document 1 discloses a disaster vehicle control device that, when disaster information is received, can start the vehicle engine without using an ignition key by entering a secret code. With this vehicle control device, when a vehicle is stopped during a disaster and the driver leaves the vehicle, the vehicle can be moved without impeding the passage of emergency vehicles or rescue operations, even without the key. In addition, as an anti-theft measure, this vehicle control device stops the engine after the vehicle has been driven a specified distance with the engine started, and restricts the vehicle from being driven with only the ignition key.

Patent Document 2 discloses a traffic management system that includes an on-board device mounted on a vehicle such as a truck, and a traffic management device that generates driving instructions for the vehicle. When a disaster or other problem occurs on the vehicle's planned driving route, the traffic management system of Patent Document 2 acquires emergency information on the disaster or other problem from an external server or the like, registers it in a database, identifies dangerous areas, and proposes reroute information that avoids the dangerous areas. This reroute information reflects labor information on the crew and takes into account the transport quality of the cargo transported by the vehicle, making it possible to generate appropriate driving instructions.

Patent Document 3 discloses a driver safety confirmation system that determines the safety of a vehicle driver based on the difference in information that represents the vehicle's state when an earthquake occurs and when the earthquake ends. This safety confirmation system makes it possible to predict the driver's safety without requiring the driver to perform any input operations.

JP 2006-144595 A JP 2019-219925 A JP 2009-265981 A

However, with the vehicle control device described in Patent Document 1, when moving a vehicle for the purpose of traffic improvement or the like after the driver has evacuated from the vehicle, smooth vehicle movement may be difficult because a PIN code must be entered and there are limitations on the distance that the vehicle can be moved. In particular, after a disaster occurs, vehicles that obstruct the passage of emergency vehicles and the like must be moved quickly, so it is desirable to be able to move vehicles without hindrance. On the other hand, measures to prevent vehicle theft are necessary.

The present invention was made in consideration of the above-mentioned circumstances, and its purpose is to enable appropriate vehicle management after a disaster occurs.

In order to achieve the above-mentioned object, a vehicle management device, a vehicle management system, and a vehicle management program according to the present invention are characterized by the following (1) to (8).
(1) A vehicle management device that manages vehicle operation,
A first acquisition unit that acquires disaster information;
A second acquisition unit that acquires location information indicating a current location of the vehicle;
an information management unit that acquires and records movement information regarding the movement of the vehicle and driver information regarding the driver of the vehicle after acquiring the disaster information;
a determination unit that determines whether the driver is the actual driver based on the recorded driver information, and if it is determined that the driver is the actual driver, determines that the purpose of the movement of the vehicle is for good use, and if it is determined that the driver is not the actual driver, determines whether the purpose of the movement of the vehicle is for bad use or good use based on the recorded movement information ;
and a notification unit that notifies the driver of the acquired disaster information by at least one of display and voice.
Vehicle management device.
(2) the travel information is information indicating at least one of a travel distance, a travel time, and a destination position of the vehicle,
The determination unit determines whether the driver is the driver himself/herself based on the recorded driver information, and if it is determined that the driver is the driver himself/herself, determines that the purpose of the movement of the vehicle is for good use, and if it is determined that the driver is not the driver himself/herself, determines whether the purpose of the movement of the vehicle is for bad use or good use based on the recorded movement information .
A vehicle management device as described in (1) above.
(3) The driver information is image data of at least the face of the driver captured by an imaging device mounted on the vehicle,
The information management unit acquires and records at least the driver information,
The determination unit performs face recognition on the captured image data, and determines whether the driver matches a driver registered in a database in which face images of a plurality of drivers are registered in advance.
A vehicle management device according to (1) or (2) above.
(4) A route guidance unit that calculates and presents a destination and a driving route of the vehicle based on the disaster information and the location information.
A vehicle management device according to any one of (1) to (3) above.
(5) A transmission unit that transmits a determination result by the determination unit.
A vehicle management device according to any one of (1) to (4) above.
(6) The determination unit is
If it is determined based on the driver information that the actual driver is a legitimate driver who has already been registered, it is determined that the purpose of the movement of the vehicle is for non-profit purposes;
If it is determined based on the driver information that the actual driver is not a legitimate driver who has already been registered, then if the travel distance and the travel time are short and the travel destination is a road or private property, it is determined that the purpose of the travel of the vehicle is for good use, and if the travel distance and the travel time are long and the travel destination is a car dealership, it is determined that the purpose of the travel of the vehicle is for bad use.
A vehicle management device as described in (2) above.
(7) The vehicle management device according to (5) above;
A vehicle management system including an on-board device mounted on the vehicle,
The vehicle-mounted device acquires the location information and the driver information and transmits them to the vehicle management device;
In the vehicle management device,
The second acquisition unit acquires at least the transmitted location information,
The information management unit acquires and records the movement information and the driver information,
The determination unit determines whether the driver is the driver himself/herself based on the recorded driver information, and if it is determined that the driver is the driver himself/herself, determines that the purpose of the movement of the vehicle is a good use purpose, and if it is determined that the driver is not the driver himself/herself, determines whether the purpose of the movement of the vehicle is a bad use purpose or a good use purpose based on the recorded movement information ;
The transmission unit transmits the determination result to a predetermined information terminal.
Vehicle management system.
(8) In a computer that manages a vehicle,
Function to obtain disaster information,
A function of acquiring location information indicating a current location of the vehicle;
A function of acquiring and recording movement information regarding the movement of the vehicle and driver information regarding the driver of the vehicle after acquiring the disaster information;
A function for determining whether the driver is the driver himself/herself based on the recorded driver information, and if it is determined that the driver is the driver himself/herself, determining that the purpose of the movement of the vehicle is for good use, and if it is determined that the driver is not the driver himself/herself, determining whether the purpose of the movement of the vehicle is for bad use or good use based on the recorded movement information; and a function for notifying the driver of the acquired disaster information by at least one of display and sound.
A vehicle management program to achieve this.

According to the vehicle management device having the above configuration (1) and the vehicle management program having the above configuration (8), when a vehicle stopped on a road or the like at the time of a disaster is moved (redriven) after the disaster, it is determined whether the movement of the vehicle is for a specified purpose. For example, it can be determined whether the movement is for abusive purposes such as theft, mischief, etc., or not for abusive purposes (for good purposes) such as traffic maintenance. Therefore, when a stopped vehicle is redriven, the vehicle can be moved smoothly without restricting the movement distance, etc. to agree to vehicle theft. In addition, if the vehicle is moved for abusive purposes, the manager, etc. can understand that the vehicle movement is for abusive purposes, and therefore it is possible to deal with the theft, etc. In this way, appropriate vehicle management after a disaster occurs.
Furthermore, according to the vehicle management device having the above configuration (1) and the vehicle management program having the above configuration (8), it is possible to make the driver aware of the occurrence of an earthquake or the like.

According to the vehicle management device having the configuration of (2) above, for example, if the travel distance or travel time is short, or if the travel destination is an evacuation facility or the like, it can be determined that the purpose is not malicious.

The vehicle management device configured as in (3) above can use facial recognition to determine whether the actual driver is the driver registered in the database.

According to the vehicle management device having the configuration of ( 5 ) above and the vehicle management system having the configuration of (7) above, for example, by transmitting the determination result that the vehicle movement is for malicious purposes to an administrator, the administrator can deal with vehicle theft, etc.

According to the vehicle management device having the above configuration ( 4 ), it is possible to guide evacuation routes that pass only along roads that were passable for vehicles during past earthquakes, for example.

The present invention enables proper vehicle management after a disaster occurs.

The present invention has been briefly described above. The details of the present invention will become clearer by reading the following description of the embodiment of the invention (hereinafter referred to as "embodiment") with reference to the attached drawings.

FIG. 1 is a diagram showing an example of the configuration of a vehicle management system according to the present embodiment. FIG. 2 is a flowchart showing an example of the operation of the vehicle-mounted device and the server when disaster information is received. FIG. 3 is a schematic diagram showing an example of the appearance of the vehicle-mounted device when receiving disaster information. FIG. 4 is an image diagram of an example of an evacuation route guidance screen on the vehicle-mounted device. FIG. 5 is a flowchart showing an example of a process for confirming the purpose of a vehicle trip by the server. FIG. 6 is an image diagram of an example of driver confirmation in the administrator PC. FIG. 7 is an image diagram showing an example of an operation when the driver confirmation result in the administrator PC is a mismatch.

<System Configuration>
An example of the configuration of a vehicle management system 1 according to an embodiment of the present invention is shown in Fig. 1. The vehicle management system shown in Fig. 1 is used for driving support of vehicles such as trucks, buses, and taxis.

The vehicle management system 1 shown in FIG. 1 includes, as customer equipment, an in-vehicle device 10 that is mounted on each vehicle and used, and an administrator PC 30 that is installed in a designated office to manage each vehicle, workers, work content, etc. The vehicle management system 1 also includes, as service provider equipment, a server 80 that performs analysis based on various data collected from the in-vehicle device 10 and provides various services related to operation management to the administrator PC 30. The vehicle management system 1 may include multiple administrator PCs 30 and multiple in-vehicle devices 10 that are installed in multiple customer offices, etc. Details will be described later, but the in-vehicle device 10 of this embodiment has functions that are useful in the event of a disaster such as a major earthquake in addition to normal digital tachograph functions.

The administrator PC 30 is composed of a general-purpose computer device installed in an office, and manages the operation status of the vehicle. In the example of FIG. 1, data communication between the vehicle-mounted device 10 and the administrator PC 30 is relayed by a base station 71, a server 80 (operation management device), and a network 70. Wireless communication between the base station 71 and the vehicle-mounted device 10 is performed, for example, over a mobile communication network (mobile line network) such as LTE (Long Term Evolution)/4G (4th Generation) or 5G (5th Generation). The network 70 is a network (packet communication network) such as the Internet, and relays data communication between the administrator PC 30 and the server 80.

In addition, data communication between the vehicle-mounted device 10 and the administrator PC 30 can be avoided under normal circumstances (except when a disaster such as a major earthquake occurs), and a memory card 65 that holds data recorded by the vehicle-mounted device 10 can be inserted into the administrator PC 30 and read from the memory card 65.

The vehicle-mounted device 10 includes various interfaces (I/F) 12A, 12B, 13, 14, 16, 19, and 29 to enable input or output of various signals.
The speed I/F 12A has a function of inputting a vehicle speed pulse signal output from a vehicle speed sensor 51 mounted on the vehicle side. The engine rotation I/F 12B has a function of inputting an engine rotation pulse signal output from the vehicle side. The external input I/F 13 is used to input various external signals, and has a function of inputting ignition data indicating whether the ignition key is on/off, etc.

The sensor input I/F 14 is used to input signals from various sensors. In the example of FIG. 1, a G sensor 28 is connected to the sensor input I/F 14. The G sensor 28 detects the magnitude of acceleration in various directions applied to the vehicle in which the vehicle-mounted device 10 is mounted. Based on the output of the G sensor 28, the control unit 11 detects sudden deceleration or sudden acceleration of the vehicle. Based on the output of the G sensor 28, the control unit 11 detects a sudden turn of the vehicle.

The analog input I/F 29 is used to input various analog signals.
The camera I/F 16 has a function for connecting the camera 23. The camera 23 is a photographing device that is provided, for example, at the center of the steering wheel of the vehicle and photographs at least the face of the driver. The camera I/F 16 has a function for taking in the video signal output by the camera 23 and converting it into predetermined digital image data suitable for computer processing. The camera I/F 16 may be connected to a plurality of cameras, such as a camera that photographs the surroundings of the vehicle.

The audio I/F 19 has the function of generating a specific audio signal that can be used for audio alerts in the event of a major earthquake.

The control unit 11, which realizes the main functions of the vehicle-mounted device 10, is composed of electronic circuits mainly including a processor of a microcomputer (CPU). This microcomputer realizes the control functions of the vehicle-mounted device 10, which will be described later, by executing programs stored in advance in the non-volatile memory 26A, etc.

The above-mentioned interfaces 12A, 12B, 13, 14, 16, and 29 are connected to the input of the control unit (CPU) 11. In addition, a speaker 20 is connected to the output of the control unit 11 via an audio I/F 19, and audio notifications related to the occurrence of a major earthquake can be made from the speaker 20.

In addition, the GPS receiving unit 15, the recording unit 17, the display unit 27, the power supply unit 25, the communication unit 24, the non-volatile memory 26A, the volatile memory 26B, the card I/F 18, the RTC unit 21, and the switch input unit 22 are connected to the control unit 11.

The GPS receiver 15 receives radio waves from multiple GPS (Global Positioning System) satellites via the antenna 15a. Based on the multiple received signals received by the GPS receiver 15, the control unit 11 can calculate and obtain position information indicating the current location of the vehicle. This position information includes latitude and longitude information of the current location of the vehicle, as well as information indicating the altitude above sea level. Furthermore, the control unit 11 can detect the movement of the vehicle using the position information based on the signals received by the GPS receiver 15.

The recording unit 17 is used to automatically record image data (captured image data) of the video output by the camera 23, for example, and hold the data for a certain period of time.
The display unit 27 can be used to display visible information such as characters necessary for operating the vehicle-mounted device 10, information reporting the occurrence of a major earthquake, and information warning drivers about driving operations so that the driver can see it.

The power supply unit 25 generates stable power from the power supply supplied from the vehicle side, and supplies the generated power to each circuit in the vehicle-mounted device 10 including the control unit 11 .
The communication unit 24 provides a wireless communication function for data communication between the vehicle-mounted device 10 and a base station 71 .

The non-volatile memory 26A is made up of a semiconductor memory, and stores in advance programs executable by the microcomputer of the control unit 11, such as an earthquake program described below, as well as various constant data and tables required for control.
The volatile memory 26B is used to temporarily store data generated by the control unit 11 during processing.

A memory card 65 carried by the driver is connected to the card I/F 18 so that it can be inserted and removed freely. The control unit 11 can read data from the memory card 65 attached to the card I/F 18, and can also write various data generated by the control unit 11 to the memory card 65 via the card I/F 18.

The RTC (real time clock) unit 21 is configured with an integrated circuit having a clock function, that is, the RTC unit 21 can generate information on the current time and grasp the elapsed time.
The switch input unit 22 is used to input signals representing the states of various switches necessary for operating the vehicle-mounted device 10 .

The administrator PC 30 is a PC that runs on a general-purpose operating system. The administrator PC 30 functions as a vehicle management device for grasping and managing the vehicle's driving status, operating status, etc. The administrator PC 30 has a control unit (CPU) 31, a communication unit 32, a display unit 33, a memory unit 34, a card I/F 35, an operation unit 36, an output unit 37, an audio I/F 38, and an external I/F 48.

The control unit 31 comprehensively controls each unit of the administrator PC 30. The communication unit 32 is capable of communicating with the server 80 via the network .
The display unit 33 can display various information that can be used for operation management of each vehicle. The storage unit 34 can acquire and manage data generated by the vehicle-mounted device 10 mounted in each vehicle.

A memory card 65 is attached to the card I/F 35 so that it can be inserted and removed freely. The card I/F 35 is used to input various data recorded in the vehicle-mounted device 10 from the memory card 65. The operation unit 36 has a keyboard, mouse, etc., and accepts operations by the administrator of the administrator PC 30. The output unit 37 outputs various data. A microphone 41 and a speaker 42 are connected to the audio I/F 38. The administrator can also make voice calls using the microphone 41 and the speaker 42.

External storage devices (not shown) such as an operation data database (DB) and a hazard map database (DB) can be connected to the external I/F 48. The hazard map DB can hold data showing locations where vehicle accidents have occurred and data showing roads that were passable when past earthquakes occurred. In addition, a driver database 85, which will be described later, can be connected to the external I/F 48.

The server 80 has a control unit (CPU) 81, a communication unit 82, a storage unit 83, and an external I/F 84. The server 80 monitors the operation status of the vehicle in which the vehicle-mounted device 10 is mounted in real time and functions as an operation management device. The communication unit 82 communicates with the vehicle-mounted device 10 via the base station 71. The communication unit 82 may also communicate with the administrator PC 30 via the network 70. Furthermore, the communication unit 82 can receive disaster information described later from an external agency server or the like via the network 70 and transmit it to the vehicle-mounted device 10. The storage unit 83 is a memory capable of storing various data, and stores operation data transmitted from the vehicle-mounted device 10. The storage unit 83 stores the vehicle's current location data (movement information) and the captured image data (driver information) of at least the face of the driver of the vehicle, which are sequentially transmitted from the vehicle-mounted device 10 when the vehicle is driven again after the occurrence of an earthquake. The storage unit 83 may also store operation data transmitted from the administrator PC 30. A driver database (DB) 85 is connected to the external I/F 84. In the driver DB 85, various information such as a driver ID, name, and face image is registered in advance for each of a plurality of drivers. In the driver DB 85, the vehicle number of the vehicle for which the driver is responsible can be registered in association with the driver ID.

The control unit 81 comprehensively controls each unit of the server 80. The control unit 81 analyzes the received operation data. Based on the vehicle's destination information and driver information, the control unit 81 determines whether the movement of the re-driven vehicle was performed for the purpose of misuse, such as theft or mischief. The control unit 81 causes the communication unit 82 to transmit the determination result to a specified communication terminal of the administrator PC 30, the police, etc.

<Example of operation when receiving disaster information>
An example of the operation of the vehicle-mounted device 10 and the server 80 when disaster information is received indicating that the seismic intensity is equal to or greater than a certain level is shown in Fig. 2. The control unit 11 of the vehicle-mounted device 10 and the control unit 81 of the server 80 work in conjunction with each functional unit of the vehicle-mounted device 10 and the server 80 to execute an earthquake program (part of the vehicle management program) stored in advance in the non-volatile memory 26A and the storage unit 83, thereby performing the operation shown in Fig. 2.

The vehicle-mounted device 10 determines whether or not an earthquake of seismic intensity 5 or more has been detected by acquiring disaster information such as an emergency earthquake warning received from an external agency server or the like via the server 80 or directly (step S1). The emergency earthquake warning is a forecast or warning issued when shaking of seismic intensity 5 or more is expected, and includes information on the epicenter (location of the earthquake). In addition to the emergency earthquake warning, the disaster information includes at least information on the epicenter, such as earthquake data from an earthquake warning system using early detection seismometers such as coastal seismometers and ocean bottom seismometers. The disaster information may include information on the seismic intensity and the area where large shaking is expected. In step S1, the vehicle-mounted device 10 may determine whether or not an earthquake of seismic intensity 4 or more has been detected by receiving the disaster information. The disaster information includes at least information indicating the area where a disaster is expected to occur, and is received by the vehicle-mounted device 10 mounted on a vehicle located in that area.

The vehicle-mounted device 10 waits until it detects an earthquake with a seismic intensity of lower 5 or more (NO in step S1), and if it does detect an earthquake (YES in step S1), it acquires location information indicating the vehicle's current location (step S2). The location information includes the latitude and longitude information of the current location as well as information about altitude above sea level. In addition, in step S2, the vehicle-mounted device 10 can alert the driver of the occurrence of a major earthquake by using at least one of the speaker 42 and the display unit 27.

Figure 3 shows a schematic diagram of the vehicle-mounted device 10 when disaster information is received. When the communication unit 24 receives an emergency earthquake alert, the vehicle-mounted device 10 displays a message d1 on the display unit 27, for example, "Major earthquake has occurred. Follow instructions to evacuate," as shown in Figure 3, and also outputs a similar message by voice from the speaker 42 to notify the driver of the occurrence of a major earthquake. In addition, the display unit 27 displays a display d2 indicating the communication status of the communication unit 24.

The vehicle-mounted device 10 judges whether the current location is above a certain level (for example, 15 m or more) above sea level (step S3). If the current location is above sea level (YES in step S3), the risk of damage such as the vehicle being submerged in water by a tsunami is low, so the vehicle-mounted device 10 informs the driver by voice and/or display that the vehicle should be stopped immediately (step S4). In this case, the vehicle-mounted device 10 guides the driver to move the vehicle to the left side of the road and evacuate with the key still in the ignition until the vehicle's speed is no longer detected, and then proceeds to the processing of step S5.

If the current location is not above a certain level above sea level (NO in step S3), the vehicle-mounted device 10 requests the server 80 to search for a route to evacuate the vehicle to a location above sea level (step S6). Upon receiving the request, the server 80 analyzes the sea level data and calculates the route, and proposes the optimal route to the vehicle-mounted device 10. The server 80 refers to an earthquake map database connected to the external I/F 84, searches for an evacuation route that can quickly increase the sea level from only roads that were passable in past earthquakes, and proposes this to the vehicle-mounted device 10. The server 80 can also change the evacuation route by taking into account road information and tsunami information obtained from information provided during earthquakes, etc.

Figure 4 is an image diagram of an example of an evacuation route guidance screen on the vehicle-mounted device 10. As shown in Figure 4, it is known that the planned route R1 (initially calculated evacuation route) from a starting point S (current location) at a low altitude to a goal point G (destination) at a high altitude passes through a danger zone D along the way, according to road information, etc. Therefore, the server 80 can change the planned route R1 to an evacuation route R2 that bypasses the danger zone D, and display the changed evacuation route R2 on the vehicle-mounted device 10, highlighting it with an arrow.

The vehicle-mounted device 10 guides the vehicle along the evacuation route R2 received from the server 80 until the vehicle reaches a certain altitude above sea level (step S7).

The vehicle-mounted device 10 judges whether the vehicle speed is 1 km/h or more (step S5). If the vehicle speed is 1 km/h or more (YES in step S5), the vehicle-mounted device 10 judges that the vehicle is moving (running) and guides the vehicle to stop (step S8). That is, the vehicle-mounted device 10 informs the driver via the display unit 27 and/or speaker 42 to avoid sudden steering and braking and to stop the vehicle on the left side of the road in a safe manner, and returns to the processing of step S5.

On the other hand, if the vehicle speed is not 1 km/h or more (NO in step S5), that is, if the vehicle is not moving, the vehicle-mounted device 10 informs the driver of precautions to take when parking the vehicle on the spot and evacuating through the display unit 27 and/or the speaker 42 (step S9). The vehicle-mounted device 10 informs the driver to park the vehicle on the left side of the road, turn off the engine, leave the engine key in the ignition or place it in an easily visible place in the vehicle such as the driver's seat, close the windows, and leave the doors unlocked, and ends the process. The vehicle-mounted device 10 detects that the ignition switch has been turned off based on the ignition data and turns off the power. At this time, the vehicle-mounted device 10 records that the earthquake program has been run. The calculation and proposal process for the evacuation route (step S6) may be performed by the vehicle-mounted device 10 or by the administrator PC 30.

<Example of operation when a vehicle is restarted after evacuation>
Next, an example of an operation for determining whether or not the movement of a vehicle is for malicious purposes when the vehicle is driven again after the occurrence of a disaster will be described with reference to Fig. 5. The server 80 performs the operation shown in Fig. 5 by executing a movement purpose determination program (part of the vehicle management program) stored in advance in the storage unit 83 by the control unit 81 in cooperation with each functional unit of the server 80.

When the ignition data input from the external input I/F 13 to the control unit 11 changes from an off state to an on state and an ignition on signal is sent to the server 80, the server 80 starts executing the program shown in FIG. 5. The server 80 determines whether a large earthquake has occurred within a certain period of time and whether the earthquake program has been run (step S21). If the answer is YES, the server 80 obtains current location data (latitude and longitude information) indicating the current location of the vehicle from the vehicle-mounted device 10 (step S22). If the answer is NO, the process ends.

The server 80 acquires the speed data indicating the vehicle speed transmitted from the vehicle-mounted device 10 and determines whether the speed is 1 km/h or more (step S23). If YES, the process proceeds to step S24, and if NO, the process returns to step S22 and acquires the current location of the vehicle.

In step S24, the server 80 instructs the vehicle-mounted device 10 to disable operation and not to display anything on the screen. Normally, when the ignition is turned on, the vehicle-mounted device 10 displays an initial screen and starts up in a state in which it can accept operations by the driver. However, according to the processing of step S24, the vehicle-mounted device 10 does not display a screen and becomes inoperable, so that the vehicle-mounted device 10 can be prevented from being misused.

Next, the server 80 transmits the vehicle's current location data to the administrator PC 30 (step S25), and transmits the captured image data of the driver's seat captured by the camera 23 at regular intervals, acquired from the vehicle-mounted device 10, to the administrator PC 30 (step S26). The captured image data includes a facial image of the driver who is actually driving the vehicle.

Next, the server 80 performs image recognition on the captured image data, checks whether the facial image included in the captured image data matches any of the facial images of drivers registered in the driver database 85, and determines whether the driver is the driver in question (step S27). This process makes it possible to determine, through facial recognition, whether the actual driver is a driver registered in the driver DB 85. In addition, in S27, the server 80 may further use information on the vehicle number that identifies the vehicle in which the vehicle-mounted device 10 is installed to check whether the facial image of the driver linked to this vehicle number matches the recognized facial image.

In step S27, the server 80 may transmit the captured image data to the administrator PC 30 and have the administrator visually confirm that the facial image contained in the captured image data matches the image registered in the driver database 85. The server 80 then determines that the owner (legitimate driver) is the owner when the fact that the captured image contains the face of the legitimate driver is input to the administrator PC 30 and transmitted to the server 80. An image diagram of driver confirmation on the administrator PC 30 is shown in FIG. 6. The administrator PC 30 displays the captured image data P transmitted from the server 80 and displays the facial image data registered in the driver database 85. The administrator compares the two images to confirm whether the facial image contained in the captured image is that of the legitimate driver, and inputs the result to the administrator PC 30, which transmits it to the server 80.

If it is determined in step S27 that the driver is the actual driver, the server 80 determines that the vehicle movement is not for malicious purposes (step S28). If it is confirmed in step S28 by image recognition that the actual driver is the legitimate driver, the server 80 notifies at least the administrator PC 30 of this fact, out of the administrator PC 30 and the vehicle-mounted device 10. Furthermore, if it is confirmed by the administrator's visual inspection that the actual driver is the legitimate driver, the server 80 notifies the vehicle-mounted device 10 of this fact and ends the process. This notification can be made by any means, such as sending an email or outputting a voice message.

On the other hand, if step S27 is No, i.e., if the driver is not the legitimate driver, the server 80 acquires the vehicle's destination data from the vehicle-mounted device 10 and transmits it to the administrator PC 30 (step S29). This process allows the administrator PC 30 to know the vehicle's destination, thereby avoiding a case where the vehicle's location becomes unknown after the driver evacuates.

Next, the server 80 analyzes the movement information based on the current location data acquired in step S22, the destination data acquired in step S29, and the time information acquired by the vehicle-mounted device 10 from these data (step S30). That is, the server 80 analyzes the movement distance, movement time, and the destination location (location information) to determine whether the driving was for abusive purposes. For example, if the movement distance and movement time are short and the destination is a road or private land, the server 80 determines that the driving was for a benign purpose such as traffic improvement (not for abusive purposes). On the other hand, if the movement distance and movement time are long and the destination is a car dealership or the like, the server 80 determines that the driving was for abusive purposes (inappropriate purposes) such as theft or mischief.

Furthermore, the server 80 may determine that the movement is for misuse purposes when the movement destination is, for example, an evacuation facility, a disaster support parking lot, a multi-story parking lot, etc., regardless of the movement time and movement distance. For example, the server 80 may store in advance in the memory unit 83 or a database a list of good/misuse purposes including information such as facility names and facility locations for determining whether the movement is for good or misuse purposes, and may determine that the movement is for good/misuse purposes depending on which list the movement destination is included in. Also, if the movement distance or movement time is shorter than a predetermined value, it may be determined that the movement is for misuse purposes. In this way, the server 80 determines whether the movement of the vehicle was for misuse purposes based on at least one of the movement distance, movement time, and destination location of the vehicle as movement information.

If it is determined in step S30 that the purpose is misuse (YES), the server 80 notifies the administrator PC 30 that the vehicle has been moved for an inappropriate purpose (step S31). In addition to or instead of notifying the administrator PC 30, the server 80 may also notify a specified contact point (communication terminal) such as the police. Since the server 80 knows the destination of the vehicle, even if the vehicle has been moved for misuse, it is possible to take measures against theft, etc. If it is determined in step S30 that the purpose is not misuse, the server 80 ends the process. At this time, the server 80 may notify the administrator PC 30 or the vehicle-mounted device 10 by any means that the actual driver is the legitimate driver.

As described above, according to the vehicle management system 1 of this embodiment, when a vehicle that was stopped on a road or the like during a disaster is driven again after the disaster, it is determined whether the movement of the vehicle was for a specified purpose based on at least one of the movement information and the driver information. In other words, it can be determined whether the movement was for abusive purposes such as theft, mischief, etc., or not for abusive purposes (for benign purposes) such as traffic maintenance, etc. Therefore, when a stopped vehicle is driven again, the movement distance, etc. is not restricted, so the vehicle can be moved smoothly. Furthermore, if the vehicle is moved for abusive purposes, the manager, etc. can know that the vehicle movement is for abusive purposes, and it becomes possible to deal with theft, etc. In this way, appropriate vehicle management after a disaster occurs.

In areas where a disaster such as a major earthquake occurs, it may be difficult to operate vehicles due to road collapses, damage from tsunamis, etc. Furthermore, from the perspective of traffic safety, it is recommended to stop vehicles when a major earthquake occurs, and not to continue operating them. According to this embodiment, when a disaster occurs, the on-board device guides the driver to an evacuation route to an appropriate location where the vehicle will not be submerged, and promptly guides the driver to evacuate from the vehicle. Therefore, even if the driver does not notice the major earthquake, or if the driver notices it but has difficulty evacuating due to a lack of information or panic, it is possible to present an appropriate evacuation route and encourage the driver to take the right action.

The present invention is not limited to the above-described embodiment, and can be modified, improved, etc. as appropriate. In addition, the material, shape, dimensions, values, form, number, location, etc. of each component in the above-described embodiment are arbitrary as long as they can achieve the present invention, and are not limited.

In the above embodiment, an example was shown in which the server 80 judges whether the movement of the vehicle is for malicious purposes, but this judgment (judgment of the purpose of the movement) may also be made by the administrator PC 30. In this case, the administrator PC 30 obtains the vehicle's current location data, speed data, captured image data, and ignition data from the vehicle-mounted device 10 via the server 80 or directly, and executes each process of S21 to S24 and S27 to S31 shown in the flowchart of FIG. 5. An image diagram of the case in which the judgment is made by the administrator PC 30 is shown in FIG. 7. As shown in FIG. 7, as an example, if the movement distance is long, the administrator PC 30 judges that the purpose of the movement is malicious, such as theft or mischief, and reports it to a specified contact point such as the police.

The vehicle-mounted device 10 may perform this travel purpose determination (the series of processes shown in FIG. 5), or may perform all of the processes shown in FIG. 2, including the route search process (step S6).

The above-mentioned processes may be shared among the vehicle-mounted device 10, the server 80, and the administrator PC 30. For example, among the processes shown in FIG. 2, the route search process (step S6) may be performed by the administrator PC 30 instead of the server 80. Similarly, among the processes shown in FIG. 5, the determination processes of S27 and S30 may be performed by the server 80 or the administrator PC 30, and the other processes may be performed by the vehicle-mounted device 10.

Furthermore, the processes related to searching and providing information about evacuation routes (S6, S7) may be performed by a reroute device such as an in-vehicle navigation device, the processes related to notifications (S28, S31) may be performed by a notification device, and the confirmation process by image recognition (S27) may be performed by a driver confirmation device. In this case, the vehicle management system 1 further includes a reroute device, a notification device, and a confirmation device, and each device is configured to be able to communicate with the in-vehicle device 10, the server 80, and the administrator PC 30. The in-vehicle device 10 then cooperates with the reroute device to execute the series of processes shown in FIG. 2, and the server 80 or the administrator PC 30 cooperates with the confirmation device and notification device to execute the series of processes shown in FIG. 5.

In the above embodiment, an example was described in which the disaster information was earthquake data, but the disaster information may be disaster prevention weather information such as tsunami information and landslide warning information, or information related to other disasters.

Here, the features of the vehicle management device, the vehicle management system, and the vehicle management program according to the above-described embodiments of the present invention will be briefly summarized and listed below in [1] to [10].
[1] A vehicle management device (server 80) for managing vehicles,
A first acquisition unit (communication unit 82, YES in step S21) that acquires disaster information;
A second acquisition unit (communication unit 82, step S22) that acquires location information indicating a current location of the vehicle;
An information management unit (control unit 81, steps S26 and S29) that acquires and records at least one of movement information regarding the movement of the vehicle and driver information regarding the driver of the vehicle after acquiring the disaster information;
and a determination unit (control unit 81, steps S27 and S30) that determines whether the movement of the vehicle has been performed for a predetermined purpose based on at least one of the recorded movement information and the driver information.
Vehicle management device (server 80).
[2] The travel information is information indicating at least one of a travel distance, a travel time, and a destination position of the vehicle,
The information management unit acquires and records at least the movement information,
The determination unit determines whether or not the movement of the vehicle has been performed for the predetermined purpose based on at least the recorded movement information.
The vehicle management device according to the above [1].
[3] The driver information is image data of at least the face of the driver captured by an imaging device mounted on the vehicle,
The information management unit acquires and records at least the driver information,
The determination unit performs face recognition on the captured image data, and determines whether the driver matches a driver registered in a database (driver database 85) in which face images of multiple drivers are registered in advance.
The vehicle management device according to the above [1] or [2].
[4] A route guidance unit that calculates and presents a destination and a driving route of the vehicle based on the disaster information and the position information.
A vehicle management device according to any one of the above [1] to [3].
[5] A transmission unit that transmits a determination result by the determination unit.
A vehicle management device according to any one of the above [1] to [4].
[6] A vehicle is equipped with the
The vehicle is provided with a notification unit (display unit 27, speaker 20) that notifies the driver of the acquired disaster information by at least one of display and voice.
A vehicle management device (vehicle-mounted device 10) according to any one of the above [1] to [5].
[7] The vehicle management device (server 80) according to [5] above;
A vehicle management system (1) including an on-board device (10) mounted on the vehicle,
The vehicle-mounted device acquires the location information and the driver information and transmits them to the vehicle management device;
In the vehicle management device,
The second acquisition unit acquires at least the transmitted location information,
The information management unit acquires and records at least the driver information of the movement information and the driver information,
The determination unit determines whether the movement of the vehicle is performed for the predetermined purpose based on at least the recorded driver information,
The transmission unit transmits the determination result to a predetermined information terminal.
Vehicle management system (1).
[8] A computer that manages a vehicle includes:
A function of acquiring disaster information (communication unit 82);
A function of acquiring location information indicating the current location of the vehicle (communication unit 82);
A function for acquiring and recording at least one of movement information regarding the movement of the vehicle and driver information regarding the driver of the vehicle after acquiring the disaster information (CPU 81), and a function for determining whether the movement of the vehicle was performed for a predetermined purpose based on at least one of the recorded movement information and the driver information (control unit 81);
A vehicle management program to achieve this.
[9] The location information includes information indicating an altitude of the current location,
The route guidance unit is
If the sea level is not equal to or higher than a certain value, the destination and the driving route in which the sea level is equal to or higher than a certain value are calculated and presented;
When the altitude is equal to or higher than a certain value, the destination and the travel route are not calculated, and the vehicle is guided to stop.
The vehicle management device (server 80) described in [5] above.
[10] When the speed of the vehicle is equal to or greater than a threshold, the information management unit acquires and records at least one of movement information regarding the movement of the vehicle and driver information regarding the driver of the vehicle, and the determination unit determines whether the movement of the vehicle was performed for a specified purpose based on at least one of the recorded movement information and the driver information.
A vehicle management device (server 80) according to any one of the above [1] to [6].

1 Vehicle management system 10 Vehicle-mounted device 11, 31, 81 Control unit (CPU)
13 External input I/F
15 GPS receiving unit 15a Antenna 24, 32, 82 Communication unit 26A Non-volatile memory 30 Administrator PC
80 Server 85 Driver database (DB)

Claims (8)

A vehicle management device that manages vehicle operation,
A first acquisition unit that acquires disaster information;
A second acquisition unit that acquires location information indicating a current location of the vehicle;
an information management unit that acquires and records movement information regarding the movement of the vehicle and driver information regarding the driver of the vehicle after acquiring the disaster information;
a determination unit that determines whether the driver is the actual driver based on the recorded driver information, and if it is determined that the driver is the actual driver, determines that the purpose of the movement of the vehicle is for good use, and if it is determined that the driver is not the actual driver, determines whether the purpose of the movement of the vehicle is for bad use or good use based on the recorded movement information ;
and a notification unit that notifies the driver of the acquired disaster information by at least one of display and voice.
Vehicle management device. The travel information is information indicating at least one of a travel distance, a travel time, and a destination position of the vehicle,
The determination unit determines whether the driver is the driver himself/herself based on the recorded driver information, and if it is determined that the driver is the driver himself/herself, determines that the purpose of the movement of the vehicle is for good use, and if it is determined that the driver is not the driver himself/herself, determines whether the purpose of the movement of the vehicle is for bad use or good use based on the recorded movement information .
The vehicle management device according to claim 1 . The driver information is image data of at least the face of the driver captured by an imaging device mounted on the vehicle,
The information management unit acquires and records at least the driver information,
The determination unit performs face recognition on the captured image data, and determines whether the driver matches a driver registered in a database in which face images of a plurality of drivers are registered in advance.
The vehicle management device according to claim 1 or 2. a route guidance unit that calculates and presents a destination and a driving route of the vehicle based on the disaster information and the location information;
The vehicle management device according to any one of claims 1 to 3. A transmission unit that transmits a determination result by the determination unit.
The vehicle management device according to any one of claims 1 to 4. The determination unit is
If it is determined based on the driver information that the actual driver is a legitimate driver who has already been registered, it is determined that the purpose of the movement of the vehicle is for non-profit purposes;
If it is determined based on the driver information that the actual driver is not a legitimate driver who has already been registered, then if the travel distance and the travel time are short and the travel destination is a road or private property, it is determined that the purpose of the travel of the vehicle is for good use, and if the travel distance and the travel time are long and the travel destination is a car dealership, it is determined that the purpose of the travel of the vehicle is for bad use.
The vehicle management device according to claim 2 . The vehicle management device according to claim 5 ;
A vehicle management system including an on-board device mounted on the vehicle,
The vehicle-mounted device acquires the location information and the driver information and transmits them to the vehicle management device;
In the vehicle management device,
The second acquisition unit acquires at least the transmitted location information,
The information management unit acquires and records the movement information and the driver information,
The determination unit determines whether the driver is the driver himself/herself based on the recorded driver information, and if it is determined that the driver is the driver himself/herself, determines that the purpose of the movement of the vehicle is a good use purpose, and if it is determined that the driver is not the driver himself/herself, determines whether the purpose of the movement of the vehicle is a bad use purpose or a good use purpose based on the recorded movement information ;
The transmission unit transmits the determination result to a predetermined information terminal.
Vehicle management system. The computer that manages the vehicle
Function to obtain disaster information,
A function of acquiring location information indicating a current location of the vehicle;
A function of acquiring and recording movement information regarding the movement of the vehicle and driver information regarding the driver of the vehicle after acquiring the disaster information;
A function for determining whether the driver is the driver himself/herself based on the recorded driver information, and if it is determined that the driver is the driver himself/herself, determining that the purpose of the movement of the vehicle is for good use, and if it is determined that the driver is not the driver himself/herself, determining whether the purpose of the movement of the vehicle is for bad use or good use based on the recorded movement information; and a function for notifying the driver of the acquired disaster information by at least one of display and sound.
A vehicle management program to achieve this.

Images