Management device, server, vehicle management system, management method, processing method for server, management program, and server program

Abstract

A vehicle management system (10) comprises: a vehicle management device (50) that acquires data related to sound detected by an acoustic sensor (25) that detects sound caused by contact between a vehicle (20) and objects outside the vehicle (20) and outputs information related to impact at the vehicle (20) not associated with shaking at the vehicle (20) as obtained from the data related to the sound; and a server (80) that, for a plurality of vehicles (20), acquires the information related to impact at the vehicle (20) not associated with shaking at the vehicle (20), associates the information about impact at the vehicle (20) not associated with shaking at the vehicle (20) with an identification number for the vehicle (20), and outputs the associated information to a terminal (90) of a manager that manages the vehicle (20).

Description

Management device, server, vehicle management system, management method, server processing method, management program, and server program CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is based on Japanese Patent Application No. 2024-120870, filed on July 26, 2024, the contents of which are incorporated herein by reference.

[0002] The present disclosure relates to a management device, a server, a vehicle management system, a management method, a server processing method, a management program, and a server program.

[0003] As described in Patent Document 1, a data processing device mounted on a vehicle is known, which includes an acceleration sensor, an in-vehicle voice recorder, a voice database, an abnormality determination means, and an abnormality data transmission means. The acceleration sensor detects acceleration and impact during vehicle movement. The in-vehicle voice recorder records voice data inside the vehicle. The voice database stores the voice data recorded by the in-vehicle voice recorder. The abnormality determination means determines whether an abnormality has occurred based on the acceleration data from the acceleration sensor. When the abnormality determination means determines that an abnormality has occurred, the abnormality data transmission means transmits in-vehicle voice data before and after the abnormality occurred to a vehicle management server that manages the vehicle and the driver using the vehicle.

[0004] Japanese Patent Application Laid-Open No. 2020-13353

[0005] The data processing device described in Patent Document 1 determines whether an abnormal situation has occurred based on acceleration data, which is information associated with changes in acceleration. Therefore, the abnormal situation determined by the data processing device described in Patent Document 1 is a collision accompanied by vehicle shaking. Therefore, the data processing device described in Patent Document 1 cannot determine collisions that do not involve vehicle shaking, such as a scrape between the vehicle and an object, contact between the vehicle and a flying stone, or contact between the door and an object while the vehicle is stopped.

[0006] The present disclosure aims to provide a management device, a server, a vehicle management system, a management method, a server processing method, a management program, and a server program that output information about a collision that does not involve vehicle shaking.

[0007] According to one aspect of the present disclosure, there is provided a management device including: an acquisition unit that acquires data related to sound detected by an acoustic sensor that detects sound generated by contact between a vehicle and an object external to the vehicle; and an output unit that outputs information related to a vehicle collision not involving vehicle sway obtained from the sound-related data. According to another aspect of the present disclosure, there is provided a management method that includes acquiring data related to sound detected by the acoustic sensor that detects sound generated by contact between a vehicle and an object external to the vehicle; and outputting information related to a vehicle collision not involving vehicle sway obtained from the sound-related data. According to yet another aspect of the present disclosure, there is provided a management program that causes the management device to function as an acquisition unit that acquires data related to sound detected by the acoustic sensor that detects sound generated by contact between the vehicle and an object external to the vehicle, and an output unit that outputs information related to a vehicle collision not involving vehicle sway obtained from the sound-related data.

[0008] According to one aspect of the present disclosure, there is provided a server including: an acquisition unit that acquires, for a plurality of vehicles, information regarding vehicle collisions not accompanied by vehicle shaking obtained from data regarding sound detected by an acoustic sensor that detects sound generated by contact between the vehicle and an object external to the vehicle; a link unit that associates the information regarding vehicle collisions not accompanied by vehicle shaking with the vehicle identification numbers; and an output unit that outputs the information associated by the link unit to a terminal of an administrator who manages the vehicles. According to another aspect of the present disclosure, there is provided a processing method of a server including: acquiring, for a plurality of vehicles, information regarding vehicle collisions not accompanied by vehicle shaking obtained from data regarding sound detected by an acoustic sensor that detects sound generated by contact between the vehicle and an object external to the vehicle; associating the information regarding vehicle collisions not accompanied by vehicle shaking with the vehicle identification numbers; and outputting the associated information to a terminal of an administrator who manages the vehicles. According to one aspect of the present disclosure, there is provided a server program that causes a server to function as an acquisition unit that acquires, for a plurality of vehicles, information regarding vehicle collisions that do not involve vehicle shaking, which is obtained from data regarding sounds detected by an acoustic sensor that detects sounds generated by contact between the vehicle and an object external to the vehicle, a link unit that associates the information regarding vehicle collisions that do not involve vehicle shaking with the vehicle identification number, and an output unit that outputs the information associated by the link unit to a terminal of an administrator who manages the vehicles.

[0009] Furthermore, according to one aspect of the present disclosure, there is provided a vehicle management system including: a management device that acquires data relating to sounds detected by an acoustic sensor that detects sounds generated by contact between a vehicle and an object external to the vehicle, and outputs information relating to vehicle collisions that do not involve vehicle shaking obtained from the sound data; and a server that acquires information relating to vehicle collisions that do not involve vehicle shaking for a plurality of vehicles, associates the information relating to vehicle collisions that do not involve vehicle shaking with the vehicle identification numbers, and outputs the associated information to a terminal of an administrator that manages the vehicles.

[0010] This allows output of information relating to a vehicle collision that does not involve vehicle shaking.

[0011] 1. A configuration diagram of a vehicle management system of a first embodiment. A diagram showing a vehicle of the vehicle management system. A flowchart showing the processing of a vehicle management device of the vehicle management system. A flowchart showing the processing of a server of the vehicle management system. A configuration diagram of a vehicle management system of a second embodiment. A configuration diagram of a vehicle management system of a third embodiment. A flowchart showing the processing of a server of the vehicle management system. A configuration diagram of a vehicle management system of a fourth embodiment. A flowchart showing the processing of a vehicle management device of the vehicle management system. A table showing the relationship between collision sounds detected by an acoustic sensor of a vehicle in a vehicle management system and the acceleration of the vehicle.

[0012] Hereinafter, embodiments will be described with reference to the drawings. In the following embodiments, identical or equivalent parts will be denoted by the same reference numerals, and description thereof will be omitted.

[0013] (First Embodiment) A vehicle management system including a management device that uses a management method and executes a management program according to this embodiment, and a server that uses a server processing method and executes a server program, outputs information about collisions that do not involve vehicle shaking. This vehicle management system is used in car sharing businesses, rental car businesses, etc. First, this vehicle management system will be described.

[0014] As shown in FIG. 1 , the vehicle management system 10 includes a vehicle 20 , a server 80 , and an administrator terminal 90 .

[0015] The vehicle 20 is managed by a car sharing business operator or a rental car business operator. The car sharing business operator and the rental car business operator correspond to managers who manage the vehicle 20.

[0016] 2 , the vehicle 20 has a left front corner 202, a right front corner 204, a left rear corner 206, and a right rear corner 208. The left front corner 202 is a corner of the vehicle 20 on the left front side of the vehicle 20. The right front corner 204 is a corner of the vehicle 20 on the right front side of the vehicle 20. The left rear corner 206 is a corner of the vehicle 20 on the left rear side of the vehicle 20. The right rear corner 208 is a corner of the vehicle 20 on the right rear side of the vehicle 20.

[0017] Furthermore, returning to FIG. 1 , the vehicle 20 has an acoustic sensor 25 , a GNSS receiver 30 , an exterior camera 35 , a vehicle speed sensor 40 , a vehicle energy detection device 45 and a vehicle management device 50 .

