JP6830690B1 - Vehicle management server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a vehicle management server capable of appropriately managing whether or not a vehicle user has caused damage such as scratches or dents on the vehicle without requiring new equipment.
A vehicle management server 10 has a pre-ride vehicle image (front) BIM1 to (rear) BIM4 and a post-ride vehicle image (front) AIM1 to be photographed and received by a user terminal before and after boarding the vehicle. (Rear surface) AIM4 is compared with each other by vehicle images in the same direction (BIMn: AIMn), and the degree (ratio) of the portion where the post-ride vehicle image AIMn changes with respect to the pre-ride vehicle image BIMn with respect to the entire vehicle image AIMn , It is determined whether or not the degree of change is equal to or greater than the set threshold of the degree of change, and it is confirmed whether or not the vehicle after use has been damaged Hn such as new scratches or dents. , A vehicle confirmation alert AL for warning that a new damaged Hn may have occurred is output to the administrator terminal 20.
[Selection diagram] FIG. 11

Description

The present invention relates to a vehicle management server.

Conventionally, a vehicle, including a private car and a commercial vehicle, is generally owned by a person who mainly uses the vehicle (a private car is an individual, a commercial vehicle is a corporation, etc.).

In recent years, the form of owning a vehicle has been reviewed from an economic and rational point of view such as parking costs, maintenance costs, taxes, etc. with respect to the frequency of vehicle use, and vehicle rental services such as rental cars and car sharing have become widespread. There is.

In the vehicle rental service, the vehicle to be rented is from the designated parking place of the vehicle at each usage date and time (departure date and time to return date and time) contracted with the renter by the user who uses the vehicle. It will be embarked and returned.

For this reason, the renter side checks each time the vehicle is rented to see if there is any new damage such as scratches or dents on the vehicle, and if there is any new damage, It is necessary to clarify where the responsibility lies.

When checking for damage to the vehicle, if the designated parking lot for the vehicle is a parking lot attached to the sales office of the renter, the employee of the sales office may check the vehicle. In the case of an unmanned parking lot such as caring, an employee of the rental company must check the vehicle by patrolling the unmanned parking lot.

An acceleration sensor is attached to the vehicle, it is determined whether or not the vehicle has collided based on the acceleration detected by the acceleration sensor, and the determination information of the collision is wirelessly notified to the management center of the renter. A vehicle rental device has been considered in which the trader can confirm the possibility of damage to the vehicle without human labor (see, for example, Patent Document 1 and Patent Document 2).

JP-A-11-242778 JP-A-2019-91247

In a conventional device such as a vehicle rental device, a sensor is attached to a vehicle to determine whether or not the vehicle has collided or contacted, and the determination information of the collision (contact) is wirelessly notified to the management center. Not only does it require new equipment for that purpose, but it is also necessary to distinguish between the impact and vibration caused by the running of the vehicle in determining whether or not the vehicle has collided or contacted, so collisions that can cause relatively large damage to the vehicle or If there is no contact, the determination information of collision (contact) is not notified to the management center, and the management center cannot confirm the occurrence of relatively small collision or damage due to contact, even if it is visually obvious.

Further, the conventional device is for the renter to unilaterally confirm that the vehicle user has caused damage to the vehicle, while the vehicle user is the vehicle user. There is a desire to prove that the vehicle was not damaged, such as new scratches or dents, during use.

The present invention has been made in view of such a problem, and it is necessary to appropriately manage whether or not a vehicle user has caused damage such as scratches or dents on the vehicle without requiring new equipment on the vehicle. and to provide a vehicle management server that is enabled.

The vehicle management server according to the present invention
A vehicle management server that has a communication function with the user terminal of the vehicle user.
The first vehicle image of the vehicle taken in the first hour and the second vehicle image of the vehicle taken in the second time after the first hour, received from the user terminal, are compared with each other. A determination means for determining whether or not the second vehicle image with respect to the first vehicle image has a change equal to or greater than a set threshold value.
An alert output means that outputs an alert when it is determined by the determination means that the second vehicle image with respect to the first vehicle image has a change equal to or greater than a set threshold value.
When it is determined by the determination means that the second vehicle image with respect to the first vehicle image has a change equal to or greater than a set threshold value, the first vehicle image determined to have the change and the second vehicle image. It is provided with a vehicle image output means for outputting a vehicle image .

According to the present invention, it is possible to appropriately manage whether or not a vehicle user has caused damage such as scratches or dents on the vehicle without requiring new equipment for the vehicle.

The figure which shows the whole structure of the vehicle management system 1 which concerns on embodiment of the program of the vehicle management server and the user terminal of this invention. The block diagram which shows the structure of the electronic circuit of the vehicle management server 10. The block diagram which shows the structure of the electronic circuit of a user terminal 30. The figure which shows an example of the management data for each user stored in the user management data storage area 12c. The figure which shows an example of the management data for each rental target vehicle stored in the vehicle management data storage area 12d. A flowchart showing a vehicle use process executed according to the vehicle management system use dedicated application (32a) of the user terminal 30. The figure which shows the operation example corresponding to the user operation before getting on the vehicle according to the vehicle use processing of a user terminal 30. The figure which shows the operation example corresponding to the user operation after getting on the vehicle according to the vehicle use processing of a user terminal 30. FIG. 5 is a flowchart showing a vehicle management process executed according to the vehicle management program (12a) of the vehicle management server 10. A flowchart showing an alert confirmation process executed according to the vehicle management program (12a) of the vehicle management server 10. The figure which shows the operation example of the vehicle confirmation alert AL according to the vehicle management process of the vehicle management server 10 and the operation example of alert confirmation by an administrator terminal 20 according to an alert confirmation process.

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

FIG. 1 is a diagram showing an overall configuration of a vehicle management system 1 according to an embodiment of a program of a vehicle management server and a user terminal of the present invention.

The vehicle management system 1 is, for example, an administrator terminal connected to the vehicle management server 10 of a vehicle renter who provides a vehicle rent service and the vehicle management server 10 directly or via a communication network (Internet / cloud). 20 and a user terminal 30 connected to the vehicle management server 10 via a communication network (Internet / cloud).

The administrator terminal 20 is operated by an employee of a vehicle renter or the like, and functions as an input / output terminal using a PC (Personal Computer) or the like for the vehicle management server 10.

The user terminal 30 is operated by a user (driver or the like) who rents a vehicle from a vehicle renter and installs a dedicated application 32a (see FIG. 3) for using the vehicle management system 1 and a camera 30C. It is configured using a tablet terminal with a light 30L, a smartphone, and the like.

