Accident analysis device, accident analysis method, and program

Abstract

An accident analysis device, an accident analysis method, and a program are provided that can reduce the mental burden on an operator. [Solution] The accident analysis device analyzes the circumstances of an accident caused by an accident vehicle based on vehicle data measured by a sensor equipped in the accident vehicle and video data captured by a camera equipped in the accident vehicle. The video data includes fear level setting information indicating whether the video data is a frightening image that may cause a mental burden to an operator. If the fear level setting information included in the video data indicates that the video data is a frightening image, the display of the video data in the analysis of the accident circumstances is restricted until a user with specific authority cancels the restriction, and if the user with specific authority does not cancel the restriction, the analysis of the circumstances of the accident caused by the accident vehicle is terminated.

Description

[Technical field]

[0001] The present invention relates to an accident analysis device, an accident analysis method, and a program. [Background technology]

[0002] When a traffic accident occurs, insurance companies calculate the percentage of fault depending on the circumstances of the accident. For example, Patent Document 1 discloses an accident analysis device that quickly compares the circumstances of the accident with past accident cases, as a self-analysis device for calculating the percentage of fault and analyzing the accident. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-194263 A Summary of the Invention [Problem to be solved by the invention]

[0004] In such accident analysis devices, the accident situation is analyzed based on the vehicle data and video data of the accident vehicle and the operation of the operator of the accident analysis device. However, the video data includes shocking images such as images of fatal accidents, which causes trauma for the operator and places a large mental burden.

[0005] The present invention has been made to solve the above-mentioned problems, and has an object to provide an accident analysis device, an accident analysis method, and a program that can reduce the mental burden on an operator. [Means for solving the problem]

[0006] In order to achieve the above object, an accident analysis device according to a first aspect of the present invention comprises: An analysis means for analyzing the situation of the accident caused by the accident vehicle based on vehicle data measured by a sensor equipped in the accident vehicle and video data captured by a camera equipped in the accident vehicle, The video data includes fear level setting information indicating whether the video data is a fearful video that may impose a mental burden on the operator, When the fear level setting information included in the video data indicates that the video data is a fearful video, the analysis means restricts display of the video data in the analysis of the accident situation until the restriction is released by a user having specific authority, and when the restriction is not released by the user having specific authority, ends the analysis of the accident situation caused by the accident vehicle. It is characterized by:

[0007] The fear level setting information includes a plurality of setting values ​​according to the fear level of the fear image, an allowable setting value acquisition means for acquiring the setting value allowable by the operator, the analysis means, when the setting value included in the fear level setting information included in the video data is not included in the setting value acceptable to the operator identified by the acceptable setting value acquisition means, restricts display of the video data in analyzing the accident situation; When the analysis means restricts the display of the video data in the analysis of the accident situation, the user having the specific authority can release the restriction or change the setting value to a value included in the setting value acceptable to the operator, the analysis means terminates the analysis of the situation of the accident caused by the accident vehicle when the display of the video data is restricted, when the restriction is not lifted by the user having the specific authority, or when the setting value is not changed to a value included in the setting value acceptable to the operator. This may be done.

[0008] when the analysis means restricts the display of the video data in analyzing the accident situation, the user having the specific authority is notified of the restriction. This may be done.

[0009] In order to achieve the above object, an accident analysis method according to a second aspect of the present invention comprises: An analysis step of analyzing the situation of the accident caused by the accident vehicle based on vehicle data measured by a sensor equipped in the accident vehicle and video data captured by a camera equipped in the accident vehicle, The video data includes fear level setting information indicating whether the video data is a fearful video that may impose a mental burden on the operator, In the analysis step, when the fear level setting information included in the video data indicates that the video data is a fearful video, display of the video data is restricted in the analysis of the accident situation until the restriction is released by a user having specific authority, and when the restriction is not released by the user having specific authority, the analysis of the accident situation caused by the accident vehicle is terminated. It is characterized by:

[0010] In order to achieve the above object, a program according to a third aspect of the present invention comprises: Computer, The vehicle accident information acquisition unit 100 functions as an analysis unit that analyzes the situation of the accident caused by the accident vehicle based on vehicle data measured by a sensor equipped in the accident vehicle and video data captured by a camera equipped in the accident vehicle; The video data includes fear level setting information indicating whether the video data is a fearful video that may impose a mental burden on the operator, When the fear level setting information included in the video data indicates that the video data is a fearful video, the analysis means restricts display of the video data in the analysis of the accident situation until the restriction is released by a user having specific authority, and when the restriction is not released by the user having specific authority, ends the analysis of the accident situation caused by the accident vehicle. It is characterized by: Effect of the Invention

[0011] According to the present invention, it is possible to provide an accident analysis device, an accident analysis method, and a program that can reduce the mental burden on an operator. [Brief description of the drawings]

[0012] [Figure 1] 1 is a diagram illustrating an example of an accident analysis system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a schematic diagram showing the state facing forward from inside the vehicle in this embodiment. [Diagram 3] FIG. 1 is a functional block diagram of a drive recorder according to an embodiment of the present invention. [Figure 4] 2 is a functional block diagram of a general center server according to the present embodiment. FIG. [Diagram 5] FIG. 2 is a diagram showing a processing flow according to the present embodiment. [Figure 6] 11 is a diagram showing an example of the configuration of a screen displayed on a terminal device of a general center in the present embodiment. FIG. [Figure 7] FIG. 4 is a diagram showing an analysis process flow according to the present embodiment. [Figure 8] FIG. 2 is a diagram showing a processing flow according to the present embodiment. [Figure 9] FIG. 2 is a diagram illustrating an example of a hardware configuration of the accident analysis device according to the present embodiment. [Figure 10] FIG. 2 is a functional block diagram of the accident analysis device according to the present embodiment. [Figure 11] 4 is a flowchart showing an outline of a processing procedure when the accident analysis device according to the present embodiment analyzes the circumstances of an accident. [Figure 12] FIG. 4 is a diagram showing an example of the configuration of a screen displayed on a terminal in the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals.

[0014] FIG. 1 is a diagram showing an example of an accident analysis system according to the present embodiment. In the accident analysis system 1 according to the present embodiment, a drive recorder 1100 (see FIG. 2) is mounted on a vehicle 1000 of an insurance policyholder, and the drive recorder 1100 is connected to a cloud storage server (not shown) and a general center server 30 via a network (including a public line network, etc.) by wireless communication. Note that in the present embodiment, an example is shown in which the drive recorder 1100 is connected to a cloud storage server (not shown) and a general center server 30 via a network (including a public line network, etc.) by wireless communication, but for example, a dedicated mirror-type terminal device having similar functions may be prepared and installed instead of the mirror 1300.

[0015] A data storage area for this customer service is secured in the cloud storage server. More specifically, a data storage area accessible by the general center server 30 or the like is secured for each drive recorder 1100 mounted in the vehicle 1000.