[0018] As shown in FIG. 2 , multiple acoustic sensors 25 are arranged on the vehicle 20, one at each of the left front corner 202, the right front corner 204, the left rear corner 206, and the right rear corner 208. Each acoustic sensor 25 includes a condenser microphone, a MEMS microphone, a piezoelectric microphone, or the like. This allows the acoustic sensor 25 to collect sounds outside the vehicle 20. The acoustic sensor 25 then converts the collected sounds into electrical signals. The acoustic sensor 25 then transmits the converted electrical signals to the vehicle management device 50 (described below) as data related to the detected sounds. A condenser microphone outputs an electrical signal representing a change in capacitance caused by a thin diaphragm vibrating due to sound pressure. A MEMS microphone is a compact microphone assembled and packaged with a MEMS chip, which serves as an acoustic transducer, and an IC chip, which processes signals. MEMS stands for Micro Electro Mechanical Systems. IC stands for Integrated Circuit. A piezo microphone is a microphone that uses a piezoelectric element to convert sound into an electrical signal.

[0019] 1 , the GNSS receiver 30 receives signals from a plurality of positioning satellites (not shown). Furthermore, the GNSS receiver 30 estimates the location of the vehicle 20 based on the received signals. Furthermore, the GNSS receiver 30 transmits data related to the estimated location of the vehicle 20 to a vehicle management device 50 (described below). Note that the positioning satellites used by the GNSS receiver 30 include, for example, GPS satellites, GLONASS satellites, Galileo satellites, and quasi-zenith satellites.

[0020] A plurality of exterior cameras 35 are arranged on the vehicle 20. Furthermore, the exterior cameras 35 capture images of scenery, objects, etc. outside the vehicle 20. Furthermore, the exterior cameras 35 transmit the captured images to the vehicle management device 50, which will be described later.

[0021] The vehicle speed sensor 40 detects the speed of the vehicle 20 and transmits data relating to the detected speed of the vehicle 20 to a vehicle management device 50 described below.

[0022] The vehicle energy detection device 45 detects the remaining energy of the battery and the remaining fuel of the vehicle 20. For example, the vehicle energy detection device 45 has a voltage sensor to detect the remaining battery capacity of the vehicle 20. Furthermore, the vehicle energy detection device 45 has a fuel sensor to detect the remaining fuel capacity of the vehicle 20. The vehicle energy detection device 45 also transmits the detected data related to the energy of the vehicle 20 to the vehicle management device 50, which will be described later.

[0023] The vehicle management device 50 corresponds to a management device and is mainly composed of a microcomputer and includes a CPU, ROM, flash memory, RAM, I / O, a communication interface, a speaker, a display, and a bus line connecting these components. Furthermore, the vehicle management device 50 executes a program stored in the ROM of the vehicle management device 50. As a result, the vehicle management device 50 acquires data from the acoustic sensor 25, the GNSS receiver 30, the exterior camera 35, the vehicle speed sensor 40, and the vehicle energy detection device 45. Furthermore, the vehicle management device 50 generates information about the vehicle 20 based on this acquired data. Furthermore, the vehicle management device 50 outputs the generated information about the vehicle 20 to the server 80 (described below). Furthermore, the vehicle management device 50 notifies the occupants of the vehicle 20 of the information about the vehicle 20 based on the generated information about the vehicle 20 using, for example, text display, sound, and light. Furthermore, based on the generated information about the vehicle 20, the vehicle management device 50 notifies the car sharing business operator and the rental car business operator of the information about the vehicle 20 via the administrator terminal 90, which will be described later, using, for example, text display, sound, and light. Details of the generation of information about the vehicle 20 by the vehicle management device 50 and the information to be notified to the occupants of the vehicle 20 will be described later.

[0024] The server 80 is mainly composed of a microcomputer and includes a CPU, ROM, flash memory, RAM, I / O, a communication interface, and a bus line connecting these components. Furthermore, the server 80 executes a program stored in the ROM of the server 80. As a result, the server 80 acquires information about the vehicles 20 from the vehicle management device 50. The vehicle management system 10 is equipped with multiple vehicles 20, and the server 80 acquires information about the vehicles 20 from the vehicle management device 50 for each of the multiple vehicles 20. The server 80 associates the acquired information about the vehicles 20 with the identification numbers of the vehicles 20. The server 80 outputs the associated information about each vehicle 20 to the administrator terminal 90, which will be described later. Details of the processing by the server 80 will be described later.

[0025] The administrator terminal 90 is a terminal owned by the car sharing business operator or the rental car business operator. Furthermore, the administrator terminal 90 acquires information from the vehicle management device 50 and the server 80. Furthermore, the administrator terminal 90 displays the information acquired from the vehicle management device 50 and the server 80 on a display or the like. This allows the car sharing business operator or the rental car business operator to check information about the vehicles 20 that they manage.

[0026] The vehicle management system 10 of the first embodiment is configured as described above. Next, the generation of information about the vehicle 20 by the execution of the program of the vehicle management device 50 and the details of the information to be notified to the occupants of the vehicle 20 will be described with reference to the flowchart of Figure 3. The program of the vehicle management device 50 is executed, for example, when the power of the vehicle 20 is turned on.

[0027] In step S100, the vehicle management device 50 acquires various data. Specifically, the vehicle management device 50 acquires data related to sounds detected by the acoustic sensor 25 from the acoustic sensor 25. Furthermore, the vehicle management device 50 acquires data related to the location of the vehicle 20 from the GNSS receiver 30. Furthermore, the vehicle management device 50 acquires image data of the area around the vehicle 20 from the exterior camera 35. Furthermore, the vehicle management device 50 acquires data related to the speed of the vehicle 20 from the vehicle speed sensor 40. Furthermore, the vehicle management device 50 acquires data related to the energy of the vehicle 20 from the vehicle energy detection device 45.

[0028] Next, in step S102, the vehicle management device 50 generates information about a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 as one piece of information about the vehicle 20 based on the data acquired in step S100.

[0029] Here, a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 includes scraping of the vehicle 20 against an object, contact of the vehicle 20 with a flying stone, contact of the door with an object while the vehicle is stopped, etc. Furthermore, the acoustic sensor 25 detects sounds outside the vehicle 20, and the sounds detected by the acoustic sensor 25 include sounds generated by contact between the vehicle 20 and an object outside the vehicle 20. Furthermore, the sounds generated by contact between the vehicle 20 and an object outside the vehicle 20 include sounds of a collision of the vehicle 20 that involves shaking of the vehicle 20 and sounds of a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20.

[0030] Then, the vehicle management device 50 uses machine learning to determine whether the sound data acquired from the acoustic sensor 25 in step S100 includes the sound of a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20.

[0031] For example, the vehicle management device 50 uses an SVM with MFCC as training data to determine whether the sound-related data acquired from the acoustic sensor 25 in step S100 includes the sound of a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20. MFCC stands for Mel-Frequency Cepstrum Coefficients. SVM stands for Support Vector Machine.

[0032] Alternatively, the vehicle management device 50 may use, for example, deep learning using a log-mel spectrogram as training data to determine whether the sound data acquired from the acoustic sensor 25 in step S100 includes the sound of a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20.

[0033] In addition, when the data contains the sound of a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20, the vehicle management device 50 identifies the type of minor collision using machine learning such as the SVM or deep learning described above.

[0034] Furthermore, when the data includes the sound of a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20, the vehicle management device 50 associates the sound of the minor collision with the time at which the sound occurred. Furthermore, the vehicle management device 50 associates the sound of the minor collision with the location at which the sound occurred, using data regarding the location of the vehicle 20 acquired from the GNSS receiver 30 in step S100. Furthermore, the vehicle management device 50 associates the sound of the minor collision with the image at the time the sound occurred, using image data acquired from the exterior camera 35 in step S100.

[0035] Furthermore, when the data includes the sound of a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20, the vehicle management device 50 uses the map and the ratio of the volumes of the minor collisions detected by the multiple acoustic sensors 25. This allows the vehicle management device 50 to estimate the location of the vehicle 20 where the minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 occurred. The map is set through experiments, simulations, etc., so as to estimate the location of the vehicle 20 where the minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 occurred. For example, assume that the ratio between the volume of the minor collision detected by the acoustic sensor 25 at the left front corner 202 and the volume of the minor collision detected by the acoustic sensor 25 at the left rear corner 206 is 0.50. Furthermore, assume that the volume of the minor collision detected by the acoustic sensor 25 at the right front corner 204 and the volume of the minor collision detected by the acoustic sensor 25 at the right rear corner 208 are zero. At this time, the vehicle management device 50 estimates that the location of the vehicle 20 where the minor collision that did not involve shaking of the vehicle 20 occurred was the center of the left side of the vehicle 20 .