FIG. 2 is a block diagram showing a configuration of an electronic circuit of the vehicle management server 10.

FIG. 3 is a block diagram showing a configuration of an electronic circuit of the user terminal 30.

As shown in FIG. 2, the vehicle management server 10 includes a CPU (processor) 11 as a computer.

The CPU (processor) 11 is read from a program stored in advance in a storage unit (storage) 12 such as a flash memory or an external recording medium 13 such as a CD-ROM by a recording medium reading unit 14 and stored in the storage unit 12. The operation of each circuit unit is controlled according to the program or the program downloaded from the Web server 40 (here, the program server) on the communication network N (Internet / cloud) via the communication unit 15 and installed in the storage unit 12.

In addition to the program storage area 12a, the storage unit 12 secures data storage areas such as a route search API storage area 12b, a user management data storage area 12c, and a vehicle management data storage area 12d.

In the program storage area 12a, in addition to the system program that controls the overall operation of the vehicle management server 10, a vehicle management program for managing the vehicle to be rented by communicating with the administrator terminal 20 and the user terminal 30 ( 12a) and the like are stored.

In the route search API storage area 12b, the Web server 40 (here, the route search server) on the communication network N is used, and the data of the position of an arbitrary place based on the map data and the recommended route between the positions of a plurality of places are used. The data of the route search API (Application Program Interface) for obtaining the data of the distance and the distance is stored.

The vehicle management server 10 includes map data instead of the route search API data, and based on the map data provided by the server 10 itself, the data of the position of an arbitrary place or the position of a plurality of places is provided. Data such as the recommended route and its distance may be obtained.

In the user management data storage area 12c, management data for each user who has made a contract with a vehicle renter to rent a vehicle is stored.

FIG. 4 is a diagram showing an example of management data for each user stored in the user management data storage area 12c.

As shown in FIG. 4, in the user management data area 12c, for each of a plurality of users, a user ID (identification number), a name, a telephone number of the user terminal 30, an email address of the user terminal 30, and so on. Each data such as the user's address is associated and stored.

In the vehicle management data storage area 12d, management data for each vehicle to be rented by the vehicle renter is stored.

FIG. 5 is a diagram showing an example of management data for each rental target vehicle stored in the vehicle management data storage area 12d.

As shown in FIG. 5, as the management data for each vehicle to be rented, for example, for each vehicle information SJ, the rental information L1, L2, ... For each rental of the vehicle corresponding to the vehicle information SJ is displayed. The data associated with the series is stored.

As the vehicle information SJ, data corresponding to each item including [rental number], [vehicle type], [vehicle number], and [parking place] is stored.

In [Rental No.], data of rental No., which is identification information added by the vehicle renter for each vehicle, is stored.

In [Vehicle type], data of the vehicle model name, which is vehicle identification information, is stored.

The number data, which is the vehicle identification information, is stored in the [vehicle number].

The data of the address which is the storage place of the vehicle is stored in the [parking place].

As the vehicle rental information Ln, data corresponding to each item including [rental date and time], [user ID], [vehicle image], [shooting confirmation], and [vehicle confirmation] is stored.

In the [rental date / time], data of the rental date / time, which is the rental start date / time to the return date / time of the vehicle corresponding to the vehicle information SJ, is stored.

The user ID data, which is the identification information of the vehicle user, is stored in the [user ID].

[Vehicle image] includes pre-boarding vehicle images (front) BIM1, (right side) BIM2, (left side) BIM3, (rear side) taken from four directions of the vehicle (vehicle body) by the user terminal 30 before boarding the vehicle. ) BIM4 and the data of the after-ride vehicle image (front) AIM1, (right side) AIM2, (left side) AIM3, and (rear side) AIM4 taken from four directions of the same vehicle (body) after boarding are stored.

In [shooting confirmation], the vehicle image (front) BIM1 to (rear surface) BIM4 before boarding is obtained from the user terminal 30, and the vehicle image (front) AIM1 to (rear surface) AIM4 after boarding is the user terminal 30. The shooting date and time and shooting position data recorded in the Exif (exchangeable image file format) file of any vehicle image (for example, (front)) are stored, and the shooting date and time of the vehicle image is stored. Data indicating whether or not the shooting position is appropriate is stored with / without shooting alert.

With / without shooting alert, when the vehicle image before boarding (front) BIM1 to (rear) BIM4 is obtained, the shooting date and time of the vehicle image before boarding is the rental start date and time of the [rental date and time] to the first half of the return date and time, for example. If it is included and the shooting position of the vehicle image before boarding is at the position corresponding to the address of [parking place] in the vehicle information SJ, it is determined that there is no shooting alert (appropriate), and the vehicle image before boarding is taken. When the date and time is not included in, for example, the first half of the rental start date and time to the return date and time of [rental date and time], or when the shooting position of the vehicle image before boarding is not at the position corresponding to the address of [parking place] in the vehicle information SJ. It is judged as "with shooting alert" (inappropriate: not the vehicle image taken before boarding the vehicle).

Similarly, when the vehicle image (front) AIM1 to (rear) AIM4 after boarding is obtained, the shooting date and time of the vehicle image after boarding is included in, for example, the latter half of the rental start date and time to the return date and time of [rental date and time]. When the shooting position of the vehicle image before boarding is at the position corresponding to the address of [parking place] in the vehicle information SJ, it is judged as "no shooting alert" (appropriate), and the shooting date and time of the vehicle image after boarding is [rental]. If the rental start date and time of [date and time] is not included in the latter half of the return date and time, or if the shooting position of the vehicle image after boarding is not at the position corresponding to the address of [parking place] in the vehicle information SJ, "shooting alert is available". "(Inappropriate: It is not a vehicle image taken after getting on the vehicle).

In [Vehicle confirmation], based on the comparison between the vehicle image (front) BIM1 to (rear surface) BIM4 before boarding and the vehicle image (front) AIM1 to (rear surface) AIM4 after boarding in [Vehicle image], before and after boarding. When there is a change above the threshold in the vehicle image in the same direction, the data of the vehicle confirmation alert indicating that the vehicle may have been damaged such as a new scratch or dent is stored, and the target of the vehicle confirmation alert is If there is a change of more than the threshold between the vehicle image before boarding (right side) BIM2 and the vehicle image after boarding (right side) AIM2, the vehicle image before boarding (right side) BIM2 and the vehicle image after boarding (right side) ) AIM2 data is stored.