[0016] The general center server 30 is composed of one or more computers, and is connected to a terminal device (not shown) installed in the general center and operated by each operator of the general center. The operator of the general center can communicate with the drive recorder 1100 installed in the vehicle 1000, road service providers, and emergency services (fire departments and private emergency service providers) using, for example, a headset connected to the terminal device.

[0017] Although not shown, a road service provider system and an emergency service system are also connected to the network, and these systems also acquire data from a data storage area designated in the cloud storage server in response to a request from the general center server 30. Also, an accident analysis device 10 and a terminal 20 are connected to the network, as shown in FIG.

[0018] The accident analysis device 10 has a function of acquiring vehicle data measured by sensors equipped in the accident vehicle 1000 (which may be referred to as the "own vehicle" in the following description for convenience) and video data captured by a camera equipped in the drive recorder 1100 of the vehicle 1000 from a cloud storage server via a network, and analyzing the circumstances of the accident caused by the vehicle 1000 based on the acquired vehicle data and video data.

[0019] The terminal 20 is a terminal operated by, for example, an operator of an insurance company, and displays the accident situation analyzed by the accident analysis device 10, accident cases corresponding to the accident conditions, and images generated by the accident analysis device 10. The terminal 20 can be any information processing device equipped with a display, such as a PC, a notebook PC, a tablet terminal, or a smartphone.

[0020] FIG. 2 shows the state of the vehicle 1000 as viewed from inside the vehicle 1000 in the forward direction. The drive recorder 1100 includes a camera, and as shown in the figure, is attached to the front portion or windshield of the vehicle 1000 so as to be able to capture images at least in the traveling direction of the vehicle 1000. The camera may be capable of capturing images in the side direction and rear direction of the vehicle 1000. As shown in FIG. 2, a well-known automatic diagnostic system 1400 (for example, an OBD (On-Board Diagnostic system-II)) is installed inside the vehicle 1000, and the automatic diagnostic system 1400 is connected to the drive recorder 1100.

[0021] 3 shows a functional block diagram of the drive recorder 1100 according to the present embodiment. The drive recorder 1100 mounted on the vehicle 1000 includes a first communication unit 1110, a second communication unit 1120, a positioning unit 1130, a video recording unit 1140, a sound recording unit 1150, an acceleration measurement unit 1160, an automatic diagnosis data acquisition unit 1170, a control unit 1180, and a data storage unit 1200.

[0022] The control unit 1180 is composed of processors such as a CPU (Central Processing Unit) and a GPU (Graphical processing unit), and causes each component to execute processing related to the customer service.

[0023] The first communication unit 1110 is a communication unit for communicating with a general center, for example, by VoIP (Voice over Internet Protocol), or may be a calling function of a general mobile phone. The second communication unit 1120 has a function for transmitting data to a cloud storage server, for example, in packets.

[0024] Furthermore, when instructed by the control unit 1180, the positioning unit 1130 acquires the absolute position (for example, latitude and longitude) of the vehicle 1000 using, for example, a Global Positioning System (GPS), and stores it in the data storage unit 1200.

[0025] The recording unit 1140 stores, for example, video data captured by a camera mounted on the drive recorder 1100 in the data storage unit 1200. The sound recording unit 1150 stores sound data input from a microphone in the data storage unit 1200. The sound recording unit 1150 may be integrated with the recording unit 1140. The recording unit 1140 records continuously when instructed to operate by the control unit 1180, for example, and stores the recorded data in the data storage unit 1200. The control unit 1180 is capable of extracting both video data for a certain period of time before a specific time and video data for a certain period of time after the specific time. The same applies to the sound recording unit 1150. The recording unit 1140 is capable of capturing video images of the outside of the vehicle 1000 and video images of the inside of the vehicle 1000.

[0026] The acceleration measuring unit 1160 measures the value of acceleration using, for example, an acceleration sensor, and outputs the value to the control unit 1180. When instructed by the control unit 1180, the automatic diagnosis data acquiring unit 1170 acquires automatic diagnosis data from the automatic diagnosis system 1400 installed inside the vehicle 1000.

[0027] The data storage unit 1200 is composed of storage devices such as memory, HDD (Hard Disk Drive) and / or SSD (Solid State Drive), and stores in advance equipment data such as company name, organization name, vehicle registration number, driver identifier (ID), telephone number, etc., and also stores data acquired by each component in response to instructions from the control unit 1180.

[0028] FIG. 4 shows a functional block diagram of the general center server 30. The general center server 30 has, as functional units, a receiving unit 311, a vehicle extraction unit 312, a policyholder database (DB) 313, a data acquisition unit 314, a data storage unit 315, a data output processing unit 316, an input processing unit 317, an analysis processing unit 318, an external notification processing unit 319, a response data storage unit 320, a call processing unit 321, and an insurance company notification unit 322. The general center server 30 has a processor such as a central processing unit (CPU) and a graphical processing unit (GPU), a memory, a storage device such as a hard disk drive (HDD) and / or a solid state drive (SSD), a communication interface (IF) for wired or wireless communication, an input device for accepting input operations, and an output device for outputting information, which work together to realize these functional units. Note that the functions of the general center server 30 may be realized in cooperation with a terminal device, and therefore there may be a function provided on the terminal device side.

[0029] The receiving unit 311 accepts an incoming call from the drive recorder 1100 addressed to a specific phone number, identifies the phone number of the drive recorder 1100 by caller ID notification, and outputs the phone number to the vehicle extraction unit 312. The receiving unit 311 transfers the incoming call from the drive recorder 1100 to the terminal device of an available operator based on predetermined rules.

[0030] The contractor DB 313 stores, for example, a telephone number, contract data, and access information (for example, a URI (Uniform Resource Identifier)) for identifying a data storage area in a cloud storage server in association with each other. At least a part of the access information may be identified by some function based on the telephone number, the vehicle registration number, etc.

[0031] The vehicle extraction unit 312 reads out the contract data and access information stored in the subscriber DB 313 from the telephone number of the drive recorder 1100, outputs the contract data and access information to the data output processing unit 316, and outputs the access information to the data acquisition unit 314.

[0032] The data acquisition unit 314 acquires data from a data storage area in the cloud storage server based on the access information, and stores the data in the data storage unit 315. The data output processing unit 316 executes processing for outputting the contract data and the data stored in the data storage unit 315 to the terminal device to which the incoming call is to be forwarded, as determined by the receiving unit 311.

[0033] The analysis processing unit 318 performs a predetermined analysis process on the video data stored in the data storage unit 315, and outputs the analysis result to a terminal device via the data output processing unit 316. The external notification processing unit 319 transmits data including access information and information for contacting the vehicle 1000 (such as the telephone number of the drive recorder 1100) to a road service provider system or an emergency organization system. The call processing unit 321 executes a process for making a call to the drive recorder 1100 in the vehicle 1000.