[0036] Furthermore, when the data includes the sound of a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20, the vehicle management device 50 uses data related to the speed of the vehicle 20 acquired from the vehicle speed sensor 40 in step S100. This allows the vehicle management device 50 to determine whether the minor collision was caused intentionally or accidentally by the occupant of the vehicle 20. For example, when the speed of the vehicle 20 is greater than zero when the sound of a minor collision occurs, the occupant of the vehicle 20 is driving the vehicle 20. Therefore, at this time, the vehicle management device 50 determines that the minor collision was caused intentionally or accidentally by the occupant of the vehicle 20. Furthermore, when the speed of the vehicle 20 is zero when the sound of a minor collision occurs, the occupant of the vehicle 20 is not driving the vehicle 20. Therefore, at this time, the vehicle management device 50 determines that the minor collision was not caused intentionally or accidentally by the occupant of the vehicle 20.

[0037] Therefore, the vehicle management device 50 associates the occurrence or non-occurrence of a minor collision, the type of minor collision, the time of the minor collision, the location of the minor collision, the image at the time of the minor collision, the location of the vehicle 20 where the minor collision occurred, and whether the minor collision was caused by the intentional or negligent act of the occupants of the vehicle 20. Furthermore, the vehicle management device 50 generates information associating these items as information regarding a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20.

[0038] Next, in step S104, the vehicle management device 50 generates information about the dirt on the vehicle 20 as one piece of information about the vehicle 20 based on the data acquired in step S100.

[0039] Here, when the vehicle 20 travels on a rough road such as a muddy road, there is a high possibility that dirt such as mud will adhere to the vehicle 20. Furthermore, when the vehicle 20 travels on a rough road such as a muddy road, a specific sound corresponding to the travel is generated.

[0040] Therefore, the vehicle management device 50 uses machine learning such as the SVM or deep learning to determine whether the sound-related data acquired from the acoustic sensor 25 in step S100 includes the sound of the vehicle 20 traveling on a rough road such as a muddy road. Furthermore, when the data includes the sound of the vehicle 20 traveling on a rough road such as a muddy road, there is a high possibility that the vehicle 20 is dirty due to mud splashes or the like. Therefore, at this time, the vehicle management device 50 determines that there is a high possibility that the vehicle 20 is dirty. Therefore, the vehicle management device 50 generates information related to the sound of the vehicle 20 traveling on a rough road such as a muddy road as information related to the dirt on the vehicle 20.

[0041] Next, in step S106, the vehicle management device 50 generates information about the energy of the vehicle 20 as one piece of information about the vehicle 20 based on the data acquired in step S100.

[0042] Specifically, the vehicle management device 50 calculates the amount of change in the remaining battery charge or remaining fuel charge from data related to the energy of the vehicle 20 acquired from the vehicle energy detection device 45 in step S100. Furthermore, when the calculated amount of change is equal to or greater than a threshold, the vehicle management device 50 determines that the battery of the vehicle 20 has been charged or that the vehicle 20 has been refueled. At this time, the vehicle management device 50 determines that energy has been injected into the vehicle 20. Therefore, the vehicle management device 50 generates information regarding whether or not energy has been injected into the vehicle 20 as information related to the energy of the vehicle 20. Note that the threshold related to the amount of change is set, for example, by experimentation, simulation, or the like, so that it is determined that energy has been injected into the vehicle 20 when the threshold is zero.

[0043] Next, in step S108, the vehicle management device 50 generates information regarding washing of the vehicle 20 as one piece of information regarding the vehicle 20 based on the data acquired in step S100.

[0044] Here, when the vehicle 20 is washed, a specific sound corresponding to the car wash is generated. Therefore, the vehicle management device 50 uses machine learning such as the SVM or deep learning described above to determine whether the sound-related data acquired from the acoustic sensor 25 in step S100 includes the sound of the vehicle 20 being washed. Furthermore, when the data includes the sound of the vehicle 20 being washed, the vehicle management device 50 determines that the vehicle 20 has been washed. Therefore, the vehicle management device 50 generates information regarding whether the vehicle 20 has been washed as information regarding the washing of the vehicle 20.

[0045] Subsequently, in step S110, the vehicle administration device 50 outputs the information generated in the processes from step S102 to step S108 to the server 80.

[0046] Next, in step S112, the vehicle management device 50 determines, from the information about the minor collision generated in step S102, whether or not a minor collision of the vehicle 20 has occurred that does not involve shaking of the vehicle 20. Furthermore, the vehicle management device 50 determines, from the information about dirt on the vehicle 20 generated in step S104, whether or not there is a high possibility that the vehicle 20 is dirty.

[0047] Then, when a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 has not occurred and the possibility that the vehicle 20 is dirty is low, the processing of the vehicle management device 50 returns to step S100. Also, when a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 has occurred, the processing of the vehicle management device 50 proceeds to step S114. Furthermore, when the possibility that the vehicle 20 is dirty is high, the processing of the vehicle management device 50 proceeds to step S114.

[0048] Step S114, which follows step S112, is executed when a minor collision of the vehicle 20 occurs without shaking of the vehicle 20, or when the vehicle 20 becomes dirty. Therefore, in step S114, if a minor collision of the vehicle 20 without shaking of the vehicle 20 occurs, the vehicle management device 50 notifies the occupant of the vehicle 20 of the occurrence and type of minor collision of the vehicle 20 without shaking of the vehicle 20, for example, by using text display, sound, and light. Furthermore, if there is a high possibility that the vehicle 20 is dirty, the vehicle management device 50 notifies the occupant of the vehicle 20 of the high possibility that the vehicle 20 is dirty, for example, by using text display, sound, and light. This allows the occupant of the vehicle 20 to recognize the minor collision and dirt of the vehicle 20. Furthermore, if there is a minor collision of the vehicle 20 without shaking of the vehicle 20, the vehicle management device 50 notifies the administrator of the occurrence and type of minor collision of the vehicle 20 without shaking of the vehicle 20 via the administrator terminal 90, for example, by using text display, sound, and light. Furthermore, if there is a high possibility that the vehicle 20 is dirty, the vehicle management device 50 notifies the administrator via the administrator terminal 90 that there is a high possibility that the vehicle 20 is dirty by using text display, sound, and light. This allows the administrator to recognize the minor collision and dirt of the vehicle 20. Thereafter, the processing of the vehicle management device 50 returns to step S100. As described above, the administrator is a car sharing business operator, a rental car business operator, or the like.

[0049] As described above, the vehicle management device 50 generates information about the vehicle 20 and notifies the occupants of the vehicle 20 of the generated information. Next, the processing of the server 80 as a result of the execution of the program on the server 80 will be described with reference to the flowchart of Figure 4. The program on the server 80 is executed, for example, when the power to the server 80 is turned on.

[0050] In step S200, the server 80 acquires information about the vehicle 20 from the vehicle management device 50. The vehicle management system 10 is equipped with a plurality of vehicles 20, and the server 80 acquires information about the vehicle 20 from the vehicle management device 50 for the plurality of vehicles 20. As described above, the information about the vehicle 20 is information about minor collisions, dirt, energy, and car washes of the vehicle 20.

[0051] Next, in step S202, the server 80 associates the information about the vehicle 20 acquired in step S200 with the identification number of the corresponding vehicle 20. Furthermore, the server 80 stores the associated information. Furthermore, for each vehicle 20, the server 80 associates information about the vehicle 20 from the past to the present with the identification number of the vehicle 20. Note that the identification number of the vehicle 20 is, for example, a number registered by a car sharing service provider or a rental car service provider.

[0052] Next, in step S204, the server 80 generates information regarding the repair of the vehicle 20.