For the storage form of the individual vehicle information SJ stored as management data for each vehicle to be rented and the rental information L1, L2, ... For each rental of the vehicle corresponding to the vehicle information SJ, refer to FIG. Not limited to the above-mentioned storage form, for example, the vehicle information SJ and its rental information L1, L2, ... Are stored in different storage areas, or the vehicle information SJ of the vehicle used by the user is used for each user. The loan information L1, L2, ... May be stored in association with each other, or may be stored in another storage form.

The storage unit 12, the recording medium reading unit 14, and the communication unit 15 are connected to the CPU 11 via the system bus, and the administrator terminal 20 is connected via the external device interface 16.

In the vehicle management server 10 configured in this way, the CPU 11 controls the operation of each part of the circuit according to the instruction described in the vehicle management program (12a), and the software and the hardware operate in cooperation with each other. A vehicle management function (see FIG. 9) and an alert confirmation function (see FIG. 10) as described in the operation description described later are realized.

As shown in FIG. 3, the user terminal 30 includes a CPU (processor) 31 as a computer.

The CPU (processor) 31 is a program stored in advance in a storage unit (storage) 32 such as a flash memory, or a program read by a recording medium reading unit 34 from an external recording medium 33 such as a memory card and stored in the storage unit 32. Alternatively, the operation of each circuit unit is controlled according to a program downloaded from the Web server 40 (program server in this case) on the communication network N (Internet / cloud) via the communication unit 35 and installed in the storage unit 32.

In addition to the program storage area 32a, the storage unit 32 secures data storage areas such as a user ID data storage area 32b, a current position data storage area 32c, an imaging data storage area 32d, and a vehicle image data storage area 32e.

In the program storage area 32a, in addition to the system program that controls the overall operation of the user terminal 30, a vehicle management system use-dedicated application for communicating with the vehicle management server 10 and making a required report according to the use of the vehicle. (32a) is stored.

In the user ID data storage area 32b, the data of the user's ID (identification information) using the user terminal 30 is stored in the user ID data storage area 32b according to, for example, the initial setting processing according to the vehicle management system use dedicated application (32a). It will be remembered.

In the current position data storage area 32c, data (current position data) indicating the current position acquired in response to the reception of the GPS (Global Positioning System) signal received by the GPS receiving unit 38 is stored.

In the imaging data storage area 32d, the imaging data captured by the imaging unit 37 as the camera 30C shown in FIG. 1 includes the current position stored in the current position data storage area 32c as the imaging position. Exif (exchangeable image file) format) Stored by a format file.

In the vehicle image data storage area 32e, four directions (front / right side) of the vehicle are sequentially photographed according to the user's operation before and after the vehicle is boarded according to the vehicle management system use dedicated application (32a). / Left side / rear side) vehicle image data is transferred and stored from the imaging data storage area 32d each time a vehicle image of one side of the vehicle is taken.

A storage unit 32, a recording medium reading unit 34, a communication unit 35, an imaging unit 37, and a GPS receiving unit 38 are connected to the CPU 31 via a system bus, and also functions as a key input unit by displaying a soft keyboard. A touch panel display unit 36, a microphone for a call, an audio input / output unit 39 that also functions as a speaker, and the like are connected.

In the user terminal 30 configured in this way, the CPU 31 controls the operation of each part of the circuit according to the instruction described in the vehicle management system use dedicated application (32a), and the software and the hardware operate in cooperation with each other. As a result, the vehicle utilization function (see FIG. 6) as described later in the operation description is realized.

Next, the operation of the vehicle management system 1 of the embodiment will be described.

<User terminal 30>
FIG. 6 is a flowchart showing a vehicle use process executed according to the vehicle management system use dedicated application (32a) of the user terminal 30.

FIG. 7 is a diagram showing an operation example corresponding to the user operation before getting on the vehicle according to the vehicle use process of the user terminal 30.

The vehicle to be rented, which the user has contracted to rent to the vehicle renter, is parked in a predetermined parking place specified by the renter.

When the user touch-operates the application activation icon AE of the standby screen GW displayed on the touch panel type display unit 36 by the user on the user terminal 30, for example, as shown in FIG. 7A, the CPU 31 uses the vehicle. The management system use dedicated application (32a) is activated, and the vehicle use process according to the dedicated application (32a) is started (step T1).

For example, the CPU 31 has two items [before boarding] and [after boarding] for selecting a report to be made for each of "before boarding" and "after boarding (at the time of return)" of the vehicle, which is obligatory when using the vehicle. ] Is displayed on the touch panel display unit 36 (step T2).

Since the user reports "before boarding" before boarding the rented vehicle, when the "before boarding" item is selected by the user in the report menu displayed on the display unit 36 (step T3). (Yes)), the CPU 31 sets the pre-ride flag in the storage unit 32 to “ON” (step T4), and as shown in FIG. 7 (A), the vehicle (body) RC in four directions (front / right side). A shooting message (for example, "Please shoot the vehicle from four directions according to the silhouette of the vehicle on the screen") for prompting the user to shoot the / left side / rear side) is displayed on the display unit 36 for a certain period of time ( Step T5). The shooting message may be output by voice.

The CPU 31 activates the imaging unit (camera) 37 (step T6). For example, first, the silhouette SIL1 on the front surface of the vehicle is displayed on the display unit 36 as a shooting guide, and the user displays the user terminal 30 on the front surface of the vehicle RC. The pre-boarding vehicle image (front) BIM1 corresponding to the imaged data of the front of the vehicle RC captured by the imaging unit (camera) 37 is displayed on the display unit 36 according to the holding to be photographed (step T7). ..

The CPU 31 recognizes and analyzes the image pickup data captured by the image pickup unit 37 (step T8), and for example, whether or not the image pickup state is appropriate with respect to the image pickup position, image pickup angle, and brightness of the image pickup data (“OK” or “OK” or “NG”) is determined based on the silhouette SILn of the vehicle for the imaging position and the imaging angle, and the brightness is determined based on the set determination value (step T9).

The CPU 31 displays a shooting indicator PI indicating the measurement state of the brightness of the imaging data at the right end of the display unit 36. Then, when it is determined that the shooting position and shooting angle are not appropriate, the silhouette SIln of the vehicle is displayed in red (default is white), and when it is determined that the brightness is not appropriate, the shooting indicator PI is displayed. Display in red (default is white). As a result, the shooting advice is displayed to the user (step T9 (No) → T10). The shooting advice may be output by voice.

The user adjusts the shooting position and shooting angle to be appropriate by changing the direction of the user terminal 30 with respect to the vehicle RC so that the silhouette SIln of the vehicle returns to white, and the light 30L is turned on and off or the amount of light emitted. Adjust so that the shooting indicator PI returns to white by changing.