[0034] The input processing unit 317 causes the data output processing unit 316, the analysis processing unit 318, the external notification processing unit 319, the call processing unit 321, etc. to perform processing in response to an instruction or input from the terminal device. The input processing unit 317 also stores data on the action taken in response to an incoming call from the drive recorder 1100 in the action data storage unit 320. The data stored in the action data storage unit 320 includes access information and contract data, and may also include text data input in the terminal device.

[0035] The insurance company notification unit 322 performs processing such as sending an email to the insurance company (agency) that sold the automobile insurance related to the vehicle 1000 in which the accident occurred, based on the data stored in the response data storage unit 320. This allows information to be shared with the insurance company.

[0036] Next, the processing contents from the occurrence of an accident to the notification to an insurance company in the accident analysis system shown in FIG. 1 will be described with reference to FIG. 5 to FIG.

[0037] The control unit 1180 continuously causes the acceleration measurement unit 1160 to measure the acceleration, and determines whether or not the measured acceleration is equal to or greater than a first threshold value that has been determined in advance. Here, it is assumed that the control unit 1180 has detected an acceleration equal to or greater than the first threshold value (FIG. 5: step S100).

[0038] When acceleration equal to or greater than a second threshold smaller than the first threshold and less than the first threshold is detected, a button for manually calling the general center may be displayed on the display device. In this case, a call is made to the general center's regular phone number, which is different from the phone number used when acceleration equal to or greater than the first threshold is detected. The general center responds with regular operations. In other cases, the drive recorder 1100 may be allowed to call the general center.

[0039] When an acceleration equal to or greater than the first threshold is detected, the control unit 1180 reads out the equipment data from the data storage unit 1200 and extracts the vehicle data including the impact event data, and the video data, etc. (step S101). The impact event data includes the date and time acquired from the clock, the position data acquired by the positioning unit 1130, the detected acceleration, and the automatic diagnosis data acquired by the automatic diagnosis data acquisition unit 1170. The video data includes the video data captured by the video recording unit 1140 and the sound data recorded by the sound recording unit 1150. As described above, the video data includes the video data, etc., for a certain period of time before the acceleration equal to or greater than the first threshold is detected, and the video data, etc., for a certain period of time after the detection. The automatic diagnosis data includes data indicating the presence or absence of damage to each of the engine, the battery, the fuel system, etc. The equipment data and the impact event data are referred to as vehicle data.

[0040] Then, the control unit 1180 transmits the extracted data (vehicle data (equipment data, impact event data) and video data, etc.) to the cloud storage server through the second communication unit 1120 (step S102). Note that the processes of steps S100 to S102 may be performed manually, for example, when an acceleration equal to or greater than a second threshold value that is smaller than the first threshold value and less than the first threshold value is detected.

[0041] When the cloud storage server receives the extracted data from the drive recorder 1100, it stores the data in a data storage area specified by, for example, the vehicle registration number, the telephone number, and the like included in the device data (step S103).

[0042] For convenience of explanation, this is described after step S103, but after step S100, the control unit 1180 causes the positioning unit 1130 to acquire position data at regular intervals, for example, and determines whether the vehicle 1000 is moving each time. If the vehicle 1000 moves a predetermined distance (for example, 200 m) or more from the position in step S100, acceleration equal to or greater than the first threshold value can be regarded as some kind of erroneous detection. Therefore, in this case, the automatic call to the general center is stopped.

[0043] That is, the control unit 1180 constantly determines whether the call stop condition is satisfied (step S104), and when the call stop condition is satisfied, stops the process (step S105). Note that when the call stop condition is satisfied before the transmission of the extracted data to the cloud storage server, the transmission of the extracted data may also be stopped.

[0044] On the other hand, if the call stop condition is not satisfied, the control unit 1180 causes the first communication unit 1110 to automatically call the general center (step S106). If an accident occurs, the driver may be injured or too upset to speak, so even if an operator at the general center receives the call, a mechanical voice is played. The operator at the general center recognizes from the mechanical voice that an operation according to this embodiment is required.

[0045] As will be described later, a callback will be made if the operator at the general center deems it necessary, and at that time a conversation will take place between the driver and the operator.

[0046] The automatic call to the general center and the transmission of the extracted data to the cloud storage server may be performed in parallel, or may be performed in the reverse order to that shown in FIG.

[0047] The receiving unit 311 of the general center server 30 receives the call from the vehicle 1000 (step S107), and outputs the telephone number obtained by the caller ID notification to the vehicle extraction unit 312. The vehicle extraction unit 312 reads out the contract data and access information by searching the contractor DB 313 by the telephone number, outputs the access information to the data acquisition unit 314, and outputs the contract data and access information to the data output processing unit 316.

[0048] The data acquisition unit 314 uses the access information identified based on the telephone number to request the stored extracted data from the cloud storage server (step S108).

[0049] When the cloud storage server receives the request for the extracted data from the general center server 30, it reads the extracted data from the data storage area specified by the access information and transmits it to the general center server 30 (step S109).

[0050] When the data acquisition unit 314 receives the extracted data from the cloud storage server, it stores the data in the data storage unit 315 (step S110). Then, the data output processing unit 316 displays the extracted data and the contract data on the terminal device determined by the receiving unit 311 (step S111).

[0051] A configuration example of a display screen in a terminal device is shown in Fig. 6. In the example of Fig. 6, a contract data display field 3101, a video display field 3102, an analysis instruction button 3103, a fear level setting value display field 3104, a fear level setting value up button 3105, a fear level setting value down button 3106, a fear level setting button 3107, an analysis result display field 3108, a vehicle data (equipment data and impact event data) display field 3109, a callback instruction button 3110, a road service request button 3111, a rescue request button 3112, a response data input field 3113, an end button 3114, a registration button 3115, and the like are included.

[0052] The contract data display field 3101 displays at least a portion of the data extracted from the contract holder DB 313. The video display field 3102 displays the video data received from the vehicle 1000. The vehicle data (equipment data and impact event data) display field 3109 displays at least a portion of the equipment data and impact event data. After listening to the mechanical voice sent from the drive recorder 1100, the operator of the terminal device checks the information displayed on such a display screen and determines the need for a callback, etc.

[0053] Further, the operator of the terminal device visually checks the video data displayed in the video display field 3102 and judges whether it is a shocking video such as a fatal accident, that is, whether it is a scary video. For example, the operator of the terminal device judges whether it is a scary video according to a predetermined manual, and when it is judged to be a scary video, sets the fear level setting information indicating that it is a scary video. Specifically, the operator of the terminal device clicks the fear level setting value up button 3105 or the fear level setting value down button 3106 according to the fear level, such as a fear level of "3" for a video of a fatal accident, a fear level of "2" for a video with heavy bleeding, and a fear level of "1" for a video of only a bone fracture, to display a fear level setting value according to the fear level in the fear level setting value display field 3104, and sets the fear level setting information of the fear level setting value by clicking the fear level setting button 3107. Note that the fear level setting value is initially set to "0". In this embodiment, when the fear level setting value is set to "1" or more, the fear level setting information indicates that the video is a scary video, and when the fear level setting value is set to "0", the fear level setting information indicates that the video is not a scary video. As will be described in detail later, the fear level setting information is associated with the video data, as well as with information such as identification information for identifying the accident and the date and time of the accident, and is registered in a cloud storage server. The fear level setting values ​​of "0" to "3" correspond to multiple levels of setting values ​​according to the fear level of the scary video.