[0053] Specifically, the server 80 determines whether or not the part of the vehicle 20 that was involved in the minor collision, which is included in the information about the vehicle 20 acquired in step S200, should be repaired by using, for example, machine learning using as training data whether or not repairs have been performed due to minor collisions from the past to the present. Therefore, the server 80 generates information about whether or not the vehicle 20 should be repaired as information about the repair of the vehicle 20.

[0054] Next, in step S206, the server 80 uses a statistical method to compile the frequency of locations where minor collisions of the vehicle 20 that do not involve shaking of the vehicle 20 have occurred, based on the information about the vehicle 20 acquired in step S200. Furthermore, the server 80 estimates, for example, the location where minor collisions of the vehicle 20 that do not involve shaking of the vehicle 20 have occurred most frequently. In this way, the server 80 identifies locations where minor collisions are likely to occur.

[0055] Next, in step S208, the server 80 uses a statistical method to compile the frequency of locations on the vehicle 20 where minor collisions of the vehicle 20 that do not involve shaking of the vehicle 20 have occurred, from the information on the vehicle 20 acquired in step S200. The server 80 also estimates, for example, the location on the vehicle 20 where minor collisions of the vehicle 20 that do not involve shaking of the vehicle 20 have occurred most frequently. In this way, the server 80 identifies locations on the vehicle 20 where minor collisions are likely to occur.

[0056] Next, in step S210, server 80 outputs the information generated in the processing from step S202 to step S208 to administrator terminal 90. Administrator terminal 90 displays the information acquired from server 80 on a display or the like. This allows car sharing operators and rental car operators to check the information on vehicles 20 that they manage. Thereafter, the processing of server 80 returns to step S200.

[0057] The processing is performed as described above by the server 80. Next, it will be described that the vehicle management system 10 including the vehicle management device 50 and the server 80 of this embodiment outputs information regarding a minor collision that does not involve shaking of the vehicle 20.

[0058] The data processing device described in Patent Document 1 determines whether an abnormal situation has occurred based on acceleration data, which is information associated with changes in acceleration. Therefore, the abnormal situation determined by the data processing device described in Patent Document 1 is a collision accompanied by shaking of the vehicle 20. Therefore, the data processing device described in Patent Document 1 cannot determine collisions that do not involve shaking of the vehicle 20, such as scraping of the vehicle 20 against an object, contact of the vehicle 20 with a flying stone, or contact of a door with an object while the vehicle is stopped.

[0059] In contrast, the acoustic sensor 25 of the vehicle 20 provided in the vehicle management system 10 of this embodiment detects sounds generated by contact between the vehicle 20 and an object external to the vehicle 20. In addition, the vehicle management device 50 provided in the vehicle 20 serves as an acquisition unit that acquires data related to the sound detected by the acoustic sensor 25 in step S100. Furthermore, in steps S102 and S110, the vehicle management device 50 serves as an output unit that outputs information related to a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20, obtained from the sound-related data, to the server 80.

[0060] This outputs information relating to a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20. This allows the information relating to the minor collision of the vehicle 20 to be confirmed.

[0061] Furthermore, the vehicle management system 10 including the vehicle management device 50 and the server 80 of the first embodiment also provides the following effects.

[0062] [1-1] In steps S102 and S110, the vehicle management device 50 outputs the time when a minor collision of the vehicle 20 occurred that did not involve shaking of the vehicle 20. Furthermore, in steps S102 and S110, the vehicle management device 50 outputs the location when a minor collision of the vehicle 20 occurred that did not involve shaking of the vehicle 20. Furthermore, in steps S102 and S110, the vehicle management device 50 outputs an image of the outside of the vehicle 20 captured when a minor collision of the vehicle 20 occurred that did not involve shaking of the vehicle 20.

[0063] This makes it possible to know the detailed situation when a minor collision of the vehicle 20 occurs without causing any shaking of the vehicle 20.

[0064] [1-2] A plurality of acoustic sensors 25 are provided on the vehicle 20. Furthermore, in steps S102 and S110, the vehicle management device 50 outputs information obtained from the volume of the sound detected by the plurality of acoustic sensors 25, and information regarding the location on the vehicle 20 where a minor collision that does not involve shaking of the vehicle 20 occurred.

[0065] This identifies the location of the vehicle 20 where a minor collision of the vehicle 20 occurred that did not involve shaking of the vehicle 20. This makes it easier to identify the location when inspecting the vehicle 20, for example.

[0066] [1-3] The acoustic sensors 25 are arranged at the left front corner 202, the right front corner 204, the left rear corner 206, and the right rear corner 208, respectively.

[0067] As a result, the location of the vehicle 20 where a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 has occurred is located at the position of the interior division point between adjacent acoustic sensors 25. This makes it easier to estimate the location of the vehicle 20 where a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 has occurred, based on the volume of the sound detected by each acoustic sensor 25.

[0068] [1-4] In steps S102 and S110, the vehicle management device 50 outputs information obtained from the speed of the vehicle 20, and information regarding whether a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 was caused by an occupant of the vehicle 20.

[0069] This makes it possible to confirm whether or not a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 is caused by the occupants of the vehicle 20. Therefore, when repairs are required due to a minor collision, it becomes easier to determine whether or not the cost of the repairs should be borne by the occupants of the vehicle 20.

[0070] [1-5] In steps S104 and S110, the vehicle management device 50 outputs information about the dirt on the vehicle 20, which information is obtained from the sound generated when the vehicle 20 travels on a rough road such as a muddy road.

[0071] This allows the driver of the vehicle 20, the car sharing operator, the rental car operator, etc., to know whether the vehicle 20 is dirty or not, and makes it easier for them to decide whether or not to wash the vehicle 20.

[0072] [1-6] In steps S106 and S110, the vehicle management device 50 outputs information regarding whether or not energy has been injected into the vehicle 20. In addition, in steps S108 and S110, the vehicle management device 50 outputs information regarding whether or not the vehicle 20 has been washed.

[0073] This allows the user to check, in addition to the information regarding a minor collision of the vehicle 20, whether the vehicle 20 has been charged, refueled, or washed.

[0074] [1-7] In steps S112 and S114, when a minor collision of vehicle 20 occurs without shaking of vehicle 20, vehicle management device 50 serves as an alarm unit that notifies the occupants of vehicle 20 that a minor collision of vehicle 20 without shaking of vehicle 20 has occurred.

[0075] This allows the occupants of the vehicle 20 to recognize that a minor collision of the vehicle 20 has occurred without causing the vehicle 20 to shake.

[0076] [1-8] In steps S112 and S114, when a minor collision of vehicle 20 occurs that does not involve shaking of vehicle 20, vehicle management device 50 serves as an alarm unit that notifies the occupants of vehicle 20 of the type of minor collision of vehicle 20 that does not involve shaking of vehicle 20.

[0077] This allows the occupant of the vehicle 20 to recognize the type of minor collision of the vehicle 20 that does not involve shaking of the vehicle 20. This makes it easier for the occupant of the vehicle 20 to determine what to do about the minor collision, for example, whether or not to repair and return the vehicle 20.

[0078] [1-9] In steps S112 and S114, when the vehicle 20 becomes dirty due to driving on a rough road such as a muddy road, the vehicle management device 50 serves as an alarm unit that notifies the occupants of the vehicle 20 that the vehicle 20 has become dirty.

[0079] This allows the occupant of the vehicle 20 to recognize that the vehicle 20 is dirty, making it easier for the occupant of the vehicle 20 to decide whether or not to wash the vehicle 20 before returning it.

[0080] [2-1] The server 80 serves as an acquisition unit that acquires information about minor collisions of the vehicles 20 that do not involve shaking of the vehicles 20 for a plurality of vehicles 20. Furthermore, the server 80 serves as a link unit that associates information about minor collisions of the vehicles 20 that do not involve shaking of the vehicles 20 with the identification numbers of the vehicles 20. The server 80 also serves as an output unit that outputs the associated information to the administrator terminal 90.

[0081] This allows car sharing businesses and rental car businesses to check information about minor collisions involving the vehicles 20 under their management in one place.

[0082] [2-2] For each vehicle 20, the server 80 associates information about minor collisions of the vehicle 20 from the past to the present that do not involve shaking of the vehicle 20 with the identification number of the vehicle 20.