The method of displaying the shooting guide by the processing of steps T7 to T10, determining whether or not the imaging state of the imaging data is appropriate, and displaying the photographing advice is not limited to the method described above, and the vehicle to be photographed is not limited to the method described above. Any method may be used as long as the vehicle image in the four directions (front / right / left / rear) can be taken as an appropriate image.

When it is determined that the imaging state of the imaging data of the front surface of the vehicle RC is "OK" (step T9 (Yes)), and the user operates to instruct the imaging (step T11 (Yes)). ), The CPU 31 stores the captured pre-ride vehicle image (front) BIM1 data in the vehicle image data storage area 32e (step T12).

Here, the CPU 31 determines whether or not the vehicle images (front) BIM1 to (rear) BIM4 in the four directions are stored in the vehicle image data storage area 32e (step T13).

When it is determined that the vehicle images (front) BIM1 to (rear) BIM4 in the four directions are not stored (step T13 (No)), the CPU 31 similarly repeats the processes of steps T7 to T12, and FIG. 7A ), The image of the vehicle before boarding (right side) BIM2 and the image of the vehicle before boarding (left side) BIM3 and the image of the vehicle before boarding (rear side) BIM4 before boarding the vehicle RC are sequentially captured in the vehicle image data storage area 32e. Remember.

When it is determined that the vehicle images (front) BIM1 to (rear) BIM4 in four directions are stored in the vehicle image data storage area 32e (step T13 (Yes)), the CPU 31 sets the pre-boarding flag in the storage unit 32 to ". In response to the determination of "ON" (step T14 [before boarding]), as shown in FIG. 7B, the vehicle image before boarding in four directions stored in the vehicle image data storage area 32e (front). The data of BIM1 to (rear) BIM4 are displayed as thumbnails on the display unit 36, and the vehicle on the communication network N (Internet / cloud) is displayed together with the user ID data stored in the user ID data storage area 32b. It is transmitted to the management server 10 (step T15).

As a result, the user can take a picture of the vehicle (vehicle body) on the front and right sides according to the vehicle management system use dedicated application (32a) before using the vehicle to be rented parked in the predetermined parking place. , Left side and rear side images can be sent to the renter's vehicle management server 10 as pre-boarding vehicle images (front) BIM1 to (rear) BIM4, and if at this point the vehicle (body) is already scratched or dented. If such damage has occurred, it can be proved that the damage was not caused by the user.

The user gets on the vehicle, makes the desired movement from the predetermined parking place, and then returns the vehicle to the predetermined parking place and gets off.

FIG. 8 is a diagram showing an operation example corresponding to a user operation after getting on the vehicle according to the vehicle use process of the user terminal 30.

Similar to the above-mentioned before getting on the vehicle, the user touches the application activation icon AE of the standby screen GW displayed on the touch panel display unit 36, for example, as shown in FIG. 8A, on the user terminal 30. When operated, the CPU 31 activates the vehicle management system use dedicated application (32a) and starts the vehicle use process according to the dedicated application (32a) (step T1).

The CPU 31 causes the touch panel display unit 36 to display a report menu (not shown) including two items [before boarding] and [after boarding] (step T2).

In order for the user to report "after boarding" after getting off the rented vehicle, when the item "after boarding" is selected by the user in the report menu displayed on the display unit 36 (step T16 (step T16). Yes)), the CPU 31 sets the post-ride flag in the storage unit 32 to “ON” (step T17), and as shown in FIG. 8A, the four directions (front surface) of the vehicle (body) RC after boarding. A shooting message (for example, "Please shoot the vehicle from four directions according to the silhouette of the vehicle on the screen") is displayed on the display unit 36 for a certain period of time to encourage the user to shoot the right side / left side / rear side. (Step T5).

The CPU 31 activates the image pickup unit (camera) 37 (step T6), and first displays the silhouette SIL1 on the front surface of the vehicle as a shooting guide on the display unit 36 as in the case before boarding the vehicle, and the user is the user. In response to holding the terminal 30 to capture the front surface of the vehicle RC, the display unit displays the post-ride vehicle image (front) AIM1 corresponding to the imaged data of the front surface of the vehicle RC imaged by the imaging unit (camera) 37. It is displayed on 36 (step T7).

The CPU 31 recognizes and analyzes the image pickup data captured by the image pickup unit 37 (step T8), and determines whether or not the image pickup state of the image pickup data is appropriate (step T9).

The CPU 31 displays shooting advice to the user in the same manner as before getting on the vehicle described above (step T9 (No) → T10).

When it is determined that the imaging state of the imaging data of the front surface of the vehicle RC is "OK" (step T9 (Yes)), and the user operates to instruct the imaging (step T11 (Yes)). ), The CPU 31 stores the captured data of the vehicle image (front) AIM1 after boarding in the vehicle image data storage area 32e (step T12).

When it is determined that the vehicle image (front) AIM1 to (rear) AIM4 in four directions are not stored in the vehicle image data storage area 32e (step T13 (No)), the CPU 31 performs the processes of steps T7 to T12. Repeatedly in the same manner, as shown in FIG. 8A, the vehicle image after boarding (right side) AIM2 and the vehicle image after boarding (left side) AIM3 after getting off the vehicle RC and after boarding, as in the case before boarding the vehicle. The vehicle image (rear surface) AIM4 is sequentially photographed and stored in the vehicle image data storage area 32e.

When it is determined that the vehicle images (front) AIM1 to (rear) AIM4 in four directions are stored in the vehicle image data storage area 32e (step T13 (Yes)), the CPU 31 sets the post-ride flag in the storage unit 32 to ". Depending on the determination that it is "ON" (step T14 [after boarding]), as shown in FIG. 8B, the vehicle image after boarding in four directions stored in the vehicle image data storage area 32e (front). The data of AIM1 to (rear surface) AIM4 are displayed as thumbnails on the display unit 36, and are transmitted to the vehicle management server 10 on the communication network N (Internet / cloud) together with the user ID data (step T18).

As a result, after returning the vehicle to a predetermined parking place using the vehicle, the user can take a picture of the vehicle (vehicle body) on the front, right, left, and rear surfaces according to the vehicle management system use dedicated application (32a). The image can be sent to the vehicle management server 10 of the renter as the vehicle image (front) AIM1 to (rear) AIM4 after boarding, and the pre-boarding vehicle image already sent to the vehicle management server 10 before boarding the vehicle. In addition to (front) BIM1 to (rear) BIM4, it is proved that the user has not caused any new damage to the vehicle due to the use of the vehicle this time, or even if it has caused the new damage. it can.