[0054] Incidentally, in the countermeasure data input field 3113, predetermined items (for example, no accident / accident) may be inputted by checking a check box.

[0055] In this embodiment, for example, when the operator clicks the analysis instruction button 3103, the input processing unit 317 causes the analysis processing unit 318 to perform analysis processing (step S112). The analysis processing may be automatically executed without an instruction from the operator.

[0056] An example of the analysis process will be described with reference to Fig. 7. The analysis processing unit 318 searches for a predetermined collision sound, for example, from sound data, and judges the presence or absence of an accident (more specifically, the probability of an accident, for example, the level of possibility of an accident) depending on the presence or absence of the predetermined collision sound, and outputs the judgment result to the data output processing unit 316 as the analysis result (step S31).

[0057] Furthermore, the analysis processing unit 318 determines the distance to an external object (an object other than the vehicle 1000) from the external video data (video data outside the vehicle 1000 captured by the recording unit 1140), determines whether or not an accident has occurred (more specifically, the probability of an accident) based on the distance to the external object (e.g., the shortest distance), and outputs the determination result to the data output processing unit 316 as the analysis result (step S32).

[0058] Furthermore, the analysis processing unit 318 determines whether the vehicle can run on its own, whether repairs are necessary, etc., from the automatic diagnosis data, and outputs the determination result as the analysis result to the data output processing unit 316 (step S33). For example, based on the presence or absence of damage to the engine, the battery, and the fuel system, it determines whether a tow truck is necessary (whether the vehicle can run on its own), whether repairs are necessary even if the vehicle can run on its own, etc.

[0059] Furthermore, the analysis processing unit 318 extracts passenger information from the internal video data (video data of the inside of the vehicle 1000 captured by the recording unit 1140) and outputs the analysis result to the data output processing unit 316 (step S34). For example, face recognition technology is used to extract the number of passengers, the age group of the passengers, the passengers' riding positions, etc. This information is used by the operator to determine whether or not to request rescue.

[0060] These are just some examples of the analysis processing, and other different processing may be added. For example, in the case of a three-axis sensor, values ​​for each axis are obtained for acceleration data, and based on these, the collision direction, the collision location on the vehicle, and other information may be extracted. Furthermore, instead of performing analysis processing for each type of data, the data may be combined to determine the probability of an accident. Furthermore, some, but not all, of these may be performed.

[0061] Returning to FIG. 5, when such an analysis process is performed, data output processing unit 316 displays the analysis result in analysis result display field 3108 shown in FIG. 6 (step S113).

[0062] Based on such display contents, the operator judges whether a response including a callback is necessary. If it is judged that a response including a callback is not necessary, the operator clicks the end button 3114. The input processing unit 317 judges that a response is not necessary in response to the instruction to end (step S114: No route) and ends the subsequent processing (step S115). Note that in this embodiment, when a response including a callback is not necessary, the processing of step S209 (see FIG. 8) described later is not executed, and the fear level setting value is not set (i.e., the initial value is "0" and the fear level setting information means that the image is not a scary image), but for example, even when a response including a callback is not necessary (step S114: No route), the processing of step S209 may be executed and then the processing may be ended.

[0063] On the other hand, if the operator determines that a response including a callback is necessary, he / she clicks, for example, a callback instruction button 3110. Then, the input processing unit 317 determines that a response is necessary (step S114: Yes route), and the process proceeds to the process in FIG.

[0064] Shifting to the explanation of the processing in FIG. 8, in response to clicking of the callback instruction button 3110, the input processing unit 317 outputs the telephone number of the drive recorder 1110 to the call processing unit 321 and makes a call to that telephone number (step S200).

[0065] The operator and the driver or passenger of the vehicle 1000 confirm the situation through a telephone call. Specifically, the operator confirms whether an accident has occurred, whether there are any injuries, and whether road service is necessary (need for a tow truck, need for repairs, etc.). At this point, various kinds of advice may be given to the driver or passenger.

[0066] If it is confirmed that there is no accident, then, for example, "no accident" is entered in the countermeasure data input field 3113 shown in FIG. 6, and the process ends.

[0067] If the occurrence of an accident is confirmed, for example, the occurrence of the accident is entered in a countermeasure data input field 3113. If details of the accident are heard, the details may be entered in the countermeasure data input field 3113. On the other hand, if the operator determines from the call that road service is necessary, he or she clicks a road service request button 3111.

[0068] Returning to Fig. 8, when the road service request button 3111 is clicked, the input processing unit 317 determines that road service is to be requested (step S201: Yes route), and causes the external notification processing unit 319 to notify the road service provider system of the access information for the extracted data, personal contact data (such as the phone number of the drive recorder 1100), etc. (step S202). The notification may include data on the possibility of self-driving and repair (such as the analysis result or the confirmation result by phone call). In addition, a phone call may be made to the road service provider.

[0069] The road service provider system receives the access information, contact personal data, etc. of the extracted data from the general center server 30, and stores them in the data storage unit (step S203). The road service provider provides road service based on the data, etc. stored in the cloud storage server (step S204). For example, it calls the drive recorder 1100 and dispatches a tow truck or other vehicle to the location included in the equipment data.

[0070] Regardless of whether road service is not requested (step S201: No route) or requested (step S201: Yes route), if the operator determines from the call that rescue is necessary, he or she clicks the rescue request button 3112 shown in FIG.

[0071] When the rescue request button 3112 is clicked, the input processing unit 317 determines that rescue is to be requested (step S205: Yes route), as shown in Fig. 8, and causes the external notification processing unit 319 to notify the emergency service system of the access information of the extracted data, the personal contact data, etc. (step S206). The notification may include passenger information (analysis results or confirmation results by phone call (degree of injury, etc.)). Additionally, a phone call may be made to the emergency service. If rescue is not to be requested (step S205: No route), the process proceeds to step S209.

[0072] The emergency service system receives the access information of the extracted data, the contact personal data, etc. from the general center server 30, and stores them in the data storage unit (step S207). The rescue service dispatches an ambulance based on the data stored in the cloud storage server (step S208).

[0073] After taking such measures, the operator of the terminal device inputs the response data such as whether or not a road service is requested and whether or not a rescue is requested into the response data input field 3113 in Fig. 6, and clicks, for example, the registration button 3115. Then, the response data input from the terminal device is output to the input processing unit 317 of the general center server 30.