[0083] This allows car sharing businesses and rental car businesses to check past information as well as current information. This makes it easier for car sharing businesses and rental car businesses to determine whether damage to the vehicle 20 when inspecting the vehicle 20 is due to a past minor collision or a current minor collision. This saves the car sharing businesses and rental car businesses the trouble of inspecting the vehicle. It also reduces the chance of misidentifying a minor collision caused by a past occupant as a minor collision caused by a current occupant. This prevents car sharing businesses and rental car businesses from unfairly charging for repairs, etc., when the vehicle 20 needs repair due to a minor collision.

[0084] [2-3] In steps S204 and S210, the server 80 outputs information regarding whether or not the vehicle 20 should be repaired, which information is obtained from information regarding repairs caused by minor collisions of the vehicle 20 that did not involve shaking of the vehicle 20 from the past to the present.

[0085] This allows car sharing operators and rental car operators to skip inspection of vehicle 20 and determine whether or not vehicle 20 should be repaired.

[0086] [2-4] In steps S206 and S210, the server 80 outputs the location where minor collisions of the vehicle 20 that do not involve shaking of the vehicle 20 have occurred most frequently. Furthermore, in steps S208 and S210, the server 80 outputs the location on the vehicle 20 where minor collisions of the vehicle 20 that do not involve shaking of the vehicle 20 have occurred most frequently.

[0087] As a result, the information output from the server 80 serves to alert the occupants of the vehicle 20 in order to prevent minor collisions of the vehicle 20. In addition, the information output from the server 80 can be used to improve roads in order to prevent minor collisions of the vehicle 20.

[0088] Second Embodiment In the second embodiment, the configuration of the vehicle management system 10 differs from that of the first embodiment. Furthermore, the processing of the vehicle management device 50 differs from that of the first embodiment. Other than these, the second embodiment is similar to the first embodiment.

[0089] Specifically, as shown in Fig. 5, the vehicle management system 10 does not include a server 80. Furthermore, in step S110, the vehicle management device 50 outputs the information generated in the processing from step S102 to step S108 to the administrator terminal 90 instead of the server 80. In this case, for example, the administrator terminal 90 performs processing similar to the processing from step S200 to step S208 of the server 80. In this way, the car sharing business operator or the rental car business operator manages their own vehicles 20.

[0090] The vehicle management system 10 of the second embodiment is configured as described above. The second embodiment also provides the same effects as the first embodiment.

[0091] Third Embodiment In the third embodiment, the configuration of the vehicle 20 is different from that of the first embodiment. Furthermore, the processing of the server 80 is different from that of the first embodiment. Other than these, the third embodiment is the same as the first embodiment.

[0092] 6, the vehicle 20 is provided with a notification device 55 instead of the vehicle management device 50. The notification device 55 has a speaker, a display, etc., and notifies the occupants of the vehicle 20 of information related to the vehicle 20 using, for example, text display, sound, and light based on a signal from the server 80.

[0093] The ROM of the server 80 stores a program for generating information about the vehicle 20 in addition to the processing program for steps S200 to S210 of the server 80. When the server 80 executes the program for generating information about the vehicle 20, as shown in the flowchart of FIG. 7 , the server 80 performs processing from steps S300 to S308 that is similar to the processing from steps S100 to S108 of the vehicle management device 50. In this way, the server 80 generates information about the vehicle 20. When the server 80 executes the processing program for steps S200 to S208 of the server 80, the server 80 acquires the generated information about the vehicle 20 in step S200. The server 80 then performs processing from steps S202 to S210 using the acquired information about the vehicle 20.

[0094] In step S310 following step S308, the server 80 determines, from the information about the minor collision generated in step S302, whether or not a minor collision of the vehicle 20 has occurred that does not involve shaking of the vehicle 20. In addition, the server 80 determines, from the information about dirt on the vehicle 20 generated in step S304, whether or not there is a high possibility that the vehicle 20 is dirty.

[0095] Then, when a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 has not occurred and the possibility that the vehicle 20 is dirty is low, the processing of the vehicle management device 50 returns to step S300. Furthermore, when a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 has occurred, the processing of the server 80 proceeds to step S312. Furthermore, when the possibility that the vehicle 20 is dirty is high, the processing of the server 80 proceeds to step S312.

[0096] Step S312, which follows step S310, is executed when a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 occurs, or when the vehicle 20 becomes dirty. Therefore, in step S312, the server 80 transmits a signal to the alarm device 55 to activate the alarm device 55. As a result, if a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 occurs, the alarm device 55 notifies the occupants of the vehicle 20 of the occurrence and type of minor collision of the vehicle 20 that does not involve shaking of the vehicle 20, for example, by using text display, sound, and light. Furthermore, if there is a high possibility that the vehicle 20 is dirty, the alarm device 55 notifies the occupants of the vehicle 20 that there is a high possibility that the vehicle 20 is dirty, by using text display, sound, and light. These operations allow the occupants of the vehicle 20 to be aware of the minor collision and dirt of the vehicle 20. Furthermore, if a minor collision of the vehicle 20 occurs without shaking of the vehicle 20, the alarm device 55 notifies the administrator via the administrator terminal 90 of the occurrence and type of minor collision of the vehicle 20 without shaking of the vehicle 20, for example, by using text display, sound, and light. Furthermore, if there is a high possibility that the vehicle 20 is dirty, the alarm device 55 notifies the administrator via the administrator terminal 90 of the high possibility that the vehicle 20 is dirty, by using text display, sound, and light. This allows the administrator to know about the minor collision and dirt of the vehicle 20. Thereafter, the processing of the server 80 returns to step S300. As described above, the administrator may be a car sharing business operator, a rental car business operator, or the like.

[0097] The vehicle management system 10 of the third embodiment is configured as described above. The third embodiment also achieves the same effects as the first embodiment. In the third embodiment, the server 80 corresponds to the management device.

[0098] Fourth Embodiment In a fourth embodiment, as shown in Fig. 8, a vehicle 20 further includes an acceleration sensor 60. Also, the processing of a vehicle management device 50 differs from that of the first embodiment. Other than this, the fourth embodiment is similar to the first embodiment.

[0099] The acceleration sensor 60 detects the acceleration of the vehicle 20 and transmits data relating to the detected acceleration of the vehicle 20 to the vehicle management device 50. Next, the processing of the vehicle management device 50 will be described with reference to the flowchart of FIG.

[0100] In step S100, the vehicle management device 50 acquires various data. Specifically, as in the first embodiment, the vehicle management device 50 acquires data related to the sound detected by the acoustic sensor 25, data related to the location of the vehicle 20, image data of the area around the vehicle 20, data related to the speed of the vehicle 20, and data related to the energy of the vehicle 20. In addition to these, the vehicle management device 50 acquires data related to the acceleration of the vehicle 20 from an acceleration sensor.

[0101] Subsequently, in step S102, information relating to the collision of the vehicle 20 is generated based on the data acquired in step S100.

[0102] 10 , when the sound detected by the acoustic sensor 25 includes a collision sound, the collision sound includes not the sound of the vehicle 20 but the sound of a collision around the vehicle 20 or of another vehicle different from the vehicle 20. Furthermore, the collision sound includes the sound of a collision of the vehicle 20 that is accompanied by shaking of the vehicle 20, and the sound of a minor collision of the vehicle 20 that is not accompanied by shaking of the vehicle 20.

[0103] Furthermore, when the absolute value |Ac| of the acceleration of the vehicle 20 is equal to or smaller than the first threshold value Ac_th1, for example, when the absolute value |Ac| of the acceleration is zero, the vehicle 20 has not received an impact and therefore is highly likely not to have collided. Therefore, at this time, the collision sound detected by the acoustic sensor 25 is highly likely to be the collision sound of a vehicle in the vicinity of the vehicle 20 or of another vehicle different from the vehicle 20.

[0104] Furthermore, when the absolute value |Ac| of the acceleration of the vehicle 20 is greater than the first threshold value Ac_th1 and less than the second threshold value Ac_th2, it is highly likely that the vehicle 20 has received an impact that does not sway the vehicle 20. Therefore, at this time, it is highly likely that the collision sound detected by the acoustic sensor 25 is the sound of a minor collision of the vehicle 20 that does not sway the vehicle 20.