If the user touches the [Close] item in the report menu displayed on the touch panel display unit 36 in step T2 (step T19 (Yes)), the CPU 31 is dedicated to using the vehicle management system. The vehicle use process according to the application (32a) is terminated.

<Vehicle management server 10>
FIG. 9 is a flowchart showing a vehicle management process executed according to the vehicle management program (12a) of the vehicle management server 10.

FIG. 10 is a flowchart showing an alert confirmation process executed according to the vehicle management program (12a) of the vehicle management server 10.

FIG. 11 is a diagram showing an operation example of the vehicle confirmation alert AL according to the vehicle management process of the vehicle management server 10 and an operation example of alert confirmation by the administrator terminal 20 according to the alert confirmation process.

When the vehicle management server 10 receives the data of the vehicle image (front) BIM1 to (rear) BIM4 before boarding together with the data of the user ID transmitted from the user terminal 30 (step S1 (Yes)), the CPU 11 , The received vehicle image before boarding (front) BIM1 to (rear) BIM4 is associated with the [vehicle image] of the vehicle rental information Ln corresponding to the received user ID in the vehicle management data storage area 12d. It is memorized (step S2).

The CPU 11 acquires the rental start date / time to the return date / time in the [rental date / time] of the rental information Ln (step S3), and the vehicle image before boarding (front) BIM1 to (front) stored in the [vehicle image] of the rental information Ln. Before boarding the vehicle, depending on whether the shooting date and time recorded in the Exif file of any of BIM4 (rear side) BIM4 (here (front) BIM1) is included in the acquired lending start date and time to the return date and time, for example, the first half. It is determined whether or not the shooting date and time taken (that is, before use) is appropriate (step S4).

When the shooting date and time of the vehicle image (front) BIM1 before boarding is included in the first half of the rental start date and time to the return date and time and it is determined that the shooting date and time is appropriate (step S4 (Yes)), the CPU 11 determines the vehicle information SJ. The position corresponding to the address of [Parking place] is acquired from the Web server 40 (here, the route search server) based on the map data according to, for example, the route search API (32b) (step S5), and the [Vehicle image] of the rental information Ln is obtained. The shooting position recorded in the Exif file of any of the pre-boarding vehicle images (front) BIM1 to (rear) BIM4 (here (front) BIM1) stored in [] is set to the acquired [parking place] address. Depending on whether or not the vehicle is included within the allowable range of the corresponding position (for example, a radius of 5 m), it is determined whether or not the vehicle is appropriate as a shooting location photographed before boarding (that is, before using) (step S6).

In step S4, when the shooting date and time of the vehicle image BIMn before boarding is not included in the first half of the rental start date and time to the return date and time, and it is determined that the shooting date and time before boarding is inappropriate (step S4 (No)), or In step S6, when the shooting position of the vehicle image BIMn before boarding is not included within the allowable range of the position corresponding to the address of [parking place], and it is determined that the shooting position before boarding is inappropriate (. Step S6 (No)), the CPU 11 manages a pre-boarding shooting alert for warning that there is a possibility that the shooting date and time or shooting position of the pre-boarding vehicle image BIMn by the user of the received user ID is incorrect. It is transmitted to the user terminal 20 and output by display, voice, or printing (step S7). Further, the CPU 11 stores the data of "pre-boarding shooting alert" in association with [shooting confirmation] of the vehicle rental information Ln corresponding to the received user ID in the vehicle management data storage area 12d.

In step S4, it is determined that the shooting date and time of the vehicle image BIMn before boarding is appropriate as the shooting date and time before boarding (Step S4 (Yes)), and in step S6, the shooting position of the vehicle image BIMn before boarding is set. When it is determined that the shooting position is appropriate before boarding (step S6 (Yes)), the CPU 11 temporarily ends a series of vehicle management processes and waits.

After that, when the vehicle management server 10 receives the data of the vehicle image (front) AIM1 to (rear) AIM4 after boarding together with the data of the user ID transmitted from the user terminal 30 (step S8 (Yes)). Similar to the case where the pre-boarding vehicle image (front) BIM1 to (rear) BIM4 is received, the CPU 11 determines the vehicle rental information Ln corresponding to the received user ID in the vehicle management data storage area 12d. The received vehicle images (front) AIM1 to (rear) AIM4 after boarding are stored in association with the [vehicle image] of (step S9).

The CPU 11 acquires the rental start date / time to the return date / time in the [rental date / time] of the rental information Ln (step S10), and the vehicle image (front) after boarding AIM1 to (front) stored in the [vehicle image] of the rental information Ln. After boarding the vehicle, depending on whether or not the shooting date and time recorded in the Exif file of any of AIM4 (here, (front) AIM1) is included in the acquired lending start date and time to the return date and time, for example, the latter half. It is determined whether or not the shooting date and time taken (that is, after use) is appropriate (step S11).

When the shooting date and time of the vehicle image (front) AIM1 after boarding is included in the latter half of the rental start date and time to the return date and time and it is determined that the shooting date and time is appropriate (step S11 (Yes)), the CPU 11 determines the vehicle information SJ. The position corresponding to the address of the [parking place] is acquired based on the map data as described above (step S12), and the vehicle image after boarding (front) AIM1 to (front) stored in the [vehicle image] of the rental information Ln. The shooting position recorded in the Exif file of any of AIM4 (rear surface) (here (front) AIM1) is within the allowable range of the position corresponding to the acquired [parking place] address (for example, radius 5 m). Depending on whether or not the vehicle is included, it is determined whether or not the vehicle is appropriate as a shooting location where the vehicle was photographed after boarding (that is, after use) (step S13).

In step S11, when the shooting date and time of the vehicle image AIMn after boarding is not included in the latter half of the rental start date and time to the return date and time, and it is determined that the shooting date and time after boarding is inappropriate (step S11 (No)), or In step S13, when the shooting position of the vehicle image AIMn after boarding is not included within the allowable range of the position corresponding to the address of [parking place], and it is determined that the shooting position after boarding is inappropriate ( Step S13 (No)), the CPU 11 manages a post-boarding shooting alert to warn that there is a possibility that the shooting date and time or shooting position of the post-boarding vehicle image AIMn by the user of the received user ID is incorrect. It is transmitted to the user terminal 20 and output by display, voice, or printing (step S14). Further, the CPU 11 stores the data of "with shooting alert after boarding" in association with [shooting confirmation] of the vehicle rental information Ln corresponding to the received user ID in the vehicle management data storage area 12d.