[0074] Whether or not rescue is requested (step S205: No route), the operator determines whether the video data displayed in the video display area 3102 shown in FIG. 6 is a scary video, and clicks the fear level setting value up button 3105, the fear level setting value down button 3106, etc. to set the fear level setting value (step S209).

[0075] Specifically, in step S209, when the fear level setting value up button 3105 or the fear level setting value down button 3106 is clicked, the value of the fear level (fear level setting value) displayed in the fear level setting value display field 3104 changes. Then, when the fear level setting button 3107 is clicked by the operator, the fear level setting value is set. In this embodiment, when the fear level setting button 3107 is clicked, the fear level setting information of the displayed fear level setting value is output to the input processing unit 317 of the general center server 30, and the fear level setting information is associated with the target extracted data (more specifically, the target video data) stored in the data storage area of ​​the cloud storage server. Note that in step S209, the general center server 30 may associate the fear level setting information with the video data received from the cloud storage server, and store the video data and the fear level setting information in the data storage area of ​​the cloud storage server.

[0076] The input processing unit 317 acquires, for example, access information, contract data, etc. from the data output processing unit 316, and stores them in the response data storage unit 320 together with the fear level setting information and response data associated with the video data (step S210).

[0077] If the handling data includes data indicating that an accident has occurred, the insurance company notification unit 322 identifies an email address from, for example, the insurance company code (agency code) included in the contract data, and sends a notification of the completion of the initial response to the accident to the insurance company (agency) (step S211). This notification may include, for example, access information, so that the insurance company (agency) can also check the data stored in the data storage area of ​​the cloud storage server.

[0078] In this way, information is shared, and the insurance company (agency) can promptly carry out its activities. A similar notification may be sent to other relevant parties, such as the safe driving manager of the company to which the driver of the vehicle 1000 belongs. By carrying out the above-mentioned processing, various customer services can be promptly and appropriately provided when an accident occurs.

[0079] In particular, by storing data in a cloud storage server, data can be shared not only with call centers, but also with road service, emergency services, and insurance companies (agents), enabling necessary services to be provided appropriately.

[0080] Also, although the service is initiated by the operator at the general center, the analysis processing unit 318 appropriately assists the operator in making decisions, which not only eliminates unnecessary callbacks but also makes it possible to avoid placing an excessive burden on the driver or passengers of the vehicle 1000 in the event of an accident. In other words, conversations that focus on the key points can be held.

[0081] The recording unit 1150 continues recording even after the data is sent to the cloud storage server by the control unit 1180, records the exchanges with the parties involved in the accident and the police and fire department after the accident occurs, and stores the recorded data separately in the cloud storage server. This may be used to give advice on insurance coverage to the driver, etc. In addition, even after the conversation with the driver, etc. is finished upon a callback from the call center, the line may be left connected so that the operator can check the surrounding sounds in real time and give advice to the driver, etc.

[0082] The data stored in the cloud storage server is later downloaded to the accident analysis device 10 installed in the accident response department of the insurance company and used to analyze the accident situation for insurance payment handling such as fault ratio negotiations. Acceleration data and the like contained in the video data and vehicle data stored in the cloud storage server may be used to classify accident types and predict accident causes and damage amounts.

[0083] Next, analysis of accident circumstances by the accident analysis device 10 in the accident analysis system shown in FIG. 1 will be described with reference to FIGS.

[0084] As described above, the accident analysis device 10 has a function of acquiring vehicle data and video data from a cloud storage server via a network, and analyzing the situation of an accident caused by the vehicle 1000 based on the acquired vehicle data and video data. The accident analysis device 10 has a function of searching for an accident case corresponding to the situation of an accident caused by the vehicle 1000 by comparing the situation of the accident acquired by the analysis with an accident case database in which the situation of accidents that have occurred in the past and information on past accident cases (hereinafter referred to as "accident cases") are associated with each other. The accident analysis device 10 also has a function of generating an image showing the situation of an accident caused by the vehicle 1000 by mapping the position of the vehicle 1000 and the position of another vehicle acquired by analyzing the situation of the accident on map data. The image showing the situation of an accident caused by the vehicle 1000 may be any type, and may be, for example, an overhead view or a video.

[0085] The accident analysis device 10 may be configured from one or more physical information processing devices such as a mainframe, a workstation, or a personal computer (PC), or may be configured using a virtual information processing device that operates on a hypervisor, or may be configured using a cloud server.

[0086] 9 is a diagram showing an example of a hardware configuration of the accident analysis device 10. The accident analysis device 10 includes a processor 11 such as a CPU (Central Processing Unit) or a GPU (Graphical processing unit), a storage device 12 such as a memory, an HDD (Hard Disk Drive) and / or an SSD (Solid State Drive), a communication IF (Interface) 13 for wired or wireless communication, an input device 14 for accepting an input operation, and an output device 15 for outputting information. The input device 14 is, for example, a keyboard, a touch panel, a mouse, and / or a microphone. The output device 15 is, for example, a display and / or a speaker.

[0087] FIG. 10 is a functional block diagram of the accident analysis device 10 according to the present embodiment. The accident analysis device 10 includes a storage unit 100, an acquisition unit 101, an analysis unit 102, a generation unit 103, a search unit 104, and an output unit 105. The storage unit 100 can be realized by using a storage device 12 included in the accident analysis device 10. The acquisition unit 101, the analysis unit 102, the generation unit 103, the search unit 104, and the output unit 105 can be realized by the processor 11 of the accident analysis device 10 executing a program stored in the storage device 12. The program can be stored in a storage medium. The storage medium storing the program may be a non-transitory computer readable storage medium. The non-transitory storage medium is not particularly limited, and may be, for example, a storage medium such as a USB memory or a CD-ROM.

[0088] The storage unit 100 stores an accident case database (DB) that associates accident situations with accident cases of the accidents, and a map data DB. The accident case DB may include information indicating the fault ratio. The accident cases and fault ratios corresponding to the situations of the accidents that have occurred may be searchable using information indicating the accident situations as a key. The map data DB includes various data such as road data, road width, direction of travel, road type, traffic signs (stop, no entry, etc.), speed limits, traffic light positions, and the number of intersecting roads at intersections. The storage unit 100 may be realized by an external server that can communicate with the accident analysis device 10. Although not shown in the figure, the storage unit 100 stores operator information about the insurance company's operators.

[0089] The acquisition unit 101 has a function of acquiring vehicle data and video data measured and captured by the vehicle 1000 (accident vehicle) from a cloud storage server.

[0090] The analysis unit 102 has a function of analyzing the situation of an accident caused by the vehicle 1000, based on the vehicle data and video data acquired by the acquisition unit 101. The situation of the accident analyzed by the analysis unit 102 may include at least the color of the traffic light when the vehicle 1000 passes through an intersection, the priority relationship when passing through the intersection, and whether or not the vehicle speed of the vehicle 1000 exceeds the speed limit.