[0105] Furthermore, when the absolute value |Ac| of the acceleration of the vehicle 20 is equal to or greater than the second threshold value Ac_th2, it is highly likely that the vehicle 20 has received an impact accompanied by shaking of the vehicle 20. Therefore, at this time, it is highly likely that the collision sound detected by the acoustic sensor 25 is the sound of a collision of the vehicle 20 accompanied by shaking of the vehicle 20.

[0106] Therefore, the vehicle management device 50 classifies the collision sound detected by the acoustic sensor 25 using data regarding the sound obtained from the acoustic sensor 25 in step S100 and data regarding the acceleration of the vehicle 20 obtained from the acceleration sensor in step S100.

[0107] For example, the vehicle management device 50 uses machine learning such as the SVM or deep learning to determine whether or not a collision sound is included in the sound-related data acquired from the acoustic sensor 25. Furthermore, if a collision sound is included in the sound-related data acquired from the acoustic sensor 25, the vehicle management device 50 determines whether or not the absolute value |Ac| of the acceleration acquired in step S100 is greater than the first threshold value Ac_th1 and less than the second threshold value Ac_th2.

[0108] When the absolute value of the acceleration |Ac| is less than or equal to the first threshold value Ac_th1, the vehicle management device 50 determines that the collision sound detected by the acoustic sensor 25 is a collision sound from the vicinity of the vehicle 20 or from another vehicle other than the vehicle 20. Furthermore, when the absolute value of the acceleration |Ac| is greater than the first threshold value Ac_th1 and less than the second threshold value Ac_th2, the vehicle management device 50 determines that the collision sound detected by the acoustic sensor 25 is a sound from a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20. Furthermore, when the absolute value of the acceleration |Ac| is greater than or equal to the second threshold value Ac_th2, the vehicle management device 50 determines that the collision sound detected by the acoustic sensor 25 is a sound from a collision of the vehicle 20 that involves shaking of the vehicle 20. The first threshold value Ac_th1 and the second threshold value Ac_th2 are set by experimentation, simulation, or the like so that the collision sounds detected by the acoustic sensor 25 can be classified.

[0109] Furthermore, if the sound-related data acquired from the acoustic sensor 25 includes a collision sound, the vehicle management device 50 associates the collision sound in the same manner as in the first embodiment. Specifically, the vehicle management device 50 associates whether or not a collision occurred, the type of collision, the time of the collision, the location of the collision, an image taken at the time of the collision, the location of the vehicle 20 that collided, and whether or not the collision was caused by the intentional or negligent actions of the occupants of the vehicle 20. The vehicle management device 50 also generates information that associates these items as information related to the collision of the vehicle 20.

[0110] The processes from step S104 to step S110 following step S102 are performed in the same manner as in the first embodiment.

[0111] In step S112 following step S110, the vehicle management device 50 determines, from the collision-related information generated in step S102, whether or not a collision has occurred for the vehicle 20. Furthermore, the vehicle management device 50 determines, from the information regarding dirt on the vehicle 20 generated in step S104, whether or not there is a high possibility that the vehicle 20 is dirty.

[0112] Then, when a collision has not occurred with respect to the vehicle 20 and the possibility that the vehicle 20 is dirty is low, the processing of the vehicle management device 50 returns to step S100. Also, when a collision has occurred with respect to the vehicle 20, the processing of the vehicle management device 50 proceeds to step S114. Furthermore, when the possibility that the vehicle 20 is dirty is high, the processing of the vehicle management device 50 proceeds to step S114.

[0113] Step S114, which follows step S112, is executed when a collision has occurred with the vehicle 20 or when the vehicle 20 has become dirty. Therefore, in step S114, if a collision has occurred with the vehicle 20, the vehicle management device 50 notifies the occupant of the vehicle 20 of the occurrence and type of collision with the vehicle 20, for example, by using text display, sound, and light. Furthermore, if there is a high possibility that the vehicle 20 is dirty, the vehicle management device 50 notifies the occupant of the vehicle 20 that there is a high possibility that the vehicle 20 is dirty, for example, by using text display, sound, and light. This allows the occupant of the vehicle 20 to recognize the collision and dirt with the vehicle 20. Furthermore, if there is a collision with the vehicle 20, the vehicle management device 50 notifies the administrator via the administrator terminal 90 of the occurrence and type of collision with the vehicle 20, for example, by using text display, sound, and light. Furthermore, if there is a high possibility that the vehicle 20 is dirty, the vehicle management device 50 notifies the administrator via the administrator terminal 90 that there is a high possibility that the vehicle 20 is dirty, for example, by using text display, sound, and light. These allow the administrator to recognize collisions and dirt on the vehicle 20. After that, the process of the vehicle management device 50 returns to step S100.

[0114] As described above, the vehicle management system 10 of the fourth embodiment is configured, and the vehicle management device 50 performs processing. This fourth embodiment also achieves the same effects as the first embodiment. In addition, the fourth embodiment also achieves the effects described below.

[0115] [3-1] The vehicle management device 50 outputs data relating to the sound detected by the acoustic sensor 25 and information relating to a minor collision of the vehicle 20 obtained from the absolute value |Ac| of the acceleration of the vehicle 20.

[0116] This makes it possible to classify the collision sounds detected by the acoustic sensor 25 into collision sounds from the surroundings of the vehicle 20 or from other vehicles different from the vehicle 20, sounds of minor collisions of the vehicle 20 that do not involve shaking of the vehicle 20, and sounds of collisions of the vehicle 20 that involve shaking of the vehicle 20. This prevents the sound of a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 from being erroneously determined to be a collision sound from the surroundings of the vehicle 20 or from other vehicles different from the vehicle 20.

[0117] [3-2] Here, when a collision sound occurs not from vehicle 20 but from the vicinity of vehicle 20 or from another vehicle other than vehicle 20, if that information is notified, it can be annoying for the occupants and managers of vehicle 20.

[0118] In contrast, in steps S102 and S114, when the sound detected by the acoustic sensor 25 includes a collision sound, the vehicle management device 50 does not output information related to a minor collision of the vehicle 20 if the absolute value of the acceleration |Ac| is equal to or less than the first threshold value Ac_th1. Furthermore, when the sound detected by the acoustic sensor 25 includes a collision sound, the vehicle management device 50 outputs information related to a minor collision of the vehicle 20 if the absolute value of the acceleration |Ac| is greater than the first threshold value Ac_th1 and less than the second threshold value Ac_th2. Furthermore, when the absolute value of the acceleration |Ac| is equal to or greater than the second threshold value Ac_th2, the vehicle management device 50 outputs information related to a collision of the vehicle 20 accompanied by shaking of the vehicle 20.

[0119] As a result, when a collision sound occurs in the vicinity of the vehicle 20 or of another vehicle other than the vehicle 20, the information is not output and therefore notified, thereby reducing the inconvenience to the occupants and managers of the vehicle 20.

[0120] (Other Embodiments) The present disclosure is not limited to the above-described embodiments, and appropriate modifications can be made to the above-described embodiments. Furthermore, it goes without saying that in each of the above-described embodiments, elements constituting the embodiments are not necessarily essential, except when expressly stated as essential or when considered to be clearly essential in principle.

[0121] The acquisition unit, output unit, notification unit, linking unit, etc., and the methods described herein may be implemented by a special-purpose computer configured by configuring a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the acquisition unit, output unit, notification unit, linking unit, etc., and the methods described herein may be implemented by a special-purpose computer configured by configuring a processor with one or more dedicated hardware logic circuits. Alternatively, the acquisition unit, output unit, notification unit, linking unit, etc., and the methods described herein may be implemented by one or more special-purpose computers configured by combining a processor and memory programmed to perform one or more functions with a processor configured with one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by a computer on a computer-readable non-transitory tangible storage medium.

[0122] In each of the above embodiments, the number of acoustic sensors 25 is four. However, the number of acoustic sensors 25 is not limited to four, and may be one or more.