In step S11, it is determined that the shooting date and time of the vehicle image AIMn after boarding is appropriate as the shooting date and time after boarding (step S11 (Yes)), and in step S13, the shooting position of the vehicle image AIMn after boarding is set. When it is determined that the shooting position is appropriate after boarding (step S13 (Yes)), the CPU 11 determines that the rental information Ln [vehicle] corresponding to the received user ID corresponds to the received user ID, as shown in FIG. 11 (A). The pre-ride vehicle image (front) BIM1 to (rear surface) BIM4 stored in the image] and the post-ride vehicle image (front) AIM1 to (rear surface) AIM4 are compared between vehicle images in the same direction. That is, the CPU 11 includes a vehicle image before boarding (front) BIM1, a vehicle image after boarding (front) AIM1, a vehicle image before boarding (right side) BIM2, a vehicle image after boarding (right side) AIM2, and a vehicle image before boarding (left side) BIM3. A comparison is made between the vehicle image after boarding (left side) AIM3, the vehicle image before boarding (rear side) BIM4, and the vehicle image after boarding (rear side) AIM4 (step S15).

The CPU 11 compares vehicle images (BIMn: AIMn) in the same direction before and after boarding of the user, analyzes a portion of the post-ride vehicle image AIMn with respect to the pre-ride vehicle image BIMn, and analyzes the changed portion. It is determined whether or not the degree (ratio) of a certain portion of the vehicle image to the entire AIMn is equal to or greater than the threshold value of the degree of change set in advance or arbitrarily set by the user (step S16).

The CPU 11 corrects, for example, differences in vehicle images (BIMn: AIMn) that are affected by their brightness, dirt, etc., and then compares their RGB levels in pixel units, as shown in FIG. 11 (A). , The portion where the RGB level change corresponding to the damage H1 and H2 such as scratches and dents is detected in the vehicle image AIMn after boarding with respect to the vehicle image BIMn before boarding. Then, the degree of the changed portion (ratio: corresponding to the magnitude of the damaged Hn) with respect to the entire vehicle image AIMn is calculated, and the degree is equal to or higher than the threshold value (for example, 2%) of the degree of change arbitrarily set by the user. It is determined whether or not it is (step S16).

As a result, it is determined whether or not the vehicle image AIMn after boarding is newly damaged with respect to the vehicle image BIMn before boarding.

In the present embodiment, the pre-ride vehicle image BIMn and the post-ride vehicle image AIMn are compared to detect a portion of the post-ride vehicle image AIMn that has a change corresponding to damage such as a new scratch or a dent. Of course, the method for this purpose is not limited to the method described above, and another method based on image processing or AI (artificial intelligence) may be used.

The degree of change in the vehicle image AIMn after boarding is equal to or greater than the set threshold of the degree of change between the vehicle images (BIMn: AIMn) in the same direction of the vehicle image BIMn before boarding and the vehicle image AIMn after boarding. When it is determined (step S16 (Yes)), the CPU 11 warns that the vehicle RC used by the user of the received user ID may have caused new damage Hn. The vehicle confirmation alert AL is transmitted to the administrator terminal 20 and output by display, voice, or printing (step S17). Further, the CPU 11 receives the data of the pre-ride vehicle image BIMn and the post-ride vehicle image AIMn for which the degree of change is determined to be equal to or higher than the threshold value together with the data of the “vehicle confirmation alert AL” in the vehicle management data storage area 12d. The vehicle rental information Ln corresponding to the user ID is stored in association with [Vehicle confirmation].

In the operation example shown in FIG. 11A, the pre-ride vehicle image BIMn and the post-ride vehicle image AIMn for which the degree of change is determined to be equal to or greater than the threshold value are the pre-ride vehicle image (right side) BIM2 and the damage H1. It corresponds to the vehicle image after boarding (right side) AIM2, the vehicle image before boarding (rear surface) BIM4, and the vehicle image after boarding (rear surface) AIM4 with damage H2.

According to the vehicle management process (see FIG. 9) of the vehicle management server 10, the pre-boarding shooting alert is output to the administrator terminal 20 in step S7, or the post-boarding shooting alert is output to the administrator terminal 20 in step S14. When the vehicle confirmation alert AL (see FIG. 11 (A)) is output to the administrator terminal 20 in step S17, for example, as shown in FIG. 11 (B), the vehicle confirmation alert AL (see FIG. 11 (A)) corresponds to the administrator terminal 20. The alert notification screen GAL for notifying the pre-boarding shooting alert, the post-boarding shooting alert, or the vehicle confirmation alert AL is displayed.

<Alert confirmation process (see Fig. 10)>
A pre-boarding shooting alert, a post-boarding shooting alert, or a vehicle confirmation alert AL is output from the vehicle management server 10 to the administrator terminal 30, and the alert notification screen GAL is displayed on the manager terminal 30 (step S21 (Yes). )), When the operation (confirmation request) for confirming the content of the alert is performed on the administrator terminal 30, the CPU 11 is the vehicle corresponding to the user ID outputting the alert in the vehicle management data storage area 12d. Based on the data associated with [Shooting confirmation] and [Vehicle confirmation] of the rental information Ln, the type of "alert" is "pre-boarding shooting alert" or "post-boarding shooting alert" or "vehicle confirmation alert". It is determined which of the above (steps S22 / S24).

Here, if it is determined as "pre-boarding shooting alert" (step S22 (Yes)), the CPU 11 associates with the [rental date and time] of the vehicle management data storage area 12d together with the user ID that outputs the alert. The shooting date and time and shooting of the pre-boarding vehicle image BIMn associated with [Shooting confirmation] for the rental start date and time of the vehicle, the return date and time, and the address that is the storage location of the vehicle associated with [Parking place]. By comparing the positions, a pre-boarding shooting alert confirmation screen for warning that the shooting date and time or shooting position of the pre-boarding vehicle image BIMn may be incorrect is generated and displayed on the administrator terminal 20 (step). S23).

Further, when it is determined as "post-boarding shooting alert" (step S22 (Yes)), the CPU 11 together with the user ID outputting the alert, as in the case of determining "pre-boarding shooting alert", is the vehicle. By comparing the shooting date and time of the vehicle image AIMn after boarding and the shooting position with respect to the rental start date and time to the return date and time and the address where the vehicle is stored, the shooting date and time or shooting position of the vehicle image AIMn after boarding is incorrect. A post-boarding shooting alert confirmation screen for warning that there is a possibility is generated and displayed on the administrator terminal 20 (step S23).