[0091] Furthermore, the vehicle data of the vehicle 1000 includes at least information indicating the absolute position of the vehicle 1000 measured by the GPS of the positioning unit 1130, and the analysis unit 102 may estimate the absolute position of the other vehicle based on the information indicating the absolute position of the vehicle 1000 (position data acquired by the positioning unit 1130) and information indicating the relative positional relationship between the vehicle 1000 and the other vehicle, which is obtained by analyzing an image of the other vehicle captured in the image data. Furthermore, the analysis unit 102 may estimate the absolute positions of the vehicle 1000 and the other vehicle in time series.

[0092] In addition, the analysis unit 102 may estimate the absolute position of the vehicle 1000 by analyzing the video data, and may analyze the circumstances of the accident by averaging the absolute position of the accident vehicle estimated by analyzing the video data and the absolute position of the vehicle 1000 measured by the positioning unit 1130 based on a predetermined weight, and considering this absolute position as the absolute position of the vehicle 1000.

[0093] In addition, the analysis unit 102 may analyze the circumstances of the accident by comparing the image size of the part of the video data in which the other vehicle is captured with data indicating the correspondence between image size and distance, and estimating the distance between the vehicle 1000 and the other vehicle, which is one piece of information indicating the relative positional relationship between the vehicle 1000 and the other vehicle.

[0094] In addition, the analysis unit 102 may analyze the circumstances of the accident by comparing the difference between the coordinates of the point in the video data where the other vehicle is captured and the center coordinates of the video data with data indicating the correspondence between coordinates and angles, and estimating the angle difference between the direction of travel of the vehicle 1000 and the direction in which the other vehicle is located, which is one piece of information indicating the relative positional relationship between the vehicle 1000 and the other vehicle.

[0095] The generating unit 103 has a function of generating an image showing the situation of an accident caused by the vehicle 1000 by mapping the absolute position of the vehicle 1000 and the absolute positions of other vehicles on map data. The image may include an overhead view and a video. For example, the generating unit 103 may generate a video in which images showing the situation of the accident are arranged in chronological order.

[0096] The search unit 104 has a function of comparing the situation of the accident caused by the vehicle 1000 analyzed by the analysis unit 102 with an accident case DB (accident case data) in which the accident situation is associated with past accident cases, thereby searching for an accident case corresponding to the situation of the accident caused by the vehicle 1000. In addition, the search unit 104 may search for the fault ratio of the vehicle 1000 in the accident caused by the vehicle 1000 as an accident case corresponding to the situation of the accident caused by the vehicle 1000.

[0097] In addition, the accident case may include one or more correction ratios (correction information) for correcting the fault ratio. When a correction ratio corresponding to the situation of the accident caused by the accident vehicle is present among the one or more correction ratios, the search unit 104 may correct the fault ratio of the accident vehicle according to the correction ratio.

[0098] The output unit 105 has a function of outputting, to the terminal 20, information indicating the accident situation analyzed by the analysis unit 102, accident cases corresponding to the accident conditions searched for by the search unit 104, and images indicating the accident situations generated by the generation unit 103.

[0099] Note that the functions of the accident analysis device 10 may be realized in cooperation with the terminal 20, and therefore the functions may be provided on the terminal 20 side. Also, the accident analysis device 10 and the terminal 20 may be integrated into one information processing device.

[0100] Next, a processing procedure when the accident analysis device 10 analyzes the situation of an accident caused by the vehicle 1000 will be described with reference to Fig. 11. Fig. 11 is a flowchart showing an outline of a processing procedure when the accident analysis device 10 analyzes the situation of an accident. In the following description, it is assumed that the vehicle data and the video data each contain time information or synchronization information. That is, in this embodiment, when analyzing video data at a certain time point, it is possible to perform the analysis using the vehicle data corresponding to that time point, and conversely, when analyzing vehicle data at a certain time point, it is possible to perform the analysis using the video data corresponding to that time point.

[0101] First, the accident analysis device 10 acquires vehicle data of the vehicle 1000 that caused the accident and video data at the time of the accident (steps S10 and S11). Specifically, the accident analysis device 10 acquires the vehicle data and video data from a cloud storage server via a network. Alternatively, the vehicle data and video data may be recorded in a non-transient storage medium such as an SD card or a USB memory, and the vehicle data and video data may be imported into the accident analysis device 10 by connecting the recording medium to the accident analysis device 10. The vehicle data and video data may also be acquired from the general center server 30 via a network. When acquiring the video data in step S11, fear level setting information associated with the video data is also acquired. The processes of steps S10 and S11 correspond to a receiving means and a receiving step.

[0102] Next, the accident analysis device 10 acquires operator information indicating information of the operator of the terminal 20 that has accessed the accident analysis device 10 (step S12). The operator information includes operator identification information for identifying the operator and an acceptable set value, which is a set value of a scary image that the operator can tolerate. In step S12, for example, based on the operator identification information input to the accident analysis device 10 via the terminal 20, operator information corresponding to the operator identified by the operator identification information is acquired from the operator information previously stored in the storage unit 100. Note that, although an example in which the operator information is previously stored in the storage unit 100 has been shown in this embodiment, the operator information may be input to the accident analysis device 10 via the terminal 20. Note that, in step S12, it is sufficient to acquire at least the acceptable set value of the operator of the terminal 20 that has accessed the accident analysis device 10. Note that the process of step S12 corresponds to an acceptable set value acquisition means for acquiring the acceptable set value of the operator.

[0103] After executing the processing of step S12, the accident analysis device 10 compares the fear level setting value indicated by the fear level setting information associated with the video data acquired in step S11 with the acceptable setting value acquired in step S12, and determines whether the fear level setting value exceeds the acceptable setting value, i.e., whether the fear level setting value of the video data acquired in step S11 exceeds the operator's acceptable setting value (step S13).

[0104] If the fear level setting value exceeds the allowable setting value (step S13; Yes route), the accident analysis device 10 notifies the administrator of that fact (step S14). In step S14, for example, a message is sent to a pre-registered administrator terminal to the effect that the fear level setting value exceeds the allowable setting value, that is, to the effect that the display of the video data is restricted in the analysis of the accident situation. In this way, if the fear level setting value exceeds the allowable setting value, the video data acquired in step S11 is not displayed in the video display field 2102 shown in FIG. 12. In other words, if the fear level setting value exceeds the allowable setting value, the display of the video data is restricted. The process of step S14 corresponds to notifying a user having a specific authority of the effect that the display of the video data is restricted in the analysis of the accident situation.