[0123] In each of the above embodiments, the acoustic sensor 25 detects sounds generated when the vehicle 20 contacts an object external to the vehicle 20, as well as sounds generated when the vehicle 20 travels on a rough road such as a muddy road. In contrast, the vehicle 20 may be provided with an acoustic sensor 25 for detecting sounds generated when the vehicle 20 travels on a rough road such as a muddy road, in addition to the acoustic sensor 25 that detects sounds generated when the vehicle 20 contacts an object external to the vehicle 20. The acoustic sensor 25 for detecting sounds generated when the vehicle 20 travels on a rough road such as a muddy road is disposed, for example, on the body of the vehicle 20 near a wheel well.

[0124] In the first and second embodiments, the vehicle management device 50 generates information about a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 from data about the sound detected by the acoustic sensor 25. In contrast, the vehicle management device 50 may generate information about a collision of the vehicle 20 that involves shaking of the vehicle 20 by using machine learning such as the SVM or deep learning, in addition to information about a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20.

[0125] In the third embodiment, the server 80 generates information about a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20 from data about the sound detected by the acoustic sensor 25. In contrast to this, the server 80 may generate information about a collision of the vehicle 20 that involves shaking of the vehicle 20 by using machine learning such as the SVM or deep learning described above, in addition to information about a minor collision of the vehicle 20 that does not involve shaking of the vehicle 20.

[0126] The above embodiments may be combined as appropriate.

[0127] (Aspects of the Present Disclosure) [Aspect 1] A management device comprising: an acquisition unit (S100) that acquires data related to sound detected by an acoustic sensor (25) that detects sound generated by contact between a vehicle (20) and an object external to the vehicle; and an output unit (S102, S110) that outputs information related to a vehicle collision not accompanied by vehicle shaking obtained from the sound data. [Aspect 2] The management device according to Aspect 1, wherein the output unit outputs at least one of the time when the vehicle collision not accompanied by vehicle shaking occurred, the location when the vehicle collision not accompanied by vehicle shaking occurred, and an image captured of the outside of the vehicle when the vehicle collision not accompanied by vehicle shaking occurred. [Aspect 3] The management device according to Aspect 1 or 2, wherein a plurality of the acoustic sensors are provided on the vehicle, and the output unit outputs information related to a location on the vehicle where the vehicle collision not accompanied by vehicle shaking occurred, the information being obtained from the volume of sound detected by the plurality of acoustic sensors. [Aspect 4] The vehicle has a left front corner (202) that is a corner of the vehicle on the left front side of the vehicle, a right front corner (204) that is a corner of the vehicle on the right front side of the vehicle, a left rear corner (206) that is a corner of the vehicle on the left rear side of the vehicle, and a right rear corner (208) that is a corner of the vehicle on the right rear side of the vehicle, and the acoustic sensors are disposed at the left front corner, the right front corner, the left rear corner, and the right rear corner, respectively. [Aspect 5] The management device according to any one of Aspects 1 to 4, wherein the output unit outputs information obtained from the speed of the vehicle, which is information regarding whether a collision of the vehicle that does not involve shaking of the vehicle was caused by an occupant of the vehicle. [Aspect 6] The management device according to any one of Aspects 1 to 5, wherein the output unit outputs information obtained from the sound of the vehicle when it travels on a rough road, which is information regarding dirt on the vehicle. [Aspect 7] The management device according to any one of Aspects 1 to 6, wherein the output unit outputs at least one of information regarding whether energy has been injected into the vehicle and information regarding whether the vehicle has been washed.[Aspect 8] The management device according to any one of Aspects 1 to 7, further comprising an alarm unit (S114) that, when a collision of the vehicle occurs that does not involve vehicle shaking, notifies an occupant of the vehicle that a collision of the vehicle has occurred that does not involve vehicle shaking. [Aspect 9] The management device according to any one of Aspects 1 to 7, further comprising an alarm unit (S114) that, when a collision of the vehicle occurs that does not involve vehicle shaking, notifies an occupant of the vehicle of the type of the collision of the vehicle that does not involve vehicle shaking. [Aspect 10] The management device according to any one of Aspects 1 to 7, further comprising an alarm unit (S114) that, when the vehicle becomes dirty due to traveling on a rough road, notifies an occupant of the vehicle that the vehicle has become dirty. [Aspect 11] The management device according to any one of Aspects 1 to 10, wherein the output unit outputs information relating to the vehicle collision not accompanied by vehicle shaking to a server (80) that acquires information relating to the vehicle collision not accompanied by vehicle shaking for a plurality of the vehicles. [Aspect 12] The management device according to any one of Aspects 1 to 11, wherein the output unit outputs information relating to the vehicle collision not accompanied by vehicle shaking to a terminal (90) of an administrator that manages the vehicles. [Aspect 13] The management device according to any one of Aspects 1 to 12, wherein the output unit outputs information relating to the vehicle collision not accompanied by vehicle shaking obtained from data relating to the sound and an absolute value of the acceleration (|Ac|) of the vehicle. [Aspect 14] The output unit, in the case where the sound detected by the acoustic sensor includes a collision sound, does not output information related to a vehicle collision not accompanied by vehicle shaking when the absolute value of the vehicle acceleration is equal to or less than a first threshold value (Ac_th1), outputs information related to a vehicle collision not accompanied by vehicle shaking when the absolute value of the vehicle acceleration is greater than the first threshold value and less than a second threshold value (Ac_th2), and outputs information related to a vehicle collision accompanied by vehicle shaking when the absolute value of the vehicle acceleration is equal to or greater than the second threshold value. This is the management device described in Aspect 13.[Aspect 15] A server comprising: an acquisition unit (S200) that acquires, for a plurality of vehicles, information about vehicle collisions not accompanied by vehicle sway, obtained from data related to sounds detected by an acoustic sensor (25) that detects sounds generated by contact between the vehicle and an object external to the vehicle; a link unit (S202) that associates the information about the vehicle collisions not accompanied by vehicle sway with the vehicle identification numbers; and an output unit (S210) that outputs the information associated by the link unit to a terminal (90) of an administrator who manages the vehicles. [Aspect 16] The server according to Aspect 13, wherein the link unit associates, for each of the vehicles, information about vehicle collisions not accompanied by vehicle sway from the past to the present with the vehicle identification number. [Aspect 17] The server according to Aspect 15 or 16, wherein the output unit outputs information about whether the vehicle should be repaired, obtained from information about repairs caused by vehicle collisions not accompanied by vehicle sway from the past to the present. [Aspect 18] The server according to any one of Aspects 15 to 17, wherein the output unit outputs at least one of a location where collisions of the vehicle not accompanied by vehicle shaking have occurred most frequently and a location on the vehicle where collisions of the vehicle not accompanied by vehicle shaking have occurred most frequently. [Aspect 19] A vehicle management system comprising: a management device (50) that acquires data related to sounds detected by an acoustic sensor (25) that detects sounds generated by contact between a vehicle (20) and an object external to the vehicle, and outputs information related to collisions of the vehicle not accompanied by vehicle shaking obtained from the data related to the sounds; and a server (80) that acquires information related to collisions of the vehicle not accompanied by vehicle shaking for a plurality of the vehicles, associates the information related to collisions of the vehicle not accompanied by vehicle shaking with identification numbers of the vehicles, and outputs the associated information to a terminal (90) of an administrator that manages the vehicles.[Aspect 20] A management method comprising: acquiring data relating to sound detected by an acoustic sensor (25) that detects sound generated by contact between a vehicle (20) and an object external to the vehicle; and outputting information relating to a vehicle collision not accompanied by vehicle shaking obtained from the sound related data. [Aspect 21] A server processing method comprising: acquiring information relating to a vehicle collision not accompanied by vehicle shaking obtained from data relating to sound detected by an acoustic sensor (25) that detects sound generated by contact between a vehicle (20) and an object external to the vehicle, for a plurality of the vehicles, associating the information relating to the vehicle collision not accompanied by vehicle shaking with the vehicle identification number, and outputting the associated information to a terminal (90) of an administrator that manages the vehicles. [Aspect 22] A management program that causes a management device to function as: an acquisition unit (S100) that acquires data related to sound detected by an acoustic sensor (25) that detects sound generated by contact between a vehicle (20) and an object external to the vehicle, and an output unit (S102, S110) that outputs information related to a vehicle collision not accompanied by vehicle shaking obtained from the sound related data. [Aspect 23] A server program that causes a server to function as: an acquisition unit (S200) that acquires information related to a vehicle collision not accompanied by vehicle shaking for a plurality of vehicles, obtained from data related to sound detected by an acoustic sensor (25) that detects sound generated by contact between a vehicle (20) and an object external to the vehicle, a link unit (S202) that associates the information related to the vehicle collision not accompanied by vehicle shaking with the vehicle identification number, and an output unit (S210) that outputs the information associated by the link unit to a terminal (90) of an administrator that manages the vehicles.