Further, when it is determined as "vehicle confirmation alert" (step S24 (Yes)), the CPU 11 together with the user ID outputting the alert, the vehicle management data storage area 12d, as shown in FIG. 11B. By comparing the pre-ride vehicle image BIMn and the post-ride vehicle image AIMn associated with [Vehicle confirmation] in the above, it is possible that the vehicle RC used by the user may have a new damage Hn. A vehicle confirmation alert confirmation screen for warning is generated and displayed on the administrator terminal 20 (step S25).

In the operation example shown in FIG. 11B, the user ID "5165456" that outputs the alert is compared with the pre-ride vehicle image (right side) BIM2 and the post-ride vehicle image (right side) AIM2 with the damage H1. Further, a vehicle confirmation alert confirmation screen generated by comparing the vehicle image before boarding (rear surface) BIM4 with the vehicle image after boarding (rear surface) AIM4 in which the damage H2 has occurred is shown.

When the user ID displayed in the confirmation screen is specified on the pre-boarding shooting alert confirmation screen, the post-boarding shooting alert confirmation screen, or the vehicle confirmation alert confirmation screen displayed on the administrator terminal 20, (step S26 (step S26 (step S26) Yes)), the CPU 11 stores the user management data (name, telephone number, email address, address, etc.) of the corresponding user stored in the user management data storage area 12c based on the designated user ID. It is read out and displayed on the administrator terminal 20 (step S27).

As a result, the employee of the vehicle renter who operates the administrator terminal 20 can easily obtain the information of the user whose alert is output together with the content of the warning of the pre-boarding shooting alert, the post-boarding shooting alert, or the vehicle confirmation alert AL. And it can be confirmed quickly.

<Summary of Embodiment>
According to the vehicle management system 1 of the embodiment, the vehicle user uses the user terminal 30 to move the vehicle in four directions [before boarding] before boarding the rented vehicle according to the vehicle management system use dedicated application (32a). When the image is taken from (front / right / left / rear), each data of the photographed vehicle image before boarding (front) BIM1 to (rear) BIM4 is transmitted to the vehicle management server 10 together with the user ID.

In addition, after the vehicle user gets off the rented vehicle [after boarding] according to the vehicle management system use dedicated application (32a) by the user terminal 30, the vehicle is again moved in four directions (front / right / left / rear). ), Each data of the photographed vehicle image (front) AIM1 to (rear) AIM4 after boarding is transmitted to the vehicle management server 10 together with the user ID.

The vehicle management server 10 uses the received vehicle images before boarding (front) BIM1 to (rear surface) BIM4 and vehicle images after boarding (front) AIM1 to (rear surface) AIM4 in the same direction (BIMn: AIMn). The degree (ratio) of the changed part of the vehicle image AIMn after boarding with respect to the vehicle image BIMn before boarding is greater than or equal to the threshold of the degree of change set in advance or arbitrarily set by the user. It is possible to determine whether or not there is a damage Hn such as a new scratch or dent on the vehicle after use, and if the degree of change is equal to or greater than the threshold value, a new damage Hn has occurred. A vehicle confirmation alert AL for warning that there is a possibility is output to the administrator terminal 20.

The vehicle management server 10 responds to the confirmation request of the vehicle confirmation alert AL from the administrator terminal 20 by displaying the pre-boarding vehicle image BIMn and the post-boarding vehicle image AIMn that are the alert targets together with the user ID that is the alert target. A comparison vehicle confirmation alert confirmation screen is generated and displayed on the administrator terminal 20.

Therefore, the vehicle renter does not need new equipment for the vehicle and does not need to check the vehicle directly, and properly manages whether the vehicle user has caused damage such as scratches or dents on the vehicle. It becomes possible to do.

In addition, the vehicle user can prove to the vehicle renter that he / she did not cause any damage such as new scratches or dents to the vehicle while using the vehicle, and also causes new damage. Even if it does, the new damage caused can be proved.

The vehicle management server 10 acquires the vehicle rental start date / time to the return date / time associated with the [rental date / time] of the vehicle management data storage area 12d and the address of the storage location of the vehicle associated with the [parking location]. , Received pre-boarding vehicle image Whether the shooting date and time recorded in the BIMn Exif file is appropriate as the pre-boarding shooting date and time for the vehicle rental start date and time to the return date and time, or the vehicle image before boarding It is determined whether the shooting position recorded in the BIMn Exif file is appropriate as the shooting position before boarding with respect to the address of the storage location of the vehicle, and if the shooting date and time or shooting position before boarding is not appropriate, Pre-boarding vehicle image A pre-boarding shooting alert for warning that the shooting date and time or shooting position of BIMn may be incorrect is output to the administrator terminal 20.

Similarly, the vehicle management server 10 has a vehicle rental start date / time to a return date / time associated with the [rental date / time] of the vehicle management data storage area 12d, and an address of the storage location of the vehicle associated with the [parking location]. The shooting date and time recorded in the received Exif file of the vehicle image after boarding is appropriate for the vehicle rental start date and time to the return date and time as the shooting date and time after boarding, or whether or not the vehicle is on board. Rear vehicle image It is determined whether or not the shooting position recorded in the Exif file of AIMn is appropriate as the shooting position after boarding with respect to the address of the storage location of the vehicle, and the shooting date and time or shooting position after boarding is appropriate. If not, a post-ride shooting alert is output to the administrator terminal 20 to warn that there is a possibility that the shooting date and time or shooting position of the post-ride vehicle image AIMn is incorrect.

Then, the vehicle management server 10 responds to the confirmation request of the pre-boarding shooting alert or the post-boarding shooting alert from the administrator terminal 20, together with the user ID that is the alert target, the vehicle rental date and time, and the vehicle parking (storage). ) Generate a pre-boarding shooting alert confirmation screen or a post-boarding shooting alert confirmation screen that compares the shooting date and time and shooting position of the pre-boarding vehicle image BIMn or the post-boarding vehicle image AIMn that was the target of the alert, and the administrator terminal 20 To display.

Therefore, the vehicle renter does not require any new equipment for the vehicle, and the user can use the vehicle based on the pre-ride vehicle image BIMn and the post-ride vehicle image AIMn taken by the user terminal 30. Not only is it possible to properly manage whether or not new damage has occurred to the vehicle, but also the vehicle image BIMn before boarding and the vehicle image AIMn after boarding are shot at the proper shooting date and time and at the proper shooting position. It will be possible to properly manage whether or not it has been used.