[0105] On the other hand, when the fear level setting value is included in the allowable setting value (when it is equal to or less than the allowable setting value), the video data acquired in step S11 is displayed in the video display field 2102 shown in FIG. 12. FIG. 12 shows an example of the configuration of the display screen in the terminal 20. In the example of FIG. 12, a basic information display field 2101 for displaying basic information such as the date and time of the accident, a video display field 2102 for displaying the video data acquired in step S11, and a password input field 2112 for inputting a video display password are included. In addition to the example shown in the figure, a field for displaying items necessary for analyzing the accident and buttons for performing operations may be included. The password input field 2112 includes a decision button for deciding the entered password. When the fear level setting value exceeds the allowable setting value, the fact that the video data acquired in step S11 is not displayed in the video display field 2102 shown in FIG. 12 corresponds to restricting the display of the video data in the analysis of the accident situation when the setting value included in the fear level setting information included in the video data is not included in the allowable setting value of the operator specified by the allowable setting value acquisition means.

[0106] After step S14 in FIG. 11, the accident analysis device 10 judges whether or not the administrator has performed a release operation (step S15), and if so (step S15; Yes route), displays the video data acquired in step S11 in the video display field 2102 shown in FIG. 12 (step S16). In step S15, whether or not the administrator has performed a release operation is judged, for example, by whether or not a valid password has been entered in the password input field 2112 shown in FIG. 12. If a valid password has been entered, it may be judged that the release operation has been performed. Note that in the present embodiment, an example in which the administrator performs a release operation by entering a valid password has been shown, but this is not limiting, and for example, the administrator may be allowed to change the fear level setting value. Specifically, if the fear level setting value indicated by the fear level setting information associated with the video data acquired in step S11 is "2" and the operator's allowable setting value is "1", the fear level setting value may be changed to "1" after the administrator enters a valid password. Then, after the fear level setting value has been changed by the administrator, the process may proceed to step S13. In addition, the administrator's release operation (more specifically, the operation of entering a valid password into the password input field 2112 shown in FIG. 12, or the operation of the administrator changing the fear level setting value) corresponds to the restriction being able to be released by a user with specific authority.

[0107] When the fear level setting value is included in the allowable setting value in step S13 (step S13; No route), or after executing the process of step S16, the accident analysis device 10 analyzes the accident situation while displaying the video data acquired in step S11 in the video display field 2102, searches for the corresponding accident case (step S17), and ends the process. On the other hand, when the administrator does not perform the release operation or the correct password is not input in step S15 (step S15; No route), the accident analysis device 10 analyzes the accident situation without displaying the video data acquired in step S11 in the video display field 2102, searches for the corresponding accident case (step S17), and ends the process. That is, when the fear level setting value exceeds the allowable setting value, and the administrator does not perform the release operation, the display of the video data is restricted. The process of step S17 corresponds to the analysis means and the analysis step.

[0108] In step S17, a number of processes are performed. For example, image analysis is performed on the video data at the time of the accident for each frame to identify one or more surrounding objects (other vehicles, people, signs, road structures, etc.) that exist around the vehicle 1000 that are captured in the image for each frame, and further, a process is performed to identify coordinates indicating the positions where the identified surrounding objects are captured in the images. Then, a process is performed to estimate the relative positional relationship between the vehicle 1000 and the surrounding objects that exist around the vehicle 1000 based on the coordinates of the identified surrounding objects.

[0109] In addition, the accident analysis device 10 estimates the absolute position of the vehicle 1000 using the position information of the vehicle 1000 acquired by the GPS of the positioning unit 1130 and / or the video data at the time of the accident, and performs a process of estimating the absolute positions of the surrounding objects present around the vehicle 1000 based on the estimated absolute position of the vehicle 1000 and the estimated relative positional relationship between the vehicle 1000 and the surrounding objects present around the vehicle 1000.

[0110] In addition, the accident analysis device 10 performs a process of generating an image (including an aerial view and a video) showing the accident situation by mapping the calculated absolute positions of the vehicle 1000 and surrounding objects around the vehicle 1000 onto map data, and performs a process of estimating the direction in which the vehicle 1000 collided with another vehicle or an obstacle (for example, a head-on collision) based on the acceleration in the forward / backward and left / right directions that occurred in the vehicle 1000 at the moment of the collision acquired by the acceleration sensor.

[0111] Next, the accident analysis device 10 performs a process of analyzing information indicating the situation of the accident caused by the vehicle 1000, using the vehicle data of the vehicle 1000, the video data at the time of the accident, the estimated absolute positions of the vehicle 1000 and the surrounding objects around the vehicle 1000, the estimated collision direction of the vehicle 1000, and the map data. The information includes a plurality of items (which may be called tags), and the situation of the accident is specified by a combination of the items. Next, the accident analysis device 10 performs a process of searching an accident case database using each item as a key to acquire an accident case corresponding to the situation of the accident caused by the vehicle 1000. Note that these processes may be performed in any order as long as no inconsistency occurs in the processes.

[0112] According to the embodiment described above, the accident analysis device 10 restricts the display of the video data when the fear level setting information associated with the acquired video data exceeds an allowable setting value for the operator of the terminal 20 that has accessed the accident analysis device 10. This makes it possible to prevent the operator from viewing a fearful video that exceeds the allowable range, thereby reducing the mental burden on the operator.

[0113] Furthermore, when the fear level setting information exceeds the allowable setting value of the operator, the accident analysis device 10 displays the video data if the administrator performs a release operation (more specifically, an operation of inputting a valid password into the password input field 2112 shown in FIG. 12 or an operation of changing the fear level setting value by the administrator). Therefore, the restriction can be released by the administrator's release operation, and the administrator can carry out the task of analyzing the accident situation while supporting the operator.

[0114] Furthermore, when the fear level setting information exceeds the allowable setting value of the operator, the accident analysis device 10 notifies the preregistered administrator terminal of a message indicating that the fear level setting value exceeds the allowable setting value, i.e., that the display of the video data will be restricted in the analysis of the accident situation. This allows the administrator to quickly support the operator.

[0115] (Modification) The present invention is not limited to the above-mentioned embodiment, and various modifications and applications are possible. For example, the vehicle 1000, the drive recorder 1100, the cloud storage server, the general center server 30, the accident analysis device 10, and the terminal 20 may not have all the technical features shown in the above-mentioned embodiment, and may have some of the configurations described in the above-mentioned embodiment so as to solve at least one problem in the conventional technology. In addition, at least a part of each of the following modifications may be combined.

[0116] In the above embodiment, the driving recorder 1100 is mounted on the vehicle 1000 of the policyholder, but this is just one example. The driving recorder 1100 may be replaced by a smartphone owned by the driver. The external video data and the internal video data may be captured by cameras mounted on the back and front of the smartphone.

[0117] In the above embodiment, the analysis processing unit 318 is provided in the general center server 30, but at least a part of the functions of the analysis processing unit 318 may be provided in the drive recorder 1100. For example, the analysis processing unit 318 may be provided in the drive recorder 1100 so as to automatically make a call only when it is determined that the level indicating the probability of an accident is equal to or higher than a predetermined level. Furthermore, passenger information may be extracted in advance, and such information may also be transmitted to the cloud storage server. Similarly, information indicating the need for repairs may be extracted in advance, and such information may also be transmitted to the cloud storage server.