Claims

1. A management device comprising: an acquisition unit (S100) that acquires data relating to a sound detected by an acoustic sensor (25) that detects a sound generated by contact between a vehicle (20) and an object external to the vehicle; and an output unit (S102, S110) that outputs information relating to a collision of the vehicle that does not involve shaking of the vehicle, which is obtained from the data relating to the sound.

2. The management device of claim 1, wherein the output unit outputs at least one of the time when the vehicle collision without vehicle shaking occurred, the location when the vehicle collision without vehicle shaking occurred, and an image of the outside of the vehicle taken when the vehicle collision without vehicle shaking occurred.

3. The management device according to claim 1 or 2, wherein the vehicle is provided with a plurality of acoustic sensors, and the output unit outputs information obtained from the volume of sound detected by the plurality of acoustic sensors, and information regarding the location of the vehicle where a collision of the vehicle that does not involve shaking of the vehicle occurred.

4. The management device described in claim 3, wherein the vehicle has a left front corner (202) that is a corner of the vehicle on the left front side of the vehicle, a right front corner (204) that is a corner of the vehicle on the right front side of the vehicle, a left rear corner (206) that is a corner of the vehicle on the left rear side of the vehicle, and a right rear corner (208) that is a corner of the vehicle on the right rear side of the vehicle, and the acoustic sensors are respectively arranged at the left front corner, the right front corner, the left rear corner and the right rear corner.

5. A management device as described in claim 1 or 2, wherein the output unit outputs information obtained from the speed of the vehicle and information regarding whether a collision of the vehicle that does not involve shaking of the vehicle is caused by an occupant of the vehicle.

6. A management device according to claim 1 or 2, wherein the output unit outputs information relating to the dirtiness of the vehicle, the information being obtained from the sound of the vehicle when it is traveling on a rough road.

7. The management device according to claim 1 or 2, wherein the output unit outputs at least one of information regarding whether or not energy has been injected into the vehicle and information regarding whether or not the vehicle has been washed.

8. The management device according to claim 1 or 2, further comprising an alarm unit (S114) that, when a collision of the vehicle occurs that does not involve shaking of the vehicle, notifies an occupant of the vehicle that a collision of the vehicle has occurred that does not involve shaking of the vehicle.

9. The management device according to claim 1 or 2, further comprising an alarm unit (S114) that, when a collision of the vehicle occurs that does not involve shaking of the vehicle, notifies an occupant of the vehicle of the type of collision of the vehicle that does not involve shaking of the vehicle.

10. The management device according to claim 1 or 2, further comprising an alarm unit (S114) that notifies the occupants of the vehicle that the vehicle has become dirty when the vehicle has become dirty due to driving on a rough road.

11. A management device as described in claim 1 or 2, wherein the output unit outputs information regarding the vehicle collision that does not involve vehicle shaking to a server (80) that acquires information regarding the vehicle collision that does not involve vehicle shaking for a plurality of the vehicles.

12. A management device as described in claim 1 or 2, wherein the output unit outputs information relating to a collision of the vehicle that does not involve shaking of the vehicle to a terminal (90) of an administrator who manages the vehicle.

13. A management device as described in claim 1 or 2, wherein the output unit outputs information regarding a collision of the vehicle that does not involve shaking of the vehicle, obtained from data regarding the sound and the absolute value of the acceleration of the vehicle (|Ac|).

14. The management device described in claim 13, wherein the output unit: when the sound detected by the acoustic sensor includes a collision sound, does not output information regarding a vehicle collision not accompanied by vehicle shaking when the absolute value of the vehicle acceleration is equal to or less than a first threshold value (Ac_th1); outputs information regarding a vehicle collision not accompanied by vehicle shaking when the absolute value of the vehicle acceleration is greater than the first threshold value and less than a second threshold value (Ac_th2); and outputs information regarding a vehicle collision accompanied by vehicle shaking when the absolute value of the vehicle acceleration is equal to or greater than the second threshold value.

15. A server comprising: an acquisition unit (S200) that acquires, for a plurality of vehicles, information relating to vehicle collisions not accompanied by vehicle shaking, obtained from data relating to sounds detected by an acoustic sensor (25) that detects sounds generated by contact between a vehicle (20) and an object external to the vehicle; a link unit (S202) that associates the information relating to vehicle collisions not accompanied by vehicle shaking with the vehicle identification numbers; and an output unit (S210) that outputs the information associated by the link unit to a terminal (90) of an administrator that manages the vehicles.

16. The server according to claim 15, wherein the linking unit associates, for each of the vehicles, information about collisions of the vehicle from the past to the present that do not involve shaking of the vehicle with the identification number of the vehicle.

17. The server according to claim 15, wherein the output unit outputs information regarding whether or not the vehicle should be repaired, the information being obtained from information regarding repairs caused by collisions of the vehicle that did not involve shaking of the vehicle from the past to the present.

18. A server according to any one of claims 15 to 17, wherein the output unit outputs at least one of the location where collisions of the vehicle not accompanied by swaying of the vehicle most frequently occurred and the location of the vehicle where collisions of the vehicle not accompanied by swaying of the vehicle most frequently occurred.

19. A vehicle management system comprising: a management device (50) that acquires data relating to sounds detected by an acoustic sensor (25) that detects sounds generated by contact between a vehicle (20) and an object external to the vehicle, and outputs information relating to a vehicle collision that does not involve vehicle shaking obtained from the sound data; and a server (80) that acquires information relating to a vehicle collision that does not involve vehicle shaking for a plurality of vehicles, associates the information relating to the vehicle collision that does not involve vehicle shaking with the vehicle identification number, and outputs the associated information to a terminal (90) of an administrator that manages the vehicles.

20. A management method comprising: acquiring data relating to a sound detected by an acoustic sensor (25) that detects a sound generated by contact between a vehicle (20) and an object external to the vehicle; and outputting information relating to a collision of the vehicle that does not involve shaking of the vehicle, obtained from the data relating to the sound.

21. A processing method of a server, comprising: acquiring, for a plurality of vehicles, information relating to vehicle collisions not accompanied by vehicle shaking, obtained from data relating to sounds detected by an acoustic sensor (25) that detects sounds generated by contact between a vehicle (20) and an object external to the vehicle; associating the information relating to vehicle collisions not accompanied by vehicle shaking with the vehicle identification numbers; and outputting the associated information to a terminal (90) of an administrator who manages the vehicles.

22. A management program that causes a management device to function as an acquisition unit (S100) that acquires data related to a sound detected by an acoustic sensor (25) that detects a sound generated by contact between a vehicle (20) and an object external to the vehicle, and an output unit (S102, S110) that outputs information related to a collision of the vehicle that does not involve shaking of the vehicle, which is obtained from the data related to the sound.

23. A server program that causes a server to function as: an acquisition unit (S200) that acquires, for a plurality of vehicles, information relating to vehicle collisions not accompanied by vehicle shaking, obtained from data relating to sounds detected by an acoustic sensor (25) that detects sounds generated by contact between a vehicle (20) and an object external to the vehicle; a link unit (S202) that associates the information relating to vehicle collisions not accompanied by vehicle shaking with the vehicle identification numbers; and an output unit (S210) that outputs the information associated by the link unit to a terminal (90) of an administrator that manages the vehicles.

Images