In the vehicle management process of the vehicle management server 10 shown in FIG. 9, when the shooting date and time of the vehicle image BIMn before boarding is appropriate, it is determined whether or not the shooting position is appropriate, and similarly, after boarding. When the shooting date and time of the vehicle image AIMn is appropriate, it is determined whether or not the shooting position is appropriate. However, it is determined whether or not the shooting date and time is appropriate and whether or not the shooting position is appropriate. It may be performed in parallel, and the shooting alerts before and after boarding may be output separately as a shooting date / time alert and a shooting position alert.

Further, in the vehicle management process of the vehicle management server 10 shown in FIG. 9, when it is determined that the shooting date and time and the shooting position of the vehicle image AIMn after boarding are appropriate, the vehicle image BIMn before boarding and the vehicle image AIMn after boarding are determined. It was configured to determine whether or not there is a change corresponding to new damage in the vehicle image AIMn after boarding by comparing with, but whether or not the shooting date and time and the shooting position of the vehicle image AIMn after boarding are appropriate. Regardless of the determination, it may be configured to determine whether or not there is a change corresponding to new damage in the vehicle image AIMn after boarding.

Each processing method by the vehicle management server 10 of the vehicle management system 1 and the user terminal 30 described in each of the above embodiments, that is, the vehicle utilization processing shown in the flowchart of FIG. 6, the vehicle management processing shown in the flowchart of FIG. Each method such as the alert confirmation process shown in the flowchart of FIG. 10 is a program that can be executed by a computer, such as a memory card (ROM card, RAM card, etc.), a magnetic disk (floppy (registered trademark) disk, hard disk, etc.). ), Optical discs (CD-ROM, DVD, etc.), semiconductor memory, and other recording media can be stored and distributed.

Further, the data of the program for realizing each method of each of the above-described embodiments can be transmitted on the communication network in the form of the program code, and the program data can be transmitted to the computer of the electronic device connected to the communication network ( By incorporating the data into the processor) by the communication unit, various functions including the vehicle use function, the vehicle management function, and the alert confirmation function described above can be realized.

The present invention is not limited to the above-described embodiment, and can be variously modified at the implementation stage without departing from the gist thereof. In addition, each embodiment may be carried out in combination as appropriate, in which case the combined effect can be obtained. Further, the above-described embodiment includes various inventions, and various inventions can be extracted by a combination selected from a plurality of disclosed constituent requirements. For example, even if some constituent requirements are deleted from all the constituent requirements shown in the embodiment, if the problem can be solved and the effect is obtained, the configuration in which the constituent requirements are deleted can be extracted as an invention.

1 ... Vehicle management system 10 ... Vehicle management server 11 ... CPU (server)
12 ... Storage unit (server)
12a ... Program storage area (vehicle management program)
12b ... Route search API storage area 12c ... User management data storage area 12d ... Vehicle management data storage area 15 ... Communication unit (server)
16 ... External device interface 20 ... Administrator terminal 30 ... User terminal 31 ... CPU (user terminal)
32 ... Storage unit (user terminal)
32a ... Program storage area (app for exclusive use of vehicle management system)
32b ... User ID data storage area 32c ... Current position data storage area 32d ... Imaging data storage area 32e ... Vehicle image data storage area 35 ... Communication unit (user terminal)
36 ... Touch panel display unit 37 ... Imaging unit 38 ... GPS receiver 40 ... Web server (program server / route search server)
N ... Communication network (Internet / Cloud)
AE ... App launch icon SILn ... Vehicle silhouette (shooting guide)
PI… Shooting indicator (shooting advice)
BIMn ... Vehicle image before boarding AIMn ... Vehicle image after boarding Hn ... Damage AL ... Vehicle confirmation alert GAL ... Alert notification screen

Claims (7)

A vehicle management server that has a communication function with the user terminal of the vehicle user.
The first vehicle image of the vehicle taken in the first hour and the second vehicle image of the vehicle taken in the second time after the first hour, received from the user terminal, are compared with each other. A determination means for determining whether or not the second vehicle image with respect to the first vehicle image has a change equal to or greater than a set threshold value.
An alert output means that outputs an alert when it is determined by the determination means that the second vehicle image with respect to the first vehicle image has a change equal to or greater than a set threshold value.
When it is determined by the determination means that the second vehicle image with respect to the first vehicle image has a change equal to or greater than a set threshold value, the first vehicle image determined to have the change and the second vehicle image. A vehicle image output means for outputting a vehicle image and
Vehicle management server equipped with. A confirmation request receiving means for receiving a confirmation request for the alert after the alert is output by the alert output means is provided.
When the confirmation request for the alert is received by the confirmation request receiving means, the vehicle image output means outputs the first vehicle image and the second vehicle image determined to have the change.
The vehicle management server according to claim 1 . The first vehicle image is a vehicle image taken before the user uses the vehicle, and the second vehicle image is a vehicle image taken after the user uses the vehicle.
The vehicle management server according to claim 1 or 2 . The first vehicle image and the second vehicle image are vehicle images of the vehicle taken from the same direction.
The vehicle management server according to any one of claims 1 to 3 . The first vehicle image has a plurality of first vehicle images obtained by photographing the vehicle from a plurality of directions.
The second vehicle image has a plurality of second vehicle images obtained by capturing the vehicle from the same plurality of directions as the first vehicle image.
The determination means is set as a second vehicle image with respect to the compared first vehicle image by comparing the plurality of first vehicle images and the plurality of second vehicle images for each vehicle image taken from the same direction. To determine if there is a change above the threshold,
The vehicle management server according to claim 4 . The rental date and time acquisition means for acquiring the rental date and time of the vehicle, and
Based on the first shooting date and time included in the imaging data of the first vehicle image or the second shooting date and time included in the imaging data of the second vehicle image, and the rental date and time of the vehicle acquired by the rental date and time acquisition means. Then, the shooting date / time determining means for determining whether or not the first shooting date / time or the second shooting date / time is appropriate, and
A shooting date / time alert output means that outputs a shooting date / time alert when the first shooting date / time or the second shooting date / time is determined to be inappropriate by the shooting date / time determination means.
The vehicle management server according to any one of claims 1 to 5 . A parking position acquisition means for acquiring a position corresponding to the parking location of the vehicle, and
Corresponds to the first shooting position included in the captured data of the first vehicle image or the second shooting position included in the captured data of the second vehicle image, and the parking place of the vehicle acquired by the parking position acquisition means. A shooting position determining means for determining whether or not the first shooting position or the second shooting position is appropriate based on the position, and
A shooting position alert output means that outputs a shooting position alert when the first shooting position or the second shooting position is determined to be inappropriate by the shooting position determining means.
The vehicle management server according to any one of claims 1 to 6 , further comprising.