[0118] The drive recorder 1100 or the general center server 30 may determine whether or not the service can be provided, for example, whether or not the contract period has expired.

[0119] In the above embodiment, in step S13 shown in FIG. 11, an example is shown in which it is determined whether the fear level setting value of the acquired video data exceeds the operator's tolerance range, but this is just one example. In step S13, for example, it may be determined whether the fear level setting value is "1" or more, that is, whether the fear level setting information indicates that the video data is a scary video, regardless of the operator's tolerance range. Then, if the fear level setting information indicates that the video data is a scary video, the process may proceed to step S14. According to this, if the fear level setting information associated with the video data received from the general center server 30 indicates that the video data is a scary video, the display of the video data is restricted in the analysis of the accident situation. Therefore, it is possible to prevent the operator from viewing the scary video, and the mental burden of the operator can be reduced. Note that determining whether the fear level setting value is "1" or more, that is, whether the fear level setting information indicates that the video data is a scary video, and restricting the display of the video data in the analysis of the accident situation when the fear level setting information included in the video data indicates that the video data is a scary video corresponds to restricting the display of the video data in the analysis of the accident situation when the fear level setting information included in the video data indicates that the video data is a scary video.

[0120] In the above embodiment, when the administrator does not perform the release operation or the correct password is not input in step S15 shown in Fig. 11 (step S15; No route), the accident situation is analyzed and a corresponding accident case is searched for in the process of step S17 without displaying the video data in the video display field 2102, but this is just one example. When the administrator does not perform the release operation or the correct password is not input in step S15 shown in Fig. 11 (step S15; No route), the process may be terminated without executing the process of step S17. In other words, when the video data is not displayed, the analysis of the accident situation and the search for the corresponding accident case may not be performed.

[0121] The accident analysis system 1 can be realized by using a normal computer, not a dedicated device. For example, the accident analysis system 1 that executes the above-mentioned processes may be configured by installing a program for executing any of the above-mentioned processes on a computer from a recording medium storing the program. Also, one accident analysis system 1 may be configured by multiple computers operating in cooperation with each other.

[0122] Furthermore, the method for supplying the program to the computer is arbitrary, and may be via a communication line, a communication network, a communication system, or the like.

[0123] Furthermore, in the case where an OS (Operating System) provides some of the above-mentioned functions, the functions other than those provided by the OS may be provided by a program.

[0124] The above-described embodiments are intended to facilitate understanding of the present invention, and are not intended to limit the present invention. The flow charts, sequences, elements included in the embodiments, and their arrangements, materials, conditions, shapes, sizes, etc. are not limited to those illustrated, and can be changed as appropriate. In addition, configurations shown in different embodiments can be partially substituted or combined with each other. [Explanation of symbols]

[0125] 1...accident analysis system, 10...accident analysis device, 11...processor, 12...storage device, 13...communication interface, 14...input device, 15...output device, 20...terminal, 30...general center server, 100...storage unit, 101...acquisition unit, 102...analysis unit, 103, 1200...generation unit, 104...search unit, 105...output unit, 311...reception unit, 312...vehicle extraction unit, 313...contractor data Database (DB), 314... data acquisition unit, 315, 1200... data storage unit, 316... data output processing unit, 317... input processing unit, 318... analysis processing unit, 319... external notification processing unit, 320... response data storage unit, 321... call processing unit, 322... insurance company notification unit, 1000... vehicle, 1100... drive recorder, 1110... first communication unit, 1120... second communication unit, 1130... positioning unit, 1140...recording unit, 1150...audio recording unit, 1160...acceleration measurement unit, 1170...automatic diagnosis data acquisition unit, 1180...control unit, 1300...mirror, 1400...automatic diagnosis system, 2101...basic information display field, 2102, 3102...video display field, 2112...password input field, 3101...contract data display field, 3103...analysis instruction button, 3104...fear level setting value display field, 3105...fear level setting value up button, 3106...fear level setting value down button, 3107...fear level setting button, 3108...analysis result display field, 3109...vehicle data (equipment data and impact event data) display field, 3110...callback instruction button, 3111...road service request button, 3112...rescue request button, 3113...response data input field, 3114...end button, 3115...registration button

Claims

1. An analysis means for analyzing the situation of the accident caused by the accident vehicle based on vehicle data measured by a sensor equipped in the accident vehicle and video data captured by a camera equipped in the accident vehicle, The video data includes fear level setting information indicating whether the video data is a fearful video that may impose a mental burden on the operator, When the fear level setting information included in the video data indicates that the video data is a fearful video, the analysis means restricts display of the video data in the analysis of the accident situation until the restriction is released by a user having specific authority, and when the restriction is not released by the user having specific authority, ends the analysis of the accident situation caused by the accident vehicle.

1. An accident analysis device comprising:

2. The fear level setting information includes a plurality of setting values ​​according to the fear level of the fear image, an allowable setting value acquisition means for acquiring the setting value allowable by the operator, the analysis means, when the setting value included in the fear level setting information included in the video data is not included in the setting value acceptable to the operator identified by the acceptable setting value acquisition means, restricts display of the video data in analyzing the accident situation; When the analysis means restricts the display of the video data in the analysis of the accident situation, the user having the specific authority can release the restriction or change the setting value to a value included in the setting value acceptable to the operator, the analysis means terminates the analysis of the situation of the accident caused by the accident vehicle when the display of the video data is restricted, when the restriction is not lifted by the user having the specific authority, or when the setting value is not changed to a value included in the setting value acceptable to the operator.

2. The accident analysis device according to claim 1 .

3. when the analysis means restricts the display of the video data in analyzing the accident situation, the user having the specific authority is notified of the restriction.

3. The accident analysis device according to claim 1 or 2.

4. An analysis step of analyzing the situation of the accident caused by the accident vehicle based on vehicle data measured by a sensor equipped in the accident vehicle and video data captured by a camera equipped in the accident vehicle, The video data includes fear level setting information indicating whether the video data is a fearful video that may impose a mental burden on the operator, In the analysis step, when the fear level setting information included in the video data indicates that the video data is a fearful video, display of the video data is restricted in the analysis of the accident situation until the restriction is released by a user having specific authority, and when the restriction is not released by the user having specific authority, the analysis of the accident situation caused by the accident vehicle is terminated.

1. An accident analysis method comprising:

5. Computer, The vehicle accident information acquisition unit 100 functions as an analysis unit that analyzes the situation of the accident caused by the accident vehicle based on vehicle data measured by a sensor equipped in the accident vehicle and video data captured by a camera equipped in the accident vehicle; The video data includes fear level setting information indicating whether the video data is a fearful video that may impose a mental burden on the operator, When the fear level setting information included in the video data indicates that the video data is a fearful video, the analysis means restricts display of the video data in the analysis of the accident situation until the restriction is released by a user having specific authority, and when the restriction is not released by the user having specific authority, ends the analysis of the accident situation caused by the accident vehicle. A program characterized by:

Images